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 539912 - crash in Panel: replying to an email
crash in Panel: replying to an email
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-06-24 09:39 UTC by Elio Voci
Modified: 2008-06-24 16:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Elio Voci 2008-06-24 09:39:39 UTC
Version: 2.20.3

What were you doing when the application crashed?
replying to an email



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-elio-4 #2 Fri Apr 4 10:10:15 CEST 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: 56274944 vsize: 56274944 resident: 30113792 share: 15941632 rss: 30113792 rss_rlim: 4294967295
CPU usage: start_time: 1214239714 rtime: 2334 utime: 2224 stime: 110 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f16720 (LWP 4801)]
[New Thread 0xb5f23b90 (LWP 8310)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6f16720 (LWP 4801))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #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 free
    from /lib/i686/cmov/libc.so.6
  • #10 ??
    from /usr/lib/gnome-panel/libclock-applet.so
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 g_timeout_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 3443
  • #0 __kernel_vsyscall


----------- .xsession-errors (7 sec old) ---------------------
** (gnome-panel:4801): WARNING **: The calendar backend for contacts:/// has crashed.
** (gnome-panel:4801): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/mtfoklshhdrosc8l5s1njn08jo@group.calendar.google.com/private-0e1937ab7d05428c234d9f2c4739e090/basic.ic
** (gnome-panel:4801): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/elio.voci@gmail.com/private-a01f5e5c435ed2528af4fb16c6e08b22/basic.ics has crashed.
** (gnome-panel:4801): WARNING **: The calendar backend for file:///home/elio/.evolution/calendar/local/system has crashed.
** (gnome-panel:4801): WARNING **: The calendar backend for contacts:/// has crashed.
** (gnome-panel:4801): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/mtfoklshhdrosc8l5s1njn08jo@group.calendar.google.com/private-0e1937ab7d05428c234d9f2c4739e090/basic.ic
** (gnome-panel:4801): WARNING **: The calendar backend for webcal://www.google.com/calendar/ical/elio.voci@gmail.com/private-a01f5e5c435ed2528af4fb16c6e08b22/basic.ics has crashed.
** (gnome-panel:4801): WARNING **: The calendar backend for file:///home/elio/.evolution/calendar/local/system has crashed.
--------------------------------------------------
Comment 1 Philip Withnall 2008-06-24 16:34:41 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 488819 ***