Tim, All,
As part of the ongoing clean up with kcontrol, where do we want to capture config options that are outdated or need changing in the default kcontol settings? We have the current etherpad from the recent discussion on kcontol revision. Do we want to use that? It seems like something like that is better than filing individual bugs for each config item found. However, we would still need a bug that says "fix defaults needed listed in etherpad X" so it isn't forgotten.
Looking through the config today on builds from yesterday, I found:
kcontol->Internet & Network -> Web Browser -> Web Shortcuts -> KDE WebSVN
that still references 'tdesvn' as the shortcut.
Ideas for handling this? What's your preference?
On 03/05/2012 01:19 PM, David C. Rankin wrote:
Looking through the config today on builds from yesterday, I found:
kcontol->Internet & Network -> Web Browser -> Web Shortcuts -> KDE WebSVN
Also Internet & Network -> Zeroconf Service Discovery -> Enable Zeroconf network browsing
results in the error dialog:
Sorry - KDE su "Command '/usr/share/avahi/enable_avahi 1' not found.
Two issues - 'KDE' and more importantly 'Command not found'.
There is no enable_avahi command:
13:21 valkyrie:~> pacman -Q | grep avahi avahi 0.6.31-1
13:21 valkyrie:~> l /usr/share/avahi/ total 24 drwxr-xr-x 3 root root 4096 Feb 21 21:32 . drwxr-xr-x 81 root root 4096 Mar 5 11:15 .. -rw-r--r-- 1 root root 560 Feb 21 21:32 avahi-service.dtd drwxr-xr-x 2 root root 4096 Feb 21 21:32 interfaces -rw-r--r-- 1 root root 5132 Feb 21 21:32 service-types
Do we want a bug on the fact there is no avahi_enable? I'll add the 'KDE' issue to wherever we decide to keep track of kcontrol issues.
Looking through the config today on
builds from yesterday, I found:
kcontol->Internet & Network -> Web Browser
-> Web Shortcuts -> KDE WebSVN
Also Internet & Network -> Zeroconf Service Discovery -> Enable Zeroconf network browsing
results in the error dialog:
Sorry - KDE su "Command '/usr/share/avahi/enable_avahi 1' not found.
Two issues - 'KDE' and more importantly 'Command not found'.
There is no enable_avahi command:
I mentioned this issue in our previous discussions about kcontrol. When a kcontrol item is not installed or can't be run, the item should not appear in the menu or should be ghosted in the tree. Additionally, the source code itself should be checked to add more robust error checking. A lot of code inherited from KDE3 is written with the presumption of the base operating system and packages.
We have an etherpad to address the kcontrol overhaul. Just place your comments and observations there. :)
Darrell
On 03/05/2012 02:17 PM, Darrell Anderson wrote:
We have an etherpad to address the kcontrol overhaul. Just place your comments and observations there. :)
OK, that what I wanted to know. I'll use etherpad 40.