Bug 381257 - KMail does not remember window size or position
Summary: KMail does not remember window size or position
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: UI (show other bugs)
Version: 5.4.3
Platform: Kubuntu Linux
: NOR normal (vote)
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-16 01:48 UTC by Ivan Adzhubey
Modified: 2021-05-26 07:26 UTC (History)
2 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 Ivan Adzhubey 2017-06-16 01:48:19 UTC
KMail2 support for KWin Window Rules is completely broken. It does not respect any of the settings entered for its window via Window Special Settings (or Application Special Settings) dialogue, e.g. the ones on the Size & Position tab.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 17.04
Release:        17.04
Codename:       zesty

$ dpkg -l kmail
||/ Name                        Version            Architecture       Description
+++-===========================-==================-==================-===========================================================
ii  kmail                       4:16.12.3-0ubuntu1 amd64              full featured graphical email client
Comment 1 Ivan Adzhubey 2017-06-17 23:00:03 UTC
FYI: The bug is still here after the Plasma 5.10.2 / KDE 5.35.0 update.
Comment 2 Matthias Mueller 2020-11-15 09:38:06 UTC
I can confirm this, too - Manjaro testing with 5.15.3 currently
Comment 3 Ricardo J. Barberis 2021-05-26 01:13:14 UTC
In newer versions, kmail (and any other application) should remember its size and position automatically, no need for windows rules. At least that works for me.

Can some of you please confirm that it still happens with a recent version of Plasma and Kmail?
Comment 4 Matthias Mueller 2021-05-26 07:26:16 UTC
it's gotten much more rare for me that it doesn't remember the correct size and position, that much i can confirm. I'd say the instances where it is launched in the wrong place are mostly after crashes or forced reboots or the like, but i'm not 100% positive.