View Full Version : Problem with "lightdm"
Good Morning
I've installed kali linux on virtualbox and i've used it normally without problems.
Today i've launch a full-upgrade and after that upgrade and reboot the VM i cant get GUI anymore every time i open it shows CLI on tty1
i've tried to remove ligthdm and reinstall it , i've tried to install gdm3, i've tried many things but its the same problem
every time i check
systemctl status lightdm
it show failed with exit-code
can any one help me please
sorry for my bad English
best regards
Is this problem fixed ? going through same issue
I have the same issue after an upgrade. the new version of libglib2.0 seems to have broken a few things lightdm-gtk-greeter seat0-greeter.log
libpango-1.0.so.0: undefined symbol: g_memdup2 and I think this is also may also be related to an issue with xorg x-0.log MESA-LOADER: failed to open bochs-drm:. I have removed and re-installed lightdm which did not fix the issue.
HillSonMX
2022-06-15, 19:44
Good Morning
I've installed kali linux on virtualbox and i've used it normally without problems.
Today i've launch a full-upgrade and after that upgrade and reboot the VM i cant get GUI anymore every time i open it shows CLI on tty1
i've tried to remove ligthdm and reinstall it , i've tried to install gdm3, i've tried many things but its the same problem
every time i check
systemctl status lightdm
it show failed with exit-code
can any one help me please
sorry for my bad English
best regards
Hi guy !! I was in same issues and find the solution !! it is not about lightdm, is about xorg config, I did a post but still not autorized by admin so i will copy paste here.
uname -a
Linux kali 5.16
I just did normal update process with
sudo apt update && sudo apt upgrade -y && sudo apt dist-upgrade && sudo apt autoremove -y && sudo apt autoclean
now
uname -a
Linux kali 5.17
and can not start normally ( black screen just after kali logo ) but still I can go to TTY (ctl+alt+(F1..F3)
I check some log file, and you can see tell is something wrong with lightdm and tty process and finally Xorg log point me to a solution.
/home/<user>/.local/share/xorg/Xorg.0.log
4943494449454946
then cheking other forum find a solution could be forcing X to use fbdev driver and provinding the framebuffer device ID by:
Create the .conf file:
/etc/X11/xorg.conf.d/fbdev.conf
Edit it:
Section "Device"
Identifier "Card0"
Driver "fbdev"
BusID "PCI:0:8:0"
EndSection
Please mind that your BusID might be different.
You can check it with: (if exist)
cat /root/xorg.conf.new
or you can just run
Xorg -configure
which will create /root/xorg.conf.new. Then look in this file for your BusID and act accordingly if it differs
(some credit to this post (https://bbs.archlinux.org/viewtopic.php?pid=2005640#p2005640) !!)
HAPPY FIXING !!! :cool: