Crash when adding customised reminder to a newly added appointment

Bug #351033 reported by Nikke
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: evolution

:: Current system and packages
Description: Ubuntu jaunty (development branch)
Release: 9.04
evolution:
  Installed: 2.26.0-0ubuntu2
  Candidate: 2.26.0-0ubuntu2
  Version table:
 *** 2.26.0-0ubuntu2 0
        500 http://se.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

:: Steps to reproduce:
1. Open the calendar
2. Right-click March 29 23.00 (current time is March 29 17:55)
3. Create new appointment
4. Add a summary ("Test") and leave all other fields as is
5. Click the alarms button
6. Choose "Customise" from the drop-down "Alarm"
7. Click "Add"-button
8. Evolution crashes

:: Expected result
The appointement should be added with an alarm set to 15 minutes before the appointment.

:: Debug output
Attached the output from running "evolution --debug file".

/Niklas

Revision history for this message
Nikke (nmellegard) wrote :
Revision history for this message
Nikke (nmellegard) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution (Ubuntu):
status: New → Invalid
Revision history for this message
Pedro Villavicencio (pedro) wrote :

btw the crash is not reproducible here.

Revision history for this message
Nikke (nmellegard) wrote :

Hello
I am running the standard gnome Ubuntu and have Apport is enabled, but it seems the crash isn't caught by it!

Regarding reproducability:
I forgot to mention that the crash happens with a Google calendar (sorry about that). I tested the same procedure with a local calendar without issues, but the same with a Google calendar crashes every time.

Thanks
N

Revision history for this message
Nikke (nmellegard) wrote :

Read post on planet Ubuntu this morning:
"Don't report bug directy to Launchpad, run ubuntu-bug instead"

Good advice. Please Pedro, close this bug and continue with bug #353226 instead.

Thanks
N

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.