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 488393 - crash in Tasks: I had just loaded Evolut...
crash in Tasks: I had just loaded Evolut...
Status: RESOLVED DUPLICATE of bug 364700
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-10-19 19:10 UTC by rjordan
Modified: 2007-10-22 22:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rjordan 2007-10-19 19:10:20 UTC 
Version: 2.10

What were you doing when the application crashed?
I had just loaded Evolution. I'm using an MS Exchange account, which tends to be buggy.


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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 138227712 vsize: 138227712 resident: 40714240 share: 32669696 rss: 40714240 rss_rlim: 4294967295
CPU usage: start_time: 1192820558 rtime: 126 utime: 102 stime: 24 cutime:0 cstime: 0 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 -1209084192 (LWP 9812)]
[New Thread -1269433456 (LWP 9842)]
[New Thread -1258943600 (LWP 9841)]
[New Thread -1295410288 (LWP 9835)]
[New Thread -1248453744 (LWP 9826)]
[New Thread -1221674096 (LWP 9825)]
[New Thread -1211184240 (LWP 9823)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171511

Thread 1 (Thread -1209084192 (LWP 9812))

  • #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 (454892 sec old) ---------------------
fixme:sync:RegisterWaitForSingleObjectEx 0x4c4 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x4d8 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x4ec 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x518 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x518 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x454 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x46c 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x498 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x4c4 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x420 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x46c 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x4c4 0x71468576 0x211ace8 0 4
fixme:sync:RegisterWaitForSingleObjectEx 0x4d8 0x71468576 0x211ace8 0 4
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-10-22 22:26:49 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 ***