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 481719 - crash in Tasks: Closing evolution by pre...
crash in Tasks: Closing evolution by pre...
Status: RESOLVED DUPLICATE of bug 445309
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-09-29 23:23 UTC by bukaj
Modified: 2007-10-01 14:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bukaj 2007-09-29 23:23:38 UTC 
Version: 2.10

What were you doing when the application crashed?
Closing evolution by pressing X icon in window caption.


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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136830976 vsize: 136830976 resident: 50130944 share: 35581952 rss: 50130944 rss_rlim: 4294967295
CPU usage: start_time: 1191071293 rtime: 2311 utime: 2108 stime: 203 cutime:643 cstime: 36 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 -1208371488 (LWP 3121)]
[New Thread -1298498672 (LWP 7391)]
[New Thread -1224914032 (LWP 7334)]
[New Thread -1345406064 (LWP 3171)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 166501

Thread 2 (Thread -1298498672 (LWP 7391))

  • #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 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #7 PR_Lock
    from /usr/lib/libnspr4.so
  • #8 ??
    from /usr/lib/libnspr4.so
  • #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 (8 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(gnome-terminal:6992): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200075 (Inbox (6 t)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
camel-Message: --
(evolution:3121): e-data-server-DEBUG: Loading categories from "/home/bukaj/.evolution/categories.xml"
(evolution:3121): e-data-server-DEBUG: Loaded 29 categories
(evolution:3121): e-data-server-ui-WARNING **: Key file does not have key '87784E9F65A0E666'
(evolution:3121): camel-imap-provider-CRITICAL **: imap_command_start: assertion `store->ostream!=NULL' failed
index:0
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-01 14:35:46 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 445309 ***