Bug 1630388

Summary:	kmail Toollbar and statusbar disappear on restart of application
Product:	[Fedora] Fedora	Reporter:	Frank Danapfel <fdanapfe>
Component:	kmail	Assignee:	Rex Dieter <rdieter>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	28	CC:	rdieter
Target Milestone:	---	Keywords:	Upstream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	kmail-18.04.3-2.fc28	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-27 02:34:16 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 Frank Danapfel 2018-09-18 13:41:23 UTC

Description of problem:
Since the latest updates of the KDE packages on my Fedora 28 system I'm having the problem that after stopping the kmail application and starting it again the toolbar and status bar are no longer visible, even though they were set to be visible before the application was stopped 

Version-Release number of selected component (if applicable):
$ rpm -qa --last|grep -i kmail
kmail-18.04.3-1.fc28.x86_64                   Thu 23 Aug 2018 18:45:11 CEST
kmail-libs-18.04.3-1.fc28.x86_64              Thu 23 Aug 2018 18:45:10 CEST
kmail-account-wizard-18.04.3-1.fc28.x86_64    Thu 23 Aug 2018 18:44:57 CEST
kf5-kmailtransport-akonadi-18.04.3-1.fc28.x86_64 Thu 23 Aug 2018 18:44:54 CEST
kf5-kmailtransport-18.04.3-1.fc28.x86_64      Thu 23 Aug 2018 18:44:54 CEST

How reproducible:
always

Steps to Reproduce:
1. start kmail and verify that in 'Settings' menu 'Show toolbar' is active and toolbar and status bar are visible
2. stop kmail and start it again
3.

Actual results:
Toolbar and status bar are no longer visible after application has been restarted

Expected results:
Toolbar and status bar should still be visible

Additional info:
This issue has been discussed upstream:
https://forum.kde.org/viewtopic.php?f=215&t=153138

As documented in the forum discussion a patch seems to be available upstream to fix this issue:
https://phabricator.kde.org/D14454

Comment 1 Rex Dieter 2018-09-18 14:04:10 UTC

See also 
https://bugs.kde.org/show_bug.cgi?id=396339

Comment 2 Fedora Update System 2018-09-18 17:04:46 UTC

kmail-18.04.3-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-a1a41ddd27

Comment 3 Fedora Update System 2018-09-18 17:05:21 UTC

kmail-18.04.3-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-2dcc691c7a

Comment 4 Fedora Update System 2018-09-20 11:10:18 UTC

kmail-18.04.3-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-2dcc691c7a

Comment 5 Fedora Update System 2018-09-20 16:16:50 UTC

kmail-18.04.3-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-a1a41ddd27

Comment 6 Frank Danapfel 2018-09-24 12:15:16 UTC

After updating to kmail-18.04.3-2.fc28.x86_64 the toolbar and statusbar are visible again after quiting and restarting kmail.

Comment 7 Fedora Update System 2018-09-27 02:34:16 UTC

kmail-18.04.3-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2018-09-28 16:56:43 UTC

kmail-18.04.3-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.