Bug 399651

Summary:	race condition with rpm DB: awkward resolution
Product:	[openSUSE] openSUSE 11.0	Reporter:	macias - <bluedzins>
Component:	libzypp	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P4 - Low	CC:	dmacvicar
Version:	RC 1
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	conflict

Description macias - 2008-06-12 13:10:01 UTC

The OSU was running all the time and I started SM. SM stated there is another process that is using rpm DB so would I like to continue or retry. First of all I would like to abort, so this is flaw #1.

I chose several times retry (meanwhile I quit OSU). It didn't change a thing. Flaw #2.

So I chose "continue", and SM stated that it cannot continue. So why bother user with a choice of continuing? Flaw #3.

Comment 1 Stephan Kulow 2008-06-13 09:09:42 UTC

can you please provide screenshots? I have my doubts it was speaking about rpm

Comment 2 macias - 2008-06-13 16:36:50 UTC

Sorry, it was not a verbatim quote :-) Anyway, ss follows.

Comment 3 macias - 2008-06-13 16:37:25 UTC

Created attachment 222078 [details]
conflict

Comment 4 Stephan Kulow 2008-06-14 07:30:47 UTC

I think this needs to be handled in libzypp somewhere - that one app can ask another to stop automated process. I.e. give the locks a priority

Comment 5 macias - 2008-06-14 08:36:30 UTC

This would be a great solution. Just note in flaw #2 -- I quit OSU, so there is only one app running that has access to rpm DB and yet it cannot get this access.

Comment 6 Duncan Mac-Vicar 2008-07-20 16:32:07 UTC

Making a multi-pid readable lock is tracked in another bug. The part of the confusing button labels I think Ladislav could look at it.

Comment 7 Michael Schröder 2008-07-21 10:47:29 UTC

What's a "multi-pid readabe lock"?

Comment 8 Ladislav Slezák 2008-07-30 08:01:10 UTC

The buttons have already been fixed, see bug #293356

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