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 492135 - crash in Battery Charge Monitor: resuming from hibernatio...
crash in Battery Charge Monitor: resuming from hibernatio...
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-10-31 19:05 UTC by avrunin
Modified: 2007-11-03 08:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description avrunin 2007-10-31 19:05:42 UTC 
What were you doing when the application crashed?
resuming from hibernation


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-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 253759488 vsize: 253759488 resident: 5517312 share: 4096000 rss: 5517312 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193847127 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496445168 (LWP 3000)]
(no debugging symbols found)
0x0000003b95e0d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 174199

Thread 1 (Thread 46912496445168 (LWP 3000))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_str_hash
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_str_hash
    from /lib64/libdbus-1.so.3
  • #6 g_str_hash
    from /lib64/libdbus-1.so.3
  • #7 libhal_device_property_exists
    from /usr/lib64/libhal.so.1
  • #8 ??
  • #9 g_str_hash
    from /usr/lib64/libhal.so.1
  • #10 dbus_connection_dispatch
    from /lib64/libdbus-1.so.3
  • #11 g_str_hash
    from /usr/lib64/libdbus-glib-1.so.2
  • #12 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #13 g_str_hash
    from /lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #15 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #16 bonobo_generic_factory_main_timeout
    from /usr/lib64/libbonobo-2.so.0
  • #17 panel_applet_factory_main_closure
    from /usr/lib64/libpanel-applet-2.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors (4988 sec old) ---------------------
Tracker version 0.6.3 Copyright (c) 2005-2007 by Jamie McCracken (jamiemcc@gnome.org)
This program is free software and comes without any warranty.
It is licensed under version 2 or later of the General Public License which can be viewed at http://www.gnu.org/licenses/gpl.txt
Initialising tracker...
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
Could not set idle IO priority...attempting best effort 7 priority
Throttle level is 0
** (nm-applet:2975): 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 Christoph Wolk 2007-11-03 08:54:29 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 ***