Black screen After Upgrade 42 to 43

eliassal · February 19, 2026, 5:25pm

Hi, I followed instructions to upgrade 42 to 43, everything went Ok, last step, I issued

dnf5 reboot upgrade

machine rebooted, an indication that upgrade will go on but after 5 to 10 seconds a I get a black screen. I followed some steps I found on thread

Black screens after logging in on newer kernels - Fedora Discussion

Booted and did Ctrl + Alt +F3

I was able to log using my user, rebooted, the screen displays

I choose 43 or 42 same thing happens, black screen.

Here is a screen shot when I did entered tty

How can I check what is wrong and not allowing right booting? Thanks in advance

In tty session, I issued the command

journalctl -b -1 --no-hostname --no-pager | fpaste

and the output is at

gnwiii · February 19, 2026, 6:27pm

Which instructions? Which hardware? Which desktop?

Note that reboot and upgrade are both commands and are normally used separately with appropriate options. You may be a victim of an AI hallucination. Before running unfamiliar commands, use the man pages and distro documentation to make sure you understand what they do, and ask here if the command isn’t found in trustworthy documentation.

theprogram · February 19, 2026, 6:40pm

For future reference, the instructions to upgrade are Upgrading Fedora

You might want to use a USB and repair your system from Anaconda installer.

eliassal · February 19, 2026, 6:56pm

@George, I followed instructions at fedora

sudo dnf upgrade –refresh
sudo dnf autremove
sudo dnf install dnf-plugin-system-upgrade
sudo dnf system-upgrade download --releasever=43
dnsf5 offline reboot

this process I used for 2 other VMs and everything went OK without any issue

eliassal · February 19, 2026, 6:59pm

I searched google but found nothing

theprogram · February 19, 2026, 7:22pm

That looks right.
In your first post you wrote a different command.

The ‘repair’ is not in the upgrade instructions.
It is something you can do if your system breaks. I don’t know how it works with a VM.

gnwiii · February 19, 2026, 9:13pm

Please be careful with typos — others may copy them. Given the number of errors in your posts, there is a chance that your issue was due to an inadvertent mistake entering a command. In courses I taught introducing Unix and the Linux, I found that using a buddy system with one user entering commands and the other reading the manuals and checking for typos was more efficient than having everyone working independently.

anothermindbomb · February 20, 2026, 12:27am

Somewhat bizarre collection of Grub options, but I presume there’s good reason for it.

Gnome-session is repeatedly dumping core in the journal paste and the entire machine is apparently running under Hyper-V, which I know nothing about - doubt it’s terribly important, it just stood out.

… However, these messages about mounts failing and Gnome crashing probably don’t help things in the display department.

