Linux Client alpha 1.12.3.6 available

You can get it from here!

Release Notes for Second Life 1.12.3(6) November 1, 2006
=====================================
Linux fixes:
* Assorted library fixes
* Work around an X bug in full-screen mouse handling

Other changes:
* Updated Mozilla libraries
* Clear Cache button also clears Mozilla cache
* Mac Mozilla browser profile no longer saved inside application bundle
* Browser agent string now identifies Second Life and SL Client version
* Mozilla lib version added to Help->About Second Life
* Added new user clothing to local files (speeds up appearance for new avatars)
* Terms of Service cannot be agreed to until the page has fully loaded

Bug fixes:
* Fixed crash when showing Profile
* Fixed various crashes on startup in MacOS
* Fixed changes not saved on gestures when edited within a prim
* Fixed new clothing appearing white on other avatars
* Disabled auto-detect hardware option on Mac - it's Windows-only
* Fixed login screen not launching links in new window on PPC Mac
* Fixed resolution box remaining grey after switching from windowed to fullscreen
* Fixed 'Auto-detect' not unchecking when user changes aspect ratio
* Fixed script command window not dismissing once it has been scrolled
* Fixed colored noise on Quicktime when first playing back a movie
* Fixed clickable area for objects in notecards
* Fixed Debug Settings to not save all changes as 'true'

Thanks for the download link, Tofu, you're a gem.

/me blowskiss

Thank you *hugggss*

Wee! Will try it as soon as I get home! With all the snow here it can take a while

So where is the Linux ChangeLog here? I see Mac and Windows changes, but nothing related to Linux at all.

Or is this simply a version bump to keep all clients at the same version number?

I'm specifically interested in the fixes for the hard-lockups in Linux with an ATI card (any driver). The version before .4 worked flawlessly, and .4 locks up the whole machine consistently after 4 seconds in SL (windowed or full screen). Previous versions did not suffer from this, and other OpenGL games work fine for hours at a time without a problem.

I've submitted a few hundred crash logs when it happens. Are they even being analyzed?

I got it working acceptably (still random crashes, but at 15-120 minute intervals - still annoying but livable barely) by serious tweaking of my xorg.conf. a copy of the relevant parts that works for me (YMMV) follows:


Section "Module"
Load "GLcore"
Load "dbe"
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "extmod"
Load "record"

Load "bitmap"
Load "ddc"
Load "dri"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "Device"
Identifier "ATI Technologies, Inc. ATI Default Card"
Driver "fglrx"
BusID "PCI:1:0:0"

Option "no_accel" "FALSE"
Option "no_dri" "FALSE"
Option "mtrr" "OFF" # disable DRI mtrr mapper, driver has its own code for mtrr
Option "AGPMask" "0x00000003" # force disable 1x and 2x AGP modes
Option "VideoOverlay" "OFF" # must be off for OpenGLOverlay to be on
Option "OpenGLOverlay" "ON" # passing the video render thru openGL seems to work fine
Option "PseudoColorVisuals" "OFF"

Option "FSAAEnable" "FALSE" # causes serious SL problems when TRUE
Option "FSAAScale" "4" # but girl it looks good!!!
Option "FSAADisableGamma" "FALSE"
Option "FSAACustomizeMSPos" "FALSE"
Option "UseFastTLS" "TRUE"
Option "BlockSignalsOnLock" "TRUE"
Option "UseInternalAGPGART" "FALSE" # stability issues when TRUE
Option "ForceGenericCPU" "FALSE"
EndSection

feel free to critique this anyone, I am always open to suggested optimisations myself too




I believe crashlogs are not quite there yet: the option to send comes up but the log isn't sent yet (at least in version .4) because Tofu wants them to sent actuallt useful data and is still working hard to define what that is.

I hope this isnt a Linux specific bug - i dont have windows so cant verify

I accept a teleport, it works, and a split second later im teleporting again, only the second time it I dont reappear anywhere, it just get left looking at a stuck progress bar saying 'requesting telepotrt', after a few mins, i appear at the destination.

1.12.3.4 wasn't working for me (client closed with no error-looking messages), 1.12.3.6 is working again. Thanks!

After I've logged in, second life just eats all available memory (around 50Mb/sec) until it
kills the machine. This is on FC4, x86-64. Previous clients (e.g. 1.11.3.1) didn't have
this problem. As a result, it's not usable for me despite having 2Gb of mem... an example:

3909 moz 25 0 1257m 1.0g 30m R 88.1 50.4 0:48.52 do-not-directly

