-
Notifications
You must be signed in to change notification settings - Fork 977
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
Crash on MacOS 14.0 #1693
Comments
Thanks for your report. Where did you download the TigerVNC client from? Or did you build it yourself? |
Downloaded from the site |
I tested the same binaries on the M1 mac mini we have here, and I unfortunately could not reproduce the crash. So it doesn't seem to be something universally broken on macOS 14. Could you try enabling debug logs in the client and share with us what they say when things crash: |
I tried the instructions but this doesn't seem to work
|
The instructions don't seem to have been updated for zsh. Change the last bit to |
Still not there
This works but you get on a command line in a new terminal window
And I can't find any log in /tmp/ |
Found it! This is the right syntax
And here is the log I get in /tmp/vncviewer.log
|
Hmm... That's odd. The log states that the server disconnected the client right away. Did you still get the crash with "CFRelease() called with NULL"? |
Looking at the stack trace, it looks like it is messing around with keyboard layouts. What keyboard layouts and input methods are configured on this system? |
Sorry I don't get what you mean here. The physical keyboard is Japanese, the input method is "Japanese - Romaji and Japanese - Kana", the system is configured in French language. |
The Japanese input methods could indeed be part of why things are misbehaving. Do you only have those two methods configured, or do you also have a western layout as well under input sources? I also forgot to ask if this used to work before an upgrade to macOS 14? |
It's actually only one method, not two.
I did not try to use a VNC client for quite some time but I do remember it worked before, however different OS and Client versions. |
Yup definitely a trouble with the Entry Methods, I add the method for a French keyboard, selected it then ran TigerVNC client and it ran flawlessly. |
A call for news, any bugfix planned? |
I'm afraid I'm unable to set up the described scenario. The system doesn't let me have just "Japanese - Romaji" and "Japanese - Kana". It doesn't allow me to remove the last western layout. Could you describe the steps to configure the input sources the same way as your system? Can you share some screenshots of your settings? |
I don't know what to tell you, that's how it was installed and configured from the start. It is configured as French language for the interface, but the keyboard is hardware-wise Japanese (machine acquired here in Japan) |
All results I get on this topic state that your setup is impossible. 😕 If you add a western layout like "U.S.", does it appear above the Japanese input sources? And can you remove it again? Here the minus is grayed out for that layout. |
Yes I can add other sources like US or French (Azerty), then remove them without trouble. |
That's very strange. Unfortunately, it is unlikely we'll be able to progress with this issue when we cannot replicate it. It also seems like this is fairly unique to your machine. I would suggest you keep a US or French layout added as well, so that your machine behaves like most macOS machines set up for Japanese input. |
I'm afraid that we won't be able to debug this issue until someone figures out the steps to get macOS in to this odd state. |
Could the fact that we can have only the Japanese entry methods be linked to the fact that we have a Japanese hardware keyboard? |
Another food for thoughts, |
That could be it, yes. Is it possible to remove the US layout on your wife's macbook? Or is it locked, like we see here? |
Nope, it is not removable. |
I had the same problem, and solved it. DO NOT DELETE "ABC" (The system default input source) from input sources. We can delete the system default input source: "ABC", if we use Google Japanese Input.
However, this is the cause of the bug. I have confirmed that TigerVNC automatically switches the input source to “ABC” from any source immediately after starting up a remote window. This is probably expected behavior. If you have already deleted "ABC" from sources, you can restore it and restart vncviewer. |
Nice find! That should hopefully work on our machines here as well and we can try to debug this. |
Describe the bug
Starting the applications end on a crash on MacOS 14.0
To Reproduce
Steps to reproduce the behavior:
Screenshots
Client (please complete the following information):
Server (please complete the following information):
The text was updated successfully, but these errors were encountered: