Is the kernel metapackage installed?

apt policy linux-image-amd64

From the horses mouth: https://ajaxnwnk.blogspot.com/2020/10/o … erver.html

Yeah, the message might be because systemd-resolved is useless

https://gist.github.com/zoilomora/f7d26 … 2cea2c844c

I'm using FF v82.0 (Alpine Linux) and I don't see that.

What is your output for the nslookup command I posted above? The dnsutils packages provides the command.

The package search page also works for me. Are you using a proxy or something? How are you handling DNS queries in your box?

~$ nslookup pkginfo.devuan.org 
Server:         9.9.9.9
Address:        9.9.9.9#53

Non-authoritative answer:
Name:   pkginfo.devuan.org
Address: 54.36.142.179
Name:   pkginfo.devuan.org
Address: 2001:41d0:2:1f68::3624:8eb3

~$

What is your video hardware and driver?

lspci -knn | grep -iA3 'vga\|3d\|display'

Your X.Org log is completely empty?

If it isn't empty then check it to see if the modesetting DDX driver is being used. Or just post it here (using code tags) so that we can check.

If you have an Intel card the modesetting driver can cause the crashes you describe so I would advise that you try the Intel DDX driver (xserver-xorg-video-intel) instead. The Debian packages page recommends otherwise but it does work better for some systems, at least in my experience.

See the top comment on the Talk section of the kernel mode setting ArchWiki page: https://wiki.archlinux.org/index.php/Ta … de_setting

Okay, thanks for the feedback

We could now try a diagnostic test: disable PulseAudio to see if that breaks cmus again.

To stop PulseAudio from starting run this command as root:

sed -i '/autospawn/s/#//g' /etc/pulse/client.conf.d/00-disable-autospawn.conf

Then log out & back in again, check if PulseAudio is disabled (the pgrep command won't produce any output if PA isn't running) and then try to start cmus.

To re-enable PulseAudio again after the test re-apply the comment to the autospawn line by running this command as root:

sed -i '/autospawn/s/^/#/' /etc/pulse/client.conf.d/00-disable-autospawn.conf

So is PulseAudio running now? Use my pgrep command to find out.

Of the four code blocks in my last post only the pgrep command was expected to produce any output. If it did not produce any output then that means that PulseAudio is not running in your system, in that case the sed command was intended to ensure that PulseAudio was started on the next login which may have got cmus working. Unfortunately the last command string would then have broken it again if you ran that as well. Sorry but I was expecting you to read and attempt to understand my post rather than just running the commands blindly like a child accepting food from a proffered spoon...

So in summary if the pgrep command now produces some output and you have a file at ~/.cmus/rc that contains the string set output_plugin=alsa then you need to delete ~/.cmus/rc then log out & back in again.

For the record the strace command was expected to create a log file called strace.cmus in whichever directory the command was run from.

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

Well yes but my aptitude command will show if anything else has been dragged in along with it.

I can't see anything relevant there but just in case I've missed something you can delete the file and then try to start cmus again to see if anything new is added.

You can also try

strace -o strace.cmus cmus

Then share the content of strace.cmus but I can't really interpret that in any meaningful way, unfortunately.

Is PulseAudio running?

pgrep -a pulse

If it isn't running then try this command as root:

sed -i '/autospawn/s/^/#/' /etc/pulse/client.conf.d/00-disable-autospawn.conf

^ That should get PA running, which may fix things.

Alternatively if you prefer to run without PulseAudio try this command as your normal user:

mkdir ~/.cmus; echo 'set output_plugin=alsa' > ~/.cmus/rc

Reference: https://bugs.archlinux.org/task/46447

That's an overview of the sources and pinning that APT sees, it is not the content of /etc/apt/sources.list.

The only suspect entry is repo.vivaldi.com, this should show us what has been installed from there:

aptitude search '?narrow(?installed, ?origin(repo.vivaldi.com))'

That was the entire content of the file? Nothing relevant to cmus then.

Well no, I would not expect it to. The point of that suggestion was to see if any error messages from cmus showed up in the original terminal from which the command was run. Did you see anything in the original terminal?

FWIW cmus works just fine in my Debian buster box.

Have you checked ~/.xsession-errors?

Perhaps also try running this from a terminal:

x-terminal-emulator -e cmus

Not sure if it will return errors from cmus though.

And you should probably share your sources, a FrankenDevuan can result in strange problems:

apt policy