( cloned from the rest of Bug 18883#c13 ) Symptom: display looks like an old CRT display when operated at wrong horizontal frequency; each line is moved some millimetres right from the line above. Display is OK throughout the graphical boot process, but go wacky when GDM starts. There is no related error messages in Xorg log nor in system journal that i can see as related. Laptop: Thinkpad T60, with 1400x1050 screen GPU: ATI RV515/M54 [Mobility Radeon X1400] Driver: "ATI Radeon HD 4870 and earlier" GDM as well as other DM and several DE i tried worked OK at sta1 release, but first days in july it broke like above for all DM and the DE i tried - For a few weeks i have had to use the workaround to use vesa and 15bpp colour and only MATE (not Gnome nor Plasma worked) After many updates today (held back a week) I can use any of SDDM, LXDM or XDM to log into Plasma, Gnome or MATE. But not GDM.
The workaround is of course to use another DM, but it takes advanced user skills to understand and apply that from being at a blurred screen and i really think GDM is such a piece that should just work, therefore i set priority High, Major.
Whiteboard: (none) => WORKAROUNDPriority: Normal => High
CC: (none) => olav
Assigning to all packagers collectively, since there is no registered maintainer for this package.
Assignee: bugsquad => pkg-bugsCC: (none) => marja11
Still valid after updates mga6 today, close to release. If someone else experience this, it would be good to try a fresh install with only Gnome and GDM. I just dont have the time right now, and this is my wifes production machine that runs nice in other aspects so i will not fiddle with it... Anyhow it is easy to just use another DM.
Helpful hint if this happen; how to switch DM Ctrl-Alt-F2 to get a command prompt type "root", enter and enter root password then install another DM if you do not have one, i.e for SDDM: urpmi sddm then issue "drakdm" to change DM, let it restart session.
Hi, This is High priority bug for a good reason. Making Mageia even better than ever is best direction. In order to do right thing, this bug should be examined and fixed as soon as possible. Packagers, please make the status to Assigned when you are working on this. Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it. On October 1st 2020, we will drop priority to normal.
That machine is physically borked now.
Resolution: (none) => OLDStatus: NEW => RESOLVED