Bug 107844

Summary:	Restoring maximised amaroK from GNOME system tray gives bad window placement
Product:	[Applications] amarok	Reporter:	John Pye <john>
Component:	general	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	l.lunak
Priority:	NOR
Version:	1.2.4
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description John Pye 2005-06-21 14:40:53 UTC

Version:           1.2.4 (using KDE KDE 3.4.1)
Installed from:    Fedora RPMs
OS:                Linux

Hi there

I'm running FC3 with GNOME and Amarok 1.2.4, KDE 3.4.1-1.0.fc3.kde. This could quite possibly be a GNOME problem, so let me know if I need to report elsewhere.

When I hit the [X] icon in the top-right of my amarok window, amarok is minimised to the system tray. That's fine. 

But if the window was maximised full-screen when I did the minimise, then when I restore the window by single-clicking on the amaroK icon in the system tray, then the window comes back in the wrong place. It comes back /almost maximised/ -- it's got the correct top-left position and vertical height, but the width of the window is slightly larger than the screen, so the righthand side of the window hangs off the screen a little bit. About 8 pixels perhaps, roughtly. Also, one other thing, if the window is maximised when I close it, it has the icon with the 'restore size' icon (two overlapping rectangles) when I close it; but when I restore it from the system tray, the restored window instead has a 'maximise' icon (indicating that it's forgotten that it was maximised at the time it was closed).

Anyway, don't know if it's a GNOME problem or an amarok problem. But it's one of those tiny niggly things that I thought I'd report coz other people have probably noticed it too.

Cheers
JP

some extra keywords: minimized maximized

Comment 1 John Pye 2005-06-21 14:42:23 UTC

I've just noticed that the same thing happens with amaroK so I'll add a report under GNOME as well. Sorry for the trouble.

JP

Comment 2 John Pye 2005-06-21 14:42:56 UTC

I've just noticed that the same thing happens with GAIM so I'll add a report under GNOME as well. Sorry for the trouble.

JP

Comment 3 Alexandre Oliveira 2005-06-22 00:14:24 UTC

Well, resolving the bug then. You could paste here a link for your GNOME bug report.

Comment 4 John Pye 2005-06-22 04:26:57 UTC

Here's a link to the bug on the GNOME bugzilla:

http://bugs.gnome.org/show_bug.cgi?id=308518

Comment 5 Lubos Lunak 2005-06-24 13:49:09 UTC

This is actually a duplicate of bug #59572.

Comment 6 John Pye 2005-06-24 16:38:04 UTC

Are you sure this is the same bug?
Certainly it looks like GNOME is doing something funny with 'forgeting the state of maximised windows' but is that the same as forgetting the state of always-on-top windows?

JP

Comment 7 John Pye 2005-06-25 08:06:26 UTC

I reported this bug over on the GNOME bugzilla under Metacity WM. Havoc Pennington replied as follows:

> The apps should probably be minimizing themselves rather than hiding/unmapping. 
> They could set skip_taskbar if the tray icon is enabled.

Comment 8 Lubos Lunak 2005-06-26 10:07:04 UTC


*** This bug has been marked as a duplicate of 59572 ***

Comment 9 Alex Peters 2006-02-18 14:12:59 UTC

Hello,

This still appears to be a problem with amaroK v1.3.1 using KDE v3.4.3 under GNOME v2.12.1.