Feb 19 18:18:12 /usr/libexec/gdm-wayland-session[1312]: dbus-daemon[1312]: [session uid=60578 pid=1312 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Feb 19 18:18:12 gnome-session-i[1341]: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Feb 19 18:18:12 gnome-session-i[1341]: Failed to check if unit gnome-session-wayland@gnome-login.target is active: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Feb 19 18:18:12 gnome-session-i[1341]: Failed to reset failed state of units: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Feb 19 18:18:12 gnome-session-i[1341]: Starting GNOME session target: gnome-session-wayland@gnome-login.target
Feb 19 18:18:12 gnome-session-i[1341]: Failed to start unit gnome-session-wayland@gnome-login.target: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.freedesktop.systemd1" does not exist
Feb 19 18:18:12 audit[1341]: ANOM_ABEND auid=4294967295 uid=60578 gid=42 ses=4294967295 subj=kernel pid=1341 comm="gnome-session-i" exe="/usr/libexec/gnome-session-init-worker" sig=5 res=1
Feb 19 18:18:12 kernel: show_signal: 9 callbacks suppressed
Feb 19 18:18:12 kernel: traps: gnome-session-i[1341] trap int3 ip:7fd3ac3a5fc3 sp:7ffdc0f1d4f0 error:0 in libglib-2.0.so.0.8600.4[4bfc3,7fd3ac35a000+a6000]
Feb 19 18:18:12 systemd-coredump[1350]: Process 1341 (gnome-session-i) of user 60578 terminated abnormally with signal 5/TRAP, processing...
Feb 19 18:18:12 systemd[1]: Created slice system-drkonqi\x2dcoredump\x2dprocessor.slice - Slice /system/drkonqi-coredump-processor.
Feb 19 18:18:12 systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump.
Feb 19 18:18:12 audit: BPF prog-id=69 op=LOAD
Feb 19 18:18:12 audit: BPF prog-id=70 op=LOAD
Feb 19 18:18:12 audit: BPF prog-id=71 op=LOAD
Feb 19 18:18:12 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@0-1-1350_1351-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:18:12 systemd[1]: Started systemd-coredump@0-1-1350_1351-0.service - Process Core Dump (PID 1350/UID 0).
Feb 19 18:18:12 audit: BPF prog-id=72 op=LOAD
Feb 19 18:18:12 audit: BPF prog-id=73 op=LOAD
Feb 19 18:18:12 audit: BPF prog-id=74 op=LOAD
Feb 19 18:18:12 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=drkonqi-coredump-processor@0-1-1350_1351-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:18:12 systemd[1]: Started drkonqi-coredump-processor@0-1-1350_1351-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Feb 19 18:18:13 abrt-dump-journal-core[873]: Failed to obtain all required information from journald
Feb 19 18:18:13 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=smb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:18:13 systemd[1]: Started smb.service - Samba SMB Daemon.
Feb 19 18:18:14 systemd[1]: dev-disk-by\x2duuid-1fdf33f1\x2d1218\x2d4dea\x2da720\x2d1b88d047e6bb.device: Job dev-disk-by\x2duuid-1fdf33f1\x2d1218\x2d4dea\x2da720\x2d1b88d047e6bb.device/start timed out.
Feb 19 18:18:14 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1fdf33f1\x2d1218\x2d4dea\x2da720\x2d1b88d047e6bb.device - /dev/disk/by-uuid/1fdf33f1-1218-4dea-a720-1b88d047e6bb.
Feb 19 18:18:14 systemd[1]: Dependency failed for mnt-salam-data.mount - /mnt/salam/data.
Feb 19 18:18:14 systemd[1]: mnt-salam-data.mount: Job mnt-salam-data.mount/start failed with result 'dependency'.
Feb 19 18:18:14 systemd[1]: dev-disk-by\x2duuid-1fdf33f1\x2d1218\x2d4dea\x2da720\x2d1b88d047e6bb.device: Job dev-disk-by\x2duuid-1fdf33f1\x2d1218\x2d4dea\x2da720\x2d1b88d047e6bb.device/start failed with result 'timeout'.
Feb 19 18:18:14 systemd-coredump[1351]: Process 1341 (gnome-session-i) of user 60578 dumped core.
                                       
                                        Module /usr/libexec/gnome-session-init-worker from rpm gnome-session-49.2-2.fc43.x86_64
                                        Module libblkid.so.1 from rpm util-linux-2.41.3-7.fc43.x86_64
                                        Module libpcre2-8.so.0 from rpm pcre2-10.47-1.fc43.x86_64
                                        Module libffi.so.8 from rpm libffi-3.5.2-1.fc43.x86_64
                                        Module libselinux.so.1 from rpm libselinux-3.9-5.fc43.x86_64
                                        Module libmount.so.1 from rpm util-linux-2.41.3-7.fc43.x86_64
                                        Module libz.so.1 from rpm zlib-ng-2.3.3-1.fc43.x86_64
                                        Module libgmodule-2.0.so.0 from rpm glib2-2.86.4-1.fc43.x86_64
                                        Module libglib-2.0.so.0 from rpm glib2-2.86.4-1.fc43.x86_64
                                        Module libgobject-2.0.so.0 from rpm glib2-2.86.4-1.fc43.x86_64
                                        Module libgio-2.0.so.0 from rpm glib2-2.86.4-1.fc43.x86_64
                                        Stack trace of thread 1341:
                                        #0  0x00007fd3ac3a5fc3 g_log_structured_array (libglib-2.0.so.0 + 0x4bfc3)
                                        #1  0x00007fd3ac3a639c g_log_default_handler (libglib-2.0.so.0 + 0x4c39c)
                                        #2  0x00007fd3ac3a10e7 g_logv (libglib-2.0.so.0 + 0x470e7)
                                        #3  0x00007fd3ac3a1483 g_log (libglib-2.0.so.0 + 0x47483)
                                        #4  0x0000558e9f2c705b main (/usr/libexec/gnome-session-init-worker + 0x105b)
                                        #5  0x00007fd3ac13e5b5 __libc_start_call_main (libc.so.6 + 0x35b5)
                                        #6  0x00007fd3ac13e668 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3668)
                                        #7  0x0000558e9f2c7645 _start (/usr/libexec/gnome-session-init-worker + 0x1645)
                                       
                                        Stack trace of thread 1348:
                                        #0  0x00007fd3ac1b59a2 __syscall_cancel_arch (libc.so.6 + 0x7a9a2)
                                        #1  0x00007fd3ac1a9c3c __internal_syscall_cancel (libc.so.6 + 0x6ec3c)
                                        #2  0x00007fd3ac1a9c84 __syscall_cancel (libc.so.6 + 0x6ec84)
                                        #3  0x00007fd3ac223706 ppoll (libc.so.6 + 0xe8706)
                                        #4  0x00007fd3ac3a4360 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x4a360)
                                        #5  0x00007fd3ac3a4423 g_main_context_iteration (libglib-2.0.so.0 + 0x4a423)
                                        #6  0x00007fd3ac3a4471 glib_worker_main (libglib-2.0.so.0 + 0x4a471)
                                        #7  0x00007fd3ac3cf742 g_thread_proxy (libglib-2.0.so.0 + 0x75742)
                                        #8  0x00007fd3ac1ad464 start_thread (libc.so.6 + 0x72464)
                                        #9  0x00007fd3ac2305ec __clone3 (libc.so.6 + 0xf55ec)
                                       
                                        Stack trace of thread 1347:
                                        #0  0x00007fd3ac22e38d syscall (libc.so.6 + 0xf338d)
                                        #1  0x00007fd3ac3c65ab g_cond_wait (libglib-2.0.so.0 + 0x6c5ab)
                                        #2  0x00007fd3ac36420c g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0xa20c)
                                        #3  0x00007fd3ac3cfbf4 g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x75bf4)
                                        #4  0x00007fd3ac3cf742 g_thread_proxy (libglib-2.0.so.0 + 0x75742)
                                        #5  0x00007fd3ac1ad464 start_thread (libc.so.6 + 0x72464)
                                        #6  0x00007fd3ac2305ec __clone3 (libc.so.6 + 0xf55ec)
                                       
                                        Stack trace of thread 1349:
                                        #0  0x00007fd3ac1b59a2 __syscall_cancel_arch (libc.so.6 + 0x7a9a2)
                                        #1  0x00007fd3ac1a9c3c __internal_syscall_cancel (libc.so.6 + 0x6ec3c)
                                        #2  0x00007fd3ac1a9c84 __syscall_cancel (libc.so.6 + 0x6ec84)
                                        #3  0x00007fd3ac223706 ppoll (libc.so.6 + 0xe8706)
                                        #4  0x00007fd3ac3a4360 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x4a360)
                                        #5  0x00007fd3ac3a451f g_main_loop_run (libglib-2.0.so.0 + 0x4a51f)
                                        #6  0x00007fd3ac5f7f92 gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0xe8f92)
                                        #7  0x00007fd3ac3cf742 g_thread_proxy (libglib-2.0.so.0 + 0x75742)
                                        #8  0x00007fd3ac1ad464 start_thread (libc.so.6 + 0x72464)
                                        #9  0x00007fd3ac2305ec __clone3 (libc.so.6 + 0xf55ec)
                                        ELF object binary architecture: AMD x86-64
Feb 19 18:18:14 systemd[1]: systemd-coredump@0-1-1350_1351-0.service: Deactivated successfully.
Feb 19 18:18:14 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-coredump@0-1-1350_1351-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 19 18:18:14 gdm-launch-environment][1210]: pam_unix(gdm-launch-environment:session): session closed for user gdm-greeter
Feb 19 18:18:14 audit: BPF prog-id=69 op=UNLOAD
Feb 19 18:18:14 audit[1210]: AUDIT1106 pid=1210 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:session_close grantors=? acct="gdm-greeter" exe="/usr/libexec/gdm-session-worker" hostname=salamlinux addr=? terminal=/dev/tty1 res=failed'
Feb 19 18:18:14 audit[1210]: AUDIT1104 pid=1210 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=PAM:setcred grantors=pam_permit acct="gdm-greeter" exe="/usr/libexec/gdm-session-worker" hostname=salamlinux addr=? terminal=/dev/tty1 res=success'
Feb 19 18:18:14 audit: BPF prog-id=71 op=UNLOAD
Feb 19 18:18:14 audit: BPF prog-id=70 op=UNLOAD
Feb 19 18:18:14 gdm[899]: Gdm: GdmDisplay: Session never registered, failing
Feb 19 18:18:14 systemd[1]: session-c1.scope: Deactivated successfully.
Feb 19 18:18:14 systemd-logind[761]: Session c1 logged out. Waiting for processes to exit.
Feb 19 18:18:14 systemd-logind[761]: Removed session c1.
Feb 19 18:18:14 gdm[899]: Gdm: Child process -1295 was already dead.
Feb 19 18:18:14 gdm[899]: Gdm: GdmDisplay: Session never registered, failing
Feb 19 18:18:14 gdm[899]: Gdm: Child process -1295 was already dead.

