Bug 440373

Summary: Discover crash
Product: [Applications] Discover Reporter: Jim Lemon <drjimlemon>
Component: discoverAssignee: Dan Leinir Turthra Jensen <leinir>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aleixpol, jodr666, nate
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.21.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Jim Lemon 2021-07-28 23:21:05 UTC
Application: plasma-discover (5.21.4)

Qt Version: 5.15.2
Frameworks Version: 5.80.0
Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.21.3
Distribution: Fedora 34 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:

I had just installed Google Chrome on Fedora 34 that I had installed the night before and cllicked on Updates (778). The Discover window disappeared. When I ran Discover from the upgrade icon on the bottom right of the screen, it showed Update (779). I again selected install all updates. It hung at 24% and when I clicked "Cancdel" this error message appeared:

Package not found Curl error (42): Operation was aborted by an application callback for https://fedora.mirror.digitalpacific.com.au/linux/updates/34/Everything/x86_64/Pasckages/g/glibc-all-langpacks-2.33-20.fc34.x86_64.rpm
[Callback aborted]: Last error: Curl error (42): Operation was aborted by an application callback for https://fedora.mirror.digitalpacific.com.au/linux/updates/34/Everything/x86_64/Pasckages/g/glibc-all-langpacks-2.33-20.fc34.x86_64.rpm
[Callback aborted]

I had to manually type in the above as I could not select the error message from the Discover window.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted

[KCrash Handler]
#4  0x00007f74b6419292 in raise () from /lib64/libc.so.6
#5  0x00007f74b64028a4 in abort () from /lib64/libc.so.6
#6  0x00007f74b687b42d in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5
#7  0x00007f74b4db7ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5
#8  0x00007f74b4dc66fa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5
#9  0x00007f74b6a794fd in void doActivate<false>(QObject*, int, void**) () from /lib64/libQt5Core.so.5
#10 0x00007f74b6a9578b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#11 0x00007f74b6a479b2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#12 0x00007f74b6a4f544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#13 0x0000561a767aa6cb in main ()
[Inferior 1 (process 5651) detached]

The reporter indicates this bug may be a duplicate of or related to bug 440370.

Possible duplicates by query: bug 440370, bug 440291, bug 440257, bug 440137, bug 440080.

Reported using DrKonqi
Comment 1 Tony 2021-07-29 21:10:36 UTC
Report is missing debug symbols, also: 

#7  0x00007f74b4db7ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5

Wayland crashed and took discover down.
Comment 2 Nate Graham 2021-07-29 23:32:35 UTC
Yep. Did KWin crash too? If so, can you attach a backtrace of the KWin crash. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
Comment 3 Bug Janitor Service 2021-08-13 04:36:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2021-08-28 04:36:47 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!