Hi,
I used the fedora-upgrade script, that rebooted my pc to install F43. The upgrade process seemed to work find until it reached 100%, to then halt for an extended period of time. I logged in with the console and was nothing using cpu. I gave it some more time and then rebooted manually.
The system came up but never went to the graphical login. I could, again, log in on the console.
I see several crashes in my journalctl:
Process 4330 (gnome-session-i) of user 0 dumped core.
Module /usr/libexec/gnome-session-init-worker from rpm gnome-session-49.1-1.fc43.x86_64
Module libblkid.so.1 from rpm util-linux-2.41.1-17.fc43.x86_64
Module libpcre2-8.so.0 from rpm pcre2-10.46-1.fc43.x86_64
Module libffi.so.8 from rpm libffi-3.5.1-2.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.1-17.fc43.x86_64
Module libz.so.1 from rpm zlib-ng-2.2.5-2.fc43.x86_64
Module libgmodule-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libglib-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libgobject-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libgio-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Stack trace of thread 4330:
#0 0x00007fc1e0b0ff03 g_log_structured_array (libglib-2.0.so.0 + 0x4bf03)
#1 0x00007fc1e0b102dc g_log_default_handler (libglib-2.0.so.0 + 0x4c2dc)
#2 0x00007fc1e0b0b027 g_logv (libglib-2.0.so.0 + 0x47027)
#3 0x00007fc1e0b0b3c3 g_log (libglib-2.0.so.0 + 0x473c3)
#4 0x000056124a85905b main (/usr/libexec/gnome-session-init-worker + 0x105b)
#5 0x00007fc1e08a75b5 __libc_start_call_main (libc.so.6 + 0x35b5)
#6 0x00007fc1e08a7668 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x3668)
#7 0x000056124a859645 _start (/usr/libexec/gnome-session-init-worker + 0x1645)
Stack trace of thread 4335:
#0 0x00007fc1e099734d syscall (libc.so.6 + 0xf334d)
#1 0x00007fc1e0b306ab g_cond_wait (libglib-2.0.so.0 + 0x6c6ab)
#2 0x00007fc1e0ace1ac g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0xa1ac)
#3 0x00007fc1e0b39ab4 g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x75ab4)
#4 0x00007fc1e0b39602 g_thread_proxy (libglib-2.0.so.0 + 0x75602)
#5 0x00007fc1e0916464 start_thread (libc.so.6 + 0x72464)
#6 0x00007fc1e09995ac __clone3 (libc.so.6 + 0xf55ac)
Stack trace of thread 4336:
#0 0x00007fc1e091e982 __syscall_cancel_arch (libc.so.6 + 0x7a982)
#1 0x00007fc1e0912c3c __internal_syscall_cancel (libc.so.6 + 0x6ec3c)
#2 0x00007fc1e0912c84 __syscall_cancel (libc.so.6 + 0x6ec84)
#3 0x00007fc1e098c6c6 ppoll (libc.so.6 + 0xe86c6)
#4 0x00007fc1e0b0e2a0 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x4a2a0)
#5 0x00007fc1e0b0e363 g_main_context_iteration (libglib-2.0.so.0 + 0x4a363)
#6 0x00007fc1e0b0e3b1 glib_worker_main (libglib-2.0.so.0 + 0x4a3b1)
#7 0x00007fc1e0b39602 g_thread_proxy (libglib-2.0.so.0 + 0x75602)
#8 0x00007fc1e0916464 start_thread (libc.so.6 + 0x72464)
#9 0x00007fc1e09995ac __clone3 (libc.so.6 + 0xf55ac)
Stack trace of thread 4337:
#0 0x00007fc1e091e982 __syscall_cancel_arch (libc.so.6 + 0x7a982)
#1 0x00007fc1e0912c3c __internal_syscall_cancel (libc.so.6 + 0x6ec3c)
#2 0x00007fc1e0912c84 __syscall_cancel (libc.so.6 + 0x6ec84)
#3 0x00007fc1e098c6c6 ppoll (libc.so.6 + 0xe86c6)
#4 0x00007fc1e0b0e2a0 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0x4a2a0)
#5 0x00007fc1e0b0e45f g_main_loop_run (libglib-2.0.so.0 + 0x4a45f)
#6 0x00007fc1e0d61f12 gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0xe8f12)
#7 0x00007fc1e0b39602 g_thread_proxy (libglib-2.0.so.0 + 0x75602)
#8 0x00007fc1e0916464 start_thread (libc.so.6 + 0x72464)
#9 0x00007fc1e09995ac __clone3 (libc.so.6 + 0xf55ac)
ELF object binary architecture: AMD x86-64
If I try to start gdm manually, I also get a core dump:
Process 3503 (gdm) of user 0 dumped core.
Module /usr/bin/gdm from rpm gdm-49.1-1.fc43.x86_64
Module libgvfscommon.so from rpm gvfs-1.58.0-1.fc43.x86_64
Module libgvfsdbus.so from rpm gvfs-1.58.0-1.fc43.x86_64
Module libnss_systemd.so.2 from rpm systemd-258.1-1.fc43.x86_64
Module libnss_sss.so.2 from rpm sssd-2.11.1-4.fc43.x86_64
Module libblkid.so.1 from rpm util-linux-2.41.1-17.fc43.x86_64
Module libudev.so.1 from rpm systemd-258.1-1.fc43.x86_64
Module libcrypt.so.2 from rpm libxcrypt-4.4.38-8.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.1-17.fc43.x86_64
Module libz.so.1 from rpm zlib-ng-2.2.5-2.fc43.x86_64
Module libgmodule-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libpcre2-8.so.0 from rpm pcre2-10.46-1.fc43.x86_64
Module libffi.so.8 from rpm libffi-3.5.1-2.fc43.x86_64
Module libcap.so.2 from rpm libcap-2.76-3.fc43.x86_64
Module libgudev-1.0.so.0 from rpm libgudev-238-8.fc43.x86_64
Module libXau.so.6 from rpm libXau-1.0.12-3.fc43.x86_64
Module libxcb.so.1 from rpm libxcb-1.17.0-6.fc43.x86_64
Module libjson-glib-1.0.so.0 from rpm json-glib-1.10.8-.fc43.x86_64
Module libaccountsservice.so.0 from rpm accountsservice-23.13.9-9.fc43.x86_64
Module libgio-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libglib-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libgobject-2.0.so.0 from rpm glib2-2.86.0-2.fc43.x86_64
Module libsystemd.so.0 from rpm systemd-258.1-1.fc43.x86_64
Stack trace of thread 3503:
#0 0x00007f91181150f8 g_logv (libglib-2.0.so.0 + 0x470f8)
I can, however, start wayland with: gnome-session –wayland
I am a bit at a loss on how to proceed.
Any help is appreciated…
)