I once again require a Debian package of Slade 3.1.13

I decided to test this out before commenting, and this was quite a journey. A short one, but still a journey. Disclaimer: I do my editing in Windows on my gaming PC, but have several Linux systems serving various purposes.

To start, I followed the instructions for installing Slade on Linux. Running Ubuntu, flatpak is not installed by default so I installed it. Canonical must not care about flatpak (of course not) because it had zero configurations despite being in their apt repo. While I could install flatpak itself, flatpak was not able to find Slade because flatpak could not even initialize to the point it could look for anything.

Option two: deb package.

The instructions for adding the repository actually broke apt to the point that apt update failed. I had to revert their changes manually.

Option three: compile from source and stuff the results in /home/<user>/bin. I may try this later when I have more time.

Anyway, back to your question: I think rather than relying on older versions of the software, we should figure out what is it about the current version that breaks then submit a PR to fix it. I am willing to take a stab at this, assuming I encounter any problems running Slade 3.2.5. I just have not bothered using Linux for Doom editing until a few minutes ago.

Sorry this does not directly answer your question, but I did want to throw it out there that this was already on my todo list. For what it is worth, cat-coffee-whiskey man will take a look when he has time in the next day or two.

15 hours ago, Caffeine said:

While I could install flatpak itself, flatpak was not able to find Slade because flatpak could not even initialize to the point it could look for anything.

Did you add Flathub as a repo? Instructions here.

Not that it particularly matters in this case, though, because last I checked the Flatpak was also affected by the TEXTUREX crash bug. That is actually an issue with wxWidgets; see plums's posts in this thread:

On Fedora I had success building SLADE from source, but that was because Fedora's wxGTK package already had EGL disabled so I didn't have to also build that myself.

20 hours ago, Caffeine said:

Anyway, back to your question: I think rather than relying on older versions of the software, we should figure out what is it about the current version that breaks then submit a PR to fix it. I am willing to take a stab at this, assuming I encounter any problems running Slade 3.2.5. I just have not bothered using Linux for Doom editing until a few minutes ago.

I checked out the issue tracker on github and someone has already reported the same issue that I had, and this report is recent so it's probably gonna be unresolved for quite some time. Also, 3.2.3-1 isn't perfect, it does have its own unique crash scenarios (setting tags in the properties window crashes the map editor). Another option I'm thinking about is trying out the other versions between 3.2.3-1 and 3.2.5, but I doubt that they'll be as stable.

4 hours ago, Shepardus said:

Did you add Flathub as a repo? Instructions here.

 

Not that it particularly matters in this case, though, because last I checked the Flatpak was also affected by the TEXTUREX crash bug. That is actually an issue with wxWidgets; see plums's posts in this thread:

On Fedora I had success building SLADE from source, but that was because Fedora's wxGTK package already had EGL disabled so I didn't have to also build that myself.

I have tried compiling Slade in the past and wxWidgets has always been a roadblock for me. I understand that you can link up a compiled version of wxWidgets to cmake, but I wonder if having 2 versions of wxWidgets on your system will cause conflicts with other programs.

7 hours ago, Shepardus said:

Did you add Flathub as a repo? Instructions here.

I need to build from source anyway if I am going to try fixing the bug and submitting a PR. However, I should set up flatpak regardless since it seems to be winning against snap which I hated from day one because it is slower than molasses.

Anyway, thanks for the help, but I want to avoid hijacking OP's thread further. I'll try to look into OP's issues this weekend if I have time. C++ is not my primary language, although I do code in it and have dabbled in wxWidgets before. I should be able to stumble my way toward a fix... eventually. Hopefully I don't disappear under a blanket of snow and power loss first with this storm in the eastern USA.

Without derailing this thread further, I do have some vague plans for a new Doom utility and getting Slade+UDB working on Linux are the first steps toward that goal. So I do have a personal incentive for fixing these bugs, too.

4 hours ago, Ar_e_en said:

Another option I'm thinking about is trying out the other versions between 3.2.3-1 and 3.2.5, but I doubt that they'll be as stable.

I downloaded the 3.2.4 Debian package and the graphics and map editor seem to work. It's also more stable than 3.2.3-1, or at least it doesn't seem to crash when applying tags to sectors. The TEXTUREX window still crashes the program tho.

9 hours ago, Ar_e_en said:

I downloaded the 3.2.4 Debian package and the graphics and map editor seem to work. It's also more stable than 3.2.3-1, or at least it doesn't seem to crash when applying tags to sectors. The TEXTUREX window still crashes the program tho.

Like @Shepardus's post (that links to my post) said, the problem with crashing on TEXTUREx isn't SLADE specifically, it's wxwidgets/wxgtk. Switching SLADE versions won't help there. (Maybe a really old version will work, but if it's a precompiled package, it'll probably depend on an older version of wxwidgets anyhow.)

I did notice that recent dev versions cause all sorts of problems on the map editor, but 3.2.5 seems stable for me so far. 3.2.4 was working fine too.