Bug 320166 - shortcut configuration panel missing
Summary: shortcut configuration panel missing
Status: RESOLVED WORKSFORME
Alias: None
Product: rekonq
Classification: Unmaintained
Component: general (show other bugs)
Version: 2.3.0
Platform: openSUSE Linux
: NOR major
Target Milestone: ---
Assignee: Andrea Diamantini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-23 10:13 UTC by nine
Modified: 2013-05-24 08:42 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nine 2013-05-23 10:13:51 UTC
The shortcut configuration panel that was implemented in 2.1 and still refered to in the documentation: http://docs.kde.org/development/en/extragear-network/rekonq/Shortcut.html seems to be missing in 2.3. The advanced panel is immediately followed by the search engines panel.

Reproducible: Always

Steps to Reproduce:
1. open Configure rekonq window
2. try to find shortcut configuration
Comment 1 Andrea Diamantini 2013-05-23 16:20:53 UTC
well... instead of opening rekonq window, just move eyes to the action over it...
Comment 2 nine 2013-05-23 16:36:12 UTC
I'm sorry, I don't understand your hint. Above the "Configure rekonq" menu entry, there's just the Help submenu. No indication of a shortcut configuration option anywhere.

Even if shortcut configuration has just been moved elsewhere and I'm just too blind to find it, this is still a bug in the documentation, so I'm repoening this bug report.
Comment 3 Jekyll Wu 2013-05-23 16:47:34 UTC
This might be a config file upgrading problem.  Do you have ~/.kde4/share/apps/rekonq/rekonqui.rc ?   Try move it to somewhere, or paste the contents here.
Comment 4 nine 2013-05-23 17:43:13 UTC
Indeed! Thank you. Removing rekonqui.rc reveals a new entry in the tools menu and I could finally remove the bogus (default) shortcut for Stop which conflicted with Next tab.
Comment 5 Andrea Diamantini 2013-05-24 08:42:26 UTC
ok, closing as worksforme, given it was a local problem.