indicator-datetime-preferences crashed with SIGABRT in g_option_context_parse()

Bug #788801 reported by Jean-Baptiste Lallement
134
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Indicator Date and Time
Fix Released
Undecided
Unassigned
indicator-datetime (Ubuntu)
Fix Released
Medium
Michael Terry
Oneiric
Fix Released
Medium
Michael Terry

Bug Description

Binary package hint: indicator-datetime

I clicked on the clock then "Time & Date Settings ..." nothing happened then this crash after few seconds.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.39-3.9-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Thu May 26 21:28:51 2011
ExecutablePath: /usr/bin/indicator-datetime-preferences
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: indicator-datetime-preferences
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_option_context_parse () from /lib/i386-linux-gnu/libglib-2.0.so.0
 gtk_parse_args () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_init_check () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_init () from /usr/lib/libgtk-x11-2.0.so.0
Title: indicator-datetime-preferences crashed with SIGABRT in g_option_context_parse()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
visibility: private → public
Changed in indicator-datetime (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
tags: added: amd64
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I just reported bug 797146, which looks a lot like this and I suspect should be considered a duplicate, but I'm not sure. Program termination in bug 797146 occurred in a way I have not previously seen in programs not being actively debugged.

From bug 797146's description: "I'm not sure whether or not this should be considered a duplicate of bug 788801. In that bug, g_logv() called abort(), which triggered abnormal program termination with SIGABRT by calling raise(). In this bug, it appears that the program is terminated within g_logv() with SIGTRAP."

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Here is the trace. From the error "GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported" it looks like it needs to be ported to gtk3

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in indicator-datetime (Ubuntu Oneiric):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Martin Pitt (pitti) wrote :

Mike, do you have time to look into porting this to GTK3?

Changed in indicator-datetime (Ubuntu Oneiric):
assignee: Canonical Desktop Team (canonical-desktop-team) → Michael Terry (mterry)
importance: Medium → High
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I just posted duplicate bug 797162, which contains a complete stack trace. (It also specifically supersedes duplicate bug bug 797146, for whatever that's worth--I filed bug 797162 before I saw that bug 797146 was being definitely considered a duplicate of this bug.)

Revision history for this message
Michael Terry (mterry) wrote :

Sure.

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

duplicate bug #783958?

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __kernel_vsyscall ()
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:60
 abort () at abort.c:94
 mklevel_prefix (level_prefix=0x2 <Address 0x2 out of bounds>, log_level=G_LOG_LEVEL_ERROR) at /build/buildd/glib2.0-2.29.8/./glib/gmessages.c:790
 ?? ()

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 indicator-datetime (Ubuntu):
importance: High → Medium
tags: removed: need-i386-retrace
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing this issue as now the date time preferences opens as expected.

Changed in indicator-datetime:
status: New → Fix Released
Changed in indicator-datetime (Ubuntu Oneiric):
status: Confirmed → Fix Released
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.