arkanoid | ubuntu 24.04 forces ssh PasswordAuthentication to be enabled | 01:54 |
---|---|---|
arkanoid | /etc/ssh/sshd_config.d folder is empty, and /etc/ssh/sshd_config file has "PasswordAuthentication no" in "Hosts *" section | 01:56 |
arkanoid | even after restarting ssh.service, clients can login using password only | 01:56 |
leftyfb | that's because you didn't restart it completely | 01:57 |
leftyfb | arkanoid: https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#openssh | 01:57 |
leftyfb | openssh 9.0p1 uses socket based by default | 01:57 |
leftyfb | https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189 | 01:57 |
arkanoid | Oh | 02:00 |
arkanoid | Yes, right. My fault. Thanks | 02:01 |
LuckyMan | during an upgrade, if the computer is shut down is there any way to turn it on and continue the release upgrade? | 02:09 |
leftyfb | LuckyMan: sometimes "sudo apt update ; sudo apt install -f && sudo apt full-upgrade" works | 02:10 |
LuckyMan | I mean a full release upgrade, but I will try that | 02:11 |
enigma9o7 | I'm not familiar enough with the do-release-upgrade process, is the download/install the last step? | 02:11 |
LuckyMan | idk | 02:11 |
enigma9o7 | Well yeahI meant for leftyb as he knows more than I :) | 02:11 |
leftyfb | enigma9o7: it's just a python script in /usr/bin/do-release-upgrade | 02:12 |
Bashing-om | LuckyMan: Depending on how far progressed - ' sudo dpkg --configure -a ' may also be of benefit. | 02:22 |
LuckyMan | Bashing-om, I think it was on the middle of the install, installing packages | 02:25 |
Bashing-om | LuckyMan: What shows ' lsb_release -a ' ? | 02:28 |
LuckyMan | Bashing-om, right now I don't have acess to the computer, I was upgrading it remotely and my father probably waked up and disconect it and went to bed again | 02:30 |
camarada | hello | 02:30 |
LuckyMan | it's 3am here, he must be sleeping | 02:31 |
Bashing-om | LuckyMan: Well, when you have access to the box we can continue this :D | 02:33 |
LuckyMan | ok thanks | 02:33 |
eawfaw | Do you guys have a trustworthy script to remove all old unused kernels on ubuntu? | 03:13 |
toddc | eawfaw: "sudo apt autoremove" or more spcific? it will keep 3 most recent plus clear old software | 03:15 |
eawfaw | toddc: After runnnig that, I run dpkg --list | grep 'linux-image-[0-9]' and I get a lot of stuff there: https://pastebin.com/ax3sWN3L are those only the last 3 kernels? Is that expected? | 03:20 |
toddc | not run into that but it may be due the wide range yu may need to manually remove the older ones 1 sec have the commands but need to find them | 03:25 |
toddc | eawfaw: my freind wrote this article for me and I still use it https://www.azloco.org/2014/06/18/remove-old-kernels/ | 03:27 |
stu | eawfaw: The lines starting with `rc` are removed packages, you only have two installed (starting with `ii`) | 03:27 |
eawfaw | I know the commands, I'm looking for a script that does everythin gautomatically | 03:27 |
eawfaw | stu: interesting, thanks! | 03:27 |
stu | check man dpkg-query if you want to read more about the list format | 03:27 |
toddc | thanks stu one more tidbit to remember | 03:28 |
=== arch_ is now known as justagenericuser | ||
justagenericuser | hi all | 03:36 |
=== xcynth_ is now known as tbowes | ||
matsaman | justagenericuser: hi | 03:40 |
=== stu is now known as [stu] | ||
=== [stu] is now known as stu | ||
LuckyMan | Bashing-om, leftyfb : It seems the computer was not disconnected after all, I could regain the connection and finish the install | 03:56 |
LuckyMan | couldn't check out if all went well after reboot because of the wayland login | 03:57 |
LuckyMan | but I'm guessing things are fine | 03:58 |
LuckyMan | tomorrow I will know | 03:58 |
Bashing-om | LuckyMan: \o/ | 04:01 |
LuckyMan | Bashing-om, it 'detected' some errors during the process thow (gtk message on screen) | 04:04 |
LuckyMan | but I just canceled the message and keep going | 04:05 |
Bashing-om | LuckyMan: Often times the package manage will suggest corrective measures. | 04:06 |
LuckyMan | and amazingly rustdesk kept working after reboot because I could connect, just couldn't login | 04:06 |
LuckyMan | nice to know | 04:07 |
=== xar_ is now known as xar | ||
nbf | hi | 06:30 |
=== TWPEagle816 is now known as TWPEagle81 | ||
Bardon | Hello, I am running Ubuntu 24.04, and when I try to poweroff my laptop, I see a black screen with the Ubuntu logo and a spinning circle below (as is expected), but then the spinning circle hangs, the whole laptop seems frozen, and it never actually powers off. The last line of journalctl says "systemd-journald[326]: Journal stopped". | 07:59 |
Bardon | The laptop is a VAIO SVS1511C5E from 2012. Could it be a hardware fault? | 08:00 |
Bardon | When I boot it up, dmesg consistently says "BUG: kernel NULL pointer dereference, address: 00000000000000a0", then "#PF: supervisor write access in kernel mode" then "#PF: error_code(0x0002) - not-present page" in highlighted red. Maybe that could be related, I don't know | 08:01 |
lotuspsychj3 | Bardon: did you try F1 at shutdown process to see text mode shut down? | 08:09 |
sixwheeledbeast | It may not be related. Best to get the error from when it hangs. So either above or use shutdown -v or even disable splash. | 08:21 |
lotuspsychj3 | Bardon: maybe you can also compare with halt from terminal | 08:21 |
oerheks | i found a tip, run bootrepair from the live iso | 08:23 |
oerheks | oops | 08:23 |
oerheks | wrong window | 08:23 |
Bardon | lotuspsychj3: I couldn't get text mode shutdown but pressing F1. Somehow I got a text mode shutdown when I shutdown the laptop immediatly after booting up. If I remember correctly, the last line says something like: reached target poweroff | 08:53 |
Bardon | lotuspsychj3: halt from terminal also hangs | 08:53 |
ravage | this may be a problem with the very old hardware | 08:54 |
Bardon | I tried disabling the virtualization from the BIOS. I tried setting intel_iommu=off in the boot command (because of a similar issue I saw on https://bbs.archlinux.org/viewtopic.php?id=253157) | 08:54 |
ravage | i also could not fine any downloads for that device on the sony site | 08:54 |
ravage | not a single bios update provided | 08:55 |
Bardon | ravage: Why are you talking about download on the sony site? Are you suggesting it could be fixed with a BIOS update? | 08:55 |
ravage | it is an error that is usually fixed by one yes | 08:56 |
Bardon | If I remember corrrectly, the issue appeared out of nowhere about 5 years ago | 08:56 |
ravage | it seems to be a power management problem | 08:56 |
ravage | new software. old hardware | 08:56 |
Bardon | my BIOS says "rev 3.7", idk if that's relevant | 08:56 |
Bardon | and my BIOS is set to Legavy, not UEFI | 08:57 |
Bardon | Legacy* | 08:57 |
Bardon | I could try to install ubuntu 14.10 or something, or set the BIOS to UEFI | 08:58 |
ravage | as long as you keep it offline do whatever you like | 08:59 |
Bardon | could setting the BIOS to UEFI solve the issue or is it not related? | 08:59 |
ravage | i dont think i will change anything really | 09:00 |
ravage | you can try of course | 09:00 |
ravage | it may be just time to retire that hardware or use it with the flaws it has | 09:00 |
Bardon | ah, maybe I can just boot a liveUSB in UEFI mode and see how poweroff behaves | 09:00 |
Bardon | ravage: Same thing in UEFI on a liveUSB :( | 09:11 |
Bardon | I also encountered a weird behaviour when booting up, I had a black screen with fans running at 100%. I powered it down with the button and then it booted fine | 09:12 |
Bardon | ravage: Maybe a solution could be to flash Coreboot on that machine | 09:12 |
Bardon | It is old enough for autoport | 09:13 |
lotuspsychj3 | Bardon: you could change your grub to always text boot/shutdown with "quiet splash" changed to "" | 09:19 |
Bardon | lotuspsychj3: Ah, thanks | 09:40 |
lotuspsychj3 | Bardon: maybe you will be able to catch more there | 09:40 |
lotuspsychj3 | always better to see whats happening to your machine in realtime | 09:40 |
Bardon | lotuspsychj3: So the last line I see is "systemd-shutdown[1]: Powering off." | 09:44 |
Bardon | The power management that could be faulty would be a firmware living in the BIOS chip, right? Something that would be overwritten by Coreboot? | 09:45 |
lotuspsychj3 | things should get tested Bardon | 09:48 |
lotuspsychj3 | if it was me, i would also try another ubuntu flavour to compare | 09:49 |
ravage | I don't think another flavor will change a kernel bug message | 09:50 |
Bardon | lotuspsychj3: What do you mean by "things should get tested"? | 09:50 |
lotuspsychj3 | Bardon: yeah like the other flavor | 09:51 |
sixwheeledbeast | I agree I can't see another flavour helping if kernel | 09:51 |
lotuspsychj3 | if its a kernel fault assumed, he could test !mainlines right? | 09:52 |
lotuspsychj3 | Bardon: did you mention ubuntu release & kernel version? | 09:53 |
Bardon | ravage: lotuspsychj3 Here is the whole dmesg output if that may help https://termbin.com/5am9 | 09:54 |
Bardon | lotuspsychj3: It is 24.04, with kernel 6.8.0-41 | 09:55 |
Bardon | The bug I was mentionning in higlighted red is at second 4.798088 | 09:57 |
Bardon | and it happens at every boot | 09:57 |
lotuspsychj3 | Bardon: did other ubuntu releases shutdown on this same machine? | 09:58 |
brenndo | never at second | 09:58 |
Bardon | lotuspsychj3: hang during poweroff you mean? That's what I remember happening from ~5 years ago, yes. I can download another release to test though | 09:59 |
brenndo | time moves .... | 10:00 |
Bardon | Should I try with 14.04? | 10:00 |
Bardon | That laptop is from 2012 | 10:00 |
ravage | No | 10:01 |
brenndo | try ritzl | 10:01 |
lotuspsychj3 | Bardon: if the kernel is suspected, you can try !mainline kernels | 10:01 |
lotuspsychj3 | !ops | brenndo is back | 10:01 |
ubottu | brenndo is back: Help! Channel emergency! (ONLY use this trigger in emergencies) - CarlFK, DJones, el, Flannel, genii, hggdh, ikonia, krytarik, mneptok, mwsb, nhandler, ogra, Pici, popey, sarnold, tomreyn, Unit193, wgrant | 10:01 |
brenndo | buku | 10:02 |
Bardon | ravage: Which one should I use? | 10:03 |
ravage | The latest supported release is 20.04 | 10:03 |
brenndo | hey ravage u are not listed | 10:03 |
ravage | But I would suggest adding Ubuntu Pro | 10:03 |
ravage | Support ends soon | 10:03 |
Bardon | ravage: If the point is to test an old kernel, then should I care about testing a supported release? | 10:04 |
Bardon | lotuspsychj3: mainline kernel as in https://github.com/bkw777/mainline? | 10:05 |
ravage | s/latest/oldest/ | 10:05 |
ravage | A not supported kernel is not helpful | 10:05 |
brenndo | read ritzl | 10:05 |
ravage | It does not get any security patches | 10:05 |
Bardon | brenndo: what that ritzl message for me? I don't know what it means, sorry | 10:05 |
ravage | So any system without security patches should only be used offline | 10:06 |
lotuspsychj3 | !mainline | Bardon | 10:06 |
ubottu | Bardon: The kernel team supply continuous mainline kernel builds which can be useful for tracking down issues or testing recent changes in the Linux kernel. More information is available at https://wiki.ubuntu.com/Kernel/MainlineBuilds | 10:06 |
Bardon | ravage: lotuspsychj3 By the way, does the dmesg output that I sent hints at a kernel bug or a hardware fault? | 10:07 |
brenndo | yes is a short introduction, distribution | 10:07 |
brenndo | @Bardon | 10:07 |
Bardon | I'm googling "ritzl linux" but I see nothing relevant. Am I missing something? | 10:08 |
ravage | Your BIOS definitely is too old to handle current power management in the kernel. Probably due to a bug or incompatibility | 10:08 |
ravage | You can try an older supported release or accept the bug | 10:08 |
ravage | I could not find any bios updates for your device | 10:09 |
Bardon | Or flash Coreboot I suppose | 10:09 |
Bardon | oh, thank you for looking it up :) | 10:09 |
ravage | Make sure to really understand coreboot | 10:09 |
brenndo | u want ritzl is nonamefile u can open in ANY editor | 10:09 |
ravage | It is not a simple replacement for any hardware | 10:09 |
Bardon | I have compiled it and flashed it multiple times, but never done it on a machine that is not officially supported already... | 10:10 |
brenndo | dont blame your device with binärcode | 10:11 |
brenndo | matters | 10:11 |
brenndo | ~ | 10:12 |
ravage | Just flashing it on unsupported hardware will probably make the system unbootable | 10:12 |
ravage | And you do not even have a bios file to restore from | 10:12 |
Bardon | Right, but then I can flash the stock bios back | 10:12 |
ravage | If that is even possible on a bricked system | 10:12 |
Bardon | I have the tools to extract a BIOS from the chip | 10:12 |
ravage | Good luck then | 10:13 |
Bardon | and the BIOS file can be extracted with flashrom on my machine :) | 10:13 |
Bardon | yes well, my chances are low but I'll give it a try I guess | 10:14 |
Bardon | It's either that, use an old release (potentially too old to be maintained) or live with the bug | 10:14 |
sixwheeledbeast | I probably wouldn't mess with the BOIS beyond looking for an updated version. | 10:15 |
lotuspsychj3 | me neither | 10:15 |
Bardon | I'll start by booting a liveusb of 14.04 to see if it powers off properly | 10:15 |
sixwheeledbeast | your most likely to end up with a brick | 10:15 |
lotuspsychj3 | Bardon: i wouldnt compare a liveusb with a physical install neither, to prove a bug | 10:16 |
sixwheeledbeast | I have an old unpopular model laptop that had a shutdown error and temporary pinned it to an older working kernel version, eventually 5 years later the kernel fix was applied. | 10:18 |
sixwheeledbeast | have you tried things like acpi=off flag? | 10:26 |
Bardon | sixwheeledbeast: No, I'll try now | 10:29 |
Bardon | 14.04 liveUSB powers off fine. 24.04 liveUSB doesn't, it has the same issue as my regular install | 10:30 |
Bardon | sixwheeledbeast: acpi=off doesn't fix the issue | 10:43 |
Bardon | I got one successfull reboot though :o (with no options in the boot command) | 10:43 |
lotuspsychj3 | lets assume its kernel 6.8 related | 10:43 |
lotuspsychj3 | try something higher Bardon | 10:44 |
Bardon | I'm very surprised by this successfull reboot... I wonder why this issue isn't consistent | 10:44 |
Bardon | lotuspsychj3: I'mm try 20.04 | 10:45 |
sixwheeledbeast | Well with my issue, I worked my way through kernel versions until I pinned down the exact version. | 10:45 |
Bardon | I don't know how to change kernels | 10:45 |
sixwheeledbeast | maybe find the last LTS release it works on for a start. | 10:45 |
Bardon | Ok | 10:46 |
Bardon | My internet is quite slow though, downloading 20.04 takes 45 minutes | 10:46 |
Bardon | ah, I'll just get the server image | 10:47 |
Bardon | Still 15 minutes to download.. | 10:47 |
=== synapt is now known as nate | ||
=== nate is now known as 073AAJEHX | ||
Bardon | 20.04 works | 11:13 |
Bardon | Downloading 22.04 | 11:13 |
Akimb | I updated from 22.04 to 24.04. Expected It to update to 24.04.01. Did the usual do_release_upgrade without any flags set. Why can't my OS see 24.04.01 ? | 11:15 |
sixwheeledbeast | I'd assume that's 5.15, maybe make note of the kernel version if your trying to find that. | 11:16 |
sixwheeledbeast | 24.04.1 is available | 11:16 |
sixwheeledbeast | I had the notification yesterday. | 11:16 |
Akimb | It is available, but my upgrade went to 24.04 for some reason | 11:17 |
Akimb | lsb_release -> Release:24.04 | 11:17 |
sixwheeledbeast | it's possibly just where your looking. | 11:20 |
sixwheeledbeast | what does "more /etc/lsb-release" or if you have it "neofetch" show. | 11:20 |
Akimb | DISTRIB_RELEASE=24.04 | 11:21 |
Akimb | via "more /etc/lsb-release" | 11:22 |
sixwheeledbeast | is there no description line? | 11:22 |
Akimb | DISTRIB_DESCRIPTION="Ubuntu 24.04 LTS" | 11:22 |
sixwheeledbeast | release is normal to be without dot version | 11:22 |
sixwheeledbeast | I can't check I'm still on 22.04 but I doubt it's anything to worry about. | 11:23 |
vic-thor | does ubuntu use debian's live-build for live iso's or something else? | 11:30 |
BluesKaj | Hi all | 11:40 |
Bardon | 22.04 does not work | 12:02 |
Bardon | So if it is a kernel issue, it lies between the latest kernel used in 20.04 LTS and the latest kernel used in 22.04 LTS | 12:03 |
Bardon | I'll download 21.04 | 12:04 |
Bardon | 21.04 (server) works. Downloading 21.10, which will be my last version to test | 12:54 |
Bardon | lotuspsychj3: sixwheeledbeast ravage: 21.04 and before seem to work fine, 21.10 and up seem to not work. | 13:24 |
Bardon | Those are the server version, tested by booting a liveUSB | 13:24 |
Bardon | Which means that kernels 5.11.0-16-generic and before work, but kernels 5.13.0-19-generic and up do not. I got the version number from "file vmlinuz", with the vmlinuz file under casper/ in the isos I downloaded | 13:29 |
Bardon | How can I bisect kernels and boot them up in Ubuntu? | 13:32 |
Bardon | Hmm I see 63 kernel releases between those two | 13:37 |
Eduardo- | Hi all. I just upgraded to Noble and noticed that the Captive Portals when connection to wifi doesn't pop-up anymore. I noticed that the file /usr/libexec/gnome-shell-portal-helper is missing. Looks like it comes from the gnome-shell package: see https://packages.ubuntu.com/search?searchon=contents&keywords=gnome-shell-portal-helper&mode=exactfilename&suite=noble&arch=any But when downloading the gnome-shell DEB package and extracting it, it | 13:38 |
Eduardo- | is not there! Can someone else help me to confirm this? Is this eventually a bug? | 13:38 |
=== pikapika_lunar is now known as militantorc | ||
Bardon | Can I boot ubuntu 22.04 with Linux kernel 5.12? | 13:40 |
Conqueror | Hello there! after upgrading ubuntu 22.04 to 24.04.1, I lost my firefox and terminator font settings :( Any recommendation? | 13:43 |
=== GreenRio- is now known as GreenRiot | ||
polo_ | I had a bug where firefox suddently stopped accepting keyboard input until i kill it and restart it , how can i report that bug | 13:58 |
ogra_ | polo_, snap info firefox | grep contact | 14:08 |
ogra_ | polo_, that is the link for bugs ... | 14:08 |
polo_ | it returned nothing | 14:10 |
ogra_ | $ snap info firefox |grep contact | 14:13 |
ogra_ | contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla | 14:13 |
nteodosio | EdFletcher, it was removed by security team: https://salsa.debian.org/gnome-team/gnome-shell/-/blob/ubuntu/noble/debian/patches/CVE-2024-36472-4.patch?ref_type=heads | 14:16 |
-ubottu:#ubuntu- In GNOME Shell through 45.7, a portal helper can be launched automatically (without user confirmation) based on network responses provided by an adversary (e.g., an adversary who controls the local Wi-Fi network), and subsequently loads untrusted JavaScript code, which may lead to resource consumption or other impacts depending on the JavaScript code's behavior. <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36472> | 14:16 | |
kk1234 | polo_ facing the same issue, you are not alone | 14:27 |
sixwheeledbeast | Bardon: apt search linux-image-5.12 is a start, whatever you install you will need to make sure you select at boot manually. | 14:46 |
Bardon | sixwheeledbeast: `apt search linux-image-5.12` doesn't list any packages | 14:53 |
sixwheeledbeast | on the distro with 5.12 available it should | 14:54 |
lotuspsychj3 | Bardon: downgrading kernels isnt the way to go, hence why i suggested !mainline kernels | 14:54 |
Bardon | sixwheeledbeast: Ah so this should be done from 21.04 or 21.10 maybe | 14:54 |
sixwheeledbeast | if you find the version with the issue you can maybe look up what changed in the changelog and report it. | 14:55 |
sixwheeledbeast | well actually maybe you should go from 5.13 and go backwards to the earliest, thinking about it. then you can rule out 5.13 | 14:58 |
Bardon | lotuspsychj3: So if I want to test the kernel version 5.12, should I download the .deb from https://kernel.ubuntu.com/mainline/v5.12/ ? | 14:58 |
Bardon | Then install it with dpkg -i ? | 14:58 |
Bardon | It says I need libssl1.1 | 15:04 |
Bardon | On 24.04, this went fine: `sudo dpkg -i linux-headers-5.12.0-051200_5.12.0-051200.202104252130_all.deb`, then `sudo dpkg -i linux-headers-5.12.0-051200-generic_5.12.0-051200.202104252130_amd64.deb` says it needs libssl1.1 | 15:05 |
Bardon | Which I'm not sure how to install | 15:05 |
Bardon | lotuspsychj3: Am I doing this right? | 15:05 |
dreamon | is there a tut howto repair grub2 on efi system? im stuck grub-install "EFI variables connot be set on this system" | 15:06 |
Bardon | Ok I manually downloaded libssl1.1 form archive.ubuntu.com and manually installed it. I'm probably making a mess, I'll reboot and see if that old kernel is available | 15:09 |
=== meLon is now known as earthmeLon | ||
Bardon | Nice! I could install kernel 5.11, got it available under GRUB, it boots fine and powers off fine :D | 15:21 |
Bardon | 5.12.0 doesn't power off fine | 15:21 |
Bardon | The binary search continues! | 15:21 |
=== Lightaphyre` is now known as Lightaphyre | ||
=== zaki is now known as 068AAI6HI | ||
vortexx | I've upgraded a laptop being used as a mediastation from 22.04 to 24.04. I want to use the new (at least for me who was on 22.04) Remote Desktop option so I can log in remotely without first logging in on the system itself. However once enabled, the RDP system on port 3389 isn't listening on the IPv4 address, only on :::3389 | 15:44 |
vortexx | is there any way to fix this? (I'm watching something on it atm but I can reboot later) | 15:44 |
Bardon | My laptop hanged while installing kernel 5.11.16 (dpkg -i *deb). I could still move the mouse and windows, but couldn't start firefox, and starting a new bash prompt would take like a minute. This is the corresponding journalctl https://termbin.com/4dg8 | 15:46 |
vortexx | also this is a Vaio Pro 11 and the shimx64.efi placed at EFI\Microsoft\Boot\bootmgfw.efi stopped working after the upgrade, I put grubx64.efi in it's place and it's working) | 15:46 |
Bardon | Is it related to the power management issue or is my CPU dying? | 15:46 |
oerheks | mainline kernels are for testing, your test failed? | 15:48 |
lotuspsychj3 | Bardon: maybe better then here in the support channel, you could file a bug against 24.04 and kernel 6.8 then keep your bug informed of all your tests | 15:51 |
Bardon | lotuspsychj3: Ok | 15:52 |
lotuspsychj3 | Bardon: you know howto file a bug against the kernel? | 15:52 |
Bardon | I'm writing it all down. I just have a few more kernels to test | 15:52 |
Bardon | lotuspsychj3: No, I've never done that | 15:52 |
oerheks | why testing different kernels, such new hardware? | 15:52 |
lotuspsychj3 | Bardon: just boot back into 6.8, then type ubuntu-bug linux from your terminal | 15:53 |
lotuspsychj3 | oerheks: he has a shotdown freeze on 6.8 | 15:53 |
lotuspsychj3 | shutdown | 15:53 |
lotuspsychj3 | on an older vaio without new bios updates | 15:53 |
Bardon | oerheks: Sorry I was going to reply. I was testing the command lotuspsychj3 mentionned | 15:54 |
Bardon | lotuspsychj3: Ok, that command seems to work. Can I add comments to that report? I might be useful for the developers to know which kernel worked for me | 15:54 |
lotuspsychj3 | Bardon: yes, enter a title for your bug + description | 15:55 |
lotuspsychj3 | after that, you can add new comments on your bug, wich tests you did | 15:55 |
sixwheeledbeast | The issue is you need to pin down the regression or the devs may not find it. It's unlikely there are many of your device about. | 15:55 |
sixwheeledbeast | you've pinned it down to 5.11 was working. | 15:57 |
oerheks | 5.11 hangs, he wrote | 15:57 |
Bardon | 5.11.20 works, 5.12 doesn't. I'm going to test 5.11.22 (latest 5.11 version) on next reboot | 15:57 |
Bardon | oerheks: Did I write that? Hmm it must be a mistake | 15:58 |
sixwheeledbeast | I'm going from past experience of issues like this. Pinning down the exact version that broke helped get it patched so much quicker | 15:58 |
oerheks | "My laptop hanged while installing kernel 5.11.16 (dpkg -i *deb)." | 15:58 |
oerheks | not a shutdown issue, maybe just impatience, did your caps lock light work while pressing? | 15:59 |
Bardon | oerheks: Right, it hanged while running that command, but I was doing that under kernel 6.8 | 16:04 |
Bardon | I was installing 5.11.16 under kernel 6.8 | 16:04 |
Bardon | I did not check if my caps lock light worked when it hanged. I would suppose it worked since I could move my mouse and start new shells (but slowly, like a minute delay in starting shells) | 16:05 |
Bardon | The latest 5.11.* kernel listed in https://kernel.ubuntu.com/mainline/ is the 5.11.22, but when I click on it, this page https://kernel.ubuntu.com/mainline/v5.11.22/ lists it as "amd64/linux-headers-5.11.0-20". So is it 5.11.0-20 or 5.11.20? | 16:07 |
Bardon | Anyways, 5.12 doesn't work, and all the 5.11.* I tried worked | 16:07 |
Bardon | including the 5.11.22 / 5.11.0-20 | 16:08 |
Bardon | I see 60 occurences of "power management" in https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.12 | 16:09 |
Bardon | Power management is like the first line of this article that talks about kernel 5.12... https://9to5linux.com/linux-5-12-kernel-officially-released-this-is-whats-new | 16:10 |
Bardon | sixwheeledbeast: I ran ubuntu-bug linux, a window appeared asking me if I wanted to send or not send, then disappeared. How can I add a comment to my bug? | 16:19 |
Bardon | well I ran `sudo ubuntu-bug linux` because I did not want to type my password multiple times | 16:20 |
=== Poster` is now known as Poster | ||
oerheks | find your bugreport nr first | 16:27 |
oerheks | xdg-open https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie/whoopsie-id) | 16:27 |
oerheks | and adding a comment is only possible with a launchpad account | 16:27 |
oerheks | oh those are woopsie reports | 16:29 |
Bardon | I see only one line, dating from 2020 | 16:31 |
=== killdadon7008 is now known as killdadon700 | ||
v4l3nce | test | 16:36 |
=== ericus9 is now known as ericus | ||
Bardon | Aaaah, `ubuntu-bug linux` is supposed to open a web browser, but since lazy me did `sudo ubuntu-bug linux` (so I didn't have to type my password multiple times), the web browser didn't show up... | 16:41 |
Bardon | I can add comments now | 16:41 |
JanC | that you have to type your password over & over again is a bug IMNSHO :) | 16:45 |
ubuntustudio | lltwmulo | 17:12 |
lotuspsychj3 | Bardon: tnx to file bug #2078726 | 17:22 |
-ubottu:#ubuntu- Bug 2078726 in linux (Ubuntu) "VAIO freezes at poweroff" [Undecided, New] https://launchpad.net/bugs/2078726 | 17:22 | |
lotuspsychj3 | Bardon: in your description, you prob meant 24.04 instead of 20.04 | 17:23 |
Bardon | Ah, right | 17:26 |
Bardon | Edited | 17:26 |
Bardon | I hope I filed that bug report correctly | 17:27 |
lotuspsychj3 | Bardon: yes, the rest of your bug report looks good to me tnx | 17:28 |
Bardon | lotuspsychj3: Does it look like an upstream bug? If so, who would fix it: Ubuntu developers or Linux developers? | 17:29 |
Bardon | I mean, whose role would it be | 17:29 |
lotuspsychj3 | Bardon: well i think you kind of proved, its about kernel versions, so that targets the ubuntu devs | 17:30 |
lotuspsychj3 | let them seek out whats it about | 17:30 |
Bardon | I'm surprised it's not something the kernel devs would take care of, since it seem to come from the kernel | 17:31 |
Bardon | lotuspsychj3: I'd be interested in digging deeper into this. Would the next step be to git-bisect the kernel to find out which commit is the culprit? | 17:32 |
lotuspsychj3 | Bardon: we have an #ubuntu-kernel channel if you like, but the devs are mostly busy doing their own stuff too | 17:33 |
lotuspsychj3 | the report came into the right hands now Bardon | 17:33 |
Bardon | lotuspsychj3: I have some time and I think I would enjoy trying to fix that bug :) | 17:35 |
Bardon | I just need some guidance since I've never done that | 17:35 |
lotuspsychj3 | Bardon: im not really the expert, but you need to test the range of affected kernels, so the devs can start seeking the culprit in a narrow range | 17:37 |
iLICKaudio6 | hello | 17:38 |
lotuspsychj3 | Bardon: also, some bugs return on kernel version series too | 17:38 |
iLICKaudio6 | help my wifi drivers not working | 17:39 |
Bardon | lotuspsychj3: Did I not already test all the relevant kernels offered in https://kernel.ubuntu.com/mainline/? | 17:39 |
Bardon | What else can I do? Compile my own kernels to pinpoint the exact commit? | 17:40 |
Bardon | lotuspsychj3: What do you mean by "some bugs return on kernel version series"? I did not understand that message sorry | 17:41 |
lotuspsychj3 | Bardon: leave the task to the devs, until they ask you to test something | 17:43 |
Bardon | lotuspsychj3: How can I learn how to fix stuff myself then :( | 17:44 |
lotuspsychj3 | feel free to contribute to ubuntu Bardon | 17:44 |
lotuspsychj3 | !contribute | 17:44 |
ubottu | To contribute and help out with Ubuntu, see https://ubuntu.com/community/contribute and https://discourse.ubuntu.com/t/37746 | 17:44 |
iLICKaudio6 | how do i fix my broadcom wifii drivers? | 17:45 |
Guest87 | hi | 17:45 |
Guest87 | checking in | 17:45 |
Bardon | Could I ask in #ubuntu-kernel if someone would be interested in guiding me to resolve it myself or would it be inapropriate? | 17:45 |
toddc | iLICKaudio6: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx | 17:46 |
iLICKaudio6 | Thanks | 17:46 |
Bardon | lotuspsychj3: Right, but that bug that I reported affects me so it motivates me, it's a nice challenge! Other bugs are not as motivating to me | 17:46 |
lotuspsychj3 | Bardon: sure, the channel is free to join | 17:46 |
=== tomaw_ is now known as tomaw | ||
iLICKaudio6 | hey i tried it but its still not working even after a restart | 17:57 |
toddc | !details | iLICKaudio6 | 18:01 |
ubottu | iLICKaudio6: Please elaborate; your question or issue may not seem clear or detailed enough for people to help you. Please give more detailed information; for example, we might need errors, steps, relevant configuration files, Ubuntu version, and hardware information. Use a !pastebin to avoid flooding the channel. | 18:01 |
toddc | chipset driver used? | 18:01 |
iLICKaudio6 | i used b43 | 18:01 |
toddc | what chipset do you have? | 18:02 |
iLICKaudio6 | BCM4312 \ | 18:02 |
toddc | iLICKaudio6: try STA it should also work for that chipset see https://askubuntu.com/questions/11993/how-do-i-install-bcm4312-wireless-drivers | 18:05 |
sixwheeledbeast | you say "tried it" to a wiki page with multiple long winded options? | 18:06 |
sixwheeledbeast | I'd start with "firmware-b43-installer" | 18:06 |
toddc | let us know if we need to edit the docs | 18:06 |
iLICKaudio6 | im already using b43 drivers | 18:09 |
=== killdadon7008 is now known as killdadon | ||
arraybolt3 | Does anyone know off the top of their heads what might be misconfigured that would make it impossible to switch to a virtual terminal (using Ctrl+Alt+F[1|2|3|4|5|6])? | 18:26 |
arraybolt3 | Using Kubuntu 24.04 LTS. | 18:28 |
brenndo | !o | 18:31 |
diogeness | arraybolt3: try this: sudo chvt <n> | 18:33 |
diogeness | Replace <n> with the number of the TTY you want to switch to (e.g., 1 for TTY1, 2 for TTY2, etc.). | 18:33 |
diogeness | see if you get any errors. | 18:34 |
Hravnkel | Good evening. Anyone here who has any idea how to solve systemd-timesyncd.service delaying boot time by 4 minutes? | 18:46 |
Hravnkel | Link to journalctl with relevant part: https://thisoldcabin.net/journalctl_with_timesyncd.txt | 18:47 |
Hravnkel | I've tried to disable the service but without success, it seems like it just starts up again even though I've run systemctl disable systemd-timesyncd before reboot. | 18:49 |
Hravnkel | I've tried to browse the web about it and it seems like this problem is quite common, but so far I haven't been able to actually solve it. | 18:49 |
Hravnkel | Running a 2009 Macbook Pro with Lubuntu. Once the initial "threshold" is passed the boot process is snappy enough and the system works like a charm in every way except for taking almost 5 minutes to boot (with four of them just totally idling at an empty terminal window). | 18:51 |
Hravnkel | systemd-analyze time gives me: Startup finished in 3.878s (kernel) + 16.669s (userspace) = 20.548s | 18:53 |
arraybolt3 | diogeness, et al: figured it out. Cascade of ridiculous user errors on my end. | 18:54 |
vortexx | Well that's disappointing. Got Remote Desktop to work on 24.04 (needs a sufficiently varied password, no surprises there). I was hoping that the laptop plugged into the TV, once I was logged in, would mirror the RDP session to the TV, but it just shows the GDM login screen. So much for that, will have to resort to Desktop Sharing instead (which requires to log onto the machine physically) | 18:55 |
=== DNS is now known as BA_Dragon | ||
=== tractelimon is now known as Gusteru | ||
vortexx | mh https://www.linuxtechi.com/things-to-do-after-installing-ubuntu-24-04/ <-- the extensions manage portrayed in this article has the ability to find and install gnome extensions... But my one doesn't. Maybe stuck in 22.04 or older land? | 19:20 |
vortexx | ah, I was missing the extensions manager. That works | 19:25 |
morgan-u | interesting. I turned global username ON, then off again. | 19:37 |
morgan-u | WaddaUno. | 19:37 |
luna_3 | chrome restores well for which I am thankful. | 19:39 |
webchat45 | Parla italiano per favore | 20:17 |
gordonjcp | !it | webchat45 | 20:18 |
ubottu | webchat45: Vai su #ubuntu-it se vuoi parlare in italiano, in questo canale usiamo solo l'inglese. Grazie! (per entrare, scrivi «/join #ubuntu-it» senza virgolette) | 20:18 |
=== arraybolt3_ is now known as arraybolt3 | ||
=== tomaw_ is now known as tomaw | ||
=== Jason-KR_ is now known as Jason-KR | ||
=== eax__ is now known as eax_ | ||
=== ajhalili2006_ is now known as ajhalili2006 | ||
=== TastyWiener9589 is now known as TastyWiener958 | ||
=== gjolly_ is now known as gjolly | ||
=== cambam1005 is now known as cambam100 | ||
=== Fischer9 is now known as Fischer | ||
=== netravnen is now known as nethrafn | ||
=== phireant7 is now known as phireant | ||
=== cyrinux7 is now known as cyrinux | ||
=== NatSocSiD` is now known as NatSocSiD | ||
=== raghavgururajan_ is now known as raghavgururajan | ||
=== himcesjf_ is now known as himcesjf | ||
=== seanh_ is now known as seanh | ||
=== egtann_ is now known as egtann | ||
=== jacob-vlijm_ is now known as jacob-vlijm | ||
=== nirojan_ is now known as nirojan | ||
=== Sidewyz1 is now known as Sidewyz | ||
=== DeepThoughts9893 is now known as DeepThoughts989 | ||
=== rwp_ is now known as rwp | ||
=== dTal_ is now known as dTal | ||
=== KNERD_ is now known as KNERD | ||
arkanoid | latest 24.04 update disabled my wifi adapted. dmesg: https://termbin.com/l36v | 20:43 |
arkanoid | it has been working fine all the way from ubuntu 18.x | 20:43 |
tomreyn | arkanoid: what's the output of cat /proc/version | 20:50 |
arkanoid | tomreyn: nerverming, I just solved it by installing linux-firmware. I think it got accidentally removed by last cleanup pass with deborphan | 20:51 |
arkanoid | thanks for the feedback | 20:51 |
tomreyn | that would explain it | 20:51 |
tomreyn | you're welcome | 20:51 |
arkanoid | I think my strategies to keep my system clean are somehow broken. Would me interesting to know how to properly detect and remove unused parts of the system. Just like unused apps on recent platforms | 20:52 |
arkanoid | I have no grasp where the system space is logically consumed. I do ncdu on my user-level data, but system-wide, I just have a list of packages and dependencies, but no hints about where and if there an opportunity to cleanup | 20:54 |
tomreyn | i guess the general approach is to just not care about it, for the most part. after all, it's just a matter of a few gigabytes more or less consumed disk space. | 20:57 |
tomreyn | so maybe what is broken is the assumption that "i need to keep my system clean" | 20:58 |
tomreyn | ...at least when it comes to apt managed packages | 20:59 |
arkanoid | tomreyn: yeah I'm talkin about system-level(apt) stuff | 21:02 |
arkanoid | I have no idea about the % of packages that are installed but not used. I have a system running since ubuntu 16. I do cleanups, and system is in line with official apt repos, but I have no idea how many packages are there unused | 21:04 |
Diagon | On my last boot, during bootup the system started to do some update, then said it couldn't do ... something (went by too fast) and shut down. I was able to then boot after that. How do I find out what was going on? | 21:06 |
tomreyn | arkanoid: ubuntu 16.xx releases are unsupported. | 21:07 |
tomreyn | (I understand this doesn't answer your question, which also applies to newer releases, but please see my take on it above) | 21:08 |
tomreyn | Diagon: you can review your system logs, which can be done using the "Logs" application on gnome-shell, or using the journalctl command (see it's --help first) in a terminal. | 21:10 |
Diagon | I've tried journalctl -xe -b-1, but I'm not seeing anything ... hmmm. | 21:11 |
tomreyn | there may or may not be separate logs for just this system-updates-during-boot process (which i think is related to packagekit, but not sure) somewhere in /var/log/ | 21:11 |
Bashing-om | Diagon: ^ Maybe /var/log/apt/history.log ? | 21:14 |
Diagon | Empty. | 21:14 |
Diagon | What is this system-update-during-boot? I had never seen it until maybe ... 9 months ago or so? | 21:15 |
Bashing-om | Diagon: Yukkie - just checked and so is mine (empty) - guess journalctl now does that function ? | 21:16 |
Diagon | journalctl doesn't even have the word "update" in there. | 21:16 |
tomreyn | i'm unsure what controls this mechanism | 21:16 |
tomreyn | (updates during boot) | 21:16 |
=== daft_ is now known as daft | ||
Bashing-om | Diagon: cronjob: /etc/cron.daily/apt-compat >> 'random_sleep' on line 49 - It will run automatically a few minutes after reboot. | 21:19 |
tomreyn | i think this is the unattended-upgrade check running in the background once the system has booted | 21:21 |
tomreyn | i.e. not the systemd task installing 'staged' packages during boot. | 21:22 |
tomreyn | Diagon: which ubuntu release are you running? | 21:23 |
Diagon | 22.04 | 21:23 |
Diagon | Are those staged updates necessary? I always update regularly anyway and would rather not have the danger of a problem on boot. | 21:24 |
Diagon | Nothing in dpkg.log either ... | 21:28 |
tomreyn | packagekit-offline-update.service may be this mechanism | 21:29 |
Diagon | journalctl -u packagekit-offline-update.service | 21:33 |
Diagon | This is apparently related to ubuntu-pro | 21:34 |
Diagon | failed to update system: E: http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 ubuntu-pro-client-l10n amd64 33.2~22.04 is not (yet) available (Could not resolve 'us.archive.ubuntu.com') | 21:34 |
Diagon | That may be related to my VPN not allowing network connections until it's up (?) | 21:34 |
tomreyn | failing to resolve us.archive.ubuntu.com should be unrelated to ubuntu pro | 21:35 |
Diagon | What I'm saying is that it appears that what's being updated is related to something ubuntu-pro is providing (?) | 21:36 |
Diagon | I'm rather shocked that systemd wants to *download* something before my system is up. This seems like a security disaster. | 21:38 |
tomreyn | https://raw.githubusercontent.com/PackageKit/PackageKit/main/docs/offline-updates.txt | 21:38 |
rbox | Diagon: which part of that is a problem | 21:39 |
tomreyn | if you have a custom vpn client setup which does not integrate well with existing systemd unit dependencies, this may be why something is trying to access the internet before your vpn client is fully setup. | 21:39 |
Diagon | As I say, I've got an always-on VPN. If it wants to connect before that's up, then that's an issue. | 21:40 |
Diagon | tomreyn / ok, so it's not "integrating well." | 21:41 |
Diagon | Is there some way to get rid of this? I update almost daily anyway. | 21:41 |
tomreyn | of the not well integrated vpn client? i would suggest uninstalling it based on what the software developers/providers recommend | 21:42 |
tomreyn | we only support ubuntu here, i'm afraid. | 21:42 |
Diagon | No, I mean get rid of prior-to-boot updates. | 21:42 |
Diagon | That link you gave says, "This functionality adds the offline updates feature to PackageKit" | 21:42 |
Diagon | But clearly this is not "offline" | 21:43 |
tomreyn | what is "this"? | 21:43 |
tomreyn | ...that's "clearly not offline" | 21:44 |
Diagon | "this" is the update that my system tried to do, which included an attempt to connect to the network and download an update. | 21:45 |
tomreyn | i agree *this* was clearly not assuming to be offline | 21:45 |
tomreyn | but i don't think that's the same process you saw while booting the system, trying to install (staged) updates | 21:46 |
Diagon | Here's the output of journalctl -u packagekit-offline-update.service | 21:49 |
Diagon | https://termbin.com/lier | 21:49 |
tomreyn | hmm, yes, that looks like it actually does online updates, i agree | 21:50 |
tomreyn | or tries to, and fails on your system | 21:51 |
tomreyn | hmm, this log actually seems to have been written while the system was preparing to shutdown, though | 21:52 |
tomreyn | ah, no, ignore this, i forgot that it reboots after it has tried to install updates | 21:53 |
Diagon | Yes. | 21:54 |
tomreyn | /var/lib/PackageKit/transactions.db seems to be an sqlite 3 database which logs past packagekit transactions | 22:02 |
pinkergloop | Hey | 23:22 |
pinkergloop | So I talked about this a long time ago, but had to get off early and got too busy to ask again for a while | 23:22 |
pinkergloop | But I dual boot Ubuntu and Windows 11 | 23:23 |
pinkergloop | And sometimes I like to access my Windows partition from Ubuntu just to put files in and out while I'm there | 23:23 |
Diagon | tomreyn : "When offline updates are disabled by turning off packagekit-offline-update.service in systemd it is still possible for offline updates to be triggered, causing boot to hang at system-update.target" | 23:23 |
Diagon | https://bugzilla.redhat.com/show_bug.cgi?id=988235 | 23:23 |
-ubottu:#ubuntu- bugzilla.redhat.com bug 988235 in Fedora "boot hangs at system-update.target when packagekit-offline-update.service is disabled" [Medium, Closed: Eol] | 23:23 | |
pinkergloop | But lately, whenever I try to mount the partition via the GUI file manager | 23:24 |
pinkergloop | I get "An error occurred while accessing 'Partition Name', the system responded: The requested operation has failed. Error mounting /dev/sda2 at /media/pinkergloop/Partition Name: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error | 23:25 |
pinkergloop | "* | 23:25 |
Diagon | tomreyn , bashing-om : https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2078751 | 23:44 |
-ubottu:#ubuntu- Launchpad bug 2078751 in packagekit (Ubuntu) "packagekit-offline-update.service is not offline! It wants a network, otherwise fails." [Undecided, New] | 23:44 | |
Bashing-om | Diagon: Good deal ^ :D | 23:47 |
serval | the option to disable the touchpad isnt working. help | 23:48 |
pinkergloop | nvm i got it it seems like | 23:51 |
pinkergloop | i just booted to windows, turned off fast startup (not certain this actually did anything tho) and ran chkdsk | 23:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!