GNOME Bugzilla – Bug 648270
crash in Deskbar: Distribution: Debian whe...
Last modified: 2011-04-20 07:08:37 UTC
What were you doing when the application crashed? Distribution: Debian wheezy/sid Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.38-2-686-bigmem #1 SMP Thu Apr 7 06:05:53 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10905000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux GTK+ Modules: gnomebreakpad 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 Traceback (most recent call last):
+ Trace 226794
app = DeskbarApplet(applet)
gnomeapplet.Applet.__init__(self)
----------- .xsession-errors --------------------- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x320002f (Iceape) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. basket(5232): Communication problem with "basket" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the kded(5490): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the kded(5577): "Error launching /usr/bin/kbuildsycoca4. Either KLauncher is not running anymore, or it failed to start the application." kdeinit4: preparing to launch /usr/bin/kglobalaccel Initializing nautilus-gdu extension Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4(7535) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(7535) kdemain: Emitting notifyDatabaseChanged () -------------------------------------------------- Distribution: Debian wheezy/sid Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.38-2-686-bigmem #1 SMP Thu Apr 7 06:05:53 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10905000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux GTK+ Modules: gnomebreakpad 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 Traceback (most recent call last):
----------- .xsession-errors --------------------- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x320002f (Iceape) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. basket(5232): Communication problem with "basket" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the kded(5490): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the kded(5577): "Error launching /usr/bin/kbuildsycoca4. Either KLauncher is not running anymore, or it failed to start the application." kdeinit4: preparing to launch /usr/bin/kglobalaccel Initializing nautilus-gdu extension Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) kbuildsycoca4(7535) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(7535) kdemain: Emitting notifyDatabaseChanged () --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 642915 ***