I get errors in the journal from attempts to start it and I don’t know how to stop that, not that it is particularly bothersome (yet) since audio still works.
mar 01 09:16:29 majtaytre pulseaudio[1828]: Failed to load module "module-x11-xsmp" (argument: "display=:1 xauthority=/run/user/1000/xauth_thAcGd session_manager=local/maj>
mar 01 09:16:29 majtaytre pulseaudio[1828]: Failed to open connection to session manager: None of the authentication protocols specified are supported
Audio works fine otherwise.
$ inxi -A
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio
driver: snd_hda_intel
Device-2: Advanced Micro Devices [AMD/ATI] Caicos HDMI Audio [Radeon HD
6450 / 7450/8450/8490 OEM R5 230/235/235X OEM] driver: snd_hda_intel
API: ALSA v: k6.12.73-1-MANJARO status: kernel-api
Server-1: PulseAudio v: 17.0-98-gb096 status: active
Or, should these ALSA and PulseAudio be replaced for something else somehow? N.b. audio works now, so if those things I already use aren’t going anywhere, well, “don’t wake the sleeping bear”. 8)
That’s a very subjective question, because although pulseaudio still works fine, Manjaro has already been defaulting to pipewire for quite some time now. Switching over is quite painless too. All it takes is to remove manjaro-pulse and install manjaro-pipewire instead, which will pull in the necessary packages.
For that matter, not that I’ve inspected my logs for any error messages in this regard, but I have searched my system for module-x11-xsmp, and it is neither a file on my system, nor the name of any package — whether from the repos or from the AUR.
We have desktop environments that have migrated to Wayland. We have others that have not. (XFCE-Wayland is a work in progress with a LONG way to go. The OpenBox family is NOT migrating, but there are Wayland alternatives based on *BOX) As long as we need to support people who use X11 desktops there will be X11 or working alternatives.
No panic is justified.
Yes, I know it isn’t, but it is no longer used on my system. A more Pythonic way of putting it (paraphrasing): “It is no more, it has gone to meet its maker. If it hadn’t been nailed to the perch it would have been pushing up the daisies. This, is an ex Parrot.”
Strange, but perhaps you haven’t been running X11 as of lately? I get this:
I sure didn’t copy it from somewhere and put it there so it must have been installed by something. Maybe as an early dependency, perhaps? The system was first installed back in 2021 (if memory serves me), so it’s been a while.
Yes, I was wondering about that, too, since QGIS complains loudly about not running on X11, and thus it gets sort of finicky and gobble up huge amounts of RAM. Not sure that’s the reason, but it’s generally is acting out. I still have my laptop to run it on, which runs X11 and that works fine.
Since this wasn’t actually a support issue, but more of a general interest question, I’m not sure who’s reply to mark as the solution. Perhaps an admin can just close this? Don’t think I can do that on my own.
That is correct. I have been running on Wayland ever since we switched to Plasma 6, and I have in the meantime removed as much of X11 as possible, albeit that certain packages still have a misguided dependency on some X11 components — they don’t actually need them, but the packager decided otherwise — and so I cannot remove all of it yet.
