evolution crashed with SIGSEGV in g_signal_emit_valist()

Bug #270271 reported by Matthias Urlichs
404
This bug affects 35 people
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Critical
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Reproducible crash when switching to Calendar view. Looks like a release blocker, didn't happen two weeks ago.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.23.91-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: evolution --component=mail
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Title: evolution crashed with SIGSEGV in g_signal_emit_valist()
Uname: Linux 2.6.26-5-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Matthias Urlichs (smurf) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:spi_atk_bridge_signal_listener (signal_hint=0xbfba521c, n_param_values=3, param_values=0x8d9fb10, data=0x8644898)
signal_emit_unlocked_R (node=0x8634a38, detail=0, instance=0x8acc228, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x8acc228, signal_id=110, detail=0,
IA__g_signal_emit_by_name (instance=0x8acc228, detailed_signal=0xb5c9b952 "children_changed")
idle_dates_changed (data=0x8acc228) at ea-cal-view.c:283

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
importance: Undecided → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, the crash is similar to http://bugzilla.gnome.org/show_bug.cgi?id=551845

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in evolution:
status: Unknown → New
Changed in evolution:
status: New → Invalid
Changed in evolution:
status: Invalid → Confirmed
Revision history for this message
Allan Caeg (allancaeg) wrote :

I know it's odd but it works fine on KDE4 Intrepid. LOL

Revision history for this message
gadLinux (gad-aguilardelgado) wrote :

The information reported by Timothy Alexander in bug #290796 works:

----
FYI for future people.

To disable accessibility, got to System->Preferences->Assistive
Technologies

Uncheck the "enable assistive technologies" box.
----

Revision history for this message
James Moschou (james-moschou) wrote :

I get this bug too when I run
$ evolution --component=mail
but not when I run evolution without any arguments.

Revision history for this message
Michael (m-gruys) wrote :

The bug does not occur anymore when you login with ssh -X <host> with another (virtual) machine and start evolution in the shell!
Then evolution does not crash anymore :-)
Strange....

Revision history for this message
Michael (m-gruys) wrote :

Please ignore my last comment.
It is as 'gadLinux' wrote: Uncheck the "enable assistive technologies" box. (System->Preferences->Assistive
Technologies)

But this was not enough for me because some processes which use this Technology were in use.
I had to log out (come into greeter screen) and do a <CTRL><ALT><F1> en log in as root
then I had to do a pkill -u <username> to kill some remaining locked processes
And then indeed the bug does not occur anymore

Revision history for this message
Benjamin Couhe (voraistos-googlemail) wrote :

I don't have assistive technologies enabled, I have tried launching evolution with and without options, and the bug only occurs when, in the calendar section, i try to click on the default "contacts" section in the tree.

Revision history for this message
Bruce Crowther (bwucie) wrote :

Last night Evolution was working fine, this morning, without having changed anything, it crashes with a sefault if I try to use the button at the bottom of the sidebar to switch to the calendar. (Ubuntu 8.10 AMD64, Evolution 2.24.1).
Experimentation has shown me that I can invoke the program to open directly into the calendar by double clicking on a date in the drop down from the clock applet. Then it will behave as normal, during that session.
If I then shut the program down in any view other than the calendar, it will segfault when I try to click from any other view, mail, memos, etc, to Calendar.
If I shutdown with in the calendar view, the program runs fine next time.
There is no record of the event in /var/crash, and I am not tech enough to know how to trace what's going on.
Using a terminal to start Evolution doesn't tell me much, as per the attachment.
At least I have a workaround, so it's only a minor annoyance.
Regards,
Bruce

Revision history for this message
Bruce Crowther (bwucie) wrote :

Shortly after posting the above, and closing down the computer, I found, on rebooting that I had the famous ".dmrc file being ignored" pop-up.
Attempting to fix that via the terminal, I must have entered a typo when recursively changing the mode and ownership of my home partition, and lost /home, and of course, booting, for a couple of hours.
After repairing that problem (via google and my WinDoze part: good thing the machine is still dual-boot!) Evolution is behaving normally. Go figure.
Kind regards,
Bruce.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now

Changed in evolution:
status: Triaged → Fix Committed
Revision history for this message
rrichter (rrichterzittau-deactivatedaccount) wrote :

Cant found a bugfix with apt-get update !
The program crashes again.

Changed in evolution:
status: Confirmed → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

upstream rolled a new stable version today which has been uploaded as a candidate update to intrepid now

Changed in evolution:
status: Invalid → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version is in jaunty now

Changed in evolution:
status: Fix Committed → Fix Released
Revision history for this message
Apteryx (maxco) wrote :

Happened to me in the latest Karmic. Apport was used to submit report. Bug is not really reproducible though. If I nail how to reproduce it I will post here.

Revision history for this message
m0m0 (a0005783) wrote :

I must confirm what Apteryx said (on Karmic Beta AMD 64). Can't reproduce it either and was the first time since I use the beta.

stlnative (stlnative)
Changed in evolution (Ubuntu):
status: Fix Released → Fix Committed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Please open a new report with apport rather than re opening this one which was closed several months ago, thanks.

Changed in evolution (Ubuntu):
status: Fix Committed → Fix Released
Changed in evolution:
importance: Unknown → Critical
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.