Bug 510999

Summary:	night light fails to activate since the upgrade to first 6.5 beta
Product:	[Applications] systemsettings	Reporter:	Vadym Krevs <vkrevs>
Component:	kcm_nightcolor	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	REOPENED ---
Severity:	normal	CC:	kwin-bugs-null, vkrevs
Priority:	NOR
Version First Reported In:	6.5.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	NIght light settings

Description Vadym Krevs 2025-10-24 08:08:05 UTC

SUMMARY

I've had night light configured to activate at 18:00 as per defaults for a long time. Ever since the upgrade to the first Plasma 6.5 beta from openSUSE OBS, it is faling to activate automatically. I have to go into "Status and Notifications", "Brightness and Colour" and manually suspend/unsuspend the night light switch in order to activate Night Light.  Still not fixed in final Plasma 6.5 rpms from openSUSE build service.

This is a desktop PC with a single monitor connected via DisplayPort. Device location is London, United Kindom. Timezone is "London".

STEPS TO REPRODUCE
1.  Set up night light settings in System Settings -> Display and Monitor -> Night Light using defaults as in the attached screenshot (activate night light at 18:00 based on device location). 
2.  
3. 

OBSERVED RESULT
At 19:00 the monitor still hasn't transitioned to night light.

EXPECTED RESULT
At 19:00 the monitor has transitioned to night light.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Graphics Platform: X11

ADDITIONAL INFORMATION

Comment 1 Vadym Krevs 2025-10-24 08:09:27 UTC

Created attachment 186077 [details]
NIght light settings

Comment 2 Sylens 2025-10-24 17:07:01 UTC

509885

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

Comment 3 Vlad Zahorodnii 2025-11-04 07:50:40 UTC

Is there anything in kwin_x11 logs? (journalctl --boot --user-unit plasma-kwin_x11)

Also does the brightness applet show a proper color temperature when night light is expected to be active?

Comment 4 Vlad Zahorodnii 2025-11-04 08:07:18 UTC

Just in case, I can't reproduce this issue on X11.

Comment 5 Vadym Krevs 2025-11-04 18:55:49 UTC

