unity-settings-daemon crashed with SIGSEGV in g_settings_backend_changed()

Bug #1282905 reported by Vyacheslav Sedov
116
This bug affects 27 people
Affects Status Importance Assigned to Milestone
unity-settings-daemon (Ubuntu)
Confirmed
High
Unassigned

Bug Description

maybe something wrong with skype

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-settings-daemon 14.04.0+14.04.20140219-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
Uname: Linux 3.13.0-10-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Fri Feb 21 11:05:37 2014
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-02-09 (12 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140208)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f46bbf452ac: mov (%rax,%r13,1),%rax
 PC (0x7f46bbf452ac) ok
 source "(%rax,%r13,1)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_backend_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
Title: unity-settings-daemon crashed with SIGSEGV in g_settings_backend_changed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Vyacheslav Sedov (schematronic) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f46bbf452ac in ?? ()
 #1 0x00007f46ac001e10 in ?? ()
 #2 0x00000000017c52d0 in ?? ()
 #3 0x00000000018095f0 in ?? ()
 #4 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

It prevents the package (or a dependent one) from functioning correctly at all.

Changed in unity-settings-daemon (Ubuntu):
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.