-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
simple64 doesn't boot on devuan. #409
Comments
Upgrade from bullseye to bookworm? For things like that it's always preferable to install from scratch... Try:
|
the third command failed: sudo: unable to resolve host host.localdomain: Name or service not known Annoying thing is, I do have the gtk3 module installed of debconf... so weird. Also, in case it worked without, I did that same command without the -f, did not work. |
https://old.reddit.com/r/debian/comments/paxg6v/after_update_sudounable_to_resolve_host/ha96xyx/ Examples:
Check for
|
Still no dice, I think it isn't related to the network, this problem. Although oddly enough, I had this problem with a different emulator of a similar kind from flatpak known as gopher64. I wonder if its a flatpak issue. Its a pity I can't build this from source without flatpak and install it. Maybe then I could get it working. That is definitely something I would appreciate, but if not, oh well. Btw, how would I be able to check if its a flatpak issue and not an operating system issue? |
Many programs use
How funny, both emulators share the same developer...
Trying to use a third or fourth app in Flatpak? To me, the symptoms reek of a missing configuration. Try:
|
I wasn't using a desktop environment though. I was using jwm.
Interesting... I tried one other app as you suggested, apparently it had the same error, but it actually launched the program. Juk I believe was its name? its a media player
I guess I can try again. the purge part I didnt do before. |
I did the first 4 steps again, same as above: sudo dpkg-reconfigure -f libgtk3-nocsd0 Not sure what this means... |
Try:
Also try:
Or:
At this point I'm already out of ideas. |
Your last commands worked in getting rid of that ld error. Only weird thing is, simple64 still doesn't launch. I am curious whats going on myself. Do you know if anyone has gotten this working on debian bookworm? Just wondered |
Unfortunately the requirements to run simple64 fluently are much higher than those of Project64 or mupen64plus. It's very likely that your CPU doesn't have the See the simple64 FAQ for more prerequisites. I recommend you RMG, the requirements are lower. The bad thing is that it doesn't have Netplay. |
There is the problem... lol. I want netplay Its a pity retroarch doesn't have a netplay compatible version of a nintendo 64 emulator. :( Why make the requirements so high anyways? Btw, yes I am using an ivy bridge quad core. At least it isn't sandy bridge. (some people obsess over those because of being able to delete the intel me completely from the bios.) I seek realistic expectations though. I avoid the network stack in that and the rest is well... meh. Coreboot + intel me neutered ftw. But anywho, that's why... I have A t430 and an x230 both of which I guess can't run your stuff even with devuan. Pity, but oh well. |
If you have a GOOD Android smartphone, you could alternatively try the pre-release version of Mupen64Plus-AE. The true publication date (update) is the file one. The one on the front is from the creation of the I don't know what the limitations and/or restrictions of Netplay are in each version. If they are the same as those of simple64, then you would be forced to always use the latest version published to date.
In layman's terms, is the developer's imposition. In reality it's a true necessity if you really want to have a good experience with simple64. I have personally rebuild the key components to be used as a plugins for UI Console with |
That's a shame that's the result, although, I read on wikipedia, that Vulkan supposedly has the possibility of even supporting sandy bridge intel devices. https://wikipedia.com/wiki/Vulkan?lang=en#2015 Ivy bridge is newer than that and yet it can't seem to work this. It does in fact have AVX support. But if it ain't something that you plan to add, this probably is lockable. Appreciate the explanation though. |
By "key components" I was referring to the mupen64plus-core and parallel-rsp forks used by simple64. Certainly, parallel-rdp is a "key component" that Vulkan uses... but it barely uses CPU. However, it can easily bring upper mid-range GPUs to their knees depending on the settings... no wonder the x8 upscaling setting was removed (disabled). In theory, Vulkan in software mode (CPU) could work with just the SSE2 instruction at 32 bits... but that would kill the whole purpose of using Vulkan in the first place (doing everything on the GPU). From my point of view, the whole point/reason of forcing the use of AVX2 in simple64 is to guarantee good performance on low-end CPUs when using simple64's mupen64plus fork in |
Describe the bug
I get this when I try to run simple64 via flatpak:
user@host:~$ flatpak run io.github.simple64.simple64
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
and then it refuses to run.
Expected behavior
simple64 should startup.
Screenshots
Add screenshots and/or a video to help explain your problem.
These really help when trying to find bugs, please include them!
Desktop (please complete the following information):
Additional context
Nothing to speak of
I tried this because I wanted to try netplay.
The text was updated successfully, but these errors were encountered: