Skip to content

Logging #93

Open
Open

Description

@Langstonius

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.

Activity

  1. dobey commented on Mar 18, 2022

    @dobey
    Contributor

    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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions