opensuse 10.1 crashte beim browsen erbarmungslos ab

[cc]

hallo

mein opensuse 10.1 crashte beim browsen mit firefox erbarmungslos ab.
ich konnte nichts machen, ausser power off knopf zu drücken.
solche abstürze kenne ich eigentlich nur aus der mickysoft welt.
log file vor dem crash:

Sep  3 21:59:28 suse zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager
Sep  3 21:59:29 suse hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 84
Sep  3 21:59:29 suse kernel: eth1: no IPv6 routers present
Sep  3 22:00:10 suse su: (to beagleindex) root on none
Sep  3 22:00:38 suse zmd: Daemon (WARN): Not starting remote web server
Sep  3 22:00:48 suse gconfd (root-4104): starting (version 2.12.1), pid 4104 user 'root'
Sep  3 22:00:48 suse gconfd (root-4104): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep  3 22:00:48 suse gconfd (root-4104): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Sep  3 22:00:48 suse gconfd (root-4104): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep  3 22:01:18 suse gconfd (root-4104): GConf server is not in use, shutting down.
Sep  3 22:01:18 suse gconfd (root-4104): Exiting
Sep  3 22:01:22 suse gconfd (root-4172): starting (version 2.12.1), pid 4172 user 'root'
Sep  3 22:01:22 suse gconfd (root-4172): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep  3 22:01:22 suse gconfd (root-4172): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Sep  3 22:01:22 suse gconfd (root-4172): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2

 

[K4m1K4tz3]

Und was soll das jetzt uns sagen?

 

[nollsa]

Starte mal den ff von der Konsole aus, und poste mal die Meldung, falls er ne Fehlermeldung rausschmeißt.

 

[traffic]

Dein Logfile-Auszug ist Müll, der Kram dort hat nichts mit dem Absturz zu tun.