https://bugs.kde.org/show_bug.cgi?id=524933
Bug ID: 524933
Summary: plasma-nm: permanent main-thread deadlock in blocking
QDBusConnection::call() from accessPointAdded signal
handler
Classification: Plasma
Product: plasmashell
Version First 6.7.4
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: Networks widget
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
Created attachment 195602
--> https://bugs.kde.org/attachment.cgi?id=195602&action=edit
gdb thread apply all bt from SIGABRT core
DESCRIPTION
Desktop was working and when I was using firefox, it rendered something basic
(not substantial), and suddenly firefox locked as did the panel and 2nd desktop
wallpaper turned black. Windows stayed open but could not click on system try
or utilize print screen. Hotkeys worked to bring up a terminal, however. Not
sure if firefox is related or coincidence is something I can't tell as I dont
see it in any of the backtrace logs.
STEPS TO REPRODUCE
Spontaneous but,
1. Running Wifi and Ethernet uplinks w/ 28 APs nearby
2. nordvpn is running in tray
3. spotify, discord, steam icons in tray
OBSERVED RESULT
System tray and panel unresponsive and 2nd screen wallpaper black from 7:49:18
onward. I could use hot keys and other commands. Print screen app/hot key did
not work, however. Was unusable until I ran systemctl --user restart
plasma-plasmashell.service.
EXPECTED RESULT
blocking d-bus calls in the networks widget should not permanently deadlock
plasmashell.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
Qt Version: 6.11.1
Kernel Version: 7.1.9-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × 13th Gen Intel® Core™ i9-13900
Memory: 64 GiB of RAM (62.5 GiB usable)
Graphics Processor: AMD Radeon Pro W6600
ADDITIONAL INFORMATION
- Panel/tray became permanently unresponsive; KWin, hotkeys, and all apps
stayed fine. Hung at 7:49:18 until I killed it ~30min later.
- Main thread stuck in QDBusConnection::call() (blocking) issued from
NetworkManager::AccessPoint::AccessPoint() → retrieveInitialProperties(),
called from within accessPointAdded signal delivery — i.e. from inside
QDBusConnectionPrivate::deliverCall(). Full trace attached.
- Two eu-stack samples 5s apart were byte-identical → deadlock, not slow-loop.
- The 25s QDBus timeout never fired.
- Only log line at time of hang: QSocketNotifier: Socket notifiers cannot be
enabled or disabled from another thread
-NetworkManager itself healthy — nmcli -t device show wls5f3 returns in 10ms,
28 APs visible.
- With Q_DBUS_BLOCKING_CALL_MAIN_THREAD_WARNING_MS=0: ~50 consecutive blocking
GetAll calls on /AccessPoint/*, one per AP, on the main thread. Log attached.
- Versions: NetworkManager 1.56.1
- Relates to Bug 409392 (closed) — same code path, but that bug describes
temporary freezes; this is a permanent hang.
--
You are receiving this mail because:
You are watching all bug changes.
