Issue with auto-rotate not working on Fedora 41

Ask Fedora
, ,
1

Hello, I would like to solve this issue.

Product Name: HP Envy x360 2-in-1 Laptop 14-fa0xxx
Product Number: 8C69

Current Status:
Active: inactive (dead) since Fri 2024-11-01 10:00:14 JST; 3min 57s ago

Software Version: iio-sensor-proxy-3.5-4.fc41.x86_64

When running sudo /usr/libexec/iio-sensor-proxy --verbose, the rotation works without issues.

I’m looking for a solution to make auto-rotate work consistently.

4 Likes
2

amdgpu を追加しました

3

Hello,

I can confirm the same issue and behaviour on a Dell Latitude 5289 after updating to Fedora 41.
Regards,

4

Updates? Having the same issue on a Samsung Galaxy Book3 360

unless I manually start it, it won’t work

5

Same here, Lenovo ThinkPad x390 yoga.

6

Same here, hp elitebook x360 1030, silverblue 41. 5289 after updating to Fedora 41.

Nov 03 23:41:32 uss-custodian-of-family-values systemd[1]: Starting iio-sensor-proxy.service - IIO Sensor Proxy service...
Nov 03 23:41:32 uss-custodian-of-family-values systemd[1]: Started iio-sensor-proxy.service - IIO Sensor Proxy service.
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.270: Failed to write current_trigger file Permission denied
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.270: Could not open for write '/sys/devices/pci0000:00/0000:00:13.0/{>
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.278: Failed to write current_trigger file Permission denied
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.279: Could not open for write '/sys/devices/pci0000:00/0000:00:13.0/{>
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.290: Failed to write current_trigger file Permission denied
Nov 03 23:41:32 uss-custodian-of-family-values iio-sensor-proxy[6893]: ** (iio-sensor-proxy:6893): WARNING **: 23:41:32.290: Could not open for write '/sys/devices/pci0000:00/0000:00:13.0/{>
Nov 03 23:41:32 uss-custodian-of-family-values systemd[1]: iio-sensor-proxy.service: Deactivated successfully.

I checked the system logs and it seems that it’s getting flagged by SELinux:

Nov 04 00:12:59 uss-custodian-of-family-values audit[13342]: AVC avc:  denied  { write } for  pid=13342 comm="iio-sensor-prox" name="enable" dev="sysfs" ino=47719 scontext=system_u:system_r>
Nov 04 00:12:59 uss-custodian-of-family-values audit[13342]: AVC avc:  denied  { create } for  pid=13342 comm="iio-sensor-prox" scontext=system_u:system_r:iiosensorproxy_t:s0 tcontext=syste>
Nov 04 00:12:59 uss-custodian-of-family-values audit[13342]: AVC avc:  denied  { write } for  pid=13342 comm="iio-sensor-prox" name="current_trigger" dev="sysfs" ino=47755 scontext=system_u>
Nov 04 00:12:59 uss-custodian-of-family-values iio-sensor-proxy[13342]: ** (iio-sensor-proxy:13342): WARNING **: 00:12:59.675: Failed to write current_trigger file Permission denied
Nov 04 00:12:59 uss-custodian-of-family-values iio-sensor-proxy[13342]: ** (iio-sensor-proxy:13342): WARNING **: 00:12:59.675: Could not open for write '/sys/devices/pci0000:00/0000:00:13.0>

I think I can write a module that will fix it but it’ll have to wait until tomorrow when I have the time to experiment with it

7

+1 for me too, dell latitude 5290 2-in-1. fedora 40 worked just fine

8

+1 for me also, using F41 on ThinkPad X1 Yoga 2nd Gen

Update: Solved the issue through switching SELinux mode from enforcing to permissive by following this guide.

More Update: Made Bugzilla reports, hopefully it will get fixed immediately.

1 Like
9

Thank you, that fixed it on my Surface Go 1, running F41 but with the linux-surface kernel!

10

The workaround at Red Hat Bugzilla – Bug 2319766 available through the link you put also fixed it for me, however I had to run, reboot and run and reboot again, because on the first reboot even though iio-sensor-proxy was active when running monitor-sensor I got orientation: undefined, on the second reboot it worked.

The workaround:
sudo grep iio-sensor /var/log/audit/audit.log | grep denied | audit2allow -M iio_sensor
sudo semodule -i iio_sensor.pp

1 Like