Bug 371872 - No single click in Dolphin or System settings
Summary: No single click in Dolphin or System settings
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: master
Platform: Ubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-30 17:15 UTC by jacques.bonder
Modified: 2018-09-27 05:35 UTC (History)
3 users (show)

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


Attachments
kdeglobals (5.68 KB, text/plain)
2016-10-31 07:59 UTC, jacques.bonder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jacques.bonder 2016-10-30 17:15:20 UTC
After setting the single click on : system settings>mouse , it doesn't work for System settings itself , Dolphin or the desktop .
  Ubuntu 16.04 
  KDE 5.23.0
  Dolphin 15.12.03
Comment 1 David Edmundson 2016-10-30 21:14:39 UTC
Please attach your ~/.config/kdeglobals and reopen this bug.
Comment 2 jacques.bonder 2016-10-31 07:59:13 UTC
Created attachment 101912 [details]
kdeglobals

  Dans kdeglobals , singleclick is true ....
Comment 3 Andrew Crouthamel 2018-09-26 22:26:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 jacques.bonder 2018-09-27 05:35:20 UTC
This bug had disappeared after several updates and some months in 2016.  Resolved