[plasmashell] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 Erlend Ydse changed: What|Removed |Added Status|RESOLVED|REOPENED CC||er.y...@pm.me Ever confirmed|0 |1 Resolution|DUPLICATE |--- --- Comment #5 from Erlend Ydse --- This still happens on KDE Plasma 5.24 using Wayland on AMD Ryzen 7 4700U. Even if the issue has been solved on X11, it is not fixed for Wayland. Therefore I suggest removing duplicate status, as this would then be a separate issue. I'll provide any logs/outputs you need. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 Erlend Ydse changed: What|Removed |Added Version|5.23.3 |5.24.0 --- Comment #6 from Erlend Ydse --- Journal log from opening the lid of the laptop, disconnecting the monitor, waiting for the panel to appear again, then connecting the monitor before closing the lid again: 10/02/2022 13:30systemd-logind Lid opened. 10/02/2022 13:30klauncher qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30kwalletd5 qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30kactivitymanagerd qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_contacts_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_newmailnotifier_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30baloorunner qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_akonotes_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_migration_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30krunner qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_control qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_birthdays_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_ical_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_indexing_agent qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_google_resource qt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_maildispatcher_agentqt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30akonadi_maildir_resourceqt.qpa.wayland: Creating a fake screen in order for Qt not to crash 10/02/2022 13:30dbus-daemon [session uid=1000 pid=758] Activating service name='org.kde.KSplash' requested by ':1.21' (uid=1000 pid=879 comm="/usr/bin/plasmashell ") 10/02/2022 13:30dbus-daemon writing oom_score_adj error: Permission denied 10/02/2022 13:30systemd Created slice User Core Session Slice. 10/02/2022 13:30systemd Started PipeWire Multimedia Service. 10/02/2022 13:30systemd Started Multimedia Service Session Manager. 10/02/2022 13:30systemd Started PipeWire PulseAudio. 10/02/2022 13:30user@1000.service SPA handle 'api.alsa.acp.device' could not be loaded; is it installed? 10/02/2022 13:30user@1000.service Failed to create 'api.alsa.acp.device' device 10/02/2022 13:30bluetoothd Player registered: sender=:1.81 path=/media_player0 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/ldac 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSink/aptx_hd 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_hd 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSink/aptx 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aac 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSink/sbc_xq 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/sbc_xq 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_ll_1 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_ll_0 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 10/02/2022 13:30bluetoothd Endpoint registered: sender=:1.81 path=/MediaEndpoint/A2DPSource/faststream 10/02/2022 13:30blue
[plasmashell] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #7 from Erlend Ydse --- I can confirm that this only happens on Wayland, not X11. It happens on cold boot, restart and logout-login, though -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #8 from Erlend Ydse --- Journal logs from restarting. I'm not sure if it is even relevant. This is all that happens before I start KSystemLog: 10/02/2022 13:52kernel audit: type=1131 audit(1644497537.862:97): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 10/02/2022 13:52audit BPF prog-id=0 op=UNLOAD 10/02/2022 13:52audit BPF prog-id=0 op=UNLOAD 10/02/2022 13:52audit BPF prog-id=0 op=UNLOAD 10/02/2022 13:52kernel audit: type=1334 audit(1644497537.992:98): prog-id=0 op=UNLOAD 10/02/2022 13:52kernel audit: type=1334 audit(1644497537.992:99): prog-id=0 op=UNLOAD 10/02/2022 13:52kernel audit: type=1334 audit(1644497537.992:100): prog-id=0 op=UNLOAD 10/02/2022 13:52systemd Starting EOS update notifier service... 10/02/2022 13:52dbus-daemon [session uid=1000 pid=763] Activating via systemd: service name='org.kde.krunner' unit='plasma-krunner.service' requested by ':1.6' (uid=1000 pid=774 comm="/usr/bin/kwin_wayland --wayland-fd 5 --socket wayl") 10/02/2022 13:52systemd Starting KRunner... 10/02/2022 13:52dbus-daemon [session uid=1000 pid=763] Successfully activated service 'org.kde.krunner' 10/02/2022 13:52systemd Started KRunner. 10/02/2022 13:52krunner QCommandLineParser: argument list cannot be empty, it should contain at least the executable name 10/02/2022 13:52krunner qt.qpa.wayland: Wayland does not support QWindow::requestActivate() 10/02/2022 13:52dbus-daemon [session uid=1000 pid=763] Activating via systemd: service name='org.kde.runners.baloo' unit='plasma-baloorunner.service' requested by ':1.50' (uid=1000 pid=2103 comm="/usr/bin/krunner ") 10/02/2022 13:52systemd Starting KRunner provider for baloo file indexer... 10/02/2022 13:52dbus-daemon [session uid=1000 pid=763] Successfully activated service 'org.kde.runners.baloo' 10/02/2022 13:52systemd Started KRunner provider for baloo file indexer. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #10 from Erlend Ydse --- It seems that the corefile for kwin_wayland is missing: ~ coredumpctl TIME PID UID GID SIG COREFILE EXE SIZE Mon 2021-12-13 14:16:37 CET 2296 1000 1000 SIGSEGV missing /usr/bin/systemsettings5 n/a Mon 2021-12-13 14:18:06 CET 18029 1000 1000 SIGSEGV missing /usr/bin/systemsettings5 n/a Mon 2021-12-13 15:11:55 CET 692 1000 1000 SIGSEGV missing /usr/bin/kwin_x11 n/a Sun 2021-12-26 14:15:43 CET 12603 1000 1000 SIGABRT missing /usr/lib/virtualbox/VirtualBoxVM n/a Sun 2021-12-26 14:17:40 CET 12693 1000 1000 SIGABRT missing /usr/lib/virtualbox/VirtualBoxVM n/a Wed 2021-12-29 16:50:14 CET 17297 1000 1000 SIGSEGV missing /usr/bin/easyeffects n/a Wed 2021-12-29 23:19:45 CET 759 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Thu 2021-12-30 17:28:43 CET 720 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Thu 2021-12-30 17:40:37 CET 4993 1000 1000 SIGSEGV missing /usr/bin/configure-printern/a Thu 2021-12-30 17:56:54 CET 29494 1000 1000 SIGABRT none /usr/lib/kf5/kdesud n/a Thu 2021-12-30 22:17:14 CET 741 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Fri 2021-12-31 13:17:13 CET 743 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Fri 2021-12-31 17:39:23 CET 720 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Mon 2022-01-03 23:57:10 CET 748 1000 1000 SIGABRT missing /usr/bin/kwin_wayland n/a Wed 2022-01-05 17:45:44 CET 1329 1000 1000 SIGABRT missing /usr/bin/kalendarac n/a Tue 2022-01-11 13:21:14 CET 862 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Thu 2022-01-13 16:00:38 CET 870 1000 1000 SIGSEGV missing /usr/bin/plasmashell n/a Wed 2022-01-26 15:17:42 CET 1563 1000 1000 SIGABRT missing /usr/bin/kalendarac n/a Thu 2022-02-10 13:47:03 CET 4654 1000 1000 SIGABRT none /usr/lib/kf5/kdesud n/a Thu 2022-02-10 13:47:06 CET 3824 1000 1000 SIGSEGV present /usr/bin/akonadiserver 1.1M In case it helps, here is the output from akonadiserver: [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". Core was generated by `/usr/bin/akonadiserver'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x55c3b68686a3 in ?? () [Current thread is 1 (Thread 0x7f2607fb2cc0 (LWP 3824))] (gdb) bt #0 0x55c3b68686a3 in ?? () #1 0x7f260c712e76 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #2 0x7f260c6ef14e in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #3 0x7f260c6efc69 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #4 0x7f260c736548 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f260aa5df13 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #6 0x7f260aab40d9 in ?? () from /usr/lib/libglib-2.0.so.0 #7 0x7f260aa5b485 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0x7f260c73a44a in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #9 0x7f260c6e744b in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #10 0x7f260c6f2b97 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #11 0x55c3b685dcc5 in ?? () #12 0x7f260c08db25 in __libc_start_main () from /usr/lib/libc.so.6 #13 0x55c3b6860bee in ?? () -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078
--- Comment #11 from Erlend Ydse ---
With debugging symbols:
Core was generated by `/usr/bin/akonadiserver'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 std::default_delete::operator() (__ptr=0x91,
this=) at /usr/include/c++/11.1.0/bits/unique_ptr.h:79
79operator()(_Tp* __ptr) const
[Current thread is 1 (Thread 0x7f2607fb2cc0 (LWP 3824))]
(gdb) bt
#0 std::default_delete::operator() (__ptr=0x91,
this=) at /usr/include/c++/11.1.0/bits/unique_ptr.h:79
#1 std::unique_ptr >::~unique_ptr
(this=, this=) at
/usr/include/c++/11.1.0/bits/unique_ptr.h:361
#2 __gnu_cxx::new_allocator >
>::destroy > > (__p=,
this=)
at /usr/include/c++/11.1.0/ext/new_allocator.h:162
#3
std::allocator_traits > >
>::destroy > > (__p=,
__a=...)
at /usr/include/c++/11.1.0/bits/alloc_traits.h:531
#4 std::vector >,
std::allocator > > >::_M_erase (Python
Exception : Request for member '_M_head_impl' is ambiguous
in type 'std::tuple >'. Candidates are:
'std::default_delete std::_Head_base<1,
std::default_delete, true>::_M_head_impl'
(std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Tuple_impl<1, std::default_delete > ->
std::_Head_base<1, std::default_delete, true>)
' std::_Head_base<0, Akonadi::Server::Connection*,
false>::_M_head_impl' (std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Head_base<0, Akonadi::Server::Connection*, false>)
__position=
{_M_t = { >> = {_M_t = std::tuple
containing = {[1] = 0x55c3b7811d70, [2] = {}}}, }}, this=)
at /usr/include/c++/11.1.0/bits/vector.tcc:177
#5 std::vector >,
std::allocator > > >::erase (Python Exception
: Request for member '_M_head_impl' is ambiguous in type
'std::tuple >'. Candidates are:
'std::default_delete std::_Head_base<1,
std::default_delete, true>::_M_head_impl'
(std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Tuple_impl<1, std::default_delete > ->
std::_Head_base<1, std::default_delete, true>)
' std::_Head_base<0, Akonadi::Server::Connection*,
false>::_M_head_impl' (std::tuple > -> std::_Tuple_impl<0,
Akonadi::Server::Connection*, std::default_delete
> -> std::_Head_base<0, Akonadi::Server::Connection*, false>)
__position=
{_M_t = { >> = {_M_t = std::tuple
containing = {[1] = 0x55c3b7811d70, [2] = {}}}, }}, this=)
at /usr/include/c++/11.1.0/bits/stl_vector.h:1431
#6 Akonadi::Server::AkonadiServer::connectionDisconnected (this=) at /usr/src/debug/akonadi-21.12.2/src/server/akonadi.cpp:234
#7 0x7f260c712e76 in QObject::event (this=,
e=0x7f25d003aa50) at kernel/qobject.cpp:1314
#8 0x7f260c6ef14e in doNotify (event=0x7f25d003aa50,
receiver=0x7ffe145860c0) at kernel/qcoreapplication.cpp:1154
#9 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1140
#10 QCoreApplication::notifyInternal2 (receiver=0x7ffe145860c0,
event=0x7f25d003aa50) at kernel/qcoreapplication.cpp:1064
#11 0x7f260c6efc69 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55c3b775f1c0) at
kernel/qcoreapplication.cpp:1821
#12 0x7f260c736548 in postEventSourceDispatch (s=0x55c3b7764350) at
kernel/qeventdispatcher_glib.cpp:277
#13 0x7f260aa5df13 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#14 0x7f260aab40d9 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x7f260aa5b485 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#16 0x7f260c73a44a in QEventDispatcherGlib::processEvents
(this=0x55c3b77617e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#17 0x7f260c6e744b in QEventLoop::exec (this=0x7ffe14585f10, flags=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#18 0x7f260c6f2b97 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#19 0x55c3b685dcc5 in AkApplicationBase::exec (this=0x7ffe14586090) at
/usr/src/debug/akonadi-21.12.2/src/shared/akapplication.cpp:107
#20 main (argc=, argv=) at
/usr/src/debug/akonadi-21.12.2/src/server/main.cpp:65
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #13 from Erlend Ydse --- If you look at the date, kwin_wayland has not crashed since the start of January. The output of coredumpctl gdb 748 is File "/var/lib/systemd/coredump/core.kwin_wayland.1000.a7b48ceb67ff410bbc72b2f12ccf2380.748.164125062900.zst" is not readable: No such file or directory So I suspect that a crash is not the reason for the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #15 from Erlend Ydse --- Still happens as of today on Plasma 5.24. Nothing in coredumpctl. No notable logs Conditions: Laptop is plugged into monitor on boot. Screens are configured to disable laptop screen when monitor is plugged in. Notable events: On successful login, the splash screen is present for longer than if the monitor is not plugged in. I suspect a timeout triggers, and then the desktop is shown with either a black wallpaper or the chosen wallpaper. No panels are visible, and adding panels makes no difference. In some cases the desktop does not display a menu on right click. Firefox is autostarted. Krunner and System Settings work via shortcuts, and it is still possible to interact with bluetooth, networks and audio via System Settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #16 from Erlend Ydse --- Updated to Plasma 5.24.1 and rebooted. Same result with black/no wallpaper -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446078] Attaching/detaching external monitors with Wayland crashes apps/hides Plasma panel
https://bugs.kde.org/show_bug.cgi?id=446078 --- Comment #18 from Erlend Ydse --- Strahinja, can you please try these steps and see if it still does not happen? 1. In System Settings > Display Configuration, change to "for only this display configuration" and disable the main screen, leave the external monitor enabled. 2. Turn off the laptop, keep the monitor connected. 3. Boot and log in with the monitor still plugged in. 4. Look for long login time and disappearing panels. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450451] New: kwin_wayland randomly crashed
https://bugs.kde.org/show_bug.cgi?id=450451 Bug ID: 450451 Summary: kwin_wayland randomly crashed Product: kwin Version: 5.24.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: er.y...@pm.me Target Milestone: --- SUMMARY kwin_wayland randomly crashed. I was using Plasma normally, and the only application open was Firefox. A short time after I clicked an unloaded tab, the crash occurred. Journal log and backtrace are in "additional information". STEPS TO REPRODUCE 1. Use external monitor with laptop monitor disabled. Only Firefox open. 2. Wait for random crash. OBSERVED RESULT Kwin crashes, taking all applications with it. After the crash, it is possible to start applications via KRunner and shortcuts. Panels disappear, wallpaper is gone. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 5.16.9-arch1-1, Plasma 5.24.1 (available in About System) KDE Plasma Version: 5.24.1 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION *Journal log from the crash:* 17/02/2022 13:03kernel audit: type=1130 audit(1645099415.441:143): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-3700-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' 17/02/2022 13:03systemd-coredumpProcess 766 (kwin_wayland) of user 1000 dumped core. Module /usr/lib/qt/plugins/imageformats/libqjpeg.so (deleted) with build-id d763136273bc3d816154f3f11b66aa349e5ba507 Module /usr/lib/qt/plugins/imageformats/libqico.so (deleted) with build-id a6a8cda2b6fc8f67e5705edb6d5c3835749b6fc2 Module /usr/lib/qt/plugins/imageformats/libqgif.so (deleted) with build-id 0f9413a6e86dd17eba78d657844c0341588da6be Module /usr/lib/libQt5PrintSupport.so.5.15.2 (deleted) with build-id 367d4ebd6b678246b134a822aabd64e80d3555aa Module /usr/lib/libQt5Network.so.5.15.2 (deleted) with build-id 67856eaa90536df8090ca2a132169fe198bb0066 Module /usr/lib/libQt5Xml.so.5.15.2 (deleted) with build-id 51fab989c4a5fb399e13d208c17622b00c75b515 Module /usr/lib/libQt5Sql.so.5.15.2 (deleted) with build-id bc82bf17f6d636c0158c7f7a5f27f3febc58d018 Module /usr/lib/libpipewire-0.3.so.0.345.0 (deleted) with build-id a9294fe09416a07d8b2d61e8d8424730a61f9f64 Module /usr/lib/libQt5Core.so.5.15.2 (deleted) with build-id aee6734627204dd2ca387bf26d90a5795001cd1c Module /usr/lib/libQt5Gui.so.5.15.2 (deleted) with build-id 5bfa3dab2c38ef6dd6d97b921b34fd6e884d947f Module /usr/lib/libQt5Widgets.so.5.15.2 (deleted) with build-id f02a7b29c755dfc364dc4113c973032b7f4e9abc Module /usr/lib/libQt5DBus.so.5.15.2 (deleted) with build-id b8427937e1990908c365e7ddafffca1a00db6a3d Module linux-vdso.so.1 with build-id e70f128dc93a0ce4141b994b2bf8b52a8ba40f28 Module libpipewire-module-session-manager.so with build-id af25c4879a26cfd14f12e57a413b724dce4bdcdd Module libpipewire-module-metadata.so with build-id 34df88d0eff0ad272de29cce48e3d3de1ea1a501 Module libpipewire-module-adapter.so with build-id 7d41ea3b2963a421b49fc718c3405aaf94c73821 Module libpipewire-module-client-device.so with build-id 268ae09ce4d79c2720ced87dbdfbda5566b35bf5 Module libpipewire-module-client-node.so with build-id b4329f12c7be70a80d6ebac16ddc2072acb0ad62 Module libpipewire-module-protocol-native.so with build-id 2453f6b7f336f18c58f7a957abaddc8bae343e7d Module libspa-dbus.so with build-id c677e18c8a540a313627161eea8ade3aff97d603 Module libspa-journal.so with build-id 06592895de2df06a6c5352f10df43acc1c06fc74 Module libspa-support.so with build-id 0adfa73891a66e0dbf96542703ffad0029a81dda Module libwebp.so.7 with build-id 0add7a572705244ed810b7e722cce7da0dcfb62c Module libwebpdemux.so.2 with build-id 7bc15ac239db643015e169a2c6cc822156eb999a Module libwebpmux.so.3 with build-id 4232d5263a45719ba12f58ed7d8cae3a0fc887de Module libqwebp.so with build-id 4c9c68e5ad684209eebcc41c23d7c9a700fa84fd Module libqwbmp.so with build-id 266f01cf84c000fff5463ee44c422737dd5a6a55 Module libtiff.so.5 with build-id e8d89a0fb0847641ddb75c5f03fa89d68155a75d Module libqtiff.so with build-id 0ecb9be29e5c5f5b86263a2fa318540a91245d4d Module libqtga.so with build-id a01f1e48b261c1e740f789da12c6e8b3651a40a9 Module libqsvg.so with build-id 528eb97e6f2c08b91aac53de95cb672fbb997155 Module libQt5Pdf.so.5 with build-id ba6bf675e8a83e05b2736a3b2d6989059c6a6cf7 Module libqpdf.so with build-id d1c9dd818ead94b07e4e75c654e8457d45417448 Module libmng.so.2 with build-id 2de13b8bba73f358ab2e323aa2209c2e2fc886e7 Module libqmng.so with build-id f82452e874e7fb0bfcca0a9b87ede1725e221bf0 Module libjpeg.so.8 with build-id 879ca18a2f58c25d77ba881db3a44a5676ef6c7d Module libjasper.so.4 with build-id 062fa02a47172a8bf53b976a67eea42a61f37f0f Module libqjp2.so with build-id 53eef9e3520a681f5c424f67125bd2cb733932e9 Module libqicns.so
[kwin] [Bug 450451] kwin_wayland randomly crashed
https://bugs.kde.org/show_bug.cgi?id=450451 Erlend Ydse changed: What|Removed |Added Keywords||wayland CC||er.y...@pm.me -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487063] New: Bluetooth gets turned off after login, even with "On login: Enable Bluetooth"
https://bugs.kde.org/show_bug.cgi?id=487063 Bug ID: 487063 Summary: Bluetooth gets turned off after login, even with "On login: Enable Bluetooth" Classification: I don't know Product: kde Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: er.y...@pm.me Target Milestone: --- SUMMARY When turning on a laptop with paired bluetooth keyboard and mouse, the devices connect when it reaches the login screen, and I can type and click. After logging in however, the bluetooth tray icon is missing, and bluetooth is disabled. I have to manually turn it on again. This seems to apply regardless of the setting "On login: Enable Bluetooth" STEPS TO REPRODUCE 1. In System Settings > Bluetooth > Settings/Configure, set "On login" to "Enable Bluetooth" 2. Reboot (might need cold reboot) 3. After login, check if bluetooth is enabled OBSERVED RESULT After login, bluetooth is disabled EXPECTED RESULT Bluetooth being enabled after login SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-arch1-2 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION The bug is a bit flaky. Sometimes bluetooth gets enabled, other times it doesn't. I'll gladly supply logs if someone tells me how. This might have some connection to Bug 457130 or Bug 429519 -- You are receiving this mail because: You are watching all bug changes.
