GNOME Bugzilla – Bug 585435
Evolution: Control i crashes/closes...
Last modified: 2009-06-18 03:42:33 UTC
Control i crashes/closes down Evolution in SuSE 11.1 64bit. Distribution: openSUSE 11.1 (x86_64) Gnome Release: 2.24.1 2009-03-09 (SUSE) BugBuddy Version: 2.24.1
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Based on what I have learned thus far from getting a backtrace report with bug-buddy, I have to inform you that bug buddy is not automatically triggered when Evolution shuts down although I have all the packages installed to obtain such a report. Perhaps you could suggest a means to force triggering of bug buddy.
Sure. :-) You can run evolution within gdb. See http://live.gnome.org/GettingTraces/Details#obtain-a-stacktrace
Thank you for the help Andre (sorry no accent). The exercise was worse than pulling hens teeth :-) But here is the stack trace and I hope that I did it right. (gdb) cont Continuing. [New Thread 0x7fde52ffd950 (LWP 7449)] [New Thread 0x7fde50ff9950 (LWP 7450)] [Thread 0x7fde50ff9950 (LWP 7450) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fde52ffd950 (LWP 7449)] 0x00007fde77bd301a in camel_mime_parser_read () from /usr/lib64/libcamel-1.2.so.14 (gdb) thread apply all bt
+ Trace 215963
Thread 7 (Thread 0x7fde52ffd950 (LWP 7449))
(gdb) Quit
Thanks. Looks like a good start, though still a bit generic and it is missing the exact file names and line numbers in the code. Can you please install debuginfo packages for evolution-data-server, evolution, glib2 and gtk2 and after that post the stacktrace from within gdb here again?
could be a dupe of bug 569700
Ok Andre, I think some progress was made here although not what you expect. Firstly, I installed the following packages: evolution-dadta-server-debuginfo and the equivalent 32bit package, glib2-debuginfo and the equivalent 32 bit package, gtk2-debuginfo and the equivalent 32 bit package, evolution-debuginfo. Why there are 32bit packages escapes me. The gdm back trace report looked almost similar to the one posted earlier containing lots of "?". Accordingly I decided not to post it. However, after installing the above 7 packages, bug-buddy got triggered and produced the following report: Distribution: openSUSE 11.1 (x86_64) Gnome Release: 2.24.1 2009-03-09 (SUSE) BugBuddy Version: 2.24.1 System: Linux 2.6.27.23-0.1-default #1 SMP 2009-05-26 17:02:05 -0400 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10502000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche Memory status: size: 705953792 vsize: 705953792 resident: 34598912 share: 23527424 rss: 34598912 rss_rlim: 18446744073709551615 CPU usage: start_time: 1244784580 rtime: 122 utime: 118 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' #[?1034h(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 0x7fcfa3fb1950 (LWP 8613)] [New Thread 0x7fcf932c8950 (LWP 8604)] [New Thread 0x7fcf99712950 (LWP 8599)] [New Thread 0x7fcfa1360950 (LWP 8598)] [New Thread 0x7fcfa37b0950 (LWP 8592)] [New Thread 0x7fcfa47b2950 (LWP 8589)] (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) 0x00007fcfb8b335af in waitpid () from /lib64/libpthread.so.0
+ Trace 215975
Thread 2 (Thread 0x7fcfa3fb1950 (LWP 8613))
No symbol table info available. The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (359 sec old) --------------------- ** (nautilus:7510): WARNING **: Unable to add monitor: Not supported gnome-session[7356]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout W: main.c: High-priority scheduling enabled in configuration but not allowed by policy. ** (nm-applet:7621): WARNING **: No connections defined beagled will run in the background. Use beagle-status to check progress of beagled. For log files check /home/heribert/.beagle/Log/current-Beagle. /usr/lib64/python2.6/site-packages/dbus/connection.py:242: DeprecationWarning: object.__init__() takes no parameters super(Connection, self).__init__(*args, **kwargs) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Starting t) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800003 (Software M) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- It appears that some other packages need to be installed - but which ones?
On second thought I decided to incude the bt report with the 7 packages installed and which I listed in my previous message. Perhaps it sheds some more light as to what is the problem. Here it goes: (gdb) cont Continuing. [New Thread 0x7fa3fd00f950 (LWP 5184)] [Thread 0x7fa3fd00f950 (LWP 5184) exited] [New Thread 0x7fa3fd00f950 (LWP 5185)] [New Thread 0x7fa3fec29950 (LWP 5186)] [Thread 0x7fa3fec29950 (LWP 5186) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fa3fd00f950 (LWP 5185)] 0x00007fa41d9a601a in camel_mime_parser_read () from /usr/lib64/libcamel-1.2.so.14 (gdb) thread apply all bt
+ Trace 215989
Thread 8 (Thread 0x7fa3fd00f950 (LWP 5185))
(gdb) q The program is running. Quit anyway (and detach it)? (y or n) y Detaching from program: /usr/bin/evolution.bin, process 4978
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 569700 ***
Thank you for your assistance to date. It is well appreciated. However I would like to make use of an earlier offer by Mr. Klapper to ask questions. I listed a query as to an updated version of Evolution in the openSuSE forum under applications. One reply referred me to openSuSE built service for updates. I have tried to install two packages, namely evolution-2.24.4-6.3.x86_64.rpm and evolution-2.24.1.1-4.9.x86_64.rpm. However none of them did install due to either differences in library files or some other requirements. I have given up to tinker any further because I did not want to jeopardize the functionality of the O/S and moreover the virtual platform and its corresponding software on which I have spend days to install and tweak. In light of the above, would you recommend the use of the built service and if so which package. I find it really unfortunate that while the bug is fixed no update is issued on the regular repository. Thank you very kindly for indulging my question.
I am not whether the patch was committed for OpenSUSE update or not. I can suggest you a link [1] where you can find 2.26.x and it won't harm your system. [1] http://download.opensuse.org/repositories/GNOME:/Evolution:/snapshots/openSUSE_11.1+GNOME_2.26/