|
Bugzilla – Full Text Bug Listing |
| Summary: | MicroOS Plasma Discover crash opening flatpakref | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Kalpa | Reporter: | rampxxxx none <rampxxxx> |
| Component: | Flatpak | Assignee: | Shawn Dunn <sfalken> |
| Status: | CONFIRMED --- | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | gerardo.gomez, rampxxxx, sfalken, stacheldrahtje |
| Version: | Current | Flags: | gerardo.gomez:
needinfo?
(rampxxxx) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Discover crash in plasma | ||
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? (sorry for the bad explanation) Yes, - Download 'com.github.k4zmu2a.spacecadetpinball.flatpakref' from flathub.org. - Double click on it in dolphin. - Dolphin crashed. Confirmed, I've tried it with a handful of .flatpakref files downloaded from flathub. Looking into it. Moving to openSUSE Kalpa Product 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 |
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).