Bug 419175 - Discover crashes every time I try to open a .flatpakrepo file
Summary: Discover crashes every time I try to open a .flatpakrepo file
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: 5.18.3
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-24 09:40 UTC by smihael
Modified: 2020-05-14 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
attachment-12139-0.html (3.07 KB, text/html)
2020-03-24 16:50 UTC, smihael
Details

Note You need to log in before you can comment on or make changes to this bug.
Description smihael 2020-03-24 09:40:39 UTC
Application: plasma-discover (5.18.3)

Qt Version: 5.14.1
Frameworks Version: 5.68.0
Operating System: Linux 5.3.0-42-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.18

-- Information about the crash:
I tried to open this file with Discover to add repository: 
https://dl.flathub.org/repo/flathub.flatpakrepo

Discover crashed, before I could click on the green Install button.
This happens both with repos already in the list and those which are not on the list (in Settings).

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated
Comment 1 smihael 2020-03-24 09:41:40 UTC
Adding works fine if I add repo by adding url directly in the settings view.
Comment 2 Kai Uwe Broulik 2020-03-24 12:56:08 UTC
Without a backtrace there's not much we can do
Comment 3 smihael 2020-03-24 16:50:25 UTC
Created attachment 126986 [details]
attachment-12139-0.html

I dont get any more information even with debug symbols enabled.

Maybe terminal output helps

invalid kns backend! "/usr/share/knsrcfiles/ksysguard.knsrc" because:
"Config group not found! Check your KNS3 installation."
adding empty sources model QStandardItemModel(0x556ea39b09e0)
org.kde.plasma.libdiscover: Couldn't find a category for  "fwupd-backend"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21:
Unable to assign [undefined] to double
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/FormLayout.qml:112:21:
Unable to assign [undefined] to double
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:44:9:
QML ActionToolBar: Binding loop detected for property "actions"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/ToolBarPageHeader.qml:44:9:
QML ActionToolBar: Binding loop detected for property "actions"
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 100 and type 'Write', disabling...
QSocketNotifier: Invalid socket 99 and type 'Read', disabling...
QSocketNotifier: Invalid socket 96 and type 'Read', disabling...
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasma-discover path = /usr/bin pid = 3563
KCrash: Arguments: /usr/bin/plasma-discover
/home/smihael/Downloads/flathub.flatpakrepo
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit
sock_file=/run/user/1000/kdeinit5__0



On Tue, 24 Mar 2020 at 13:56, Kai Uwe Broulik <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=419175
>
> Kai Uwe Broulik <kde@privat.broulik.de> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |BACKTRACE
>                  CC|                            |kde@privat.broulik.de
>
> --- Comment #2 from Kai Uwe Broulik <kde@privat.broulik.de> ---
> Without a backtrace there's not much we can do
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Bug Janitor Service 2020-04-08 04:33:12 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 5 Christoph Feck 2020-04-14 14:24:55 UTC
Please ask for help in a forum of your distribution how to provide a backtrace.

More information is also available at https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 6 Bug Janitor Service 2020-04-29 04:33:13 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 7 Bug Janitor Service 2020-05-14 04:33:13 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!