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 447617 - crash in Tasks: Using evolution, with ev...
crash in Tasks: Using evolution, with ev...
Status: RESOLVED DUPLICATE of bug 431342
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-14 17:20 UTC by Aldo Feshti
Modified: 2007-06-14 19:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Aldo Feshti 2007-06-14 17:20:48 UTC
What were you doing when the application crashed?
Using evolution, with evolution-connector, just clickn to "Sent" folder mail (local mails) (path:.evolution/mail/local/..).


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 138498048 vsize: 138498048 resident: 47857664 share: 34865152 rss: 47857664 rss_rlim: 4294967295
CPU usage: start_time: 1181831327 rtime: 2014 utime: 1884 stime: 130 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208383776 (LWP 8035)]
[New Thread -1277621360 (LWP 16593)]
[New Thread -1299534960 (LWP 14629)]
[New Thread -1299268720 (LWP 8074)]
[New Thread -1238508656 (LWP 8060)]
[New Thread -1227625584 (LWP 8059)]
(no debugging symbols found)
0x00592402 in __kernel_vsyscall ()

Thread 2 (Thread -1277621360 (LWP 16593))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 camel_object_cast
    from /usr/lib/libcamel-1.2.so.10
  • #7 camel_local_summary_check
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #8 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #9 camel_folder_refresh_info
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6


----------- .xsession-errors (24 sec old) ---------------------
warning: .dynamic section for "/usr/lib/librsvg-2.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbz2.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 André Klapper 2007-06-14 19:42:47 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 431342 ***