bleistift2

You know, [email protected] exists.

I did try to catch all of these signals:

                | "SIGABRT"
                | "SIGALRM"
                | "SIGBUS"
                | "SIGCHLD"
                | "SIGCONT"
                | "SIGFPE"
                | "SIGHUP"
                | "SIGILL"
                | "SIGINT"
                | "SIGIO"
                | "SIGIOT"
                | "SIGKILL"
                | "SIGPIPE"
                | "SIGPOLL"
                | "SIGPROF"
                | "SIGPWR"
                | "SIGQUIT"
                | "SIGSEGV"
                | "SIGSTKFLT"
                | "SIGSTOP"
                | "SIGSYS"
                | "SIGTERM"
                | "SIGTRAP"
                | "SIGTSTP"
                | "SIGTTIN"
                | "SIGTTOU"
                | "SIGUNUSED"
                | "SIGURG"
                | "SIGUSR1"
                | "SIGUSR2"
                | "SIGVTALRM"
                | "SIGWINCH"
                | "SIGXCPU"
                | "SIGXFSZ"
                | "SIGBREAK"
                | "SIGLOST"
                | "SIGINFO";

Sehr gerne, du Edwin.

You can’t know that from my issue description, but throwing a database at that problem really is ridiculous overkill.

Still thanks for the suggestion

When I run the script myself and kill it, it gets the signal and acts correctly. Only when I poweroff the system, this doesn’t work.

I also tried prepending exec, but no dice.

When I run the script myself and kill it, it gets the signal and acts correctly. Only when I poweroff the system, this doesn’t work.

if you have a laptop with a hybrid GPU

That is something I really care about. Thanks!

[Edit: I just checked. Something is handling the switch automatically on my system]

I’m not a super-savvy user. Can someone explain to me why I should care about X vs Wayland? Everything seems to work with X, and as I’ve just read, many programs don’t support Wayland. So will this transition just lead to lots of broken software once someone decides they won’t ship with X by default anymore?

It’s a node process invoked by a run.sh, which gets executed via a .desktop file in the ~/.config/autostart directory.

I went with a systemd unit now and it works.

The constant nagging by you systemd people worked. I’ve written a unit that does what I need it to do. That was more annoying than I think it needed to be, but well… my solution didn’t work at all.

Persist everything to disk in real time.

That’s the thing I’m trying to avoid.

6. Built-in Local AI Assistant

Yess, because if I’ve learned one thing in the past year, then it’s that users love AI being shoved into everything!

Why stop at an AI assistant? Build AI into the kernel, I say! Let AI handle system calls, so everyone can be a low-level programmer! The kernel will just guess what your intentions were!