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 512749 - crash in Tasks:
crash in Tasks:
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: 2008-01-29 09:50 UTC by capitan
Modified: 2008-01-29 18:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description capitan 2008-01-29 09:50:25 UTC 
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 147361792 vsize: 147361792 resident: 29786112 share: 17518592 rss: 29786112 rss_rlim: 4294967295
CPU usage: start_time: 1201595421 rtime: 646 utime: 412 stime: 234 cutime:50 cstime: 27 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 -1208551712 (LWP 3430)]
[New Thread -1299305584 (LWP 3485)]
[New Thread -1271276656 (LWP 3457)]
[New Thread -1238266992 (LWP 3454)]
[New Thread -1227777136 (LWP 3451)]
(no debugging symbols found)
0x00682402 in __kernel_vsyscall ()

+ Trace 187166

Thread 2 (Thread -1299305584 (LWP 3485))

  • #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 ---------------------
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:3430): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3430): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:3430): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x8d
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x8d
--------------------------------------------------
Comment 1 Tobias Mueller 2008-01-29 18:19:21 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 ***