[00:43] <s3cz0ne> no dice?
[00:45] <s3cz0ne> Anbody know of a graphical SAMBA config program that will work under Plasma?
[01:35] <Gilti> What in the world is Tor ..... Yes I know ID ten T alert
[01:36] <Gilti> some of you may remember me from a few nights ago under the name giltibobcat
[01:39] <Gilti> amazing so many people so little chatting
[03:26] <hhernandez> I noticed that when I installed the Nvidia drivers that I need to reinstall hal to get some sitres to work again. I have had to do this a few times. I wondering is this an known issue?
[06:52] <carlo__> Hi~ I'm running Kubuntu 15.05, the package bluedevil installed, but I can't find bluetooth from system settings and system tray. sorry for my language!
[06:54] <carlo__> I can launch bluetooth by "kcmshell4 bluedeviladapters"
[07:28] <lordievader> Good morning.
[08:05] <mirkop> hi there, i have some sort of issue with cryptdisks. Using Kubuntu 15.04 I get prompted for my crypt password during boot for all kernels up to -21. All other kernels after that crap out and i don't get prompted for my crypt password
[08:06] <lordievader> mirkop: Cryptdisk? Is that ecryptfs or LUKS (or something else)?
[08:07] <mirkop> lordievader: Its LUKS
[08:10] <lordievader> mirkop: You could break init at mount and see if you can unlock your luks volume manually.
[08:11] <mirkop> lordievader: yep, good point. I will try that. Still wonder why the behaviour would change with a different kernel...
[08:12] <lordievader> Yeah, it is kind of strange that it changes with a -xx kernel change.
[08:13] <mirkop> lordievader: its pretty much standard ubuntu install with an encryped home directory which is on a dedicated partition
[08:14] <lordievader> Ah, then it can also be a systemd update.
[08:14] <mirkop> lordievader: kernel -15 and -21 are fine but then -26 and onwards fail
[08:14] <lordievader> Is systemd updated recently?
[08:14] <mirkop> umm
[08:15] <mirkop> let me check
[08:20] <mirkop> mmh there was a systemd update around the time i got the latest working kernel
[08:21] <mirkop> what do you think could have changed with systemd?
[08:21] <mirkop> I just need a hint then i can go away and investigate myself
[08:22] <lordievader> Well if the rootfs ain't luks it is likely that systemd takes care of the unlocking of the volume. Is the luks volume defined in /etc/crypttab?
[08:23] <mirkop> only a home directory is encrypted and yes the luks volume is in the crypttab
[08:24] <lordievader> Hmm, systemd should read that file to determine what to open.
[08:24] <mirkop> i am pretty sure i have tried to remove in from crypttab
[08:24] <mirkop> cause i thought it doesnt necessarily need to be available during boot
[08:26] <mirkop> *decrypted during boot
[08:38] <lordievader> Well if you want to login... your home dir should be available at that time ;)
[08:47] <mirkop> lordievader: i wasnt telling the truth
[08:47] <mirkop> problem is the later kernels can't find the root device
[08:48] <lordievader> Ah, that is a different problem.
[08:49] <mirkop> Indeed ;-)
[08:49] <lordievader> Break init at mount point and see if you can find it yourself.
[08:49] <mirkop> i end up in a busybox
[08:49] <mirkop> and I cannot see the devices under /dev/mapper
[08:49] <lordievader> Lvm?
[08:50] <mirkop> thats the root
[08:50] <mirkop> /dev/mapper/kubuntu--vg-root
[08:50] <mirkop> yep
[08:50] <lordievader> Right, can you see the disk itself?
[08:51] <mirkop> mmh
[08:51] <mirkop> you mean pvdisplay?
[08:51] <mirkop> or  /dev/sdX?
[08:51] <lordievader> No, I mean is /dev/sda (or whatever) available.
[08:51] <mirkop> I havent checked that
[08:51] <mirkop> brb
[08:52] <mirkop> just need to reboot
[08:58] <mirkop_> lordievader: well we are back to encryption
[08:59] <mirkop_> so it looks like sda5 is encrypted
[08:59] <mirkop_> which is a physical volume
[08:59] <mirkop_> for the one VG i have
[08:59] <mirkop_> which contains the root
[08:59] <mirkop_> the root fs is encrypted
[09:00] <lordievader> mirkop_: Do you tell your initrd that it is encrypted?
[09:01] <mirkop_> not sure. I have checked the grub.cfg and it doesnt have any special flags
[09:01] <mirkop_> its pretty much the same for all kernels
[09:04] <lordievader> Hmm, it seems I have forgotten how Ubuntu does luks.
[09:04] <lordievader> Or grub/initrd for that matter.
[09:04] <mirkop_> no worries
[09:05] <TJ-> For root-fs? it installs cryptsetup and conf/conf.d/cryptroot and supporting scripts/libs in the initrd
[09:05] <mirkop_> I will do some digging
[09:05] <TJ-> For encrypted GRUB root,it  does it via "GRUB_ENABLE_CRYPTODISK=y" passed to grub-install
[09:05] <lordievader> Ah, TJ- is here to save the day ;)
[09:06] <TJ-> For the latter, there's no GRUB command-line (only rescue shell) until the GRUB root is unlocked
[09:07] <mirkop_> so I should try to add GRUB_CRYPTODISK_ENABLE=y to /etc/default/grub ?
[09:07] <mirkop_> and run update-grub?
[09:08] <TJ-> run grub-install too. It has to build a core.img with cryptdisk, gcry_rijndael, luks modules included
[09:09] <TJ-> and it embeds the cryptroot UUID
[09:10] <TJ-> An interesting note of caution: On UEFI with SecureBoot encrypted GRUB root will fail, because the EFI signed image pre-built by Canonical and signed with their key doesn't include the modules.
[09:12] <mirkop_> reboot
[09:12] <mirkop_> will be right back
[09:12] <mirkop_> ...hopefully
[09:15] <mirkop_> mmh
[09:16] <mirkop_> grub-install /dev/sda probably didnt create the image
[09:16] <mirkop_> it ran only a second or so
[09:16] <mirkop_> It gets a bit late here
[09:16] <mirkop_> thanks for your help guys
[09:16] <TJ-> mirkop_: "grub-install -v" will tell you what it is doing
[09:18] <mirkop_> it didnt generate a new core.img
[09:18] <mirkop_> anyway, thanks again
[09:18] <TJ-> mirkop_: "grub-install -v /dev/sda" didn't? Hmmm, that is strange. what error?
[09:18] <mirkop_> no error
[09:18] <mirkop_> it was fine
[09:18] <mirkop_> but it didnt fix the issue
[09:19] <TJ-> mirkop_: were there lots of lines of output with '-v' ... those are reporting the modules being linked into the image.
[09:20] <mirkop_> yep, lots of lines
[09:20] <mirkop_> I just ran it again
[09:20] <TJ-> mirkop_: oh! in "/etc/default/grub" it should be "GRUB_ENABLE_CRYPTODISK=1" not "=y" !
[09:21] <mirkop_> ok
[09:21] <mirkop_> one more try :-)
[09:23] <TJ-> Arghh! No, I was caught by the bug I fixed! see bug 1278114 and GRUB bug 41524! It *should* be "=y" but the documentation is wrong!
[09:24] <TJ-> Silly ubottu, I said *GRUB* bug!
[09:24] <TJ-> mirkop_: oh! in "/etc/default/grub" it should be "GRUB_ENABLE_CRYPTODISK=1" not "=y" !
[09:24] <TJ-> Arghh! No, I was caught by the bug I fixed! see bug 1278114 and GRUB bug-41524! It *should* be "=y" but the documentation is wrong!
[09:24] <mirkop_> haha
[09:24] <mirkop_> classic
[09:25] <TJ-> sorry! I always get confused by that. The reason I told you wrong is I grepped the strings in grub-isntall for 15.10's GRUB and it still has the buggy value; I'd assumed we'd synced with upstream by now and fixed it
[09:25] <mirkop_> ill try this
[09:25] <mirkop_> GRUB_CRYPTODISK_ENABLE=y
[09:25] <mirkop_> no quote
[09:25] <mirkop_> quotes
[09:26] <TJ-> mirkop_: Here's the last few lines of my "/etc/default/grub" (that works!):
[09:26] <TJ-> # Uncomment to get a beep at grub start
[09:26] <TJ-> #GRUB_INIT_TUNE="480 440 1"
[09:26] <TJ-> GRUB_ENABLE_CRYPTODISK=y
[09:26] <TJ-> GRUB_DISABLE_OS_PROBER=true
[09:27] <TJ-> There was another earlier bug I seem to recall where documentation got the variable name wrong, and it looks like you have that "GRUB_CRYPTODISK_ENABLE" is incorrect, it should be "GRUB_ENABLE_CRYPTODISK"
[09:27] <TJ-> Grrr, he's in and out faster than a ...!
[09:30] <mirkop_> it didnt
[09:30] <mirkop_> arrg
[09:30] <mirkop_> I will check with you guys again tomorrow
[09:32] <TJ-> There was another earlier bug I seem to recall where documentation got the variable name wrong, and it looks like you have that "GRUB_CRYPTODISK_ENABLE" is incorrect, it should be "GRUB_ENABLE_CRYPTODISK"
[09:32] <TJ-> mirkop_: I am assuming the issue you are trying to fix is an unecrypted GRUB root file-system ?
[09:33] <TJ-> s/unencrypted/encrypted/
[09:33] <mirkop_> thats right
[09:34] <TJ-> good :)
[09:37] <mirkop_> allright
[09:37] <mirkop_> so something has changed
[09:37] <mirkop_> I now get an error
[09:37] <mirkop_> "device name required"
[09:37] <TJ-> *when* do you see that?
[09:37] <mirkop_> between grub and loading the kernel
[09:38] <mirkop_> just after grub
[09:38] <lordievader> Wasn't there some crypt_root you needed to set or something?
[09:38] <mirkop_> still, the old kernel loads
[09:38] <mirkop_> -21 loads
[09:38] <TJ-> mirkop_: Can we go back a few minutes, so I can confirm something? In the reboots you have been doing to test this, was grub failing and presenting a "grub rescue>" prompt?
[09:39] <lordievader> I remeber having to set something on my gentoo box when I still used an genkernel's initramfs.
[09:39] <mirkop_> I always get a busybox shell
[09:39] <lordievader> crypt_root=UUID=<encrypted partition uuid>
[09:39] <mirkop_> so I guess i get beyond grub
[09:39] <lordievader> ^ that.
[09:39] <TJ-> mirkop_: So you always got Busybox shell. So therefore GRUB's root FS *cannot* have be an encrypted device!
[09:39] <mirkop_> true
[09:40] <mirkop_> :-)
[09:40] <TJ-> So all this messing with GRUB_ENABLE_CRYPTODISK is pointless
[09:40] <mirkop_> I shall reverse the chage
[09:40] <TJ-> So you *don't* have an encrypted GRUB!
[09:40] <lordievader> mirkop_: Set the crypt_root ;)
[09:40] <TJ-> OK, so the issue will be re-generation of the initrd.img. That relies on the "/etc/crypttab" entry for the root file-system
[09:41] <TJ-> mirkop_: Which Ubuntu release is it?
[09:41] <mirkop_> 15.04
[09:41] <TJ-> Right, so the PC is using systemd-init
[09:41] <TJ-> Are you using a LUKS key-file to unlock the encrypted root file-system?
[09:42] <mirkop_> not sure
[09:42] <TJ-> mirkop_: show us "/etc/crypttab" assuming you've not got any secrets in it as comments
[09:42] <mirkop_> sda5_crypt UUID=2419f722-087a-42ef-a6bb-da0cdedeec4c none luks,discard
[09:44] <TJ-> mirkop_: Good. Now do "sudo update-initramfs -vu -k $(uname -r) |& tee /tmp/initrd.log" and then "pastebinit /tmp/initrd.log"
[09:45] <mirkop_> umm
[09:45] <mirkop_> i dont want to do that for my current kernel
[09:45] <mirkop_> cause that is the only one that is still working
[09:46] <TJ-> mirkop_: Give it an older kernel version then, with the -k option
[09:46] <mirkop_> will do 3.19.0-28-generic
[09:47] <mirkop_> http://paste.ubuntu.com/12610219/
[09:49] <TJ-> Line 605 looks promising, as does line 704
[09:50] <TJ-> mirkop_: Now do "update-gub" to ensure the grub.cfg has the correct entries and that should be all done. If it fails after that you've got some custom/manual changes that are throwing things out.
[09:50] <mirkop_> i have removed the cryptdisk line from /etc/default/grub
[09:51] <TJ-> mirkop_: Good, that wouldn't hurt but wasn't used.
[09:53] <mirkop_> woohoo. the world is a bit safer. I am running the latest kerne
[09:54] <mirkop_> i thought the update-initramfs command is being executed with every kernel update
[09:54] <mirkop_> thanks TJ and lordievader
[09:54] <TJ-> mirkop_: it should be, it's called by a post-inst kernel hook
[09:54] <mirkop_> ill better run it manually after
[09:55] <mirkop_> a kernerl upgrad
[09:55] <mirkop_> e
[09:55] <TJ-> mirkop_: of just use "lsinitramfs /boot/xxxx | grep 'crypt[ds]' " and check the cryptsetup and cryptroot files are in
[09:55] <TJ-> s/of just/or just/
[09:56] <mirkop_> ok sweet
[09:56] <mirkop_> will do
[09:56] <TJ-> sheesh, my typing is terrible today! ... "...  | grep 'crypt[sr]' " !
[11:05] <BluesKaj> 'Morning folks
[11:11] <diziart_> Hi all
[11:11] <lordievader> o/
[12:52] <dexterlabs> I'm running 15.04, and I regularly have issues with kscreen.
[12:52] <dexterlabs> that the saved configuration causes some processes to segfault.
[12:52] <dexterlabs> Where is the best place to debug this?
[12:52] <dexterlabs>  Im no kde-dev, so I mean to let other devs figure out what's going wrong.
[12:52] <BluesKaj> dexterlabs, plasmashell -v, in the terminal
[12:53] <dexterlabs> plasmashell -v
[12:53] <dexterlabs> kf5.kiconthemes: "Theme tree: (Breeze Dark)"
[12:53] <dexterlabs> Unknown option 'v'.
[12:53] <BluesKaj> make sure it's  -v ?
[12:53] <dexterlabs> it is
[12:53] <dexterlabs> plasmashell  -h
[12:53] <dexterlabs> kf5.kiconthemes: "Theme tree: (Breeze Dark)"
[12:53] <dexterlabs> Usage: plasmashell [options]
[12:53] <dexterlabs> Options:
[12:53] <dexterlabs>   -h, --help                   Displays this help.
[12:53] <dexterlabs>   -d, --qmljsdebugger          Enable QML Javascript debugger
[12:53] <dexterlabs>   -w, --windowed               Force a windowed view for testing purposes
[12:53] <dexterlabs>   -n, --no-respawn             Do not restart plasma-shell automatically after
[12:54] <dexterlabs>                                a crash
[12:54] <dexterlabs>   -c, --crashes <n>            Recent number of crashes
[12:54] <dexterlabs>   -s, --shut-up                Shuts up the output
[12:54] <dexterlabs>   -p, --shell-plugin <plugin>  Fplasmashell  -h
[12:54] <dexterlabs> kf5.kiconthemes: "Theme tree: (Breeze Dark)"
[12:54] <dexterlabs> Usage: plasmashell [options]
[12:54] <dexterlabs> Options:
[12:54] <dexterlabs>   -h, --help                   Displays this help.
[12:54] <dexterlabs>   -d, --qmljsdebugger          Enable QML Javascript debugger
[12:54] <dexterlabs>   -w, --windowed               Force a windowed view for testing purposes
[12:54] <BluesKaj> !paste
[12:54] <dexterlabs>   -n, --no-respawn             Do not restart plasma-shell automatically after
[12:54] <dexterlabs>                                a crash
[12:54] <dexterlabs>   -c, --crashes <n>            Recent number of crashes
[12:54] <dexterlabs>   -s, --shut-up                Shuts up the output
[12:54] <dexterlabs>   -p, --shell-plugin <plugin>  Force loading the given shell plugin
[12:54] <dexterlabs>   -a, --standalone             Load plasmashell as a standalone application,
[12:54] <dexterlabs>                                needs the shell-plugin option to be specified
[12:54] <dexterlabs> orce loading the given shell plugin
[12:54] <dexterlabs>   -a, --standalone             Load plasmashell as a standalone application,
[12:54] <dexterlabs>                                needs the shell-plugin option to be specified
[12:54] <BluesKaj> dexterlabs,  stop this
[12:54] <dexterlabs> srry
[12:55] <dexterlabs> BluesKaj: http://paste.ubuntu.com/12611898/
[12:59] <BluesKaj> dexterlabs,  here's mine http://pastebin.ca/3178090
[13:00] <BluesKaj> you'll see that plasmashell -v is an option, I think you need to enable the backports in your sources.list
[13:01] <dexterlabs> I didn't enable the backports.
[13:02] <BluesKaj> plasma 5.4 should be available if you enable them
[13:05] <dexterlabs> cool, will do. thanks!
[13:16] <dexterlabs> Hmm, I did have backports enabled appearantly
[13:17] <dexterlabs> this is the one right? http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu
[13:17] <dexterlabs> Or should I add: ppa:kubuntu-ci/stable
[13:21] <BluesKaj> dexterlabs,  run sudo apt dist-upgrade
[13:24] <dexterlabs> I'm up to date.
[13:25] <BluesKaj> I'm on 15.10 beta2 , i'm surprised plasma 5.4 isn't in the backports on 15.04 yet
[13:26] <BluesKaj> you can add the ppa
[13:29] <dexterlabs> which ppa?
[13:29] <dexterlabs> the kubuntu-ci one?
[13:34] <BluesKaj> yes dexterlabs  sudo add-apt-repository ppa:kubuntu-ci/stable, and if that doesn't work you may want to comment the backports
[13:38] <BluesKaj> dexterlabs,  did you try to install plasma-desktop with the backports enabled, sorry i forgot to mention thet
[13:41] <dexterlabs> No, I installed kubuntu by downloading the image from the site
[13:41] <dexterlabs> but plasma-desktop is the newest version
[13:43] <dexterlabs> BluesKaj: Now upgrading to kubuntu-ci
[13:55] <dexterlabs> BlueKaj: Thank you, plasmashell appearantly has -v in the new version.
[17:11] <rene_> Hi. On my Kubuntu vivid i get an timeout when trying to connect to my company vpn server.
[17:12] <rene_> the same config on my Linux Mint laptop works. What can i compare to find the reason?
[17:15] <rene_> openvpn version seams to be the same 2.3.2 x86_64 with differen build dates
[17:17] <rene_> the message it breaks is:UDPv4 link remote: [AF_INET]xxx.xxx.xxx.xxx:1194. VPN connection 'Rene' connect timeout exceeded.
[17:17] <samsher> I installed kubuntu just now but now when I login kde plasma lags due to absence of nvidia driver! now how do I install nvidia driver? network seems not working as well.
[17:18] <rene_> on mint there comes [xxx.xxx.xxx.xxx] Peer Connection Initiated with [AF_INET]xxx.xxx.xxx.xxx:1194
[18:06] <rene_> oh found the partly reason
[18:06] <rene_> there was some route left to the vpn server in the routing table
[18:07] <rene_> so that openvpn couldnt get a route to the host
[19:09] <Draggin> Good evening. My question isn't necessarily a Kubuntu question as such, but I'm running Kubuntu, so I thought I'd come check for a starting point here. The issue is really with an old AGP8x nVidia graphics card and the nVidia legacy drivers on Kubuntu 14.10 - with the drivers installed, my display is horribly grabled (almost as if the refresh rate isn't correct, or something like that), without the (nVidia) drivers
[19:09] <Draggin>  (using Nouveau, I assume), I get stuck in an endless login loop at the lightdm login screen
[19:09] <HackerII> maybe try the 173 drivers
[19:10] <HackerII> sure is an old card
[19:10] <Draggin> HackerII
[19:11] <Draggin> According to the nVidia site, I should be using the 304 drivers...
[19:11] <Draggin> Why do you think the 173 drivers might do the trick?
[19:11] <HackerII> what card is it actually 8**** ?
[19:11] <HackerII> and, is it a notebook card ?
[19:13] <HackerII> o, didnt see the  AGP
[19:13] <Draggin> HackerII - it's an nVidia GeForce 6200
[19:13] <HackerII> so, id still try the 173 driver
[19:13] <Draggin> Well old :)
[19:14] <Draggin> But this machine is pretty old itself and doesn't have built-in graphics, so I'm stuck with this card...
[19:14] <HackerII> ic that
[19:14] <HackerII> im not sure 304 will work with nvidia6 tho,
[19:14] <Draggin> Having a look at the 173 drivers now
[19:15] <HackerII> yeah do that
[19:15] <HackerII> 173 is closer to that agp than any i kno of right now
[19:16] <Draggin> Ah. I see now. Yeah, it does actually sound like I should be using those, and not 304... Wonder why the nVidia driver selector page recommends 304 then. Let me see what happens when I try 173. Will keep you posted in a minute :)
[19:16] <HackerII> ive seen alot of that there
[19:16] <HackerII> couldnt tellya
[19:17] <HackerII> dont forget to sudo apt-get purge nvidia*
[19:17] <HackerII> then install 173
[19:18] <HackerII> and reboot after
[19:18] <HackerII> brb coffee
[19:22] <BluesKaj> Draggin,  perhaps nvidia gave you the 8000 series rec'd driver
[19:22] <BluesKaj> Draggin,  perhaps nvidia gave you the 8000 series rec'd driver
[19:23] <BluesKaj> oops
[19:24] <Draggin> BluesKaj - I suppose it's possible, but this is the page I used: http://www.nvidia.com/Download/index.aspx it allows you to fill in all the details of your card and then tells you the appropriate driver
[19:24] <BluesKaj> no need to purge nvidia, apt will autoremove the existing driver during the new driver installation
[19:24] <Draggin> BluesKaj - suppose a purge wouldn't hurt though, right?
[19:25] <BluesKaj> Draggin,  well, that's your call , but it is redundant
[19:30] <Draggin> HackerII, BluesKaj - Hmmm... next problem... In the past, I've used the Xorg Edgers PPA to install the nVidia drivers, but either I'm doing something wrong, or the 173 drivers aren't available in that PPA... Should I just manually download and install the 173 drivers from the nVidia site?
[19:32] <soee> why you want 173 ?
[19:32] <BluesKaj> Draggin,  no they should be available in the repos
[19:32] <TJ-> Draggin: They're in the restricted repo
[19:33] <Draggin> Ah - TJ- thanks
[19:33] <Draggin> Let me enable that quickly
[19:42] <Draggin> Okay no... I'm getting stuck...
[19:43] <Draggin> 304 is available, 310, 331, 313 and 319, but no 173
[19:47] <BluesKaj> Draggin,  then your only option is the nvidia site if the 304 doesn't work on that card
[19:48] <Draggin> BluesKaj - Shoot... I've never installed a driver in Linux that way... Hope it doesn't muck things up even worse. I suppose 173 isn't in the repositories anymore because 304 superceded it?
[19:50] <HackerII> ive got about 5 mins, ill post some directions, after that your at the mercy of the rest here
[19:50] <BluesKaj> Draggin,  there used to be a legacy repos for older OSs, but  if you're on a recent ubuntu then there's no point for thatone
[19:51] <Draggin> HackerII - thanks :)
[19:52] <HackerII> download the 173 to your home,  drop to terminal with ctrl+alt+f2,  sudo service lightdm stop    .. then...  sudo sh ./NVIDIA-Linux-x86-173***.run  ** = the last numbers of 173, say yes to all, when done sudo reboot
[19:55] <Draggin> HackerII - great, thanks :) Just finished downloading, going to copy it over to the messed up machine now and give it a shot. Holding thumbs... Thanks for all the help!
[19:56] <HackerII> if it complains that there is already nvidia on it,  do  .. sudo apt-get remove --purge nvidia*
[19:56] <BluesKaj> Draggin,  which ubuntu do you have on that old  machine?
[19:56] <HackerII> then install 173
[19:58] <Draggin> BluesKaj - Kubuntu 14.10, why?
[19:58] <HackerII> what processor does it have
[20:00] <HackerII> also, if the card is only 128, make sure you alocate more ram from bios
[20:00] <BluesKaj> kde4 good stuff, altho 14.10 is EOL. Some like the new plasma 5 on 15.04, others don't , I'm still using 14.04 LTS
[20:00] <HackerII> yeah
[20:00] <HackerII> i think 173 is in 14-04 also
[20:00] <BluesKaj> but I am testing 15.10 beta2 atm
[20:01] <BluesKaj> 14.04 has long term support, that's why I'm sticking with it as my main OS
[20:01] <HackerII> i always do, have 12 and 14
[20:02] <HackerII> waiting to see 16 to see systemd work
[20:03] <BluesKaj> 15.04 and 15.10 have systemd
[20:03] <HackerII> yeah
[20:03] <HackerII> i quit the 6 month gig when it stopped 18 month suppoer
[20:04] <HackerII> support
[20:04] <HackerII> i havent used kde since 3.5
[20:06] <BluesKaj> well, I'm thinking kde4 plasma4 is their best effort so far, plasma5/kf5 doesn't impress me much
[20:06] <HackerII> i wondered if that worked out, they always say, get it now works great
[20:07] <HackerII> +, the color scheme looks like crayola
[20:08] <HackerII> my friend just pulled up, bbl
[20:11] <BluesKaj> the plasma5 default desktop wallpaper is silly, that's first thing to go
[20:24] <Draggin> Gah!
[21:14] <mornando> Hi
[21:15] <mornando> I'm looking to upgrade my OS to run Kubuntu but i'm concerned that my graphics driver will not work
[21:16] <mparillo> I recommend a live usb to see if it works out of the box
[21:16] <mparillo> Even if it doesn't, and you have some patience there are folks here who have experience with graphics drivers (not me).
[21:30] <Draggin> Finally got it all up and running!
[21:31] <Draggin> HackerII - looks like BluesKaj has left, but thanks so much for all the advice and assistance...
[21:31] <Draggin> Perhaps I can now push a few more months out of this machine before having to replace it with something decent and modern :)
[21:37] <Draggin> Thanks again! G'night!
[22:01] <zKarp> Hello, is there anyway to allow KMAIL to access KWallet without having to type the password?
[23:08] <txonis> Has anyone noticed that on 15.10, Shift+Del file delete warnings are gone?
[23:08] <txonis> (inside Dolphin)
[23:09] <txonis> quite scary, since pressing shift by mistakes means your files are gone, without option to opt-out
[23:10] <bprompt> txonis:    doesn't dolphin dump them into the trash?   it does for me
[23:11] <bprompt> well, I'm not on 15.10 anyhow, 12.04, but I think it's a dolphin setting, as opposed to not being there
[23:12] <txonis> shift+delete deletes them without trash
[23:12] <bprompt> hmm
[23:12] <txonis> if you revert all changes from dolphin to default, it warns you, but something made my kde settings from 15.04 ignore that warning in 15.10
[23:12] <txonis> and I'm pretty sure I had warnings before
[23:13] <bprompt> txonis:   ok... I can buy that, well, use something else then :), I use krusader, and you have the choice to either delete completely or to trash
[23:13] <txonis> sorry, I only noticed now that reverting settings left it as supposed to
[23:14] <txonis> bprompt: sure. But dolphin is the default file manager. I like deleting directly without trash:/, but I wonder what went wrong during the migration
[23:14] <bprompt> hmm hmm dunno
[23:15] <bprompt> txonis:    btw, you can change default apps in settings :)
[23:15] <txonis> it must be kde related anyway
[23:15] <bprompt> so, is the one shipped, yes, is not bad either, but I do dual-panes, thus
[23:15] <txonis> bprompt: I do, I can even create my own. But do you believe most do? heh
[23:15] <bprompt> txonis:     krusader is a kde app
[23:16] <txonis> bprompt: dolphin does folder splitting
[23:16] <bprompt> just a bit independent on lots of settings
[23:16] <txonis> ie, dual panels
[23:16] <txonis> and integrates nicely with konsole
[23:17] <bprompt> txonis:   yes and no, it does, I use it now and then, yes, krusader has much more flexibility IMO, like each pane does its own tabbing, Iike I usually run each pane with 9tabs or so each
[23:18] <txonis> to each their own, heh. I use terminal mostly
[23:19] <txonis> I tend to use dolphin when I want to manage multimedia files due to the preview
[23:19] <txonis> no need to open the files and delete (!)
[23:19] <bprompt> same with krusader, actually, in krusader you can tell it what terminal app you wish, but konsole is great, and it integrates with it as well
[23:19] <txonis> thus my worry