Bug 789133

Summary:	Zypper & Yast blocked by packagekit indefinitely
Product:	[openSUSE] openSUSE 12.2	Reporter:	Forgotten User j8kcTVFsEa <forgotten_j8kcTVFsEa>
Component:	YaST2	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	forgotten_gp-dpinp5x, forgotten_j8kcTVFsEa
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User j8kcTVFsEa 2012-11-10 00:56:07 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.5 Safari/537.17

Fresh install of OpenSUSE 12.2, user cannot operate the package management system because it is blocked by packagekit INDEFINITELY.


Reproducible: Always

Steps to Reproduce:
1.Install OS.
2.Open terminal to use zypper OR open Yast2 Software management GUI
3.Attempt to add remove any software.
Actual Results:  
All attempts to operate the package management with zypper or Yast2 produce an error message stating packagekit has blocked the operation.

Clicking 'yes' to kill packagekit does not work. The user is presented with unending prompts to kill pakagekit until clicking 'no' & abandoning attempts to use the package management system.

Attempting to use packagekit to make package changes produces a non responsive dialog. Nothing further happens.

Expected Results:  
The package management system will promptly be able to operate without hindrance upon installation of the operating system.

Only way to fix the problem:

1) Open Apper Updater & reconfigure to 'never' check.

2) Set "apper" to not automatically start.
(In KDE, that's at "Configure Desktop" --> "Startup and Shutdown" --> "Service Manager")

3) Reboot & remove packagekit (and apper).
(In KDE open a terminal(console) & issue: sudo zypper rm packagekit)


User is finally free to use Zypper in terminal(console) or Yast in GUI as intended.

Comment 1 Michael Andres 2012-11-12 11:10:11 UTC

Looks like sometimes packagekit does not respond to the shutdown request zypper sends via dbus.

*** This bug has been marked as a duplicate of bug 731450 ***

Comment 2 Forgotten User j8kcTVFsEa 2012-11-13 01:41:16 UTC

(In reply to comment #1)
> Looks like sometimes packagekit does not respond to the shutdown request zypper
> sends via dbus.
> 
> *** This bug has been marked as a duplicate of bug 731450 ***

On my systems, packagekit never responds hence my need to kill it & remove it.

Comment 3 Forgotten User gp-dpinp5x 2013-01-04 03:27:19 UTC

I have just upgraded from openSUSE 12.1 to 12.2. I encountered this on the first attempt to run the package updater from YAST2.

The message that I receive is, "System management is locked by the application with pid 4321 (/usr/lib/packagekitd). Close this application before trying again."

However I can't find packagekit or 4321 in the output of "ps aux". I conclude that it isn't actually running, and therefore can't be killed. There might be a stale lock file hanging around, possibly from before the upgrade.

Comment 4 Forgotten User gp-dpinp5x 2013-01-04 03:32:58 UTC

Upon closing the updater and running it again (but not restarting YAST2), it appears to be functioning normally. So perhaps the issue is that it killed packagekit but it didn't detect that it had done so.