[plasmashell] [Bug 523890] New: kded6 crashes when scanning Wi-Fi QR code in Plasma NetworkManager applet

https://bugs.kde.org/show_bug.cgi?id=523890

            Bug ID: 523890
           Summary: kded6 crashes when scanning Wi-Fi QR code in Plasma
                    NetworkManager applet
    Classification: Plasma
           Product: plasmashell
      Version First master
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Networking in general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

Created attachment 194872
  --> https://bugs.kde.org/attachment.cgi?id=194872&action=edit
crash log for kde6 after QR code scan

DESCRIPTION
kded6 crashes when attempting to scan/import a Wi-Fi connection using a QR code
from the Plasma NetworkManager applet.

STEPS TO REPRODUCE
1. Open the Plasma NetworkManager applet from the system tray.
2. Open the Wi-Fi section.
3. Select the option to scan/import a Wi-Fi QR code.
4. Provide a valid Wi-Fi QR code that wasn't scanned/saved previously.
5. Wifi successfully connects to the provided network.
6. Observe that kded6 crashes at the same time as step 5.

OBSERVED RESULT
kded6 crashes while processing the QR code.

EXPECTED RESULT
kded6 should continue running normally.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.3
KDE Frameworks Version: 6.28.0
Qt Version: 6.11.1
Kernel Version: 7.1.5-201.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 32 GiB of RAM (27.3 GiB usable)
Graphics Processor: AMD Radeon Graphics


ADDITIONAL INFORMATION
kde6 has been updated with the Plasma Frameworks version 6.28.0 on Fedora KDE
44 since I last observed this crash. I have faced this issues 3 times in the
last 3 weeks (13th July, 25th July and 4th August). 

Full crash log is in the "PID 2479 (kded6).txt" file attached with this bug
report.

The timestamps are wrong in my crash report probably because I was travelling
between different time zones.

Possibly related to bugs --> 522313 and 523807

-- 
You are receiving this mail because:
You are watching all bug changes.