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 444874 - crash in Tasks: Closing the application....
crash in Tasks: Closing the application....
Status: RESOLVED DUPLICATE of bug 334966
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-06 20:19 UTC by Gwegowee
Modified: 2007-06-11 21:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Gwegowee 2007-06-06 20:19:04 UTC
What were you doing when the application crashed?
Closing the application.  Evolution


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.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 791371776 vsize: 791371776 resident: 101437440 share: 24264704 rss: 101437440 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181131786 rtime: 8873 utime: 6716 stime: 2157 cutime:33 cstime: 30 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496402016 (LWP 3335)]
[New Thread 1136679248 (LWP 6478)]
[New Thread 1105475920 (LWP 3397)]
(no debugging symbols found)
0x0000003ce9c0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496402016 (LWP 3335))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strcmp
    from /lib64/libc.so.6
  • #4 e_shell_window_set_title
  • #5 ??
  • #6 GNOME_Evolution_ShellView_setTitle
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #7 e_component_view_set_title
    from /usr/lib64/evolution/2.10/libeshell.so.0
  • #8 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #9 ??
    from /lib64/libglib-2.0.so.0
  • #10 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #13 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #14 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (675 sec old) ---------------------
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
(evolution:3335): calendar-gui-CRITICAL **: e_week_view_add_event: assertion `end > add_event_data->week_view->day_starts[0]' failed
--------------------------------------------------
Comment 1 André Klapper 2007-06-11 21:18:34 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 334966 ***