[00:11] <joh6nn> using kubuntu 14.04, my screensaver always locks, even if i set screen locker type to screensaver, and uncheck "require password"
[00:11] <joh6nn> i don't see a way to set it to not lock the screen
[00:12] <joh6nn> i found a KDE bug report for this from 4.10, but it says that it was fixed in 2013: https://bugs.kde.org/show_bug.cgi?id=310871
[00:15] <joh6nn> is anyone else seeing this behavior, or am i just doing something wrong?
[01:02] <mark__> hi
[01:04] <mark__> are there other rooms?
[01:05] <TheFakeazneD525> mark__: uh... I guess
[01:05] <TheFakeazneD525> what do you have in mind mark
[01:05] <TheFakeazneD525> er, mark__
[01:05] <Unit193> !alis
[01:11] <mark__> ok i give up
[01:13] <dolomite> ok
[02:22] <LogicalDash> Sometimes when I have to change the resolution, like for certain games, it causes fonts to go blurry when I switch back to my full screen resolution. Pretty sure this is to do with desktop effects since the fonts clear up when I suspend desktop effects.
[02:22] <LogicalDash> Is there a way to prevent this? Or at least make it stop without disabling desktop effects altogether?
[02:27] <abnemo> hello. is anybody there?
[02:34] <valorie> !ask | aboudreault
[04:53] <shannon> hello
[06:28] <lordievader> Good morning.
[06:28] <TheFakeazneD525> guten morgen :}
[06:30] <lordievader> Hey TheFakeazneD525, how are you?
[06:30] <TheFakeazneD525> I'm good, you?
[06:32] <lordievader> Haven't had my first coffee yet.
[06:33]  * TheFakeazneD525 slides lordievader a coffee
[06:34] <lordievader> Thanks :)
[10:30] <alvin> Is it me, or is plasma5 (14.10 beta) missing a GUI printer configuration?
[10:50] <BluesKaj> Hi all
[11:11] <alvin> Good afternoon. (Well, here it's afternoon)
[11:12] <alvin> and another session with Plasma5. Bending it to my will.
[11:12] <alvin> We've yet to see who is strongest.
[11:15] <lordievader> alvin: You are, and if not.. sudo ;)
[11:15] <alvin> lol
[11:16] <alvin> "I am root"
[11:17] <lordievader> alvin: That's bad practice ;)
[11:17] <alvin> I know. But somebody has to be
[11:18] <alvin> By the way, plasma5 will not be offered as the default choice for 14.10 I suppose?
[11:20] <BluesKaj> 5 still needs a lot of work so i doubt it
[11:22] <alvin> That's good. It would be too soon.
[11:25] <alvin> Hmm, I files this bug 1282531 in february, but it has not received any attention. Should this be filed in Debian instead? (Speedcrunch used to be included in Kubuntu by default if I remember correctly)
[12:16] <floown> hello
[12:17] <floown> I have installed Moblock (Peerguardian) but Chokoq is bloqued
[12:17] <floown> I have add :  twitter:199.16.156.102 in /etc/pgl/allow.p2p
[12:17] <floown> I have restart de daemon, but my timeline is not read
[12:17] <floown> What's wrong?
[12:24] <alvin> floown: I've never used Moblock. That said, you probably have to allow the Twitter API. Do you know where Choqok connects?
[12:25] <alvin> host twitter.com points to 4 addresses.
[12:25] <floown> Ah ok!
[12:25] <floown> what's the ip please?
[12:25] <floown> Have do a ping
[12:25] <alvin> Just type this in your terminal: host twitter.com
[12:25] <floown> ok
[12:30] <alvin> floown: According to wireshark, Choqok connects to api.twitter.com, so use the addresses from host api.twitter.com and you'll be fine.
[12:33] <floown> alvin: thx a lot, it works with the right servers
[12:33] <alvin> :-)
[14:47] <ik_> hi ¡¡
[14:47] <lordievader> o/
[14:47] <SonikkuAmerica> \o
[14:48] <ik_> mmmmm ...
[14:49] <lordievader> Such randomness...
[15:51] <xiex> admin
[16:12] <rberg_> I messed up big time.. can anybody tell me what the kubuntu default font is in kate?
[16:14] <rberg_> I accidentally changed it :( I was looking at m+ so I could put it in the konsole config manually
[16:14] <BluesKaj> rberg_, it's set in system settings>app appearance>fonts , but usually the ubuntu font is default if no changes were made
[16:19] <rberg_> ubuntu medium looks ok.. thanks.. but I dont think that is what it was
[16:23] <BluesKaj> rberg_, changes in system settings fonts is global for the user, but not as user with root permissions
[16:24] <jinksies> rberg_: I think the default is not medium but regular
[16:24] <jinksies> size 9
[16:27] <rberg_> I should also note I changed the font in kate only.. I think the system monospace font looks like what I want
[16:29] <rberg_> ahh yeah when I do kdesudo kate its using monospace
[16:31] <BluesKaj> you can make it global with root permissions by running kdesudo systemsettings in krunner then adjusting the fonts
[19:05] <DaHoC> Hi everyone, I want to install kubuntu on my new machine, the core should go on the SSD and the /home, /tmp, /swap should go to the normal HDD. Is it ok to put symlinks for these from the SSD to HDD or do I need separate partitions on the HDD for each of /home, /var, /tmp, /swap, etc.?
[19:06] <lordievader> DaHoC: Make the folders on the ssd and set the mount point of those partitions (that reside on the HDD) to those folders.
[19:08] <DaHoC> lordievader: Thanks, I did not find this in any tutorial but this seems logical to me. To be certain, write operations to e.g. /home then would affect only the normal HDD and not the SSD?
[19:08]  * BluesKaj_ wonders why so many partitions
[19:08] <DaHoC> BluesKaj_: How else to go about it? I only see these 2 options?
[19:09] <lordievader> DaHoC: Jup. Perhaps you should read up on partitions/mounting.
[19:10] <lordievader> DaHoC: BluesKaj_ is right though, you don't need a separate partition for all those folders. Unless you want a really specific setup ;)
[19:10] <DaHoC> lordievader: Ok, how to do it in detail is pretty clear to me.. I just wanted to make sure I have the correct understanding because I did not find it in any tutorial. How can I use a single partition for all these folders then?
[19:11] <lordievader> DaHoC: You can suffice with one partition /. However I can understand that you only want some of the system on the SSD and the rest on the HDD.
[19:13] <DaHoC> lordievader: Yes I agree, I read that it is suggested to put write-intensive paths (like /tmp, /var, /home) out of the SSD and onto the HDD.
[19:13] <lordievader> DaHoC: I can understand that. Then you do have to make multiple partitions.
[19:14] <DaHoC> Why does the symlinks approach not work then? It would avoid write operations on the SSD as well, right?
[19:19] <BluesKaj_> writing to ssds isn't as damaging as rumors say, most new ssds are very resilient now
[19:22] <DaHoC> BluesKaj_: lordievader: So you basically suggest installing the whole Linux onto the SSD?
[19:24] <BluesKaj_> DaHoC, the / on the ssd and /home and swap on the hdd, perhaps ...what do you think lordievader?
[19:29] <DaHoC> BluesKaj_, lordievader: Thank you, that is also an easy way/compromise without many partitions :-)
[19:30] <BluesKaj_> DaHoC, yes one of the knowledgable guys over at #linux suggested that arrangement as well
[19:31] <BluesKaj_> makes for a faster pc apparently, DaHoC
[19:31] <DaHoC> BluesKaj_: ok, thanks :-)
[19:34] <Guest24243> hi
[19:34] <BluesKaj_> hi
[19:35] <Guest24243> i just installed kubuntu on this acer aspire v3 111p, but when rebooting, it tells me there is no bootable device
[19:35] <Guest24243> missing grub install_
[19:36] <Guest24243> that should have been a question mark, i suffer form english keyboard layout by mistake...
[19:37] <BluesKaj_> Guest24243, did you install in UEFI mode ?
[19:37] <lordievader> DaHoC: I'd put /tmp also on the hdd or even better in a tmpfs.
[19:37] <Guest24243> BluesKaj_: i don't know, the device is running in uefi mode,but the installer didn't tell me as far as I noticed
[19:38] <Guest24243> i'm running in the live iso right now
[19:39] <BluesKaj_> ok , try sudo grub-install /dev/sda
[19:39] <Guest24243> i don't know the root password
[19:40] <BluesKaj_> it doesn't matter from the live cd
[19:41] <BluesKaj_> assuming the mbr or equivalent  is on sda of course
[19:41] <Guest24243> grub-install: error: failed to get canonical path of `/cow'
[19:41] <BluesKaj_> damn gpt
[19:43] <BluesKaj_> are you dual booting windows and kubuntu ?
[19:43] <BluesKaj_> Guest24243, ^
[19:43] <Guest24243> BluesKaj_: i try my best to wipe widows
[19:44] <Guest24243> windows, and i can not make smileys using english keyboard...
[19:44] <BluesKaj_> Guest24243, use gparted live-media, it's the best for cleaning out windows partitions
[19:46] <Guest24243> BluesKaj_: i deleted the windows filesystem, and created a 64G partition for / and the rest for /home
[19:46] <Guest24243> maybe it is just missing a boot flag
[19:47] <BluesKaj_> Guest24243, 64G for / is a bit large, 16G is plenty
[19:48] <BluesKaj_> also 1.5x your RAM for a swap aprtition if you have under 4GRAM
[19:48] <BluesKaj_> swap partition that is
[19:49] <Guest24243> i made a 8g swap, which should be plenty
[19:49] <Guest24243> 4g ram
[19:49] <Guest24243> maybe i should start over...
[19:49] <BluesKaj_> Guest24243, yup, that's fine if you can spare the space
[19:49] <Guest24243> fdisk tells me sda have only /sda1, but in dolphin, there is both partitions
[19:50] <Guest24243> iwould mostly like to make the whole thing boot!
[19:51] <BluesKaj_> yes fdisk only gives numbered partitions
[19:51] <lordievader> Guest24243: Gpt disk?
[19:51] <Guest24243> gparted does not appear to be intstalled
[19:52] <Guest24243> how can i know?
[19:52] <Guest24243> i used the "manual" option of the installer
[19:53] <BluesKaj_> gparted is a small OS that is burned to a cd or created on usb
[19:53] <lordievader> Guest24243: fdisk doesn't support gpt, that could explain why you only see one partition. gdisk is a version of fdisk with gpt support.
[19:53] <Guest24243> i try gdisk :)
[19:53] <lordievader> BluesKaj_: What?
[19:53] <Guest24243> gdisk sees all my partitions
[19:53] <lordievader> BluesKaj_: gparted is a gui around parted.
[19:55] <BluesKaj_> it runs as a live cd OS tho with terminal access etc
[19:55] <BluesKaj_> lordievader,^
[19:55] <Guest24243> how to install grub?
[19:55] <lordievader> BluesKaj_: You are talking about the gparted live cd http://gparted.org/livecd.php
[19:55] <BluesKaj_> Guest24243, ubiquity will install grub when you install kubuntu
[19:56] <lordievader> Guest24243: "sudo grub-install /dev/<hard-disk-in-question>" didn't work?
[19:56] <BluesKaj_> yes , lordievader , that's what I suggested to Guest24243 earlier
[19:56] <Guest24243> BluesKaj_: appearently id didn't, but maybe i just have to retry...
[19:57] <Guest24243> lordievader: nope, it complains about "not being able to get cannonical path of /cow"
[19:57] <TheFakeazneD525> lordievader: but why not KDE Partitionmangler tho
[19:57] <lordievader> Guest24243: Make  sure you have /boot mounted and point the grub installer to that directory.
[19:57] <BluesKaj_> Guest24243, have you repartitoned the installation ?
[19:57] <Guest24243> no
[19:57] <BluesKaj_> ok
[19:58] <Guest24243> the installer seemed to want to make one big partition. I want / to be on a different partition than /home, to be able to reinstall properly
[19:58] <lordievader> Guest24243: You could chroot into your install and install grub from there.
[19:59] <Guest24243> where in the process does the kubuntu installer install grub? it appearently halted after asking me to reboot - maybe i should have been patient at that point?
[20:00] <BluesKaj_> usually right at the finish
[20:00] <Guest24243> ok, thanks a lot - i will just redo the install and make / a bit smaller :)
[20:02] <BluesKaj_> best to prepartition your drive with gparted before installing then use manual partitioning to set the mountpoints for / and /home \
[20:02] <BluesKaj_> during the install procedure
[20:03] <lordievader> BluesKaj_: What's wrong with the partitioner on the live-cd?
[20:03] <TheFakeazneD525> ^
[20:03] <TheFakeazneD525> KDE Partition Manager exists :c
[20:03] <TheFakeazneD525> why not that
[20:03] <BluesKaj_> not as many options
[20:04] <lordievader> BluesKaj_: Options such as? (I agree it isn't as flexible as I'd like to see, but for basic things it does the job)
[20:04] <BluesKaj_> setting the / and /home sizes and the mountpoints
[20:05] <BluesKaj_> but I must admit I haven't used ubiquity to partition any drives in many yrs
[20:06] <Guest24243> it seemed to work fine, my only problem appears to be that grub is not installed
[20:06] <lordievader> BluesKaj_: As long as you don't want encryption/lvm it is quite capable of doing those things.
[20:06] <Guest24243> i just retry :-)
[20:07] <Guest24243> i'll come back in a while, hopefully from an installed system :)
[20:08] <BluesKaj_> lordievader, I always preferred to use gparted before installing an OS, found it easier that's all
[20:09] <lordievader> BluesKaj_: Ofcourse your choice, was just wondering why you recommended gparted over the live-cd partitioner.
[20:11] <BluesKaj_> lordievader, maybe ubiquity is better at partitioning than it used to be
[20:37] <andersl> hello again
[20:37] <andersl> i still can not get a working install
[20:37] <andersl> no bootable device
[20:38] <andersl> can the live iso be used to start a os on the system?
[20:39] <andersl> i was guest<some number> before
[20:41] <andersl> no konqueror package?! :$
[20:42] <lordievader> andersl: Same error when installing grub?
[20:47] <andersl> lordievader: i read, and find the --boot-directory option to grub-install... :)
[20:47] <andersl> i get errors
[20:48] <lordievader> andersl: Okay, I get the feeling that will not solve your problems... actually.
[20:48] <lordievader> andersl: The same or different?
[20:48] <andersl> grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
[20:48] <lordievader> andersl: Ah, that is usefull. The first partition should be a BIOS boot partition.
[20:48] <andersl> grub-install: warning: Embedding is not possible.  GRUB can only be installed in this setup by using blocklists.  However, blocklists are UNRELIABLE and their use is discouraged..
[20:48] <andersl> grub-install: error
[20:49] <andersl> so i need to reinstall AGAIN???
[20:49] <andersl> your installer is no fun:\
[20:49] <TJ-> andersl: Is the system UEFI? If so, it's started in CSM legacy mode and therefore 'grub-pc' needs a ~ 1MB partition to install core.img to
[20:50] <lordievader> andersl: https://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=4#doc_chap3 explains how to make a bios partition.
[20:50] <andersl> TJ-: the system is uefi, but i do not understand the rest
[20:50] <TJ-> andersl: The installers will boot in UEFI *or* Legacy BIOS mode, and that decision is made by the motherboard firmware and you, the user, selecting the boot method via the boot device menu, usually
[20:51] <andersl> the system is in uefi mode, i expected the installer to handle that gracefully
[20:52] <andersl> is it possible to install kubuntu on uefi system?
[20:52] <TJ-> andersl: Some mobo UEFI firmware makes it difficult to differentiate the UEFI and Legacy boot options - usually there will be 2 almost identical entries for the boot device in the boot menu, one for UEFI and the other for Legacy. There is no standard naming to help users though, so you have to try it and see, sometimes
[20:52] <andersl> it is very easy to see here, there is "uefi" or "legacy"
[20:53] <andersl> but the installer appearently fails to ensure this is done correctly
[20:54] <TJ-> andersl: E.g. I've had something clear like "UEFI: USB mass storage" and "BIOS: USB mass storage" but I've also had "USB Mass Storage" and "IDE USB mass storage" - the latter indicating BIOS/Legacy mode boot
[20:54] <andersl> TJ-: you had those where?
[20:54] <TJ-> andersl: It isn't the installers job - it can only work with the mode the motherboard firmware starts the system in
[20:55] <TJ-> andersl: In the UEFI boot device menu of 2 different systems; the first was easy to understand, the second was try-it-and-see
[20:55] <andersl> ... which is uefi.secure boot is of. but how do i get a system that can boot?
[20:55] <andersl> it seems to be the partition table? Do I need to manually create a partition for grub?
[20:55] <TJ-> andersl: If the system starts in UEFI mode the installer will know and will use "grub-efi" package to install the grubx64.efi EFI boot loader into the EFI system partition
[20:56] <andersl> then why doesn't my system boot?
[20:56] <TJ-> andersl: But when the system is started in Legacy/BIOS mode the installer will have to use "grub-pc" which can only install the Legacy BIOS boot code (MBR sector + core.img in a boot-partition for GPT)
[20:57] <andersl> i am in uefi mode
[20:57] <TJ-> andersl: What device are you installing from? USB or DVD?
[20:57] <andersl> usb
[20:57] <TJ-> andersl: OK. When the system starts you can press a key to get a boot device menu, yes?
[20:58] <andersl> TJ-: yes
[21:00] <TJ-> andersl: If the USB device is bootable in both UEFI and BIOS modes, that device should have 2 entries in the boot device menu. I've found sometimes I need to cause the menu to scroll down to find other modes  (and that no scroll-bar is displayed to indicate there are other boot options off-screen)
[21:01] <andersl> TJ-: and?
[21:02] <TJ-> andersl: So, to ensure the OS starts in UEFI mode the correct one of the two boot options is required, and as I said, it's not possible to know ahead of time how the firmware will describe the modes in the menu.
[21:03] <TJ-> andersl: Here's an illustrated guide, in case it helps makes the process clearer: https://iam.tj/kb/pc/boot/
[21:05] <andersl> appearently, the special grub partition is missing from my harddisk
[21:05] <andersl> is therea way to create that?
[21:05] <TJ-> andersl: You're happy for the system to boot in Legacy/BIOS mode?
[21:06] <TJ-> andersl: I thought from what you said earlier you wanted it to boot in UEFI mode
[21:07] <andersl> i do, are those mutually exclusive?
[21:10] <TJ-> andersl: You'll need to ensure the Live ISO/Installer boots in UEFI mode and repair the installed system by removing "grub-pc" and installing "grub-efi"
[21:11] <TJ-> andersl: Or else reinstall after ensuring the system boots the installer in UEFI mode
[21:11] <andersl> i have to reboot it and check the boot menu?
[21:12] <TJ-> andersl: The system boot device menu, yes .. or you could disable CSM Legacy mode in the firmware setup screens so it *can't* start the OS in Legacy mode.
[21:17] <andersl> appearently, my usb stick is NOT booted in uefi mode. But I do NOT understand why. The BIOS is in uefi mode.
[21:17] <andersl> is there another functional way to install kubuntu?
[21:18] <TJ-> andersl: Hmmm, I'm about to try and reproduce your scenario here. How did you write the ISO to the USB mass storage device?
[21:18] <andersl> TJ-: using something odd imagewriter on windows xp. maybe i should download it here and use dd...
[21:19] <andersl> in the meantime, can I install digikam in the live image and use it? I have some images to deliver...
[21:20] <TJ-> andersl: You could; or if you can wait until my Kubuntu ISO download is done, I can confirm it *should* work for you before you tear your hair out :)
[21:20] <TJ-> andersl: provided there's enough RAM, yes
[21:20] <andersl> TJ-: I'll wait, while trying digikam
[21:21] <andersl>  if it is not getting too late, i feel stressed and sad
[21:22] <TJ-> andersl: I can imagine; many system and motherboard manufacturers have made rather a mess of their UEFI deployments, we see this kind of issue very frequently.
[21:23] <TJ-> andersl: It was the rush to ensure they could use the "Certified for Windows 8" Microsoft marketing materials
[21:24] <andersl> TJ-: several users have reported installing ubuntu and mint linux on this device without problems.
[21:24] <andersl> it is sold with linux on it in germany
[21:25] <TJ-> andersl: Well I am assuming the Kubuntu installer is using the same base as the Ubuntu one, therefore it should be able to boot in UEFI or BIOS mode. I'll test it in a VM in a few moments, just got to brew some tea
[21:27] <andersl> TJ-: highly appreciated!:)
[21:35] <TJ-> andersl: Kubuntu ISO will boot in UEFI mode, if the system starts it in that mode
[21:36] <TJ-> andersl: It'll first show a regular GRUB menu with "Start Ubuntu", "OEM install (for manufacturers)", and "Check disk for defects"
[21:37] <andersl> TJ-: I have that menu as well
[21:38] <TJ-> andersl: This one? https://iam.tj/projects/misc/kubuntu-ISO-uefi-boot.png
[21:38] <andersl> my only problem is that after the install, does not boot, system says "no bootable device"
[21:38] <andersl> exactly
[21:40] <andersl> i do not know when I will find time to fight this again...
[21:40] <TJ-> andersl: OK., well that's good. Does the disk it is installed to contain data that has to be kept, or is the installer able to over-write the disk?
[21:41] <andersl> so far, the installer overwrites the disk. I
[21:41] <andersl> 'm downloading images to a usb hdd...
[21:41] <TJ-> andersl: OK, so it will do two very important things: 1) create a GUID Partition Table, and in that a FAT32 EFI System Partition
[21:43] <andersl> TJ-: how can i see if that has happened?
[21:44] <TJ-> andersl: It'll also install the "grub-efi" package, which will be used to install the GRUB EFI boot loader in the EFI SP - the reference you made much earlier about GRUB complaining about a missing BIOS boot partition only occurs if the system is in BIOS mode -
[21:44] <TJ-> andersl: I'm doing a test install into a VM image now just to be sure it happens as it should
[21:44] <andersl> i don't appear to have a grub-efi command
[21:45] <TJ-> andersl: No, it's not a command  - it is a package that is installed which contains the correct dependencies to have all the correct EFI tools instead of BIOS tools
[21:48] <andersl> i think the EFI partition is missing here
[21:48] <andersl> maybe it should be created by hand if I use manual partitioning?
[21:48] <TJ-> andersl: "gdisk -l /dev/sda" will list GPT of  a device
[21:48] <TJ-> andersl: Yes, it should
[21:48] <TJ-> andersl: Did you use manual partitioning?
[21:49] <andersl> there is my mistake then
[21:49] <andersl> yes, because the auto just would create one huge partition
[21:49] <andersl> I need /home to be separate, to feel safe :)
[21:50] <TJ-> andersl: It'd actually create 2: the ESP and another .... I'd recommend using LVM though, since you can then (re)allocate space in the volume group and use multiple Logical Volumes, for things like /home/, /var/, and whatever else you need
[21:51] <andersl> guided LVMmode in the installer?
[21:51] <TJ-> andersl: ha! installer ran out of memory in the VM - I gave it 1GB, should have been enough !
[21:51] <andersl> :\
[21:51] <TJ-> andersl: I'd hope it's intelligent enough but it might need Manual override :)
[21:52] <andersl> i try that next time , likely tomorrow - I need to make a few photos, and then go to bed...
[21:54] <TJ-> I'll test it in the VM, if I find anything unexpected I'll leave you a Memo on here
[21:54] <andersl> thanks :)
[21:55] <TJ-> andersl: I'm trying the "Guided - use entire disk and set up LVM"
[21:55] <andersl> that is what Ithought I'd do
[21:57] <TJ-> andersl: I started it from the "Try Kubuntu" desktop so that when the installer is finished I can use the live environment to check it, and to reassign space in the VG to add a /home/ LV
[21:57] <andersl> i installed from the live system last time
[21:58] <TJ-> andersl: That would make it impossible to change the VG allocation before the reboot. I'd recommend the "Try Kubuntu" approach
[22:40] <andersl> guided whole disk + LVM just creates one giga partition :\
[22:52] <TJ-> andersl: funny you should pop up - I've just completed the guide of how to create the /home/ :  http://iam.tj/projects/misc/kubuntu-installer-LVM-separate-home.sh
[22:54] <andersl> hm, i try manually again, without lvm. Next time, maybe.
[22:54] <andersl> Do you know if I can find a konqueror package for kubuntu somewhere?
[22:55] <TJ-> andersl: It's simple to shrink the root file-system so you can add an LV for /home/
[22:55] <andersl> but why?
[22:59] <TJ-> andersl: Because as I said earlier, the Guided install allocates the entire disk to the root file-system.
[22:59] <andersl> Ok, I can appreciate that :)
[23:00] <TJ-> andersl: The alternative is to do it all through manual partitioning, of course, but its easy to miss a step that way
[23:01] <andersl> I hope i didnt miss a step this time...
[23:01] <TJ-> andersl: The script I wrote is the exact commands; with comments for each step. Use it as a check on what you want to do
[23:04] <andersl> i try to find a way to save it to a safe place...
[23:04] <TJ-> andersl: I won't remove it from my server, so you can always return to it
[23:11] <andersl> so, now I am in the installed system :-))
[23:12] <andersl> adding the EFI partition was the missing thing'
[23:23] <andersl> I appear to be running kde 4.13.3 or so, is there a way to get 4.14 without ending up in a package hell?
[23:24] <valorie> andersl: http://www.kubuntu.org/news/kde-sc-4.14
[23:24] <valorie> that is a devel provided PPA and very reliable in my experience
[23:27] <valorie> I'm using 4.14 without incident
[23:48] <andersl> valorie: thanks :) will adding this mean an update will be offered on my system?
[23:48] <TheFakeazneD525> andersl: yeah
[23:48] <TheFakeazneD525> run apt-get update and then run an upgrade
[23:48] <TheFakeazneD525> I like muon update manager :)
[23:50] <andersl> ok, thanks
[23:50] <andersl> tomorrow, i have to get some sleep. You have been very helpful in her! :)
[23:52] <valorie> andersl: that's why we're here!
[23:54] <TheFakeazneD525> valorie: so are we backed fully by Blue Sys, or partially by both Canonical and Blue?