FS#22423 - [wicd] shouldn't put .desktop file in /etc/xdg/autostart
Attached to Project:
Arch Linux
Opened by Peter Lewis (petelewis) - Friday, 14 January 2011, 09:30 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 20 March 2011, 17:19 GMT
Opened by Peter Lewis (petelewis) - Friday, 14 January 2011, 09:30 GMT
Last edited by Isenmann Daniel (ise) - Sunday, 20 March 2011, 17:19 GMT
|
Details
Description: The wicd package places a .desktop file for its
GTK client in /etc/xdg/autostart, which I don't think should
be there. This means that the GTK client will automatically
be started for all users on the machine using an XDG
compliant desktop.
They should be given the choice about using this client or another, in the usual way - having the option to include the .desktop file in their own XDG autostart file. Please remove the .desktop file from /etc/xdg/autostart. Additional info: * package version(s): 1.7.0-6 Thanks. |
This task depends upon
Closed by Isenmann Daniel (ise)
Sunday, 20 March 2011, 17:19 GMT
Reason for closing: Fixed
Additional comments about closing: Package was splitted into two seperated packages like mentioned in last comment.
Sunday, 20 March 2011, 17:19 GMT
Reason for closing: Fixed
Additional comments about closing: Package was splitted into two seperated packages like mentioned in last comment.
Heres an easy way to disable it:
http://www.linuxquestions.org/questions/slackware-14/wicd-client-gtk-how-to-get-rid-of-it-843979/#post4157514
Although IMO a better solution is splitting the wicd package into non GTK and GTK parts.
FWIW, I'd quite like to have the client installed in case I need to use it, but the majority of the time I don't want it running. Splitting the GTK part out wouldn't solve this use case.
all software that i know and are suppose to run at login have by default a file in /etc/xdg/autostart. From a DE perspective its perfectly normal because users don't have to know what "services" have to start, but i can disable them from autostart by unchecking them from Startup Applications. All XDG compliant DEs have such thing.
The number of users who expect to work out of the box is greater than the number of users who don't want it. You want to have wicd installed but you don't want the client to autostart. I have the same configuration but with networkmanager.
The applet simply doesn't appear when networkmanager daemon is not started and i used netcfg as default network manager. Maybe you should try this and open a feature request upstream if doesn't do the same.
Also, the wicd service is started anyway if it's in DAEMONS, and will connect to the network regardless of whether or not a client is running (that's one of the benefits of wicd). The client is only required if you want to change the settings.
As an aside, I couldn't find an entry for wicd in the KDE services configuration dialog to let me disable it being started at login, as you suggested. I'd have to follow what Greg's link suggests. This all seems overkill.
FS#22550- [wicd] Split package into wicd and wicd-gtk" I will try to split the wicd package into wicd and wicd-gtk. wicd will have all the stuff you need that the core application and ncurses interface is running. The whole GTK stuff will be in the wicd-gtk package including the autostart file.