Bug 388990 - Discover fails to install flatpak application
Summary: Discover fails to install flatpak application
Status: RESOLVED NOT A BUG
Alias: None
Product: Discover
Classification: Applications
Component: Flatpak Backend (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-15 07:18 UTC by Mustafa Muhammad
Modified: 2018-01-17 05:12 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mustafa Muhammad 2018-01-15 07:18:43 UTC
Discover fails to install an application, I tested Telegram, I started Discover from terminal and got this log:

mustafa@mustafa-pc:~$ plasma-discover 
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not found! Check your KNS3 installation."
Discarding invalid backend "ksysguard.knsrc"
Discarding invalid backend "servicemenu.knsrc"
setting currentApplicationBackend PackageKitBackend(0x21e4ee0)
Failed to install "org.telegram.desktop" : "GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file does not start with a group"

Using Neon dev git-unstable, Discover version 5.11.90
With flatpak backend installed
Comment 1 Mustafa Muhammad 2018-01-15 07:36:28 UTC
OK, the problem is probably in flatpak, it didn't install it from console too:

mustafa@mustafa-pc:~$ flatpak install flathub org.telegram.desktop
Installing: org.telegram.desktop/x86_64/stable from flathub
[####################] 1 metadata, 0 content objects fetched; 569 B transferred in 1 se
error: GDBus.Error:org.freedesktop.DBus.Error.Failed: Error deploying: Key file does not start with a group
Comment 2 Aleix Pol 2018-01-15 12:04:44 UTC
Please check your installation.
Comment 3 Mustafa Muhammad 2018-01-17 05:12:33 UTC
(In reply to Aleix Pol from comment #2)
> Please check your installation.

Yes, it was fixed by the upstream flatpak fix, thank you.