You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello.
I currently have an issue where i've gotten the keyboard working but im running into an odd issue on boot where it goes to 100% cpu and essentially blocks the system.
If i kill it, and let it start as it should, via qprocess in the application, it works fine.
Im am looking for where the logs would be so I can try and determine:
-Why its starting itself when it should be started by the application
-Why, when it starts itself, it uses 100% cpu.
Activity
dobey commentedon Mar 18, 2022
What system is this on? How did you install maliit?
Generally, yes, maliit should be started by whatever window manager you're using, and not by arbitrary applications.
Any log messages just go to STDOUT/STDERR, so should appear wherever the same output appears for whatever is starting maliit.
If it's using 100% CPU, you should probably also attach gdb to the process to see where it is stuck in an infinite loop at.