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 493852 - crash in Tasks: These fault happens clos...
crash in Tasks: These fault happens clos...
Status: RESOLVED DUPLICATE of bug 405646
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-11-05 19:29 UTC by sergio
Modified: 2007-11-05 23:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sergio 2007-11-05 19:29:22 UTC
Version: 2.10

What were you doing when the application crashed?
These fault happens closing the mail application, but not frecuently, only observed once!!, at the moment there are a lot of mails into inbox folder, aproximately 80 mail messages, but there is not any synchronization active at the same time, the main method used was POP...
Many thanks for your great work!!!!
BR,
Sergio.


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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 144789504 vsize: 144789504 resident: 58568704 share: 45662208 rss: 58568704 rss_rlim: 4294967295
CPU usage: start_time: 1194290216 rtime: 1082 utime: 1002 stime: 80 cutime:60 cstime: 19 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 -1208899872 (LWP 3007)]
[New Thread -1288623216 (LWP 3189)]
[New Thread -1256158320 (LWP 3045)]
[New Thread -1266644080 (LWP 3041)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 4 (Thread -1266644080 (LWP 3041))

  • #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 (29 sec old) ---------------------
(evolution:3007): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa2c0020'
(evolution:3007): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa2c0140'
Mon Nov  5 20:25:13 2007
 CConn:       Throughput 16041 kbit/s - changing to raw encoding
 CConn:       Using raw encoding
 CConn:       Throughput 15968 kbit/s - changing to hextile encoding
 CConn:       Using hextile encoding
Mon Nov  5 20:25:14 2007
 CConn:       Throughput 16002 kbit/s - changing to raw encoding
 CConn:       Using raw encoding
 CConn:       Throughput 15761 kbit/s - changing to hextile encoding
 CConn:       Using hextile encoding
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-05 23:23:12 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 405646 ***