[00:08] jeez there's a lot of people here [00:08] don't worry most are working or asleep or something [00:08] We are quietly judging you [00:09] * CouchOkie does feel quietly judges [00:10] everybody is watching [00:10] question. how do I unlock a 19.10 usb I want to rewrite because the computer doesnt see boot information. It seems to be locked to read only. How do I change that? [00:10] avion, you mean you want to write data to a live usb [00:11] yes? [00:12] rany not quite. I have a usb and I want to overwrite it all as a persistent 1910 ... https://pasteboard.co/J53IEUP.png [00:12] right now it is not a boot medium. I did not make it. [00:13] ah I see, I dont know how to do it manually but look into unetbootin [00:13] it does that automatically for you [00:14] i followed some webpage directions. maybe I needed a sudo [00:14] I will try it again. thanks. better just to redo it. [00:15] CouchOkie, there are always a lot of people "apparently" here. I expect that they can scroll back and learnsomething if they eer get around to it. [00:16] or if their name gets called. [00:17] I am usually afk but i visit occasionally [00:17] irc logs are public, no need to scroll back ;) [00:20] and the logs go back to 2004. impressive [00:54] Hi All [00:55] Can we upgrade to ubuntu 20.04 LTS from 18.04 ? I tried and getting this There is no development version of an LTS available. [00:55] To upgrade to the latest non-LTS develoment release [00:57] kolaman: what shows ' grep -i ^prompt /etc/update-manager/release-upgrades ' ? [00:57] kolaman, try asking in ubuntu+1 too [00:57] Prompt=lts Bashing-om [00:58] isn't ubuntu 20.04 lts available for release ? [00:58] not yet, soon [00:58] typically, LTS upgrades are not released until the first .1 release (typically in July) [00:58] kolaman: Should workie - #ubuntu+1 for continued assistance. [00:58] ah ok so to upgade I need to wait for july pragmaticenigma [00:59] kolaman: https://help.ubuntu.com/lts/serverguide/installing-upgrading.html says that "-d" is used for upgrading LTS to LTS before the first point release. I expect that after 20.04 is released (tomorrow) you will be able to use do-release-upgrade --devel-release to upgrade. The recommendation is to wait for 20.04.1 before upgrading. [01:00] Jordan_U: that isn't correct.. .the -d enables the development channel. meaning that you would get the next version, however, as soon as 20.10 is started, the system will update to that [01:00] kolaman, there might be a way to upgrade to a pre-release version, but that's not for the context of this channel. and we about 1 day away. [01:01] From https://help.ubuntu.com/lts/serverguide/installing-upgrading.html: Upgrading to a development release is not recommended for production environments. [01:01] Where should I install a local 32bit library? Looking for an equilavent for /usr/local but for 32bit [01:01] which also would apply to someone running Ubuntu on their daily use machine [01:02] Thanks pragmaticenigma , I'll wait for one more day (23 started in my region) :) [01:02] pragmaticenigma, would it still tag to 20.10 if update-manager is set to lts? wouldn't it try to find a 22.04 lts? [01:03] pragmaticenigma: Since there isn't a direct upgrade path from Ubuntu 18.04 to 20.10 I would not expect --devel-release to upgrade to it either. Are you saying that the documentation at https://help.ubuntu.com/lts/serverguide/installing-upgrading.html is wrong? Do you have a better reference? If so, we should edit the documentation. [01:05] Jordan_U: Your question doesn't make any sense to me [01:06] you probably meant mine [01:06] pragmaticenigma: I quoted information from the official documentation. You said that information was wrong. If it is wrong, then the documentation should be fixed. [01:08] Jordan_U: I'll clarify... Using -d should only be used if the user intended to remain on the development channel. It should not be recommended as a way to upgrade a machine to 20.04. [01:11] If a user wants to be on 20.04 at time of release, the best method is to install fresh. The upgrade path hasn't been finished and using -d doesn't force the upgrade, it places the machine into the development release channel. [01:11] pragmaticenigma: That doesn't seem to match what the official documentation says "If you want to update before, e.g. on a subset of machines to evaluate the LTS upgrade for your setup the same argument as an upgrade to a dev release has to be used via the -d switch." There is no warning that using do-release-upgrade -d to upgrade to 20.04 after release, but before release of 20.04.1, will lead to your [01:11] Ubuntu install trying to upgrade to 20.10 before it is released. I also think that it is unlikely that that is how upgrades would work, from my experience and understanding of how upgrades work. Should we add a warning about to the documentation? If so, do you have a source for your information? [01:12] Jordan_U: in the very same article you quoted is a warning about using the "-d" switch. "Upgrading to a development release is not recommended for production environments." Which applies to everyday machines. [01:12] if someone is has a test system, and doesn't mind buggy behavior, then sure "-d" to your hearts content [01:13] pragmaticenigma: Indeed, which is why in my original comment that is what I said. We are in agreement on that point. We are not in agreement about your second point, and I am becomming more certain that you are wrong on that point. [01:14] Jordan_U: I'm trying to track down where I found my information [01:17] the question is, after tomorrow, and when 20.10 development starts, but there is no 20.04.1 yet. And someone on 18.04 lts uses the -d parameter, will the result be 20.10 development version, or 20.04 lts (release version, but not recommended cause point release is not out) [01:18] do-release-upgrade -d should use whatever this file is saying is 'new' https://changelogs.ubuntu.com/meta-release-development [01:18] I thought prompt on /etc/update-manager/release-upgrades still took effect. [01:18] and I think the non--d version uses https://changelogs.ubuntu.com/meta-release === zbenjamin is now known as Guest46282 === zbenjamin_ is now known as zbenjamin [01:26] Jordan_U: What sarnold had said... that's what I was meaning. When the file that is at "https://changelogs.ubuntu.com/meta-release-development" has a version number greater than the currently installed version number, I believe it triggers the upgrade prompt. I don't believe the "developer channel" has a concept of LTS versus regular release, and looking at the file that was posted, there doesn't appear to be anything flagging [01:26] those releases as LTS and regular. [01:31] hi does anyone run hashicorp vault on ubuntu? [01:32] im having some trouble starting it and not understanding what im doing wrong [01:33] so what will be the result of doing the instructions on the help page, after 20.10 development starts, but before the point release of lts is out? [01:51] jStefan: which help page? [01:52] pragmaticenigma, https://help.ubuntu.com/lts/serverguide/installing-upgrading.html [01:54] jStefan: When the link that sarnold posted is updated to include 20.10... you will receive a prompt that an upgrade is available. that happens regardless of the point release [01:54] So i'm in a bit of a pickle here, having issues running 'make' and it seems the issue is with my python installs: https://paste.ubuntu.com/p/2KjK2YdHnG/ [01:55] looks like i might have python3.6 all mixed up here but i'm unsure as to how i would be able to correct it without messing up my whole system [01:56] jStefan: The "point releases" are when packages are merged into the main repos and new images are released for the LTS to reduce the number of updates a user has to perform after install. [01:56] jStefan: Updated/patched packages are merged into the main repos [01:59] pragmaticenigma, so what the help page says will not wok if development of 20.10 started and there's no point release 20.04.1 yet [01:59] work* [02:01] jStefan: You're mixing things up [02:01] jStefan: Let's simplify. If you prefer or require the usage of LTS releases. Do not use the -d option with do-release-upgarde [02:03] pragmaticenigma, the help page is not that simplified, it mentions -d [02:03] jStefan: you're also mixing up terms and parts of what was said [02:06] pragmaticenigma, what I understood is, if you want to upgrade from 18.04 to 20.04 after it's released but before the point release is out you need -d. But what happens if 20.10 is the latest "Development version" ? [02:06] jStefan: That is wrong [02:06] that is what I'm trying to tell you [02:07] jStefan: at the very least, that is incomplete [02:08] jStefan: Officially there are LTS releases and normal/regular releases. There is also development releases. When you use the "-d" option with "do-release-upgrade" you will join that machine to the development channel. Which is completely different and has nothing to do with the release cycles of LTS and regular releases [02:09] pragmaticenigma, then the help page needs to be fixed [02:10] upgrade in your settings give 'to LTS' or 'to any release, pretty clear [02:10] jStefan: there is nothing wrong with the page. It clearly states that using the "-d" option "upgrades to a development version of Ubuntu" [02:10] carefull with the -d option, it might mix things up [02:10] "LTS systems are only automatically considered for an upgrade to the next LTS via do-release-upgrade with the first point release. So for example 14.04 will only upgrade once 16.04.1 is released. If you want to update before, e.g. on a subset of machines to evaluate the LTS upgrade for your setup the same argument as an upgrade to a dev release has to be used via the -d switch. " [02:11] that's a bit misleading. [02:11] housecat, definitely misleading [02:12] I would agree partially... I don't think there is anything misleading... My feeling is the page is incomplete [02:12] setting ourselves in that point in time, it I read it as to go from 14.04 to 16.04 before any point release you need -d [02:13] You have to read the entire document from top-to-bottom... you would then have seen the part about the development release channel as well as the warning. [02:13] If you were about to read a book, would you start with the last page? or would you start from the beginning? [02:13] dear lord [02:14] n #linuxmint [02:15] next week, when the development of 20.10 starts, so -d would be funny to see [02:15] it'll be a while before -d starts pointing at 20.10 [02:15] by friday, 20.04 would be officially out, the document suggests to use -d because there is no point release yet. that would only work as long as 20.10 doesn't exist. that's misleading. [02:15] .. [02:15] i'm unsure whether it'll actually happen before or after 20.04.1 comes out. it takes a while, so there's a good chance it'll be after [02:16] wrong, that is utterly correct [02:16] istr last time around it (deliberately) happened after [02:16] but anyway. that really should be clarified somewhere :\ [02:16] development starts as the name is announced? [02:17] oerheks: do-release-upgrade -d does not point to the next development release immediately after development starts. [02:18] housecat: where do you have that information from? [02:18] that is what happened with focal, IIRC [02:23] housecat: do-release-upgrade -d changes the URL it normally monitors for upgrades "https://changelogs.ubuntu.com/meta-release" to the development channel "https://changelogs.ubuntu.com/meta-release-development" ... when that second link gets its information updated... that's when the system update tools will start notifying there is a release to upgrade to. I have not been able to find any documentation that dictates when that [02:23] file will be updated, so I would take that to mean it is completely up to the development teams to choose when they publish and update that file. [02:23] pragmaticenigma: I'm well aware of how do-release-upgrade works, thanks. [02:24] It's unfortunate that changelogs.ubuntu.com doesn't seem to be under version control. It'd make it significantly easier to educate people who rely more on Google than on experience. [02:24] housecat: you're making baseless assumptions without putting any proof of your statements. In all honestly, you don't know, so don't make your assumptions out to be fact without some sort of published documentation on the official ubuntu domain [02:26] in any case, i think last time i had to upgrade an lts "early", i did what oerheks suggested and changed the prompt to any release. then changed it back after the update. [02:27] i really don't remember all that well, it was a few years ago xD [02:27] jStefan: That will work, yes... part of the point release wait is because at the .1 release point, the upgrade bugs will have been properly worked out [02:28] or at least most of the bugs will have been addressed [02:28] *whatever you do*, keep a fresh iso on usb ready [02:28] :) [02:28] even better... make a back up of your system before you run any upgrade [02:29] then you have an undo button with less work [02:29] in that last case, we weren't too attached to was on that system had something gone wrong. [02:31] I've learned... when you have a backup... it seems nothing ever goes wrong [02:36] pragmaticenigma: just checked with a release team member and they've confirmed that I'm correct [02:37] can someone tell me why I should continune to use systemd-resolvd rather than what my dhcp provides? [02:37] pragmaticenigma: specifically: < bdmurray> housecat: you are absolutely correct and release upgrades from 18.04 LTS to 20.04 LTS will not be enabled until 20.04.1 and you are also correct that do-release-upgrade -d on Ubuntu 18.04 LTS will point to Ubuntu 20.04 LTS. [02:38] housecat: that's incomplete [02:39] pragmaticenigma: https://paste.debian.net/hidden/3ed61f4b/ [02:39] housecat: it's also hearsay... Until I see it published and documented on an Ubuntu domain website [02:40] housecat: you are taking one persons word... you didn't provide what channel that was stated in... and you posting a link to pastebin (on debian's site no less) is all highly suspicious [02:41] pragmaticenigma: please take a step back and stop bad faith accusations here [02:41] ....Which pastebin you use changes the validity..? That's something. [02:42] 1804 wanting to make a persistent usb of 1910 using the entire 8g usb. -- saw this and was confused. what does this mean --> Mkusb will use ‘the whole device’, actually only the head end (size of the iso file), but the rest of the device is not available. [02:42] el: I won't step back from inaccurate information being handed out [02:43] tripelbb, step by step, https://www.linuxuprising.com/2019/03/create-persistent-storage-live-usb-with.html [02:43] the docs do set an example of -d, my only doubt is what is the expected result depending on which point of time it is performed at. [02:43] oerheks, mij buddy [02:43] pragmaticenigma: inaccurate information is not being given out. an op has intervened to correct information including seeking advice from the release team [02:44] actually i mispeak, the op intervened to prevent inaccurate information being given out by seeking the advice from the release team [02:44] jStefan: If you use do-release-upgrade -d on 18.04 before the release of 20.04.1, you will go to 20.04. If you use do-release-upgrade on 18.04 after the release of 20.04.1, you will go to 20.04(.1). [02:45] housecat, that seems pretty clear. Even if development of 20.10 has been started? [02:45] yes this page more precisely. same site. https://www.linuxuprising.com/search/max-results=12?q=make+persistent+usb [02:45] jStefan: Correct. [02:46] yes this page more precisely. same site. https://www.linuxuprising.com/2019/03/create-persistent-storage-live-usb-with.html [02:53] now it is a 19.10 that wont boot) [02:54] whoa my whole line vanished. [02:56] it did not ask me if I want the dus version as the page said. - then it asks me "if I expect the drive to contain filesystems other than VFAT or ISO 9600" - I dont know if they are talkign about the usb as is (is a wont boot 1910) or as I want it to be. I have a choice of yes not Idontknow. oerheks [02:56] !isitout [02:56] It's not out yet! Come visit #ubuntu-release-party and hang out. Don't forget your party hat! [02:57] (I got the same thing before and said I dont know.) [02:57] tripelbb, start with fat32 [02:57] so I should say no? [02:58] or yes? [02:58] Basically it hung on locked usb the last time but someone here told me that isnt possible so I decided to start over. [02:58] oerheks, [03:00] i think 'N' ? [03:00] the more I read about systemd-resolved the less i like [03:01] !isitout [03:01] It's not out yet! Come visit #ubuntu-release-party and hang out. Don't forget your party hat! [03:03] so I answered Yes I expect filesystems other than those to, and no on the next question about something that was not fat32. took the drive out and in per instructions. now it says select how to ope (the iso file) >> No applications found. click on downarrow, nothing comes up. --- remember I started this by opening mkusb. oerheks [03:07] oerheks, I clicked off that window in disgust. then it looked good in mkusb-plug console. NOW..sbd : YWA : usb has iso9660+ : SMI USB disk (newline) task:'--puer' (then source and target ...terminated by user. == so I gues they were asking about what is already on the drive???Confusion reighns. Help plz. [03:08] should I reformat the drive? [03:09] oh. oerheks dont bother. I am going to start over [03:11] oerheks, I started again. i reinstalled the program today. In the list of What kind of drive do you want to make - a boot drive was not on the list (as it says on the webpage) [03:12] i am going to update upgrade just in case. (helpless I am) [03:12] Anyone has this issue where the Spotify snap would freeze on Ubuntu 19.10? [03:16] oerheks, same thing. maybe persisten live drie means that it is a boot drive (as I assumed the first 3 times. === Dr_Manhattan is now known as Guest72491 [03:22] oerheks, are you still here? and in this? mkusb quit again. it said terminated by user?? [03:22] ok audio question with bluetooth. when running pithos (as an example) the audio switches back to default from bluetooth with song changes. disabling default works but... [03:22] 18.04 [03:24] well this didnt work at all. yet. [03:29] tripelbb, what you trying to make a boot drive out of === Perfec7 is now known as Perfec7[OFF] [03:37] any news on the 20.04lts release? [03:38] cgipython: visit #ubuntu-release-party and hang out :) [03:54] hello, im trying to setup ircd-hybrid.. for some reason I can connect to it locally but when I try to connect from elsewhere the connection times out. I am listening on all available ip addresses and ufw service is not enabled. Any suggetions? [03:55] ubuntu 18 LTS [03:55] hello [03:56] Is it okay to upgrade now from 18.04 to 20.04, or is there more waiting to do? [03:59] Hi everyone, I wanted to know whether the Ubuntu 20.04 LTS has been released? [03:59] still beta [04:00] dmahajan980: tomorrow sometime [04:01] Thanks @Thanos @genhaoqi [04:05] SWE442: https://askubuntu.com/questions/125392/why-is-no-new-release-found-when-upgrading-from-a-lts-to-the-next - see here. [04:07] @kryten thanks [04:14] That new shutdown/reboot thing is just terrible. Too much clicking [04:28] Frustration. I want to write 1910 to a USB. Startup disk creater in 1804. And it says couldn't write the disk image to the device /dev/sdb -- what now? [04:31] Wait. The disc has 19.10 now. It worked. (Scratch head) will try to boot off it. [04:40] Hi! [04:41] is anybody there? [04:43] hello? [04:44] Hi, I'm testing from within pidgin client [04:45] same, is it me or this server is dead? [04:45] @zuwuko [04:45] Hey I'm trying to launch but recive this error http://dpaste.com/27GE6ZY [04:45] I was on freenode a few days ago with some activity [04:45] *launch live wallpaper [04:51] Hi testing from within pidgin client [04:56] brianXS: if you have a question to ask, just go ahead and ask it up front. if people who know the answer see the question they'll answer [05:25] what xmpp server client works with voice calls, video calls, voice messages? [05:25] looking to setup self hosted "whatsapp" or "signal" style [05:26] prosody provide these features? === PowerTower_121 is now known as PowerTower_120 [05:44] i have a couple of files encrypted using gpg with the same passphrase. One of them gives me "decryption failed: Bad session key" error. Is there a fix? [05:44] Rest of the files decrypt fine. [05:48] might try gpg2 on it [05:54] v64, that didn't work [05:54] damn [06:01] Hi everyone, just did a dist-upgrade -d to 20.04 but my laptop brightness control is gone, both the keyboard mapping and the gnome widget. Any tips? [06:01] trying to find where ubuntu stores the solid background colors. I like the blue as its a chalky blue black. Cant find it anywhere in the file structure. Any ideas? [06:04] subfj, I wrote a small perl script to create a background image file and loaded it with eog. [06:07] subfj: do you want to find out what color it is, or do you want to change it? [06:09] grawity i want to copy it to my other windows and mac computers [06:10] subfj, https://drive.google.com/file/d/1MAtp-wEuKTx0pSrJ53LJFuiCO3I48k6P/view?usp=sharing [06:12] thanks JoeBk [06:13] open it with eog then right click and make it wallpaper. [06:13] thinking i need to edit this for 4k res [06:14] change width and height [06:14] ya, saw that [06:14] reinstalling my vm, will do. thanks [06:15] actually it will get scaled to whatever you screen size is. [06:16] oh nice [06:24] subfj: make a screenshot then pick the color using an image editor [06:25] grawity the blue gray looks like drywall, its not a solid color [06:27] hello, can anyone help me? i got error on `apt-get update` and it tells me there is no Release file on repo "http://it.archive.ubuntu.com/ubuntu disco Release" [06:27] I think it's caused by some package i've installed but how to find that? [06:27] simo3n: disco is EOL, see https://help.ubuntu.com/community/EOLUpgrades for upgrade instructions and the path for the old-releases repo [06:28] (that is in fact the cause of the error you're getting) [06:28] okok thank you so much, im looking on it [06:35] housecat, thank you so much, it worked so well :D [06:41] simo3n: you need to upgrade, not just point the repos to old-releases, you're not getting security fixes [06:44] ok ducasse thank you; i just point the repos for the moment, ill upgrade soon [06:48] Hi, i am trying to install libobenblas but I think the link is broken and I am getting this error again and again , https://pastebin.com/rvnp0zb6 [06:48] is there a way to install it? [06:49] fiter: you are running an eol release [06:49] !eol | fiter [06:49] fiter: 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 [06:50] fiter: you need to upgrade to a supported release, see the last link [06:51] ducasse how to add these required deb http://old-releases.ubuntu.com/ubuntu/ CODENAME main restricted universe multiverse to the sources.list? [06:53] change the url in sources.list to point to the old-releases url [07:06] ducasse this mine sources.list , now I put it at the end https://pastebin.com/3w0ZEULc? [07:06] I am talking about these links deb http://old-releases.ubuntu.com/ubuntu/ CODENAME main restricted universe multiversedeb http://old-releases.ubuntu.com/ubuntu/ CODENAME-updates main restricted universe multiversedeb http://old-releases.ubuntu.com/ubuntu/ CODENAME-security main restricted universe multiverse [07:09] fiter: replace all 'pk.archive' with 'old-releases' [07:15] ducasse I have changed and now when I run sudo aptitude install update-manager-core update-manager , get aptitude command not found [07:16] when I run sudo apt install update-manager-core update-manager then I get update-manager is already the newest version (1:19.04.5).update-manager-core is already the newest version (1:19.04.5) [07:16] what should I do next? [07:17] follow the url you were given earlier [07:17] I am using apt instead of aptitude and following that link [07:17] this one https://help.ubuntu.com/community/EOLUpgrades [07:18] do the sudo perl line [07:19] then 'sudo apt update && sudo apt dist-upgrade && sudo do-release-upgrade' [07:19] ducasse when I do the sudo perl line I dont see anything [07:19] good [07:24] ducasse done [07:24] upto here sudo apt update && sudo apt dist-upgrade && sudo do-release-upgrade [07:25] now do that to upgrade, but backup first [07:25] ducasse which one? [07:26] I have ran the above command already [07:26] sudo apt update... [07:26] did it finish upgrading ok? [07:26] Reading package lists... Done E: The repository 'http://security.ubuntu.com/ubuntu disco-security Release' no longer has a Release file.N: Updating from such a repository can't be done securely, and is therefore disabled by default.N: See [07:26] apt-secure(8) manpage for repository creation and user configuration details. [07:28] you can change the sources.list file to replace the security urls too [07:28] ducasse how? [07:29] replace security.ubuntu.com with old-releases.ubuntu.com [07:30] all this is described in detail on the wiki [07:32] ducasse I have replaced, now I re run these commands ? sudo apt update && sudo apt dist-upgrade && sudo do-release-upgrade? [07:32] yep [07:37] I have a computer with 16GB ram that I'm going to be installing Ubuntu Server on. With that much RAM and the fact that it's a server that will never be put into sleep or ever turned off, do I really need a swap partition? [07:38] I'm trying to get access to a fat32-formatted usb stick. I've tried what I know about chown and chmod, but when I go to properties, it keeps telling me that it is owned by root [07:39] Where is it mounted at ? [07:39] What's the path you mounted it on ? [07:39] ducasse done - Filesize:66659170 [weak] Last modification reported: Mon, 20 Apr 2020 22:57:09 +0000E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? [07:39] then I tried sudo apt-get update so I got [07:39] devslash: sudo chmod 777 -Rf /media/steve/42E9-FD42/ [07:40] ducasse Hit:9 http://old-releases.ubuntu.com/ubuntu disco-backports InReleaseHit:10 https://repo.skype.com/deb stable InReleaseHit:11 http://old-releases.ubuntu.com/ubuntu disco-security InReleaseReading package lists... Done [07:40] I usually do -R not -Rf [07:40] devslash: Something tells me that I need something in the /dev/ [07:40] Are you trying to cd to that location [07:40] I want to migrate some mp3s on to it [07:40] fiter: run 'sudo apt update && sudo apt install -f' [07:41] Are you trying to write to it but its read only ? [07:41] ducasse I have run sudo apt update && sudo apt install -f and got Reading state information... Done0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. [07:42] Sbur3: fat filesystems do not support permissions, you need to mount it with right options [07:42] ~ducasse: Have you a miracle command line thing? [07:42] Yea theres mount parameter for setting permissions when you mount the volume [07:43] I don't remember it off the top of my head [07:43] I think uid=1000, gid=10 [07:43] Sbur3: mount -o uid=1000 ... [07:43] devslash: ducasse: So should I eject it and remount it to see what happens? I'm using Ubuntu, but the use would be for an MP3 player. Thought that fat would be better for a non-Linux thing [07:44] Yes [07:44] I use Arch, btw [07:44] The problem is you mounted it as root and your user account cant write to the usb drive unless you add the mount option [07:44] ducasse: When do I do the mount -o thing? [07:45] When you mount it [07:45] mount -o uid=1000,gid=100 /dev/whatever /mnt/whatever [07:45] Oh sudo that [07:46] Sbur3: iirc, the desktop should mount it as your uid if you use that to mount it [07:46] Ducasse have you used ubuntu server [07:46] ducasse: I'm a bit of a newbie to this .... I tend to plug things in and let it mount [07:47] devslash: yes, i run several [07:47] I have a computer with 16GB ram that I'm going to be installing Ubuntu Server on. With that much RAM and the fact that it's a server that will never be put into sleep or ever turned off, do I really need a swap partition? [07:48] devslash: maybe not, but a 2gb swapfile won't hurt [07:48] devslash: Let's say that it is sdc1, would /mnt/ be the same thing or what? [07:48] Yea it would [07:49] You should use the same command but add -o and the rest of that part after mount [07:49] Like I typed it [07:49] devslash: so /dev/sdc1 /mnt/sdc1 ...? [07:49] make sure /mnt/sdc1 exists [07:49] Yea as long as that location exists already in /mnt [07:49] Yea [07:49] or just use /mnt [07:49] No [07:50] You should use subdirectories [07:50] Like /mnt/usb [07:52] it's completely fine to just use /mnt if you don't expect to mount more than one device at any given time [07:57] does anyone have the 20.04LTS update available for them yet? I'm not seeing anything personally when I run the do-distribution-upgrade command on the command line [07:58] was just wondering if it is just me or not [07:58] 20.04 isnt out yet [07:58] it will probably be out sometime in late morning or afternoon though [07:59] bettencb: I prefer waiting for the release candidate when it tells me that it is there. There is a way around that, but I'd discourage it [08:00] so my software updater will just notify me when it's time? This is my first distro upgrade i'll be a part of [08:00] Sbur3: sorry meant for that to go to you [08:00] Sbur3: ^^^^ [08:00] bettencb: which release are you on? [08:00] 18.04LTS [08:00] ducasse: ^ [08:01] then you will be notified on the first point release [08:01] ie 20.04.1 [08:01] ducasse: is that the one schedule in july? [08:01] something like that [08:02] Hello [08:02] ducasse: damn... I thought I'd be able to today. I can't even do a fresh install to get 20.04 LTS yet? [08:02] when it's released, yes [08:02] Do you know what time we can have Ubuntu's Iso? [08:03] ducasse: what does it meant when it says it was scheduled to be released today then? [08:03] Herve33: I'm trying to figure out too [08:03] exactly that :) [08:03] Herve33: possibly not yet I guess [08:03] ducasse: so again? if it's released how do I get it then as Herve33 and I are both wondering how to get the iso [08:04] it's not done yet [08:04] ducasse: lol thanks for the help mate [08:04] join #ubuntu-release-party and wait [08:04] I search minimal.iso for 20.04 [08:04] ducasse: thank you [08:04] ducasse: you def could of lead with that [08:05] Thanks ducasse [08:05] hi [08:06] into a ubuntu-18.04.4 how can I install kernel 4.15 ? [08:06] sacarde: purge the hwe packages [08:06] !hwe | sacarde [08:06] sacarde: The Ubuntu LTS enablement stacks provide newer kernel and X support for existing LTS releases, see https://wiki.ubuntu.com/Kernel/LTSEnablementStack [08:07] but I installed fromn 18.04.4 iso, I have hwe? [08:08] yes, if you install from 18.04 you don't [08:08] doing that I remove 5.3 kernel? [08:09] yes, and install linux-image-generic [08:09] !info linux-image-generic bionic [08:09] linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 4.15.0.96.87 (bionic), package size 2 kB, installed size 16 kB [08:09] can I have dual kernel? [08:10] you can have as many as you want, the latest will be booted by default === shrini-afk is now known as shrini [08:10] you can select another in grub [08:11] but if I remove hwe packages, I remove 5.3 kernel? [08:11] yes, or just install linux-image-generic [08:12] ok.. I understand [08:12] I try... thank you ducasse [08:12] !isitout [08:12] It's not out yet! Come visit #ubuntu-release-party and hang out. Don't forget your party hat! [08:18] hey how do i upgrade to the stable [08:18] i am on the preview version [08:19] !final | mixxit [08:19] mixxit: If you install a development version of Ubuntu Focal and keep up with package updates, then you will be upgraded to the official release of 20.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal. [08:20] mixxit: but it's not out [08:23] says 0 to install [08:23] all good yeah? [08:25] yes [08:25] oh its no t out [08:25] ok i will try again i thought it was out today sorry [08:25] today is not over' [08:26] some friend at work linked me releases note [08:26] i should have read more carefully :D [08:26] join #ubuntu-release-party [08:26] thanks mate! [08:27] wow [08:27] hexchat does not lend itself to the display scaling setting of 200 in ubuntu [08:28] guess i go back to squinting hehe [08:34] why is some mount's ownership changed to systemd-timesync:systemd-journal? [08:43] !isitout [08:43] It's not out yet! Come visit #ubuntu-release-party and hang out. Don't forget your party hat! [09:01] hello, how could it be that the snap file is deleted but files are still readable on mount point? /var/lib/snapd/snaps/core_8689.snap (deleted) on /media/paul/disk type squashfs (ro,nosuid,nodev,relatime,uhelper=udisks2 [09:02] Hello, I'm using Ubuntu MATE 19.10, and I'm installing azpainter from source. When I run ./confifure in the source directory, it gives an error "checking for "/usr/include/freetype2/ft2build.h"... no [09:03] Correction: checking for "/usr/include/freetype2/ft2build.h"... no [09:03] interrobangd: files will continue to exist for as long as they are held open by some program [09:03] hi, how save is it to connect to an online account like google ? they are asking for a lot of permissions [09:03] And then it says, configure: error: (freetype) ft2build.h not found [09:03] interrobangd: which in this case is the filesystem image held open by the 'loop mount' driver [09:04] weird [09:04] The problem i think is that libfreetype, or freetype2 is not installed, but I tried to install both using apt, but the package is not found [09:07] Does anyone know how to install libfreetype or freetype2? [09:08] it's already installed; it's always installed, because it's the library used to put text on screen [09:08] what you need to install is the devel package for it (headers, etc.) [09:09] I think the package is named libfreetype-dev [09:09] oh, okay [09:09] But, it isn't found by apt [09:09] what else does `apt search libfreetype` find? (I actually don't have Ubuntu at hand to check) [09:10] oh, okay [09:11] http://dpaste.com/0PVWZKJ [09:11] It found 4 packages [09:11] libfreetype-dev [09:11] ah yeah, libfreetype6-dev [09:12]