Description of problem: External HDMI screen displays freezed image if connected after boot. If HDMI is connecte before starting computer, external screen works as expected. Version-Release number of selected component (if applicable): Mageia 6 How reproducible: Connect an HDMI external screen when computer is already on with a logged in user. External screen only shows a freezed image of your desktop. No new opened window is displayed, mouse pointer does not move. Reboot the computer without disconnecting the screen and log on. The external screen is now usable. Mageia 5 was not affected.
Does it also happen when you switch to e.g. tty2 and attach the HDMI monitor, is the tty2 screen then frozen on the external monitor, too? If not: which DE and DM do you use?
Keywords: (none) => NEEDINFOSummary: External HDMI screen displays freezed image if connected after boot => External HDMI screen displays frozen image if connected after bootCC: (none) => marja11
Hello, Got this problem with on intel 520 kernel 4.14.18-desktop-1.mga6 Answering your question: - Disconnect screen - Move to tty2 - Connect screen At this point output is cloned and none of the screens is frozen. - Move to tty1 again - It retrieves last configuration, in my case only external monitor. I must add that cloned output never fails. Just extended configuration leaves a screen frozen it may be the built-in or the external. If I rotate between modes with meta+p at some point the extended configuration works but totally random. Note: Forcing modes with xrandr also leaves the screen frozen. I may try any other test you ask. Regards.
CC: (none) => tl16887
@ Asimov Thanks for your comment. Does it happen with any display manager and any desktop environment?
Installed task-xfce and checked. I really can't replicate the problem once in xfce. As soon as I change again to kde/plasma the freezing screen problem appears once again. At this point I'm pretty sure that plasma is the culprit.
Just a small detail. Although the screens don't freeze in XFCE the background does. I mean, the last window you close remains "printed" in the background and moving windows around leaves a trace (windows solitaire effect if you know what I mean.
Marja: It's the default configuration so Plasma 5 + SDDM. Asimov's solution fixes the problem. I have an HD Graphics 530 video card + GM108M [GeForce 940MX] (disabled, Bumblebee not installed).
Thanks, Aurgier. Assigning to KDE team. @ Asimov Do you mind filing a separate bug report for the other issue, the windows "trace" in Xfce?
Assignee: bugsquad => kdeKeywords: NEEDINFO => (none)
Hello, I'm affected by the same bug. For me, it happens only after a first suspend/wake up operation. Applications displayed on the HDMI display are still active, I can drag them on the built-in screen, they appear to be hidden behind a mask. I'm affected by this bug since some weeks ago, this was not the case at Mageia 6 installation. Also Intel graphics Plasma5 / SDDM
CC: (none) => yves.brungard_mageia
I wonder if this is related to kernel. Today, I'm in a situation where the HDMI monitor is not seen. If I plug/unplug the monitor, journalctl doesn't report any event. I find that suspicious.
Just been trying to get Plasma/SDDM Mageia-6.1 on HP Probook 450 to use external Advent 1024x768 monitor (connnected to HDMI port with monitor's DVI socket). But SystemSettings denies all knowledge of external monitor, and Fn+F4 on Probook says "No external display". MMC/Hardware shows "Intel HD Graphics 5500 VGA-compatible controller". [Different result if connect a Lenovo ThinkPad 11e to the HDMI end of the cable connected to the monitor's DVI socket: The ThinkPad's Desktop appeared on the external monitor, but the ThinkPad's screen cursor was then inoperable, so dead end.] Elsewhere I see success if using Xfce rather than Plasma, so points to Plasma bug. Will try again with Plasma with more recent monitor...
CC: (none) => maurice
Hi, thanks for reporting this bug. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:OLD
Resolution: (none) => OLDCC: (none) => ouaurelienStatus: NEW => RESOLVED