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 598295 - crash in Evolution Mail and Calendar: opening evolution - that...
crash in Evolution Mail and Calendar: opening evolution - that...
Status: RESOLVED DUPLICATE of bug 595260
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-13 15:27 UTC by Chad Feller
Modified: 2010-02-27 12:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Chad Feller 2009-10-13 15:27:51 UTC
What were you doing when the application crashed?
opening evolution - that is, evolution had just opened, I hadn't even had a chance to click on my new mail messages yet.  My folder(s) had just finished synchronizing w/ the exchange server (using exchange-mapi).


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-09-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 762884096 vsize: 762884096 resident: 55984128 share: 25939968 rss: 55984128 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255447226 rtime: 1593 utime: 1470 stime: 123 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f23b6936950 (LWP 28477)]
[New Thread 0x7f23b7137950 (LWP 28415)]
[New Thread 0x7f23b7fff950 (LWP 28412)]
[New Thread 0x7f23bcf65950 (LWP 28410)]
[New Thread 0x7f23bd972950 (LWP 28409)]
[New Thread 0x7f23beb87950 (LWP 28407)]
[New Thread 0x7f23bf388950 (LWP 28406)]
0x00007f23d5f8228f in waitpid () from /lib/libpthread.so.0

Thread 2 (Thread 0x7f23b6936950 (LWP 28477))

  • #0 __lll_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_lock_102
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 mapi_sync_deleted
    at camel-mapi-folder.c line 744
  • #5 session_thread_proxy
    at camel-session.c line 592
  • #6 g_thread_pool_thread_proxy
    at /tmp/buildd/glib2.0-2.22.0/glib/gthreadpool.c line 265
  • #7 g_thread_create_proxy
    at /tmp/buildd/glib2.0-2.22.0/glib/gthread.c line 635
  • #8 start_thread
    from /lib/libpthread.so.0
  • #9 clone
    from /lib/libc.so.6
  • #10 ??


----------- .xsession-errors (484 sec old) ---------------------
** (gnome-power-manager:27838): WARNING **: This machine is not identified as a laptop.system.formfactor is server.
** (gnome-power-manager:27838): WARNING **: This machine is not identified as a laptop.system.formfactor is server.
** (gnome-power-manager:27838): DEBUG: This machine is not identified as a laptop.system.formfactor is server.
** (gnome-power-manager:27838): DEBUG: We are not a laptop, so not even trying
(gnome-panel:27851): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -45 and height 24
** (nautilus:27852): WARNING **: Unable to add monitor: Not supported
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-10-13 15:31:22 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 bug 595260 ***
Comment 2 Cosimo Cecchi 2010-02-27 12:33:23 UTC
*** Bug 610653 has been marked as a duplicate of this bug. ***