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 417738 - crash in Power Statistics: had disk usage analyzer ...
crash in Power Statistics: had disk usage analyzer ...
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)
Depends on:
Blocks:
 
 
Reported: 2007-03-13 03:09 UTC by krstork
Modified: 2007-03-15 16:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description krstork 2007-03-13 03:09:33 UTC 
What were you doing when the application crashed?
had disk usage analyzer open, power history,andblack jack then it popped up.  running from live cd.  this computer sucks.......it is very slow on windows that is installed so itwas no surprise something crashed :) nice job with fedora! 


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: 48967680 vsize: 0 resident: 48967680 share: 0 rss: 12447744 rss_rlim: 0
CPU usage: start_time: 1173740726 rtime: 0 utime: 73 stime: 0 cutime:57 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 -1208985888 (LWP 3039)]
(no debugging symbols found)
0x006a5402 in __kernel_vsyscall ()

+ Trace 118188

Thread 1 (Thread -1208985888 (LWP 3039))

  • #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 (91 sec old) ---------------------
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1041, in entry_callback
    self.entry_validate(widget)
  File "/usr/lib/python2.5/site-packages/gnome_sudoku/gsudoku.py", line 1078, in entry_validate
    self.__entries__[conflict].set_error_highlight(True)
KeyError
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
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Richard Hughes 2007-03-15 16:47:19 UTC 

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