[16:58] <vicky45> i'm trying to install ubuntu studio 20.1 in 4 gb ram which is giving notification "the system does not have enough working memory. At least 4gb is required". Is there any way to install?
[16:58] <Eickmeyer[m]> vicky45: That was changed before the beta, you need to download a more recent version. Check https://ubuntustudio.org/download
[17:00] <Eickmeyer[m]> vicky45: That said, less than 4GB of RAM isn't enough to run many of the applications included. Using less than 4GB of RAM is highly discouraged.
[17:00] <vicky45> I downloaded the image yesterday only. Is the restriction changed today?
[17:01] <Eickmeyer[m]> vicky45: It changed before the beta release. Let me double-check to make sure that got pushed.
[17:03] <vicky45> "ubuntustudio-20.10-beta-dvd-amd64.iso" is the file name which is downloaded yesterday.
[17:04] <oerheks> 20.1 = 20.04.1 or 20.10 ?
[17:05] <Eickmeyer[m]> vicky45: The requirement was lowered to 2GB 7 days ago. I'm in a meeting right now, but I'll check on this as soon as possible. You might also try downloading a daily image at https://cdimage.ubuntu.com/ubuntustudio/dvd
[17:05] <Eickmeyer[m]> *17 days ago\
[17:07] <vicky45> 20.10, kernel version : 5.8.0-20
[17:10] <vicky45> Thanks for the reply Elickmeye, I will download it tomorrow and check anyhow due to this I would know the support option in Ubuntu. :):)
[17:23] <vicky3> is there any command option to skip first installation step in calamares??? Asking just for curiosity.
[20:52] <Kraus> I'm curious, was there some recent Ubuntu update that started screwing with nameserver IPs? or something to do with nameserver resolve?
[20:58] <Kraus> What happens at 127.0.0.53?
[20:58] <corrinado[m]> I'm assuming you're on a 20.04 base?
[20:58] <corrinado[m]> I haven't seen anything like that from the 20.04 updates
[20:59] <Kraus> Yes, 20.04
[21:00] <Kraus> Both my workstation and server's resolv.conf are pointing to 127.0.0.53 and I'm not able to resolve LAN hostnames. "ping: (or ssh): hostname: Temporary failure in name resolution"
[21:00] <corrinado[m]> Port 53 is typically DNS. But I'd expect that to be written as 127.0.0.1:53
[21:02] <Kraus> What's weirder is this seems to have started sometime during the night(?). I was able to SSH just fine at least a day or two ago.
[21:03] <corrinado[m]> Using DHCP from your router?  Have you tried to reset it?  I've found that some consumer-grade devices will fall down with DHCP occasionally.
[21:05] <Kraus> Reset the router, no change. Rebooted both computers with the issue, no change. Changed the nameserver to 192.168.1.1 (the router) which fixed the problem until the computer reboot, then it reset the nameserver to 127.0.0.53
[21:06] <Kraus> So.. how can I find out what's going on at 127.0.0.53?
[21:07] <Kraus> Wait a minute.
[21:07] <Kraus> ....
[21:09] <Kraus> Nope, okay. I changed resolv.conf to read `nameserver 127.0.0.1:53` to see if that would also fix it, and it didn't work.
[21:10] <Kraus> Unless I have to restart a service
[21:11] <Kraus> (which apparently I don't, because when I switched it to 192.168.1.1 it fixed it instantly)
[21:17] <Kraus> Yeah, looking at my history, I can determine I last successfully resolved hostname through ssh about 2-3 days ago. So... something happened on both my machines since then that is now preventing this.
[21:17] <oerheks> yes, until you reboot..
[21:17] <oerheks> use  /etc/resolvconf/resolv.conf.d/tail >> https://askubuntu.com/questions/1012641/dns-set-to-systemds-127-0-0-53-how-to-change-permanently
[21:17] <Kraus> Right, I saw that thread.
[21:17] <Kraus> The question is, why did this suddenly start happening in the first place?
[21:18] <Kraus> A botched update?
[21:20] <Kraus> Because the only thing I've done on my server is run updates, It has to be an update.
[21:27] <Kraus> https://askubuntu.com/questions/1244860/dns-issues-after-upgrading-to-20-04
[22:26] <guiverc> FYI: only, I just saw https://askubuntu.com/questions/1283513/ubuntu-studio-20-10-require-4gb-ram (it doesn't need an answer!) where user says 2GB is acceptable [via https://ubuntustudio.org/download/] but *groovy* won't install in it (reports 4GB needed)..  This maybe known (site due to change on groovy's release), but posted here as FYI in case it's not in your plan already
[22:28] <Eickmeyer[m]> guiverc: It appears to have been an issue in the beta, apparently the change I made didn't make it in time for freeze. If one were to upgrade calamares-settings-ubuntustudio on the beta, that would be fixed.
[22:29] <guiverc> thanks Eickmeyer[m] :)
[22:30] <Eickmeyer[m]> guiverc: That or I totally botched it. Looking at the changelog, that apparently didn't make it.
[22:33] <Eickmeyer[m]> guiverc: Apparently I did the change but forgot to upload to the archive. *facepalm*
[22:33] <guiverc> it was caught !! that's what matters!
[23:06] <guiverc2> if you need bug filed (sru etc), I'll do it & can report back to OP on askubu; maybe the user will feel connected/contrib-wise?; one less (petty) task for you Eickmeyer maybe
[23:08] <Eickmeyer[m]> guiverc2: Shouldn't, need an SRU since it's not released yet. The release team just needs to sign-off on it. The diff is tiny tiny tiny. https://launchpadlibrarian.net/501916238/calamares-settings-ubuntu_1%3A20.10.9_1%3A20.10.10.diff.gz
[23:08] <guiverc2> :)  even better
[23:09] <Eickmeyer[m]> guiverc2: You can feel free to report that it was an oversight that should be fixed in the daily builds within 48 hours.
[23:11] <guiverc2> it was reported by tester on askubu, I followed up here, you've put fix in motion.. no need for more
[23:12]  * guiverc2 suspects lp stats & bug fixes on lp won't matter to you
[23:12] <Eickmeyer[m]> Yeah, not really.