TEXTUREx editor multiple issues both on Linux and Windows #1672
Comments
|
Some additional notes: I noticed the zoom in and out are somehow working since it can be done using the mousewheel. But nothing displays. I suspect the checkboxes are doing the same. The fields around the graphic interface are all working and saving the changes works. But it's very difficult to do anything when you can't see what you're doing. |
|
Here's a slightly similar issue I made in July last year: #1549 |
|
Things got even worse lately. Now not only the Start page just displays a blank window (fortunately you can still open files and folders using the menu) the TEXTUREx editor freezes entirely SLADE now... |
|
I'm having the same issue on Linux, where the program instantly crashes, without even so much as a "This program crashed!" dialog box. Luckily, I was able to get it running on my terminal, and when I reproduced the bug, this is what it gave me: I was not able to get anything else from the terminal whilst I was running the program. |
|
Same issues here. Everything else works just fine, but whenever i open a TEXTURES lump i get one of two things: texture Version: 3.2.5 Operating System: Linux 5.15.0-105-generic x86_64 Stack Trace: Last Log Messages: On my end the crash only happens when i close the program and then try to open the TEXTURES lump for the second time. Whenever i create one, add textures to it and open it up for the first time, the program doesn't crash but then again no preview, just the UI Elements and a black preview window.
I'm using the flatpak version, platforms etc... are all up to date. Some info about my OS: System: Graphics: |
|
Updated to 3.2.6 and there's some new. Now, when opening a TEXTURE file, the following crash log is reported, similar to #1685 : It seems to not find openGL. Though it's installed. (i use mesa drivers) (Also the problem with the Start page not loading is still there) |
|
What version of wxWidgets is it built with? Should say in the console log. I think there might be some issue with the version of wx that the flatpak SLADE is built with |
|
I don't use flatpak. I build slade using AUR. Here in this case I compiled slade manually since AUR is not up-to-date yet. I use wxwidgets v3.2.5 I'm going to try the flatpak version though, just to check. EDIT: well, same problem, both with the start page (becoming pitch black though, instead of just empty) and same error with TEXTURE lump. |
|
I switched to debian for multiple reasons but still same problem in there. I use the flatpak version. (and the crash handler also crashes :| ) |
|
I switched from flatpak to the debian package available in the drd repos. And all the problems i mentionned got fixed. Start page works again and no issues at all when editing TEXTUREx. So, tempoprary fix: use Debian and install Slade using the debian drd repo. 🤷♂️ Note though: The debian package version needs the |
|
Compatibility with all currently supported versions of Debian and Ubuntu. That said the latest package should have binaries for both (it would be possible to make a single universal binary but I don't really feel like going that deep into dependency building). Which is used is determined by /usr/bin/slade by running: ldconfig -N -p | awk '$1 == "libwebkit2gtk-4.1.so.0"'Does this return nothing for you? |
It returns me this: |
|
That's the expected output, so it should be running the 4.1 binary. |
|
And yet, if i launch slade without libwebkit2gtk-4.0, i get this and it doesn't run: |
|
You edited out your note about ldconfig needing to specifically be /sbin/ldconfig. Did you have new information or what that still valid? I can change the script to specifically call /sbin/ldconfig in the next build, but Ubuntu definitely puts /sbin in the PATH by default. A bit surprised Debian would differ there. You can modify /usr/bin/slade accordingly in the mean time, apt should unconditionally overwrite the file on package upgrade. |
|
Ubuntu might do that but pure Debian definitely doesn't add So yeah maybe it would be relevant to add |
|
uname -a
On X11 (AwesomeWM): Slade crashes after open TEXTUREx editor
|
Black screen also show on X11 with nvidia (i.e |
|
Heads up to say I had to ditch debian cuz issues and had to return to arch. And i'm still facing the problem :( |
|
Although I'm still having the issue on the native Linux excecutable, I don't experience this problem when I'm running the Windows .exe on Wine. I'd love to get the stack trace, but the program crashes before the window even shows up, and trying to run the program with a terminal only gives a "button lost focus even though it didn't have it" debug message. If it helps, I use the linux-zen kernel on Arch Linux, with AMD architecture. |
That's the thing. I, like all the others who got the problem, use nvidia. |
I don't think it is GPU(driver) related because I'm having the same issues on Gentoo Linux running an Intel UHD630 GT2 iGPU. I Successfully build the latest git master using the cmake flag to pull and build it's own wxWidgets. Still the same crash. No idea why @sirjuddington won't try fix that. Maybe he cannot reproduce it?! |
|
Well jmfergeau noted that it doesn't happen on Debian with my packages. I can't say I'm doing anything particularly special with my packages besides building wxWidgets and SFML myself for static linking. My binaries are built with GCC 11. wxWidgets build: Slade build: Nothing special about the SFML build. |
Might be a case of wxWidgets having different versions and/or code on different distros then? Completely at a loss for ideas if not, but if so, maybe Slade should bundle the version of wxWidgets known to fully work instead on relying on the distro for the dependency? |
Thanks for the hint. Using |
No. Since Slade so often finds bugs in wxWidgets it's not viable for my packages to use a system provided copy of wxWidgets while still retaining 5 years of back support for Ubuntu/Debian versions. The latest version is compiled from the official sources and statically linked. However like most projects, the build system for wxWidgets auto detects what's available on the system and configures itself so builds can differ. Or I guess in this case I intentionally disable a feature since it has been noted to be problematic with the current version of wxWidgets.
Oh that's a little surprising. I was under the impression that others in this thread would have already tried that. It has been noted that wxWidgets without EGL fixes a TEXTURE editor crash here: #1390 (comment) |
|
Although the AUR's pkgbuild has had the EDIT: ...now the program immediately crashes when opening any kind of sound. |
|
That needs to be specified on the wxWidgets build not SLADE. The AUR package maintainer will need to build a custom wxWidgets as part of the SLADE package instead of using the system copy. For the sound thing, make sure you're using SFML 2.6 instead of SFML 3.0 as that sounds like #1759. |
|
@kinker31 @Blzut3 can you please try (on arch) and see if you can reproduce the error? If that doesn't resolve it, please try install https://aur.archlinux.org/packages/wxwidgets-gtk3-noegl |
Although attempting to run Slade directly through the terminal gives me
|
|
Well, bad news. I've just installed the patched wxwidgets of @envolution and it resolved nothing for me. Still same problem both for TEXTUREx editor and the start page... So I guess the problem is something else for linux... :( |
|
@jmfergeau I don't really want to commandeer this issue log, but please make sure you're calling slade with GDK_BACKEND=x11. I issued a new PKGBUILD that deprecates the need for wxwidgets-gtk-noegl so you can reinstall wxwidgets-gtk, then install slade, then run if that doesn't work and post to https://aur.archlinux.org/packages/slade |
|
@envolution I use Ubuntu and maintain the deb package for Slade, so can't test your package but of course feel free to reach out if you need to compare notes. For this issue in particular don't worry too much about causing too much packaging noise here since until something changes this is a packaging issue. As an aside, I think you might be able to set CMAKE_INSTALL_RPATH on the Slade build to avoid needing to run patchelf if you prefer. @jmfergeau Given you say you have the start page issue definitely double check that you're running under XWayland (GDK_BACKEND=x11). |
|
the real problem for me was that I forgot i was using the flatpak version. (for the reason that I could at least reach the editor with this one rather than having an abrupt crash on it.) So I reverted to the aur one. Though I noticed the aur package provides its own wxwidgets it builds with, so I have the feeling the slade built wants to use this one... anyway @Blzut3 and @envolution I don't use wayland because nvidia so i'm already natively on x11. And still same problem, even if I add GDK_BACKEND=x11. |
|
@jmfergeau i made another change to aur/slade that should (hopefully) resolve it for you |
|
@jmfergeau Wayland should work on nvidia at this point, although I wouldn't blame you for wanting to give it a little more time to bake in their drivers. Interesting that you're seeing problems on native X11 though, would seem that the problem you're facing may be different from the common one everyone else is facing. You may want to do a debug build and get a complete stack trace (since the dump you posted in May doesn't have Slade symbol names). |
|
@envolution I got the update and tried. Nothing changed, still crashing like before. :/ But well, thanks for trying. @Blzut3 Wayland works for me but electron-chromium-based programs are having problems. And I use several of them (like discord and my browser) and can't afford to not use them. Anyway I tried gdb on slade but gdb simply refuses to let me because EDIT: I noticed that, if i hit continue, I get more errors, but the TEXTUREx editor finally manages to open. It still has the same problem as on the flatpak, though. But it got me a thousand lines of backtraces that can maybe help. |
|
If you're using the aur package, /usr/bin/slade is a shell script, /usr/bin/slade3.bin is the binary you'd want to open with gdb |
|
Those assertions indicate that wxWidgets is failing to create an OpenGL context for some reason. (I assume other OpenGL software works fine.) Search results for that message don't reveal much except that maybe the attributes specified are incompatible? Don't know much about OpenGL programming so I really don't know what to make of any of that myself. |
|
@jmfergeau I just want to rule out a possibility of you using older packages I created. Can you confirm you have the system wxwidgets and slade is linked properly to the custom one (as below)? |
|
@envolution here's what I got with the commands you sent: Also, thanks for the point out. I could run gdb on slade and I got the following In this file slade_gdb_log.txt I don't know if it can help but just in case... and yes @Blzut3 I have other stuff using opengl and they all run like a charm. Slade is the only one that doesn't. (And as I'm trying, I just noticed that even the map editor crashes on me. Which is very problematic to me since UDB is very bad on linux and I have no better alternatives for making maps now :( ) |
|
@jmfergeau you'll definitely want to replace wxwidgets-gtk3-noegl with wxwidgets-gtk3 - it was an unsuccessful attempt at working around the issue. It's no longer needed as you may notice aur/slade builds wxwidgets-gtk3 internally. I don't think this is causing the current issue for you, but it's not helping either. |
|
@envolution well indeed since same problem with and without so I guess i can revert to the usual one at this point. |
|
I found a temporary "fix" to use slade while waiting for the fix: make a vmware machine (because qemu and virtualbox failed there) then install debian then slade via the drd repo. Worked like a charm after some tweaks. |
|
I found another issue that seems related to it: the "convert to png" is completely messed up if used on a pc that has the issues. On my tests, the texture ended up being grayscale and all messed up. Though, everything goes fine if I do it on my debian vm. |
SLADE Version
3.2.5, 3.2.6
OS
Windows, Linux
Editor
Resource editor
Steps to Reproduce and Observed Behavior
Expected Behavior
the Texturex editor should display the window editor correctly and be fully interactive
NOTE: For the crash on linux, I found a workaround. Very weird, but it works:
Sorry if it has already been posted. I checked everywhere but haven't found anything similar.
Screenshots
The text was updated successfully, but these errors were encountered: