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 451562 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 432796
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-27 10:48 UTC by leongyh74
Modified: 2007-06-27 13:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description leongyh74 2007-06-27 10:48:26 UTC
Version: 2.10

What were you doing when the application crashed?



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 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 234954752 vsize: 234954752 resident: 90771456 share: 75563008 rss: 90771456 rss_rlim: 4294967295
CPU usage: start_time: 1182939599 rtime: 2106 utime: 1925 stime: 181 cutime:2 cstime: 9 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208211744 (LWP 2858)]
[New Thread -1348576368 (LWP 3347)]
[New Thread -1286251632 (LWP 3081)]
[New Thread -1262093424 (LWP 3079)]
[New Thread -1272583280 (LWP 2895)]
(no debugging symbols found)
0x00929402 in __kernel_vsyscall ()

Thread 5 (Thread -1272583280 (LWP 2895))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 __nptl_deallocate_tsd
    from /lib/libpthread.so.0
  • #10 start_thread
    from /lib/libpthread.so.0
  • #11 clone
    from /lib/libc.so.6


----------- .xsession-errors (218 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a001dc (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
ICE default IO error handler doing an exit(), pid = 3030, errno = 0
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a01433 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(evolution:2858): e-data-server-DEBUG: Loading categories from "/home/lyh/.evolution/categories.xml"
(evolution:2858): e-data-server-DEBUG: Loaded 30 categories
(evolution:2858): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:2858): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9ef8488'
(evolution:2858): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x9ef85a8'
--------------------------------------------------
Comment 1 palfrey 2007-06-27 13:33:39 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 432796 ***