Replies: 4 comments
-
Hi 0chroma,
Could you please try the recent version with statically linked protobuf? FYI. the log files are available at ~/.config/mozc/ (or ~/.mozc) |
Beta Was this translation helpful? Give feedback.
-
thank you for the hint! I'll take a look at how the protobuf libs are being linked when I can |
Beta Was this translation helpful? Give feedback.
-
Was there any update on this? I'm converting this to discussion as it seems there is no immediate action item in the Mozc side. |
Beta Was this translation helpful? Give feedback.
-
no updates yet, since it's a debian package I don't have a ton of control over how the libraries are linked. It does work on debian though, I'm wondering if maybe a socket isn't getting shared correctly or something |
Beta Was this translation helpful? Give feedback.
-
Description
When using the linux distribution VanillaOS, mozc doesn't seem to work properly.
Steps to reproduce
Steps to reproduce the behavior:
abroot pkg add ibus-mozc; abroot pkg apply
Expected behavior
Mozc starts correctly and allows input
Actual behavior
The following dialogs appear:
"Failed to get current config values."
"Cannot start conversion engine. Please restart your computer."
Screenshots
n/a
Version or commit-id
2.28.4715.102
Environment
Investigations
(e.g. Mozc-2.28.4960.100+24.11.oss).
Additional context
It appears that it may be related to some sort of IPC setup, see the following strace excerpt:
From what I know about VanillaOS, there's two major differences that could cause this. Either mozc doesn't like that
/usr
is a link to/.system/usr
, or there's some file in the root FS it's expecting read/write access to but can only get read access.The relevant bug report in VanillaOS is here, many of us would be happy to help diagnose further! Vanilla-OS/live-iso#68
Beta Was this translation helpful? Give feedback.
All reactions