Bug 423315

Summary: weird settings interaction on desktop
Product: [Plasma] Bluedevil Reporter: Gerry Gavigan <gerrysw11>
Component: generalAssignee: David Rosca <nowrep>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate, plasma-bugs
Priority: NOR    
Version: 5.19.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: attachment-6714-0.html

Description Gerry Gavigan 2020-06-21 10:37:44 UTC
STEPS TO REPRODUCE
1. close laptop lid
2. wake

OBSERVED RESULT

bluetooth switched off
restoring bluetooth causes left-hand mouse settings reverted to default
left-handed radio button in system settings has to be toggled *off*
logging out and logging back in again causes the mouse to be right-handed (as expected by previous action)
 

EXPECTED RESULT

nothing changes

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.19
KDE Frameworks Version: 20.04
Qt Version: 5.15

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2020-06-22 16:41:40 UTC
Sounds a bit like Bug 414559.

Does this happen if you manually run `sudo udevadm trigger -s input` in a terminal window?
Comment 2 Gerry Gavigan 2020-06-22 23:05:39 UTC
Created attachment 129598 [details]
attachment-6714-0.html

yes

On Mon, 22 Jun 2020 at 17:41, Nate Graham <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=423315
>
> Nate Graham <nate@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |nate@kde.org
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> Sounds a bit like Bug 414559.
>
> Does this happen if you manually run `sudo udevadm trigger -s input` in a
> terminal window?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Gerry Gavigan 2020-06-22 23:06:46 UTC
yes
Comment 4 Gerry Gavigan 2020-06-22 23:42:31 UTC
though it also happens after an update (not always but often) via the KDE software updater in Tumbleweed
Comment 5 Nate Graham 2020-06-23 00:09:54 UTC
(In reply to Gerry Gavigan from comment #4)
> though it also happens after an update (not always but often) via the KDE
> software updater in Tumbleweed
Yep, I see the same thing. It's the same root cause, as far as I can tell.

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