Bug 180524 - Fullscreen windows cant be resized. No window borders.
Summary: Fullscreen windows cant be resized. No window borders.
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-01-13 05:13 UTC by Chad Carew
Modified: 2018-10-21 04:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot you requested (77.31 KB, image/jpeg)
2009-01-24 14:07 UTC, Chad Carew
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chad Carew 2009-01-13 05:13:13 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Certain windows (so far ive noticed Kpatience and Kmahjongg) when maximized, and then closed, when the program is run again they start in full screen. There is no window border and it cannot be resized. Using Kwin and Kde windows decorator.
Comment 1 Martin Flöser 2009-01-13 11:35:49 UTC
Kmahjongg does not have a fullscreen mode, so I assume they are shown maximized without window decoration (which is strange). You should be able to use alt+f3 to open the window menu and to restore the window, so that it can be resized again.

Are you sure that you are using KWin and not Compioz? I'm asking because kde-window-decorator is part of Compiz.
Comment 2 Chad Carew 2009-01-13 21:00:35 UTC
Okay then Im not using kde-window-decorator. I couldnt find where to change the window decorator to be sure, but in system settings I go to General->Default Applications->Window Manager and Kwin is selected, NOT compiz. So I am confident that it is Kwin. Sorry for the bad info. The odd thing is I can maximize the window the first time and its fine, shows the window borders. Its only if you then close it and then restart the program such that it starts in full screen, there are no borders. Alt+f3 doesn't seem to do anything. Right clicking on it in the taskbar and selecting "resize" does not do anything. Right clicking in the taskbar and de-selecting "maximize" does not do anything. The only fix I have come up with is to open kmahjonggrc in ~/.kde4/share/config and delete any entries relating to screen size, then restarting kmahjongg (or Kpatience or whatever).
Comment 3 Martin Flöser 2009-01-15 11:30:41 UTC
I still have problems understanding this bug and I cannot reproduce.

First of all does the application open in fullscreen or maximized? It is a difference. You are talking of fullscreen but in that case there should not be a panel visible and if panel is visible you should still be able to exit fullscreen mode via right clicking the taskbar entry.

And I do not understand why alt+f3 does not work, but I have an idea. Could you please try to temporarily disable compositing via alt+shift+f12 and then try alt+f3 again?

And please post the relevant section from kmahjonggrc so that we can see the exact settings.
Comment 4 Paul Broadbent 2009-01-16 16:25:05 UTC
I'm suffering from a similar problem that I think is likely to be caused by the same bug. Although for me it is happening will all KDE apps (well, all those that I've tried: okular, kmail, dolphin and konsole). (Amarok is fine, but I think that is different anyway).

I am running the recently released KDE 4.2 release candidate on Ubunutu. I had no issues until I upgraded to 4.2 (before then I didn't even have KDE fully installed, just a couple of KDE 4.0 apps). Everything seems fine when running KDE, but when running gnome (with compiz window manager) I'm getting this issue.

The problem is that the KDE apps have a habit of opening fullscreen with no window borders, making them impossible to resize. They also don't Unmaximize when I select the option from their right-click menu in the taskbar. They are totally filling the screen, overlapping the bars at the top and bottom of the screen.

To reproduce simply maximize any KDE app (in gnome or KDE), close it and then start it in gnome. When the app is originally maximized it maximizes fine, the problems only occur the next time it starts in gnome.

I've discovered two ways to temporarily get round it:
1) Open the app in KDE, then it looks fine and I can unmaximize it with no problems.
2) Edit the app's rc file. (I've only tried this this konsole and kmail). Find the "[Main Window]" section and delete either the Height line, or the Width line. For me, in their broken state the settings look like this:

[Main Window]
Height 1050=1051
State=AAAA/wAAAAD9AAAAAAAABpAAAAN6AAAABAAAAAQAAAAIAAAACPwAAAACAAAAAgAAAAAAAAACAAAAAQAAABYAbQBhAGkAbgBUAG8AbwBsAEIAYQByAQAAAAAAAAaQAAAAAAAAAAA=
Width 1680=1681

Deleting either the Height or Width line will cause the app to open windowed, and can then be safely maximised (you just need to remember to unminimize it before you close it, or it will be stuck fullscreen again next time it is opened).

Alt+F3 does nothing. But perhaps it isn't supposed to, as I'm running gnome.

I'm using a wide screen monitor, at 1680x1050.
Comment 5 Chad Carew 2009-01-24 08:33:45 UTC
I suppose I should have said I maximize the window. I too am using a wide screen monitor at 1680*1050. 

To reproduce: Open Kmahjongg, or Kpatience, or Okular, or Gwenview (there may even be others i have not tried yet). Maximize the window. Close the window. Again open the program. It now is displayed with no window borders. The only way to fix the problem is to either edit or delete the corresponding ~/.kde4/share/config/(corresponding config rc file). 

For example my gwenviewrc file is now:
Height 1050=1005
State=AAAA/wAAAAD9AAAAAAAABcwAAAOlAAAABAAAAAQAAAAIAAAACPwAAAABAAAAAgAAAAEAAAAWAG0AYQBpAG4AVABvAG8AbABCAGEAcgEAAAAAAAAFzAAAAAAAAAAA
Width 1680=1484

[General]


SideBarIsVisible=false

[MainWindow]
Height 1050=1051
State=AAAA/wAAAAD9AAAAAAAABpAAAAPSAAAABAAAAAQAAAAIAAAACPwAAAABAAAAAgAAAAEAAAAWAG0AYQBpAG4AVABvAG8AbABCAGEAcgEAAAAAAAAGkAAAAAAAAAAA
Width 1680=1681

Deleting any info related to window size, and restarting the program, fixes the problem until I once again maximize it.
Comment 6 Martin Flöser 2009-01-24 09:49:56 UTC
could you please provide us a screenshot. If possible containing the menu when right clicking on the taskbar menu entry?

Are you perhaps able to use alt+left mouse button or right mouse button to move or resize the window?
Comment 7 Chad Carew 2009-01-24 14:07:25 UTC
Created attachment 30560 [details]
Screenshot you requested
Comment 8 Martin Flöser 2009-01-24 17:31:16 UTC
According to the screenshot you are able to move and resize the window. So the window is neither maximized nor in full screen mode.

Screenshot also looks like KDE 4.1. Please try again after upgrading to 4.2 ;-)
Comment 9 Chad Carew 2009-01-25 02:06:23 UTC
Maybe something has changed in 4.2 *very* recently that i dont know about but as per the info i filled out to created this bug report, i am using mandriva cooker repos. About KDE: K Desktop Environment
Version 4.1.96 (KDE 4.1.96 ***(KDE 4.2 RC1))***
Comment 10 FiNeX 2010-10-10 18:27:20 UTC
Hi Chad, I've not correctly understood the problem, anyway I've done some tests and I'm not able to reproduce the bug. Are you still experiencing this issue using a more recent KDE version? 

Moreover which style were you using?
Comment 11 Thomas Lübking 2010-10-10 20:09:50 UTC
"Alt+F3 does nothing"
a) your not using kwin, or
b) kwin crashed (do other windows have decorations) or
c) you explicitly changed the default shortcuts

can you at least toggle "no border" in the advanced submenu of the taskbar rmb menu?
Comment 12 Andrew Crouthamel 2018-09-20 22:04:52 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 set the bug status 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 13 Andrew Crouthamel 2018-10-21 04:38:39 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!