[00:27] <bjsnider> Sarvatt, ping
[00:31] <yofel> hm, what's upstream for nvidia-settings? (I'm wondering where to send the patch on bug 604525 to)
[00:31] <ubot4> Launchpad bug 604525 in nvidia-settings (Ubuntu) (and 1 other project) "nvidia-settings "Configure Display Device" menu should be drop-down list instead of dialog box (affects: 1) (heat: 8)" [Wishlist,New] https://launchpad.net/bugs/604525
[06:24] <hyperair> Sarvatt: [ 13004.621] (II) intel(0): Kernel page flipping support detected, enabling
[06:24] <hyperair> thankfully the hangs seem minor enough that i can get back in by using ssh
[06:28] <RAOF> Yeah, Sarvatt said he was going to drop that patch to get closer to git.
[06:30] <RAOF> Damn, what has happened to all the amd64 PPA buildds?
[06:30] <hyperair> RAOF: take a look at https://launchpad.net/builders
[06:31] <RAOF> Hah.  The kernel thwarts me again!
[06:31] <hyperair> lol
[06:31] <RAOF> Have you tried the intel-legacy DDX?
[06:31] <hyperair> what's that?
[06:32] <ricotz> RAOF, hello
[06:32] <RAOF> hyperair: https://edge.launchpad.net/~raof/+archive/aubergine/+packages
[06:32] <RAOF> ricotz: Hello.
[06:32] <ricotz> are there some currently known issues with nouveau in maverick?
[06:33] <RAOF> hyperair: It's essentially a gem-less DDX grafted onto 2.12 for those not using KMS.
[06:33] <RAOF> ricotz: Not known by me particularly.  Are you going to tell me of one? :)
[06:33] <hyperair> RAOF: ah i see. but why would i not want to use KMS?
[06:33] <RAOF> hyperair: Because you've got an i8xx card, and GEM has been a one-way ticket to random GPU hangs.
[06:34] <RAOF> That's not why _you'd_ want it, that's why someone would want it.
[06:34] <hyperair> RAOF: no, i've got an i965 card.
[06:34] <hyperair> ah i see.
[06:34] <ricotz> i cant start a normal x session, xorg.0.log say "no screens found", is there some race condition between kms and gdm or something?
[06:34] <RAOF> And _I'd_ like you to test it, so it can go upstream and we can have rainbow-dancing unicorns.
[06:34] <RAOF> ricotz: Care to pastebin dmesg & Xorg.0.log?
[06:35] <ricotz> it seems to work after a xserver reinstall so ureadahead it triggered, i think
[06:35] <hyperair> RAOF: test how? just install it and leave things be?
[06:35] <RAOF> hyperair: Yup.
[06:35] <hyperair> or do i have to disable KMS?
[06:35] <RAOF> Well, you can try disabling KMS.
[06:35] <RAOF> And checking that it doesn't explode horribly.
[06:36] <hyperair> heh okay.
[06:36] <hyperair> i'll give it a go.
[06:36] <RAOF> But even just installing it and finding the KMS works fine is useful.
[06:36] <RAOF> s/the/that/g
[06:36] <hyperair> i'll give it a go once your amd64 builds are done.
[06:37] <ricotz> RAOF, http://paste.pocoo.org/show/238186/ - http://paste.pocoo.org/show/238187/
[06:38] <ricotz> RAOF, it happens with maverick packages and edgers
[06:38] <RAOF> So, the very first thing I see is that you're using xorg-edgers ;)
[06:39] <ricotz> yes, but i am getting the same error without edgers
[06:41] <RAOF> Hm.
[06:42] <RAOF> As they say in the movies: let me check my notes.
[06:43] <ricotz> RAOF, ok
[06:48] <ricotz> RAOF, xorg.failsafe.log of x which is working right now - http://paste.pocoo.org/show/238191/
[06:50] <dupondje> nouveau is broken atm in maverick ?
[06:55] <RAOF> Apparently the answer is “yes”
[06:55] <RAOF> ricotz: Just for my own amusement, can you get a non-edgers Xorg.0.log?
[06:56] <ricotz> RAOF, can you confirm this problem? ok, this will take some time
[06:58] <dupondje> https://launchpad.net/ubuntu/+source/libdrm/2.4.21-1ubuntu1/+build/1874547
[06:58] <dupondje> could this be the reason ?
[06:58] <RAOF> No, that's not going to be the reason.
[07:01] <RAOF> I'll update my nouveau laptop & see if this happens locally.
[07:03] <ricotz> RAOF, mhh, now i got it with my intel laptop
[07:03] <dupondje> its broken since yesterday evening somewhere ..
[07:03] <dupondje> dunno what got upgraded since then
[07:04] <RAOF> dupondje: Learn to love the Ubuntu Software Centre.
[07:04] <RAOF> Fire it up, and hit “history”
[07:05] <RAOF> Tada!  An answer to the question: what upgraded since last night :)
[07:05] <dupondje> i'm not on my broken laptop atm :) can't check
[07:06] <ricotz_> RAOF, for me it started before yesterday
[07:07] <dupondje> I updated @ around 16:00 and rebooted, everything was fine.
[07:08] <RAOF> ricotz_: You've got the same problem with an intel laptop?
[07:08] <RAOF> I'm *definitely* not seeing it, then.
[07:08] <ricotz_> i am just getting the nouveau log
[07:11] <ricotz_> RAOF, ok, first boot after "downgrade" http://paste.plurk.com/show/280757/
[07:12] <ricotz_> second boot http://paste.plurk.com/show/280758/
[07:13] <dupondje> second looks quite the same error like I got ...
[07:13] <ricotz_> RAOF, with intel http://paste.plurk.com/show/280759/
[07:14] <RAOF> Ok.  So it looks a lot like libdrm is broken for you.
[07:14] <RAOF> Or, possibly, the kernel.
[07:15] <dupondje> I rebooted after kernel upgrade, and then it still worked ...
[07:15] <RAOF> Does this only happen with 2.6.35-8-generic?
[07:15] <dupondje> no
[07:15] <RAOF> Hah, too slow.
[07:15] <ricotz_> it also happened with -7
[07:16] <ricotz_> on intel it seemed to start with -8
[07:17] <RAOF> Ok, I've got  a newer libdrm 'cause I'm testing the legacy DDX.  I'll downgrade that and see.
[07:25] <RAOF> Nope, still works fine here.
[07:26] <RAOF> What versions of libdrm, libdrm-intel, libdrm-nouveau, kernel, DDX, and xserver are you using?
[07:27] <ricotz> the current maverick versions
[07:27] <dupondje> same here ...
[07:28] <RAOF> So, 2.4.20-1ubuntu2, 2.6.35-8-generic, intel 2.11.0, and 1.8.2RC2?
[07:28] <dupondje> can't check atm :(
[07:31] <RAOF> Got an xorg.conf?
[07:31] <ricotz> libdrm 2.4.20-2ubuntu1 - kernel 35-8 - intel 2:2.11.0-1ubuntu2 - xserver-xorg 2:<IP_ADDRESS>2-0ubuntu2
[07:31] <ricotz> no
[07:34] <RAOF> I need to run some errands - I'll ponder this while I do so, and while the nouveau lappy is updating.
[07:35] <ricotz> ok, np
[07:35] <dupondje> ricotz: amd64 or i386 ?
[07:35] <ricotz> both amd64
[07:38] <dupondje> you also RAOF  ?
[07:53] <RAOF> dupondje: Yup.  amd64
[08:37] <ricotz> RAOF, any progress? using nomodeset gets it to work
[08:37] <RAOF> ricotz: For values of “work” equal to “uses vesa instead”, I presume :)
[08:38] <RAOF> It doesn't help that I can't reproduce this locally :/
[08:38] <ricotz> oh you are right this disables nouveau
[08:39] <ricotz> so it might be a hardware specific problem
[08:40] <RAOF> It shouldn't be.
[08:41] <ricotz> i tested kernel 35.7-11 which works on the first boot, and freezes on the second
[08:41] <RAOF> It's not entirely obvious why drmGetBusid is returning "" rather than “pci:0000:01:00.0”, though.
[08:41] <RAOF> Works on the first boot, fails on the second?
[08:42] <RAOF> I don't suppose that if you log off and log in again it works?
[08:43] <ricotz> no i need to reboot, like i said, it seems to be related to some trigger which is called after a new kernel/x installation
[08:43] <ricotz> like ureadahead which delays some things
[08:44] <dupondje> after kernel upgrade it was still working here ... tho only 1 reboot, so might have been lucky ;)
[08:44] <RAOF> Can you confirm that?  Delete /var/lib/ureadahead/pack and it'll re-profile for you.
[08:46] <ricotz> RAOF, will try that
[08:56] <RAOF> You know what?  I need to get a big, beefy desktop machine to build stuff on.
[08:57] <ricotz_> RAOF, i have restarted now couple times, deleting this ureadahead pack file seems to resolve it
[08:59] <RAOF> Can you give me two dmesg logs — one that has worked and one that hasn't?
[08:59] <ricotz_> is the "var.run.pack" introduced recently?
[09:00] <RAOF> You get one pack per filesystem.
[09:00] <RAOF> The root filesystem gets “pack”; the others get “boot.pack”, “usr.pack”, etc.
[09:01] <ricotz_> ok, then it is fine
[09:05] <ricotz> RAOF, FAIL: http://paste.pocoo.org/show/238215/ - GOOD: http://paste.pocoo.org/show/238216/
[09:06] <ricotz> i hope these are the right ones (after rebooting this much)
[09:07] <RAOF> Wait - the *second* one is good?
[09:08] <ricotz> this is the current boot
[09:09] <RAOF> Oh, of course.  ureadahead.  *That's* why udev would be starting some 12 seconds earlier in the second trace.
[09:10] <RAOF> So, I'd guess that if you removed “splash” from your kernel command line, this would work.
[09:12] <ricotz> it seems to work already
[09:13] <RAOF> Even without deleting the pack?
[09:13] <RAOF> You had a problem before - are you suggesting that this has magically fixed itself? :)
[09:14] <ricotz> yes, i have deleted it twice, but not the third time
[09:14] <ricotz> i will reboot again to be sure
[09:16] <ricotz_> ok, there is it again :(
[09:16] <dupondje> https://launchpad.net/ubuntu/+source/libdrm/2.4.21-1ubuntu1/+build/1874547 is build ... maby install ? :)-
[09:17] <RAOF> I'd be surprised if that fixed it.
[09:18] <steveire> Is there any other useful information I can put in this bug report? https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/606001
[09:18] <ubot4> Launchpad bug 606001 in xorg (Ubuntu) "Dual screen setup does not work after installation (affects: 1) (heat: 6)" [Undecided,New]
[09:20] <ricotz_> RAOF, removing "splash" doesnt work
[09:20] <RAOF> Well that's put a crimp in an otherwise damn-fine theory :)
[09:21] <RAOF> Dump a file containing “FRAMEBUFFER=y” into /usr/share/initramfs-tools/conf.d ?  That'll get the drm module added to the initramfs, which should make loading it (a) faster and (b) independent of ureadahead.
[09:22] <ricotz_> ok
[09:24] <RAOF> steveire: What have you done to try and get a dual-head display?
[09:25] <steveire> RAOF: I have opened system settings and gone to the 'monitors' section, which tells me I do not have 2 monitors.
[09:25] <RAOF> steveire: Also, running “apport-collect 606001” will attach all sorts of tasty information.
[09:26] <steveire> "This module is only for configuring systems with a single desktop spread across multiple monitors. You do not appear to have this configuration."
[09:28] <RAOF> Ok.  That would be useful information to have on the bug :)
[09:28] <ricotz_> RAOF, patching initramfs works
[09:29] <RAOF> Consistently?
[09:29] <ricotz_> i will reboot a third time, but fsck might do some things here
[09:30] <ricotz_> i need to reset the fscheck count
[09:31] <steveire> RAOF: Is that apport thing interactive? Can I see the info it sends back before it does?
[09:32] <steveire> http://dpaste.com/218731/
[09:32] <RAOF> steveire: I think so, from memory.
[09:33] <RAOF> You want to give it access - it'll upload xorg.0.log, dmesg, etc.
[09:33] <steveire> It implies it will upload more than that. unspecified 'private data'
[09:34] <steveire> And it doesn't tell me if I can review it or not.
[09:34] <RAOF> No, that means that it will be able to write to bugs you've marked as “private”
[09:36] <ricotz_> RAOF, ok, two working reboots
[09:40] <steveire> RAOF: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/606175 I can't run apport-collect yet
[09:40] <ubot4> Launchpad bug 606175 in apport (Ubuntu) "apport-collect does not tell me what it will do (affects: 1) (heat: 6)" [Undecided,New]
[09:42] <RAOF> steveire: I've just checked - it will show you what it'll send.
[09:45] <steveire> RAOF: This post http://blog.grossmeier.net/2009/03/02/apport-collect-just-what-you-wanted/ says it works without any other interaction with the reporter
[09:47] <steveire> The man page is also not very clear on it http://man.he.net/man1/apport-collect
[09:52] <RAOF> Well, I've just checked with a report on staging, and it pops up the “here's the stuff we'll be reporting” page.
[09:52] <RAOF> Possibly if you run it without X it doesn't do that, but it's generally pretty careful to ensure you can easily find out what data is being reported.
[09:56] <ricotz> RAOF, so it looks like a race condition, something has gotten slower or faster so this problem appears
[09:56] <RAOF> Right.
[09:57] <ricotz> now nouveau is loaded 1 second ealier, but initrd is 16MB now
[09:58] <RAOF> Because it's got all the drm modules in it, yeah.
[09:58] <RAOF> Plus plymouth
[09:58] <steveire> I don't see why it needs 'write access' to read dmesg...
[09:59] <RAOF> It needs write access to your *launchpad* account.
[09:59] <RAOF> Otherwise it can't add anything to the bug, obviously!
[10:00] <RAOF> Is that not obvious from the messages - both in the terminal, and the launchpad message?
[10:03] <RAOF> steveire: Well, I guess it's clearly not obvious, or you wouldn't be asking the question.  If you can think of a better wording, feel free to add it to the apport bug you just submitted.
[10:09] <steveire> RAOF: Ok, well I ran the tool
[10:23] <RAOF> steveire: Ok, now I'm confused.  Only one of your shiny, fancy dell monitors is showing an image?
[10:24] <RAOF> steveire: As far as X is concerned, they should be both lit up and running.
[10:24] <jcristau> means the kernel is confused, afaict
[10:25] <RAOF> I guess so.
[10:25]  * RAOF heads to dinner.
[10:26] <steveire> That's correct. Only one of them is useful. The other is completely blank
[11:08] <RAOF> steveire: I don't suppose running “xrandr --output DVI-I-2 --right-of DVI-1-1” does anything?
[11:20] <ara> hello all!
[11:20] <ara> in the middle of a big X upload?
[11:20] <ara> I think I upgraded and rebooted at the wrong time :)
[11:20] <ara> my X won't boot anymore
[11:21] <steveire> stephen@chimera:~$ xrandr --output DVI-I-2 --right-of DVI-1-1
[11:21] <steveire> xrandr: cannot find output "DVI-1-1"
[11:21] <jcristau> steveire: DVI-I-1, not DVI-1-1
[11:23] <steveire_> That command borked my workstation once I'd fixed the 1 to an I
[11:25] <steveire_> All my windows disappeared, and I had fragments of plasmoids in different places and nothing worked. I had to hard-reset
[11:25] <steveire_> And now it's having a hard time booting.
[11:27] <RAOF> Well, at least it had some impact, even if it wasn't particularly good. :/
[11:28] <RAOF> ara: No - the next flurry of X will be xserver 1.9, which I won't upload until it stops crashing with clutter apps.
[11:28] <RAOF> Gah, too slow.
[11:29] <jcristau> maybe mark it as blocking 1.9 in bugzilla?
[11:29] <jcristau> where "it" is the bug you filed
[11:29] <RAOF> I wasn't sure if I should do that - I guess I could.
[11:30] <steveire> I'm wondering if I should try again. You know that xkcd comic with the lightning machine?
[11:31] <RAOF> Heh.
[11:31] <RAOF> “Hm.  I wonder if it does that *every* time”
[11:31] <steveire> What is the command supposed to do?
[11:31] <tseliot> steveire_: I found kde 4 to act in a weird way when using multiple screens. None of this can be reproduce in gnome, at least here
[11:31] <RAOF> That's meant to make one of your displays left of the other - IE: de-clone them
[11:32] <RAOF> I certainly found that KDE4 didn't deal particularly well with multiple heads.  It didn't go totally bananas, though.
[11:32] <RAOF> jcristau: Incidentally, I'm thinking of attending XDS, and I was wondering what you thought.
[11:36] <steveire> Maybe I'll install ubuntu-desktop and see what happens. Even the boot splash only appears on one screen though.
[11:36] <RAOF> ara: No - the next flurry of X will be xserver 1.9, which I won't upload until it stops crashing with clutter apps.
[11:36] <RAOF> steveire: Which is strange, given that it worked on the livecd.
[11:37] <RAOF> jcristau: Bug marked as blocking.
[11:37] <jcristau> i think this xds is the first time i might be able to attend
[11:39] <steveire> Indeed.
[11:58] <dupondje> is the x-issue fixed already ? or bugreport / workaround ? That I can boot my computer again this evening :)
[12:00] <jcristau> whatever "the x-issue" means...
[12:07] <RAOF> dupondje: If you add the drm module to your initramfs you'll avoid the race condition.
[12:08] <RAOF> ricotz: Did you file a bug, incidentally?
[12:08] <ricotz> RAOF, no, i havent
[12:11] <RAOF> Please do so - I can't fix that race off the top of my head, so a bug will be needed.
[12:16] <ricotz> RAOF, will do, as soon i can
[12:33] <ricotz> RAOF, what about this bug report https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/459639
[12:33] <ubot4> Launchpad bug 459639 in xorg-server (Ubuntu) "[Karmic] X server starts randomly in failsafe when starting from cold boot (affects: 6) (heat: 42)" [High,Confirmed]
[12:34] <jcristau> karmic?
[12:38] <dupondje> and not only from cold boot imo :)
[12:38] <ricotz> yeah, i will file a new one
[12:40] <RAOF> And a huge muddle of multiple “X doesn't start” bugs.
[12:40] <RAOF> Handy hint: the binary blob not starting is *almost always* a different bug to any free driver not starting :)
[12:46] <seb128> http://launchpadlibrarian.net/52029105/buildlog_ubuntu-maverick-i386.clutter-gtk-0.10_0.10.4-0ubuntu3_FAILEDTOBUILD.txt.gz
[12:47] <seb128> is that libgl installability issue known?
[12:52] <ricotz> RAOF, https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/606244
[12:52] <ubot4> Launchpad bug 606244 in xorg-server (Ubuntu) "X doesn't find a screen and is not starting due a race condition (affects: 1) (heat: 6)" [Undecided,New]
[13:15] <RAOF> seb128: clutter-gtk builds fine locally.  I guess it could be an i386 issue?
[13:15] <seb128> I figure it out now
[13:16] <seb128> I newed libkms1 to universe yesterday
[13:16] <seb128> I've promoted it now, should be fixed after the next publisher run
[13:16] <seb128> would be nice to document new libraries in the changelog though
[13:16] <seb128> so we know what to do when newing them
[13:16] <seb128> Sarvatt, ^
[13:16] <RAOF> Aaah, the newer libdrm.  Right.
[13:16] <yofel> short question, what's upstream for nvidia-settings? (where to send a patch..)
[13:17] <seb128> or to use -v to list debian changes
[13:17] <RAOF> That obviously hasn't hit my amd64 mirror yet.
[13:19] <RAOF> Well, back to packing.
[13:20] <tseliot> yofel: you can contact Aaron plattner
[13:20] <yofel> where?
[13:22] <tseliot> you can have a look at whatever commit in git an see his address: http://cgit.freedesktop.org/~aplattner/nvidia-settings/commit/?id=655fb95354fdfb7ffe5f44f0341c132165b0c983
[13:22] <tseliot> what kind of change is that?
[13:23] <yofel> bug 604525
[13:23] <ubot4> Launchpad bug 604525 in nvidia-settings (Ubuntu) (and 1 other project) "nvidia-settings "Configure Display Device" menu should be drop-down list instead of dialog box (affects: 1) (heat: 10)" [Wishlist,Confirmed] https://launchpad.net/bugs/604525
[13:23] <tseliot> aah, that one
[13:23] <tseliot> yes, feel free to send Aaron a patch
[13:23] <yofel> was asking as launchapd doesn't tell me where to find upstream..
[13:23] <yofel> thanks
[13:24] <tseliot> seb128: I didn't notice that there were new libraries when I tested/sponsor the upload. So it's my bad too
[13:25] <seb128> tseliot, that's ok, I figure what the issue was now ;-)
[13:25] <tseliot> good
[13:35] <dupondje> RAOF: so its a kernel bug? But why is it broken for -7 and -8 since today ? and it worked without issues for days on -7 ? :)
[13:43] <dupondje> somebody else hitting the https://bugs.edge.launchpad.net/ubuntu/+source/xorg-server/+bug/606244 bug ?
[13:43] <ubot4> Launchpad bug 606244 in linux (Ubuntu) "X doesn't find a screen and is not starting due a race condition (affects: 2) (heat: 12)" [Undecided,New]
[13:53] <tseliot> maybe you should try the latest libdrm
[13:53] <dupondje> yea indeed :)
[13:53] <dupondje> i'm not @ home, so I can't test
[13:53] <dupondje> but I commented the bug
[13:57] <tseliot> ok
[14:36] <dupondje> https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/606244
[14:36] <ubot4> Launchpad bug 606244 in libdrm (Ubuntu) "X doesn't find a screen and is not starting due a race condition (affects: 2) (heat: 12)" [Undecided,Fix released]
[14:36] <dupondje> like I tough
[14:36] <dupondje> libdrm and its fixed :)
[14:41] <tseliot> very good
[14:41] <tseliot> thanks for testing
[14:49] <ricotz> dupondje, the problem is i was hitting this bug also with edgers ppa
[14:50] <ricotz> where libdrm was up2date for some time
[16:36] <dupondje> ricotz: so you still have it with newest libdrm ?!
[16:36] <dupondje> feel free to re-open then btw :)
[16:40] <Sarvatt> the stuff in the section of the changelog you quoted was already in the previous libdrm dupondje
[16:41] <dupondje> mmmm weird it started working then after libdrm update here ..
[16:43] <dupondje> Sarvatt: previous version was 2.4.20-2ubuntu1, now its 2.4.21-1ubuntu1
[16:44] <dupondje> the changelog section is in 2.4.20-3 ..
[16:44] <Sarvatt> yeah I know, but I did the abi bump stuff from 2.4.20-3 in 2.4.20-2ubuntu1 before they did it in debian, thats why we didn't bother merging 2.4.20-3
[16:45] <dupondje> ah but 2.4.20-2ubuntu1 gives +      03_revert_abi_change.diff - Obsolete
[16:45] <dupondje> anyway it was broken here, and libdrm update resolved it ... so something must be changed ;)
[16:46] <Sarvatt> your initrd got rebuilt with the FRAMEBUFFER=Y maybe? :)
[16:46] <dupondje> well no :s
[16:46] <dupondje> it didn't even regenerated my initrd :)
[16:49] <dupondje> was getting completely the same error as ricotz
[16:50] <Sarvatt> i dont see anything in libdrm that would have affected that
[16:53] <dupondje> [    51.454] drmOpenByBusid: drmGetBusid reports  => when it was broken
[16:54] <dupondje> [    25.539] drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
[16:54] <dupondje> now
[16:54] <dupondje> :)
[16:55] <dupondje> ricotz: did you try libdrm_2.4.21-1 ?
[16:56] <Sarvatt> that happens when the kernel drm isn't ready when the ddx is trying to start
[16:59] <dupondje> look, I gonne try to reboot some times, to see if it still works :)
[17:01] <Sarvatt> do you guys have agp cards by any chance?
[17:06] <dupondje> Seems like i've been very lucky, that the first boot after libdrm upgrade worked :p
[17:07] <dupondje> https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/606244
[17:07] <dupondje> so not fixed ... :)
[17:07] <ubot4> Launchpad bug 606244 in libdrm (Ubuntu) "X doesn't find a screen and is not starting due a race condition (affects: 2) (heat: 12)" [Undecided,New]
[17:08] <Sarvatt> do you guys have agp cards by any chance?
[17:08] <dupondje> in my old computer yes :)
[17:09] <ricotz> dupondje, i havent tried it with the maverick version, i am using edgers which gave me the same error
[17:09] <ricotz> Sarvatt, it is a PCIs card
[17:09] <ricotz> PCIe
[17:10] <dupondje> its laptop here, so euh pcie bus also I bet
[17:11] <ricotz> dupondje, so you are still getting the error?
[17:11] <ricotz> dupondje, nm ;)
[17:11] <dupondje> yep :s
[17:12] <dupondje> been very lucky that just after the libdrm reboot it worked :p
[17:12] <dupondje> the reboot after I upgraded libdrm .. :)
[17:12] <ricotz> yes, like i said before the first boot after some kernel/x changes it works
[17:13] <dupondje> I also see kernel bug in boot: [   33.758638] BUG: unable to handle kernel NULL pointer dereference at<PHONE_NUMBER>0003c0
[17:13] <dupondje> :p
[17:13] <dupondje> [   33.758809] Process plymouthd (pid: 375, threadinfo ffff880037e28000, task ffff880037d38000)
[17:13] <ricotz> brb
[17:44] <hyperair> Sarvatt: i've observed something rather interesting.once i'm past the first GPU hang, (ssh in and forcefully kill X and restart gdm), it doesn't hang any more.
[17:45] <hyperair> Sarvatt: also, the first hang happens very quickly after logging in, within the first 5 hours or so.
[17:46] <hyperair> my current uptime is 15h. Xorg's uptime is 12h
[17:46] <hyperair> er wait. 11h 23m
[17:49] <bryce2>  Sarvatt, tseliot, if lp #567007 sounds like a useful launchpad feature, mind clicking 'Affects me too'?  The more people marked as it affects them, the more likely it'll be to get on the Launchpad team's planning list when work starts on search improvement
[17:49] <ubot4> Launchpad bug 567007 in malone "User-specific default tag search parameters (affects: 1) (heat: 3)" [Low,Triaged] https://launchpad.net/bugs/567007
[17:52] <Sarvatt> done, that would be a nice feature :)
[18:02] <Darxus> There's a fix for bug #541492.  It involves 5 source packages (one of which is linux).  What needs to be done to get them in Maverick?
[18:02] <ubot4> Launchpad bug 541492 in xserver-xorg-video-intel (Ubuntu Lucid) (and 2 other projects) "MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?) (affects: 77) (dups: 30) (heat: 523)" [High,Triaged] https://launchpad.net/bugs/541492
[18:07] <dupondje> everything seem to crash now :s
[18:37] <dupondje> ricotz: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/606393 you have this also ?
[18:37] <ubot4> Launchpad bug 606393 in linux (Ubuntu) "BUG: unable to handle kernel NULL pointer dereference at<PHONE_NUMBER>0003c0 (affects: 1) (heat: 6)" [Undecided,New]
[18:58] <ricotz> dupondje, yes, this is plymouthd trying
[18:58] <ricotz> dupondje, should be the same problem which causes X to fail
[19:51] <bjsnider> Sarvatt, remember that issue with nvidia-current where it's creating two modprobe.conf files?
[20:00] <Sarvatt> bjsnider: ya want tseliot, but yeah I remember it :)
[20:01] <bjsnider> what i don't understand is, the alternatives are putting one of the files by a link into the /etc/modprobe.d directory, the one without the alias, and yet the system behaves as though it knows about the alias
[20:05] <Sarvatt> look at the dkms.conf
[20:05] <Sarvatt> DEST_MODULE_NAME[0]="nvidia-current"
[20:05] <Sarvatt> guessing thats why
[20:06] <bjsnider> yeah, the module is built as nvidia-current
[20:06] <bjsnider> but the xorg.conf says nvidia
[20:06] <bjsnider> without the alias the system should fail to load that module because it doesn't exist
[20:07] <bjsnider> and it intermittently does so
[20:07] <bjsnider> but for some reason it works most of the time. i can't see why.
[20:08] <Sarvatt> the xorg.conf doesn't have anything to do with it though, the ddx module is still nvidia_drv
[20:08] <bjsnider> then what is the alias used for?
[20:09] <Sarvatt> it only loads if it wasn't loaded by udev already at startup but yeah i thought it might run into the same problem because thats hardcoded to load nvidia.ko and dkms is just renaming it to nvidia-current.ko instead of aliasing nvidia to nvidia-current
[20:10] <Sarvatt> it's still built as nvidia.ko by dkms just installed as nvidia-current.ko after
[20:10] <bjsnider> without the alias i have tried modprobe nvidia, and the response is no such module exists
[20:11] <Sarvatt> you'd need to change that DEST_MODULE_NAME to nvidia and alias nvidia nvidia-current to do that
[20:12] <bjsnider> $ lsmod|grep nvidia
[20:12] <bjsnider> nvidia              11105770  38
[20:14] <Sarvatt> the module is nvidia-current.ko though, its confusing :(
[20:14] <bjsnider> i think what you have here is the dx module is being renamed so that each nvidia module can be built and installed at the same time
[20:15] <bjsnider> i'm fairly sure putting driver "nvidia" in the xorg.conf file is the same as saying modprobe nvidia
[20:48] <Sarvatt> the xorg.conf driver you pick specifies which _drv to load bjsnider, nothing to do with kernel modules
[20:49] <Sarvatt> the X driver can load kernel modules though
[20:51] <Sarvatt> those nvidia_drv.so's are swapped around with the /usr/lib/xorg/extra-modules alternative pointing to the different driver's directories
[20:55] <Sarvatt> xf86LoadKernelModule() does it, i see that in nvidia_drv.so. it'll be trying to load nvidia that doesn't exist probably if it hasn't already been loaded by udev before
[22:01] <bryce2> tjaalton, BEL?


[00:13] <rick_h_> huwshimi: morning, how goes?
[00:25] <huwshimi> rick_h_: Hey! Good thanks. Yourself?
[00:26] <rick_h_> huwshimi: party party, LUG meeting
[00:27] <rick_h_> huwshimi: I wanted to check in on your test stuff. I know I wasn't amazing helpful with Y.later, while it's in the code base I've not used it much so wasn't sure
[00:27] <rick_h_> huwshimi: but I know I had looked at how to do testing around the animations and had those couple of ideas for you, not sure if they helped?
[00:27] <huwshimi> rick_h_: Sounds fun!
[00:28] <huwshimi> rick_h_: The main problem is that it messes with other tests. I think I'll just go with an extra check to see if the node exists. I know that will only come into play in the tests, but I don't have a better idea :)
[11:58] <rick_h_> frankban: thanks for the notes. i'll put that machiner file stuff back. No reason to pull it especially in a pyjuju specific branch
[11:58] <frankban> rick_h_: +1
[12:00] <frankban> rick_h_: do you have a chance later to review + intensively QA my branch?
[12:00] <rick_h_> frankban: sure thing.
[12:00] <frankban> rick_h_: thanks!
[13:30] <bac> benji: good news!  we now have two stuck baskets.  progress.
[13:30] <benji> heh
[13:51] <hatch> gooood morning
[13:53] <rick_h_> mornnig
[13:53] <rick_h_> or something
[13:53] <hatch> haha, hows it going?\
[13:53] <rick_h_> well, ec2 hates me but other than that...ok
[13:55] <hatch> boo ec2
[14:06] <rick_h_> frankban: I've definitely done something that's taken the test run time waaaay up. the test_deployer test runs forever compared to trunk
[14:09] <frankban> rick_h_: looking again at your new mp
[14:09] <frankban> rick_h_: is the deployed gui slow as well?
[14:10] <rick_h_> I'll try it again. I did a manually make deploy once to make sure it was working but didn't time it
[14:10] <rick_h_> what should a make deploy run time be about?
[14:11] <frankban> rick_h_: https://codereview.appspot.com/52440043/diff/1/tests/20-functional.test line 61 on the right: force_machine should be 0
[14:11] <frankban> not None
[14:11] <frankban> rick_h_: so the functional tests are creating new machines, that takes lots of time
[14:11] <rick_h_> ahhhhh!
[14:12] <frankban> rick_h_: I think you can safely delete that line and just pass force_machine=0 to juju_deploy()
[14:12] <rick_h_> bah, bad if replacement there. Gotcha
[14:12] <rick_h_> rgr
[14:12] <frankban> cool
[14:13] <rick_h_> thanks, I hated that everything seemed fine but didn't want to land it with these long test runs
[14:13] <rick_h_> will do one more test run and will reduced the test time back to 40min if all goes well
[14:13] <frankban> rick_h_: +1
[14:13] <rick_h_> jujugui afk for a sec while I go pick up new glasses.
[14:16] <hazmat> rick_h_, google glasses ? :-)
[14:38] <rick_h_> hazmat: hah, not quite. More like "old-man glasses"
[14:38] <rick_h_> hazmat: I'm more a watch guy, waiting for that steel to ship :)
[14:40] <rick_h_> man, new glasses adjust period...begin!
[14:41] <hatch> shouldn't take toooo long
[14:42] <hatch> hazmat interesting bug report re a node api module
[14:42] <rick_h_> lady is telling me that "you had a 15 degree axis of rotation change that'll take some getting used to". Not sure wtf that means but it's strange.
[14:42] <rick_h_> hatch: +1 on that as well :)
[14:43] <hatch> it's quite a bit of work beyond face value because we actually use a modified api because of the guiserveer
[14:43] <hatch> but I can see that being fixed
[14:43] <rick_h_> right
[14:43] <rick_h_> but overall it's an awesome idea
[14:43] <hatch> agreed
[14:43] <rick_h_> <3 api libs
[14:43] <hatch> we'll just add that to the list of things to do.....lol
[14:45] <hatch> rick_h_ I'm going to review huw's branch just fyi
[15:08] <bac> jujugui: i've stopped charm/basket ingestion on staging.jujucharms.com so i can analyze the existing failure state without looking at a moving target.  let me know if that causes you any problems.
[15:08] <rick_h_> bac: rgr
[15:08] <bac> rick_h_: so you've got astigmatism and it's rotating?
[15:09] <rick_h_> bac: I have no idea. I've always had just a light correction, -.25 and .5 or something
[15:09] <rick_h_> but this year one eye went to a full 1.0
[15:10] <rick_h_> and never heard of the axis stuff until today
[15:11] <bac> rick_h_, benji: it looks like the stuck baskets are caused by entries in basket-queue that are locked and have been there for a while.  my theory is that they were locked when the process was abruptly stopped for some reason, though i cannot prove it.  Q: any reason to not delete the incoming charm and bundle queues at start up?
[15:11] <hatch> rick_h_ I asked, it's possible but as the delta increases the likelyhood the dr screwed up does too :)
[15:12] <hazmat> rick_h_, pebble steel is ships in two weeks. https://getpebble.com/steel
[15:12] <rick_h_> bac: hmmm, the worry is that something falls through the cracks
[15:12] <bac> rick_h_: i think the axis is for astigmatism.  other problems (near/far sight) are not rotationally sensitive but astigmatism is.
[15:12] <rick_h_> bac: I can't work up a case where it could atm though
[15:12] <rick_h_> hazmat: yep, order placed...just now impatient
[15:13] <bac> jujugui: <commerce>speaking of wrist-based gadgets, anyone interested in a slightly used fitbit?  the original, not the one with the time display.</commerce>
[15:14] <rick_h_> bac: hah, I can't give mine away
[15:14] <bac> oh, really?
[15:14] <rick_h_> it's on its second person
[15:14] <rick_h_> yea, gave it to a friend that tried to give it back and made them give it to a friend
[15:14] <hazmat> bac, rick_h_ i'd be interested re fitbit.. you mean the original pod or the wrist thingy?
[15:14] <bac> i like it, but it was made obsolete by the motion chip on the new iphone
[15:14] <bac> hazmat: original wrist
[15:15] <hazmat> hmm.. pass.. doesn't work with a standing desk very well.
[15:15] <bac> hazmat: the flex
[15:16] <bac> rick_h_: i did a comparison to fitbit vs phone.  and the logs were almost identical.  not worth having an extra doohickey if i'm always going to have the phone in my pocket.
[15:17] <rick_h_> bac: yea, I got tried of having two 'watches' and it was so inaccurate
[15:17] <rick_h_> once told me I took 680 steps in a shower
[15:17] <rick_h_> that and does't work with my phone (though they did just update it this past week) so I got rid of it
[15:18] <bac> ha.  yeah, hammering confuses it too
[15:30] <hazmat> is gary out today?
[15:31] <hatch> hazmat till friday
[15:31] <hatch> anything I can help with?
[15:39] <hatch> brb in 15, relocating
[15:50] <Makyo> jujugui call in 10
[15:53] <hatch> jujugui call in 7
[15:58] <hatch> jujugui call in 2
[15:58] <benji> call in 1:48
[15:59] <Makyo> :T
[16:07] <benji> rick_h_: come back!
[16:07] <rick_h_> benji: oh righ
[16:07] <rick_h_> right
[16:20] <hatch> 119kph wind right now
[16:21] <benji> yow!
[16:26] <hatch> ooookk well the 119kph wind gusts have knocked out the power
[16:27] <hatch> well...knocking out...
[16:56] <hatch> yay power
[17:03] <rick_h_> yay
[17:03] <rick_h_> charge those batteries
[17:10] <hatch> you bet, all plugged in now
[17:57] <hatch> it's so quiet
[17:59] <rick_h_> ssshhhh
[18:00] <rick_h_> I'm trying to juju set juju-gui juju-gui-source="https://github.com/juju/juju-gui.git network-prototype"
[18:03] <hatch> :)
[18:06] <rick_h_> hmm, well it errors but it loaded the source
[18:06] <rick_h_> https://ec2-50-16-67-171.compute-1.amazonaws.com
[18:06] <rick_h_> hatch: should this work?
[18:06] <hatch> looking
[18:06] <rick_h_> getting juju.views.NetworkListView is not defined
[18:07] <hatch> rick_h_ it's possible that the file which has that view is not getting rolled up
[18:07] <rick_h_> k, will call that a "not my problem" problem atm
[18:07] <rick_h_> but it worked bwuhahahaha
[18:09] <hatch> I believe it was only ever used with make devel
[18:09] <hatch> yeah I'd say it's a success for the deployment system though :)
[18:09] <rick_h_> https://ec2-50-16-67-171.compute-1.amazonaws.com/juju-ui/version.js is good so I'll roll with it
[18:12] <hatch> rick_h_ maybe the source should be two values
[18:12] <hatch> so the repo as one and the branch as the other
[18:12] <hatch> and maybe taking it one step further, the hash
[18:12] <hatch> so that we can 'update' something to a new source version
[18:15] <rick_h_> hatch: yea, I started down that path but it's kind of a pita
[18:15] <rick_h_> going with space to specify a branch/sha
[18:15] <rick_h_> and @123hfehw for a sha
[18:15] <rick_h_> so right now I'm testing  juju set juju-gui juju-gui-source="https://github.com/juju/juju-gui.git @c7ddd186"
[18:15] <hatch> yeah I bet - I'm just thinking of the story where we want to use a certain branch but then keep it updated when new changes are pushed to it
[18:16] <hatch> do you have to use the @?
[18:16] <rick_h_> yes, because it's the diff between a checkout and a checkout -b
[18:17] <hatch> can you not go `git checkout mybranch` and it'll just checkout the latest revno?
[18:17] <rick_h_> not if the branch doens't exist yet :)
[18:17] <rick_h_> you need the -b
[18:18] <rick_h_> if you have a local branch with that name, sure
[18:18] <rick_h_> you can't do git clone url branch
[18:18] <rick_h_> you have to git clone url && git co -bt branch
[18:19] <hatch> wel you CAN but that doesn't actually solve the issue of requiring some indicator that it's a hash
[18:20] <rick_h_> huh?
[18:20] <hatch> git clone -b brancho --single-branch <repo>
[18:22] <rick_h_> bah, this sucks. because we did a shallow clone you can't checkout a hash anyway.
[18:22] <rick_h_> have to unshallow it first
[18:22]  * rick_h_ checks git version on precise
[18:23] <hatch> hmm
[18:23] <hatch> it seems like there should be a way to pull down said hash
[18:24] <rick_h_> working on it since git fetch --unshallow is only in trusty :(
[18:28] <hatch> rick_h_ could we not say they need to specify a repo and branch name then a hash?
[18:29] <hatch> then we could use the single branch checkout
[18:29] <hatch> which should be fast....I think
[18:29] <rick_h_> but a hash has nothing to do with a branch. It's just a single git commit in a detached head state
[18:29] <hatch> right but if we already have the single branch pulled down we will have that hash
[18:29] <hatch> it's not ideal, but in order to support the widest range of systems
[18:31] <hatch> I don't know if this idea will work just thinking of alternatives :)
[18:32] <rick_h_> yea, sorry testing out here. --depth=20000 gets me caught up and I can git co hash
[18:32] <rick_h_> I know we *can* do a lot of things. Just trying to cover initial bases atm
[18:32] <rick_h_> been on this card for a week and trying to support everything git does will drive me nuts
[18:33] <hatch> well we don't need to support everything. The BIG thing is a branch
[18:33] <rick_h_> right, and branch works
[18:33] <hatch> that's the primary goal, I think a hash is a 'nice to have'
[18:33] <rick_h_> now, I can see wanting to go back to an old commit in that branch to see "does xxx work"
[18:33] <hatch> yeah for sure
[18:33] <hatch> or move forward because you have updated that branch
[18:34] <rick_h_> but even that can be done by the dev with "git checkout hash && git co -b test-feature && git push origin test-feature"
[18:34] <hatch> juju needs a 'trigger' config option :)
[18:58] <hatch> dimitern are you still around?
[19:33] <benji> rick_h_: I think I tracked down the cause of https://bugs.launchpad.net/charmworld/+bug/1263120.  Let me know when you have a minute to chat about it.  Thanks.
[19:33] <_mup_> Bug #1263120: self related services in a bundle fail proof <charmworld:Triaged> <https://launchpad.net/bugs/1263120>
[19:34] <rick_h_> benji: sure thing, your hangout or mine?
[19:34] <benji> rick_h_: I'll make one.
[19:35] <benji> rick_h_: https://plus.google.com/hangouts/_/7acpi7cc7l9l3r0bdfembikccg?hl=en
[19:45]  * Makyo runs out quickly to grab MiniDP->VGA adapter.  Kind of important for presentations D:
[20:22] <bac> yay, me, i'm sort of back
[20:23] <rick_h_> lies!
[20:27] <hatch> hah the power keeps dropping out here
[20:27] <hatch> it's like there is a switch that gets tripped when the power lines get stretched to far lol
[20:42] <bac> hatch i think my ISP is on your power grid.  not sure how that happened.
[20:43] <hatch> haha - ours is usually really stable, I guess 100+km winds are around it's limit
[20:44] <hatch> bac https://twitter.com/nheagy/status/423513314446962688
[20:44] <bac> hatch: you should use that three weeks in the summer when the ground isn't frozen to bury those lines
[20:45] <hatch> haha, they are except for the major powerlines...or something like that
[20:45] <bac> wow, that's a twisty mess
[20:45] <hatch> heh yup
[20:46] <rick_h_> yxe?
[20:46] <hatch> Saskatoon
[20:46] <hatch> airport code
[20:47] <rick_h_> umm, ok. No idea wtf the y and x and e came from, but I'll take your word for it
[20:49] <hatch> rick_h_ well the Canadian airports start with y. But I have no idea how they decide where the other 2 come from
[20:49] <rick_h_> y are you going to canada?
[20:50] <hatch> lol
[20:50] <rick_h_> it's X-tremely E-...fail
[20:50] <hatch> E-lectric
[20:51] <rick_h_> I thought it was rather un-electric currently :P
[20:52] <hatch> lol
[21:21] <bac> jujugui: anon
[21:21] <rick_h_> c-ya
[21:28] <lazypower> So, juju-quickstart
[21:29] <lazypower> this is awesome!
[21:29] <rick_h_> :)
[21:31] <lazypower> it deploys the gui by default too?
[21:31] <lazypower> oh man
[21:31] <rick_h_> yea, on node 0, pre-packaged so it installs super fast
[21:31] <rick_h_> should auto log you in with your admin secret as well
[21:31] <rick_h_> at least that feature landed, not sure on released/what version you're using
[21:32] <lazypower> I'm running trusty, but i digress - this is good stuff
[21:32] <hatch> :)
[21:33] <rick_h_> we'll let frankban know you like his baby
[21:34] <lazypower> i file bugs against juju-quickstart right?
[21:34] <rick_h_> sure
[21:34] <lazypower> Ah, probably better to put it in the merge request
[21:35] <rick_h_> lazypower: are you testing out the branch I sent jcastro ?
[21:35] <lazypower> indeed
[21:35] <lazypower> When the local machine takes longer than the deployer expects to come online it fails the quickstart
[21:35] <rick_h_> lazypower: ah, then yea. Please put them actually over in the code review page link. Look for the 'codereview.reitveld' link in the MP
[21:35] <rick_h_> oh, that's a bug and different that the MP
[21:36] <rick_h_> file that as a real bug then please
[21:36] <rick_h_> mainly I wanted to get some others to help qa that interactive ncurses mode stuff
[21:36] <rick_h_> but yea, it'll hit 1.0 in this branch so want to make sure it's solid pre-1.0 and that seems like a bug to hit.
[21:37] <lazypower> no problem i'll keep working through the ncurses stuff, i've got creds to do it.
[21:37] <rick_h_> cool, appreciate it
[21:41] <lazypower> dude it works with the mouse too?
[21:41] <rick_h_> yep
[21:41] <lazypower> i'm a fan
[21:41] <lazypower> ship it
[21:41] <lazypower> good thing i'm not your final quality gate
[21:47] <lazypower> rick_h_, i've configured everything but openstack. Looks solid to me
[21:47] <lazypower> thumbs up
[21:48] <rick_h_> lazypower: cool, thanks
[21:55] <lazypower> *note the form validation was an excellent touch
[21:55] <marcoceppi> rick_h_: it's related to this, https://bugs.launchpad.net/juju-core/+bug/1269519 kapil knows about it
[21:55] <_mup_> Bug #1269519: Error on allwatcher api <juju-core:New> <juju-deployer:New> <https://launchpad.net/bugs/1269519>
[21:55] <marcoceppi> if you guys find a solution to it, please let me know
[21:56] <rick_h_> marcoceppi: k
[22:11] <huwshimi> Morning
[22:19] <hatch> mornin huwshimi
[22:20] <huwshimi> hatch: Hey. Thanks for the review!
[22:20] <hatch> np, hope my comments make sense, I'm also open to pushback on the widget vs view thing :)
[22:21] <huwshimi> hatch: It all makes sense and seems straight forward
[22:22] <hatch> excellent
[22:30] <huwshimi> hatch: Are you all settled into home timezone yet?
[22:30] <hatch> huwshimi when I came back I actually went snowboarding in another timezone and just got back late last night haha
[22:30] <huwshimi> hatch: hah!
[22:30] <hatch> 3 timezones in 1.5weeks
[22:30] <hatch> too much
[22:30] <huwshimi> ouch
[22:37] <hatch> is there a GUI bug about making multiple relations to the same service?
[22:37] <hatch> I can't seem to find it
[22:37] <hatch> my search foo might be failing
[22:58] <Makyo> hatch, ping.
[22:58] <hatch> hey
[22:59] <Makyo> I think my current card is related to double-dispatch and removing full-screen, but having a hard time digging into it, because it only shows up in prod.
[22:59] <Makyo> I don't want to leave it hanging, and am getting nowhere.
[22:59] <Makyo> Interested?
[22:59] <Makyo> Need to review frankban's branch before EoD/vacation.
[23:00] <hatch> yeah I can pick it up
[23:01] <Makyo> hatch, cheers.  I've tracked it down to somewhere in subapp/browser/browser.js, one of the state functions (it inits, but doesn't complete)
[23:02] <hatch> alright I'll pick it up first thing


