Ubuntu
evolution package

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

Bug #273951 reported by Joe
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Evolution
Expired
Critical
evolution (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: evolution

Description: Ubuntu intrepid (development branch)
Release: 8.10

evolution:
  Installed: 2.24.0-0ubuntu1
  Candidate: 2.24.0-0ubuntu1
  Version table:
 *** 2.24.0-0ubuntu1 0
        500 http://ubuntu.intergenia.de intrepid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/evolution/2.24/evolution-alarm-notify
Package: evolution 2.24.0-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/lib/evolution/2.24/evolution-alarm-notify --oaf-activate-iid=OAFIID:GNOME_Evolution_Calendar_AlarmNotify_Factory:2.24 --oaf-ior-fd=20
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 SHELL=/bin/bash
Signal: 11
SourcePackage: evolution
StacktraceTop:
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
 gtk_window_group_new () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_window_get_group () from /usr/lib/libgtk-x11-2.0.so.0
Title: evolution-alarm-notify crashed with SIGSEGV in g_object_newv()
Uname: Linux 2.6.27-4-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare

Tags: apport-crash
Revision history for this message
Joe (classicmaster) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_object_new_valist (object_type=160518568, first_property_name=0x0,
IA__g_object_new (object_type=160518568, first_property_name=0x0)
IA__gtk_window_group_new () at /build/buildd/gtk+2.0-2.14.2/gtk/gtkwindow.c:7390
IA__gtk_window_get_group (window=0x0) at /build/buildd/gtk+2.0-2.14.2/gtk/gtkwindow.c:7523
gtk_main_get_window_group (widget=<value optimized out>)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in evolution:
importance: Undecided → Medium
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=553631

Changed in evolution:
assignee: nobody → desktop-bugs
status: New → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Unknown → New
Revision history for this message
Douglas Escalante (djescalante) wrote :

He tenido problemas al leer los correos en correo evolution, obteniendo el siguiente mensaje "evolution-alarm-notify crashed with SIGSEGV in g_object_newv()".
Alguien tienen forma de solucionar el problema

Bug Watch Updater (bug-watch-updater)
Changed in evolution:
importance: Unknown → Critical
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: New → Expired
Revision history for this message
Omer Akram (om26er) wrote :

upstream bug closed since this version of evolution is no longer supported and there have been no duplicate bug reports. closing the ubuntu bug too. if you still have the issue in ubuntu 10.10 please re-open this bug.

Changed in evolution (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → Invalid
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I think I have seen something quite similar to this bug. I made a fresh report as Bug #1548226 which includes some valid symbolic stack traces. Hopefully the developers will be able to use them to work on the issue.

Should this bug ticket be marked as a duplicate of Bug #1548226 as the circumstances in which it happens are very similar?

If this is thought to be the same bug then perhaps the upstream records should also be amended as I must be using a more recent version of evolution.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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