|
|
|
ok, I've found a work around, I disabled quicktime with the -noquicktime comandline option and it is connecting perfectly (except I had to turn off vide ont he preferences to prevent crashing when there was video around, I'll be posting my system specs in a bit
erm, I can't edit comments? bollocks, I forgot to mention it seemed the issue was related to quicktime freezing sl during the login process and screwing it up
the info from about second life
Second Life 1.18.1 (134) Jul 27 2007 10:11:29 (Second Life Voice First Look) CPU: Intel Pentium 4 (Unknown model) (2999 MHz) what else is needed? Can we please clarify if Second Life is actually crashing on you (the viewer is quitting) or stalling at connect as you describe? It's not quite clear. We're going to import this and it may be worth looking deeper. Thanks for the info.
it stays running, but freezes for a few moments when quicktime is loading and then it goes to the "connecting to region" stage and won't go past it, the progress bar stays oscilating its brightness and if I click on the quit button SL will quit as expected, so it is responding
the crash I mentioned that happens when running the client without quictime seems to happen when there is a video stream on the parcel I'm in, and I think it might only happens when the stream gets played (by a script or otherwise), if necessary I can re-activate video and do more tests updated it to the current version onc emore
the problem is still here ont he new RC :/
chanegd the enviroment to reflect my current viewer, but it seems the problems happens opn more than one type of viewer
have you tried uninstalling quicktime and reinstalling it?
yes, including with the latest qt version (the oen that fixes the security hole), as well with using that QT Alternative thing, still can only login with the -noquicktime command line option :/
Hey, even with -noquicktime it still crashed, but I used -purge (to clear cached files) and I managed to login again and interesting enough I ended up in Cape Heaven, that was the same location I ended up when SL crashed a few days ago.
I tried the -purge but still hangs cause of qt if I don't disable it :\
with the RC now usign gstreamer, this issue isn't happening anymore (the issue involved quicktime, which isn't being used on the rc anymore), shoudl this be closed? if so, which of the closing options?
Resolved per TigroSpottystripes comment. Please reopen if you see this issue again.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
hanging at connecting to region unless the -noquicktime commandline option is used
"unknown circuit" search:
http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&query=%22unkown+circuit%22&summary=true&description=true&body=true
Just one issue there, probably not related.
"connecting to region" search:
http://jira.secondlife.com/secure/IssueNavigator.jspa?reset=true&&query=%22connecting+to+region%22&summary=true&description=true&body=true
SVC-53looks somewhat promising, but the log entries mentioned there don't really match what you've posted in the forum. Furthermore, in the last comment in the issue, Rob Linden has said that that issue has become so confused as to be useless, and he requests that we only link to it, rather than actually reopening it.So, I think that means that this is a new issue, and it shouldn't be closed as a duplicate. I'm going to create a link that says that this issue "relates to"
SVC-53, by clicking "link" on the left under Operations, and filling inSVC-53.Now, as to the issue itself...
You've provided some useful information in the forums, so I'm going to edit this issue and move that over here.
Now, we need a little more information. Please give a more detailed description of your computer, including your CPU speed/type, video card, amount of RAM, etc. Let us know if you're running any kind of firewall software. Since this is a network issue, give us a description of your internet connection, ie who your service provider is, and what boxes are between you and the internet, such as a cable modem, a linksys router, etc. Also, edit the description to let us know when this problem started, anything that might have changed just before that (ie a crash), and how often this happens (every time? Has it fixed yet?).
I think that should pretty much cover it. You can click "all" just above my comment to see the changes that I made to your issue in detail.