Bug 479193 - With Qt 6.7, user is prompted to apply changes without changing any settings
Summary: With Qt 6.7, user is prompted to apply changes without changing any settings
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_nightcolor (other bugs)
Version First Reported In: 5.91.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2023-12-30 18:20 UTC by Unknown
Modified: 2024-05-19 21:43 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.1
Sentry Crash Report:


Attachments
Screenshot of settings prompt (184.18 KB, image/png)
2023-12-30 18:20 UTC, Unknown
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2023-12-30 18:20:03 UTC
Created attachment 164557 [details]
Screenshot of settings prompt

SUMMARY
If a user visits the Night Light KCM in System Settings, does not make any changes to the settings and then navigates to away to another KCM they are incorrectly shown a prompt that says: "The settings of the current module have changed. Do you want to apply the changes or discard them?".

STEPS TO REPRODUCE
1. Launch System Settings
2. Navigate to Colors and Themes
3. Navigate to Night Light
4. Navigate to an adjacent KCM such as Colors or Application Style
5. System Settings displays a prompt that states that settings have changed and need to be applied or discarded


OBSERVED RESULT
System Settings displays a prompt that states that settings have changed and need to be applied or discarded

EXPECTED RESULT
System Settings does not display a prompt when no settings have been modified

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.6.8/Plasma 6
(available in About System)
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0

ADDITIONAL INFORMATION
Comment 1 fanzhuyifan 2023-12-31 04:38:52 UTC
Can reproduce on arch linux, beta 2.
Comment 2 Nate Graham 2024-01-11 19:54:15 UTC
Should be fixed in RC1. I can't reproduce this anymore and I recall something to fix it.
Comment 3 fanzhuyifan 2024-01-11 19:56:31 UTC
(In reply to Nate Graham from comment #2)
> Should be fixed in RC1. I can't reproduce this anymore and I recall
> something to fix it.

Can still reproduce on a source build from last night on arch linux.
Comment 4 fanzhuyifan 2024-01-11 19:59:32 UTC
Cannot reproduce on neon unstable though, so I am suspecting a Qt 6.7 issue.
Comment 5 Nate Graham 2024-01-11 20:29:54 UTC
Seems possible.
Comment 6 Unknown 2024-01-22 01:57:36 UTC
(In reply to fanzhuyifan from comment #3)
> (In reply to Nate Graham from comment #2)
> > Should be fixed in RC1. I can't reproduce this anymore and I recall
> > something to fix it.
> 
> Can still reproduce on a source build from last night on arch linux.

Same here.  Plasma RC1, Qt 6.7.0 (Arch Linux of course)
Comment 7 Arek Guzinski 2024-03-05 21:29:06 UTC
Happening to me on current neon (plasma/kf 6.0.0, qt 6.6.2, wayland)
Comment 8 Nate Graham 2024-05-19 21:43:57 UTC
Fixed now, at least for Plasma 6.1, maybe even earlier.