indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Indicator Date and Time |
Fix Released
|
Undecided
|
Unassigned | ||
Unity Foundations |
Fix Released
|
High
|
Karl Lattimer | ||
unity-2d |
Fix Released
|
High
|
Unassigned | ||
indicator-datetime (Ubuntu) |
Fix Released
|
High
|
Karl Lattimer |
Bug Description
Binary package hint: indicator-datetime
Crashed just after login.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.1.96-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-6-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
Date: Sat Mar 12 14:32:03 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64+mac (20110307)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x4048fa: mov 0x0(%rbp,
PC (0x004048fa) ok
source "0x0(%rbp,%rcx,1)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
?? ()
?? ()
?? ()
g_main_
?? () from /lib/libglib-
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Related branches
- Ted Gould (community): Approve
-
Diff: 364 lines (+121/-69)2 files modifiedsrc/datetime-service.c (+113/-53)
src/indicator-datetime.c (+8/-16)
- Ken VanDine: Pending requested
-
Diff: 301 lines (+59/-27) (has conflicts)8 files modifiedChangeLog (+32/-0)
configure (+10/-19)
configure.ac (+1/-2)
data/datetime-dialog.ui (+0/-1)
debian/changelog (+14/-0)
debian/control (+0/-2)
src/datetime-prefs.c (+0/-1)
src/datetime-service.c (+2/-2)
Changed in unity-2d: | |
importance: | Undecided → High |
milestone: | none → 3.8 |
visibility: | private → public |
Changed in indicator-datetime (Ubuntu): | |
importance: | Undecided → High |
Changed in unity-foundations: | |
importance: | Undecided → High |
assignee: | nobody → Karl Lattimer (karl-qdh) |
Changed in indicator-datetime (Ubuntu): | |
milestone: | none → ubuntu-11.04-beta-1 |
Changed in unity-foundations: | |
milestone: | none → unity-3.6.6 |
Changed in indicator-datetime (Ubuntu): | |
assignee: | nobody → Karl Lattimer (karl-qdh) |
Changed in indicator-datetime: | |
milestone: | none → 0.1.98 |
status: | New → Fix Released |
Changed in unity-foundations: | |
status: | New → Fix Released |
Changed in unity-2d: | |
status: | New → Fix Released |
@Florian, is this bug reproducible?
Can you install debug symbols and try to get a better stack trace (installing related -dbgsym packages should be enough)