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 517240 - crash in Tasks:
crash in Tasks:
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: 2008-02-18 15:27 UTC by andrew.liimatta
Modified: 2008-02-20 06:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description andrew.liimatta 2008-02-18 15:27:57 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 09:29:36 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 711348224 vsize: 711348224 resident: 45826048 share: 22568960 rss: 45826048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1202927520 rtime: 5941 utime: 2463 stime: 3478 cutime:44 cstime: 73 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 46912496438880 (LWP 28694)]
[New Thread 1084229968 (LWP 29990)]
[New Thread 1115965776 (LWP 28722)]
(no debugging symbols found)
0x0000003f5860d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496438880 (LWP 28694))

  • #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 (306 sec old) ---------------------
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:28694): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-20 06:04:54 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 ***