indicator-datetime-service crashed with SIGSEGV in g_main_context_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: indicator-datetime
1) $ lsb_release -rd
Description: Ubuntu Natty (development branch)
Release: 11.04
2) $ apt-cache policy indicator-datetime
indicator-datetime:
Zainstalowana: 0.1.96-0ubuntu1
Kandydująca: 0.1.96-0ubuntu1
Tabela wersji:
*** 0.1.96-0ubuntu1 0
500 http://
100 /var/lib/
3) Nothing
4) It crashed out without any visible reason. From now on I noticed that my timer started counting seconds properly, previously it counted every other second.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-datetime 0.1.96-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 8 15:44:41 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=pl_PL:en
LANG=pl_PL.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: Upgraded to natty on 2011-03-07 (1 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #729444, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.