Description of problem: Crashes on startup after clean KDE install, is affecting everyone ATM. Version-Release number of selected component: mariadb-server-3:11.8.6-1.fc45 Additional info: reporter: libreport-2.17.15 type: CCpp reason: mariadbd killed by SIGSEGV journald_cursor: s=434821102c544201956586d0966eb3fc;i=d40;b=a39d865f27144ca39337f150c6ab376d;m=4614eca;t=64abd86d301dd;x=3fc44daf436956df executable: /usr/libexec/mariadbd cmdline: /usr/bin/mysqld --defaults-file=/home/test/.local/share/akonadi/mysql.conf --datadir=/home/test/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.kalendarac rootdir: / uid: 1000 kernel: 6.20.0-0.rc0.260212gc22e26bd0906e.3.fc45.x86_64 package: mariadb-server-3:11.8.6-1.fc45 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: __syscall_cancel_arch comment: Crashes on startup after clean KDE install, is affecting everyone ATM. Truncated backtrace: Thread no. 3 (16 frames) #0 __syscall_cancel_arch at ../sysdeps/unix/sysv/linux/x86_64/syscall_cancel.S:56 #1 __internal_syscall_cancel at cancellation.c:49 #2 __futex_abstimed_wait_common64 at futex-internal.c:57 #3 __futex_abstimed_wait_common at futex-internal.c:87 #4 __futex_abstimed_wait_cancelable64 at futex-internal.c:139 #5 __pthread_cond_wait_common at pthread_cond_wait.c:421 #6 ___pthread_cond_clockwait64 at pthread_cond_wait.c:517 #8 std::__condvar::wait_until at /usr/include/c++/16/bits/std_mutex.h:188 #9 std::condition_variable::__wait_until_impl<std::chrono::duration<long, std::ratio<1l, 1000000000l> > > at /usr/include/c++/16/condition_variable:197 #10 std::condition_variable::wait_until<std::chrono::duration<long, std::ratio<1l, 1000000000l> > > at /usr/include/c++/16/condition_variable:115 #11 std::condition_variable::wait_for<long, std::ratio<1l, 1000l> > at /usr/include/c++/16/condition_variable:167 #12 tpool::thread_pool_generic::wait_for_tasks at /usr/src/debug/mariadb11.8-11.8.6-1.fc45.x86_64/tpool/tpool_generic.cc:431 #13 tpool::thread_pool_generic::get_task at /usr/src/debug/mariadb11.8-11.8.6-1.fc45.x86_64/tpool/tpool_generic.cc:484 #14 tpool::thread_pool_generic::worker_main at /usr/src/debug/mariadb11.8-11.8.6-1.fc45.x86_64/tpool/tpool_generic.cc:529 #15 std::execute_native_thread_routine at ../../../../../libstdc++-v3/src/c++11/thread.cc:105 #17 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 2129404 [details] File: proc_pid_status
Created attachment 2129405 [details] File: maps
Created attachment 2129406 [details] File: limits
Created attachment 2129407 [details] File: environ
Created attachment 2129408 [details] File: open_fds
Created attachment 2129409 [details] File: mountinfo
Created attachment 2129410 [details] File: os_info
Created attachment 2129411 [details] File: cpuinfo
Created attachment 2129412 [details] File: core_backtrace
Created attachment 2129413 [details] File: dso_list
Created attachment 2129414 [details] File: backtrace
Just for a bit more info: ever since mariadb11.8-11.8.6-1 landed in F44 and Rawhide, we get a crash when KDE starts. This affects all openQA tests and multiple users have also reported seeing it in local testing. I reproduced it in a VM to get this report. Just install any F44 or Rawhide KDE live since 2026-02-09 - e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20260213.n.1/compose/KDE/x86_64/iso/Fedora-KDE-Desktop-Live-Rawhide-20260213.n.1.x86_64.iso - boot the installed system, create a user, log in, and you should see the crash. Proposing as a Final blocker per https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria#SELinux_and_crash_notifications "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."
+3 in https://pagure.io/fedora-qa/blocker-review/issue/2034 and it's a pretty clear violation, marking accepted.
Also proposing as a Beta FE, as this is highly visible and probably actually breaks stuff, so we should fix it for Beta if we can.
*** This bug has been marked as a duplicate of bug 2438390 ***