indicator-sync-service crashed with SIGSEGV in g_type_check_instance_is_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-sync (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
despues de arrancar actualizacion de software
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: indicator-sync 12.10.5daily13.
ProcVersionSign
Uname: Linux 3.8.0-11-generic i686
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
Date: Sun Mar 10 11:47:24 2013
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2013-02-17 (20 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130213)
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=es_ES.UTF-8
SegvAnalysis:
Segfault happened at: 0xb751f1f7 <g_type_
PC (0xb751f1f7) ok
source "$0x4" ok
destination "0xe(%ecx)" (0x2e67727a) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: indicator-sync
StacktraceTop:
g_type_
g_object_unref () from /usr/lib/
?? () from /usr/lib/
g_object_unref () from /usr/lib/
?? ()
Title: indicator-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
gnome-
gnome-
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 #1123924, 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.