Related: https://xnux.eu/log/#017

And what's wrong with LineageOS & GrapheneOS? They're both open source operating systems that leverage Android rather than GNU/Linux and so would seem *much* better suited to smartphone usage.

No need to mess around with gsettings, the indexing can be disabled from the options panel.

If you consider this problem to be fixed then please prepend [SOLVED] to the thread title (in the first post) to help others who encounter this issue. Thanks.

Almost all the desktop environments have some sort of indexing feature, it's actually quite useful for some users.

Yes, you've mentioned that before but I didn't reply so as not to derail the thread. Perhaps you should open a new thread about search engines and their relevant merits, I would be interested to hear others' opinions.

No, it doesn't:

https://pkginfo.devuan.org/cgi-bin/poli … ge&q=gnome

https://pkgs.alpinelinux.org/package/ed … 6_64/gnome

https://github.com/openbsd/ports/tree/m … me/desktop

Neither Alpine Linux nor OpenBSD could run systemd even if they wanted to but they both have packages for the GNOME desktop.

Try this:

rm ~/.xsession-errors
nautilus

Then check ~/.xsession-errors after Nautilus launches.

EDIT: https://unix.stackexchange.com/question … ing-buster

https://docs.docker.com/develop/develop … aseimages/

Please don't full quote unnecessarily, it degrades the readability of the thread.

I suppose. Running four commands would be quicker though.

# apt install network-manager{,-gnome}

Not sure if that even works without systemd though. I don't use it myself but I know that it has to be removed in Debian buster if you want to use sysvinit, OpenRC or runit-init instead of systemd.

I don't think so, debhelper should do that for you. If it doesn't then file a bug with Debian (after reproducing the problem in a Debian system).

Please read the first two sentences of the first post in this thread. The OP has already fixed the problem you are experiencing and so does not need your help.

That file is supplied by the libpulse0 package:

dpkg -L libpulse0 | grep autospawn

Or:

$ dpkg -S /etc/pulse/client.conf.d/00-disable-autospawn.conf 
libpulse0:amd64: /etc/pulse/client.conf.d/00-disable-autospawn.conf
$

Is the alsa-utils package installed? If so then make sure that the /etc/init.d/alsa-utils init script is enabled — that should save the audio level on shutdown and restore it when the machine is booted again.

I don't think an init script would be appropriate for a per-user script running something in an X session. It is possible to run services just for one user and with the various permissions required for X with systemd but I don't know how to do that with other service managers.

^ +1

Yeah, docker's default image is based on Alpine Linux and that is fundamentally incompatible with systemd because it uses musl libc.

There's systemd-nspawn

But seriously, how about LXC? I don't actually run any servers though so my opinion is pretty worthless.

Yes, docker is superfluous and just adds an extra layer to Kubernetes' container system:

https://www.tariqislam.com/posts/kubernetes-docker-dep/

Probably.

Yes, it does seem to be somewhat contradictory, not sure why

If you run it without -f then it accepts input from STDIN:

$ at now + 1 minute        
warning: commands will be executed using /bin/sh
at> DISPLAY=:0 /usr/bin/x-terminal-emulator
at> <EOT>
job 11 at Sat Dec 12 19:52:00 2020
$

(<ctrl>+d exits the prompt.)

EDIT: or with a here string:

$ at now + 1 minute <<<'DISPLAY=:0 /usr/bin/x-terminal-emulator'
warning: commands will be executed using /bin/sh
job 13 at Sat Dec 12 19:58:00 2020
~$

A here document also works.

The -f switch causes the command to be read from a file, which you have specified as /usr/local/bin/st.

Try this instead:

echo 'DISPLAY=:0 /usr/local/bin/st' > ~/test
at now + 1 minute -f ~/test

^ That works for me. Note that any environmental variables are not passed to the command so they must be specified explicitly.

Actually the man page says:

So try

at -t 12121600 -f ~/test

HTH

EDIT: that example runs the command on 2020-12-12 at 16:00.