Replies: 3 comments 8 replies
|
@lokize this is definitely some issue on your end and not the codebase and I'll need to look at the trace file but it seems you can't even get to that. Are you by any chance running at the same time some other apps that can interfere like other tiling WMs? |
|
I'm not. Unfortunately, I can't view the logs or click on any of the app's menus. I can still use OmniWM to some extent, even with the bugs, but I can't do anything beyond that because every menu I try to open closes immediately. |
|
Try the newest version 0.6.2 I've added launch checker for some conflicting apps and a permission check to make sure you don't have something running that might interfere or that you may have not given all the permissions it needs, but judging by your description of errors it truly seems like you have an app running in the background that is interfering with OmniWM |
|
I've already tried a full uninstall, including deleting all OmniWM configuration files and application data, then reinstalling the latest version, but the problem still persists. The app launches, but every menu, settings window, or preference panel closes immediately after opening. This happens consistently even after a clean reinstall. |
|
|
|
While monitoring OmniWM through: log stream --process OmniWM --info I noticed that whenever a menu or settings window opens, it is immediately closed by AppKit: window finishing close Shortly after, OmniWM throws an exception: *** Assertion failure in CUINamedVectorGlyph.m The logs show a crash/assertion occurring inside Apple's SwiftUI/CoreUI rendering stack. |
|
any news on this? I have the same error on macos 27 beta 8 |
|
@tecumses please provide OmniWMs trace file as I can't reproduce this as all tried it multiple times and simply can't and then I'll be able to help you out as it will allow me to precisly see what is happening. Think of it like a picture vs words |
|
how exactly can I do this? $ omniwmctl capture start trace phase recording than it crashes immediately when I try to open a menu entry after reopening phase idle edit: |
|
Thanks both, and sorry this took a while to pin down. It is not on your end, and it is fixed. What happens: on the macOS 27 betas, CoreUI's SF Symbol rendering breaks when the process's C numeric locale uses a comma as the decimal separator (German, Portuguese, Spanish, French, ...). Symbols stop rendering, and the first SwiftUI window that draws not-yet-cached symbols (Settings, App Rules, Report a Bug, ...) trips a new CoreUI assertion, so macOS terminates the app. OmniWM was setting that locale itself: the embedded Ghostty terminal engine initializes at launch and applies your system region to the process locale. My Mac is set to English (Canada), which uses a dot, so I could never reproduce it. Reinstalling cannot help because the state is your Language & Region setting. Credit where due: the locale trigger was isolated by two cmux users chasing the same crash (manaflow-ai/cmux#7880). I confirmed it here with a 20-line SwiftUI program that crashes with Fix: OmniWM now restores the numeric locale to C right after the terminal engine initializes. It will be in the next release. Until then this launch method is a verified workaround for the same bug in cmux: I have also filed it with Apple as FB24679653 ("SF Symbols render blank and apps crash when the process LC_NUMERIC locale uses a comma decimal separator", macOS 27 beta, CoreUI). If you are on the macOS 27 beta in a comma-decimal region, filing a short duplicate that references that number is the most effective thing you can do to get it fixed in the OS itself. Could you both confirm that System Settings > General > Language & Region shows a comma as your decimal separator (e.g. 1.234,56)? That closes the loop on the diagnosis. Fixed: beb7a59 |
|
hello, |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'm currently testing OmniWM 0.6.1 on macOS 27.0 Golden Gate Beta and have encountered a critical issue that makes the application difficult to configure and use.
Main Issue
Whenever I try to open the Settings, Preferences, or Advanced window, the window briefly appears and then OmniWM immediately closes or crashes.
The same behavior occurs with several other menu actions. As a result, I’m unable to access or modify any settings.
Additional Issues
I've also noticed a few window management problems:
Environment
Steps to Reproduce
Thanks!
All reactions