Bug 399683 - fwupd crashes discover
Summary: fwupd crashes discover
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: fwupd Backend (show other bugs)
Version: 5.14.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Abhijeet Sharma
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-11 23:07 UTC by John Ramsden
Modified: 2018-10-16 23:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John Ramsden 2018-10-11 23:07:01 UTC 
SUMMARY

fwupd crashes discover if it's enabled. I end up getting a segmentation fault. Using fwupd and plasma from arch.

STEPS TO REPRODUCE
1. Start discover
2. Check for updates with lvfs enabled
3. Wait for segfault

SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.0
Qt Version: 5.11.2
KDE Frameworks Version: 5.50.0
Kernel Version: 4.18.12-arch1-1-ARCH
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
Memory: 31.4 GiB of RAM
Comment 1 Neousr 2018-10-12 16:25:04 UTC 
I was able to see this in action a couple of times. But after today updates i no longer able to reproduce it.

If you continue to be affected a backtrace is needed you can find more info in the crash reports section on https://community.kde.org/Get_Involved/Bug_Reporting
Comment 2 Aleix Pol 2018-10-16 12:22:10 UTC 
Please provide at least the information Neousr asked or steps to reproduce.

I'm running locally ARchLinux and don't experience this issue. Could very well be that it's already fixed.
Comment 3 Neousr 2018-10-16 15:37:22 UTC 
Since lvfs wasn't working as expected Bug 399653 there was no way to replicate, so it seems that this can be a duplicate of Bug 397863 since it stopped after 5.51 landed. So unless a backtrace is added i don't think more can be done.
Comment 4 Aleix Pol 2018-10-16 23:04:05 UTC 
Let's assume it's fixed, I fixed a bunch of issues in fwupd for 5.14.1 anyway. If a new one happens, please report a new bug.