Reproducable core dump about gtklock HOT 6 CLOSED

Do you mean the core dump itself? It's caused on purpose by g_error, so it's not really a bug but the docs explicitly don't recommend it for this use case. I'll change it to a message and graceful exit.

from gtklock.

I don't understand the issue here? I assume one instance of gtklock stays running?

from gtklock.

Core dump is usually an indicator that something went pretty wrong. Sorry, I had assumed that gtklock could be causing another issue I was debugging on my desktop. It's because, coredumps will register as pretty large error cases on journalctl output.

from gtklock.

Yeah, you're right. I shouldn't have used g_error without consulting the documentation.

from gtklock.

I "fixed" it in master. The solution is a bit clumsy but better that a core dump.

from gtklock.

Thanks

from gtklock.