[00:47] <Patrick_> When does ubuntu 23.10 become available as a normal upgrade? It doesn't show up in update-manager, and do-release-upgrade says no new release found.
[00:48] <leftyfb> $soon
[00:49] <leftyfb> We do not have a more accurate answer than that
[00:50] <Patrick_> it's alright if you don't know when but do you know if it's being delayed more than usual? If so, why? I don't know if it usually available on october 10th or after a delay?
[00:50] <leftyfb> the upgrade path is never available on the day it gets released
[00:51] <Patrick_> I see
[00:51] <ravage> if you feel adventurous you can use the -d flag
[00:52] <Patrick_> I considered it but considered that there could be downsides. not sure what to think
[00:52] <ravage> downside is that you may run into open bugs
[00:53] <ravage> there is a reason why it is not officially available yet
[01:00] <toddc> ravage: I assume it is due to retesting for third party issues that delayed the iso release that now need to corrected and verified
[01:00] <ravage> i does not have anything to do with the release of the iso
[01:01] <realivanjx> what is this mount? https://files.catbox.moe/dftedc.png
[01:02] <leftyfb> realivanjx: it's an orphaned snap loopback mount from a snap package version that was updated and the old one removed
[01:02] <leftyfb> realivanjx: there's a bug that's already been reported but hasn't been fixed yet. All you can do it reboot for it to go away. Otherwise, you can ignore it
[01:04] <realivanjx> thanks leftyfb it is gone now
[01:24] <Patrick_> but I run into open bugs every day on my current release that the last few before that
[01:24] <Patrick_> *and the last few*
[01:37] <enyc> Patrick_: well you know depends how adventurous you want to be :O
[01:37] <enyc> Patrick_: I don't know if its' still generally true but debian tends to release "when its ready" and ubuntu tend to push a bit fater to fit a schedule and fix issues later.
[01:38] <enyc> Patrick_: Notice ubuntu certainly for LTS, tend to offer release as LTS-LTS upgrade only after .1 point release at least later.
[01:38] <ravage> well. debian does not release every 6 months
[01:38] <enyc> indeed
[01:38] <ravage> so it you want to compare anything here it is the LTS releases
[01:39] <ravage> and they are usually very stable
[01:39] <enyc> ravage: seen trouble myself but usually by .1 ... better =)  but sure
[01:39] <ravage> thats why upgrades from LTS are always to the .1 release
[01:40] <enyc> I remember back in the day 6.04 ending up as 6.06 due to issues  then 6.10 creating fun with dash as sh and allsorts :O
[01:42] <Patrick_> I'll mention a few of the bigger ones in case anyone knows anything about them
[01:43] <Patrick_> Gnome doesn't remember window position in X, yet it used to. I know this isn't specific to ubuntu since I've experienced it in Fedora. But it's pretty surprising considering how bad that is, imo.
[01:43] <Patrick_> I guess gnome doesn't care about X any more
[01:44] <enyc> Patrick_: fwiw kde plasma new tools becoming more interesting aiui but another story ;o
[01:44] <eigar> What is standard font in Firefox on Ubuntu? about:preferences -> Fonts
[01:44] <eigar> Ubuntu something?
[01:46] <Patrick_> In ubuntu 23.04/gnome/X I've experienced muting audio in the main controls, locking the desktop, unlocking, playing audio without touching the audio and it's playing at full volume. It's happened a handful of times.
[01:47] <Patrick_> In ubuntu 23.04/gnome/X I've experienced locking the desktop, then for unknown reasons the lock screen disappears for a few seconds and shows open application windows, then goes back to the lock screen.
[01:48] <Patrick_> that has happened 2-3 times
[01:49] <Patrick_> at that point, I don't know if I should be blaming and abandoning gnome, ubuntu, or both
[01:50] <rbox> probably ubuntru
[01:50] <enyc> Patrick_: you could try a different variant anyhow ;o
[01:51] <Patrick_> I don't know if that lock screen bug is reported and I'd like to report it but I don't know how to reproduce it
[01:51] <enyc> Patrick_: kubuntu / KDE (or debian+kde)  might be good to 'compare with' and  ubuntucinnamon (or mint cinnamon)  might be nice to try too ... work out what you find fits well, at least thats my opinion ...
[01:52] <enyc> Patrick_: nice of you to care so much [!]
[01:54] <Patrick_> it feels irresponsible to not report it, but I don't know if it will make a difference
[01:54] <enyc> I don't know either ;o
[01:54] <Patrick_> I think I have a slight clue of what's going on
[01:54] <enyc> Patrick_: there are some links about bug reporting in #ubuntu-bugs channel topic
[01:54] <Patrick_> I'm not sure if here or #linux is better to get feedback on the bug
[01:55] <Patrick_> or gnome
[01:55] <enyc> Patrick_: you (might) want to ask there politely about the problem with where bugs fall between lines, but its more for bug team rather than "talk about specific bug"
[02:32] <ruser> is it possible for chroot to be failing to launch bash because it can't find a library?
[02:33] <ruser> 'chroot: failed to run command ‘/bin/bash’: No such file or directory'
[02:34] <ruser> It seems to me it's failing to find coreutils.mo in chroot env, am i correct?  https://termbin.com/s345
[02:48] <ruser> whops, not it
[03:05] <morgan-u2> 22.04 got the last update. I cant function with discord any more. when I scoroll it pastes musltiple copies of what is in the buffer and then the input section takes up the screen. It was bad but got worse. NON FUNCTIONAIRE'
[03:05] <morgan-u2> kaput
[03:07] <matsaman> sounds like your mousewheel is broken
[03:07] <matsaman> or mapped quite wrongly
[03:07] <matsaman> you got a lot of buttons on your mouse?
[03:30] <MuckRaker> I have to do this for the future security of those to whom have the acolites to do so: here it gooes.
[03:30] <MuckRaker> https://www.unplugged.com/upphone/
[03:30] <MuckRaker> Thank you for your time and efforts.
[03:31] <MuckRaker> Pass it on.
[03:33] <MuckRaker> NO More Google.
[03:34] <MuckRaker> FreeDome.
[03:35] <MuckRaker> Good Nite.
[04:29] <morgan-u2> my problem stopped.  NP
[05:14] <DumbLDoor> Hi All! I have a weird issue here. The caps lock is somehow toggled, it works perfectly fine on the log in screen though. Any idea?
[05:17] <DumbLDoor> CAPS LOCK REVERSED - ANY IDEAS?
[05:32] <toddc> DumbLDoor: fresh install? caps may have been on during setup and password is backwards
[05:32] <toddc>   done that before
[06:28] <sadbee> hello
[06:28] <sadbee> hello
[06:29] <Billy7> Hi
[06:29] <sadbee> 你好
[06:30] <Billy7> 你们会说中文吗？
[06:31] <Billy7> 有人吗
[06:52] <dioman> hello
[06:52] <tekisui> privet
[06:52] <tekisui> why does lubuntu keep lowering audio volume ?
[06:52] <tekisui> just at random
[06:53] <tekisui> i need to blast ac/dc to wake the neighbours up
[06:53] <toddc> !ask | dioman
[06:53] <tekisui> could telegram be responcible ??
[06:53] <tekisui> a message client
[06:55] <tekisui> i still remember installing audio manually :D
[06:55] <tekisui> sjees
[06:55] <toddc> tekisui: I use telegram on Gnome with no sound issues
[06:55] <dioman> What about ubuntu =#
[06:55] <tekisui> i dunno am using lubuntu
[06:55] <tekisui> light version
[06:56] <tekisui> ok
[06:57] <toddc> I think lubuntu still uses alsa but I would check hardware and audio settings
[06:57] <toddc> dioman: welcome
[06:58] <tekisui> hmm
[07:00] <toddc> tekisui: not related but the remote volume on my headphones I always seem to bump or set something on the kb volume
[07:00] <tekisui> nah i didn´t touch it..
[07:01] <toddc> np just possible thoughts
[07:01] <tekisui> ok..
[07:02] <tekisui> maybe it´s youtube
[07:02] <tekisui> or firefox
[07:02] <tekisui> danke
[07:03] <Lvl4Sword> Was just about to say.. you can go into settings and see what volume is at for individual programs.
[07:03] <Lvl4Sword> But they left, au revoir.
[09:01] <[twisti]> on boot of a new system, i am greeted with something about "Expanded Security Maintenance", which looks like advertisements for a paid service, is that right ? its a tiny home server, so im not seeing myself paying for something like that
[09:10] <toddc> !pro | [twisti]
[09:11] <toddc> 50 if you are a ubuntu member
[09:18] <[twisti]> thanks
[09:23] <Saiuk> I think, my ubuntu drain my battery anomalously, 30 % in one hour, i came from another debian distro (parrot) but my battery life was very long.
[12:47] <pantalaimon> Hi, I get a kernel panic after upgrading to 23.10 because it's unable to mount the root fs. I have btrfs on my root partition and the "List of bdev filesystems" I get as part of the kernel output before the panic does not contain btrfs. Is the module missing from the kernel image?
[12:49] <ravage> https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/2038715
[12:49] -ubottu:#ubuntu- Launchpad bug 2038715 in linux (Ubuntu) "6.5.0-7.7 kernel not working with Btrfs" [Undecided, Confirmed]
[12:50] <pantalaimon> 😩
[12:51] <pantalaimon> I get the same with the 6.2 kernel that is left from 23.04 though
[12:52] <ravage> i guess you could manually add the module to the initramfs
[12:53] <ravage> add to /etc/initramfs-tools/modules and rebuild it
[12:53] <ravage> maybe you can chroot from the livecd
[12:53] <pantalaimon> Thank you, I'll try that
[12:56] <ravage> you can try https://p.haxxors.com/initrdimg-65.0-9-generic
[12:56] <ravage> this is the one i just updated in my VM
[12:57] <ravage> but if you are on the livecd anyway it should not be too hard to create yourself
[13:09] <pantalaimon> uh I get the same error when trying to boot the LiveUSB
[13:10] <pantalaimon> ok there I first get /dev/root: Can't open blockdev
[13:10] <ravage> but the liveusb does not even use btrfs
[13:10] <ravage> it should start
[13:14] <BluesKaj> Hi all
[13:16] <pantalaimon> ravage: I know! It works on a different machine
[14:48] <ken-ken> Hi. Anybody can help me ? i can't connect to libera server from weechat terminal
[14:52] <oerheks> https://help.ubuntu.com/community/WeeChat it should automaticly?
[14:52] <oerheks> remove ~/.weechat/weechat.conf  and try again?
[14:53] <ken-ken> thank you. i will try it
[14:57] <ken-ken> not work. connection refused
[14:58] <mybalzitch> kinda off topic for #ubuntu
[14:58] <mybalzitch> what port are you using
[14:59] <mybalzitch> #help can probably help you, or #weechat
[14:59] <ken-ken> 6697
[15:18] <ferz> Hi
[15:20] <ferz> How can I disable unbound?  Or at least be able to disable its blacklist?
[15:20] <ravage> ubuntu does not come with unbound installed
[15:20] <ravage> so you reverse the steps you did
[15:26] <oerheks> systemctl status unbound
[15:28] <ferz> ravage: I see it in a docker and snapped pkg
[15:29] <leftyfb> ferz: docker containers are VERY customized, almost unsupportable builds of ubuntu. As stated, unbound does not get instaled on default installations of ubuntu. Either customize the docker container to not add unbound, or use: sudo systemctl disable unbound
[15:31] <oerheks> and likely /etc/unbound/unbound.conf.d/blacklist.conf
[15:37] <ferz> leftyfb & ravage: thank you
[15:39] <ferz> is it dnsmasq to answer on 127.0.0.53 ?
[15:41] <ravage> on ubuntu it is usually systemd-resolved
[15:41] <leftyfb> ferz: you REALLY need to seek support from whoever made the docker container. We have no way of knowing how it's configured or what packages the author installed
[15:46] <ferz> I've disabled and removed any docker package from my laptop.
[15:46] <leftyfb> ferz: what release of ubuntu are you running on your laptop?
[15:46] <ruser> What kind of permissions should  /boot/grub/ have?   [I'm trying to install grub-pc but it is failing]
[15:47] <leftyfb> ruser: as long as you didn't remove all permissions from it, root should be able to access it just fine
[15:48] <oerheks> https://paste.ubuntu.com/p/nT3PnKRrWx/plain/
[15:48] <ruser> leftyfb: in my case Access: (0000/d---------)  Uid: (    0/    root)   Gid: (    0/    root)
[15:49] <ruser> leftyfb: hence the question
[15:49] <leftyfb> ruser: why did you do that?
[15:49] <ferz> leftyfb: 22.04.3 LTS (Jammy Jellyfish)
[15:49] <leftyfb> ferz: what exactly is your issue at this time?
[15:50] <jeremy31> ruser: If the drive have GPT partitioning?
[15:51] <ferz> leftyfb: I want be sure that there is not any "filter" in my system in dns name resolution
[15:51] <ruser> leftyfb: I can't say that I did.  long story  i'm following this gist https://gist.github.com/NiklasGollenstede/c74f92eb75b781d24a057965443866bb to try to install zfs on an a array.  however, my motherboard is anctient and doesn't support uefi. I am installed most of the way through by now, just need to have bootloader working correctly.
[15:51] <leftyfb> ferz: there is not in a default install of ubuntu
[15:51] <ferz> leftyfb: yes, I understand.
[15:52] <ruser> leftyfb: the original script installs uefi, i'm trying to do grub-pc/legacy. on top of it all, the MB bios only sees one drive.
[15:53] <ruser> Not to mention the identifiers are too long to tell which one speicifically is it, i suppose I could tryto trace it to the markings on PCB but i'd rather keep that option in my pocket
[15:54] <ruser> So i'm nearly last step, trying to get the system to boot
[15:55] <ruser> I've stayed out of the tech for a few years due to personal issues, so i missed on some knowledge
[15:56] <ruser> Either way, what are the permissions supposed to be?
[15:57] <ferz> leftyfb: I've found. It was a filter on router dns service.
[15:59] <ruser> grub-install: error: cannot open directory `/boot/grub/i386-pc': No such file or directory.
[15:59] <ruser> So i'm down the rabit hole of what should be there, permissions, etc
[16:01] <ruser> I would manually create the directory if that's the issue, but then I noticed permissions are set to 000 for some reason
[16:01] <ruser> Any help/ideas would be appreciated.
[16:01] <leftyfb> ruser: drwxr-xr-x 5 root root 4096 Oct 19 15:07 /boot/grub
[16:02] <leftyfb> though the fact that was modified in first place tells me your script did an unknown amount of damage
[16:07] <ruser> leftyfb: yeah, i don't know how to recover from this. there is definitely some wierdness going on with grub config in the script.   i'm also currently in the chrooted env, maybe  i screwed something else up?
[16:08] <leftyfb> reinstal
[16:09] <ruser> i'm not sure i can setup raidz1 with encrypted boot via default installation scripts :/
[16:10] <ruser> is there any chance i could also get a listing of that directory?
[16:11] <ravage> ruser: setup a default install in a VM and compare?
[16:12] <ravage> you seem to have a lot of modifications on your system and i dont think anyone can follow the steps you did and really help
[16:12] <ruser> ravage: yeah, that tracks, but also feels i'm ->||<- this close to a booting working system :)
[16:13] <ruser> it feels like this is the final piece to go
[16:13] <ruser> maybe i'm wrong and naive :)
[16:27] <ruser> Ugh, I don't get it. /dev/sdb1 on /boot/efi type vfat (rw,nodev,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)   bp_one/BOOT/ubuntu_77td1d on /boot type zfs (rw,nodev,relatime,xattr,posixacl)
[16:28] <ruser> yet I can't chmod 000 to anything else
[16:47] <pantalaimon> Hi, I tried re-generating initramfs (with compression set to gzip and rootfs=btrfs) and installed different kernels from the mainline ppa, but linux still doesn't find any root device
[16:47] <pantalaimon> I can boot off a grml live USB but not off a Ubuntu Live USB
[16:53] <ruser> ugh, why is the immutable attribute is set to /boot/grub
[16:54] <leftyfb> ruser: blame the custom script you ran
[16:55] <ruser> i'm blaming the foot gun really
[16:55] <leftyfb> ruser: reinstall
[16:55] <leftyfb> you have a broken system due to a custom script
[16:56] <ruser> The only chattr i see is in the
[16:56] <ruser> function mkmnt { # Makes a mount point that is read-only when not mounted. 1: path if mountpoint -q $1; then return 1;
[16:56] <ruser> fi mkdir -p $1; chmod 000 $1; chattr +i $1
[16:57] <ruser> leftyfb:  I think i have broken system due to my desires really.
[16:57] <ruser> While this is a major PITA i'm finding myself re-learning things so, i consider this is personal growth exercise again :)
[16:58] <ruser> I dropped out for a bit from this field due to a TBI :/
[17:00] <pantalaimon> hm the Ubuntu 23.04 iso still boots 🤔
[17:03] <lotuspsychje> pantalaimon: 23.04 is not eol yet
[17:03] <pantalaimon> lotuspsychje: sure but I just upgraded by system to 23.10 anyway, but now I get a kernel panic because it can't find the root fs on boot
[17:04] <pantalaimon> when booting the 23.10 liveUSB I get the very same error
[17:04] <pantalaimon> oddly enough, booting the old kernel (from 23.04) does show the same error
[17:05] <lotuspsychje> pantalaimon: can you share your dmesg with the volunteers, they can have a look for you
[17:05] <ruser> leftyfb: also, want to say thank you for all the help you've been providing over the years. I appreciate it.
[17:06] <leftyfb> ruser: np
[17:07] <pantalaimon> lotuspsychje: sure, I'll have to take a photo though as it panics before writing anything to disc
[17:15] <pantalaimon> lotuspsychje: https://i.imgur.com/evFM3G4.jpg is what I get
[17:17] <oerheks> there seems to be a newer bios
[17:17] <oerheks> https://www.asus.com/us/supportonly/p8z68-v/helpdesk_bios/
[17:17] <oerheks> 2012/11/27
[17:18] <pantalaimon> oerheks: 3603 is already the latest version
[17:18] <whiten> I need an advice. I have i3 7gen mff pc and I would like to set up a plex server. Is it going to offer worse performance or consume more power with ubuntu desktop than with ubuntu server? It will run headless, however from time to time it would be easier to sort thing out using desktop gui. What do you think?
[17:19] <oerheks> likely it consumes more cycles, so yes, more power
[17:55] <phr34k> is it possible to use socks proxy with apt-get?
[17:55] <ravage> yes
[17:56] <phr34k> I keep seeing information on the internet that when you set apt.conf you can specify it, but when it's on http_proxy environment variable it keeps giving me an error about unsupported proxy.
[17:56] <freakyy85> yay, here with 23.10.1 just freshly installed everything is working!
[17:56] <ravage> https://gist.github.com/wonderbeyond/3448c2f281062d61716efa1d8083a102
[17:56] <freakyy85> can someone give me a good free game? =D
[17:57] <ravage> freakyy85: https://snapcraft.io/search?category=games
[17:58] <ravage> or just use steam
[18:06] <phr34k> the problem is that I'm doing snapcraft, and so i can kinda only pass http_proxy and https_proxy which just seems to set the environment variables, but apt always seems to complain about unsupported proxy.
[18:08] <ravage> thats a question for #snappy or their forum
[18:09] <phr34k> i.e. 2023-10-23 01:08:53.372 :: 2023-10-22 18:08:51.650 :: Unsupported proxy configured: socks5://10.231.20.1:9998
[18:09] <phr34k> 2023-10-23 01:08:53.372 :: 2023-10-22 18:08:52.231 :: Reading package lists...
[18:09] <phr34k> 2023-10-23 01:08:53.372 :: 2023-10-22 18:08:52.237 :: E: The repository 'http://archive.ubuntu.com/ubuntu jammy Release' no longer has a Release file.
[18:09] <phr34k> 2023-10-23 01:08:53.372 :: 2023-10-22 18:08:52.238 :: E: The repository 'http://security.ubuntu.com/ubuntu jammy-security Release' no longer has a Release file.
[18:10] <phr34k> well the problem isn't snapcraft related, specifically, snapcraft just imposes some restrictions but it's the but apt-get command thats actually failing.
[18:11] <oerheks> maybe use apt instead of apt-get?
[18:13] <phr34k> well in the snapcraft.yaml file the packages are defined like this     build-packages: [clang, cmake, git, ninja-build, pkg-config, libgtk-3-dev, liblzma-dev, libunwind-dev, curl, unzip, rsync]
[18:13] <phr34k> and perform apt/apt-get command for it.
[18:16] <phr34k>  but yeah, I mean, I am just wondering its complaining about proxy and how to get it working if its alledgly fully supported
[18:18] <oerheks> better try #snappy
[18:21] <ravage> but the first step would be to test if your proxy works on a default ubuntu installation
[18:21] <ravage> with the same envs
[18:21] <ravage> if not you have to fix your proxy
[18:22] <phr34k> yes it works, I can call curl -v -x socks5h://10.231.20.1:9998 https://www.youtube.com without a problem.
[18:22] <ravage> ok and you already have a difference there in protocol
[18:23] <phr34k> yes that's true because I have already been testing this for a couple of hours prior to asking for help, so i have tested a variety of things.
[18:23] <oerheks>  socks5  socks5h ?
[18:24] <ravage> also curl is not the same as apt
[18:24] <ravage> so try to get apt working outside of snap with your proxy
[18:24] <phr34k> no, curl is not the same as apt but you were asking me to verify if the proxy was actually working, so I said I tested it with curl.
[18:24] <ravage> if you already use snapcraft you maybe use lxd with it
[18:25] <ravage> start a container. test it
[18:25] <phr34k> okay let me be very clear here:
[18:25] <ravage> if you do not use containers with snapcraft maybe switch. uses much less resources than a VM
[18:26] <phr34k> - I can easilly go inside of the containers through lxd or snapcraft pull -shell and test some commands
[18:27] <phr34k> - the actual proxy server itself works and is reachable, its not a firewall issue or something like that, the proxy works fine with curl itself
[18:30] <phr34k> the problem is specifically apt only seems to support http proxy not a socks proxy, at least when configured through environment variable. Normally you can work around this with something like proxychains, the actual problem that I have is inside of the lxd/lxd container the network is instable and I am bypassing that issue with a proxy.
[18:31] <jacfoster>  apt only supports socks5h URI. man apt-transport-http under "Proxy configuration"
[18:32] <phr34k> jacfoster I am testing with sock5h also
[18:32] <jacfoster> What's the output from that?
[18:35] <phr34k> 2023-10-23 01:34:48.796 :: 2023-10-22 18:24:23.904 Requested build-packages already installed: ['clang', 'cmake', 'curl', 'gcc', 'git', 'libgtk-3-dev', 'liblzma-dev', 'libunwind-dev', 'make', 'ninja-build', 'pkg-config', 'rsync', 'unzip']
[18:35] <phr34k> 2023-10-23 01:34:48.796 :: 2023-10-22 18:24:56.320 The http error when checking the store for gtk-common-themes is 500 (retries left 5)
[18:35] <phr34k> 2023-10-23 01:34:48.797 :: 2023-10-22 18:25:28.551 The http error when checking the store for gtk-common-themes is 500 (retries left 4)
[18:36] <phr34k> 2023-10-23 01:34:48.797 :: 2023-10-22 18:26:00.783 The http error when checking the store for gtk-common-themes is 500 (retries left 3)
[18:36] <phr34k> 2023-10-23 01:34:48.797 :: 2023-10-22 18:26:33.006 The http error when checking the store for gtk-common-themes is 500 (retries left 2)
[18:36] <phr34k> 2023-10-23 01:34:48.797 :: 2023-10-22 18:27:05.240 The http error when checking the store for gtk-common-themes is 500 (retries left 1)
[18:38] <jacfoster> That's a server error, isn't it? Not an apt error?
[18:43] <jacfoster> Ok, so apt is reaching the server? The errors posted are from snapcraft? Not familiar. I just noticed the socks5h protocol error because I ran into that years ago.
[18:44] <phr34k> yes, that looks like it, but the server itself works fine with curl or git commands.
[19:48] <root> hello
[19:48] <Guest7806> hello
[19:49] <Guest7806> HELLOOO
[20:08] <cbreak> hi
[20:29] <whiten> I have a question concerning mounting drives in linux.
[20:30] <whiten> I want to use one dir from already mounted drive (ubuntu is installed on it) and join it to my mergerfs setup. Can I somehow mount that single dir as if it was a different drive?
[20:39] <Yakov> if i use ls how to output only files that contain word 'date'
[20:41] <oerheks> ls -c -lt *PRO* will return file which has PRO in its file name.
[20:41] <oerheks> so easy to find, find . ! -name . -prune -type f -name '*PRO*
[20:43] <JanC> whiten: I thought mergerfs always works with directories, not drives?
[20:46] <JanC> you can mount a directory to another place with a bind mount (see --bind in the mount manpage), but I'm not sure how that's useful with mergerfs...
[20:47] <JanC> Yakov: do you mean finding a word inside the file, or only in the filename?
[20:49] <whiten> JanC I thought that it would be nice to merge mountpoints that match certain pattern: eg. hdd_* in /mnt . It would be elegant if all there is to mount was in one place.
[20:49] <whiten> I meant 'to merge'
[20:51] <JanC> you could probably just do that with a symlink too (if mergerfs supports following through that), but otherwise a bind mount would be the solution, I suppose
[20:51] <Yakov> JanC, I meant files or directories, but inside file can be useful too
[20:54] <JanC> if you only mean in the name, "ls *date*" (without the quotes) should be enough
[20:54] <oerheks> -R for directories too ?
[20:55] <JanC> well, all other ls options could be combined, of course, but that depends on what else they want...
[20:57] <bitchin> Hey.
[20:57] <bitchin> When's the next version coming out?
[20:57] <JanC> thye one that is already out?
[20:57] <JanC> the*
[20:57] <bitchin> next one after
[20:58] <ravage> the next release will be 24.04
[20:58] <ravage> in april 2024
[20:59] <JanC> the next LTS is planned for April 2024 (if everything goes well & all that)
[21:25] <Yakov> need to call c++ program as I do with cmd ./program using ubuntu shortcut.  Please see how I proceed with python script in attached file | https://ibb.co/ggRfFgc |  need to do the same for c++ |
[21:28] <gordonjcp> Yakov: so set the path to wherever you've put your program
[21:28] <whiten> I put this in fstab: /home/ubusr/dir1 /mnt/disk1   none  bind,nofail
[21:28] <whiten> I cannot make any changes in /mnt/disk1 as it appears it is read-only. Why?
[21:32] <Yakov> gordonjcp , you mean path to g++?
[21:39] <gordonjcp> Yakov: no, your compiled program
[21:41] <Yakov> gordonjcp, build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod
[21:42] <Yakov> what should I insert to field Command?
[21:43] <rfm> Yakov, just put the absolute path to the binary (something like /home/...../program) in as the only thing in the command.
[21:46] <Yakov>  /home/supernova/build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod/GUI-prod does not work
[21:48] <oerheks> what guide do you follow?
[21:48] <oerheks> ' does not work'  is not informative, pastebin the output when you try?
[21:49] <rfm> Yakov, in a terminal, "cd ~" then enter that path as a command.  What does it do?
[22:00] <Yakov> oerheks, it must call my ./GUI program rfm, cd /home/supernova/build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod/GUI-prod  | bash: cd: /home/supernova/build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod/GUI-prod: Not a directory
[22:01] <oerheks> cd /home/supernova/build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod/
[22:02] <Yakov> yes it will do cd, but I want to open my c++ program which build to this fold to be called with shortcut
[22:02] <rfm> Yakov, that's not what I asked. cd to your home directory, then run the command.   oerheks, the idea here is to simulate the environment the shortcut will execute the command in.  I
[22:03] <oerheks> oh oke,.
[22:03] <oerheks> use $HOME as variable ..
[22:04] <Yakov> rfm, same issue after I cd to home
[22:04] <oerheks>  $HOME/build-GUI-Desktop_Qt_6_2_4_GCC_64bit-Prod/
[22:05] <sudobash> how is network-manager removed from ubuntu repos?
[22:06] <oerheks> is it?
[22:06] <rfm> Yakov, if you just entered the path as a command, the shell would not complain "not a directory".
[22:06] <whiten> Does ubuntu server support exfat? I cannot mount exfat drive.
[22:07] <sudobash> the move from network-manager to netplan is a tragedy
[22:07] <oerheks> the kernel supports exfat for a while now
[22:07] <oerheks> sudobash, it is not removed from the repos, what kind of ubuntu do you use? server?
[22:07] <sudobash> how does Ubuntu keep breaking the same stuff for 10+ years over and over and over again?
[22:08] <sudobash> it works great and then you break it and it has gone in that exact cycle for 10+ years, what keeps causing this?
[22:08] <whiten> oerheks This usb drive was working fine on ubuntu dekstop live whereas i cannot mount it on ubuntu server.  ;/
[22:08] <oerheks> oh. just a monolog rant?
[22:08] <sudobash> new devs trying to make their mark?
[22:09] <sudobash> I'm sick and tired of Canonical breaking the same stuff over and over again, how is that a rant?
[22:09] <oerheks> whiten, one thing that could prevent mounting is a dirty filesystem/error in it
[22:09] <whiten> It works on desktop though.
[22:10] <oerheks> use fsck.exfat to check?
[22:11] <sudobash> stop breaking the OS ever 6 months
[22:13] <sudobash> also, I found a dumb bug in 23.10 because of Canonical's insistence on changing the way wireless gets configured every few releases
[22:13] <Yakov> rfm, bro it works, thanks
[22:14] <sudobash> netplan is super broken and will write multiple yaml configs for the same wifi network
[22:15] <sudobash> might as well be Windows XP now
[22:15] <whiten> fsck.exfat: command not found
[22:17] <oerheks> whiten, you do have exfat-fuse exfat-utils installed?
[22:18] <whiten> no, if it is not in ubuntu server by default i don't
[22:40] <sudobash> netplan single handedly destroyed the integrity and reputation of Ubuntu
[22:40] <Yakov> I want to share screenshot with Ubuntu terminal to get url (like imageshare) any services?
[22:42] <toddc> !pasre | Yakov
[22:42] <toddc> !paste | Yakov
[22:42] <Yakov> please guide me how to use this
[22:42] <Yakov> https://api.imgbb.com/
[22:43] <sudobash> Ubuntu 23.10 wireless is broken because of either netplan, gnome or network-manager applet, create a hidden network with WPA2 password with special chars and try to connect
[22:43] <sudobash> it will create infinite netplan yaml configs for every failed attempt
[22:43] <sudobash> SPECIAL!
[22:44] <JanC> did you file a bug report?
[22:44] <sudobash> F NO
[22:44] <sudobash> screw canonical for switching to that POS netplan
[22:44] <sudobash> this the the last straw
[22:44] <sudobash> I'm NEVER using Ubuntu again because of these dumb preventable mistakes
[22:44] <sudobash> this is insane, networking has worked for 20+ years, stop breaking stuff
[22:45] <sudobash> I shouldn't have to file a bug report, because networking has been around for how many years now?
[22:45] <sudobash> why is it broken?
[22:45] <sudobash> no bug report should be required, the fact that a bug report for a networking issues is required is a bug is Canonicals design itself
[22:45] <oerheks> if you ask why, file a bugreport?
[22:46] <sudobash> Canonical is flawed if it's breaking networking
[22:46] <sudobash> amateurish
[22:47] <sudobash> how about stop changing working networking configuration then there won't be any bugs?
[22:47] <sudobash> I should file a bug report on the fact that I have to file a bug report on something networking related?..........
[22:47] <JanC> I don't know what is going wrong with your setup, but if there are no bug reports they can't fix it
[22:47] <kostkon> sudobash, ok you've made your point, now change to a different distro and see if we care. Or ask here for support regarding your problem and stop repeating the same things all the time
[22:47] <sudobash> IT SHOULDN'T BE BROKEN IN THE FIRST PLACE
[22:48] <sudobash> UBUNTU SHOULD HAVE NEVER SWITCHED TO NETPLAN
[22:48] <JanC> netplan has been used for years...
[22:48] <sudobash> yea on server, just switched on Desktop
[22:48] <JanC> netplan has been used on desktop for years too
[22:48] <sudobash> maybe no one noticed this dumb bug?"
[22:49] <sudobash> it points to incompetence
[22:49] <kostkon> sudobash, turns out it's just you
[22:49] <sudobash> netplan infinitely creates the same network config on every failed attempt because Gnome can't connect to a hidden network with special chars, but Mate can No problem
[22:49] <JanC> of course something might have changed, and triggering a bug now, that's why you have to report it
[22:50] <sudobash> no it's not just me and I will embarrass the F out of Ubuntu, Gnome and Netplan if you want to treat me like that
[22:50] <sudobash> I've been using Ubuntu since it came out
[22:50] <oerheks> 'special chars'
[22:50] <oerheks> which one?
[22:50] <JanC> I doubt it's the first time you see a bug then...
[22:51] <sudobash> that would involve me giving you part of my wifi password
[22:51] <oerheks> no details no fun
[22:51] <sudobash> keep playing games
[22:51] <sudobash> I'm not some idiot newb
[22:51] <oerheks> is it & or ? /...
[22:51] <sudobash> $
[22:51] <JanC> we don't need the whole password, just the one character that causes issues
[22:51] <sudobash> which makes a lot of sense
[22:51] <sudobash> that single char causes more wifi problems than any other special char
[22:52] <JanC> that sounds like there might be a quoting/escaping issue somewhere?
[22:52] <sudobash> for MULTIPLE systems
[22:52] <ravage> actually we dont need it. the bug report he does not want to create needs it. so this whole thing is pointless
[22:52] <sudobash> a bug report for something that shouldn't have changed...........
[22:52] <sudobash> why keep breaking shit every 6 months?
[22:52] <oerheks> logically one would avoid $ and &
[22:52] <sudobash> incompetent
[22:52] <JanC> all bug reports are about things that shouldn't happen
[22:53] <sudobash> I shouldn't have to ommit a special char because the programmer doesn't know how to handle it
[22:53] <sudobash> especially such a simple and common special char
[22:53] <sudobash> points to incompetence
[22:53] <sudobash> serious incompetence
[22:53] <sudobash> pathetic
[22:54] <sudobash> it even works in mate but not gnome and just keeps creating the same yaml config file over and over and over infinite times, like that makes sense....
[22:54] <sudobash> good job netplan....
[22:55] <sudobash> great job canonical and gnome and netplan
[22:55] <sudobash> Mate is the only winner
[22:55] <sudobash> Mate must be developed by some OG devs
[22:56] <sudobash> Makes you wonder who the devs are for the buggy shit, they need to be banned from OSS
[22:56] <oerheks> The SSID can be any alphanumeric, case-sensitive entry from 2 to 32 characters. The printable characters plus the space (ASCII 0x20) are allowed, but these six characters are not:
[22:56] <oerheks> ?, ", $, [, \, ], and +.
[22:57] <oerheks> deal with it.
[22:57] <sudobash> it's not in the SSID
[22:57] <sudobash> idiot
[22:57] <sudobash> I NEVER said that
[22:57] <sudobash> I even said the OPPOSITE of that
[22:57] <sudobash> are you some kid or something?
[22:58] <sudobash> This also works in EVERY other OS on the planet!
[22:58] <sudobash> so, just deal with it points to more incompetence
[22:58] <sudobash> oh we can't figure it out, so just deal with it
[22:58] <sudobash> yea that's what Microsoft said....
[22:59] <sudobash> Look, I'm sorry for ranting, but you all have got to stop breaking stuff
[23:00] <toddc> netplan works for me
[23:01] <sudobash> you know, that's just not good enough, because the yaml files are super touchy compared to interfaces file which always works on everything for everyone, the only reason to change that is to break it.
[23:02] <sudobash> therefore I'm here to declare that I believe someone at Canonical is maliciously trying to destroy the OS from the inside
[23:02] <toddc> systemd all over again?
[23:03] <sudobash> the only reason for changing over the netplan was to be malicious
[23:03] <sudobash> most of Canonical's decisions are malicious
[23:03] <sudobash> I think their intentions are only to stir up controversy for publicity
[23:05] <sudobash> embarrassing they picked Gnome 3 over Mate (Gnome 2)
[23:06] <tomreyn> sudobash: can we get back to keeping this a support (only) chat now, please?
[23:07] <user12> i am a newbie. how can i run a command, kill it and restart it every 5 minutes?
[23:07] <sudobash> support? yea if you can call it that...
[23:07] <sudobash> go for it...
[23:08] <rbox> crontab
[23:08] <ravage> or maybe these days you use a systemd timer
[23:08] <ravage> crontab still works fine of course
[23:08] <sudobash> right, because God forbid we leave ANYTHING alone
[23:08] <user12> syntax of the command or one liner?
[23:09] <sudobash> if it works perfectly, BREAK IT!
[23:09] <sudobash> user12, it's interactive in vim or nano
[23:09] <sudobash> crontab -e
[23:09] <sudobash> the syntax is very important so best to use a generator
[23:10] <sudobash> something like crontab.guru
[23:10] <EriC^^> sudobash: knock knock
[23:11] <sudobash> ban
[23:11] <ravage> user12: you may have to figure out the kill part. the cron only takes care of running a command. not ending it
[23:11] <sudobash> pkill is pretty easy
[23:11] <sudobash> easier than kill for a cron script at least, just supply a name like "pkill chrome"
[23:12] <sudobash> EriC: kline?
[23:12] <sudobash> I'm guessing that's who's at the door
[23:12] <sudobash> or at min a kick ban
[23:12] <user12> so what would the oneliner would look like?
[23:12] <EriC^^> nah i'm not an ops here, but yeah i think you are about to get kicked or something
[23:13] <sudobash> man you gotta figure that out user12
[23:13] <sudobash> you can combine commands with ; and &&
[23:14] <EriC^^> why dont you join the discuss or offtopic channel instead of here, and all's good
[23:14] <sudobash> we don't know what you're trying to do, but something like "pkill [commandname];commandname &"
[23:14] <EriC^^> #ubuntu-discuss #ubuntu-offtopic
[23:14] <user12> that i know, but all i want to do is start foobar, kill foobar, restart foobar every 5 minutes
[23:14] <sudobash> I'm done ranting and will help with support
[23:14] <EriC^^> \o/
[23:14] <EriC^^> sounds good
[23:14] <EriC^^> user12: maybe some cronjob?
[23:15] <EriC^^> nevermind, didnt read the backlog here
[23:15] <sudobash> user12, you might want to consider a little different approach like cron kills foobar then restarts it immediately? every 5 min
[23:15] <sudobash> you just have to kill it before it runs
[23:15] <sudobash> then it's running the entire 5 minutes
[23:16] <EriC^^> user12: how do you usually kill the command?
[23:16] <sudobash> I'll give you a one liner, but don't make a habit of being spoon fed
[23:17] <sudobash> */5 * * * * pkill foobar && foobar &
[23:17] <sudobash> */5 * * * * pkill foobar; foobar &
[23:17] <sudobash> either one of those should work, although 1 is probable better?
[23:17] <user12> thanks
[23:18] <sudobash> because that says start foobar in background if pkill foobar is successful
[23:18] <JanC> the version with && won't work
[23:18] <EriC^^> i think the 1st never runs, cause pkill will always return false
[23:18] <sudobash> ahhh what is pkills return value?
[23:18] <sudobash> that was all a guess
[23:19] <JanC> it has a manpage  :)
[23:19] <EriC^^> in this case false cause foobar never started
[23:19] <EriC^^> but the 2nd works i think
[23:19] <sudobash> yea you're right, it would only work if it was running already
[23:23] <JanC> might want to use -x option of pkill also
[23:24] <JanC> otherwise it will also kill processes that contain foobar in their name...
[23:24] <sudobash> yea depends on what foobar is
[23:25] <sudobash> how unique it is
[23:25] <JanC> always better be safe than sorry
[23:25] <sudobash> yea cause think of "pkill x"
[23:25] <sudobash> like trying to kill X11
[23:25] <sudobash> that wreaks havoc lol
[23:25] <EriC^^> hehe
[23:26] <JanC> otherwise maybe after the next upgrade it will start to kill an important new thing and you will come here ranting that Ubuntu sucks  :P
[23:26] <sudobash> I mean Ubuntu is awesome, it just makes dumb mistakes, I've loved Ubuntu for a long time
[23:27] <sudobash> I just wish it would get its act together because stuff like what I ranted about has been happening for a very long time
[23:28] <sudobash> it's what makes Ubuntu difficult for new users
[23:28] <EriC^^> i feel like it's free and all, as long as the pc doesnt explode it's all good
[23:29] <sudobash> Yea I get that, but it's not very secure compared to Windows 10 now days
[23:30] <sudobash> Windows 10 has integrated all their Xbox security stuff even the hypervisor memory integrity protections
[23:30] <sudobash> Ubuntu 23.10 is just starting with TPM security
[23:30] <sudobash> a lot needs to happen very quickly, especially because of BlackLotus
[23:31] <sudobash> I installed latest 10 today and it automatically puts you in a hypervisor if your PC supports it
[23:31] <tomreyn> sudobash: you're off-topic on this support chat again. opinion and rants just don't belong here. i'll mute you for a few days.
[23:31] <sudobash> all because you dont want security discussion
[23:32] <sudobash> nice
[23:32] <EriC^^> sudobash: there's #ubuntu-discuss for these type of stuff, feel free to discuss there and support here
[23:49] <tomreyn> for transparency, this +q turned into a +b because they were making false claims about what the mute was about, and continued to rant on other channels on the namespace.