Summary: | Kmix OSD scrambeled and misplaced | ||
---|---|---|---|
Product: | [Applications] kmix | Reporter: | Uriel <jbytecoder> |
Component: | On-Screen-Display (OSD) | Assignee: | Christian Esken <esken> |
Status: | RESOLVED MOVED | ||
Severity: | normal | CC: | eMail, igor.poboiko, pavloh, vegittoss15, zanetu |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
snapshot of corrupted volume indicator appearing at the top-left corner
Patch with some extra debug output Debbuging output of Kmix Filtered Kmix debug output |
Description
Uriel
2010-02-20 23:42:11 UTC
Created attachment 43594 [details]
snapshot of corrupted volume indicator appearing at the top-left corner
snapshot of corrupted volume indicator appearing at the top-left corner
I can confirm this with KDE 4.4.2 on Kubuntu 9.10. And the same thing happens when I left-click network manager applet in the system tray. (Right-click is ok, though.) Reloading the window manager (eg through "Compiz Fusion Icon") may temporarily eliminate the issue, but it won't be long before the bug appears again. Reference: http://forum.kde.org/viewtopic.php?f=67&t=86026 Does the window manager you use differ from KDE default one (kwin)? (e.g do you use compiz/compiz-fusion/etc?) The question is to all who have this bug. *** Bug 262275 has been marked as a duplicate of this bug. *** This bug dose not appear with kwin window manager, using kwin manager everything is ok, this problem appears only using compiz-fusion, however i think it should work because there is another indicator that looks like the kmix one and it is to show the brightness, and this one is positioned correctly, while kmix goes to the corneer, if any info are needed i will try to supply them. thanks for interests :) Created attachment 59422 [details]
Patch with some extra debug output
It is strange because brightness OSD widget uses exactly the same code as KMix's OSD does :)
If you use Gentoo it may be possible for you to build KMix with that patch. It just adds some extra debug output. It would be great if you build it, enable KMix debug output in 'kdebugdialog', restart kmix and post here debug information it shows when it tries to show broken OSD. It should look like
---
kmix(30505) KMixWindow::showVolumeDisplay: OSD DEBUG (rect): QRect(0,0 1366x768)
kmix(30505) KMixWindow::showVolumeDisplay: OSD DEBUG (size): QRect(0,0 1366x768)
kmix(30505) KMixWindow::showVolumeDisplay: OSD DEBUG (pos): 517 614
---
(actually, I need only strings with "OSD DEBUG" substring)
Created attachment 59574 [details]
Debbuging output of Kmix
Full output just in case the whole context is needed
Created attachment 59576 [details]
Filtered Kmix debug output
I fltered out the OSD debugging info into this file, as you asked durring the debuging i changed the volume three times - once the OSD was placed correctly, secondly there was no OSD, finally the OSD was in the top left corner, its strange because the debug shows that the position of OSD is setup correctly, the problem might be somewhere else :/
I'm sorry I only thought that the brightness control works good, shortly after posting i saw that it also moves to the corner after first appearance
maybe it is a problem with compiz, but it dosen't really recognize the OSD as "real" window can't move it and so on. I also had a problem earlier with adding widgets to plasma, when I entered the "Add widget window" it appeared a little bit to low, and it got overlapped by task manager, and it did happen only under compiz, -> but now it works great the add Wigest window positoion id grea, so maybe something can be done to help this :)
maybe you will have another idea, what might be wrong , i'm happy to test stuff
*** Bug 229786 has been marked as a duplicate of this bug. *** Thanks. Well, that's pretty stange. But according to the Qt documentation (http://doc.trolltech.com/4.7/application-windows.html#x11-peculiarities) [...] Furthermore, a toolkit cannot simply place windows on the screen. All Qt can do is to send certain hints to the window manager. The window manager, a separate process, may either obey, ignore or misunderstand them. Due to the partially unclear Inter-Client Communication Conventions Manual (ICCCM), window placement is handled quite differently in existing window managers. [...] So it is definitely looks like Compiz behaviour (it's simple: we call setGeometry to the window with the position we need, and compiz doesn't place it there, and documentation says that it is possible). Moreover, it looks like we cannot anyhow solve it except showing this bug to compiz devs. PS google shows that it was placed somewhere around compiz forums (http://forum.compiz.org/viewtopic.php?f=86&t=13428&p=81955, more than 8 months ago, btw!), without an answer. Maybe someone should send a letter to their mailing list or write in IRC?.. I can confirm this bug (as it is still marked as unconfirmed) with current KDE 4.7.0 installed from default Arch Linux packages. For me both the volume and brightness sliders are mis-positioned in the top left corner of the screen. (In reply to comment #11) > I can confirm this bug (as it is still marked as unconfirmed) with current KDE > 4.7.0 installed from default Arch Linux packages. For me both the volume and > brightness sliders are mis-positioned in the top left corner of the screen. Hi Edgar, You may try voting for this bug to bring it to confirmed status sooner. (Did you notice the "Vote" link right above "Version Fixed In:" on this page?) When the votes exceed 70 (correct me if I were wrong), the bug will be automatically confirmed by popular vote. As for the bug itself, it still occurs on my kubuntu 10.10 64-bit with kde v4.6.2 and compiz v0.8.6. In my case, the volume and brightness osd's are both placed incorrectly, that is, in the top left corner after first use. Thanks for doing the analyzing. So we know now that the positions that KMix calculates are correct. It looks like Compiz doesn't comply to that, so please report this bug to Compiz. Greetings, Christian Someone who is affected by this Problem (and can answer questions and possibly test the Compiz changes) should report this to the Compiz developers. Moving this bug to "WAITING FOR INFO" until this is done and we receive feedback. No reply from bug reporter. Closing bug. Should be tracked in Compiz bug system. |