[opensuse-kde] Configuring the start order of apps when starting session
Hi there, is it possible with KDE 4.6.0 to set the order of the start of apps when a KDE session starts? I would like to have the Networkmanager to be the first thing that starts to establish a internet connection. Currently the korganizer module starts before Networkmanager. I would like to be Networkmanager first. Regards Malte PS: good old Amiga OS 3 could change the start order virtually 20 years ago ;-) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sun, Mar 20, 2011 at 10:16 PM, Malte Gell <malte.gell@gmx.de> wrote:
Hi there,
is it possible with KDE 4.6.0 to set the order of the start of apps when a KDE session starts? I would like to have the Networkmanager to be the first thing that starts to establish a internet connection. Currently the korganizer module starts before Networkmanager. I would like to be Networkmanager first.
Regards Malte
PS: good old Amiga OS 3 could change the start order virtually 20 years ago ;-)
I'm not aware of such a method, but have you submitted a bug report about the problem? Rather than these sorts of work-arounds, it would be better if applications weren't started until after other applications they depend on. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Mandag den 21. marts 2011 03:16:54 skrev Malte Gell:
is it possible with KDE 4.6.0 to set the order of the start of apps when a KDE session starts? I would like to have the Networkmanager to be the first thing that starts to establish a internet connection. Currently the korganizer module starts before Networkmanager. I would like to be Networkmanager first.
I wonder if you did a dvd install, and hence are using KNetworkManager? (cuz of a bug) Install 'plasmoid-networkmanagement' if it's not already installed, being a plasmoid, I should think it would start up before any apps. and KNM is dead anyway, you should use PNM. So it's two flies with one stroke, if my guess is correct that you're currently using KNM. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Martin Schlander <martin.schlander@gmail.com> wrote
I wonder if you did a dvd install, and hence are using KNetworkManager? (cuz of a bug)
Yes I use the DVD install.
Install 'plasmoid-networkmanagement' if it's not already installed, being a plasmoid, I should think it would start up before any apps. and KNM is dead anyway, you should use PNM.
So it's two flies with one stroke, if my guess is correct that you're currently using KNM.
What the hell is "PNM"? I thought Networkmanager is the current networking layer. Malte -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Mon, 21 Mar 2011 10:48, Malte Gell <malte.gell@...> wrote:
Martin Schlander <martin.schlander@...> wrote
I wonder if you did a dvd install, and hence are using KNetworkManager? (cuz of a bug)
Yes I use the DVD install.
Install 'plasmoid-networkmanagement' if it's not already installed, being a plasmoid, I should think it would start up before any apps. and KNM is dead anyway, you should use PNM.
So it's two flies with one stroke, if my guess is correct that you're currently using KNM.
What the hell is "PNM"? I thought Networkmanager is the current networking layer.
KNM = Kde Networkmanager (Frontend) PNM = plasmoid-networkmanagement (Frontend, Plasma) GNM = nm-applet from package NetworkManager-gnome (Frontend, Gnome, Systray, works also in KDE) Networkmanager = Backend + cli Personally I tried to do something like this by renameing the starting entries (*.service, *.desktop) with numbers in front of the names to get an reliable starting sequence at the beginning of the Networkmanager era. Got feed up with it and gone back to the 'old' ifup/ifdown on my Desktops. -- HTH, Yamaban out. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday, March 21, 2011 03:16:54 Malte Gell wrote:
is it possible with KDE 4.6.0 to set the order of the start of apps when a KDE session starts? I would like to have the Networkmanager to be the first thing that starts to establish a internet connection. Currently the korganizer module starts before Networkmanager. I would like to be Networkmanager first.
Why? Let me guess: Your problem is not that the startup order is wrong, but that korganizer doesn't understand that it's offline, and doesn't get noticed when it's online, hence won't refresh the data from your webservice. That's a one or two line change in korganizer, best is to file a bugreport against it. Or am I guessing wrongly? :)
PS: good old Amiga OS 3 could change the start order virtually 20 years ago ;-)
And it's now, 20 years later, still the wrong way to go about it. :) You can actually determine when something's started during session setup, but that is not exposed to the user, and I don't think it should. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Wed, 23 Mar 2011 11:37:16 +0100 schrieb Sebastian Kügler <sebas@kde.org>:
Let me guess: Your problem is not that the startup order is wrong, but that korganizer doesn't understand that it's offline, and doesn't get noticed when it's online, hence won't refresh the data from your webservice. That's a one or two line change in korganizer, best is to file a bugreport against it.
That is correct. Korganizer fetches data from my Google calendar and when the system is offline it produces an error message. I think Korganizer can be set to fetch calendars every X minutes which would be a workaround. Malte btw: being able to set the start order of apps would be a good thing though -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Wednesday, March 23, 2011 22:21:33 Malte Gell wrote:
Am Wed, 23 Mar 2011 11:37:16 +0100
schrieb Sebastian Kügler <sebas@kde.org>:
Let me guess: Your problem is not that the startup order is wrong, but that korganizer doesn't understand that it's offline, and doesn't get noticed when it's online, hence won't refresh the data from your webservice. That's a one or two line change in korganizer, best is to file a bugreport against it.
That is correct. Korganizer fetches data from my Google calendar and when the system is offline it produces an error message. I think Korganizer can be set to fetch calendars every X minutes which would be a workaround.
That's also not the right way to go about it. KDE's Solid framework can notify you once the network comes up, you connect your apps' synching and updating mechanism to that signal, and you get *INSTANT* updates once your network comes up. I've actually done this for quassel some time ago, and it works nicely: I remove the network connection, quassel goes into disconnected mode immediately. As soon as the network comes up again, quassel reconnects without any sort of timeout. My experience is, that a timeout is not very useful for applications anyway, since the first thing I'd do after the network comes up is hit the refresh button anyway, so the updating has to happen immediately, if it should be useful. Anyway, please file a WISHLIST bug against korganizer that it should update on network connect.
Malte btw: being able to set the start order of apps would be a good thing though
Why? You just pointed out that your usecase is a completely different issue... Besides, apps might be started in parallel (which certainly improves startup performance on multicore systems with fast disks), so there isn't really an order to begin with. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (5)
-
Malte Gell -
Martin Schlander -
Sebastian Kügler -
todd rme -
Yamaban