GrandOrgue hangs if left unplayed for a while

[William-Purvis]

I've been running GrandOrgue on our new church organ and occasionally, if left for a while during a long sermon or other activity the organ appears to freeze and fails to respond to the console. This only seems to happen when running without a PC monitor plugged in.

Operating system is Linux Debian 12, using Jack2. Manuals as cut-down commercial keyboards (with USB output), while stops, pistons, etc. are home-grown Arduino-based scanners, again with USB. The version of Grandorgue is probably a little behind the latest version, but I suspect it is not directly to blame for this behaviour.

Our organist prefers to run without the monitor, and it seems to work OK like that, but if left for a while it will freeze and can only be restarted by powering off and rebooting. I have spent many long periods with a monitor plugged in, and doing nothing with no adverse effects, so I have never been able to investigate the cause. It finally dawned on me that it might be down to the lack of a monitor, though I don't see why it should have any effect. We have now been running with the monitor plugged in, but hidden, and it has not shown up this behaviour now for several weeks.

Has anyone else been trying to run headless on Linux?

[oleg68]

It looks like the computer goes to sleep due an inactivity. Look at the journal log.

[William-Purvis]

But only when it's headless?

[oleg68]

But only when it's headless?

Why not? Look at the system journal log.

[oleg68]

@William-Purvis What version of GrandOrgue is it? There was a "freese" problem with jack2 and a very old version of GrandOrgue.

[William-Purvis]

Not sure, without a trip to the church, my laptop copy is v13.3.0, so it will be fairly close to that, Certainly 13.?.?
Do you have any more details?

I tried to bring it on yesterday, unplugged the monitor, booted up, checked it was working, then left it for about 90
minutes, but it was still OK. It only seems to happen during a church service! I will leave the monitor unplugged and
try again tomorrow. If I can get it to freeze, I will then check the system journal.

[oleg68]

Do you have any more details?

There was an old issue #702. It was fixed at 3.4.2 with #837

[William-Purvis]

Doesn't sound to be related - this is something that crops up when the machine has been idle for quite a while. The only time that
I managed to get in when it had frozen, Jack seemed to have stopped, but not gone away. Jack Messages didn't mean anything to me, but if I can repeat this, I'll collect what messages and journal entries I can, and report further.