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 467649 - crash in Tasks: Closing evolution, did n...
crash in Tasks: Closing evolution, did n...
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-08-17 13:24 UTC by Jens Hardings Perl
Modified: 2007-08-22 18:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Jens Hardings Perl 2007-08-17 13:24:31 UTC 
Version: 2.10

What were you doing when the application crashed?
Closing evolution, did not even look at tasks, only mail.


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: gnuAquaSE
Icon Theme: Smokey-Blue

Memory status: size: 206659584 vsize: 206659584 resident: 122961920 share: 34000896 rss: 122961920 rss_rlim: 4294967295
CPU usage: start_time: 1187355141 rtime: 11884 utime: 10230 stime: 1654 cutime:4 cstime: 15 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 -1208935696 (LWP 21899)]
[New Thread -1294992496 (LWP 22322)]
[New Thread -1232704624 (LWP 22214)]
[New Thread -1265632368 (LWP 21949)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 155909

Thread 2 (Thread -1294992496 (LWP 22322))

  • #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 (20 sec old) ---------------------
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkHTML::cite-color' of type `GdkColor' from rc file value ""(null)"" of type `gchararray'
<memory>:1: Invalid color constant '(null)'
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkHTML::cite-color' of type `GdkColor' from rc file value ""(null)"" of type `gchararray'
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
BBDB spinning up...
(evolution:21899): e-data-server-DEBUG: Loading categories from "/home/jhp/.evolution/categories.xml"
(evolution:21899): e-data-server-DEBUG: Loaded 30 categories
(evolution:21899): libebook-WARNING **: invalid escape, passing it through
camel-Message: --
camel-Message: --
inside eab_vcard_control_new
--------------------------------------------------
Comment 1 André Klapper 2007-08-22 18:06:51 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 445309 ***