Bug 480619

Summary: Doesnt detect --user repository until a failed attempt to "add the flathub remote"
Product: [Applications] Discover Reporter: Henning <boredsquirrel>
Component: Flatpak BackendAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: minor CC: aleixpol, jgrulich, john.liptrot, nate, travier
Priority: NOR Keywords: qt6
Version First Reported In: 5.92.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Henning 2024-01-31 19:46:51 UTC
1. Close Discover (GUI)

2. Add the user flathub remote

flatpak remote-add --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak remote-delete --system flathub

3. Open Discover and its "repos"  section
It does not detect that repo i.e. it didnt fully close on GUI close.

4. Press the "add flathub" button. This will try to add it systemwide which requires an additional group for nonwheel users. Cancel the addition.

Now Discover reloads and shows the user flathub repo. But it has no icon.

This is a minor issue. Best would be to allow adding the flathub repo systemwide or only for this user on choice. Adding only for this user doesnt need any password prompt too.

Specified App:
kdsoap-ws-discovery-client-0.3.0-1.fc40.x86_64
plasma-discover-libs-5.92.0-3.fc40.x86_64
plasma-discover-5.92.0-3.fc40.x86_64
plasma-discover-flatpak-5.92.0-3.fc40.x86_64
plasma-discover-rpm-ostree-5.92.0-3.fc40.x86_64
plasma-discover-notifier-5.92.0-3.fc40.x86_64

flatpak 1.15.6
--- Software ---
OS: Fedora Linux 40.20240130.0 (Kinoite Prerelease)
KDE Plasma: 5.92.0
Comment 1 Nate Graham 2024-02-06 23:01:15 UTC
> It does not detect that repo i.e. it didnt fully close on GUI close.
What leads yo to the conclusion that Discover didn't fully close? Did you verify this with `ps -e | grep -i discover`? Or was that a guess?
Comment 2 Henning 2024-02-06 23:08:54 UTC
I  got the idea that it doesnt really close due to the updater indicator often present even after closing it. And the fact that it didnt reload the available repos too
Comment 3 Nate Graham 2024-02-06 23:31:44 UTC
Ok, can you verify your theory by doing what I suggested?
Comment 4 Henning 2024-02-07 10:32:52 UTC
2332 ?        00:00:01 DiscoverNotifie

This process is still running after closing discover.

reproducing:

>> flatpak remote-delete --force --user flathub
>> pkg-config refresh
# discover not opened manually until now
>> plasma-discover (through GUI, had no internet connection for some reason, didnt show flathub)
>> flatpak remote-add --user flathub https://dl.flathub.org/repo/flathub.flatpakrepo
>> plasma-discover
org.kde.plasma.libdiscover: OdrsReviewsBackend: Fetch ratings: false
Couldn't get latest commit for [all my flatpak apps listed here]

So I assume plasma-discover was not running as I invoked it via Terminal. Closed the process through terminal.

Now launched Discover again, flathub (user) is showing up.

This is strange, as it should have shown up before. But this is pretty minor, may be possible to close.
Comment 5 Henning 2024-02-07 10:33:35 UTC
and that spello in the first line is not me. I think that is this bug

https://bugs.kde.org/show_bug.cgi?id=479037

seems to be a rendering issue in konsole?
Comment 6 Nate Graham 2024-02-07 17:27:54 UTC
That's DiscoverNotifier, not Discover. Different processes. So it looks like Discover is not still running in the background.
Comment 7 john.liptrot 2025-10-10 19:10:04 UTC
Hi Henning,

Is this still an issue for you?

I've tested this and cannot reproduce this issue.

Thanks.

Operating System: KDE Linux 2025-10-10
KDE Plasma Version: 6.5.80
KDE Frameworks Version: 6.20.0
Qt Version: 6.9.2
Kernel Version: 6.17.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 2 × Intel® Pentium® 3805U @ 1.90GHz
Memory: 4 GiB of RAM (3.7 GiB usable)
Graphics Processor: Intel® HD Graphics
Manufacturer: LENOVO
Product Name: 80EW
System Version: Lenovo B50-80
Comment 8 Bug Janitor Service 2025-10-25 03:47:43 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2025-11-09 03:47:52 UTC
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.