[01:28] <guiverc> romo, can't you get it from http://cdimages.ubuntu.com/xubuntu/releases/20.04.1/release/  (SHA256SUMS.gpg is there)
[01:53] <romo> guiverc: yeah, I've definitely been there. instructions on the pubkey are actually here: https://ubuntu.com/tutorials/how-to-verify-ubuntu#4-retrieve-the-correct-signature-key
[01:56] <romo> the key/fingerprint itself ist just a tad less obvious to find than I am used to with other distros so I got super weirded out - but it's there and it's up to date
[01:58] <romo> thank you for your answer, that actually stopped me in my tracks for a bit...
[13:51] <CorvetteZR1> hello.  i have a xubuntu "terminal server" with lots of users (over 100), although at any given time there are maybe 5-10 active users.  but i'm noticing all 100+ users have a pulseaudio process running
[13:52] <CorvetteZR1> how can i make pulseaudio start for each user only when they are logged in rather than start for all on boot?  is this possible?
[13:52] <CorvetteZR1> i assume it's tied into systemd somehow and systemd is starting them all at boot
[14:32] <tomreyn> i was thinking its a systemd user service. you probably have lingering enabled for the systemd user manager, keeping services running all the time.
[14:32] <tomreyn> CorvetteZR1: ^
[14:32] <tomreyn> loginctl list-users
[14:33] <tomreyn> systemd user manager looks like this in  ps:    /usr/lib/systemd/systemd --user   (as run by the respective user)
[14:33] <tomreyn> loginctl enable-linger myuser    enables lingering
[14:36] <CorvetteZR1> tomreyn, right.  but doesn't lingering mean only if user logs in and starts a process...then it'll linger after he logs out
[14:37] <CorvetteZR1> in this case it seems a bunch of processes for each user start before they even log in.  is that expected behaviour?
[14:39] <tomreyn> CorvetteZR1: while this is for Arch Linux, not *Ubuntu, I think it still applies: https://wiki.archlinux.org/index.php/systemd/User#Automatic_start-up_of_systemd_user_instances
[14:40] <tomreyn> so lingering does exactly this: start user managers and thus their services at boot rather than just during active sessions
[14:42] <tomreyn> so i guess your options are to either disable lingering fpr users, or to modify the pulseaudio user service so that it'll not use lingering
[14:44] <CorvetteZR1> tomreyn, ok, got it.  this explains it all.  thank you!
[14:53] <tomreyn> you're welcome
[17:41] <topSitandReach> I am running Xubuntu on QEMU. How is the setup different from running Xubuntu natively?
[17:41] <topSitandReach> Version 20.04 LTS
[18:45] <topSitandReach> How do I make my entire wallpaper black on Xubuntu 20.04 LTS "Focal Fossa" (20.04.1)?
[18:48] <krytarik> topSitandReach: Select "None" as the "Style", then "Solid color" as the "Color", and set the first color box to black.
[19:51] <tayirvadai> Hi, i recently moved from another distribution to xubuntu
[19:51] <tayirvadai> but it seems to have corrupted my LVM + LUKS
[19:52] <tayirvadai> pvdisplay no longer is able to see the partition and gparted shows filesystem type unknown
[20:01] <maxFlexGuest> On Xubuntu, how do I create my own IRC?
[20:11] <diogenes_> maxFlexGuest, install hexchat.
[20:36] <maxFlexGuest> Does hex chat work on Xubuntu version 20.04 LTS with 2GB (2048MB) of RAM memory? I am on a virtual machine with 16 gigabytes of virtual storage.
[21:26] <maxFlexGuest> How do I install hexchat? (I am on Xubuntu 20.04 LTS on a virtual machine with 2GB of system memory and 16GB of storage.)
[21:34] <krytarik> Well,.. did you try my solid black desktop background advice yet!?
[21:38] <Maik> maxFlexGuest: would be nice to keep one nickname if you want help. On how to install software in *buntu, there are many tutorials and documentation to be found on the web.
[21:39] <Maik> search first and if stuck then ask for help
[21:39] <Maik> also creating a own IRC channel isn't a specific xubuntu issue imho
[21:40] <Maik> and for such a thing there's info to be found on freenode
[21:41] <Maik> thought so that would happen
[22:17] <nsh> Xorg (XFCE/lightdm) on xubuntu 20.04.1 using 8077216K (~8GB) memory
[22:17] <nsh> any thoughts on how to debug/fix?