evolution crashed with SIGSEGV in strlen()

Bug #299021 reported by Nick Jenkins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

I'm presuming this is not a dupe of bug 292637 because I was not in offline mode when this happened (or at least, I did not manually put the app into offline mode), and app had been running for a while (i.e. was not starting up).

Happened when double clicking on calendar item, which had just been imported into the calendar (the calendar item was a flight booking .ICS file generated by an airline's flight reservation system).

Ubuntu 8.04.1, evolution 2.22.3.1

ProblemType: Crash
Architecture: amd64
Date: Mon Nov 17 23:23:17 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evolution
Package: evolution 2.22.3.1-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: evolution --component=mail
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 strlen () from /lib/libc.so.6
 e_dialog_editable_set ()
 ?? ()
 ?? ()
 ?? ()
Title: evolution crashed with SIGSEGV in strlen()
Uname: Linux 2.6.24-21-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Tags: apport-crash
Revision history for this message
Nick Jenkins (nickpj) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:strlen () from /lib/libc.so.6
e_dialog_editable_set (widget=0x250e6d0,
event_page_fill_widgets (page=0x2532ac0,
real_edit_comp (editor=0x180e4c0, comp=0x7fa93f943ee0)
event_editor_edit_comp (editor=0x180e4c0,

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
Pedro Villavicencio (pedro) wrote :

Thanks for your report, that's known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=517625

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in evolution:
status: Unknown → New
Changed in evolution:
importance: Unknown → Critical
status: New → Expired
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

hardy not longer supported
please change status to Won't fix

Revision history for this message
Nick Jenkins (nickpj) wrote :

Yes this bug is obsolete now (software is 5+ years old), but I can't see a bug status option for "Obsolete" or "Expired", only "Invalid" - but this was a valid problem in this software. Seems like there's no status available that I can select that reflects what actually happened?

Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

change status to invalid

Changed in evolution (Ubuntu):
status: Triaged → Invalid
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.