I'm running the latest KDE from kde-testing: kdebase-4.1.96-1.fc10.x86_64, etc
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart. I'm also running the kdenetwork applet and the battery manager plasmoid, and don't think I need these gnome applets, but I can't figure out how to get rid of them. I can quit them, but they always restart.
There are no entries in ~/.kde/Autostart, nor are there any listings in the "Autostart" portion of systemsettings. Session management seems to be working in general, in that normal applications are restarted if and only if they were running when I logged out last. But these two applets seem impossible to kill.
Am I right in thinking that I don't need them, and if so, how do I keep them from starting (short of removing them from my system altogether?).
Jeff Anderson
Gnome autostart apps are in /etc/xdg/autostart.
Martin
On Tue, Jan 20, 2009 at 11:18 PM, Jeffrey D Anderson jdanderson@lbl.gov wrote:
I'm running the latest KDE from kde-testing: kdebase-4.1.96-1.fc10.x86_64, etc
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart. I'm also running the kdenetwork applet and the battery manager plasmoid, and don't think I need these gnome applets, but I can't figure out how to get rid of them. I can quit them, but they always restart.
There are no entries in ~/.kde/Autostart, nor are there any listings in the "Autostart" portion of systemsettings. Session management seems to be working in general, in that normal applications are restarted if and only if they were running when I logged out last. But these two applets seem impossible to kill.
Am I right in thinking that I don't need them, and if so, how do I keep them from starting (short of removing them from my system altogether?).
Jeff Anderson
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
I'm running the latest KDE from kde-testing: kdebase-4.1.96-1.fc10.x86_64, etc
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart. I'm also running the kdenetwork applet and the battery manager plasmoid, and don't think I need these gnome applets, but I can't figure out how to get rid of them. I can quit them, but they always restart.
There are no entries in ~/.kde/Autostart, nor are there any listings in the "Autostart" portion of systemsettings. Session management seems to be working in general, in that normal applications are restarted if and only if they were running when I logged out last. But these two applets seem impossible to kill.
Am I right in thinking that I don't need them, and if so, how do I keep them from starting (short of removing them from my system altogether?).
Gnome autostart apps are in /etc/xdg/autostart.
Right. The autostarting situation is currently a mess. The preference managers in KDE and GNOME both do the wrong thing. To fix it, copy gnome-power-manager.desktop and nm-applet.desktop (and whatever else you want to stop from autostarting in KDE) from /etc/xdg/autostart/ to ~/.config/autostart/. Then append the line "NotShowIn=KDE;" to each file.
See http://standards.freedesktop.org/autostart-spec/autostart-spec-latest.html for an explanation of how this is supposed to work.
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
On Wednesday 21 January 2009 08:16:42 Kevin Kofler wrote:
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
And what about gpk-update-icon? Is it needed in KDE.
Martin Kho
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
Martin Kho wrote:
On Wednesday 21 January 2009 08:16:42 Kevin Kofler wrote:
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
And what about gpk-update-icon? Is it needed in KDE.
Same boat, not really, kpackagekit is the way to go.
(We're still trying to come up with a way to be able to use both, ie, have kpackagekit disable gpk-update-icon when it is installed, but it doesn't work yet, and may never. boo :( )
-- Rex
2009/1/21 Rex Dieter rdieter@math.unl.edu:
Martin Kho wrote:
On Wednesday 21 January 2009 08:16:42 Kevin Kofler wrote:
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
And what about gpk-update-icon? Is it needed in KDE.
Same boat, not really, kpackagekit is the way to go.
(We're still trying to come up with a way to be able to use both, ie, have kpackagekit disable gpk-update-icon when it is installed, but it doesn't work yet, and may never. boo :( )
-- Rex
Now that kpackagekit exists, isn't it the Gnome maintainers team who have to keep the gpk-update-icon out off the way, ie, by putting "NotShowIn=KDE;" in their desktop file? I've added this line and gpk-update-icon no longer shows up. Is there a situation where KDE is installed and kpackagekit isn't?
Martin Kho
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde
On Wednesday 21 January 2009 14:26:10 Martin Kho wrote:
2009/1/21 Rex Dieter rdieter@math.unl.edu:
Martin Kho wrote:
On Wednesday 21 January 2009 08:16:42 Kevin Kofler wrote:
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
And what about gpk-update-icon? Is it needed in KDE.
Same boat, not really, kpackagekit is the way to go.
(We're still trying to come up with a way to be able to use both, ie, have kpackagekit disable gpk-update-icon when it is installed, but it doesn't work yet, and may never. boo :( )
-- Rex
Now that kpackagekit exists, isn't it the Gnome maintainers team who have to keep the gpk-update-icon out off the way, ie, by putting "NotShowIn=KDE;" in their desktop file? I've added this line and gpk-update-icon no longer shows up. Is there a situation where KDE is installed and kpackagekit isn't?
Martin Kho
I wouldn't know how it's set up by default but at least I don't have kpackagekit nor PackageKit installed. I use Yum for package management. So I guess the answer is; yes, such a situation is possible. :)
Martin Kho wrote:
2009/1/21 Rex Dieter rdieter@math.unl.edu:
Martin Kho wrote:
On Wednesday 21 January 2009 08:16:42 Kevin Kofler wrote:
Jeffrey D Anderson wrote:
I notice that every time I restart my desktop nm-applet and guidance-power-manager restart.
guidance-power-manager is not a GNOME applet, it's an applet from KDE extragear. But it isn't needed with 4.2 anymore, you can use the battery plasmoid, which uses PowerDevil for power management, instead.
nm-applet is still needed, the NM plasmoid is not ready yet.
Kevin Kofler
And what about gpk-update-icon? Is it needed in KDE.
Same boat, not really, kpackagekit is the way to go.
(We're still trying to come up with a way to be able to use both, ie, have kpackagekit disable gpk-update-icon when it is installed, but it doesn't work yet, and may never. boo :( )
Now that kpackagekit exists, isn't it the Gnome maintainers team who have to keep the gpk-update-icon out off the way, ie, by putting "NotShowIn=KDE;" in their desktop file? I've added this line and gpk-update-icon no longer shows up. Is there a situation where KDE is installed and kpackagekit isn't?
Right... I'd like to avoid that if at all possible, to allow the use of gpk-update-icon in kde (if kpackagekit isn't installed, esp for F-9 users where kpackagekit wasn't available at release).
But, we may end up having no viable alternative other than the NotShowIn=KDE hammer.
-- Rex
On Wednesday, 21 בJanuary 2009, Rex Dieter wrote:
(We're still trying to come up with a way to be able to use both, ie, have kpackagekit disable gpk-update-icon when it is installed, but it doesn't work yet, and may never. boo :( )
If it was an install-time problem, it could have been solved via alternatives(8). However, the biggest problem is that on the same system we may have both KDE/GNOME installed (that's what I do) and each user login to her preferred desktop environment.
This means we have a login-time personal decision. The trick proposed by freeslkr solves this but it doesn't feel like a systematic solution.
For end users, this is far from intuitive and without GUI wrappers would force them to edit the desktop files instead of adding/removing files/links which is easier and less error prone.
Also, system-administrators who want to set system-wide preferences for autostart would need to edit the contents of these files which is not the best thing (rpmverify anybody?)
IMO, the problem could have a cleaner solution within the current autostart framework by judicious use of symlinks: - All potential desktop files installed to a shared pool. E.g: /usr/share/xdg/autostart - Have per-desktop and generic directories: /etc/xdg/autostart/{KDE,GNOME,FOOBAR,generic} - The per-user autostart directories have similar structure: ~/.config/autostart/{KDE,GNOME,FOOBAR,generic} - The default XDG_CONFIG_DIRS in each desktop (e.g: KDE) is: /etc/xdg/autostart/KDE:/etc/xdg/autostart/generic - Now a simple symlinking of selected entries in /usr/share/xdg/autostart to the wanted directories would achieve the required result.
Advantages: - I think it's still consistent with fdo autostart draft standard. - Normally only the symlinks need to be created/moved/removed. - It's easy to manage with a chkconfig style utility. - It's easy to create management GUI for those who need it. - desktop file contents are not altered in the common case. - But the admin may still have a custom copy of the desktop file if needed (e.g: drop it in /etc/xdg/autostart-local and link to it from the required desktop directory).
Thoughts?