gsd-color[1032]: failed to set screen _ICC_PROFILE

Bug #1747891 reported by dino99
158
This bug affects 34 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Confirmed
Medium
gnome-settings-daemon (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Get that error logged:

gsd-color[1032]: failed to set screen _ICC_PROFILE: Failed to open file “/home/oem/.local/share/icc/edid-3ed66b5b66c8e176b2d44c8563cdad28.icc”: Permission denied

This is related to (colormgr get-profiles output):

Filename: /var/lib/gdm3/.local/share/icc/edid-3ed66b5b66c8e176b2d44c8563cdad28.icc
Profile ID: icc-b11214f828f359ffc2d54bd918e8de7b
Metadata: CMF_version=3.26.2
Metadata: EDID_serial=SN-000000001
Metadata: CMF_binary=gnome-settings-daemon
Metadata: EDID_md5=3ed66b5b66c8e176b2d44c8563cdad28
Metadata: CMF_product=gnome-settings-daemon
Metadata: EDID_mnft=MTC
Metadata: FILE_checksum=b11214f828f359ffc2d54bd918e8de7b
Metadata: EDID_model=MON-SIS289
Metadata: DATA_source=edid
Metadata: MAPPING_device_id=xrandr-Mars-Tech Corporation-MON-SIS289-SN-000000001
Metadata: EDID_manufacturer=Mars-Tech Corporation

Actual rights (set by the default install):

oem@ubuntu:~$ ls -l /home/oem/.local/share/icc/
-rw-rw-r-- 1 oem oem 1552 Dec 1 20:22 edid-3ed66b5b66c8e176b2d44c8563cdad28.icc

I've tried to follow that howto; but it should be set out of the box:
https://askubuntu.com/questions/199661/how-do-you-set-system-display-color-profiles-in-xubuntu-and-lubuntu

note: if that apply to an other package than gsd, please do change/add

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.26.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Feb 7 12:11:12 2018
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Changed in gnome-settings-daemon:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Cedric Bhihe (cedric-bhihe) wrote :

This bug also appears in Arch linux 4.18.10 running gdm 3.30.1 on X11 (xorg server 1.20.1).

Revision history for this message
bblodfon (bblodfon) wrote :

[Maybe also related](https://askubuntu.com/questions/1114350/ubuntu-18-04-1-freezes-when-connecting-to-a-second-screen)? I have added some syslog errors if that helps anyone solve the issue.

Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
Revision history for this message
Klaus Bielke (k-bielke) wrote :

I get this error from the sessiom of GDM3:

$ journalctl -b -u user-120.slice -p 0..6 | grep -e gdm -e icc
Aug 19 16:28:21 lieselotte systemd[1]: Created slice User Slice of gdm.
Aug 19 16:28:21 lieselotte systemd[911]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0)
Aug 19 16:28:41 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung
Aug 19 16:28:42 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung

gsd-color from user id 120 trys reading a private file of user id 1000. That seems wrong by design. It's a security fault.

Revision history for this message
Jerry Quinn (jlquinn) wrote :

The last comment of this bug report appears to describe what's happening:

https://bugzilla.redhat.com/show_bug.cgi?id=1641541

There are 2 Xorg processes running for some reason. One I'm logged into, and the other is on another VT. The one I'm logged into has my user id. The other one has uid gdm.

The Xorg with uid gdm has a child gsd-color process with the pid that matches the errant log message.

There is also a gsd-color process with my uid that is a child of systemd --user. I assume this happens when I logged in.

So this seems to be a bad byproduct of there being 2 Xorgs and gdms running. Why does this happen anyway?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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