[00:54] <howudodat> unable to get my laptop to suspend (Power Off -> Suspend).  https://pastebin.com/psJi9zYG logfile shows some devices failed to suspend or early wake event detected.  on V22.04
[00:57] <oxfuxxx> double check you have as much swap-space as internal laptop RAM, it might be something else tho.
[00:59] <arooni> anyone know how to address this error message in unison when invoking from cron:  https://gist.github.com/arooni/e54557482e05d2319a217cdc7009c6ec
[00:59] <howudodat> yikes, my swap has never been that large.  I have 64G mem and 4G swap.  BTW, it did suspend with 20.04
[01:23] <arooni> anyone have any guidance? https://github.com/bcpierce00/unison/issues/712
[02:47] <xamboni> I built a desktop tower around mid year 2021 and loaded Ubuntu 20.04. Everything went well in the beginning but the transition from 5.11.0-46-generic to 5.13.0-27-generic now hangs on boot. Today I connected my serial port and directed prints to ttyS0. The first error I see is "[FAILED] Failed to mount Mount unit…-common-themes, revision 1515." Are there any steps I can take to try and isolate this error in 5.13?
[02:50] <xamboni> I can provide the full boot log if there is a convenient place to upload it.
[02:51] <xamboni> I am comfortable debugging the kernel but this appears to be user space. If I skipped steps for asking about an issue I apologize and can review rules.
[02:53] <lotuspsychje> xamboni: if you can boot into an earlier kernel and compare this with current 5.13 maybe you could file a !bug about that
[02:53] <xamboni> lotuspsychje: Would that be comparing prints during the boot process? I can still boot into 5-11.0-46.
[02:54] <lotuspsychje> xamboni: no i mean comparing kernels and prove its 5.13 faulty, if you can indeed still boot into 5.11
[02:55] <lotuspsychje> is that a server or desktop xamboni ?
[02:56] <xamboni> This is a desktop.
[02:56] <lotuspsychje> ok
[02:57] <xamboni> lotuspsychje: Ok I will pull the diff between the two kernels and see if anything sticks out. The chances of this being a kernel issue are high? Given my boot gets past init.d I initially thought this might be something Ubuntu related.
[02:59] <lotuspsychje> xamboni: well if you can still boot earlier kernel(s) we could assume its a 5.13 thing, but maybe more logs might give us more insights about what actualy happens
[03:00] <xamboni> lotuspsychje: Ok, probably a good idea to get a good log out of 5.11 before I continue. I can paste bin my current complete log if that helps for now.
[03:01] <lotuspsychje> sure, share it with the volunteers, maybe someone can pinpoint soomething
[03:03] <xamboni> lotuspsuchje: Thanks for the help. The entire log can be found here: https://pastebin.com/9FMDsJF1
[03:05] <lotuspsychje> xamboni: [FAILED] Failed to mount Mount unit… gnome-3-38-2004, revision 87. doesnt look too good either
[03:06] <lotuspsychje>  34.117963] watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [systemd-udevd:443]
[03:07] <lotuspsychje> not sure what this is myself xamboni kernel or snapd...
[03:07] <lotuspsychje> !info linux-image-generic focal
[03:08] <xamboni> lotuspsychje: Seems to be along the lines of systemd which is out of my wheelhouse for sure. I usually focus on getting the kernel up and ok so this is new to me.
[03:08] <lotuspsychje> xamboni: is your system up to date?
[03:08] <lotuspsychje> otherwise you could try some things on recoverymode
[03:09] <xamboni> I would think it is up to date unless there is something I can try outside apt upgrade.
[03:09] <lotuspsychje> xamboni: apt doesnt complain about something?
[03:10] <xamboni> lotuspsychje: At the moment no.
[03:10] <lotuspsychje> kk
[03:12] <lotuspsychje> if it was snapd issue, we could purge and reinstall it for testing, but if its runs fine on 5.11 must be a kernel combo thing
[03:12] <xamboni> Hmmm this is a tough one. First things first though. Let me get a good boot log so I can see what the next print should be.
[03:35] <tomreyn> xamboni: "Optimized the system compatibility" *could* be relevant (you have 1.80) https://www.asrock.com/mb/Intel/B560M-HDV/index.asp#BIOS
[03:40] <xamboni> tomreyn: Thinking I might try updating the BIOS?
[03:41] <xamboni> I can try that real quick. Thanks for the suggestion.
[03:43] <tomreyn> xamboni: it's a far fetched idea. should not do harm. but i'm not sure what really happened.
[03:44] <xamboni> tomreyn: Not a bad idea though. I'll try it now. Thanks for the input.
[04:00] <xamboni> Sadly still a failure after the BIOS upgrade.
[04:02] <tomreyn> xamboni: still a cpu core lockup?
[04:02] <wez> BIOS still exists? I thought it was all EFI / firmware these days.
[04:03] <tomreyn> mainboard vendors still callit BIOS, though, "UEFI BIOS"
[04:04] <xamboni> tomreyn: I don't have the log this time because it was a quick boot but still the same bios splash hang.
[04:04] <xamboni> wez: :) you are right.
[04:04] <tomreyn> !bootlog
[04:05] <tomreyn> or use your serial console and log the output ;)
[04:05] <xamboni> I log ttyS0. It is a nicer setup.
[04:06] <wez> tomreyn: yeah but it's not really the right term to use any more right?  I mean the same as using the term SSL, that has been deprecated for years now.
[04:06] <tomreyn> wez: i concur.
[04:06] <wez> tomreyn: And lets see, another still used term that is deprecated is 1st, 2nd and 3rd degree burns.
[04:07] <xamboni> wez: Spot on. I am old though..
[04:07] <wez> I think we need to sort this all out :)
[04:07] <tomreyn> xamboni: maybe do some stress testing on the old kernel if you still have it
[04:08] <tomreyn> you should be able to switch to it from the grub menu
[04:08] <xamboni> I have the old kernel. I have to fall back to use the machine.
[04:08] <wez> Make those terms taboo like a number of common words that have been banned due to racial or other modern day colloquialisms being associated with them.
[04:11] <xamboni> wez: I was able to boot into the older BIOS over firewire. Sadly DES encryption is just too much for the older firmware to handle.
[04:11] <wez> xamboni: I thought DES was broken too.
[04:11] <xamboni> Thank you guys for the input. I'll sit down tot his issue a bit more this weekend and see if I can pinpoint the hang.
[04:12] <xamboni> wez: ... I was just trying to think up older terms and get them in the same sentence. :)
[04:12] <wez> xamboni: :P
[04:13] <wez> xamboni: Speaking of old things, I miss the turbo button on my computer :(
[04:15] <xamboni> wez: I was looking at pckeyboard.com (unicomp keyboards) to try and get a ps/2 old style buckling situation going again.
[04:22] <xamboni> Thanks for the input. I'll check back once I get more info on the mysterious boot hang.
[04:39] <webchat38> Hello.
[04:40] <webchat38> Is this a chat room where i can ask for help regarding my ubuntu OS?
[04:42] <yupeak> yes
[04:42] <wez> webchat38: https://www.nohello.com
[04:42] <webchat38> hi, Thnak you for responding
[04:42] <webchat38> so i just upgraded my ubuntu
[04:43] <webchat38> from the previous version 21.10 to the new 22.04
[04:44] <webchat38> but the upgrade completed it seems that there is a major issue with my system
[04:44] <webchat38> when the PC restarted...
[04:44] <webchat38> the initial screen and the grub menu looked ok..
[04:45] <webchat38> i have installed 3 OS's in my system
[04:45] <webchat38> windows 10, Linux mint and Ubuntu....
[04:46] <webchat38> although im still just a beginer i guess with linux and dont have much knowledge about much of the commands etc..,
[04:47] <webchat38> i still like to learn more about linux ona daily basis
[04:47] <webchat38> now the problem is..
[04:48] <webchat38> or rather are...
[04:49] <webchat38> the grub menu shows the Previous version of Ubuntu even after the update, which is not the biggest problem though......
[04:49] <webchat38> but after i select ubuntu...
[04:50] <webchat38> the system starts with everything being big..
[04:50] <webchat38> as if there is a something wrong with the display settings..
[04:51] <webchat38> just to inform you, i have never faced this problem in any of my previous upgrades that i ahve done..
[04:52] <webchat38> now, the screen from the ' loading 22.04 ' proceeds ahead to the password screen after which i enter my password and then it logs on...
[04:53] <jStefan> did you intend to keep the old version ?
[04:53] <webchat38> but the display settings are still not adjusted
[04:53] <webchat38> no, its now the new version and i dont wanna revert back to the old version
[04:54] <webchat38> so i went into the display settings and i checked to find "unknown resolution"...
[04:55] <webchat38> with only the option for one setting ( i think some 480*640 or so)
[04:56] <webchat38> so then i googled the matter under "unknown resolution"
[04:56] <webchat38> and seeked the help of several sites including ubuntu forom's
[04:57] <webchat38> here's a list of the things that i have tried that have words for some according to what i have read
[04:58] <webchat38> changed the setting of language to English US everywhere...
[04:59] <webchat38> using the GUI checked for additional drivers....which said non avabl
[05:00] <webchat38> even used the terminal for apt update upgrade...
[05:00] <jStefan> hmm
[05:01] <webchat38> the checked the mutiverse etc repository setting if it was checked in the gui
[05:01] <jStefan> when you go to "additional drivers", what driver does it say its currently using?
[05:02] <webchat38> later even found out that my sound is not working..
[05:02] <webchat38> bluethooth is not getting detected
[05:03] <alkisg> webchat38: it's possible that you're using mint's grub, which points to old ubuntu's kernel
[05:03] <alkisg> In that case, you need to run `update-grub` from inside the new ubuntu, so that it re-generates grub.cfg
[05:03] <alkisg> Try sudo update-grub, then reboot
[05:03] <webchat38> when i went to additional drivers in the gui it just said something like non required
[05:03] <alkisg> Then go to mint, then sudo update-grub from there as well
[05:03] <webchat38> i did the upgrade grub as well
[05:04] <webchat38> and then rebooted
[05:04] <alkisg> In both your linux installations?
[05:04] <webchat38> but all the problems still persist
[05:04] <webchat38> no only in ubuntu
[05:04] <alkisg> What's the output of: uname -a
[05:06] <webchat38> the the thing is....my linux mint after i upgraded that and performed a update, it just gets stuck at the password screen and even if i enter the correct password it loops back to the enter passord screen and im unable to even reach the desktop
[05:07] <alkisg> In your Ubuntu installation, what's the output of: uname -a
[05:07] <webchat38> as my unbuntu was working i didnt bother to go deep into the issue with mint
[05:08] <webchat38> " output of Uname -a" could u let me know what this is? as in?
[05:09] <alkisg> You open a terminal, run `uname -a`, and tell us the result
[05:09] <alkisg> It will show your kernel version
[05:09] <webchat38> so im just a beginner with linux, forgive me for my lack of knowledge
[05:09] <webchat38> ok ill need to check that
[05:09] <alkisg> You're on windows atm?
[05:09] <webchat38> im right now using my windows OS
[05:10] <webchat38> yes
[05:10] <alkisg> OK, reboot and join from Ubuntu
[05:10] <webchat38> ok
[05:10] <webchat38> let me try loging in from my phone as well using a browser in case i can
[05:11] <webchat38> now how do i come with the same id
[05:11] <webchat38> lol
[05:11] <webchat38> let me just check
[05:12] <alkisg> It's best to provide a nickname so that people remember you; and replace that webchatXX one
[05:13] <webchat38> im just checking what i can do
[05:14] <webchat38> ok
[05:14] <webchat38> so on my phone i've joined in as another user
[05:14] <webchat38> 'webchat3852'
[05:14] <webchat3852> It's working here
[05:15] <webchat3852> So i guess I'll try messaging from here then
[05:16] <webchat38> im now going to close this chat and continue as 'webchat 3852'
[05:22] <webchat3852> Sorry for the long wait
[05:23] <webchat3852> I realy thank everyone in advance for helping me out here
[05:23] <webchat3852> Was stressed out about this since the past almost 9 hours now
[05:24] <webchat3852> I appreciate all the help
[05:24] <webchat3852> My pc is now restarting
[05:24] <webchat3852> I'll load Ubuntu and open a terminal
[05:25] <webchat3852> Hopefully in the next one minute approximately
[05:27] <webchat3852> Ok just entered my password
[05:27] <webchat3852> Now starting a terminal
[05:29] <dadofapollo> webchat3852: I can't really help with the actual problem but here is a link to register a nick https://libera.chat/guides/registration
[05:30] <webchat3852> Ok so after running the uname -a...
[05:31] <webchat3852> It says..
[05:32] <webchat3852> 5.13.0-28 generic # 31 Ubuntu
[05:35] <alkisg> webchat3852: 22.04 has 5.15 kernel; you're booted with the older kernel which isn't properly installed anymore
[05:35] <alkisg> webchat3852: what's the output of this? ls -l /sys/firmware/efi
[05:36] <webchat3852> Let me check
[05:36] <alkisg> And also this: ls -l /boot | nc termbin.com 9999
[05:43] <webchat3852> Ok i think I'm doing something wrong
[05:43] <webchat3852> So for the second one..
[05:44] <webchat3852> I.e ls -l / boot...
[05:44] <webchat3852> I'm getting ' https ://termbin.com/mfgf
[05:45] <webchat3852> And for the first one I'm getting an error, but let me do it again
[05:51] <alkisg> webchat3852: OK now run: sudo dpkg-reconfigure grub-pc
[05:51] <alkisg> And press "enter" in all prompts
[05:51] <alkisg> This will allow Ubuntu's grub to be the main grub, instead of Mint's grub, which has the old version
[05:52] <webchat3852> When i type ls - l/sys/firmware/efi , I'm getting an error
[05:52] <webchat3852> Ok
[05:54] <webchat3852> Will press enter for all
[05:58] <webchat3852> After clicking enter 3 times
[05:58] <webchat3852> It's not proceeding further from the 3rd screen
[05:59] <webchat3852> It says...
[06:00] <webchat3852> The grub package is being upgraded.this menu allows you to select which devices you'd like grub-install to be automatically run for, if any.
[06:01] <alkisg> You can use tab, space, enter to navigate. Select your whole disk if it's not already selected, e.g. /dev/sda (not sda1), then navigate to the ok button
[06:01] <webchat3852> There are 3 paragraphs
[06:01] <webchat3852> Ok i used tab
[06:02] <webchat3852> It selected ok
[06:02] <webchat3852> Thanks for that
[06:02] <webchat3852> I guess it did not show me the whole screen and there was more to it
[06:03] <webchat3852> There's a fourth paragraph as well saying ' note:-'
[06:03] <webchat3852> Everything is enlarged and big .
[06:04] <webchat3852> Pressed enter
[06:04] <alkisg> Just press the ok buttons , and reboot after it's done :)
[06:05] <webchat3852> Selected the correct drive
[06:05] <webchat3852> Sda6 where Ubuntu is
[06:05] <webchat3852> Now it's processing
[06:06] <webchat3852> Once again thank you so much
[06:06] <webchat3852> I'm almost In tears right now
[06:06] <webchat3852> And greatfull that I'm getting help
[06:06] <alkisg> Eeeew
[06:06] <alkisg> Do not select sda6
[06:06] <webchat3852> I was so upset and stressed since last night
[06:06] <alkisg> Re-run it and select sda, like I said
[06:07] <webchat3852> Holy crap
[06:07] <alkisg> > Select your whole disk if it's not already selected, e.g. /dev/sda (not sda1), then navigate to the ok button
[06:07] <webchat3852> It's finished
[06:07] <webchat3852> Can I just run it again?
[06:07] <alkisg> Yes
[06:08] <webchat3852> Ok
[06:08] <webchat3852> Doing it again
[06:08] <alkisg> Check sda, uncheck sda6
[06:08] <webchat3852> I'm so sorry
[06:08] <webchat3852> Ok
[06:08] <webchat3852> Starting it again then
[06:09] <webchat3852> Ok
[06:09] <webchat3852> Started again
[06:10] <webchat3852> Selecting sda
[06:10] <webchat3852> Selected
[06:10] <webchat3852> Gonna press ok now
[06:11] <webchat3852> Ok done
[06:11] <webchat3852> Processing
[06:12] <webchat3852> Will reboot once it's done ...
[06:13] <webchat3852> Ok it's done
[06:13] <webchat3852> Gonna reboot now
[06:14] <webchat3852> Rebooting
[06:14] <alkisg> !enter
[06:15] <webchat3852> Ok, the grub menu looks like the previous one with no change. It says Ubuntu 21.10
[06:16] <webchat3852> Selected Ubuntu
[06:17] <alkisg> Did you manage to check sda? Do you have another disk?
[06:17] <webchat3852> Ok restart complete, and no change to the system...
[06:18] <webchat3852> Yeah I selected and entered ok ok sda
[06:18] <webchat3852> I have 2 HDD drives
[06:18] <alkisg> It's possible that your grub is in sdb then; run sudo dpkg-reconfigure once more, and select sdb as well
[06:19] <webchat3852> Ok
[06:19] <webchat3852> Sure
[06:19] <alkisg> (it depends on which disk you have selected as the first one, in bios)
[06:19] <webchat3852> Ooo ok
[06:19] <alkisg> So now check both sda and sdb, and nothing more, no sda1 or sda6
[06:19] <webchat3852> Sorry about that, i should have mentioned it, didn't realise that
[06:19] <webchat3852> Ok
[06:22] <webchat3852> There's an asterisk mark on the /dev/sdb
[06:23] <webchat3852> Proceeding with that and going ahead with sdb
[06:24] <alkisg> There were asterisks already, on both sda and sdb?
[06:25] <alkisg> Anyway after it's done, run this to be 100% sure: sudo grub-install /dev/sda; sudo grub-install /dev/sdb
[06:25] <alkisg> Then reboot
[06:28] <webchat3852> Ok
[06:29] <webchat3852> It's done so to be 100 percent sure running the grub-install sda and sdb
[06:29] <webchat3852> Will reboot after that
[06:30] <webchat3852> Thanks
[06:34] <webchat3852> Rebooting
[06:35] <webchat3852> O wonderful, grub menu change showing Ubuntu as the first option
[06:35] <Sinsun_> what is /srv
[06:35] <webchat3852> Ok it's starting this time with small letters
[06:35] <webchat3852> Oooo
[06:35] <webchat3852> Ok
[06:36] <webchat3852> Looks good
[06:36] <alkisg> Great
[06:36] <webchat3852> It's starting up
[06:36] <webchat3852> The Ubuntu logo now looks normal
[06:36] <webchat3852> Processing
[06:37] <webchat3852> Ok now at the enter password screen which also looks normal
[06:38] <webchat3852> With the correct resolution
[06:38] <webchat3852> Entering the password
[06:38] <alkisg> You don't need to mention all steps, you can just tell us the end result :)
[06:39] <webchat3852> Eureka
[06:39] <webchat3852> Success
[06:39] <webchat3852> Ok now I'm crying with tears of joy
[06:40] <webchat3852> Lol
[06:40] <webchat3852> It's resolved
[06:40] <webchat3852> OMG
[06:40] <webchat3852> Thank you thank you thank
[06:41] <webchat3852> Everyone thank you soooooooooooooo much
[06:41] <webchat3852> Alkisg thank you sooooooooooooooooooooooooooo oooooooooooo much
[06:41] <nightBulb> Greetings people, I recently upgraded to Ubuntu 22.04 on a Laptop, problem is, the laptop no longer wakes up by touchpad interaction, have to press the power button to wake it up.
[06:42] <alkisg> You're welcome :)
[06:42] <webchat3852> I don't even know what to say right now
[06:42] <nightBulb> Just to clarify, sleep and wakeup are working fine, but
[06:42] <webchat3852> Thank you for your time, your patience, your guidance
[06:42] <nightBulb> touchpad interaction to wake no linger works ...
[06:43] <nightBulb> s/linger/longer/
[06:44] <nightBulb> any thoughts ... ?
[07:04] <nightBulb> anyone ... ?
[07:05] <alkisg> systemctl --failed ==> fwupd-refresh.service: failed
[07:05] <alkisg> I see that unit as failed in most of my 20.04 and 22.04 installations; is that a global issue or is it just me? If I run it manually, it works...
[07:08] <branant> alkisg: I can confirm. Same here on clean installation of 22.04.
[07:09] <alkisg> Thank you branant; I think the problem is this: # grep Exit /lib/systemd/system/fwupd-refresh.service
[07:09] <alkisg> SuccessExitStatus=2
[07:09] <alkisg> I.e. it expects a failure! as a successful exit
[07:11] <alkisg> The man page says `Commands  that successfully execute will return "0", but commands that have no actions but successfully execute will return "2"`
[07:12] <alkisg> I guess the semantics of what "no action" is changed in some update, and it's now considered as failing
[07:12] <alkisg> *means
[07:18] <branant> It makes sense. Thanks for the explanation.
[07:35] <EriC^^> good morning all
[07:38] <ick> @alkisg what do you see for systemctl status fwupd-refresh.service ?
[07:38] <ick> I get Process: ... ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE)
[07:38] <alkisg> ick:  (code=exited, status=1/FAILURE)
[07:39] <alkisg> If I comment out the `SuccessExitStatus=2` line and reboot, it bypasses the problem
[07:39] <ick> This is not the Success=2 we were looking for
[07:39] <alkisg> I guess we need to report this issue...
[07:39] <alkisg> fwupdmgr returns 0, while the unit expects 2
[07:39] <alkisg> By commenting out that line in the unit, it's not in failed state anymore
[07:41] <ick> Where does the refreshed metadata go? can we look for it?
[07:41] <alkisg> Ah, a better idea: SuccessExitStatus=  Takes a list of exit status definitions that, when returned by the main service process, will be considered successful termination
[07:41] <alkisg> We can put both 0 and 2 there instead of commenting it out
[07:42] <ick> what does status=1/FAILURE mean then? 1 is neither 0 nor 2
[07:44] <alkisg> It's a generic "it was not zero"
[07:44] <alkisg> Instead of printing the actual error code, they always print 1
[07:45] <ick> "they" = what ?
[07:45] <ick> That's not a normal coding standard in my limited experience.
[07:46] <alkisg> They => probably the systemd code that prints that line
[07:46] <alkisg> Instead of printf("%d/FAILURE\n", code") they have printf ("1/FAILURE\n")
[07:47] <ick> oh, systemd. Cannot stop applauding.
[07:47] <ick> Yes, 2 is 1
[07:50] <ick> How to find the relevant code to see where the fw metadata goes?
[07:54] <ick> i see that man fwupdmgr fwupdtool fwupdagent are all exceedingly brief, and point to no further documentation.  Are these documented anywhere?
[07:57] <ick> fwupdmgr --help gives something
[08:01] <ick> fwupdmgr verify   # this only reports failures on UHD graphics 630 and system firmware
[08:01] <ick> @alkisg, what do you see for:   fwupdmgr verify
[08:02] <alkisg> A menu, and then if I select something I get: failed to verify 82541PI Gigabit Ethernet Controller (PRO/1000 GT Desktop Adapter): No release found for version 05
[08:03] <alkisg> But the program itself doesn't matter, I'm only worried about the failed service part
[08:03] <alkisg> I fixed it by setting SuccessExitStatus=0,2, but it should be reported in launchpad... sorry no time to do it currently
[08:04] <ick> Is it expected that everything fwupdmgr attempts to verify, fails?
[08:06] <ick> More precisely, is it a concern if  "failed to read firmware: Error reading from file: Input/output error",  or "failed to verify System Firmware: No stored checksums for 1.12.0"
[08:11] <alkisg> I submitted the issue in https://github.com/fwupd/fwupd/issues/4567
[08:14] <ick> Thanks for doing that. What can we do about the firmware errors?
[08:15] <ick> failed to verify CoffeeLake-S GT2 [UHD Graphics 630]: failed to read firmware: Error reading from file: Input/output error
[08:15] <ick> failed to verify System Firmware: No stored checksums for 1.12.0
[08:34] <lallaa4ka> ребятки тут кто есть.
[08:35] <lallaa4ka> Ё
[08:35] <lallaa4ka> ?
[08:38] <zetheroo> When to hardware updates end for Ubuntu 20.04?
[09:25] <webchat59> Hello. I'm having trouble making my sound work after upgrading to ubuntu 22.04 from 21.10. Could anyone give me a hand? I'm seeing dummy speaker on sound. And I search a little and it seams to be related to pulseaudio. Y try starting, restarting, etc, but the deamon won't start.
[09:28] <ogra> the daemon starts as part of the user session, do not try to start it as a system daemon
[09:29] <ogra> are you sure it is not running already (how did you check ?)
[09:29] <circuitbone> `pulseaudio -k` ?
[09:31] <webchat59> pacmd list-cards
[09:31] <webchat59> No PulseAudio daemon running, or not running as session daemon.
[09:32] <ogra> aha
[09:32] <ogra> have you tried creating a fresh test user yet ? to see if some old config hangs around in your existing account ?
[09:32] <webchat59> Hum, no. I could try that.
[09:33] <webchat59> Also tried:
[09:33] <webchat59> systemctl enable pulseaudio
[09:33] <webchat59> Failed to enable unit: Unit file pulseaudio.service does not exist.
[09:33] <ogra> yeah, it should not 🙂 like i said above ... it is a session daemon
[09:34] <webchat59> I see
[09:34] <ogra> normally started when you log in to the session and owne by your user
[09:34] <ogra> *owned
[09:40] <webchat59> Same result for test user. :/
[09:40] <ogra> well, one dtapint more, you know it is not old config ... delete the user ...
[09:40] <ogra> *datapoint
[09:41] <ogra> lets look at the other side of things ... start with "cat /proc/asound/cards" to see if you have a driver loaded at all
[09:41] <webchat59> cat /proc/asound/cards
[09:41] <webchat59>  0 [PCH            ]: HDA-Intel - HDA Intel PCH
[09:41] <webchat59>                       HDA Intel PCH at 0xa121c000 irq 141
[09:42] <webchat59> Is that correct?
[09:42] <ogra> looks good
[09:43] <ogra> does "aplay -l" also list devices ?
[09:43] <webchat59> Yes:
[09:43] <webchat59> aplay -l
[09:43] <webchat59> **** List of PLAYBACK Hardware Devices ****
[09:43] <webchat59> card 0: PCH [HDA Intel PCH], device 0: ALC257 Analog [ALC257 Analog]
[09:43] <webchat59>   Subdevices: 1/1
[09:43] <webchat59>   Subdevice #0: subdevice #0
[09:44] <ogra> webchat59, better dont paste directly into the channel for longer pastes 😉
[09:45] <webchat59> Yes, sorry about that.
[09:46] <ogra> journalctl | grep pulse | nc termbin.com 9999
[09:46] <ogra> run that and give the url it returns
[09:46] <webchat59> https://termbin.com/7fg0e
[09:51] <ogra> webchat59, hmm, that looks weird, especially the update-manager warnings indicate you have some wrong package sources around that break something
[09:51] <ogra> do you have any audio related PPAs enabled ?
[09:52] <webchat59> Not that I recall. How could I check for that?
[09:55] <ick> is this a concern? In dmesg there are many lines like this : audit: type=1400 audit(): apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/run/mount/utab" pid=N comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=N ouid=0 ,
[09:55] <ogra> check in your software settings, there is a tab "additional software" or some such, that should list all PPAs
[09:58] <webchat59> Pipewire
[09:59] <ogra> ick, i think these are harmless
[09:59] <ogra> webchat59, well, pipewire is a pulseaudio replacement ...
[09:59] <webchat59> But I think the ppa is disabled?
[10:00] <webchat59> Should that matter?
[10:01] <ogra> webchat59, if you installed from it before the upgrade and it has the same packages as 22.04 but with higher versions, that created a mess
[10:04] <webchat59> I see. Is there a way for me to solve that without changing much the configuration?
[10:04] <ogra> apt-cache policy pulseaudio pipewire-pulse | nc termbin.com 9999
[10:04] <ogra> lest see where these come from
[10:05] <webchat59> https://termbin.com/32hv
[10:05] <ogra> hmm, looks fine
[10:08] <ogra> so it must be other packages, i.e. some libs ...
[10:09] <ogra> i'd go thrugh the list of the packages in that PPA and check all of them with the "apt-cache policy" command like above to see if there is any of them still from the PPA or without any source
[10:11] <zetheroo> When to hardware updates end for Ubuntu 20.04?
[10:11] <zetheroo> *do
[10:11] <webchat59> Alright, I'll go through them.
[10:11] <ogra> zetheroo, hardware updates ?
[10:12] <zetheroo> ogra:  I saw an Ubuntu release graphic showing maintenance and hardware updates
[10:12] <ogra> zetheroo, you mean kernel updates ?
[10:12] <zetheroo> trying to find the graphic again ...
[10:12] <ogra> https://ubuntu.com/about/release-cycle
[10:13] <zetheroo> right
[10:13] <zetheroo> oh it changed
[10:14] <ogra> LTS release are supported for 10y ...
[10:14] <zetheroo> We have an older version of the graphic which shows 'Hardware and maintenance updates' and then 'Maintenance updates'
[10:14] <ogra> after 5y you need to use ubuntu advantage to get security updates though
[10:14] <ogra> (which is free for persona use, paid for commercial use)
[10:14] <ogra> *personal
[10:15] <zetheroo> now it says 'Interim release Standard Support' where before it said 'Maintenance updates'
[10:15] <ogra> yeah, some marketing terms changed 🙂
[10:16] <zetheroo> oh no ... not even ... the 'Maintenance updates' is completely gone ... as in, it looks like it's merged with the 'Hardware and maintenance updates' phase.
[10:17] <ogra> on a technical level nothing changed thogh ...
[10:18] <ogra> (the different support phases are still the same, just their naming is different ... i think to better distinguish LTS from non LTS)
[10:18] <zetheroo> this is the graphic we were using https://www.fossmint.com/wp-content/uploads/2016/04/Ubuntu-Release-Cycle.png
[10:19] <ogra> right ... same but different ...
[10:19] <ogra> technically nothing changed 🙂
[10:20] <zetheroo> There was the dark orange and then the light orange ... which looks like it's merged into one continuous orange bar .. which to me means that, unlike previously, the 'Hardware updates' are prolonged.
[10:21] <zetheroo> .... prolonged for twice as long as previously.
[10:36] <webchat59> Finally got the speakers working.
[10:36] <webchat59> https://ubuntuhandbook.org/index.php/2022/04/pipewire-replace-pulseaudio-ubuntu-2204/
[10:37] <webchat59> Thanks ogra for the help!!
[10:41] <ogra> zetheroo, nah. LTses always have gotten support and kernel updates for 5y regardless how you split the marketing terms 🙂
[10:41] <ogra> webchat59, yay
[10:43] <zetheroo> ogra: ok, all good
[11:03] <WeeBey> I'm happy to report that I'm now using juicy jammy. Yay!
[11:04] <WeeBey> but the kernel has the same little bug as 5.16.19 that I was trying out where on boot, I get some error messages and not the nice clean ubuntu boot screen.
[11:15] <Acheron> WeeBey, have you checked the bug reports?
[11:16] <WeeBey> I think I did a few weeks ago and came across people just ignoring such error messages
[11:16] <WeeBey> They're ACPI related
[11:17] <Acheron> journalctl -b --all --pri=3
[11:17] <Acheron> that command will let you see them
[11:19] <WeeBey> Acheron, nice.
[11:19] <Acheron> ACPI Error: ?
[11:19] <WeeBey> Bunch of  ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.PEG2.WKEN], AE_ALREADY_EXISTS (20210730/dswload2-326)
[11:19] <Acheron> everyone has a few of them depending on the age of the hardware
[11:19] <WeeBey> Acheron, I think that's why I read that people just shrugged them off.
[11:19] <Acheron> yeah
[11:20] <Acheron> they are just warnings
[11:20] <WeeBey> Yeah but but but... they break the nice boot screen. :D :D
[11:20] <WeeBey> this one is new! kernel: dell_smbios: Unable to run on non-Dell system Ha
[11:20] <Acheron> well nothing is perfect
[11:21] <WeeBey> indeed.
[11:21] <WeeBey> Thanks for that the top on viewing them. :-)
[11:22] <WeeBey> Oh, lots of nvidial-drm failed to grab modset ownership. These are the alpha and omega. They were there at the beginning and will be there after we're gone.
[11:22] <ick> Is this a concern: 75% of the lines in dmesg are of the form audit: type=1400 audit(): apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/run/mount/utab" pid=N comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=N ouid=0
[11:23] <ogra> ick, as i said before, you can ignore them, this is harmless noise (feel free to report them as a bug though)
[11:24] <Acheron> ick i would check on Mozilla's website
[11:24] <Acheron> i've never seen DENIED before
[11:25] <ick> ogra, thank you. sorry I didn't notice you reply earlier,
[11:27] <WeeBey> ogra, yes, I follow.
[11:28] <Nander> I decided to try and fix my laptop issues (as yesterday) by trying a fresh reinstall, and the installer just crashed on me
[11:28] <Nander> Full system freeze
[11:28] <ick> what is utab anyway?
[11:28] <ick> Nander is your hardware new or old?
[11:28] <Nander> 11th gen i9 new
[11:29] <Nander> 96GB RAM
[11:29] <ick> what OS worked before on it?
[11:29] <Nander> It does a small graphical glitch, and then gives up
[11:29] <Nander> Xubuntu didn´t work well (same glitch), Linux Mint (just tried it) didn´t seem to support the hardware properly
[11:32] <ick> Probably bleeding edge hardware.... did you try live USB ?
[11:32] <Nander> The live USB just crashed on me
[11:32] <Nander> Just before formatting the drive
[11:34] <ick> on the USB, Is there a safe graphics option, and did you try that?
[11:34] <Nander> not yet, can do
[11:34] <Nander> But, then, won't I just run into crashes after install?
[11:34] <ick> Depends on if there are updates for your hardware not on the USB
[11:35] <ick> But yes it is a possibility
[11:35] <Nander> Is ubuntu different in that from xubuntu?
[11:35] <ick> I sometimes have needed to boot with kernel option nomodeset, until the driver gets updated.
[11:36] <Nander> What does that do?
[11:37] <ick> Until someone more knowledgable speaks up, I'll just stay it keeps the graphics subsystem from taking a flying leap into the abyss.
[11:38] <Nander> Fyi btw, I have no nvidia and no amd card
[11:38] <Nander> just intel
[11:42] <ick> https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
[11:43] <ldlflw> https://w.metty.us/regsiter687
[11:43] <Nander> thx
[11:44] <Nander> Why that second link?
[11:44] <ick> Looks like spam to me
[11:44] <Acheron> yes, it is
[11:45] <Acheron> i was spammed in pvt
[11:45] <Acheron> any chance an OP could take care of that?
[11:47] <ick> Nander: I'm guessing here, but I would first try to install in safe graphics mode, boot in safe graphics mode, update everything, and then try a normal boot.  I don't know whether safe mode includes nomodeset already (anyone know?) so maybe try the nomodeset as a second strategy.
[11:47] <Nander> It's installing in safe graphics mode now
[11:47] <Nander> Time for coffee
[11:49] <WeeBey> Nander, ohman, that's rough.
[11:50] <Nander> only saving grace, I am getting paid for the hours I  am spending on this
[11:50] <WeeBey> Nander, I got this laptop and it took me two weeks of suffering to make it work.
[11:50] <Nander> I first had a temporary laptop from work, and managed to break that one before my coffee got cold
[11:52] <Nander> WeeBey do you know what got it working?
[11:53] <ogra> you should aim for a job in QA ... sounds liek you have some talent 😉
[11:53] <ogra> *like
[11:53] <BluesKaj> Hi all
[11:54] <WeeBey> Nander, hmm. I was getting a lot of crashes. I changed so many things trying. I should have documented it!
[11:55] <WeeBey> Nander, I followed a few things from here, but it's vendor specific. https://rolandguelle.github.io/razer-blade-stealth-linux/ubuntu-18-04.html
[11:55] <Nander> I am intrigued by the lack of others reporting similar issues
[11:55] <WeeBey> Even though I was on 21.10, a lot of the issues were still there.
[11:55] <WeeBey> Nander, but that's post install.
[11:56] <Nander> It seems to have just happened on the freaking unlock crypto screen
[12:39] <Nander> Issue persisted... I am gonna try a different linux flavor to see what that does
[12:39] <Nander> If the issues then continue, I'm gonna ask IT to install windows on it to see what that does
[12:51] <vardhan> Dont know if this is related to ubuntu but -- Im on Ubuntu 20.04. Somehow whenever I used the backstroke key, it pops up a terminal like window on the right of the screen, which goes away only on another backstroke (not with exit)
[12:51] <vardhan> I am unable to type the backstroke key (even in this msg for e.g.) as it is somehow mapped to opening a terminal
[12:52] <vardhan> Not able get answers from search engines.. someonw has any idea how to unmap this key?
[12:53] <JoeBk> vardhan, what does "keyoard shortcuts" show?
[12:57] <vardhan> JoeBk, sorry how to I get that?
[12:58] <vardhan> Got it
[12:59] <vardhan> Nothing mapped to backtick in keyboard shotcuts
[13:02] <MyWay85> Hi again, yesterday I updated ubuntu and dell firmware and after that I couldn't boot anymore, neither using old kernel, recovery or system recovery. In every case a get a blank screen, or it gets stuck at initial ramdisk loading. Or if I change some bios settings I get a kernel panic, after a out of memory. I'm on ubuntu 20.04. I can boot with a
[13:02] <MyWay85> live, any idea on what I could do?
[13:17] <BluesKaj> dell firmware in bios?
[13:20] <MyWay85> It asked me to restart, then updated dell things before boot, then I couldn't boot anything anymore, but live it works
[13:20] <MyWay85> No idea what it updated, it was saying something about intel security if I remember well
[13:21] <MyWay85> And not even sure that's the problem because before ubuntu updated itself
[13:21] <MyWay85> But running the old kernel it is the same
[13:22] <BluesKaj> what did you  change in the bios settings?
[13:22] <WeeBey> Well, i tried putting the laptop to suspend with juicy jammy and I got full crash. Had to hard-reboot. :-o
[13:22] <MyWay85> Nothing, I tried one time booting with intel sgx enabled and secure mode off
[13:22] <BluesKaj> if you enabled fast boot that could be problematic on linux
[13:23] <MyWay85> No fast boot enabled
[13:24] <MyWay85> No way to have a more detailed log of what's going on when it gets stuck there?
[13:43] <lagk4365> hello, help can't register an account and I can't and I really need it - https://w.metty.us/regsiter687
[13:44] <lotuspsychje> thats not really ubuntu related lagk4365
[14:07] <howudodat> unable to get my laptop to suspend (Power Off -> Suspend).it acts like it does, but then the screen comes back on and wifi re-enables, never sleeps.  https://pastebin.com/psJi9zYG, so I created /usr/lib/systemd/system-sleep/10-brcmfmac.sh to remove module brcmfmac pre sleep.  That doesn't seem to help either.  BTW, if I manually rmmod brcmfmac and then do power->suspend, it shuts the system down (not sleep).
[14:08] <howudodat> this is new for 22.04, 20.04 suspended "fine"  (I say fine becuase suspend and lid close has always been bit flaky)
[14:27] <krish> 123
[14:37] <ogra> howudodat, run "ubuntu-bug linux" and report it ... the module should be properly unloaded without you needing to apply hacks ...
[14:40] <lotuspsychje> maybe Jeremy31 knows something^ he's our wifi wizard
[15:16] <Furai> https://wiki.ubuntu.com/Releases
[15:16] <Furai> Is it mistake that 22.04 isn't tagged LTS here?
[15:16] <MyWay79> hi again
[15:17] <MyWay79> I'm trying to run update-initramfs -c -k 5.13.0-40-generic from a live, after chrooting on my hd system, but I'm getting
[15:17] <MyWay79> mkinitramfs: MODULES dep requires mounted sysfs on /sys
[15:18] <MyWay79> (always trying to solve that dell issue I was talking before here)
[15:18] <leftyfb> MyWay79: exit out of the chroot
[15:18] <leftyfb> MyWay79: for i in dev sys proc ; do sudo mount -o bind /$i /target/chroot/$i ; done
[15:18] <leftyfb> then chroot
[15:19] <MyWay79> mount: /target/chroot/dev: mount point does not exist.
[15:19] <MyWay79> mount: /target/chroot/sys: mount point does not exist.
[15:19] <MyWay79> mount: /target/chroot/proc: mount point does not exist
[15:19] <leftyfb> replace /target/chroot of course
[15:19] <MyWay79> (zfs here)
[15:19] <MyWay79> ah ok
[15:19] <leftyfb> replace /target/chroot with the location of your mounted environment you're trying to chroot into
[15:20] <MyWay79> cryptsetup: ERROR: Couldn't resolve device rpool/ROOT/ubuntu_odljlc
[15:20] <MyWay79> now I'm getting this, when running update-initramfs
[15:20] <MyWay79> cryptsetup: WARNING: Couldn't determine root device
[15:20] <MyWay79> and this
[15:23] <MyWay79> initr got generated anyway, but I don't know whether I can try to reboot and it will find references again or not
[15:30] <jhutchins> Furai: It isn't flagged as LTS until 22.04.1
[15:30] <jhutchins> Furai: Gives us a chance to make sure there aren't any lurking bugs that could snuff production systems.
[15:31] <MyWay32> can't remember the nickname of who helped me, but thanks, it worked
[15:32] <jhutchins> https://arstechnica.com/information-technology/2022/04/microsoft-finds-linux-desktop-flaw-that-gives-root-to-untrusted-users/
[15:32] <MyWay32> also, for people having that dell issue after update, with ubuntu stuck at init ramdisk loading, the solution is here: https://askubuntu.com/questions/1341163/ubuntu-20-04-21-04-stuck-in-grub-after-encryption (even if no encryption)
[15:45] <Furai> jhutchins, thought that's the case, thanks for clarifygin.
[15:45] <Furai> clarification*
[15:51] <kryten> Furai: Me otoh though, looking at the revision history of the page wrt earlier LTS releases, don't think leaving the "LTS" off there (as well as not bold-marking it) is intended in this case.
[15:54] <jhutchins> kryten: Yes, it is.  LTS will be 22.04.1
[15:58] <ogra> mind you, we do not leave it off in os-release or lsb_release ... i.e. on disk it already says LTS
[15:58] <ogra> (which i always found confusing 🙂 )
[15:59] <ravage> it also says so all over ubuntu.com
[15:59] <ogra> yeah, consistency is for whimps 😛
[16:18] <kryten> jhutchins: You are welcome to take a look at the revision history of the wiki page yourself.
[16:25] <scanno> I must say that nVidia (RTX-3060 on a laptop) and Wayland are still not a good match. A lot of graphic glitches and suspend / wakeup breaks graphics.
[16:27] <ravage> thats why wayland is currently disabled on installations with nvidia
[16:49] <scanno> X11 has its own problem on my system. There some applications have a font so small that I can hardly read it (high resolution laptop screen, nvidia as dedicated graphic card, resolution of the laptop screen cannot be changed in settings). Only way is to enable Factional Scaling and set a scale of 125%. Most windows are displayed correctly, but not all. Using wayland I do not have that problem.
[17:00] <leftyfb> scanno: if you don't scaling, you won't have the small font issue
[17:01] <scanno> leftyfb: But then the whole screen is too small to read due to the high resolution of the screen.
[17:01] <leftyfb> then lower the resolution
[17:02] <scanno> leftyfb: I cannot. Resolution is fixed
[17:03] <leftyfb> did you try in the display settings and nvidia-settings?
[17:03] <scanno> Display settings is fixed at 2560x1600 (16:10)
[17:04] <leftyfb> and using the nvidia-settings application?
[17:04] <scanno> And nvidia-settings also only has 2560x1600
[17:05] <leftyfb> scanno: try a different nvidia driver
[17:08] <scanno> Right now I am using 510, the recommended version
[17:09] <leftyfb> try a different one
[17:10] <scanno> I will try the 470 that us available in Additional Drivers
[17:16] <scanno> Oh nice now my network is broken, the problem is still there and my back light is always at 100% and cannot revert driver because of the lack of network
[17:19] <scanno> Hmm USB also is not working any more. Grrr
[17:22] <leftyfb> scanno: did it remove the 510 packages?
[17:22] <leftyfb> grep 510 /var/log/dpkg.log
[17:23] <NCEric> Hi, I've asked a couple days ago about middle click to paste in 22.04.  In the past (20.04 and earlier) when you had newlines in your selection and middle clicked to paste into a terminal the terminal would execute those lines.  Currently on 22.04 you have to press [enter] on your keyboard.  What changed?
[17:23] <NCEric> I tried using Xorg instead of Wayland, same issue.  Nobody seems to be active in #gnome
[17:29] <scanno> Well I guess I will have to reinstall again
[17:29] <enigma9o7[m]> I just confirmed that NCEric, interesting.
[17:30] <enigma9o7[m]> And I'm not using gnome, so doesn't seem to be a gnome thing.  I am using x11 tho.
[17:30] <scanno> Will be faster in the end. I just hope my licenses of prop software will still work because I cannot deactivate them now
[17:31] <ioria> NCEric, https://bugs.launchpad.net/ubuntu-online/+bug/1970644
[17:31] <enigma9o7[m]> The weird part is I thought hte middle click paste was an x11 thing, so surprised the behavior is the same in wayland.
[17:34] <enigma9o7[m]> so that bug implies its a change in bash thats doing it
[17:34] <ioria> he says it works on tcsh
[17:34] <enigma9o7[m]> which makes sense how it seems desktop and display server agnostic
[17:49] <NCEric> ioria, yea... thats definitely it.  Perhaps it's a bash thing
[17:50] <ioria> maybe....
[17:50] <howudodat> need some help getting 5.1 surround working over hdmi.  I do pc -> samsung tv -> sound bar (over hdmi arc).  With my nvidia shield I get 5.1 sound.  with netflix directly on the tv I get hdmi sound.  With the PC, if I set to 2channel I get left and right, but 5.1, I can hear FL and FR but not the other channels.  Card is an AMD renoir, which uses intel_hda, but I'm kind of stuck on this one
[18:05] <howudodat> middle click is not a bug, it's due to an upstream change in readline with bracketed paste mode iirc.  the behaviour can be changed, see: https://bugzilla.redhat.com/show_bug.cgi?id=1954366 and https://lists.gnu.org/archive/html/bug-readline/2020-12/msg00000.html
[18:06] <howudodat> a feature is just a bug dressed up in a tuxedo
[18:08] <sarnold> howudodat: thanks
[18:12] <TheBigK> hi, i updated today to kubuntu 22.04. And since this is most likely not special to kubuntu: libxfixes3:amd64 <- this package is older in 22.04 than in 21.10 ... would i upgrade... it would actually do A TON of dependencies... any thoughts about this? https://paste.debian.net/1239339/
[18:12] <howudodat> apparently amd has an audio co-processor driver for renoir, but I cant seem to find it
[18:16] <sarnold> TheBigK: hmm, https://launchpad.net/ubuntu/+source/libxfixes  seems to show impish has 1:5.0.3-2build1 and jammy has 1:6.0.0-1
[18:16] <sarnold> TheBigK: maybe apt policy libxfixes3  will show some more information?
[18:17] <TheBigK> https://paste.debian.net/1239340/
[18:18] <TheBigK> i dont like how debian/ubuntu handles updates... that u have to write a script to see if every installed package has a mirror behind it... it should be able to highlight those...
[18:20] <sarnold> TheBigK: there is a tool, though it's not hte easiest thing to use .. https://termbin.com/54n6
[18:22] <TheBigK> didnt know that. nice... do you know if theres something similar for debian
[18:22] <TheBigK> ?
[18:22] <sarnold> not that I know of :(
[18:25] <Dyrcona> I am trying to set up ejabberd on ubuntu 22.04 server, and when I start it with systemctl, the systemctl process hangs even though ejabberd starts. There's a message in the log implying that ejabberd is unable to notify systemd that it started, but I'm not sure how to resolve that. Anyone seen this? Got any ideas? Google has not exactly been helpful.
[18:26] <sarnold> TheBigK: I can't find that libxfixes3 package version *anywhere* :(
[18:27] <TheBigK> https://packages.ubuntu.com/jammy/libxfixes3
[18:28] <sarnold> TheBigK: sorry, I meant the 1:6.0.0-4~ubuntu21.10 that you've got now
[18:28] <TheBigK> im confused as well :D
[18:29] <TheBigK> i could boot back into 21.10... thanks to btrfs magic... but im too lazy right now
[18:30] <TheBigK> i love btrfs for this... something went wrong? role back... ez
[18:31] <veegee> How is ifconfig not standard on ubuntu
[18:31] <TheBigK> veegee: why would u need it...
[18:31] <leftyfb> veegee: it's deprecated
[18:31] <sarnold> veegee: ifconfig was replaced with ip about twenty years ago
[18:32] <TheBigK> yep :)
[18:32] <veegee> did not know that
[18:32] <veegee> ubuntu in general does fucking stupid things like create mir, bzr, snap, etc.
[18:32] <TheBigK> its like using nslookup still :D
[18:32] <leftyfb> veegee: please don't
[18:32] <veegee> So I assumed this was another one of their dumbshit ideas
[18:32] <veegee> forgot to throw launchpad in there
[18:33] <veegee> but you get the point
[18:33] <leftyfb> veegee: feel free to throw your opinions in #ubuntu-offtopic. Not here
[18:33] <veegee> But it's very very much on topic
[18:33] <veegee> doesn't matter, no more to say about it anyway
[18:34] <veegee> sarnold are you exaggerating about the 20 years?
[18:34] <veegee> Or was it actually deprecated ~20 years ago?
[18:34] <TheBigK> 20 years is  too much
[18:34] <leftyfb> https://www.ibm.com/support/pages/apar/IV95244
[18:35] <leftyfb> looks like at least 5
[18:35] <veegee> ok, is there any modern resource with information like this?
[18:35] <veegee> I didn't know about that, so there's probably a lot more I didn't know
[18:35] <veegee> is iptables deprecated too?
[18:36] <sarnold> veegee: it might have been 23-ish years? this guide references an iproute2 release from 1999 http://www.policyrouting.org/iproute2.doc.html#ss9.0
[18:36] <leftyfb> I think nftables is what all the cool kids are using now
[18:36] <TheBigK> i rly hated the /etc/network/interface config for the longest time cause the of the syntax. i rly late realized that u could configure multiple ips on one interface without using virtual interfaces... :D
[18:36] <veegee> See there's a difference between engineers making decisions and javascript script kiddies making framework of the week
[18:36] <TheBigK> since then im in love with it again :D
[18:36] <veegee> But I know javascript script kiddies wouldn't have anywhere close to the skills to understand nftables so I know what you mean
[18:37] <leftyfb> veegee: do you have an ubuntu support question?
[18:37] <Dyrcona> veegee: You can still use iptables if you want. It's there. If you want to see the standard way of configuring networking these days look up netplan and ip.
[18:37] <veegee> 1. How do you remove snap and cloud init?
[18:37] <TheBigK> what is cloud init
[18:37] <leftyfb> veegee: same as any other package
[18:37] <veegee> 2. what's the official network manager?
[18:37] <veegee> for servers
[18:38] <leftyfb> netplan
[18:38] <Dyrcona> veegee: 2. netplan
[18:38] <leftyfb> technically systemd-networkd
[18:38] <leftyfb> but netplan to configure it easier
[18:38] <veegee> leftyfb netplan is a frontend for that? '
[18:38] <leftyfb> yes
[18:38] <veegee> ok great thanks
[18:38] <leftyfb> networkd can be used standalone if you choose
[18:39] <veegee> other than disabling the hostname module in cloud init, what's the proper way to set your hostname persistently?
[18:39] <veegee> changing /etc/hostname obviously doesn't work
[18:39] <leftyfb> hostnamectl
[18:39] <veegee> is that persistent across reboots? Last time I did that, it wasn't
[18:41] <leftyfb> yes
[18:42] <tomreyn> unless you have cloud init and "preserve_hostname" is false there
[18:42] <veegee> yeah I have to check what the installer does by default
[18:44] <veegee> Any disadvantage to using a 10.0.0.0/16 subnet? Other than arp noise?
[18:44] <veegee> Not sure how significant arp traffic will be with a /16 subnet
[18:44] <leftyfb> veegee: that's not an ubuntu support question. Try #networking
[18:48] <leftyfb> veegee: pretty sure preserve_hostname is set to false by default btw. I just checked all of my servers and a newly create lxd container
[18:48] <veegee> leftyfb thanks
[18:58] <mikeyFetch> Hi, I just upgraded to 22.04. Now, screenfetch says my DE is GNOME 41.4,  but neofetch says it is GNOME 42.0. Why would screenfetch and neofetch disagree like this?
[19:00] <sarnold> you may need to read the source code of both of them to figure out what they're measuring
[19:00] <Maik> also keep in mind that 22.04 is using Gnome 42 but some apps are still 41.4
[19:03] <mikeyFetch> Thanks @sarnold and @Maik
[19:13] <Guest38> I had trouble when the last update was downloaded and installed
[19:15] <Dyrcona> Disabling the apparmor profile for usr.sbin.ejabberdctl resolves my ejabberd issue.
[19:16] <svip> Apparently, a snap installed video player is unable to access files mounted via sshfs in my /home directory.
[19:18] <svip> Is it possible to install a snap application without any restrictions to what files it may access?
[19:20] <sarnold> svip: not really; you can hand-edit the apparmor policy that snapd has generated and reload that
[19:21] <svip> sarnold: Which is located where?
[19:27] <sarnold> svip: /var/lib/snapd/apparmor/profiles
[19:27] <sarnold> that took way longer than I expected.. sheesh :)
[19:29] <svip> I am not sure how to edit these files.
[19:32] <oerheks> the --classic switch with installing snap does not solve sshfs issue AFAIK
[19:33] <sarnold> svip: the easy thing is to put that profile into complain mode, try sudo aa-complain -d /var/lib/snapd/apparmor/profiles snap.foo.bar  for whatever the profile name is -- that might do the trick, if it does, it'll save a lot more discussion :) hehe
[19:35] <svip> sarnold: I don't have aa-complain, nor is it in apt.
[19:37] <svip> sarnold: Nevermind, found it
[19:38] <sarnold> svip: d'oh, sorry :/ any luck?
[19:38] <svip> Hm, it just says "tunables/global not found".
[19:39] <sarnold> dang :(
[19:40] <sarnold> svip: so.. edit the /var/lib/snapd/apparmor/whatever file with your favourite editor, find the profile line that looks like this:
[19:40] <sarnold> profile "snap.matterhorn.matterhorn" (attach_disconnected,mediate_deleted) {
[19:40] <sarnold> and add a new flag to that list, 'complain':
[19:40] <sarnold> profile "snap.matterhorn.matterhorn" (attach_disconnected,mediate_deleted,complain) {
[19:41] <sarnold> then reload the profile with sudo apparmor_parser --replace /var/lib/snapd/apparmor/whatever
[19:42] <svip> sarnold: Still says it cannot open the path.
[19:43] <svip> Unfortunately, I am not sure I have enough time anymore.
[19:43] <sarnold> svip: *sigh* :( sorry
[19:43] <svip> So I'll give up for now.
[19:43] <svip> Thanks for the attempt, though.
[19:46] <ioria> svip, have you tried removable-media ?
[19:46] <svip> ioria: Yes.
[19:46] <ioria> ok
[19:47] <svip> I think it is a specific sshfs mount situation.
[19:47] <svip> I even tried moving it to /media, and see if that worked.
[19:47] <svip> Didn't.
[19:49] <ioria>  svip and pointing to   /run/user/1000/gvfs/ ?
[19:52] <svip> Err, no.  I mounted the sshfs path in directory in /media.
[19:53] <svip> Are you suggesting I somehow mount the sshfs path within the snap snadbox?
[19:53] <ioria> svip, nope... what is ? vlc ?
[19:54] <svip> omxplayer-pi, it's on a PI.
[19:54] <ioria> i can't find it ...
[19:55] <svip> It's mentioned here: https://snapcraft.io/omxplayer-pi
[19:56] <ioria> ogra, are you there ?
[19:58] <ravage> he has not touched that snap in a while :)
[19:59]  * ogra is eating dinner ... 
[19:59] <ioria> sorry mate
[19:59] <ogra> but omxplayer is dead upstream since several years ... i need to delete that snap
[19:59] <ioria> svip, come back tomorrow :þ
[20:00] <ioria> ogra, thanx
[20:00] <ogra> the upstream code can nt work with the newer pi drivers anymore
[20:00] <sarnold> :(
[20:00] <svip> Ah OK.
[20:00] <ogra> there is a vlc-pi snap i maintain (which i have ot touched in a while either, but that should work)
[20:00] <svip> Nevermind then.
[20:00] <svip> Hm, I will try that.
[20:01] <svip> I just liked omxplayer being CLI-based.
[20:01] <svip> On my desktop I still use MPlayer.
[20:01] <ioria> mpv is ok
[20:01] <svip> Old habits die hard.
[20:01] <ogra> same here ... i eve have a few snaps where i embed mplayr for video bits
[20:01] <ioria> yeah
[20:01] <ogra> *even
[20:01] <ogra> geez, whats up with my kbd eating chars !
[20:04]  * ogra checks metrics of omxplayer-pi, lets see how many installs it even has out there 
[20:05] <ogra> wow, still 220 users ...
[20:06] <ogra> ok, unlisted ... now people will at least not find it in searches anymore
[20:06] <rajivmars> hi all, i m going to install ubuntu 22.04 in my 1tb hard disk (entirely). i will select 'erase and install ubuntu' option. I just wanted to know that what partitions ubuntu make automatically?
[20:07] <ogra> by default just one big one
[20:07] <ravage> rajivmars, if UEFI also one for that probably
[20:07] <rajivmars> ogra, is is going to make swap?
[20:07] <ogra> yeah
[20:07] <ravage> swap file
[20:07] <ogra> a swapfile (since 18.04)
[20:07] <ravage> no extra part
[20:08] <rajivmars> ravage, ok! is it better to make partitions manually than automatic?
[20:08] <ogra> i personally like the default ... but thats totally up to you
[20:08] <ravage> that depends on your use case. for a default desktop user automatic is totoally fine
[20:08] <rajivmars> ok got it.
[20:11] <jhutchins> I recommend a single partition - minus EFI and swap if you want it.  Breaking up the running space just assures that the space you need will be on the wrong partition, unless you know _exactly_ how much data you're going to collect and where.
[20:11] <jhutchins> I heard a rumor that the installer defaults to that scheme these days.
[20:15] <ogra> exactly, what jhutchins said ... !!
[20:38] <ktwo> do you mean raw 5.1 surround or an encoded one? like DD / DTS?
[20:41] <ktwo> Note that uncompressed 5.1 with just "ARC" is not possible, Youll need eARC (Do you have it?) : https://cdn.mos.cms.futurecdn.net/DLhSzp3ad5vzgn9TNWCYGJ-970-80.jpg.webp
[20:45] <ktwo> But first check if you really have eARC because if you don't have it, it wont transmit uncompressed 5.1. To test compressed 5.1 you can use a DD encoded dvd or bluray and see if it passes trough
[20:46] <ogra> ktwo, did you ht the wrong window/channel ?
[20:46] <ogra> *hit
[21:05] <enigma9o7[m]> they are both bash scripts so you can probably check pretty easily what command they use to check that
[21:09] <enigma9o7[m]> line 1763 of neofetch
[21:16]  * ogra wonder whats going on here with people talking into the void 
[21:16] <ktwo> isnt it the -classic flag?
[21:17] <ILOVEROCKANDROLL> QUESTION PLEASE!
[21:17] <ILOVEROCKANDROLL> QUESTION PLEASE!
[21:17] <sarnold> ogra: ktwo's just got three hours of lag
[21:17] <ILOVEROCKANDROLL> thanks
[21:17] <sarnold> ILOVEROCKANDROLL: please don't.
[21:17] <ILOVEROCKANDROLL> is it right that
[21:18] <ILOVEROCKANDROLL> ubuntu desktop amd64 iso has timestamp from 19th april
[21:18] <ILOVEROCKANDROLL> ????????!?!?!?!?!
[21:19] <oerheks> that would be the beta
[21:19] <oerheks> daily build
[21:19] <ogra> nope
[21:19] <ogra> 19th is corrct
[21:20] <ILOVEROCKANDROLL> really
[21:20] <ILOVEROCKANDROLL> cant  be or is it
[21:20] <ogra> is
[21:20] <ILOVEROCKANDROLL> ok thanks
[21:20] <ILOVEROCKANDROLL> you devs are the best people oall over the world !
[21:20] <ogra> the images need to be tested before release 😉
[21:20] <ogra> that takes its time
[21:20] <ILOVEROCKANDROLL> yes but ubu 20.04 release was
[21:20] <ILOVEROCKANDROLL> same day
[21:20] <ILOVEROCKANDROLL> and very late
[21:21] <ILOVEROCKANDROLL> i can remember really good
[21:21] <ogra> because there was a last minute re-spin to fix a serious bug
[21:21] <ILOVEROCKANDROLL> ah ok!
[21:22] <ogra> (in the installer IIRC, nothing that could be fixed by an update)
[21:22] <ILOVEROCKANDROLL> thats true !
[21:45] <Rusty_Almighty> Does anyone here know if the NFS server included with Ubuntu 20.04 supports NFS4 on arm?
[21:45] <Rusty_Almighty> nfs-common_1.3.4-2.5ubuntu3.4_arm64.deb specifically.
[22:03] <jhutchins> Rusty_Almighty: It should, it's been supported upstream for years.
[22:04] <jhutchins> Rusty_Almighty: Still, most commercial appliances don't support it.
[22:12] <ksx4system> is it only me or there's a bug in Files? if you right-click within any disk (network or local) to get properties cake diagram will be all black no matter how much space is actually used/left
[22:12] <ksx4system> 22.04 amd64
[22:19] <Rusty_Almighty> @jhutchins: HMMM.. I'm entirely perplexed on why my small SBC doesn't seem to have nfs version 4 enabled.
[22:20] <Rusty_Almighty> Not even sure where to look honestly. Is there a location that would disable nfs4?
[22:27] <sarnold> Rusty_Almighty: there's some advice on https://help.ubuntu.com/community/NFSv4Howto but it hasn't been updated in a few years; it won't perfectly reflect 20.04 but might still be useful
[22:37] <Rusty_Almighty> @sarnold: I've already looked into it.
[22:38] <Rusty_Almighty> I wouldn't be on IRC if the advice there had worked.
[22:49] <jhutchins> ksx4system: Is this a new install or an upgrade (if an upgrade, from what)?
[22:50] <jhutchins> The reason that the NFS documentation hasn't been updated in a few years is that nothing significant has changed.
[22:52] <jhutchins> Rusty_Almighty: What have you done to enable it?  Is it not listening for requests on both 3 and 4?  What configuration file are you using?  Why do you think it's disabled?
[23:08] <goddard> can i move print jobs to another printer
[23:08] <jhutchins> Must not be important, I guess.
[23:10] <jhutchins> !cups
[23:10] <jhutchins> goddard: I'm pretty sure I've seen that option.
[23:11] <goddard> jhutchins: im looking at my jobs in gnome settings and i can only see they are pending
[23:12] <Rusty_Almighty> @jhutchins: it's listening on version 3 and I can mount on version 3 just fine. I require version 4.
[23:14] <jhutchins> Rusty_Almighty: Did you build the NAS server, or is it something that came on the hardware?
[23:14] <Rusty_Almighty> I built it on an espresso bin which is a raspberry pi like appliance.
[23:14] <jhutchins> Rusty_Almighty: What's your source for the OS?
[23:15] <Rusty_Almighty> I built the file system, but the kernel is a stock kernel.
[23:15] <Rusty_Almighty> Then directly loaded onto an sdcard.
[23:16] <jhutchins> Rusty_Almighty: "Stock" what?  What's your source?
[23:16] <jhutchins> Rusty_Almighty: I'd like to help you, but I need to know what you're running.
[23:17] <jhutchins> https://linuxize.com/post/how-to-install-and-configure-an-nfs-server-on-ubuntu-20-04/
[23:17] <Rusty_Almighty> 5.10.110 #1 SMP PREEMPT Mon Apr 11 10:26:15 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
[23:18] <jhutchins> Rusty_Almighty: Ok, you don't want to cooperate.  I'm done.
[23:18] <Rusty_Almighty> From apt.
[23:19] <Rusty_Almighty> But if you're gonna be toxic about it. I've got several other conversations going.
[23:21] <Rusty_Almighty> @jhutchins: not sure what your looking for.