Any KDE4 application started in GNOME becomes full screen

[Peter Soetens]

Binary package hint: kde4libs

So all my KDE applications occupy the whole GNOME desktop (aka full screen mode).

This bug applies to any KDE4 application (and not to the GNOME applications).
It happened when I upgraded to KDE 4.1.4 (proposed) This bug was not present in KDE 4.1.3.

KDE4 applications aware of 'Full Screen' mode (like Konqueror) detect this and allow to leave the full
screen mode. Others remain stuck (like Kontact). When you close the application and start it again, it enters
full screen mode again.

[Andreas Wenning (andreas-wenning)]

Hi.

Thanks for taking your time to report the problem.

Can I please have you look, if the file ".kde/share/config/kwinrulesrc" exists in your home-directory. If it does, please attach it?

[Andreas Wenning (andreas-wenning)]

Oh, and while you are at it. Can you test if this happens with a new user? And maybe provide a screen shot just after starting eg. konqueror?

[Peter Soetens (peter-soetens)]

The bug doesn't happen with a new user. So it must be caused by the upgrade process itself.
While I'm at it, my icon theme was screwed (wrong icons at all places, very confusing) as well after the upgrade, but I could fix it by re-setting it in the configuration screen.

[Andreas Wenning (andreas-wenning)]

@Peter
Okay, it sounds like it could be some sort of configuration option, that gives a problem. Is it real fullscreen (eg. the border of the window is gone as well)? This behavior is done by the window manager which in the case of a gnome-session normally is either metacity or compiz.

[Peter Soetens (peter-soetens)]

yes it's a 'pure' full screen, no borders, and konqueror itself nicely detects that it's running in full screen mode.
I could try to turn compiz of for the bugged user account.

[Peter Soetens (peter-soetens)]

Ok, I found a work-around. As you suggested, I turned off compiz in Gnome (System->Preferences->Appearance->Visual Effects->None) and now everything works as normal again. When I turn compiz on again ('Normal effects'), the apps go in 'true' full screen again.

[Andreas Wenning (andreas-wenning)]

After some looking around, it seems that others have had similar problems with compiz + kde applications, where compiz always start them in fullscreen. (Both kde3, 4.1.x, 4.2 branch).

Try looking here:
http://ubuntuforums.org/showthread.php?p=6608130
does this fix your problem?

[Peter Soetens (peter-soetens)]

Yes. The proposed workaround on forum post on http://ubuntuforums.org/showthread.php?p=6608130 fixes my issue.

The correct workaround is to disable a workaround :-)

Uncheck the checkbox located at:

 System -> Preferences -> CompizConfig Settings Manager -> Utility -> Workarounds -> Legacy Fullscreen Support

Thanks for helping me nailing this one down !

[Andreas Wenning (andreas-wenning)]

Perfect. Thanks for the quick responses as well.

[stefaca (stefaca)]

my problem was with Krusader & Okular. Okular was a minor problem because CTRL+ALT+F exit fullscreen mod but it was anoing. Krusader was a bigger problem but whole problem was resolved by turning off deskop effects (not compiz user). little bit sad but a have panel and I can use them.

[Jeff Dag (jeff-dagenais)]

I am using gnome (ubuntu 10.10). Any KDE app I maximize and quit in this state, when re-launched starts fullscreen (like kdesvn or kgraphviewer). And for apps that have no "enter/leave fullscreen" its then impossible to break out of this.

The problem does go away when disabling the "Legacy Fullscreen Support" under the workarounds of compiz config settings manager. But I don't know yet if disabling this will screw up something else.

There is clearly a bug somewhere. I would guess KDE doesn't feed the correct hints to compiz to signal it wants to be maximized.

Perhaps the "Legacy fullscreen support" option should be made to be rules based instead of global.

[jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.