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 478533 - crash in Tasks: I started send/receive
crash in Tasks: I started send/receive
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-09-20 09:42 UTC by mirza.pasovic
Modified: 2007-09-24 17:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mirza.pasovic 2007-09-20 09:42:12 UTC
Version: 2.10

What were you doing when the application crashed?
I started send/receive



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

Memory status: size: 145215488 vsize: 145215488 resident: 50270208 share: 41222144 rss: 50270208 rss_rlim: 4294967295
CPU usage: start_time: 1190281312 rtime: 101 utime: 92 stime: 9 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 -1208498464 (LWP 18959)]
[New Thread -1284318320 (LWP 18987)]
[New Thread -1225274480 (LWP 18981)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208498464 (LWP 18959))

  • #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 (8495 sec old) ---------------------
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2955): 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-09-24 17:36:45 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 ***