After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 509557 - crash in Battery Charge Monitor:
crash in Battery Charge Monitor:
Status: RESOLVED DUPLICATE of bug 446097
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-15 07:09 UTC by QingLong
Modified: 2008-01-15 21:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description QingLong 2008-01-15 07:09:38 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: 7753728 share: 6639616 rss: 7753728 rss_rlim: 4294967295
CPU usage: start_time: 1200380908 rtime: 6 utime: 4 stime: 2 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 -1208813856 (LWP 2915)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208813856 (LWP 2915))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 ??
    from /lib/libdbus-1.so.3
  • #8 ??
    from /lib/libdbus-1.so.3
  • #9 dbus_move_error
    from /lib/libdbus-1.so.3
  • #10 libhal_device_property_exists
    from /usr/lib/libhal.so.1
  • #11 ??
  • #12 ??
    from /usr/lib/libhal.so.1
  • #13 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #14 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #19 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #21 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #22 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #23 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (18 sec old) ---------------------
localuser:klimenko being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2781
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:2781): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
(gnome-panel:2846): 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
--------------------------------------------------
Comment 1 Bruno Boaventura 2008-01-15 21:35:02 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 446097 ***