tl;dr When I turn on user_allow_other in /etc/fuse.conf in Fedora Linux 43, the suspend feature stops working.

Background

I wanted to create a Samba share below a gocryptfs mount point. Since I ran into an access permissions problem when I tried that and that gocryptfs uses FUSE, I figured that I had to enable user_allow_other in FUSE and add the -allow_other option when starting gocryptfs.

In the end, this idea did not solve the access problem. But that's also when I ran into the suspend problem.

Discussion

The way the suspend feature broke after enabling user_allow_other is itself weird. It only freezes the system the second time I try to suspend it. The first suspend and wake up work fine. The freeze only happens on the second suspend.

I have no idea how a FUSE setting can affect power management. When transitioning the system to suspend state, does systemd somehow touch a userspace filesystem? This issue will be difficult and annoying to debug because I have to reboot the laptop every time it freezes on suspend.

About that Android Studio Narwhal to Otter upgrade...

I guess this will teach me not to upgrade software at night before a weekend.

An upgrade to Android Studio Otter popped up in the notifications yesterday. It actually has a feature I wanted, support for Backup & Sync of IDE settings, so I clicked on the update. Android Studio downloaded it and restarted.

Then I saw that lots of Jetpack Compose state variables were flagged in the IDE with the “Assigned value is never read” warning. On the surface, these variables do look like they are assigned but never again used within the block. However, they are actually delegates and we are using the side effect of assigning to these variables. In Jetpack Compose, a typical effect is to recompose part of the UI when a state variable changes.

These spurious warnings seem to be related to this reported issue. We'll have to wait for the release of Kotlin 2.3. The fix (not producing that warning when the assignment occurs in a non-inline lambda) is already available in the 2.3 beta but the Kotlin team won't be backporting it to Kotlin 2.2.

In the meantime, I'll just turn off that particular warning in Android Studio settings.