[00:19] <telgareith> nothing runs properly in virtualbox
[01:37] <mybalzitch> define nothing, and properly.
[02:01] <tomasd_> Hola Team, soy nuevo en lubuntu, gusto en saludarlos
[02:02] <Bashing-om> !es | tomasd_
[02:04] <tomasd_> Oh Thank You #bashing-om, i prefer more information in spanish, see you
[02:05] <Bashing-om> tomasd_: Glad I could help.
[02:11] <Crackva> Search two girls (UK, US, AU) for administration DCHUB.ONE international DC++
[02:11] <Crackva> https://vk.com/dchub.club?w=wall-209405006_174
[04:33] <pushkarnk> 10 xr
[04:33] <pushkarnk> ;'
[04:46] <badusername2262> hello?
[05:21] <pushkarnk> please ignore my prev ping, my 4yo got curious with the IRC window ;-)
[07:28] <tudor> hi everyone !
[07:28] <tudor> what would be the best option to move a plesk server? Migration or backup/restore?
[07:52] <Apachez> hi
[08:57] <lotuspsychje> tudor: not really an ubuntu issue?
[09:15] <realivanjx> will ubuntu pro livepatch come to arm64 architecture? is it just not possible or already being worked on?
[09:19] <lotuspsychje> realivanjx: https://ubuntu.com/blog/ubuntu-pro-now-available-on-aws-graviton-instances
[09:20] <realivanjx> it does not mention livepatch
[09:25] <tudor> lotuspsychje: thank you for your help ! I didn't say it was strictly an ubuntu problem, I was asking for more of an opinion, but thank you for bothering to answer me.
[09:26] <lotuspsychje> tudor: feel free to try your question in #ubuntu-offtopic ?
[09:36] <oerheks> " If you have engineering resources and are interested in bringing Livepatch Service to your ARM64 platforms, please reach out to the Canonical Kernel team" https://blog.surgut.co.uk/2024/01/ubuntu-livepatch-fips-s390-arm64.html?m=1
[09:36] <lotuspsychje> realivanjx: ^
[10:29] <Dhagor> hello
[10:29] <Dhagor> need support
[10:30] <EriC^^> !ask
[10:30] <oerheks> :-)
[10:31] <Dhagor> i've pulled an image, built a docker file and built it. running the image does nothing
[10:31] <Dhagor> supertool@DESKTOP-98MNGEP:~$ docker run ubuntu:16.04
[10:31] <Dhagor> docker: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix /var/run/docker.sock: connect: permission denied.
[10:31] <Dhagor> See 'docker run --help'.
[10:31] <Dhagor> supertool@DESKTOP-98MNGEP:~$ sudo docker run ubuntu:16.04
[10:31] <Dhagor> supertool@DESKTOP-98MNGEP:~$ sudo docker run .docker.io/library/ubuntu:16.04
[10:31] <Dhagor> docker: invalid reference format.
[10:31] <Dhagor> See 'docker run --help'.
[10:31] <oerheks> !paste
[10:31] <oerheks> 16.04 docker..?
[10:32] <oerheks> try a supported version, 22.04?
[10:32] <Dhagor> should not really matter
[10:32] <Dhagor> i need that specific version
[10:32] <Dhagor> the thing is that as you can see, docker ps shows no started containers
[10:33] <Dhagor> worth a mention, im using wls in win, so not perhaps the ideal env
[10:34] <oerheks> oh, wls has its own support channel
[10:34] <oerheks> !wsl
[10:34] <oerheks> #windows-wsl
[10:35] <Dhagor>  => => writing image sha256:5bc9b99a386e43c125844cec5303babdab181d72b9edb0ac317c3259bdc44613                       0.0s
[10:35] <Dhagor>  => => naming to docker.io/library/ubuntu:16.04
[10:35] <oerheks> and EOL images surely matter
[12:09] <kfcmcdoburger> Hello everybody
[12:13] <kfcmcdoburger> Is there somebody who can help me please? I think there is a rootkit on my Ubuntu
[13:36] <BluesKaj> Hi all
[14:02] <Bibbles> Hi everyone. I have a weird problem here on 22.04. When my system suspends it brings down the network -before- unmounting a mounted NAS. So when I have running applications with opened files on this NAS, the suspend process will try to halt these applications. But as they are depended on a working network, they just won't. The result is that suspend just hangs indefinately (or until finally a timeout occors). Is there a way to solve th
[14:02] <Bibbles>  problem? I tried running a script in /lib/systemd/system-sleep/ But at the time that script is running, the network is already down.
[14:19] <Nitrigaur> I need some help identifying which paths a snap package can accesss and how it is mounted from the the perspective of that package (kicad)
[14:21] <Mulka> Для сборки EiskaltDC++ с поддержкой unicode на Ubnutu нужно сделать всего несколько простых дейтсвий...
[14:21] <Mulka> ____
[14:21] <Nitrigaur> I'm trying to add a library to kicad in order to add a Raspberry Pi Pico W, but it does not find it in the paths I have copied it to.
[14:21] <Mulka> To build EiskaltDC++ with unicode support on Ubuntu, you need to do just a few simple steps...
[14:21] <Mulka> https://vk.com/dchub.club?w=wall-209405006_175
[14:22] <oerheks> Nitrigaur, in your home folder, /home/<username>/snap/<snap name>/common i guess
[14:26] <Nitrigaur> oerheks, I have tried that already, but kicad can't see that for some reason. I'm a bit new to the whole snap ecosystem, but in Kicad the paths configured point to /usr/share/... paths. Are those paths relative to the /snap filetree, or are they real /usr/share references?
[14:27] <oerheks> i think the real /usr/share folder on /
[14:28] <oerheks> just tested, kicad opens my home folder..
[14:29] <oerheks> i do see when i open a demo, i cannot save it  '/usr/share/kicad/demos/'
[14:31] <Nitrigaur> oerheks, first of all: Thank you for the test :-) . Is there a way to get a list of all the paths that a snap package has access to?
[14:37] <ravage> Snap allows access to your /home folder. Everything else is contained in the snap
[14:38] <oerheks> settings > applications > snap > settings
[14:38] <ravage> It will never have access to /usr/share on your host
[14:38] <oerheks> for kicad there is an option for removable media.
[14:38] <ravage> That is possible too yes
[14:38] <oerheks> ravage, oddly kicad loads demos from /usr/share/
[14:45] <Nitrigaur> oerheks, I have not seen this settings entry yet. Thank you.
[14:45] <ravage> layout:
[14:45] <ravage>   /usr/share/kicad:
[14:45] <ravage>     bind: $SNAP/usr/share/kicad
[14:45] <ravage> so that is mapped to your snap directory
[14:46] <lacrymology> I can't start jack, I tried QjackCtl, I don't think the server is starting at all
[14:48] <Nitrigaur> ravage, ah, so the snap package has specific access to /usr/share/kicad, because it has been bound to it's snap path.
[14:48] <ravage> right
[14:48] <ravage> but that is read only because it is part of the snap package
[14:50] <Nitrigaur> ravage, that seems rather awkward if you want to add a component library system wide, or perhaps I'm getting ahead of myself.
[14:51] <ravage> it this is the only path you can use then yes
[14:53] <Nitrigaur> ravage, actually this Kicad 7.0 package tries to find my library in the Kicad 6 path: /home/$USER/snap/kicad/6/.local/share/kicad/7.0/symbols/74XXJL.kicad_sym . It gets stranger and stranger
[14:54] <Nitrigaur> This makes me long for the simple .deb-days...
[14:55] <oerheks> https://launchpad.net/~kicad/+archive/ubuntu/kicad-7.0-releases
[14:56] <ravage> there is nothing special about other paths in that snap package. so the software just looks in there
[14:56] <ravage> and 6 is not a version of the software. it is revision 6 of the snap
[14:57] <ravage> 6 should be linked to /home/$USER/snap/kicad/current
[14:58] <ravage> * to /home/$USER/snap/kicad/current. or better the other way around
[14:58] <Nitrigaur> ravage, that makes sense to some extent. Thanks for the clarification
[15:03] <Nitrigaur> oerheks, settings -> applications -> snap -> settings does not exist on my system. I'm running Ubuntu 23.10.
[15:03] <oerheks> settings -> applications -> snapname ..
[15:03] <ravage> the permissions are all auto connected except maybe the removeable-media one
[15:04] <oerheks> kicad got a lot of entries there
[15:05] <ravage> so if removeable media is what you need you can try "sudo snap connect kicad:removable-media"
[15:05] <Nitrigaur> oerheks, true, at least accesss to my /home drive is on and should solve a lot of issues.
[15:05] <ravage> the home interface should auto connect on unstall
[15:06] <Nitrigaur> ravage, yes it does. I'll look up the version of the snap and it's mounts through /run/snapd
[15:07] <ravage> but you can try to set it again of course with "sudo snap connect kicad:home :home"
[15:07] <ravage> but is only allows you to read non-hidden files
[15:08] <ravage> it will not give  any access to dotfiles or dirs by default
[15:09] <Nitrigaur> ravage, that's a problem, because .local is part of the default path it tries to lookup.
[15:09] <ravage> from what you pasted it does look in ~/snap/  for that
[15:09] <ravage> and not your actual home directory
[15:09] <Nitrigaur> True.
[15:21] <Nitrigaur> ravage, I've looked up the snap version and it's version 8 and that's also where the symlink "current" points to. Probably the original Kicad project was made when version 6 was still current. The library got moved to the current file tree, so it might work to remove the lib from the library overview and re-add it in the current dir. Still, that does not provide a solution to put a library in a path that is accessible to all users on this system.
[15:23] <ravage> https://snapcraft.io/kicad says the stable version i 7.0.10
[15:23] <ravage> *is
[15:27] <Nitrigaur> ravage, true, that's the same with my install, however, as you correctly pointed out that is not the version of the snap, which is version 8. I've tried re-adding the library at the place it's currently at: /home/$USER/snap/kicad/8/.local/share/kicad/symbols, but this does not work. Kicad can access the directory, but sees no files there, even through the terminal I can clearly see the files, along with the correct extensions.
[15:28] <Nitrigaur> Before you ask, yes, they are readable to world, not only to my $USER.
[15:29] <leftyfb> Nitrigaur: you're not supposed to mess with /home/$UER/snap/<app>/current or any of the named version directories
[15:30] <leftyfb> Nitrigaur: if a snap isn't working properly, please file a bug
[15:30] <leftyfb> !bug | Nitrigaur
[15:39] <JanC> snap bugs ≠ ubuntu bugs
[15:42] <Nitrigaur> JanC, indeed and the links in the Software store point to the Kicad project, not to a space where I can report issues on the snap package from Nick Koe.
[15:44] <JanC> seems like KiCad also has an official PPA, maybe try those packages?
[15:47] <Nitrigaur> JanC, I suppose so. I hope it won't break when I upgrade to Ubuntu 24.04.
[15:47] <Nitrigaur> JanC, thanks for the suggestion btw.
[15:50] <JanC> if you use the official distro-upgrader it will disable the PPA before the upgrade
[16:00] <JanC> Nitrigaur: the Snap isn't listed as official on the KiCad website, but the PPA is, so maybe best to use that for now
[16:09] <Nitrigaur> JanC, yes, though only the alternative snap package (Kicad 7.05) clearly states that. Nickoe is one of the official Kicad developers though.
[16:09] <Nitrigaur> JanC, Installing the PPA now. Thanks again.
[16:09] <JanC> the official download/install page for linux doesn't even mention the Snap
[16:09] <JanC> on the KiCad site
[16:10] <JanC> maybe they know the Snap isn't 100% ready yet?  dunno...
[16:14] <Nitrigaur> JanC, could be. The PPA is far larger than the snap used to be, so it's probably more complete.
[16:24] <alf> ciao
[16:40] <Nitrigaur> JanC, oerheks, the PPA works like a treat. Thanks again :-).
[16:40] <oerheks> have fun!
[16:40] <unjustice1> Hi, I recently got a new desktop and I believe I have blocked myself out by messing up the hard drive mount point. I am close to fixing it, but could use a little guidance.
[16:42] <unjustice1> I was backing up files onto the new computer's hard drive and it ran out of space, when I tried to save to the secondary hard drive, I could not. So I followed instructions here:https://support.system76.com/articles/extra-drive/
[16:42] <unjustice1> Now, when I boot I get this error: "[FAILED] failed to start system logging service"
[16:43] <unjustice1> I was able to drop into a shell prompt by loading in recovery mode for ubuntu
[16:43] <unjustice1> now what I see is that the "ExtraDrive" folder that I made in /home/user contains all of the same data as the original drive.
[16:45] <unjustice1> I am trying to log back in and ideally backup files on the second drive, but I am hesistant to format from the outside and risk losing some of the data that I was in the process of backing up.
[16:45] <unjustice1> I am not sure if this is a result of overloading my original drive (I think there was 4G left or less), or a result of messing with mounting of the "ExtraDrive"
[16:45] <unjustice1> anyone have any experience with this?
[16:48] <mei> why you don't run a live ubuntu and backup the stuff?
[16:51] <unjustice1> @mei I'll try again, the first USB I tried wouldn't boot
[16:51] <unjustice1> probably need a different iso
[16:54] <JanC> don't you have an external drive to backup to?
[17:07] <unjustice1> @JanC, 90% of what I was backing up was from an external onto the internal
[17:08] <unjustice1> @JanC, just that last 10% or so of data that I would like to retain
[17:13] <mei> i don't understand what you have to recover from the internal disk
[17:14]  * JanC is confused about "backing up from external to internal"
[17:14] <JanC> that seems backwards
[17:14] <mei> yeah, it's like you already have your data on the external drive. but at the same time you want to recover things from the internal drive :s
[17:15] <JanC> and if you still have all data on the external disk then I'm not sure what exactly the problem is--can't you just re-install the system & start all over?
[17:15] <mei> ^
[17:23] <unjustice1> So basically I had a 2TB backup external drive and a 750GB external drive when my computer crashed completely. I got a new computer with two 2TB drives
[17:23] <unjustice1> I moved everything from the the drives onto the new 2TB drive, the second 2TB drive I could not load onto
[17:24] <unjustice1> so I followed the mount instructions listed above.
[17:24] <unjustice1> In the process, I deleted the 750GB external
[17:24] <unjustice1> Now, I cannot login
[17:25] <JanC> you probably can't login because the disk is full
[17:25] <JanC> the main disk
[17:25] <JanC> (except for a small space reserved for root)
[17:25] <unjustice1> @JanC that is what I suspected, is there a way to check if this is the problem? then I can delete the less sensitive stuff
[17:25] <unjustice1> or just delete stuff and reboot?
[17:28] <JanC> there are several things you can try to delete
[17:28] <unjustice1> also, how do I delete files when I can only see them as read-only (recovery mode)? Otherwise I cannot access the shell
[17:29] <JanC> e.g. in theory everything under /home/<user>/.cache should not be a problem if you delete it
[17:30] <JanC> you can re-mount as rw in the recovery mode
[17:33] <unjustice1> @JanC
[17:33] <unjustice1> "mount -o remount,rw /" ?
[17:33] <unjustice1> basically sudo mount -o, rw /?
[17:37] <Nitrigaur> Thanks everyone, I'm going to cook.
[17:38] <JanC> unjustice1: no need for sudo in the recovery mode, as you are already root
[17:39] <JanC> so "mount -o remount,rw /" should be enough
[17:39] <JanC> also see https://wiki.ubuntu.com/RecoveryMode
[17:42] <JanC> if deleting everything in /home/<user>/.cache (where <user> is your username) is not enough then you can look at deleting some stuff that is still on the external disk also (so you would still have a copy of it)
[17:46] <unjustice1> @JanC just deleted a ton of stuff, same error "failed to start system logging service"
[17:56] <JanC> is that the only error?  maybe also check dmesg, journalctl & log files in /var/log/ in the recovery console...
[18:07] <unjustice1> @JanC yeah, I tried unmounting the ExtraDrive as well, and that didn't change anything
[18:07] <unjustice1> @JanC, I'll check dmesg
[18:19] <unjustice1> @JanC whole lotta of errors in dmesg, trying to make sense of them
[18:37] <leftyfb> unjustice1: dmesg ata/io errors = bad drive. Potentially just a corrupt filesystem, but usually it's due to bad hardware
[18:39] <leftyfb> unjustice1: you could try running fsck on the unmounted filesystem. But if the drive has a hardware issue, this sort of actively could make things worse
[18:39] <unjustice1> @leftyb "perf uncore: Cannot find matched IMC device"
[18:40] <unjustice1> @leftyfb "platform eisa.0: EISA: Cannot allocate resource for mainboard"
[18:41] <leftyfb> unjustice1: sudo dmesg --level=emerg,alert,crit,err | nc termbin.com 9999
[18:41] <unjustice1> @leftyb "platform eisa.0: Cannot allocate resource for EISA slot" for slots 1-8
[18:44] <unjustice1> @leftyb "nc: addrinfo for host "termbin.com" port 9999: Temporary failure in name resolution"
[18:44] <oerheks> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326
[18:44] -ubottu:#ubuntu- Launchpad bug 1837326 in linux (Ubuntu) "platform eisa.0: EISA: Cannot allocate resource for mainboard" [Undecided, Confirmed]
[18:44] <leftyfb> unjustice1: can you connect your machine to the internet and run it again?
[18:45] <unjustice1> @leftyb, you mean just unplug the network cable and connect again? The boot now freaks out connecting to wifi and gives an error in dmesg
[18:45] <leftyfb> unjustice1: are you still our of disk space on your root partition?
[18:46] <leftyfb> our/out*
[18:46] <pagios> : when doing an upgrade from ubuntu 6 for exampel to ubuntu  9, can i go directly like that by updating the soruce.list to ubuntu ; apt update upgrade etc, or should i go from 6 to 7 then 7 to 7 then 8 to 9 ?
[18:46] <unjustice1> @leftyb: shouldn't be I deleted a lot of stuff, is there a way to check?
[18:46] <leftyfb> pagios: go troll someone else .... again
[18:46] <oerheks> there is no 6, 7, 8, 9..
[18:47] <oerheks> you are clearly running debian
[18:47] <leftyfb> oerheks: they've been trolling here for a while now
[18:48] <pagios> yes ytrying to understand the concept of release update
[18:48] <pagios> if. ican jump versions
[18:48] <leftyfb> pagios: go troll elsewhere
[18:48] <oerheks> one can jump from lts to lts
[18:49] <pagios> from consecutive lts right?
[18:49] <pagios> seems i can also use apt-listchanges and view the changelogs
[18:50] <leftyfb> unjustice1: this is what I suggest. Remove all storage devices except for your main drive with your OS on it. Boot it using live USB. Mount the drive and delete a few gigabytes of your least important data. Unmount and run fsck on it. Then boot it normally and see where things stand
[18:50] <leftyfb> pagios: what release of ubuntu are you running?
[18:50] <pagios> 18
[18:50] <pagios> wanna see if i can jum pto 22.04 directly
[18:50] <unjustice1> @leftyb, alright I will try this
[18:50] <leftyfb> pagios: ( cat /etc/os-release ; uname -a ) | nc termbin.com 9999
[18:52] <leftyfb> pagios: please paste the resulting URL here
[18:53] <leftyfb> pagios: hello?
[18:53] <pagios> brb
[18:55] <unjustice1> leftyb: I cannot boot from usb either, "can not mount dev/loop0 on /filesystem.squashfs failed:invalid argument"
[18:56] <unjustice1> leftyb: also "ERROR:unable to locate IOAPIC for GSI 27"
[18:56] <leftyfb> unjustice1: make a new usb flash drive with the ubuntu desktop iso on it
[18:56] <unjustice1> leftyb: will do
[19:00] <leftyfb> pagios: when you're back, please run this instead:   ( cat /etc/os-release ; uname -a ; sudo tune2fs -l $(findmnt -n -o SOURCE /) | grep created ) | nc termbin.com 9999
[19:02] <unjustice1> leftyb: Ubuntu Studio 22.04.3 LTS from https://ubuntustudio.org/download/ written with rufus should work fine, right?
[19:02] <leftyfb> unjustice1: https://releases.ubuntu.com/22.04.3/ubuntu-22.04.3-desktop-amd64.iso
[19:03] <unjustice1> leftyb: alrighty then
[19:05] <unjustice1> leftyb: that download link you sent keeps failing for some reason, good lord I must be cursed
[19:06] <leftyfb> unjustice1: do you have another computer?
[19:11] <bprompt> unjustice1: alternatively, you could try this mirror images -> https://mirrors.aliyun.com/ubuntu-releases/22.04/ubuntu-22.04.3-desktop-amd64.iso   OR  https://mirrors.sdu.edu.cn/ubuntu-releases/22.04.3/ubuntu-22.04.3-desktop-amd64.iso
[19:12] <unjustice1> bprompt: thanks, I think it is working now...very slowly. It failed like 5 times but it seems to be working now.
[19:13] <unjustice1> I need to run errands, but I will return after I have tried the new bootable USB
[19:13] <unjustice1> leftyb: thanks, I'll be back and let you know if it works or not
[20:09] <rooter0_> I have a nanocomputer called an Odroid N2+, which boots off of an SD card.  I need to install Ubuntu onto that SD card.  Can I put it in my x86_64 laptop, and somehow install aarch64 onto the SD card?
[20:09] <rooter0_> https://www.hardkernel.com/shop/odroid-n2-with-4gbyte-ram-2/
[20:10] <rooter0_> It is a superb device, but needs newer firmware than Odroid provides.
[20:10] <rbox> is there an ubuntu iamge for it?
[20:13] <rooter0_> There is, but it's 20.
[20:13] <oerheks> https://wiki.odroid.com/odroid-n2/os_images/os_images
[20:14] <rooter0_> 22 - Two years old.
[20:15] <leftyfb> rooter0_: 20.04 is still supported by the ubuntu community and it sounds like 22.04 isn't supported by your hardware manufacturer for your hardware
[20:16] <rooter0_> 22.04 is there, but it's from 2022.
[20:16] <leftyfb> ok, so use that
[20:17] <rbox> rooter0_: so an apt update and upgrade, and its from the current day
[20:17] <rooter0_> Well...  I'm looking for a way to install something current.
[20:17] <leftyfb> rooter0_: install the 22.04 image and then do updates = current
[20:20] <JanC> 22.04 is the current LTS
[20:21] <rooter0_> Ok.  I'd just like to know how to make it myself.
[20:21] <rooter0_> I'm an infosec type and have a hard time trusting third parties.
[20:22] <rbox> then you should be compiling everything yourself
[20:22] <rooter0_> Poo, not necessary.
[20:23] <leftyfb> rooter0_: if you don't trust your hardware manufacturer, then don't use their hardware
[20:24] <rbox> sounds like you trust 3rd parties then
[20:24] <rooter0_> Alright.  This has not been a waste of time...
[20:24] <JanC> ?
[21:14] <younder> balena etchercat burn a image onto a sd card. You need sd3.0 reader on our PC/laptop or simular
[21:15] <younder> etcher
[21:15] <younder> https://etcher.balena.io/
[21:16] <younder> https://www.amazon.com/IOGEAR-MicroSD-Reader-Writer-GFR204SD/dp/B0046TJG1U
[21:18] <younder> lsusb to find device, dd -if <our image> -of <our card device> -bs 64Mib
[21:18] <leftyfb> younder: can we help you with something?
[21:18] <younder> could also work
[21:20] <younder> Some suggestions to something rooter0_ questioned earlier.. Never mind. It's late
[21:20] <leftyfb> they left the channel an hour ago
[23:07] <unjustice1> leftyb: alright, I got the usb live disk up and running
[23:08] <unjustice1> leftyb: no mouse cursor for some reason, but I can probably get by with keyboard only