Bug 1382421 - xfce4-xkb-plugin should require xfce4-settings
Summary: xfce4-xkb-plugin should require xfce4-settings
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-xkb-plugin
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mukundan Ragavan
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-06 15:46 UTC by Vadim Raskhozhev
Modified: 2017-06-16 21:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-16 21:04:11 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vadim Raskhozhev 2016-10-06 15:46:20 UTC 
Description of problem: if one uses xfce4-panel and its xfce4-xkb-plugin in isolation from the whole Xfce then click on "Keyboard settings" does nothing unless xfce4-settings manually installed.


Version-Release number of selected component (if applicable): 
xfce4-panel-4.12.0-5.fc24.i686
xfce4-xkb-plugin-0.7.1-6.fc24.i686


How reproducible: always


Steps to Reproduce:
1. Ensure you have xfce4-panel but have no Xfce in a whole
2. Launch xfce4-panel
3. Add "Keyboard layouts" applet
4. Right click on it
5. Click on "Keyboard settings" menu item

Actual results: nothing


Expected results: keyboard settings dialog window


Additional info: a line
"Requires:  xfce4-settings"
in xfce4-xkb-plugin.spec would solve the case.
Comment 1 Fedora Admin XMLRPC Client 2017-01-28 15:13:07 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 2 Mukundan Ragavan 2017-02-05 23:56:58 UTC 
I will fix this and push an update soon.

Thanks for the report.
Comment 3 Filipe Rosset 2017-06-16 21:04:11 UTC 
Fixed in http://pkgs.fedoraproject.org/cgit/rpms/xfce4-xkb-plugin.git/commit/?id=6a9a93e06a5926bd7a1f799bbf3989f13ad613af
Note You need to log in before you can comment on or make changes to this bug.