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 511132 - crash in Tasks:
crash in Tasks:
Status: RESOLVED DUPLICATE of bug 431459
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-01-21 21:37 UTC by bertral
Modified: 2008-01-22 12:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bertral 2008-01-21 21:37:21 UTC
Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 195915776 vsize: 195915776 resident: 72613888 share: 32538624 rss: 72613888 rss_rlim: 4294967295
CPU usage: start_time: 1200951126 rtime: 2050 utime: 1922 stime: 128 cutime:0 cstime: 1 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 -1208510752 (LWP 10236)]
[New Thread -1247712368 (LWP 10280)]
[New Thread -1259340912 (LWP 10259)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208510752 (LWP 10236))

  • #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 ---------------------
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/New Product Alliances/Colorbok
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/New Product Alliances/ICI
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/New Product Alliances/IIMAK
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/New Product Alliances/Microsoft
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Research & Development/R & D Archive/Chemical Research/Cambridge Lab Move
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Sales/IBC/Executive Share
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Web Internet Email - Incoming/Buzz - Zink.com
(evolution:10236): evolution-mail-WARNING **: Failed to refresh folders: No such folder Public Folders/Snaps
--------------------------------------------------
Comment 1 Sankar P 2008-01-22 07:04:31 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

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 2008-01-22 12:12:07 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 431459 ***