Crash when adding customised reminder to a newly added appointment

Bug #353226 reported by Nikke
8
Affects Status Importance Assigned to Milestone
Evolution
Fix Released
Medium
evolution (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

This is the same as bug #351033 but reported through ubuntu-bug (read a post about it on Planet Ubuntu this morning!).

Cheers
N

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: evolution 2.26.0-0ubuntu2
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux 2.6.28-11-generic x86_64

Related branches

Revision history for this message
Nikke (nmellegard) wrote :
Revision history for this message
Nikke (nmellegard) wrote :

In summary (from the previous bug report):

:: Steps to reproduce:
1. Open the _Google_ calendar (this is not reproducible with a local 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 appointment should be added with an alarm set to 15 minutes before the appointment.

:: Debug output
Attached the output from running "evolution --debug file".
Note! The crash is not caught by apport...

/N

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

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

Backtrace attached!

/N

Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in evolution (Ubuntu):
status: Incomplete → Triaged
Changed in evolution:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream and the fix will be in jaunty

Changed in evolution (Ubuntu):
status: Triaged → Fix Committed
Changed in evolution:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package evolution - 2.26.0-0ubuntu3

---------------
evolution (2.26.0-0ubuntu3) jaunty; urgency=low

  * debian/patches/90_svn_update.patch:
    - update to the current svn version so it get testing before next tarball
      (lp: #233620, #347852, #302637, #345189, #290287, #353226)

 -- Sebastien Bacher <email address hidden> Wed, 08 Apr 2009 18:24:08 +0200

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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