GNOME Bugzilla – Bug 551813
crash in Deskbar: opening skype and pidgin...
Last modified: 2008-09-11 15:51:16 UTC
What were you doing when the application crashed? opening skype and pidgin while writing on the deskbar Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- Warning: No symbols defined for <I78> (keycode 248) Warning: No symbols defined for <I79> (keycode 249) Warning: No symbols defined for <I7A> (keycode 250) Warning: No symbols defined for <I7B> (keycode 251) Warning: No symbols defined for <I7C> (keycode 252) Warning: No symbols defined for <I7D> (keycode 253) Warning: No symbols defined for <I7E> (keycode 254) Warning: No symbols defined for <I7F> (keycode 255) Shutdown failed or nothing to shut down. ** (gnome-settings-daemon:3368): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory Window manager warning: Failed to read saved session file /home/bjaast/.metacity/sessions/default0.ms: Failed to open file '/home/bjaast/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3400085 specified for 0x340008c (cdcat). -------------------------------------------------- Traceback (most recent call last):
+ Trace 206638
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 475351 ***