[xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()

Bug #968198 reported by Erick Brunzell
134
This bug affects 28 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Got this crash report on initial boot after upgrade from Oneiric to Precise.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.3.92-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Thu Mar 29 06:46:06 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 SHELL=/bin/false
 LANG=en_US.UTF-8
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
UpgradeStatus: Upgraded to precise on 2012-03-29 (0 days ago)
UserGroups:

Revision history for this message
Erick Brunzell (lbsolost) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceTop.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgtk-3-common version 3.3.20-0ubuntu1 required, but 3.4.0-0ubuntu1 is available
libdconf0 version 0.11.7-0ubuntu1 required, but 0.12.0-0ubuntu1 is available
outdated debug symbol package for libdconf0: package version 0.12.0-0ubuntu1 dbgsym version 0.11.7-0ubuntu1
libpango1.0-0 version 1.29.5-0ubuntu1 required, but 1.30.0-0ubuntu1 is available
libnotify4 version 0.7.4-1 required, but 0.7.5-1 is available
outdated debug symbol package for libnotify4: package version 0.7.5-1 dbgsym version 0.7.4-1
gnome-settings-daemon version 3.3.92-0ubuntu2 required, but 3.4.0-0ubuntu1 is available
outdated debug symbol package for gnome-settings-daemon: package version 3.4.0-0ubuntu1 dbgsym version 3.3.92-0ubuntu2
nautilus-data version 1:3.3.92-0ubuntu2 required, but 1:3.4.0-0ubuntu1 is available
libglib2.0-0 version 2.31.22-0ubuntu1 required, but 2.32.0-0ubuntu1 is available
dconf-service version 0.11.7-0ubuntu1 required, but 0.12.0-0ubuntu1 is available
outdated debug symbol package for dconf-service: package version 0.12.0-0ubuntu1 dbgsym version 0.11.7-0ubuntu1
gnome-desktop3-data version 3.3.92-0ubuntu1 required, but 3.4.0-0ubuntu1 is available
libgnome-desktop-3-2 version 3.3.92-0ubuntu1 required, but 3.4.0-0ubuntu1 is available
outdated debug symbol package for libgnome-desktop-3-2: package version 3.4.0-0ubuntu1 dbgsym version 3.3.92-0ubuntu1
libatk1.0-0 version 2.3.95-0ubuntu1 required, but 2.4.0-0ubuntu1 is available
outdated debug symbol package for libatk1.0-0: package version 2.4.0-0ubuntu1 dbgsym version 2.3.95-0ubuntu1
libgtk-3-0 version 3.3.20-0ubuntu1 required, but 3.4.0-0ubuntu1 is available
gsettings-desktop-schemas version 3.3.92-0ubuntu1 required, but 3.4.0-0ubuntu1 is available
dconf-gsettings-backend version 0.11.7-0ubuntu1 required, but 0.12.0-0ubuntu1 is available
outdated debug symbol package for dconf-gsettings-backend: package version 0.12.0-0ubuntu1 dbgsym version 0.11.7-0ubuntu1
libatk1.0-data version 2.3.95-0ubuntu1 required, but 2.4.0-0ubuntu1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/968198

tags: added: iso-testing
Revision history for this message
Erick Brunzell (lbsolost) wrote :

I'm performing a Lucid > Precise upgrade on that machine ATM but later today I'll reboot that OS and check the package status. I did reboot that OS twice after apport reported this error and all seemed well, so it appears to have effected only the initial boot after upgrade.

Also, possibly unrelated, but I had to edit fstab because it had an invalid swap UUID. Just mentioning that in case someone else encounters the same error.

Revision history for this message
Attila Hammer (hammera) wrote :

Happened my system this error a clean installation.
I enabled the proposed repository and installed all upgrades to awailable latest stable GNOME release packages.
Prewious I newer see this issue.

Attila

Revision history for this message
Kai Timmer (eh79o) wrote :

Happens to me on every boot. I have the newest available packages installed.

Revision history for this message
jerrylamos (jerrylamos) wrote :

New install of 20120411 build 3.2.0-23 was using "Home Folder" launcher. Acer
Aspire 1 netbook has been running Alpha 1 & 2, Beta 1 & 2 O.K. given usual development bugs.
Unity-2D running as designed, except for this bug so far. I don't care for Unity-3D fuzzy foggy out of focus huge hieroglyphics Compiz overhead theme.

Jerry

Revision history for this message
sl45sms (sl45sms) wrote :

happens on clean install to vaio vgn-p21z with all upgrades installed.

Revision history for this message
Richard Foulkes (rbsfou) wrote :

Asus 1201n, fresh install. Unity 2d, as hadn't got round to installing nvidia-current yet.

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.