Bug 462011

Summary: Flatpak install issue
Product: [Applications] Discover Reporter: Chuzu Nix <nixchuz>
Component: discoverAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aleixpol, nate
Priority: NOR Keywords: drkonqi
Version: 5.26.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Chuzu Nix 2022-11-18 21:32:07 UTC 
Application: plasma-discover (5.26.3)

Qt Version: 5.15.7
Frameworks Version: 5.100.0
Operating System: Linux 6.0.8-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.3 [KCrashBackend]

-- Information about the crash:
When trying to install flatpak, discover install comes up but there is no install button and discover eventually crashes.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault

[KCrash Handler]
#4  0x00007fd859ef6347 in QMutex::lock() () from /lib64/libQt5Core.so.5
#5  0x00007fd85a0ddfe4 in QCoreApplicationPrivate::lockThreadPostEventList(QObject*) () from /lib64/libQt5Core.so.5
#6  0x00007fd85a0df5c9 in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /lib64/libQt5Core.so.5
#7  0x00007fd81014afbc in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so
#8  0x00007fd85a1132cd in ?? () from /lib64/libQt5Core.so.5
#9  0x00007fd859eff8d5 in QFutureWatcherBase::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007fd85b3a53fe in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007fd85a0dc128 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#12 0x00007fd85a0df0c1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#13 0x00007fd85a134353 in ?? () from /lib64/libQt5Core.so.5
#14 0x00007fd85891ca90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#15 0x00007fd85891ce48 in ?? () from /lib64/libglib-2.0.so.0
#16 0x00007fd85891cedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#17 0x00007fd85a133b56 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#18 0x00007fd85a0dab9b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#19 0x00007fd85a0e2d06 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#20 0x000055a6f4a021d0 in ?? ()
#21 0x00007fd85982c5b0 in __libc_start_call_main () from /lib64/libc.so.6
#22 0x00007fd85982c679 in __libc_start_main_impl () from /lib64/libc.so.6
#23 0x000055a6f4a02ba5 in ?? ()
[Inferior 1 (process 4968) detached]

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

Reported using DrKonqi
Comment 1 Nate Graham 2022-11-29 20:18:13 UTC 
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong:

> #7  0x00007fd81014afbc in ?? () from /usr/lib64/qt5/plugins/discover/flatpak-backend.so

Could you please install debug symbols for Discover's flatpak backend package, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Thanks again!
Comment 2 Bug Janitor Service 2022-12-14 05:14:06 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 3 Bug Janitor Service 2022-12-29 05:25:41 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!