Bug 1615818

Summary:	Apper crashes after any update
Product:	[Fedora] Fedora	Reporter:	Jukka Lahtinen <jtfjdehf>
Component:	apper	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	rdieter, rhughes, smparrish
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-25 03:53:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jukka Lahtinen 2018-08-14 10:16:28 UTC

Description of problem:
Whenever I upgrade some packages with apper, apper crashes with a segmentation fault after it has finished the update process and is supposed to show the list of remaining updatable packages again.

Version-Release number of selected component (if applicable):
1.0.0-1.fc28.x86_64

How reproducible:
Happens always since I upgraded my Fedora to 28.

Steps to Reproduce:
1. Start apper and click updates
2. Uncheck the box for "nn Updates selected" and select one or more packages
3. Click Update

Actual results:
Crash after the update process. When started from Konsole, it shows several rows of "kf5.kwidgetsaddons: Invalid pixmap specified." during the process, and finally "Segmentation fault" when the apper window disappears.

Expected results:
Apper upgrades the selected packages and returns to the listing of packages.

Additional info:

Comment 1 Jukka Lahtinen 2018-11-18 21:37:50 UTC

I upgraded to Fedora 29, and this still happens with apper-1.0.0-3.fc29.x86_64

Comment 2 Rex Dieter 2018-11-21 17:16:47 UTC

please report the issue to bugs.kde.org if possible, thanks.

Comment 3 Rex Dieter 2018-11-25 03:53:38 UTC

Thanks for reporting at
https://bugs.kde.org/show_bug.cgi?id=401381

We'll continue to track it there.