indicator-datetime-service crashed with SIGSEGV in g_object_ref()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-datetime (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
servant at The-Goddess in ~
$ lsb_release -rd
Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
servant at The-Goddess in ~
$ apt-cache policy indicator-datetime
indicator-datetime:
Installed: 12.10.3+
Candidate: 12.10.3+
Version table:
*** 12.10.3+
500 http://
100 /var/lib/
This crash literaly randomly occurs over a givn period that my machine is on.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: indicator-datetime 12.10.3+
ProcVersionSign
Uname: Linux 3.10.0-6-generic i686
ApportVersion: 2.12-0ubuntu3
Architecture: i386
CrashCounter: 1
Date: Wed Aug 7 16:11:16 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-08-01 (6 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_US
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0xb74150ee <g_object_ref+30>: cmpl $0x50,(%eax)
PC (0xb74150ee) ok
source "$0x50" ok
destination "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-datetime
StacktraceTop:
g_object_ref () from /usr/lib/
g_weak_ref_get () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/i386-
g_main_
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1197645, 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.