=== furry is now known as fur === DubPirate0 is now known as DubPirate [00:03] ? === DubPirate5 is now known as DubPirate === chris14_ is now known as chris14 === ubuntu is now known as Guest136 [03:16] not even SASL.. === chris14_ is now known as chris14 [05:41] hello [05:42] anyone alive? [05:45] Was there a mass extinction event I'm not aware of yet? [05:46] i cant get the app store to work on ubuntu [05:46] the categories are blank [05:46] gnome-software or the snap store? noble or jammy? [05:47] Ubuntu Software [05:47] That must be frustrating. I'd try patience, and in the meantime until it works right use apt. [05:48] i may either reinstall ubuntu [05:48] or switch to VoidLinux [05:48] i like my wobbly windows though, on ubuntu [05:48] Well that sounds serious. Is this is a consistent problem, or only happening now? I've certainly seen that with gnome-software, sometimes it's really really really slow to do stuff, seems like nothing happening. [05:49] But I thought the new snap store was a completely rewrite in flutter or something and not so flakey. [05:49] I have never used the app store [05:49] hmm [05:49] im new to linux [05:49] so i cant really speak [05:49] not even sure how to find it [05:50] Well it may be in your menu under ubuntu software? [05:50] which used to direct to ubuntu's version of gnome-software on older versions of ubuntu, but then to a snap of gnome-software, and my understanding is on current versions a whole new app store. [05:52] so how do i fix this? [05:53] can i reinstall the app store with the terminal? [05:53] "Ubuntu Software" [06:04] shadowhawk, sudo snap refresh snap-store [06:46] partay === Alpha is now known as Guest9185 === Guest9185 is now known as Alpha [08:27] https://imgur.com/kpTulHE [08:28] I am using Ubuntu 24.04LTS. I use to see an orange highlighted light sometimes when i minimize my browser firefox. Any solution please. Kindly find above link of image [09:12] jaco strange, it's not in any other app? [10:48] Is is possible to postpone popups from programs and system until I have stopped typing? [10:51] So what I would like to is to give priority to the human interface I'm actually using and have other processes that request attention to wait patiently until I am done with interfacing, maybe with a 5-second delay. === PasiZ5 is now known as PasiZ [13:25] Im having problems running snap-store-proxy on 22.04, the nginx part of the snap refuses to launch [13:30] what's the deal with ubuntu pro and will it cost me money? [13:30] Snap store requires a web certificate [13:31] ubuntu pro? [13:31] !pro | JoeLlama [13:31] JoeLlama: Ubuntu Pro is a service offered by Canonical for expanded CVE patching, ten-years security maintenance and optional support. Anyone can use Ubuntu Pro for free for personal use on up to 5 machines. For details please see https://ubuntu.com/pro and https://discourse.ubuntu.com/t/ubuntu-pro-faq [13:32] oh ok ravage [13:33] is ubuntu pro a good thing? downside? [13:34] Mostly on the plus side like access to a real-time kernel [13:34] (on x86) [13:39] oh okay [13:39] access as in real-time operating system younder? [13:39] https://ubuntu.com/real-time [13:40] * JoeLlama likes www.micrium.com although the RTOS is now every expensive [13:40] sweet I read up thanks younder [13:58] when gnome-shell (xsession?) gets setup in ubuntu is there normally some mechanism to setup dbus? [14:03] Gnome shell is just a shell. It has no relations to dbus [14:04] D-Spy is the best way to see what is going on dbus [14:05] (Linux bash is nothing like powershell) [14:10] does restarting ssh.service reload sshd_config in 24.04? [14:12] sshd.service ssh is the client [14:13] younder: I don't have any sshd.service :/ [14:14] younder: ssh.service is the name of the ssh daemon [14:14] grolongo: yes [14:14] grolongo: you can also use sudo systemctl reload ssh [14:15] alright let me check [14:16] sorry rechecked myself and found that it does [14:18] leftyfb: but does it reload the sshd_config? I did both "systemctl restart ssh.service" and "systemctl reload ssh" after setting "PasswordAuthentication no" in my sshd_config and I'm still able to login with a password. [14:18] yes [14:19] that's odd then [14:19] grolongo: egrep -v -- "#|^$" /etc/ssh/sshd_config | nc termbin.com 9999 [14:20] this will post your sshd_config to termbin.com for us to see [14:20] security? [14:20] younder: what about security? [14:21] whats a good way to browse files in your terminal thats not cd and ls? some interactive tool. do people use that or are u just using cd and ls etc? [14:22] magga: good = ls and cd. An alternative is midnight commander. The package and binary is called mc [14:22] ok :) [14:23] leftyfb: https://termbin.com/n6d9 [14:24] hm, why do you have so many things uncommented? [14:25] these are defaults for the most part [14:25] not in Ubuntu they're not [14:26] ubuntu certainly doesn't set UsePAM to no [14:27] grolongo: what linux distro are you running? [14:27] ubuntu 24.04 [14:27] true usepam is yes by default [14:27] and you have it set to no [14:28] I definitely don't need PAM since I'm using a key [14:28] grolongo: what are you trying to accomplish exactly by making all these changes to the sshd_config beyond disabling keyboard auth? [14:29] key based auth solely [14:29] nothing works even after hardening the conf [14:30] that's why I'm not even sure restarting ssh.service reloads the config [14:30] grolongo: because you have made changes you don't fully understand. Put it all back and just disable keyboard auth [14:30] I should try by changing the port to see if that changes anything [14:30] younder: well, the gnome apps apparently require access to dbus so i assume that when gnome-shell starts is when the dbus session address gets set. [14:31] grolongo: disabling PAM auth will not allow you to login as a linux user, regardless of how it's authenticated [14:31] grolongo: put it all back [14:31] It works on my machines and I only set 'PubkeyAuthentication yes' and 'PasswordAuthentication no' [14:31] younder: he disabled PAM auth. That's the issue [14:32] I figured as much [14:32] if it's not using PAM, where is it getting the user from [14:32] grolongo: put your sshd_config back to default and just disable password auth [14:32] so back to defaults and do what I did and it should work [14:32] that will be "hardened" enough [14:33] So what I would like to is to give priority to the human interface I'm actually using and have other processes that request attention to wait patiently until I am done with interfacing, maybe with a 5-second delay. [14:33] I'm running Ubuntu 24.04 [14:34] Nitrigaur: what? [14:35] leftyfb: switching back UsePAM to yes and restarting sshd still let me login with a password [14:35] (Ubuntu has a close integration with Samba to allow hybrid integration with Windows and I thing disallowing PAM auth breaks something) [14:36] leftyfb, I hate being interrupted by system popups while typing in a program. Is there a way to configure the system so it waits until there has been no HID input for 5 seconds? [14:37] grolongo: https://paste.ubuntu.com/p/QZdX9cxqCg/ this is all you need. Comment out the rest [14:37] leftyfb: thats what I thought, even changing the default port to something like 34700 and reloading the ssh service has 0 effect. [14:37] Nitrigaur: that sounds VERY non-trivial. Maybe just disable notifications in settings [14:38] so there is something wrong with the ssh/sshd service [14:38] grolongo: not unless you've modified it [14:38] all I changed is the sshd_config that's all [14:38] grolongo: journalctl -u ssh -S today | nc termbin.com 9999 [14:39] I'm guessing something in your config is invalid [14:39] and I've used that exact same sshd_config that I linked you on debian machines without problem [14:39] ok wait [14:45] grolongo: also, you haven't used that same exact config on Debian and been able to authenticate using a key to a linux user account. UsePAM is what allows you to auth to linux user accounts. If you disable that, the only way you're logging in is if you setup users within the ssh config. [14:45] leftyfb, Yes, I understand that it's probably quite hard to configure that, if even possible with the present Desktop Environment ( I use Gnome right now ). I just thought this would be quite fitting for an environment that is centered around serving the user, but not getting in his/ her way. Maybe I should discuss this with the KDE team, since they are actively asking for what users would like to see in a new version [14:45] of KDE. afaik, Gnome is much more closed to that. [14:48] Sounds like you mind is made up. Personally I prefer Gnome. [14:53] leftyfb: I did though. I only use SSH keys to login, never needed to have UsePAM enabled. [14:54] younder, I like both Gnome and KDE. And I've been using Gnome as my daily driver since Warthy Warthog ;-). It's just that the Gnome team keep very much to themselves in comparison with the team behind KDE. What I like about Gnome is it's simplicity, but on the flipside, I find that many features should have been part of a settings window and not delegated to Tweaks or third party plug-ins. But it's hard to keep a [14:54] balance between serene and configurable. [14:56] grolongo: sudo cp /usr/share/openssh/sshd_config /etc/ssh/sshd_config && sudo sed -i 's/^#PasswordAuthentication.*/PasswordAuthentication no/g' /etc/ssh/sshd_config && sudo systemctl restart ssh [14:56] I'll copy the default sshd_config and start from scratch with the most minimal tweaks [14:56] grolongo: start with only disabling PasswordAuthentication [14:56] yep, will do that [14:56] the command I posted will do that for you [14:59] hi ubuntu auto mounts filesystems attached via usb. how can I disable this functionality momentarily? [15:00] imi: https://unix.stackexchange.com/questions/333721/how-to-stop-auto-mounting-of-devices-in-ubuntu [15:00] thanks [15:03] I think the BIOS is much underestimated here. I use it to disallow boot from unauthorized devices and set a BIOS password [15:03] leftyfb: nothing change. I can still login with user/password like "ssh grolongo@foo" enter password and it works. [15:04] grolongo: egrep -v -- "#|^$" /etc/ssh/sshd_config | nc termbin.com 9999 [15:04] leftyfb: I even changed the default port and restarted ssh service and it still allows without specifying -p 22222 [15:05] grolongo: ( egrep -v -- "#|^$" /etc/ssh/sshd_config ; journalctl -u ssh -S today ) | nc termbin.com 9999 [15:06] What you really want is to prevent access to your system, 2 things have to happen 1. You need to prevent anyone for changing your BIOS settings except you, the passower. 2. You need to make sure your data isn't just copied, so encrypt you drive, LUCS. [15:06] leftyfb: https://termbin.com/jxkv [15:06] younder: lets stick to providing support that people are asking for [15:06] sure [15:07] grolongo: do you have anything in /etc/ssh/sshd_config.d/ ? [15:08] leftyfb: you nailed it [15:08] it does look like the UsePAM setting is different in 24.04. It does work disabling it in 22.04 [15:08] I have a 50-cloud-init.conf file with a single line "PasswordAuthentication yes" in it :s [15:09] that doesn't explain the port change [15:09] indeed [15:09] let me change that file first to see what happens, I don't know where does that come from [15:10] grolongo: this is a container or cloud instance? [15:11] the cloud image has that in there by default [15:12] I have pihole running in a docker container that's all [15:13] my machine is a laptop running as a server on my local network [15:13] ubuntu 24.04 installed bare metal [15:14] I haven't installed 24.04 onto bare metal yet. They might be using the same cloud image by default [15:14] to be precise it's the ubuntu server image, not the ubuntu desktop one [15:15] right [15:15] I'm not sure if that file is here by default or if something put it there after [15:15] let me check real quick on my other vm [15:16] it is [15:18] have to head out now [15:18] no problem thanks for the help! [15:28] thx leftyb, take care :-) [16:00] I have 24.04 on my systems all around. [16:01] grolongo: did you get you sshd to work? [16:03] I had to get the shops before they closed. === tomaw_ is now known as tomaw === seanh1 is now known as seanh [19:23] how does ubuntu start up so fast? [19:23] what dark magic does it do [19:24] I'm building a distro and I want my distro to start fast too [19:24] welcome [19:24] > how does ubuntu start up so fast? [19:24] magic [19:24] :scream: [19:24] LOL [19:25] breh [19:26] there tons of reasons [19:26] like boot manager, init systems and etc etc [19:27] Ooo! does it have some kind of precaching like Windows Fast Startup? [19:27] because like after the kernel finishes loading the bootanimation just display like 2 frames and it boots GDM immediatly [19:27] hmmm [19:27] are you creating a distro based debian? [19:27] You probably have fastboot enabled in bios :p [19:28] hm no, I'm using alpine as a base [19:28] fur: yeah x3 but Ubuntu is the only distro that starts up this fast [19:28] not even Windows starts up this fast [19:29] becasue windows is overbloated by micro$oft [19:29] it's true but win 8.1 start fast [19:29] https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1869655 [19:29] -ubottu:#ubuntu- Launchpad bug 1869655 in Plymouth "Boot animations start too late to be useful" [Unknown, New] [19:29] grin [19:30] this is a fun bug report, like bug #1 [19:30] -ubottu:#ubuntu- Bug 1 in Ubuntu Malaysia LoCo Team "Microsoft has a majority market share" [Critical, In Progress] https://launchpad.net/bugs/1 [19:30] sorry, your system is too fast [19:30] Suser91: win 8.1 was the least usable version but also the last to not be a spyware [19:30] indeed for sure [19:30] Which is probably the reason it was booting so fast [19:31] btw. Linux Mint revived my old laptop ) all works fast [19:31] mint is offtopic here [19:32] JenyaRus nice [19:32] technically still ubuntu :) [19:32] :) [19:32] for of ubuntu yes :) [19:32] fork* [19:32] well [19:32] ubuntu without snaps [19:33] yesterday I had this weird issue with my Ubuntu install where I was receiving like 1 Mbps down and 600 up, it's supposed to be 600 up and 600 down. This morning I checked again and the issue fixed itself lmao [19:33] brazilian isp moment [19:35] oh yeah I'm from Brazil [19:35] !discuss | aragubas fur JenyaRus Suser91 [19:35] aragubas fur JenyaRus Suser91: Want to talk about Ubuntu, but don't have a support question? /join #ubuntu-discuss for non-support Ubuntu discussion, or try #ubuntu-offtopic for general chat. Thanks! [19:35] oh alrighty! [19:36] okay [19:36] good point [19:36] ok [19:55] I have installed two apps with pipx, I wanted to upgrade today with upgrade-all, but it said: No module named pip, As if it can't find pip in the virtualenv anymore.? [19:59] pipx upgrade-all [20:00] pipx ensurepath # would make it discoverable [20:00] https://itsfoss.com/install-pipx-ubuntu/ === silvano is now known as strongholds [21:09] oerheks: pipx upgrade-all gives this error message: No module named pip for each appp that should be upgraded. pipx ensurepath : 'is already in PATH.' [21:19] i see a few topics, but no solution https://stackoverflow.com/questions/76499565/python-does-not-find-module-installed-with-pipx [21:20] cant you just re-create that venv? [21:20] maybe it got broken by python3 update? [21:38] managing something as simple and crucial as openssh which has been working fine for decades is now a total nightmare thx to the systemd socket implementation in 24.04. amazing. === JanC is now known as Guest737 [21:41] grolongo: https://p.haxxors.com/xs525c53.txt [21:42] you may need to reboot once [21:43] ravage: thanks for the tip. this is insane. [21:45] grolongo: what's a "nightmare" about it? [21:46] change is hard [21:50] gordonjcp: go have fun trying to change something as simple as your sshd port [21:50] see https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189 [21:51] ravage: so [21:51] sshd_conf changes are ignored [21:51] ravage: the way it works now, it works like oldschool inetd? [21:52] i did not complain about anything here. just pointing out the change [21:53] ravage: the instructions in there seem pretty straightforward tbh [21:53] that is correct [21:53] you cannot not complain when something was working fine for decades and suddenly breaks for no reasonable reason [21:53] ravage: change it in the appropriate config file so that systemd which is working like xinetd knows where to look [21:54] grolongo: yeah, but the way it works now, Unix services have worked like that for ~50 years [21:54] so [21:54] please stop mentioning me [21:54] im dont with this topic [21:54] *done [21:54] it is in the releasenotes? [21:54] ravage: I'm just saying I prefer the way it works now, and thank you for linking to that helpful document [21:55] "change it in the appropriate config file" so sshd_config right? that should be the only config file you need to tweak for ssh. [21:55] grolongo: but sshd isn't even running at that point [21:55] grolongo: have you ever used inetd? [21:55] https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890#more-consistent-application-of-openssl-and-gnutls-system-configurations [21:55] it is in the release notes [21:56] https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890 [21:57] you changed port, tried to restart ssh, but not networkmanager or changed netplan? [21:58] oerheks: yes, that should have been it right? change port in sshd_config, restart ssh service. that's it. like everybody was doing for that past two decades. [21:59] grolongo: but the sshd service isn't running [21:59] grolongo: how would it know to pick up that port? [22:00] oh yes my bad, it's not sshd.service now, it's just ssh.service, because why not rename it as well haha [22:07] grolongo: do you actually understand what the difference in principle here is? [22:07] grolongo: have you ever used inetd or xinetd? [22:09] no [22:10] but I know the principle that is: if it works, don't touch it [22:24] gordonjcp: did you read the comments in the link posted above? looks like I'm not the only one [22:28] grolongo: so here's the thing [22:28] grolongo: experienced Linux users would adapt very quickly to doing it this way, because this is the right way to do it [22:32] what is the "correct way"? because it looks like nobody agrees with it in the comments [22:37] gordonjcp: not only the changes explanations don't make any sense, it's also bugged: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041 [22:37] -ubottu:#ubuntu- Launchpad bug 2069041 in openssh (Ubuntu Noble) "Changing Port in sshd_config requires calling systemctl daemon-reload" [Medium, In Progress] [22:37] this is pure madness that something like this went through into an LTS [23:06] "socket activation" with inetd used to be the norm on many older unix/linux systems [23:11] grolongo: in 24.04, you make your changes to sshd_config , run sudo systemctl daemon-reload && sudo systemctl restart ssh [23:12] or follow https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-ubuntu-22-10-and-later/30189#:~:text=systemctl%20disable%20%2D%2Dnow%20ssh.socket%0Arm%20%2Df%20/etc/systemd/system/ssh.service.d/00%2Dsocket.conf%0Arm%20%2Df%20/etc/systemd/system/ssh.socket.d/addresses.conf%0Asystemctl%20daemon%2Dreload%0Asystemctl%20enable%20%2D%2Dnow%20ssh.service [23:16] why do you even need to restart anything if it's socket-based [23:16] it might be running [23:16] because the socket isn't looking for changes in the sshd_config [23:20] leftyfb: but I thought the "daemon" wasn't even launched until the socket connection is made, and wouldn't it then read sshd_config anew? [23:21] JanC: I thought (like the old way) changes were never designed to apply to running instances [23:21] that being the case, I don't see how it being running would matter [23:21] leftyfb: thank you, but remember earlier we didn't know know why the port wasn't changed, and it's not even mentioned as a comment in the config file [23:22] yup, that sucks [23:22] bparker: actually, once I ran daemon-reload once, it seems now all changes I make only require restarting the ssh service [23:23] even when changing the port number or listening address? [23:24] confirmed. On a fresh boot, if I make changes to the port, I need to daemon-reload, then restart ssh. After that, I can make further changes and only need to restart ssh ... until the next reboot [23:26] Hello openssh user, you want to change your ListenAddress interfaces? Edit sshd_config, save, reload the daemon. Have a nice day! [23:26] 25 years later: "if more than one ListenAddress setting is declared, the configuration is not migrated because systemd’s ListenStream has different semantics: any address configured which is not present at boot time would cause the ssh.socket unit to not start. Because it is not possible to reliably determine at upgrade time whether ssh.socket could fail to start on reboot, if you have more than one ListenAddress configured, [23:26] your system will not be migrated to socket-based activation but instead the daemon will be started on boot as before." [23:27] grolongo: you can ignore the "migration" section completely. It doesn't apply to 24.04 and only applies to upgrading to 22.10, 23.04 and 23.10 from previous releases [23:28] grolongo: just use sshd_config and run daemon-reload and restart ssh [23:29] or mask the sockets and restart ssh and go back to the way it was ... just like ravage pointed out to you and the discourse link provided to you [23:29] leftyfb: I did daemon-reload earlier and it broke my ssh installation literally :) even after a reinstall it is still broken. [23:29] define broken [23:29] daemon-reload won't break your ssh unless you have other issues going on [23:32] explains things if he did. [23:34] dmesg? [23:35] this is a dpkg issue [23:35] grolongo: so you're not going to provide any details on your issue? [23:37] grolongo: alright, well, let someone here know when you'd like support. I suggesting asking for help sooner rather than later so you don't make things worse in the meantime. [23:37] leftyfb: this is unrelated to the original issue, even though this new issue is related to systemd managing ssh [23:37] it's not [23:37] grolongo: please post details of the issue [23:38] it sounds like either you made things worse somehow or there's a misunderstanding [23:38] leftyfb: the other issue you figured out was that odd file in sshd_config.d/, I'm still wondering why is that file present [23:39] grolongo: ok, good luck [23:43] https://askubuntu.com/questions/1516262/why-is-50-cloud-init-conf-created [23:43] lol [23:43] >like 99% of all people [23:43] lol, lmao even [23:46] So that cloud init shit messed things up again [23:46] 99% of 'sane' people [23:46] younder: lets not [23:47] grolongo: do you have an issue you'd like help with? [23:47] been there still trying to adjust [23:48] younder: sudo apt remove --purge cloud-init [23:48] no thanks but I can't wait to see sysadmins worldwide when they migrate to 24.04 :D [23:48] ... [23:48] grolongo: good luck [23:48] I think it will be fine [23:50] competent sysadmins read release notes for new installs, keep up with changes in the industry, know how to read logs and debug [23:50] Infrared_: why are you sending CTCP request, are you okay? [23:50] the better ones use automation tools which force systems into their desires state and adjust as needed [23:52] leftyfb: the release notes doesn't mention anything specific, links to a thread with 2 bug reports in it, and the OP of said thread even admits the lack of documentation in the release. [23:52] grolongo: ok, so work around the issue as documented and move on [23:52] I was also caught completely off guard with the ssh switch to socket-based [23:52] grolongo: file a bug for a lack of documentation if you are interested in helping others [23:52] and I was in a rush trying to get a new box up [23:53] so it was quite frustrating [23:53] bparker: it's also news to me, but now I know how to work around it so I'm done thinking about it [23:53] not everyone thinks that should be how things should be [23:53] is this behavior the same on debian? [23:54] if so, why the fuzz? [23:55] No, its Ubuntu who has been modifying the network setup with netplan and cloud-init [23:55] younder: stop [23:56] what are they doing wrong? [23:56] wrong. https://gist.github.com/dazeb/fde301b5035e8af3b040c6109c3d8170 [23:56] lolz, saturday support [23:56] welcome to IRC I guess [23:56] Debian also has netplan [23:56] as do most other modern distro [23:57] topic: answers might not satisfy you .. [23:57] "you're asking the wrong question" [23:59] what I want to understand is why would you change something so vital that has been working for decades and is reliable across many different OSes (including BSDs ofc), into something that is barely comprehensible (lack of documentation), much more complicated to configure (when that works), bodged and that shouldn't have pass a QC before an LTS. [23:59] grolongo: file a bug or feel free to rant/discuss in #ubuntu-offtopic [23:59] the bugs have already been filed [23:59] grolongo: also: same reason we don't use LILO anymore. It's called progress [23:59] lol. === dtomato2 is now known as dtomato