[00:32] <__pp__> hi
[00:33] <__pp__> so, it looks like the latest systemd-services package broke my system...
[00:33] <__pp__> services are starting twice, some kernel modules won't start, and so on
[00:35] <__pp__> I'm guessing it's a problem in that package though... not that I know exactly were this comes from
[00:35] <__pp__> systemd-services:amd64 (204-0ubuntu11, 204-0ubuntu12)
[00:40] <__pp__> brb
[00:44] <snadge> oh lord.. ubuntu is going systemd? :(
[00:44] <snadge> id better read up about that :p
[00:45] <bekks> Thank god 12.04 is supported until 2017.
[00:46] <snadge> i think the wiki is out of date
[00:46] <snadge> its not mentioning any systemd by default thing anyway
[00:47] <snadge> it still says that its experimental and should be avoided like the plague
[00:47] <snadge> which is still accurate i guess
[00:53] <snadge> maybe the question should be more about whether debian is going to do it
[00:55] <pepee> <- __pp__ , forget everything I said, it was a misconfigured update that broke everything, apt fixed it all by itself :D
[03:29] <MichaelP> kubuntu 13.10 jokey keeps crashing.. how do i install the fglrx drivers ?
[07:17] <Kristall> Which 13.10 is considered the most stable, ubuntu/xubuntu/lubuntu/kubuntu(lol)
[09:46] <Xpp> hi
[09:50] <alankila> oh god, new ubuntu is tri-arch? I have libx32, lib64, lib
[12:21] <BluesKaj_> 'Morning folks
[12:57] <hellyeah> hey
[12:57] <hellyeah> should i ask question about 13.04 here
[12:57] <BluesKaj_> hellyeah, try #ubuntu
[12:57] <hellyeah> this is for 13.10
[12:57] <hellyeah> ?
[12:57] <hellyeah> ??
[12:58] <BluesKaj_> yes
[12:58] <hellyeah> hmm
[12:58] <hellyeah> how is 13.10 going?
[12:58] <hellyeah> you know 13.04 still have some problems
[12:59] <ikonia> hellyeah: do you need help with 13.04, yes/no?
[13:00] <BluesKaj_> hell 13.10 is coming along fine so far
[13:00] <BluesKaj_> hellyeah,^
[13:01] <hellyeah> i just wonder for 13.04 , ubuntu+1 is true place or not
[13:01] <hellyeah> i need some help
[13:01] <ikonia> hellyeah: you've already been told "no" #ubuntu+1 is for 13.10 and #ubuntu is for 13.04
[13:01] <BluesKaj_> did you read my post about ubuntu
[13:01] <hellyeah> BluesKaj_:  what post?
[13:02] <BluesKaj_> try #ubuntu
[13:02] <hellyeah> ha
[13:02] <hellyeah> okey
[13:03] <hellyeah> i supposed you have blog or something :D
[13:03] <hellyeah> i will try it
[13:03] <BluesKaj_> if you need help with 13.04 then ask in #ubuntu channel , that's the point here
[13:03] <hellyeah> what is the time of releasing 13.10?
[13:03] <hellyeah> got it man
[13:03] <BluesKaj_> read the topic for release datres'
[13:05] <hellyeah> what is the reason of releasing new version  in six months
[18:14] <alankila> Odd thing, the new kernel 3.11.0-8 didn't boot
[18:15] <alankila> It printed the UUIDs of the filesystems it found and the values didn't match blkid or grub opinion. I didn't change the filesystems even. They were the same, and -7 booted and -8 couldn't discover where that UUID was located
[18:15] <alankila> on btrfs, too. Not sure what changed. I was able to boot by going into grub menu and doing root=/dev/sda2 because that's where it is
[18:34] <penguin42> alankila: you could try using blkid to read the uuids
[18:40] <alankila> I did. They are the same as ever.
[18:40] <alankila> All worked in user space and grub, but the kernel was confused.
[18:41] <penguin42> ok, please file that - that really shouldn't happen