View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006602 | DarkRadiant | GUI | public | 12.01.2025 22:00 | 12.01.2025 22:01 |
Reporter | YourHotGothAunt | Assigned To | |||
Priority | normal | Severity | crash | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Flatpak | OS | Gentoo Linux | OS Version | ~amd64 |
Product Version | 3.9.0 | ||||
Summary | 0006602: Flatpak build of DarkRadiant still crashes when opening Light Inspector | ||||
Description | The Flatpak version of DarkRadiant still crashes when you try to open the light inspector. Building and running directly on the host resolves the crash, at least in my case. I wasn't witness to the original crash bug that was present prior to 3.8.0, but the fact that it *only* occurs in Flatpak makes me think this isn't necessarily a duplicate of that crash, or a regression. | ||||
Steps To Reproduce | * Open DarkRadiant via Flatpak. * Open the Light Inspector (whether a map is loaded or not is irrelevant). | ||||
Additional Information | Willing to attach a crash dump, my only blocker is "I don't know how to get one out of GDB while in Flatpak." Official Flatpak documentation instructions [1] can launch GDB, but I can't get any useful information out of it even with debug symbols installed(?). I'm also more likely to just keep the host-built version installed, and uninstall the Flatpak version after I've gotten you a crash dump. I just thought I'd at least come start the crash report process first. [1]: https://docs.flatpak.org/en/latest/debugging.html | ||||
Tags | No tags attached. | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
12.01.2025 22:00 | YourHotGothAunt | New Issue | |
12.01.2025 22:01 | YourHotGothAunt | Additional Information Updated | |
12.01.2025 22:01 | YourHotGothAunt | Additional Information Updated | |
12.01.2025 22:01 | YourHotGothAunt | Note Added: 0016948 |