By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2685 - Khotkeys KCM module doesn't open using "settings:/" service
Summary: Khotkeys KCM module doesn't open using "settings:/" service
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Michele Calgaro
URL:
Depends on:
Blocks: R14.0.4
  Show dependency treegraph
 
Reported: 2016-08-29 11:56 CDT by Q4OS Team
Modified: 2016-09-11 04:44 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Q4OS Team 2016-08-29 11:56:04 CDT
Exact steps to reproduce:
- Fresh TDE stable (14.0.3) installation on Debian Jessie
- Open konqueror file browser
- Write 'settings:/' to the location and go
- Click 'Regional & Accessibility' icon
- Click 'Input Actions' icon
- Khotkeys KCM module will not open
Comment 1 Michele Calgaro 2016-08-31 10:03:31 CDT
Problem confirmed. An "open with" dialog is open instead of TCM module.
Comment 2 Michele Calgaro 2016-09-09 10:18:22 CDT
problem found. I should have a patch ready by tomorrow or sunday for testing.
Comment 3 Michele Calgaro 2016-09-11 04:42:40 CDT
Fixed in commits 6960221 (tdebase - r14.1.x), ac46822 (tdebase - r14.0.x), 40d63eb (tde-packaging r14.1.x) and b2cc8a3 (tde-packaging r14.0.x).

For reference, the two files that have been deleted did not have any function. khotkeys is launched at the beginning by kcminit_startup, based on the entries of the file /opt/trinity/share/applications/tde/khotkeys.desktop
Comment 4 Michele Calgaro 2016-09-11 04:44:11 CDT
Q4OS Team, thanks for reporting the bug! Please keep up with testing :-)