GNOME Bugzilla – Bug 460617
Evolution was running in the background and bug-buddy reported a crash
Last modified: 2008-08-27 03:24:32 UTC
Steps to reproduce: 1. See bug buddy report. Stack trace: System: Linux 2.6.22-rc3 #2 SMP Thu May 31 22:22:37 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 71692288 vsize: 0 resident: 71692288 share: 0 rss: 13303808 rss_rlim: 0 CPU usage: start_time: 1185453380 rtime: 0 utime: 292 stime: 0 cutime:245 cstime: 0 timeout: 47 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208994096 (LWP 4148)] [New Thread -1238369392 (LWP 10343)] [New Thread -1211139184 (LWP 4153)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7f35410 in __kernel_vsyscall ()
+ Trace 150717
Thread 2 (Thread -1238369392 (LWP 10343))
----------- .xsession-errors (167 sec old) --------------------- Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000063 (Buddy List) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. CalDAV Eplugin starting up ... ** (evolution:4411): WARNING **: LDAP authentication failed (0xffffffff) ** (evolution:4411): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:4411): DEBUG: mailto URL program: evolution BBDB spinning up... (evolution:4411): e-data-server-DEBUG: Loading categories from "/sultan/.evolution/categories.xml" (evolution:4411): e-data-server-DEBUG: Loaded 29 categories Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4c000a9 specified for 0x4c000ad ( ). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4c000f0 specified for 0x4c000f4 ( ). Window manager warning: Invalid WM_TRANSIENT_FOR window 0xce specified for 0x5000004 (Initializi). (gnome-terminal:4137): Vte-WARNING **: No handler for control sequence `device-control-string' defined. -------------------------------------------------- Other information:
I don't have much in the way of details, as Evolution was simply running in the background when bug-buddy reported a crash. I'm connecting to a corporate MS Exchange server. The only other thing I can report is that I've been getting a warning dialog with the message: Error while refreshing folder. Lost connection to Evolution Exchange backend process. This message appears everytime I click on an existing folder from my Exchange account (which appear under Personal Folders in the left-hand browser pane). When this starts happening, I have to restart evolution. I do not know why the backend process fails. I assume the crash is the back end process reported by bug-buddy, and the subsequent error messages are due to the fact that the back end crashed. If there is anything I can do to generate more information, please do let me know.
I just ran into this problem as well - in looking at the bugreport debugging output, it looks as if evolution was doing a background contact sync with exchange... System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 82432000 vsize: 82432000 resident: 16564224 share: 9760768 rss: 16564224 rss_rlim: 4294967295 CPU usage: start_time: 1189198785 rtime: 960 utime: 838 stime: 122 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/evolution-exchange-storage' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208523040 (LWP 17649)] [New Thread -1210889328 (LWP 1332)] [New Thread -1210623088 (LWP 17650)] 0x00110402 in __kernel_vsyscall ()
+ Trace 162158
Thread 2 (Thread -1210889328 (LWP 1332))
----------- .xsession-errors (7264563 sec old) --------------------- ** Message: don't know how to handle video/x-flv ** Message: Error: You do not have a decoder installed to handle this file. You might need to install the necessary plugins. gstplaybasebin.c(2182): prepare_output (): /play totem-video-thumbnailer couln't open file 'file:///home/dsteckbeck/Media/WorkingWithMonkeys.flv' Reason: The playback of this movie requires a Flash demuxer plugin which is not installed.. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Error: Bad annotation destination position Error: Bad annotation destination position Window manager warning: Invalid WM_TRANSIENT_FOR window 0x64 specified for 0x1274111 (). Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x1278746 (Pictures); these messages lack timestamps and therefore suck. ** (gnome-panel:2671): WARNING **: Could not ask power manager to suspend: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security polic --------------------------------------------------
In my view reported bug is dup of bug 458247 but traces provided in comment#2 are totally different.
+ Trace 189825
Wait I fixed this for 2.21.91+ Just see bug #501295
Please reopen the bug if you still face in current stable 2.22.3.1, thanks. *** This bug has been marked as a duplicate of 501295 ***