Description of problem: I use Mageia 8 with two monitors side by side, all 27" 1920*1080 screens, but I've constated some slight differences between how Plasma is shown when I connect to my main account or the secondary account. - on the main account I get, after the login screen, black screens background with white logo in the middle and a small white 'Plasma by KDE' logo in the right bottom coin. when desktop opens my two screens have each the background I've set but the left screen is overlaping on the right screen by about 20 pixels, and the right screen is overlaping on the left one by about 10 pixels. so when I open a software and put it on the right or left side of the screens I see a part of it displayed on the other screen :( - now if I connect to my secondary account I get, still after the identical login screen, an habitual blue screen with btw, a small white Mageia logo in the middle with a progress bar running at its bottom til it opens the desktop. there I have my two screens with each their backgrounds and ZERO overlaping... Question : Why the heck I get two different behaviors when I connect to one account or another, when the system and users uses the same screen system (KDE Plasma) from a new base installation made from scratch ??? I have made no special config of the screens, appart disabling the screenblanker. the two users share the same system and screen preferences (as I've copied the user2 kde prefs (those who are in the user directory) to the user 1 to see if that will change anything to my problem. there is no differences, same behaviors and the overlaping problem is still there. I'm puzzled as if I take a screenshot of the screens there is no overlaping visible in it... Version-Release number of selected component (if applicable): Plasmaa-desktop v5.20.4-4.mga8 How reproducible: no idea :( I've stumbled upon that problem by hazard and really don't see how to correct it or reproduce it... Steps to Reproduce: 1. 2. 3.
CC: (none) => jfbachelet
Do you use Wayland?
CC: (none) => lovaren
wayland ? nope. is it installed and activated by default ? I don't think so. what could activate it whitout my knowlege ?
the only thing I had to do for my two monitors' works with mageia8 as it was under mageia7.1 was to modify a little the grub config like it is said there : https://bugs.mageia.org/show_bug.cgi?id=28817#c14 but there is no wayland terms used in there...
Thank you for this curious report. This new bug re the overlap between the two screens is is a leftover from: https://bugs.mageia.org/show_bug.cgi?id=28817#c15 for which https://bugs.mageia.org/show_bug.cgi?id=28817#c11 gives the graphics details; and https://bugs.mageia.org/show_bug.cgi?id=28817#c14 the explanation and a fix. The problem of different behaviour between the first and second users is new. Can you please post the O/P of: $ inxi -S -Gxx to confirm that the fix above does leave you using 'radeon' and not 'amdgu'. And also a trimmed output (to show just the essential) of the equivalent lines of 'xrandr --verbose' as shown below from my own system, just for the actual resolutions used by each screen: $ xrandr --verbose Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192 HDMI-0 disconnected primary (normal left inverted right x axis y axis) ... VGA-0 connected 1366x768+0+0 (0x54) normal (normal left inverted right x axis y axis) 410mm x 230mm ... 1366x768 (0x54) 85.500MHz +HSync +VSync *current +preferred h: width 1366 start 1436 end 1579 total 1792 skew 0 clock 47.71KHz v: height 768 start 771 end 774 total 798 clock 59.79Hz ... and the same for the second screen ... In case this helps. On my own system: $ inxi -Gxx Graphics: Device-1: AMD Wrestler [Radeon HD 7310] vendor: Acer Incorporated ALI driver: radeon v: kernel bus ID: 00:01.0 chip ID: 1002:9809 Display: x11 server: Mageia X.org 1.20.12 driver: ati,radeon,v4l resolution: 1366x768~60Hz s-dpi: 96 OpenGL: renderer: AMD PALM (DRM 2.50.0 / 5.10.52-desktop-1.mga8 LLVM 11.0.1) It is using 'radeon' automatically. (I think Wayland is irrelevant: you have to install a specfic pkg to have it, and choose it from the login desktop menu).
Summary: Question about KDE Plasma => Plasma two-screen behaviour differs between first & second usersCC: (none) => lewyssmith
(In reply to Lewis Smith from comment #4) > Thank you for this curious report. > > This new bug re the overlap between the two screens is is a leftover from: > https://bugs.mageia.org/show_bug.cgi?id=28817#c15 > for which https://bugs.mageia.org/show_bug.cgi?id=28817#c11 gives the > graphics details; and https://bugs.mageia.org/show_bug.cgi?id=28817#c14 the > explanation and a fix. > > The problem of different behaviour between the first and second users is new. > > Can you please post the O/P of: > $ inxi -S -Gxx > to confirm that the fix above does leave you using 'radeon' and not 'amdgu'. here it is : $ inxi -S -Gxx System: Host: localhost Kernel: 5.10.52-desktop-1.mga8 x86_64 bits: 64 compiler: gcc v: 10.3.0 Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: SDDM Distro: Mageia 8 mga8 Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102 Device-2: AMD Oland XT [Radeon HD 8670 / R5 340X OEM / R7 250/350/350X OEM] vendor: PC Partner Limited driver: radeon v: kernel bus ID: 02:00.0 chip ID: 1002:6610 Display: x11 server: Mageia X.org 1.20.12 compositor: kwin_x11 driver: ati,radeon,v4l resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: AMD OLAND (DRM 2.50.0 5.10.52-desktop-1.mga8 LLVM 11.0.1) v: 4.5 Mesa 21.1.5 direct render: Yes > > And also a trimmed output (to show just the essential) of the equivalent > lines of 'xrandr --verbose' as shown below from my own system, just for the > actual resolutions used by each screen: here it is : $ xrandr --verbose Screen 0: minimum 320 x 200, current 3839 x 1080, maximum 16384 x 16384 HDMI-0 connected primary 1920x1080+0+0 (0x55) normal (normal left inverted right x axis y axis) 598mm x 336mm (this is the left screen) Identifier: 0x51 Timestamp: 67130 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff000469c42701010101 16190103803c2278ea53a5a756529c26 115054afef808100814081809500b300 8bc0a9400101023a801871382d40582c 450056502100001e000000fd00324c1e 530f000a202020202020000000fc0056 433237390a20202020202020000000ff 0046354c4d52533036303432320a012b 02031df14a900403021f131211051423 0907078301000065030c001000023a80 1871382d40582c450056502100001e01 1d007251d01e206e2855005650210000 1e8c0ad08a20e02d10103e9600565021 000018011d8018711c1620582c250056 502100009e0000000000000000000000 0000000000000000000000000000008c TearFree: auto supported: off, on, auto output_csc: bypass supported: bypass, tvrgb, ycbcr601, ycbcr709 audio: auto supported: off, on, auto scaling mode: None supported: None, Full, Center, Full aspect dither: off supported: off, on underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, on, auto coherent: 1 range: (0, 1) link-status: Good supported: Good, Bad CONNECTOR_ID: 46 supported: 46 non-desktop: 0 range: (0, 1) 1920x1080 (0x55) 148.500MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz > and the same for the second screen VGA-0 connected 1920x1080+1919+0 (0x55) normal (normal left inverted right x axis y axis) 598mm x 336mm (this the right screen) Identifier: 0x53 Timestamp: 67130 Subpixel: no subpixels Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff004c2ddb0834363130 0c1601030e3c22782af831a4564f9d27 0f5054bfef80714f81c0810081809500 a9c0b3000101023a801871382d40582c 450056502100001e000000fd00384b1e 5111000a202020202020000000fc0053 3237423335300a2020202020000000ff 0048344d433330353436300a20200039 TearFree: auto supported: off, on, auto output_csc: bypass supported: bypass, tvrgb, ycbcr601, ycbcr709 scaling mode: None supported: None, Full, Center, Full aspect load detection: 1 range: (0, 1) link-status: Good supported: Good, Bad CONNECTOR_ID: 50 supported: 50 non-desktop: 0 range: (0, 1) 1920x1080 (0x55) 148.500MHz +HSync +VSync *current +preferred h: width 1920 start 2008 end 2052 total 2200 skew 0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz these results are for the main account, do you need the secondary account results too ? (can't get it now, I have a 3TB hardisk salvage running) > (I think Wayland is irrelevant: you have to install a specfic pkg to have > it, and choose it from the login desktop menu). think so too, I've only one gui system installed and it's plasma.
Thank you for the extra graphics info. > I've only one gui system installed and it's plasma Other possible things to test if you can: do you know whether either problem (slightly rotated screens; user differences) happens just with your installed Plasma? * So first, try if you can the Plasma Live ISO 'live', without installing it. I imagine you have to configure something for the two screens. If the rotated screen does not show, that suffices; if it does, please add a second user to see whether those differences show. * Second, it is a big thing to ask, but necessary since we cannot reproduce the problems ourselves: would you be willing to install another simple desktop to see whether it happens also there? I would suggest either LxQt (to keep to Qt), or LXDE: task-lxqt-minimal or task-lxde-minimal The bemole is that it is *not* recommended to uninstall a desktop, so you would then be well advised to keep it. But without noticing it unless you specifically choose it at login.
Status: NEW => NEEDINFO
hello ^^) je vais essayer, par contre j'ai remarqué un truc après la mises à jour de kernel récente : mes deux user ont maintenant le même écran noir avec les logos blancs et le 'plasma par kde' en bas à droite au boot. Mais, le recouvrement est toujours la pour mon user principal et toujours inexistant pour mon user secondaire... ensuite j'ai booté sur la seconde interface ultra legère proposée installée par défaut et là aussi j'ai un recouvrement partiel sur les écrans du user principal comme avec plasma... et pas sur le user secondaire... y a un truc que je comprends pas là.
oups ! sorry forgot to write in english, so : I will try this, btw, I've seen something since the last kernel updates, I now have the same black screens with white logos and 'plasma by kde' in the right lower coin on all my users at boot. btw II the problem is still there and my first user have still the overlaping screens, while the second user have still no overlap... newt, I've tried booting the ultra light gui interface that installed by default and constated the same screen overlaping for my first user and no overlap for my second user... there is something I don't understand there...
(In reply to Jean-François Bachelet from comment #8) > btw, I've seen something since the last kernel updates, I > now have the same black screens with white logos and 'plasma by kde' in the > right lower coin on all my users at boot This is a known Plasma problem which arises for obscure reasons (there is a bug about it after changing themes), and in my experience - once you get it, it stays! Luckily it is only visual, not functional. > btw II the problem is still there and my first user have still the > overlaping screens, while the second user have still no overlap... > [since last kernel update] > > new, I've tried booting the ultra light gui interface that installed by > default and constated the same screen overlaping for my first user and no > overlap for my second user... > there is something I don't understand there... Thank you for all your evidence & tests. I see no choice but to assign this to the hardware-oriented team.
Status: NEEDINFO => NEWCC: lewyssmith => (none)Assignee: bugsquad => kernel