[00:54] 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] double check you have as much swap-space as internal laptop RAM, it might be something else tho. [00:59] anyone know how to address this error message in unison when invoking from cron: https://gist.github.com/arooni/e54557482e05d2319a217cdc7009c6ec [00:59] yikes, my swap has never been that large. I have 64G mem and 4G swap. BTW, it did suspend with 20.04 [01:23] anyone have any guidance? https://github.com/bcpierce00/unison/issues/712 [01:23] Issue 712 in bcpierce00/unison "Unison from command line works great, but cannot seem to invoke the same profile from cron" [Open] [02:47] 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] I can provide the full boot log if there is a convenient place to upload it. [02:51] 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] 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] lotuspsychje: Would that be comparing prints during the boot process? I can still boot into 5-11.0-46. [02:54] xamboni: no i mean comparing kernels and prove its 5.13 faulty, if you can indeed still boot into 5.11 [02:55] is that a server or desktop xamboni ? [02:56] This is a desktop. [02:56] ok [02:57] 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] 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] 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] sure, share it with the volunteers, maybe someone can pinpoint soomething [03:03] lotuspsuchje: Thanks for the help. The entire log can be found here: https://pastebin.com/9FMDsJF1 [03:05] xamboni: [FAILED] Failed to mount Mount unit… gnome-3-38-2004, revision 87. doesnt look too good either [03:06] 34.117963] watchdog: BUG: soft lockup - CPU#9 stuck for 26s! [systemd-udevd:443] [03:07] not sure what this is myself xamboni kernel or snapd... [03:07] !info linux-image-generic focal [03:08] 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] linux-image-generic (5.4.0.109.113, focal): Generic Linux kernel image. In component main, is optional. Built by linux-meta. Size 3 kB / 19 kB. (Only available for amd64, armhf, arm64, powerpc, ppc64el, s390x.) [03:08] xamboni: is your system up to date? [03:08] otherwise you could try some things on recoverymode [03:09] I would think it is up to date unless there is something I can try outside apt upgrade. [03:09] xamboni: apt doesnt complain about something? [03:10] lotuspsychje: At the moment no. [03:10] kk [03:12] 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] 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] 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] tomreyn: Thinking I might try updating the BIOS? [03:41] I can try that real quick. Thanks for the suggestion. [03:43] xamboni: it's a far fetched idea. should not do harm. but i'm not sure what really happened. [03:44] tomreyn: Not a bad idea though. I'll try it now. Thanks for the input. [04:00] Sadly still a failure after the BIOS upgrade. [04:02] xamboni: still a cpu core lockup? [04:02] BIOS still exists? I thought it was all EFI / firmware these days. [04:03] mainboard vendors still callit BIOS, though, "UEFI BIOS" [04:04] tomreyn: I don't have the log this time because it was a quick boot but still the same bios splash hang. [04:04] wez: :) you are right. [04:04] !bootlog [04:04] To get a more verbose log of the boot process, remove "quiet" and "splash" from the kernel boot parameters and add "debug systemd.log_level=info". For info on editing kernel boot parameters, see https://wiki.ubuntu.com/Kernel/KernelBootParameters [04:05] or use your serial console and log the output ;) [04:05] I log ttyS0. It is a nicer setup. [04:06] 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] wez: i concur. [04:06] tomreyn: And lets see, another still used term that is deprecated is 1st, 2nd and 3rd degree burns. [04:07] wez: Spot on. I am old though.. [04:07] I think we need to sort this all out :) [04:07] xamboni: maybe do some stress testing on the old kernel if you still have it [04:08] you should be able to switch to it from the grub menu [04:08] I have the old kernel. I have to fall back to use the machine. [04:08] 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] 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] xamboni: I thought DES was broken too. [04:11] 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] wez: ... I was just trying to think up older terms and get them in the same sentence. :) [04:12] xamboni: :P [04:13] xamboni: Speaking of old things, I miss the turbo button on my computer :( [04:15] wez: I was looking at pckeyboard.com (unicomp keyboards) to try and get a ps/2 old style buckling situation going again. [04:22] Thanks for the input. I'll check back once I get more info on the mysterious boot hang. [04:39] Hello. [04:40] Is this a chat room where i can ask for help regarding my ubuntu OS? [04:42] yes [04:42] webchat38: https://www.nohello.com [04:42] hi, Thnak you for responding [04:42] so i just upgraded my ubuntu [04:43] from the previous version 21.10 to the new 22.04 [04:44] but the upgrade completed it seems that there is a major issue with my system [04:44] when the PC restarted... [04:44] the initial screen and the grub menu looked ok.. [04:45] i have installed 3 OS's in my system [04:45] windows 10, Linux mint and Ubuntu.... [04:46] although im still just a beginer i guess with linux and dont have much knowledge about much of the commands etc.., [04:47] i still like to learn more about linux ona daily basis [04:47] now the problem is.. [04:48] or rather are... [04:49] the grub menu shows the Previous version of Ubuntu even after the update, which is not the biggest problem though...... [04:49] but after i select ubuntu... [04:50] the system starts with everything being big.. [04:50] as if there is a something wrong with the display settings.. [04:51] just to inform you, i have never faced this problem in any of my previous upgrades that i ahve done.. [04:52] 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] did you intend to keep the old version ? [04:53] but the display settings are still not adjusted [04:53] no, its now the new version and i dont wanna revert back to the old version [04:54] so i went into the display settings and i checked to find "unknown resolution"... [04:55] with only the option for one setting ( i think some 480*640 or so) [04:56] so then i googled the matter under "unknown resolution" [04:56] and seeked the help of several sites including ubuntu forom's [04:57] here's a list of the things that i have tried that have words for some according to what i have read [04:58] changed the setting of language to English US everywhere... [04:59] using the GUI checked for additional drivers....which said non avabl [05:00] even used the terminal for apt update upgrade... [05:00] hmm [05:01] the checked the mutiverse etc repository setting if it was checked in the gui [05:01] when you go to "additional drivers", what driver does it say its currently using? [05:02] later even found out that my sound is not working.. [05:02] bluethooth is not getting detected [05:03] webchat38: it's possible that you're using mint's grub, which points to old ubuntu's kernel [05:03] In that case, you need to run `update-grub` from inside the new ubuntu, so that it re-generates grub.cfg [05:03] Try sudo update-grub, then reboot [05:03] when i went to additional drivers in the gui it just said something like non required [05:03] Then go to mint, then sudo update-grub from there as well [05:03] i did the upgrade grub as well [05:04] and then rebooted [05:04] In both your linux installations? [05:04] but all the problems still persist [05:04] no only in ubuntu [05:04] What's the output of: uname -a [05:06] 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] In your Ubuntu installation, what's the output of: uname -a [05:07] as my unbuntu was working i didnt bother to go deep into the issue with mint [05:08] " output of Uname -a" could u let me know what this is? as in? [05:09] You open a terminal, run `uname -a`, and tell us the result [05:09] It will show your kernel version [05:09] so im just a beginner with linux, forgive me for my lack of knowledge [05:09] ok ill need to check that [05:09] You're on windows atm? [05:09] im right now using my windows OS [05:10] yes [05:10] OK, reboot and join from Ubuntu [05:10] ok [05:10] let me try loging in from my phone as well using a browser in case i can [05:11] now how do i come with the same id [05:11] lol [05:11] let me just check [05:12] It's best to provide a nickname so that people remember you; and replace that webchatXX one [05:13] im just checking what i can do [05:14] ok [05:14] so on my phone i've joined in as another user [05:14] 'webchat3852' [05:14] It's working here [05:15] So i guess I'll try messaging from here then [05:16] im now going to close this chat and continue as 'webchat 3852' [05:22] Sorry for the long wait [05:23] I realy thank everyone in advance for helping me out here [05:23] Was stressed out about this since the past almost 9 hours now [05:24] I appreciate all the help [05:24] My pc is now restarting [05:24] I'll load Ubuntu and open a terminal [05:25] Hopefully in the next one minute approximately [05:27] Ok just entered my password [05:27] Now starting a terminal [05:29] 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] Ok so after running the uname -a... [05:31] It says.. [05:32] 5.13.0-28 generic # 31 Ubuntu [05:35] webchat3852: 22.04 has 5.15 kernel; you're booted with the older kernel which isn't properly installed anymore [05:35] webchat3852: what's the output of this? ls -l /sys/firmware/efi [05:36] Let me check [05:36] And also this: ls -l /boot | nc termbin.com 9999 [05:43] Ok i think I'm doing something wrong [05:43] So for the second one.. [05:44] I.e ls -l / boot... [05:44] I'm getting ' https ://termbin.com/mfgf [05:45] And for the first one I'm getting an error, but let me do it again [05:51] webchat3852: OK now run: sudo dpkg-reconfigure grub-pc [05:51] And press "enter" in all prompts [05:51] This will allow Ubuntu's grub to be the main grub, instead of Mint's grub, which has the old version [05:52] When i type ls - l/sys/firmware/efi , I'm getting an error [05:52] Ok [05:54] Will press enter for all [05:58] After clicking enter 3 times [05:58] It's not proceeding further from the 3rd screen [05:59] It says... [06:00] 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] 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] There are 3 paragraphs [06:01] Ok i used tab [06:02] It selected ok [06:02] Thanks for that [06:02] I guess it did not show me the whole screen and there was more to it [06:03] There's a fourth paragraph as well saying ' note:-' [06:03] Everything is enlarged and big . [06:04] Pressed enter [06:04] Just press the ok buttons , and reboot after it's done :) [06:05] Selected the correct drive [06:05] Sda6 where Ubuntu is [06:05] Now it's processing [06:06] Once again thank you so much [06:06] I'm almost In tears right now [06:06] And greatfull that I'm getting help [06:06] Eeeew [06:06] Do not select sda6 [06:06] I was so upset and stressed since last night [06:06] Re-run it and select sda, like I said [06:07] Holy crap [06:07] > Select your whole disk if it's not already selected, e.g. /dev/sda (not sda1), then navigate to the ok button [06:07] It's finished [06:07] Can I just run it again? [06:07] Yes [06:08] Ok [06:08] Doing it again [06:08] Check sda, uncheck sda6 [06:08] I'm so sorry [06:08] Ok [06:08] Starting it again then [06:09] Ok [06:09] Started again [06:10] Selecting sda [06:10] Selected [06:10] Gonna press ok now [06:11] Ok done [06:11] Processing [06:12] Will reboot once it's done ... [06:13] Ok it's done [06:13] Gonna reboot now [06:14] Rebooting [06:14] !enter [06:14] Please try and keep as much of your info as possible on ONE line - easier to follow for everyone. [06:15] Ok, the grub menu looks like the previous one with no change. It says Ubuntu 21.10 [06:16] Selected Ubuntu [06:17] Did you manage to check sda? Do you have another disk? [06:17] Ok restart complete, and no change to the system... [06:18] Yeah I selected and entered ok ok sda [06:18] I have 2 HDD drives [06:18] It's possible that your grub is in sdb then; run sudo dpkg-reconfigure once more, and select sdb as well [06:19] Ok [06:19] Sure [06:19] (it depends on which disk you have selected as the first one, in bios) [06:19] Ooo ok [06:19] So now check both sda and sdb, and nothing more, no sda1 or sda6 [06:19] Sorry about that, i should have mentioned it, didn't realise that [06:19] Ok [06:22] There's an asterisk mark on the /dev/sdb [06:23] Proceeding with that and going ahead with sdb [06:24] There were asterisks already, on both sda and sdb? [06:25] Anyway after it's done, run this to be 100% sure: sudo grub-install /dev/sda; sudo grub-install /dev/sdb [06:25] Then reboot [06:28] Ok [06:29] It's done so to be 100 percent sure running the grub-install sda and sdb [06:29] Will reboot after that [06:30] Thanks [06:34] Rebooting [06:35] O wonderful, grub menu change showing Ubuntu as the first option [06:35] what is /srv [06:35] Ok it's starting this time with small letters [06:35] Oooo [06:35] Ok [06:36] Looks good [06:36] Great [06:36] It's starting up [06:36] The Ubuntu logo now looks normal [06:36] Processing [06:37] Ok now at the enter password screen which also looks normal [06:38] With the correct resolution [06:38] Entering the password [06:38] You don't need to mention all steps, you can just tell us the end result :) === gschanuel6 is now known as gschanuel [06:39] Eureka [06:39] Success [06:39] Ok now I'm crying with tears of joy [06:40] Lol [06:40] It's resolved [06:40] OMG [06:40] Thank you thank you thank [06:41] Everyone thank you soooooooooooooo much [06:41] Alkisg thank you sooooooooooooooooooooooooooo oooooooooooo much [06:41] 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] You're welcome :) [06:42] I don't even know what to say right now [06:42] Just to clarify, sleep and wakeup are working fine, but [06:42] Thank you for your time, your patience, your guidance [06:42] touchpad interaction to wake no linger works ... [06:43] s/linger/longer/ [06:44] any thoughts ... ? === bran is now known as branant [07:04] anyone ... ? [07:05] systemctl --failed ==> fwupd-refresh.service: failed [07:05] 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] alkisg: I can confirm. Same here on clean installation of 22.04. [07:09] Thank you branant; I think the problem is this: # grep Exit /lib/systemd/system/fwupd-refresh.service [07:09] SuccessExitStatus=2 [07:09] I.e. it expects a failure! as a successful exit === bran is now known as branant === aSah is now known as Haffi_ [07:11] 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] I guess the semantics of what "no action" is changed in some update, and it's now considered as failing [07:12] *means [07:18] It makes sense. Thanks for the explanation. [07:35] good morning all [07:38] @alkisg what do you see for systemctl status fwupd-refresh.service ? [07:38] I get Process: ... ExecStart=/usr/bin/fwupdmgr refresh (code=exited, status=1/FAILURE) [07:38] ick: (code=exited, status=1/FAILURE) [07:39] If I comment out the `SuccessExitStatus=2` line and reboot, it bypasses the problem [07:39] This is not the Success=2 we were looking for [07:39] I guess we need to report this issue... [07:39] fwupdmgr returns 0, while the unit expects 2 [07:39] By commenting out that line in the unit, it's not in failed state anymore [07:41] Where does the refreshed metadata go? can we look for it? [07:41] 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] We can put both 0 and 2 there instead of commenting it out [07:42] what does status=1/FAILURE mean then? 1 is neither 0 nor 2 [07:44] It's a generic "it was not zero" [07:44] Instead of printing the actual error code, they always print 1 [07:45] "they" = what ? [07:45] That's not a normal coding standard in my limited experience. [07:46] They => probably the systemd code that prints that line [07:46] Instead of printf("%d/FAILURE\n", code") they have printf ("1/FAILURE\n") [07:47] oh, systemd. Cannot stop applauding. [07:47] Yes, 2 is 1 === Guest92 is now known as nikitasbstu [07:50] How to find the relevant code to see where the fw metadata goes? [07:54] i see that man fwupdmgr fwupdtool fwupdagent are all exceedingly brief, and point to no further documentation. Are these documented anywhere? [07:57] fwupdmgr --help gives something [08:01] fwupdmgr verify # this only reports failures on UHD graphics 630 and system firmware [08:01] @alkisg, what do you see for: fwupdmgr verify [08:02] 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] But the program itself doesn't matter, I'm only worried about the failed service part [08:03] I fixed it by setting SuccessExitStatus=0,2, but it should be reported in launchpad... sorry no time to do it currently [08:04] Is it expected that everything fwupdmgr attempts to verify, fails? [08:06] 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] I submitted the issue in https://github.com/fwupd/fwupd/issues/4567 [08:11] Issue 4567 in fwupd/fwupd "Should SuccessExitStatus=2 be SuccessExitStatus=0,2?" [Open] [08:14] Thanks for doing that. What can we do about the firmware errors? [08:15] failed to verify CoffeeLake-S GT2 [UHD Graphics 630]: failed to read firmware: Error reading from file: Input/output error [08:15] failed to verify System Firmware: No stored checksums for 1.12.0 === diskin is now known as Guest4157 [08:34] ребятки тут кто есть. [08:35] Ё [08:35] ? [08:38] When to hardware updates end for Ubuntu 20.04? [09:25] 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] the daemon starts as part of the user session, do not try to start it as a system daemon [09:29] are you sure it is not running already (how did you check ?) [09:29] `pulseaudio -k` ? [09:31] pacmd list-cards [09:31] No PulseAudio daemon running, or not running as session daemon. [09:32] aha [09:32] have you tried creating a fresh test user yet ? to see if some old config hangs around in your existing account ? [09:32] Hum, no. I could try that. [09:33] Also tried: [09:33] systemctl enable pulseaudio [09:33] Failed to enable unit: Unit file pulseaudio.service does not exist. [09:33] yeah, it should not 🙂 like i said above ... it is a session daemon [09:34] I see [09:34] normally started when you log in to the session and owne by your user [09:34] *owned [09:40] Same result for test user. :/ [09:40] well, one dtapint more, you know it is not old config ... delete the user ... [09:40] *datapoint [09:41] 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] cat /proc/asound/cards [09:41] 0 [PCH ]: HDA-Intel - HDA Intel PCH [09:41] HDA Intel PCH at 0xa121c000 irq 141 [09:42] Is that correct? [09:42] looks good [09:43] does "aplay -l" also list devices ? [09:43] Yes: [09:43] aplay -l [09:43] **** List of PLAYBACK Hardware Devices **** [09:43] card 0: PCH [HDA Intel PCH], device 0: ALC257 Analog [ALC257 Analog] [09:43] Subdevices: 1/1 [09:43] Subdevice #0: subdevice #0 === kushagra0 is now known as kushagra [09:44] webchat59, better dont paste directly into the channel for longer pastes 😉 [09:45] Yes, sorry about that. [09:46] journalctl | grep pulse | nc termbin.com 9999 [09:46] run that and give the url it returns [09:46] https://termbin.com/7fg0e [09:51] webchat59, hmm, that looks weird, especially the update-manager warnings indicate you have some wrong package sources around that break something [09:51] do you have any audio related PPAs enabled ? [09:52] Not that I recall. How could I check for that? [09:55] 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] check in your software settings, there is a tab "additional software" or some such, that should list all PPAs [09:58] Pipewire [09:59] ick, i think these are harmless [09:59] webchat59, well, pipewire is a pulseaudio replacement ... [09:59] But I think the ppa is disabled? [10:00] Should that matter? [10:01] 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] I see. Is there a way for me to solve that without changing much the configuration? [10:04] apt-cache policy pulseaudio pipewire-pulse | nc termbin.com 9999 [10:04] lest see where these come from [10:05] https://termbin.com/32hv [10:05] hmm, looks fine [10:08] so it must be other packages, i.e. some libs ... [10:09] 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] When to hardware updates end for Ubuntu 20.04? [10:11] *do [10:11] Alright, I'll go through them. [10:11] zetheroo, hardware updates ? [10:12] ogra: I saw an Ubuntu release graphic showing maintenance and hardware updates [10:12] zetheroo, you mean kernel updates ? [10:12] trying to find the graphic again ... [10:12] https://ubuntu.com/about/release-cycle [10:13] right [10:13] oh it changed [10:14] LTS release are supported for 10y ... [10:14] We have an older version of the graphic which shows 'Hardware and maintenance updates' and then 'Maintenance updates' [10:14] after 5y you need to use ubuntu advantage to get security updates though [10:14] (which is free for persona use, paid for commercial use) [10:14] *personal [10:15] now it says 'Interim release Standard Support' where before it said 'Maintenance updates' [10:15] yeah, some marketing terms changed 🙂 [10:16] 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] on a technical level nothing changed thogh ... [10:18] (the different support phases are still the same, just their naming is different ... i think to better distinguish LTS from non LTS) [10:18] this is the graphic we were using https://www.fossmint.com/wp-content/uploads/2016/04/Ubuntu-Release-Cycle.png [10:19] right ... same but different ... [10:19] technically nothing changed 🙂 [10:20]