caffeine isn't working

[githlacker]

the extension is simply not working, like when i enable it after couple of hours my laptop just gets suspend even though i have set the timer to infinite

[svenjacobs]

Same problem here. My computer suspends after 15 minutes even though Caffeine is enabled indefinitely.

• Caffeine 55
• Fedora 41
• Gnome 47

Maybe it has something to do with Fedora 41 changing the default power profile management daemon?

[bam80]

See also: #354

I see no mention of Gnome 47 in Readme, should it work there or some porting is needed?

[stuarthayhurst]

Does anyone not running Fedora have this issue? We had reports of it failing on Fedora a while ago (I think it was a beta version at the time?), and since then I've seen many reports like this, but all on Fedora.

Perhaps it's an upstream policy change of some sort, on how it interprets the different flags we can set in the inhibitor?

Can anyone that can reproduce this post the output of systemd-inhibit --list with Caffeine enabled and disabled?

[bam80]

@stuarthayhurst

Caffeine disabled:

$ systemd-inhibit --listst
WHO            UID  USER PID  COMM           WHAT                                                     WHY                                       MODE 
ModemManager   0    root 990  ModemManager   sleep                                                    ModemManager needs to reset devices       delay
NetworkManager 0    root 1031 NetworkManager sleep                                                    NetworkManager needs to turn off networks delay
UPower         0    root 933  upowerd        sleep                                                    Pause device polling                      delay
GNOME Shell    1001 bam  2050 gnome-shell    sleep                                                    GNOME needs to lock the screen            delay
bam            1001 bam  2179 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses                 block
bam            1001 bam  2179 gsd-media-keys sleep                                                    GNOME handling keypresses                 delay
bam            1001 bam  2183 gsd-power      sleep                                                    GNOME needs to lock the screen            delay

7 inhibitors listed.

Enabled:

$ systemd-inhibit --list
WHO            UID  USER PID  COMM            WHAT                                                     WHY                                       MODE 
ModemManager   0    root 990  ModemManager    sleep                                                    ModemManager needs to reset devices       delay
NetworkManager 0    root 1031 NetworkManager  sleep                                                    NetworkManager needs to turn off networks delay
UPower         0    root 933  upowerd         sleep                                                    Pause device polling                      delay
GNOME Shell    1001 bam  2050 gnome-shell     sleep                                                    GNOME needs to lock the screen            delay
bam            1001 bam  2179 gsd-media-keys  handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses                 block
bam            1001 bam  2179 gsd-media-keys  sleep                                                    GNOME handling keypresses                 delay
bam            1001 bam  2183 gsd-power       sleep                                                    GNOME needs to lock the screen            delay
bam            1001 bam  1977 gnome-session-b sleep                                                    user session inhibited                    block

8 inhibitors listed.

[bam80]

I wonder if it's #132 related.

[stuarthayhurst]

Thanks, that shows Caffeine is creating the inhibitor then. It looks like the system is ignoring it, which would be upstream unless we're creating it incorrectly.

Just to check, the bug you're reporting is that if you enable Caffeine, then leave the system as it is, it goes to sleep? If you're closing the lid or manually locking the screen, that's something else (more like #132).

[bam80]

I wonder if it's #132 related.

That was it, see the "solution".

Without it, the "user session inhibited" inhibitor gets removed on screen lock (not necessary manually), revealing the issue.