[00:13] <mparillo> frenda: For me (on Wily) simply right-click on your Application Launcher (the K) and select Alternatives.
[00:18] <Aniar> hi. I have a weird problem I can't figure out - I just fresh-built Kubuntu 15.04 on an SSD on a Thinkpad.  Every time I reboot /usr/sbin/bluetoothd is 0644. I "chmod +x /usr/sbin/bluetooth && systemctl start bluetooth" and BT works. but next reboot, it's back to 644.  /home is NOT mounted separately, and I'm not losing any data there, so this is specific, as far as I can see, to /usr/sbin/bluetoothd. anyone seen anything like thi
[07:33] <lordievader> Good morning.
[07:39] <Hari_> Hai, I need some help about installing Kubuntu 15.04
[07:39] <lordievader> At what point do you get stuck?
[07:42] <Hari__> The installer crashes when I come to the keyboard setup screen
[07:43] <Hari__> I think it is a problem of the installer. Is there anyway I can bypass the default installation route?
[07:44] <lordievader> Does it crash with some kind of a traceback?
[07:44] <Hari__> traceback means?
[07:44] <lordievader> Error message of where in the code things went wrong.
[07:45] <Hari__> Yeah...
[07:45] <lordievader> Could you pastebin that by any chance?
[07:45] <Hari__> I don't have it with me now, but I'll get it.
[07:46] <Hari__> Is there anyway to bypass that keyboard selection screen manually?
[07:46] <lordievader> I'm not sure.
[07:47] <Hari__> Ah OK
[07:47] <lordievader> As a work around you could take the mini iso, that has a text based installer.
[07:49] <Hari__> What is that mini iso?
[07:49] <Hari__> Where can I get it?
[07:50] <lordievader> https://help.ubuntu.com/community/Installation/MinimalCD
[07:53] <Hari_> I just did a search and it seems there isn't any mini installer for kubuntu
[07:55] <lordievader> Hari_: All flavors have the same minimal iso. During the installation you select which de you want.
[07:55] <Hari_> Ah thanks:)
[07:56] <Hari_> I'll do it then.
[08:26] <ejay> hi all
[08:37] <lordievader> o/
[09:24] <alvin> The mini installer still exists? I didn't know that? Does it have the same installer as the old 'alternate installer' which could do more?
[09:30] <lordievader> Ubiquity has caught up quite a bit. I think they are now at the same level of functionality.
[09:31] <Haali_Kubuntu_15> kubu15, persistent random marquee selection on desktop. Any fix?
[09:32] <Haali_Kubuntu_15> here is a pic https://drive.google.com/file/d/0B6ITlt_K4rvlSUJHOWZ6YlFNanM/view?usp=sharing
[11:39] <BluesKaj> Hiyas all
[13:05] <alvin> Do I need extra packages in order to get krdc to connect to a VNC server?
[13:24] <madmouser1> alvin: should not just make sure the VNC plugin is not disabled by accident
[13:29] <kalib> Hello guys, after my last upgrade my kde/plasma5 is kind of broken.. Can I restore it to the defautl configs? I mean, perhaps rm -rf .config/kde*, rm -rf .config/plasma*, rm -rf /.local/share/kde*, rm -rf .local/share/plasma* ?
[13:32] <soee> kalib: i think there are also some settings related to configuration directly inside .config
[13:32] <kalib> soee: so, what do you suggest to completely restore my kde/plasma 5?
[13:34] <alvin> madmouser1: Thanks, but it is enabled. I'll need to dig into this. Might be the server too.
[13:36] <soee> https://plus.google.com/+AndreaDelSarto88/posts/dbn6VWiQLJ7 :)
[15:11] <macvez> Haven't been on IRC since 2001
[15:11] <macvez> Anyone alive in here?
[15:15] <Pici> yes.
[16:35] <FirstTimeUser> hello
[16:35] <FirstTimeUser> i need some help with kubuntu.... i just uinstalled it
[16:35]  * FirstTimeUser slaps boubbin around a bit with a large fishbot
[17:14] <blah-> which one is better, kubuntu or xubuntu?
[17:15] <BluesKaj> blah-, it's a matter of taste, mostly
[17:16] <BluesKaj> never tried Xubuntu so i can't judge anyway
[17:16] <blah-> i'm installing kubuntu now :)
[17:17] <BluesKaj> !xubuntu
[17:23] <blah-> !kubuntu
[17:25] <blah-> !ubuntu
[17:25] <genii> Hehe GNOME
[17:26] <blah-> nice
[17:26] <genii> !lubuntu
[17:27] <blah-> :)
[18:02] <ik_> hi
[19:56] <adroit_machine> how do I add downloaded packages in muon discover?
[20:08] <aaa__> s.a
[20:58] <Copernicus22> acpi pcc probe failed    after upgrade to ubuntu 15.04 :(
[20:59] <Copernicus22> been googling, not much luck :sss
[21:00] <TJ-> Copernicus22: don't worry about it; it's just a verbose debug message left in by mistake
[21:00] <Copernicus22> I get a busybox
[21:00] <Copernicus22> can't boot
[21:01] <TJ-> Copernicus22: unrelated to ACPI PCC probe
[21:01] <Copernicus22>  /dev/disk/by-id/.... does not exist
[21:03] <TJ-> Copernicus22: That sounds like a systemd-init not finding one of the file-systems required to boot the system
[21:03] <TJ-> Probably the root FS. Does the system use LUKS/dm-crypt full disk encryption?
[21:04] <Copernicus22> its not encrypted
[21:04] <TJ-> Copernicus22: that makes things simpler.
[21:04] <Copernicus22> I can't see the partitions
[21:04] <Copernicus22> it's a striped raid disk
[21:04] <TJ-> what does "cat /proc/cmdline" show as the root=
[21:05] <TJ-> How many disks in the RAID array? is it just RAID-0 ?
[21:05] <Copernicus22> can't run commands
[21:05] <Copernicus22> 2 disks in raid 0
[21:05] <TJ-> I thought you had the busybox prompt?
[21:05] <Copernicus22> I booted from a livedisk I mean
[21:06] <Copernicus22> at the moment
[21:06] <TJ-> Copernicus22: Ahhh!
[21:06] <TJ-> Have you chroot mounted the broken config ?
[21:07] <Copernicus22> not yet, I'll have to google how to do that
[21:07] <Copernicus22> what do I google for?
[21:07] <Copernicus22> I did it once before but it's like 10 years ago :)
[21:08] <TJ-> First thing to do is check the live dmesg/kern.log to see if there are any I/O errors reported from those disks. RAID-0 is not particularly safe. A minor failure on one drive and the entire RAID device / file-system is gone
[21:09] <TJ-> Next thing is is to "sudo apt-get install smartmontools" and run "sudo smartctl --all /dev/sdX" to check the health of each device
[21:09] <Copernicus22> I was able to use a disk recovery tool from windows to backup my home dir
[21:10] <TJ-> If one device is failing the array likely won't be able to assemble
[21:11] <Copernicus22> yeah it seems that way
[21:11] <Copernicus22> strange that the diskrecovery tool still could read most of the files though
[21:12] <Copernicus22> at least it seamed that way
[21:13] <TJ-> With 2 disks I'd always prefer RAID-1 mirror.
[21:14] <Copernicus22> no errors logged
[21:18] <Copernicus22> TJ-: http://pastebin.com/nbxF6ig4
[21:18] <Copernicus22> brb
[21:20] <Copernicus22> b
[21:21] <TJ-> Copernicus22: that's good news. Maybe it is simply that the initrd.img didn't get correctly configured with the mdadm RAID config
[21:22] <Copernicus22> TJ-: mdadm ?
[21:22] <Copernicus22> initrd.img?
[21:23] <TJ-> mdadm is the multiple disk admin
[21:23] <Copernicus22> ok
[21:23] <TJ-> initrd.img == initial ramdisk (where the root file-system is found and mounted,and busybox shell lives)
[21:24] <Copernicus22> maybe I should follow this guide?
[21:25] <Copernicus22> http://feeding.cloud.geek.nz/posts/setting-up-raid-on-existing/
[21:25] <Copernicus22> TJ-: oh no not exactly
[21:26] <Copernicus22> it has the tools I need though :)
[21:26] <Copernicus22> right?
[21:26] <TJ-> Your issue may simply be the MD device for root-file-system has the wrong name (sometimes what installs as /dev/md0 becomes /dev/md127 on reboot
[21:28] <TJ-> It depends on which metadata version is used by mdadm on the disks. Nowadays it is supposed to be v1.2, but if it's v0.9 for example the device ID would need to be configured in the mdadm.conf which is copied to the initrd.img by update-initramfs
[21:29] <Copernicus22> TJ-: can you give me some pointers to learn how to do all this from a live cd?
[21:30] <Copernicus22> or busybox
[21:30] <Copernicus22> it's not really clear what you are saying in your last 2 lines
[21:32] <Copernicus22> all quite new to me :)
[21:32] <TJ-> Copernicus22: Well, the issues are quite complex. Why did you use RAID-0 if you're not familiar with managing it?
[21:32] <Copernicus22> TJ-: It's really fast :)
[21:32] <Copernicus22> 500mb/sec
[21:33]  * Vito blames raid 0
[21:33] <Vito> ssd + no swap (or -> 0 swapiness) are better
[21:33] <TJ-> Yeah... it fails faster too
[21:33] <Copernicus22> I'm going to implement and test a good backup system :)
[21:34] <Copernicus22> after I fix this
[21:34] <Vito> raid 10 is better then
[21:35] <Copernicus22> Vito: hmmz, I'll look in to it
[21:35] <Vito> everything depends on your budget
[21:36] <Copernicus22> it's a laptop
[21:36] <Vito> ssd then
[21:36] <Copernicus22> yes
[21:36] <Vito> ssd for os, no swap and an hdd into the second slot
[21:36] <Copernicus22> no space for another hard disk
[21:36] <Vito> for /home
[21:36] <Copernicus22> I've got 2 ssd's and a hdd
[21:38] <Copernicus22> I never knew it was such a risk
[21:38] <Copernicus22> raid 0
[21:38] <Vito> raird 0 is by definition :'D
[21:38] <Vito> -r
[21:38] <Copernicus22> :)
[21:39] <Copernicus22> apparently
[21:39] <Vito> it also depends on the disks
[21:40] <Copernicus22> why can't i see the partitions using the livecd?
[21:40] <Vito> using two disks with a significantly long mtbf could bring overall mtbf to a single average disk's one
[21:40] <Copernicus22> I tried a couple partition tools
[21:41] <Vito> I have a very few experience with raid 0 for reasons above, sorry :(
[21:44] <Copernicus22> ok I'll try again tomorrow, thx anyways
[21:44] <Copernicus22> gnite
[21:44] <Vito> maybe a software raid needs some package like mdadm
[21:44] <Vito> (software raid is also evil)
[21:45] <Copernicus22> sudo mdadm --assemble --scan
[21:46] <Copernicus22> should show me the partitions?
[21:46] <Copernicus22> http://askubuntu.com/questions/15933/how-to-access-md-raid-via-live-cd
[21:46] <TJ-> Copernicus22: there may be no partitions
[21:47] <Copernicus22> yeah
[21:50] <Copernicus22> TJ-: http://pastebin.com/1qYxxAvD
[21:50] <Copernicus22> State : active failed
[21:51] <Copernicus22> TJ-: do you know what this means?
[21:51] <TJ-> Copernicus22: Ahhh, so it is Fake-RAID rather than Software-RAID, as in the metadata is set by the controller
[21:52] <TJ-> Copernicus22: " Slots : [_U]" suggests you need to enter the BIOS RAID setup and try to fix it from there. the "_" suggests a mising array member
[21:54] <Vito> --force option could work also
[21:56] <Copernicus22> I checked, doesnt miss a member
[21:56] <Copernicus22> Vito, force?
[21:56] <TJ-> "Disk00 Serial : P02430111202" is "active failed" so something has gone wrong somewhere
[21:57] <TJ-> Copernicus22: does the kernel command-line include "nomdmonddf nomdmonisw" ?
[21:58] <Copernicus22> the uuid doesnt match my grub.conf
[21:58] <Vito> https://raid.wiki.kernel.org/index.php/RAID_Recovery#Trying_to_assemble_using_--force
[21:59] <Vito> but TJ- knows more than me so it's up to him now
[21:59] <Copernicus22> Vito: ok thx
[22:01] <Copernicus22> http://pastebin.com/ZCA25s2N
[22:01] <Copernicus22> I need to make a config file first it seems
[22:01] <Copernicus22> sudo mdadm --assemble --force /dev/md127
[22:01] <Copernicus22> mdadm: /dev/md127 not identified in config file.
[22:01] <TJ-> Copernicus22: the UUID if part of the RAID metadata; not the file-system for ROOT
[22:02] <TJ-> s/if part/is part/
[22:02] <Copernicus22> TJ-: ok
[22:03] <Copernicus22> anyways, I should really go to sleep now, thx again guys, see you tomorrow maybe
[22:04] <TJ-> Copernicus22: you could try "sudo mdadm --assemble /dev/md127 /dev/sda /dev/sdb"
[22:08] <Vito> forcing
[22:14] <Copernicus22> s
[22:14] <Copernicus22> udo mdadm --assemble /dev/md127 /dev/sda /dev/sdb --force
[22:14] <Copernicus22> mdadm: /dev/sda is busy - skipping
[22:14] <Copernicus22> mdadm: /dev/sdb is busy - skipping
[22:15] <TJ-> Sounds like it's already partitially in-use. check with "cat /proc/mdstat"
[22:15] <Copernicus22> TJ-: didn't work
[22:17] <Copernicus22> can I paste 9 lines here or pastebin ? :)
[22:17] <Copernicus22> http://pastebin.com/bjpxrjkz
[22:19] <TJ-> Copernicus22: how the heck!
[22:19] <TJ-> Copernicus22: if you can drop md126 I think it'd work :) It looks like somehow they array has split
[22:19] <Copernicus22> TJ-: hehe
[22:20] <Vito> .-.
[22:20] <Vito> repeat with me, "raid 0 is evil"
[22:20] <TJ-> "sudo mdadm --stop /dev/md126"
[22:20] <Copernicus22> haha
[22:35] <Copernicus22> blk_update_request: critical target error, dev sr0, sector 2563432
[22:37] <Copernicus22> dmesg
[22:37] <Copernicus22> ok really going to sleep now, cya :)
[22:39] <TJ-> sr0 is SCSI removable, e.g. DVD