[00:02] <johnny_linux> from what im seeing, you may have to contact tak development.
[00:10] <tomreyn> phyphor: the latest open bug report against squid is from april this year.
[00:11] <tomreyn> phyphor: actually may 22
[00:14] <tomreyn> gneeriiloeepdeer: apparently you can run takc, their command line tool for windows, through wine.
[00:14] <gneeriiloeepdeer> jesus...
[00:15] <gneeriiloeepdeer> will that convert tak to flac?
[00:16] <tomreyn> it will "decode" it, supposedly to wav? most likely not to competing compressed lossless audio format flac.
[00:18] <tomreyn> https://ubuntuforums.org/showthread.php?t=1681489&&p=10429725#post10429725 has a -help output for takc 2.0.0
[00:24] <johnny_linux> gneeriiloeepdeer,  put the file in windows and convert it to another format.. nuff said.
[00:25] <gneeriiloeepdeer> thx tomreyn and johnny_linux
[00:25] <johnny_linux> k
[00:43] <johnny_linux> Its pretty characteristic that we constantly have to define common logic to define simplicity.
[00:43] <johnny_linux> "me"
[00:48] <jhutchins> johnny_linux: "Put the file in Windows".  Windows has not been available here since ~2006.
[00:48] <johnny_linux> I quit "windows" back in 2k
[00:49] <johnny_linux> aka "windoze"
[00:52] <johnny_linux> Technology has to have efforts to internalize to be capable to determanize. .. thats the battle .. most cant sirvive
[00:53] <johnny_linux> survive
[00:54] <johnny_linux> Im almost 80.. we seen t coming with TTL.
[00:54] <johnny_linux> Along with the TRS 80
[00:55] <johnny_linux> on a unstable 5 voly supply that always expolded TTL
[00:56] <johnny_linux> volt
[00:56] <laguna> xtrs in ubuntu packages still runs some old trs80model 1 stuff
[00:57] <johnny_linux> I graduated engineering back yrs ago, we seen it.. i stifle
[00:58] <johnny_linux> I worked for westinghouse in 78
[00:58] <laguna> i worked for radio shack to get the model 1 out to the public
[00:58] <laguna> that was long ago
[00:59] <johnny_linux> I am a retired ham / commercial / police radio repairman.
[01:00] <laguna> johnny i worked for heathkit in the radio days before the model 1
[01:00] <laguna> johnny i also was a ham back in the old days
[01:00] <johnny_linux> heathkit was good
[01:00] <johnny_linux> not accurate .. but good
[01:01] <laguna> johnny yes those were the days of exploring electronic circuits back in the tube days
[01:01] <johnny_linux> kinda like mfj.. total garbage
[01:02] <laguna> johnny woah wrong channel i meant to put these comments in ubuntu-offtopic
[01:02] <johnny_linux> when you can take a vintage yaesu 101ee and make it sng.... then yur a tech.
[01:03] <laguna> johnny yes i remember the yeasu when it first came out to compete with some older collins stuff
[01:03] <johnny_linux> with GE tubes
[01:04] <johnny_linux> one of my friends who started fingerhut started with 1k ram
[01:04] <laguna> johnny i will talk more about the old days in ubuntu-offtopic
[01:04] <johnny_linux> ok.. thanks for letting me blabber.. no worries
[01:07] <johnny_linux> Thanks people for letting me profice.
[01:09] <johnny_linux> NOTE: im retired and like to educate and blabble.. I stifle. thanks.
[01:31] <deego> So, I launch a terminal using M-T, and start typing. Sometimes, that happens before the terminal launches. And, certain keys, such as "a" or "v" launch this nice feature "find files on desktop."  How do I disable this nice feature?
[01:32] <deego> That is, if you type "a" or "v" on an empty desktop, this feature launches itself.
[01:35] <arraybolt3> deego: Sadly, it looks like this feature is part of a GNOME Shell extension that is included by default in Ubuntu, and it offers no way to disable the "find files on desktop" feature.
[01:36] <deego> arraybolt3: thanks
[01:36] <arraybolt3> Sure, sorry that the answer was kinda crummy.
[01:37] <deego> not your fault. thanks for answering
[01:37] <arraybolt3> (My info came from https://forum.manjaro.org/t/pressing-spacebar-on-the-desktop-brings-up-annoying-prompt-i-want-to-disable-this/86044 for what it's worth.)
[01:37] <arraybolt3> (And I have a GNOME Shell extensions manager on my system, thus how I know that the extension exists by default on Ubuntu.)
[01:38] <arraybolt3> (Turning off the feature makes stuff vanish from your desktop though :/ )
[01:38] <arraybolt3> (stuff = my "Home" icon)
[01:38] <deego> ah. thanks! On debian, I use xfce, because i don't want 1000 bells and whistles stealing my shortcuts with every apt install. On ubuntu, still getting used to things.. I'm not sure I should switch yet.
[01:39] <arraybolt3> deego: If you wanted Ubuntu + XFCE, you might check out Xubuntu.
[01:39] <deego> ah, will do
[01:39] <arraybolt3> It's the exact same OS as Ubuntu, but with XFCE rather than GNOME. It's an official Ubuntu flavor and is supported here.)
[01:40] <arraybolt3> (And it has different apps preinstalled, but whatever, you know what I'm trying to say :P)
[01:41] <deego> haha, yes. i'm just .. scared of switching. So much effort put in to make things work with this one.  And, some weird matplotlib/wayland stuff that finally got to a working condition..
[01:42] <arraybolt3> deego: Makes sense. You might try running Xubuntu in a virtual machine just to see what you think first. It runs nicely for me like that.
[01:42] <deego> ++
[02:15] <johnny_linux> good=nite folks. thank you for your time.
[03:02] <ibn-batot> good morning
[03:27] <Soulmadness12> I need to include the following grub modules in x86_64-efi: vbe.mod,vga.mod and ieee1275_fb.mod. I was looking at this script: https://git.launchpad.net/~ubuntu-core-dev/grub/+git/ubuntu/tree/debian/build-efi-images?h=ubuntu#n87 but where is it at?
[06:33] <BlackOps> Is this the original channel from freenode?
[06:36] <Nautilus> I think most chans moved to Libera
[06:36] <nicoz> lol
[06:37] <BlackOps> Wikipedia agrees with you but I wanted to hear it from a human so ...
[06:37] <nicoz> freenode channels are migrated to libera.chat
[06:37] <nicoz> lool :P
[06:38] <Nautilus> been a while since IRCing?  ;)
[06:40] <BlackOps> Just thinking about it a lot. I was using Solaris recently ... I don't understand it fully as not every Linux feature cloned exactly then just thought more and more, hence the question. But I don't want to pull away from topic
[07:01] <JerOfPanic> hi
[07:02] <BlackOps> Hey
[10:25] <LionLinux1> Hi
[10:25] <LionLinux1> I'm trying to randomize my hostname upon every device startup, I can create a systemd service to apply the hostname randomization using a system service, but I need the code to select a random line/word from a wordlist, can someone here help me with the code that says "Pick 1 random line/word from this wordlist.txt"?
[10:25] <LionLinux1> I think the code I got a few days ago was similar to "sudo hostnamectl set-hostname (someprogram 1 wordlist.txt)"
[10:25] <LionLinux1> And basically it would set the hostname to the output of the randomly chosen word from the word-list.
[10:31] <ravage> LionLinux1: shuf -n1  /usr/share/dict/american-english | sed "s/'//g" | tr '[:upper:]' '[:lower:]'
[10:32] <LionLinux1> thats way more complex
[10:32] <LionLinux1> than the code I saw a week ago
[10:32] <LionLinux1> What do you think of this
[10:32] <LionLinux1> 'sudo hostnamectl set-hostname (shuf -n 1 wordlist.txt)'
[10:33] <ravage> it will generate invalid hostnames
[10:33] <ravage> the list includes '
[10:33] <ogra> shuf -n1 /usr/share/dict/american-english
[10:33] <ravage> also i prever lower case hostnames
[10:33] <LionLinux1> What if my list doesnt include '
[10:34] <ravage> if the list includes only valid hostnames you can use just shuf
[10:34] <ogra> yeah
[10:34] <LionLinux1> yeah just words
[10:34] <LionLinux1> andrew, james, etc
[10:34] <ogra> and you dont want sudo in there if it is a service handled script
[10:34] <LionLinux1> ok
[10:35] <LionLinux1> How can I make this .sh script run at startup, before the WIFI interface is brought up
[10:35] <LionLinux1> It has to fully work before WIFI interface is even starting
[10:35] <LionLinux1> So the hostname is set
[10:36] <LionLinux1> I suppose I could set this as a shutdown task too, to run as the PC shuts off
[10:36] <LionLinux1> Then when I boot up, the new hostname is already set from the last shutdown
[10:37] <LionLinux1> And is it shuf -n1 or -n 1 ?
[10:37] <ravage> both works
[10:37] <ogra> try "Before=network-online.target" in your unit file
[10:38] <ravage> https://p.haxxors.com/ksto6q8r.txt
[10:38] <LionLinux1> perfect, thanks
[10:38] <ravage> something like this. but i have not tried it yet
[10:38] <LionLinux1> And would this code function? "sudo hostnamectl set-hostname (shuf -n 1 wordlist.txt)"
[10:38] <ogra> or even before "network.target"
[10:38] <tomreyn> and make sure you're not using / reconfigure services which expect a static hostname to work. such as mdadm raids.
[10:39] <ogra> see https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
[10:39] <LionLinux1> The goal is to randomize my hostname so the WIFI router I connect to sees a new hostname every time I start my PC and connect
[10:40] <ravage> not sure how that helps but if thats your goal so be it
[10:40] <LionLinux1> the goal is network anonymity
[10:41] <LionLinux1> I randomize my MAC addresses for the WIFI chip
[10:41] <LionLinux1> so I also need to randomize my hostnames
[10:41] <ravage> you could just send an alternative dhcp name or none ar all
[10:41] <ravage> *at all
[10:42] <LionLinux1> woah thanks
[10:42] <LionLinux1> can i u help me pls
[10:43] <LionLinux1> 'network-pre.target' looks perfect for setting the random host before boot
[10:43] <LionLinux1> before wifi comes on i mean
[10:43] <ravage> check /etc/dhcp/dhclient.conf
[10:44] <LionLinux1> and then what
[10:44] <ravage> look for "send host-name = gethostname();"
[10:44] <ravage> you could replace that with your random string on boot
[10:45] <ravage> like " send host-name = random123 ;"
[10:45] <ravage> i guess some script with as sed replace would be enough
[10:52] <ravage> LionLinux1, sed "/send host-name =/c\send host-name = `uuidgen | md5sum | cut -c1-12`" /etc/dhcp/dhclient.conf
[10:52] <ravage> you could test with that
[10:52] <ravage> then add -i to to the actual replace
[11:13] <hao> hi, I'm having printer issue and google didn't give me much results. My printer is epson 3255 series, I'm on ubuntu 22.04, and already installed the driver which downloaded from the official epson site (although it seems to me this driver didn't do much, and the printer's description still saying "driverless")
[11:14] <lotuspsychje> hao: did you add the printer in gnomes systemsettings?
[11:14] <hao> the problem is about the print quality, on Mac, this printer have 5 level of printing quality to choose, and the output is very sharp even if I choose level 3. But on ubunut, there is only two option: Normal or High. but even the High option is kinda blurred.
[11:15] <hao> lotuspsychje: how?
[11:15] <hao> I just installed the *.deb driver, and the printer showed up, I thought the driver setup is done
[11:15] <lotuspsychje> hao: systemsettings icon/printers/add printer
[11:16] <hao> trying to run systemsettings, gave me "command not found"
[11:17] <hao> I'll install it then try again
[11:17] <lotuspsychje> hao: systemsettings are default on gnome/ubuntu-desktop
[11:18] <lotuspsychje> the grey gear icon
[11:18] <hao> you mean the "Settings" gui app?
[11:18] <lotuspsychje> yep
[11:20] <hao> it appeared in the printer list, I remember it was detected automactilly (It's a wifi connected printer), and also I remembered I have manually added it, too
[11:20] <hao> is there additional step requried?
[11:21] <hao> I also treid tweak the options in localhost:631
[11:21] <hao> but in localhost:631, it has only two level of print quality,too
[11:21] <lotuspsychje> hao: you see the printer in the list in settings?
[11:22] <hao> yes
[11:22] <hao> It's kinda weird though, cause I actually see two... only one of them is trully usable
[11:23] <lotuspsychje> hao: if it doesnt work properly, you can also click on the printers details to look for ppd file or drivers
[11:23] <lotuspsychje> some cases it ads multiple printers indeed, use the one working
[11:29] <hao> I tried "searching for drivers", it showed something "cpus-filter1.**" at end, but the printer still tagged "driverless". as for ppd file, I don't know what it is, will do some google searching
[11:42] <CptHaddock> Is there any way to boot into a legacy bios from a live USB?
[12:06] <tomreyn> CptHaddock: by "boot into a legacy bios" do you mean "booting an operating system installed in legacy bios mode" or "accessing the bios setup screen"?
[12:07] <tomreyn> generally, what you boot from doesn't change the boot mode. the boot mode is defined by the (uefi?) 'bios' firmware and its configuration.
[12:07] <CptHaddock> tomreyn: Accessing the bios screen. I'm currently unable to get into bios setup using F2 or Del on an Acer laptop.
[12:07] <tomreyn> do you have a multi-boot setup with windows there?
[12:08] <beansncheese> esc on asus
[12:08] <beansncheese> oh acer you said nvm
[12:09] <CptHaddock> tomreyn: No. There was an issue with Windows and I wanted to demonstrate something with the LiveUSB and now can no longer get back into Windows :(
[12:10] <tomreyn> CptHaddock: so that's an ubuntu live usb?
[12:10] <CptHaddock> Yep
[12:11] <tomreyn> you can boot to the bios using:  sudo systemctl reboot --firmware-setup
[12:11] <CptHaddock> tomreyn: aye, I saw that, but I could only get the live usb working by switching to legacy bios from uefi in setup. So the firmware-setup command doesn't seem to work because there's no EFI
[12:14] <tomreyn> CptHaddock: grep -e "^menuentry " /boot/grub/grub.cfg     # Does it list "System setup"?
[12:14] <tomreyn> uh wait you need to do that for the grub.cfg that's on your persistent ubuntu installation, if any
[12:16] <tomreyn> i guess if you can't boot anything in uefi mode then you have quite the catch22 there.
[12:19] <tomreyn> ah here's another approach, that can work (or could break your windows installation, hopefully you have backups):
[12:19] <CptHaddock> tomreyn: Yep, opening the case now to see if I clear the CMOS
[12:19] <tomreyn> sudo mount -t ntfs-3g -o remove_hiberfile /dev/sdb1 /mnt
[12:19] <tomreyn> sudo umount /mnt
[12:20] <tomreyn> this assumes sdb1 is your main windows partition ("Drive C")
[12:21] <tomreyn> CptHaddock: clearing cmos would be my last option - or setting a jumper, which can be less inconvenient. see hardware manual.
[12:21] <tomreyn> good luck.
[12:23] <CptHaddock> Thanks tomreyn. Yes, I don't want to mess with the Windows installation atm. That said, the live USB will allow a dual boot system right? One that doesn't touch the Windows install?
[12:25] <tomreyn> CptHaddock: If you can clean up the windows file system / remove the hibernation file, then the uefi booted ubuntu installer should offer to install next to an existing windows installation.
[12:26] <tomreyn> i would not recommend installing ubuntu ins a different boot mode (legacy bios) than the windows installation.
[12:27] <tomreyn> i do recommend disabling "fast boot / startup" in windows and the bios when you multi-boot. you shuold also fix windows (registry patch) so it will no longer expect the hardware clock to be in local time (but UTC)
[12:30] <CptHaddock> tomreyn: Thanks man. I'm going the CMOS route atm. I'll look into the dual boot option if this doesn't work. Cheers :)
[12:30] <tomreyn> CptHaddock: https://wiki.archlinux.org/title/Dual_boot_with_Windows discusses many of the dualboot problems and how they can be solved.
[12:38] <BluesKaj> Hi all
[12:46] <MrGrymReaper> I have a technical question related to monitors and GPUs, specifically does the current releases of Ubuntu support adaptive synchronization of monitor display output on desktop environments?
[12:47] <MrGrymReaper> The reason being I have a monitor which operates at 144Hz and is adaptive synchronisation supporting so are wondering, how well will it cope under Ubuntu?
[12:50] <MrGrymReaper> So can anyone answer this please?
[12:50] <lotuspsychje> !patience | MrGrymReaper
[13:46] <MrGrymReaper> I also have another but different question, you know of Steam's Proton which is open source on GitHub well has anyone tried creating a varient of the GOG Galaxy snap using it?
[13:56] <orxiuer> hello
[13:58] <orxiuer> anybody?
[13:59] <orxiuer> how are you?
[14:00] <cbreak> fine
[14:01] <seanh> I can't access https://github.blog/ from my PC, with any app. For example `ping github.blog` gives "Destination Host Unreachable". Browsers can't reach it either. Only that domain is affected--other sites work fine. Other devices on the same network can access github.blog just fine. There's nothing in my /etc/hosts file. For DNS I'm using 1.1.1.1. I'm stumped. Any ideas?
[14:07] <seanh> It's not temporary either. It has been broken for weeks
[14:08] <cbreak> dig github.blog ?
[14:08] <cbreak> seanh: do you have some weird routing table setup for 192.0.0.0/8?
[14:09] <seanh> cbreak: I haven't changed anything to do with IP routing deliberately. Where could I look for that?
[14:12] <cbreak> what's the output of `ip route`?
[14:16] <cbreak> (but really, github.blog sounds like some scam URL... I wouldn't trust it)
[14:16] <OerHeks> url is valid.
[14:17] <cbreak> yes... but it's a URL a scammer would use
[14:17] <OerHeks> for unclear connection issues; restart your router?
[14:17] <cbreak> seanh said other devices on the same network work fine... so I suspect something in the routing table to act up
[14:17] <cbreak> ip route should show that... if it's caused by local routing...
[14:18] <cbreak> well, have to make dinner...
[14:19] <seanh> cbreak: Here's `ip route`: https://gist.github.com/seanh/5b93532e6d38a68a080b0fb04417fb6f
[14:19] <seanh> I'll leave IRC connected and check back for any replies later
[14:21] <OerHeks> not worthy to mention docker..?
[14:22] <seanh> OerHeks: could docker somehow be responsible for this?
[14:24] <cbreak> OerHeks: 192.0.0.0/8 dev br-29546c23ecb2 proto kernel scope link src 192.168.43.1 linkdown  // this is the problem
[14:24] <cbreak> sorry, seanh
[14:25] <seanh> I was wondering about that in ip route's output as well
[14:25] <cbreak> check what created that bridge
[14:25] <seanh> I've no idea how I'd check that
[14:25] <cbreak> I have no idea how to do it, but if you remove that routing table entry / that bridge, it should work
[14:26] <cbreak> the other 172 entries are also suspect
[14:26] <cbreak> who ever set that thing up had no regard for the functionality of your network
[14:27] <seanh> The br-* names are making me wonder if my Brother printer driver created these
[14:27] <cbreak> I'd think it's a bridge.
[14:28] <cbreak> bridge link show
[14:31] <seanh> cbreak: `bridge link show` outputs nothing
[14:32] <tomreyn> seanh: try this:   sudo grep -Fra br-29546c23ecb2 /etc
[14:33] <cbreak> maybe they're stale entries from something :/
[14:34] <cbreak> did you ever use something like docker, lxc, or some vpn that might set up a bridge for some reason?
[14:34] <cbreak> (although docker's / lcx's bridges look different here)
[14:34] <seanh> tomreyn: nothing
[14:35] <seanh> cbreak: I do use Docker for development, yes
[14:35] <cbreak> bridge fdb show shows a lot more... not sure what those mean though
[14:36] <seanh> Yeah `bridge fdb` gives more detail but none of it means anything to me
[14:37] <tomreyn> what does    docker network ls    print?
[14:37] <seanh> I have some `docker0` bridges and a lots of these `br-*` ones
[14:38] <seanh> Here's `docker network ls`: https://gist.github.com/seanh/aabeec0099aff472912f0d69ef51d94c
[14:40] <seanh> I guess I could just try deleting these routes with `ip route del`
[14:40] <tomreyn> seanh: note how those IDs match the IDs of your bridge interfaces
[14:41] <tomreyn> so apparently those bridges are managed by docker
[14:41] <tomreyn> you'll want to get rid of or redefine the "sparky_spark_net" network allocation in whatever you use to manage docker
[14:43] <seanh> Ok, so the 192.0.0.0/8 bridge (which I think is the one that's blocking github.blog) is 29546c23ecb2 which corresponds to a Docker container from a project called Sparky, which is one of my work projects
[14:43] <seanh> It's Docker Compose I think
[14:44] <tomreyn> 192.0.0.0/8 spans both public and private ip address ranges. configuring this for internal use is wrong in the first place.
[14:45] <tomreyn> it also overlaps with your LAN's address range, making it even worse
[14:45] <seanh> tomreyn cbreak: Thanks, I took down the Sparky project's Docker Compose containers and now I can load github.blog again. I'll report the issue to the project's developers
[14:46] <seanh> This was the docker-compose.yml file responsible: https://gist.github.com/seanh/fc8cfb4a016765bcb1496b6457331ce6
[14:46] <seanh> I don't know Docker Compose networking but lots of 191.168 stuff in there
[14:47] <tomreyn> line 9 should have said 192.168.43.0/24
[14:48] <seanh> tomreyn: Thanks, I have no idea what that means but I'll add it to the issue report that I'm writing
[14:49] <seanh> It's a private GitHub project so I can't share the issue unfortunately
[14:51] <tomreyn> you could read up on network segmentation and RFC1918 sometime.
[14:52] <seanh> tomreyn: Thanks for the pointer
[14:56] <seanh> tomreyn cbreak: Here's a copy of the internal issue report that I wrote up: https://gist.github.com/seanh/d2f1417c407ece0a8e7cd3b0d5915e75
[14:56] <seanh> Huge thanks for this, it has been bothering me for weeks!
[14:56] <seanh> And now I can warn others off installing this project until we get that fixed
[15:01] <tomreyn> seanh: your issue report should be fine to explain to someone who is into basic networking segmentation and understands private / public IPv4 address ranges what the problem is. And hopefully someone in your org understands those basic principles. there is also #networking and probably #docker if you folks have more questions on these topics.
[15:04] <seanh> tomreyn: Thanks!
[15:06] <cbreak> seanh: https://en.wikipedia.org/wiki/Reserved_IP_addresses
[15:06] <tomreyn> i don't know much about docker networking, but would hope that it has a way to automatically choose a suitable (unused) RFC1918 subnet for a given project (during docker-compose). the fixed subnet allocation as it's done in this docker-compose.yaml file will certainly cause problems for one or the other user.
[15:07] <seanh> tomreyn: Not an expert myself either but at a glance that looks to me like we're doing something totally dodgy/wrong in order to try to connect the Docker containers together when I believe Docker Compose already sets them up to be able to access each other by default
[15:09] <tomreyn> https://github.com/docker/compose/issues/4336 seems to suggest that specifying a fixed address range for a project should not be done, and instead docker should pick a suitable range by whatever means it has for this purpose.
[15:10] <tomreyn> see also https://stackoverflow.com/questions/46845381/how-do-configure-docker-compose-to-use-a-given-subnet-if-a-variable-is-set-or-c
[15:12] <seanh> Added those links to the issue report
[15:28] <squarecircle> stupid question: how do I debug my port forward? I get a connection refused, though ipv4_forward is activated and the iptables rule worked before
[15:28] <squarecircle> :/
[15:33] <squarecircle> iptables -L -t nat als shows
[15:34] <squarecircle> DNAT       tcp  --  anywhere             anywhere             tcp dpt:22222 to:192.168.100.2:22
[15:34] <squarecircle> so, should be working
[15:45] <arraybolt3> squarecircle: I don't know much about this sort of networking stuff, but are you sure that there's not something else in your network messing things up, like double NAT or something?
[15:48] <squarecircle> arraybolt3: If I guess correct, then no. Theres no NAT anywhere, except the machine I want to forward ports on
[16:25] <jhutchins> squarecircle:  http://tldp.org/HOWTO/IP-Masquerade-HOWTO/
[16:25] <jhutchins> squarecircle: I think you may need an ACCEPT rule.
[17:42] <squarecircle> jhutchins: accept rule it was
[17:43] <squarecircle> jhutchins: thx :)
[17:46] <jhutchins> !+
[18:45] <hao> is there a good guide on how to build your own kernel? with all those config options, how could I know which ones to choose to build the slimest kernel?
[18:46] <hao> I have the <linux kernel in a nutshell>, it's too dated. can someone recommend some link?
[18:46] <bougyman> Are you building for an embedded device or something?
[18:46] <bougyman> I mean, what's the reason for doing this?
[18:47] <hao> general interest... I'm determined to learn the deep secret of linux kernel :D
[18:47] <bougyman> Ah, I get it.
[18:48] <bougyman> just go through the config menu, hit every single thing there, read the docs on the options, and disable all of them you think you can get away with.
[18:48] <bougyman> Rinse, repeat.
[18:48] <hao> okay....
[18:48] <bougyman> There is not doc that can replace that experience.
[18:48] <bougyman> *no doc.
[18:48] <hao> seems the right hard way to go
[18:57] <tomreyn> hao: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[19:01] <projjalm> Hello, don't mind this message. I'm testing irssi
[19:04] <hao> tomreyn, thanks
[19:09] <linsux> lenovo y530 cannot wake up from suspend
[19:09] <linsux> gui is frozen
[19:09] <linsux> had to press ctrl alt f2 to cml
[19:22] <jhutchins> hao: Building your own stripped kernel is the hard way to go to begin with.
[19:22] <jhutchins> hao: It's still really worth it to see what all the things the kernel does, and what modules do.
[19:23] <MonoL> Is this an appropriate place to express my joy and appreciation of snaps?
[19:23] <jhutchins> hao: If you turn on verbose text for booting you'll see a lot of un-necessary stuff being loaded or tried to load and failed because there's no hardware there.
[19:23] <jhutchins> MonoL: Probably not.
[19:23] <ravage> MonoL, #snappy
[19:31] <saltd> MonoL this is windows related channel only
[19:57] <arraybolt3> saltd: Please don't spread misinformation, this is the **Ubuntu** tech support channel. Windows stuff is over in #windows I believe.
[20:02]  * saltd [OK] Stopping misinformation ...
[20:29] <enigma9o7[m]> Do packages in universe get security updates?  Or only main?
[20:30] <Habbie> the short summary is "don't count on anything in universe"
[20:45] <mrec> in snap packages are IPC, shared memory and eg. unix domain sockets shared with the host?
[20:46] <ravage> mrec, sounds like a question for #snappy
[20:48] <mrec> ravage: thanks!
[21:42] <hays> can i use ufw to forward port 8443 to 443
[21:43] <hays> i find scant info on the internet that this is possible without using iptables
[21:46] <EriC^^> hays: you should be able to, ufw is just a front for iptables
[21:47] <hays> it seems like i can forward a port without changing the port number
[21:47] <EriC^^> hays: https://serverfault.com/questions/238563/can-i-use-ufw-to-setup-a-port-forward
[21:48] <hays> heh, yeah... so iptables
[21:49] <EriC^^> below it mentions something about having it after ufw 0.34 or something
[21:49] <BlackOps> UFW is da shit!
[21:50] <BlackOps> Sorry - had to say that. It's a light footprint, it installs real fast, and it's so much simpler than Windows firewalls
[21:50] <BlackOps> Carry on - I won't make more noise
[21:55] <eelstrebor> i'm going to have to find a new browser for linux - firefox keeps crashing
[21:59] <jhutchins> hays: iptables is what does the forwarding.  That's like saying you want to run linux without loading the kernel.
[21:59] <hays> isn't ufw a front end to iptables
[22:00] <jhutchins> hays: Yes.
[22:01] <hays> so it seems like to do this i need to edit a file rather than issue a command
[22:02] <hays> e.g.  /etc/ufw/before.rules
[22:05] <jhutchins> !ufw
[22:06] <jhutchins> hays: I dunno, I always just wrote iptables rules and used one of the methods of saving and applying them.   UFW does the same thing, but with a wrapper.
[22:07] <hays> yeah. my bind is that if i want to use ufw, it appears im put in the position of interactively editing a file
[22:07] <hays> so maybe i can't use it for this use case, since this is easy to do non-interactively
[22:07] <hays> with iptables
[22:19] <Guest75> Hi fellows. Is this chat the adequate local to ask for help from "sudo do-release-upgrade"?
[22:21] <Bashing-om> Guest75: Yes - state the issue.
[22:22] <Guest75> Thanks Bashing-om!
[22:23] <Guest75> I have a dell inspiron with system in a ssd and home in hdd. I searched about how update 20.04 to 22.04, but this was fruitless.
[22:24] <enigma9o7[m]> If sudo do-release-upgrade is failing, it's probably good idea to share the full output in a pastebin (i.e. paste.debian.net) for us to look at.
[22:24] <Guest75> after sudo do-release-upgrade in terminal, opened from nautilus, I receive these error messages.
[22:25] <Guest75> oh. great! I will post the outputs...
[22:27] <Guest75> http://paste.debian.net/1254304/
[22:39] <Guest7512> http://paste.debian.net/1254304/
[22:43] <Bashing-om> Guest7512: I can not make much of the trace - what shows ' sudo apt update ; sudo apt upgrade ' ?
[22:44] <enigma9o7[m]> first `export LC_ALL=C`
[22:44] <Guest7512> All fine. I have did these before and all is updated. 'do-release-upgrade"
[22:44] <enigma9o7[m]> that'll set your terminal english til you exit
[22:44] <enigma9o7[m]> make it easire for us to understand
[22:45] <enigma9o7[m]> Hmmm.
[22:49] <Bashing-om> Guest7512: Then does ' sudo dpkg --configure -a ' say that the package manager is happy happy ?
[22:49] <Guest7512> thanks enigma9o7[m]! but "export LC_ALL=C" didn't put results in english
[22:50] <enigma9o7[m]> weird
[22:50] <enigma9o7[m]> I thought it did.
[22:50] <enigma9o7[m]> Just ignore me then.
[22:51] <Guest7512> "sudo dpkg --configure -a" fine
[23:01] <Zepeler> Now I enter via a client. My problem, I suppose, is related to ubuntu instaled in a SSD and Home in a HDD
[23:02] <Guest7512> Zepeler is the same gues...
[23:11] <Zepeler> This is my output of "user@user:/$ sudo do-release-upgrade. I trying upgrade from 20.04 to 22.04.
[23:11] <Zepeler> http://paste.debian.net/1254304/
[23:14] <arraybolt3> Zepeler: I wonder if setting the system to display only in English would fix it? I see that the error seems to be related to a Unicode something-or-other.
[23:16] <Zepeler> Sounds good @arraybolt3. I will change language system.
[23:27] <arraybolt3> Zepeler: Just FYI, you may want to back up all of your data real quick. You should usually do this before trying to upgrade your system.
[23:27] <arraybolt3> (Make sure to get any passwords saved in your browser or password manager, if you use features like that)
[23:28] <arraybolt3> (FYI = for your information)
[23:28] <OerHeks> and test your backups.
[23:28] <Zepeler> Now, in english...
[23:28] <Zepeler> http://paste.debian.net/1254305/
[23:30] <OerHeks> did you run a proper apt update before? new lists
[23:31] <Zepeler> thanks @arraybolt3. I made backup today.
[23:31] <arraybolt3> Zepeler: Can you run "cat /etc/apt/sources.list | nc termbin.com 9999" in a terminal, then send the link that command outputs?
[23:34] <Zepeler> https://termbin.com/89za
[23:35] <arraybolt3> (It's getting hung up on some file not being found I can see, but the file that isn't found looks like it ought to be being created, so it might be related to the non-standard partition layout like Zepeler thought initially. Not sure.)
[23:35] <Zepeler> @OerHeks. Thanks. sudo apt-get update is fine.
[23:35] <BlackOps> Who has any advice on how to check for memory corruption or suspicious memory share other than using memstat?
[23:36] <BlackOps> *rkhunter has given me a warning
[23:36] <OerHeks> memtest86
[23:37] <BlackOps> Oh, I should have typed that as well
[23:37] <BlackOps> But that's for memory corruption. I need to find out which process is secretly eating memory or detect a rootkit
[23:37] <BlackOps> Of course, if it's at the firmware level, that gets real hard and scary
[23:38] <arraybolt3> BlackOps: Did you do anything in particular that would give you cause to think that a rootkit may have been installed (i.e., installed software from an untrustworthy source, or left your system alone where a malicious user had physical access to it)?
[23:38] <OerHeks> but you run debian
[23:39] <BlackOps> Yes ... strange input/output behavior, some of which I have fixed but it's anomolous
[23:39] <BlackOps> *anomalous
[23:40] <BlackOps> I think I fixed some of it with imwheel ... You can do a man of that program after installing it with sudo apt install imwheel -y and it is a cool program. But I'm still seeing things that don't add up. A user made an offhand comment as a joke but when I thought about it ... him insinuating playfully that I've been hacked, I started getting
[23:40] <BlackOps> paranoid. Could just be in my head
[23:40] <BlackOps> I ran a who and there's not a suspious user  on my host
 command
[23:41] <arraybolt3> BlackOps: Oh dear. I highly suspect that a BIOS-level rootkit isn't the problem, due to the high effort and low payoff such a rootkit would take to run, but if malware is installed on your system, the best course of action is a full wipe and reinstall. That's the only near-guaranteed way to remove malware.
[23:41] <arraybolt3> If you already have backups, that's best, if not, you can make a backup and then try to recover the data from it later (hopefully without bringing back the malware).
[23:42] <BlackOps> Yes, I have Clonezilla backups
[23:42] <BlackOps> But if I do that, I can't study the behavior as it will be eradicated
[23:42] <BlackOps> I apologize if I am not helping by mitigating advice. Just  trying to think it through
[23:43] <arraybolt3> BlackOps: I see what you're saying. However, studying the behavior is likely not in your best interest. Malware analysis is an advanced job, malware eradication is all you should be worried about unless you work as a malware analyst (in my opinion, anyway).
[23:43] <BlackOps> I'm in /var/log from rkhunter
[23:44] <BlackOps> I have a master's degree in cybersecurity
[23:44] <BlackOps> I know how to study it ... I just thought, well, I'm using Ubuntu. There might be a security expert in here too
[23:45] <arraybolt3> BlackOps: Oh. Well if that's the case, then malware analysis is exactly what you want to do. I don't know enough to have good advice there, sadly. I think there's some file that gives you full access to the entire RAM of the system somewhere though (kcore?).
[23:45] <arraybolt3> (I believe it only exists if Secure Boot is disabled. And obviously it requires root privileges to access.)
[23:45] <arraybolt3> Lemme see if I can find it...
[23:45] <BlackOps> Yes ... it's also scrary. I created a trojan the other day and it escaped the VM files and into the host from the guest
[23:45] <BlackOps> But I won't go off topic
[23:45] <BlackOps> Carry on
[23:47] <arraybolt3> BlackOps: I think /proc/kcore is the file that gives you full RAM access.
[23:48] <BlackOps> Perfect - that's exactly what I was looking for, to the 'T'
[23:48] <arraybolt3> As for how to *parse* that mess, no clue, but there it is.
[23:48] <BlackOps> Looking for size discrepancies
[23:48] <BlackOps> https://unix.stackexchange.com/questions/243239/why-is-the-size-of-proc-kcore-file-so-bigger-than-the-physical-memory-size