evolution-alarm-notify crashed after daylight saving change

Bug #748551 reported by Rick Pontefract
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

The evolution alarm notifier process crashed when waking up my laptop the morning after the clocks went back due to daylight savings ending in New Zealand.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu10.2
ProcVersionSignature: Ubuntu 2.6.32-30.59-generic-pae 2.6.32.29+drm33.13
Uname: Linux 2.6.32-30-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Apr 3 07:08:34 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/evolution/2.28/evolution-alarm-notify
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
ProcCmdline: /usr/lib/evolution/2.28/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.28 --oaf-ior-fd=38
ProcEnviron:
 LANG=en_NZ.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x805b1dd <alarm_trigger_cb+877>: mov 0xc(%eax),%eax
 PC (0x0805b1dd) ok
 source "0xc(%eax)" (0x636f6c3b) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: evolution
StacktraceTop:
 popup_notification (alarm_id=0xa02a148, trigger=1301745600,
 alarm_trigger_cb (alarm_id=0xa02a148, trigger=1301745600, data=0xa025000)
 alarm_ready_cb (data=0x0) at alarm.c:108
 g_timeout_dispatch (source=0xa01b680, callback=0x636f6c2f,
 g_main_dispatch (context=0x9fb38a0)
Title: evolution-alarm-notify crashed with SIGSEGV in popup_notification()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Rick Pontefract (rjpontefract) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 alarm_trigger_cb (alarm_id=0xa02a148, trigger=1301745600,
 alarm_ready_cb (data=0x0) at alarm.c:108
 g_timeout_dispatch (source=0xa01b680, callback=0x636f6c2f,
 IA__g_main_context_dispatch (context=0x9fb38a0)
 g_main_context_iterate (context=0x9fb38a0,

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jörg Frings-Fürst (jff-de) wrote :

10.04 is not longer supported
change status to invalid

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