=== genii is now known as genii-core [04:38] hi all i have had to install my psc printer scanner copier drivers manually running ubuntu desktop 20.04.3. How do i check if successful from the terminal please? i knonw i could just use it but i would like to know what is used to look be it some systemd command or otherwise, thank you [04:42] yarp: You might try: lpstat -p [04:42] can anyone tell me the name of the service that takes care of printers is it just cups or is that only for a server(mine is plugged in via usb) [04:43] thank u genii-core [04:45] yarp: If it uses SANE for scanning, the scanner part might also be listed if you issue: scanimage -L [04:46] ( assuming sane-utils is installed) [04:48] just checked not installed but i ran sudo systemctrl status saned.s [04:48] will install now cheers [04:49] is there a way to get unetbootin from this live cd or is there another way to work with an iso? [04:49] https://pastebin.com/BqvfgcMY [04:49] ^failure [04:50] do you know the name of the scan document program that comes with vanilla desktop ubuntu 20.04.3;pretty sure i did a minimal and didnt get extra packages-nothing found when i search unity with string scan [04:51] my software centre is shot also [04:51] other wise id just type in scan and install away [04:52] nevermind sorted it [05:10] does anyone know how to get a printers ip address, assuming its plugged in via usb? [05:10] (to the OS;Ubuntu, not the router) === Leon_ is now known as Guest7929 === Bashing-1m is now known as Bashing-om === y0sh- is now known as y0sh_ === synapt is now known as nate === greknod2821 is now known as greknod282 === Phase6 is now known as Phase === Xard0 is now known as Xard === zareem4 is now known as zareem === haggertk_ is now known as haggertk === Itaru3 is now known as Itaru [06:21] I have user autoinstall for creating the custom ISO for ubuntu 20.04, now I am trying to create the same for 21.10 but I see there are some directories are missing and autoinstall does not works. Is there any changes happened or new installer introduced? Could anyone please help me. [06:28] How to automate installation for ubuntu 21.10?? autoinstall?? [06:31] prawat: https://ubuntu.com/server/docs/install/autoinstall-quickstart [06:31] totally sucks. documentation is awful. good luck :) === gacuxz1 is now known as gacuxz === gacuxz1 is now known as gacuxz === martums54 is now known as martums5 [08:21] I'm using Ubuntu 21.10 with kernel 5.13 and I need perf from kernel 5.16 or newer. What are my options to install it? I'm told that it should work with 5.13 if I can manage to build it. [08:24] osa1: you could compile it yourself which is difficult, or, you could find a PPA that has the kernel you want. I don't know if there are officially supported PPAs like this, you may run into issues and we may not be able to help you === ShmoSeph is now known as pshhh === weq_ is now known as weq [11:38] what are the correct persmissions of the /usr directory and the subdirectories? [11:38] should they all belong to root? [11:39] Yes [11:40] ok [11:40] butcause i recursively change owner to root on /usr and sudo stopped working [11:40] however i fixed that from a live system === ahso1 is now known as ahso [13:34] Hi folks === BlessJah_ is now known as BlessJah [13:42] Hello BluesKaj [13:43] hi riboczki [13:50] hello. I have been trying to automate install of Ubuntu 21.10 desktop. All the information I could found online points to modifying grub.cfg to provide command line options to kernel. but for some reason I could not get it working. after the boot it lands in live session desktop instead of starting the install. any ideas? [14:50] + [14:56] -0.5 [15:15] Does someone know a watchdog device (maybe for the internal usb port) that works fine with ubuntu? [15:44] sreve: What is your understanding of "watchdog'? Watching for what? Responding how? Does it smell like a dog? [15:46] jhutchins: presumably https://en.wikipedia.org/wiki/Watchdog_timer [16:07] cambrian_invader: That's one possibility, I can think of others. [16:11] Hello, what program can edit sqlite databases in the terminal? [16:11] Liblx: sqlite [16:11] Liblx: sudo apt install sqlite3 [16:11] oh... :) thanks, gordonjcp [16:11] Liblx: yes, it really is that simple, I bet you're almost disappointed now [16:12] i didn't think about that. :D [16:12] I know right [16:12] no dissapointment [16:12] almost too obvious to think of [16:12] and thanks for the fast answer [16:13] what, you mean you weren't steeling yourself for hours of setting up bizarre libraries with infantile names so you could run Visual Fortran++ Sqlite Designer? [16:14] ;) [16:24] I admit I was surprised when a default install of postgresql didn't include the CLI client. [16:32] Just another area: When I connected to an external hard drive and the name changed, the mount point still uses the old name. How can I change that? For example 'Pbuntu' to 'Ubuntu' then the mount point is still /media/USER/Ubuntu/. [16:34] Hi, can you advice how to fix key absence of the repository ? https://imgur.com/2BNq3lf.png [16:34] How to add a proper key to [16:35] Liblx: If you use the UUID instead of a volume name, the mount point can be made consistent. [16:36] XATRIX: If the web site for the repository doesn't have instructions, it's a good sign that this is not a reputable, reliable source. [16:44] jhutchins: this repo was added by my hosting panel [16:45] XATRIX, sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 467B942D3A79BD29 ; then run sudo apt update [16:50] Hi, it looks Ubuntu is unable to shutdown completely. I'm using focal stable version, with AMD architecture one. What could be the root cause? [16:51] XATRIX: Are you providing hosting services to non-technical users? [16:51] node1: The most common cause is either a shared network mount that is not un-mounted before the networking system is taken down, or some piece of hardware that does not acknowledge the shutdown. [16:53] How to identify those hardware ? [16:54] It looks either the problem is with the Ubuntu OS, or some malacious code. But before coming to any conclusion. I would like to confirm from you people. [16:54] Is that i'm not the only one who facing this issue. [16:55] I don't have any shared network mount, but yes in bios ethernet cable port is enabled. [16:56] jhutchins: thanks! [17:03] jhutchins: it's for private use only [17:06] XATRIX: In that case a web-based administration system is a really bad idea. They are written with the assumption that a competent, console-based administrator will be behind them to fix the problems that WILL be caused by them. [17:07] jhutchins: thanks, but my question was about how to fix repository GnuPG key [17:07] XATRIX: Which is an example of what the web admin panels don't do right. [17:08] XATRIX: Again, your solution should be to follow the directions provided by the repo maintainers. [17:26] hi [17:26] have this problem [17:26] E: Encountered a section with no Package: header [17:26] E: Problem with MergeList /var/lib/apt/lists/apt.releases.hashicorp.com_dists_hirsute_main_binary-amd64_Packages [17:26] E: The package lists or status file could not be parsed or opened. [17:26] Does anyone know the solution for the problem which i have shared? [17:27] I wasn't here when you shared it [17:27] Can you reshare [17:27] thelounge3589: is that 21.04? [17:27] Maik: yes [17:27] sure, [17:27] thelounge3589: 21.04 is EOL [17:28] !21.04 | thelounge3589 [17:28] thelounge3589: Ubuntu 21.04 (Hirsute Hippo) was the 34th release of Ubuntu, support ended on January 20, 2022. See !eol and https://lists.ubuntu.com/archives/ubuntu-announce/2022-January/000276.html [17:28] it looks my Ubuntu is unable to shutdown completely. I'm using focal stable version, with AMD architecture on my laptop. What could be the root cause? [17:28] ah ok [17:28] either upgrade to or perform a clean install of 21.10 [17:28] thelounge I guess the repo was shut down [17:29] thank you Maik [17:29] node1 what do you mean? She's it freeze partway through shutdown? [17:29] thelounge3589: no problem, you're welcome [17:29] Is there an error of some sort on screen? [17:29] `She's it freeze partway` I'm unable to understand this part? [17:30] *Does it freeze [17:31] If you hit escape while powering down, you should get messages in text instead of the visual shutdown [17:31] Those messages might tell you what's wrong [17:31] No. it does not freeze, everything is completely off [It looks] but the batter led is still running. I need to press the power button again to make it shutdown completely[ to off led battery ] [17:32] s/batter/battery [17:32] It looks something is wrong with os not the hardware here. [17:33] Is it perhaps sleeping instead of shutdown? [17:33] node1: Why do you think it is not the hardware? [17:33] Does this happen if you select shutdown rather than press the power button [17:36] Or just run "sudo shutdown now" [17:37] Using shutdown or poweroff -f , it works but at the end battery led is still continous runing. [17:37] I need to again press the power button for 10 seconds to completely off my laptop. [17:38] I have another disk external through that i have tried booting it and making it poweroff it works effectively but not with this Ubuntu focal. [17:39] Even i have checked every things inside hardware upto the voltage on the circuits everything looks great. [17:39] The problem is with Ubuntu. [17:40] try Puppy Linux [17:41] Or any mallacious code which is might be inside it.[I'm not sure] [17:42] That's what i would like to confirm is this problem is with me or with others? Might be someone has filled a bug regarding such incident? [17:42] let's not recommend any other distros but try to find a solution for the issue, shall we HHauser? [17:43] node1: Not that it's anything useful, but one of the things you learn by trying different operating sysgtems is that sometimes hardware problems exist and some systems don't reveal them, Either they know about them and they work around the problem, or they just ignore it. [17:44] node1: If it's _not_ a hung mount, the most frequent solution is to try a different kernel. [17:44] node1: I did a focal reinstall a few days ago and it has very long shutdown after reinstall but I have looked into it [17:44] jhutchins, Yes trying with different kernel would might solve this problem [17:45] Maybe xanmod kernel? [17:46] I use that sometimes [17:46] But you know when i reinstalled the same version of Ubuntu on my other external disk and booted it using usb, i found it works perfectly. [17:46] node1: edit I did not look into the problem as it does shut dow after several minutes [17:48] Well there is solution to reinstall the Ubuntu again, but that's not what i would likes to do this time. I would like to goo deeper and find the root cause. [17:48] node1: maybe you installed a kernel extension of some sort [17:48] Because something fishy is going on thats for sure [17:48] Shutdowns are tricky, because the system isn't accessible, and the record is usually cleared when it's reset or the power is killed. [17:49] The Ubuntu installer should be solid enough that repeating an install should have the same results as the first try. [17:49] Apart from secure boot options does anyone here would like to suggest if somebody using Ubuntu or Linux as distro? [17:50] Like i use Ubuntu for my personal computing, how would i protect myself from external threats? specially from browsers? [17:50] Keep them up to date [17:51] I think that's the biggest thing [17:51] Up to date means? upgrade it? [17:52] Yes [17:52] Just install updates frequently [17:52] I think that's mostly all you can do [17:53] ok [17:54] Though some use browser snaps for the container [17:56] okay [17:59] A decent firewall at the router is a good defense. [18:04] From a very limited attack vector though [18:07] I've never really bothered that much with security-in-depth [18:07] "don't use stupid passwords", "keep things updated" [18:25] so when I run lsb_release -a I see 20.04.3, however I see I'm on 5.13 kernel...how am I on the 5.13 kernel if its supposed to come out with the 20.04.4 release at the end of Feb? [18:30] kur1j: the HWE kernel is 5.13 [18:31] leftyfb: but it seems im on -generic 5.13.0-27-generic? [18:32] ok? [18:32] kur1j: is something broken? [18:32] kur1j: that is the hwe kernel and it's correct [18:33] hmmm is that enabled by default? [18:33] yes [18:33] we are having really weird problems where our GPUs are failing [18:33] I attributed it to kernel versions [18:34] kur1j: then reboot into the previous kernel [18:34] still broken [18:34] then it's not an issue with the latest kernel [18:34] im trying to troubleshoot but this machine is remote so I'm having to walk someone through it...slowly [18:34] nVidia? [18:34] yeah NVidia [18:34] then it's probably a driver issue [18:34] like we refreshed this machine, install all the drivers on it its working [18:35] next day, they messaged me and said it doesn't work [18:35] * Maik blames nVidia drivers [18:35] I mean I would tend to agree...but it didn't change [18:36] I had problems with the nouveau drivers freezing the display [18:36] "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure the latest NVIDIA driver is installed and running" [18:39] anyone running Ubuntu 22.04 know if you can get "Heal selection" and "Liquid rescale" to work in gimp simply by installing gimp and gimp-plugin-registry? [18:40] Currently on 20.04 I have to do this workaround: https://discourse.ubuntu.com/t/gimp-woes-in-20-04/15828/14 [18:42] ELFrederich: we only support stable releases in this channel, for questions about 22.04 please join #ubuntu-next [18:42] Maik, thanks... will do [18:47] Hello. How do I export an apparmor profile which is located in the kernel? [18:50] howdy, I installed libncurses-dev on a 18.04, this selected libncurses5-dev. When linking a program I have /usr/bin/ld: cannot find -lncursesw [18:51] aren't paths for lib packages seen by default by ld? [18:51] I ran ldconfig, if that's of any help === russjr080 is now known as russjr08 === scoobydoo_ is now known as scoobydoo === Jubes2 is now known as Jubes === SmokenatorZ66 is now known as SmokenatorZ6 === adamus1red_ is now known as adamus1red === beaver is now known as pong [18:58] oh libncursesw5-dev, with a trailing 'w' === withered_wolf is now known as thoughtfu === thoughtfu is now known as withered_wolf [19:17] yeah, something is absolutely screwed up with Ubuntu and the way its handling these nvidia drivers [19:18] probably more nVidia's fault for not making proper drivers for linux [19:19] i can't figure out a reliable way to install them [19:19] and KEEP it functioning === genii-core is now known as genii [19:19] I don't know if its hardware issues (e.g. overheating), drivers updating for the card, kernel updating and blowing up the drivers [19:19] like its a mess [19:20] not helpful but i'm glad i got rid of nVidia [19:20] OR if its PICNIC problem with users jerking off with installing mess they shouldn't [19:20] yeah unfortunately we can't [19:20] users doing ML work so they rely on CUDA which means no other option really [19:21] can't blame Ubuntu for not working nVidia drivers [19:22] so running apt-get install nvidia-driver-470-server doesnt work...but running the GUI update and it works? or running ubuntu-drivers autoinstall doesn't work either? [19:22] like its inconsistent on what "makes" it work [19:22] its fickle at best [19:24] I've had the "most" luck with "ubuntu-drivers autoinstall" to get the drivers installed [19:25] kur1j: There are a LOT of people who are very happily running nvidia hardware with a variety of drivers and sources and NO problems. [19:26] kur1j: I think one thing you're seeing is that upgrading through nvidia's packages and utilities follows a different path from internal Ubuntu package management, and there's more than one scheme within Ubuntu. [19:29] last year I booted several distros from USB and they all had problems with the Nouveau driver freezing, which surprised me. [19:31] jhutchins: I'm not disagreeing it works. we have 50+ machines on various versions of ubuntu 16.04, 18.04, 20.04. The problems seem to crop up when things "get updated" kernel updates, driver updates, etc. Like the kernel goes from 5.11 to 5.13 automatically, reboot, nvidia driver breaks...even though we used the native "ubuntu-drivers autoinstall" command to install the drivers [19:32] running random apt-get purge nvidia-* and reinstalling with various methods somehow works [19:33] kur1j: I use an installation that uses dkms to manage the actuall driver in-use, and a packaged wrapper that sees to updating it when the kernel gets updated. [19:33] specifically what? [19:33] Having to deal with third-party drivers when there's a kernel update is as old as managed packages on Linux. [19:34] (It's one of the reason real Linux admins maintain their console skills.) [19:34] kur1j: It's a non-Ubuntu distro, so the specifics would be off-topic here. [19:35] well "ubuntu-drivers autoinstall" is supposed to be the native ubuntu managed nvidia driver install path [19:35] Still, it seems like getting a handle on what steps are actually required and how to trigger them is the trick. [19:35] which included DKMS [19:36] kur1j: Which is great unless somebody decided there was a bigger shinyer version number and cheated. [19:36] kur1j: give me one sec... [19:36] kur1j: this has sparked something in my memory about `ubuntu-drivers` and gpgpu and some possible bugs. i feel like it should have been solved [19:40] I believe part of it may be a mismatch between the tools and the driver. So the driver may install 470, but the tools don't get upgrade (or vice versa). You can check that you have both the 470 driver and nvidia-utils-470-server [19:42] hmmm [19:43] i'm digging through my past history, because there was a bug that got reported by a partner re: the server drivers, and one thing that popped up was `ubuntu-drivers` not always behaving as it should. but that should have been fixed in October [19:43] what is the recommended fool proof way [19:43] I don't have a public bug [19:43] of installing it [19:44] https://help.ubuntu.com/community/NvidiaDriversInstallation is the stated "public" way [19:44] which is what you're doing. it could be an issue with making sure to specify `--gpgpu` or setting a specific driver version rather than `autoinstall [19:45] well thats whats crazy is it "works" but then like if the kernel gets updated something breaks [19:46] the best way I have figured out how to get it back working is purging all of nvidia and running those steps again..._sometimes_ it works sometimes it doesnt... [19:46] then sometimes just running the update through the GUI works? [19:46] its super inconsistent [19:46] and then I can't get it back in the "jacked up state" [19:51] on a kernel update, it should be rebuilding dkms. Is this on baremetal, vms, or in a cloud? [19:51] baremetal [19:51] laptops [19:51] ok, so these are desktop installs with nvidia cards...interesting... [19:52] yup [19:52] lambda labs laptops [19:52] https://lambdalabs.com/deep-learning/laptops/tensorbook [19:53] do they have their own firmware and drivers or is it stock Ubuntu? [19:54] we reformat them and put bonestock ubuntu images on it [19:54] this same thing happens with other systems [19:54] Dell workstations [19:54] supermicro servers [19:55] if the kernel changes...its random if it will have a functioning nvidia driver after boot [19:56] we have this in ansible so we image it with the default image bone stock, run ansible on it which installs the drivers and our LDAP stuff [19:57] and then it will run for some period of time, kernel updates. if it works I don't know about it, but if it breaks I get an email from someone bitching about it lol [19:57] are you seeing any errors in `dmesg` when it happens? [19:59] just the same error about nvidia-smi not being able to communicate [19:59] ill see if I can get some better logs next time it happens [20:00] but usually when I get it, the person is all pissy they can't work so I'm just trying to get it back functioning so they don't throw me under the buss that I'm the cause of their issues [20:00] when I get a less cranky user I'll see if I can dig into it more and capture some logs [20:00] I will say that 18.04 I've had a lot less issues [20:01] 1/10 it will happen vs 9/10 on 20.04 [20:01] you should check if nvidia-smi ends up in a mismatch too. nvidia-smi -h prints out a ton of junk, but the first line gives the version. it may be that nvidia-utils failed to upgrade with the driver. [20:02] ill add that to my notes to check [20:02] kur1j: Any chance you could set up a standby laptop and just swap it when there was a problem so you'd have a specimine to work on? [20:02] and send me one of those $4000 laptops too, so I can help troubleshoot :) [20:02] hi guys, im tryng to connect to my ubuntu pc that keyboard,but nothing happen, some help please?https://www.trust.com/it/product/17911-adura-wireless-multimedia-keyboard#downloads [20:03] 18.04 seems to be... "automatic update happens with kernel change..." "nvidia-smi version missmatch..." "reboot..." problem fixes it self [20:03] freetester: I don't know that keyboard, but does it require proprietary drivers? [20:03] 20.04 seems to be..."automatic update happens with kernel change..." "nvidia-smi barfs"..."reboot" nvidia-smi barfs...start uninstall reinstalling etc. haha [20:04] jhutchins most of them are tied up and we don't have spares we keep ordering them and people keep snatching them up and using them due to chip shortage [20:04] I think we have like 25-30 of them at this point at various generations [20:05] i dont think so, it used its usb key, and in the manual page nothing to mention about driver... probably yes but i cant find anything about [20:05] jchittum thank [20:07] freetester: my quick check says it shouldn't. could you provide a little more info? what version of Ubuntu? [20:07] freetester: try: lsusb [20:07] in a terminal, and see what it lists [20:10] jchittum ubuntu 21.10 [20:10] wait i attach on pastebin result of lsusb [20:11] https://pastebin.com/XJG2PrtU === dl is now known as Guest3545 === Guest3545 is now known as deathlife [20:13] hello!!! [20:14] freetester: Line 7 appears to show the keyboard properly detected. [20:14] yes i saw it [20:15] but it doesnt work [20:15] some advice or idea? [20:16] freetester: Do the lights respond? Do the trackball or it's buttons do anything? [20:17] freetester: Does the wired keyboard work normally? [20:18] no nothing respond but the keyboard is on [20:18] freetester: How do you know it's on? [20:18] the normal wired keyboard work properly [20:19] for the red light inside [20:19] freetester: I will assume you booted the system with the keyboard attached ... [20:19] does keyboard work in the boot settings menu? [20:20] freetester: There might be a setting in the BIOS for "Legacy USB" devices or something like that, you might try enabling that. [20:20] yes [20:20] start with it [20:21] i ll goo in the bios to take a look [20:21] see u in 5 minute [20:21] yeah, maybe you can use it in the bios at least [20:22] Keyboards are such a basic standard that fortunately almost nobody tries to mess around and require special drivers or anything. [20:23] yeah, I wonder if it's even possible to have a keybaord with proprietary drivers for [20:23] it would fail in the boot menu, no [20:23] yeah, for all the basic functionality of keyboards they _should_ just work on Ubuntu. the prorprietary stuff i see is about setting macros and such [20:23] so it's software to configure the keyboards, not the basic functionality [20:23] hello i have a problem in ubuntu 18.04 i try like two days to make upgrade to a version 20.04 and i get message [20:23] yeah, that makes more sense [20:23] what message? [20:24] Please install all available updates for your release before upgrading. this a message [20:24] i make updates and doing everything but is not work [20:25] maybe sudo apt dist-upgrade [20:25] i do [20:25] oh, ok [20:25] nothing [20:27] how i can please make upgrade to 20.04 please? [20:28] you could force it by editing the source lists manually [20:28] someone might have a better recomendation though [20:29] i check everything [20:31] is graphviz the best out there? I am looking for an advanced .dot editor that would have drag/click/arrow/line/connect facilities. Any clues? [20:31] !eolupgrade [20:31] End-Of-Life is when security updates and support for an Ubuntu release stop. Make sure to update Ubuntu before it goes EOL so you get updates promptly for newly-discovered security vulnerabilities. See https://help.ubuntu.com/community/EOL and https://wiki.ubuntu.com/Releases for more info. Looking to upgrade from an EOL release? See https://help.ubuntu.com/community/EOLUpgrades [20:31] darksis: That last part might be useful. [20:32] "Upgrade before you're EOL" is pretty useless for people who are already having problems. [20:33] Intelo: What 's a .dot editor? [20:34] this what i get manytime Err:8 https://mirror.isoc.org.il/pub/ubuntu bionic-archive Release [20:34] that link has the manual upgrade instructions [20:34] then why is not give to me make a upgrade? [20:35] darksis: whats the line following the line you just pasted? [20:36] https://help.ubuntu.com/community/EOLUpgrades [20:36] darksis, you should disable/purge your ppas [20:36] MattWThomas: 18.04 LTS is not EOL, yet [20:37] this not really help to me i do everything [20:37] ioria how? [20:37] tomreyn: it's just that the manual steps can be used outside EOL [20:37] not necessarily a good idea, but it should work [20:38] darksis, ppa-purge or just try to disable them in Settings -> Software& Updates [20:38] MattWThomas: might work, but it's not the recommended approach [20:38] tomreyn: fair [20:38] ioria this possible make in commands? [20:39] darksis: can you show the full output of: sudo apt update - you could post it to https://paste.debian.net for example [20:39] tomreyn: Could you post the recommended approach so we can see if that's what he's doing? [20:39] darksis, yes, you comment your .list files in /etc/apt/sourcres.list [20:39] *sources.list [20:39] darksis, ot /etc/sources.list.d [20:40] jhutchins: do-release-upgrade on CLI or update-manager -c for GUI [20:40] darksis, grep -r -i ppa /etc/apt/ [20:41] !paste [20:41] For posting multi-line texts into the channel, please use https://paste.ubuntu.com | To post !screenshots use https://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [20:41] jhutchins: i would think this is what was attempted and produced the "Please install all available updates for your release before upgrading." message, though. most likely due to the unsuable apt source. [20:41] darksis, grep -r -i ppa /etc/apt/ | nc termbin.com 9999 [20:42] this what i have in list [20:42] https://paste.ubuntu.com/p/kBn8f6vZff/ [20:43] that looks good to me [20:43] yes but not upgrade [20:43] darksis, grep -r -i ppa /etc/apt/ ; what's the output ? null ? [20:43] there could be something in sources.list.d [20:43] jhutchins google graphviz dot [20:44] jhutchins: after *successfully* updating package information from currently configured apt sources and installing all pending updates *successfully*, update-manager -c should display this: https://i.imgur.com/pRK1dhJ.png [20:44] which is what iora is helping you search for [20:44] not work grep -r -i ppa /etc/apt/ | nc termbin.com 9999 [20:45] darksis, just run : 'grep -r -i ppa /etc/apt/ ' [20:47] this what i get https://paste.ubuntu.com/p/Yy57jgWYH8/ [20:47] after i make the commands grep -r -i ppa /etc/apt/ [20:47] i think the root cause of darksis' problems (possibly in addition to unsupported PPAs) is that their apt is configured to load package info for a "bionic-archive" repository from a mirror which does not have this component https://mirror.isoc.org.il/pub/ubuntu/dists/ [20:48] how i do it is have commands please? [20:48] darksis, you hace a lot of ppas [20:48] *have [20:48] yes [20:48] what i need to do about it? [20:49] darksis, and honestly i don't knoe this server mirror of mirror.isoc.org.il [20:49] me too [20:50] darksis, run this 'do-release-upgrade -c' [20:50] active PPAs from darksis (padding added by myself): https://termbin.com/vsep [20:51] now i see the upgrade to 20.04 [20:51] (others were either from .save files or commented out) [20:52] darksis, yes, you see that but some external sources stop it [20:52] then how i fix it please? [20:52] foreign packages/package versions (fix apt sources first): apt list --installed | grep ',local\]$' | nc termbin.com 9999 [20:52] darksis, if you ask me, purge all your ppa, change your sources.list to an official mirror [20:53] how? [20:54] darksis, ls /etc/apt/sources.list.d | nc termbin.com 9999 === Kristine_ is now known as Kristine [21:04] how do people feel about rm /etc/apt/sources.list.d/* [21:04] that would remove everything except the official ubuntu repos [21:18] not work === diskin is now known as Guest3608 === diskin_ is now known as diskin [21:18] is not make upgrade someone please? [21:20] MattWThomas: the packages would remain though, better to use ppa-purge to get rid of them and revert to the default state [21:21] darksis: when you try to upgrade what's the error it gives? [21:22] on sec i show to you [21:22] ok [21:27] Eric this what i see https://paste.ubuntu.com/p/jbH7Ndzj8d/ after i make update [21:28] ah [21:31] darksis: type "tail -v -n+1 /etc/apt/sources.list.d/*" and paste please [21:33] https://paste.ubuntu.com/p/6hP3vm3WwM/ [21:35] you see Eric? [21:35] darksis: odd, it looks like its trying to get bionic-archive Release but it's commented out in the sources.list [21:36] darksis: just see one more type 'grep -i "archive release" /etc/apt/sources.list' what does it give you? [21:36] is there a "#" at the start? [21:37] i see it read but not with # [21:38] oh [21:39] something like this? deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release [21:40] yes [21:41] ok, type "sudo nano /etc/apt/sources.list" and add a "#" at the start of the line [21:42] then save with ctrl+o and exit [21:42] Eric add to where # ? [21:43] at the very start of it, #deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release [21:45] if you want you could run sudo sed -i 's@deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release@#deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release@' [21:45] sorry, sudo sed -i 's@deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release@#deb http://mirror.isoc.org.il/pub/ubuntu bionic-archive Release@' /etc/apt/sources.list [21:48] https://paste.ubuntu.com/p/CjrHZ8WBJN/ Eric [21:48] not work [21:48] darksis: did the sudo apt-get update work? no Err? [21:48] err [21:49] https://paste.ubuntu.com/p/GQqcgw6JHW/ take Eric [21:51] darksis: ok i think i see the problem, if you go to https://mirror.isoc.org.il/pub/ubuntu/dists/ there's no bionic-archive [21:51] yes [21:51] i think the root cause of darksis' problems (possibly in addition to unsupported PPAs) is that their apt is configured to load package info for a "bionic-archive" repository from a mirror which does not have this component https://mirror.isoc.org.il/pub/ubuntu/dists/ [21:52] i joined late *shrug* [21:52] i didn't have time to guide, though :-/ [21:53] what i need to do please? [21:54] darksis: type sudo sed -i 's@deb http://mirror.isoc.org.il/pub/ubuntu/ bionic-archive@#deb http://mirror.isoc.org.il/pub/ubuntu/ bionic-archive@' [21:54] darksis: sorry type sudo sed -i 's@deb http://mirror.isoc.org.il/pub/ubuntu/ bionic-archive@#deb http://mirror.isoc.org.il/pub/ubuntu/ bionic-archive@' /etc/apt/sources.list [21:56] darksis: you probably want to enable the universe repo too [21:57] darksis: sudo sed -i 's@#deb http://mirror.isoc.org.il/pub/ubuntu/ bionic universe@deb http://mirror.isoc.org.il/pub/ubuntu/ bionic universe@' /etc/apt/sources.list [21:57]