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 508093 - crash in Panel: My computer was starting...
crash in Panel: My computer was starting...
Status: RESOLVED DUPLICATE of bug 453033
Product: gnome-panel
Classification: Other
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-08 17:00 UTC by Bastien Lacoste
Modified: 2008-01-09 22:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Bastien Lacoste 2008-01-08 17:00:35 UTC 
Version: 2.20.1

What were you doing when the application crashed?
My computer was starting.


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.1 2007-11-26 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-gentoo-r9ekra #6 PREEMPT Sun Nov 11 21:19:25 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 39145472 vsize: 39145472 resident: 14110720 share: 11386880 rss: 14110720 rss_rlim: 4294967295
CPU usage: start_time: 1198530748 rtime: 61 utime: 57 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/libthread_db.so.1".
0xffffe410 in __kernel_vsyscall ()

+ Trace 184544

  • #0 __kernel_vsyscall
  • #1 waitpid
    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 idle_populate_func
    at gtkrecentchoosermenu.c line 929
  • #10 gdk_threads_dispatch
    at gdk.c line 470
  • #11 g_idle_dispatch
    at gmain.c line 4132
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #13 g_main_context_iterate
    at gmain.c line 2694
  • #14 IA__g_main_loop_run
    at gmain.c line 2898
  • #15 IA__gtk_main
    at gtkmain.c line 1146
  • #16 main
    at main.c line 95 


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
Cannot access memory at address 0x5
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-09 22:24:44 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 453033 ***