In an attempt to reproduce bug 789961 on the Oneiric i386 20110614 daily-live (same indicator-datetime package version: 0.2.3-0ubuntu3), I logged in with a unity-2d session and clicked "Time & Date Settings..." in the time/date (calendar) applet menu. This similar crash occurred instead. This crash is a bit strange, since signal 5 is SIGTRAP, which typically occurs only when a program is being actively debugged.
I'm not sure whether or not this should be considered a duplicate of bug 789961. 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.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.0-0.1-generic 3.0.0-rc2
Uname: Linux 3.0-0-generic i686
Architecture: i386
Date: Tue Jun 14 11:31:31 2011
ExecutablePath: /usr/bin/indicator-datetime-preferences
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110614)
ProcCmdline: indicator-datetime-preferences
ProcCwd: /
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
Signal: 5
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 signal 5 in g_option_context_parse()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Binary package hint: indicator-datetime
In an attempt to reproduce bug 789961 on the Oneiric i386 20110614 daily-live (same indicator-datetime package version: 0.2.3-0ubuntu3), I logged in with a unity-2d session and clicked "Time & Date Settings..." in the time/date (calendar) applet menu. This similar crash occurred instead. This crash is a bit strange, since signal 5 is SIGTRAP, which typically occurs only when a program is being actively debugged.
I'm not sure whether or not this should be considered a duplicate of bug 789961. 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.
ProblemType: Crash ature: Ubuntu 3.0-0.1-generic 3.0.0-rc2 indicator- datetime- preferences datetime- preferences libgtk- x11-2.0. so.0 context_ parse () from /lib/i386- linux-gnu/ libglib- 2.0.so. 0 libgtk- x11-2.0. so.0 libgtk- x11-2.0. so.0 libgtk- x11-2.0. so.0 datetime- preferences crashed with signal 5 in g_option_ context_ parse()
DistroRelease: Ubuntu 11.10
Package: indicator-datetime 0.2.3-0ubuntu3
ProcVersionSign
Uname: Linux 3.0-0-generic i686
Architecture: i386
Date: Tue Jun 14 11:31:31 2011
ExecutablePath: /usr/bin/
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110614)
ProcCmdline: indicator-
ProcCwd: /
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
Signal: 5
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