[00:07] <WaV> Got a question about .desktop file syntax
[00:08] <WaV> This particular line: Exec=env WINEPREFIX="/home/user/.PlayOnLinux/wineprefix/.wine" /opt/wine-staging/bin/wine /home/user/.PlayOnLinux/wineprefix/.wine/drive_c/Program\ Files\ \(x86\)/Some\ Program/Program.exe
[00:08] <jiffe1> hmm, so nvidia-utils-510-server and nvidia-cuda-toolkit conflict?
[00:08] <WaV> It works the way its intended, but is it the correct way? Or is there no "right" way as long as it works?
[00:11] <rdr> WaV: usually it's just a simple command
[00:11] <rdr> like "firefox %U"
[00:11] <WaV> rdr: The reason I ask is because with most programs that run behind wine, I see the Exec line in the .desktop file with something like "wine start /unix c:\\\\windows etc etc"
[00:12] <rdr> not sure, most of my wine stuff is just steam games handled through proton
[00:12] <rdr> i think that's just different ways of doing it
[00:14] <WaV> Like I said, it runs the program under the most recent wine-staging as opposed to the system wine, and it runs under the correct wine prefix and everything. I just wasn't sure if the syntax was right or if i should even worry about syntax if it's running as expected.
[00:14] <WaV> (running wine-staging is expected)
[00:14] <rdr> yeah if it works it doesn't matter if it's a little scuffed
[00:14] <WaV> cool
[00:14] <rdr> did playonlinux make the desktop file?
[00:15] <WaV> PlayOnLinux foobared the desktop file and I fixed it I guess you could say.
[00:15] <WaV> Wouldn't run at all.
[00:16] <WaV> PlayOnLinux had something like Exec=/usr/share/playonlinux --run "Program" %F
[00:16] <WaV> which did nothing
[00:31] <morganu> what is the keystroke to give me the list of key commands?   Please 20.04
[00:31] <morganu> I keep trying super this and that.
[00:32] <davetoo_> morganu: tab key?
[00:32] <morganu> oh no I turned on reading text. How to turn it off.?
[00:33] <morganu> is reading as I type.
[00:33] <sarnold> morganu: maybe windows+h ?
[00:33] <morganu> windows plus h isminimizing windows one at a time.
[00:34] <morganu> it brings this up as an infopage but not in chrome, just in ubuntu. https://help.ubuntu.com/stable/ubuntu-help/shell-keyboard-shortcuts.html
[00:35] <morganu> How do I get this to stop reading what I type and the title of every web page that comes up.
[00:35] <morganu> It even reads chars I cant see.
[00:35] <davetoo_> Ha! Ha! </nelson>
[00:37] <morganu> I tried activities but it just gives me a program (that I havent installed) that will read ebooks aloud.
[00:37] <morganu> Help this is reading every key I type out loud.
[00:38] <morganu> including shift keys
[00:39] <morganu> will reboot.
[00:46] <de-facto> is there a way to restrict the audio slider from wildly wiggling around on its own?
[00:46] <de-facto> its quite annoying because it creates a crackling noise
[00:47] <Peppi-> hello
[00:48] <Peppi-> on the cli how can I tell what ports are "open"
[00:48] <arraybolt3> davetoo_: Did you purposefully give malicious advice?
[00:48] <Peppi-> or rather how do I even know the firewall is working?
[00:48] <Peppi-> I have a feeling it must not be
[00:48] <Peppi-> by default
[00:49] <arraybolt3> davetoo_: Nevermind, I see sarnold said to use Win+H. I'm pretty sure he's not malicious, so this was just a mistake. Sorry, there was a channel emergency yesterday and I'm still a bit touchy after that...
[00:50] <sarnold> de-facto: maybe whatever application you're using has a setting for automatic gain or automatic output levels or something
[00:50] <arraybolt3> And I can't read... I'm getting the order of events all confused.
[00:50] <de-facto> sarnold, what is that? never heard of that?
[00:51] <de-facto> i am using firefox watching youtube
[00:51] <sarnold> Peppi-: iptables -L ? ss -lnp ?
[00:51] <de-facto> how can i disable automatic gain?
[00:51] <de-facto> i dont want any program to be able to control volume levels at all
[00:51] <sarnold> de-facto: oh weird, I thought you were using MS teams or skype or something like that
[00:51] <de-facto> not even tried that yet
[00:52] <Peppi-> sarnold, Try `iptables -h' or 'iptables --help' for more information.
[00:52] <de-facto> its an issue i always have with any version of ubunut
[00:52] <Peppi-> but think I might have it figured
[00:52] <de-facto> for years already
[00:52] <de-facto> basically anything autio is not really usable
[00:52] <de-facto> *audio
[00:54] <de-facto> sometimes its so bad that it only crackles, other times it perfect
[00:54] <morganu> SOLVED: System Settings -> Universal Access -> Seeing -> Screen reader -> Off Or a hotkey "Alt-Super-S"
[00:54] <de-facto> when it crackles i can see the audio slider wiggling around like crazy
[00:54] <de-facto> by itself
[00:54] <sarnold> morganu: woot
[00:55] <morganu> that was after rebooting didnt work.
[00:55] <morganu> It is called "narrator" but searching on the word accessibility worked.
[00:56] <morganu> sometimes my audio on zoom makes me sound like minnie mouse but not always. In any meeting it is either all fine or all squeaky. (not asking for help just commenting.)
[00:57] <morganu> I have given up and use a tablet
[00:57] <sarnold> morganu: heh, yeah, I've been doing all my meetings on an old android phone, their bluetooth works way better..
[00:58] <sarnold> morganu: I'm hoping that pipewire in 22.04 works well enough for the newer bluetooth codecs, I'm looking forward to trying it.. my ancient android phone has some hardware problems, one of these days it's not going to survive a reboot..
[01:44] <GSMarquis> My 6700xt fans wont ramp up. and my, mem  86c, junction 105c, edge 85c,
[02:16] <morganu> sarnold, what is pipewire...   PipeWire PipeWire is a project that aims to greatly improve handling of audio and video under Linux. It provides a low-latency, graph based processing engine on top of audio and video devices that can be used to support the use cases currently handled by both pulseaudio and JACK.
[02:16] <Unit193> Pipewire is to pulseaudio as pulseaudio was to alsa? :P
[02:17] <morganu> PipeWire is a multimedia framework
[02:17] <sarnold> Unit193: more like s/pulseaudio/pipewire/ ;)
[02:17] <morganu> I havent used those things.
[02:17] <Unit193> sarnold: Hmm?  pipey means to replace pulsey.
[02:18] <sarnold> Unit193: you know how gnome folks like to throw away and replace programs every few years? it took a bit longer with pulseaudio than usual ..
[02:18] <sarnold> Unit193: yeah
[02:18] <Unit193> I switched to pipewire twice, twice I ran into issues and had to go back.
[02:19] <morganu> sarnold, I understand that kind of thing. I have an old android tablet that cannot see a BT5. earbud etc.
[02:19] <morganu> Target used to have cheap phones.
[02:20] <sarnold> Unit193: for that authenticate pulseaudio replacement experience? :)
[02:20] <sarnold> it only took five-ish years for pulseaudio to get stable enough to use daily without pulseaudio -k first..
[02:21] <morganu> sarnold u.offtopic
[02:44] <morganu> ubuntu help fail: says Super+Tab
[02:44] <morganu> Quickly switch between windows. Hold down Shift for reverse order. == actual it switches between applications, not say, a set of open chrome windows.  ---  whoever wrote it just get it wrong.
[02:45] <morganu> alt-escape goes through all windows.
[02:49] <Nearrexa> Hi there! I'm looking to update my TLS CA Certificates, since they are outdated. How would I best go about this?
[02:50] <sarnold> I hear good things about certbot
[02:51] <Nearrexa> Isn
[02:51] <sarnold> I also hear good things about https://caddyserver.com/ but that's a pretty big switch
[02:51] <Nearrexa> 't cert bot for server-side certs?
[02:52] <sarnold> yes, that's normally what people update, heh
[02:53] <Nearrexa> I'm looking to update my client-side certificate authority stuff -- I'm having trouble connecting to many TLS servers. I have installed the latest ca-certificates package, I think.
[02:54] <sarnold> quite often site admins won't use the complete chain of certs; it's worth trying https://www.ssllabs.com/ssltest/analyze.html?viaform=on&d= on the sites you're using and seeing if they're misconfigured
[02:58] <Nearrexa> I'm pretty sure my CA certs are the same as they were in 2016, and my distro, a xenial compatible, hasn't received an update for them afaik.
[03:04] <jhutchins> Nearrexa: So you're running a non-Ubuntu installation that's six years old?  I would expec a number of things to be different, and if you were to try to fix it using Ubuntu 16.04 files or packages, you're likely to make things worse.
[03:05] <jhutchins> Nearrexa: Does the "compatible" distro not have any updates or upgrade path?
[03:05] <Nearrexa> jhutchins: I'm already using Ubuntu packages -- it's a Puppy.
[03:06] <jhutchins> Nearrexa: Mixing packages from different distributions is a great way to get practice doing clean reinstalls.
[03:06] <ravage> it is not supported here. seek support with their support channels :)
[03:07] <Nearrexa> ravaege: Alright. Do you think you could direct me to a channel where this is on-topic?
[03:07] <ravage> no idea. maybe https://forum.puppylinux.com/ ?
[03:08] <jhutchins> Nearrexa: Theoretically, you should be able to find, download, and install the certs on your own, but I'm not sure where you'd find anything step-by-step.
[03:08] <Nearrexa> ravage: I'm not looking for a Puppy-specific solution, just where to find CA certificates that are up-to-date.
[03:09] <jhutchins> Nearrexa: https://en.wikipedia.org/wiki/Certificate_authority
[03:09] <jhutchins> Start there.
[03:09] <Nearrexa> jhutchins: Is there maybe an index of some current consensus on root certs?
[03:09] <jhutchins> Nearrexa: I'm pretty sure there have been some changes in the signatures and encoding over that period.
[03:10] <jhutchins> Nearrexa: Maybe some of the older TLS howtos would have more details on how to build the chain.  http://tldp.org
[03:11] <jhutchins> Nearrexa: iirc you also have to identify and remove the certificates that have been revoked.
[03:12] <Nearrexa> jhutchins: That's fair. I'll try and see where I can get them, thanks for your help.
[03:12] <jhutchins> Nearrexa: https://www.exoscale.com/syslog/securing-web-properties-through-https/
[03:14] <jhutchins> The older and more generic docs are going to have more detail on the manual procedure.
[03:15] <Nearrexa> jhutchins: Not quite sure how that link would help, appears to be for servers mainly.
[03:16] <jhutchins> Nearrexa: Once you understand what's happening at the server end, you'll know what has to happen on the client end.
[03:16] <jhutchins> Nearrexa: I did a search on "tls howto" and there are several docs.
[03:16] <jhutchins> It used to be necessary to set this stuff up manually on both ends.
[03:17] <jhutchins> Lots of fun figuring out how to make a secure connection to a server that hasn't had anybody who knew how to make changes for years.
[03:17] <jhutchins> "We fired those guys.  They just sat around and told us how we couldn't do anything."
[03:18] <jhutchins> The receptionist changes the backup tapes.
[03:20] <jhutchins> WEll, I'm off to catch the ISS flyover.  See y'all in the morning.
[03:21] <jhutchins> Nearrexa: Good luck.
[03:21] <Nearrexa> jhutchins: My main issue isn't not understanding how TLS works in detail, it's not knowing where I can get accurate, recent certificates, I have a basic understanding about where to put certificates -- for me, they all appear to be in /etc/ssl/certs, in PEM format, and bundled into a ca-certificates.crt, presumably by update-ca-certificates
[03:21] <Nearrexa> Thanks
[03:21] <Nearrexa> Have fun
[03:41] <Guest89> mlaga97. I would think that by default, just slow down the read speed and wait for target disk.
[03:44] <mlaga97> @Guest89 Unfortunately, the kernel has no mechanism of being able to accomplish that and we are stuck with setting those parameters
[03:44] <darwin> no seamonkey .deb?! :O
[03:44] <mlaga97> That being said, I have no freaking clue why Ubuntu doesn't have it set to something sane out of the box
[03:46] <ywnkmn_> just wondering why pop!os is still using X server in 22.04? (it's based on Ubunntu)
[03:46] <ravage> !popos | ywnkmn_
[04:28] <davetoo_> arraybolt3: No, sorry, I was just making his text-to-speech laugh at him
[05:01] <brandoneliza> I think I am using the vesa framebuffer on startup grub boots at 1024x768 and my monitor native resolution is 1366x768 how to fix resolution?
[05:51] <timblechmann> hi! i'm running into https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402 ... basically the initramfs is corrupted (too big?), leaving my system unbootable
[05:53] <timblechmann> makes me wonder how to recover? booting into a livecd and chroot-ing into my system works, but i cannot change the configuration to `MODULES=dep` (the chrooted update-initramfs cannot infer the filesystem of `/` (as it's technically not mounted)
[06:18] <alkisg> timblechmann: the easiest way would be to use grub > advanced options > previous kernel/initrd
[06:18] <alkisg> Otherwise, mount /dev/sdax /mnt; cd /mnt; for d in proc sys dev dev/pts run; do mount /$d $d; done; chroot . update-initramfs -u;
[06:55] <timblechmann> alkisg, unfortunately the 22.04 update removed the previous kernels and `update-initramfs -u` in the chroot doesn't work with `MODULES=dep` (and that's necessary otherwise the initrd is too big) ...
[06:56] <alkisg> timblechmann: did you run the `mount --bind` commands that I said? If so, what's the exact error?
[06:56] <timblechmann> could hack my way around by scp-ing the kernel from another computer over and boot that ...
[06:58] <timblechmann> alkisg; yes ... i've bind-mounted proc/dev/sys ... with `MODULES=dep` `update-initramfs` will try to infer the partition type of `/`, but with the chroot environment `/` isn't listed in the mount (probably `/proc/mount`?)
[07:38] <unamalagestionyd> bajen a esa isabel mamana
[07:38] <unamalagestionyd> que no mande3 mas
[07:38] <unamalagestionyd> a turganti
[07:38] <unamalagestionyd> desde hace rato
[07:38] <unamalagestionyd> quien la subo
[07:38] <unamalagestionyd> subio
[07:38] <unamalagestionyd> que no mande3 mas
[07:38] <unamalagestionyd> que no decida as nada
[07:39] <unamalagestionyd> bastantes cagadas viene deciendiendo
[07:40] <unamalagestionyd> tiene la cabeza
[07:40] <unamalagestionyd> llena de ele3ctrodos
[07:40] <unamalagestionyd> y chips
[07:40] <unamalagestionyd> sauenselos
[07:40] <unamalagestionyd> asi no jode mas
[08:01] <T3sla> hi
[08:40] <Guest5673> anyone know a channel for webserver questions? got problems with pfsense-opnsense
[09:27] <neuromance> hi there! the latest ubuntu-proposed update in 22.04 broke my nvidia's gpu functionality.
[09:28] <neuromance> I can't work with driver version 515 nor 510 anymore ... The following packages have unmet dependencies: linux-modules-nvidia-510-generic-hwe-22.04 : Depends: linux-modules-nvidia-510-5.15.0-32-generic (= 5.15.0-32.33) but it is not going to be installed
[09:29] <neuromance> I had no problems running Nvidia drivers v515 (RTX 30-series) up until this morning
[09:30] <neuromance> the 5.15.0-32 kernel bump apparently broke it all since there's no nvidia packages for that, not in nvidia's own repositorys, not in the graphics ppa, not in ubuntu's proposed repos ...
[09:30] <neuromance> can't use nvidia's drivers v515 nor 510 ...
[09:31] <neuromance> (;__;)
[09:32] <neuromance> the card is right there with 'lspci'
[09:35] <ogra> neuromance, -proposed is something you should never enable permanently, it is the repo to check for broken dependencies ...
[09:35] <ogra> (before something goes into the archive)
[09:39] <neuromance> am wondering though over why is Nvidia offering only 510.68.02 as their latest Linux drivers for GeForce cards, and yet I can see v515
[09:40] <neuromance> also, running the Nvidia updater from their pages thinks I still have the driver v.515 installed even though I've purged+autoremoved it
[09:44] <neuromance>   ERROR: Failed to run `/usr/sbin/dkms build -m nvidia -v 510.68.02 -k 5.15.0-32-lowlatency`: Error! Your kernel headers for kernel 5.15.0-32-lowlatency cannot be found.
[09:44] <neuromance> Please install the linux-headers-5.15.0-32-lowlatency package or use the                  --kernelsourcedir option to tell DKMS where it's located.
[09:44] <neuromance> ^ any ideas?
[09:46] <ogra> you have a pretty messed up system ... did you do something like enabling proposed and running "sudo apt install nvidia*" ?
[09:46] <ogra> (seems you have many different flavours of the drivers installed)
[09:47] <neuromance> Reinstallation of linux-headers-5.15.0-32-generic is not possible, it cannot be downloaded.
[09:48] <neuromance> ogra nope, but I run the Nvidia devkits on this
[09:48] <neuromance> should I just purge all nvidia drivers and try from there on?
[09:48] <ogra> disable proposed (and leave it off), remove all nvidia driver packages you can find, make sure you have only linux-generic installed and running, then re-install 510 from the archive
[09:49] <neuromance> ogra already disabled proposed ...
[09:50] <neuromance> ogra thanks for the help. FYI; this is what I've got installed. https://pastebin.com/4BvatNX1
[09:51] <ogra> right, so try to move on from there ... try cleaning up all the nvidia packages, use apt remove --purge to make sure their config files are also gone (there is a lot "rc" in your list)
[09:52] <neuromance> thanks, will do, thank you so much for the help.
[09:52] <ogra> ... make sure you only have linux-generic and its whole dependency chain installed
[09:53] <ogra> then re-install the driver (preferably through the software-sources gui tool)
[09:53] <neuromance> ogra however my main concern is that the kernel got bumped to "5.15.0-32" with the latest update; my sysinfo says I'm running "5.15.0-32-lowlatency"
[09:54] <neuromance> (idk if I should run "generic" instead of "lowlatency" ? what's the differnce?)
[09:54] <ogra> why did you install that flavour at all ?
[09:54] <neuromance> this is a pretty new workstation
[09:54] <ogra> lowlatency is needed for something like realtime audio processing, i.e. if you want to run a recording studio
[09:55] <ogra> it is optimized for such a use case ...
[09:55] <ogra> if you did not know what it is when installing it, why did you install it ?
[09:55] <neuromance> well, this is a neural network training workstation
[09:56] <neuromance> ogra it was the only package available for this new kernel bump
[09:56] <neuromance> I do run TimeShift so I could always revert
[09:56] <ogra> well, it is not available yet
[09:56] <ogra> you pulled it from a testing repo (-proposed) that is not for general use
[09:57] <neuromance> yep ... I've usually used it without much hassles though, and I've noticed that if I don't enable it, something else gets dragged behind
[09:57] <ogra> enabling proposed and blindly running something like apt upgrade or apt ful-upgrade will definitely mess up your system
[09:57] <neuromance> well there we go again.
[09:58] <ogra> you should only enable it to pull a single package or a single set of packages for testing, then diable it again ... never do a full system upgrade with it enabled on a production system
[09:58] <neuromance> just what am I supposed to trust then when these are always coming through the software updater, and there's constant security bulletins on new threats and how you should keep up to date..etc.
[09:58] <neuromance> 22.04 worked pretty bad for me initially
[09:59] <ogra> it does for me too
[09:59] <neuromance> the only way it started to work somewhat "as expected", was to enable the proposed
[10:00] <neuromance> I mean with all due respect, it's an absurd statement of "not installing updates if you don't know what they are"? are you implying that I should go through the code myself whenever there's an update to my existing packages?
[10:00] <neuromance> and even then ... how would I know if they work without trying them?
[10:01] <ogra> neuromance, well, did you read the text above the proposed option in the software-settings app when you turned it on ?
[10:01] <neuromance> ogra yes I did, and that's why I'm reverting with timeshift atm
[10:01] <ogra> neuromance, really ?
[10:02] <neuromance> well, I just wanted people to know that it's broken and there's that
[10:02] <ogra> neuromance, i'm talking about this text that says that it will introduce instability: https://askubuntu.com/questions/785414/is-it-ok-to-enable-proposed-updates-during-ubuntus-development-cycle
[10:02] <neuromance> so that other people don't end up in the same situation if they i.e. have the proposed enabled
[10:02] <ogra> (IIRC it did not change since xenial, should still say the same (no english install here))
[10:02] <ogra> neuromance, well do not enable it
[10:03] <neuromance> yes, since there's no way to back it up because there's dependencies that aren't there yet, I'll just revert from my Timeshift dailies.
[10:03] <neuromance> I mean "back it up" = revert
[10:03] <ogra> right, and leave proposed off unless you want to test a single package
[10:04] <ogra> (or someone asks you to in a bug conversation on launchpad)
[12:08] <BluesKaj> Hi all
[12:13] <Tinkery> Hi all my friend uses Pysolfc, since 22.04 its broken, is the package broken or something, it starts and directly closes after launch
[12:16] <filename> ltrace/strace
[12:28] <rrr> how might I remove or disable netplan?
[12:33] <Descriptioned> Hello, how i can disable automatic turn on on startup of remote desktop sharing? and i cant see monitor sharing.. :(
[12:34] <Descriptioned> Help?
[12:35] <BluesKaj> rrr, why ?
[12:36] <ioria> Descriptioned, you mean : SystemSettings -> Sharing   ?
[12:37] <Descriptioned> ioria: yes
[12:37] <ioria> Descriptioned, go there and disable it
[12:37] <Descriptioned> i cant stop from autostart desktop sharing, and i can install screen sharing
[12:38] <Descriptioned> ioria: i disable it but it autostart every time i power on my laptop
[12:38] <rrr> BluesKaj, I created some unecessary bridge devices and kvm complains about it.
[12:38] <ioria> Descriptioned,  ps -A | grep -i vino
[12:39] <Descriptioned> ioria: nothing happends vino its installed.
[12:39] <BluesKaj> rrr, netplan merely points to networkmanager in my system
[12:39] <ioria> Descriptioned,  is it running ?
[12:39] <Descriptioned> i need to restart
[12:40] <Descriptioned> to see if its autostart again on startup
[12:40] <Descriptioned> fub@Fubatron:~$ ps -A | grep -i vino
[12:40] <Descriptioned> fub@Fubatron:~$
[12:44] <Descriptioned> ioria: desktop sharing it stills auto start on startup
[12:44] <Descriptioned> settings>sharing>remote desktop
[12:44] <Descriptioned> and sharing also on by it self
[12:45] <ioria> Descriptioned,  that thing is basically vino-server; if vino it's not running, it cannot be autostarted
[12:46] <Descriptioned> ioria: since i have vino and since i reboot laptop and i go to settings>sharing and it's on when  i restarted was off that means it on autostart . boh
[13:05] <tomreyn> ioria: i assume it's actually gnome-remote-desktop now (not vino), at least on 22.04 / wayland
[13:06] <oerheks> standard would be gnome-remote-desktop.service, not vino
[13:06] <oerheks> oh
[13:07] <tomreyn> which apparently provides an RDP service, not a VNC
[13:08] <tomreyn> or both? depends on libvncserver1 and libfreerdp-server2-2
[13:10] <tomreyn> ah, it's actually on the release notes
[13:15] <eno1> why my ubuntu dont have screen sharing, and that damn remote desktop turns on automatically after every restart? thanks.
[13:17] <tomreyn> how do you know it does not 'have screen sharing'? and which ubuntu version are you running, which graphical desktop / window manager / graphics server?
[13:18] <eno1> tomreyn: because on settings>sharing i cant see the screen sharing.. im on 20.04 i just installed it on my laptop before 2 days
[13:19] <eno1> escription:	Ubuntu 22.04 LTS
[13:19] <eno1> Release:	22.04
[13:19] <oerheks> eno1, build in RDP or your installed vino?
[13:19] <oerheks> vino is not in the settings, you need to disable it manually, i guess
[13:20] <WaV> vino is deprecated
[13:20] <eno1> oerheks: i dident see the screen sharing and then i installed vino, but i dident see screen sharing so i removed it the other problem now is that remote desktop it's autostarting on every startup
[13:21] <tomreyn> sudo apt update && sudo apt install vino_ gnome-remote-desktop
[13:22] <eno1> im crossing my fingers :P
[13:23] <eno1> E: Unable to locate package vino_
[13:23] <eno1> typing was correct? i just copy paste on terminal
[13:23] <tomreyn> does    ls ~/.config/autostart    list anything related to desktop sharing, such as *vino* *vinagre* *remote* *rdp* *rdesktop* ?
[13:23] <eno1> E: Unable to locate package vino_gnome-remote-desktop
[13:24] <tomreyn> hmm, i must have gotten the usage wrong, sorry
[13:24] <eno1> tomreyn: ls ~/.config/autostart does not show up anything
[13:25] <eno1> i installed this version on my laptop two days ago i also update/upgrade i installed only pidgin so i dident mess with anything, only with vino
[13:25] <tomreyn> eno1: sudo apt update && sudo apt purge vino && sudo apt install gnome-remote-desktop
[13:26] <rrr> I have a bridge configured that interferes with my internet connection and I can recover the connection by deleting the device in question in network-manager. How do I make this change permanent?
[13:27] <tomreyn> eno1:    echo $XDG_SESSION_TYPE    says what?
[13:28] <eno1> tomreyn: wayland
[13:28] <eno1> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[13:28] <eno1> fub@Fubatron:~$ echo $XDG_SESSION_TYPE
[13:28] <eno1> wayland
[13:28] <tomreyn> eno1: alright, did you run the apt commands above?
[13:28] <tomreyn> okay you did
[13:28] <eno1> sorry for flood
[13:29] <eno1> yea i did 0 upgrade 0 everything
[13:29] <tomreyn> let me see if i can reproduce the desktop sharing reactivating itself
[13:29] <eno1> ok thank you
[13:30] <eno1> i need to activate screen sharing also to share with my smart TV it does not appears on the list only "remote desktop" and "media sharing"
[13:30] <tomreyn> yes, reproduced. looks like a generic bug.
[13:32] <tomreyn> would you report this bug, eno1?
[13:32] <tomreyn> !bug | eno1
[13:32] <eno1> tomreyn: you can report it if you want
[13:32] <tomreyn> well, i'd prefer you doing so, because you mean to use it.
[13:32] <tomreyn> i'm not actually using 22.04 LTS
[13:33] <eno1> ok i will please if you can find me a solution for screen sharing that dont appears and how to stop autostart ON desktop sharing
[13:34] <tomreyn> now for the "dont have screen sharing", it's not clear how you tested, yet. can you describe this more?
[13:35] <eno1> settings> sharing> it apperas only (Remote Desktop) (media sharing) option no Screen sharing there
[13:36] <tomreyn> eno1: can you take a screenshot and post it on imgur.com or similar, then post the url here?
[13:38] <eno1> ok
[13:38] <oerheks> indeed, vino is not in that menu
[13:39] <tomreyn> here, it looks like this https://i.imgur.com/QGYvlhY.png and this https://i.imgur.com/vMdF6bi.png
[13:44] <eno1> tomreyn: https://ibb.co/jwzSbsQ
[13:44] <eno1> laptop crashed :/
[13:46] <eno1> https://imgur.com/a/qJTDraY
[13:46] <eno1> imgur also
[13:47] <tomreyn> crashed how?
[13:47] <eno1> https://imgur.com/QqO3kp4
[13:47] <eno1> i dont see screen sharing and remote desktop goes on by it self
[13:48] <tomreyn> you seem to have posted the same image 3 times now, intentional?
[13:49] <BaconPackets> Hey folks, I am trying to use the minimal Ubuntu images.
[13:49] <BaconPackets> My goal is to create a small custom image to use for common troubleshooting cases. It would be nice for that image to be extremely small.
[13:49] <BaconPackets> That said, these minimal cloud Ubuntu images seem to require uv-tools and might not be fully compatible with common virt-xxxxxx commands.
[13:49] <BaconPackets> Is there a better image that could be leveraged?
[13:49] <tomreyn> eno1: what happens when you click on the button to the right of the "Sharing" window title in the title bar?
[13:49] <ogra> tomreyn, likely because three times is a charm 🙂
[13:49] <eno1> https://imgur.com/E02VAwj
[13:50] <oerheks> BaconPackets, live-server should be perfect for thath
[13:50] <eno1> tomreyn: it goes off but as i restart it goes on automatically
[13:51] <tomreyn> eno1: so you are able to activate screen sharing. you are not able to permanently deactivate it - that's understood, which is why i suggest reporting a bug on that. but i'm now trying to understand why you are saying it is not usable when it's active?
[13:52] <eno1> tomreyn: its not usable yes
[13:52] <tomreyn> eno1: can you explain why you are saying so, how you tested, which errors you encountered?
[13:52] <eno1> and it autostart by it self on system restart i think i will go to reinstall Ubuntu its very weird because i did not tweak or installed anything else
[13:53] <BaconPackets> oerheks - Do you have a direct link to those .img? I am trying to sort three the 4-6 different .img Ubuntu seems to offer. '=D
[13:53] <tomreyn> eno1: reinstalling won't help overcome an actual software bug.
[13:53] <oerheks> https://cdimage.ubuntu.com/releases/22.04/release/
[13:54] <eno1> tomreyn: how i can share my laptop screen on smart tv if there is not an option
[13:55] <eno1> oerheks: thanks for the link
[13:55] <tomreyn> eno1: you attach a cable to the tv's hdmi or DP or USB-C port for video signal input
[13:55] <descent1> chromium
[13:55] <descent1> if you have roku
[13:56] <tomreyn> eno1: that's not remote desktop / desktop sharing
[13:56] <eno1> what i should download ? descent i tried everything
[13:56] <descent1> sudo apt install chromium-browser
[13:56] <ogra> eno1, does your TV have a chromecast app ?
[13:57] <ogra> you can use chromium to share to a chromecast ... and there is mkchromecast in the arhive to do dsktop charing via the chromecase protocol
[13:57] <ogra> *archive
[13:57] <ogra> geez ... my typing
[13:58] <descent1> i think roku shows up in chromium too
[13:58] <ogra> well, most android TVs have chromecast preinstalled nowadays anyway
[13:58] <ogra> for others you might need some extra app ... like roku
[13:59] <eno1> so i cannot share my laptop screen wirelessly on my smart tv ?
[13:59] <ogra> you can with mkchromecast
[13:59] <eno1> im on a new samsung tv
[14:01] <eno1> thanks guys <3
[14:02] <eno1> im going to install older build thanks
[14:02]  * ogra wonders what that means now ... 
[14:02] <ogra> ... but we'll probably never know 🙂
[14:02] <tomreyn> unless "it does not work"
[14:03] <tomreyn> i don't expect i can count on them to file the bug also
[14:07] <rrr> network-config isn't preserving the network state I have configured and one bridge device isn't staying disabled, what can I try?
[14:07] <sahil> apt update
[14:07] <sahil> hey!
[14:12] <rrr> I have a broken package where libnvida-common can't be removed and it conflicts with libnvidia-common-510
[14:22] <rrr> ooh, I mayve purged all nvidia packages.
[14:25] <tomreyn> rrr: if you make changes in network-manager (though i'm not sure what "network-config" is?) they should persist, unless you have setup something which creates configurations outside of it.
[14:25] <tomreyn> my guess is you're using some third party vpn which comes with broken scripts.
[14:27] <rrr> well the vpn is doing okay, I didn't suspect it.
[14:27] <rrr> it is using network-manager as well.
[14:55] <rrr> ahh hah, my problems resolved.
[15:06] <jhutchins> We may never know ...
[15:07] <BluesKaj> maybe he edited resolv.conf
[15:08] <BluesKaj> and dumped network-manager...that method used to work before systemd
[15:31] <rrr> open source nvidia provide drivers...
[15:31] <rrr> what's that
[15:33] <Maik> !ot | rrr
[15:36] <rrr> I am already registered
[15:37] <BUSY> is there a better tool than netstat or ss for checking the network bandwidth usage from one particular process?
[15:41] <jhutchins> BUSY: I think you'd probably have to get into something like Wireshark that can examine packets in order to categorize what traffic is associated with what process.
[15:41] <jhutchins> BUSY: Some routers have that kind of capability.
[15:57] <Maik> rrr: just to let you know that offtopic is a better place to discuss that
[15:58] <Wlamber> Hello, I got a question concerning setting up NThost in my inittab. Now Ive understood that inittab no longer excists in Ubuntu (for a while now but hey never heared of it :P) But how can I sort this out and where about should I add this piece of code?
[15:58] <Wlamber> The code:     pvx1:235:respawn:/pxplus/pxplus \*nthost -ARG port uid umask >/dev/null </dev/null
[15:58] <Wlamber>  Where pvx1:235:respawn  'inittab' parameters that cause UNIX to spawn *NTHost at all normal execution levels and keep it running.
[15:58] <Wlamber> pxplus/pxplus
[15:58] <Wlamber>  Location of the PxPlus executable.
[15:58] <Wlamber> \  *nthost
[15:58] <tomreyn> !paste | Wlamber
[16:01] <Wlamber> Hello, I got a question concerning setting up NThost in my inittab. Now Ive understood that inittab no longer excists in Ubuntu (for a while now but hey never heared of it :P) But how can I sort this out and where about should I add this piece of code?
[16:01] <Wlamber> To run *NTHost as a UNIX service, add a line similar to the following to the system 'inittab' file (usually in the directory /etc/):
[16:01] <Wlamber>     pvx1:235:respawn:/pxplus/pxplus \*nthost -ARG port uid umask >/dev/null </dev/null
[16:01] <Wlamber> Where:
[16:01] <Wlamber> pvx1:235:respawn
[16:01] <Wlamber> 'inittab' parameters that cause UNIX to spawn *NTHost at all normal execution levels and keep it running.
[16:01] <Wlamber> Note:
[16:02] <ogra> !paste | Wlamber ...
[16:02] <tomreyn> Wlamber: please read what ubottu told you above. last chance.
[16:03] <tomreyn> Wlamber: you can talk again now, but don'T copy and paste again
[16:05] <Wlamber> Hello, I got a question concerning setting up NThost in my inittab. Now Ive understood that inittab no longer excists in Ubuntu (for a while now but hey never heared of it :P) But how can I sort this out and where about should I add this piece of code? https://paste.ubuntu.com/p/qfQc8pKyx5/
[16:06] <tomreyn> Wlamber: which ubuntu version are you running, and how did you install pxplus (and which version of it)?
[16:06] <tomreyn> we usually only support software which comes with ubuntu here, you may or may not be able to get support here with pxplus
[16:07] <Wlamber> I am running Ubuntu server 20.04. Pxplus isnt installed as a service, it just registered itself to get a serial code. Its located in the /home/pxplus directory (need to chance that in the innit file ofcourse)
[16:08] <Wlamber> And the pxplus version is  PxPlus Development Suite 2021 Sep 2021 (Current Build V18.20)
[16:10] <tomreyn> Wlamber: so you downloaded the "Ubuntu Version 20 (Focal Fossa) (64 Bit)" archive named pxp1820-0000-U20-64.taz from https://home.pvxplus.com/pgsrvr.pvp?pg=dl_pxp1820 and unpacked it in your /home/someusername ?
[16:10] <Wlamber> correct, it is running so thats all fine
[16:12] <Wlamber> But when a client connects that NThost should start a new instance (if I understand it correctly) Their installation guide tells me to add that pastbin code to the innittab file, but Ubuntu no longer uses that but instead uses Upstart, but I am a tad bit lost with that :)
[16:12] <Wlamber> https://manual.pvxplus.com/PXPLUS/windx/nthost.htm this is their guide written out
[16:15] <tomreyn> talk to "pxv plus" and ask them to fix their "Ubuntu 20" release - which is actually "Ubuntu 20.04 LTS". Ubuntu 20.04 uses systemd, inittab has not been supported for a long time. They will need to come up with a systemd unit.
[16:16] <tomreyn> (you could also learn to write a systemd unit which does this yourself)
[16:16] <Wlamber> since its one line I recon that would be the easyest way (doubt theyll add that code)
[16:18] <ogra> Wlamber, well, inittab has not been used for more than a decade in ubuntu (or most other major linux distros)
[16:21] <Wlamber> ogra that explains why I never heared of it, Ill try finding out how to write that piece of code in a systemd command. Do you guys perhaps have any pointers for where I could look? :)
[16:26] <tomreyn> Wlamber: http://manpages.ubuntu.com/manpages/focal/en/man5/systemd.service.5.html
[16:27] <tomreyn> and http://manpages.ubuntu.com/manpages/focal/en/man5/systemd.unit.5.html
[16:28] <tomreyn> if you have the man-db package installed, you can also access these on your computer using   man 5 systemd.service   and    man 5 systemd.unit
[16:29] <Wlamber> Oke :)  Ill go cry in a corner while I try to read through these! :)  Thanks for your help thus far
[16:52] <rrr> how can I check what version of nvidia-driver is running?
[16:53] <kostkon_> !details | rrr
[16:53] <rrr> I tried nvidia-smi but I wanted to test if I compiled and installed the open-sauce drivers correctly.
[16:55] <tomreyn> lsmod     lists loaded modules,     modinfo somemodule     provides information on module "somemodule"
[17:52] <ioria> tomreyn, if you're still interested : https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1971415
[18:06] <july> hello, i'd like to know if the new lts version is capable of legacy bios boot with auto partitioning installation method?
[18:08] <EriC^> july: it should
[18:09] <oerheks> all ubuntu' s are, AFAIK
[18:20] <cbreak> I read that bios boot stuff via grub has problems with 4k sector drives... (not just in ubuntu)
[18:23] <oerheks> not seen issues with 4k sectors and grub2
[18:23] <oerheks> and is that relevant?
[18:23] <cbreak> maybe
[18:24] <leftyfb> legacy BIOS's are limited to 512b sectors and won't seek drives with 4k. That's a hardware limitation, nothing to do with the OS
[18:25] <cbreak> so ubuntu can't be installed on such drives for legacy booting, because the drives themselves aren't supported for legacy booting
[18:26] <leftyfb> cbreak: nor can any other OS on the planet
[18:26] <cbreak> exactly
[18:26] <leftyfb> nothing to do with the OS, the BIOS doesn't see the drive at all
[18:27] <cbreak> maybe it could be made work by offloading the boot loader to some external device, like an usb stick
[18:27] <cbreak> nothing I'd want to run productively :/
[18:27] <leftyfb> you know it's the BIOS that reads the hardware plugged into it right?
[18:27] <leftyfb> it has nothing to do with the boot loader
[18:28] <leftyfb> if the BIOS doesn't see the drive, no amount of software is going to fix that
[18:30] <cbreak> the bios doesn't have to see the hardware if you put the bootloader on an other device which the bios sees, and then the boot loader can continue the boot process. Or do you mean that grub can't load devices that aren't recognized by the bios itself, even when it is invoked correctly?
[18:31] <leftyfb> if the BIOS doesn't recognize a device, the OS isn't going to either
[18:31] <leftyfb> put another way, if the BIOS doesn't recognize a device, full stop
[18:31] <cbreak> I'm not convinced. Because an OS can use 4k drives on a computer booted from a bios
[18:31] <cbreak> just not for booting off of
[18:33] <ogra> you could use a floppy to boot, once the kernel is up and has a driver for the controller it surely should see the disk ...
[18:33] <cbreak> or... a usb stick...
[18:33] <ogra> (will just be hard to find a floppy drive 😛 )
[18:39]  * alkisg wasn't able to install ubuntu 22.04 server on MBR, it kept crashing; had to switch to GPT, install, backup, reformat as MBR and restore :/
[18:41] <lotuspsychje> there are some bugs & stuff to read on jammys releasenotes (if its your case(s))
[18:43]  * alkisg hasn't seen any issues about MBR mentioned in the release notes
[18:43] <alkisg> I've reproduced it 3-4 times though before giving up...
[18:43] <lotuspsychje> kk
[18:45] <july> No.  Auto partitioning creates UEFI boot partition so you have to set your bior to uefi mode. With manual partitioning you can set up normal /Boot mbr
[18:45] <alkisg> With manual partitioning and setting up mbr, it crashes
[18:46] <alkisg> (the server one, not the desktop)
[18:46] <leftyfb> july: if you have an answer, why did you ask the question?
[18:46] <lotuspsychje> ravage: did your bug got resolved yet on setup?
[18:48] <ravage> no
[18:48] <lotuspsychje> you had a crash too right ravage ?
[18:49] <ravage> i have a destroyed system on zfs with snaps :)
[18:50] <lotuspsychje> kk
[18:58] <ravage> downloaded morbius
[18:58] <ravage> heh
[18:59] <ravage> never mind
[19:30] <july> leftyfb I wanted to know if anybody knows this
[19:34] <cbreak> alkisg: why not use efi booting?
[19:34] <cbreak> ravage: the https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066 problem?
[19:35] <oerheks> Juan, if your machine has UEFI, you want to override the bootmenu with legacy mbr boot, it should be available
[19:35] <cbreak> I'm still holding off switching to 22.04 from 21.10 because of that
[19:35] <oerheks> Juan, sorry, for july who boots the channel
[19:36] <cbreak> I'm also currently considering uninstalling zsys, anyone got any experience with that?
[19:49] <lsd|2> krycha UFC!!!
[19:49] <mrkubax10> wrong channel I guess :D
[20:38] <ravage> cbreak, yes that one
[20:39] <cbreak> maybe I should just split my boot pool
[20:39] <cbreak> and upgrade one of the halves :D
[20:51] <r4fkramer> Hello everyone. This is my first time here after more than 5 years in absence. I have Ubuntu installed continuously in a virtual machine, and now I also want to install Ubuntu 22.04 LTS in bare metal mode.
[20:52] <r4fkramer> I'm Debian User, but I gonna install Ubuntu in real hardware thanks to ZFS features installed and integrated directly in kernel, that impresses me a lot.
[21:01] <r4fkramer> My question is: in version 20.04 LTS ZFS is treated as still in an experimental phase, therefore not fully stable. Please, I'd like to know if this status remains the same in the 22.04 LTS release, or if ZFS in this release can be considered definitively stable for use as a Server in a production environment (Database Server).
[21:01] <cbreak> r4fkramer: zfs is nice in ubuntu, but the encryption support isn't straight forward. And in 22.04 there's this: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1970066
[21:02] <cbreak> I use zfs on ubuntu at work with hundreds of TB of data, and it's quite nice
[21:02] <cbreak> but not as boot filesystem
[21:02] <r4fkramer> Thanks for answering cbreacck and ubottu.
[21:02] <cbreak> (Here at home I boot off of zfs, which also works, but I did some manual ... things for it :)
[21:03] <r4fkramer> Please cbreack, you said you use it in a server with hundreds of TB..Hundreds ?
[21:04] <cbreak> well, two servers with slightly more than 100 each
[21:04] <cbreak> also, you should get an irc client with autocomplete :D
[21:05] <r4fkramer> Sorry, not so clear: getting an IRC Cliente with autocomplete ?
[21:05] <r4fkramer> What does 'autocomplete' mean in this case ?
[21:05] <cbreak> yeah. then you only have to type cb<tab> and won't have to mis-spell my name :D
[21:05] <r4fkramer> Oh fine, thanks
[21:06] <cbreak> to me, zfs support in ubuntu seems production ready.
[21:06] <cbreak> boot-zfs support isn't well integrated
[21:06] <cbreak> I don't think it's even available in the server install, and it does weird things for the desktop installer
[21:06] <cbreak> but for separate data pools it works well
[21:06] <r4fkramer> Ok, this information you provide is too important for me.
[21:08] <r4fkramer> I intend to install ubuntu 22.04 in real hardware next days, but with zfs, not ext4, just for tests and to learn a little bit more about zfs features. Do you consider a good intention ? Or, should I use another OS to practice zfs, such as Open Indiana or FreeBSD ?
[21:08] <r4fkramer> I'd like to get it running fine in a Linux Distro, that is why I opted for Ubuntu.
[21:10] <cbreak> any of them will work.
[21:11] <cbreak> OpenZFS is now a shared codebase between linux, macos and the BSDs
[21:12] <r4fkramer> I don't want to bore you with these questions, but being a total beginner, my level of doubts is still very elementary.
[21:12] <r4fkramer> Do you consider ZFS to be as stable on Ubuntu as it is already on FreeBSD or Illumos Distros?
[21:12] <r4fkramer> According you said above...
[21:15] <cbreak> I've not noticed a difference in stability
[21:15] <r4fkramer> Despite the fact it does weird thinks for the desktop installer...
[21:15] <cbreak> and nowadays it's a shared codebase, so a lot of the code is the same anyway
[21:17] <ravage> i use ZFS on 22.04. so far no problems except the bug mentionen above. i installed it before the release and somehow my system is not affected. i can use snaps.
[21:17] <r4fkramer> Fine cbreak, You were a 'Light at the end of the tunnel' now, explaining these important details to me. I have other questions that I will bring here with time, but I just have to thank you for your attention and patience:)
[21:17] <ravage> the integration of ZFS in Ubuntu aside (zsys) ZFS is very stable in linux
[21:18] <ravage> i use it on a lot of storage servers
[21:18] <r4fkramer> Fine ravage, thanks for answering. So, except for the bug described above, haven't you never experienced any issues with ZFS in ubuntu 22.04 LTS ?
[21:19] <ravage> you may have to clean up your system and boot pool snapshots from time to time
[21:19] <r4fkramer> Oh, I see.
[21:19] <ravage> there is no auto clean yet
[21:20] <ravage> every kernel update and apt operation creates a snapshot and en entry in your grub menu
[21:20] <ravage> *an
[21:20] <cbreak> r4fkramer: there's #zfsonlinux as well, for zfs related questions. and #zfs of course
[21:20] <r4fkramer> I saw openzfs requirements specifically for 22.04 in openzfs official site
[21:21] <r4fkramer> Thank you very much for information cbreak.
[21:21] <r4fkramer> yes, ravage, I noticed about it before - it creates snapshots all the time
[21:21] <r4fkramer> news entries in grub menu
[21:27] <SuperLag> RHEL has a kickstart config tool... is there something like that for Ubuntu?
[21:27] <cbreak> what does that tool do?
[21:28] <r4fkramer> I'll start visiting the ZFS-specific channels suggested here. If you have any suggestions about Documentation or book about openZFS, I would appreciate it.
[21:28] <SuperLag> kickstart file is like an answer file that contains all the install-time options you want to set. It's a way to automation your installs.
[21:28] <oerheks> Ubuntu no longer officially supports the old debian installer / kickstart files. At least we went with cloud init instead reinventing another standard
[21:29] <ravage> and it kind of works :P
[21:29] <oerheks> https://cloudinit.readthedocs.io/en/latest/topics/examples.html
[21:30] <r4fkramer> Last question: Apparmor is more natively integrated into Debian based Distros than SELinux. I would like to know if there are any specific unresolved issues regarding SELinux being configured on Ubuntu.
[21:31] <gordonjcp> r4fkramer: SELinux exists, which is an unresolved issue
[21:31] <oerheks> r4fkramer, look at launchpad bugs?
[21:31] <r4fkramer> I'd rather using it instead of Apparmor in Ubuntu 22.04
[21:31] <ravage> selinux is disables in Debian and Ubuntu by default. You can use it of course. https://wiki.debian.org/SELinux
[21:31] <oerheks> good luck with that
[21:32] <r4fkramer> Thank you ravage
[21:32] <ravage> the ubuntu wiki is so outdated that it links to Ubuntu
[21:32] <ravage> that may be warning enough :)
[21:32] <ravage> eh links to debian
[21:32] <r4fkramer> OK ravage, I'll take care about it. Really thank you very much for advertisement :)
[21:33] <gordonjcp> r4fkramer: you could use SELinux, or if you really wanted to be secure you could just run a drill through the motherboard in a few spots
[21:34] <gordonjcp> r4fkramer: it won't work with a bunch of 16mm holes drilled through the PCB, but it will work just as well as with SELinux and consume a lot less power
[21:34] <r4fkramer> Never looked at it before, oerheks.
[21:35] <oerheks> *depending the wattage of that drill
[21:35] <gordonjcp> oerheks: true
[21:35] <cbreak> is selinux better than just running the thing inside lxc?
[21:35] <gordonjcp> no
[21:36] <cbreak> good.
[21:36] <gordonjcp> SELinux is terrible
[21:36] <cbreak> lxc is quite nice
[21:36] <gordonjcp> at least in my opinion
[21:36] <ethanhs> Hi, I am trying to use virt-install with --install, which queries libosinfo. It seems however that the Python bindings may be broken, because when I try to run Libosinfo.Loader().get_db().get_os_list().get_length() I get 0, which seems to be indicating that it isn't finding the correct osinfo files. I queried dpkg and the xml files do seem to be installed to /usr/share/osinfo
[21:36] <gordonjcp> and you know what they say about opinions
[21:36] <gordonjcp> but it always seems like SELinux is a kind of "here's how to patch things up so the security holes aren't *too* leaky"
[21:36] <gordonjcp> rather than just doing it right in the first place
[21:38] <r4fkramer> gordonjcp, Do you consider SELinux itself a bad choice, or just in case it is configured on Ubuntu instead of Apparmor ?
[21:38] <r4fkramer> In Rocky Linux it works fine
[21:39] <r4fkramer> for it's natively configured in RHEL, Alma Linux and Rocky Linux.
[21:42] <r4fkramer> Thank you very much for attention and Great Support !:) Bye all !
[21:42] <gordonjcp> aw, they left