[00:54] <Guest61592> I'm using kubuntu. I like it.
[01:04] <jrss> hello guys.
[01:05] <jrss> I just used kde partitions to clear an internal hard drive, but it's read only. why? How do I change that?
[01:05] <jrss> I tried sudo mount -o remount,rw '/media/...'
[01:05] <jrss> but it doesn't seem to work.
[01:13] <Antisoche> jrss: From the commandline, umount the directory, then manually mount it explicitly (mount /dev/foo /media/bar). Are there any messages? Does "dmesg | tail" say anything interesting?
[01:14] <Guest61592> jrss: make sure BIOS is set to not secure boot
[01:15] <jrss> how do I unmount?
[01:15] <jrss> what's the command I mean.
[01:16] <jrss> mount -o unmount?
[01:16] <Antisoche> sudo umount /path/to/thing
[01:17] <jrss> umount insteadn of unmount? that confused me.. ok but got it hmmm
[01:17] <jrss> my hdd seems to be in /media/user though
[01:17] <jrss> I never went to /dev....
[01:18] <Antisoche> Is it still mounted or were you able to unmount it?
[01:18] <Antisoche> If it's still mounted, do: 'mount | grep /media/user'
[01:18] <jrss> it's unmounted because I can't go to /media/user now
[01:18] <jrss> was able to before
[01:20] <Antisoche> okay, do this: 'sudo udiskctl status'
[01:20] <Antisoche> Sorry: udisksctl status
[01:20] <jrss> ok
[01:20] <jrss> I think I see it there
[01:21] <Antisoche> What is the 'device' ?
[01:21] <jrss> I can't tell which partition though
[01:21] <jrss> there are two that are WDC, which is what my hard drive though
[01:21] <Antisoche> so: sudo fdisk -l /dev/thing
[01:21] <jrss> oh wait I can use KDE partition to tell me
[01:22] <jrss>  dev/thing? what do you mean by that
[01:23] <jrss> what is "thing"?
[01:23] <jrss> I see two EDC until udiskctl, two serials. this doesn't make any sense
[01:23] <Antisoche> Use the KDE tool. You should see /dev/sdXN where 'X' is a letter and 'N' is a number. /dev/sde6 for example
[01:24] <Guest61592> try `df' to see your drives
[01:24] <jrss> ah ha. ok
[01:25] <jrss> ok now I saw some details, running fdisk -l on /dev/sdc (in my case
[01:25] <jrss> ..now what then?
[01:25] <Antisoche> So you should be able to "sudo mount /dev/sdXN /mnt" now.
[01:25] <Antisoche> Something will probably print to the screen.
[01:26] <jrss> sudo mount /dev/sdc makes sense
[01:26] <jrss> but mnt? you mean the path?
[01:26] <jrss> so I called it space. it would be $mount /dev/sdc/space
[01:26] <jrss> ya?
[01:26] <Antisoche> You need to say where to put the mount. The folder '/mnt' is just hanging out there waiting for you to mount something there.
[01:26] <jrss> sudo.. I will sudo it
[01:27] <Antisoche> ie: "sudo mount /dev/sdc1 /mnt"
[01:27] <jrss> oh shit. you had space there
[01:27] <jrss> sorry it's hard to see ok
[01:27] <jrss> so I just did it lets see
[01:28] <jrss> I still can't create a folder in it in dolphin >.>
[01:28] <jrss> it's grayed o ut
[01:28] <Antisoche> That's a different issue...
[01:28] <Antisoche> Can you: "sudo touch /mnt/xxx"
[01:28] <jrss> hmm. looks like it.
[01:29] <Antisoche> Okay, so, backing up: what filesystem type is it?
[01:29] <jrss> yep! that worked
[01:29] <jrss> etx4
[01:29] <jrss> ext4 sory
[01:30] <Antisoche> So ... when you mount it, it's going to be owned by root. If you want to be able to write to it as your user, you need to 'chown <user> /mnt'
[01:30] <Antisoche> Or, probably: "chown 1000 /mnt"
[01:30] <Antisoche> But using yout username is safer
[01:30] <jrss> ok did it
[01:30] <jrss> needed sudo but yeah
[01:31] <Antisoche> (Type 'id' to see your user id).
[01:31] <Antisoche> Yes, as root is the owner, only root cahn change ownership. You should be all set now though
[01:31] <jrss> hmmmm ok so now can I see it in dolphin?
[01:31] <jrss> what I originally wanted is for Steam to use it for my games -.-
[01:31] <Antisoche> You tell me :)
[01:32] <jrss> oh shit it works!
[01:32] <jrss> and it's still called space in dolphon
[01:32] <jrss> I don't understand what mnt is..
[01:32] <jrss> because the mounting point is /media no?
[01:32] <jrss> thi still confuses me
[01:32] <Antisoche> You come from Windows?
[01:32] <jrss> Eh.. I've been in linux for a while
[01:32] <jrss> but windows and mac yeah
[01:32] <jrss> <.<
[01:33] <jrss> never wrapped my head around all of this
[01:33] <jrss> I called it space, that's the label. but, I was sure /media/user/name is the mounting point. guess.. not?
[01:34] <jrss> oh shit wait. wait wait wait.
[01:34] <jrss> media  is for external stuff.
[01:34] <Antisoche> So, if *nix, a directory is just a place where you can mount a new filesystem. '/mnt' has been around forever. udisks2 is the hip new thing for USB devices and it uses /media/<user> (or /var/run/<user>). We you typed 'mount' you put it on /mnt, but you can put it whereever you like. /home/<user>/.steam may make sense for your use case; I don't know how Steam works.
[01:34] <jrss> hmmmmmmmm
[01:35] <jrss> ok so yeah, nedia/user/something is my external and such..
[01:36] <Antisoche> Generally, yes. You can manage that with 'udisksctl' from the commandline.
[01:36] <jrss> can I change mnt later without much hasle?
[01:37] <jrss> I liked space more <.<
[01:37] <Antisoche> Try this: "sudo umount /mnt" (you probably need to close Dolphin for this). Then: "udisksctl mount -b /dev/sdc1" (no sudo). Not 100% sure what happens there, but it's safe.
[01:38] <jrss> well I'm installing now so I'll wait
[01:38] <Antisoche> If you want it fixed in some place (like /home/steam) you need to put it in /etc/fstab.
[01:38] <jrss> oh. how do I do that
[01:39] <jrss> I need to read up on all of this it sounds complicated
[01:40] <Antisoche> Just edit the file /etc/fstab ... it's pretty straightforward. There is a manpage that explains it but it'll be like: "/dev/sdc1 /home/<mntpoint> ext4 defaults 0 0"
[01:41] <Antisoche> If you're happy with where udisks2 puts it, though, you don't need to change anything. That's just to put it somewhere special to you.
[01:41] <jrss> well dolphin calls it "space" because that's the label I  gave it
[01:41] <jrss> and I guess as long as I can navigate to it
[01:41] <Antisoche> I'm sure you can change the label
[01:42] <jrss> label is ok that's what I like
[01:42] <jrss> just not sure where's the path to get to it from command line now lol
[01:42] <jrss> "/dev/sdc1 doesn't seem to be there
[01:44] <Antisoche> Well, I don't know what you're looking at, actually. There are three things: (a) the device representing the physical device (/dev/foo); (b) The place in the filesystem where it is mounted (/mnt or /media/user/foo or /opt/foo or /home/foo/steam); and (c) the filesystem itself can have an internal label so the computer can find it if the device is plugged into a different port and shows up on /dev/sdf one day.
[01:45] <Antisoche> You never told me what partition it was, you just said it was somewhere on /dev/sdc. Use the correct partition number.
[01:45] <jrss> ah ha. ok
[01:45] <jrss> so the path... if I want to do cd/...
[01:45] <jrss> I need to use the mounting point? that's (b) in your explination?
[01:45] <Antisoche> ...is (b), yes
[01:45] <jrss> it is a ext4
[01:45] <jrss> filesystem
[01:45] <jrss> and the label is "spacE"
[01:46] <jrss> which is (c) in what you said
[01:46] <Antisoche> Maybe. Usually the label is a UUID, which is a big ugly number, but you may be able to give it a name like "spacE"; I've never looked
[01:47] <jrss> I'm still having hard time understanding what is (a). b I understand, that's where you actually mount the drive, and therefore where you navigate, got it. label is just a name the OS calls it, ok.
[01:47] <jrss> but what is a? what is it for lol
[01:47] <jrss> hope you don't mind I like to learn >.>
[01:47] <Antisoche> Well (a) is what the OS calls it. (c) is what it calls itself.
[01:48] <jrss> ok so I understand a now.. I think,,, but now I'm lost on C lol
[01:48] <jrss> The OS needs to refer to it somehow, ok yes get it. sdc1
[01:48] <jrss> which is what we have, and it's probably a linux standard I saw before..
[01:49] <jrss> si there are sda, sdb, sdc... sdc1 for partition etc. that I saw before it makes sense (if I'm right?)_
[01:49] <coderphive> dude I am 100% done using POS nvidia drivers
[01:51] <Guest61592> coderphive: did you do the latest 990?
[01:51] <Guest61592> or 890 or whatever
[01:51] <Guest61592> weird error messages?
[01:51] <Guest61592> did you use the .sh from the nvidia site or the ones from the ubuntu up-stream?
[01:51] <coderphive> I have dual monitors and every time I try to boot with it it locks KDE
[01:51] <coderphive> upstream
[01:51] <Antisoche> Explaining /dev is a big topic. In short, in the bad old days there was an interface called IDE. Most Mobos had two IDE ports, and each IDE port could hold 2 drives. /dev/hda was IDE bus 1, drive 1; /dev/hdb was bus 1, port 2; /dev/hdc was bus 2, port 1, and /dev/hdd was /dev/hdd. This doesn't work when USB devices show up for instance, so they get "the next" letter based on when they are detected. They use the SCSI disk subsystem, so /
[01:51] <Antisoche> dev/sdX (SCSI disk). IDE went away and was replaced with SATA, which also uses the SCSI subsystem, so now "Hard Drives" are all "Scsi Discs" of some type. There's a lot of history and udev manages all of that now, but in short what the OS calls it is a little less important, and udisks2 was create to manage that complexity for the user. At the OS it's udev.
[01:53] <Guest61592> coderphive: there should be config files with xorg when KUbuntu starts to load services concerning the KDE desktop services that can tell the computer to correctly load both monitors up correctly when your computer boots. Someone should write a book about it for you: "How to get KDE to correctly load 2x monitors on-boot For Dummies"
[01:54] <coderphive> I've generated those
[01:54] <coderphive> We're not going to play the user error game here
[01:54] <coderphive> they're POS drivers, end of story
[01:54] <Guest61592> oh so now we've got more advanced problems
[01:55] <Guest61592> wait Until Kubuntu 18.04.2?
[01:55] <Guest61592> 90% j/king
[01:55] <Antisoche> jrss: Yeah, you get it. The other new thing is UUID and GUIDs, which are just giant numbers that are supposed to be globally unique. When you make a new fielsystem, it gets this number as a "label" so you can uniquely identify it no matter what /dev/sdX it shows up on. You can change the label so that you can make 1000 clones of the drive and then just change the label to be able to uniquely identify them. It's not too complex. Just a
[01:55] <Antisoche> name/number embedded in the filesystem. You can think of it as a hidden file, except you can't actually see it without using special filesystem tools.
[01:55] <coderphive> Nope
[01:55] <coderphive> nvidia is getting purged right now
[01:55] <Guest61592> NooOooOooOO...*dies*
[01:55] <coderphive> I hope their engineers watch this channel too
[01:56] <coderphive> If I wrote code this half ass I'd never have a job
[01:56] <Guest61592> *echos a dark voice* nvidia dies tonight
[01:56] <coderphive> that'd be dope
[01:56] <coderphive> They're a pretty useless company anyway
[01:57] <Guest61592> you think their drivers would be so stable that they'd release stable drivers that don't need to be updated for *every* card they have all the time
[01:57] <viewer|64481> Hey peeps
[01:57] <Guest61592> sup
[01:57] <Antisoche> Guest61592: sounds like you're asking for a card that doesn't do anything new
[01:58] <Guest61592> Antisoche: well maybe not new, but newish, sure. like dual-monitors.
[01:58] <Guest61592> graphics drivers are one of the most notorious parts of a system, even Windows screws it up half the time
[01:58] <viewer|64481> I'm stuck in low resolution hell with nvidia 18.04 :(
[01:59] <Guest61592> poor viewer|64481, enjoy the big fonts
[01:59] <coderphive> yeah and of course there's nothing in the logs about it
[01:59] <coderphive> genius
[01:59] <coderphive> gg nvidia
[01:59] <coderphive> you fail again
[02:00] <Guest61592> good job nvidia, hurting people on purpose, for shame!
[02:00] <Guest61592> nvidia is now 0.5(%) of nvidia
[02:01] <Guest61592> and ubuntu, for shame on not configuring the upstream nvidia packages with leet codes
[02:01] <Guest61592> coderphive: could try reading the upstream README's
[02:01] <Guest61592> maybe they have something about dual-monitor on-boot for KDE systems
[02:03] <viewer|64481> so any chance 18.04 works with 10 series nvidia or am I the 0.01%
[02:04] <Guest61592> it's a flat fail. let me guess you got a gaming laptop viewer|64481?
[02:04] <viewer|64481> No PC man
[02:04] <Guest61592> Hmmm
[02:04] <Guest61592> Does it use Optane?
[02:04] <Guest61592> Intel Optane
[02:04] <viewer|64481> No optane
[02:05] <Guest61592> Hmm..well, I guess there is a 13% chance the latest upstream nvidia drivers will solve your problem once installed
[02:05] <Guest61592> and a fresh restart
[02:05] <Guest61592> with fresh electricity
[02:05] <Guest61592> with fresh coffee
[02:06] <viewer|64481> Fresh install and cant get nvidia-390 to install
[02:06] <Guest61592> Let me guess, you're out of hard drive space
[02:07] <Guest61592> No but seriously, what's theerror?
[02:07] <viewer|64481> Im stuck on xorg
[02:08] <Guest61592> so xorg already has a boyfriend?
[02:08] <Guest61592> j/king
[02:09] <viewer|64481> Only option now is back to 16.04 or another distro
[02:09] <Guest61592> hmmm... well... hmmm
[02:09] <Guest61592> and 16.04 works better?
[02:09] <viewer|64481> 16.04 worked perfect
[02:10] <Guest61592> you could try the older nvidia-890 or whatever
[02:10] <viewer|64481> Cant change drivers, stuck on xorg
[02:11] <Guest61592> if you give me the total error there might be a really easy solution like `dpkg --add-architecture i386; apt update; apt install nvidia-390'
[02:11] <Guest61592> as root of course
[02:12] <viewer|64481> apt install 390 works but wont detect monitor, just stays in xorg
[02:13] <Guest61592> ooooh, so now you're in this recovery non-GUI login?
[02:13] <Guest61592> that just sucks
[02:13] <viewer|64481> I can boot to os, just cant use nvidia drivers
[02:14] <Guest61592> try reinstalling and then if that doesn't aid you then read the README files that came with the nvidia drivers
[02:14] <Guest61592> they'd be in somewhere like: /usr/share/doc/nvidia*
[02:15] <viewer|64481> Tried do it through System settings
[02:16] <Guest61592> try to execute nvidia-settings or something
[02:17] <viewer|64481> nvidia-setting works
[02:18] <Guest61592> if your computer is new enough you might need to install the nvidia drivers from the nvidia website, but I am only 3% sure that is a good idea.
[02:19] <viewer|64481> its x99 not that new
[02:20] <Guest61592> ok then if I were you I'd downgrade your nvidia upstream drivers. There are two ones, 390 and like 389 or something
[02:30] <valorie> it's never a good idea to install from the website
[02:30] <valorie> much better to get the edgers ppa or so
[02:31] <valorie> then if it doesn't work, you can ppa-purge easily
[02:31] <valorie> !ppa-purge
[02:32] <Guest61592> yeah I could imagine how scary it would be to use the nvidia from the website seeing how brutal it can actually be
[02:33] <Guest61592> I'm being 94% serious
[02:33] <Guest61592> it's a graphics driver that's suppose to do uber magic for the whole xorg scheme across a multitude of libraries that use their skill in the battle of GUI
[03:11] <valorie> @Anarcho Taoist right-click works great here
[03:14] <viewer|78098> I'm baack
[03:14] <viewer|78098> Got proper now, resolution but now have black desktop
[03:15] <valorie> that I don't know
[03:15] <valorie> I tested it many times but never that feature
[03:15] <valorie> that I recall
[03:17] <Guest84349> viewer|78098: so its sorta working?
[03:17] <valorie> that is certainly possible, Anarcho Taoist
[03:17] <viewer|78098> yes nvidia-390 is working but desktop is black
[03:19] <valorie> "working"
[03:19] <Guest84349> you're racist?
[03:19] <valorie> Guest84349: such remarks are not funny and not welcome here
[03:44] <valorie> well, you have control over single/double click in systemsettings as well
[04:00] <valorie> ok
[04:58] <jimhamill> Hi all, am trying to run Kubuntu 18.04 in a VirtualBox VM, but when I install the virtualbox-guest-x11 extension, my desktop renders incorrectly and I appear to have problems with all QML applications. I've enabled 3D acceleration on the VM Host settings and have set Video RAM to 128MB (Maximum allowed). Has anyone else bumped into this issue and have a solution?
[05:27] <valorie> jimhamill: I'm running a vm right now but with win10
[05:27] <valorie> I have the vb-guest stuff but don't recall anything about 3d
[05:27] <valorie> no problems here
[05:28] <valorie> besides the gagWin10
[05:28] <valorie> :-)
[05:35] <jimhamill> Thanks @valorie... I've encountered this a few times (usually Kubuntu within Kubuntu VirtualBox VM), but haven't been able to find much info on it on Google. I'll keep searching, see if I can pull up more info.
[05:36] <valorie> well, I've been installing and using VMs for a few years -- usually kubuntu within kubuntu for testing
[05:36] <valorie> in general it Just Works
[05:51] <CruX|> hi i have issue with KDE panel (in old kde it was called kicker)
[05:52] <CruX|> when I start opengl game this panel stops refreshing
[05:52] <CruX|> if renderer is opengl 3.1 I must restart kde to get back to normal
[05:52] <valorie> hmmm
[05:52] <valorie> when it stops updating, in my experience, it crashed
[05:52] <valorie> if you restart plasmashell that's enough
[05:53] <CruX|> it is not crashing but I see no update
[05:53] <CruX|> I am using nvidia proprietary drivers btw
[05:53] <CruX|> is it known bug ?
[05:53] <valorie> ok, but frozen perhaps
[05:53] <valorie> I do kquitapp5 plasmashell in the cli
[05:53] <valorie> then in krunner: plasmashell
[05:54] <valorie> rather than restarting
[05:54] <CruX|> ah great
[05:54] <valorie> I use nvidia too
[05:54] <valorie> unsure if it's a known bug
[05:54] <valorie> but so easy to work around I've not pursued reporting it
[05:54] <CruX|> I killed this panel with ctrl+alt+esc
[05:55] <CruX|> but didn't know a name of that program :D
[05:56] <valorie> I hang out in #plasma enough to get some hints
[05:56] <valorie> :-)
[05:58] <CruX|> valorie: and is there a solution for that ? It is really anoyng
[05:58] <valorie> I guess report it?
[05:58] <valorie> the problem is that most plasma development is not on X, it's on wayland which is the future
[05:58] <valorie> sort of leaves us nvidia users frustated
[05:59] <valorie> frustrated
[05:59] <valorie> unless nvidia decides to play nice with everyone else
[06:00] <CruX|> But I wonder why is this happening in very simple thing like panel
[06:00] <CruX|> games are more complicated like this and there are no bigger issues
[06:01] <valorie> that I don't know
[06:01] <CruX|> so kubuntu on intel gpu is using wayland by default ?
[06:01] <valorie> I don't think the panel is simple though
[06:02] <valorie> it does a lot
[06:02] <valorie> no, we're not wayland yet
[06:02] <valorie> even Ubuntu retreated from making it default for now
[06:02] <valorie> I suppose I should test that on my non-nvidia machine
[06:03] <CruX|> with wayland we loose ability to launx gui app over network ?
[06:03] <valorie> hmmm, dunno
[06:03] <valorie> I never do that, so never looked into it
[06:35] <anto79> ciao a tutti
[07:16] <Oldtrouble> Hello. Trying out linux. I have a wireless USB thing
[07:17] <Oldtrouble> I'm stretchign a cord across the room to be here. How do I get wireless turned on?
[07:48] <vespertatia> Oldtrouble: sudo apt install net-tools
[07:48] <vespertatia> then see if you can find the network interface using: ifconfig
[07:51] <Oldtrouble> nope
[07:56] <zxq9> "A wireless USB thing" <- This means a USB wifi adapter?
[08:02] <Oldtrouble> zxq9: yes
[08:42] <zxq9> Meh, just left. For posterity: https://wiki.debian.org/WiFi
[08:43] <zxq9> Between that and the Gentoo wiki on it I've always gotten USB wifi to work.
[12:00] <BluesKaj> Hey folks
[13:02] <airking> Hello!  X is being very weird.  When i reboot i get a login screen, and logging in pops uo the kubuntu logo then it just goes back to the login screen.
[13:04] <airking> if i change my tty and attempt to run startx i get "/usr/lib/xorg/Xorg: symbol lookuo error: /usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol: exaGetPixmapDriverPrivate"
[13:04] <airking> even as sudo, same thing
[13:08] <airking> I tried rebooting and now my login screen is just black with the mouse
[13:17] <coderphive> is there any way to get kscreen to recognize multiple GPU's?
[13:20] <coderphive> honestly the lack of support for multiple monitors/gpus is horrendous
[13:20] <coderphive> I can't believe it still exists today
[13:20] <BluesKaj> airking, ctl+alt+F2, login, then run sudo systemctl enable sddm, then sudo systenctl start sddm , that should bring you to your gui login page
[13:21] <BluesKaj> typo correction: system control
[13:22] <BluesKaj> oops that's wrong too, it's systemctl
[13:35] <proctrap> hah, I survived my ubuntu upgrade
[13:35] <proctrap> only took 3 hours in front of a broken nvidia driver, reinstalling the desktop & sddm
[13:35] <proctrap> only because do-release-upgrade disabled 3rd party repos
[13:36] <proctrap> ( as complete kubuntu-desktop was marked as autoremove)
[13:39] <BluesKaj> coderphive, 2 separate gpus, like one onboard and another on PCI?
[13:42] <BluesKaj> proctrap, there was no need to do release-upgrade if you were already running Bionic
[13:46] <proctrap> BluesKaj: 17.10
[13:47] <proctrap> which is end of live
[13:47] <proctrap> *life
[13:47] <BluesKaj> eol ..ok good
[13:49] <BluesKaj> proctrap, did you receive a notification to upgrade from your package manager?
 @FitchBryan, Why is this bot still in the group? Fry it.
