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 496417 - crash in Tasks: opening my email package
crash in Tasks: opening my email package
Status: RESOLVED DUPLICATE of bug 339602
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-11-13 11:26 UTC by g7ltt
Modified: 2007-11-14 00:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description g7ltt 2007-11-13 11:26:50 UTC 
Version: 2.10

What were you doing when the application crashed?
opening my email package


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 173883392 vsize: 173883392 resident: 72585216 share: 31444992 rss: 72585216 rss_rlim: 4294967295
CPU usage: start_time: 1194923555 rtime: 4563 utime: 3056 stime: 1507 cutime:197 cstime: 50 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208260896 (LWP 16209)]
[New Thread -1246073968 (LWP 16263)]
[New Thread -1278932080 (LWP 16235)]
[New Thread -1235584112 (LWP 16230)]
[New Thread -1225094256 (LWP 16227)]
(no debugging symbols found)
0x0055d402 in __kernel_vsyscall ()

+ Trace 177397

Thread 2 (Thread -1246073968 (LWP 16263))

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


----------- .xsession-errors (9 sec old) ---------------------
(evolution:16209): camel-WARNING **: Could not find key entry for word 'hbgpne8ajcmihbcehvhbovlhm': Invalid or incomplete multibyte or wide character
(evolution:16209): camel-WARNING **: Could not find key entry for word 'sc000700mjiwmdc4nzk0': Invalid or incomplete multibyte or wide character
(evolution:16209): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset
(evolution:16209): e-data-server-WARNING **: Could not open converter for 'unicode-1-1-utf-7' to 'UTF-8' charset
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-14 00:46:48 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 339602 ***