| Summary: | Crash when using Discover along with Yast | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | honzamison |
| Component: | discover | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | bburgess, bogdanstefan, brynncantelon, chouinard, DShelley1992, edgar.nash, ifjkisstamas, kde, larrosa, Mohammed_ElAfifi, nate, nuaanjzizy |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.12.4 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/discover/6ee190414604f471327fc9613c96f246047d6ac2 | Version Fixed In: | 5.12.5 |
| Sentry Crash Report: | |||
| Attachments: |
zypper_lr_-d
bug.txt bug2.txt New crash information added by DrKonqi |
||
|
Description
honzamison
2018-04-10 15:30:55 UTC
Some questions in order to have more information... Can you write here the output of running "zypper lr -d" ? Just to try to reproduce your system configuration. Did you run "zypper dup" to update your system recently? I tried updating my system and can't reproduce this (nor I could reproduce it before updating) Can you reproduce the problem without yast running in the background? and after a system restart? Created attachment 111965 [details] zypper_lr_-d Hi, i did not run zypper dup recently and the problem only appear when i have yast software management running on the background. Discovery->settings throw segfault only if yast software management is running on the background but when i start discovery and then software management both seems to work fine. On Wed, Apr 11, 2018 at 1:10 PM, Antonio Larrosa <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=392971 > > Antonio Larrosa <larrosa@kde.org> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > CC| |larrosa@kde.org > > --- Comment #1 from Antonio Larrosa <larrosa@kde.org> --- > Some questions in order to have more information... > > Can you write here the output of running "zypper lr -d" ? Just to try to > reproduce your system configuration. > > Did you run "zypper dup" to update your system recently? I tried updating > my > system and can't reproduce this (nor I could reproduce it before updating) > > Can you reproduce the problem without yast running in the background? and > after > a system restart? > > -- > You are receiving this mail because: > You reported the bug. > *** Bug 393235 has been marked as a duplicate of this bug. *** Seems like it happens in Fedora too, so it's possibly not an opensuse thing. Could you run it from the terminal and tell me if you get something like "Discarding invalid backend "something.knsrc""? Created attachment 112234 [details] bug.txt Hi, bug.txt is all i get after i start discover from terminal with yast swmanager running on the background and clicking settings in it. without yast swmanager running on the background i get bug2.txt On Mon, Apr 23, 2018 at 12:48 PM, Aleix Pol <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=392971 > > --- Comment #4 from Aleix Pol <aleixpol@kde.org> --- > Seems like it happens in Fedora too, so it's possibly not an opensuse > thing. > > Could you run it from the terminal and tell me if you get something like > "Discarding invalid backend "something.knsrc""? > > -- > You are receiving this mail because: > You reported the bug. > Created attachment 112235 [details]
bug2.txt
Seems like Yast being open locks the zypper db and makes Discover go crazy. *** Bug 393874 has been marked as a duplicate of this bug. *** *** Bug 393884 has been marked as a duplicate of this bug. *** Those last two duplicates have the backtrace, but are from Ubuntu 18.04. Looks like it's not just YaST that does this. Created attachment 112467 [details]
New crash information added by DrKonqi
plasma-discover (5.12.4) using Qt 5.10.1
- What I was doing when the application crashed:
When I open discover and try to go to "Settings", the app crashes. Before it crashes, it shows an error message saying the following: "Error when getting information for file "/var/cache/PackageKit/28/metadata/rpmfusion-nonfree/repodata/appstream.xml.gz": No such file or directory".
-- Backtrace (Reduced):
#7 0x00007ff18704fbc0 in AbstractResourcesBackend::Filters::shouldFilter(AbstractResource*) const () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#8 0x00007ff18704ff6b in AbstractResourcesBackend::Filters::filterJustInCase(QVector<AbstractResource*>&) const () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#9 0x00007ff187047446 in ResourcesProxyModel::addResources(QVector<AbstractResource*> const&) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
[...]
#11 0x00007ff187060636 in ResultsStream::resourcesFound(QVector<AbstractResource*> const&) () from /usr/lib64/plasma-discover/libDiscoverCommon.so
#12 0x00007ff18703f6dc in AggregatedResultsStream::emitResults() () from /usr/lib64/plasma-discover/libDiscoverCommon.so
*** Bug 393979 has been marked as a duplicate of this bug. *** *** Bug 394258 has been marked as a duplicate of this bug. *** *** Bug 394225 has been marked as a duplicate of this bug. *** Git commit 6ee190414604f471327fc9613c96f246047d6ac2 by Aleix Pol. Committed on 15/05/2018 at 15:46. Pushed by apol into branch 'Plasma/5.12'. Fix crash When removing resources, remove its references as well. M +5 -0 libdiscover/backends/PackageKitBackend/PackageKitBackend.cpp https://commits.kde.org/discover/6ee190414604f471327fc9613c96f246047d6ac2 *** Bug 394722 has been marked as a duplicate of this bug. *** *** Bug 395270 has been marked as a duplicate of this bug. *** *** Bug 395551 has been marked as a duplicate of this bug. *** |