Bug 497433

Summary: Discover crashes as soon as updates refreshed. IPv6 Problem
Product: [Applications] Discover Reporter: Jono <jonowaring>
Component: discoverAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aleixpol, nate
Priority: NOR    
Version First Reported In: 6.2.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jono 2024-12-13 22:34:10 UTC 
SUMMARY

Discover crashes as soon as updates refreshed. 


STEPS TO REPRODUCE
1. Open discover (Updates Refresh [by default])
2. Discover crashes (appears to be as soon as Updates refresh completes, before being able to click 'Update All')
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 41
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.10-300.fc41.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 5700 XT


ADDITIONAL INFORMATION

When trying to submit a crash report (KDE, Unable due to backtrace never completing), there was an error which included a comment to IPv6.

Disabling IPv6 on the system fixed the issue. Discover now does not crash, can update as normal.
Comment 1 Jono 2024-12-14 02:59:20 UTC 
Further,

Tried to recreate by enabling IPv6 on the network interface and restarting PC. Discover does not crash with IPv6 re-enabled. 

I had this same issue on two PC's, both I was using terminal to update for months until I found disabling IPv6 fixed the crashing problem. But as above, I am unable to now recreate the crashing behaviour, even despite undoing the change that fixed it.
Comment 2 Nate Graham 2024-12-16 20:33:16 UTC 
If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the `coredumpctl` command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl?

Thanks!
Comment 3 Bug Janitor Service 2024-12-31 03:47:25 UTC 
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2025-01-15 03:47:51 UTC 
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.