Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I launched Budgie desktop with Miriway using budgie-wayland-session-miriway from ngompa/wlmagpie COPR. Version-Release number of selected component: miriway-25.12-2.fc44 Additional info: reporter: libreport-2.17.15 type: CCpp reason: miriway-shell killed by SIGABRT journald_cursor: s=21345b14c6864aa6ab266d6bca9a44a0;i=14e9;b=fd26717adc724872ae915d408603213f;m=18070fb;t=648aebe1c9605;x=284e0bb99b645b05 executable: /usr/bin/miriway-shell cmdline: miriway-shell --display-config=static=/miriway-shell.display-config --add-wayland-extensions=all --x11-displayfd 5 cgroup: 0::/user.slice/user-1000.slice/session-2.scope rootdir: / uid: 1000 kernel: 6.18.0-65.fc44.x86_64 package: miriway-25.12-2.fc44 runlevel: /bin/sh: line 1: runlevel: command not found backtrace_rating: 4 crash_function: mir::fatal_error_abort comment: I launched Budgie desktop with Miriway using budgie-wayland-session-miriway from ngompa/wlmagpie COPR. Truncated backtrace: Thread no. 1 (26 frames) #1 mir::fatal_error_abort at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/core/fatal.cpp:40 #2 (anonymous namespace)::fatal_signal_cleanup at /usr/include/c++/16/bits/basic_string.h:238 #4 wl_resource_post_event at ../src/wayland-server.c:259 #5 std::function<void(wl_resource*)>::operator() at /usr/include/c++/16/bits/std_function.h:581 #6 operator() at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/server/frontend_wayland/wayland_connector.cpp:587 #7 std::__invoke_impl<void, mir::frontend::WaylandConnector::for_each_output_binding(mir::wayland::Client*, mir::graphics::DisplayConfigurationOutputId, const std::function<void(wl_resource*)>&)::<lambda(mir::frontend::OutputInstance*)>&, mir::frontend::OutputInstance*> at /usr/include/c++/16/bits/invoke.h:63 #8 std::__invoke_r<void, mir::frontend::WaylandConnector::for_each_output_binding(mir::wayland::Client*, mir::graphics::DisplayConfigurationOutputId, const std::function<void(wl_resource*)>&)::<lambda(mir::frontend::OutputInstance*)>&, mir::frontend::OutputInstance*> at /usr/include/c++/16/bits/invoke.h:113 #9 std::_Function_handler<void(mir::frontend::OutputInstance*), mir::frontend::WaylandConnector::for_each_output_binding(mir::wayland::Client*, mir::graphics::DisplayConfigurationOutputId, const std::function<void(wl_resource*)>&)::<lambda(mir::frontend::OutputInstance*)> >::_M_invoke(const std::_Any_data &, mir::frontend::OutputInstance *&&) at /usr/include/c++/16/bits/std_function.h:295 #10 std::function<void(mir::frontend::OutputInstance*)>::operator() at /usr/include/c++/16/bits/std_function.h:581 #11 mir::frontend::OutputGlobal::for_each_output_bound_by at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/server/frontend_wayland/output_manager.cpp:189 #12 mir::frontend::WaylandConnector::for_each_output_binding at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/server/frontend_wayland/wayland_connector.cpp:587 #13 mir::Server::for_each_output_binding at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/server/server.cpp:798 #14 miral::WaylandTools::Self::for_each_output_binding at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/miral/wayland_tools.cpp:41 #15 miral::WaylandTools::for_each_binding at /usr/src/debug/mir-2.25.1-3.fc44.x86_64/src/miral/wayland_tools.cpp:70 #16 miriway::ExtWorkspaceManagerV1::output_added at /usr/src/debug/miriway-25.12-2.fc44.x86_64/miriway_ext_workspace_v1.cpp:224 #17 miriway::ExtWorkspaceManagerV1::Global::bind at /usr/src/debug/miriway-25.12-2.fc44.x86_64/miriway_ext_workspace_v1.cpp:366 #18 mir::wayland::ExtWorkspaceManagerV1::Thunks::bind_thunk at /usr/src/debug/miriway-25.12-2.fc44.x86_64/wayland-generated/ext-workspace-v1_wrapper.cpp:100 #19 ffi_call_unix64 at ../src/x86/unix64.S:104 #20 ffi_call_int at ../src/x86/ffi64.c:676 #21 ffi_call at ../src/x86/ffi64.c:713 #22 wl_closure_invoke at ../src/connection.c:1241 #23 wl_client_connection_data at ../src/wayland-server.c:483 #24 wl_event_loop_dispatch at ../src/event-loop.c:1059 #25 wl_display_run at ../src/wayland-server.c:1584 #26 std::execute_native_thread_routine at ../../../../../libstdc++-v3/src/c++11/thread.cc:105 #28 __clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Created attachment 2122622 [details] File: proc_pid_status
Created attachment 2122623 [details] File: maps
Created attachment 2122624 [details] File: limits
Created attachment 2122625 [details] File: environ
Created attachment 2122626 [details] File: open_fds
Created attachment 2122627 [details] File: mountinfo
Created attachment 2122628 [details] File: os_info
Created attachment 2122629 [details] File: cpuinfo
Created attachment 2122630 [details] File: core_backtrace
Created attachment 2122631 [details] File: dso_list
Created attachment 2122632 [details] File: backtrace
That stacktrace looks weird: we're binding the "global", have created a workspace manager and are populating it with the outputs. There isn't any obvious way that interpreting the protocol differently would lead to a crash. Any chance of a WAYLAND_DEBUG log? Or a reproducer?
This bug appears to have been reported against 'rawhide' during the Fedora Linux 45 development cycle. Changing version to 45.
FEDORA-2026-5877049fca (mir-2.29.0-1.fc45, miracle-wm-0.11.0-1.fc45, and 1 more) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-5877049fca
FEDORA-2026-5877049fca has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-5877049fca` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5877049fca See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-5877049fca (mir-2.29.0-1.fc45, miracle-wm-0.11.0-1.fc45, and 1 more) has been pushed to the Fedora 45 stable repository. If problem still persists, please make note of it in this bug report.