https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #20 from Nate Graham ---
(In reply to Domenico Panella from comment #17)
> I say that the keyboard layout defined in kcms are the settings.
> If i change the layout via applet/shortcut then it changes from a setting to
> a state because i
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #19 from Andrey ---
(In reply to Nate Graham from comment #16)
> In general, state is safe to discard with minimal user annoyance, whereas
> settings should always be persistent no matter what.
I would say if the data to be saved is
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #18 from Domenico Panella ---
The idea should be that everything we do in kcms is a setting, everything we do
via applet/shortcut
should be a change of the setting state, as such keeping it or not if we set to
save the session or not.
--
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #17 from Domenico Panella ---
I say that the keyboard layout defined in kcms are the settings.
If i change the layout via applet/shortcut then it changes from a setting to a
state because i am not doing that in kcms
it's only a
https://bugs.kde.org/show_bug.cgi?id=431481
Nate Graham changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #15 from Andrey ---
(In reply to Nate Graham from comment #14)
> Medin's point that we don't reset sound and brightness for empty sessions
> actually points at those needing to be reset too, since those are state and
> not settings.
That is
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #14 from Nate Graham ---
Medin's point that we don't reset sound and brightness for empty sessions
actually points at those needing to be reset too, since those are state and not
settings.
Should we mark this as RESOLVED INTENTIONAL and
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #13 from Andrey ---
Medin, this is because the current layout was considered state and not a
setting.
The setting saves in the moment you change it (usually backed by KConfig object
internally).
The state saves when session saves, so
https://bugs.kde.org/show_bug.cgi?id=431481
Andrey changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
|
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #12 from medin ---
(In reply to Domenico Panella from comment #11)
> On X11 this MR should fix this behaviour.
> https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/416
>
> Now, it loads the top most layout defined in kcms in
https://bugs.kde.org/show_bug.cgi?id=431481
Domenico Panella changed:
What|Removed |Added
CC||pando...@gmail.com
--- Comment #11 from
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #10 from Andrey ---
(In reply to medin from comment #8)
> when I run coredumpctl I found many crashes of
> kglobalaccel5, kalarm and akonadi* services.
Could you file an separate issue for that maybe?
So we could sort it out if it's known
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #9 from Nate Graham ---
Okay, so you're using that setting to work around bugs. We should just fix
those bugs instead. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431481
--- Comment #8 from medin ---
(In reply to Nate Graham from comment #7)
> I don't know what users expect from it.
As someone who logout and reboots many times my laptop, I'm often (not always)
getting serious slowness from "Restore last session"
https://bugs.kde.org/show_bug.cgi?id=431481
Nate Graham changed:
What|Removed |Added
Keywords||wayland
Severity|normal
15 matches
Mail list logo
