Bug 436068 - Brightness widget fails to restore setting and sometimes doesn't load at all
Summary: Brightness widget fails to restore setting and sometimes doesn't load at all
Status: RESOLVED DUPLICATE of bug 433675
Alias: None
Product: plasmashell
Classification: Plasma
Component: Battery Monitor (show other bugs)
Version: 5.21.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: 1.0
Assignee: Kai Uwe Broulik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-23 00:08 UTC by medin
Modified: 2021-09-24 18:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description medin 2021-04-23 00:08:01 UTC 
If I disable "Allow automatic sleep and lock" in brightness widget then logout and login I found that "Allow automatic sleep and lock" is always enabled, this happens both with Restore session and Empty new session modes.
If you repeat the process of disabling "Allow automatic sleep and lock" then logout twice or more you will find that brightness widget stopped to be loaded in tray system.

Operating System: Manjaro Linux
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2
Kernel Version: 5.4.112-1-MANJARO
OS Type: 64-bit
Graphics Platform: X11
Comment 1 Nate Graham 2021-08-07 16:57:29 UTC 
Is this reproducible in Plasma 5.22? Or does the issue turn into Bug 433675?
Comment 2 medin 2021-08-07 18:41:20 UTC 
(In reply to Nate Graham from comment #1)
> Is this reproducible in Plasma 5.22? Or does the issue turn into Bug 433675?

The same problem is persistent, if you enable "Inhibit automatic sleep and screen locking" then logout and login you will find it disabled, and after one or more repeat of the previous scenario the brightness widget doesn't load at all, and if you reboot you will always get "Inhibit automatic sleep and screen locking" disabled.
Comment 3 Nate Graham 2021-08-09 17:19:10 UTC 
Hmm, Cannot reproduce those issues when I reboot with the setting checked.
Comment 4 Nate Graham 2021-09-24 18:46:29 UTC 
Ah, this is actually the same root cause as Bug 433675, which is fixed in Plasma 5.23 now.

*** This bug has been marked as a duplicate of bug 433675 ***