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 498567 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 449996
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 18:25 UTC by default
Modified: 2007-11-20 18:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description default 2007-11-20 18:25:43 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.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 888852480 vsize: 888852480 resident: 119549952 share: 97521664 rss: 119549952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1195481621 rtime: 3116 utime: 2766 stime: 350 cutime:0 cstime: 0 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 46912496481648 (LWP 4499)]
[New Thread 1105209680 (LWP 19231)]
[New Thread 1147169104 (LWP 19229)]
[New Thread 1168148816 (LWP 19227)]
[New Thread 1126189392 (LWP 19226)]
[New Thread 1136679248 (LWP 5786)]
[New Thread 1074006352 (LWP 5760)]
[New Thread 1094719824 (LWP 4505)]
(no debugging symbols found)
0x000000363080d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496481648 (LWP 4499))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 g_slice_free_chain_with_offset
    from /lib64/libglib-2.0.so.0
  • #7 ??
    from /usr/lib64/libpango-1.0.so.0
  • #8 pango_layout_set_text
    from /usr/lib64/libpango-1.0.so.0
  • #9 e_clipped_label_set_text
    from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
  • #10 e_info_label_set_info
    from /usr/lib64/evolution/2.10/libemiscwidgets.so.0
  • #11 ??
    from /usr/lib64/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib64/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #14 ??
    from /lib64/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #17 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (1017 sec old) ---------------------
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
(pidgin:17789): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
(pidgin:17789): GStreamer-CRITICAL **: 
Trying to dispose element fakesink, but it is not in the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
--------------------------------------------------
Comment 1 Christian Kirbach 2007-11-20 18:45:29 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 449996 ***