Bug 422618 - Special Application/Window Settings inconsistent behaviour (dual monitor set-up)
Summary: Special Application/Window Settings inconsistent behaviour (dual monitor set-up)
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kwin
Classification: Plasma
Component: rules (show other bugs)
Version: 5.18.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-08 09:11 UTC by Nick Elliott
Modified: 2023-09-06 10:38 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Elliott 2020-06-08 09:11:04 UTC
SUMMARY
Inconsistent behaviour when using special window or application settings, they work for some applications and not others.

e.g in Dolphin they appear to work 100% in all situations. Some applications, like LibreOffice, the settings are not applied as expected e.g. "apply initially" for which screen and whether the windows if maximised horizontally and vertically

STEPS TO REPRODUCE
1. Open LibreOffice Calc and go to Configure Special Window Settings...
2. Set the following
   - Maximised horizontally.....Apply Initially.....Yes
   - Maximised vertically.....Apply Initially.....Yes
   - Screen.....Apply Initially.....2
3. OK and close LibreOffice Calc

OBSERVED RESULT
When I start LibreOffice Calc it opens on screen 1 and NOT maximised either vertically or horizontally

EXPECTED RESULT
I would expect the special Window Settings to be applied on starting LibreOffice Calc so that the application loads on screen 2 with its windows maximised both vertically and horizontally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04 amd64
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
These settings worked in previous versions of Kubuntu. I am running a fresh install of Kubuntu 20.04.
Comment 1 David Edmundson 2023-09-06 10:38:54 UTC
This bug was reported against an outdated version of KWin. We have made many changes since the. 
If the issue persists in newer versions can you reopen the bug report updating the version number.