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

StacktraceTop:
 xft_settings_set_xsettings (settings=<optimized out>, manager=<optimized out>) at gsd-xsettings-manager.c:470
 update_xft_settings (manager=0x97c8000) at gsd-xsettings-manager.c:564
 xft_callback (manager=0x97c8000, settings=<optimized out>, key=<optimized out>) at gsd-xsettings-manager.c:577
 g_cclosure_marshal_VOID__STRINGv (closure=0x97fd7d0, return_value=0x0, instance=0x97ef4c8, args=0xbfc6eb3c "\277Pm\t\001", marshal_data=0x0, n_params=1, param_types=0x970d3c8) at /build/buildd/glib2.0-2.31.20/./gobject/gmarshal.c:1004
 _g_closure_invoke_va (closure=0x97fd7d0, return_value=0x0, instance=0x97ef4c8, args=0xbfc6eb3c "\277Pm\t\001", n_params=1, param_types=0x970d3c8) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:840

logged in using xrdp and remmina remote desktop, 2when the crash occured

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

Package: gnome-settings-daemon 3.4.1-0ubuntu1
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon

Error happened on a fresh installed 12.04-release w/o any related user activity (only firefox where running).

Stack trace indicates this seems to be related to XFT settings changing. Changing these from dconf-editor [1] doesn't trigger the problem for me.

[1] Open dconf-editor, change settings in /org/gnome/settings-daemon/plugins/xsettings

This bug was fixed in the package gnome-settings-daemon - 3.4.2-0ubuntu2

---------------
gnome-settings-daemon (3.4.2-0ubuntu2) quantal; urgency=low

  * debian/patches/xsettings_signal_handling.patch:
    - upstream bugzilla patch, fix segfaults in the xsettings code which
      seem to happen at logout
      (lp: #946295, #948347, #963704)
 -- Sebastien Bacher <email address hidden> Wed, 23 May 2012 21:50:41 +0200

Hello! This bug is attached to an upload in the queue for precise-proposed. However, it does not contain the requisite fields for the SRU team to process the upload. Please add them per the process outlined here. To be more succinct, make sure the bug description lists these fields: "Impact, Dev Fix, Stable Fix, Regression Potential, Test case".

https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

The upload will likely not be looked at by the SRU team until these fields are present.

Thank you!

see bug #946295 for the SRU summary

Hello Scott, or anyone else affected,

Accepted gnome-settings-daemon into precise-proposed. The package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Tried gnome-settings-daemon (3.4.2-0ubuntu2) from precise-proposed on a HP cedar-trail model, the error message remains.

Setting back to In-Progress verification-failed based on comment #18

it's unclear that "the error message remains." is the same issue, could you give details on what error message you get exactly and where?

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/948347

@Sebastien

The error message is attached.

does anyone has a regression with the fix? it seems to work for some people and failing the SRU on it if there is no regression seems unnecessary

After installing the package in -proposed, the same error box still pop up in first boot due to gnome-settings-daemon
Steps to reproduce:
1. Boot from USB installer and install system on a Cedar Trail machine
2. Complete OOBE and boot into system
3. Wait for 5-10 minutes and observe

./kern.log:Jun 5 10:18:41 ubuntu-desktop kernel: [ 362.707513] gnome-settings-[24692]: segfault at 6 ip b47b76b3 sp bfd25760 error 4 in libxsettings.so[b47b2000+9000]

is the timestamp the one from after installation or is that coming from the liveCD system? did you restart g-s-d after installing it?

@ ebastien Bacher, the timestamp was after OOBE.
No manually stop/restart was done.

Sorry, the previous message was for Sebastien Bacher (S of the first name was missing).

ok, somebody having the issue will need to debug it I guess then...

We made some further checks. When OOBE ends and lightdm starts, the gnome-setting-daemon is invoked via lightdm, and soon crashed.

settings to verification-done to unblock the SRU, the update has no regression and fixes some other bugs, we will reopen the bug once the SRU moves to -updates

@Tammy -- How much memory is this machine configured with?

This error happened Ubuntu 12.10 Alpha 3 64 bit, when logged in Ubuntu 2D.

12.10 Alpha 3 Ubuntu 2D i386 32 bit new install Unity 2D, referring to post #31, 2 GB.

.iso as of August 4
Linux Compaq 3.5.0-7-generic #7-Ubuntu SMP Tue Jul 31 07:23:07 UTC 2012 i686 i686 i686 GNU/Linux

Does "won't fix" mean 12.10 will release with this bug?

Jerry

Hallo
Reproducible in real hardware (nvidia) with ubuntu 20120915 desktop testing oem install.
See bug 1051415
This pc is also affected by:
Sep 15 22:59:15 oem-K8NF4G-SATA2 kernel: [ 1449.572931] [drm] nouveau 0000:00:05.0: fail ttm_validate
Sep 15 22:59:15 oem-K8NF4G-SATA2 kernel: [ 1449.572942] [drm] nouveau 0000:00:05.0: validate vram_list
Sep 15 22:59:15 oem-K8NF4G-SATA2 kernel: [ 1449.580132] [drm] nouveau 0000:00:05.0: validate: -12

downgrade to medium: not a quantal release blocker (already shipped quantal with it. Ensuring that someone still continue to work on it though

Reopened oem-priority task, this affects some of our 32-bit 12.04 OEM builds.

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".