GNOME Bugzilla – Bug 515173
crash in Battery Charge Monitor:
Last modified: 2008-02-08 14:56:20 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 24690688 vsize: 24690688 resident: 7749632 share: 6639616 rss: 7749632 rss_rlim: 4294967295 CPU usage: start_time: 1202467444 rtime: 4 utime: 3 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/battstat-applet-2' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208240416 (LWP 2921)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188520
Thread 1 (Thread -1208240416 (LWP 2921))
----------- .xsession-errors (8 sec old) --------------------- localuser:klimenko being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2789 Identity added: /home/klimenko/.ssh/id_rsa (/home/klimenko/.ssh/id_rsa) ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name (gnome-session:2789): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch Identity added: /home/klimenko/.ssh/identity (klimenko@stas) Traceback (most recent call last): File "/usr/bin/puplet", line 315, in updates_avail_notify self._showNotify(notify, urgency) File "/usr/bin/puplet", line 241, in _showNotify if not self.notify.show(): gobject.GError: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the netw --------------------------------------------------
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 446097 ***