Summary: | Discover crashed in flatpak_dir_list_refs() when closing just after an update | ||
---|---|---|---|
Product: | [Applications] Discover | Reporter: | Rodrigo Pedra Brum <rodrigo.pedra> |
Component: | Flatpak Backend | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | aleixpol, fsw0422, jgrulich, kde, matt.fagnani, nate, qydwhotmail, rooksy, sitter, travier |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.25.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
Rodrigo Pedra Brum
2022-10-06 20:37:23 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: #6 0x00007f04d44decd2 in () at /usr/lib64/qt5/plugins/discover/flatpak-backend.so #7 0x00007f04d44def39 in () at /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! 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! Hey Nate, Sorry for not responding earlier, somehow the e-mails for this but report got sent to a different tag in my GMail. I often update through CLI and seldom through Discover, but I will try to replicate the bug as soon as I get a flatpak update. Thanks for looking into it. Nate, I tried twice this week and I can't replicate it anymore. I will close the bug for now, and if I can replicate it I will reopen it again. Thanks! (In reply to Rodrigo Pedra Brum from comment #4) > Nate, > > I tried twice this week and I can't replicate it anymore. I will close the > bug for now, and if I can replicate it I will reopen it again. > > Thanks! For what its worth, I can recreate it every time. It only happens when it completes an actual update. Its been happening for a couple of months now. Here's the KDE Crash Handler output from the latest crash ... Executable: plasma-discover PID: 5434 Signal: Segmentation fault (11) Time: 11/7/22 7:02:42 PM PST Application: plasma-discover (5.24.7) Qt Version: 5.15.3 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-52-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.04.1 LTS DrKonqi: 5.24.5 [KCrashBackend] Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x00007f0936e43275 in QQuickWindow::mouseGrabberItem() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x00007f0936e45aef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x00007f0936e2d195 in QQuickItemPrivate::derefWindow() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x00007f0936e2dd58 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x00007f0936e2e03c in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x00007f0936faf859 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x00007f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x00007f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x00007f0936faf859 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x00007f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x00007f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x00007f0936fb0789 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #16 0x00007f09352a2a6e in QObjectPrivate::deleteChildren() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x00007f09352ad924 in QObject::~QObject() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x00007f08f827b609 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #19 0x00007f0935cac463 in QV4::MemoryManager::sweep(bool, void (*)(char const*)) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x00007f0935cac5a9 in QV4::MemoryManager::~MemoryManager() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x00007f0935d290e4 in QV4::ExecutionEngine::~ExecutionEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x00007f0935d137e2 in QJSEngine::~QJSEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x00007f0935ef1a3d in QQmlApplicationEngine::~QQmlApplicationEngine() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x0000556ec8d19411 in ?? () #25 0x0000556ec8d1943d in ?? () #26 0x00007f09352a51c3 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x00007f0936423713 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x00007f0935277e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x00007f093527af27 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x00007f093527ed0c in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x0000556ec8d17838 in ?? () #32 0x00007f0934b95d90 in __libc_start_call_main (main=main@entry=0x556ec8d16f40, argc=argc@entry=3, argv=argv@entry=0x7ffe6faa6ef8) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x00007f0934b95e40 in __libc_start_main_impl (main=0x556ec8d16f40, argc=3, argv=0x7ffe6faa6ef8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe6faa6ee8) at ../csu/libc-start.c:392 #34 0x0000556ec8d18275 in ?? () [Inferior 1 (process 5434) detached] Adrian, your backtrace looks different so I think it's a different crash. If you can truly reproduce it 100%, please do file a new bug report for it. Thanks! (In reply to Nate Graham from comment #6) > Adrian, your backtrace looks different so I think it's a different crash. If > you can truly reproduce it 100%, please do file a new bug report for it. > Thanks! I've tired to use the "Report Bug" button on the "Discover -- The KDE Crash Handler" window, but it keeps telling me "This report does not contain enough information for the developers, so the automated bug reporting process is not enabled for this crash". I select 'Yes'/'Every time'/'What I was doing when the application "Discover" crashed' options of "What do you know about the crash?". That probably means you don't have debug symbols installed. (In reply to Nate Graham from comment #8) > That probably means you don't have debug symbols installed. That stack trace isn't enough? Seems like an uphill fight just to do the right thing and report a bug. :/ Indeed, unfortunately some distros don't make it easy. I wish they all did. No, the stack trace is not enough if it's missing debug symbols. That makes it impossible to debug, except for *maybe* identifying the issue as a duplicate of another one. Created attachment 155103 [details]
New crash information added by DrKonqi
plasma-discover (5.26.80) using Qt 5.15.7
Discover crashed after the window is closed. From the backtrace flatpak and gio were involved.
-- Backtrace (Reduced):
#6 0x00007f1a1620449b in g_cancellable_is_cancelled (cancellable=cancellable@entry=0x55bac21e7420) at ../gio/gcancellable.c:297
#7 0x00007f1a162044be in g_cancellable_set_error_if_cancelled (cancellable=cancellable@entry=0x55bac21e7420, error=error@entry=0x0) at ../gio/gcancellable.c:314
#8 0x00007f1a16215c21 in g_file_query_info (file=0x7f199fc56380, attributes=0x7f1a1631342e "standard::type", flags=G_FILE_QUERY_INFO_NONE, cancellable=0x55bac21e7420, error=0x0) at ../gio/gfile.c:1324
#9 0x00007f1a16215db9 in g_file_query_exists (file=file@entry=0x7f199fc56380, cancellable=cancellable@entry=0x55bac21e7420) at ../gio/gfile.c:1219
#10 0x00007f1a03ec5e29 in flatpak_dir_list_refs (self=0x7f199f898080 [FlatpakDir], kinds=FLATPAK_KINDS_APP, cancellable=0x55bac21e7420, error=0x7f19e0dfca68) at common/flatpak-dir.c:6613
Created attachment 155140 [details]
New crash information added by DrKonqi
plasma-discover (5.26.80) using Qt 5.15.7
Crashed again after closing Discover
-- Backtrace (Reduced):
#6 0x00007f68f300449b in g_cancellable_is_cancelled (cancellable=cancellable@entry=0x55dcc4e3a820) at ../gio/gcancellable.c:297
#7 0x00007f68f30044be in g_cancellable_set_error_if_cancelled (cancellable=cancellable@entry=0x55dcc4e3a820, error=error@entry=0x0) at ../gio/gcancellable.c:314
#8 0x00007f68f3015c21 in g_file_query_info (file=0x7f689074e800, attributes=0x7f68f311342e "standard::type", flags=G_FILE_QUERY_INFO_NONE, cancellable=0x55dcc4e3a820, error=0x0) at ../gio/gfile.c:1324
#9 0x00007f68f3015db9 in g_file_query_exists (file=file@entry=0x7f689074e800, cancellable=cancellable@entry=0x55dcc4e3a820) at ../gio/gfile.c:1219
#10 0x00007f68dff2ce29 in flatpak_dir_list_refs (self=0x7f689c210620 [FlatpakDir], kinds=FLATPAK_KINDS_APP, cancellable=0x55dcc4e3a820, error=0x7f68b5bbca68) at common/flatpak-dir.c:6613
Created attachment 157650 [details]
New crash information added by DrKonqi
plasma-discover (5.24.7) using Qt 5.15.3
- What I was doing when the application crashed:
Whenever I update software with Discover and close the window, it crashes
- Unusual behavior I noticed:
It only happens after I update apps. If I just open Discover and close window, it doesn't happen
- Custom settings of the application:
There is not custom settings. I use KDE Plasma 5.24.7 and Ubuntu 22.04.2 LTS
-- Backtrace (Reduced):
#4 0x00007f89c5ad0275 in QQuickWindow::mouseGrabberItem() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5 0x00007f89c5ad2aef in QQuickWindowPrivate::removeGrabber(QQuickItem*, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6 0x00007f89c5aba195 in QQuickItemPrivate::derefWindow() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7 0x00007f89c5abad58 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#8 0x00007f89c5abb03c in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
Created attachment 158107 [details]
New crash information added by DrKonqi
plasma-discover (5.27.4) using Qt 5.15.8
Discover was installing a flatpak in the background, and after the flatpak was installed, Discover crashed.
-- Backtrace (Reduced):
#6 0x00007f258dbd745b in g_cancellable_is_cancelled (cancellable=cancellable@entry=0x555ee9145240) at ../gio/gcancellable.c:304
#7 0x00007f258dbd747e in g_cancellable_set_error_if_cancelled (cancellable=cancellable@entry=0x555ee9145240, error=error@entry=0x0) at ../gio/gcancellable.c:321
#8 0x00007f258dbe8221 in g_file_query_info (file=0x7f24ec2223d0, attributes=0x7f258dce1bee "standard::type", flags=G_FILE_QUERY_INFO_NONE, cancellable=0x555ee9145240, error=0x0) at ../gio/gfile.c:1324
#9 0x00007f258dbe8389 in g_file_query_exists (file=file@entry=0x7f24ec2223d0, cancellable=cancellable@entry=0x555ee9145240) at ../gio/gfile.c:1219
#10 0x00007f256105d159 in flatpak_dir_list_refs (self=0x7f24ec018bb0 [FlatpakDir], kinds=FLATPAK_KINDS_APP, cancellable=0x555ee9145240, error=0x7f25467fba58) at common/flatpak-dir.c:6618
*** Bug 439619 has been marked as a duplicate of this bug. *** *** Bug 481698 has been marked as a duplicate of this bug. *** I am wondering if maybe we are simply closing resources out from under the flatpak worker thread. Is anyone able to reproduce this on 6.x? 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! 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! |