[00:35] <emma> hello everyone
[00:52] <etrigan63[m]> So has there been any updates as when Plasma 5.13.x will get backported to 18.04? I know that they are waiting on the latest version of QT for a bunch of stuff but I can't seem to get a rough idea of timeframe out of anyone.
[03:50] <suffokated> hello :)   i'm running into a problem with an external hard drive, on 18.04 - i used the KDE Partition Manager to make the entire drive encrypted with LUKS/ext4 but whenever I mount it via Device Notifier, then open with File Manager (Dolphin), I can't copy anything to it.  I can't even make directories.  I'm assuming it's being mounted as read only but I double checked in the partition manager just to make sure it wasn't read-only permissions, it's
[03:50] <suffokated> not.  How do I enable write privledges?  I don't encounter the same problem with my thumbdrives but I haven't tried LUKS on those yet
[04:09] <etrigan63[m]> suffokated: Is this to be mounted at boot time or just when you attach the drive? I have RAID-5 array via USB 3.0 that I mount at boot time. It's not encrypted so it is much simpler.  To mount at boot time read this: https://blog.tinned-software.net/automount-a-luks-encrypted-volume-on-system-start/
[04:10] <etrigan63[m]> To mount on demand read this: https://askubuntu.com/questions/63594/mount-encrypted-volumes-from-command-line
[04:10] <suffokated> the drive will house some sensitive data, not one i intend on keeping plugged in unless using it.
[04:11] <suffokated> thanks!  will do so now :)
[04:11] <etrigan63[m]> Glad I could help.
[04:21] <suffokated> etrigan63: well mounting was no problem, but I still cannot copy or create anything on the drive :/
[04:21] <suffokated> mkdir: cannot create directory ‘test’: Permission denied
[04:22] <etrigan63[m]> Did you unlock the drive with its password?
[04:22] <suffokated> yes, and as sudo it lets me create directories.  is it not possible to work with the drive as my local user account?
[04:23] <suffokated> guessing i will need to manually add it to fstab for that
[04:24] <etrigan63[m]> It could be that root is the owner. You'd have to check permissions now that you have unlocked it. The udiskctl command needs to be executed without sudo.
[04:24] <suffokated> yes i executed the commands as an underpriviledged user
[04:24] <suffokated> i only tried sudo to make a directory to see if that had any difference, and it did
[04:25] <suffokated> so root must own the device lol
[04:25] <etrigan63[m]> It's non-privileged, but I get what you mean.
[04:25] <suffokated> gotcha, still sorta new to this :)
[04:26] <suffokated> can i just chown -R /dev/sdb1 ? lol
[04:27] <suffokated> well i think it's chown -R user.user /dev/sdb1
[04:27] <etrigan63[m]> Checking the exact syntax. Normally this is handled via fstab file.
[04:29] <etrigan63[m]> when you mount the drive, what is the mount point?
[04:29] <suffokated> into /media/user/driveUUID
[04:31] <etrigan63[m]> sudo chmod 777 /media/user/driveUUID
[04:32] <etrigan63[m]> or
[04:32] <etrigan63[m]> sudo chown -R johndoe:johndoe /media/user/driveUUID
[04:33] <etrigan63[m]> I feel the second one is safer than the first.
[04:34] <suffokated> yes :)  i did the second, then used 0700 for chmod :)
[04:34] <etrigan63[m]> A safer bet is to create your own mount point instead of letting the system decide for you.
[04:34] <etrigan63[m]> sudo mkdir /mnt/MyMount
[04:35] <etrigan63[m]> sudo chown mylogin:mylogin /mnt/MyMount
[04:37] <suffokated> nods
[04:37] <suffokated> if i add it to fstab, and it's not plugged in, will that have any negative effects on booting?
[04:38] <suffokated> such as not letting the system boot because fstab can't find the device?
[04:41]  * etrigan63[m] sent a long message:  < https://matrix.org/_matrix/media/v1/download/matrix.org/lbOQYrCvVExOcvXijVDBfPzJ >
[04:43] <suffokated> okay, thanks again, i'll do that :)  much appreciated!
[04:43] <etrigan63[m]> Once you have the mount point created, you could use a bash script to handle the opening/mounting and one for unmounting and closing.
[04:44] <suffokated> i haven't tried any bash scripting yet, still feel like i'll always forever be learning basics haha
[04:44] <etrigan63[m]> Don't forget to chown the mount point to yourself.
[04:45] <etrigan63[m]> I've been using linux for years and I learn soemthing new every day.
[04:46] <suffokated> i did use it full time for about a year
[04:46] <suffokated> but that was over a decade ago :)
[04:47] <suffokated> struggling to remember things now
[04:47] <suffokated> 1803 tipped me over the edge though, our entire household moved to Kubuntu
[04:49] <qbsd> any advice on what to do about updates today that killed my nvidia driver dead and replaced it with nouveau? is this a known issue?
[04:49] <etrigan63[m]> The Only Thing That Is Constant Is Change - Heraclitus
[04:50] <etrigan63[m]> qbsd: Run lsmod | grep nvidia to see if it is actually running nouveau.
[04:51] <qbsd> already looked at Xorg.log
[04:52] <qbsd> and lsmod shows nouveau as well
[04:53] <etrigan63[m]> What does the Driver Manager report?
[04:56] <qbsd> it says nvidia 390, and it lies
[04:57] <qbsd> this is an old gts-450, and in the past nvidia tends to shuffle out support in the newest driver releases for older legacy cards
[04:57] <etrigan63[m]> Mine says I am running nouveau and it's not installed on my system.
[04:57] <etrigan63[m]> I have a GTX 1080
[04:58] <etrigan63[m]> Only because I can't get OpenCL to work with AMD cards yet.
[04:58] <qbsd> if it is a known problem and people are looking at it maybe I'll leave it as is for a test case to gather info; or clonezilla back to known good
[04:59] <suffokated> i had a similar problem, Kubuntu said I was using nvidia-drivers but Xorg's log said I was using nouveau.  Secure boot in bios was the culprit in my case
[04:59] <etrigan63[m]> Hmmm, I will have to check that.
[04:59] <qbsd> this is a z77 ivy bridge. I do not have secure boot
[05:00] <etrigan63[m]> I have an X399 Threadripper. It does have secure boot.
[05:00] <etrigan63[m]> brb
[05:02] <qbsd> driver manager is b0rked. tried to select downgrade to 340 and now I have 2 copies of 'using nouveau'
[05:02] <qbsd> oh well, gonna roll back until devs figure it out. will try updating again in a week or two
[05:03] <qbsd> thanks
[09:39] <BluesKaj> Hi folks
[13:36] <Quantos> Hello, I'm having an issue installing the Oracle VBox Guest Additions on KUbuntu 18.04.1 LTS
[13:37] <diogenes_> which is?
[13:38] <Quantos> Well, it won't install at all
[13:39] <Quantos> I must be missing a step somewhere
[13:39] <Quantos> But I can't seem to find it
[13:39] <diogenes_> and what is host os?
[13:40] <Quantos> Oh, host OS is Win 10
[13:40] <Quantos> I know, it sucks
[13:40] <Quantos> I lost a bet and now I'm learning Windows
[13:41] <diogenes_>  /j #windows
[13:42] <Quantos> I'm assuming that you're trying to be funny
[13:45] <hateball> #virtualbox would probably be more accurate
[22:12] <Quantos> I'm having problems installing the VBox Guest Additions to my KUbuntu 18.04.1 LTS guest running on Win 10 host