Bug 228179 - konversation does not remember window size from systray icon
Summary: konversation does not remember window size from systray icon
Status: RESOLVED WORKSFORME
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.2.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-02-23 11:11 UTC by p92
Modified: 2018-10-27 04:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description p92 2010-02-23 11:11:13 UTC
Version:           1.2.3 (using 4.4.00 (KDE 4.4.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-19-generic

setup konversation to show the systray icon
maximize konversation window
now click on X to close the window
now click on systray icon to restore konversation window

=> konversation win is restored on a fixed size and position

expected : konversation window restored in the same position and size it had before beeing closed

note: kontact had the same bug in the beginning of kde4 life
Comment 1 Eike Hein 2010-02-23 14:24:25 UTC
I can't reproduce this here on two different KDE 4.4 systems, but we can have a look through contact's SVN history and try to find out what they changed.
Comment 2 Eike Hein 2010-02-23 18:48:56 UTC
Additional info: Jonathan Thomas from Kubuntu tells me that this only happens when there's no config yet. If you set the Konversation window to a custom size and then quit and restart, the problem goes away.

This is most likely a bug in KMainWindow's (in kdelibs) restore-size-from-config-file-on-creation code where that code also gets run on tray restore rather than just initial window creation when it shouldn't, and messes things up.
Comment 3 p92 2010-02-24 01:06:51 UTC
well I agree with comment #2   the problem disappears at subsequent launches, but this can confuse a newbie into thinking kde is not well polished.
Comment 4 Eike Hein 2010-02-24 01:13:10 UTC
Comment #2 wasn't meant to say that it shouldn't be fixed :). The way bug tracking works is that we collect all the information we have about the circumstances in which a defect arises, because being able to reproduce a bug is usually necessary to be able to fix a bug. Without the info up there, a developer looking into the matter might not be able to reproduce it, so he/she can't take a closer look at what happens and why it happens and how it can be fixed.
Comment 5 p92 2010-02-24 01:24:11 UTC
note that i did not close this bug ;) at least it could be confirmed now
Comment 6 Artem S. Tashkinov 2010-06-11 12:26:23 UTC
Confirming as for KDE 4.5 beta 2 and Konverstation 1.3 (stable release).
Comment 7 Myriam Schweingruber 2013-04-14 09:07:16 UTC
Is this still valid for Konversation 1.4 or 1.5 RC1? At least I can't reproduce this with 1.5 RC1 on KDE 4.10.2
Comment 8 Dmitry Bigunyak 2013-05-29 13:12:33 UTC
It is still valid for KDE 4.10.2 and Konversation 1.4 :(
Comment 9 Eike Hein 2013-05-29 13:14:00 UTC
It's a kdelibs bug, not a Konversation bug ... and iirc we found some kind of workaround, but I forgot it again, but it was something around the order of setting the size and quitting once ...
Comment 10 Andrew Crouthamel 2018-09-24 02:07:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 11 Andrew Crouthamel 2018-10-27 04:01:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!