Once my desktop (KDE 5.13.3) starts, the update manager immediately reports “unable to connect…”, because the wireless is not yet connected.
The update manager isn’t listed in “System Settings -> Startup & Shutdown” as I expected it to be, and I don’t know what it’s called or where to find it.
Is there any way to delay it’s startup?
Can’t you right click on it and switch it off?
As you are running Tumbleweed, you do not need it, running
zypper dup
is the only supported way of updating Tumbleweed.
BTW, I do not use Tumbleweed and even then I have not installed the applet, nor PackageManager. I rely on YaST and/or zypper for managing my software.
Hello and thanks for the swift reply.
No, apparently not -
http://repo.duckdns.org/pub/junk/Screenshot_20190320_094632.png
I turned it down to weekly for now though, just to stop it annoying me.
I’ve already used it to update my system and it seems to work perfectly, but if you say that I’m not supposed to use it then I won’t.
That does however beg the question of why it’s supplied as default though, might be worth removing it if it’s causing problems eh?
But that’s all purely academic, back to my actual question - is there a way of delaying it’s start, and/or disabling it?
https://marc.info/?l=opensuse-factory&m=155058644006564&w=2
https://marc.info/?l=opensuse-factory&m=155084132025492&w=2
Specifically
PackageKit should now transparently switch from “up” to “dup” on Tumbleweed
Yes, I know. Littaraly token, I am not correct.
Personaly I do not see any gain in using non-openSUSE “solutions” for a problems that wasn’t there because openSUSE has YaST Software and zypper and that will remain the mainstay of software management on openSUSE. New developments/features will take place there and PackageKit will always lag behind.
Recommend if you want to try something experimental…
I found that the “packagekit.service” is invoked during bootup.
at
/usr/lib/systemd/system/packagekit.service
Recommend try prepending a Sleep timer to the Execstart command.
Remember that you never edit original systemd Unit files directly, copy the the file to /etc/systemd/* as appropriate (system or user), then editing your copy… Your copy will over-ride whatever is original and if you ever want to undo your modification you only have to delete your copied version.
The actual sleep value should be however long it takes for your system to boot up to where you login, plus whatever additional time you want to include.
I don’t know if the bootup parallelism will kick in and allow your boot process to proceed while running packagekit is delayed, if it doesn’t then maybe you can submit a bug/feature request to https://bugzilla.opensuse.org (I can’t think of a reason for packagekit to be a critical requirement for booting) or figure out what is requiring packagekit and try modifying that yourself.
I can’t think of any way an additional delay like this would materially affect normal packagekit operation.
HTH,
TSU
I don’t think there is. This has come up in the past.
However, you can speed up the start of the Wireless connection.
Get into the NetworkManager Connection Editor, and edit your connection. Look for the security tab.
There should be several options for storing the connection password. One of those options is to store unencrypted in a file. Choose that option. And note that the file is not readable by other users.
Once you have done that, it should start to connect as soon as you login – without having to open “kwallet”.
That might still not be fast enough. Once you have that set, then go into the connection editor again. And this time, set it to share the connection with all users. This will require the root password to save the changes. After that, it should connect before you login.