166499 2008-07-14 09:54:06 +0000 on launch/show restore the previous size and placement of the window (regression) 2008-10-29 00:21:43 +0000 1 1 2 Applications akregator general unspecified Compiled Sources Linux RESOLVED DUPLICATE 153590 NOR normal --- 0 bluedzins pim-bugs-null danarmak emmanuel.surleau marcus osterfeld 0 oldest_to_newest 624400 0 bluedzins 2008-07-14 09:54:06 +0000 Version: (using Devel) Installed from: Compiled sources on launch/show restore the previous size and placement of the window (regression) Steps: run akregator maximize window close it now click on systray icon --> window size and placement is not remembered In KDE3 it worked fine. Related report: https://bugs.kde.org/show_bug.cgi?id=153590 627404 1 risto 2008-07-21 08:16:37 +0000 Confirmed here, KDE 4.1rc1 on Kubuntu Akregator doesn't remember the maximized window size 627977 2 free.imr 2008-07-22 16:18:49 +0000 Tested in kde 4.0.98 akregator 1.2.50 mandriva rpms from last builds, and it works here. So it' has been probably fixed meanwhile, check in your distros against last packages. 628024 3 bluedzins 2008-07-22 17:53:31 +0000 Works on show, does not work on launch. 628471 4 risto 2008-07-23 19:27:20 +0000 Funny but now again it seems to work, I'm not sure if there was an update.. But it remembers the position both on start and restore. 628508 5 bluedzins 2008-07-23 20:37:36 +0000 Same as in #3. Does not work for start (KDE4Daily). 635719 6 cyril.bay 2008-08-09 00:00:31 +0000 Confirmed, with KDE 4.1.00 (Kubuntu final KDE 4.1 packages), Akregator 1.2.50. 644917 7 marcus 2008-09-09 10:00:13 +0000 Bug confirmed for Debian KDE 4.1.1 on show from systray, contrary to #3. 644919 8 marcus 2008-09-09 10:04:27 +0000 However I can make the bug go away by restarting akregator. After that it keeps the selected size. I have a dual-monitor setup, where I alternate between one and two monitors. 646039 9 emmanuel.surleau 2008-09-13 15:53:44 +0000 Confirmed on Debian 4.1.1. Size not restored when restarting akregator. 658295 10 osterfeld 2008-10-29 00:21:43 +0000 *** This bug has been marked as a duplicate of bug 153590 ***