indicator-datetime-preferences crashed with SIGABRT in g_option_context_parse()
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
ProcVersionSign
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
Date: Thu May 26 21:28:51 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
ProcCmdline: indicator-
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
Signal: 6
SourcePackage: indicator-datetime
StacktraceTop:
?? () from /usr/lib/
g_option_
gtk_parse_args () from /usr/lib/
gtk_init_check () from /usr/lib/
gtk_init () from /usr/lib/
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Related branches
- Indicator Applet Developers: Pending requested
-
Diff: 371 lines (+89/-151)4 files modifiedconfigure.ac (+27/-68)
libmap/cc-timezone-map.c (+9/-43)
src/datetime-prefs.c (+50/-37)
src/timezone-completion.c (+3/-3)
Changed in indicator-datetime (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: amd64 |
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."