Description of problem:
knetworkmanager does not place a .desktop file in $KDEDIRS/share/autostart
causing it to not always appear in the systray applet on login.
knetworkmanager's .desktop is in $KDEDIRS/share/autostart while running the F7
livecd and it has the required entries for KDE to autostart it.
Version-Release number of selected component (if applicable):
knetworkmanager-0.1-0.9.svn20070409.fc7 (I chose kdenetwork as the component
because knetworkmanager is not yet in the list.)
With a fresh user created, knetworkmanager does appear to start. Upon
restoring my existing /home partition and user, knetworkmanager fails to
Steps to Reproduce:
1. Login, knetworkmanager icon is not present in the systray.
2. Find it on the menu and start it. Icon appears in the systray,
configuration set to start at login.
3.Re-login and note the absence of knetworkmanager's icon in the systray.
knetworkmanager refuses to start with KDE even after checking the associated
checkbox in the app's configuration tool.
knetworkmanager should start at login if configured to do so.
I've noticed kpowersave (also start-able at login) does place a .desktop file
works for me.
I've also been told Novell/SuSE
include /usr/share/autostart/knetworkmanager-autostart.desktop in their
Kerry Beagle does not start too.
may be related to bug #243611
Doncho, probably worth filing a separate bug against kerry.
I'd like to confirm that this bug (knetworkmanager not starting with your
session) is affecting me as well. Fedora 7,
Tried out the knetworkmanger-0.2 koji build, and it actually started with my kde
session! Looks like we have a winner.
knetworkmanager-0.2-0.1.svn20070815.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.
You might want to add "OnlyShowIn=KDE;" to the desktop file
in /usr/share/autostart since Gnome has its own panel.
knetworkmanager-0.2-0.1.svn20070815.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.