Bug 717065 - gnome-settings-daemon crashes at start on Rawhide: mislabeled profiles in ~/.local/share/icc
Summary: gnome-settings-daemon crashes at start on Rawhide: mislabeled profiles in ~/....
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: colord
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-27 20:30 UTC by Adam Williamson
Modified: 2011-06-28 10:59 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 10:59:57 UTC
Type: ---


Attachments (Terms of Use)

Description Adam Williamson 2011-06-27 20:30:49 UTC
On current Rawhide, gnome-settings-daemon doesn't seem to be working right. If I log into GNOME fallback mode (Shell isn't working either), I see all default settings, and g-s-d isn't running per ps. If I try and run it manually, it seems to kick in for a second or two - the display blanks and comes back, and it seems to be appyling some of my settings - then it stops running and dumps back to console. Console messages:

[adamw@adam ~]$ /usr/libexec/gnome-settings-daemon
     
(gnome-settings-daemon:3137): color-plugin-WARNING **: failed to enumerate directory /home/adamw/.color/icc: No such file or directory
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
     
(gnome-settings-daemon:3137): color-plugin-WARNING **: Failed to CreateProfile: The connection is closed
     
(gnome-settings-daemon:3137): color-plugin-WARNING **: Failed to CreateProfile: The connection is closed

abrt doesn't see this as a crash.

Comment 1 Adam Williamson 2011-06-27 21:41:56 UTC
I've fixed up Shell, but still see this problem when logging in with Shell. Can't get g-s-d to run at all.

Comment 2 Adam Williamson 2011-06-27 21:49:46 UTC
This seems to be a SELinux / gnome color issue. With setenforce Permissive, it works. SELinux denials I see in /var/log/messages:

Jun 27 14:47:17 adam setroubleshoot: SELinux is preventing dbus-daemon from read access on the file /home/adamw/.local/share/icc/edid-a1dd0f8e73312854d25b60a3bb674e02.icc. For complete SELinux messages. run sealert -l b137df03-971f-49be-b757-2b4259bd6e7d
Jun 27 14:47:17 adam setroubleshoot: SELinux is preventing /usr/libexec/colord from read access on the file /home/adamw/.local/share/icc/edid-a1dd0f8e73312854d25b60a3bb674e02.icc. For complete SELinux messages. run sealert -l 54297855-1897-47d1-b18e-c79b4671fe62
Jun 27 14:47:17 adam setroubleshoot: SELinux is preventing /usr/libexec/colord from getattr access on the file /home/adamw/.local/share/icc/edid-a1dd0f8e73312854d25b60a3bb674e02.icc. For complete SELinux messages. run sealert -l fa9f32f8-f1ab-40d7-9bff-3bd554ba82e7
Jun 27 14:47:17 adam setroubleshoot: SELinux is preventing /usr/libexec/colord from read access on the file /home/adamw/.local/share/icc/edid-a1dd0f8e73312854d25b60a3bb674e02.icc. For complete SELinux messages. run sealert -l 54297855-1897-47d1-b18e-c79b4671fe62

I can't run sealert at present. Re-assigning to selinux-policy.

Comment 3 Adam Williamson 2011-06-27 21:52:15 UTC
ok, got sealert to work and it looks like these files got mislabeled somehow, restorecon fixed it. But not sure how they got mislabeled, I did not adjust them manually at all. colord problem?

Comment 4 Daniel Walsh 2011-06-28 10:59:57 UTC
No I think this was a policy update problem, where we changed the label on this directory but did not relabel it correctly for some reason.


Note You need to log in before you can comment on or make changes to this bug.