UBUNTU 8.04.3 crashes with snowball and official

since November 18 or 19, 2009

-- my PC --
FOXCONN am2 winfast6100m2ma with nforce410
AMD 4400+ x2 64
2048MB DDR2-800
PCIe nvidia
fx 7300gs
Audigy SE

No changes in system,
all updates of last week so far for the Ubuntu Gnome 8.04.3 LTS
(before the new series of crashes appeared)
So i bet it has something to do with the last rolling restarts' changes.

-- i did test it with those SL viewers --
SecondLife-i686-1.23.5.136274 (the weeks before even more stable as my windowsXP SL viewer)
Snowglobe-i686-1.1.3.2906
Snowglobe-i686-1.2.4.3007

all crashes the same in everyone of them,
so it is something the viewers have in common (or the server changes)

the crashes usually occur after teleports 1,2,3 minutes later in the new tp'd sim.

NO CRASHES of THAT 'sort' in the windowsXP SP3 , newest SL viewer version,
same Computer (multiboot with Grub)

Can you run snowglobe from a terminal and in case of a crash post the end of the output there? That might give some hint on the cause.

It is with snowball AND 'official' viewers.

SecondLife-i686-1.23.5.136274
(the weeks before even more stable as my windowsXP SL viewer)

Snowglobe-i686-1.1.3.2906
Snowglobe-i686-1.2.4.3007

does snowball do better terminal outputs?

how many lines of the end of the output ?

Snowglobe-i686-1.2.4.3007

as i wrote:
crashes usually occur after teleports 1,2,3 minutes later in the new tp'd sim.

Here Snowglobe HANGS (not the usual type of CRASH)
after region to another region TP ---


2009-11-25T16:39:54Z INFO: addRegion: Adding new region (760:1006)
2009-11-25T16:39:54Z INFO: addRegion: Host: 216.82.32.198:13001
2009-11-25T16:39:54Z INFO: process_enable_simulator: simulator_enable() Enabling 216.82.32.198:13001 with code 844587098
2009-11-25T16:39:54Z INFO: display_stats: FPS: 18.50
2009-11-25T16:39:55Z INFO: idle: Transmitting sessions stats
2009-11-25T16:39:55Z INFO: send_stats: Misc Stats: int_1: i926 int_2: i54
2009-11-25T16:39:55Z INFO: send_stats: Misc Stats: string_1: '1108' string_2: !
2009-11-25T16:39:55Z INFO: addToMessage: STAT: Version: 0
2009-11-25T16:39:55Z INFO: addToMessage: STAT: Vertex Buffers Enabled: 1
2009-11-25T16:39:56Z INFO: LLViewerParcelMedia::update: New parcel, parcel id = 16, region id = fddd072b-ec0d-42e5-8f64-9ab093bd5f9f
2009-11-25T16:39:56Z INFO: process_enable_simulator: simulator_enable() Enabling 216.82.32.198:13001 with code 844587098
2009-11-25T16:39:56Z INFO: result: ViewerStatsResponder::result
2009-11-25T16:39:58Z INFO: setSeedCapability: posting to seed https://sim7196.agni.lindenlab.com:12043/cap/07f51b08-4b68-3302-cb73-ed0c50b2730f
2009-11-25T16:40:00Z INFO: LLEventPollResponder: LLEventPoll initialized with sender 216.82.32.198:13001
2009-11-25T16:40:00Z INFO: start: LLEventPollResponder:tart <31> https://sim7196.agni.lindenlab.com:12043/cap/1d0eea74-c2e2-c101-1232-73073352854b
2009-11-25T16:40:00Z INFO: setSender: LLHTTPSender:etSender 216.82.32.198:13001
2009-11-25T16:40:04Z INFO: display_stats: FPS: 13.60
2009-11-25T16:40:07Z INFO: idle: Kills on unknown objects: 1
2009-11-25T16:40:12Z INFO: idle: Kills on unknown objects: 225
2009-11-25T16:40:14Z INFO: display_stats: FPS: 17.60
2009-11-25T16:40:15Z WARNING: getTargetAttachmentPoint: Object attachment point invalid: 128
2009-11-25T16:40:17Z INFO: idle: Kills on unknown objects: 2
2009-11-25T16:40:22Z INFO: idle: Kills on unknown objects: 1
2009-11-25T16:40:22Z INFO: checkPacketInID: packet_out_of_order - got packet 3462 expecting 3437 from 216.82.38.73:13002
2009-11-25T16:40:24Z INFO: display_stats: FPS: 13.20
2009-11-25T16:40:26Z INFO: checkPacketInID: packet_out_of_order - got packet 4046 expecting 4030 from 216.82.38.73:13002
2009-11-25T16:40:27Z INFO: idle: Kills on unknown objects: 521

---HANG---

Can't see anything suspect in the log. But when the viewer hangs instead of crashing, that's not too surprising.

Changes in server software usually aren't going to affect the client, at least not in a selective fashion. If a bug in the server is going to affect the client, it will affect ALL clients that hit the bug in the same way, regardless of platform.

I haven't run Hardy in quite some time; but I recall several issues that caused me no end of trouble until I was able to resolve them, either by tweaking config files or by installing backports. I would check on the usual suspects here: Outdated video graphics drivers (particularly if you are stuck using the nVidia 169 drivers) or an old Pulseaudio version (If Pulseaudio dies, it can freeze up your viewer) can cause no end of headaches on Hardy.

that all sounds like problems with no end for me (my usual experience with some things when i use ubuntu)
hopefully things may be solved with the coming version 10 LTS of ubuntu.

i need a new 'box' anyway now (the old PC needs some changes and i need a full replacement system at home)
until then i will buy me either maybe a miniMAC (that includes OS10.6 - not at least "OSX desktop features" were a main reason i came to ubuntu 6.06.1 back in the days 2007)
or
a new PC that comes with (bulk) windows 7 software (all ~500 euro anyway)
so i can wait for things to come and using ubuntu10.04 LTS (or Debian 6.0) in 2010 alongside.