Tumbleweed upgrade problems (on old 32bit laptop)

English Install/Boot/Login
1

This happened now a few times. When trying to upgrade I get a list of packages to upgrade, then they are downloaded and then this happens:

Checking for file conflicts: ...........................................................[done]
( 1/25) Installing: handbrake-gtk-1.0.3-2.3.i586 ......................................[error]
Installation of handbrake-gtk-1.0.3-2.3.i586 failed:
Error: Subprocess failed. Error: RPM failed: warning: waiting for exclusive lock on /var/lib/rpm/Packages                                                                                   
error: cannot get exclusive lock on /var/lib/rpm/Packages                                     
error: cannot open Packages index using db4 - Operation not permitted (1)
error: cannot open Packages database in /var/lib/rpm
....
....
<after a few retries [r chosen] I abort>
...
Abort, retry, ignore? [a/r/i] (a): a
Problem occurred during or after installation or removal of packages:
Installation aborted by user

Please see the above error message for a hint.

Later I try again and at some stage the upgrade installs. So I am trying again and again today but I would like a solution. Any ideas anyone?
Regards
Uli

2

Do you have Packagekit or somesuch installed/running? Any update alert software is redundant and counter-productive with Tumbleweed.
Are there any zombie “.pid” files in “/run” from an abandoned run of zypper?

3

Thanks for your reply, eng-int. I wondered about any update software as well. Normally after starting Tumbleweed, the first thing I do is open the command line for a zypper dup. If there is a software alert where can I disable it? - is it a cron job? I will check next time when I am on my tumbleweed computer.
Cheers
Uli

4

Have you disabled all repos except for the main openSUSE repos? If not, that can cause some problems.

You can always enable those after the upgrade and then check for updates/upgrades in them.

5

Thank you, Fraser_Bell, but this happend only within the last 2-3 weeks and I probably haven’t added a repo for at least half a year. I must admit I have a few added repos - often only for a single piece of software. But I will try this with the next update.
Cheers
uli

6

Yes … not sure if it has anything to do with it, or not, but perhaps it might help.

7

One more thing - after aborting the upgrade I restarted it again and after the 3rd time the upgrade went through. Nothing has changed with the repositories, so it really looks like the packagekit is running at the start-up as eng-int suggested.

8

package kit runs too check for updates at login and blocks other updaters since you can not run two at the same time wait a bit and packagekit should finish or kill it’s PID

9

Thanks, gogalthorp, can this be turned off since there is no need in Tumbleweed for the packagekit to run to check for updates?

10

Assuming KDE/Plasma5 desktop:
In YaST2 | Software Manager
Dependencies – Select “Cleanup when Deleting Packages"
Search for and delete “þackageKit” and "pk-update-icon”
Everything in a “packagekit” search should be removed except for possiblby a couple of libraries required by KDE4 software.

Return to YaST2 Software Manager and lock (Taboo) “þackageKit” and "pk-update-icon”.

11

Thank you, eng-int, I will do this as soon as I have a bit more time!
Cheers
Uli