hav3mercy Nov 8, 2024 @ 10:20am
DosBox error (linux)
As of yesterday, launcning steam also launches 2 zenity popup windows with a DosBox error. One of them complains about "-d3d12" flag being unrecognized, the other says something about an unsupported DosBox app.

Any ideas/suggestions what that is and how to debug, where exactly these errors are coming from?
I am on Garuda Linux.
Originally posted by r.linder:
Shouldn't be anything because Ive used Garuda too and haven't seen that

Something you installed is probably the cause, maybe one of the gaming packages that's really old and for dosbox

The error should also mean that dosbox is installed so if you don't use dosbox, remove it
< >
Showing 1-9 of 9 comments
Philco7a Nov 8, 2024 @ 11:33am 
India coded. delete it and install Linux Mint. "Edge" version if you have a fast CPU and 4080/4090
r.linder Nov 8, 2024 @ 4:08pm 
DOSBox is for running DOS operating systems, it's obviously not going to run D3D12

Don't install a bunch of random crap from the AUR and you won't have problems with Arch
hav3mercy Nov 9, 2024 @ 1:43am 
I haven't installed anything new for months, I only run garuda-update on a regular basis to update packages. That's why it is strange this started happening & it only happens when I launch Steam.
hav3mercy Nov 9, 2024 @ 1:48am 
It seems I just found the source of the error, although still no idea why it's there in the first place.
There are 2 Steam apps - Steam (Runtime) and Steam (Native). I've been using Steam (Native) since the beginning, and that one is throwing the errors. If I launch Steam (Runtime), which seems to self-close and run Steam (Native) anyway, then there are no errors.
Omega Nov 9, 2024 @ 3:28am 
Originally posted by hav3mercy:
It seems I just found the source of the error, although still no idea why it's there in the first place.
There are 2 Steam apps - Steam (Runtime) and Steam (Native). I've been using Steam (Native) since the beginning, and that one is throwing the errors. If I launch Steam (Runtime), which seems to self-close and run Steam (Native) anyway, then there are no errors.
Steam Native runs games against your native system libraries. The benefit of doing this is that your system libraries are likely much more up-to-date than what the Steam Runtime ships.

The downside is that these updated libraries may break compatibility with games are Steam.
hav3mercy Nov 11, 2024 @ 10:56am 
Originally posted by r.linder:
DOSBox is for running DOS operating systems, it's obviously not going to run D3D12

Don't install a bunch of random crap from the AUR and you won't have problems with Arch
It would be great to know, what kind of DOS app is steam running alongside it to cause this.
The author of this thread has indicated that this post answers the original topic.
r.linder Nov 11, 2024 @ 5:40pm 
Shouldn't be anything because Ive used Garuda too and haven't seen that

Something you installed is probably the cause, maybe one of the gaming packages that's really old and for dosbox

The error should also mean that dosbox is installed so if you don't use dosbox, remove it
Last edited by r.linder; Nov 11, 2024 @ 5:40pm
hav3mercy Nov 12, 2024 @ 2:46am 
It seems the only tool that uses DOSBox is Boxtron, which, as I understand, is another compatibility tool for Steam. I guess I should start with that one, because Boxtron has DOSBox as a dependency.

-----------------------------------------------
UPDATE
After doing

pacman -Rcns boxtron

and restarting Steam, the errors are gone, which tells me that they were indeed produced by Boxtron/DOSBox, probably some misconfiguration on init, but since I do not play any games that would require Boxtron, away it goes.

@r.linder thank you for the hints
Last edited by hav3mercy; Nov 12, 2024 @ 3:02am
Just want to pop in and say that for me, I had them installed with Proton Community Updater, and removing them fixed the problem for me
< >
Showing 1-9 of 9 comments
Per page: 1530 50

Date Posted: Nov 8, 2024 @ 10:20am
Posts: 9