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 516579 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 364700
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-14 23:22 UTC by fperez
Modified: 2008-02-15 02:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description fperez 2008-02-14 23:22:18 UTC
Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 141688832 vsize: 141688832 resident: 46510080 share: 38146048 rss: 46510080 rss_rlim: 4294967295
CPU usage: start_time: 1203031312 rtime: 81 utime: 70 stime: 11 cutime:0 cstime: 2 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 -1208965408 (LWP 20965)]
[New Thread -1225319536 (LWP 20994)]
[New Thread -1247810672 (LWP 20986)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208965408 (LWP 20965))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #9 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (11484 sec old) ---------------------
        1230 (  240,2 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  05-07-05Tue  5 Jul 2005 08 02 35 -0600  CST .txt
        1103 (  107,7 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  06-05-05Fri  6 May 2005 22 44 13 -0600  CST .txt
        1103 (  215,4 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  06-09-05Tue  6 Sep 2005 19 20 50 -0500  EST .txt
        1357 (  165,6 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  07-06-05Tue  7 Jun 2005 16 05 54 -0600  CST .txt
        1103 (  134,6 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  07-07-05Thu  7 Jul 2005 08 12 31 -0600  CST .txt
        1996 (  974,6 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  07-09-05Wed  7 Sep 2005 19 35 09 -0500  EST .txt
        1611 (  224,7 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  08-02-05Tue  8 Feb 2005 14 31 44 -0600  CST .txt
        1103 (  538,6 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  08-02-05Tue  8 Feb 2005 16 16 00 -0600  CST .txt
        1103 (  215,4 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  08-08-05Mon  8 Aug 2005 14 42 12 -0500  EST .txt
        2119 ( 1034,7 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  08-08-05Mon  8 Aug 2005 16 49 22 -0500  EST .txt
        1103 (  215,4 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  09-06-05Thu  9 Jun 2005 11 26 45 -0600  CST .txt
        1104 (  539,1 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  10-03-05Thu  10 Mar 2005 19 01 57 -0600  CST .txt
        1231 (  171,7 kb/s) \EdcIDSE\VARIOS\buzon\864 IMSS  11-02-05Fri  11 Feb 2005 12 34 11 -0600  CST .txt
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2008-02-15 02:59:30 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 364700 ***