Scroll crashed: where to find logs, etc.?

[bluefander]

Hello,

I am using scroll 1.12.21.
Yesterday scroll crashed. I started scide (SuperCollider) and scroll just turned black.
I tried to reboot via TTY and the system wasn't able to do this because it couldn't terminate scroll. So I was only able to shut it down via the power button.

I am sorry for being so unspecific. I tried to find information in journalctl, but I couldn't find anything related to the crash.
I was checking here:
https://wiki.archlinux.org/title/General_troubleshooting
But I am not quite sure where to find logs that would be related to the issue.

Would anyone have ideas where I could check for logs that might be helpful to pinpoint the problem?

Thanks!

[dawsers]

If it crashed, you can always do:

coredumpctl dump scroll

But you say you couldn't terminate it, so it didn't really crash, and that means there will be no useful core dump. Maybe the screen just went black. From another TTY you should always be able to kill scroll's PID, using kill -9.

[bluefander]

Ah, I see.
Yeah, makes more sense to say it went black than calling it a crash then.

Thanks for your ideas!
Can't recall having seen this behavior before with scroll...

[dawsers]

If you want to get a log, you can start scroll like this:

scroll --debug 2>&1 | tee /tmp/scroll_log.txt

[bluefander]

Should I be able to add this to the scroll.desktop file like this?

[Desktop Entry]
Name=Scroll
Comment=An i3-compatible Wayland compositor (sway) with a PaperWM layout
Exec=scroll --debug 2>&1 | tee /tmp/scroll_log.txt
Type=Application
DesktopNames=scroll;wlroots

I tried to, but then scroll fails when I start it from a login manager.
From a TTY it works, of course.

[dawsers]

It is better if you only use --debug etc. for very specific cases, because it will be less performant. If I were you, I would run that version from the TTY instead of modifying your main Desktop file, as you may later forget to change it back.

Another thing to take in consideration is if you find a bug, please confirm it happens in the git version too, not just in the stable version. I don't patch the stable version, if the bug is serious enough, I release another "stable" version, but it will be base on whatever is currently in the git one.

[bluefander]

I see.

Ok, will try to find the bug it in the git version.
I don't know whether I am able to reproduce this problem anytime soon, since I was just doing stuff at my computer which worked without the slightest problem in the past all the time. Felt more like a very strange accident.
But will try and see...

Thanks for your ideas!