Bug 157293 - Clicking the icon (of certain apps) in the systray brings up a default-size window
Summary: Clicking the icon (of certain apps) in the systray brings up a default-size w...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kdeui (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 161551 181160 184499 184719 187313 209197 209505 215092 216497 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-02-06 22:06 UTC by Mikko C.
Modified: 2010-08-31 04:28 UTC (History)
18 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikko C. 2008-02-06 22:06:27 UTC
Version:            (using Devel)
Installed from:    Compiled sources
Compiler:          Gcc-4.2.2 
OS:                Linux

Currently, I'm experiencing this with two KDE4 applications: Amarok and KTorrent.
So I don't think it's an app-related problem.
All the other apps (KDE3 mainly) work as expected.


How to Reproduce:
- Resize the window to a non-standard size (full screen for example).
- Make it go in the plasma systray, by closing it.
- Click the icon in the systray: the window size is now back to the default.


P.S:
Sorry if this bug was reported already, I couldn't find it.
Comment 1 Mikko C. 2008-04-07 20:36:50 UTC
Today this has been solved in Amarok 2: http://websvn.kde.org/?view=rev&sortby=date&revision=794074

So I'm guessing it's not a KDE bug like I thought.

Hopefully Joris will fix it in KTorrent too ;)
Comment 2 Joris Guisson 2008-04-08 10:15:13 UTC
How can this solve anything ? The fix in amarok is just another way of saving and restoring the window size and position (which really should be done by calling KMainWindow::setAutoSaveSettings).

The changes here do not even get called when the window is hidden or shown.

Comment 3 Mikko C. 2008-04-08 16:00:09 UTC
I'm absolutely no programmer so I don't know.
The only thing I know is that after *that* revision the bug is gone from Amarok :D

Joris, can you reproduce the bug? If so, and if it's not a KTorrent bug, will you report it?
Comment 4 Joris Guisson 2008-04-08 20:34:21 UTC
Indeed this is very strange, I guess we can try doing the same as amarok, to see if it helps.
Comment 5 Joris Guisson 2008-05-03 19:38:20 UTC
*** Bug 161551 has been marked as a duplicate of this bug. ***
Comment 6 Joris Guisson 2008-05-03 19:59:49 UTC
OK, I have now done the same as amarok and the problem is gone. So there is certainly something going wrong with KMainWindow::setAutoSaveSettings
Comment 7 Mikko C. 2008-05-04 10:07:40 UTC
uhm, for me, the problem is still present in rev803739.
Comment 8 Mikko C. 2008-05-04 10:31:03 UTC
never mind, restarting KTorrent was not enough, I had to restart kde: now it seems to be working correctly :)
Thanks
Comment 9 Mikko C. 2009-01-18 12:01:47 UTC
*** Bug 181160 has been marked as a duplicate of this bug. ***
Comment 10 Unknown 2009-02-02 06:00:36 UTC
The problem is still present in KTorrent-3.1.2 using KDE 4.2.00 in Ubuntu 8.10.

Thanks a lot...
Comment 11 Ruchir Brahmbhatt 2009-02-02 06:03:51 UTC
I cal also confirm on kde 4.2.0 in opensuse 11.1.
Comment 12 Eike Hein 2009-02-18 13:00:14 UTC
*** Bug 184499 has been marked as a duplicate of this bug. ***
Comment 13 Joris Guisson 2009-02-18 14:32:56 UTC
*** Bug 184719 has been marked as a duplicate of this bug. ***
Comment 14 Joris Guisson 2009-03-16 18:36:05 UTC
*** Bug 187313 has been marked as a duplicate of this bug. ***
Comment 15 Christoph Feck 2009-05-21 11:43:37 UTC
I cannot confirm in current trunk (r970844) for KTorrent. It remembers window size both from systray and between exits. Is there any remaining app which has this problem?
Comment 16 missive 2009-05-23 16:21:16 UTC
Amarok (as of r971770) still has this problem, but only sometimes.

That is, sometimes when I build it, the problem is there, but for other builds it is corrected. Right now, it's broken.
Comment 17 Mikko C. 2009-10-02 12:04:42 UTC
*** Bug 209197 has been marked as a duplicate of this bug. ***
Comment 18 Dan Dart 2009-10-02 12:10:59 UTC
It's back with Amarok 2.2 (NEON Ubuntu Jaunty repo).
Comment 19 Mikko C. 2009-10-05 13:46:10 UTC
*** Bug 209505 has been marked as a duplicate of this bug. ***
Comment 20 Dan Dart 2009-10-05 14:30:07 UTC
Amarok Neon now behaves properly even though I haven't upgraded it!
Comment 21 Yop69 2009-10-05 17:04:10 UTC
(In reply to comment #20)
> Amarok Neon now behaves properly even though I haven't upgraded it!

No Amarok Neon have the bug :(
The click on the systray button to show Amarok maximized not work. Amarok is nearly maximized but no maximized :(.

So the bug is still here
Comment 22 Mikko C. 2009-10-07 22:11:30 UTC
*** Bug 209806 has been marked as a duplicate of this bug. ***
Comment 23 Jaromir Smrcek 2009-11-11 00:12:37 UTC
The bug is there for kTorrent 3.2.3 (kde 4.3.1)
Comment 24 Myriam Schweingruber 2009-11-18 11:25:12 UTC
*** Bug 215092 has been marked as a duplicate of this bug. ***
Comment 25 Joris Guisson 2009-11-28 19:02:21 UTC
*** Bug 216497 has been marked as a duplicate of this bug. ***
Comment 26 Christoph Feck 2009-12-11 02:05:38 UTC
Let me understand this bug correctly. As I try on latest trunk, I see the following behavior (using KTorrent from trunk):

Procedure I: Hiding a normal (unmaximized) window

1 Start a program
 A-> The size is the last used size
2 Hide it using systray
3 Show it using systray
 B-> The size is same as in A

So far I see no error here.

Procedure II: Hiding a maximized window

1 Start a program
 A-> The size is the last used size
2 Maximize it
 B-> The size is maximized
3 Hide it using systray
4 Show it using systray
 C-> The size is maximized, same as in B
5 Unmaximize/restore
 D-> The size is restored, but different than in result A.

So what I see is only result D from procedure II is wrong. Correct? If any other result is different from what I see here, please state the exact bug.

From what I understand, this is a kwin/NETWM bug. You cannot open a window maximized, and also tell it what the non-maximized size is. You could open non-maximized to tell it the correct size, then immediately maximizing it, but this would result in flicker.

KWin maintainers: solution?
Comment 27 Attila Oláh 2009-12-11 14:20:15 UTC
To Christoph Feck:

If this is the current problem, then it is far not that frustrating than it was when this bug was reported. IIRC the original problem was that when a window was moved to systray (i.e. a maximized window), and it was shown again, it was not the same size and position as before minimizing to systray.
Comment 28 Christoph Feck 2010-08-31 04:28:22 UTC
The remaining issue from comment #26 is bug 214325. Closing this one, assuming the original reported issue is fixed.