F5F Stay Refreshed Software Operating Systems The login screen graphics on lightdmLinux are experiencing a glitch.

The login screen graphics on lightdmLinux are experiencing a glitch.

The login screen graphics on lightdmLinux are experiencing a glitch.

N
NeeGrow
Junior Member
46
05-16-2023, 02:05 PM
#1
I began configuring Linux for dual boot earlier this week and made adjustments like modifying the login screen to avoid the default Dell boot menu that appears all blue. This gives it a more Windows-like feel with KDE, though I still encounter strange graphical issues when restarting or selecting boot options. Could anyone suggest possible reasons and solutions? Thanks in advance, Ultraforce.
N
NeeGrow
05-16-2023, 02:05 PM #1

I began configuring Linux for dual boot earlier this week and made adjustments like modifying the login screen to avoid the default Dell boot menu that appears all blue. This gives it a more Windows-like feel with KDE, though I still encounter strange graphical issues when restarting or selecting boot options. Could anyone suggest possible reasons and solutions? Thanks in advance, Ultraforce.

D
daisygirl876
Junior Member
9
05-16-2023, 03:54 PM
#2
Open "The Advanced options for POPOS" and choose recovery. If it clears the screen, note the installed graphics driver and kernel version, along with your hardware details.
D
daisygirl876
05-16-2023, 03:54 PM #2

Open "The Advanced options for POPOS" and choose recovery. If it clears the screen, note the installed graphics driver and kernel version, along with your hardware details.

D
dylosama
Member
150
05-16-2023, 04:27 PM
#3
After choosing recovery, I also updated the grub and repair files. It worked smoothly once I restarted, but switching to Windows and then back again didn’t resolve the problem. Based on the visual issues, it seems related to both my C: drive with Windows installed and having Pop!_OS boot drives on the same physical device. My kernel version is Linux 5.15.8-76051508-generic x86_64, and I’m using a NVIDIA driver version 470.86. My hardware details are: OS – Windows 10 / Pop!_OS 21.10 x86-64? What was originally installed? Windows 10. Is this an OEM version (pre-installed) or a full retail purchase? It was the OEM version, but I’ve refactored the C drive and possibly removed some original components. The system was built in March 2018. How old is the OS? Have you reinstalled it? Yes, the CPU is an Intel® Core™ i7-8700K at 3.70GHz, the graphics card is NVIDIA GeForce GTX 1070, and the motherboard is Dell Inc.0DF42J .98V69N2.CNPE10081400S4. The power supply details are unclear (laptop or not). I don’t know the exact manufacturer name. The Express Service Code is 20127130958; I’ll verify the precise model when switching back to Windows. Desktop monitors include Asus VZ27V and Lenovo LEN C32q-20, with the Asus using a display port and the Lenovo using HDMI.
D
dylosama
05-16-2023, 04:27 PM #3

After choosing recovery, I also updated the grub and repair files. It worked smoothly once I restarted, but switching to Windows and then back again didn’t resolve the problem. Based on the visual issues, it seems related to both my C: drive with Windows installed and having Pop!_OS boot drives on the same physical device. My kernel version is Linux 5.15.8-76051508-generic x86_64, and I’m using a NVIDIA driver version 470.86. My hardware details are: OS – Windows 10 / Pop!_OS 21.10 x86-64? What was originally installed? Windows 10. Is this an OEM version (pre-installed) or a full retail purchase? It was the OEM version, but I’ve refactored the C drive and possibly removed some original components. The system was built in March 2018. How old is the OS? Have you reinstalled it? Yes, the CPU is an Intel® Core™ i7-8700K at 3.70GHz, the graphics card is NVIDIA GeForce GTX 1070, and the motherboard is Dell Inc.0DF42J .98V69N2.CNPE10081400S4. The power supply details are unclear (laptop or not). I don’t know the exact manufacturer name. The Express Service Code is 20127130958; I’ll verify the precise model when switching back to Windows. Desktop monitors include Asus VZ27V and Lenovo LEN C32q-20, with the Asus using a display port and the Lenovo using HDMI.

Y
Yoyet
Junior Member
31
06-02-2023, 05:07 AM
#4
I encounter a comparable problem sometimes on Arch Linux with my 750TI, though it mainly occurs when I switch back from Windows to Linux after rebooting. During the brief X server startup phase, remnants of my previous Windows session appear on the screen—likely because NVidia doesn’t fully clear video memory at reboot. This was unsettling initially; upon launching Linux, the login screen displayed a warped image of the Terminator. It’s been this way for roughly four years now. I suspect others might face the same issue since your system seems to retain Windows UI elements from the last session. If you see clear images during a fresh boot (from full shutdown to full power), it probably means something was left in video RAM. When a clean reboot occurs, it should read properly. If not, it may point to issues with how Linux handles video memory until it’s mounted correctly. There’s no standard method to erase video memory or reset it completely except by writing a custom program that fills the RAM with zeros.
Y
Yoyet
06-02-2023, 05:07 AM #4

I encounter a comparable problem sometimes on Arch Linux with my 750TI, though it mainly occurs when I switch back from Windows to Linux after rebooting. During the brief X server startup phase, remnants of my previous Windows session appear on the screen—likely because NVidia doesn’t fully clear video memory at reboot. This was unsettling initially; upon launching Linux, the login screen displayed a warped image of the Terminator. It’s been this way for roughly four years now. I suspect others might face the same issue since your system seems to retain Windows UI elements from the last session. If you see clear images during a fresh boot (from full shutdown to full power), it probably means something was left in video RAM. When a clean reboot occurs, it should read properly. If not, it may point to issues with how Linux handles video memory until it’s mounted correctly. There’s no standard method to erase video memory or reset it completely except by writing a custom program that fills the RAM with zeros.

K
kalleboii
Senior Member
738
06-09-2023, 12:43 AM
#5
It doesn’t seem like a major issue based on what you’ve experienced. The graphical problem appears to happen only after switching between boot states, not during regular use.
K
kalleboii
06-09-2023, 12:43 AM #5

It doesn’t seem like a major issue based on what you’ve experienced. The graphical problem appears to happen only after switching between boot states, not during regular use.