Version: (using KDE KDE 3.1.1a) Installed from: Mandrake RPMs OS: Linux I have 2 screen (not xinerama) and kicker on my first screen can be place as it would be on my second screen (I can place kicker vertically at 1024 on my 1600x1200) and a other bug (always because the 2 kwin are confused each other) the bubble who appear for kopete in kicker is upsidedow on my second screen.
Created attachment 1687 [details] Here, the bubble placement error The frist attachement shows like the bublle appears
Created attachment 1688 [details] kicker placement Here, the kicker can be place like it would be on my second screen (at 1024 pixel of 1600)
I can confirm the kicker mis-placement; it applies to all panels. Can be duplicated by placing KasBar at the bottom of :0.1 and the Main Panel at bottom of :0.0. One or the other will be lifted off the bottom of the screen by the width of the other. (usualy the Main Panel is the one to be lifted.)
The buble problem is out... but the kicker placement is still yet (or is a feature ;-)
Is this bug still present in a recent KDE version, such as 3.5.9?
This is still valid in KDE 4. Using current Mandriva Cooker (development branch) KDE 4 packages, I experience the bug as described above. Using a laptop with an internal display at 1280x800 and an external monitor at 1680x1050, with the X.org Intel driver (so using RandR 1.2 - using the default monitor layout, which is clone), when I log in to KDE 4, the 'kicker' is rendered in the position and size appropriate for the 1280x800 display, not the 1680x1050 one. So on the external monitor, it floats about three quarters of the way up the desktop, anchored on the left hand side but not extending all the way across the desktop. Looks very silly. The background is also rendered incorrectly. It's as if KDE renders it twice, once at 1680x1050 and once at 1280x800, with the 1280x800 one on top of the 1680x1050 one. This should be trivial to reproduce - find a laptop with an Intel adapter, plug in an external monitor of a different resolution, and log in to KDE 4 with a clean profile.
@Adam: can you reproduce the bug with the new KDE 4.3 too?
Being the initial report on kicker (KDE3) and being kicker no more developed I'm closing this bug. @Adam: if you can reproduce something similar in KDE4. Please report it separately. Thanks