=== chris14_ is now known as chris14
[01:48] <charles> I put a micro sd card in and looking at it with Disks, it says Partition 1 is 32gb GB Fat.   Is that the right format to install Ubuntu onto using the Imager application?
[01:54] <rbox> charles: you should read the documentation
[02:19] <Eickmeyer> rbox: From !guidelines:  "Telling people to "RTFM" or to "just google it" is not very polite. Ideally, you should find them a link, or at least give them some directions to documentation they can use."
[02:30] <loswedseded> has do-release-upgrade been deprecated?
[02:58] <ruser> Good evening, everyone, I did get my system installed and booted, and even snapshotted in zfs.  I did a release-upgrade and now i'm stuck in the rescue mode.  Two questions. First. Is there a way to to launch ssh server?  any attempt to do so drops me right back into maintnenace mode and no daemon.  2. mount reports invalid boot record signagure, failed to read boot sector, and failed to recognize exfat
[02:59] <ruser> type. finally wrong fs type, bad option, bad superblock on /dev/sdv1, missing codepage or helper program or other error.   Prior to do-release-update it worked fine.  What should i try to figure out next?
[02:59] <ruser> whops, i just borked the partition
[03:00] <ruser> i'm going to reinstall but i have a feeling i'll end up here
[03:00] <ruser> or rather i have the old info so i'll return the system to the prior state
[03:03] <ruser> nvm, i didn't do anyting
[03:03] <ruser> My prior two questions stand
=== Rahoul9 is now known as Rahoul
=== JanC_ is now known as JanC
[05:21] <jStefan> join #apache-ws
[05:21] <jStefan> oops
[05:21] <jStefan> sry
[05:22] <jStefan> ... in the wrong net too :(
[09:53] <gordonjcp> this is a bit more generic than Ubuntu-specific but is there a decent parametric EQ that'll work inline with PulseAudio?
[09:53] <gordonjcp> there's pulseaudio-equalizer but that's a graphic EQ
[10:32] <cbreak> isn't ubuntu going away from pulse?
[10:43] <lotuspsychje> cbreak: i think its still in between worlds, some versions still on pulse, newer going to pipewire
=== Vercas6 is now known as Vercas
[12:21] <lorenzo> lorenzo
=== stenno is now known as Guest5049
=== chao is now known as stenno
=== sotaoverride is now known as Guest1925
=== sotaover1ide is now known as sotaoverride
[13:27] <BluesKaj> Hi all
[13:28] <centHOGG> kk
[13:47] <DocMors> is there a way to, preferably automatically, repair a nackered snap installation?
[13:47] <DocMors> or do I better do a full reinstall?
[13:48] <BluesKaj> use a non-snap version if available
[13:51] <DocMors> yes but without it 5 or apps are no longer available, I think I finally jump and find a distro without snaps. I was with Ubuntu for more than 15 years but this I don't want to fight
[13:52] <centHOGG> i use(d) both snap & crossover. Wine capability primarily
[13:54] <BluesKaj> which ubuntu release are you running DocMors ?
[13:54] <DocMors> 22.04
[13:54] <ravage> what error do you get?
[13:55] <DocMors> sudo snap refresh firefox
[13:55] <DocMors> error: cannot perform the following tasks:
[13:55] <DocMors> - Run post-refresh hook of "firefox" snap if present (run hook "post-refresh": cannot locate base snap core22: No such file or directory)
[13:56] <ravage> sudo snap install core22
[13:56] <DocMors> I think the issue is not with firefox but with this core22
[13:56] <DocMors> and gues what that was the first I tried
[13:56] <DocMors> sudo snap install core22
[13:56] <DocMors> snap "core22" is already installed, see 'snap help refresh'
[13:57] <ravage> well. we are not psychic. we dont know what you tried
[13:57] <DocMors> sudo snap remove core22
[13:57] <DocMors> error: cannot remove "core22": snap "core22" is not removable: snap is being used by snaps
[13:57] <DocMors>        cameractrls, cups, gnome-42-2204 and telegram-desktop.
[13:58] <DocMors> same with purge, I tried to apt purge snapd too
[13:58] <ravage> do other snaps work?
[13:58] <ravage> telegram for example?
[13:58] <DocMors> all with reinstall and reboot but totally no joy. I don't find anything that shows me how to manage broken snaps either
[13:58] <DocMors> nope all dead snaps are dead
[13:59] <DocMors> it's this core22 thing and like said I don't find anything how to fix that
[13:59] <ravage> ok so get a list from "snap list"
[13:59] <DocMors> need to calm down
[13:59] <ravage> remove the snaps. it will greate snapshots on remove
[13:59] <ravage> so your data are still there
[14:00] <DocMors> so remove all blovking snaps and then remove / reinstall core22 ?
[14:00] <ravage> i would even remove snapd with --purge
[14:00] <ravage> then install snapd again
[14:00] <ravage> before you reinstall check if /var/lib/snapd/snaps is also empty
[14:00] <ravage> if not remove all files in there too
[14:01] <ravage> you dont have to remove snaps like the core snaps
[14:01] <ravage> only real applications
[14:01] <DocMors> now that core snap is the culprit methinks
[14:03] <ravage> and remove with purge i mean by apt
[14:04] <DocMors> let see whether we get this running again
[14:04] <DocMors> and thka
[14:04] <DocMors> thanks
[14:15]  * DocMors hands a huge cookie to ravage
[14:15] <DocMors> thank god no reinstall
[14:15] <ravage> \o/ nom nom
[14:17] <DocMors> if I wasn't so riled I'd even write up how to get this fixed, there isn't much about it on the web.
[14:17] <DocMors> maybe tomorrow
[15:29] <Ecko> When i apt install php-common, it automatically select php8.2-common. Is this some sort of symlink?
[15:32] <ioria> the ondrej ppa, probably
[16:25] <noent> hey. I'm having some issues with the keyboard settings in Ubuntu 22.04. During installation I set "de (neo2)" as keyboard language, but in a lot of applications it jumps back to normal German keyboard e.g. when pressing ctrl. So I have to press different keys for e.g. ^c which is quite annoying. Iirc there was a bug with Xorg that caused this behavior for all layouts with XkbVariant and there was a work around, but I can't seem to find it right now
[16:25] <sem> Is this page still current? (Bug with fonts blocking the 23.10 upgrade path) https://discourse.ubuntu.com/t/mantic-minotaur-23-10-release-status-tracking/37887
[16:32] <Eickmeyer> sem: Yes.
[16:32] <sem> Thanks
[16:32] <Eickmeyer> sem: Reason being is that 24.04 hasn't yet opened for development, the blocking bug requires it be opened.
[16:33] <sem> I wasn't sure if there was a meeting on monday that was going to address that. Are they going to wait to completely clear the bug before opening the taps
[16:33] <Eickmeyer> sem: Yes.
[16:34] <Eickmeyer> As stated in the bug, the verification of the bug must be completed by verifying with nn (24.04).
[16:38] <sem> I'm just curious, why do they need to make sure it works from mantic -> nn in order to allow lunar -> mantic ?
[16:40] <Eickmeyer> sem: ubuntu-release-upgrader works by downloading from the release being upgraded to and then running within the release being upgraded from. Therefore, they want to make sure it's not broken going nn -> mantic first.
[16:41] <Eickmeyer> sem: All development within Ubuntu works by working in the development release first and then backporting fixes to the next highest release.
[16:41] <Eickmeyer> s/highest release/highest supported release
[16:42] <Eickmeyer> sem: Also, to add to that, there is a planning sprint going on right now, so you really need patience.
[16:43] <Eickmeyer> sem: The developers in charge of ubuntu-release-upgrader are stretched pretty thin.
[16:44] <sem> That makes sense to me to do development that way. The part that is confusing I guess is if it has already been tested and works for lunar -> mantic, why block the upgrade path? Will it introduce problems later if the fix doesn't work for mantic -> nn?
[16:46] <Eickmeyer> sem: The problem is the last test for lunar -> mantic didn't work, and as stated before, the "Fix Released" change happens automatically in the bug tracker and can be a misnomer. This fix requires manual verification to know for certain and *must* be verified by the developer that did the fix using the process they use.
[16:47] <sem> ah ok. There's a comment saying that the fixed packages were in -upgrades and people were unsubscribing from the bug, so I thought it was done
=== de-facto_ is now known as de-facto
[16:48] <Eickmeyer> sem: That is an automatic comment, believe it or not.
[16:48] <Eickmeyer> sem: Or, rather, semi-automated.
[16:48] <sem> Ah, ok, I thought that was someone signing off on the fix :p
[16:48] <Eickmeyer> Nope.
[16:48] <Eickmeyer> It's a semi-automated part of the SRU process.
[16:49] <sem> I appreciate your patience explaining all of this process. I was hoping that 23.10 would fix some bugs on my system, but I will keep waiting patiently
[16:49] <Eickmeyer> The rest of the verification has yet to be completed. When that's completed (as stated in the comment in the bug report), the block will be lifted and upgrades will be enabled.
[16:50] <Eickmeyer> You're welcome. It's a very, very careful process and doesn't usually take this long, but a lot of things went awry close to release this time.
[17:24] <robson-fa> I'm having a problem with OpenVPN, on my Ubuntu 22.04 Desktop. When I connect, using a configured connection to my company, I can access my internal network, but only by IP address, I can't access using the name of my resource. I can see that the IP of my internal DNS is put into the file /run/systemd/resolve/resolv.conf, but it's not working. The
[17:24] <robson-fa> file /etc/resolv.conf is a symbolic link to the file /run/systemd/resolve/stub-resolv.conf, which is not updated with the IP Address of my internal DNS. I changed the symbolic link of /etc/resolv.conf to /run/systemd/resolve/resolv.conf and everything start to work. I'd like to know if is there way to do it works without this change of symbolic
[17:24] <robson-fa> link?
[17:34] <ioria> robson-fa, you might try with openvpn-systemd-resolved
[17:55] <[twisti]> im trying to understand how firewall works on ubuntu (lts 22), and all guides i read refer to ufw, and the first step is usually enabling ufw. does that mean that by default, ubuntu has no firewall activated ?
[17:56] <leftyfb> [twisti]: correct
[17:56] <[twisti]> alright, thanks. i am debugging being unable to access a port, so the firewall config is then probably not something i should be looking at right now
[17:57] <leftyfb> also correct
[17:57] <[twisti]> i just spooled up a blank server install, and ufw status reports inactive, i just wanted to make sure it didnt default to another firewall solution
[18:04] <jStefan> [twisti], did you try something like "ss -tlnp"? and are you trying to reach the port via the internet or local network ?
[18:05] <[twisti]> jStefan: thanks, i solved it already, just when you open a port and cant connect to it from a remote machine, FW was my first go-to to check. turned out kubectl port-forwarding binds to 127.0.0.1 only by default
[18:37] <Dex2x> Hi all, I have samba instance running and my shares are working except for one, I don't see the [share] config in my /etc/samba/smb.conf , I do have a /var/lib/samba/usershares/series file, but this folder doesn't seem to be exposed?
[18:48] <Fishermango> hey guys , I'm using Android 12 and my wifi connection keeps switching between 2. or ghz and 5ghz, breaking downloads and streams. I can't figure out how to set a specific band on Android settings, and i cant modify the router.
[18:49] <ruser> This is an #ubuntu channel?
[18:49] <Fishermango> Great, i can't join android
[18:49] <oerheks> you might need to regeister with libera for #android
[18:50] <Fishermango> i can't
[18:50] <oerheks> !register
[18:50] <ubottu> For information on registering your IRC nick, see https://libera.chat/guides/registration - For any further help, ask in #libera
=== k001 is now known as k000
=== debianero_ is now known as debianero
[20:29] <kai> Evening folks
[20:31] <kai> I can't seem to access the internet from my 22.04 laptop after installing updates earlier today, and I'm a bit stumped how to debug this
[20:32] <kai> I'm connected to WiFi, DNS lookups seem to work, but nothing else
[20:32] <leftyfb> kai: can you ping your router?
[20:32] <kai> Yes, but nothing on the outside
[20:33] <leftyfb> can you ping 1.1.1.1 ?
[20:33] <kai> Tried on multiple networks,  so it's not the router
[20:34] <leftyfb> kai: "ip route" does that show the ip of your router?
[20:35] <kai> Leftyfb: yup
[20:35] <kai> The ping to 1.1.1.1 fails, btw
[20:36] <kai> I'm currently connected to my phone's hotspot, so I'm sure the network connection should work
[20:36] <leftyfb> kai: is this a laptop? Desktop? Server? virtual machine? docker container? other?
[20:37] <kai> A laptop
[20:37] <leftyfb> I would recommend testing being hardwired to your router, wifi if you can't hardwire
[20:37] <kai> And as I said, DNS seems to work
[20:37] <jStefan> the laptop can connect to the internet via the phone's hotspot, but not your wiif?
[20:37] <jStefan> wifi*
[20:38] <kai> No, no matter what wifi network I'm on, no connection
[20:38] <leftyfb> kai: host ubuntu.com 8.8.8.8    # what does this give you?
[20:39] <kai> That times out, but without specifying the Google DNS I get a result
[20:39] <kai> But I assume that's because that's coming in via the router
[20:40] <leftyfb> kai: ok, so DNS is only "working" because your router is probably doing resolutions for you. You can't actually communicate with the internet
[20:41] <kai> That's my assumption, too. I didn't realise that DNS was just screwing with me before
[20:41] <leftyfb> kai: look in your network settings. Make sure you're not using a profile that is set with static network settings. You should be using DHCP for everything
[20:42] <kai> Yeah, I'm on dhcp, otherwise I wouldn't get the right ip,  route,  and DNS settings
[20:42] <jStefan> if it can get dns from the router and nothing else, maybe it's missing a routing rule? and just generating unreachables?? just a guess
[20:43] <kai> ip route shows a default route, though
[20:44] <kai> And if I connect to a different WiFi network, that route updates as expected
[20:45] <jStefan> could another route be interfering with the default route?
[20:47] <kai> No, not that I'd see, no custom routes
[20:49] <oerheks> with weird connection issues; reboot the router?
[20:50] <kai> Not my router,  but I have the same symptoms on four different networks already
[20:50] <leftyfb> kai: sudo iptables -L -n # got any firewall rules ?
[20:51] <kai> I also checked that, no rules
[20:53] <kai> I don't have wireshark installed,  unfortunately
[20:54] <leftyfb> I didn't ask to run wireshark
[20:55] <kai> Yeah, just saying that I'd love to see what kind of traffic I can see on the interface
[20:56] <kai> iptables lists no rules set with the default policy of accept
[21:01] <kai> Hm, I just realised I have an ubuntu desktop iso image  and a USB driv
[21:01] <leftyfb> kai: are you able to try hardwired? Or a different wireless adapter(USB)?
[21:01] <kai> I'll give that a spin to see if it's a config issue
[21:02] <kai> No, no ethernet ports here, and I don't carry a spare adapter
[21:22] <kai> Anyway, thanks for the debugging help, I need to go offline for tonight
[21:43] <kai> Ok, couldn't leave it alone. Wifi works from the live image, so it's a software problem for sure
[22:42] <SeanMatula> Hello everyone!
[22:42] <redlegion> howdy
[22:43] <SeanMatula> I'm having trouble with a MicroOVN install. Anyone know if it works with arm64? It appears the openvswitch service isn't starting after the "snap install", and I think that has to due with loading kernel module.
[22:54] <carpatu> my cpu fan makes a small noise for 5 min when cool at boot time
[22:54] <carpatu> replace?
[22:55] <leftyfb> carpatu: you should ask in #hardware. Ubuntu doesn't make cpu fans
[22:55] <carpatu> thats a good channel thanks