Bug 934553

Summary:	During updates if ADOBE license is agreed to this does not seem to be passed back to the installer.
Product:	[openSUSE] openSUSE Distribution	Reporter:	Forgotten User U4acEPPbQT <forgotten_U4acEPPbQT>
Component:	Other	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	wbauer
Version:	13.2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User U4acEPPbQT 2015-06-12 11:18:35 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier: 

When the updates available icon appears in the panel and I attempt install them, if there the a flash license to agree to the update hangs with status "Waiting for tasks to complete" This survives a reboot. Canceling the license agreement (don't agree) cancels the whole process

Reproducible: Always

Steps to Reproduce:
1.Click on update icon when an ADOBE Flash update is pending.
2.Select install
3. Agree to license
Actual Results:  
No packages are updated and the update never completes.

Expected Results:  
Update should complete.

If you attempt to install a software package (in my case libxml2-devel) while the "waiting for tasks to complete" status is still showing you will receive a conflict notice that gives unlocking the the flash package as a resolution.

Doing this will then give a further conflict for KDE-flash and a resolution of installing the ADOBE update. Accepting the resolution will install the package requested to be installed and all updates in the patch set that were requested via the Software updater icon.

I've had this happen on both 13.1 and 13.2 (didn't resolve it on 13.1) as well as on both a desktop and laptop, all X86_64.

I've marked this as Major because when it happens all update checking/installing is effectively blocked.

Comment 1 Wolfgang Bauer 2015-06-12 11:27:47 UTC

The issue with the updater hanging when a license agreement is necessary has already been reported as bug#908730 .

I never saw this on 13.1 though (which I don't use any more).
Did you update PackageKit to a newer version from some additional repo there maybe?

And what exactly is this "conflict" you mention?
Apper/PackageKit do not allow to resolve conflicts manually. They just fail if there is a conflict.
Or are you using YaST in this case?

Comment 2 Forgotten User U4acEPPbQT 2015-06-12 11:42:40 UTC

Sorry I should have been clearer.

The 'conflict' was reported when I attempted to install a package via YaST ->Software Management after the 'Waiting for tasks to complete' status was shown.

I included that because it both showed a possible problem area and a work-around if someone was having the problem.

DaveC

Comment 3 Forgotten User U4acEPPbQT 2015-06-12 12:02:22 UTC

(In reply to Wolfgang Bauer from comment #1)
> The issue with the updater hanging when a license agreement is necessary has
> already been reported as bug#908730 .
> 
> I never saw this on 13.1 though (which I don't use any more).
> Did you update PackageKit to a newer version from some additional repo there
> maybe?
> 
> And what exactly is this "conflict" you mention?
> Apper/PackageKit do not allow to resolve conflicts manually. They just fail
> if there is a conflict.
> Or are you using YaST in this case?

Created a new comment instead of replying Comment was: 

> Sorry I should have been clearer.

> The 'conflict' was reported when I attempted to install a package via YaST >> ->Software Management after the 'Waiting for tasks to complete' status was shown.

> I included that because it both showed a possible problem area and a 
> work-around if someone was having the problem.

Added: bug#908730 was on a tumblweed report so I didn't pick i up.

DaveC

Comment 4 Wolfgang Bauer 2015-06-12 12:26:44 UTC

(In reply to David Craddock from comment #2)
> The 'conflict' was reported when I attempted to install a package via YaST
> ->Software Management after the 'Waiting for tasks to complete' status was
> shown.

Well, YaST is totally unrelated to the update applet, which uses PackageKit.

Using YaST->Online Update/Software Management or "zypper patch"/"zypper up" to install the updates is a workaround though. Those have no problems with the license agreement. You might have to kill packagekitd though if it is running.

Another workaround would be to interact with PackageKit in any way, this should resolve the hanging state.
E.g. run "pkcon refresh" or "pkcon get-updates" in a terminal, or run Apper (the application) or pk-update-viewer and check for updates there. The original, already running, update should continue then.

I'm marking this as duplicate of the other bug now.
Please feel free to report the YaST conflict separately if you think it is a bug.
I cannot reproduce this though. Actually YaST should complain that the software management is blocked by PackageKit and offer to ask it to quit (which might not work at all in this case, but that's a different problem and is also reported already AFAIK).

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

Comment 5 Wolfgang Bauer 2015-06-12 12:30:43 UTC

(In reply to David Craddock from comment #3)
> Added: bug#908730 was on a tumblweed report so I didn't pick i up.

Yes. The same issue exists in 13.2 and Tumbleweed. It seems to be a bug in all PackageKit 1.0.x versions AFAICT, and isn't fixed yet even in Tumbleweed's version.

Still, there's no need to keep two bugs open for the same problem. If it gets fixed in Tumbleweed, I will make sure that the fix will be released as update for 13.2 as well (and 13.1 if necessary, but as mentioned, I never saw the problem there).