Bug ID | 1177621 |
---|---|
Summary | Redshift's apparmor rule blocks reading a symlinked configuration file |
Classification | openSUSE |
Product | openSUSE Tumbleweed |
Version | Current |
Hardware | Other |
OS | Other |
Status | NEW |
Severity | Normal |
Priority | P5 - None |
Component | X11 Applications |
Assignee | screening-team-bugs@suse.de |
Reporter | dcermak@suse.com |
QA Contact | qa-bugs@suse.de |
Found By | --- |
Blocker | --- |
I have my redshift configuration symlinked to /home/dan/.config/redshift/redshift.conf from /home/dan/dotfiles/xorg/.config/redshift/redshift.conf. However, the apparmor rule that is shipped with redshift, prevents it from actually reading the configuration file as revealed by strace: openat(AT_FDCWD, "/home/dan/.config/redshift/redshift.conf", O_RDONLY) = -1 EACCES (Permission denied) Could the apparmor rule be extended to allow to follow symlinks? Also, I am wondering if this is a regression, since I was using redshift for a few years without issues and this broke just recently (after a reinstall so not sure what the cause was here)