[12:16] <tjaalton> looks like xorg-server has been accumulating a bunch of crashers all over the place
[12:16] <tjaalton> drivers etc
[12:58] <tjaalton> uh, how can a system running on nouveau crash with a trace that points to ../src/sna/sna_threads.c?
[12:59] <tjaalton> ahh hybrid, of course..
[13:09] <bjsnider> use the bios switch, turn off one of the chips
[13:09] <bjsnider> if you don't have a switch, that's unfortunate
[13:10] <tjaalton> nah triaging bugs
[13:34] <bcurtiswx_> why would .Xauthority file not let me login from lightDM even with the 664 user:user for permissions
[13:35] <bcurtiswx_> upon removing the file it let me login, but appeared to have the right permissions to allow me to login
[13:35] <bjsnider> mine is 600 user:user
[13:36] <bjsnider> maybe it wasn't permissions. maybe the file was corrupt
[13:36] <bcurtiswx_> bjsnider: so then what was causing it to become corrupt?
[13:37] <bcurtiswx_> i haven't purposely messed with that file specifically, only done updates in Saucy
[13:37] <bjsnider> impossible question to answer
[13:38] <bcurtiswx_> it's happened twice in the past week
[13:38] <bcurtiswx_> past 2 weeks*
[13:38] <bcurtiswx_> It's a simple workaround and all, but seems like possibly a bigger issue
[13:39] <bcurtiswx_> there's no error that says your .Xauthority file is corrupt that would clue even experienced users into why it happens if they see it for the first time
[13:40] <bjsnider> well, i dunno. i'm not on saucy yet, and i don't log in with lightdm
[13:40] <bjsnider> file a bug if you want
[13:40] <bjsnider> should be against lightdm i suppose
[13:41] <bcurtiswx_> I will next time it arises, that way i can attach my .Xauthority file to the bug report
[14:23] <bjsnider> bugs don't arise, they manifest themselves
[15:08] <bjsnider> i don't understand this movie by nvidia. are they saying the blob isn't good enough?
[15:08] <bjsnider> they'd rather have people using nouveau?
[15:09] <tjaalton> they want distros to provide better OOTB experience
[15:09] <tjaalton> which is not happening
[15:10] <tjaalton> right now
[15:10] <bjsnider> i see
[15:10] <tjaalton> you need to read the original announcement, not phoronix ;)
[15:10] <bjsnider> they want the first boot to be better just before users are prompted to install the blob
[15:10] <tjaalton> phoronix jumped the gun
[15:11] <tjaalton> it's a start
[15:11] <bjsnider> i'm reading ars
[15:12] <tjaalton> yeah that's more accurate
[15:12] <tjaalton> actual quotes
[15:12] <tjaalton> "basic 3d rendering"
[15:13] <tjaalton> maybe related to libglvnd too
[15:13] <bjsnider> not sure why all of a sudden after so many years they'd make this decision
[15:13] <bjsnider> they had their own nv driver for that
[15:14] <bjsnider> they abandoned it
[15:14] <tjaalton> maybe it took years to get this far
[15:14] <tjaalton> behind the curtains
[15:14] <tjaalton> they abandoned nv because nouveau was already the default on distros and doing kms
[15:15] <bjsnider> yes but that would have been the time to make this movie
[15:15] <tjaalton> and nv was obfuscated
[15:15] <tjaalton> doubt they were just sitting on the docs
[15:16] <tjaalton> just writing them takes time
[15:16] <bjsnider> they had to be written down somewhere originally
[15:16] <bjsnider> they're not keeping everything in their heads over there
[15:17] <bjsnider> it takes time to redact aspects of them that are patented
[15:17] <tjaalton> exactly
[15:17] <tjaalton> and make the lawyers happy
[15:17] <bjsnider> i don't think it would take this much time
[15:18] <bjsnider> they could have claimed they were going to do this around the time they abandoned nv


