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 479207 - crash in Tasks: je quittai evolution
crash in Tasks: je quittai evolution
Status: RESOLVED DUPLICATE of bug 459958
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-22 09:00 UTC by dniger
Modified: 2007-09-23 14:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description dniger 2007-09-22 09:00:13 UTC
Version: 2.10

What were you doing when the application crashed?
je quittai evolution


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

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 573902848 vsize: 573902848 resident: 60698624 share: 40722432 rss: 60698624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190450701 rtime: 416 utime: 372 stime: 44 cutime:179 cstime: 21 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 46912496406672 (LWP 2917)]
[New Thread 1105209680 (LWP 3194)]
[New Thread 1189394768 (LWP 3138)]
[New Thread 1126455632 (LWP 2967)]
[New Thread 1084229968 (LWP 2940)]
(no debugging symbols found)
0x000000393620d97f in waitpid () from /lib64/libpthread.so.0

Thread 5 (Thread 1084229968 (LWP 2940))

  • #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 ??
    from /lib64/libglib-2.0.so.0
  • #5 ??
    from /lib64/libglib-2.0.so.0
  • #6 ??
    from /lib64/libglib-2.0.so.0
  • #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 (264 sec old) ---------------------
report junk?? Canadian pharmaceuticals
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600056 (OpenOffice)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600056 (OpenOffice)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:2917): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib64/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2917): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x858480'
(evolution:2917): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x859480'
(evolution:2917): e-data-server-DEBUG: Loading categories from "/home/David/.evolution/categories.xml"
(evolution:2917): e-data-server-DEBUG: Loaded 29 categories
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-23 14:44: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 459958 ***