Bug 330775 - no window decoration on restart if previously closed when fullscreen
Summary: no window decoration on restart if previously closed when fullscreen
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.12.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-04 22:43 UTC by ggrocca
Modified: 2014-02-08 14:22 UTC (History)
3 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 ggrocca 2014-02-04 22:43:31 UTC
Konsole sometimes starts with a window that is as big as a fullscreen one would be, but that is not fullscreen nor normal. It has a window bar and title, but no decorations or borders. It is impossibile to resize it. The only way to get out of this unfunctional state is to press the "resize/maximize" button on the window bar.
This happens only after Konsole has been previously closed by sending ctrl-D when fullscreen.

Reproducible: Always

Steps to Reproduce:
1. go fullscreen.
2. close with a ctrl-D.
3. open konsole again.
Actual Results:  
big window that as bar but no borders (inconsistent state) and cannot be resized by normal means.

Expected Results:  
either:
1) open konsole fullscreen;
2) open a normal konsole window that is as big as the previous, NON-fullscreen normal konsole windows was;
3) open a normal konsole windows that is as big as the current desktop allows (maximazed state).

I think all three options could be considered valid. My preference is option 2) because it seems to me that fullscreen is a special state that should not be remembered across quits, and therefore the normal state of the window should be then remembered (and would be lost otherwise).

It seems to me that 3) would be the worst option, since it would go to a state that was never set by the user, I wouldn't see the point and would consider it a slight misfeature.
Comment 1 Christoph Feck 2014-02-04 23:47:48 UTC
Are you using KWin as the window manager?
Comment 2 ggrocca 2014-02-05 13:13:16 UTC
(In reply to comment #1)
> Are you using KWin as the window manager?

Yep, I'm using KWin!

If there is additional info you may need (configuration of Konsole or Kwin, tests I could run, etc) please ask without problem.
Comment 3 Thomas Lübking 2014-02-05 19:18:20 UTC
when konsole enters this state, please run "xwininfo" and "xprop" and click the window each time the cursor turns '+'
This will print some info on the window. Please attach that here.
Also please post the output of "kwin --version"

(If I do as suggested, i simply get a maximized konsole)
Comment 4 ggrocca 2014-02-08 12:09:41 UTC
Sorry for the late answer, I was away these last few days.

I've tried my other KDE installation at work (on kubuntu instead of arch, same versions - Konsole 2.12.1 and KWin 4.12.0) and I cannot reproduce the bug: when I try to move the window it unmaximizes before doing anything else.

Back at home today I realized that this is not a Konsole specific problem but a window manager one related to all maximized windows. When I maximize a window (on arch), trying to move it always give the results that the maximized window moves "as it is" and is left there with no borders and no resize handles. It obviously still has a bar and I can unmaximize it - the only doable thing at that point. KDE on Kubuntu unmaximizes the window on its own instead.

I'm closing the bug as INVALID and I'm not attaching the requested X info since the bug is obviously not Konsole related. I'm sorry that I didn't notice it at first,  but I almost never use maximize - for the few applications that need screen estate I usually configure fullscreen shortcuts.

I'd still like to hear a suggestion though. Do you think this is a bug, or there's something in my configuration causing this? Should I report a bug to KWin developers?

Thanks!
Comment 5 Thomas Lübking 2014-02-08 13:05:18 UTC
Preserving the maximization state is intended, borders on maxmized windows are decoration specific.

running "kcmshell4 kwinscreenedges" allows you to enable "maximize windows when dragged to upper screen border" what mimics the "aero snap" behavior and will unmaximize (and restore to the unmaximized size) when dragging away a maximized window from the upper screen edge.
Comment 6 ggrocca 2014-02-08 14:22:42 UTC
I see. Not a bug at all then... Thanks for the configuration tip