Bug 417874

Summary: Segfault upon asking for Mobile Broadband PIN
Product: [Frameworks and Libraries] frameworks-modemmanager-qt Reporter: Calvin Hoy <calvin.f.hoy>
Component: generalAssignee: Jan Grulich <jgrulich>
Status: RESOLVED FIXED    
Severity: crash CC: calvin.f.hoy, jgrulich, kdelibs-bugs-null, lamarque, lukas.tinkl
Priority: NOR    
Version First Reported In: 5.67.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 5.18.1, 5.12.9
Sentry Crash Report:
Attachments: Backtrace

Description Calvin Hoy 2020-02-19 14:43:56 UTC
Created attachment 126163 [details]
Backtrace

SUMMARY
After upgrading to KDE Plasma 5.18, I've noticed that my tray icons sometimes disappear and custom keyboard shortcuts stopped working. I've managed to narrow the cause down to KDED5 failing to open the PIN entry dialogue for the mobile broadband modem.
I am not entirely sure if this is an issue specific to my install or machine, rather than KDED5, but it does occur consistently.

STEPS TO REPRODUCE
1. Plug in mobile broadband modem (wake up laptop).
2. Wait for mobile broadband modem to be detected (check in e.g. Modem Manager GUI).

EXPECTED RESULT
The built-in PIN entry dialog appears and functions as it did until now.

OBSERVED RESULT
KDED5 continually crashes with segmentation faults until PIN is entered another way (e.g. via Modem Manager GUI), eventually stops restarting. If KDED5 is restarted manually after PIN has been entered, it runs fine.

SOFTWARE/OS VERSIONS
openSUSE Tumbleweed 20200214
KDE Plasma Version: 5.18.0
KDE Frameworks Version: 5.67
Qt Version: 5.14.1
Kernel version: 5.5.1-1

ADDITIONAL INFORMATION
The KDE crash handler caught a backtrace, which I have attached below.
Comment 1 Calvin Hoy 2020-02-19 14:50:07 UTC
In addition, KDE also fails to put the system into standby while the modem is attached and detected by the OS.
systemctl suspend works, however.
Hibernation etc. are not affected.
Comment 2 Jan Grulich 2020-02-24 11:03:28 UTC
This has been fixed already.
Comment 3 Calvin Hoy 2020-02-24 11:09:58 UTC
Ahh, good to hear. When was this?
Comment 5 Calvin Hoy 2020-02-24 11:13:10 UTC
Ah I see, cheers! I'll close this, then.