[13:51] <proctrap> BluesKaj: no, but I didn't expect one either
[13:51] <proctrap> BluesKaj: eol is eol I would say..
[13:51] <proctrap> https://news.softpedia.com/news/ubuntu-17-10-artful-aardvark-reached-end-of-life-upgrade-to-ubuntu-18-04-lts-522022.shtml
[13:51] <proctrap> https://en.wikipedia.org/wiki/Kubuntu#Releases
[13:51] <coderphive> man
[13:51] <coderphive> I finally got it fixed
[13:52] <coderphive> multi-gpu support is a joke
[13:52] <coderphive> Basically had to make kscreen and nvidia jive
[13:52] <proctrap> coderphive: using some dual stack with nvidia prime
[13:53] <coderphive> what's that?
[13:53] <proctrap> coderphive: since 18.04 it's re-writing initramfs, dunno why
[13:53] <coderphive> wow
[13:53] <coderphive> I hope that's not what I'm in for
[13:53] <proctrap> coderphive: switched between intel and nvidia, you've to reboot for that
[13:53] <coderphive> I have dual 980's at least
[13:53] <coderphive> basically they were both fighting over xrandr it seems
[13:53] <proctrap> coderphive: using that together with bbswitch to power safe when intel's in charge
[13:54] <proctrap> coderphive: prime is basically rewriting my x11 config, so upon reboot the other one is in charge
[13:54] <BluesKaj> nvidia-prime is mostly for Optimus systems on laptops that use an intel gpu for lower loads then an nvidia for the higher loads,
[13:55] <coderphive> oh okay
[13:55] <coderphive> oh, switchable graphics
[13:55] <coderphive> aka
[13:55] <proctrap> coderphive: you mean two gpus at the same time ?
[13:55] <coderphive> yeap
[13:55] <proctrap> aaaah
[13:55] <proctrap> so I got you wron
[13:55] <coderphive> using Base Mosaic
[13:56] <coderphive> bruh, straight up masochism
[13:56] <proctrap> BluesKaj: well I just followed https://help.ubuntu.com/community/BionicUpgrades/Kubuntu#Upgrade_Kubuntu_from_16.04_or_17.10_to_18.04
[13:57] <proctrap> BluesKaj: and as the nvidia driver is from another repo it disabled the 3rd party repo
[13:57] <proctrap> but also marked the whole KDE stack for autoremove
[13:57] <proctrap> but this time I got around by booting into recovery, re-adding nvidia, dist-upgrade on it
[13:57] <proctrap> and doing a apt install kubuntu-desktop
[13:58] <proctrap> so, this time I didn't reinstall the whole system
[13:58] <proctrap> (I tried the upgrade upon 18.04 release already, back then had to roll back and reinstall 17.10)
[13:59] <BluesKaj> proctrap, yeah, next time don't let your OS lapse into EOL :-)
[13:59] <proctrap> BluesKaj: uhm
[13:59] <proctrap> BluesKaj: I've just waited till I've had the time to come up with all of this
[13:59] <proctrap> BluesKaj: I've done that before EOL, upon the first 18.04 release
[13:59] <proctrap> except, the same stuff hapened
[14:00] <proctrap> blackscreen upon boot
[14:00] <proctrap> BluesKaj: so I tried before, leading to a complete reinstall as I didn't have had the time
[14:01] <BluesKaj> proctrap, always make sure  to upgrade all packages if your OS repos are still active before upgrading to next release
[14:02] <proctrap> BluesKaj: the thing is I trusted it first
[14:02] <proctrap> BluesKaj: like "ok, let's do that first, probably some changes required before doing the 3rd parties"
[14:02] <coderphive> That's basically what I did
[14:02] <coderphive> A ton of recovery bouncing
[14:02] <coderphive> lol
[14:02] <coderphive> Garbage
[14:02] <proctrap> BluesKaj: I mean if that tool disabled 3rd parties on its own, it'll have a reason for that
[14:03] <proctrap> was my idea
[14:03] <proctrap> what I didn't get is why apt marked the complete KDE desktop for autoremove
[14:03] <proctrap> coderphive: back in time is still the best tool for such stuff :D
[14:04] <BluesKaj> I never use 3rd  parties when upgrading to a new release...seldom use them anyway
[14:05] <BluesKaj> ok, bbl, stuff to do for a few mins
[14:06] <coderphive> uh
[14:06] <coderphive> I think the graphics drivers have some tie into the desktop
[14:06] <coderphive> They do with normal ubuntu desktop
[14:06] <proctrap> coderphive: hm, yeah that could be it
[14:07] <proctrap> coderphive: (first time I tried that upgrade (before EOL) I was like "okay, it'll probably do it right", removing the complete desktop..)
[14:46] <iome> mina
[14:47] <BluesKaj> proctrap, never seen the whole desktop get removed on an upgrade
[14:48] <BluesKaj> release
[15:07] <iome> salve a tutti
[18:52] <foo__> hello
[18:52] <foo__> i have a question reguarding konsole
[18:53] <foo__> i accidently deleted the key binding lists, is there a way to recover those?
[19:04] <genii> foo__: Those files are in package konsole-kpart
[19:05] <genii> So you could ctrl-alt-F1 and then: sudo apt-get install --reinstall konsole-kpart      ...then alt-F7 back to Kubuntu
[19:35] <mralc2> is there a recommend backup app in kubuntu?
[19:37] <genii> !info kbackup
[19:37] <genii> Hm
 @mralc2, Backintime-qt4 is pretty good
[19:51] <mralc2> thanks Scyt4l3 i have a look
[19:52] <mralc2> thanks @Scyt4l3 i have a look
[23:31] <jrss> is there a remote desktop server with kubuntu?
[23:31] <jrss> I used the minimal install so maybe not... what is recommended? I will be connecting from a SUSE OS VM
[23:32] <jrss> or windows actually. that would work to
[23:32] <jrss> so connecting from windows or SUSE OS to Kubuntu
[23:34] <jrss> Krfb?