gnome-settings-daemon crashed with SIGSEGV in g_file_make_directory_with_parents()

Bug #1035725 reported by critin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

Fresh install of Quantal ubuntu 12.10 daily build, Aug.11, standard desktop i386. System fail upon restart after usb install.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic i686
ApportVersion: 2.4-0ubuntu6
Architecture: i386
Date: Sat Aug 11 13:01:11 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120811.1)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0xb70f9504 <g_file_make_directory_with_parents+260>: cmpl $0x1,0x4(%eax)
 PC (0xb70f9504) ok
 source "$0x1" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_file_make_directory_with_parents () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 gcm_profile_store_search () from /usr/lib/gnome-settings-daemon-3.0/libcolor.so
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libcolor.so
 g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: gnome-settings-daemon crashed with SIGSEGV in g_file_make_directory_with_parents()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
critin (critin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1034715, 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.

visibility: private → public
tags: removed: need-i386-retrace
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.