Complete failure to start

The new linux client completely fails to start for me: no error messages I can find, just absolutely .., nothing. The start up script runs and lets me know its an alpha release, and then, that's all she wrote.

I am at a loss as to where to start debugging this.

I'm running Ubuntu 6.06 with an ATI Radion 9550.

Same here...

I had no problems running on GNU/Linux with 12.2.2.9 - sound working, okay textures - but suddenly everything stopped working after I downloaded 1.12.3.4 client. I don't know how to transfer my settings from the old client installation, so I just unpacked and ran the new client in a fresh directory. I got a login box, then the client successfully connects to SL, downloads cache texture, asks me about streaming music, even starts playing some music, and then exits without error messages. Any help will be appreciated.

Are you starting the game from a console? If not, try that and see if you can find an error message in the output after the game exits.

Already tried that: that's how I know the startup script executes (saying its alpha). But no error messages: just the execution of the script, and its done.

I suppose I could try executing the scripts commands by hand on the binary and see whether the binary will complain to me.

ADDED: I ran the script commands by hand and still got nothing, so I tried doing to the binary what it says not to do It replied:

muskie@esox:~/SecondLife/bin$ ./do-not-directly-run-secondlife-bin
./do-not-directly-run-secondlife-bin: error while loading shared libraries: libx mlrpc.so.0: cannot open shared object file: No such file or directory

I do not however know if that is interesting or if it is to be expected if you try to run the binary.

You must run the script, because it sets a few enviroment varibles that allow it to use the shipped libraries. It's why it says

do-not-directly-run-secondlife-bin

Damn good suggestion, isn't it?

Did you follow the thread as to why I ran it like that?

I was trying to tease out some kind of useful debugging information. I was not trying to actually "run" Secondlife.

Yes, the "Missing shared object" message is to be expected when you try running the binary yourself.

You could try the following to see, if that gives you a clue on what's happening:

cd ~/SecondLife/
LD_LIBRARY_PATH="`pwd`"/lib:"${LD_LIBRARY_PATH}" bin/do-not-directly-run-secondlife-bin

Maybe the error log doesn't get forwarded properly to stdout, so tee / cat can pick it up.

That at least gives me something:

muskie@esox:~/SecondLife$ LD_LIBRARY_PATH="`pwd`"/lib:"${LD_LIBRARY_PATH}" bin/do-not-directly-run-secondlife-bin
Segmentation fault

So I went a-digging through my system logs to see if there were any additional hints, and I found a bunch of interesting fglrx errors :/

Given that Ubuntu has released Edgy today I'm going to upgrade the whole thing (yeah, not a very courageous approach to a segfault). If the errors continue (and I have no reason to believe my beloved ATI card won't be producing plenty of additional errors for my debugging enjoyment...) I'll be back here with more confusion and perhaps even a useful idea or two.




tee/cat gave me nothing of interest (just what I've seen already).