Bug 2455578 - Miriway crashing during boot sequence [NEEDINFO]
Summary: Miriway crashing during boot sequence
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: miriway
Version: 44
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Neal Gompa
QA Contact:
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:116112bc2da80b0dfaa96194b32...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-06 20:14 UTC by yusufxkhalid
Modified: 2026-04-11 21:37 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
yusufxkhalid: fedora_prioritized_bug?
yusufxkhalid: needinfo?


Attachments (Terms of Use)
File: proc_pid_status (1.47 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: maps (47.61 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: limits (1.29 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: environ (746 bytes, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: open_fds (17.31 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: mountinfo (3.55 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: os_info (682 bytes, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: cpuinfo (3.37 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: core_backtrace (69.43 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: exploitable (81 bytes, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: dso_list (8.22 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details
File: backtrace (97.56 KB, text/plain)
2026-04-06 20:14 UTC, yusufxkhalid
no flags Details

Description yusufxkhalid 2026-04-06 20:14:04 UTC
Description of problem:
I'm simply testing the fedora 44 budgie I was running a hardware check, and diagnostic for my computer. Then noticed the error report in my terminal I have no issues logging in everything else works fine, yeah system shouldn't be crashing.

Version-Release number of selected component:
miriway-26.01-1.fc44

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         miriway-shell killed by SIGSEGV
journald_cursor: s=09bd7db41c8e4e278be62210faa1e70b;i=4b743;b=aaba963eeb0f47a48859d9feaae1bbd7;m=24911eb;t=64cb17c28b10c;x=20bc5b237c076f96
executable:     /usr/bin/miriway-shell
cmdline:        /usr/bin/miriway-shell --add-wayland-extensions=zwlr_layer_shell_v1
cgroup:         0::/user.slice/user-965.slice/session-c1.scope
rootdir:        /
uid:            965
kernel:         6.19.6-300.fc44.x86_64
package:        miriway-26.01-1.fc44
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: std::_Hashtable<unsigned long, std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const>, std::allocator<std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::_M_find_before_node
comment:        I'm simply testing the fedora 44 budgie I was running a hardware check, and diagnostic for my computer. Then noticed the error report in my terminal I have no issues logging in everything else works fine, yeah system shouldn't be crashing.

Truncated backtrace:
Thread no. 1 (22 frames)
 #0 std::_Hashtable<unsigned long, std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const>, std::allocator<std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::_M_find_before_node at /usr/include/c++/16/bits/hashtable.h:2212
 #1 std::_Hashtable<unsigned long, std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const>, std::allocator<std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::_M_locate at /usr/include/c++/16/bits/hashtable.h:2286
 #2 std::_Hashtable<unsigned long, std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const>, std::allocator<std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::find at /usr/include/c++/16/bits/hashtable.h:1921
 #3 std::unordered_map<unsigned long, mir::LogindConsoleServices::Device const* const, std::hash<unsigned long>, std::equal_to<unsigned long>, std::allocator<std::pair<unsigned long const, mir::LogindConsoleServices::Device const* const> > >::find at /usr/include/c++/16/bits/unordered_map.h:962
 #4 operator() at /usr/src/debug/mir-2.25.1-5.fc44.x86_64/src/server/console/logind_console_services.cpp:508
 #5 std::__invoke_impl<void, mir::LogindConsoleServices::acquire_device(int, int, std::unique_ptr<mir::Device::Observer>)::<lambda(const mir::LogindConsoleServices::Device*)>&, const mir::LogindConsoleServices::Device*> at /usr/include/c++/16/bits/invoke.h:63
 #6 std::__invoke_r<void, mir::LogindConsoleServices::acquire_device(int, int, std::unique_ptr<mir::Device::Observer>)::<lambda(const mir::LogindConsoleServices::Device*)>&, const mir::LogindConsoleServices::Device*> at /usr/include/c++/16/bits/invoke.h:113
 #7 std::_Function_handler<void(const mir::LogindConsoleServices::Device*), mir::LogindConsoleServices::acquire_device(int, int, std::unique_ptr<mir::Device::Observer>)::<lambda(const mir::LogindConsoleServices::Device*)> >::_M_invoke(const std::_Any_data &, const mir::LogindConsoleServices::Device *&&) at /usr/include/c++/16/bits/std_function.h:295
 #8 std::function<void(mir::LogindConsoleServices::Device const*)>::operator() at /usr/include/c++/16/bits/std_function.h:581
 #9 mir::LogindConsoleServices::Device::~Device at /usr/src/debug/mir-2.25.1-5.fc44.x86_64/src/server/console/logind_console_services.cpp:356
 #11 std::default_delete<mir::Device>::operator() at /usr/include/c++/16/bits/unique_ptr.h:86
 #12 std::unique_ptr<mir::Device, std::default_delete<mir::Device> >::~unique_ptr at /usr/include/c++/16/bits/unique_ptr.h:398
 #13 mir::graphics::gbm::Platform::~Platform at /usr/src/debug/mir-2.25.1-5.fc44.x86_64/src/platforms/gbm-kms/server/kms/platform.cpp:128
 #15 std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release at /usr/include/c++/16/bits/shared_ptr_base.h:423
 #17 std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count at /usr/include/c++/16/bits/shared_ptr_base.h:1129
 #18 std::__shared_ptr<void, (__gnu_cxx::_Lock_policy)2>::~__shared_ptr at /usr/include/c++/16/bits/shared_ptr_base.h:1603
 #19 std::shared_ptr<void>::~shared_ptr at /usr/include/c++/16/bits/shared_ptr.h:175
 #20 std::destroy_at<std::shared_ptr<void> > at /usr/include/c++/16/bits/stl_construct.h:88
 #21 std::_Destroy<std::shared_ptr<void> > at /usr/include/c++/16/bits/stl_construct.h:164
 #22 std::_Destroy<std::shared_ptr<void>*> at /usr/include/c++/16/bits/stl_construct.h:226
 #23 std::_Destroy<std::shared_ptr<mir::graphics::DisplayPlatform>*, std::shared_ptr<mir::graphics::DisplayPlatform> > at /usr/include/c++/16/bits/alloc_traits.h:1045
 #24 std::vector<std::shared_ptr<mir::graphics::DisplayPlatform>, std::allocator<std::shared_ptr<mir::graphics::DisplayPlatform> > >::~vector at /usr/include/c++/16/bits/stl_vector.h:792

Comment 1 yusufxkhalid 2026-04-06 20:14:07 UTC
Created attachment 2136055 [details]
File: proc_pid_status

Comment 2 yusufxkhalid 2026-04-06 20:14:08 UTC
Created attachment 2136056 [details]
File: maps

Comment 3 yusufxkhalid 2026-04-06 20:14:09 UTC
Created attachment 2136057 [details]
File: limits

Comment 4 yusufxkhalid 2026-04-06 20:14:11 UTC
Created attachment 2136058 [details]
File: environ

Comment 5 yusufxkhalid 2026-04-06 20:14:12 UTC
Created attachment 2136059 [details]
File: open_fds

Comment 6 yusufxkhalid 2026-04-06 20:14:13 UTC
Created attachment 2136060 [details]
File: mountinfo

Comment 7 yusufxkhalid 2026-04-06 20:14:14 UTC
Created attachment 2136061 [details]
File: os_info

Comment 8 yusufxkhalid 2026-04-06 20:14:15 UTC
Created attachment 2136062 [details]
File: cpuinfo

Comment 9 yusufxkhalid 2026-04-06 20:14:17 UTC
Created attachment 2136063 [details]
File: core_backtrace

Comment 10 yusufxkhalid 2026-04-06 20:14:18 UTC
Created attachment 2136064 [details]
File: exploitable

Comment 11 yusufxkhalid 2026-04-06 20:14:19 UTC
Created attachment 2136065 [details]
File: dso_list

Comment 12 yusufxkhalid 2026-04-06 20:14:20 UTC
Created attachment 2136066 [details]
File: backtrace


Note You need to log in before you can comment on or make changes to this bug.