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 453495 - crash in Tasks: Clicked the title bar "c...
crash in Tasks: Clicked the title bar "c...
Status: RESOLVED DUPLICATE of bug 450163
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-03 20:53 UTC by Gregory Fowler
Modified: 2007-07-03 23:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Gregory Fowler 2007-07-03 20:53:42 UTC 
Version: 2.10

What were you doing when the application crashed?
Clicked the title bar "close application button" on the far right


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 637018112 vsize: 637018112 resident: 69885952 share: 33275904 rss: 69885952 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183400835 rtime: 9121 utime: 8566 stime: 555 cutime:1 cstime: 5 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 46912496377440 (LWP 24203)]
[New Thread 1126189392 (LWP 14926)]
[New Thread 1084229968 (LWP 24628)]
[New Thread 1084496208 (LWP 24270)]
(no debugging symbols found)
0x0000003cc340d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 145552

Thread 2 (Thread 1126189392 (LWP 14926))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 <signal handler called>
  • #4 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #5 PR_Lock
    from /usr/lib64/libnspr4.so
  • #6 ??
    from /usr/lib64/libnspr4.so
  • #7 __nptl_deallocate_tsd
    from /lib64/libpthread.so.0
  • #8 start_thread
    from /lib64/libpthread.so.0
  • #9 clone
    from /lib64/libc.so.6 


----------- .xsession-errors ---------------------
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:24203): camel-WARNING **: camel_exception_get_id called with NULL parameter.
inside eab_vcard_control_new
inside eab_vcard_control_new
--------------------------------------------------
Comment 1 Karsten Bräckelmann 2007-07-03 23:13:26 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 450163 ***