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

Labwc crashes. How to enable logging? #317

Closed
CrendKing opened this issue Nov 6, 2024 · 4 comments
Closed

Labwc crashes. How to enable logging? #317

CrendKing opened this issue Nov 6, 2024 · 4 comments

Comments

@CrendKing
Copy link

I switched from Wayfire to Labwc, and experiencing Labwc crashing when a program of mine which uses enigo to simulate keyboard inputs. This program works fine under Wayfire. It also has no problem for mouse inputs.

Before I report this to enigo, I'd like to enable debug logging of Labwc to a file, so I can give them more info. I tried to modify /usr/bin/labwc-pi with exec /usr/bin/labwc -m $@ --debug > /tmp/labwc.log, but then labwc will fail to start at all.

@spl237
Copy link

spl237 commented Nov 6, 2024

Try removing the $@ from that line.

@CrendKing
Copy link
Author

CrendKing commented Nov 6, 2024

Thanks. I got the log at crash. Reported to enigo

@Consolatis
Copy link

Please also report the bug at https://github.com/labwc/labwc. Even if enigo is doing something wrong labwc should not crash because of it. The log you posted in the enigo issue does not contain the relevant part for labwc itself (might need a 2>&1 to also catch stderror).

@CrendKing
Copy link
Author

That's all the log I can get. The command line was something like labwc -m --debug 2>/tmp/labwc.log. If I do 2>&1 >/tmp/labwc.log, labwc would not even start (which I do not understand).

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

3 participants