osu! crashes at first launch - macOS
See original GitHub issueDescribe the bug: First time installing osu!lazer on this machine. Attempting to launch it will result in an instant crash. Nothing appears at all. In the video, app is launched from the dock. However, the same thing occurs when launching from the Applications folder and by right click opening.
For further reference I am running macOS 11.2.3 on MacBookPro11,1.
Screenshots or videos showing encountered issue: https://www.youtube.com/watch?v=254BsHbQh8s
osu!lazer version: 2021.331.0
Logs: ~/.local/share/osu directory is not created at all either.
Only crash log I can get is the one macOS provides when an application crashes, available here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
[Archived] Osu Mac OS Agent Crashes instantly when I try to ...
I just installed Mac OS Big Sur and now am having an issue with the Osu Mac OS Agent, it crashes instantly as...
Read more >Startup issues - osu!mac - Read the Docs
You need to launch the game twice, since the first time always crashes · Startup will take 1-2 minutes. or the game will...
Read more >A game called osu keep crashing : r/MacOS
i was in osu, and then suddenly the app just closed by itself. it said osu crashed and for me to restart my...
Read more >osu!macOS Agent crashes on startup - Read the Docs
osu !macOS Agent crashes when you attempt to start it. To diagnose the issue, move osu!macOS Agent to the Desktop and run the...
Read more >new osu!lazer update (2021-331.0) crashes on my ...
issue: since I downloaded the update about 12 hours ago, the game would crash before opening fully, it would show its icon bouncing...
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
No results found
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
sounds like whatever made
~/.local
on your PC was originally run withsudo
. Lesson: don’t usesudo
.That would be unusual, but not impossible. You should be able to use
ls -l
(or some macOS finder tools, I’m not sure, not a mac user) to check this in the future.Either way, closing as resolved.