Bug 221762 - Kwin snap/split causes a second instance of the same program to open split
Summary: Kwin snap/split causes a second instance of the same program to open split
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdeui (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-08 09:00 UTC by Justin Newman
Modified: 2023-01-20 05:08 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Newman 2010-01-08 09:00:48 UTC
Version:           4.3.90 (using Devel)
Compiler:          gcc version 4.4.2 20091222 (Red Hat 4.4.2-20) 
OS:                Linux
Installed from:    Compiled sources

Steps to reproduce:

1. Open Dolphin
2. Snap to left edge
3. Open another instance of Dolphin

This works with any program.

Expected results: Second instance of dolphin opens at "normal" size.

Actual results: Second instance opens "split screen" size.

Other notes: The second instance doesn't unsnap either, it has to be resized manually or closed. After the first window is unsnapped new instances go back to opening the proper size.

This *may* be considered desired behaviour when opening a second instance and there is only one other, split, window open, but even then it should unsnap correctly. When there are multiple (more than one) windows open, it should definitely open normal size instead of split.

It seems to me to be a product of KWin remembering window sizes, which should probably be disabled for snapped windows.
Comment 1 lucas 2010-01-09 11:47:07 UTC
It's the application that's remembering the window size, not KWin.

Because of how quick tiling works I can't see a way to fix.
- There's no sane way of telling the application that it's quick tiled and we cannot add a way as it will only work for applications that support it.
- KWin cannot have the window open up normal size as KWin doesn't know what the normal size was.
- KWin cannot mark the window as being quick tiled initially as it still needs to know what the normal size was to restore the window to when the user untiles it.
Comment 2 Justin Newman 2010-01-09 12:05:50 UTC
Well, I don't know the implementation details obviously, but upon further inspection the problem seems to actually only be with KDE apps. Konsole, Dolphin, etc do it and Firefox, Picard, and company don't.

Which, yes, indicates that it's not KWin doing the remembering. Do most apps only save/remember their size when closed, while KDE apps always keep track of their current size? The fact that the behaviour seems consistent across all KDE apps indicates to me that this could be a KDE wide issue that could be fixed somewhere within, rather than having to be fixed in each app.

But, as usual, I'm just stabbing in the dark. Whatever the cause, I don't think it should be considered desired/proper behaviour. Maybe I can get a second opinion on this part?
Comment 3 Thomas Lübking 2012-03-16 23:48:02 UTC
KMainWindow could store it's size on close only - otherwise this is just the intended behavior (opens with last applied size, how it got there doesn't matter)

There's not much kwin could do (not even guess this was a quick tiled window and unsnap, because we don't know the former size since there was none) and possibly this is no bug at all, but the sheer lack of a brain interface.

You can workaround this by either
dolphin --geometry 800x400
or applying an initial size rule in 
"kcmshell4 kwinrules"
Comment 4 Andrew Crouthamel 2018-11-06 15:11:08 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-11-18 03:34:07 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Justin Zobel 2022-12-21 23:58:16 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 7 Bug Janitor Service 2023-01-05 05:24:54 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Bug Janitor Service 2023-01-20 05:08:16 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!