Jump to content

SL under Mageia KDE


Nightsy
 Share

You are about to reply to a thread that has been inactive for 3853 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

I'm running Mageia, and for the life of me cannot figure out how to get the SL viewer to work. I follow the instructions, unpack the files, but nothing happens when I click on the secondlife icon. It simply does nothing, where I understand it should be launching the viewer. No error messages appear, just... nothing.

 

Could  I be missing some dependencies?

Link to comment
Share on other sites

I'm running Mageia, and for the life of me cannot figure out how to get the SL viewer to work. I follow the instructions, unpack the files, but nothing happens when I click on the secondlife icon. It simply does nothing, where I understand it should be launching the viewer. No error messages appear, just... nothing.

 

Could  I be missing some dependencies?

Link to comment
Share on other sites


Nightsy wrote:

From a terminal, I get "command not found". It does not seem that the "secondlife" file is executable, no matter which viewer I try or how mant times I re-download the pack.

If that were the case, Mageia would have to be a lot more broken than I'd consider possible.

 

 

From a terminal, cd into the directory where the file is extracted and "ls -la secondlife" -- I'll be very surprised if it doesn't report "-rwxr-xr-x" ... and assuming it does: you know that the current directory is typically not in the default search path, right? so you'd have to issue "./secondlife" to execute it.

Link to comment
Share on other sites

Ah, the "./secondlife" does seem to do something, at least. Thanks for the tip, I did not find that yet in any other troubleshooter/manual I read on this.

 

The command does give this output:

"./secondlife: line 95: ./etc/register_secondlifeprotocol.sh: No such file or directory
./secondlife: line 98: ./etc/refresh_desktop_app_entry.sh: No such file or directory
./secondlife: line 138: bin/do-not-directly-run-secondlife-bin: No such file or directory
*** Bad shutdown ($LL_RUN_ERR). ***

You are running the Second Life Viewer on a x86_64 platform.  The
most common problems when launching the Viewer (particularly
'bin/do-not-directly-run-secondlife-bin: not found' and 'error while
loading shared libraries') may be solved by installing your Linux
distribution's 32-bit compatibility packages.
For example, on Ubuntu and other Debian-based Linuxes you might run:
$ sudo apt-get install ia32-libs ia32-libs-gtk ia32-libs-kde ia32-libs-sdl

*******************************************************
This is a BETA release of the Second Life linux client.
Thank you for testing!
Please see README-linux.txt before reporting problems."

 

So I suppose I will have to install the 32-bit compatibility packages and try again.

Link to comment
Share on other sites

That would be:

total 216
drwxr-xr-x 11   4096 Sep 25 21:45 ./
drwxrwxr-x  6   4096 Sep 30 20:04 ../
drwxr-xr-x  2     4096 Sep 12 06:07 app_settings/
drwxr-xr-x  2    4096 Sep 12 06:07 bin/
drwxr-xr-x  2    4096 Sep 12 06:07 character/
drwxr-xr-x  2    4096 Sep 12 06:05 etc/
-rwxr-xr-x  1     15841 Sep 12 05:43 featuretable_linux.txt*
drwxr-xr-x  2    4096 Sep 12 06:07 fonts/
-rwxr-xr-x  1     34253 Sep 12 05:43 gpu_table.txt*
-rwxr-xr-x  1     2375 Sep 12 05:43 install.sh*
drwxr-xr-x  2    4096 Sep 12 06:07 lib/
-rwxr-xr-x  1     35357 Sep 12 05:43 licenses.txt*
-rwxr-xr-x  1     3608 Sep 12 05:43 README-linux-joystick.txt*
-rwxr-xr-x  1     11191 Sep 12 05:43 README-linux.txt*
-rwxr-xr-x  1     3338 Sep 12 05:43 README-linux-voice.txt*
drwxr-xr-x  2    4096 Sep 12 06:05 res-sdl/
drwxr-xr-x  2     4096 Sep 25 21:45 Second/
-rwxr-xr-x  1      6306 Sep 12 05:43 secondlife*
-rwxr-xr-x  1      47946 Sep 12 05:43 secondlife_icon.png*
drwxr-xr-x  2     4096 Sep 12 06:07 skins/
-rw-r--r--  1    42 Sep 12 05:47 summary.json

 

Note that I removed my personal name from between those numbers :-).

Link to comment
Share on other sites

Aside from the "Second/" directory that looks fine. I've got no idea what Mageia broke there. For reference, this is what is in my bin/ and etc/ subdirectories:

bin/:total 54252-rwxr-xr-x 1 jennifer jennifer 50686923 Sep 11 22:07 do-not-directly-run-secondlife-bin-rwxr-xr-x 1 jennifer jennifer  3229276 Sep 11 22:07 linux-crash-logger.bindrwxr-xr-x 2 jennifer jennifer     4096 Sep 11 22:07 llplugin-rwxr-xr-x 1 jennifer jennifer  1166456 Sep 11 22:07 SLPlugin-rwxr-xr-x 1 jennifer jennifer   448627 Sep 11 22:07 SLVoice-rwxr-xr-x 1 jennifer jennifer     7431 Sep 11 21:43 update_installetc/:total 16-rwxr-xr-x 1 jennifer jennifer  248 Sep 11 21:43 handle_secondlifeprotocol.sh-rwxr-xr-x 1 jennifer jennifer 2611 Sep 11 21:43 launch_url.sh                                                                                              -rwxr-xr-x 1 jennifer jennifer 1041 Sep 11 21:43 refresh_desktop_app_entry.sh                                                                               -rwxr-xr-x 1 jennifer jennifer 1516 Sep 11 21:43 register_secondlifeprotocol.sh

 If there were missing 32bit libraries the viewer would/should crash with a missing library error. Just to make sure, the path it gives you in the error is correct, right?

When running "ldd bin/do-not-directly-run-secondlife-bin | grep 'not found'" I get the following list:

        libalut.so => not found        libcollada14dom.so => not found        libhunspell-1.3.so.0 => not found        libboost_program_options-mt.so.1.52.0 => not found        libboost_regex-mt.so.1.52.0 => not found        libboost_context-mt.so.1.52.0 => not found        libfmodex.so => not found        libGLOD.so => not found        libboost_thread-mt.so.1.52.0 => not found        libboost_filesystem-mt.so.1.52.0 => not found        libaprutil-1.so.0 => not found        libapr-1.so.0 => not found

 However, all those are in the lib/ subdirectory.

Anyway. I don't know enough about Mageia to figure out what broke where. All files seem to be where they should be.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 3853 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...