 alkisg, I have successfully removed all of grub, but I cannot do anything to the protected package shim-signed
[05:08] <alkisg> paculino, why, what's the error message?
 "this is a protected package; it should not be removed"
 Muon does not say it is locked, but it does say it is broken (since its dependencies were removed)
 Would just reinstall it with apt with -f option be sufficient?
[05:28] <alkisg> paculino, use apt, not muon
[05:28] <alkisg> What's the output of: sudo apt purge shim-signed
[05:29] <alkisg> Don't press enter if it says it's dangerous or it'll remove more stuff
 I am not using muon; I was using dpkg
 E: Unmet dependencies
 aptitude does not want to do anything since os-prober and ubiquity need grub-common
[05:31] <alkisg> paculino, please pastebin your whole screen with the output of apt purge
[05:31] <alkisg> ubiquity is the ubuntu installer, it shouldn't be used in an installed system
 https://pastebin.com/nYqLn8sf
[05:33] <alkisg> paculino, today I don't have much time. Do you mind sharing a terminal to finish this sooner?
 Should I uninstall ubiquity? I didn't think I would ever need it, but did not want to uninstall it and it end up being useful
 Sure, but I'm afraid you'll have to walk me through sharing the terminal
[05:33] <alkisg> ubiquity isn't installed in ubuntu. Only linuxmint has it because of a bug they have
[05:33] <alkisg> sudo apt install epoptes-client
[05:34] <alkisg> And then: /usr/share/epoptes-client/share-terminal 81.186.20.0
 It wants to reinstall grub before doing that
[05:34] <alkisg> OK let it reinstall grub
[05:34] <alkisg> You have broken packages now
[05:35] <alkisg> That's what I want to solve but it'll take a lot of time via irc/pastebin, while it'll be fast with terminal sharing
[05:36] <alkisg> You have half jammy sources, half kinetic sources
[05:37] <alkisg> So I'll also fix your installation now, it's completely broken, half 22.04 and half 22.10
 I am aware of mixed sources; someone told me to do that for a certain package
 Should I no longer follow their tech advice?
[05:38] <alkisg> Hrm, you actually have more 22.10 than 22.04 now
 I had a failed update before adding the kinetic sources for a certain package; at the time it appeared it did not go through
[05:39] <alkisg> So since you actually have 22.10, the correct kernel for you would be 5.19
 My plan was to get 5.15 then try to redo the update
 Well, not get, but revert
[05:41] <alkisg> I was advising 5.15 because I thought you had 22.04; that's not true though, you have more 22.10 than 22.04
[05:41] <alkisg> You shouldn't have 5.15 with 22.10
 lsb-release said I had 22.04, so I thought 5.15 was correct rather than 5.19; in any case, the 5.19...longnumber was not correct
[05:44] <alkisg> cat /etc/os-release to see your version
 That also said 22.04 the last I checked
[05:45] <alkisg> What was the initial installation? Please be honest about that part, did you e.g. start from popos  or linuxmint and now it ended up to be kubuntu 22.10?
[05:45] <alkisg> Your os-release says 22.10
[05:46] <alkisg> That answer will help us avoid pitfalls
 PopOS, then I tried to reinstall/overwrite over it with Kubuntu 22.04, and it appeared to have no issues initially
[05:47] <alkisg> Did you reinstall kubuntu over it, or did you try to upgrade to kubuntu?
[05:47] <alkisg> I.e. was the initial popos supposedly wiped completely?
 I did not wipe it since I thought it would just be overwritten
[05:48] <alkisg> OK. So the problem is that popos has a mix, they e.g. ship the 5.19 kernel while they're mostly 22.04
[05:48] <alkisg> I would strongly recommend a reinstallation while keeping ONLY home
[05:48] <alkisg> So you can't upgrade popos to ubuntu without having to undo all their modifications
[05:49] <alkisg> These glitches will haunt you for a lot of time, you'll have to be an ..un-developer of popos to remove them
[05:49] <alkisg> All these small forks of ubuntu do not do proper packaging
[05:49] <alkisg> They just go around in the file system and touch whatever they want
[05:49] <alkisg> So upgrades cannot fix what they manually mess with
 I will keep home, make a new boot partition, and fresh install on that partition as soon as possible, only keeping this original boot partition as a back up in case of any errors.
[05:50] <alkisg> If you want me to quickly fix your grub issue, I can do that, but I strongly suggest that you download an ubuntu 22.04 and reinstall while keeping home, and not waste time in upgrading popos to ubuntu
[05:50] <alkisg> You can keep all your dirs in a subdirectory
[05:50] <alkisg> E.g. I put them in /srv/popos
[05:51] <alkisg> See they even have casper installed, this is the part that boots live CDs
[05:51] <alkisg> They didn't implement the "uninstallation" part of the ubuntu installer correctly, so any popos installation has bad packages installed by default
 I cannot borrow live installation media until Tuesday or Thursday at the earliest; could I just have grub in the meantime?
[05:52] <alkisg> OK
[05:53] <alkisg> popos is still injecting systemd-boot
 I will never again trust an installer or anything to totally overright something when I want it to.
[05:53] <alkisg> I haven't used popos nor systemd-boot, so I do not know how to remove that
[05:53] <alkisg> I believe you should NOT be using grub against popos wishes, and you should stick with your distribution defaults
[05:54] <alkisg> Now e.g. you'll install grub but it won't even take effect because popos will inject systemd-boot instead
[05:55] <alkisg> Well now supposedly grub has taken over from systemd-boot
[05:56] <alkisg> But I can't be sure, this now is neither popos nor ubuntu, it's chaos
[05:56] <alkisg> You may cross your fingers and try to reboot...
 Okay, thank you and please forgive me for the horrible mistakes I made.
[05:58] <alkisg> You should have been honest about popos. It's not that we don't want to help. It's that when we give ubuntu help (e.g. fix grub or restore 5.15. kernel) to popos users (that have systemd-boot and 5.19 kernel), chaos happens
[05:58] <alkisg> Users thing "based on debian, eh, they're all the same". That's not true, advice for one distribution will break another distribution
 I thought pop was overwritten
[05:59] <alkisg> You can't switch distributions by upgrading. Only with clean installations.
[05:59] <alkisg> If you had installed ubuntu over popos, instead of trying to upgrade, then it would have indeed been overwritten
 I am in grub now
[05:59] <alkisg> It would have warned about "formatting /", you'd have said "yes" and you'd have no more popos
[06:00] <alkisg> OK, does it boot?
 It gave me a list of commands
[06:00] <alkisg> No boot menu?
 It is bash more or less
[06:01] <alkisg> set root=(hd
[06:01] <alkisg> Write that, then press tab twice, then screenshot
 https://irc-attachments.kde.org/299a7f3f/file_61448.jpg
[06:02] <alkisg> write 1, then tab twice, then screenshot
[06:02] <alkisg> set root=(hd1,   and then two tabs to list the partitions
 I believe that is the internal : https://irc-attachments.kde.org/3ab1b573/file_61449.jpg
[06:04] <alkisg> Indeed, go back and write hd0, then two tabs and photo again
 https://irc-attachments.kde.org/3d991b0a/file_61450.jpg
[06:04] <alkisg> So that also clears up the question about "popos wasn't seeing your internal disk", I guess it's some udev rule they add for "security"
[06:05] <alkisg> set root=(hd0,gpt4)
[06:05] <alkisg> configfile /boot/grub/grub.c
[06:05] <alkisg> and that point press tab
[06:05] <alkisg> Does it autocomplete the grub.cfg filename?
 I think I was prompted about seeing the internal disk. It does not autocomplete
[06:06] <alkisg> Then the problem is that you remove and/or reinstalled grub without running `update-grub`, so the grub.cfg isn't there
[06:06] <alkisg> Type: linux /boot/vmli
[06:06] <alkisg> and press tab, does it autocomplete? Don't press enter
 It does
[06:07] <alkisg> OK, this is the whole line: linux /boot/vmlinuz root=/dev/sda4
[06:07] <alkisg> And then: initrd /boot/initrd.img
[06:07] <alkisg> And then: boot
 It works
[06:10] <alkisg> When it boots, share a terminal once more: /usr/share/epoptes-client/share-terminal 81.186.20.0
 Alright
[06:21] <alkisg> paculino, it's so slow because you're using a usb2 port
[06:21] <alkisg> paculino, if it's a usb3 case, put it in a usb3 port
[06:21] <alkisg> Anyway it's ready, you may reboot
 I know it is slow because of the port/cord
 Would you a free art commission or something? I'm broke right now but if you have a kofi or something I can repay your for the help once I finish and get reimbursed for my current commission.
[06:35] <alkisg> Thank you paculino, don't worry about it. If I understood you correctly, you're able to do some art? I may ping you if I need a logo for one of my open source projects :)
 Alright (I can do traditional, digital 3d, 2d raster, or 2d vector). Thank you again. I have learned at least. I will try to keep the next learning experience to be mostly from dumb mistakes.
 What is the problem? : https://irc-attachments.kde.org/2feed544/file_61451.jpg
[06:46] <alkisg> It's stuck there? If so, try to reboot, press "e" in grub to edit the command, remove the "quiet splash" part, and press f10 then to boot with a detailed screen output
 No it is not stuck
 It just shows up when i turn it off
 What does it means?
[12:32] <oerheks> why is 25 sec bad?
[14:06] <BluesKaj> Hi all
[21:13] <^Gecko^> hey.  trying to install kubuntu 22.04 lts on an older laptop.  thing boots fine but once xwindows loads it seems to just stop doing anything.  can I run the install from the shell?
[21:13] <^Gecko^> (It's not locked up, I can still log in to the shell with ctrl+alt+f2)
[21:14] <valorie> you could try `plasmashell &`
[21:14] <valorie> and see if plasmashell starts
[21:15] <valorie> if not, at least you would get some error message
[21:15] <valorie> ^Gecko^:  ^^
[21:16] <^Gecko^> this is to say that xwindows doesn't really finish loading, afaik.  all I see it the mouse and the desktop background
[21:16] <^Gecko^> plasmashell & gives me an error about "could not connect to the display"
[21:17] <^Gecko^> https://photos.app.goo.gl/HSmRR48BFLw5e8mG8
[21:18] <valorie> hmmm, your old lappy might be too old
[21:18] <^Gecko^> rofl, maybe.  core solo
[21:19] <valorie> that said I run the newest on my travel laptop, which is perhaps 8 years old
[21:19] <valorie> and this one is .... 4 or 5?
[21:19] <valorie> Sysinfo for 'valorie-Oryx-Pro': Running inside KDE Plasma 5.25.5 on Ubuntu 22.10 (Kinetic Kudu) powered by Linux 5.19.16-76051916-generic, CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz at 2800-3576/3800 MHz, RAM: 11904/32054 MB, Storage: 297/1143 GB, 244 procs, 90.65h up
[21:19] <^Gecko^> https://www.notebookcheck.net/Dell-Latitude-XT-Series.18625.0.html
[21:20] <valorie> I'm no hardware expert
[21:20] <^Gecko^> this came out in 2007'ish I think
[21:20] <valorie> what did that laptop run before?
[21:20] <^Gecko^> it's got win7 on it right now
[21:20] <^Gecko^> not great though, heh
[21:21] <valorie> is it 32-bit?
[21:21] <valorie> because we don't provide that anymore
[21:23] <^Gecko^> looks like the core 2 solo is 64
[21:26] <valorie> I dunno. Plasma is really light, compared to what it was years ago
[21:26] <^Gecko^> https://www.intel.com/content/www/us/en/products/sku/31789/intel-core2-solo-processor-u2100-1m-cache-1-06-ghz-533-mhz-fsb/specifications.html
[21:26] <valorie> but it seems something isn't correctly detecting your display
[21:26] <valorie> how about putting something like Lubuntu on a thumb drive and seeing if that will boot?
[21:28] <^Gecko^> lubuntu
[21:28] <^Gecko^> oops
[21:28] <valorie> I would suggest asking in #kde but it's Sunday and evening for Europe, so you might get not many answers
[21:28] <valorie> right, you might try #lubuntu
[21:28] <^Gecko^> i meant to type that in the browser, lol, but yeah I'm doing that now
[21:33] <valorie> best of luck! I love saving old lappys with linux
[21:43] <^Gecko^> weird hard drive in this thing, a 1.8" parallel ata ZIF
[21:43] <^Gecko^> only 80gb
[21:47] <^Gecko^> ok lubuntu loads ok
[22:30] <^Gecko^> trackpad is super glitchy. :(  lower set of buttons don't work at all and tap to click doesn't work.  touchscreen works though
[23:17] <mybalzitch> ^Gecko^: do you need to borrow a ps2 mouse?