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 502050 - crash in Battery Charge Monitor: coming out of suspend (u...
crash in Battery Charge Monitor: coming out of suspend (u...
Status: RESOLVED DUPLICATE of bug 501605
Product: gnome-applets
Classification: Other
Component: battery
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-06 13:48 UTC by aparsons
Modified: 2007-12-06 19:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description aparsons 2007-12-06 13:48:27 UTC
What were you doing when the application crashed?
coming out of suspend (usually not a problem)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 25550848 vsize: 25550848 resident: 3792896 share: 2973696 rss: 3792896 rss_rlim: 4294967295
CPU usage: start_time: 1196874183 rtime: 320 utime: 25 stime: 295 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 -1208829328 (LWP 2984)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208829328 (LWP 2984))

  • #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 (7 sec old) ---------------------
(gnome-terminal:2887): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000004 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(gnome-terminal:2887): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** Message: <info>  You are now connected to the wired network.
(gnome-terminal:2887): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-terminal:2887): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** Message: <info>  You are now connected to the wired network.
--------------------------------------------------
Comment 1 palfrey 2007-12-06 19:15:29 UTC
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 501605 ***