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 513061 - crash in Panel: closing after having int...
crash in Panel: closing after having int...
Status: RESOLVED DUPLICATE of bug 488819
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-30 10:38 UTC by Elio Voci
Modified: 2008-01-30 18:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Elio Voci 2008-01-30 10:38:28 UTC 
Version: 2.20.3

What were you doing when the application crashed?
closing after having interrupted a never-ending checking new mail 


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22 #1 Wed Jan 16 20:22:40 ULAT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 58052608 vsize: 58052608 resident: 24485888 share: 15904768 rss: 24485888 rss_rlim: 4294967295
CPU usage: start_time: 1200532757 rtime: 772 utime: 730 stime: 42 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f7e6b0 (LWP 4006)]
[New Thread 0xb5f09b90 (LWP 5061)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 187357

Thread 1 (Thread 0xb6f7e6b0 (LWP 4006))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.4/glib/gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 e_source_list_peek_groups
    from /usr/lib/libedataserver-1.2.so.9
  • #7 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #8 ??
  • #9 ??
  • #10 pthread_mutex_lock
    from /lib/i686/cmov/libpthread.so.0
  • #11 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #12 ??
    from /lib/i686/cmov/libpthread.so.0
  • #13 ??
  • #14 ??
  • #15 g_timeout_dispatch
    at /tmp/buildd/glib2.0-2.14.4/glib/gmain.c line 3488
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6 sec old) ---------------------
Loading Spamassasin as the default junk plugin
get prometeion imap://prometeion@imap.gmail.com/
Find Items 0
** (gnome-panel:4006): WARNING **: The calendar backend for contacts:/// has crashed.
** (gnome-panel:4006): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/mtfoklshhdrosc8l5s1njn08jo@group.calendar.google.com/private-0e1937ab7d05428c234d9f2c4739e090/basic.ic
** (gnome-panel:4006): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/4asjdvl64vro8n211nj446sddk@group.calendar.google.com/private-650525c563707b1cc296ffff8a4f6a31/basic.ic
** (gnome-panel:4006): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/fsm62vpbrq58ivu4k46pks1eeg@group.calendar.google.com/private-4e1360f0385a844843e46a5120440dd6/basic.ic
** (gnome-panel:4006): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/elio.voci@gmail.com/private-a01f5e5c435ed2528af4fb16c6e08b22/basic.ics has crashed.
** (gnome-panel:4006): WARNING **: The calendar backend for file:///home/elio/.evolution/calendar/local/system has crashed.
--------------------------------------------------
Comment 1 Philip Withnall 2008-01-30 18:22:03 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 488819 ***