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 547812 - crash in Evolution Mail and Calendar: Closing the application
crash in Evolution Mail and Calendar: Closing the application
Status: RESOLVED DUPLICATE of bug 541872
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-08-14 18:02 UTC by ptimmons
Modified: 2008-09-04 00:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description ptimmons 2008-08-14 18:02:21 UTC 
What were you doing when the application crashed?
Closing the application


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 723206144 vsize: 723206144 resident: 102785024 share: 32825344 rss: 102785024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1218735285 rtime: 12212 utime: 7194 stime: 5018 cutime:0 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9509eb3790 (LWP 18151)]
[New Thread 0x439d4950 (LWP 18721)]
[New Thread 0x4118e950 (LWP 18720)]
(no debugging symbols found)
0x00007f95057895ff in waitpid () from /lib/libpthread.so.0

+ Trace 205167

Thread 1 (Thread 0x7f9509eb3790 (LWP 18151))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #8 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #9 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #10 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #11 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #12 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #13 XRE_TermEmbedding
    from /usr/lib/xulrunner-1.9/libxul.so
  • #14 ??
    from /usr/lib/xulrunner-1.9/libxul.so
  • #15 gecko_shutdown
    from /usr/lib/evolution/2.22/plugins/liborg-gnome-evolution-rss.so
  • #16 exit
    from /lib/libc.so.6
  • #17 __libc_start_main
    from /lib/libc.so.6
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors ---------------------
(nm-vpn-properties:17491): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -11 and height 1
(nm-vpn-properties:17491): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height 1
(nm-vpn-properties:17491): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height 1
(nm-vpn-properties:17491): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -14 and height -2
(nm-vpn-properties:9444): Gtk-CRITICAL **: gtk_expander_set_expanded: assertion `GTK_IS_EXPANDER (expander)' failed
bbdb: Buddy list has changed since last sync.
(evolution:18151): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(evolution:18151): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
RSS: cleaning all remaining sessions ...done
--------------------------------------------------
Comment 1 Tobias Mueller 2008-08-14 23:01:36 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 André Klapper 2008-09-04 00:22:51 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 541872 ***