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 489837 - crash in Tasks: Scanning through my emai...
crash in Tasks: Scanning through my emai...
Status: RESOLVED DUPLICATE of bug 239441
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-10-24 15:35 UTC by Bob Gustafson
Modified: 2007-10-28 14:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Bob Gustafson 2007-10-24 15:35:12 UTC
Version: 2.10

What were you doing when the application crashed?
Scanning through my email. May have inadvertently opened an email - which then went wild - opening many windows. I don't think it was spam - an IEEE notice (!!!)


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: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 452218880 vsize: 452218880 resident: 256102400 share: 52109312 rss: 256102400 rss_rlim: 4294967295
CPU usage: start_time: 1192509886 rtime: 540096 utime: 358763 stime: 181333 cutime:3 cstime: 30 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 -1208596768 (LWP 27371)]
[New Thread -1541407856 (LWP 3128)]
[New Thread -1526731888 (LWP 3127)]
[New Thread -1516242032 (LWP 3126)]
[New Thread -1501566064 (LWP 3124)]
[New Thread -1491076208 (LWP 3123)]
[New Thread -1476396144 (LWP 3122)]
[New Thread -1463817328 (LWP 3121)]
[New Thread -1453327472 (LWP 3120)]
[New Thread -1367290992 (LWP 3119)]
[New Thread -1415685232 (LWP 3118)]
[New Thread -1220306032 (LWP 27407)]
[New Thread -1312351344 (LWP 27406)]
[New Thread -1232077936 (LWP 27390)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208596768 (LWP 27371))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #6 ??
    from /usr/lib/evolution/2.10/libetable.so.0
  • #7 resort_model
    from /usr/lib/evolution/2.10/libetable.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libpango-1.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/lib/libcrypto.so.6" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libsoup-2.2.so.8" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgnutls.so.13" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 André Klapper 2007-10-28 14:08:08 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 239441 ***