evolution-alarm-notify crashed with SIGSEGV

Bug #181233 reported by Dagfinn Ilmari Mannsåker
8
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

The crash occured immediately on login.

ProblemType: Crash
Architecture: i386
Date: Tue Jan 8 13:08:14 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/evolution/2.22/evolution-alarm-notify
Package: evolution 2.21.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/2.22/evolution-alarm-notify --sm-config-prefix /evolution-alarm-notify-jb9q6u/ --sm-client-id 117f000001000119767799700000059980006 --screen 0
ProcCwd: /home/ilmari
ProcEnviron:
 LC_TIME=en_IE.UTF-8
 LANGUAGE=en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
Stacktrace:
 #0 0xb6e8263b in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: evolution-alarm-notify crashed with SIGSEGV
Uname: Linux vesla 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner staff video

Revision history for this message
Dagfinn Ilmari Mannsåker (ilmari) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /lib/tls/i686/cmov/libc.so.6
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in evolution:
status: Incomplete → 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.