evolution-alarm-notify crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #354067 reported by Alexey Ozerov
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

System was upgraded from 8.10 to Alfa 6.
I suppose that this error was appeared exactly after upgrade, but I didn't send the report because I had a problem with 'Report problem' feature: I didn't get any GUI windows after password's entering. After upgrade on 02 April this issue was disappeared.

0) Hardware: Laptop Samsung X50-T00

1) $ lsb_release -rd
Description: Ubuntu jaunty (development branch)
Release: 9.04

2) $ apt-cache policy evolution-alarm-notify
W: Unable to locate package evolution-alarm-notify

3) I didn't expect Application problems after system start.

4) I've got 4 "Application problems" report with gdebi (https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/354052), evolution (https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/354061), xneur & evolution-alarm-notify(this report) All these reports will be/already sent to launchpad, probably they all have the same root cause.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/evolution/2.26/evolution-alarm-notify
Package: evolution 2.26.0-0ubuntu2
ProcCmdline: /usr/lib/evolution/2.26/evolution-alarm-notify
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: evolution-alarm-notify crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare vboxusers video

Revision history for this message
Alexey Ozerov (alexozerov) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:open_alarm_dialog (tray_data=0xa121538) at alarm-queue.c:295
tray_icon_clicked_cb (widget=<value optimized out>,
icon_activated (icon=0xa0e4158) at alarm-queue.c:1375
IA__g_cclosure_marshal_VOID__VOID (closure=0xa111be8,
IA__g_closure_invoke (closure=0xa111be8, return_value=0x0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Changed in evolution (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=577770

Changed in evolution (Ubuntu):
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in evolution:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Upstream is requesting more information:

"a) close evolution
b) run evolution --force-shutdown
c) change key /apps/evolution/calendar/notify/last_notification_time
   to some small value, or even empty, which will invoke all the alarms again
d) run evolution, or directly evolution-alarm-notify, and click on the icon to
show all the alarms, what will happen.
Thanks in advance.
"

Could you please do it and comment back? thanks in advance.

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

Any news about this ? did you test what we asked to you? Upstream is waiting for that information, could you please test?

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

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in evolution (Ubuntu):
status: Incomplete → Invalid
Changed in evolution:
status: Incomplete → Invalid
Changed in evolution:
importance: Unknown → Critical
status: Invalid → Expired
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.