GNOME Bugzilla – Bug 650214
crash in Deskbar: Distribution: Debian whe...
Last modified: 2011-05-15 12:01:00 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 Sun May 8 15:43:39 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 227124
app = DeskbarApplet(applet)
gnomeapplet.Applet.__init__(self)
----------- .xsession-errors --------------------- QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance() kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kbuildsycoca4(11699) KBuildSycoca::checkTimestamps: checking file timestamps K3bQProcess::QProcess(0x0) K3bQProcess::QProcess(0x0) ERROR:dbus.proxies:Introspect error on :1.25:/org/freedesktop/NetworkManagerSettings: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes includ k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! kbuildsycoca4(11699) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(11699) kdemain: Emitting notifyDatabaseChanged () Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0002f (Iceape) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- 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 Sun May 8 15:43:39 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 --------------------- QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance() kdeinit4: preparing to launch /usr/bin/kbuildsycoca4 kbuildsycoca4 running... kbuildsycoca4(11699) KBuildSycoca::checkTimestamps: checking file timestamps K3bQProcess::QProcess(0x0) K3bQProcess::QProcess(0x0) ERROR:dbus.proxies:Introspect error on :1.25:/org/freedesktop/NetworkManagerSettings: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes includ k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory! k3b(5133)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! kbuildsycoca4(11699) KBuildSycoca::checkTimestamps: timestamps check ok kbuildsycoca4(11699) kdemain: Emitting notifyDatabaseChanged () Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e0002f (Iceape) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 ***