[01:39] <flaccid> interesting question. how can i find out the latest AKI for ubuntu 10.04 official ?
[01:43] <erichammond> flaccid: It depends on the region and architecture
[01:44] <erichammond> The latest 32-bit us-east-1 Ubuntu 10.04 is ami-06ad526f.  An ec2-describe-images shows the kernel as: aki-407d9529
[01:45] <erichammond> Recent Ubuntu AMIs use a PV AKI and load the actual kernel code from the AMI.
[01:45] <erichammond> This lets you upgrade in place and not have to switch to a new AMI/AKI for reboots and the like.
[01:46] <flaccid> how did you work out that it was the latest AMI?
[01:47] <erichammond> flaccid: There's this web site that lists all of the latest Ubuntu AMIs in a table at the top of the home page: http://alestic.com
[01:47] <erichammond> :)
[01:47] <flaccid> sure and how did you create that list?
[01:48] <erichammond> Or you can query it dynamically (same as I do on Alestic.com) through URLs like: http://uec-images.ubuntu.com/query/natty/server/released.current.txt
[01:48] <erichammond> Ah, that even lists the AKI ids.
[01:48] <flaccid> or http://cloud.ubuntu.com/ami/ might be suffice
[01:48] <erichammond> Yep.  All depends on how you like finding things
[01:49] <flaccid> there is only 1 edition built and published, 'ubuntu server' ?
[01:50] <erichammond> flaccid: I don't understand the question.
[01:50] <flaccid> http://uec-images.ubuntu.com/query/lucid/server/released.current.txt
[01:50] <flaccid> has 'server' in url
[01:50] <flaccid> and 2nd column
[01:50] <flaccid> http://cloud.ubuntu.com/ami/ does not have such a column or ref
[01:51] <erichammond> Ubuntu currently publishes server images for official release.
[01:51] <flaccid> ok thanks very much
[01:51] <erichammond> They have desktop images that are build daily but are not officially supported.
[01:51] <erichammond> yet
[01:51] <flaccid> i see
[01:52] <erichammond> Ubuntu server for EC2/UEC is very slightly different from Ubuntu server you can download. It has the cloud-init package and some other tweaks to make it work well in the EC2/UEC environments.
[01:52] <flaccid> ack
[01:53] <erichammond> er, different from the Ubuntu server you can download from http://www.ubuntu.com/download/ubuntu/download
[01:53] <flaccid> happy to hear that UEC is getting rid of euca
[01:54] <erichammond> You can also download the EC2/UEC images themselves from places like http://uec-images.ubuntu.com/natty/current/natty-server-uec-amd64.tar.gz
[01:55] <erichammond> I use those downloadable images to build custom Ubuntu AMIs.
[02:34] <flaccid> cool thanks erichammond
[10:52] <safinaskar> how to use ubuntu in the cloud??? i opened 10.cloud.ubuntu.com, but i don't see button to enter cloud ubuntu machine. i done all instructions: i created launchpad account and i imported ssh key
[11:02] <safinaskar> HOW TO ENTER CLOUD MACHINE VIA WEB-INTERFACE??????
[11:43] <kim0> doh .. too bad he didn't wait
[12:50] <koolhead11> meep ..
[17:50] <smoser> Daviey, https://blueprints.launchpad.net/ubuntu/+spec/community-o-openstack-book
[17:52] <smoser> so why do you think having docs packaged is bad ?
[17:52] <smoser> i *really* like that i can apt-get install <package>-doc and then go on a plane
[17:53] <smoser> and this conversation illustrates very well why i think that blueprints suck for conversation as there is no evidence on that page that usch a conversation ever occurred.
[17:53] <smoser> kim0, ^
[17:53] <kim0> yeah
[17:54] <kim0> I'm not strongly for or against ..
[17:54] <kim0> generating a pdf and making it available online is good enough for me
[17:55] <smoser> kim0, but that is completely *not* what we do with almost every thing else
[17:57] <smoser> that argument would imply that http://manpages.ubuntu.com/ would be enough
[17:57] <smoser> and we should not package man pages
[17:57] <smoser> which is obviously asinine
[17:57] <kim0> should we start a public thread on should be made available offline and what shouldn't
[17:58] <smoser> i dont really know how to address it.
[17:58] <smoser> but it is very difficult in an online format to address the fact that there are multiple different versions in different versions of Ubuntu and those *need* different doc
[17:59] <kim0> yeah, this can get complex
[18:01] <kim0> I think it's probably best to discuss on the server list
[18:04] <Daviey> smoser: Why is apt-get > wget http://*.pdf ?
[18:20] <smoser> one is discoverable, one is not