Op woensdag 8 november 2017 13:59:03 CET schreef Richard Brown:
On 8 November 2017 at 13:42, Freek de Kruijf
wrote: You say "the package manager" - which package manager?
I'm not able to reproduce what you're reporting with zypper or YaST, example below:
The following package is going to be upgraded: libquicktime0
1 package to upgrade. Overall download size: 0 B. Already cached: 189.0 KiB. No additional space will be used or freed after the operation. Continue? [y/n/...? shows all options] (y): y In cache libquicktime0-1.2.4cvs20150223-13.1.x86_64.rpm
(1/1), 189.0 KiB (565.3 KiB unpacked)
Checking for file conflicts: ......................................................................... ... .......[done] (1/1) Installing: libquicktime0-1.2.4cvs20150223-13.1.x86_64 ...................................................[done]
The package manager which is present as an icon in the system tray of a Plasma desktop. I assume this is the front-end of the package PackageKit.
-- fr.gr.
member openSUSE Freek de Kruijf
I can confirm that packagekit behaves fine (logs below)
Therefore I have two theories
1- A bug that is specific to KDE's wrapper around PackageKit - it's theoretically possible Plasma's frontend is doing something stupid 2- User error - are you sure you didn't have any other rpm tools accessing the database at the time? zypper? YaST - the error could very easily be a perfectly valid "I cant access the database because it's locked" warning
When PackageKit went wrong, after that I did a zypper dup, which went OK. At the moment of the error I did not start or use any other thing to update the packages. Right after starting my desktop and plasma I saw the icon active in the system tray. Shortly after that I got the message about 3 packages waiting to be updated. So I acknowledged the update action, which resulted in the error message. I did the same you did with pink-pony, and it went OK. At that moment there was a new message that two packages waited for updating with that icon in the system tray. Acknowledging it went OK now. So maybe a temporary glitz, which is resolved now? Will come back when it reappears. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org