[03:03] <Tubby> !ops
[10:55] <alkisg> [   24.073489] Buffer I/O error on device zram0, logical block 384465
[10:55] <alkisg> ...is zram going to be enabled by default?!
[10:57] <alkisg> Meh it can't even be uninstalled properly...
[10:58]  * alkisg checks if the recent i915 crashes were because of zram...
[11:05] <alkisg> OK no the i915 hangs were due to the newest trusty kernel, not due to zram io errors
[11:05] <elfy> alkisg: not sure it's default for anything but lubuntu, but could be wrong
[11:06] <elfy> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1246664
[11:07] <alkisg> elfy: hmm then maybe ltsp pulled it, thanks. Although I still have the i/o errors on up-to-date trusty.
[11:07]  * alkisg just purged it though so no harm done
[11:08] <elfy> I don't know much about it to be honest, but I couldn't find anything more recent than a discussion in December 2012
[11:08] <alkisg> Ouch, yup, ltsp-client pulled it, I'll file a bug report
[11:09]  * alkisg thought we had lowered zram-config to plain suggests:... in ltsp...
[11:09] <elfy> :)
[11:20] <alkisg> Ah OK I forgot, we did that but didn't yet release a new LTSP version :) http://bazaar.launchpad.net/~vagrantc/ltsp/ltsp-debian-packaging/revision/1190
[11:25] <elfy> :)
[12:18] <BluesKaj> Howdy all
[12:18] <penguin42> Hey BK
[12:19] <BluesKaj> hi penguin42
[14:19] <penguin42> I wish they'd fix /boot filling up
[14:19]  * mamarley just puts /boot on the same partition as / unless he has a good reason not to.
[14:23] <BluesKaj> wth?
[14:26] <BluesKaj> thought /boot was no longer useful. A reasonably sized / plus /home partitions with attention to old dependencies with autoremove and autoclean keep / from filling up here
[14:27]  * mamarley just has one little FAT32 partition for /boot/efi and a big EXT4 partition for / and everything on it.
[14:28] <alkisg> Different OSes use the same /boot/grub dir, so one can't use a single /boot partition anyway
[14:28] <alkisg> *distros
[14:28] <penguin42> well I don't think I manually partitioned this machine; ah it's because I'm using LVM - so it created a /boot because it doesn't realise grub can do lvm
[14:28]  * alkisg has a purge-kernels script that removes all kernels...
[14:28] <alkisg> *old
[14:30] <BluesKaj> I keep 2 or 3 kernels, usually purge the older ones periodically
[14:31] <penguin42> yeh wth it doesn't do that automatically
[14:32] <elfy> why would it - I might want to keep 1, BluesKaj 2 and you 3 :)
[14:32] <Daekdroom> I thought it did that by default o.o
[14:32] <Daekdroom> I remember apt-get autoremove cleaning and leaving only 2 kernels in 13.10
[14:33] <Daekdroom> Not sure whose feature is that. Ubuntu or apt-get.
[14:33] <penguin42> hmm, something odd is going on here du -ms /boot - 81M - df is showing its 236M being full
[14:33] <BluesKaj> well 2 is usually enough
[14:33] <Daekdroom> I keep 2.
[14:33] <Daekdroom> But I'm not sure about how many I do in fact have installed.
[14:34] <alkisg>  The older headers are removed, the older images no
[14:34] <Daekdroom> Ah. Only 2. Although before the last kernel update I had only one.
[14:34] <alkisg> It'd be nice if it marked the autoinstalled ones, and removed all of them except for the last 2, and the manually installed ones
[14:39]  * alkisg is using vmlinuz-3.2.0-4-486 from debian as a fallback...
[14:40] <alkisg> ..and actually I've just booted with it because i915 crashes with the most recent trusty kernel :D
[14:40] <alkisg> It's also handy for non-pae / non-cmov clients
[14:49] <BluesKaj> alkisg,a hint , try the libgl1-mesa-dri-experimental module, seems to have solved the crashes here
[14:51] <BluesKaj> using the i915 as well of course, works on unity and kde btw
[15:21] <alkisg> Thanks for the hint BluesKaj
[15:23] <BluesKaj> alkisg, np ,let me know if it helps
[16:03] <ryaxnb> will ubuntu 14.04 ship with Nautilus 3.10?
[19:49] <BluesKaj> hmm, unity is one broken desktop...I can't use it on a large monitor, poor font and dpi options...guess it's meant for tablets and phones
[19:50] <bekks> Works fine here on large displays.
[19:50] <BluesKaj> well, if it does then the settings must be hidden somewhere out of sight
[19:56] <bekks> No chhanged settings, just installed the nvidia driver.
[19:57] <BluesKaj> I'm 3.5M away from a large screen plasma monitor ...my kde font settings etc are accessible and readable on kubuntu... if there are font settings other than larger in universal access then I'd like to know where to find them
[19:57] <BluesKaj> on unity
[19:58] <BluesKaj> yes i also installed the nvidia drivers
[19:58] <bekks> So which resolution does your plasma monitor have then?
[19:59] <BluesKaj> 1920x1080
[19:59] <bekks> And which size does that plasma monitor have?
[19:59] <BluesKaj> 46 inch
[20:00] <bekks> It's obvious that 1920x1080 on a 46inch will be somehow - large :)
[20:00] <BluesKaj> I have the dpi up to 120 on kde
[20:01] <BluesKaj> makes for somewhat clearer letters
[20:01] <bekks> Then get a calculator and see which resolution would be necessary to get 120dpi on a 46inch.
[20:01] <bekks> It will be larger than 1920x1080 by far.
[20:02] <BluesKaj> don't need a calc , works fine on kde , unity , not so much
[20:08] <BluesKaj> i realize it's an unusuial setup , but lots of ppl are using their desktops as home theater/media servers and I'm surprised that canonical doesn't seem to realize that ...Im sure the settings can be changed to be readable, but why so difficult to find
[20:31] <mamarley> BluesKaj: Just use KDE :)
[20:32] <penguin42> mamarley: Yep!
[20:32] <penguin42> (although the KDE plasma calculator is pretty grim)
[20:33]  * mamarley doesn't even use any plasma widgets.
[20:38] <BluesKaj> like I said , don't need a calc for kde
[20:40] <penguin42> it doesn't mean we won't give you one :-)
[20:40] <mamarley> It is better to have it and not need it than need it and not have it.
[20:43] <BluesKaj> penguin42, every once in a while I try ubuntu/unity on small hdd that I have connected via sata to the mobo for different distro testing , so to speak , and every time i try ubuntu again I'm reminded of it's lack of options and flexibility...guess that little drive have a new occupant soon :)
[20:43] <penguin42> nod
[20:43] <BluesKaj> will have
[20:43] <penguin42> BluesKaj: Yeh I never try unity any more
[20:43] <mamarley> Whenever I try any DE other than KDE, I am reminded of its lack of configuration and flexibility.
[20:43]  * BluesKaj nods as well
[20:45]  * penguin42 is hoping kde5 doesn't break that
[20:46] <mamarley> I don't think they will.
[20:47] <mcristo> Is anyone on 14.04 yet?
[20:47]  * mamarley is.
[20:47] <penguin42> nod
[20:47] <mcristo> Impressions so far?
[20:48] <mcristo> Still on 12.04 and curious
[20:48] <BluesKaj> mcristo, most users here probly are
[20:48] <mamarley> Besides the upstart-caused kernel panicking, it has been good.
[20:48] <mcristo> Thankyou - sry new to IRC
[20:49] <BluesKaj> sorry for what mcristo, you're doing fine
[20:50] <mcristo> What do you guys normally do here?
[20:53] <BluesKaj> mostly support users who have problems with "buntu-devel" releases
[20:53] <penguin42> mamarley: It's not upstarts fault to be fair, it's broken graphics drivers
[20:53] <mcristo> Gotcha.  Thanks!
[20:53] <mamarley> penguin42: Maybe that was something else.  Have a look at https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1269731.
[20:54] <mamarley> Upstart was crashing because of malformed .conf files.
[20:55] <penguin42> that's init not kernel
[20:56] <mamarley> penguin42: Yes, but if init segfaults, it causes a KP.
[20:57] <penguin42> shrug, not really - it's just telling you userland fowled up
[20:58] <penguin42> anyway, time to give up fighting zoneminder for today