Skip to content
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

Logging #93

Open
Langstonius opened this issue Mar 17, 2022 · 1 comment
Open

Logging #93

Langstonius opened this issue Mar 17, 2022 · 1 comment

Comments

@Langstonius
Copy link

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.

Thank you for your time.

@dobey
Copy link
Contributor

dobey commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants