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 498616 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 455329
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-20 22:23 UTC by x
Modified: 2007-12-02 15:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description x 2007-11-20 22:23:30 UTC
Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.1-21.fc7PAE #1 SMP Thu Nov 1 20:56:47 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: 144461824 vsize: 144461824 resident: 63868928 share: 40022016 rss: 63868928 rss_rlim: 4294967295
CPU usage: start_time: 1195507974 rtime: 10378 utime: 9766 stime: 612 cutime:63 cstime: 105 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 -1209157920 (LWP 29850)]
[New Thread -1240908912 (LWP 23073)]
[New Thread -1282716784 (LWP 18736)]
[New Thread -1230742640 (LWP 29891)]
[New Thread -1251398768 (LWP 29880)]
(no debugging symbols found)
0x00110410 in __kernel_vsyscall ()

Thread 2 (Thread -1240908912 (LWP 23073))

  • #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 ??
  • #7 camel_message_info_ptr
    from /usr/lib/libcamel-provider-1.2.so.10
  • #8 ??
    from /usr/lib/libcamel-provider-1.2.so.10
  • #9 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #10 camel_folder_summary_save
    from /usr/lib/libcamel-provider-1.2.so.10
  • #11 ??
    from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so
  • #12 camel_folder_sync
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6


----------- .xsession-errors (13682 sec old) ---------------------
(evolution:29850): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:29850): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:29850): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:29850): calendar-gui-CRITICAL **: e_day_view_add_event: assertion `end > add_event_data->day_view->lower' failed
(evolution:29850): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:29850): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:29850): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(gnome-terminal:3436): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Comment 1 Akhil Laddha 2007-11-21 07:03:57 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk,
glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided
by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 Tobias Mueller 2007-12-02 15:17:11 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 455329 ***