Bug 135146 - Window automatically shades sporadically
Summary: Window automatically shades sporadically
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 148139 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-10-05 15:12 UTC by Clifton Craig
Modified: 2008-04-28 07:56 UTC (History)
4 users (show)

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 Clifton Craig 2006-10-05 15:12:45 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
Compiler:          JDK-1.4.x and above 
OS:                Linux

When a Java swing application opens a new window I experience random window shading or maximizing. The window will either shade or open in such a maximized state that the title bar falls off screen. When it goes into shade mode it remains locked. Any attempts to unshade result in automatic reshading. The only way out is to close the window or dialog with the shading problem. I see the behaviour most often in my Java IDE, IntelliJ Idea as I work with it most often. However I have had it occur in various other swing based apps. It's been a problem since KDE 3.4.x and is really a pain especially during development. I've never seen it happen prior to my upgrade to 3.4.x. which leads me to believe it is a bug in the Kwin code base. However I wish to file the bug with Sun as well. I originally saw the problem with JRE 1.4.2 and KDE 3.4.0. I have since upgraded both KDE and my JRE repeatedly and every version of KDE and JRE exposes the problem.
Comment 1 Philip Rodrigues 2006-10-05 22:49:17 UTC
Does the same problem occur with non-KDE window managers?
Comment 2 Clifton Craig 2006-10-06 03:04:06 UTC
No. I tried with XFCE on Mepis and also with Gnome on Ubuntu and never had the issue. However it happens rather frequently on KDE/Kubuntu
Comment 3 Andy Goossens 2006-10-11 11:28:00 UTC
I can confirm this bug. I have exactly the same problem using the IntelliJ Idea application. Eclipse on the other hand does not trigger this problem.

At this moment I'm using KDE 3.5.4 with JDK 1.5.0_08, CentOS 4.4. One of my colleagues at work does not see this problem, the only difference he's using KDE 3.3. I assume this bug was introduced somewhere between KDE 3.3 and 3.4.
Comment 4 Andy Goossens 2006-10-11 11:33:15 UTC
Reassigning this bug to kwin. Konqueror has nothing to do with this bug.
Comment 5 Anodos 2006-10-16 20:07:02 UTC
I can confirm this bug.  I am running Kubuntu 6.06 (KDE version 3.5.2, Qt 3.3.6) on a dual core AMD 64 X2 4400+ processor with the 2.6.15-27-k7 #1 SMP PREEMPT kernel.  Because of the randomness of this bug, I wonder if it is a race condition in the window manager?  Maybe this only happens on SMP or PREEMPT?  Gnome does not seem to have this problem at all.  I was running one of the Kubuntu betas for a while, and recently did an upgrade to the latest release in hopes of fixing this bug, but to no avail.  I should note I have this thing running on a dual display system off of a single nVidia card using nVidia's non open source drivers.  Kubuntu set up my displays, but they both share a single desktop, so it must be Xinerama.
In my case, the bug will sometimes maximize a window, but also sometimes shade the window.  When the window gets shaded, it will not accept any input and it becomes impossible to unshade the window.  Sometimes pressing ALT-F4 on the window will close it, and sometimes it won't (same thing with the "X" on the window).  When ALT-F4 doesn't work, the only way to close the window is to close the application.
Oh, java -version produces: Java HotSpot(TM) Server VM (build 1.5.0_08-b03, mixed mode)
This is Sun's JVM, of course.
Comment 6 Raman Gupta 2007-02-15 23:09:59 UTC
I can confirm this bug on Fedora Core 6 (KDE 3.5.6) on an Intel Xeon.

# uname -a
Linux hostname 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 i686 i386 GNU/Linux

# java -version
java version "1.5.0_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b03)
Java HotSpot(TM) Client VM (build 1.5.0_09-b03, mixed mode)

# rpm -qa | egrep "(xorg-x11-drv-nvidia|kdebase|xorg-x11-server-Xorg)"
xorg-x11-drv-nvidia-1.0.9746-7.lvn6
xorg-x11-server-Xorg-1.1.1-47.5.fc6
kdebase-3.5.6-0.1.fc6

Single-head display running nvidia closed source drivers.
Comment 7 Andy Goossens 2007-02-16 18:50:35 UTC
Bug is still present in KDE 3.5.6
Comment 8 Quiks 2007-02-28 10:04:07 UTC
I'm using Kubuntu 6.10 (Edgy) with KDE 3.5.5 and JDK 1.5.0_11.
I'm also having the same issue.
Comment 9 Lubos Lunak 2007-06-04 14:16:03 UTC
I suggest reporting this issue to Java developers if you haven't already. Java is quite known for being crappy when it comes to communication with window managers and it's very likely its fault (despite the fact that it shown only with KWin). Windows should change to shaded state only when the user or the application asks for it, so it's probably Java getting something wrong and mistakenly asks for shading. Besides, I've already tried to debug this and it was pain, debugging the problem from the Java side should be hopefully simpler.
Comment 10 Andreas Joseph Krogh 2007-06-04 14:27:51 UTC
I haven't seen this with JAVA-6.
Comment 11 Lubos Lunak 2007-08-02 14:11:26 UTC
*** Bug 148139 has been marked as a duplicate of this bug. ***
Comment 12 Lubos Lunak 2007-08-02 14:14:44 UTC
Based on comment #9 and input from the duplicate I'll close this as being a very very likely a Java bug.

The workaround, as mentioned in the duplicate, is to use KWin's window-specific settings: On the window, use Alt+F3/Advanced/Special window settings , enable 'Shaded', set it to 'Force' and leave the checkbox unchecked.
Comment 13 Anandram K R 2008-04-28 07:56:07 UTC
@Lubos Lunak

I am also getting the same problem occasionally in KDE version above 3.4. Also, I am able to reproduce this in both jdk 1.4 and jdk 1.5. Can you please let me know the Java bug ID for the same?