[00:34] <ahoneybun> XD
[00:34] <ahoneybun> jck77: going to try to make it to the Ubuntu Hour in Ft Lauderdale?
[00:34] <ahoneybun> we can carpool
[01:36] <danstoner> I am trying to figure out the license for some Ubuntu-included media.
[01:36] <danstoner> for example: /usr/share/sounds/purple/alert.wav
[02:02] <ahoneybun> purple sounds like from libpurple danstoner
[04:32] <mhall119> danstoner: `dpkg-query --show $file` will tell you what package a file is from, then /usr/share/doc/$package/copyright will usually hve the license
[04:33] <mhall119> sorry, --search not --show
[12:50] <danstoner> mhall119: thanks, that helps.
[14:05] <DammitJim> how do I disable automatica critical updates?
[14:07] <mhall119> DammitJim: open "Software & Updates", go to "Updates" tab
[14:07] <DammitJim> command line no desktop :(
[14:12] <DammitJim> :D
[14:12] <mhall119> yeah, not sure, looking at conf files to see if I can find it
[14:12] <DammitJim> is there a setting somewhere I need to disable? I saw something under 10persistant
[14:13] <DammitJim> or something like that
[14:13] <DammitJim> something in /etc/apt/apt.d or something like that
[14:13] <DammitJim> /etc/apt/apt.conf.d
[14:13] <mhall119> yeah, I think it's /etc/apt/apt/conf.d/10periodic
[14:13] <DammitJim> where it says updates
[14:14] <DammitJim> I guess that's what I enabled when I installed ubuntu server and said I want critical updates?
[14:14] <mhall119> maybe also apt/apt.conf.d/50unattended-upgrades
[14:14] <mhall119> probably
[14:14] <DammitJim> mhall119, I just opened that, but I don't even know what to put on there
[14:15] <DammitJim> I guess my -security line 3 is uncommented
[14:15] <DammitJim> maybe that's it?
[14:15] <mhall119> I think so,yes
[14:16] <mhall119> but I'm just guessing too :)
[14:22] <DammitJim> ok
[14:23] <DammitJim> I couldn't find this information online
[14:23] <DammitJim> I wonder how I can programmatically change this
[14:23] <DammitJim> You see, I am having issues with the boot partition getting filled up
[15:19] <mhall119> DammitJim: /boot or / ?
[15:24] <DammitJim>  /boot
[15:24] <mhall119> I think there's a different config somewhere that says what kernels to keep
[15:26] <DammitJim> oh really?
[15:26] <DammitJim> now, that's very very helpful mhall119 !
[18:28] <Nothing_Much> libnih? lolol
[18:28] <Nothing_Much> is nih supposed to mean something? or is it a joke?
[18:33] <stickystyle> NIH = Not Invented Here, https://en.wikipedia.org/wiki/Not_invented_here. Where did libnih show up? I’d like to name some of my own lib’s that :D
[18:43] <Nothing_Much> stickystyle, Someone I was arguing about Ubuntu last night said Canonical didn't use libg or something, so they made libnih or something.
[18:43] <Nothing_Much> But honestly, that's the whole point of FOSS, there is no issue.
[18:43] <Nothing_Much> And NIH syndrome exists everywhere in FOSS, if Ubuntu did make libnih, then I'd say it's a joke given that most FOSS enthusiasts are also filled with ideas that could be considered "NIH".
[18:48] <Nothing_Much> stickystyle, Nerds are weird.


[07:34] <elacheche> Morning
[08:03] <nabdev> morning
[08:04] <elacheche> wassup!
[08:10] <nabdev> fine working as usualy
[16:22] <Dro__> hi


[02:03] -queuebot:#ubuntu-release- New: accepted node-rollup [amd64] (cosmic-proposed) [0.50.0-1build1]
[03:56] <slangasek> doko: python2.7/arm64 reproducible autopkgtest regression
[03:57] <slangasek> doko, infinity: also, glibc/amd64 fails its autopkgtest with the new binutils
[06:46] <mitya57> Can someone please reject gnome-flashback upload in bionic SRU queue? I want to add one more fix to it.
[16:00] <cpaelzer> slangasek: thanks for the qemu/glibc trigger
[16:01] <cpaelzer> I didn't have the time yet to look in detail, all others so far turned out to be real nova/cinder things fixed by jamespage - so I didn't realize it was glibc this time


[00:53] <lns> for anyone who's interested, i wrote up procedures on how to create mandatory shared/global firefox bookmarks for all users
[00:53] <lns> http://lns.wikidot.com/firefoxglobalbookmarks
[00:53] <lns> this will be the only time i mention it ;)
[00:54] <LaserJock> heh
[02:07] <jsgotangco> yo LaserJock how are things?
[02:08] <LaserJock> interesting
[02:09] <jsgotangco> lol
[02:11] <LaserJock> very very busy
[02:13] <jsgotangco> same here :)
[03:16] <boggystudios> I stepped out for a bit
[03:17] <boggystudios> johnny: What I mean is I want to creat a custom variation of edubuntu with a different theme, custom repository, custom bootsplash, all that jazz
[03:18] <boggystudios> johnny: the end result would be a disc that I can pop in a machine and install a particular school's distro
[03:51] <jsgotangco> nice lp uses postgres
[06:26] <achandrashekar> hello I wanted to point out that smbldap-installer that moquist wrote gave a lot of fits on 7.10 install. However, the how-to-forge guide works flawlessly. The main issue that I have with the isntalled is the soft boot no entry..and I had a lot of trouble with how the installer configures smb.conf. I wanted to point this out because it will leave a system from booting correctly.
[06:27] <achandrashekar> So its a an FYI..and I was able to replicate the issue..everytime i used the installer
[06:27] <achandrashekar> My suggestion is to use the howtoforge guide availble..it works flawlessly
[06:27] <achandrashekar> In addition the ldap-client configuration also has issues.
[06:27] <kgoetz> achandrashekar: have you told moquist about the problem/s?
[06:28] <achandrashekar> since edubuntu primarily makes use of the ldap.conf...it no longer uses lbnssswitch.conf
[06:28] <achandrashekar> so the installer tries to do an install against that.
[06:28] <achandrashekar> i cant get a hold of moquist..because im pretty busy during the day
[06:28] <achandrashekar> but hoping someone could pass this on.
[06:29] <kgoetz> hes just over there *points* - send him a PM
[06:29] <achandrashekar> kgoetz: is that ltsp channel? as in "there"?
[06:30] <kgoetz> achandrashekar: "there" is 'in this channel as we speak'
[06:31] <achandrashekar> kgoetz: sorry a little confused here.. i dont seem to see his name in the channel
[06:32] <achandrashekar> woops i see him
[06:32] <kgoetz> achandrashekar: i can tab complete his name, so he is in here. (unless your not actually talking about moquist )
[06:32] <achandrashekar> no..its moquist indeed.
[06:32] <achandrashekar> just offline i suppose..
[06:33] <achandrashekar> so basically send him a private message?
[06:33] <kgoetz> or email. the key bit is that you need to tell him if his script is busted
[06:35] <achandrashekar> kgoetz: ill be happy to.
[06:35] <achandrashekar> kgoetz: one of the key issues right of the bat, is that slapd.pid is not created and hence the ldappopulate breaks
[06:36] <achandrashekar> but i will definitely let him know
[06:36] <achandrashekar> by email or whatever means
[06:36] <achandrashekar> however... as stated before
[06:36] <achandrashekar> the definitive working guide...the how-to-forge guide works flawlessly
[06:37] <achandrashekar> and is well written.
[06:37] <achandrashekar> and mught save quite a bit of time simply to script that.
[06:37] <achandrashekar> :)
[06:37] <kgoetz> thanks for letting us know :)
[06:37] <achandrashekar> np...i spent a week on that
[06:37] <achandrashekar> and some sleepless nights wonder what I did wrong.
[06:38] <achandrashekar> but I started all over..and the guide that is how to forge worked first time -
[06:39] <achandrashekar> this is what i am referring to - http://www.howtoforge.com/openldap-samba-domain-controller-ubuntu7.10
[06:40] <achandrashekar> and for clients this is VERY IMPORTANT as 7.10 no longer makes use of the libpam.conf or libnss.conf https://help.ubuntu.com/community/LDAPClientAuthentication
[06:40] <achandrashekar> I really think that the main wiki for setup of  ltsp setup such that it uses ldap-auth should refer to those
[06:41] <achandrashekar> and im not sure who to talk to to change or append the guide
[06:41] <achandrashekar> this will keep many people happy in NOT having to spend hours to figure out what the lock up issue is for klog daemon on bootup
[06:41] <achandrashekar> kgoetz: know who appends such guides?
[06:45] <kgoetz> no i dont
[06:46] <achandrashekar> i see....no problem...
[06:46]  * kgoetz had the problem with libpam.conf and libnss.conf too
[06:47] <kgoetz> achandrashekar: actuallyk, ping #ubuntu-doc
[06:47] <kgoetz> and ask them about it
[06:47] <achandrashekar> the last guide and most definitive for infrastructure setup is the following - https://wiki.edubuntu.org/EdubuntuDHCPload-balancingFailover
[06:48] <achandrashekar> However from a strategic stand point of setup for standalones, there are some methodical steps
[06:48] <achandrashekar> Id suggest this - 1) setup up BOTH standalones 2) get smb ldap working with shared home drives 3) do the dhcp failover
[06:48] <achandrashekar> in that order
[06:48] <achandrashekar> ;)
[06:49] <achandrashekar> and hence added to the docs for handbook
[06:49] <achandrashekar> but ill suggest that in ubuntu-doc
[06:49] <achandrashekar> with the afore mentioned links above
[06:50] <achandrashekar> I certainly appreciate all the help though...and the documentation is really what got me figured out.
[06:50] <achandrashekar> Ill post progress of our infrastructure in days to come.
[06:50] <achandrashekar> :)
[07:04] <achandrashekar> kgoetz: a bit quiet in the channel..and I might have to try during the day.
[07:05] <kgoetz> achandrashekar: be patient
[07:05]  * kgoetz off home
[07:05] <achandrashekar> no issues.
[07:06] <achandrashekar> ;)
[07:58] <RichEd> achandrashekar: i suggest you (1) mail ogra & cc sbalneav or (2) edit the wiki page yourself !
[07:58] <RichEd> for option (1) i'll msg you the email addresses
[07:58] <achandrashekar> great.
[07:59] <RichEd> but option (2) is better ... if you've spotted an inconsistency from personal experience, you're the best one to explain to others :)
[07:59] <achandrashekar> and Im considering a bit of write up and I can have it reviewed before publication.
[08:04] <RichEd> achandrashekar: if you accurately describe what you experienced, in such a way that it would have helped you, then that's the best review
[08:04] <achandrashekar> Id be happy to do that
[08:05] <achandrashekar> it should take a day or so..but I will formulate all of my thoughts effectively
[11:55] <ogra> ***** meeting reminder, edubuntu meeting in #ubuntu-meeting in 2min *****
[11:56] <stgraber> right, I'll be there but only for the tech part
[11:56] <stgraber> then I have to go to an edubuntu deployement :)
[11:57] <ogra> heh
[11:57] <ogra> ***** meeting reminder, edubuntu meeting in #ubuntu-meeting starts now *****
[13:48] <xivulon> ogra, stgraber please see http://paste.ubuntu-nl.org/57575/
[14:07] <ogra_cmpc> xivulon, yeah, thats fine
[14:07] <ogra_cmpc> as i said, i wont cry :)
[14:18] <xivulon> ogra_cmpc: sorry for that, will try to make it up to you in the next release
[14:53] <Nubae> is there a reason why some computers would get stuck during the pxe boot process after the ................ done.
[14:53] <Nubae> and then continue after a minute or 2
[14:53] <Nubae> ?
[14:53] <ogra_cmpc> boot without quiet and see what they are doing :)
[14:54] <ogra_cmpc> in the pxe config
[14:54] <Nubae> hmmm yeah didnt think of that
[14:55] <ogra_cmpc> i have seen delays with clocksource detection during kernl unpacking
[14:55] <ogra_cmpc> check for that
[15:44] <alumno10> hi all, I tried a coreduo as a client and youtube still see slow
[15:44] <alumno10> the server is a amd 1,2ghz but now i was using just core duo client, so . whats the problem?
[16:37] <LaserJock> I suppose we had the early meeting today?
[16:39] <ogra_cmpc> yup
[16:40]  * ogra_cmpc wonderws what he did to his classmat ... its unusual fast
[16:40] <stgraber> :)
[16:40] <LaserJock> ogra_cmpc: I uploaded 5 squeak packages to NEW last night
[16:40] <LaserJock> I had to do quite a lot of work
[16:40] <ogra_cmpc> yeah, saw that
[16:40] <ogra_cmpc> many many thanks for that
[16:40]  * ogra_cmpc hugs LaserJock
[16:42] <LaserJock> I even put in transitional packages and did a test upgrade
[16:42] <LaserJock> it actually worked ;-)
[16:43] <ogra_cmpc> wow
[16:43] <ogra_cmpc> !
[16:43] <ogra_cmpc> you see me impressed
[16:43] <LaserJock> it'll close 10 bugs
[16:43] <LaserJock> that was fun to put in the changelog ;-)
[16:43] <LaserJock> anyway, hopefully the archive admins take it
[16:44] <LaserJock> it's a messy set of packages
[16:46] <LaserJock> and I *finally* got to send a "It's all fixed" email to gcompris-devel
[16:46] <LaserJock> and went through their "test suite" on Hardy and everything's looking pretty good
[19:32] <alumno10> hi all
[19:32] <alumno10> is there a problem with intel gigabit integrated adapter and ubuntu?
[19:42] <alumno10> wake up all
[19:48] <johnny> ogra_cmpc, !
[19:48] <johnny> initial patch for fixing sabayon
[19:48] <johnny> or rather.. sabayon in xnest
[19:51] <johnny> libxklavier patch
[20:09] <alumno10> johnny, i just have to change chroot kernel by a newer one?
[20:10] <alumno10> *have->can
[20:10] <alumno10> english isn't my main language
[20:12] <johnny> huh
[20:12] <johnny> to a newer one ? sure?
[20:12] <johnny> but why are you asking me?
[20:12] <johnny> i don't really know how
[20:15] <johnny> ogra, ogra_cmpc http://bugzilla.gnome.org/show_bug.cgi?id=516318
[20:15] <ubotu> Gnome bug 516318 in plugins "crash when run inside xnest (keyboard plugin)" [Normal,New]
[20:15] <johnny> pawtch attached
[20:17]  * ogra_cmpc hugs johnny
[20:18] <alumno10> somebody can watch fluidly youtube in clients?
[20:20] <johnny> i'd say there are two real bugs that need to be solved for sabayon to be usable truly
[20:21] <johnny> at least.. registered so far that is
[20:21] <johnny> one, is allowing panel applets to be removed and added.. or modified
[20:21] <johnny> the other is the mozilla bookmarks merge
[20:22] <johnny> i'm going to be focusing on the panel applets one when i get more time
[20:22] <ogra_cmpc> but both were not in former versions
[20:22] <johnny> ?
[20:22] <ogra_cmpc> and both are whishlist items
[20:22] <johnny> they've been active bugs up til now
[20:22] <ogra_cmpc> right
[20:22] <johnny> they are not wishlist imo
[20:23] <ogra_cmpc> but they are no regressions to what we had in former releases
[20:23] <johnny> that is true
[20:23] <ogra_cmpc> since both are features that didnt work yet
[20:23] <johnny> but that doesn't satisfy me :)
[20:23] <ogra_cmpc> right, but if the fix requires big changes they are unlikely to get past the release amangers
[20:26] <ogra_cmpc> the firefox import sounds like a critical candidate here
[20:26] <johnny> sure, but at least i will be providing a deb for seperate usage
[20:26] <johnny> for folks who really need the new features
[20:26] <ogra_cmpc> well, lets at least try to get them in
[20:27] <ogra_cmpc> but its hard to convince the guys that its not a new feature but a bug :)
[20:28] <johnny> as a non ubuntu dev, i only care that ubuntu users have the option to get the newer one, if they want the good stuff :)
[20:29] <ogra_cmpc> as ubuntu dev i care that all our users benefit form a fix :)
[20:29] <ogra_cmpc> so if its possible to get it in it should ...
[20:29] <johnny> well sure
[20:30] <johnny> cuz that will help uncover any more bugs :)
[20:30] <johnny> many*
[20:33] <johnny> i'm going to email scotty about the local apps thing
[20:33] <johnny> i have a friend who wants help me hack it
[20:33] <johnny> can you send me his email in a pm?
[20:34] <ogra_cmpc><EMAIL_ADDRESS>[20:34] <ogra_cmpc> no need for pm :)
[20:38] <johnny> ok. thanks ogra
[20:38] <ogra_cmpc> i'll start putting time into it as well right after release
[20:39] <johnny> so, what is the best howto to use usptream ltsp for development on?
[20:40] <johnny> been wondering if i should help dberkholz with ltsp in gentoo, as a way to get more of a feeling on how it ties together at a deeper level
[20:41] <ogra_cmpc> well, the upstream code is the deepest level you can get to i guess
[20:41] <ogra_cmpc> everuything deeper depends on the knowledge of your os
[20:41] <ogra_cmpc> since ltsp5 is all about distro integration
[20:42] <ogra_cmpc> so work on the distro you are most familiar with
[20:42] <ogra_cmpc> that makes most sense
[20:43] <johnny> dberkholz prolly doesn't have time to truly work on it, he just took over the PR position at gentoo it seems
[20:43] <johnny> plus whatever he does for a day job :)
[20:43] <ogra_cmpc> well, he started something recently ... with vagrant
[20:43] <johnny> and maintaining most of the sci packages for gentoo
[20:43] <johnny> yes, the hackfest
[20:43] <ogra_cmpc> right
[20:44] <johnny> i'll be finding more about that
[20:44] <ogra_cmpc> that should ahve some outcome
[20:44] <johnny> i plan on deploying 99% of ltsp installs on ubuntu
[20:44] <ogra_cmpc> i think he submitted a bunch of code upiostream
[20:44] <johnny> but, i have spent the most time actually using gentoo
[20:44] <ogra_cmpc> i thinnk i saw a commit carrying his name
[20:45] <ogra_cmpc> well, the actual final implementation of gentoo will very likely be massively different from ubuntus
[20:45] <ogra_cmpc> the way you handle initramfs and netbooting, the way you handle the initscripts etc
[20:46] <johnny> we'll see what we can do to keep it as much commonality as possible
[20:46] <ogra_cmpc> right
[20:46] <ogra_cmpc> i think the common stuff is already quite fine after debian, ubuntu and redhat went over it
[20:47] <ogra_cmpc> i dont think you will find much stuff that would be disturbing
[20:47] <johnny> hmm..so.. maybe i should have dev setup for both then..
[20:47] <ogra_cmpc> the tricky bits are the core pieces i listed above
[23:40] <supreme> hi all
[23:40] <supreme> im alumnoXX


