-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dwarf fortress crashes on start on Fedora 36 with TBWT print mode #81
Comments
Are you running in a virtual machine? |
This is laptop with mobile nvidia quadro K4000M card. Not optimus.
Nvidia driver download page offers driver 418.113 so I would assume it is a problem of this specific system. |
I have the same issue on (native) F36 with Intel graphics; I tried a local build. This breaks, too. |
I want to report that I have no issue running on newer hardware with latest driver DF is running Wayland native on nvidia 3080 with PRIME offload on 515.76 driver from negativo. I do get I found the code with error in renderer_opengl.hpp file:
It appears to be calling this function from enabler.cpp:
That in turn calls this from win32_compat.cpp:
So from what I observed the segfault happens while trying to render that gtk message dialog: the error message window appears and it has the title but no content and at that exact moment dwarf fortress segfaults. There is also no output to stderr in |
Changing print mode to TWBT or TWBT_Legacy causes DF to segfault and crash on startup. Blank df window briefly appears with blank "error" window over it before closing. I see no error log entries except for the core dump in system journal.
I did a clean install of rpm https://github.com/McArcady/lnp-forge/releases/download/0.47.05-r6/linux-dwarf-pack-0.47.05_r6-1.x86_64.rpm
No previous installation existed.
I am not sure if it is a problem with the build or something on my side. This laptop is too weak to decently run DF anyway so I won't be trying to compile locally or debug further for at least a few weeks.
The text was updated successfully, but these errors were encountered: