osu! Linux AppImage hangs straight after "This is an early development build" screen
See original GitHub issueDescribe the crash:
The game seems to open correctly, but it freezes right after showing the “development build” splash screen. No terminal output is shown. The window is also unresponsive to the close command, it’s necessary to kill
the frozen game.
Screenshots or videos showing encountered issue:
simplescreenrecorder-2020-02-22_15.44.59.zip
osu!lazer version: 2020.221.1
Logs: No terminal output, no logs written to journal or to file.
Computer Specifications: CPU: Intel i5 7200-U (dual core) GPU: Intel HD Graphics 620 Memory: 8 GB Display resolution: 1920x1080 OS: Arch Linux Kernel version: 5.5.5-arch1-1
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (1 by maintainers)
Top Results From Across the Web
[Archived] can someone help I cant open osu lazer appimage
I just tried the latest AppImage here on Arch as well and it worked out of the box, I'd say to try a...
Read more >Osu Lazer Hanging on Start screen (Arch Linux) : r/osugame
My osu lazer launcher has suddenly hung, and I don't get the welcome screen, I'm using Arch Linux, with KDE & have installed...
Read more >I made a (currently up-to-date) guide for installing osu! on ...
I downloaded lutrisThen I downloaded osu! After that I reset my pc and it ran. But only on the first time after a...
Read more >Low-latency osu! on Linux - ThePooN's Blog
To make it simple, we'll consider two main sources of audio latency: the audio server & the audio source (Wine/the game). Usually, Linux...
Read more >mGBA 0.10.0
Note also that mGBA is written primarily by a single developer, so at times progress can stagnate; after all, mGBA has a bus...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Great to hear. I’ll close this issue for now, but this failure pattern is a recurring theme that needs addressing framework-side. Thanks for the help diagnosing this issue!
I had to change the IntroSequence = Circles also. Arch Linux current.