[00:00] <apb1963> huh?
[00:00] <apb1963> my drives are internal
[00:00] <apb1963> sata
[00:01] <tomreyn> so you had removed the usb stick you had installed from?
[00:01] <apb1963> yes
[00:01] <apb1963> it told me to
[00:01] <tomreyn> right, that's good
[00:01] <tomreyn> then just reboot, kepping things as they are, this may already fix it
[00:02] <apb1963> there are 4 options,.. can you tell me which one?
[00:03] <tomreyn> can you tell me which options you see?
[00:03] <apb1963> login, then journalctl
[00:03] <apb1963> systemctl reboot
[00:03] <apb1963> systemctl default
[00:03] <apb1963> ^D to enter maint mode
[00:04] <tomreyn> do the journalctl
[00:04] <apb1963> Yeah except logging in isn't an option,  lol
[00:04] <tomreyn> pressing enter does nothing?
[00:05] <apb1963> whoops... I read it wrong,  Enter for maintenance; CTL-D to continue
[00:06] <apb1963> ^D to try again to boot into default mode
[00:07] <tomreyn> you'll probbaly need to manually run fsck against your root file system because you had long-pressed earlier.
[00:07] <apb1963> So ^D and CTRL-D have two different instructions
[00:07] <apb1963> long pressed?
[00:07] <tomreyn> the power button
[00:08] <apb1963> so maintenance mode?
[00:08] <tomreyn> i need to catch some sleep, need to leave it there. if you do a web search on thismessage you see on screen you'll find instructions on how to proceed.
[00:09] <apb1963> ok, thanks for all the help!!!
[00:09] <tomreyn> yes, enter meintenance mode, fsck whatever your root file system (the main file system) is
[00:09] <apb1963> you can't fsck a mounted file system...
[00:10] <apb1963> and this booted the wrong one anyway I guess.
[00:10] <apb1963> oh well.  g'night!
[00:11] <tomreyn> you can run fsck on a read-only mounted file system.
[00:12] <tomreyn> you may actually need to fix this file system from a live / installer system, though.
[00:14] <apb1963> yeah, from a livedisk is the only way I know of
[00:14] <tomreyn> why this happened in the first place is a question you should examine furhter later. maybe your disk is falling apart. check their status using smartmontools and    smartctl -x /dev/sdXYZ    later.
[00:14] <tomreyn> see you, good luck.-
[00:14] <apb1963> I'll just try to let it reboot from maint mode and go from there
[00:15] <apb1963> disks are old, but fine
[00:15] <apb1963> have smartmon running continuously
[00:15] <apb1963> No idea why it happens...
[00:19] <apb1963> journalctl has a lot of failures
[00:24] <TJ-> tomreyn: solved the Firefox useragent issue - and I was correct, it's a 'duh!' - "privacy.resistFingerprinting = true" causes a common OS and version to be reported, and I had previously set that
[00:25] <TJ-> hence, Windows and v78 instead of Linux and v88! "Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Firefox/78.0"
[00:33] <cuddlyer> I'm trying to delete a thin LVM that is part of a VG that is a whole mdadm device (md2). lvremove hangs for a long time, it seems to take longer the bigger the LVM is and the processes waiting for I/O look like this: https://pastebin.com/raw/T6Xdgbyj Anyone any ideas on how to avoid the long time to delete the LVM? Deleting LVMs within the thin pool seems to be quick.
[00:35] <apb1963> woohoo!  20.04 up and at'em!
[00:35] <apb1963> TJ-, Hiya TJ!
[00:35] <TJ-> cuddlyer: is the metadata on a different PV?
[00:36] <p0a> Hello to get a working python development environment
[00:36] <p0a> what packages should I install?
[00:36] <cuddlyer> TJ: No, I checked it before and it wasn't, I didn't specify a separate place to store it upon thin LVM creation regardless.
[00:37] <TJ-> cuddlyer: speculating here, but that may be the cause, since it's having to remove the metadata and the block mappings
[00:38] <cuddlyer> TJ: Is there a reason why that might take so long? I specified the metadata as 5G upon thin LVM creation.
[00:38] <cuddlyer> 5G is quite big I believe but I wanted to ensure I didn't run out.
[00:39] <TJ-> cuddlyer: it's not the size (if my hypothesis is correct) it's the fact metadata and data are on the same PV (MD raid 10) so you've got I/O for both hitting the same physical storage devices
[00:40] <TJ-> cuddlyer: are there snapshots associated with it too?
[00:41] <cuddlyer> TJ: I see, this thin LVM hasn't been used, I made it then tried to remove it a few minutes later. I initially had a 500GB LVM and that took about 1 hour to delete, this one is 3.7TB and is taking a lot longer, I waited 2 hours before rebooting and have waited almost 1 hour again so far.
[00:41] <cuddlyer> The mdadm device is 4 x NVMe SSD in raid 10 that are performing well so it's odd any major I/O operation would take this long.
[00:42] <TJ-> cuddlyer: ahhhhh then maybe the underlying MD is syncing? have you checked "cat /proc/mdstat"
[00:43] <TJ-> cuddlyer: did you also recently create the MD ?
[00:43] <cuddlyer> TJ: No syncing showing in that output but as seen in the processes waiting for I/O output I showed, it does show the md2 device (the one related to this LVM) that it is waiting, I also see the md2 in iotop for example.
[00:43] <cuddlyer> I already let the md device fully sync previously
[00:43] <cuddlyer> iotop has this in it: 591 be/4 root        0.00 B/s    0.00 B/s  0.00 % 99.18 % [md2_raid10]
[00:43] <cuddlyer> Only shows when I do the lvremove
[00:43] <TJ-> cuddlyer: OK... that's the usual suspect :)
[00:43] <TJ-> cuddlyer: have you checked the kernel log for I/O errors?
[00:45] <cuddlyer> TJ: Yeah, just this showing every few minutes: https://pastebin.com/raw/PhLnZ2PZ
[00:46] <TJ-> cuddlyer: SSDs? "blkdev_issue_discard+0x7b/0xd0" --- could be that - the device TRIMing
[00:47] <cuddlyer> TJ: Yeah, SSDs
[00:47] <TJ-> I'd focus on that. does the MD know to passthrough the TRIM?
[00:48] <cuddlyer> TJ: I just assumed it did by default, I've never had a problem with mdadm passing through trim before.
[00:49] <cuddlyer> I can see that my trim.timer ran a few mins before I started the lvremove
[00:49] <cuddlyer> I can't find any processes currently running with 'trim' in the name.
[00:49] <TJ-> cuddlyer: you're not alone https://unix.stackexchange.com/questions/631422/blkdiscard-hangs-on-md-raid-10-on-pcie-ssds
[00:50] <cuddlyer> Interesting
[00:51] <cuddlyer> I wonder why the issue only comes to light once I try to delete a lvm, I can make the LVM and make LVMs within the thin pool and use them all okay, it all goes wrong upon lvremove, unless that tries to force trim.
[00:51] <TJ-> cuddlyer: this is more informative https://bugzilla.kernel.org/show_bug.cgi?id=117051
[00:52] <TJ-> cuddlyer: comment #9 may help
[00:54] <cuddlyer> TJ: Thank you. Interestingly, my nomerges is set to 0 on these by default.
[00:54] <cuddlyer> Guess I could try 1
[00:55] <TJ-> cuddlyer: =0 appears to be the expected default
[00:56] <cuddlyer> I also found this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578
[00:57] <TJ-> I think you found the issue then!
[00:58] <TJ-> cuddlyer: can you install a later kernel?
[00:58] <cuddlyer> TJ: Yes, thank you for mentioning discards, at least I've something to research more :)
[00:58] <TJ-> !mainline | cuddlyer
[00:59] <cuddlyer> Thanks
[01:01] <TJ-> cuddlyer: seems from that bug report the 5.8 kernel in 20.04 has the fix - what kernel/release are you using?
[01:01] <cuddlyer> TJ: 20.04.2. Default kernel installed is 5.4.0-72
[01:03] <TJ-> cuddlyer: you can get the 5.8 kernel with "apt install linux-generic-hwe-20.04"
[01:03] <TJ-> or if you're using the lowlatency alternatives, "linux-lowlatency-hwe-20.04"
[01:05] <cuddlyer> I hadn't looked into the lowlatency one before but looks like throughput can suffer so I'll stick with the normal one, thanks for mentioning that.
[01:06] <TJ-> lowlatency is great for desktop or deterministic requirements (avoiding lag) , generic is generally used for -server
[01:06] <cuddlyer> Got it, thanks
[01:06] <TJ-> I've been using lowlatency for about 12 years now and feel the snappier response
[01:09] <cuddlyer> In this case it's a server so maybe better sticking with generic, at least to begin with but good to know about lowlatency in case I come across a use-case for it.
[01:12] <apb1963> I'm kindofglad I didn't make /home a mount point; I don't know if it would of overwritten anything in my home dir.  But now I'm wondering if it's safe to mount my hdd on top of this fresh /home or if it needs fixup to get from 16.04 to 20.04
[01:13] <apb1963> s/home dir./home dir during install/
[01:17] <TJ-> apb1963: if you add /home as an entry in fstab, then restart, it will be fine... HOWEVER ... there may be user settings for the desktop environment that causes unexpected issues with the more recent code. 98% chanve it'll be fine, though
[01:18] <TJ-> cuddlyer: hope hte 5.8 fixes it, got to go.
[01:25] <apb1963> tj- Yes...  the user settings for the desktop env are what I'm worried about.
[01:26] <apb1963> I guess it's whack a mole then.
[01:28] <apb1963> speaking of settings...  The menu of choices for screen blanking is... not to my taste.  I like to blank after 60-120 minutes in general.  No fun when the screen blanks while you're watching a movie :)
[01:29] <apb1963> It should be a text box for numerals... not a pre-set drop down menu.
[01:29] <apb1963> IMHO
[01:30] <apb1963> Did i say movie?  I meant video :)
[02:08] <Intelo> in x2go,  If I want to run "local desktop connection" (the one the server is already running), it goes well with one user. But if I have to users (one is active and other other is in 'switched session'), then I see a black screen while connecting with x2goclient. Any clues?
[02:09] <Intelo> is it a problem with ubuntu?
[02:57] <Intelo> Hi
[02:57] <Intelo>  I cannot 'startx' on virtualbox when doing it by tty alt+ctrl+f2/3/4'. it says https://termbin.com/pqq4b
[03:03] <Intelo> now logs are https://termbin.com/cmeq
[06:09] <OceanGao> Anyone here?
[06:11] <OceanGao> Anyone here?
[06:11] <enyc> maybe
[06:16] <OceanGao> Well, there's something wrong with my ssh on Ubuntu...
[06:17] <OceanGao> I don't know if I can ask this question here, but I uses WSL Ubuntu 20.04
[06:17] <OceanGao> I tried to ask the same thing on #ubuntu-on-windows, but no one answered
[06:19] <OceanGao> Anyway, I can't connect my Ubuntu via ssh, while I'm sure that sshd is running, and I entered correct port, address and username
[06:19] <OceanGao> Anyone here?
[08:16] <omega_doom> Is there away to diagnose wifi hotspot? My wifi disconnects but syslog shows that device is stil connected. https://termbin.com/yarwx
[08:18] <omega_doom> When i connect device again then syslog shows - disconnect/connect like it wasn't disconnected before.
[09:04] <[VMGuy23]> What device? What de? Can you still access the internet while "disconnected"?
[09:14] <omega_doom> @VMGuy23 No, it is disconnected. Actualy if i ping the device when syslog shows disconnection right away.
[09:15] <[VMGuy23]> Strange. I don't really know much about this, but hopefully someone else will come and help you.
[09:16] <Trevizer> Do you have static IP?
[09:17] <omega_doom> @Trevizer Hotspot?
[09:24] <omega_doom> And ping is very long.
[09:25] <[VMGuy23]> Hello, I need glibc 2.33 in a snap package i'm making. What core versiondo I need to get the right version? (core18 does not work, core20 doesnt either)
[09:29] <omega_doom> Ping is very strange https://termbin.com/59w5
[09:41] <omega_doom> I had short power outage. Do you have any guess about such ping? https://termbin.com/59w5
[09:43] <[VMGuy23]> Might be a corruption
[09:43] <mgedmin> the access point rebooted during the outage?
[09:43] <mgedmin> you were offline for ~60 seconds
[09:43] <[VMGuy23]> That is, if it was a PC which required power at all time
[09:44] <[VMGuy23]> Oh wait I thought that the power outage was when it broke whoops
[09:44] <mgedmin> the 18 second ttls are fun, but wifi
[09:44] <mgedmin> maybe check signal/noise ratios with something like wavemon
[09:44] <omega_doom> No, it was just short power outage. The power was and is ok.
[09:46] <omega_doom> What is also strange that bluetooth keeps disconnting when i turn on device wifi.
[09:46] <[VMGuy23]> What is the device?
[09:49] <omega_doom> VMGuy23: Galaxy-A50
[09:50] <omega_doom> Do you think it might be device problem?
[09:51] <omega_doom> I have same problem for two devices. They are both Galaxy-A50
[09:52] <[VMGuy23]> Probably device problem
[09:53] <omega_doom> Do you think both devices have same problem?
[09:55] <[VMGuy23]> Yeah, probably a driver issue
[09:58] <omega_doom> Thanks, i will check it. It is possible. It was a big update sometime ago.
[10:05] <stdedos> My Ubuntu is stuck in a login loop when trying to enter my desktop. When I login, the screen gets black and soon after that the login screen comes back.
[10:06] <stdedos> I have tried following some suggestions online (e.g. checking .Xerrors, etc) but they didn't help
[10:06] <mgedmin> the session is crashing for some reason -- you should be able to see it with journalctl, if you manage to log in
[10:06] <stdedos> I have ssh access; I just cannot login IRL to it
[10:06] <mgedmin> as for logging in, you could try a different session type in gdm, or you could log in into a text console on ctrl+alt+f3
[10:06] <mgedmin> or ssh, yeah
[10:07] <mgedmin> running `journalctl -f` over ssh and then trying to log in might be best
[10:10] <stdedos> I guess that sounds like the worst one? `(EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the`
[10:15] <txtsd> Hello. I have 20.04 LTS on a laptop. It keeps hanging for 3-7 seconds intermittently every 20-30 seconds. I've checked CPU and RAM, and it happens even when usage is super low. I'm so SICK of this I just want the laptop to work.
[10:15] <txtsd> Here's a dmesg log: https://0x0.st/-aYB.log
[10:15] <txtsd> It happens on stock kernel, as well as liquorix.
[10:15] <txtsd> Currently running liquorix
[10:16] <txtsd> Are those ACPI errors in the log relevant?
[10:16] <omega_doom> VMGuy23: I checked. There are no updates for that device. Last one was month ago.
[10:18] <txtsd> Or is AMDGPU the cause of the freezing?
[11:25] <stdedos> Turns out to be NVRM: API mismatch: the client has the version 460.73.01, but this kernel module has the version 460.39.  Please make sure that this kernel module and all NVIDIA driver components have the same version.
[11:25] <stdedos> Interesting
[11:30] <cbreak> stdedos: that can happen after an update, before rebooting
[11:31] <stdedos> Yeah, after digging that out I guessed
[11:31] <stdedos> It's a bit annoying that there is no way to downgrade, or switch to noveuau (or however it's called :-p), to allow for a system to stay alive
[11:32] <stdedos> (surprisingly, it was possible to upgrade the mods manually without any apparent loss)
[12:15] <p0a> Hello, what packages should I install to have a working python developer environment?
[12:17] <ThinkT510> p0a: that depends on your preferences. python3 is already installed by default. if all you need is a text editor then that is all you need to install
[12:17] <p0a> ThinkT510: I'm getting some issues about ~/.local/bin/etc not being in $PATH when I build packages
[12:17] <p0a> (github projects that I build with `make')
[12:19] <ThinkT510> have you added it to your $PATH?
[12:19] <p0a> It's not in my $PATH no
[12:20] <ThinkT510> that is what the error is telling you
[12:27] <mgedmin> I believe the default .profile and/or .bashrc adds ~/.local/bin to PATH if that directory exists at login time
[12:27] <mgedmin> yeah, /etc/skel/.profile
[12:28] <mgedmin> for python dev it's helpful to install python3-dev and maybe build-essential etc. for building extension modules
[12:28] <mgedmin> python3-venv may come in handy too
[12:31] <p0a> mgedmin: yes, thank you :)
[12:35] <BluesKaj> Hi folks
[13:50] <goodTimesImmort> Want to get a new/newish laptop, keeping security and stability in mind so looking at Ubuntu or maybe even Xubuntu right off the bat. Currently doing some research, but was wondering if the room had any favorites or "definitely avoid this" type of advice...
[13:50] <goodTimesImmort> Currently running Xubunutu on an older Asus that's starting to overheat (battery) and a Toshiba satellite that I managed to possibly brick (stuck at "loading innovation" which apparently is common enough with those). Thank you for any input.
[13:50] <lotuspsychje> !hardware | goodTimesImmort
[14:01] <larsmartin_> https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843 some one have idea how to solve?
[14:06] <floogy> Hi, is it possible to dump a non migrated table from mysql80 as mysql57format and reload it into mysql80? Otherwise I'm afraid, that I have to downgrade or parallel install(?) mysql57 on focal, to dump/reload it.
[14:07] <floogy> 2021-05-03T09:39:27.368939Z 2 [ERROR] [MY-011082] [Server] Table upgrade required for `zencart1`.`coupon_gv_customer`. Please dump/reload table to fix it!
[14:07] <floogy> 2021-05-03T09:39:30.066946Z 0 [ERROR] [MY-010022] [Server] Failed to Populate DD tables.
[14:07] <floogy> 2021-05-03T09:39:30.067889Z 0 [ERROR] [MY-010119] [Server] Aborting
[14:08] <leftyfb> !paste | floogy
[14:08] <leftyfb> floogy: have you tried asking in #mysql ?
[14:08] <floogy> No, not yet.
[14:09] <floogy> After upgrading bionic to focal, Mysql-8.0 doesn't start up, with the error messages above in mysql/error.log
[14:10] <floogy> I guess all other tables were migrated successfully, but zencart1
[14:10] <leftyfb> floogy: looks like your issue is with your db, not the mysql install on ubuntu
[14:11] <floogy> yes, it didn't ugraded the data structures of zencart1 db successfully and gives the hint to "dump/reload table to fix it!"
[14:12] <leftyfb> floogy: https://bugs.mysql.com/bug.php?id=93101
[14:12] <floogy> So, I'm wondering, how I can dump itor reload it without starting successfully an mysql instance :(
[14:12] <leftyfb> ""In-place upgrade to MySQL 8.0 is not supported if tables contain old temporal columns in pre-5.6.4 format (TIME, DATETIME, and TIMESTAMP columns without support for fractional seconds precision). If your tables still use the old temporal column format, upgrade them before attempting an in-place upgrade to MySQL 8.0. For more information, see Changes in MySQL 5.7.""
[14:13] <floogy> yes. Okay.  - this time - forgot to dump/upgrade beforehand ...
[14:15] <floogy> So I may have to downgrade mysql, but I'm not sure, if mysql57 will  start with the other upgraded tables in mysql80 format ...
[14:15] <leftyfb> floogy: you should really ask in #mysql for further help. Your issue is very specific to do with mysql and data structures ad conversion and not with ubuntu
[14:16] <floogy> Okay, I can ask there. Maybe I then have to go back here for downgrading purpose.
[14:17] <leftyfb> floogy: I would really look into help with fixing the db and not messing with your install any longer. Not your main install anyway. lxd containers would be great for experimenting with previous versions of ubuntu/mysql
[14:42] <diskin> hi everyone, is there a good guide how to better organize partitions for a desktop Ubuntu installation on an 240Gb NVMe drive?
[14:45] <ravage> what do you want to organize? why would that be specific to a NVMEe? in general LVM or ZFS are good ways to organize a drive
[14:52] <leftyfb> diskin: just install ubuntu and stick with the defaults. Unless you have specific needs for separate partitions, you don't need them
[14:53] <diskin> leftyfb, one thing comes to my mind, is to protect / partition from being filled in. So I thought about creating a separate /home at least. Also isn't it good to have /tmp, /boot to be separated from / ?
[14:54] <leftyfb> diskin: don't fill up your drive. 240G is plenty of space
[14:54] <diskin> ravage, thanks. I don't know if anything is specific to a NVMe... And I haven't used LVM or ZFS yet.
[14:55] <diskin> leftyfb, I saw a case (even subscribed to a bug) when a bad network card was spamming to /var/log and filled up / and the system crashed
[14:57] <leftyfb> diskin: having /home on a separate partition isn't going to help that. Also, journald has settings to rotate and purge logs. The defaults should prevent such an issue
[14:58] <Syntaxerror> Hello everyone :)  I'm trying to upgrade an ubuntu Server installation from LTS 16.04.7 to the next LTS-Version via 'do-release-update -m server' and I'm wondering why it wants to install a whole load of icon-themes?
[14:58] <Syntaxerror> Neither Unity nor Gnome are installed (or any desktop, to my knowledge)
[14:59] <diskin> leftyfb, so you suggest to let Ubuntu do the job? I've been doing it for many friends' machines, but decided to do something "special" for my own :)
[14:59] <leftyfb> Syntaxerror: check your installed packages with: apt list --installed
[14:59] <leftyfb> diskin: correct
[14:59] <diskin> leftyfb, okies. thanks!
[15:00] <Syntaxerror> leftyfb: Anything specific I should look out for? 'apt-get remove *-desktop' didn't find any package to remove
[15:00] <leftyfb> Syntaxerror: look for gnome/desktop/xorg packages
[15:03] <Syntaxerror> leftyfb: Nope, nothing of the sort. I DID notice that it wants to install libsoup-gnome2.4-1 during the upgrade
[15:04] <diskin> one more thing: I loaded the live USB with 20.04.1 and played with the machine for a while, then opened top, xload, system monitor and left it running. I was checking and there were no errors. Next day (more than 24 hours after the boot) I woke up the display and saw old OS (windows) booted up. The live USB was not configured to preserve data, so I could not check logs. Is it possible that the OS rebooted itself after
[15:04] <diskin> some time? I doubt, but there were no power outage during that time, and nobody touched the machine... Thanks.
[15:04] <leftyfb> Syntaxerror: can you name of the icon-theme package names?
[15:04] <Syntaxerror> No packages called *esktop or *org or *nome (except for the one mentioned). Which makes it even weirder that it wants to install icon-themes
[15:05] <leftyfb> diskin: unlikely, unless there was some significant crash. Either way, a live environment is a poor method of gathering benchmarks
[15:07] <Syntaxerror> leftyfb: adwaita-icon-theme hicolor-icon-theme humanity-icon-theme
[15:07] <Syntaxerror> qt5-gtk-platformtheme
[15:09] <chaslinux> Trying to do an automated pxe install of 20.04. Have it netbooting and working non-automated, but seem to be doing something wrong. I do have both nfs and http working and bringing up http://<server ip> brings up the apache default page. But automation doesn't seem to work. Here's my pxelinux.cfg/default file: https://pastebin.ubuntu.com/p/xsy2tPxk5R/
[15:09] <diskin> leftyfb, thanks. the system was known to be faulty in the past, there was a guess that it could be bad PSU, after all, the PSU burned out, and was replaced. So I wanted to check how good are the things with the new PSU. :) Will install the OS and see. Thanks again.
[15:09] <leftyfb> Syntaxerror: look at: apt show humanity-icon-theme
[15:11] <leftyfb> chaslinux: https://discourse.ubuntu.com/t/netbooting-the-live-server-installer/14510
[15:11] <leftyfb> diskin: a live usb isn't going to help you debug that. Get a PSU tester
[15:13] <Syntaxerror> leftyfb: None of the Tasks of Depends of that are installed. I have the following ubuntu-* Packages installed: ubuntu-advantage-tool ubuntu-cloudimage-keyring ubuntu-core-launcher ubuntu-keyring ubuntu-minimal ubuntu-release-upgrader-core ubuntu-server ubuntu-stadnard
[15:13] <Syntaxerror> *standard
[15:14] <leftyfb> Syntaxerror: for i in `apt show humanity-icon-theme|awk -F: '/Task/ {print $2}'|tr -d ,`; do apt list --installed 2>/dev/null|grep $i;done
[15:15] <Syntaxerror> leftyfb: empty (except for the warning about apt's CLI interface)
[15:16] <leftyfb> Syntaxerror: someone has a way to do a reverse dep on a package name.  forget what is was though
[15:23] <lunar>  hello, quick question. Recently installed Ubuntu and I have a secondary ssd in my laptop. The drive seems to only be readable. Previously was a windows disk but I've formatted it and set up a new partition table. Still can't install anything to it. Any thoughts?
[15:24] <shoober420> hi frens
[15:24] <lunar> tried a few resolution posts I found but nothing has worked yet
[15:24] <shoober420> #join /fedora
[15:24] <shoober420> im trying to find out what dependency is missing from a program
[15:24] <shoober420> ldd only gets so far
[15:25] <shoober420> is there another why i can find out what dependency is missing form a program
[15:25] <shoober420> i feel like i need to LF_PRELOAD it
[15:25] <Syntaxerror> leftyfb: Well, can't really find a reason for the themes. Maybe because some fonts-* packages are installed? But one of these seems to depend on ubuntu-server (which, funnily enough, doesn't have ANY packages in its task)
[15:26] <lunar> sorry dropped for some reason
[15:26] <Syntaxerror> shoober420: apt-get check?
[15:26] <shoober420> i installed steam manually, so it cant be seen by the package manager
[15:29] <Syntaxerror> shoober420: Have you run dpkg -I <steam-package filename>?
[15:29] <leftyfb> Syntaxerror: ah, found it:  reverse-depends humanity-icon-theme
[15:31] <Syntaxerror> leftyfb: that's in ubuntu-dev-tools, which will install A LOT of packages. But I'm on a VM and have a snapshot ready, so I'll try that
[15:31] <leftyfb> shoober420: install it from apt. We can't support packages you built from source
[15:34] <Syntaxerror> leftyfb: None of the dependencies of humanity-icon-theme are currently installed. I don't think that's the correct direction anyway. Wouldn't we have to check the dependencies on a 18.04.5 instead of the 16.04.7 that I'm trying to get rid of?
[15:34] <lunar> rebooted
[15:35] <TJ-> Syntaxerror: leftyfb there's an alternative if you don't mind using some brain power too "apt-cache dotty $package  | less "
[15:37] <Syntaxerror> I feel like it might have to do with imagemagick being installed?
[15:40] <TJ-> Syntaxerror: could be, since imagemagick leads to imagemagick-6.q16 which has Depends: libc6 (>= 2.4), libmagickcore-6.q16-6 (>= 8:6.9.10.2), libmagickwand-6.q16-6 (>= 8:6.9.10.2), hicolor-icon-theme
[15:41] <Syntaxerror> TJ-: I just tried removing imagemackick and then ran do-release-upgrade again, but it still wants to install the icon themes.
[15:41] <Syntaxerror> I'll update the VM for now and will afterwards look what the dependencies look like
[15:42] <Syntaxerror> If I can determine a root cause: great! I roll back the snapshot, remove the cculprit and upgrade. Otherwise I'll uninstall the themes later on
[15:44] <TJ-> Syntaxerror: add debug info with this option in the command "-o Debug::pkgDepCache::Marker=true "
[15:45] <TJ-> Syntaxerror: that'll show each time a package is marked for install/hold/removal/etc so you'll need to look further than just the first mention of adwaita-icon-theme to understand the final situation
[15:45] <TJ-> Syntaxerror: ^^^ the -o option is on an apt/apt-get command
[15:46] <Syntaxerror> TJ-: I'll try that should I have problems. Upgrade is already running for now
[15:46] <TJ-> Syntaxerror: see "man 5 apt.conf" and search for Debug:: to see other options
[16:08] <lunar> fstab doesn't seem to let me update the file :/
[16:08] <leftyfb> lunar: use sudo
[16:09] <lunar> sudo vim /etc/fstab correct?
[16:09] <lunar> that's what I'm using
[16:10] <leftyfb> lunar: what version of ubuntu?
[16:11] <lunar> 21.04
[16:22] <leftyfb> lunar: what error message are you getting?
[16:23] <lunar> I don't think they are errors particularly.
[16:23] <lunar> Sorry getting acclimated to linux
[16:23] <leftyfb> lunar: then what is the issue exactly?
[16:23] <lunar> I try to add this to the file
[16:24] <lunar> "/dev/sdb1    /hdd    ext4    defaults    0    0"
[16:24] <lunar> however using sda1
[16:24] <lunar> but it doesn't look like it's adding it to the file if that makes sense
[16:24] <leftyfb> lunar: why do you say that?
[16:24] <ThinkT510> lunar: if you are not accustomed to using vim then you might want to try nano
[16:25] <leftyfb> ThinkT510: that is not the issue
[16:25] <leftyfb> lunar: once you add the line, run: sudo mount -a
[16:27] <lunar> if it tells me the file already exists I just want to edit the existing one correct?
[16:27] <Syntaxerror> lunar: are you using vi?
[16:28] <lunar> vim
[16:28] <Syntaxerror> If so, you have to press the following buttons to save a quit
[16:28] <Syntaxerror> Escape
[16:28] <Syntaxerror> :wq
[16:28] <Syntaxerror> ^^^ *save and quit
[16:29] <Syntaxerror> because it sounds to me like you're not writing the file, but rather only exiting out of vim
[16:30] <lunar> is this spacing in the config a tab or something?
[16:31] <leftyfb> doesn't matter
[16:31] <leftyfb> lunar: "if it tells me the file already exists"  where are you seeing this error? Please take a screenshot or use pastebin
[16:31] <leftyfb> !paste | lunar
[16:32] <lunar> I see it when I use vim /etc/fstab
[16:32] <leftyfb> lunar: screenshot or pastebin please
[16:32] <lunar> ok
[16:37] <lunar> https://paste.pics/1b69fcf9e19ec8142ea4a6602499088b
[16:37] <lunar> There I assume I'm just editing the existing not creating a new one
[16:39] <ThinkT510> lunar: I can't see your screenshot. Also, you don't create a new fstab file (you should be editing the current one).
[16:39] <lunar> hmm odd, I can see it in the link
[16:42] <leftyfb> lunar: it looks like you either have another terminal editing the same file or we need to do a cleanup
[16:43] <leftyfb> lunar: did your machine reboot while you were editing that file?
[16:43] <lunar> I did have to reboot so it's possible
[16:43] <leftyfb> lunar: close out all vim sessions you have
[16:43] <lunar> I don't believe I was editing it but it was likely opened by the system
[16:43] <lunar> ok
[16:43] <leftyfb> (DO NOT just "X" out the terminal window)
[16:44] <lunar> ok I think I'm out of them
[16:44] <leftyfb> lunar: sudo rm /etc/.fstab.swp
[16:44] <leftyfb> lunar: then edit your fstab. You should not see the error message again
[16:45] <lunar> ok that didn't pop up again
[16:46] <leftyfb> lunar: ok, you should be fine now
[16:46] <lunar> I guess I'm thrown off by the editing of the file, it's blinking at the end but I can't create a new line
[16:47] <leftyfb> lunar: ok, exit out of vim and use nano
[16:47] <leftyfb> lunar: or learn how to use vim https://www.openvim.com/
[16:47] <ThinkT510> lunar: vim is a modal editor. first you move the cursor where you want then you press i to enter insert mode then you can type.
[16:48] <lunar> are there direct benefits of one over the other?
[16:48] <leftyfb> lunar: there are. vim is more powerful. Nano is more intuitive
[16:48] <ThinkT510> lunar: nano is a lot simpler. if you become proficient with vim it can save you a lot of time but it has a learning curve.
[16:56] <lunar> insert mode let me update it (correctly I believe) but now I get E45 readonly option is set
[16:56] <lunar> I'll definitely go through that vim tutorial if it's a better tool
[16:57] <lunar> when I try to use the :wq to save an exit
[16:57] <lunar> and*
[16:58] <leftyfb> lunar: sounds like you didn't use sudo
[17:00] <ogra> lunar, to get out of the file without saving (which you want if you can not write it) use :q!
[17:04] <lunar> ok I think it let me save the file. A little odd because the first run I used sudo so I'm not sure?
[17:05] <lunar> when I used sudo mount /hdd it told me there was a parse error but is stated as ignored.
[17:05] <explodes> Apparently my intuition that snap is bad is not far from popular opinion
[17:06] <ogra> explodes, whats bad about snap ?
[17:06] <lunar> I still don't see the drive mounted though
[17:10] <leftyfb> lunar: do you have the directory "/hdd" created? What filesystem is sda1?
[17:11] <lunar> I did create the hdd directory and it was gpt
[17:12] <lunar> under other locations I only see the boot disk though
[17:12] <lunar> gparted sees it but it doesn't seem writeable which is what led me here
[17:13] <leftyfb> lunar: gpt is not a filesystem
[17:13] <lunar> oops sorry
[17:13] <lunar> ext4
[17:14] <leftyfb> lunar: sudo mount /dev/sda1 /hdd  # what does this give you?
[17:14] <lunar> I misread that
[17:15] <lunar> telling me it's mounted on hdd
[17:15] <leftyfb> lunar: mount|grep hdd  # does show it mounted?
[17:16] <lunar> looks like it is so maybe that worked, however I don't see it under files?
[17:16] <leftyfb> under files?
[17:17] <ogra> you need to go to "Computer" i think
[17:17] <lunar> yes the file explorer on the left task bar
[17:17] <leftyfb> lunar: sudo ls -l /hdd
[17:18] <leftyfb> lunar: or, in "file" hit CTRL+L and type: /hdd # at the top
[17:18] <leftyfb> and hit enter
[17:19] <lunar> looks like that went to a directory, but I can't create folders, etc. within it
[17:19] <lunar> permissions tab says I'm not the owner
[17:20] <lunar> owner is root
[17:20] <leftyfb> lunar: ok, then you'll need to change the permissions on the mount(fstab) and/or the actual filesystem according to your needs
[17:20] <lunar> so I need to add permissions for my account
[17:20] <leftyfb> lunar: https://help.ubuntu.com/community/Fstab#File_System_Specific_Examples
[17:24] <NIKKE1> Hello, I cant login to ubuntu server as sudo, neither can my friend. Is there anything we can do except go to the office and hardware reboot
[17:24] <NIKKE1> complains about password
[17:24] <NIKKE1> could login earlier
[17:25] <leftyfb> NIKKE1: you mean you can't run any commands as sudo? Or are you trying to login via ssh as root?
[17:25] <NIKKE1> login via ssh as root
[17:25] <leftyfb> NIKKE1: don't
[17:25] <leftyfb> NIKKE1: why do you need to?
[17:25] <NIKKE1> i need to reinstall docker
[17:25] <leftyfb> NIKKE1: ok, so login as a user and use sudo to install docker
[17:26] <NIKKE1> but cant login as sudo
[17:26] <leftyfb> NIKKE1: can you login with a user?
[17:26] <NIKKE1> yes
[17:26] <leftyfb> NIKKE1: can you run: sudo apt update ?
[17:26] <NIKKE1> it asks for password and when i put pw it says incorrect
[17:26] <NIKKE1> "sorry, try again"
[17:27] <leftyfb> NIKKE1: the password is your users password, no roots
[17:27] <NIKKE1> i know but it doesnt work
[17:27] <NIKKE1> i can login to server
[17:27] <NIKKE1> but not use sudo
[17:28] <NIKKE1> some person was suspecting some daemon isnt working
[17:28] <NIKKE1> "daemon responsible for sudoers is not up and running"
[17:29] <NIKKE1> is this a thing?
[17:31] <leftyfb> NIKKE1: there is no sudoers daemon. If someone messed with the suoders file or some authentication module/configs, then that could be causing your issues
[17:33] <NIKKE1> leftyfb are you sure? I dont think anyone has messed up with them
[17:33] <NIKKE1> can Docker or something disturb it?
[17:33] <leftyfb> NIKKE1: we really have nothing to go on here
[17:33] <leftyfb> NIKKE1: unlikely
[17:33] <NIKKE1> so hardware reboot is only choice?
[17:34] <leftyfb> NIKKE1: if you can't authenticate to sudoers, there's nothing that can be done remotely.
[17:34] <NIKKE1> yea
[17:34] <leftyfb> NIKKE1: I don't think a reboot is going to help
[17:35] <leftyfb> NIKKE1: you need to get on it, either logging in as root locally if you enabled root login or boot with a live cd/usb. I would start with looking at any sudoers files and their syntax
[17:35] <leftyfb> NIKKE1: what version of ubuntu?
[17:35] <NIKKE1> leftyfb 20.04 LTS
[17:36] <NIKKE1> university version cubbli
[17:36] <NIKKE1> Welcome to Cubbli/Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-50-generic x86_64)
[17:37] <leftyfb> NIKKE1: uh, it looks like Cubbli Linux is a custom distro based on Ubuntu
[17:38] <NIKKE1> yea it is, i think its heavily based on ubuntu though, its what our university uses
[17:39] <leftyfb> NIKKE1: I think you need to seek support from your university for this. We can't support 3rd party Ubuntu derivatives
[17:39] <NIKKE1> leftyfb yes I understand, but I suspect whatever would work on ubuntu would also work there, but ok
[17:40] <leftyfb> NIKKE1: we have no way of knowing how the distro was modified
[17:40] <leftyfb> NIKKE1: especially with an authentication issue at a university
[17:41] <TJ-> NIKKE1: could the 'incorrect password' be due to different keyboard/language settings ?
[17:41] <NIKKE1> TJ- nah, neither capslock, the other sudoer couldnt suddenly login to sudo either
[17:42] <TJ-> NIKKE1: see the Cubbli project page. in the TODO "Protect users from using sudo to run pip or conda."
[17:44] <TJ-> NIKKE1: also "...you can run the command i-want-sudo-access... " at bottom of https://wiki.helsinki.fi/display/it4sci/Administrator+%28sudo%29+rights+in+Cubbli+Linux
[17:46] <leftyfb> yeah, looking over that page, I wouldn't touch this distro with a 10ft pole
[17:46] <NIKKE1> TJ yea the  upper one might be relevant, i have to ask the IT department tomorrow, but the bottom one is for laptops
[17:46] <NIKKE1> that the uni lends to students
[18:05] <Syntaxerror> leftyfb: TJ-: You for your help earlier. I've successfully updated to  18.04.5 LTS but forgot to check where the *-icon-theme packages came from
[18:08] <area51pilot> Can anyone give me some insight as to why after a clean install the 2nd nvme drive is not mounted as a 2nd writable disk?  Even if I mount the disk its not writable ( https://pasteboard.co/K0dmZ3F.png)
[18:11] <TJ-> area51pilot: in what way not writable? does your user have permission to write to the location?
[18:11] <sarnold> area51pilot: check the mount flags in use on the filesystem via the /proc/mounts file
[18:12] <area51pilot> nosuid,nodev,nofail,x-gvfs-show
[18:16] <sarnold> area51pilot: looks good; now check the permissions; run namei -l on a path on that filesystem, that'll show user/group/permission on all the directories above it and it's very helpful to spot a directory that might be missing an 'x' or whatever
[18:20] <area51pilot> sarnold: https://pasteboard.co/K0dsi3j.png
[18:21] <sarnold> area51pilot: that's the raw device; it's very rare to write directly to that, though some databases might..
[18:24] <area51pilot> sarnold so this device is not usable for data storage? I guess Im not quite understanding what the system is using the 2nd disk for
[18:25] <sarnold> area51pilot: hmm. I think I may have misunderstood you.
[18:26] <sarnold> area51pilot: is there a filesystem already on this disk? did it come from another machine?
[18:27] <area51pilot> sarnold: :)  it was a new LG Gram 14 that came with 2 500GB nvme m.2 drives in it ... I ran a clean install of 21.04
[18:27] <sarnold> area51pilot: aha! then there's perhaps no filesystem on it and it's not being used for anything
[18:28] <area51pilot> sarnold: ok, i do see its formatted to Ext4 so obviously not Win based format, when I mount it I see a lost+found folder but cant write anything to it.
[18:30] <sarnold> area51pilot: do the namei -l on the mounted path
[18:31] <area51pilot> asrnold: the main disk?
[18:32] <sarnold> area51pilot: no, where you've mounted this second disk
[18:32] <area51pilot> sarnold: this is the first disk: https://pasteboard.co/K0dxhem.png
[18:32] <area51pilot> that was the original paste i posted
[18:33] <sarnold> area51pilot: that's just the raw device
[18:33] <sarnold> area51pilot: you have to mount a filesystem in order to do anything with it
[18:33] <sarnold> area51pilot: what's the output of mount | grep nvme  ?
[18:35] <area51pilot> sarnold: https://pasteboard.co/K0dylHh.png
[18:36] <sarnold> area51pilot: what's the output of namei -l /media/area51pilot/disk2/  ?
[18:36] <pavlos> how do you mount it? example: /dev/nvme1n1p1 /mnt/data auto defaults 0 0
[18:37] <area51pilot> sarnold: https://pasteboard.co/K0dzgyc.png
[18:38] <sarnold> area51pilot: okay, cool, so it's currently owned by root. how do you want to use this disk? do you want your user account to own the whole thing? or do you want different users on your computer to be able to use it?
[18:39] <area51pilot> sarnold: i'm the only user so just myself is fine
[18:39] <area51pilot> sarnold: I'd like to store local backups to it
[18:41] <lunar> I need to do the same to my ssd that's secondary to the nvme
[18:41] <lunar> storing code there, at least that's my intent
[18:42] <sarnold> area51pilot: okay, a simple sudo chown area51pilot:area51pilot /media/area51pilot/disk2  would probably set you up
[18:43] <area51pilot> pavlos: I didnt make any changes after the init install
[18:43] <pavlos> ok, sarnold is helping you
[18:45] <area51pilot> pavlos: yes, thank you ... the problem is solved now. I dont know what i was thinking
[18:45] <apb1963> 20.04; Libreoffice Calc - https://snipboard.io/5816i3.jpg  I am unable to open/use the file.  When I click on it, nothing happens.  Also, you will see in that view when I right click on the Calc icon it does not look normal; the icon is "shriveled" rather than showing a thumbnail of the file.  Clicking on it fails to enlarge the file and basically nothing happens.  Note that this problem suddenly popped up, I didn't have any
[18:45] <apb1963> problems with the same file yesterday.  And, it's not just one file... it's any file I try to open.
[18:45] <area51pilot> sarnold: thank you, that was it
[18:46] <sarnold> area51pilot: woot :)
[18:46] <area51pilot> ;) affirmative!
[18:55] <pavlos> apb1963 open Calc, Tools>Options, click revert, ok, quit calc, try again
[18:57] <last1> how can I get networkmanager to manage netplan so I can configure network using nmtui ?
[18:57] <last1> I installed network-manager but nmcli shows my netifs as unmanaged
[18:58] <Spock_ncc1701> Hi, Ubuntu 20.04 user here, using network-manager-openvpn-gnome. I'm looking for a way to open a web browser upon OpenVPN client connection.
[19:00] <leftyfb> Spock_ncc1701: https://askubuntu.com/a/1217803/1151311
[19:01] <sarnold> last1: the netplan yaml given on https://netplan.io/ shows how to configure netplan to let networkmanager do the whole network
[19:02] <lunar> I tried that same command but still can't save to my second disk
[19:02] <B0g4r7> I hate you systemd.
[19:02] <lunar> shows mounted but still isn't listed under computer
[19:02] <Spock_ncc1701> leftyfb, thanks, does it works with multiple VPN connections?
[19:03] <area51pilot> lunar: do  you see it under +Other Locations
[19:03] <leftyfb> B0g4r7: lets not
[19:03] <lunar> negative
[19:04] <lunar> I see computer which is the boot drive nvme but that's it.
[19:04] <leftyfb> Spock_ncc1701: you run your script to look for interfaces being up or not
[19:04] <leftyfb> Spock_ncc1701: AFAIK, you can't run multiple VPN clients concurrently
[19:04] <Spock_ncc1701> thanks
[19:05] <Spock_ncc1701> I run them one at a time
[19:05] <B0g4r7> It's unmounting my disks again all my itself, thinking it knows best.
[19:06] <leftyfb> B0g4r7: do you have a support question you'd like help with?
[19:06] <area51pilot> lunar: do you see it listed when you run:  mount | grep nvme
[19:06] <B0g4r7> leftyfb, sure, how can I stop systemd from unmounting my disks?
[19:06] <B0g4r7> I mount, systemd immediately unmounts.
[19:07] <lunar> I think I see the boot disk
[19:07] <leftyfb> B0g4r7: what version of ubuntu? Please post logs showing "systemd" unmounting your disks
[19:07] <lunar> the secondary is a 3.5" ssd
[19:07] <B0g4r7> 20.04.  one sec.
[19:09] <lunar> I see it in gparted but when I try to save anything to /dev/sda1/ it acts like it's mia
[19:10] <lunar> it does give me the unmount option too so something is off
[19:10] <B0g4r7> leftyfb, https://pastebin.com/nyfSRufW
[19:11] <last1> so should nmtui replace the /etc/netplan yaml config ?
[19:12] <last1> because it's not doing that and upon restart it goes back to whatever is in that file
[19:12] <leftyfb> B0g4r7: did you run "sudo systemd daemon-reload"  after making changes?
[19:12] <area51pilot> lunar: and you ran  sudo chown username:username /dev/sda1
[19:12] <area51pilot> lunar: using your username
[19:12] <B0g4r7> leftyfb, I did.  That trick worked yesterday, but it's not today.
[19:13] <B0g4r7> well, I did sudo systemctl deamon-reload
[19:13] <leftyfb> B0g4r7: are you doing maintenance on your btrfs?
[19:14] <B0g4r7> Yeah, more or less.  Moving data around, making new partitions, etc.
[19:14] <leftyfb> B0g4r7: https://unix.stackexchange.com/a/563301
[19:15] <lunar> @area51pilot yep
[19:15] <tomreyn> lunar: hi. i haven't followed the full conversation, and may have missed important details. however, "when I try to save anything to /dev/sda1/ it acts like it's mia" makes me think you're misunderstanding a concept there. /dev/sda1 would be a reference to the first partition on the first SATA disk. to access a file system on this partition, you would need to mount it to some location, then access the file system there.
[19:16] <tomreyn> i.e. you would not ever save files to /dev/sda1 but to the mount point you have mounted the file system to.
[19:17] <tomreyn> if that's what's you're doing, just ignore the above. ;-)
[19:17] <B0g4r7> leftyfb, Thanks, I tried the suggested command, but the behavior is unchanged.
[19:18] <lunar> @tomreyn It has the first disk labeled as nvme0n1
[19:18] <lunar> not sure why that's just what the ubuntu install labeled it as
[19:18] <leftyfb> B0g4r7: you'll need to replace backup with your specific mount.
[19:18] <lunar> the ssd secondary disk is showing in gparted as /dev/sda
[19:19] <lunar> while the primary is /dev/nvme0n1p1 and p2
[19:19] <tomreyn> lunar: /dev/nvme0n1 is the first NVME device ("disk"), that's different from /dev/sda (the first sata device ("disk"))
[19:20] <lunar> understood
[19:20] <lunar> it gives me the unmount option so that would mean it's mounted somewhere correct?
[19:21] <tomreyn> yes, probably. you're using the "Disks" graphical disk management software in Ubuntu's default graphical window manger Gnome, right?
[19:22] <B0g4r7> Hmm, OK, makes sense.  I still can't seem to make it work.
[19:22] <lunar> it's gparted, this OS is newer to me so I figured the gui would help initially
[19:22] <lunar> and that seemed to be a commonly recommended one
[19:22] <B0g4r7> It puts these weird \x2d escape characters in the string.
[19:22] <tomreyn> lunar: ^ also: running "mount" in a terminal should hint on where it is mounted.
[19:22] <B0g4r7> I guess it doesn't like hyphens.
[19:23] <B0g4r7> I think it needs a good stabbing right in its bit bucket.
[19:23] <lunar> it says /hdd as I was shown earlier
[19:24] <B0g4r7> I wish it would just mind its business and not fiddle around with my mounts.
[19:24] <lunar> I don't see it listed under other locations nor did chown allow me to even point to it as a storage location in an ide I installed
[19:25] <leftyfb> B0g4r7: it's managing your btrfs volume and taking appropriate measures when it becomes degraded
[19:25] <tomreyn> lunar: hmm, i think at this point, to help further (if needed at all!), i'd need the full output of "mount", which you can produce by running, in a terminal,    mount | nc termbin.com 9999    and pasting the url it returns here. as well as a description of what you're trying to achieve.
[19:25] <leftyfb> B0g4r7: did you try sudo systemctl mask usb14-003-plot.mount ?
[19:26] <B0g4r7> I tried that, using the escaped version that gets printed in the log...
[19:26] <B0g4r7> I don't think the fs is degraded.
[19:26] <tomreyn> lunar: running chown against /dev/sda1 was, i'm afraid, probably not the right thing to do (even though i can't yet claim to understand what you're trying to achieve - you usually don't do this).
[19:26] <leftyfb> B0g4r7: did you try as I just typed it?
[19:26] <B0g4r7> In fact it's brand new.
[19:27] <lunar> @tomreyn https://pastebin.com/9Dn4z946
[19:27] <lunar> I'm just trying to point a code repository for an ide at it, within a dedicated folder.
[19:27] <tomreyn> what is "it"?
[19:28] <lunar> that second drive
[19:28] <tomreyn>  /dev/sda, right?
[19:28] <lunar> I don't want to store it on the OS drive in case I need to reinstall, etc.
[19:28] <lunar> yes
[19:28] <B0g4r7> I tried it now.
[19:29] <B0g4r7> The behavior is the same.  I mount, systemd complains about "unit is bound to inactive unit blah blah", and unmounts it.
[19:29] <tomreyn> lunar: okay, so the ext4 file system that's stored on the file system on the /dev/sda1 partition is currently mounted on /hdd (a non-standard but usable mount point)
[19:30] <tomreyn> lunar: now what's missing to make you a happy lunar?
[19:30] <lunar> so I have to use /hdd as the path for the install?
[19:30] <lunar> well it doesn't seem to allow me to save anything there
[19:31] <tomreyn> lunar: correction of the above: okay, so the ext4 file system that's stored on the /dev/sda1 partition is currently mounted on /hdd (a non-standard but usable mount point)
[19:31] <tomreyn> lunar: what are you meaning to install to /hdd ?
[19:32] <tomreyn> said code repository for some ide?
[19:32] <lunar> yes, I would point it at /hdd correct?
[19:32] <tomreyn> you can do so, yes
[19:32] <lunar> ok
[19:32] <lunar> I think it can see that
[19:33] <lunar> I was looking as /dev/sda1 as a unc path if that makes sense
[19:33] <tomreyn> an easier approach to do all this is to not manually mout something to a specific mount poiont, and have udisks handle it for you
[19:33] <lunar> so I have to target the mount point
[19:33] <tomreyn> *mouNt
[19:34] <tomreyn> udisks can mount file systems for you through the file browser GUI
[19:34] <lunar> you said /hdd was non standard. That is what I found in the ubuntu forum. So I should use udisks instead?
[19:36] <tomreyn> lunar: lyou generally have two options how you want to go about mounting file systems. one is to configure them in /etc/fstab, and set a fixed location where the file system will be mounted to on each boot. that's probably the approach you took so far. the other approach is one where you just prepare the file system and then use the graphical file browser to mount this file system, on demand, to an automatically generaled location in
[19:36] <tomreyn> /media/$USERNAME/
[19:37] <tomreyn> lunar: the latter isn't useful if you want it to be mounted automatically, on boot
[19:38] <tomreyn> lunar: we can revisit this topic later, though. thisis not about the "i cannot write to /hdd" topic, that's a different one. would you like to look into this one first?
[19:39] <lunar> sure
[19:39] <tomreyn> lunar: the common location you do fstab-mounts at would be /mnt/SOMETHING
[19:40] <tomreyn> ...or into some other existing directory (but normally not at /something, though this also works)
[19:40] <freebench> hi, can anyone send proper manual of how to reset a forgotten root pwd ?
[19:40] <lunar> So in computer I see HDD but when I go into it I cannot write to the directory.
[19:40] <B0g4r7> Well it looks like the solution for me is to comment out all of /etc/fstab, do systemctl deamon-reload, fix /etc/fstab, and then do my business.
[19:40] <lunar> only has root permissions though
[19:40] <lunar> so I should chown /hdd?
[19:42] <tomreyn> lunar: right, this is because of file system permissions. you need to enable your user to write there. the easiest way to do so is to run, while the file system is mounted at /hdd, sudo chown -R $USER:$USER /hdd
[19:42] <tomreyn> (I'm assuming here that your primary group has the same name as your user has, an ubuntu default)
[19:43] <lunar> yeah I haven't changed any security groups if that is what you are asking.
[19:43] <tomreyn> right, i'm assuming that the output of    id -un    is identical to that of     id -gn
[19:45] <MontyCarleau> Hey all, I'm trying to make a server on port 8888 publicly accessible, but, so far, failing. I created an iptables rule that shows requests for 8888 and while curl -0's to 8888 are successfully logged, requests to myserver.com:8888 do not appear. The firewall is currently inactive. Anywhere else I should be looking?
[19:46] <tomreyn> lunar: so if that's the case you can gop ahead and run the chown command.
[19:46] <lunar> they are
[19:46] <lunar> ok I'll do that now
[19:47] <lunar> I think that worked
[19:47] <sarnold> MontyCarleau: double-check with sudo ss -tlnp that your service is bound to a publically-visible address
[19:47] <lunar> I guess I see where I was confused, the mount point is the path where I was using the device (I think)
[19:47] <lunar> learning :/
[19:48] <tomreyn> lunar: right. you don't usually change ownership on /dev/something
[19:48] <tomreyn> lunar: is this something we should undo / fix?
[19:49] <lunar> how do I check if it's set wrong on the device?
[19:50] <MontyCarleau> @sarnold ss shows that the PID of my server process is listening on 0.0.0.0:8888 with Peer Address of 0.0.0.0:*
[19:50] <tomreyn> lunar: ls -l /dev/sda*
[19:50] <sarnold> MontyCarleau: alright, promising start
[19:50] <lunar> @tomreyn it's showing my group and user for sda1
[19:51] <tomreyn> lunar: third and fourth column should say "root" and "disk"
[19:51] <lunar> so it is incorrect now it looks like
[19:51] <tomreyn> lunar: can you show the full output, just to be sure it's actually still the disk device?
[19:52] <lunar> brw-rw---- 1 root  disk  8, 0 May  3 11:36 /dev/sda
[19:52] <lunar> brw-rw---- 1 lunar lunar 8, 1 May  3 11:36 /dev/sda1
[19:52] <B0g4r7> leftyfb, thanks for your help and patience.
[19:52] <tomreyn> lunar: alright, let's fix this:  sudo chown root:disk /dev/sda1
[19:53] <tomreyn> !netsplit
[19:53] <lunar> ok then lol
[19:54] <lunar> @tomreyn that fixed it thank you
[19:54] <tomreyn> lunar: great. did you edit /etc/fstab to have /dev/sda1 mounted to /hdd on boot, yet?
[19:55] <tomreyn> or would you prefer handling it the 'GUI way' (but having to mount manually then, after logging in)
 lunar: great. did you edit /etc/fstab to have /dev/sda1 mounted to /hdd on boot, yet? or would you prefer handling it the 'GUI way' (but having to mount manually then, after logging in)
[19:56] <lunar> I did edit the fstab earlier so I think it mounts on boot
[19:57] <tomreyn> lunar: alright. if *you* want, we could double check the line you added there?
[19:57] <tomreyn> ... or just reboot and see whether it'll be there
[19:58] <apb1963> or mount -a instead of rebooting should be a reasonable facsimile of the boot process for mounting
[19:58] <nuala2> first time installed something (knowingly) via snap: sameboy. but it won't recognise my gamepad. is that maybe something snap related? do i have to give permission for it or anything (snap noob here)
[19:58] <tomreyn> after unmoounting it, yes
[19:59] <lunar> "/dev/sda1    /hdd    ext4    defaults    0    0"
[19:59] <lunar> That's the line entered
[19:59] <lunar> so typically you use media not hdd?
[19:59] <tomreyn> lunar: this should work.
[20:00] <apb1963> 20.04; Libreoffice Calc - https://snipboard.io/5816i3.jpg  I am unable to open/use the file.  When I click on it, nothing happens.  Also, you will see in that view when I right click on the Calc icon it does not look normal; the icon is "shriveled" rather than showing a thumbnail of the file.  Clicking on it fails to enlarge the file and basically nothing happens.  Note that this problem suddenly popped up, I didn't have any
[20:00] <apb1963> problems with the same file yesterday.  And, it's not just one file... it's any file I try to open.
[20:00] <tomreyn> lunar: /media is what is automatically used by "udisks". /mnt is where you normally do static (fstab) mounts
[20:01] <lunar> ok cool, this is all new to me. I'm a system admin and I want to explore more than windows which is 99.9% of what we run.
[20:01] <leftyfb> B0g4r7: did you solve the issue?
[20:01] <tomreyn> lunar: beware, you might get to like it at some point. ;-) after some initial frustration, possibly.
[20:02] <lunar> Could I rename the mount or would it just be better to make a new one and assign it to sda1?
[20:03] <nuala> (pls disregard my premature question: retroarch via snap works fine. so i suspect issue in the software :> )
[20:03] <lunar> I hope I do end up liking it honestly
[20:04] <tomreyn> lunar: to move the mount point into the 'proper' place? you would unomunt it, move (or delete and re-create) the mount point (a directory), update fstab, mount it
[20:04] <lunar> I guess I don't know what a best practice would be, or any consequences of a rename.
[20:04] <lunar> Where is the proper place? I don't want to learn bad habits lol
[20:05] <tomreyn> !fhs | lunar: some background on the file system hierachy
[20:05] <tomreyn> !man | lunar
[20:05] <lunar> ok
[20:06] <tomreyn> (apt) package: man-db
[20:06] <B0g4r7> leftyfb, yes, see above.  I had to comment out all the fstab lines, systemctl deamon-reload, then fix fstab.
[20:07] <tomreyn> lunar: for your fstab controlled /dev/sda1 mount, the proper place is /mnt/whateveryouwantotocallit
[20:08] <tomreyn> lunar: this is more a matter of keeping conventions. using /hdd is not strictly wrong, it's also not entirely uncommon, but it's not "how it's meant to be done".
[20:08] <tomreyn> it wouldn't break things, though
[20:08] <lunar> understood
[20:09] <lunar> I feel like in learning the file system/OS it would make sense to use common practices
[20:09] <lunar> at least initially until my confort levels go up
[20:09] <lunar> comfort*
[20:09] <tomreyn> ^ good approach :)
[20:15] <tomreyn> !terminal | lunar: another good document to get you started
[20:16] <lunar> thank you @tomreyn I'm going to bookmark that
[20:18] <tomreyn> you're welcome
[20:22] <lunar> @tomreyn so you would mount mnt on the device and create subdirectories or mount the full path?
[20:23] <lunar> when I tried as /mnt/data I received a pattern not found error
[20:23] <tomreyn> lunar: with the fstab approach, i would   mkdir /mnt/something-i-like-it-to-be-known-by    and update fstab to use that
[20:23] <lunar> ok
[20:24] <tomreyn> lunar: that's AFTER unomounting it
[20:24] <tomreyn> you only mount each (non network) file system to one location normally
[21:27] <texla> Is 21.04 the latest ltd copy of ubuntu ??
[21:28] <Bashing-om> !releases | texla
[21:28] <jeremy31> texla: 20.04 is the latest lts
[21:32] <texla> jeremy 31 Thanks for the info
[21:36] <ExcessiveAggro> Afternoon.  I have a DHCP wireless connection and I'd like to always use a set of static DNS servers regardless of the wireless network i connect to.  How does one accomplish that?  I tried a few things but it doesnt seem to respect it
[21:54] <ExcessiveAggro> i was able to get this solved by using this command - "sudo nano /etc/resolvconf/resolv.conf.d/tail"
[22:31] <bumblefuzz> is there a way to do a system integrity check and compare important system file hashes against trusted hashes for those system files?
[22:42] <jaffachief> I have a raspberry pi 4 running groovy. No hirsute update is available, and it doesn't seem to be supported for hirsute on the downloads page. I can't find any discussion of this anywhere - will there ever be support for hirsute on rpi4 or should I look at reinstalling with focal?
[23:21] <rfm> jaffachief, I don't know what's happening with the upgrade, but there are rpi images in https://cdimage.ubuntu.com/releases/21.04/release/ so it's supported for new installs at least.
[23:22] <sarnold> jaffachief,rfm, probably https://lists.ubuntu.com/archives/ubuntu-devel/2021-April/041448.html
[23:28] <rfm> sarnold, jaffachief curiously when I ran do_release_upgrade, no -d, on my groovy system (not rpi) on Saturday it kicked right off (and worked) so upgrades have been turned on for at least some archs.
[23:31] <sarnold> rfm: oh curious
[23:42] <rfm> Hm. certainly no hirsute in changelogs.ubuntu.com/meta-release now; easier to believe my memory is faulty and I used -d rather than it was there transiently
[23:52] <TJ-> rfm: I think I saw talk in -devel of it being pulled due to issues