Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1555914 - After upgrade to plasma-systemsettings-5.12.2-1, mouse is no longer present in KDE Input Devices panel
Summary: After upgrade to plasma-systemsettings-5.12.2-1, mouse is no longer present i...
Keywords:
Status: CLOSED DUPLICATE of bug 1555403
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-systemsettings
Version: 27
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-14 20:01 UTC by Brian Daniels
Modified: 2018-03-15 04:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 04:20:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Brian Daniels 2018-03-14 20:01:33 UTC 
Description of problem:
After applying dnf updates including plasma-systemsettings-5.12.2-1, my KDE desktop no longer has mouse options under Input Devices.  Keyboard, Joystick, and Touchpad are the only items listed.  My existing mouse speed settings were lost as well.  Adding a new user and logging in as them did not correct the issue.

Version-Release number of selected component (if applicable):
5.12.2-1

How reproducible:
Always

Steps to Reproduce:
1. Upgrade Fedora to current packages and reboot.
2. Log in to KDE and go to System Settings.
3. Look at Input Devices.

Actual results:
No mouse section or options present.

Expected results:
Mouse control panel should be available.

Additional info:
Previous version installed was plasma-systemsettings-5.11.5-1.fc27.x86_64
Comment 1 Rex Dieter 2018-03-15 04:20:54 UTC 

*** This bug has been marked as a duplicate of bug 1555403 ***
Note You need to log in before you can comment on or make changes to this bug.