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 493758 - crash in Tasks:
crash in Tasks:
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-11-05 15:14 UTC by mirza.pasovic
Modified: 2007-11-05 23:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mirza.pasovic 2007-11-05 15:14:38 UTC
Version: 2.10

What were you doing when the application crashed?



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.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 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: 126464000 vsize: 126464000 resident: 39260160 share: 32718848 rss: 39260160 rss_rlim: 4294967295
CPU usage: start_time: 1194275664 rtime: 135 utime: 121 stime: 14 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 -1208973600 (LWP 12237)]
[New Thread -1284396144 (LWP 12263)]
[New Thread -1225839728 (LWP 12254)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208973600 (LWP 12237))

  • #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 (33008 sec old) ---------------------
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:3041): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Tobias Mueller 2007-11-05 23:26:39 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 ***