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 425287 - crash in Power Statistics: attempting to enable des...
crash in Power Statistics: attempting to enable des...
Status: RESOLVED DUPLICATE of bug 414075
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-04-01 22:03 UTC by rh
Modified: 2007-04-02 16:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rh 2007-04-01 22:03:50 UTC 
What were you doing when the application crashed?
attempting to enable desktop effects


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-20 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3023.fc7 #1 SMP Sun Mar 25 21:47:10 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 282710016 vsize: 282710016 resident: 13996032 share: 10018816 rss: 13996032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1175454163 rtime: 38 utime: 28 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912676857088 (LWP 4081)]
(no debugging symbols found)
0x00002aaab00ed805 in waitpid () from /lib64/libpthread.so.0

+ Trace 124173

Thread 1 (Thread 46912676857088 (LWP 4081))

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


----------- .xsession-errors (6 sec old) ---------------------
You can override this setting using the beagle-config or beagle-settings tools.
    _dbus_bindings.UInt32(0))
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 169, in __call__
    reply_message = self._connection.send_message_with_reply_and_block(message, timeout)
dbus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name edu.duke.linux.yum was not provided by any .service files
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
compiz: No GLXFBConfig for default depth, this isn't going to work.
compiz: Failed to manage screen: 0
compiz: No manageable screens found on display :0.0
--------------------------------------------------
Comment 1 palfrey 2007-04-02 16:27:09 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 414075 ***