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 574179 - crash in Evolution: email
crash in Evolution: email
Status: RESOLVED DUPLICATE of bug 556555
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-03-04 20:49 UTC by potmail
Modified: 2009-03-05 12:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description potmail 2009-03-04 20:49:44 UTC
What were you doing when the application crashed?
email


Distribution: openSUSE 11.1 (i586)
Gnome Release: 2.24.1 2008-12-03 (SUSE)
BugBuddy Version: 2.24.1

System: Linux 2.6.27.19-3.2-default #1 SMP 2009-02-25 15:40:44 +0100 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 108625920 vsize: 108625920 resident: 26779648 share: 20365312 rss: 26779648 rss_rlim: 18446744073709551615
CPU usage: start_time: 1236199728 rtime: 90 utime: 82 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb2458b90 (LWP 5313)]
[New Thread 0xb3577b90 (LWP 5301)]
[New Thread 0xb4d53b90 (LWP 5298)]
(no debugging symbols found)
0xffffe430 in __kernel_vsyscall ()

Thread 4 (Thread 0xb4d53b90 (LWP 5298))

  • #0 __kernel_vsyscall
  • #1 __lll_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_lock_89
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 <signal handler called>
  • #5 camel_folder_summary_load_from_db
    from /usr/lib/libcamel-provider-1.2.so.14
  • #6 camel_exchange_summary_new
    at camel-exchange-summary.c line 145
  • #7 camel_exchange_folder_construct
    at camel-exchange-folder.c line 999
  • #8 exchange_get_folder
    at camel-exchange-store.c line 516
  • #9 camel_store_get_folder
    from /usr/lib/libcamel-provider-1.2.so.14
  • #10 mail_tool_uri_to_folder
    from /usr/lib/evolution/2.24/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.24/components/libevolution-mail.so
  • #12 ??
    from /usr/lib/evolution/2.24/components/libevolution-mail.so
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 start_thread
    from /lib/libpthread.so.0
  • #16 clone
    from /lib/libc.so.6
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (140 sec old) ---------------------
** (gsynaptics-init:4173): WARNING **: Using synclient
W: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
W: core-util.c: setpriority(): Toegang geweigerd
W: ltdl-bind-now.c: Failed to find original dlopen loader.
** (nm-applet:4176): WARNING **: No connections defined
beagled will run in the background.
Use beagle-status to check progress of beagled.
For log files check /home/michiel/.beagle/Log/current-Beagle.
Windowmanager waarschuwing:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Starten va)
Windowmanager waarschuwing:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Windowmanager waarschuwing:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Softwarebe)
Windowmanager waarschuwing:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Milan Crha 2009-03-05 12:40:39 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 556555 ***