924662 – Apper shows details of one patch file, but going to the other it does not show the details

Bug 924662 - Apper shows details of one patch file, but going to the other it does not show the details

Summary: Apper shows details of one patch file, but going to the other it does not sho...

Status:	RESOLVED DUPLICATE of bug 855993

Alias:	None

Product:	openSUSE Distribution
Classification:	openSUSE
Component:	KDE Applications (show other bugs)
Version:	13.2
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2015-03-27 11:02 UTC by Freek de Kruijf
Modified:	2015-03-27 11:13 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Freek de Kruijf 2015-03-27 11:02:12 UTC

Just now, 2015-03-27, I am trying to update openSUSE 13.2 using apper. There are two patch files for security updates, 2015-265 and 2015-266. When I select one of these the details are show at the bottom. After that selecting the other, I keep seeing the dots going round and round. Canceling the application and starting it again and selecting the other shows the details, selecting the one which showed the details the first time, only shows the round going dots.

Comment 1 Wolfgang Bauer 2015-03-27 11:13:41 UTC

Known problem, that exists since years (11.4 at least).

In short, Apper's update ids seem to get invalid when packagekitd shuts itself down (it does that by default after 15 seconds of idle time).

As a workaround you could raise the ShutdownTimeout value in /etc/PackageKit/PackageKit.conf (or remove the setting completely, that packagekitd doesn't quit at all), but then packagekitd will of course block YaST/zypper for a longer time period.

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