(that's 1Gb RSS!)

I've seen this on windows and linux, though not for a while. Are you on a wireless internet connection by any chance? There's something weird with resends/acks over wireless - you can sometimes tell the wireless people because it looks like they say the same thing twice in a row!

I have encountered this once or twice recently. I am suspecting it is related to the present packet-loss/lag issues, but I am not an expert on deep-internet-thingies

A linux 1.13.0.0 Preview is available here: http://secondlife.com/community/preview.php

There are no linux-specific changes, so I'm not giving it its own thread (yet!).

Great! Something to play with during the outage

I'd be surprised if the beta grid was still available during today's network/database maintainance, sadly! But perhaps.

Yeah, I'm in FC5 32 bit and this new release is a real memory pig for me too. Just about completely unusable even before connecting. I click the Preferences button after launching the client and wait ... and wait ... and wait. First time I've run into this, the other releases are fine.

Edited to change this to completely unusable. I can't even log in. It just sits there on Connecting to Region. Interestingly, the rest of my system doesn't seem affected. It's just SL that crawls to a stop.

Edited again to add that after a reboot suddenly it's fine. Huh.

Perhaps it's something with the way FC's kernels are modified. Have either of you tried compiling a vanilla kernel from kernel.org and seeing if it doesn't continually run up memory? I'm on Kubuntu and it's holding steady at around 400mb.

As I just edited my post to reflect, oddly a reboot has made SL usable. Thought for a bit I was going to have to finally try the Windows version in WINE.

Strange. I'm not having many problems. Could it be a libc difference?

Same thing happens to me on openSUSE 10.1 - I have 2 GB RAM on this machine (with a craptastic ATI Rage card) and it eats all 2 GB then moves on to swap, and eats all of that too. Quite ugly.

Hi everyone!
I've gone over the SL client a few times this week with different leak detectors and haven't found anything unusual. Thus I suspect that it's something specific to the affected systems' system libraries or drivers. It would be helpful to find the common factor - in a dedicated forum thread.

Hi, I'm on Kubuntu Edgy Eft, newest packages, with proprietory ATI drivers.

When starting SL, it logs in, but as soon as the avatar appears, the whole computer freezes, I can't even shutdown via konsole, nor can I kill the X server.

Any ideas?

From the soon-to-be-released README:
PROBLEM 2:- My whole system seems to hang when running Second Life.
SOLUTION:- This is typically a hardware/driver issue. The first thing to
do is to check that you have the most recent official drivers for your
graphics card.
SOLUTION:- Some residents with ATI cards have reported that running
'sudo aticonfig --locked-userpages=off' before running Second Life solves
their stability issues.
SOLUTION:- As a last resort, you can disable most of Second Life's advanced
graphics features by editing the 'secondlife' script and uncommenting
the line which reads 'export LL_GL_NOEXT=x'

Thinkpad T43p, 1G Ram ATI V3200
fglrx 8.31.5-1.2.6.18_1.2849

So I have these params set:

Option "no_accel" "no"
Option "no_dri" "no"
Option "FSAAEnable" "no"
Option "KernelModuleParm" "locked-userpages=0"
Option "VideoOverlay" "on"

and I have
export LL_GL_NOEXT=x

set.

Here's the issue.

About 75% of the time I start up and I get
fglX11AllocateManagedSurface: __FGLTexMgrAllocMem failed!!

over and over again and things are super slow and I just ctrl-c

About 25% of the time, however, if I put up with the messages and extreme slowness for about 2 minutes, the messages stop and everything will work fine, for hours.

This _sort_ of thing is mentioned as being a /dev/shm permission or posix shared memory problem, I don't think that's the problem, for one thing everything is stock, for another I can see openGL programs create files in /dev/shm just fine, and it doesn't explain why it works eventually.

Before I tried the
Option "KernelModuleParm" "locked-userpages=0"
I got lockups.

Any ideas?

EDIT:
This seems to be much better in
1.13.0.5 ( I couldn't log into the test grid until recently)

I _was_ able to get the problem by maximizing the window and turning on FSAA, but that's kind of asking for it at 1600x1200.

On thing that I noticed was that I see this:

2006-11-27T04:43:32Z WARNING: VRAM amount not detected, defaulting to 512 MB
2006-11-27T04:43:32Z INFO: *** DETECTED 1009.63 MB of system memory.
2006-11-27T04:43:32Z INFO: Graphics Card memory set to 128 MB

Which is a bit ambiguous to me. Is it confused or not? I have 128MB.

I use Kubuntu Dapper on an ASUS A2500D with ATi Mobility Radeon 9600 and free drivers. Some works work well, while others don't. It seems that the problem is with the fonts in input and select fields. (Not plain texts.) There I have black fonts with black background. If I select the text, then I can read it. Otherwise ililsibel.

You can find two screenshots at
http://blog.educomm.hu/tmp/secondlife1.png
and
http://blog.educomm.hu/tmp/secondlife.png