indicator-datetime-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The bug happens on a ACER v5-571G with nvidia 620M Optimus, nvidia drivers and nvdia-prime.
Every time at boot
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 13.10.0+
ProcVersionSign
Uname: Linux 3.11.0-5-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12.1-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 9 21:03:12 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-06-23 (78 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcCwd: /home/gmkey
SegvAnalysis:
Segfault happened at: 0x7fa727aa8f90 <_IO_vfprintf_
PC (0x7fa727aa8f90) ok
source "%es:(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
Title: indicator-
UpgradeStatus: Upgraded to saucy on 2013-09-09 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1195874, 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.