GNOME Bugzilla – Bug 597342
crash in Evolution: after downgrading to 2.2...
Last modified: 2009-10-04 22:55:54 UTC
What were you doing when the application crashed? after downgrading to 2.27.92: opensuse-11-2-M8:/home/marco # rpm -qi evolution Name : evolution Relocations: (not relocatable) Version : 2.27.92 Vendor: openSUSE Release : 1.2 Build Date: ven 25 set 2009 13:36:36 BRT Install Date: dom 04 ott 2009 15:26:05 BRT Build Host: build12 Group : Productivity/Networking/Email/Clients Source RPM: evolution-2.27.92-1.2.src.rpm Size : 13735851 License: LGPL v2.0 only ; LGPL v3 only Signature : RSA/8, ven 25 set 2009 13:48:11 BRT, Key ID b88b2fd43dbdc284 Packager : http://bugs.opensuse.org URL : http://gnome.org/projects/evolution/ Summary : The Integrated GNOME Mail, Calendar, and Address Book Suite Description : Evolution consists of modular components (at the moment: mailer, calendar, and address book) that should make daily life easier. Because of the modular design, it is possible to plug new components into Evolution or embed the existing ones in other applications. Distribution: openSUSE Factory I back to edit one message which I wish to reply selecting a part of the body to delete, but evolution crashed again Distribution: openSUSE 11.2 Milestone 8 (i586) Gnome Release: 2.28.0 (null) (SUSE) BugBuddy Version: 2.28.0 System: Linux 2.6.31-10-default #1 SMP 2009-09-29 11:18:23 +0200 i686 X Vendor: The X.Org Foundation X Vendor Release: 10604000 Selinux: No Accessibility: Disabled GTK+ Theme: OpenSuse-NextG-theme Icon Theme: OxygenRefit2-green-version GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 375939072 vsize: 375939072 resident: 47439872 share: 30101504 rss: 47439872 rss_rlim: 18446744073709551615 CPU usage: start_time: 1254681144 rtime: 4469 utime: 902 stime: 3567 cutime:8 cstime: 182 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution.bin' [Thread debugging using libthread_db enabled] [New Thread 0xa4da6b70 (LWP 5513)] [New Thread 0xa4506b70 (LWP 5512)] [New Thread 0xa5739b70 (LWP 5446)] [New Thread 0xb2bb1b70 (LWP 5445)] [New Thread 0xb4bc1b70 (LWP 5439)] [New Thread 0xb53c2b70 (LWP 5438)] 0xffffe422 in __kernel_vsyscall ()
+ Trace 218049
Thread 1 (Thread 0xb61e7760 (LWP 5404))
A debugging session is active. Inferior 1 [process 5404] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (2953 sec old) --------------------- Nautilus-Share-Message: ------------------------------------------ Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' ha restituito l'errore 255: net usershare: usershares are currently disabled Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x4c00004 non valido per 0x4c00024 (amarok). InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 091004 15:01:19 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. InnoDB: Reading tablespace information from the .ibd files... InnoDB: Restoring possible half-written data pages from the doublewrite InnoDB: buffer... <unknown program name>(3733)/: Communication problem with "amarok" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the Object::connect: No such signal KLineEdit::downPressed() --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 596290 ***
Created attachment 144749 [details] bug-buddy registration