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

etrace doesn't close antstream-arcade #66

Open
popey opened this issue Sep 2, 2021 · 1 comment
Open

etrace doesn't close antstream-arcade #66

popey opened this issue Sep 2, 2021 · 1 comment

Comments

@popey
Copy link

popey commented Sep 2, 2021

alan@robot:~$ etrace analyze-snap antstream-arcade
[sudo] password for alan: 
original snap size: 280.74 MiB
original compression format is xz
content snap slot dependencies: []
exit status 1

The antstream-arcade window opens, and stays open.

@anonymouse64
Copy link
Contributor

Unfortunately, this is a case where some application's window names/classes don't cleanly map to their snap name, so the assumptions I have built into etrace don't pick the right thing automatically and so you need to do something like this:

etrace exec --silent --no-trace antstream-arcade --window-class-name="Antstream Arcade"

however I still have a TODO to support all the --window-class-name, etc. options in analyze-snap (though that should be pretty easy to add), and I also need to document better what to do when etrace can't figure out how to close the window automatically so folks know how to look for it (that will be harder I think).

Alternatively, something like a command to let etrace interactively find the window and then tell the user the set of options that work with this snap would be most helpful

etrace detect-window-opts anstream-arcade
Window possibly detected as WID "0xff020df" with title "SOME UNPREDICTABLE WINDOW TITLE"
Please close the window manually to confirm this is the correct window
Success! Use these options in the future:
etrace <cmd> --window-class-name="SOME UNPREDICTABLE WINDOW TITLE"

but failing time to implement all the logic for that just a basic explanation of how to use xdotoool and wmctrl -l, etc. would be best I think

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