If things are printed on top of each other, try script?

https://man.freebsd.org/cgi/man.cgi?query=script&apropos=0&s...

But, if you're getting console debugs from the kernel, that wouldn't be captured either... Otoh, debug output from the kernel should also go into logs or dmesg or something?

You'll capture everything and maybe be able to figure it out from there?

▲

maxjohan 4 days ago | parent [-]

Thanks for the input! Sounds promising. I've to admit, 'script' doesn't say anything to me yet. I've to look into it.

About the logs, yes, I have yet to dive into that. The _everything_ part makes it very tedious, so I had hoped for another solution :)

▲

ranger_danger 4 days ago | parent | next [-]

If script doesn't work, you could maybe try starting everything from within GNU screen or tmux with logging turned on?

	▲	maxjohan 3 days ago \| parent [-]
		These methods would fetch Sway error messages, but nothing else, no? This is not about Sway messages.

▲

toast0 4 days ago | parent | prev [-]

oh, one more thing... your pipeline is only capturing stdout; errors often get logged to stderr ... script (or screen/tmux logging) will capture both though.

	▲	maxjohan 3 days ago \| parent [-]
		Thanks for the notice! Embarrassing rookie mistake ;)