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 459591 - crash in Battery Charge Monitor: suspending to ram
crash in Battery Charge Monitor: suspending to ram
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: 2007-07-23 14:45 UTC by Joel Schaerer
Modified: 2007-07-26 05:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Joel Schaerer 2007-07-23 14:45:55 UTC 
What were you doing when the application crashed?
suspending to ram


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.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 23826432 vsize: 23826432 resident: 8376320 share: 7245824 rss: 8376320 rss_rlim: 4294967295
CPU usage: start_time: 1185201851 rtime: 13 utime: 10 stime: 3 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 -1209005456 (LWP 2476)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 149991

Thread 1 (Thread -1209005456 (LWP 2476))

  • #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 (10 sec old) ---------------------
Initializing nautilus-image-converter extension
Initializing nautilus-search-tool extension
Initializing nautilus-open-terminal extension
(gnome-panel:2278): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0xa076158
Unable to open desktop file file:///home/schaerer/Desktop/Armadillo%20Run.desktop for panel launcher: No such file or directory
** Message: <info>  You are now connected to the wireless network 'creatis'.
(gnome-terminal:2538): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
** (nm-applet:2298): WARNING **: <WARN>  nma_dbus_device_properties_cb(): dbus returned an error.
  (org.freedesktop.DBus.Error.NoReply) Message did not receive a reply (timeout by message bus)
--------------------------------------------------
Comment 1 Philip Withnall 2007-07-26 05:01:09 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 ***