Bug 289844

Summary: Akregator forgets pane sizes when launched as part of the KDE session
Product: [Applications] akregator Reporter: Jakub Januszkiewicz <jakub.januszkiewicz>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: goodhabit, s2
Priority: NOR    
Version: 4.8   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jakub Januszkiewicz 2011-12-26 11:45:14 UTC 
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

Almost every time I start my KDE session, the page sizes in Akregator are reset. The Feeds pane is too wide, the middle pane is too wide (or too high, depending on which layout is chosen) and the article pane is too narrow/short.

It doesn't happen when I run Akregator manually - it only occurs when it is started automatically as a part of the session.

This has been happening since at least 4.2 and still happens in 4.7.4 (I couldn't choose that version when reporting this bug so I chose 4.7.3).

Reproducible: Sometimes

Steps to Reproduce:
1. Start Akregator.
2. Change pane sizes to your liking.
3. Exit KDE session and start it again.

Actual Results:  
Pane sizes are usually changed.

Expected Results:  
Pane sizes stay the way they were.
Comment 1 Maarten De Meyer 2012-11-25 11:26:49 UTC 
*** Bug 210254 has been marked as a duplicate of this bug. ***
Comment 2 Maarten De Meyer 2012-11-25 11:26:57 UTC 
*** Bug 259366 has been marked as a duplicate of this bug. ***
Comment 3 Denis Kurz 2016-09-24 19:38:27 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:30:33 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.