[15:28] <ogra_> hmm, how would i get xfsprogs-udeb installed on a running mini.iso install
[15:29] <xnox> tell anna to fetch it
[15:30] <xnox> (no joke)
[15:30] <ogra_> anna-install xfsprogs-udeb only gets me a black shell
[15:30] <ogra_> i.e. it just resets the terminal
[15:30] <xnox> there is a kernel/d-i pressed option to fetch optional udebs.
[15:31] <ogra_> well, i dont want to reboot :/
[15:31]  * ogra_ tries to recover data from an old server md raid with xfs ...
[15:32] <ogra_> and obviously it wants me to run xfs_repair before i mount
[15:34]  * ogra_ doesnt get why we ship mkfs.xfs by default but not the fscks tools for it
[16:15] <cjwatson> anna-install xfsprogs-udeb probably won't tell you it's done anything, but the udeb contents look right.
[16:16] <cjwatson> Though indeed we probably ought to ship checking tools.  We probably don't because d-i itself doesn't use them currently, and nobody ever cared enough about xfs to fix it up for rescue purposes.
[16:17] <cjwatson> That is, anna-install will install that package even if it doesn't say anything.  (Unless you're before the "retrieving additional components" stage in the installer, in which case it will simply queue it for installation when you get that far.)
[16:27] <ogra_> yeah, i found it already gets installed ... but only has mkfs.xfs inside
[16:27] <ogra_> i helped myself with making a tarball from the actual deb contents ... all fine now
[16:27] <ogra_> i dont get what has ever ridden me to use xfs ...