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 413927 - crash in Power Statistics: haldaemon didn't start o...
crash in Power Statistics: haldaemon didn't start o...
Status: RESOLVED DUPLICATE of bug 412345
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-statistics
2.17.x
Other All
: High critical
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
: 414066 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-03-02 17:41 UTC by wadenton
Modified: 2007-03-04 12:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description wadenton 2007-03-02 17:41:56 UTC
What were you doing when the application crashed?
haldaemon didn't start on bootup; I did a "service haldaemon start", then ran gnome-power-manager. Then tried to run power history. It ran OK for about a minute, not logging any data, then crashed.


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.17.91 2007-02-13 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:37:35 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: Enforcing
Accessibility: Enabled

Memory status: size: 51535872 vsize: 0 resident: 51535872 share: 0 rss: 12840960 rss_rlim: 0
CPU usage: start_time: 1172857213 rtime: 0 utime: 111 stime: 0 cutime:95 cstime: 0 timeout: 16 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-power-statistics'

(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 -1208473888 (LWP 3075)]
(no debugging symbols found)
0x00592402 in __kernel_vsyscall ()

Thread 1 (Thread -1208473888 (LWP 3075))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 ??
    from /lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #8 ??
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #14 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Failed to read private dictionary. This problem might be a problem of Anthy.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Saving to syslog: Could not connect to GNOME Power Manager.
Perhaps the program is not running or you are using an old version?Bonobo accessibility support initialized
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-03 14:14:05 UTC
*** Bug 414066 has been marked as a duplicate of this bug. ***
Comment 2 Richard Hughes 2007-03-04 12:11:56 UTC

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