[opensuse-factory] 12.2 M2, Packagekit blockt zypper and Yast Software management
Downloaded the Build 0258 DVD and installed the 12.2 on one of the partitions. Installation was without problems. Update after installation was done without problem. Problem started after I wanted to install KMail. Both Zypper and Yast refused to do their work, complaining about a running packagekit. The offered choice to stop the package kit did not work. Was able to start the software management wit a konsole with package-manager. Known problem? -- Linux User 183145 using KDE4 on a Pentium IV , powered by openSUSE 12.1 (i586) Kernel: 3.3.0-16-desktop KDE Development Platform: 4.8.1 (4.8.1) "release 483") 15:55pm up 1:10, 3 users, load average: 1.21, 0.72, 0.60 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/23/12 05:07, Constant Brouerius van Nidek pecked at the keyboard and wrote:
Downloaded the Build 0258 DVD and installed the 12.2 on one of the partitions. Installation was without problems. Update after installation was done without problem. Problem started after I wanted to install KMail. Both Zypper and Yast refused to do their work, complaining about a running packagekit. The offered choice to stop the package kit did not work. Was able to start the software management wit a konsole with package-manager.
Known problem?
I had the samw problem and ended up removing package kit. If it doesn't want to play nice it has no place on my system. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Mar 23, 2012 at 10:07, Constant Brouerius van Nidek
Downloaded the Build 0258 DVD and installed the 12.2 on one of the partitions. Installation was without problems. Update after installation was done without problem. Problem started after I wanted to install KMail. Both Zypper and Yast refused to do their work, complaining about a running packagekit. The offered choice to stop the package kit did not work. Was able to start the software management wit a konsole with package-manager.
Known problem?
You see this on current versions of openSUSE as well.. ie it's not just something that shows up on 12.2M2. Particularly right after a boot, or right after a clean install, PackageKit will be running to query for updates. I wouldn't call it a bug... only one process can have a lock on the RPM database at a time... unless it holds on to the database lock for a long time - my experience playing with the 12.2 releases is that it releases teh lock just as it has in previous releases, but I haven't beat it up too much either. It will (or at least it should) eventually finish it's tasks and release the RPM database lock. The offered choice to stop PackageKit will work, but it's not immediate... it takes a while to exit cleanly. C. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/23/2012 01:15 PM, C wrote:
You see this on current versions of openSUSE as well.. ie it's not just something that shows up on 12.2M2. Particularly right after a boot, or right after a clean install, PackageKit will be running to query for updates. I wouldn't call it a bug... only one process can have a lock on the RPM database at a time... unless it holds on to the database lock for a long time - my experience playing with the 12.2 releases is that it releases teh lock just as it has in previous releases, but I haven't beat it up too much either.
It will (or at least it should) eventually finish it's tasks and release the RPM database lock. The offered choice to stop PackageKit will work, but it's not immediate... it takes a while to exit cleanly.
C.
Actually it is a bug. PackageKit holds teh ZYpp lock. There is no reason we lock ZYpp for read only operations. The only exception is refreshing before calculating the updates, but we can introduce some synchronization there. Not worth reporting it. We are pretty aware of the problem, but fixing it is not a small effort and the urgency is not that high. There was a urgent bug before, where PackageKit never released the lock, but it got fixed with newer releases of PackageKit. Duncan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 23/03/12 20:07, Constant Brouerius van Nidek wrote:
Downloaded the Build 0258 DVD and installed the 12.2 on one of the partitions. Installation was without problems. Update after installation was done without problem. Problem started after I wanted to install KMail. Both Zypper and Yast refused to do their work, complaining about a running packagekit. The offered choice to stop the package kit did not work. Was able to start the software management wit a konsole with package-manager.
Known problem?
I am not sure that it is a "problem". It is simply that packagekit is accessing the repos to refresh them and then advise you if there are updates available. You have 2 choices to stop packagkit dead in its tracks: use the command 'ps aux' as root and then use 'kill xxxxx' where xxxxx is the packagekit's ID number; or you go to Kickoff>Applications>System>>Monitor>System Monitor and kill the process there (just like you would do in Windows). Oh, the last option is to keep answering YES for for packagekit to stop until it finally succumbs to the YES :-) . BC -- Wife sent me to the doctor to get the pills for me to have an erection. When I came back I gave her the packet of slimming pills. I am still looking for somewhere to live. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Basil Chupin -
C -
Constant Brouerius van Nidek -
Duncan Mac-Vicar P. -
Ken Schneider - openSUSE