[04:05] <slangasek> someone here have a recent system with an SSD and Intel video?
[04:05] <ScottK> Define recent?
[04:05] <ScottK> I have a Dell Mini 10v with SSD.
[04:06] <ScottK> slangasek: Act fast if you need something.  My pillow calls.
[04:07] <slangasek> ScottK: can you test lp:ubuntu/initramfs-tools?
[04:08] <ScottK> What do I need to do?
[04:08] <slangasek> download, build, install, echo FRAMEBUFFER=y > /etc/initramfs-tools/conf.d/framebuffer, update-initramfs -u, reboot
[04:09] <slangasek> confirm that you get the right splash screen and that X comes up after
[04:10] <ScottK> Sounds doable.
[04:12] <ScottK> It's been a bit since I messed with the sacrificial lamb, so 220 packages to update first.
[04:12] <slangasek> ok :)
[04:15] <slangasek> in theory this branch fixes cryptsetup+binary video drivers, but it does carry an increased risk of a race condition causing vesafb to be loaded instead of the free drm driver for some users... want to get an idea of whether that's really a problem in practice
[04:15] <slangasek> actually, come to think of it, this is all in the initramfs so SSD *shouldn't* make a difference at all
[04:15] <slangasek> but more data points are still welcome
[04:16] <ScottK> OK
[04:35] <ScottK> Seems fine.
[04:35] <ScottK> Rebooted a couple of times without issue.
[04:37] <slangasek> cool
[04:38] <slangasek> want to accept initramfs-tools from the queue then? :-)
[04:39] <slangasek> (if not, no worries)
[04:45] <ScottK> Done.
[04:47] <slangasek> cheers
[04:48]  * slangasek uploads an nvidia-graphics-drivers to go with that
[05:33] <Laibsch> Can somebody help me identify what fixed bug 460616 in natty?  I'd like to see if it's possible to backport this to lucid.  bryceh?
[05:35] <Laibsch> I had a look through the upstream ticket and upstream git, but was unable to precisely identify what fixed this
[06:19] <slangasek> cjwatson: writing it all down while it's fresh in my mind; would you care to cast an eye over https://wiki.ubuntu.com/BootGraphicsArchitecture ?
[09:06] <hrw> I am going to hate LP build failures. my packages (armel-cross-toolchain-base and armhf-cross-toolchain-base) both ftfbs on launchpad. but when I built them locally in pbuilder or in LP chroot they got built fine. arghhhhhh
[12:10] <marsfligth> Please, how to resume from 'hibernation' or 'suspend' status pressing the 'usb keyboard' instead of press the computer power button?
[14:29] <siretart> infinity: uploaded. if accepted, it'll need another upload of libav-extra (though that's in multiverse)
[14:41] <infinity> Hrm.  This would probably be easier to review if I unpack it and compare patched sources...
[14:56] <infinity> siretart: Go ahead with the -extra upload, this looks quite reasonable, letting it in.
[14:56] <infinity> The security team will thank you, I'm sure. :P
[20:02] <cjwatson> slangasek: I've corrected Q-FUNK's misconception in bug 864803, but he says that that misconception came from you, so I thought I'd check whether that was an accurate representation or whether he misunderstood something
[20:06] <slangasek> cjwatson: yes, I know it was an imprecise statement but we're doing =keep by default so it seemed negligible
[20:07] <slangasek> cjwatson: speaking of my misconceptions though, any thoughts on https://wiki.ubuntu.com/BootGraphicsArchitecture ?
[20:10] <stgraber> slangasek: btw, reading through that wiki page reminded me of an issue I notice on that box I just reinstalled with Oneiric server. At boot time I get stuck on vt7 so I have to manually switch to vt1 to have a login screen. Any idea where that bug would be coming from? (I'd expect "something" to do a chvt 1)
[20:12] <cjwatson> slangasek: yeah, have started looking at it but won't have a full review for you until tomorrow
[20:12] <cjwatson> slangasek: some of the statements about GRUB are a bit inaccurate - how much do you care about when such and such a feature was introducd?
[20:13] <cjwatson> I'm pretty certain that gfxmode=auto was introduced well after gfxpayload=keep
[20:30] <slangasek> cjwatson: I care that we not include false statements, but probably can't be bothered to track down when the features were *actually* introduced where it's wrong.  So we can just omit the references to the timeline :)
[20:32] <slangasek> stgraber: I guess plymouth-stop.conf should handle the vt switch?
[20:32] <slangasek> how was this handled previously?  did it stop working when we started using vt.handoff=7?
[20:35] <slangasek> cjwatson: when I wrote that, I was thinking in terms of when features entered into the default usage in Ubuntu, btw, rather than when they became available upstream; not that this necessarily means I'm any more accurate
[20:36] <stgraber> slangasek: I don't remember seeing that pre-Oneiric but I'm going to do a minimal install of natty and oneiric in a VM to make sure.
[21:08] <bookpage> can i connect vnc output to the $DISPLAY var in ubuntu?
[21:30] <cjwatson> slangasek: can't quite remember; gfxpayload=keep was on and off for a while; I wrote gfxmode=auto support so that it would be easier to consistently make gfxpayload=keep the default and get a consistent video mode
[21:31] <cjwatson> or rather I wrote the VBE mode detection for gfxmode=auto
[21:49] <stgraber> slangasek: reproduced the missing vt switch on natty too (netinstalled so it may have been introduced in an SRU)
[22:33] <infinity> A shiny nickel to the first person who proposed a clean, regression-free, and vaguely elegant way to make cron.daily not run for a day after installation, so new user experience isn't horribly awful within the first 5 seconds. :P
[22:39] <micahg> infinity: is install time recorded anywhere?
[22:40] <lifeless> micahg: yes
[22:40] <nigelb> That's probably the least dirty solution.
[22:41] <nigelb> I was dreaming up checking if a certain file exists, if not touch filename, and exit the cron. If it does, execute the cron.
[22:42] <nigelb> But that's probably not clean.
[22:42] <lifeless> I think infinity was using irony ;)
[22:42] <lifeless> or something like it
[22:42] <nigelb> Hah.
[22:43] <infinity> It was born of grumpy, whether there was also ironic sarcasm involved is an exercise to the reader.
[22:43]  * micahg + IRC sarcasm = syntax error
[22:43] <infinity> I think I might be able to blame anacron, though.
[22:44] <infinity> In which case, the most elegant solution might be to smack some stamp files with a stick on install.
[22:44] <infinity> Pretend that cron has run recently, instead of, like, never.
[22:44] <nigelb> Its 4 am and my neck hurts like crazy. I've temporarily lost the ability to spot sarcasm.
[22:44] <lifeless> nigelb: can I suggest going to bed?
[22:45] <nigelb> lifeless: I'm taking that suggestion right about now. :)