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 529493 - crash in Panel: This has happened during...
crash in Panel: This has happened during...
Status: RESOLVED DUPLICATE of bug 378854
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-04-23 07:00 UTC by d.sastre.medina
Modified: 2008-04-23 15:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description d.sastre.medina 2008-04-23 07:00:09 UTC 
Version: 2.20.3

What were you doing when the application crashed?
This has happened during a freeze of Evolution, I had to kill it and then Bug Buddy reported this error.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-686-bigmem #1 SMP Sun Feb 10 21:47:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 55406592 vsize: 55406592 resident: 22376448 share: 14233600 rss: 22376448 rss_rlim: 4294967295
CPU usage: start_time: 1208929071 rtime: 552 utime: 510 stime: 42 cutime:93 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6db9720 (LWP 9012)]
[New Thread 0xb6197b90 (LWP 14078)]
[New Thread 0xb61d8b90 (LWP 14065)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 195908

Thread 1 (Thread 0xb6db9720 (LWP 9012))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 g_slist_remove
    from /usr/lib/libglib-2.0.so.0
  • #7 backend_died_cb
    at calendar-sources.c line 432
  • #8 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (295 sec old) ---------------------
b7ef4000-b7ef6000 rwxp 00001000 08:04 38895      /usr/lib/gconv/ISO8859-15.so
b7ef6000-b7efd000 r-xs 00000000 08:04 8865       /usr/lib/gconv/gconv-modules.cache
b7efd000-b7f04000 r-xp 0049d000 08:04 57066      /usr/lib/locale/locale-archive
b7f04000-b7f5a000 r-xp 00000000 08:04 206279     /usr/lib/evolution/2.12/libemiscwidgets.so.0.0.0
b7f5a000-b7f5f000 rwxp 00055000 08:04 206279     /usr/lib/evolution/2.12/libemiscwidgets.so.0.0.0
b7f5f000-b7f60000 rwxp b7f5f000 00:00 0 
b7f60000-b7f64000 r-xp 00000000 08:04 206924     /usr/lib/evolution/2.12/libetimezonedialog.so.0.0.0
b7f64000-b7f65000 rwxp 00003000 08:04 206924     /usr/lib/evolution/2.12/libetimezonedialog.so.0.0.0
b7f65000-b7f72000 r-xp 00000000 08:04 206357     /usr/lib/evolution/2.12/libeshell.so.0.0.0
b7f72000-b7f74000 rwxp 0000c000 08:04 206357     /usr/lib/evolution/2.12/libeshell.so.0.0.0
b7f74000-b7f76000 rwxp b7f74000 00:00 0 
b7f76000-b7f92000 r-xp 00000000 08:04 26702      /lib/ld-2.7.so
b7f92000-b7f94000 rwxp 0001b000 08:04 26702      /lib/ld-2.7.so
bfb07000-bfb1c000 rw-p bfb07000 00:00 0          [stack]
ffffe000-fffff000 r-xp 00000000 00:00 0          [vdso]
--------------------------------------------------
Comment 1 Philip Withnall 2008-04-23 15:58:58 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 378854 ***