I’ve just setup my mother’s desktop PC (HP P6510F) which has a wired connection to the internet, with 64-bit openSUSE-11.3 KDE-4.4.4 desktop. Her PC also has a wireless device, so I decided to set that up. I have it working with the internet (using knetworkmanager), but I have to launch knetworkmanager from a terminal each boot, as it is not launched every boot by default.
What is the ‘proper’ way to have knetworkmanager launched every boot in KDE4 ? (I can hack at this, but if there is a preferred/recommended method, I would rather use that).
I suspect no more detail is needed, but in case one is curious:
But are you set up in the Yast as ifup or networkmanager?
My Laptops spend most of their life hooked up to the wire (they do not run as ifup but rather networkmanager)
I just connect/disconnect the wire as and when and it all happens like magic.
If networkmanager is running at shutdown, it should start again at reboot.
I really just want it done the ‘nominal’ way this is done. I assume knetworkmanager is launched with KDE4 is started. It would not make sence to me to have it launched before (but I confess I am not knowledgeable in this). I know of the KDE4 autostart method, but I’ve never had to do that with my 2 laptops, so it surprises me a bit I need to do that here. … I’ll have to go check my laptops to see how they are setup (mind you they have different hardware).
I really just want it done the ‘nominal’ way this is done.
The KDE-autostart is as nominal as you can get - what’s the problem with it?
However, there seems to be a second way of autostarting in KDE4, because my ~/.kde4/Autostart/ is empty, yet Yakuake starts as soon as I log into KDE. As mentioned, there’s a module in the KDE4-systemsettings to manage autostarts (where I can find an entry for Yakuake), you should give it a peek.