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 441832 - crash in Tasks: opening the application
crash in Tasks: opening the application
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-05-28 14:42 UTC by Duncan Innes
Modified: 2007-05-28 19:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Duncan Innes 2007-05-28 14:42:56 UTC
What were you doing when the application crashed?
opening the application


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

System: Linux 2.6.21-1.3167.fc7 #1 SMP Thu May 17 23:05:53 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: 128946176 vsize: 128946176 resident: 26812416 share: 15740928 rss: 26812416 rss_rlim: 4294967295
CPU usage: start_time: 1180363356 rtime: 88 utime: 81 stime: 7 cutime:44 cstime: 11 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 -1208232224 (LWP 2876)]
[New Thread -1255875696 (LWP 2913)]
[New Thread -1291506800 (LWP 2900)]
[New Thread -1234502768 (LWP 2896)]
[New Thread -1224012912 (LWP 2893)]
(no debugging symbols found)
0x00a52402 in __kernel_vsyscall ()

Thread 2 (Thread -1255875696 (LWP 2913))

  • #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 (8 sec old) ---------------------
(bug-buddy:2813): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:2813): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:2813): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:2813): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
CalDAV Eplugin starting up ...
** (evolution:2831): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2831): DEBUG: mailto URL program: evolution
(evolution:2831): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
CalDAV Eplugin starting up ...
** (evolution:2876): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2876): DEBUG: mailto URL program: evolution
(evolution:2876): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-05-28 19:19:05 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 431342 ***