Beim verwenden vom VMWare Player unter Ubuntu ist Ubuntu 6.1 abgestürzt.
Beim neuen starten erscheint jetzt der BugBuddy mit folgender Fehlermeldung:
Memory status: size: 35426304 vsize: 0 resident: 35426304 share: 0 rss: 15368192 rss_rlim: 0
CPU usage: start_time: 1171377011 rtime: 0 utime: 76 stime: 0 cutime:70 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-panel'
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225075024 (LWP 5607)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb7664323 in __waitpid_nocancel ()
from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7f5c1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
#3
Linux 14.981 Themen, 106.344 Beiträge
Wenn dieser Player die Ursache war, dann wirst du das Problem wieder bekommen.
Deshalb sollst du auch die Workstation Version nutzen und dir eine serial besorgen. Ich sagte besorgen ;-).
Die Konfiguration der beiden Desktops KDE und Gnome wird im /home Verzeichnis unter .gnome oder .kde abgespeichert.
Wenn mir so was passiert ist, habe ich einfach die Konfigurationsdatei des KDE im /home Verzeichnis gelöscht.
Beim nächsten Start wurde der KDE nochmal neu konfiguriert.
Eine Reparatur des KDE mit einem Editor war nie möglich.
Reparieren kannst du die Konfigurationsdateien im /etc Verzeichnis. Diese Dateien sind so gemacht, das man sie auch mit einem Editor bearbeiten kann. In den Debian Richtlinien für die Entwickler steht, wenn der Administrator eine Konfigurationsdatei im /etc Verzeichnis mit einem Editor verändert hat, dann darf diese Datei nicht automatisch überschrieben werden. Ich nehme an, da Ubuntu eine abgespeckte Debian testing Version ist, ist es bei Ubuntu auch so.
Ich würde mal die entsprechende Konfigurationsdatei von gnome im /home Verzeichnis löschen.