Bug 319977 - doesn't remember monitor after being closed
Summary: doesn't remember monitor after being closed
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.7.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: 2.8
Assignee: Amarok Developers
URL:
Keywords:
: 322347 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-18 12:28 UTC by jozi
Modified: 2014-05-11 14:54 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description jozi 2013-05-18 12:28:28 UTC 
on systems with two or more monitors amarok keeps opening on #1, even if it was closed on another one.

Reproducible: Always

Steps to Reproduce:
1. open amarok and move it to second monitor
2. end the program
3. start it again
Actual Results:  
amarok opens on monitor #1.

if it was in full screen mode, it reverts to the last size before. if it was in a specific size, it opens in that size.

Expected Results:  
amarok should have started exactly where it was closed before.
Comment 1 Ricardo Varas 2013-10-09 13:36:45 UTC 
I can confirm this bug happening in Linux as well under the same steps to reproduce.
Amarok Version 2.8-git
Using KDE 4.11.2
Comment 2 Dan Meltzer 2014-05-08 18:13:07 UTC 
*** Bug 322347 has been marked as a duplicate of this bug. ***
Comment 3 Dan Meltzer 2014-05-11 14:54:13 UTC 
Window placement is up to the window manager.  I can't think of any program that restores to exactly the same spot on a restart when you manually close it and reopen.  It restores fine on a session restore here for me, so I think this is invalid.