(In reply to Vlad Zahorodnii from comment #3)
> Is there anything in kwin_x11 logs? (journalctl --boot --user-unit
> plasma-kwin_x11)
> 
> Also does the brightness applet show a proper color temperature when night
> light is expected to be active?

Nothing that stands out to me.

$ journalctl --boot --user-unit plasma-kwin_x11 
Hint: You are currently not seeing messages from the system.
      Users in the 'systemd-journal' group can see all messages. Pass -q to
      turn off this notice.
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 11:58:56 hulk kwin_x11[3197]: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 02 12:03:13 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 1338, resource id: 13643922, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 12:03:13 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 1339, resource id: 29360145, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 02 12:04:39 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 60614, resource id: 13650166, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 12:04:39 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 60615, resource id: 29360153, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 02 14:09:52 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 17062, resource id: 13703756, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 14:09:52 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 17063, resource id: 29360219, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 02 14:09:57 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 20634, resource id: 13704008, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 14:09:57 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 20635, resource id: 29360221, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 02 16:57:46 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 25214, resource id: 13741570, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 16:57:46 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 25215, resource id: 29360276, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 02 20:35:51 hulk kwin_x11[3197]: XCB error: 152 (BadDamage), sequence: 40008, resource id: 13786986, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 02 20:35:51 hulk kwin_x11[3197]: XCB error: 3 (BadWindow), sequence: 40009, resource id: 29360353, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 03 08:55:00 hulk kwin_x11[3197]: Could not delete framebuffer because no context is current
Nov 03 08:55:00 hulk systemd[2944]: plasma-kwin_x11.service: Main process exited, code=exited, status=15/n/a
Nov 03 08:55:00 hulk systemd[2944]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 17:39:39 hulk kwin_x11[3839]: "\"fsrestore6\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 03 19:23:04 hulk kwin_x11[3839]: XCB error: 152 (BadDamage), sequence: 5478, resource id: 13660821, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 03 19:23:04 hulk kwin_x11[3839]: XCB error: 3 (BadWindow), sequence: 5479, resource id: 29360164, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 03 19:23:15 hulk kwin_x11[3839]: XCB error: 152 (BadDamage), sequence: 9085, resource id: 13661085, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 03 19:23:15 hulk kwin_x11[3839]: XCB error: 3 (BadWindow), sequence: 9086, resource id: 29360168, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 03 19:23:44 hulk kwin_x11[3839]: XCB error: 152 (BadDamage), sequence: 17943, resource id: 13661586, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 03 19:23:44 hulk kwin_x11[3839]: XCB error: 3 (BadWindow), sequence: 17944, resource id: 29360176, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 03 20:13:44 hulk kwin_x11[3839]: QDBusConnection: couldn't handle call to Teardown, no slot matched
Nov 03 20:13:44 hulk kwin_x11[3839]: QDBusConnection: couldn't handle call to Teardown, no slot matched
Nov 03 20:13:44 hulk kwin_x11[3839]: Could not find slot Krunner1Adaptor::Teardown
Nov 04 07:21:09 hulk kwin_x11[3839]: XCB error: 152 (BadDamage), sequence: 11729, resource id: 13697043, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Nov 04 07:21:09 hulk kwin_x11[3839]: XCB error: 3 (BadWindow), sequence: 11730, resource id: 29361439, major code: 129 (SHAPE), minor code: 6 (Input)
Nov 04 09:18:25 hulk kwin_x11[3839]: The X11 connection broke: I/O error (code 1)
Nov 04 09:18:25 hulk kwin_x11[3839]: XIO:  fatal IO error 4 (Interrupted system call) on X server ":0"
Nov 04 09:18:25 hulk kwin_x11[3839]:       after 57 requests (57 known processed) with 0 events remaining.
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 12 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 11 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 10 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 9 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 8 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 7 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 2 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 1 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk kwin_x11[3839]: QThreadStorage: entry 0 destroyed before end of thread 0x561f15f71d30
Nov 04 09:18:25 hulk systemd[3591]: plasma-kwin_x11.service: Main process exited, code=exited, status=1/FAILURE
Nov 04 09:18:25 hulk systemd[3591]: plasma-kwin_x11.service: Failed with result 'exit-code'.
Nov 04 17:25:00 hulk kwin_x11[6438]: "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 04 17:25:00 hulk kwin_x11[6438]: "\"fsrestore2\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 04 17:25:00 hulk kwin_x11[6438]: "\"fsrestore3\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 04 17:25:00 hulk kwin_x11[6438]: "\"fsrestore4\" - conversion of \"0,0,0,0\" to QRect failed"
Nov 04 17:25:00 hulk kwin_x11[6438]: "\"fsrestore5\" - conversion of \"0,0,0,0\" to QRect failed"

Comment 6 Vlad Zahorodnii 2025-11-05 07:58:54 UTC

> Also does the brightness applet show a proper color temperature when night light is expected to be active?

.

Comment 7 Vadym Krevs 2025-11-05 18:26:46 UTC

(In reply to Vlad Zahorodnii from comment #6)
> > Also does the brightness applet show a proper color temperature when night light is expected to be active?
> 
> .

Yes. Also, I got some updates from opensuse build service earlier today, and the issue appears to be finally fixed.

Comment 8 Vadym Krevs 2025-12-04 23:08:52 UTC

Reopening - finally found a reliable way to reproduce the issue I have.

Ensure your PC has 2 users.

* one user whose night light is configured to activate at 18:00 as per defaults (dame as in the original summary of this issue) aka "home" user
* another user whose night light is not configured to activate at all aka "work" user.

Log off from the "home" user account and log in into "work" user account before night light activation time, say 9:00 :-) Work using the "work" account a bit late, then log off and  log in as the "home" user after the night light transition is supposed to take place, say 19:00.

After logging in as the "home" user at 19:00 (which is half an hour after the transition to night light was supposed to complete) , note that night light activation did not take place on login and one has to use the Birghtness and Color applet to suspend/unsuspend night light in order to force the transition.

Comment 9 Vadym Krevs 2025-12-04 23:14:03 UTC

Same happens if I do an "init 3; init 5" after night light has activated - automatically or manually - and log in as "home" user. The night light does not activate automatically.