Hi all.

First: I'm on neon/focal/unstable (which I'm generally quite happy with - thanks for the work!).

Since about 2 days I lost access to basically everything seat related (sound, USB gadgets, removable storage). As far as I can tell, udev's builtin 'uaccess' is not setting ACLs. I have modified one of my udev rules (the one from Solaar [https://github.com/pwr-Solaar/Solaar], to be more precise) to use MODE/GROUP (in addition to TAG+="uaccess", TAG+="udev-acl") - with this I can access the device as expected (through plugdev group membership), ACLs are not set at all, however.

I'm very happy to dig deeper - any suggestions are welcome.

Cheers.

Hi!

You can use the `udevadm` tool to perform tests, monitor and/or trigger events. That should get you some exact error messages to handle.

Thanks (und Grüße)

I tried the whole udevadm dance. It does RUN 'uaccess' - just to be informed that it retains the ownership (which is root/0600 without MODE/GROUP setting as described above).

Y.

P.S.: I didn't try any of the other now "missing" sub-systems as long as I have the "Solaar" target (which is a Logitech unifying receiver) ...

For testing I switched temporarily to GDM3 - et voilà, everything is back.

So, it seems to be an issue with SDDM (I assume, it was the update on Aug 13th to sddm;0.19.0+p20.04+tunstable+git20210813.0153-0). I can't see anything obvious in the logs.

You could check the changes login scripts. Does the --login change lead to problems due to default tools triggered by .bashrc/.profile/.whatever? Can you try login with a fresh added user?

https://github.com/sddm/sddm/pull/1437 should address this

apachelogger wrote:https://github.com/sddm/sddm/pull/1437 should address this

Kudos!