GNOME Bugzilla – Bug 528022
Crash in exchange_get_folder_info at camel-exchange-store.c
Last modified: 2010-09-20 04:38:12 UTC
What were you doing when the application crashed? svn build Revision: 35364. Quit evo. --force-shutdown. restart evo. processing mail. crash Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.1 2008-04-10 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.24-gentoo-r4 #1 SMP PREEMPT Mon Mar 31 12:07:10 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: marble-look Icon Theme: gnome Memory status: size: 161087488 vsize: 161087488 resident: 50270208 share: 20078592 rss: 50270208 rss_rlim: 4294967295 CPU usage: start_time: 1208176362 rtime: 701 utime: 637 stime: 64 cutime:8 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/evo/bin/evolution' [?1034hUsing host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb667a6d0 (LWP 25510)] [New Thread 0xb1f2db90 (LWP 26054)] [New Thread 0xb071bb90 (LWP 25648)] [New Thread 0xb2824b90 (LWP 25535)] [New Thread 0xb4032b90 (LWP 25532)] 0xb7f57410 in __kernel_vsyscall ()
+ Trace 195191
Thread 2 (Thread 0xb1f2db90 (LWP 26054))
----------- .xsession-errors (3463 sec old) --------------------- compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 compiz (animation) - Debug: polygon.c: pset null at line 1424 --------------------------------------------------
*** Bug 559608 has been marked as a duplicate of this bug. ***
*** Bug 576084 has been marked as a duplicate of this bug. ***
*** Bug 592889 has been marked as a duplicate of this bug. ***
*** Bug 520556 has been marked as a duplicate of this bug. ***
*** Bug 583860 has been marked as a duplicate of this bug. ***
*** Bug 603009 has been marked as a duplicate of this bug. ***
last dupe in 2.28.x
*** Bug 603836 has been marked as a duplicate of this bug. ***
I got the crash in 2.28.2
+ Trace 220622
*** Bug 610931 has been marked as a duplicate of this bug. ***
Why is this bug still "UNCONFIRMED" given that so many people have reported (a duplicate of) this bug? Why has this bug not been fixed, although it was reported almost 2 years ago? Is there any workaround? (I really want to be able to run evolution when I am off-line, see Bug 610931)
(In reply to comment #11) > Is there any workaround? (I really want to be able to run evolution when I am > off-line, see Bug 610931) Maybe not as that related, but if you are not using it, then try to disable assistive technologies in your system (and restart the machine). Maybe it'll help, as I do not have it enabled, and I can run Evolution in offline with evolution-exchange account enabled. -------------------------------------------------------------------------------- Can anyone of you try to reproduce this in an upcoming 2.30, please? There changed couple internal things in evolution-exchange, so maybe something changed with respect of this issue as well. Thanks in advance.
How can I disable assistive technologies in a KDE session?
configure desktop -> accessibility ?
I don't find something like "assistive technologies" in "System Settings" -> "Accessibility" or "System Settings" -> "Desktop" :-(
*** Bug 616525 has been marked as a duplicate of this bug. ***
*** Bug 617048 has been marked as a duplicate of this bug. ***
*** Bug 621162 has been marked as a duplicate of this bug. ***
Hm. All the crashers are on 2.28 so far. Could you please test with Evolution-2.30+?
This is Debian "Stable" and I do not want to upgrade, yet. Maybe I should better avoid reporting
Hmm, Debian "Stable" was even older: Version: 2.22.3.dfsg-1 Replaces: ximian-connector Provides: ximian-connector Depends: evolution (>= 2.22.3.1), libart-2.0-2 (>= 2.3.18), libatk1.0-0 (>= 1.20.0), libbonobo2-0 (>= 2.15.0), libbonoboui2-0 (>= 2.15.1), libc6 (>= 2.7-1), libcairo2 (>= 1.2.4), libcamel1.2-11 (>= 2.22.3), libebook1.2-9 (>= 2.22.3), libecal1.2-7 (>= 2.22.3), libedata-book1.2-2 (>= 2.22.3), libedata-cal1.2-6 (>= 2.22.3), libedataserver1.2-9 (>= 2.22.3), libedataserverui1.2-8 (>= 2.22.3), libexchange-storage1.2-3 (>= 2.22.3), libfontconfig1 (>= 2.4.0), libfreetype6 (>= 2.3.5), libgconf2-4 (>= 2.13.5), libglade2-0 (>= 1:2.6.1), libglib2.0-0 (>= 2.15.3), libgnome2-0 (>= 2.17.3), libgnomecanvas2-0 (>= 2.11.1), libgnomeui-0 (>= 2.17.1), libgnomevfs2-0 (>= 1:2.17.90), libgtk2.0-0 (>= 2.12.0), libice6 (>= 1:1.0.0), libldap-2.4-2 (>= 2.4.7), liborbit2 (>= 1:2.14.10), libpango1.0-0 (>= 1.20.3), libpixman-1-0, libpng12-0 (>= 1.2.13-4), libpopt0 (>= 1.14), libsm6, libsoup2.4-1 (>= 2.4.1), libx11-6, libxcb-render-util0, libxcb-render0, libxcb1, libxml2 (>= 2.6.27), libxrender1, zlib1g (>= 1:1.1.4), gconf2 (>= 2.10.1-2)
I also do not want to upgrade to evolution 2.30, because I have only "production systems" and do not want to take the risk of having an unproductive system. As evolution 2.28 is distributed with, e.g., Ubuntu 10.04 *LTS*, it would be great if this bug could be fixed (also) in 2.28. Thanks :-)
You'll have to ask Ubuntu for 2.28 support. Upstream support of 2.28 ended with the release of 2.30.
Please feel free to reopen the bug if the problem still occurs with current stable version of Evolution 2.30.3 or upcoming 2.32.0, thanks.