Bug 1211561 - MicroOS Plasma Discover crash opening flatpakref
Summary: MicroOS Plasma Discover crash opening flatpakref
Status: CONFIRMED
Alias: None
Product: openSUSE Kalpa
Classification: openSUSE
Component: Flatpak (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P2 - High : Normal
Target Milestone: ---
Assignee: Shawn Dunn
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-05-19 19:59 UTC by rampxxxx none
Modified: 2024-06-05 22:01 UTC (History)
4 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
gerardo.gomez: needinfo? (rampxxxx)

Attachments
Discover crash in plasma (70.48 KB, image/png)
2023-05-19 19:59 UTC, rampxxxx none 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description rampxxxx none 2023-05-19 19:59:40 UTC 
Created attachment 867133 [details]
Discover crash in plasma

Opening a flatpak ref (space cadet pinball) downloaded from flathub.org to Download folder crash discover (double click from dolphin).
Comment 1 Shawn Dunn 2023-05-20 03:12:19 UTC 
Ok, so I'm having a hard time understanding what you did here.   

You downloaded the file com.github.k4zmu2a.spacecadetpinball.flatpakref manually from flathub, and then double-clicked on it in Dolphin?
Comment 2 rampxxxx none 2023-05-20 03:23:10 UTC 
(sorry for the bad explanation)
Yes,

- Download 'com.github.k4zmu2a.spacecadetpinball.flatpakref' from flathub.org.
- Double click on it in dolphin.
- Dolphin crashed.
Comment 3 Shawn Dunn 2023-05-20 16:00:55 UTC 
Confirmed, I've tried it with a handful of .flatpakref files downloaded from flathub.   Looking into it.
Comment 4 Shawn Dunn 2023-05-20 17:55:29 UTC 
https://bugs.kde.org/show_bug.cgi?id=470054
Comment 5 Shawn Dunn 2023-06-30 16:40:20 UTC 
Moving to openSUSE Kalpa Product
Comment 6 Gerardo Gomez Rodriguez 2024-06-05 22:01:14 UTC 
I was not able to reproduce this. Looks like this got fixed recently.

@rampxxxx can you try again?. The only gotcha is that opening from Dolphin (file browser) could look like nothing is happening but it takes a bit to show Discover. You should be able to follow the progress of discover by showing the journalctl logs, like: journalctl -b -f