-
Notifications
You must be signed in to change notification settings - Fork 277
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
Occasional crashes #1657
Comments
Ones in a while I got something like that too... but I can't figure out how X interface work and how to look up what the error mean based on major/minor_opcode (yet).
For the second one, I suspect there's something going on with the notification system --- refer to #1544 that one is fixed, but it's fixed after 4.0.0.dev11 while you're using 4.0.0.dev10. |
That fix sounds promising! I know that notifications sometimes freeze up on my system for short durations. I will report back when I try out |
I'm still running
After that it just stopped working and I had to restart it. I will set up dev11 at some point, I just thought I would start collecting these error messages. |
Here are some more errors that I'm getting now:
|
I'm still on 4.0.0.dev10, I'm running on the unstable branch of NixOS, but it seems like Plover still isn't updated. I will try overriding it to get the latest version. |
It seems some of the recently added dependencies to Plover don't exist on NixOS yet, so I'm stuck on |
Using the AppImage is really the only officially supported way of running Plover on Linux. For what it's worth, though, dnaq has a flake for running Plover in NixOS: https://github.com/dnaq/plover-flake I believe that should make it easier to run the latest version. |
Describe the bug
Hi!
It seems that at random times that plover crashes for me. It's usually when plover has been running for some time. Sometimes it spams notifications with stack traces, and at other times it simply dies. I think it's related to dbus being occupied.
execute_engine_command
is usually mentioned in some way. Restarting plover fixes the issue until it crashes again later on.Here's the stack trace of a recent crash:
I thought I would just report it. I can't reliably reproduce it.
Operating system
Hardware
It's just a normal ASCII keyboard with a custom keyboard layout. It's connected to a T480 ThinkPad laptop via USB.
The text was updated successfully, but these errors were encountered: