| === DrManhattan_ is now known as DrManhattan | ||
| === antonispgs4 is now known as antonispgs | ||
| === medic2016_ is now known as medic2016 | ||
| === PEAKTOP is now known as router | ||
| === router is now known as Guest7730 | ||
| === Guest7730 is now known as PEAKTOP | ||
| sprokkel | Hi Question: I need an iptables expert: I have this computer with two network interfaces, both have internet connection. I want to send DNS traffic through interf1 and HTTP(S) traffic through interf2. I have this script https://paste.linux.chat/?c05dbc81ca6949bc#ESyXVQfmvUYD7NmmZbWSZumn2bHdBcahWuzuvesYLjNM but I can't get it work. Any idea's? | 06:19 |
|---|---|---|
| qvq | hello | 08:04 |
| qvq | Bayangan: hello | 08:05 |
| qvq | I need a sovereign healthcare plan | 08:06 |
| qvq | I looked at startups in Israel since I will ne the sourcecode for the only sovereign nation on earth and they look like botscript business | 08:08 |
| qvq | Nanovation wasn't enough bloodpressure telemetry | 08:08 |
| qvq | that is like script kiddy stuff | 08:08 |
| qvq | get real | 08:09 |
| === EriC^^3 is now known as EriC^^ | ||
| === aGung is now known as Bayangan | ||
| === kiska36 is now known as kiska3 | ||
| === mrbutthead0 is now known as mrbutthead | ||
| === Dhag0r is now known as Dhagor | ||
| === u0_a98 is now known as Snoop | ||
| PeGaSuS | when using `apt build-dep <package>` can I tell APT to noty install a specific dependency? in this case, I have `libcurl4-openssl-dev` but `apt build-dep weechat` wants to replace it with `libcurl4-gnutls-dev` and I rather keep the openssl one | 09:39 |
| sixwheeledbeast | pin the one you want to keep? | 09:41 |
| === unixeng66837 is now known as unixeng6683 | ||
| pa | can 22.04 run on 5.4 series kernel? | 09:54 |
| pa | i mean, it does on 5.15 | 09:54 |
| ravage | I don't know if it can. It is not supported at all | 09:58 |
| ravage | So avoid it at almost any cost | 09:58 |
| sixwheeledbeast | why, is may first thought. | 10:00 |
| sixwheeledbeast | my | 10:00 |
| === unixeng66837 is now known as unixeng6683 | ||
| === kostkon_ is now known as kostkon | ||
| j_w_t | yes it can... Check out the mainline project. | 11:32 |
| BluesKaj | Hi all | 12:13 |
| lotuspsychj3 | |N3on21|: did your bug changed to a private bug or so? | 12:17 |
| pekdon | hello there | 12:29 |
| lotuspsychj3 | welcome pekdon | 12:30 |
| Snoop | hi | 12:40 |
| lotuspsychj3 | welcome Snoop | 12:41 |
| realivanjx | so my ubuntu server just froze for some reason and rebooted because of watchdog timer. where can i start to look for in the system? | 12:46 |
| CosmicDJ | realivanjx: I'd start with the kernel logs in the journal | 12:47 |
| realivanjx | which file is it? sorry im not really familiar with kernel log files | 12:48 |
| realivanjx | is it /var/log/kern.log? | 12:49 |
| ravage | sudo journalctl --list-boots | 12:49 |
| ravage | sudo journalctl -k -b-1 | 12:49 |
| realivanjx | "sudo journalctl -k -b-1" the last log from there was like an hour+ ago | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸 U S A N o .1 🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| lotuspsychj3 | not here nuke97 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸 U S A N o .1 🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| lotuspsychj3 | !ops | nuke97 | 12:52 |
| ubottu | nuke97: 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 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸 U S A N o .1 🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:52 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:57 |
| nuke97 | 🇺🇸🇺🇸🇺🇸 U S A N o .1 🇺🇸🇺🇸🇺🇸 | 12:57 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:57 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:57 |
| nuke97 | 🇺🇸🇺🇸🇺🇸 U S A N o .1 🇺🇸🇺🇸🇺🇸 | 12:57 |
| nuke97 | 🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸🇺🇸 | 12:57 |
| TheGreatUSA | USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! USA! | 12:57 |
| TheGreatUSA66 | 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! | 13:01 |
| TheGreatUSA66 | 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! | 13:01 |
| TheGreatUSA66 | 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! | 13:01 |
| UnitedWeWin | 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! | 13:02 |
| UnitedWeWin | 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! | 13:02 |
| UnitedWeWin | 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! | 13:02 |
| realivanjx | :| | 13:03 |
| RuleTheWorld | 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! | 13:06 |
| RuleTheWorld | 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! | 13:06 |
| RuleTheWorld | 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! | 13:06 |
| Infrared_ | !ops | RuleTheWorld | 13:06 |
| ubottu | RuleTheWorld: 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 | 13:06 |
| === RuleTheWorld65 is now known as hey | ||
| Infrared_ | !ops | hey | 13:09 |
| ubottu | hey: 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 | 13:09 |
| === hey is now known as everyplzza | ||
| everyplzza | 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! | 13:09 |
| everyplzza | 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! | 13:09 |
| everyplzza | 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! 🏳️⚧️ USA! 🏴☠️ USA! 🏳️🌈 USA! | 13:09 |
| pragmaticenigma | Infrared_: best to just let this run its course, if you keep doing that, it only encourages it to happen more because they know someone is paying attention | 13:10 |
| Infrared_ | pragmaticenigma: If it's better not to let the operators know that somebody is flooding the channel, perhaps having an option to message them in an emergency doesn't make much sense :) It doesn't seem to be doing much to stop the flag-waving psychopaths in the audience | 13:10 |
| pragmaticenigma | Infrared_: it's happening in multiple channels right now, if anything, it's probably up to libera admins to take action at this point. | 13:11 |
| Infrared_ | pragmaticenigma: They already have :) At least somebody is awake today. | 13:12 |
| pragmaticenigma | Infrared_: you can also join the ops channel and message directly there. It usually better than the bot trigger here when it comes to spammers | 13:12 |
| sixwheeledbeast | ozone? | 13:13 |
| Infrared_ | Poor guy seems to be having connection problems all of a sudden, must have waved his flag too hard and got on somebody's nerves :)\ | 13:15 |
| BluesKaj | his ip published so.... | 13:23 |
| BluesKaj | LA | 13:24 |
| pragmaticenigma | In this day, IP spoofing is the norm, so are proxy gateways, VPNs, and tor. IP address really means nothing | 13:25 |
| BluesKaj | yeah but maybe not savvy enough to use one | 13:26 |
| BluesKaj | not everyone is like you pragmaticenigma :-) | 13:27 |
| pragmaticenigma | just sayin' since a few IPs were coming from the same subnet for that spammer | 13:28 |
| Jym | Good morning, I was working with someone last week, but got disconnected. My question/issue is listed here https://pastebin.com/raw/s2ag0cHa | 14:13 |
| sixwheeledbeast | Probably the simplest way is to use "=saved" and save the last kernel loaded if you can instruct them to do that. | 14:25 |
| Jym | sixwheeledbeast Currently booted into -113. So if I change GRUB_DEFAULT=saved | 14:28 |
| Jym | GRUB_SAVEDEFAULT=true, then sudo update-grub it should take? I'm kinda curious as to why the boot MENU isn't being displayed as well. | 14:28 |
| Jym | ...or why the 20 second timer isn't working | 14:28 |
| pragmaticenigma | Jym: I think there are two settings for the boot menu... setting the timeout is one of them, and another to actually display it always | 14:29 |
| Jym | pragmaticenigma I have =menu and nsplash removed | 14:30 |
| sixwheeledbeast | timeout style menu | 14:30 |
| Jym | nosplash* | 14:31 |
| pragmaticenigma | Jym: I think the option is GRUB_HIDDEN_TIMEOUT ... where the grub screen remain blanked, but accessible if the user presses the right key | 14:31 |
| pragmaticenigma | within the defined timeout | 14:31 |
| pragmaticenigma | nosplash is for the plymouth boot screen, does not affect grub | 14:31 |
| Jym | GRUB_TIMEOUT_STYLE=menu | 14:32 |
| sixwheeledbeast | I don't have hidden timeout and i get grub on boot... | 14:32 |
| pragmaticenigma | Jym: that's not what I'm referring to... there is GRUB_TIMEOUT and GRUB_HIDDEN_TIMEOUT ... they are two separate things | 14:34 |
| sixwheeledbeast | hidden timeout is for a countdown to press a button for grub | 14:34 |
| Jym | I'm not wanting anything hidden, and I thought I disabled all that? | 14:35 |
| pragmaticenigma | No: The time the screen remains blank but available for display is determined by a setting in /etc/default/grub (GRUB_HIDDEN_TIMEOUT) | 14:35 |
| sixwheeledbeast | https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html | 14:35 |
| pragmaticenigma | https://help.ubuntu.com/community/Grub2 | 14:35 |
| pragmaticenigma | Under the section Hidden | 14:35 |
| sixwheeledbeast | AIUI they want grub menu on boot not a countdown and then grub menu | 14:37 |
| pragmaticenigma | you're not reading what I'm saying | 14:37 |
| pragmaticenigma | There are TWO options. One sets the countdown timer... the other keeps the screen blank while the timer counts down. If you press the shift key within that time, the menu will appear | 14:38 |
| Jym | Ok, but I DO NOT want a blank screen, just give a menu. Haven't I already disabled all the "hidden" things? | 14:39 |
| pragmaticenigma | GRUB_HIDDEN_TIMEOUT is that option, adding it and setting it to zero should result in the GRUB menu always displaying on boot | 14:39 |
| Jym | OH | 14:39 |
| Jym | adding GRUB_HIDDEN_TIMEOUT=0 will display the menu, but still give the 20 seconds until it boots the default? | 14:40 |
| pragmaticenigma | I'm trying to find the exact documentation to make sure what I'm saying is correct. but that should be correct | 14:40 |
| pragmaticenigma | Jym: On this documenation https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html ... look for "GRUB_HIDDEN_TIMEOUT"... it explains Wait this many seconds before displaying the menu. If ESC or F4 are pressed, or SHIFT is held down during that time, display the menu and wait for input according to ‘GRUB_TIMEOUT’. If a hotkey associated with a menu entry is pressed, boot the associated menu entry immediate | 14:42 |
| pragmaticenigma | ly. If the timeout expires before either of these happens, display the menu for the number of seconds specified in ‘GRUB_TIMEOUT’ before booting the default entry. | 14:42 |
| pragmaticenigma | Jym: Make sure that GRUB_TIMEOUT is not set to zero, or the menu will never be displayed unless the hot keys are already held down when GRUB loads | 14:43 |
| Jym | GRUB_TIMEOUT=20 | 14:45 |
| BigDickKonqi | hi | 14:45 |
| BigDickKonqi | i | 14:45 |
| BigDickKonqi | have | 14:45 |
| BigDickKonqi | a | 14:45 |
| BigDickKonqi | really | 14:45 |
| BigDickKonqi | think | 14:45 |
| BigDickKonqi | *thick | 14:45 |
| Jym | pragmaticenigma Does this look correct? https://pastebin.com/raw/ckVY6g8s | 14:54 |
| Jym | sixwheeledbeast more eyes never hurts =) ^^^^^ | 14:55 |
| pragmaticenigma | Jym: Currently reading up on the GRUB_TIMEOUT_STYLE option, which appears to be preferred over the GRUB_HIDDEN_TIMEOUT | 14:56 |
| Jym | pragmaticenigma I never actually got a menu displayed. Had to have her hit ESC then go into ADVANCED menu to select -113 | 14:57 |
| pragmaticenigma | Jym: was the GRUB_TIMEOUT_STYLE already set to menu before, or is that change you've made today? | 14:59 |
| Jym | Yes, it was already set to MENU before today | 14:59 |
| Jym | When the menu never appeared, I enabled the BEEP to let her know when to hit the ESC key. | 15:00 |
| pragmaticenigma | give me a moment to that config here | 15:01 |
| Guest46 | sudo nmcli connection up Wi-Fi\ connection\ 1 | 15:01 |
| Guest46 | Error: Connection activation failed: 802.1X supplicant took too long to authenticate | 15:01 |
| Guest46 | how do i setup a wpa3 personal hotspot on ubuntu 24.04 | 15:02 |
| Jym | k | 15:03 |
| sixwheeledbeast | was afk, i have just re read I still dont get why the other option even matters. To make it easier to read just remove the duplicated commented lines. | 15:06 |
| sixwheeledbeast | you have grub default twice as well | 15:07 |
| Jym | sixwheeledbeast It's jsut my way if a muck something up, I know what it was and can revert back | 15:08 |
| sixwheeledbeast | copy the original file elsewhere before you edit it. | 15:09 |
| Jym | Oh I made a backup of every edit =) | 15:09 |
| sixwheeledbeast | You will be able to read it better and pick up this double entry. | 15:10 |
| pragmaticenigma | Jym: I was able to confirm that you do not need to use `GRUB_HIDDEN_TIMEOUT=0` when using `GRUB_TIMEOUT_STYLE=menu` | 15:11 |
| Jym | I only see one for GRUB_DEFAULT=1 (plus one commented out above it) https://pastebin.com/raw/ckVY6g8s | 15:11 |
| pragmaticenigma | so that kind of puts us back at where you started this conversation | 15:12 |
| Jym | pragmaticenigma Ok, I'll comment out the =0 line | 15:12 |
| pragmaticenigma | Jym: I'd just remove it entirely. It is documented as a deprecated feature. Removed due to its confusing name | 15:12 |
| pragmaticenigma | GRUB_TIMEOUT_STYLE was added to replace it | 15:12 |
| sixwheeledbeast | this is my file, which always shows the menu for 10 seconds on boot before selecting option 0 (first in the list). https://pastebin.com/raw/pa8wGMcx | 15:13 |
| pragmaticenigma | that's pretty much the same that I had for my testing as well | 15:15 |
| sixwheeledbeast | You need to replace GRUB_DEFAULT to =saved and then add GRUB_SAVEDEFAULT=true the line under that. You will probably want to clear my fsck option if you use that file. | 15:16 |
| Jym | Here is the current grub (before update-grub) https://pastebin.com/raw/fvE7C5nU | 15:17 |
| pragmaticenigma | Jym: when commmiting these changes... are you using `sudo update-grub2` ? | 15:17 |
| sixwheeledbeast | you still have default twice | 15:17 |
| sixwheeledbeast | ... | 15:17 |
| Jym | sixwheeledbeast I see it now, will remove the =1 | 15:18 |
| Jym | pragmaticenigma No, just update-grub, not update-grub2 | 15:19 |
| sixwheeledbeast | you didn't have to remove all the comments :P just helps without the dups. | 15:20 |
| Jym | =) | 15:20 |
| sixwheeledbeast | should be right then if you update-grub. | 15:22 |
| pragmaticenigma | Jym: nevermind, it was a goose chase... I thought there was a difference until I found /usr/sbin/update-grub2 is just symlined to /usr/sbin/update-grub | 15:23 |
| === five618480330 is now known as five61848033 | ||
| Jym | pragmaticenigma No worries, I man update-grub and got: update-grub is a stub for running grub-mkconfig -o /boot/grub/grub.cfg | 15:24 |
| Jym | to generate a grub2 config file. | 15:24 |
| Jym | Ok, I'll run sudo -H update-grub, reboot, and see what happens =) | 15:26 |
| === five618480336 is now known as five61848033 | ||
| sixwheeledbeast | You'll obviously have to select the correct menu entry for it to save for the next boot. | 15:30 |
| === pikapika_lunar is now known as militantorc | ||
| Jym | sixwheeledbeast But the issue that remains is there is no MENU being displayed. I'm in kernel -113 right now because she hit ESC and went into the ADVANCED menu and selected it. | 15:35 |
| osmos_ | fdhf | 15:36 |
| osmos_ | hello | 15:36 |
| sixwheeledbeast | hmm | 15:36 |
| pragmaticenigma | Jym: The beep might be happening before the screen has time to display anything. Is your contact maybe needing to wait just a count of 2 before pressing any keys? | 15:37 |
| sixwheeledbeast | does selecting the correct kernel work at least? | 15:37 |
| pragmaticenigma | Jym: or, perhaps your contact needs to just trust the process and let it try to boot all on its own for a cycle? | 15:38 |
| Jym | pragmaticenigma I enabled the BEEP because no menu was being displayed, and the 20 second timer wasn't being acknowledged. | 15:39 |
| Jym | https://pastebin.com/raw/sLxt1mua | 15:39 |
| Jym | sixwheeledbeast Only from the ADVANCED menu | 15:39 |
| Jym | manually involked | 15:39 |
| sixwheeledbeast | on the next boot if you leave it to timeout it doesn't auto select 113? | 15:40 |
| Jym | I'll find out in 90 seconds =) | 15:40 |
| pragmaticenigma | Jym: I think the issue might be that paitence is needed. The beep is there to indicate there's a menu. But it may take a moment or two for the graphics display to sync and display the text. ... oh okay, you're already having them try the wait and see suggestion | 15:40 |
| === pushkarnk1 is now known as pushkarnk | ||
| Jym | Damn, booted into -116 | 15:42 |
| sixwheeledbeast | so it's not reading the file. | 15:43 |
| Jym | I thoguht that might be the issue, but then I enabled BEEP and that worked | 15:44 |
| Jym | So it's reading at least SOME of the file | 15:44 |
| Bert | Hi. I'm migrating from Ubuntu 18.04 to a new installation of Ubuntu 24.04 and I've been noticing something strange. I thought all fonts looked quite "thin" so I wanted to go from Ubuntu Regular to Ubuntu Medium inside "Appearance" but even after logging out or rebooting there's zero difference. However, when I change to a completely different font, the change is immediate and huge. Do other people have this | 15:46 |
| Bert | same issue? I feel like this is a bug to do with space escaping/quoting where it's always picking Ubuntu Light instead of Regular or Medium or Bold, but I'd love other to help verify this. | 15:46 |
| Bert | *others | 15:47 |
| pragmaticenigma | I don't have 24.04 on anything. but if you have scaling enabled for a higher resolution display, that might be something to look into | 15:48 |
| ioria | Bert, are you talking about this ? https://ubuntuhandbook.org/index.php/2023/04/restore-old-fonts-ubuntu-2304/ | 15:49 |
| Bert | it's on autodetect on the "monitor preferences" thing | 15:50 |
| sixwheeledbeast | Jym: it will fallback if there is something wrong. double check the file again. did you run grub-mkconfig like it suggests? | 15:51 |
| Bert | ioria: I wasn't aware of that even | 15:51 |
| Bert | I was just comparing settings between 18.04 and 24.04 | 15:51 |
| Bert | and I noticed that changing boldness did nothing and that the preview doesn't match reality | 15:52 |
| Bert | it feels very bugged honestly | 15:52 |
| === ice9_ is now known as ice9 | ||
| ioria | Bert, can you try to set bold text in gnome-terminal preferences ? | 15:53 |
| Bert | ioria: mate-terminal, but sure | 15:53 |
| Jym | sixwheeledbeast Current grub file: https://pastebin.com/raw/VZ5zAeGE -- Never touched grub-mkconfig, just update-grub | 15:54 |
| Bert | ioria: in my terminal if I overwrite system defaults it does make a difference | 15:54 |
| Bert | how odd | 15:54 |
| ioria | Bert, ok, thanks | 15:54 |
| Bert | I do feel like it's just always applying the same Ubuntu font from "Appearance Preferences" | 15:55 |
| Bert | but I'm gonna try that blogpost you linked | 15:55 |
| Bert | that sounds interesting | 15:55 |
| ioria | Bert, if you install fonts-ubuntu-classic it will remove the Splash... be cautious | 15:55 |
| pragmaticenigma | Jym: Get them to boot all the way with 113. Then do a clean shutdown. Then have them to do the start up and just let it do its thing. Boot is the hardest, most patience testing thing to deal with | 15:57 |
| Bert | ioria: it's weird, it complains but it went ahead | 15:58 |
| Bert | and didn't remove any dependencies | 15:58 |
| ioria | ah, ok | 15:58 |
| Jym | pragmaticenigma I can get to 113, but only via ESC > ADVANCED > then selecting 113. Will that be enough? | 15:58 |
| Bert | it looks much better after a logout and login | 15:59 |
| Bert | must say this was quite odd: | 15:59 |
| Bert | dpkg: fonts-ubuntu: dependency problems, but removing anyway as you requested: | 15:59 |
| Bert | ubuntu-mate-default-settings depends on fonts-ubuntu. | 15:59 |
| Bert | plymouth-label depends on fonts-ubuntu. | 15:59 |
| Bert | mate-desktop-environment-core depends on fonts-cantarell | fonts-ubuntu; however: | 15:59 |
| Bert | Package fonts-cantarell is not installed. | 15:59 |
| pragmaticenigma | Jym: for the first go, yes. then try a reboot after that is successful. I'm not familiar with the saved option, I'm wondering if there's some other way to trigger that? | 16:00 |
| ioria | Bert, does not sound safe | 16:00 |
| Jym | pragmaticenigma Yeah, I was thinking that too (abut the trigger). | 16:01 |
| Bert | ioria: yeah I'm gonna try and see what I can do to make dependencies happy | 16:01 |
| ioria | Bert, check the 'autoremove' | 16:01 |
| Bert | autoremove and -f install don't want to change anything, how odd | 16:02 |
| ioria | Bert, dpkg -l | grep plymouth | 16:02 |
| Bert | all results have "ii" status | 16:03 |
| ioria | ok | 16:03 |
| Bert | odd | 16:03 |
| Bert | it doesn't feel like this should be fine :P | 16:03 |
| ioria | yep | 16:03 |
| Bert | to be fair, all these dependencies should be "fonts-ubuntu | fonts-ubuntu-classic" | 16:05 |
| === five618480337 is now known as five61848033 | ||
| Bert | or fonts-ubuntu-classic should supply fonts-ubuntu hence fulfilling the depency still | 16:05 |
| Bert | maybe that's still what's happening? | 16:05 |
| Bert | ah yeah: Provides: fonts-ubuntu | 16:06 |
| Bert | then it ought to be fine and just not complain | 16:06 |
| Bert | very very odd | 16:06 |
| beowuff | Anyone here use byobu, or know where I can find info? I'm having trouble finding any suggestions about running byobu and then connecting to a host with byobu and best practices. | 16:21 |
| pragmaticenigma | beowuff: I just use tmux directly, not sure what byobu adds beyond being a wrapper around screen/tmux | 16:26 |
| beowuff | It adds a few nice features that I like. Basically, sets up tmux in a way that I like, but I get it. | 16:28 |
| beowuff | What do you do about running tmux in tmux? Like, multiple layers through sshing to other hosts. | 16:29 |
| beowuff | I'm just wondering what kind of issues there might be and/or work arounds, or if I should just not worry about it. XD | 16:30 |
| beowuff | Searching for byobu in byobu doesn't return anything helpful. :) | 16:30 |
| pragmaticenigma | took me way too much effort to finally land here: https://github.com/dustinkirkland/byobu | 16:31 |
| beowuff | Wow, that actually worked as a search for tmux, though. | 16:31 |
| beowuff | Okay, thanks for the link. I'll check it out. | 16:32 |
| pragmaticenigma | That's just the source code from the developer.. I found the project page with a ton of dead links | 16:32 |
| beowuff | You know, it's weird. I've searched byobu a ton, and never came across the code. | 16:32 |
| pragmaticenigma | I found it buried deep... they don't link to their repo on the site from what I can tell. or not a very good link. Just to a build file on launchpad. From there, I found a link to it's project page, and from there found a change log entry stating thigns were migrated to github | 16:33 |
| beowuff | Eh, maybe I should just dive deeper into tmux. | 16:34 |
| pragmaticenigma | beowuff: the only issue I can think of running multi-layers in any of them is status bars being used. They both can take up a couple lines at the bottom of the screen for their status. Which may make working in multi-layer a little more difficult | 16:35 |
| pragmaticenigma | I get the appeal though... SSH into a primary target machine, then SSH from there to other machines. If the primary machine connection is lost, it can be re-established without having to start all over | 16:36 |
| beowuff | I'm sshing in from a mac using iTerm2, so I'm not too worried about layering. I can't imagine ever going more than three deep, but I suppose there's always the possibility. | 16:36 |
| pragmaticenigma | and having a similar session on the secondary machines means those sessions can be re-established too | 16:36 |
| beowuff | Alright, I've got a lot to think/read now. You guys are awesome! Thank you. | 16:37 |
| Jym | pragmaticenigma sixwheeledbeast Well, it FINALLY worked! When the BEEP happened, hit SPACE, then ADVANCED, then 113, rebooted and it became the "saved default". Rebooted a couple of times and 113 was booted up without any intervention. If you hit ESC at the BEEP, it dropped to a grub prompt (thus SPACE instead). | 16:45 |
| pragmaticenigma | interesting | 16:46 |
| Jym | pragmaticenigma So, selecting 113 from ADVANCED is a trigger for SAVED at least =) | 16:46 |
| pragmaticenigma | that would make sense. odd that the differentiation is between using Escape versus Space to get there | 16:47 |
| Jym | Yeah, no clue on that, no mention of SPACE either, -shrug- | 16:48 |
| Jym | undocumented feature =) | 16:48 |
| Jym | pragmaticenigma sixwheeledbeast Just wanted to thank you guys, very much appreciated =) | 16:49 |
| * pragmaticenigma wonders what f4 would do | 16:50 | |
| Jym | DO IT, what could go wrong??? | 16:50 |
| enigma9o7 | how bout a game of global thermonuclear war? | 16:51 |
| Jym | tic-tac-toe... | 16:51 |
| pragmaticenigma | Jym: I'll keep it in mind when I start decommissioning that system. Right now it's vital to a few things for my network | 16:52 |
| Jym | pragmaticenigma Got backup? | 16:52 |
| pragmaticenigma | about half way through a thought occured to me that I could have done the testing i was doing in a VM | 16:52 |
| pragmaticenigma | Jym: what's a backup?! *smirk* | 16:53 |
| pragmaticenigma | "backups" are already provisioned and running under Rocky Linux. just a couple loose ends to tie up | 16:54 |
| Jym | pragmaticenigma I'm at a point now that I am working on dual independent systems that will just rsync to each other at the system level. Will be in conjunction with ventoy running a VM on baremetal =) | 16:55 |
| pragmaticenigma | The new machines are running docker instances of the things I have running "bare metal" under ubuntu. DNS being one of them. Ubuntu is just still set as the primary DNS, so when it goes down, the natives get restless | 16:56 |
| enigma9o7 | ventoy can boot VMs now? That's quite a development. | 17:00 |
| Jym | I haven't even looked at Dockers. I like the idea of booting a VM on bare metal, then I can clone (maybe snapshot) to a compeltely different box | 17:01 |
| Jym | enigma9o7 Yeah https://www.ventoy.net/en/doc_vlnk.html | 17:02 |
| pragmaticenigma | Jym: I'm not completely sold on the idea of docker, but the nice thing is that I can have all my data stored locally, and easily update the docker container with the application without risk of loss of data. Same goes for easier migrations | 17:03 |
| Jym | pragmaticenigma I got my ass bitten WAY TOO MUCH to muck with something "new" right now, just want something that is reliable. I had a brown out wipe out the PS, mobo, boot disc, and one of 4 drives in the NAS. | 17:05 |
| Jym | two hp elite in tandem works for me | 17:05 |
| Jym | each with a 4TB nvme for data | 17:06 |
| pragmaticenigma | well... docker isn't going to solve hardware failures... though if the data survives, getting back online is a lot easier | 17:09 |
| Jym | TWO of these (as example) https://www.amazon.com/HP-EliteDesk-Quad-Core-Professional-Bit-Multi-Language-English/dp/B08KSGKHVS | 17:11 |
| pragmaticenigma | well... there's ya problem.. HP :P | 17:12 |
| Jym | LMAO I haven't bought them yet =) | 17:12 |
| Jym | They have good reviews on YT | 17:12 |
| Jym | they also have m2 slots for 4TB NVME =) | 17:13 |
| Jym | Using a 256GB SSD is way overkill for a ventoy boot drive, but so what?! lol | 17:14 |
| Jym | I jut wish it had 10GigE port =) | 17:15 |
| Elliria | Hey there. I've got a LibreOffice Calc spreadsheet that consists of three pages. One has text in two of the cells and the other two pages each have a small table followed by a chart generated from the table. When I export to PDF, all three pages are exported, but the Table of Contents in the PDF sidebar only shows one clickable page. Any idea what I should change to get all three clickable pages in that sidebar? | 17:32 |
| Elliria | I thought I'd add that I've created lots of PDF files from LibreOffice Writer and not seen this behavior. I'm not sure if it's a Calc thing or not, but this is new to me. | 17:33 |
| Jym | Elliria you might try #LibreOffice | 17:35 |
| pragmaticenigma | It might be more to do with "pages" really aren't a thing in spreadsheets. just that when printing/publishing to a fixed size format, that the program has to arbitrarially cut the spread into sections to fit. | 17:35 |
| pragmaticenigma | Elliria: You may have luck putting things into separate sheets within the file. Maybe each sheet will get it's own page in the TOC. | 17:36 |
| Elliria | Yep. I just tried that and it seems to be the magic. Thank you! | 17:37 |
| Elliria | Apparently, even though sheets are separated into pages (as shown by the little indicator lines on them), that doesn't count when it comes to exporting. Interesting. | 17:38 |
| pragmaticenigma | yep... they just help you see if you were printing where the page breaks would line up. But there's no way to indicate what each segment represents, so it would be considered all part of the same overall sheet | 17:39 |
| Elliria | Well, this is definitely good to know and will end up in my ever-growing personal wiki so I don't forget it later. Heh. | 17:39 |
| pragmaticenigma | The folks in #libreoffice may have more suggestions to help fill it out more | 17:40 |
| Elliria | Ah, true. Thanks. | 17:41 |
| Elliria | Nobody replied there, but this worked perfectly and I've now got a sharable document. Thank you so much! | 17:51 |
| Jym | The lights are on, but nobody's home =) | 17:58 |
| === tom_ is now known as paul424 | ||
| Juest | hello, is it possible to upgrade a installation successfully over chroot? | 19:00 |
| Juest | trying to upgrade 22.04 to 24.04 | 19:00 |
| Juest | thinking in performing the upgrade via chroot on a different distro | 19:01 |
| Juest | i understand if its not supported but, is it possible? | 19:01 |
| Juest | should it be a systemd distro and preferably ubuntu? | 19:01 |
| pragmaticenigma | Not recommended, and not likely something that would be supported here. Official upgrade tools and channels are preferred for support here | 19:02 |
| Juest | again i understand that | 19:02 |
| Juest | thanks pragmaticenigma | 19:03 |
| pragmaticenigma | Juest: if you're working from a broken system, chroot would be a tool used to help resolve that. Upgrades have a lot of pre and post scripts to be run before and after packages are upgraded. So the correct sources are pulled for future updates. | 19:04 |
| Juest | pragmaticenigma: i am simply looking to upgrade it that way because i refuse to reboot to it | 19:04 |
| pragmaticenigma | Juest: 22.04 has a long life ahead of it... if it's working for you now, you have some time before you will have to upgrade to get a newer kernel to keep up with vulnerability patching. | 19:06 |
| Juest | right, well then i'd be interested in keeping it up to date through chroot upgrading | 19:07 |
| Juest | s/upgrading// | 19:07 |
| Juest | and also to gain some personal experience with that aspect | 19:08 |
| pragmaticenigma | okay, as I said, it's not supported update mechanism. chroot isn't for doing that. It's typically for taking a storage volume from a non-working machine, putting it into a working machine then using chroot to use the active kernel with the software located on the broken volume. It's not an upgrading tool | 19:10 |
| Juest | once again i am aware of that but i do see the ability to update systems offline through the power of chrooting | 19:11 |
| pragmaticenigma | I don't know where you gotten that idea... that's not its purpose... and your phrasing leads me to believe you're just here to troll | 19:12 |
| Juest | pragmaticenigma: okay, you're showing rigidity about experimental ideas. i am not here to troll. i guess the conversation is over then. | 19:14 |
| Apachez | Im too lazy to file any bugreport but in case somebody cares - updating from 22.04 LTS to 24.04 LTS (old install thats been alive since 18.xx somewhere) fails to install systemd-resolved which means that halfway the do-release-upgrade it will fail with fetching snap images and completing the install | 19:15 |
| Apachez | workaround is to manually add xx.archive.ubuntu.com and security.ubuntu.com and api.snapcraft.io to the /etc/hosts and then before reboot manuall add systemd-resolved through "apt-get install systemd-resolved" | 19:16 |
| oerheks | chroot is a kind of way booting it | 19:17 |
| oerheks | Apachez, did you use the -d option? upgrade path is not out yet | 19:18 |
| pragmaticenigma | Apachez: I think sometime around the 18.04 release there was a recommendation to do a clean install and not an upgrade. Though I'm uncertain on that. But something you should know... posting about bugs here does nothing. This channel is not monitored for bug reports, and a bug report requires being able to recreate the issue which is why you wuold need to file the bug report so you can file all the relevant information about your system | 19:19 |
| pragmaticenigma | to help developers recreate and fix the issue. | 19:19 |
| pragmaticenigma | Juest: if you want experimental stuff like that, I recommend asking in #linux then | 19:20 |
| Juest | ah, good to have a reminder of the upgrade path of 22.04 to 24.04 not being allowed yet | 19:21 |
| oerheks | if you do, prepare a fresh 24.04 iso on usb | 19:21 |
| Juest | so once its august i can start thinking in upgrading my ubuntu installs | 19:21 |
| Juest | oh? but the existing system does currently function | 19:22 |
| oerheks | will it, if you use the -d development upgrade ? | 19:22 |
| oerheks | ofcourse i wish you do not need it. | 19:23 |
| pragmaticenigma | just don't use the -d ... especially with the release of it going to be so near in the future... just wait, less of a headache if something breaks | 19:23 |
| Juest | im not planning to preemptively upgrade with the -d option | 19:24 |
| Juest | i have read that the upgrade path enablement is slated for august 2024 | 19:33 |
| oerheks | around 15th | 19:36 |
| Bert | it's parallel with the 24.04.1 release, no? | 19:39 |
| Bert | I used to just wait for that | 19:39 |
| pragmaticenigma | Not so much parallel, as much as Ubuntu 24.04 is considered stable with the realse of 24.04.1 and thus they activate the upgrade channels from older versions | 19:41 |
| chrisgt | I have ubuntu 24.04 and cannot get the grub menu on boot by holding down or mashing shift. | 19:47 |
| chrisgt | I installed a bad kernel and had to fix it from chroot on a live recovery boot, would have been easy if i could boot to grub | 19:47 |
| oerheks | it could be esc or left shift, tap repeatedly | 19:49 |
| oerheks | see the grub manual | 19:49 |
| oerheks | !grub | 19:49 |
| ubottu | GRUB2 is the default Ubuntu boot manager. Lost GRUB after installing Windows? See https://help.ubuntu.com/community/RestoreGrub - For more information and troubleshooting for GRUB2 please refer to https://help.ubuntu.com/community/Grub2 | 19:49 |
| pragmaticenigma | chrisgt: are you asking for help, or just making a comment about your experience? | 19:49 |
| oerheks | probably an UEFI machine? | 19:49 |
| pragmaticenigma | let them reply | 19:49 |
| chrisgt | i'm looking for help, sorry for giving the backstory on why | 19:51 |
| chrisgt | I was mashing left shift, i'll try right shift and esc | 19:51 |
| pragmaticenigma | chrisgt: might work better to press and hold shift instead. I really do not understand why Ubuntu ships with a zero timeout on grub... it should be at least 3 seconds to give people a chance to press a key to get the screen to come up | 19:52 |
| pragmaticenigma | chrisgt: when you say installed a bad kernel, I assume one that you compiled yourself or got from another source than the ubuntu software repos? | 19:53 |
| chrisgt | ESC gets me there, the problem is hitting ESC in the main grub window brings you to the grub shell, ESC also brings up some EFI info page... fun! | 19:53 |
| oerheks | left shift it is. but have fun, trying somthing different. | 19:53 |
| chrisgt | yea i compiled a kernel myself as a have an issue with the hfsplus driver and wanted debug info, add some stuff to dmesg, and the latest source | 19:54 |
| chrisgt | left shift doesn't work, allows it to boot | 19:54 |
| oerheks | weird, then there must be more users complaining, search the forums on your machine id? | 19:57 |
| oerheks | left shift or esc, there is no other key defined. | 19:58 |
| chrisgt | ESC works, it's just annoying because it brings me to the EFI info screen, then if i hold it down it exits the grub selection screen to the grub shell | 19:58 |
| pragmaticenigma | chrisgt: for your future self... when messing with kernels... change your grub settings to have a longer timeout and not hide the grub boot menu | 19:59 |
| pragmaticenigma | *grub configuration | 19:59 |
| chrisgt | pragmaticenigma: lol yea, i'll certainly do that. i use debian everywhere else other than this laptop so this kinda caught me off guard | 19:59 |
| pragmaticenigma | `/etc/default/grub` change GRUB_TIMEOUT=20 (or some other sane seconds count) and GRUB_TIMEOUT_STYLE=menu | 20:00 |
| chrisgt | awesome, thanks | 20:00 |
| pragmaticenigma | luckily hadn't closed that tab from earlier today :) | 20:01 |
| chrisgt | i haven't had to compile a whole kernel for quite a long time, this one really threw me for a loop | 20:02 |
| Apachez | oerheks: nope, no -d | 20:13 |
| Apachez | pragmaticenigma: I know, I was just hoping IF somebody cars and have a bugzilla account (or wherever bugs end up at) they could just copy paste my lines :) | 20:14 |
| Apachez | oerheks: which was why I got surprised, I thought it would go to 23.10 first (or even 22.10, 23.04 etc) but it jumped straight to 24.04 from 22.04 | 20:15 |
| === solarwind24 is now known as solarwind | ||
| === fullstack is now known as mostafa | ||
| oerheks | no, upgrade or do-release-upgrade does not work yet. weird. | 20:43 |
| toddc | 24.04.1? | 20:47 |
| oerheks | yes, in august | 20:47 |
| toddc | yes I would not expect inplace upgrade till then | 20:48 |
| toddc | and still prefer clean installs either way if possible --less chance of issues | 20:50 |
| de-facto | when ssh collapses in the middle of a apt upgrade session, how do i re-run the post install scripts of all those packages? | 21:05 |
| enigma9o7 | it tells you when you try to apt upgrade, something about dpkg cfg -a or something but that isnt quite it | 21:05 |
| oerheks | apt install -f | 21:06 |
| enigma9o7 | (so just try to apt upgrade and see what it tells you, it'll give you the exact command) | 21:06 |
| justme_ | I'm sorry to ask but after I did a atp upgrade and it updated the kernel things are starting to breaking including my vm's that now won't start | 21:13 |
| justme_ | How do I tell ubuntu from within ubuntu to use a earlier kernel at next reboot | 21:14 |
| bprompt | justme_: usually on a kernel update, it makes a new vmlinuz img, but it keeps the old ones, so from the Grub menu, you'd have a choice to boot to either kernel, new or old one | 21:16 |
| justme_ | the old one is also around checked with dpkg. But sadly it's a system where I don't have keyboard and screen access ( and no kvm yet ) so have to get it done from within ubuntu | 21:18 |
| justme_ | btw its a 22.04 server install | 21:19 |
| de-facto | thanks | 21:21 |
| oerheks | Tons of guides out there, https://askubuntu.com/questions/1308901/setting-older-kernel-version-as-default | 21:22 |
| oerheks | but you better find out why your "VMs" do not run | 21:24 |
| bprompt | justme_: one way I can think of offhand, is simply editing /boot/grub/grub.cfg which is where the Grub menus is at, it uses a default entry, simply change the defaulted entry from the menus there, so it defaults to the Old kernel | 21:24 |
| justme_ | oerheks thank you very much for that link gonna look at it. Unfortunately it's not the first time a kernel update from has broken my virtual box vm's and got them to instant report stuck and pegged at 99% cpu | 21:27 |
| oerheks | "sudo modprobe vboxdrv, you get modprobe: ERROR: could not insert 'vboxdrv': Required key not available" | 21:33 |
| oerheks | The solution is to manually sign the key EVERY time this happens, because the signing is KERNEL-DEPENDENT. It is related to Secure Boot. | 21:33 |
| justme_ | oerheks there is no secure boot, but is right now going over my log and looks like after ether the ubuntu update ( their system package ) or the kernel then it doesnt like the cpu anymore | 21:37 |
| justme_ | so looks like posible removed from the kernel | 21:37 |
| oerheks | so,, what happens when you run: sudo modprobe vboxdrv | 21:38 |
| oerheks | then reboot | 21:38 |
| justme_ | it won't fix it since it is loaded ffs. The kernel literally reports the cpu wrong its a i7 and the kernel now in thhe latest reports it as i5 | 21:40 |
| oerheks | lolz | 21:43 |
| oerheks | have fun booting the older kerne; | 21:44 |
| oerheks | -l | 21:44 |
| phrack_extractor | I'm trying to extract a file and can't figure out how to translate & save the file | 21:46 |
| phrack_extractor | It's from phrack | 21:46 |
| phrack_extractor | http://www.phrack.org/issues/70/5.html#article | 21:46 |
| phrack_extractor | Near the bottom is --[ 9 - Source Code | 21:47 |
| phrack_extractor | begin 644 vm_escape.tar.gz | 21:47 |
| phrack_extractor | I don't know how it is encoded to save it | 21:47 |
| justme_ | oerheks just tried even that I knew it wouldnt change anything since my virtualbux webui works so it were loaded | 21:47 |
| justme_ | and still totally same result | 21:47 |
| oerheks | phrack_extractor, this is not the pentest support channel | 21:48 |
| phrack_extractor | Ok | 21:49 |
| justme_ | oerheks but unfortunately the link you gave me won't work ether since that does also rely on having keyboard and screen access to set it at boot | 21:52 |
| oerheks | no, do that, editing grub, after boot and login | 21:56 |
| oerheks | i stop with this, wonky hardware, now you have no access, not even ssh ? | 21:56 |
| gigi | 1234 | 21:59 |
| justme_ | I have access since its the host server there also are main server ( so are on the ssh over the management vpn network ) so I have shell access | 22:03 |
| justme_ | Its just I have no hw access | 22:03 |
| justme_ | since it's vm's on that server there is keep getting stuck at starting and I saw the logs from | 22:04 |
| justme_ | but thwe guide you sent says directly "These settings will ensure that your system boots with the last kernel you chose during boot." and that I won't be able to do since again no hw/kvm access | 22:06 |
| justme_ | oerheks so sorry to ask how would I then set the kernel in the grubfile to the other kernel now the guied sayd set to saved and chose at next boot | 22:14 |
| Tingo | justme_: did you $ sudo update and $ sudo upgrade ? now during upgrade it also has been your kernel ? can you show me Pastebin of it ? | 22:30 |
| Tingo | Normally, it will auto configured your New Kernel in Grub.. and on Reboot it will auto pick new kernel.. | 22:31 |
| justme_ | Yes it were a normal apt update and apt upgrade, and it upgraded the kernel to 5.15.0-116-generic where I were on 5.15.0-113-generic I believe | 22:34 |
| justme_ | yes it did also that and that was messed it all up sunce the virtualbox vm's now won't start on the new kernel and it shows in log as it tries to report my I7 cpu as a I5 to virtualbox but the vbox driver works fine since my virtualbox webui works totally fine | 22:36 |
| justme_ | it's just the vm's gets stuck right away so that is why I try to get back on the prior kernel and sadly does not have HW access so have to do it from ssh | 22:38 |
| justme_ | Tingo what would you like to have the pastebin of? | 22:39 |
| bparker | where can I find a list of supported USB wifi adapters that work out of the box on a stock 22.04 install? | 22:44 |
| bparker | especially stable ones perferably... I have tried 3 different ones already and they either fail to connect or the firmware crashes within a few hours | 22:45 |
| bparker | preferably* | 22:45 |
| Tingo | justme_: you can reboot your VM whenever it startup then press ESC key continuesly .. it will show Grub Menu .. you will see Ubuntu option click on it and then choose OLD kernel from List.. | 22:54 |
| justme_ | But that wont work omg omg It's on the actual HW server I need to roll back since no vm's can start and get stuck at 99% cpu from start after the update. And I have NO HW ACCESS so I can't chose at boot I have to do it from within ubuntu before rebooting | 22:56 |
| xangua | bparker: I'd get a wifi card better, Intel ax210 is what I got | 22:57 |
| Guest7191 | hi everyone | 22:58 |
| justme_ | but it's after this were upgraded that all the issues started with apt upgrade ( just found the log ) https://pastebin.com/dzZCk1i1 | 22:58 |
| oerheks | bparker, maybe the 54mbit ones | 22:59 |
| oerheks | many advanced wifi adapters need firmware, that is undoable on a live iso | 22:59 |
| oerheks | good start https://wireless.wiki.kernel.org/ | 23:00 |
| Tingo | justme_ pastebin the result of this command $ dmesg | 23:02 |
| justme_ | No I'm not posting full dmesg specially a place there is public archived for all time since that is full of personal hostnames, ips etc and miles long and general personal identifiable information. also virtualbox does log to its own files so that does not help | 23:08 |
| justme_ | and specially since its so long a log that it's imposible to censor all | 23:09 |
| Tingo | ok..have to check where it is getting stuck.. | 23:09 |
| Tingo | when did you $ sudo apt upgrade.. it had sucessfully installed all packages ? | 23:09 |
| oerheks | time to get hw access .. bring monitor and mouse 🤪 | 23:10 |
| Tingo | so you meant to say that your all Virtualbox VMs are not Booting normal.. only this Ubuntu left which didnt reboot yet? | 23:11 |
| oerheks | you won' t provide logs, on wonky hardware, so how could we be of help? | 23:11 |
| === linuxman1 is now known as linuxman | ||
| justme_ | I did the upgrade maybe 7 hours ago and everything works excepts ity broke virtualbox after the kernel update | 23:13 |
| bparker | xangua: I can only use USB, sorry | 23:14 |
| justme_ | and it were after the reboot it were aperant that the kernel broke virtualbox ( upgraded 2024-07-22 18:59:20 UTC as seen in the link I posted from what it upgraded ) | 23:16 |
| Tingo | which OS and Virtualbox version is running on Host server ? | 23:16 |
| Tingo | justme_: pastebin this $ cat /boot/grub/grub.cfg | 23:16 |
| justme_ | this is the host we are talking about that the link also is from ( the apt upgrade log ) it's ubuntu 22.04 LTS and I believe virtualbox 6.1.50 headless | 23:18 |
| justme_ | Tingo this is the grubfile from the host server https://pastebin.com/Ch6Lt9UE | 23:21 |
| Tingo | oh, so we are dealing HOST OS which is running Virtualbox, i thought we are talking about Virtual Machine on virtualbox.... | 23:21 |
| Tingo | this command vboxmanage --version will show your Version.. | 23:22 |
| justme_ | the vm's it self are getting stuck right away when started as a result of the kernel upgrade | 23:22 |
| justme_ | and yes its the host machine we are dealing with since it's affecting both windows and linux vm's since its vbox it self there report stuck on the vm's and 99% cpu on them as soon power on is hit on them as in instant. So it is the host there needs to get the kernel rolled back from the upgrade today | 23:24 |
| Tingo | which kernel is it currently showing on this command ? uname -r | 23:24 |
| justme_ | its virtualbox 6.1.50r161033 btw | 23:25 |
| justme_ | its the newest5.15.0-116-generic since the server got rebooted since the kernel update | 23:25 |
| justme_ | and yeah if I only had hardware access I would then just have changed at boot and then uninstalled it | 23:27 |
| Tingo | ls -l /boot | 23:31 |
| Tingo | have to check that all old kernel files... | 23:31 |
| justme_ | https://pastebin.com/FfBKYVuV | 23:34 |
| Tingo | after $ sudo apt upgrade command.. did you also gave command $ sudo apt autoremove ? | 23:35 |
| justme_ | no I never do the autoremove or purge before some days after just in case there is a issue and the version is removed from apt | 23:36 |
| justme_ | so there were only run apt update and apt upgrade and then rebooted since there were kernel update | 23:37 |
| justme_ | and specially since there were kernel update | 23:39 |
| justme_ | Tingo not sure if you lost my answer since saw your client disconnected, but no I did not autoremove or purge since specially when there were kernels then I always wait a few days for that just in case of issues | 23:48 |
| Tingo | back.. Sorry, was away.. | 23:52 |
| Tingo | 2 min | 23:53 |
| justme_ | no worries at all | 23:54 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!