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 451650 - crash in Tasks: Waiting for the evolutio...
crash in Tasks: Waiting for the evolutio...
Status: RESOLVED DUPLICATE of bug 387143
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-06-27 15:41 UTC by bschmidt
Modified: 2007-10-12 13:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bschmidt 2007-06-27 15:41:16 UTC 
Version: 2.10

What were you doing when the application crashed?
Waiting for the evolution window to redraw - it appeared hung and would not redraw in a reasonable period of time.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 298635264 vsize: 298635264 resident: 173776896 share: 45215744 rss: 173776896 rss_rlim: 4294967295
CPU usage: start_time: 1182950272 rtime: 51398 utime: 40584 stime: 10814 cutime:1 cstime: 5 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 -1208932640 (LWP 18749)]
[New Thread -1330398320 (LWP 20083)]
[New Thread -1208935536 (LWP 19191)]
[New Thread -1274713200 (LWP 18823)]
[New Thread -1264223344 (LWP 18778)]
[New Thread -1253340272 (LWP 18777)]
(no debugging symbols found)
0x00456402 in __kernel_vsyscall ()

+ Trace 144141

Thread 1 (Thread -1208932640 (LWP 18749))

  • #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 resort_model
    from /usr/lib/evolution/2.10/libetable.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (16 sec old) ---------------------
(evolution:18749): libebook-WARNING **: invalid escape, passing it through
apps file failure
apps file failure
(evolution:18749): libebook-WARNING **: invalid escape, passing it through
apps file failure
apps file failure
apps file failure
apps file failure
(evolution:18749): libebook-WARNING **: invalid escape, passing it through
apps file failure
apps file failure
apps file failure
apps file failure
--------------------------------------------------
Comment 1 palfrey 2007-06-28 13:55:14 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-10-12 13:18:04 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 387143 ***