When I initially installed this computer (Asus eeePC 1001PE, KDE 4.4.5, Debian Squeeze) KNetworkmanager was launched at start-up and working fine. Suddenly my wife started complaining that Opera gave "Network errors" after a fresh start.

I have set up KNetworkmanager in Settings -> System Settings -> Advanced -> Autostart, but to no avail. Looking in ~/.config/autostart showed a file KNetworkManager.Desktop.

Then I created manually a link in ~/.kde/Autostart/knetworkmanager to /usr/bin/knetworkmanager. This actually succeeded in starting KNetworkmanager when KDE was launched.

WHy doesn't this simply work as expected?

jlinkels

It is possible that the file in ~/.config/autostart was empty other than for a Hidden=true line, which indicates that this system wide autostart item should be disabled.

These are the last lines of KNetworkManager.Desktop:

Code: Select all

OnlyShowIn=KDE;
Path=
StartupNotify=false
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-DCOP-ServiceType=Unique
X-KDE-StartupNotify=false
X-KDE-SubstituteUID=false
X-KDE-UniqueApplet=true
X-KDE-Username=
X-KDE-autostart-after=panel
X-KDE-autostart-condition=networkmanagementrc:General:Autostart:true


Before these lines there a few dozen lines with the name of the program in different languages.

The file KNetworkManager.Desktop is executable for the user, read for group and others.

Is there a log file somewhere describing the details of what happened with this autostart mechanism?

jlinkels

I see, that is not expected. However, the problem here is that the Path= element effectively clears the path to execute, meaning this file has no effect what so ever. Setting the Path= line to be: Path=/usr/bin/knetworkmanager would fix the autostart.

As far as I know, the Autostart mechanism has no specific logging, but related messages should be stored in ~/.xsession-errors. You may need to enable certain debugging areas in "kdebugdialog" to get the needed output.

I'll try that.

Thanks