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 485374 - crash in Evolution Mail: clicking on the Add butt...
crash in Evolution Mail: clicking on the Add butt...
Status: RESOLVED DUPLICATE of bug 487832
Product: evolution
Classification: Applications
Component: Calendar
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-10 12:30 UTC by antonio
Modified: 2007-12-29 19:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description antonio 2007-10-10 12:30:29 UTC
What were you doing when the application crashed?
clicking on the Add button for calendar publishing


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.0

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 124854272 vsize: 124854272 resident: 35360768 share: 19288064 rss: 35360768 rss_rlim: 4294967295
CPU usage: start_time: 1192019275 rtime: 530 utime: 506 stime: 24 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb69486b0 (LWP 29677)]
[New Thread 0xb27feb90 (LWP 29702)]
[New Thread 0xb2fffb90 (LWP 29701)]
[New Thread 0xb3986b90 (LWP 29698)]
[New Thread 0xb42ffb90 (LWP 29695)]
[New Thread 0xb546ab90 (LWP 29691)]
[New Thread 0xb5c74b90 (LWP 29689)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb69486b0 (LWP 29677))

  • #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 segv_redirect
    at main.c line 413
  • #6 <signal handler called>
  • #7 url_add_clicked
    at publish-calendar.c line 341
  • #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 (9080 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a00003 specified for 0x2a27240 (Choose Fil).
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800028 specified for 0x380006b ().
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3800028 specified for 0x3800077 ().
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800028 (Fonality H)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800093 (       )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 André Klapper 2007-12-29 19:42:42 UTC
the stacktrace in bug 487832 is even more complete

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