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 510309 - crash in Power Manager: Just after screensaver u...
crash in Power Manager: Just after screensaver u...
Status: RESOLVED DUPLICATE of bug 420419
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.20.x
Other All
: High critical
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-01-18 01:48 UTC by Christopher Beland
Modified: 2008-01-19 22:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Christopher Beland 2008-01-18 01:48:35 UTC 
What were you doing when the application crashed?
Just after screensaver unlock


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.2 2007-11-27 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 45400064 vsize: 45400064 resident: 6807552 share: 5111808 rss: 6807552 rss_rlim: 4294967295
CPU usage: start_time: 1200341468 rtime: 1028 utime: 882 stime: 146 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208603984 (LWP 2212)]
0x00110402 in __kernel_vsyscall ()

+ Trace 185769

Thread 1 (Thread -1208603984 (LWP 2212))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 screensaver_auth_request_cb
    at gpm-manager.c line 1190
  • #10 IA__g_cclosure_marshal_VOID__BOOLEAN
    at gmarshal.c line 111
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gpm_screensaver_auth_end
    at gpm-screensaver.c line 80
  • #16 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #17 marshal_dbus_message_to_g_marshaller
    at dbus-gproxy.c line 1642
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1695
  • #23 dbus_connection_dispatch
    at dbus-connection.c line 4350
  • #24 message_queue_dispatch
    at dbus-gmain.c line 101
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #26 g_main_context_iterate
    at gmain.c line 2694
  • #27 IA__g_main_loop_run
    at gmain.c line 2898
  • #28 main
    at gpm-main.c line 267
  • #29 __libc_start_main
    at libc-start.c line 220
  • #30 _start
  • #0 __kernel_vsyscall 




----------- .xsession-errors (265045 sec old) ---------------------
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
(evolution:3877): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Bruno Boaventura 2008-01-18 23:21:50 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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