[00:00] sal-mon: Can you still get into the BIOS settings? [00:00] yes I can [00:00] (also thank you for helping me) [00:00] Also, it would be interesting to know if other alternative operating systems (say, FreeDOS and NetBSD) are able to boot or not. [00:01] If FreeDOS can boot, but NetBSD and Linux both fail, that would lead me to believe that maybe the CPU blew a transistor or some such and killed the 64-bit capabilities or something like that. [00:01] I hope it doesn't come to that, I'm downloading a copy of freeDOS right now [00:01] You might try opening the thing up and seeing if it's clogged up with dust - maybe there's a short on the motherboard causing the issue. [00:02] If it is, carefully dusting it out might not be a bad idea (though discharge yourself on some grounded metal object before starting so that you don't kill the system with static - my best friend once killed a computer with static!). [00:02] It is dusty, it's acting as a server under the stairs, but wouldn't it just shut down? [00:02] hm, did maybe a surge occur? kinda reminds me of mine I had roughly 12 years ago [00:02] it's plugged into a UPS [00:02] Also I wonder what MemTest86 does? [00:03] memtest was stuck on the first test for hours (around 12), that's when I swapped out the RAM [00:03] Was it still sticking even after the RAM swap? [00:04] I haven't tried that yet, I'll boot ubuntu off a usb then try memtest again [00:04] (Fatal exception in interrupt, attempted to kill init, MemTest problems... this is all reeking of hardware failure to me.) [00:05] sal-mon: don't use the "memtester" software if you're referring to that. use the bootable memtest86 or memtest86+ [00:06] https://www.memtest86.com/ [00:08] tomreyn: I'm using the memtest that's included in GRUB [00:08] that's https://www.memtest.org/ then, that's fine if you have older hardware [00:09] sal-mon: Do you have more than 4 GB RAM? [00:09] I have 8gb of ram [00:09] sal-mon: I'd try the site I linked to then, Memtest86+ just gets stuck at the 4 GB RAM barrier in my testing. [00:09] btw https://launchpad.net/ubuntu/+source/pcmemtest packaged version of https://github.com/martinwhitaker/pcmemtest :) [00:10] don't run a 32-bit version of it? ;P [00:10] (I think they're still using some horribly ancient version of MemTest86+ in Ubuntu. Might be something to look into fixing.) [00:10] unfortunately only for newer releases, but because it just drops an uefi thingy on disk, it installed on an old xenial system of mine with no effort :D [00:11] oh god, which version of memtest do I install then? the v9.5 beta? [00:11] I really hope that it's something silly, like too much dust on the mobo [00:11] sal-mon: I'd go with the V4 since it sounds like you have a BIOS system. [00:12] sal-mon: Here you go: https://www.memtest86.com/downloads/memtest86-4.3.7-usb.tar.gz [00:13] thank you, I'll boot it now and leave it for a while [00:14] sal-mon: The archive extracts, then it has a .img file inside that you flash to a USB and boot from. [00:14] can I use ventoy? [00:14] sal-mon: Probably? I have no clue, but it's worth a shot. [00:15] If ventoy doesn't work and you don't feel like fighting with dd, you can probably use balenaEtcher. [00:15] yeah google says ventoy does support img files, thanks again! [00:15] sal-mon: ventoy.net says it works [00:15] 👍️ [00:16] (If you do end up having to use Etcher, make sure to use it on an empty drive or a drive with no important data, since using Etcher to flash a drive will render the rest of the data on the drive inaccessible!) === ledeni_ is now known as ledeni [00:20] on the other hand you'd get free read-backverification of written data, which might be a good idea if you have to write the usb on *this* computer [00:20] sal-mon: Also if you do dust out your system, use some non-static-creating material too so you don't fry anything out. [00:20] (the better option is to download and write the usb on another computer which you know works well) [00:21] I'm flashing freeDOS on my other linux pc right now, is a feather good for anti static dusting? [00:22] sal-mon: I've used chicken feathers successfully in the past. (Not a joke.) [00:22] (And now you all probably can tell that I live on what used to be a farm.) [00:22] (I don't know what type mine is, I appreciate you taking this seriously) [00:28] alrighty, balena says freeDOS doesn't have a bootable partition, sure enough, it said something about not finding a UEFI image, so I'm testing with memtest86 (also flashed with balena) and it's actually testing now! y'all awesome, I'll be back when It's done with a few passes [00:29] sal-mon: \o/ Nice! [00:31] (Also I forgot FreeDOS probably won't work with Etcher, for it you probably will have an easier time using ventoy.) [00:32] Oh man, FreeDOS might not even work with ventoy. Nevermind, lets' [00:32] s just stick with memtest86. [00:51] oh and if memtest doesn't turn up with any errors, what should I do, other than dusting my pc off (I'll disassemble it completely and dust off everything) [00:54] i had a pc go wonky from dust [00:54] dusted it and worked fine [00:55] used air compressor [00:55] this gives me hope, I'll do that now, memtest says there are no errors thankfullyu === dewwii_ is now known as deww === M4he is now known as mahe [01:43] aaaaaaaaaaaaa [01:43] so probably like, once a month or so, I have to install something that's just not in the main repos [01:44] and it takes ages to figure out what's going on and I usually end up giving up or compiling from source or something [01:44] like right now I'm trying to install a more recent version of llvm so I can have c++17 features and everything is pain [01:45] wow you'd think after all these months you'd be getting better at it [01:45] Sounds rough. [01:46] can someone explain what's going on with this whole thing or point me toward a thing I can read that untangles it because I want to try to just not have this happen again [01:46] if you want software that's not packaged yet, that's just kind of the way it goes [01:47] maybe someone could explain, but you'd hav eto provide more details as to what you've done, maybe share some output, etc. [01:47] jhutchins: Just got back from 2nd job. Same error when trying to connect with the debian client. [01:51] Why does, 'echo $XDG_CURRENT_DESKTOP' return nothing for me? [01:51] cuz nothing set it [01:51] obviously :) [01:51] maybe lxde or xfce or something? [01:52] the desktops that always set it are ones that support wayland [01:52] and they'll set it to wayland or x11 [01:52] but some of the other desktops dont set it at all [01:52] i've also seen it say tty sometimes too [01:54] So that kinda means you can trust it when it says wayland, but when it says nothing, you can't be 100% sure but its probably x11 or tty. [01:54] errr trust it when it says something [01:54] but when it says nothing, you can guess its likely x11 or tty, but not surely [01:56] @somniad if I were you, I'd setup a VM for development that uses another distro if you need LLVM 15. [01:56] enigma9o7[m]: btw somniad left nine minutes ago [01:56] Then you can run something less stable than ubuntu, but not worry about it too much if something goes wrong, other than your project which is likely just data you could get even if the OS broke or something. [01:57] oops [02:47] umm, I just cleaned my pc completely and booted ubuntu on a usb drive, it's currently stuck on: [drm] Initialised amdgpu 3.42.0 20150101 for 0000:26:00.0 on minor 0 [02:47] so I guess that's better than kernel panicking [02:48] heh :/ [02:51] sal-mon: What did you have on it before? [02:52] sal-mon: What image is on the USB? [02:53] just a regular ubuntu 22.04 install, I had this issue where it would just kernel panic, the kind people here recommended I clean the pc, so I did [02:53] but now it's stuck on this issue [02:53] oh the cursor stopped blinking [02:54] so, what's the best way to know what desktop is running? [02:54] sal-mon: Pretty clearly something not quite right with the amd driver. [02:54] out of the frying pan and into the fire [02:54] how would I start troubleshooting this? [02:54] johnfg: What did you install? Did you see a menu when you logged in? [02:55] !install [02:55] Ubuntu can be installed in lots of ways. Please see https://help.ubuntu.com/community/Installation for documentation. Problems during install? See https://wiki.ubuntu.com/CommonProblemsInstall - See also !automate [02:55] yes, ubuntu 22.04 on a live USB, I saw the regular GNU GRUB menu [02:55] sal-mon: That question was for johnfg, but good. [02:56] oh sorry, it's 5am right now [02:57] Yeah, I've got to knock off here as well. There are usually some pretty helpful people during US business hours. [03:32] hello new problem has occurred after using an updated media tool to install ubuntu I was finnally able to install sort of the only thing that comes up is an odd message from GRU GRUB [03:34] (what's the message) === Guest2328 is now known as Polo [03:35] Minimal Bash-Like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. [03:36] did you click any buttons on the keyboard? [03:36] accidentally perhaps? [03:37] no and pressing shift or esc to try and get to the other GRUB menu during bootup did nothing [03:44] i just rebooted the system with no input devices plugged in to verify still having the same problem === chrono_ is now known as chrono [03:52] hello [04:03] potter [04:04] ? [04:29] jj === runbgp4 is now known as runbgp === doc|home is now known as doc [05:21] morning 20.04.5 downloaded and updated [05:23] Nice work [06:07] Hi! Is that tzdata kept back a known behavior in 22.04.1 LTS? [06:14] webchat16: Probably phased updates once again. [06:15] webchat16: Yep, looks like the packages has been 10% phased. Just wait, it will install on your system eventually. (It's held back on mine too.) [06:16] Or run `sudo apt install tzdata` to install it now without waiting for the phased updates === sonOfRa_ is now known as sonOfRa === martums4642 is now known as martums === kdas_ is now known as kushal === ajfriesen6 is now known as ajfriesen [07:15] Hey there, can someone tell me why I am getting this error. And How to solve it? [07:15] W: https://packages.microsoft.com/ubuntu/18.04/mssql-server-2019/dists/bionic/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. [07:16] jack: https://askubuntu.com/questions/1398344/apt-key-deprecation-warning-when-updating-system === pah is now known as pa [07:32] hi [07:32] downeast: No any solution gien in that site working on my laptop. If you have other solution too . please do send it. [07:38] jack: update your key [07:39] Ikonia: How to update the key. [07:39] jack: read the post Downeast gave you, and read the deprecation section in apt-keys as the error said [07:41] i get the impression the ubuntu:bionic docker hub image was built from proposed instead of updates [07:41] because it has libsystemd0 237-3ubuntu10.54 [07:42] can anybody confirm? i cannot install libsystemd-dev because of it [07:42] confirm what sorry ? [07:43] that the docker hub image was built from proposed instead of updates [07:43] mail the maintainer to get a factual response [07:43] only someone with access to the compose file will know what it was built from [07:44] oh, they're not public? [07:44] .53 is the latest in the updates repo for bionic, so it certainly doesn't seem to be from core repo [07:44] Habbie: if they are public, you'll have the same access as the rest of us [07:44] so you can confirm [07:44] yes - and if i s/updates/proposed/ in sources.list i get 54 [07:45] seems a logical assumption [07:45] ta [07:45] will look for the sources [07:47] ok, the docker images are built from https://partner-images.canonical.com/oci/bionic/ [07:47] where 0815 had .53 and 0829 indeed has .54 [07:47] naughty and sloppy [07:47] so the docker maintainer is not to blame - next step, https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+ref/ubuntu/master [07:47] (not that i care about blame) [07:48] hello, semi-OT but on a fresh installed 22 I see an issue with glibc but I am not sure what it actually is [07:48] sorry, don't see the releveance of that launchpad link ? [07:48] I get this python wheel package for linux https://files.pythonhosted.org/packages/4c/a1/0562e98d39347530af4b03327bf66dde4a51f2420b64b8e6bfde005d6e70/PySide6_Essentials-6.3.1-cp36-abi3-manylinux_2_28_x86_64.whl [07:49] ikonia, that's what builds the rootfs tarballs that the docker image is then also generated from [07:49] Habbie: so the livecd is shipping a root FS with random out of band packages ? [07:49] this is a zip file (mind you 70 MB), I unzip it and run ldd on PySide6/QtQml.abi3.so and ldd chokes on it, returning 2 without any output [07:49] ikonia, it sure looks that way [07:50] Habbie: even naughtier and sloppier [07:50] well, mistakes happen, i'm not here to blame or judge, just to find a solution :) [07:50] I'd certainly log a bug against the docker package and let the maintainer work it out with upstream [07:51] I'll have a look at the running livecd as I'm interested now [07:51] ikonia, oh very good, that saves me time :) [07:57] ohh [07:57] ikonia, http://cloud-images.ubuntu.com/bionic/ [07:57] ikonia, there's a newer 0901 here that fixes it [07:58] ahhh a newer image [07:58] I'm still curious if it's in the livecd [07:59] highly depends on what build you grab i think [07:59] just going to grab the latest, as that's what people should be using === nomad1 is now known as nomad_fr [07:59] fixing an obsolete problem doesn't make sense to me [08:00] i agree [08:00] i've asked in #ubuntu-cloud if they can do a rebuild of the docker image with the 0901 version, as that should fix all [08:01] ahhh so there is a disjoint there too, the image has been updated, but the cloud images are still using the old one [08:02] http://cloud-images.ubuntu.com/bionic/ has 0901; https://partner-images.canonical.com/oci/bionic/ does not; and presumably docker images are built from the latter [08:07] somebody in #ubuntu-cloud is going to have a look [08:09] well that feels like a win [08:09] yep [08:09] thank you for thinking with me :) === EriC^^_ is now known as EriC^^ [09:17] when trying to run sudo apt-get upgrade it says a few packages such as headers were kept back, why doesn't it upgrade them? [09:18] towser: can you pastebin your apt output please [09:18] volunteers will take a look for you [09:23] towser, most likely because these are phased updates ... apt policy should tell you about it ... if they are phased, just wait or do a forced update by spcifying all package names in your apt update call [09:24] this is the output I get https://justpaste.it/8lznw [09:27] 3 packages are not upgraded [09:35] Welp. Once again I have gotten myself in a bit of trouble. My system is running Ubuntu Desktop 22.04. I downloaded an Ubuntu Kinetic ISO, flashed it to a USB drive, then installed it directly onto a second USB drive to do a test for a bug. After fighting with my system for quite a while, I managed to get the new Kinetic install to boot and finished my testing... and then discovered that I had managed to scramble the bootloader on my main [09:35] drive. On my main system. :( I got given a GRUB rescue prompt. Thankfully I'm decent at maneuvering this particular screen and managed to get my main system to boot, but I'm pretty sure I need to reinstall the bootloader at this point. Anyone know right off the top of their heads the right command? My system uses UEFI, Secure Boot is disabled, and I'm not dual-booting. [09:36] greetings, my servers are accessing cloudfront service. I didn't configure this and I want to stop it. How can stop cloudfront access [09:37] iomari891: CloudFront appears to be a CDN related to Amazon Web Services. Perhaps an application or site you have installed is accessing it automatically? [09:38] arraybolt3[m]: EriC^ is out uefi wizard [09:38] *our [09:38] iomari891: At any rate, the first step would be to identify which process is accessing CloudFront. That should get you on the right path. I don't know off the top of my head how to do this, but someone else here might. [09:39] lotuspsychje: Thanks! [09:39] (Shoulda known better than to do a QA test on my main laptop, but I figured, hey, I can recover even if it nukes my drive, what could go wrong? 🤦‍♂️) [09:39] *a bare-metal QA test [09:48] how do I update the packages that wern't upgraded? [09:49] towser: did you see the advice ogra gave you? [09:50] towser: Did you check to see if they were still phasing? If they are, you shouldn't install them yourself (I mean you can but it's not necessary and could be a bad idea in rare instancces). [09:51] Try "apt-cache policy ", that will tell if if it's phasing or not. [09:51] If somewhere you see something that looks like "(phased 10%)" in the output, then it's phasing and you can just leave it be. [09:54] nope not phasing [09:54] towser: Are you using "sudo apt upgrade" to upgrade? If so, try "sudo apt full-upgrade" instead. [09:56] that upgrades the ones it didn't upgrade before, thank you [09:56] towser: No problem, glad it worked! [10:10] arraybolt3[m]: thanks [10:11] (re: the boot issue I was facing - solution ended up being "sudo grub-install" in a terminal. Everything's back to normal now.) [10:21] I have a huge list of ip addresses in xx.xx.xx.xx/xx format. I noticed some of the lines overlap others meaning that there would be duplicate ip addresses contained on the subnet. Is there any tool that can flag any line that conflict with another line? meaning any line that has an overlap in the ips. Hope this makes sense. [10:23] iomari891: Are these basically just duplicate lines in a file? [10:24] iomari891: If so, a Bash script should do the trick. [10:24] there's aggregate, grepcidr, various ruby and python modules for dealing with networks [10:26] iomari891: you could do "sort -u /path/to/file" it should remove the duplicate lines [10:26] EriC^^: I think they need to know what lines occur more than once, not just remove the duplicates. [10:26] Like, find them, leave them, highlight them. [10:26] oh [10:27] iomari891: use sort /path/to/file | uniq -c [10:27] This just seems like a job for grep... [10:27] it'll give you a count of them [10:28] EriC^^: And once again, someone has knocked my advanced shell scripting idea out of the park with a dirt simple one-liner. I may need to brush up on my Bash skills... === DSyndrome is now known as Death_Syn [11:21] hi all [11:22] after renaming VG and LV on which /-fs lives, and doing `update-initramfs -u -k all` it complains (NO encrypted fs present!) "cryptsetup: ERROR: couldn't resolve device such and such" ... trouble ahead if i reboot? or fine? [11:22] also, update-grub does not want to run: "error: failed to get canonical path" ... how can i let it know about the new names? [11:23] did you update the /etc/crypttab too? [11:23] esv: no, because it's empty. like i said, that machine doesn't have any encrypted partitions / drives. [11:23] ooh , [11:23] i see [11:24] hence my question if that error can be ignored [11:24] did you reinstall the grub? [11:24] tried to [11:24] but ... "failed to get canonical path" [11:26] did you update /etc/default/grub too? [11:26] what happens if you run grub-install? [11:26] hmm [11:27] "installation finished. no error reported" [11:27] what do you have in GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? [11:28] empty [11:28] as in, ="" [11:28] k [11:28] hmm, adding [11:28] GRUB_DEVICE=/dev/ubuntu-vg/ubuntu-lv [11:28] seems to have helped some [11:29] esv: full output is now https://gist.github.com/sixtyfive/8fd5c225f29f6512ed54617f44e01225 [11:29] (system/root was the VG/LV's previous names ... now they're ubuntu-vg/ubuntu-lv) [11:30] so i think grub config / install are fine [11:31] still not trusting the initrd to be fine === IshSookun1 is now known as IshSookun [11:32] https://gist.github.com/sixtyfive/7b105a74fc57cf8669a4566025198642 [11:32] i mean, the whole thing might resolve itself with a reboot. or the reboot might not work out :P [11:33] great way to learn :) [11:34] only that if it fails i will have to pack up a laptop and a USB/Ethernet adapter, get up on my bicycle, head to the other side of town, plug in to the iDRAC, yadda yadda [11:34] but yeah it's unknowable at this point so i'll just try [11:34] don't have a live usb stick? [11:35] well, yeah, would need to pack that up, too ... but got no keys to the room and got no keys to the rack [11:35] so better hope someone with keys is there, too [11:36] ok i hit enter on the "reboot" ... what does it matter, on monday someone _will_ be there with keys and it's not being used as a production machine atm [11:38] i recovered mine with a live usb stick, well, with help too. [11:40] was about to ask what do you have for: "set root=" in /boot/grub/grub.cfg [11:45] Imagemagick in ubuntu is broken, it will refuse to write any pdf [11:45] error "convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/421." [11:46] solution that works confirmed: https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion [11:51] Hello #ubuntu! https://askubuntu.com/questions/1427122/cant-find-out-if-ubuntu-server-is-using-all-the-disk-space Any help would be greatly appreciatted! [11:53] Did Canonical make the decision to drop libssl 1.x last-minute before the release of 22.04, or were there months or more before they made that call? Does anyone know? [11:56] esv: recovering with a USB stick is always ok. what i often find difficult is to predict everything that _might_ happen and see to it that it doesn't [11:57] ah! came back up! tadaaa! [11:57] \o/ [12:00] Hi all [12:00] hi 75 [12:00] Does Ubuntu Desktop 22.04 supports UEFI SecureBoot with Full Disk Encryption ? [12:00] it supports FDE, i don't know about SB, sorry === yano1 is now known as yano [12:01] rapha I noticed that Ubuntu Core supports UEFI SecureBoot, but for some reason I can't say the same for Ubuntu Desktop [12:01] I believe it does, there is always a risky way to verify [12:02] * rapha doesnt even know if any of his hardware supports UEFI SecureBoot [12:02] @esv I'd expect it to be published... it is a good feature [12:02] I believe I am using it, is that the bitlocker thing? [12:02] Kind of [12:03] I know that Bitlocker supports it, but it isn't necessarily activated, I think you should verify that [12:05] I am on 22.04 and my company requires bitlocker enabled to access company resources (which I am using right now) [12:05] not sure if it is desktop or server version thou. [12:07] joseraeiro, i guess it looks like you have a "/dev/sda: 500 GiB, 536870912000 bytes" but your filesystem root "/" is on "dev/mapper/ubuntu--vg-ubuntu--lv: 100 GiB, 107374182400 bytes" [12:07] hence you seem to only use 20% of the available disk for your filesystem [12:08] the ouptut of vgs would come handy [12:08] ^^ joseraeiro [12:27] Hi all [12:32] hey [12:56] lotuspsychje: btw, if you remember my issue with the crashes which happen when the screen turns off/sleep? well, tried to get more logs, which just don't exist. I recovered some logs, and nothing shows up (there are no logs just before I hit the sleep button for example) and there is no crash log file :( [12:57] oh and the oem kernel works the same (intel panel self refresh even worse) [13:00] you may need to increase verbosity of whatever crashes [13:03] tomreyn: at least something got fixed, as the caps lock led doesn't blink anymore (but not sure if that means the kernel _doesn't_ crash anymore. but at the same time nothing gets the laptop out of that state [13:03] tomreyn: idk does it help? even when the logs stop at 1-2 mins before the crash? [13:05] if "the logs stop" because the logging daemon stops at that point, then increasing verbosity won't help. if "the logs stop" at this time because no service is trying to log anything, then it may help. [13:05] did you set up kernel debugging? [13:05] did you attach a serial console or a netconsole? [13:06] https://wiki.ubuntu.com/Kernel/Debugging https://wiki.ubuntu.com/Kernel/KernelDebuggingTricks [13:07] if the wiki would load for me ;) 504 [13:10] tomreyn: btw, connecting a serial console is not possible for me, as I only ever have this laptop on me (and traveling on top of that) [13:15] https://web.archive.org/web/20220707143403/https://wiki.ubuntu.com/Kernel/Debugging [13:15] you can probably find cached copies of these pages on we.archive.org [13:15] ah geirha beat me to it [13:18] nice thanks. didn't think about it [13:19] murmel: you can use a mobile phone (at least android devices, not sure about ios) as a terminal connecting to a serial console provided by your laptop, given you have a suitable cable (with a suitable chipset, such as FTDI FT232, Prolific PL2303) === MrA is now known as Ders [13:31] murmel: so a regular kernel + oem kernel act the same on your issue, maybe its an acpi related bug? [13:35] good point - if it's a bios bug this would also explain why you're not seeing anything logged about it on linux's end (other than *maybe* during boot when it parses acpi tables) [13:36] murmel: could you pastebin your current dmesg again, so maybe we can focus on acpi this time? [13:40] Hello, last night my pc was stuck on a variety of errors, (stdin: not a typewriter, kernel panic - not syncing: fatal exception in interrupt, kernel panic - not syncing: attempted to kill init, [CR2: 000000000000000000000008 CR3: 000000000000000000000000000008]) [13:40] and uhh, I'm not sure what to do exactly [13:41] I've cleaned out my pc, ran memtest, but I'm sill not sure what's the issue, I think it's one thing that causes these [13:41] because it happens on a live usb too [13:44] !details | sal-mon elaborate a bit more please [13:44] sal-mon elaborate a bit more please: 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. [13:47] tomreyn: lotuspsychje: awesome will look into it as I have an android device. and I really hope that it's not acpi :/ as the device is already 4 years old, I won't assume that dell would fix it. brb 1hr for some food [13:51] sal-mon: ubuntu release, kernel version and dmesg in a pastebin would be useful for the volunteers to take a deeper look into your issue [13:52] esv, sudo vgs -a [13:52] [sudo] password for next-it: [13:52] VG #PV #LV #SN Attr VSize VFree [13:52] ubuntu-vg 1 1 0 wz--n- <498.00g <398.00g [13:52] alright, a few days ago I shut down my pc (Ryzen 3 3200G, 8gb of ram, Ubuntu 22.04) completely normally, and the next morning it gave me this error: [End kernel panic: not syncing - fatal exception in interrupt] and booting from a live usb (ubuntu 22.04, flashed with balenaEtcher) gave me the same error, so after some advice on here, I ran memtest [13:52] (RAM's fine) and cleaned out my pc completely, however, now it returns this: [End kernel panic: not syncing - attempted to kill init!]. I think it's one error or something went wrong that it's causing a bunch of errors. [13:52] (I can't boot into an OS to check anything though) [13:53] de-facto, and how could I use the remaining disk space and mount it in /? [13:53] murmel: you won't strictly need the serial console if the system survives whatever happens there. just an ssh shell and increased kernel loglevel on that tty [13:53] sal-mon: did you try to enter grub==>recoverymode yet? [13:54] !paste | joseraeiro [13:54] joseraeiro: For posting multi-line texts into the channel, please use https://dpaste.com | To post !screenshots use https://imgur.com | !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [13:55] lotuspsychje: the recovery options for ubuntu? yes, they also returned similar errors, unless there's another rescue mode? (also thank you for helping me) [13:55] sal-mon: try again entering a recoverymode and enable networking + fallback to a rootshell (if you get that far) [13:56] sal-mon: also test older kernels, in case its an issue about the recent kernel update [14:12] sal-mon: you could try connecting the disk to a different computer and accessing the logs from there. it would be good to see a dmesg (run: dmsg | nc termbin.com 9999) of the system booting. [14:12] this may help provide you with a better guess on which hardware component is broken [14:12] lotuspsychje: sorry for the delay, but all the recovery options for ubuntu give the same error: [End kernel panic: not syncing - fatal exception in interrupt] [14:13] tomreyn: it's an internal disk, and I don't have a SATA to USB cable [14:13] and not another computer with a sata controller, i assume? [14:14] unfortunately nope [14:14] sal-mon: did you change anything on your computer lately? [14:14] well, those cables are cheap. [14:15] I did upgrade to 22.04 around two weeks ago [14:16] sal-mon: do you get the same kernel panic on a 20.04 liveusb too? [14:16] I'm downloading the ISO right now, I'll test it soon, thanks [14:17] allright cross fingers its jammy related [14:30] lotuspsychje: after a bit of kernel parameter modifying I got the furthest I ever did! but now outputs stdin: not a typewriter and the cursor's frozen [14:33] hihi [14:34] i am thinking of buying a touchscreen pc/monitor. does ubuntu have drivers for using a touchscreen? or is there some other version suitable for a touchscreen-only pc? [14:34] sal-mon: this can be a red herring, but worth a try: sal-mon: remove any usb devices you don't need, especially usb hubs. if you have a spare keyboard, replace your keyboard, too. if not, make sure its wire isn't twitched. see what happens if you only connect the keyboard after boot [14:35] theos: Ubuntu should support touchscreens out of the box. [14:35] tomreyn: I only have the usb drive, keyboard and HDMI cable plugged into the pc [14:35] I guess it depends on the exact touchscreen hardware, but the one I used to use worked just fine, and another person with a touchscreen also had his working. [14:35] I'll try unplugging the keyboard really fast lol [14:36] arraybolt3[m] thats good to know. thanks a lot. are you using the vga port or hdmi? [14:38] theos: I've used both ports. I have a monitor with a touchscreen that connected over a USB cable, so the touchscreen signal and the video signal were transmitted separately AFAICT. (Sadly my cat broke the screen, but while it worked, it worked!) [14:39] arraybolt3[m], so a touchscreen worked on VGA? Did it also have to have a USB connection? [14:40] rob0: Yep, worked on VGA with a USB connection. It also required the USB connection when using HDMI. [14:40] arraybolt3[m] i see. so vga for video and usb for touch signal. hah I have to keep it away from my cats then. thanks. [14:40] oh. The only one I've had is a built-in laptop monitor, and I never bothered to look it up in lsusb. [14:40] theos: 👍️ Glad to help! And yeah, careful of cats that knock stuff down. The screen works but the glass is broken on mine and the touch no longer functions (or at least it didn't last I tried). [14:41] Mine is LCD, not glass. [14:41] :D [14:41] LCD's still exist? I thought it was all LEDs these days [14:42] wez, idk tbh [14:42] LED is the backlight. LCD is the screen. [14:42] all I know for sure is, not glass [14:43] theos: Unless you use an OLED screen. [14:43] or an e-ink display [14:44] arraybolt3[m] those are amazing! thinking of buying an OLED phone. [14:44] theos: You can have LED as the screen too [14:44] not just the backlight [14:48] tomreyn have been waiting for an e-ink/e-paper ubuntu phone which can fold like newspaper and fit inside the pocket, for a decade or so. i am sure it will be available in the next 100 years :D [14:48] wez yes you are right [14:49] theos: I am yes [14:49] grub keeps adding entries in the ubuntu options list on jammy jellyfish [14:49] i have several of the same entries in the grub boot list [14:52] everytime i update the kernel more entries get added in the ubuntu options list it just gets longer and longer with same entries [14:53] laguna, do you regularly run apt autoremove or apt autopurge ? [14:53] I am running LUbuntu. I just started getting the blue splash screen, pause for about a minute, then black, no desktop. How do I repair this? [14:53] ioria yes i ran apt autoremove to remove the old kernel after the new installs [14:54] laguna, and you still have several entriesin the grub menu ? [14:54] is there a part that can fail other than RAM and not show up in POST? because I feel most of my issues have an underlying problem' [14:54] ioria yes and they are duplicates of the new kernel [14:54] laguna, please, run dpkg -l | grep linux-image | nc termbin.com 9999 [14:54] ok [14:56] ioria i ran it but i don't see anything in the terminal [14:56] lotuspsychje: hm, can't see anything. (but also not _that_ good at reading acpi stuff) https://termbin.com/pcwy [14:56] eh maybe tomreyn ^ xD [14:56] laguna, the cmd is correct, try again [14:57] ioria ok it comes back with this link https://termbin.com/c1ep [14:57] ioria i ran it without sudo [14:57] sure [14:58] Did anyone reply to my question about libssl version in Ubuntu 22.04? I can't find any mentions of my nick ... [14:58] laguna, i'd say , you keep 5.15.0-46 and 47 and purge the others... unless you need them [14:59] zetheroo, i don't think there were answers [14:59] Habbie: okay [14:59] well i use the old 5.3 source....and i already autoremove 5.15.0.46 [15:00] laguna, run : ls /var/lib/initramfs-tools/ | nc termbin.com 9999 [15:01] GrandPa-G: is this a new installation? did it work previously? was there any other event that could have caused this to happen, such as a version upgrade or a hardware failure? [15:02] ioria i get this ls: cannot access '/var/lib/initramfs-tools/': No such file or directory [15:02] yes, worked for months. Yesterday it worked. I think it worked when I started this am, but not positive. I did try to put a nvida (old) card into it, got this conidtion for sure, took it out and back to onboard video. That is all. ssh works fine. [15:03] laguna, try again , you mispelled ? [15:03] GrandPa-G: do you have a spare computer you're chatting from now? [15:04] tomreyn, yes [15:04] GrandPa-G: oh you say ssh works fine, that's good. is the system online, too, can you ping -c3 1.1.1.1 without it reporting 100% lost? [15:04] I'm getting this error booting ubuntu 20.04 from a usb drive: ata2: SATA link down (SStatus 0 SControl 300) [15:05] it's 10 mins and it's still frozen [15:05] nothing's plugged in apart from the usb drive it's booting from [15:05] ioria same result there is no initramfs-tools in /var/lib [15:05] if you can ssh in, you know the machine is not crashed [15:05] hey folks. this is what's in my .vnc logfile from when I tried to connect from a debian system: https://paste.ubuntu.com/p/gd5mzMSCVx/ [15:05] tomreyn, -c doesn't work on windows, but I can ping fine. [15:06] GrandPa-G: i mean on the lubuntu system, which you can login to via ssh [15:06]