Hi, I have setup a new fresh fedora 43 VM on Hyper-V, everything went OK and I was able to access it using ssh.
As I I need from time to time to access it using RDP, I added XFCE environment as follows
sudo dnf install @xfce-desktop-environment
sudo systemctl set-default graphical.target
I reboot, it never displays the logging UI and gets stuck somewhere but still I can access it with ssh
Hi.
You should look at the logs of lightdm (/var/log/lightdm/*.log) and in the system
journal to troubleshoot that.
That said, I suggest to not use the graphical.target and thus stay in
multi-user.target and use only RDP for a graphical session:
Thanks Francis, yes it is my intenetion to access the server using ssh but from time to time I need to access the server with the GUI. I will check the logs for lightdm
You said that RDP works. Why not using only RDP to have a GUI?
@francismontagnac I would like to understand why it is getting stuck and does not show the logon Screen.
When you enable that graphical.target, doesnât that service âtake overâ TTY1 by default. Maybe you could work around the problem by changing the systemd service to launch on TTY2 by default?
Notice the Conflicts=getty@tty1.service:[1]
# systemctl cat display-manager.service
# /usr/lib/systemd/system/lxdm.service
[Unit]
Description=LXDM (Lightweight X11 Display Manager)
#Documentation=man:lxdm(8)
Conflicts=getty@tty1.service
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service livesys-late.service
#Conflicts=plymouth-quit.service
[Service]
ExecStart=/usr/sbin/lxdm
Restart=always
IgnoreSIGPIPE=no
#BusName=org.freedesktop.lxdm
[Install]
Alias=display-manager.service
That probably prevents the getty@tty1.service from starting when graphical.target is enabled.
Iâm showing LXDM, because that is what I have available on an existing system, but I assume XFCE has something similar. âŠď¸
lightdm is used in this case, and has also: Conflicts=getty@tty1.service
(and Conflicts=plymouth-quit.service) and works for years on bare machines.
This is not even a black screen, looks like lightdm is unable to start Xorg. The
logs should show that.
Again: I think itâs not worth to try to fix that:
@FrancisFrancis, hee is the lo for lightdm when I try to retstat it
Apr 23 12:00:23 pemaster systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 12:00:23 pemaster systemd[1]: lightdm.service: Failed with result âexit-codeâ.
Apr 23 12:00:23 pemaster systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Apr 23 12:00:23 pemaster systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 4.
Apr 23 12:00:23 pemaster systemd[1]: Starting lightdm.service - Light Display ManagerâŚ
Apr 23 12:00:23 pemaster systemd[1]: Started lightdm.service - Light Display Manager.
Apr 23 12:00:23 pemaster lightdm[44564]: Error updating user /org/freedesktop/Accounts/User1000: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such>
Apr 23 12:00:23 pemaster lightdm[44564]: Error updating user /org/freedesktop/Accounts/User1001: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such>
Apr 23 12:00:24 pemaster systemd-coredump[44579]: [đĄ] Process 44574 (Xorg) of user 0 dumped core.Module /usr/libexec/Xorg from rpm xorg-x11-server-21.1.21-1.fc43.x86_64 Module libexpat.so.1 from rpm expat-2.7.3-1.fc43.x86_64 Module libgbm.so.1 from rpm mesa-25.3.6-3.fc43.x86_64 Module modesetting_drv.so from rpm xorg-x11-server-21.1.21-1.fc43.x86_64 Module libxcb.so.1 from rpm libxcb-1.17.0-6.fc43.x86_64 Module libGLdispatch.so.0 from rpm libglvnd-1.7.0-8.fc43.x86_64 Module libXext.so.6 from rpm libXext-1.3.6-4.fc43.x86_64 Module libX11.so.6 from rpm libX11-1.8.13-1.fc43.x86_64 Module libGLX.so.0 from rpm libglvnd-1.7.0-8.fc43.x86_64 Module libGL.so.1 from rpm libglvnd-1.7.0-8.fc43.x86_64 Module libglx.so from rpm xorg-x11-server-21.1.21-1.fc43.x86_64 Module libbrotlicommon.so.1 from rpm brotli-1.2.0-1.fc43.x86_64 Module libgraphite2.so.3 from rpm graphite2-1.3.14-19.fc43.x86_64 Module libglib-2.0.so.0 from rpm glib2-2.86.5-1.fc43.x86_64 Module libbrotlidec.so.1 from rpm brotli-1.2.0-1.fc43.x86_64 Module libharfbuzz.so.0 from rpm harfbuzz-11.5.1-2.fc43.x86_64 Module libpng16.so.16 from rpm libpng-1.6.56-1.fc43.x86_64 Module libbz2.so.1 from rpm bzip2-1.0.8-21.fc43.x86_64 Module libcap-ng.so.0 from rpm libcap-ng-0.9.3-1.fc43.x86_64 Module libpcre2-8.so.0 from rpm pcre2-10.47-1.fc43.x86_64 Module libcap.so.2 from rpm libcap-2.76-4.fc43.x86_64 Module libfreetype.so.6 from rpm freetype-2.13.3-3.fc43.x86_64 Module libfontenc.so.1 from rpm libfontenc-1.1.8-4.fc43.x86_64 Module libz.so.1 from rpm zlib-ng-2.3.3-2.fc43.x86_64 Module libxcvt.so.0 from rpm libxcvt-0.1.2-10.fc43.x86_64 Module libdrm.so.2 from rpm libdrm-2.4.131-1.fc43.x86_64 Module libudev.so.1 from rpm systemd-258.7-1.fc43.x86_64 Module libdbus-1.so.3 from rpm dbus-1.16.0-4.fc43.x86_64 Module libunwind.so.8 from rpm libunwind-1.8.1-3.fc43.x86_64 Module libaudit.so.1 from rpm audit-4.1.4-1.fc43.x86_64 Module libselinux.so.1 from rpm libselinux-3.9-5.fc43.x86_64 Module libsystemd.so.0 from rpm systemd-258.7-1.fc43.x86_64 Module libxshmfence.so.1 from rpm libxshmfence-1.3.2-7.fc43.x86_64 Module libXfont2.so.2 from rpm libXfont2-2.0.7-3.fc43.x86_64 Module libXdmcp.so.6 from rpm libXdmcp-1.1.5-4.fc43.x86_64 Module libXau.so.6 from rpm libXau-1.0.12-3.fc43.x86_64 Module libcrypto.so.3 from rpm openssl-3.5.4-2.fc43.x86_64 Module libpciaccess.so.0 from rpm libpciaccess-0.16-16.fc43.x86_64 Module libpixman-1.so.0 from rpm pixman-0.46.2-2.fc43.x86_64 Stack trace of thread 44574: #0 0x00007fde0b2863cc __pthread_kill_implementation (libc.so.6 + 0x743cc) #1 0x00007fde0b22c15e raise (libc.so.6 + 0x1a15e) #2 0x00007fde0b2136d0 abort (libc.so.6 + 0x16d0) #3 0x00000000005344be OsAbort (/usr/libexec/Xorg + 0x1344be) #4 0x0000000000540500 FatalError (/usr/libexec/Xorg + 0x140500) #5 0x000000000055a572 InitOutput (/usr/libexec/Xorg + 0x15a572) #6 0x0000000000411c77 main (/usr/libexec/Xorg + 0x11c77) #7 0x00007fde0b2155b5 __libc_start_call_main (libc.so.6 + 0x35b5) #8 0x00007fde0b215668 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3668) #9 0x00000000004130c5 _start (/usr/libexec/Xorg + 0x130c5) ELF object binary architecture: AMD x86-64Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Failed with result âexit-codeâ.
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 5.
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Start request repeated too quickly.
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Failed with result âexit-codeâ.
Apr 23 12:00:24 pemaster systemd[1]: Failed to start lightdm.service - Light Display Manager.
Apr 23 12:00:24 pemaster systemd[1]: lightdm.service: Triggering OnFailure= dependencies.
lines 264-309/309 (END)
That isnât a lightdm issue, xorg has crashed, it looks like a graphics driver issue.
I have other F43 desktop VMs (not server setup as this one) and no issues as this one
You need to have getty@tty1 stopped when running a display manager on tty1. Otherwise you get access conflicts. Notice that getty@tty1 is enabled by default, and the other gettyâs are started on demand. Therefore you need the Conflicts line to stop getty@tty1.
In the xfce environment with lightdm, lightdm as well as the graphical session is run on tty1. This is different from gnome where the graphical session runs on tty2
Try installing base-x
sudo dnf group install base-x
$ dnf group info base-x
Updating and loading repositories:
Repositories loaded.
Id : base-x
Name : base-x
Description : Local X.org display server
Installed : yes
Order :
Langonly :
Uservisible : no
Repositories : @System
Mandatory packages : glx-utils
: mesa-dri-drivers
: mesa-vulkan-drivers
: plymouth-system-theme
: xorg-x11-drv-amdgpu
: xorg-x11-drv-ati
: xorg-x11-drv-evdev
: xorg-x11-drv-intel
: xorg-x11-drv-libinput
: xorg-x11-drv-nouveau
: xorg-x11-drv-openchrome
: xorg-x11-drv-qxl
: xorg-x11-drv-vmware
: xorg-x11-drv-wacom
: xorg-x11-server-Xorg
: xorg-x11-xauth
: xorg-x11-xinit
lightdm only has minimal xorg requires
$ rpm -qR lightdm |grep xorg
xorg-x11-server-Xorg
xorg-x11-xinit
Thanks @Villy, how ttyi can be stopped in conflicts? should I delete the conflict line in the service?
Maybe raise the vt number in /usr/share/lightdm/lightdm.conf.d/50-minimum-vt.conf
No. getty@tty1.service is not the problem: I use lightdm for years without having
to bother about that.
You will have a shell (a getty) on tty2 (or tty3 etc) if Hyper-V allows you to send Ctrl-Alt-F2
(F3âŚ) to the console.
As Leigh said, installing the base-x group may help.
/var/log/Xorg.0.log may also give some hint. What gives:
grep -E '\((EE|WW)' /var/log/Xorg.0.logPS: Please paste here as Preformatted text using the </> button: thatâs far easier to read.
Did you also change the LightDM service to start on another TTY? If not, that wonât work.
Iâm not sure how you get LightDM to run on a different TTY, but it looks like Leigh found the answer. If that still doesnât work, you might try adding TTYPath=/dev/tty2 in the [Service] section (or whatever TTY you want to move LightDM to).
That Conflicts= needs to be the same as whatever TTY you have your GUI running on.
Presumably, if you move the GUI to some other TTY, you will be able to get a console login prompt on the default TTY1 that HyperV connects to.
Trivia: The old X11 server used to run on TTY7 by default.
grep -E â((EE|WW)â /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 554.881] (WW) Warning, couldnât open module fbdev
[ 554.881] (EE) Failed to load module âfbdevâ (module does not exist, 0)
[ 554.883] (WW) Warning, couldnât open module vesa
[ 554.883] (EE) Failed to load module âvesaâ (module does not exist, 0)
[ 554.891] (WW) Falling back to old probe method for modesetting
[ 554.919] (EE) Screen 0 deleted because of no matching config section.
[ 554.920] (EE)
[ 554.920] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 554.920] (EE)
[ 554.920] (EE)
[ 554.920] (EE) Please also check the log file at â/var/log/Xorg.0.logâ for additional information.
[ 554.920] (EE)
[ 554.972] (EE) Server terminated with error (1). Closing log file.