![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900 Bug ID: 1223900 Summary: sddm: issue with XAUTHORITY Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: gcomes.obs@gmail.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- In xfce I use redshift to adjust the monitor night color. If I use lightdm as displaymanager, redshift works normally. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Using method `randr'. Waiting for current location to become available... etc... But if I use sddm as displaymanager, redshift doesn't work. Typing the command: redshift -o gives the output: Trying location provider `geoclue2'... Using provider `geoclue2'. Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified `RANDR Query Version' returned error -1 Initialization of randr failed. Trying next method... Authorization required, but no authorization protocol specified Authorization required, but no authorization protocol specified X request failed: XOpenDisplay Initialization of vidmode failed. Trying next method... No more methods to try. The output of: strace redshift -o contains: access("/tmp/xauth_WYBTin", R_OK) = 0 openat(AT_FDCWD, "/tmp/xauth_WYBTin", O_RDONLY) = -1 EACCES (Permission denied) The failure of redshift is due to the fact that somehow it cannot access /tmp/xauth_WYBTin (the value of $XAUTHORITY) However such file is readable by the user running redshift and other xprograms work fine. Leap 15.5 (sddm 0.19) works fine as did the previous versions. The issue started with sddm 0.20 (https://build.opensuse.org/package/show/openSUSE:Factory/sddm?rev=64) and is currently present in Leap 15.6 and tumbleweed. I could not figure out what exactly in sddm 0.20 is causing the problem. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c2
Giacomo Comes
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c3
--- Comment #3 from Giacomo Comes
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c5
--- Comment #5 from Giacomo Comes
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c6
--- Comment #6 from Christian Boltz
There are at least two more entries that should go in
: owner /tmp/xauth_* r, (for sddm)
Agreed, even if "yet another path" is annoying. Submitted upstream as https://gitlab.com/apparmor/apparmor/-/merge_requests/1249 I'll also include the patch in the next submission to Tumbleweed.
owner @{run}/user/*/.mutter-Xwaylandauth.* (for gnome on Xwayland)
That rule already exists since 2020. Do you have any audit.log entries that show issues with this file? -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c7
--- Comment #7 from OBSbugzilla Bot
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c8
--- Comment #8 from Giacomo Comes
owner @{run}/user/*/.mutter-Xwaylandauth.* (for gnome on Xwayland)
That rule already exists since 2020. Do you have any audit.log entries that show issues with this file?
You are right, my mistake. The rule is already there. I was having trouble with redshift on gnome on wayland, but it turns out the issue was unrelated to XAUTHORITY and apparmor. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1223900
https://bugzilla.suse.com/show_bug.cgi?id=1223900#c9
Christian Boltz
participants (1)
-
bugzilla_noreply@suse.com