| Summary: | KDE 4 taskbar is always on top of fullscreen applications | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Julien Gouesse <gouessej> |
| Component: | RPM Packages | Assignee: | John Balcaen <balcaen.john> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | gouessej, marja11 |
| Version: | 1 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | https://qa.mandriva.com/show_bug.cgi?id=45636 | ||
| Whiteboard: | |||
| Source RPM: | kdebase4-workspace | CVE: | |
| Status comment: | |||
|
Description
Julien Gouesse
2011-06-20 00:19:10 CEST
Ahmad Samir
2011-06-20 00:57:00 CEST
Assignee:
bugsquad =>
balcaen.john In fact there's 2 bugs here : 1) the problem with full screen for java apps 2) the strange behaviour when exiting for warmux. Could you report them upstream (with the empathy bug as an example if it's possible ) and report the url here so we can eventually backport them on mageia 1? Do you mean I should write 2 separate bug reports? The difference with the Mandriva bug that I quote is that this one had been fixed only for native applications. Maybe i'm misread but if i'm not wrong you find 2 bugs on mageia : 1) for full screen for java apps 2) for native application going full screen Regarding the mandriva bug report it seems to have been fixed by upstream (compiz) and not by mandriva. The 2 bugs seems different for me : 1) in one case the panel is always visible when running a java app in full screen -> maybe kwin does not respect/understand the full screen required by the java app & it should be report upstream to get them fixed (with the empathy bug you talked about because there's probably something useful for kwin's dev) A possible workaround here is to set the panel to use the autohide feature or to allow it to be recover by others windows) 2) for the second bug you're talking about some strange behaviour with some native applications when they're exiting after a full screen. It could be related to a driver problem, the use eventually of desktop effect etc etc, but it's not related (from my point of view at least) to java strange behaviour. If you're using desktop effect maybe you can use the option to disable them for apps going full screen. I have disabled desktop effects since the installation. Ok I will write another bug report in KDE bug tracker and another one in NVidia bug tracker except that if the bad exiting behavior is specific to a library used in Warmux (SDL?). Could you add me in cc in the kde bug so i can follow it? Regarding warmux could you eventually reproduce this strange behavior in gnome/XFCE ? I have installed GNOME only to test these things and these 2 bugs are not reproducible with this window manager. Warmux' bug comes from SDL: https://bugs.kde.org/show_bug.cgi?id=170488 Fullscreen bug with Java: https://bugs.kde.org/show_bug.cgi?id=276159 Just adding some info on the bug. #170488 from kde as been closed as Invalid, #276159 is still in discussion (which is quite instructive btw). Keywords:
(none) =>
UPSTREAM (In reply to comment #9) > Just adding some info on the bug. > #170488 from kde as been closed as Invalid, #276159 is still in discussion > (which is quite instructive btw). Nothing happened there since june 29th CC:
(none) =>
marja11 Hi I tried to port the required fix from NEWT (native windowing system of JOGL 2.0 which is a Java binding of the OpenGL API) to AWT (abstract window toolkit, most basic windowing standard toolkit of Java, included in all JREs and SDKs). Unfortunately, I failed. I decided to switch to NEWT. Maybe an Oracle engineer will fix it later. Best regards. Is this bug still valid? Yes, it is still valid. I haven't been able to spend much time on fixing this bug in AWT. The bug is still reproducible. I switched to NEWT in my own first person shooter and it works like a charm. The AWT version of my game is still concerned by this bug. Hi There is a workaround for Warmux and all those applications that mess with my task bar on exit. It doesn't happen when the screen frequency has not been modified during the switch to exclusive full screen mode. As for the AWT bug, it is still reproducible with OpenJDK 1.7 update 3. Best regards.
Julien Gouesse
2012-07-10 22:46:34 CEST
CC:
(none) =>
gouessej This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |