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 488223 - crash in Power Manager: xscreensaver
crash in Power Manager: xscreensaver
Status: RESOLVED DUPLICATE of bug 420419
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.17.x
Other All
: High critical
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-19 11:09 UTC by tadeu.andrade
Modified: 2008-02-10 19:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description tadeu.andrade 2007-10-19 11:09:41 UTC
What were you doing when the application crashed?
xscreensaver


Distribution: Unknown
Gnome Release: 2.20.0 2007-10-15 (FreeBSD GNOME Project)
BugBuddy Version: 2.20.1

System: FreeBSD 6.2-RELEASE-p7 FreeBSD 6.2-RELEASE-p7 #2: Fri Aug 10 10:05:54 BRT 2007     tadeu@tadeu.cin.ufpe.br:/usr/obj/usr/src/sys/GENERIC i386
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Noia

Memory status: size: 43660 vsize: 43660 resident: 22140 share: 43148869 rss: 22140 rss_rlim: 5535
CPU usage: start_time: 0 rtime: 133 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

Backtrace was generated from '/usr/local/bin/gnome-power-manager'

(no debugging symbols found)...[New LWP 100106]
[Switching to LWP 100106]
0x291e26cd in wait4 () from /lib/libc.so.6

Thread 1 (LWP 100106)

  • #0 wait4
    from /lib/libc.so.6
  • #1 waitpid
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.2
  • #3 g_spawn_sync
    from /usr/local/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/local/lib/libglib-2.0.so.0
  • #5 bugbuddy_segv_handle
    from /usr/local/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 sigaction
    from /lib/libpthread.so.2
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 sigaction
    from /lib/libpthread.so.2
  • #13 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/local/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/local/lib/libgobject-2.0.so.0
  • #15 g_signal_has_handler_pending
    from /usr/local/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/local/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/local/lib/libgobject-2.0.so.0
  • #18 ??
  • #19 g_cclosure_marshal_VOID__VOID
    from /usr/local/lib/libgobject-2.0.so.0
  • #20 dbus_g_proxy_get_type
    from /usr/local/lib/libdbus-glib-1.so.2
  • #21 g_closure_invoke
    from /usr/local/lib/libgobject-2.0.so.0
  • #22 g_signal_has_handler_pending
    from /usr/local/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/local/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/local/lib/libgobject-2.0.so.0
  • #25 dbus_g_proxy_get_type
    from /usr/local/lib/libdbus-glib-1.so.2
  • #26 dbus_connection_dispatch
    from /usr/local/lib/libdbus-1.so.3
  • #27 dbus_g_message_get_message
    from /usr/local/lib/libdbus-glib-1.so.2
  • #28 g_main_context_dispatch
    from /usr/local/lib/libglib-2.0.so.0
  • #29 g_main_context_acquire
    from /usr/local/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/local/lib/libglib-2.0.so.0
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 libhal_marshal_VOID__STRING_BOOLEAN_BOOLEAN_BOOLEAN
  • #38 ??
Output of custom script "gnome-power-bugreport.sh":
Distro version:       Kernel version:       6.2-RELEASE-p7
g-p-m version:        2.20.0
HAL version:          0.5.8
System manufacturer:  missing
System version:       missing
System product:       missing
AC adapter present:   no
Battery present:      no
Laptop panel present: no
CPU scaling present:  no
Battery Information:
GNOME Power Manager Process Information:
HAL Process Information:




----------- .xsession-errors (53940 sec old) ---------------------
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] Determining new status for thiagoamorim@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::bestJabberResource(const XMPP::Jid&, bool)] Determining best resource for thiagoamorim@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::lockedJabberResource(const XMPP::Jid&)] No lock available for thiagoamorim@gmail.com
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] New status for thiagoamorim@gmail.com is Offline
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] Determining new status for ulliane.delfino@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::bestJabberResource(const XMPP::Jid&, bool)] Determining best resource for ulliane.delfino@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::lockedJabberResource(const XMPP::Jid&)] No lock available for ulliane.delfino@gmail.com
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] New status for ulliane.delfino@gmail.com is Offline
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] Determining new status for vanessaedisandra@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::bestJabberResource(const XMPP::Jid&, bool)] Determining best resource for vanessaedisandra@gmail.com
kopete (jabber): [JabberResource* JabberResourcePool::lockedJabberResource(const XMPP::Jid&)] No lock available for vanessaedisandra@gmail.com
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] New status for vanessaedisandra@gmail.com is Offline
kopete (jabber): [void JabberBaseContact::reevaluateStatus()] Determining new status for washyngtonfreitas@gmail.com
kopete (jabber): [JabberRes
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-10-29 14:29:16 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2008-02-10 19:55:46 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 420419 ***