francismontagnac · February 20, 2026, 8:19am

I suspect that the upgrade to F43 is partial.

Running sudo dnf check should give not output.

If it is not the case, follow: Repos seem to all be out of date after upgrading to 43 - #4 by vgaetera

eliassal · February 20, 2026, 9:21am

Hi Francis, sudo dnf check gave no output

eliassal · February 20, 2026, 9:22am

Hi Steve, 1 week ago I upgraded from 41 to 42 without any issue

pg-tips · February 20, 2026, 9:33am

Based on these lines in your journal:

Feb 19 18:18:07 (systemd)[1255]: user@60578.service: PAM failed: Authentication service cannot retrieve authentication info
Feb 19 18:18:07 unix_chkpwd[1265]: could not obtain user info (gdm-greeter)
Feb 19 18:18:07 (systemd)[1255]: user@60578.service: Failed to set up PAM session: Operation not permitted
Feb 19 18:18:07 (systemd)[1255]: user@60578.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted

Could it be this issue?

francismontagnac · February 20, 2026, 9:37am

Probably yes, this issue with the gdm-greeter user should be fixed first, but the
journal shows also failures to start Xorg:

Feb 19 18:18:23 /usr/libexec/gdm-x-session[1689]: Fatal server error:
Feb 19 18:18:23 /usr/libexec/gdm-x-session[1689]: (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices

I’m not using Gnome, but AFAIK, in F43, the Xorg support of Gnome has been suppressed.

Paste (if possible as text please, and with the </> button) your /etc/gdm/custom.conf file.

eliassal · February 20, 2026, 10:42am

Here is the content of custom.conf

francismontagnac · February 20, 2026, 11:26am

This is correct: #WaylandEnable=false is commented.
The journal shows also that GDM attempts to use wayland but fails, then tries Xorg:

Feb 19 18:18:12 /usr/libexec/gdm-wayland-session[1312]: dbus-daemon[1312]: [session uid=60578 pid=1312 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
...
Feb 19 18:18:23 /usr/libexec/gdm-x-session[1689]: (--) Log file renamed from "/run/gdm/home/gdm-greeter/.local/share/xorg/Xorg.pid-1689.log" to "/run/gdm/home/gdm-greeter/.local/share/xorg/Xorg.0.log"

You should first correct the issue with the gdm-greeter user. See the earlier P G post

eliassal · February 20, 2026, 11:29am

@francismontagnac I also followed instructions at the url “Repos seems…….” but it did not help.

I issued as indicated but it did not help still getting black screen after reboot

sudo dnf distro-sync --refresh --releasever=43 --allowerasing --skip-broken --setopt=protected_packages=

update started as you can notice in the snapshot but it seems that there are 3 packages not found

anothermindbomb · February 20, 2026, 11:31am

looks fine to me. Mirror not available but if you look at the line above the file was downloaded from another mirror to 100%, successfully.

No need to post pure text as screenshots by the way; if you do they cannot be cut and pasted, searched, indexed and take up more server space.

eliassal · February 20, 2026, 11:42am

so many thanks @francismontagnac I issued

sudo authselect select local with-silent-lastlog with-fingerprint with-mdns4 --force

rebooted and I was able to reboot and access my fedora 43 using RDP. Thanks again for all

eliassal · February 25, 2026, 7:33pm

Hi @francismontagnac I have a similar and strange issue for a 2nd fedora 43. I updated this VM 3 weeks ago and I was able to work with it but today after restarting this VM, at the begining in the boot screen goes to the fedora 42 line. I choose 43 it starts, I get the UI try to log and UI just comes back again and again without being able to open the session. I did run (ctrl+alt+F3), the following 2 statements which went fine

sudo dnf distro-sync --refresh --releasever=43 --allowerasing --skip-broken --setopt=protected_packages=

sudo authselect select local with-silent-lastlog with-fingerprint with-mdns4 --force

rebooted but still same behavior

francismontagnac · February 26, 2026, 6:21am

Hi @eliassal.
Perhaps not the same issue. Let’s see.
Can you please:

reboot with the F43 kernel
reproduce once the black screen
go then to tty3 (ctrl+alt+F3)
execute: ( inxi -Fzxx; journalctl -b --no-hostname ) | fpaste
paste here the URL

Topic		Replies	Views
Updated to Fedora 43 and booting gets stuck Ask Fedora workstation	19	2600	December 26, 2025
Fedora 43 upgrade failed: had to manually reboot, now GDM coredumps Ask Fedora	45	3847	January 9, 2026
Fedora 43 Update issue Ask Fedora	15	6677	November 22, 2025
Long boot times and black screen at boot after updating from 42 to 43 Ask Fedora	1	202	December 7, 2025
Fedora failing to boot after attempting to update to from 42 to 43 Ask Fedora nvidia , workstation , f42 , f43	27	596	February 13, 2026

Black screen After Upgrade 42 to 43

Related topics