Bug 478332 – crash in Tasks: I was connecting to gmai...

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 478332 - crash in Tasks: I was connecting to gmai...


Summary:	crash in Tasks: I was connecting to gmai...


Status:	RESOLVED DUPLICATE of bug 364700

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-19 12:13 UTC by mirza.pasovic
Modified:	2007-09-24 17:37 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description mirza.pasovic 2007-09-19 12:13:23 UTC

Version: 2.10

What were you doing when the application crashed?
I was connecting to gmail.com


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: 117620736 vsize: 117620736 resident: 40292352 share: 32694272 rss: 40292352 rss_rlim: 4294967295
CPU usage: start_time: 1190203979 rtime: 92 utime: 83 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 -1209162016 (LWP 4529)]
[New Thread -1274668144 (LWP 4557)]
[New Thread -1225938032 (LWP 4551)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 163972

Thread 1 (Thread -1209162016 (LWP 4529))

#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 ---------------------
(mail-notification:2969): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:2969): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
CalDAV Eplugin starting up ...
(evolution:4529): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one
(evolution:4529): e-utils-WARNING **: Plugin 'Bogofilter junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution:4529): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:4529): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(mail-notification:2969): mail-notification-WARNING **: pasovic@creatis.insa-lyon.fr: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
--------------------------------------------------

Comment 1 Tobias Mueller 2007-09-24 17:37:35 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 ***