[12:16] <BenC> kylem: works on my pata_amd
[12:16] <kylem> lazka, er, maybe?
[12:16] <lazka> kylem, what should be the dev name?
[12:16] <kylem> mount -t iso9660 /dev/scd0 /mount
[12:16] <trejack> FYI my problem persists with a new install from today's daily build.
[12:17] <Nafallo> /dev/cdrom
[12:17] <BenC> trejack: Try: http://people.ubuntu.com/~kyle/kernels/feisty/linux-image-2.6.20-15-generic_2.6.20-15.27_i386.deb
[12:17] <kylem> trejack, what problem?
[12:17] <BenC> kylem: trejack was also having the pata_amd issue
[12:17] <kylem> ok
[12:17] <lazka> no medium found..
[12:17] <BenC> lazka: do you have a disk in there?
[12:17] <trejack> I can't.  Wiped my working 2.6.20-17 install
[12:18] <lazka> yeah, i will  look for a cleaner one..
[12:18] <trejack> Wait a sec - I can chroot in from my edgy
[12:18] <moodydeath> is it the correct device, laska? ... could be scd1, too, if you got more
[12:18] <trejack> I'll be back
[12:19] <lazka> ok, /dev/cdrom is my dvd-drive
[12:19] <lazka> and its working
[12:20] <lazka> but i cant find the lite-on
[12:21] <lazka> kylem, it makes some noise but doesnt spin up
[12:21] <BenC> [   30.987575]  scsi 1:0:1:0: CD-ROM            PLEXTOR  DVD-ROM PX-116A2 1.00 PQ: 0 ANSI: 5
[12:22] <BenC> that's the only thing I see connected
[12:22] <kylem> it only found one ATAPI device
[12:22] <BenC> There is only /dev/sr0, no /dev/sr1
[12:22] <kylem> and didn't even whine about the rest
[12:22] <kylem> are you sure it's cabled properly?
[12:23] <heno> kylem: are you building an amd64 version for testing as well?
[12:24] <lazka> kylem, should be, i'll check with 20.13 again if it still works there, k?
[12:24] <BenC> heno: I am, I'll upload it when it's done
[12:24] <kylem> ok
[12:24] <heno> ok, cool
[12:27] <lazka> kylem, bad news, works ok with 20.13
[12:28] <BenC> lazka: can you pastebin dmesg from .13?
[12:29] <lazka> http://pastebin.ubuntu-nl.org/15681/
[12:29] <lazka> [   32.828189]  hdc: LITE-ON LTR-52246S, ATAPI CD/DVD-ROM drive
[12:29] <BenC> kylem: amd64 is uploading to my ~/, I'll let you put it next to yours
[12:29] <BenC> hdc?!
[12:30] <kylem> you must have shuffled pci ids?
[12:30] <lazka> umh what?
[12:30] <kylem> brb.
[12:30] <BenC> -13 -> -14 == ata update
[12:30] <BenC> probably moved from amd ide to pata_amd
[12:30] <Nafallo> pata_amd still used hd? in -13 for me aswell
[12:31] <Nafallo> or that :-)
[12:31] <BenC> brb
[12:34] <lazka> it did say that in the bugreport...
[12:45] <BenC> kylem: if the problem we're having is just in pata_amd, maybe switching back to the amd IDE driver is best
[12:45] <BenC> looks like the quick fix didn't take care of all the problems
[12:49] <trejack> No good for me, either.  (Iused the -15.27 kernel).  The dmesg is at http://librarian.launchpad.net/7331329/dmesg2.txt
[12:50] <BenC> still showing exceptions for trejack too
[12:50] <trejack> Don't know if this will help or not, but when I booted into the live cd, it at first couldn't use any of my existing partitions.
[12:51] <trejack> I reformated the sda3 one using gparted, and it completed in seconds, and my sda1 partition was suddenly available, as well
[12:52] <BenC> trejack: doing a new build to revert back to amd74xx driver
[12:52] <BenC> lazka, moodydeath: you guys willing to test another kernel in about 30 minutes?
[12:53] <lazka> BenC: yep
[12:53] <trejack> I'll check back in 30.  Thanks
[12:53] <moodydeath> yep
[12:53] <BenC> thanks, build started, will post here when it's done
[01:09] <moodydeath> is this the new one ?
[01:09] <lazka> moodydeath: no
[01:09] <moodydeath> kk :)
[01:09] <moodydeath> ah ... should read the whole topic ... -_-
[01:10] <lazka> there is so much crap on TV at night :P omg
[01:21] <BenC> builds are done, getting ready to upload
[01:22] <defendguin> hey BenC
[01:22] <defendguin> apparently the mmc card reader fix isn't working
[01:23] <BenC> it was reported to work for many people
[01:23] <defendguin> hmmm
[01:23] <BenC> it doesn't resolve all mmc issues
[01:23] <defendguin> i wish i had a card on me
[01:23] <BenC> it was just one major regression
[01:24] <BenC> 53b205c5fbe264a700454a4f5416d0a8  linux-image-2.6.20-15-generic_2.6.20-15.26_amd64.deb
[01:24] <BenC> 7a5f4a0801be29c9c614b3d1a673edf2  linux-image-2.6.20-15-generic_2.6.20-15.26_i386.deb
[01:24] <BenC> http://people.ubuntu.com/~bcollins/kernels/feisty-release/
[01:24] <moodydeath> dl running :D
[01:25] <BenC> note that kernel changes pata_amd back to amd74xx, so your devices will go to hdX
[01:25] <BenC> moodydeath: it's still being uploaded
[01:25] <moodydeath> hmm
[01:25] <BenC> probably be completed in about 5 minutes
[01:25] <BenC> probably less
[01:25] <MrNOKIA> is it a 32 or a 64 bit version ?
[01:25] <moodydeath> i'll f5 ;)
[01:27] <MrNOKIA> i'm sorry, i must be missing something
[01:27] <MrNOKIA> i'm using linux-image-2.6.20-15-generic_2.6.20-15.27_i386.deb
[01:27] <trex37> what's the file size?
[01:28] <MrNOKIA> the new file is .26 ?
[01:28] <MrNOKIA> 21 Mb
[01:29] <lazka> it's ready
[01:29] <MrNOKIA> yes,but...
[01:29] <MrNOKIA> why is it .26 now ?
[01:30] <MrNOKIA> i.m on .27 for about an hour
[01:31] <moodydeath> .27 was a version from kyle
[01:31] <MrNOKIA> kile ?
[01:31] <MrNOKIA> kyle ?
[01:33] <moodydeath> BenC: kernel boots ... as fast as -12 did
[01:33] <moodydeath> testing drives
[01:34] <MrNOKIA> moodydeath, what is kyle ? should i try the new kernel now ?
[01:34] <moodydeath> scd0 & scd1 working :D
[01:35] <moodydeath>  http://people.ubuntu.com/~kyle/kernels/feisty/ <-- here is the .27 ...  but i think the .26 which was released some minutes ago is the new one
[01:36] <lazka> Ubuntu 2.6.20-15.26-generic
[01:36] <lazka> http://pastebin.ubuntu-nl.org/15700/
[01:36] <lazka> everything back to normal
[01:37] <moodydeath>  http://pastebin.ubuntu-nl.org/15701
[01:37] <moodydeath> me, too :D
[01:38] <lazka> BenC: is it intentional that ivtv isn't working with your builds?
[01:38] <lazka> it worked with kylem's build
[01:39] <trejack> Yay!  That one did it
[01:39] <trejack> what do you need from me?
[01:44] <BenC> lazka: no, I didn't change that
[01:44] <BenC> trejack: dmesg please
[01:44] <lazka> BenC: what do you mean?
[01:44] <BenC> lazka: ivtv
[01:45] <cjwatson_> lazka: from your log earlier it looked like you were just missing the firmware
[01:45] <cjwatson_> iirc
[01:45] <lazka> BenC: your build is 2 MB smaller..
[01:45] <BenC> lazka: could be a left out the firmware
[01:45] <BenC> quirk in the build
[01:46] <lazka> thats what i mean..
[01:46] <BenC> lazka: try copying it from /lib/firmware/linux-image-2.6.20-13-generic/
[01:46] <BenC> it wont happen in the final build
[01:46] <lazka> ok, thanks
[01:46] <BenC> I trimmed some things out of the build to speed things up
[01:46] <BenC> mainly linux-headers, linux-debug, and apparently firmware
[01:47] <lazka> ah, i see, however.. i'm going to bed now, already 2 am here.
[01:47] <BenC> lazka: thanks
[01:47] <lazka> gn8 all
[01:47] <BenC> Mithrandir, cjwatson: The three testers we had that reported the problem have reported success
[01:47] <BenC> the fix was reverting back to amd74xx IDE driver instead of pata_amd
[01:47] <cjwatson> right, do you have the diff or is it in git?
[01:48] <BenC> so it's a relatively safe and isolated fix
[01:48] <BenC> amd74xx was actually being used up until about 5 weeks ago
[01:48] <cjwatson> I'm actually just going to bed, but I am happy to be woken up once it's uploaded
[01:48] <BenC> will be done in about 10 minutes
[01:48] <cjwatson> ok
[01:48] <cjwatson> send me an SMS on my mobile number?
[01:49] <BenC> cjwatson: Ok
[01:49] <BenC> cjwatson: wait, I can't send Intl SMS
[01:50] <BenC> unless you have an email that redirects
[01:51] <BenC> trejack, lazka, moodydeath: thanks for the testing!
[01:51] <moodydeath> np :)
[01:51] <MrNOKIA> np ?
[01:51] <BenC> the past few days, we've been very fortunate to have folks coming around to bear the burden of our test builds
[01:51] <BenC> MrNOKIA: np == no problem
[01:52] <BenC> MrNOKIA: were you having the pata_amd problems?
[01:52] <moodydeath> will there be something like a final version, that will need a test ?
[01:52] <MrNOKIA> sorry
[01:52] <MrNOKIA> i knew that
[01:52] <BenC> moodydeath: by tomorrow there should be something in your update manager :)
[01:52] <MrNOKIA> I guess
[01:52] <BenC> MrNOKIA: could you test the kernel in the topic URL?
[01:53] <BenC> I'm sure it will work for you, if that's in fact the issue you were having
[01:53] <MrNOKIA> I could'nt boot the new kernel untill the .25 version came up
[01:53] <trejack> http://librarian.launchpad.net/7331974/dmesg3.txt
[01:53] <MrNOKIA> i posted info on the dedicated thread
[01:53] <MrNOKIA> hope it helped
[01:54] <MrNOKIA> my nick is pretty much the same as on ubuntuforums :)
[01:54] <BenC> MrNOKIA: ok, thanks
[01:54] <BenC> trejack: excellent, thanks
[01:54] <BenC> cjwatson, Mithrandir: kernel away
[01:54] <trejack> Thank you!
[01:55] <trejack> I must say I was intimidated by all of this at first, but it's been a pleasure...
[01:55] <MrNOKIA> BenC: a new kernel ?
[01:56] <MrNOKIA> i see only the 15 april .26 version
[02:08] <defendguin> got it all fixed?
[02:23] <BenC> defendguin: looks that way
[02:23] <BenC> MrNOKIA: the one in my dir in the URL is the same as the one I uploaded (sans some firmware)
[04:17] <gnufied> extended attributes are enabled on stock ubuntu dapper kernels?
[04:17] <gnufied> if yes, then how do i find out?
[04:19] <crimsun> grep -i xattr /boot/config-$(uname -r)
[04:19] <gnufied> thanks, so its enabled.
[04:54] <yoasif> i just saw the post on ubuntuforums about the sata_nv issue... how can i help?
[04:54] <mjg59> Should be fixed now
[04:55] <mjg59> See the topic
[04:55] <yoasif> ty
[04:56] <yoasif> hmm, 15-27 is listed on ubuntuforums, should i get that, or the one in the topic?
[04:56] <yoasif> (i am experiencing the PATA issues)
[04:57] <mjg59> 15.27 is the latest, I believe
[04:57] <mjg59> It's worth a go
[04:57] <yoasif> ok
[05:00] <yoasif> mjg59: do you have any ideas what the problem might be if every once in a while, the screen goes all wonky (the screen gets compressed down, and a load of copies of the screen get patterned, and skewed)
[05:00] <yoasif> ssh doesn't work, and i've tried just using vesa
[05:00] <mjg59> No
[05:01] <yoasif> heh... i'm really wondering how i can describe the issue properly.
[05:18] <keturn> sounds a little like your graphics card aesploded
[05:18] <yoasif> it's onboard
[05:18] <yoasif> and a pretty new mobo
[06:29] <cjwatson> -15.27 kernel belatedly accepted - builds will start running as soon as I can manage it
[06:30] <kylem> thanks colin
[06:32] <cjwatson> http://librarian.launchpad.net/7331974/dmesg3.txt (from trejack earlier) has some DriveReady SeekComplete Error stuff before the kernel finally gets hda going - is that unrelated?
[06:32] <kylem> unlikely
[06:33] <kylem> oh, yeah
[06:33] <mjg59> Likely that it's unrealted, by the looks of it
[06:33] <kylem> i thought hda was the missing cdrom
[06:33] <mjg59> BadCRC is either complete timing fuckup, or bad cable
[06:33] <kylem> likely a 40pin cable
[06:34] <mjg59> But, hell, drivers/ide has never really worked
[06:34] <cjwatson> hda has a partition table in that dmesg so it's not a cdrom
[06:34] <kylem> right
[06:34] <mjg59> It ends up coming up in pio mode
[06:34] <kylem> works by magic
[06:34] <kylem> sheer force of will
[06:34] <mjg59> Not ideal, but it'll do
[06:34] <cjwatson> ha
[06:34] <kylem> hmm, mark lord lives in the same city as me
[06:35] <kylem> i can walk over and beat him up if you want
[06:35] <kylem> :P
[06:35] <cjwatson> ok, publisher's running, I'm off back to sleep
[06:35] <mjg59> Oh, that system looks shitted anyway
[06:35] <kylem> cjwatson, night
[06:35] <mjg59> [   20.079279]  ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[06:35] <mjg59> [   20.079317]  ...trying to set up timer (IRQ0) through the 8259A ...  failed.
[06:35] <mjg59> [   20.079320]  ...trying to set up timer as Virtual Wire IRQ... failed.
[06:35] <mjg59> [   20.119013]  ...trying to set up timer as ExtINT IRQ... works.
[06:35] <mjg59> Never seen that on an nvidia board before
[06:36] <cjwatson> phone me if it all blows up, and I'll try not to fall straight back to sleep again :-/
[06:36] <cjwatson> Mithrandir has it set up so that the kernel builds on palmer this time
[06:37] <mjg59> cjwatson: The errors there don't look related to any of the HPA/libata stuff
[06:38] <cjwatson> ok, thanks
[07:24] <bdgraue> cjwatson: linux-image-2.6.20-15-generic_2.6.20-15.26_i386.deb  works for me
[08:40] <Nafallo> kylem: my server seems to have kept itself from hanging after I removed irqpoll :-).
[09:17] <crimsun> BenC: I've emailed you a tested and verified patch for #105582. Please consider applying it to avoid a regression from dapper.
[09:19] <Mithrandir> crimsun: too late, but it should go into an SRU
[09:20] <crimsun> Mithrandir: whatever you guys [have]  decide[d]
[09:21] <Mithrandir> crimsun: sorry. :-/
[09:39] <benh> crimsun: here ? :-)
[09:39] <crimsun> yep.
[09:39] <benh> ok, so it's indeed Version: 2.6.20-15.25
[09:40] <benh> and it blows up when moving the mouse
[09:40] <benh> on a Quad G5
[09:40] <benh> linux-image-2.6.20-15-powerpc64-smp, in console mode, minimum install (no X, no gpm)
[09:40] <benh> I don't have a hardcopy of the crash yet, it crashes at irq time, so no log
[09:40] <benh> backtrace shows that it comes from usb -> input -> evdev
[09:41] <benh> and it might be blowing up in do_gettimeofday() which would be VERY strange
[09:41] <benh> are there some known ubuntu patches in that area ?
[09:43] <benh> crimsun: yup, I think BenC is asleep :-( pung him already on some other channel, didn't help
[09:44] <benh> I'm a bit lost with launchpad, how do I look at the bugs reported for a given package ?
[09:44] <benh> https://launchpad.net/ubuntu/+source/linux-source-2.6.20 seems to indicate that a .27 is out
[09:44] <benh> though it hasn't hit au.archive.ubuntu.com
[09:45] <benh> might be worth for me trying to dig that and check before filing a bug report
[09:45] <crimsun> https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bugs
[09:46] <benh> hrm.. I don't see it
[09:46] <benh> me gets the source and have a look how on earch do_gettimeofday() could crash ...
[09:48] <Mithrandir> -15.27 probably won't hit au.archive for another couple of hours, but you can get it off archive.ubuntu.com or launchpad.
[09:49] <benh> yup, I'll try that too
[09:50] <Mithrandir> https://launchpad.net/+builds/+build/318987/linux-image-2.6.20-15-powerpc64-smp
[09:51] <benh> not on archive's Package file yet, I'll wait and look at hte source in the meantime
[09:51] <benh> ok
[09:51] <benh> that would do too I suppose :-0
[09:51] <Mithrandir> I really can't believe we wouldn't have massive amounts of bug reports about that bug, unless there's something special with your hardware.
[09:52] <benh> nothing special that I can see... just a fairly ordinary quad G5
[09:52] <`sam`> does -25.27 need testing for sata_nv or is it known to work? because i'm installing now...
[09:52] <benh> anyway, have to run, will be back later & investigate
[09:53] <benh> have 2 disks though and using an lvm but heh... that shouldn't matter :-)
[09:53] <bdgraue> 15-26 is running fine with sata_nv
[09:53] <bdgraue> -15.26 i mean
[09:54] <Mithrandir> `sam`: we want as much testing as we can get on the latest kernel (-15.27).  Even if previous ones worked fine, we want to make sure there are no regressions.
[09:54] <Mithrandir> `sam`: so if you have a bit of time to spare, it's much appreciated.
[09:54] <bdgraue> Mithrandir: i'll try the new -15.27 too
[09:55] <`sam`> ok, i've had -15.25 installed but have still been running -14.23... going to reboot now and see
[10:03] <`sam`> well -15.27 boots for me
[10:03] <`sam`> took me a few minutes because i had changed my xorg.conf about 30 minutes ago and had messed it up
[10:04] <Mithrandir> `sam`: good to hear, CD-ROM/DVD-ROM and all works too?
[10:06] <`sam`> yeah i just tested a dvd and it started playing in totem
[10:07] <Mithrandir> great
[10:07] <Mithrandir> please tell us if you have other (kernel-related) regressions?
[10:10] <bdgraue> Mithrandir: where can i get the 15-27?
[10:10] <`sam`> like what? anything specific you want me to check out?
[10:12] <bdgraue> are the 2.6.20-15.27 not available for i386 yet?
[10:13] <`sam`> bdgraue, have you checked in update-manager? i just found it there about 25 minutes ago
[10:14] <bdgraue> `sam`: not here i have archive.ubuntu.com
[10:14] <Mithrandir> bdgraue: are you on i386?  If so, the kernel is not done yet.
[10:15] <bdgraue> ok then
[10:15] <bdgraue> i'll wait :-)
[10:16] <macd> palmer is cooking hot ;)
[10:17] <bdgraue> Status:	Currently building
[10:17] <bdgraue> :-)
[10:17] <`sam`> Mithrandir, was the drive detection the main problem? if there's anything else i could test i've got time... even though i don't know what all i'm looking for :)
[10:21] <Mithrandir> `sam`: yes, the problems were all related to drive detection and also some HPA.
[10:22] <Mithrandir> can you run dmesg | grep hpa in a shell and paste the contents somewhere?
[10:23] <`sam`> it's only 2 lines, can i paste it here?
[10:24] <Mithrandir> sure
[10:24] <`sam`> [   24.478810]  ata1.00: ata_hpa_resize 1: sectors = 312500000, hpa_sectors = 312500000
[10:24] <`sam`> [   24.490762]  ata1.00: ata_hpa_resize 1: sectors = 312500000, hpa_sectors = 312500000
[10:25] <Mithrandir> ok, and no scary errors of any kind in dmesg?
[10:27] <`sam`> i don't think so, but i don't know what this is:
[10:27] <`sam`> [   25.958194]  ATA: abnormal status 0x7F on port 0x0000000000010967
[10:29] <Mithrandir> hm
[10:30] <Mithrandir> not great, but if it all works, I wouldn't worry too much
[10:37] <`sam`> what is the hpa exactly? i'm just finding stuff about thinkpads...
[10:37] <benh> Mithrandir: crash still happens with .27
[10:37] <benh> Mithrandir: will investigate
[10:39] <benh> Mithrandir: do you guys have extra patches on top of mainline like some of the -rt or clock sources stuff ? some of that is known to introduce fancy breakage on ppc
[10:40] <benh> (still d/l the source on my crappy link here)
[10:40] <cjwatson> `sam`: http://en.wikipedia.org/wiki/Host_Protected_Area
[10:40] <Mithrandir> benh: we have lowlatency, but it's not enabled in the default kernels.
[10:40] <benh> k
[10:41] <cjwatson> our kernel's in git if that helps
[10:41] <Mithrandir> benh: I'm not a kernel hacker, so I'm not sure what other patches have been brought in.
[10:41] <benh> ok, because the scary thing is ... there is -no way- such an error could happen in gettimeofday on normal mainline
[10:42] <benh> unless there have been kernel memory corruption :-(
[10:42] <cjwatson> http://git.kernel.org/?p=linux/kernel/git/bcollins/ubuntu-feisty.git;a=summary
[10:43] <benh>  ... or it's passed a crap argument
[10:43] <benh> which is probably the likely cause... need to disasm to see where exactly the crash occurs
[10:43] <cjwatson> Mithrandir: -15.27/i386 is in accepted, if you hadn't already noticed; feel like accepting d-i?
[10:43] <benh> I wounder if stupid mousemu could be causing it
[10:48] <Mithrandir> cjwatson: ah, just got there then, I'll accept it
[10:49] <benh> Mithrandir: ok, if you kill mouseemu, it doesn't crash
[10:49] <Mithrandir> is mouseemu kernel mode?
[10:49] <benh> Mithrandir: at this point, I'm about 99% convinced it's some crap in uinput vs. 32 bits apps on 64 bits kernels
[10:50] <benh> Mithrandir: no, but it uses some whacky kernel interfaces (uinput) which I wouldn't be surprised at all is broken
[10:50] <benh> Mithrandir: there is a long tradition of brokenness in the input layer userland interfaces, especially vs 32/64 bits
[10:50] <Mithrandir> hmkay.
[10:50] <benh> Mithrandir: it's likely that running a 32 bits mouseemu on a 64 bits x86 will crash too
[10:51] <benh> Mithrandir: I'll have to investigate in more details but can't do that tonight, in the meantime, it might be worth (if possible) to disable mouseemu by default on powerpc64
[10:51] <Mithrandir> we don't support 64 bit kernels and 32 bit userland on x86_64, so that's not really that important.
[10:51] <benh> Mithrandir: hehe, fair enough :-)
[10:51] <Mithrandir> "you run this and it breaks?  You get to keep both pieces."
[10:52] <benh> Mithrandir: well, I know powerpc isn't officially supported anymore.. but if you guys want to avoid that problem, the short term band-aid is to disable mouseemu on 64 bits powerpc's
[10:52] <Mithrandir> cjwatson: ^^ ; your code, your call, I'm not sure what's a reasonable direction to go in from here.
[10:52] <benh> Mithrandir: want me to file a launchpad entry ?
[10:52] <Mithrandir> benh: yes, a bug would be good.
[10:52] <benh> Mithrandir: I'll try to debug that properly later, I'll be away for most of next week though
[10:52] <Mithrandir> benh: yes, I'm trying to think of a way to not end up saying "sorry, ppc is SOL".
[10:52] <benh> Mithrandir: :-)
[10:53] <benh> Mithrandir: well... it would hit ps3
[10:53] <Mithrandir> it would, which is bad.
[10:53] <Mithrandir> I'm wondering if we can do it in an SRU or not..
[10:53] <benh> I'd say just don't install mousemu by default on 64 bits ppc's ... I suppose you install it by default bcs of 1 buttons apple mice...
[10:54] <benh> anyway, I'll file a launchpad entry tonight so it's at least tracked before I go
[10:54] <benh> I'll try to find out what's wrong in the kernel later
[10:56] <cjwatson> Mithrandir: wah, need to do that before d-i goes in
[10:56] <cjwatson> Mithrandir: can you reject it temporarily?
[10:58] <cjwatson> benh: one-button mice> right, the old sysctl approach isn't available on x86 for Intel Macs and I wanted to have the same scheme across architectures
[10:58] <cjwatson> it was working fine for me on 32-bit powerpc :-/
[10:58] <benh> cjwatson: faiir enough
[10:58] <benh> cjwatson: yeah, well, uinput is a pile of poo unfortunately
[10:58] <benh> cjwatson: I'll check if the problem is still in upstream 2.6.21-whatever-git-of-the-day first
[10:58] <cjwatson> Mithrandir: I've rejected debian-installer so that I can squeeze hw-detect in front
[10:59] <cjwatson> benh: the powerpc64 option sounds reasonable
[10:59] <benh> another option might be to build it as a 64 bits binary :-) if the bug is what I think, that might work
[10:59] <cjwatson> can't do that at this point
[10:59] <cjwatson> it's the same binary package on powerpc32 and powerpc64, would involve massive fiddling
[10:59] <cjwatson> also we're right at the wire
[11:00] <cjwatson> literally if this had been half an hour later it would have been too late ;)
[11:00] <benh> heh
[11:00] <benh> I knew it was a good idea to try out fesity on this g5 :-)
[11:01] <cjwatson> meh, this means I have to figure out whether the running system is ppc64
[11:01] <benh> I've been running it on the laptop for some time, had minor issues, but overall good
[11:01] <cjwatson> arch_get_kernel_flavour () {
[11:01] <cjwatson>         CPU=`grep '^cpu[[:space:] ] *:' "$CPUINFO" | head -n1 | cut -d: -f2 | sed 's/^ *//; s/[, ] .*//' | tr A-Z a-z`
[11:01] <cjwatson>         case "$CPU" in
[11:01] <benh> cjwatson: ugly way: check /proc/ppc64 :-)
[11:01] <cjwatson>                 power3|i-star|s-star|power4|power4+|ppc970*|power5|power5+|cell)
[11:01] <cjwatson>                         family=powerpc64
[11:01] <benh> nah
[11:01] <cjwatson> will have to duplicate crap like that I guess
[11:01] <benh> don't test the cpu model
[11:01] <cjwatson> benh: huh, that actually exists?
[11:01] <benh> that's too ugly for words
[11:01] <cjwatson> I know, but it's all we had
[11:01] <benh> cjwatson: it does in 2.6.20 :-0
[11:01] <cjwatson> neat
[11:02] <benh> let me dbl check it does on your kernel...
[11:02] <cjwatson> the code's there, but I'm no expert
[11:03] <benh> it does
[11:03] <benh> either that or you check for uname -a containing powerpc64
[11:03] <benh> I'm sure there are better ways :-)
[11:03] <benh> but you should never have to check for individual cpu models
[11:03] <benh> anyway, anything that works for you...
[11:04] <cjwatson> might change that at some point, cpuinfo testing is useful though because of the automatic test framework there
[11:04] <cjwatson> could probably teach it about uname output if it doesn't know already
[11:04] <cjwatson> anyway, I'll [ ! -d /proc/ppc64 ]  in hw-detect, thanks
[11:06] <benh> yah, it's dir with various crap in it
[11:06] <benh> we can't really remove it because of some stupid stuff relying on it
[11:07] <benh> so it will stay a bit longer...
[11:07] <benh> anyway, use whatever is best for you
[11:07] <benh> btw, I was impressed how good the installer was vs. setting up yaboot
[11:07] <benh> I was installing on sdb, with lvm & all, sda had my debian stuff etc..
[11:07] <benh> and the installer figured it all out, and setup yaboot.conf entries for my sda stuff too, neat !
[11:08] <cjwatson> Mithrandir: could you review hw-detect 1.45ubuntu5 to work around benh's bug?
[11:08] <cjwatson> then binaries of that need to be accepted before re-accepting debian-installer
[11:08] <Mithrandir> not in the queue yet, but yes, will do in two minutes
[11:08] <cjwatson> benh: yeah, the os-prober stuff for detecting other systems is nice
[11:09] <cjwatson> still keep getting the odd report of ofpath glitches
[11:09] <benh> yeah, for some reason, I didn't hit those tho
[11:09] <benh> (I was expecting to :-)
[11:09] <benh> I think it re-used my boot partition on sda which is probably why it worked
[11:10] <cjwatson> we do have a couple of ofpath patches, think I sent them to Debian a while back
[11:10] <cjwatson> not entirely sure they're right on all systems though
[11:11] <benh> I'm filing a launchpad entry for the kernel bug so we can track it
[11:11] <cjwatson> had a report the other day which suggests not, though I haven't seen the /proc/device-tree/ tarball for it yet
[11:12] <cjwatson> thanks. so you reckon it's lack of 64/32-bit thunking in the uinput ioctls?
[11:13] <benh> it's either that or a bug in the thunking... either way, it shouldn't crash the kernel :-)
[11:13] <Mithrandir> are those ioctls available to the user?  If so, we should get this fixed in a security upload.
[11:13] <cjwatson> Mithrandir: yes, mouseemu is userspace
[11:13] <cjwatson> oh to non-root you mean?
[11:13] <Mithrandir> well, non-root user.  "root can crash the kernel" isn't very interesting.
[11:14] <benh> I suspect it might use read/write instead of ioctl's ... but I'll confirm all that when I have time to dig, after I'm back from Perth next week
[11:14] <cjwatson> probably to anyone who can read/write /dev/input/*
[11:14] <benh> depends on the permission on uinput
[11:14] <cjwatson> benh: ioctl to set up the virtual device, read/write to interact with it
[11:14] <benh> uinput is a hack that allows to filter input events from userspace
[11:14] <cjwatson> crw-rw---- 1 root root 10, 223 2007-04-12 10:28 uinput
[11:14] <benh> yeah
[11:14] <cjwatson> at the moment
[11:14] <benh> ok, so it's not -too- bad... still worth fixing at one point
[11:15] <Mithrandir> sure, it's worth fixing, but not getting into (another) panic about.
[11:15] <benh> either a small fix if easy, or just forbid read/write on 32 bits if not a simple fix
[11:15] <benh> sure
[11:15] <benh> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/106723
[11:16] <cjwatson> thanks
[11:17] <benh> the input layer 32/64 its thunking is known to be a total PITA
[11:17] <benh> anyway, I'll dig when I can, not enabling mouseemu by default on powerpc64 is a good enough workaround for now as far as I'm concerned
[11:17] <Mithrandir> hw-detect accepted.
[11:18] <cjwatson> ta
[11:18] <Mithrandir> cjwatson: is d-i going to run with the correct kernel (32/64 bit)?
[11:18] <cjwatson> benh: yeah, the ghastly /etc/sysctl.conf-is-different-on-powerpc hack is still in place so 1-button mice won't break anyway
[11:18] <cjwatson> Mithrandir: yes
[11:18] <Mithrandir> ok
[11:18] <cjwatson> one doesn't work on the other
[11:19] <benh> we used to have G5 support on 32 bits ... along time ago :-) we ditched it at least 2 yrs ago
[11:19] <benh> it was a pain to maintain
[11:19] <cjwatson> very glad I didn't revert /etc/sysctl.conf to stock now ...
[11:23] <benh> btw, out of curiosity, what is the policy for updates vs security ?
[11:23] <benh> like feisty-updates vs. feisty-security repos
[11:24] <benh> or more specifically, in what circumstances are things updated when it's not a security update ?
[11:24] <Mithrandir> when there is "significant breakage".
[11:24] <benh> I would suspect... bugs (things don't work) but what is the threshold for a bug to be actually fixed in a release vs. in the next version ?
[11:24] <benh> ah ok
[11:25] <benh> well, I suppose it's a matter of somebody to decide wether it's significant enough and the fix unintrusive enough then...
[11:25] <benh> fair enough
[11:25] <Mithrandir> it's always a matter of judgement, but it's for high-impact bugs which can be fixed in a localised fashion and we're reasonably sure it won't break anything else.
[11:25] <benh> yup, makes sense
[11:26] <benh> I wonder if mplayer not working on most 32 bits powerpc's will be fixed thn ;-)
[11:26] <Mithrandir> https://wiki.ubuntu.com/StableReleaseUpdates under "When" has the criteria.
[11:26] <benh> (it's apparently compiled with an option for using instructions that don't exist on most 32 bits cpus)
[11:26] <benh> oh well, we'll see
[11:27] <Mithrandir> mplayer is multiverse, so less stringent about updates to it.
[11:27] <benh> yeah
[11:27] <Mithrandir> it's also not a core component; updates to glibc have to be much more serious than updates to, say, bluez-cups
[11:28] <benh> yup
[11:28] <benh> ok, have to go, thanks for the workaround !
[11:28] <Mithrandir> see you
[11:28] <benh> bye
[11:59] <bdgraue> 2.6.20-15.27 work well, no more problems here, i think
[12:06] <bdgraue> if i can do somethink, you have to tell me :-)
[12:53] <cjwatson> bdgraue: great, much appreciatted
[12:53] <cjwatson> -t
[12:54] <bdgraue> :-)
[03:54] <`sam`> what's the deal with <IP_ADDRESS>.14, i think it's the same as 2.6.20-15.27? i'm trying to explain it to somebody in #ubuntu+1 but don't completely understand it myself
[04:22] <gene6482> this is a kernel question but it needs support, so if i'm in the wrong place i'm sorry, basically i have a toshiba laptop with sound issues and after some research have learned that my dsdt is buggy, can anyone help me fix it?
[04:22] <defendguin> i don't suppose michael bienia is in here?
[04:45] <Nafallo> defendguin: try -motu
[04:45] <defendguin> -motu?
[04:45] <Nafallo> #ubuntu-motu
[04:45] <defendguin> ahh
[04:47] <gortiz> ehm.. sorry, but someone will ever upload also the restricted driver for -15.25??
[04:48] <gortiz> ?
[04:50] <gortiz> is there someone?
[04:52] <Nafallo> gortiz: some developers haven't had much sleep the last three or four days. please calm down :-)
[04:52] <gortiz> sorry Nafallo
[04:52] <gortiz> i didn't want to be arrogant
[04:52] <Nafallo> it's okey. I'm not one of them ;-)
[04:53] <gortiz> ok i ask to forgive me..
[04:53] <gortiz> Nafallo, do you know if they are uploading also the restricted drivers?
[04:53] <gortiz> I can't test it withot them..
[04:53] <Nafallo> gortiz: at some point I'm sure they will :-)
[04:53] <gortiz> lol Nafallo
[04:53] <gortiz> thanks bye
[04:55] <Nafallo> they even seems to BE uploaded already :-)
[04:55] <Nafallo> gortiz: ^
[04:55] <gortiz> ok so it's my mirror to be outdated..
[04:56] <gortiz> i'll wait the italian mirror to be updated.. :)
[04:56] <gortiz> thanks
[05:00] <gortiz> ehm.. ok i've controlled.. it's the -15.27 not -15.25 the one i need..
[05:00] <gortiz> i'm on -15.25 and i haven't any problem
[05:01] <mjg59> -15.25 and -15.27 use the same l-r-m
[05:02] <Nafallo> -15.20
[05:14] <MrNOKIA> guys, may i ask what's the diference between  linux-headers-2.6.20-13-lowlatency and linux-headers-2.6.20-13-generic
[05:15] <gortiz> MrNOKIA, ehm the lowlatency?
[05:15] <MrNOKIA> in other words, what is more desirable to have on a dual-core centrino ?
[05:15] <gortiz> generic
[05:15] <MrNOKIA> the genreric or the low-latency kernel ?
[05:16] <MrNOKIA> lowlatency kernels are for slow cpu's ?
[05:16] <MrNOKIA> pardon if i'm mistaking
[05:17] <gortiz> no, lowlatency are for special uses on computers that need a very lowlatency..
[05:17] <MrNOKIA> like editing audio/video ?
[05:17] <gortiz> no
[05:18] <gortiz> MrNOKIA, don't worry i dont think that you need them you can use the generic
[05:18] <gortiz> :)
[05:18] <gortiz> bye
[05:18] <MrNOKIA> thanks
[05:19] <gortiz> :)
[05:19] <MrNOKIA> i just wanna clarify some issues regarding linux in general
[05:19] <MrNOKIA> that's why i asked
[05:20] <mjg59> MrNOKIA: #ubuntu is a better place for support questions
[05:21] <MrNOKIA> thanks mjg59
[06:19] <defendguin> mjg59: you can close that bug 44615 the fix works
[06:28] <defendguin> nevermind i got it
[06:36] <gene6482> this is a kernel question but it needs support, so if i'm in the wrong place i'm sorry, basically i have a toshiba laptop with sound issues and after some research have learned that my dsdt is buggy, can anyone help me fix it?
[09:14] <pokoko> g'day everyone. In Ubuntu (Linux kernel 2.6.17-11), i think there's a bug where a mounted usb device doesn't get recognised after a suspend/resume. Has this been worked out yet or some solution which I am unaware of ?
[10:01] <blueyed> Bug 106028 is still not fixed, although it's a key feature AFAIK. Not even Importance of the bug has been set..
[10:02] <blueyed> Malone bug 106028 in linux-source-2.6.20 "Kvm not installable in feisty" [Undecided,Confirmed]  https://launchpad.net/bugs/106028
[11:24] <cjwatson> blueyed: people set way too much stock in the Importance field, but yes, that should get fixed; I'll try to see to it tomorrow if nobody beats me to it
[11:25] <cjwatson> the number of people complaining about the Importance field there in fact encourages me to leave it unset simply as a demonstration ;-)
[11:26] <blueyed> cjwatson: lol, yeah. But OTOH it would be really bad if this showstopper would make it into the RC or final, wouldn't it?
[11:26] <cjwatson> "but yes, that should get fixed; I'll try to see to it tomorrow if nobody beats me to it"
[11:27] <blueyed> sure. I understand this. But the last time this was brought to IRC the answer was "it will be fixed soonish" (Bug #105263).
[11:28] <cjwatson> I don't know what you think you're going to achieve by further haranguing me given that I've already promised to look at it
[11:29] <cjwatson> looks like the kvm-api-9 provides change was one of the things that was committed to kernel mainline but not to the -15 branches, so best thing is probably to revert kvm's dependency
[11:29] <cjwatson> but, tomorrow
[11:34] <BenC> It's in git
[11:34] <BenC> it's going to be fixed on the first post-release update
[11:35] <cjwatson> BenC: kvm needs to be fixed for release, IMO
[11:35] <MrNOKIA> git ?
[11:35] <cjwatson> i.e. installable
[11:35] <BenC> cjwatson: kvm doesn't even work unless you use universe, so I'd argue it's not that bad?
[11:35] <cjwatson> honestly I think it should do Depends: kvm-api-9 | kvm-modules-2
[11:36] <cjwatson> it's a feature we've highlighted in our release notes
[11:36] <cjwatson> it's kind of an oversight that it's in universe given that IMO, but I do think it needs to work
[11:36] <BenC> cjwatson: do you want me to do another kernel upload to fix it? :)
[11:36] <cjwatson> no, I want kvm's dependencies to DTRT with what we've got
[11:36] <BenC> or wait for post-RC
[11:36] <cjwatson> unless you're saying there is no way a kvm upload can fix it?
[11:37] <BenC> cjwatson: it can't, they are broken because the kernel doesn't provide the right modules to work with kvm-18
[11:37] <cjwatson> can we revert kvm then?
[11:37] <cjwatson> blow it back with an epoch
[11:37] <BenC> we really want kvm-18, but sure, we can downgrade kvm package to kvm-16
[11:37] <cjwatson> I'll look at that tomorrow then
[11:38] <BenC> https://launchpad.net/ubuntu/+source/kvm
[11:38] <BenC> the previous version, 16-1ubuntu1 works with current kernel
[11:38] <cjwatson> I don't think another kernel upload for this is likely to be an option unless there are further critical problems
[11:38] <BenC> cjwatson: I can do it pretty quickly now, and test it
[11:38] <cjwatson> ok, thanks
[11:38] <Nafallo> epoch :-/
[11:39] <cjwatson> Nafallo: people get hung up about epochs, but shouldn't
[11:39] <cjwatson> BenC: ok, that works too, but it's Sunday so ...
[11:39] <Nafallo> well, they are evil :-P
[11:39] <BenC> epochs are a dpkg gift above
[11:39] <cjwatson> Nafallo: no they aren't
[11:39] <Nafallo> so we might not want to sync with Debian at some point then I take it :-)
[11:39] <BenC> cjwatson: good night
[11:40] <Nafallo> night.


[12:49] <WilsonBradley> Are the classes dead? https://wiki.ubuntu.com/Classroom#Following_Ubuntu_Classroom_on_identi.ca_and_twitter
[12:50] <WilsonBradley> the schedule is old
[12:55] <WilsonBradley> ?
[13:36] <Mkaysi> WilsonBradley<EMAIL_ADDRESS>[13:36] <Mkaysi> There aren't just any classes planned.


[07:50] <duflu> abi-check says we removed a function from MIR_CLIENT_DETAIL_9 ... that's OK right?
[07:53] <duflu> alan_g ^
[07:54] <alan_g> duflu: yes(ish)
[07:55] <RAOF> I would also say yes.
[07:55] <duflu> It's an ABI but not as public
[07:55] <alan_g> It won't break clients, the things it would break are distributed at the same time
[07:55] <duflu> Indeed
[07:56] <duflu> Just looks bad for our tooling as even after I fixed some minor problems 'make abi-check' fails due to it
[07:56] <duflu> So you can't tell if other failures lurk after it
[07:56]  * alan_g would like to reorg the code - but that would break ABIs
[07:58]  * RAOF is happy to break any ABI that isn't the client ABI.
[07:59] <alan_g> MirAL brings a new hope of a stable server-side ABI (but that includes getting mircommon stable)
[07:59] <duflu> I would like to say it's too late in the week to think about that but I am presently looking at it
[07:59] <RAOF> Re-exporting symbols is a thing, right?
[08:00] <RAOF> Hm.
[08:00] <alan_g> Hmm that is a thought
[08:00] <duflu> RAOF: Definitely, in theory. Just need to know how with our tools
[08:01] <RAOF> Actually, *why* can't we just include mircommon statically into mirclient?
[08:01] <duflu> Because it's a waste of space. Also the break already happened anyway
[08:01] <RAOF> I mean, we could *remove* libmircommon as a thing.
[08:01] <alan_g> Because it is used by platform modules, the mirserver and mircommon
[08:01] <RAOF> It's a trivial waste of space, and it simplifies our lives.
[08:02] <alan_g> ODR rule
[08:02] <duflu> RAOF: That solves the symbol version problems sure. But not header changes... ODR
[08:02] <RAOF> alan_g: The ODR rule doesn't apply here, though?
[08:02] <alan_g> Why not?
[08:02] <duflu> Common sense by some other name then. Database normalization (?!
[08:02] <duflu> )
[08:03] <RAOF> Because there are no C++ objects in the interface between mirclient and mirserver/mirplatforms?
[08:04] <duflu> libmirprotobuf is C++ but a different lib
[08:04] <RAOF> I mean, it's not an ODR violation if glib internally has a class called mir::Dispatchable but it's not exported in the symbol table and never appears in the interfaces.
[08:04] <duflu> Don't worry about it. We all know a fix is possible at the binary level. Just need to work out the high level syntax
[08:04] <RAOF> (If that *is* an ODR violation then that's another area where C++ is insane)
[08:05] <RAOF> (This might require getting rid of mirclientdetail, which exists, from memory, purely for the benefit of acceptance tests?)
[08:05] <alan_g> I think also for the debug extension rubbish
[08:06] <RAOF> Yeah, I'm happy to fold that in.
[08:06] <RAOF> We'll have an *actual* extension mechanism *someday*.
[08:06] <alan_g> One day we'll work out exactly what we need in what libraries and declare version 1
[08:07] <duflu> I actually wanted to look at a version "25" but that idea fell flat when I realized mirserver is already higher :(
[08:07] <duflu> How did we get here?
[08:07] <alan_g> good intentions
[08:08] <alan_g> Good session for the sprint?
[08:10] <duflu> alan_g: Sounds like a session we've had (multiple times?) before
[08:10] <duflu> Not sure I want to go through that again
[08:10] <RAOF> This seems like a different session?
[08:11] <RAOF> “How can we make it so that mirclient (a) exports no C++ symbols and (b) is standalone”?
[08:11] <RAOF> I don't think we've asked that before.
[08:11] <duflu> I thought we kind of had tests for it?
[08:11] <duflu> Or similar...
[08:11] <alan_g> And (c) how do we make a stable server ABI?
[08:11] <duflu> Making sure it doesn't re-export mircommon
[08:12] <alan_g> The stuff MirAL actually uses from mircommon actually should be stable
[08:12] <duflu> You can use anyone else's API/ABIs in your headers if they are version < 3. Otherwise (if they are ours) then maybe not
[08:13] <alan_g> To make 3rd-party platforms viable they need a stable ABI from mircommon
[08:13] <alan_g> To make 3rd-party server viable they need a stable ABI from mircommon + miral
[08:13] <duflu> We break libmirplatform often too
[08:13] <alan_g> Yep, all part of the big question
[08:14] <duflu> BTW, I just logged some relevant bugs
[08:14] <alan_g> I think we're now at a point where it is feasible, and getting important enough
[08:14] <RAOF> An alternative: we ask legal to get the appropriate verbiage to make it clear that loadable platform modules *aren't* covered by the GPL, and then not expect them to link to mircommon.
[08:15] <alan_g> mircommon provides stuff like "Rectangles" that we should be able to make stable
[08:15] <RAOF> Absolutely.
[08:15] <RAOF> Which is why having modules expect the server to supply those symbols is perfectly sensible :)
[08:16] <RAOF> Actually, if mirclient stops linking with mircommon then we lose the pressure for mircommon to be the things common to client and server.
[08:16] <duflu> BTW I've tried some experiments intentionally breaking things. Turns out a full wildcard * does not break existing symbols, but a partial one like ReadableFd does.
[08:17] <RAOF> Which would make stripping out all the bits which *aren't* super-stable easier.
[08:17] <duflu> I would also like to build one libmir* of everything with all symbols for testing, and then strip the private bits. No more object libs
[08:17] <alan_g> I don't see a problem with linking to mircommon + mirplatform - we "just" need to ensure they only publish stable stuff.
[08:18] <RAOF> Yeah, that's right.
[08:18] <duflu> Remind me why mirplatform exists?
[08:18] <RAOF> One of the current problems is that mircommon is that stable stuff, *plus* the bits shared between server and client that we actively change.
[08:19] <alan_g> To define the interface between server and platform
[08:19] <alan_g> (in an LGPL library)
[08:19] <duflu> alan_g: Remember we have the graphics and input ABIs which are different to mirplatform
[08:19] <alan_g> Follows from long discussions with legal
[08:20] <duflu> Oh. Too lawyerish for a Friday
[08:20] <RAOF> Yeah; again, an alternative would be an explicit grant of “no, your modules don't need to be GPL”
[08:20] <alan_g> Yeah, we'll not solve it here
[08:21] <alan_g> One of the current problems is that mircommon is that stable stuff, *plus* the bits shared between server and client *and platform* that we actively change.
[08:23] <RAOF> And one of the problems there is that I fully expect us to change the *platform ABI* reasonably frequently.
[08:23] <duflu> Another reason why I would prefer our namespaces followed the library names... so you could also find #include "mir/common/*"
[08:23] <RAOF> (For example: I don't think there's *ever* been an Xorg release that didn't change the graphics ABI)
[08:23] <alan_g> I think we now have enough platforms to shake out the right abstractions
[08:23] <duflu> RAOF: Xorg has the benefit of less frequent releases
[08:24] <duflu> Slightly
[08:24] <RAOF> duflu: Yes. I absolutely don't expect us to be bumping our platform ABI every release. But once a year seems perfectly plausible.
[08:24] <RAOF> Now, our platforms are doing an easier job for us than Xorg's platforms, but still.
[08:24] <duflu> RAOF: A separate stable trunk to save up those breaks?
[08:25] <RAOF> Support >1 ABI.
[08:25] <duflu> Or that
[08:25] <RAOF> We've got it all set up so that we can (reasonably easily) do that!
[08:25]  * RAOF EOD. For the moment.
[08:25] <duflu> Or dinner
[08:39] <duflu> alan_g: A bug that exists in mir_proving_server can't be MirAL can it?
[08:39] <duflu> Or can it
[08:39] <alan_g> They could have the same bug
[08:40] <alan_g> But MirAL code isn't in proving_server
[08:41] <duflu> Indeed
[08:42] <duflu> So bug invalid for MirAL
[13:05] <alf_> Saviq: greyback: Hi! How do apps tell unity8/qtmir that they want to keep the display on? Is it done through QT?
[13:22] <greyback> alf_: not through Qt itself, I think people use the dbus api that powerd offers to keep the display on
[13:23] <alf_> greyback: ok, how is losing focus handled?
[13:23] <greyback> alf_: I *think* we trust the application to be good
[13:23] <greyback> I'd need to look into it
[13:23] <greyback> going off old memories here
[13:25] <alf_> greyback: thanks, this came up again because I am working on the snap interface for keeping the screen on, and wasn't sure if things had changed.
[13:26] <greyback> no changes afaik
[13:27] <alf_> greyback: Ideally, as discussed in the past such requests should be sent to Unity8, and then unity8 can decide what to do depending on form factor, focus etc
[13:27] <greyback> alf_: correct
[13:27] <greyback> but nothing has happened on that front
[13:28] <alf_> greyback: yeah, I will update the snap iface to work with what's currently in place and we can revisit the topic (perhaps in the sprint)
[14:51] <alan_g> bschaefer: as my pointer confinement guru - could you check the miral integration? https://code.launchpad.net/~alan-griffiths/miral/confine_pointer/+merge/306635
[14:52] <bschaefer> alan_g, yes!
[14:53] <bschaefer> looks nice
[14:54] <bschaefer> the only thing /me trying to remember if you'll need to specifically do something on a window creation spec for confinement
[14:54] <bschaefer> alan_g, also how come you have to do the #if?
[14:55] <alan_g> miral presents the same API/ABI on xenial as on yakkety
[14:55] <alan_g> But xenial is on Mir-0.22
[14:55] <bschaefer> o dang /me hopes it wont become an #if nightmere :|
[14:55] <bschaefer> nightmare*
[14:56] <bschaefer> alan_g, without actually testing it looks good to me (have you tried out the example?)
[14:56]  * alan_g is only supporting LTS, Yakkety, and lp:mir
[14:57] <alan_g> bschaefer: not yet
[14:57]  * alan_g remembers not knowing what the example should do
[14:57] <bschaefer> alan_g, i can re-compile and test it out after the standup
[14:57] <bschaefer> alan_g, i made a mir demo :) (mir_demo_client_pointer_confinement)
[14:58] <alan_g> I remember not knowing what to expect from that
[14:59] <bschaefer> alan_g, o .. right well you should be able to move the red square for ever when pointer confinement is on
[14:59] <bschaefer> when its off your cursor will go our of the screen boundary
[15:01] <alan_g> I need something more recent that 0.24 don't I?
[15:03] <bschaefer> alan_g, yeah there are some changes in 0.25 that fixed some pointer confinement issues
[15:03] <bschaefer> mainly with WM stuff
[15:03] <bschaefer> moving/resizing etf
[15:03] <bschaefer> etc*
[15:04] <alan_g> I mean for the demo
[15:04] <bschaefer> alan_g, hmm i thought the demo was in 0.24 but i only have trunk mir branch /me checks
[15:05] <alan_g> bschaefer: could you try it then - miral builds much faster
[15:06] <bschaefer> alan_g, yeah i must have been compiling a chunk of mir not miral when i mention it the other day (took less then a min for miral)
[15:06] <bschaefer> http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/examples/pointer_confinement.c
[15:06] <bschaefer> alan_g, but yeah ill test after standup
[15:43] <alan_g> bschaefer: well, it seems to do something
[15:43] <bschaefer> alan_g, haha thats good (was answering an OSK)
[15:43] <bschaefer> alan_g, theres hot keys to disable pointer confinement
[15:43] <bschaefer> p i think
[15:44] <alan_g> Yes, I had to read the code. and "F" to toggle fullscreen (What happened to F11?)
[15:44] <bschaefer> alan_g, umm me breaking the standard :)
[15:45] <alan_g> Yes, you ignore "close the window" too
[15:45] <alan_g> ;)
[15:46] <bschaefer> haha
[15:46] <bschaefer> i thought i put q back in
[15:46] <bschaefer> or tried to filter those events through...
[15:46] <bschaefer> (do the underlying handle event)
[15:47]  * bschaefer compiling now
[15:48] <bschaefer> alan_g, umm invalid free / next
[15:48]  * bschaefer checks things
[15:49] <bschaefer> huh using 0.24 but i tihnk i compiled against 0.25 for some reason
[15:50] <alan_g> I mean mir_event_type_close_surface
[15:50] <bschaefer> alan_g, o ... that would have been something to use
[15:50] <alan_g> It's only an example, but...
[15:51] <bschaefer> yeah i like examples to be just as good as our code
[15:51] <bschaefer> (mainly people look at examples to write their code)
[15:54] <bschaefer_> that was strange..
[15:55] <alan_g> ldconfig?
[15:56]  * bschaefer_ doesnt understand joke
[15:56] <bschaefer_> alan_g, i hit that mirshell session next thing
[15:57] <bschaefer_> (possibly) where input didnt work but went to a tty to attempt to step through it and once i hit the tty hot keys my machine just stopped
[15:58] <alan_g> bschaefer_: that's an evil bug.
[15:58] <bschaefer_> yeah... im trying to get you more info
[15:58] <bschaefer_> alan_g, i seem to hit it only using the x11 platform
[15:59] <alan_g> then possibly one for camako
[15:59] <bschaefer_> possibly just need more info before i can really poke anyone :(
[15:59] <bschaefer_> a way to reproduce would be nice :)
[16:00] <alan_g> yes, might mir-trunk related - which I don't use be default
[16:00] <bschaefer> alan_g, very true i use trunk mir
[16:00] <bschaefer> could be an ABI issue as well?
[16:00] <bschaefer> no
[16:00] <bschaefer> that would cause a crash...
[16:00] <alan_g> *probably*
[16:00] <bschaefer> i suppose if it ... somehow ABI match the bytes to a different function...
[16:01] <bschaefer> haha that would be funny...
[16:18] <anpok_> i think thats because the x11 platform tries to grab the keyboard?
[16:20] <alan_g> probably need to ssh in from another computer
[16:22] <bschaefer> alan_g, i was lucky to get into a tty for that current backtrace we have... but it froze this last time
[16:22] <bschaefer> anpok_, could be, the strange thing all mouse events work fine
[16:23] <bschaefer> (it just almost feels like the mir shell keeps grabbing focus ... ie keyboard grab?)
[16:56] <alan_g> bschaefer: http://voices.canonical.com/alan.griffiths/2016/09/23/debugging-mir-servertoolkit-interactions/
[16:57] <bschaefer> alan_g, sweet thanks i will be using this!
[16:57] <bschaefer> for more debugging info for reports
[16:58]  * bschaefer will be sure to include logs for reports as well
[16:58] <alan_g> :)


[02:10] <IamTrying> http://paste.ubuntu.com/6081763/  - I have a problem with USB devices, like now my devices are connected but lsusb shows nothing
[02:10] <IamTrying> Is it possible to ignore using xhci_hcd and use UHCI_HCD ?
[02:11] <IamTrying> xhci_hcd is causing all those problems as a result all usb devices get lost or behave abnormally.
[04:11] <ntzrmtthihu777> Hallo, filed a bug, they wish to for me to test it against 13.10; is the current iso capable of a grub2 iso boot?
[04:17] <wilee-nilee> ntzrmtthihu777, should be
[04:21] <ntzrmtthihu777> wilee-nilee: sup man, lol. on another note, what kernel does it use?
[04:22] <wilee-nilee> ntzrmtthihu777, Not 3.11 something I believe I'm in another os right now
[04:22] <wilee-nilee> sure
[04:25] <ntzrmtthihu777> kk, I've jumped ship for arch, but I figure I should follow up on this bug till the end for the sake of others.
[12:53] <BluesKaj> 'Morning folks
[14:05] <Munchor> Hi everyone, is ubiquity broken? Flashed latest daily build, and Ubiquity on a terminal wont run
[14:05] <Munchor> Plus, if I just Install Ubuntu as opposed to Try Ubuntu Without Installing, it will say there was a problem with the installer and loads the live desktop
[14:11] <BluesKaj> Munchor, which image, beta1 ?
[14:11] <Munchor> daily build
[14:11] <Munchor> Since beta 1 has been released, I will assume it is post-beta1
[14:13] <BluesKaj> yeah , one would assume
[14:14] <Munchor> I would normally expect a Critical bug on Launchpads Ubiquity but since I cant find it, I am a bit to lost
[14:14] <Munchor> I cant really install Ubuntu, I am stuck
[14:14] <BluesKaj> Munchor, considered 13.04 ?
[14:15] <Munchor> I need 13.10 since I am a developer of an Ubuntu-derived distro (elementary) and we are moving to 13.10 as a base
[14:16] <BluesKaj> then a do-release-upgrade -d . that's what i did when ubiquity balked on previous Ubuntus
[14:17] <BluesKaj> one has to completely upgrade 13.04 first of course , it's a bit long and ponderous , but it works
[14:17] <Munchor> I have a 13.04 install
[14:17] <Munchor> so all I have to do is go on my 13.04 install and run do-release-upgrade -d?
[14:18] <Munchor> I thought Upgrading only worked after 13.10 had been released
[14:18] <BluesKaj> like I said , upgrade/distupgrade your 13.04 install first
[14:19] <Munchor> as in apt-get update, apt-get upgrade and apt-get distupgrade?
[14:19] <BluesKaj> not if you use the -d in the string
[14:19] <BluesKaj> -d for development
[14:19] <BluesKaj> dist-upgrade
[14:20] <Munchor> awesome, will reboot and get to it now, thanks for the help
[14:20] <BluesKaj> np , let us know how it goes
[14:24] <Zoiaguyver> Munchor: Does ubiquity just hang and do nothing from terminal?
[14:25] <Munchor> exactly Zoiaguyver
[14:25] <Munchor> I can't even C-c it, I have to open another shell and sudo killall ubiquity
[14:25] <Munchor> On the September 8th build that is
[14:26] <Munchor> Other elementary developers mentioned that it doesn't work if you Try Ubuntu Without Installing
[14:26] <Zoiaguyver> Yeah there was a problem I had with one of them that i needed to disable the sso signon
[14:27] <Zoiaguyver> They included the sso in the installer, but I'll see if i can find the command a sec, it was something like "ubiquity --sso-login" or something and that allowed me to atleast get it installed
[14:28] <Munchor> I just logged in on the hard disk installer, but I guess it doesn't hurt to go back and try that
[14:28] <Munchor> before I try the dist-upgrade method BluesKaj suggested
[14:31] <Munchor> So I ran ubiquity  --help
[14:31] <Munchor> ubuntu@ubuntu:~$ ubiquity --no-sso
[14:31] <BluesKaj> by all means , if it will shorten the install time
[14:31] <Munchor> and found that, and it just stays there
[14:31] <Munchor> oh wait
[14:31] <Munchor> it opened!
[14:31] <Munchor> yeah this worked
[14:32] <Zoiaguyver> thats the one!
[14:33] <Munchor> oh interesting
[14:33] <Munchor> Ubiquity now seems to detect my Ubuntu 13.04 and suggests upgrading it
[14:33] <Munchor> Besides installing side-by-side and reinstalling
[14:33] <Zoiaguyver> sorry was looking for the bug that i found about it, but as per usual I lost it >.>
[14:34] <Munchor> I wonder if I should go with that, to avoid copying over my backup files
[14:34] <Munchor> The general word is that upgrades arent clean, but messy
[14:34] <Zoiaguyver> They can be very messy
[14:35] <Zoiaguyver> I've tested it a few times with the Alphas and it seemed ok apart from some directories whining about not being empty
[14:35] <Munchor> yeah I chose Reinstall for a clean install sake
[15:29] <Munchor> Zoiaguyver: BluesKaj: despite Ubiquity issues, install went as smooth as possible (went for a haircut and came back and it was installed), everything seems to work
[15:29] <Munchor> thank you
[15:32] <BluesKaj> Munchor, good to hear :)
[17:10] <BluesKaj> wonder what happened to users & groups in system settings on Kubuntu , don't see there , just the user manager , which has no "add to group" option
[17:11] <Ian_Corne> Anyone know how to de-activate auto log in?
[17:18] <Ian_Corne> unity still horribly broken for my used :(
[17:18] <Ian_Corne> user*
[17:18] <BluesKaj> Ian_Corne, dunno about ubuntu , but on kubuntu it's system settings>login screen>general tab
[17:19] <Ian_Corne> Yeah I found an answer on askubuntu
[17:19] <Ian_Corne> any Idea how to fix no launcher showing up when logging into ubuntu?
[17:19] <Ian_Corne> (unity)
[17:20] <Ian_Corne> maybe a clean install would be advisable..
[17:20] <Ian_Corne> I'll first try unity8 :p
[17:22] <Ian_Corne> nope :)
[17:26] <BluesKaj> Ian_Corne, install lightdm?
[17:27] <Ian_Corne> i got it :)
[17:27] <Ian_Corne> http://ubuntuhandbook.org/index.php/2013/08/reset-unity-and-compiz-in-ubuntu-13-10/
[17:27] <Ian_Corne> now I'm running KDE and Unity at the same time :p
[17:27] <Ian_Corne> the first command fixed it for me :)
[17:28] <BluesKaj> your Kmenu in kubuntu must well populated :)
[17:28] <Ian_Corne> I have no idea :p
[17:28] <Ian_Corne> Just used kubuntu to get to something visual
[17:28] <Ian_Corne> to have the browser open
[17:29] <Ian_Corne> the lens pops up fast
[17:30] <Ian_Corne> If I open more than one tab in chrome, it doesn't have the label anymore
[17:31] <BluesKaj> not an ubuntu/unity fan , i can't take the visuals or the clunky desktop
[17:32] <Ian_Corne> Hehe, I think the same about kde :)
[17:33] <Ian_Corne> My gnome terminal kept shrinking to whatever size of text was displayed
[17:34]  * BluesKaj shrugs, i don't mix n match
[17:36] <Ian_Corne> oh, got two labels to show on chrome! :p
[18:42] <johnjohn101> wishing the Mir developers good luck with everything going against them.
[18:45] <_kas> could any one help with a video issue i am having after upgrading from 13.04 to 13.10?  I get an error after bootup that the system in running in low-graphics mode and it wont load a graphical login.  Intel HD 4000 video card.
[18:45] <BluesKaj> desktop or laptop , _kas?
[18:45] <_kas> laptop
[18:46] <BluesKaj>   is it a dual gpu system?
[18:47] <_kas> i am able to use a different TTY, login via text mode, and startx.  i think start unity with unity --replace
[18:47] <_kas> BluesKaj, no
[18:49] <bekks> _kas: You should not use startx.
[18:49] <bekks> _kas: Instead, better use gdm, because startx will mess up permissions.
[18:50] <ali1234> it's also very insecure
[18:50] <_kas> bekks, OK.  is gdm or lightdm used in 13.10?
[18:50] <bekks> _kas: lightdm
[18:52] <_kas> bekks, before starting x directly I tried restart lightdm.  I get a black screen
[18:52] <_kas> sudo reboot
[18:54] <ali1234> don't use reboot, use shutdown -r now
[18:55] <_kas> lightdm results in a black screen with a flashing white cursor
[18:57] <bekks> Then check the logs. Reboot doesnt help.
[18:59] <_kas> sorry if i missed any advice prior to my last msg.  I got dropped from IRC and had to join back in.
[21:35] <pepee> hi. I want to report a couple bugs..
[21:36] <pepee> I'm using an AMD laptop, and I'm unable to resume from suspend
[21:36] <pepee> also, X crashes after closing glxgears (by pressing alt+f4)
[21:39] <pepee> this is an hybrid ATI/ATI system, radeon HD 6755g2 (radeon HD 6520g + HD 6750M)


[09:20] <gema> hi, can I subscribe to the mailing list<EMAIL_ADDRESS>without being part of the bug-control?
[09:21] <gema> I'd like to start a thread about defect analysis and gather opinions and that list strikes me as the right one to do that
[10:06] <gema> well, I sent the email
[10:06] <gema> I hope it goes through
[12:24] <hggdh> gema: subscription to the Bug Control mailing list is restricted to the members
[12:24] <hggdh> gema: and good morning (or afternoon, as it may be)
[12:24] <pedro_> bom dia hggdh :-)
[12:24] <hggdh> buen dia pedro_ :-)
[12:26] <hggdh> actually, I see no reason to have the ML restricted to members
[12:26] <hggdh> hum
[12:26] <hggdh> we should discuss this
[12:28] <gema> morning, hggdh and pedro_
[12:28] <gema> I sent an email, did it arrive?
[12:28] <pedro_> buenos dias gema
[12:28] <gema> buenos dias pedro_
[12:29] <hggdh> gema: I just moderated it, should be on its merry way
[12:29] <gema> cool, thanks!
[12:31] <jibel> hggdh, pedro_ gema good morning
[12:31] <gema> morning jibel
[12:31] <jibel> hggdh, crash reports are sent to the list and may contain private information.
[12:31] <hggdh> jibel: bon jour monsier
[12:31] <hggdh> jibel: oh yes
[12:32] <pedro_> jibel, Bon après-midi to you :-)
[12:32] <gema> jibel: the archive shows the emails
[12:32] <gema> I mean, if that is the case, are you making sure they don't get archived?
[12:32] <hggdh> now, that's a good question...
[12:33]  * hggdh expects everything gets archived
[12:33] <jibel> pedro_, Buenas tardes señor :)
[12:34] <jibel> gema, indeed, that's what I was thinking while I pressed enter
[12:34] <hggdh> darn! we live among poliglotes!
[12:34] <hggdh> aye, all there
[12:36] <hggdh> oh boy, 29 messages to moderate on the server-bugs list... and I am pretty sure it is all spam.
[12:36]  * hggdh goes clean some spam
[12:37] <gema> hggdh: what about using some software for that? I have heard there are pretty good spam filters out there :P
[12:39] <hggdh> gema: these are the left overs
[12:39] <gema> ahh, ok :)
[14:29] <RedSingularity> mvo: Any idea what can cause the "install update" button not to function?
[14:32] <RedSingularity> mvo: the user is saying that clicking the button has no effect. Seems to work under root though.
[14:37] <mvo> RedSingularity: hello! is there any more info on this available? anything in ~/.xsession-errors or the terminal that u-m was started in?
[14:37] <mvo> RedSingularity: it should log some sort of info when this happens :/
[14:38] <ogra_> and is the user actually an admin user ? :)
[14:38] <ogra_> or doesnt PK bind to that anymore ?
[14:42] <RedSingularity> mvo: will ask.  One more thing.  When the main.log doesnt give a specific package, like 'ubuntu-desktop', thats being held back, what package can I start looking in for the 'trail' of errors?
[14:43] <mvo> RedSingularity: I usually start from the last entriy and work my way back
[14:44] <RedSingularity> mvo: ah good.  Thanks :)
[14:44] <mvo> RedSingularity: but it can be a bit hard to follow, do you have a specific example? we can have a look together (or you can have a look and I double check the results, whatever you prefer) :)
[14:44] <RedSingularity> mvo: let me have a look for an example...
[14:45] <mvo> no rush
[14:50] <RedSingularity> mvo: bug 831799 is an example.  Look at the ERROR part in the main log.  NO package is mentioned.
[14:51] <ubot4> Launchpad bug 831799 in update-manager (Ubuntu) "update-manager error after painful upgrade from 10.04 to 10.10 (affects: 2) (heat: 19)" [Undecided,Incomplete] https://launchpad.net/bugs/831799
[14:51] <RedSingularity> mvo: looks like i narrowed it to libavcodec52.  Not sure if thats correct.
[14:52] <mvo> RedSingularity: thanks, let me have a look
[14:59] <mvo> RedSingularity: right, so I suspect its actually " Installing libavutil50 as Depends of libswscale0" the libswscale0 that has a breaks on mplayer, but I haven't look closer where this mplayer comes from and/or if its a problem of the archive or of a third party site
[15:00] <mvo> RedSingularity: lateron, mplayer is rather unhappy about libswscale0 and libavcodec52, the combination seems to be deadly :)
[15:12] <RedSingularity> mvo: does the mplayer error 'branch' to those two packages?  Is it possible to branch multiple ways in these apt logs?
[15:16] <mvo> RedSingularity: they are definitely confusing, let me re-look at this to make sure I'm not missing something
[15:21] <RedSingularity> mvo: I followed it to libavcodec52. Maybe it branched to the other package too though.
[17:28] <jploz> hello out there!
[17:29] <Abhijit> hi jpds
[17:29] <Abhijit> jploz,
[17:30] <jploz> I've one general question regarding bugs and different ubuntu versions: Image a package which is packaged with different versions in several ubuntu releases
[17:30] <jploz> that is (for example) version 0.1 in Lucid, 0.2 in Natty etc.
[17:31] <jploz> Now, I've some bug reports related to version 0.1
[17:31] <jploz> these are fixed in version 0.2 of the package
[17:32] <jploz> Question: how to handle such szenario? What'd the correct bug status in Ubuntu?
[17:33] <micahg> jploz: https://wiki.ubuntu.com/Bugs/Responses#Fixed_in_Development_release_while_still_existing_in_a_previous_release
[17:33] <jtaylor> jploz: you should evaluate if the bug is important enough for a stable release update
[17:33] <jtaylor> https://wiki.ubuntu.com/StableReleaseUpdates
[17:33] <jploz> Let's say it is important enough.
[17:34] <jtaylor> then follow the instructions on that wiki page
[17:34] <jploz> Can I track the status of the bug over several ubuntu release?
[17:34] <jtaylor> yes you need to nominate it for a series
[17:34] <micahg> only bug control can nominate
[17:34] <jploz> ah
[17:34] <micahg> jploz: you can request a nomination here though
[17:34] <jploz> this makes things clearer
[17:36] <jploz> what is the recommended way? Nominate bugs for each series? Or just set them to "Fix released" as soon as a new version (that fixes the bug) is out?
[17:42] <micahg> jploz: if it's known fixed in the devel release it should be fix released, if it no longer affects the devel release (invalid) with a nomination for a previous series if worth SRUing
[17:44] <jploz> what does it take to become a member of bug control?
[17:45] <micahg> jploz: https://launchpad.net/~ubuntu-bugcontrol
[17:46] <jploz> ok, so for the beginning I could ask for nominations here, right?
[17:52] <micahg> jploz: yes
[17:52] <micahg> jploz: are you planning on fixing any of these?
[17:59] <jploz> @micahg: I'm asking because of the package `sbackup`. Lucid has version 0.10.5 with many bug reports and some of them are severe, Maverick has version 0.11.x which is quite a rewrite and fixes most of them. Many of the old bugs are "Won't fix" because it is impossible to port patches from 0.11 to 0.10. However, some (most annoying) of the old bugs could get fixed, therefore my questions.
[17:59] <meetingology`> jploz: Error: "micahg:" is not a valid command.
[17:59] <jploz> micahg: I'm asking because of the package `sbackup`. Lucid has version 0.10.5 with many bug reports and some of them are severe, Maverick has version 0.11.x which is quite a rewrite and fixes most of them. Many of the old bugs are "Won't fix" because it is impossible to port patches from 0.11 to 0.10. However, some (most annoying) of the old bugs could get fixed, therefore my questions.
[18:00] <jtaylor> maybe a backport would be appropriate
[18:00] <jtaylor> via ubuntu-backports
[18:01] <jtaylor> https://wiki.ubuntu.com/UbuntuBackports
[18:03] <jploz> Thanks to everyone. This solved my questions. Thanks a lot. Bye
[18:06] <micahg> jploz: jtaylor, yes sbackup would be a fine candidate for backports
[18:06] <micahg> jploz: I was just going to suggest if you're going to fix it, you can ask for bug tasks in #ubuntu-motu
[18:07] <micahg> if it's just that someone else could fix it if they like, just ask for a nomination here
[18:10] <jploz> micahg: bug tasks?
[18:11] <micahg> jploz: where you can set statuses/and or take it to work on it on a per release basis
[18:13] <niclas> Hi, if I need help to report a bug is this the place to ask? Or should I ask in a different room maybe? Don't know which package to file the bug against.
[18:14] <jploz> micahg: ok, thanks to you. I got the differences now (I did a SRU some times ago already). thank you. bye
[19:25] <dust_> hi - i got a bug in kubuntu beta2 concerning kleopatra kgpg and gnupg - but i don't know how and where to file it
[19:27] <micahg> yofel: ^^
[19:27] <yofel> what's the bug?
[19:28] <dust_> starting watchgnupg out of kmail adds the following lines to gnupg.conf:
[19:28] <dust_> debug-level basic
[19:28] <dust_> log-file socket:///home/dust/.gnupg/log-socket
[19:29] <dust_> wheter on the commandline or in kgpg - it doesn't start without outcommenting these lines again - kleopatra doesn't show the keys anymore but starts
[19:31] <dust_> this is what kgpg or gpg on the commanline sais:
[19:31] <dust_> gpg: /home/dust/.gnupg/gpg.conf:248: argument not expected
[19:31] <dust_> gpg: /home/dust/.gnupg/gpg.conf:249: invalid option
[19:33]  * yofel wonders why gpg log viewer is greyed out for him o.O
[19:35] <dust_> you've got to install kleopatra - i guess then also watchgnupg is installed
[19:35] <dust_> ?!?
[19:36] <yofel> watchgnupg was installed, kleopatra indeed wasn't
[19:40] <yofel> dust_: I don't quite understand why the config file says the entries were added with gpgconf, but even gpgconf --check-config errors out
[19:41] <yofel> I can confirm the issue though
[19:42] <dust_> well where to file this issue? - launchpad -  bugs.kde.org ?
[19:43] <yofel> dust_: start by filing it against kleopatra https://bugs.kde.org/enter_bug.cgi?product=kleopatra&format=guided
[19:43] <dust_> ok
[19:43] <dust_> thanks
[19:59] <dust_> yofel: it's filed - i hope it's clear enough - need link?
[20:01] <yofel> found it
[20:04] <dust_> ok gn8 - got to go to bed now :) thanks again for your help


[00:57] <benonsoftware> Hi all
[20:20] <head_victim> If there are any C++ in here with a few minutes of spare time if they can please sing out
[20:22] <head_victim> I'd just like to run an email past you, not take up hours of your time :)


[00:32] <fta> dtchen, now that i'm using vdpau, mplayer exposes some audio gliches, like if the sound was not able to keep up with the video
[00:33] <fta>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
[00:33] <fta> 21537 fta       20   0  168m  41m  12m S   10  2.1   6:24.76 mplayer
[00:33] <fta>  1078 root      20   0  601m  53m  10m S    5  2.6  34:45.63 Xorg
[00:33] <fta>  1524 fta        9 -11  157m 9520 7016 S    3  0.5  10:22.38 pulseaudio
[00:34] <fta> that's when playing a hi def file
[00:34] <fta> VIDEO:  [avc1]  1280x536  24bpp  23.976 fps    0.0 kbps ( 0.0 kbyte/s)
[00:34] <fta> Opening audio decoder: [libdca] DTS decoding with libdca
[00:34] <fta> Stream with high frequencies VQ coding
[00:34] <fta> AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio: 192000->192000)
[00:34] <fta> Selected audio codec: [dts] afm: libdca (DTS-libdca)
[00:34] <dtchen> doesn't surprise me; there's quite some optimisation remaining
[00:35] <fta> AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample)
[00:36] <fta> you mean in p-a or vdpau?
[00:36] <dtchen> the former, at least
[00:41] <fta> regular 720p now take 0~2% CPU so that's plenty of cpu left for p-a & X
[00:42] <fta> this one is kind of tougher to play
[00:49] <fta> FIREFOX_3_6b2_RELEASE
[01:01] <micahg1> fta: I'll try to package ff3.6b2 later tonight
[01:02] <micahg> fta: are you subscribed to something where you see the releases?
[01:08] <fta> yes
[01:09] <fta> rss
[01:09] <fta> like http://hg.mozilla.org/releases/mozilla-1.9.2/atom-tags
[01:09] <fta> http://hg.mozilla.org/mozilla-central/atom-tags
[01:09] <fta> etc
[01:13] <micahg> ah, cool
[02:03] <meatbun> i have suggestion to firefox, on the downloading-pop up, i would like to easily see the source address which i am doing. right now i have to manually copy and paste it to notepad and to gedit
[06:53] <micahg1> fta: I made the fixes for ff3.7 daily, but it needs to be reviewed before committing
[09:41] <hyperair> hello. has anyone noticed the missing "undo closed tab" feature from the daily builds of firefox?
[09:41] <hyperair> and possibly the broken "view image" feature among other context menu options for images in firefox daily?
[10:10]  * asac waves
[10:14] <asac> hyperair: which daily build?
[10:14] <asac> which version?
[10:14] <hyperair> firefox-3.7: Installed: 3.7~a1~hg20091105r34606+nobinonly-0ubuntu1~umd1
[10:16] <asac> ok. everything is possible on trunk ;) ...
[10:16] <asac> hyperair: when did it disappear?
[10:16] <hyperair> hmm a few days ago
[10:16] <hyperair> i'm not very sure when
[10:16] <asac> let me upgrade to latest ...
[10:16] <hyperair> i could add it back with tab mix plus, but for some reason, it removes all my toolbar buttons that have been added by extensions
[10:17] <eagles0513875> hey asac :)
[10:22] <asac> hi
[10:22] <asac> hyperair: will take a bit till system has all updates ...
[10:23] <asac> dpm: hi. yes, wonder if we should really have a dedicated session. maybe we can put mozilla stuff in some other translator session?
[10:34] <dpm> hey asac, morning. Thanks for coming back to me on this. The only one on the community track it could fit into would be https://blueprints.edge.launchpad.net/ubuntu/+spec/community-lucid-browser-start-page-l10n, but that one has not really got to do with Firefox. We've got room in the community track, so scheduling a new one wouldn't be a problem. If we cannot fit it in any existing one I'd go for scheduling an informative session - IIRC correctl
[10:34] <dpm> y you were telling some time ago that in the future we might have different versions of FF, and I'd like to discuss how this will affect translations. Also devmode, etc.
[10:39] <asac> dpm: ok. i will just add an informational spec for this cycle and subscribe you (will do all this spec stuff later today, after catching up on various things)
[10:39] <asac> dpm: in case we dont get a slot on desktop track we can put that on community
[10:40] <hyperair> asac: it's fine, take your time
[10:41] <dpm> asac, yes, sure. But jono would like to have all community blueprints by today, so if it doesn't fit in the desktop track, please let me know laer on and I'll file one on the community track
[10:42] <dpm> thanks
[11:25] <fta> jcastro, "On 2009-11-15, six days from now, your membership in the Ubuntu Bug Control (ubuntu-bugcontrol) Launchpad team is due to expire."  could you please do something for me?
[11:26] <fta> asac, hi!
[11:27] <fta> asac, you now have pptp & vpnc in the nmt ppa
[11:28] <asac> fta: oh ;)
[11:28] <asac> fta: thx ... :-P
[11:28] <asac> hi
[11:28] <asac> what triggered this?
[11:28] <asac> fta: bugcontrol is bdmurray ;) ^^^
[11:29] <asac> bdmurray: ^^
[11:31] <fta> http://paste.ubuntu.com/314007/
[11:32] <asac> ah
[11:32] <asac> yeah
[11:32] <asac> so two of them are in this channel ;)
[11:41] <fta> asac, we have a seg fault during build in lpia
[11:41] <asac> hmm
[11:41] <asac> 1.9.3 only, right?
[11:41] <asac> fta: do you have a lpia install? guess its all i386 nowadays?
[11:41] <asac> (netbook)
[11:42] <fta> no lpia, it didn't even boot on my netbook
[11:43] <asac> let me check if we have a porter machine or something where i can log in and check
[11:43] <asac> fta: crashes everywhere or just karmic/lucid?
[11:43] <fta> karmic
[11:43] <fta> no lucid yet
[11:44] <asac> ok makes sense i guess ;)
[11:44] <fta> bug 478691 makes it difficult to add lucid
[11:51] <asac> fta: what does that fix imply?
[11:51] <asac> http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/9685
[11:51] <asac> i dont get it ;)
[11:51] <asac> Ensure that if a currently-building build exists for the same
[11:51] <asac>
[11:51] <asac> 573
[11:51] <asac>         # ppa archive and architecture currently building then we don't
[11:51] <asac>
[11:51] <asac> 574
[11:51] <asac>         # consider another as a candidate.
[11:51] <asac> that sentence makes not much sense to me
[11:52] <fta> there are 12~15 builders per arch now, a given ppa can only start 1 build per arch at a time, even if the other ones are all idle
[11:52] <asac> ok. lets do the ppa split ;)
[11:53] <asac> at least for mozillas that should help
[11:53] <fta> yep, it's cheating though
[11:54] <asac> https://bugs.edge.launchpad.net/soyuz/+bug/478691/comments/3
[11:58] <fta> took 14 hours for umd yesterday
[11:58] <fta> and 10h for ucd with just 1 package
[12:03] <asac> fta: bug 393534
[12:03] <asac> isnt that your bug?
[12:03] <fta> no
[12:04] <fta> well, maybe the same root cause
[12:08] <asac> fta: you still have a bug after the engine fixes?
[12:15] <fta> no
[12:20] <asac> good ;)
[13:33] <fta> asac, grrr, each time i restart ff3.7, the session is gone
[13:33] <fta> empty
[14:16] <asac> hmm ... wonder if this new scheduling also applies for native ppas like the security ppa
[14:16] <asac> would be bad :(
[14:17] <asac> let me check
[16:03] <gnomefreak> im 97% i am leave to go to pennsylvania(sp) saterday ill be gone until jan/feb however i am bringing atleast one of my pc's not sure if its this one or not
[16:11] <wolfslack> will it be possible to integrate thunderbird tasks with google at some point?
[16:13] <gnomefreak> ? lightning?
[16:14] <gnomefreak> i dont reall if tbird3 will beable to sync with google but as of today i dont see it
[16:14] <wolfslack> yes, using lightning.
[16:15] <gnomefreak> calendar-google-provider
[16:15] <gnomefreak> as i recall that is what you want
[16:16] <wolfslack> considering your name i dare to ask a non-channel topic question: Is evolution to be seen as a part of gnome? I find it frustrating that so many packages depend on it.
[16:16] <wolfslack> yeah sure, calendar work fine. Tasks don't.
[16:16] <gnomefreak> i dont use evo
[16:17] <gnomefreak> ther eis a bug on that (maybe more than 1) but i havent gotten a changce to look into it
[16:17] <wolfslack> But im sure you have it installed.
[16:17] <gnomefreak> wolfslack: nope i removed it
[16:17] <gnomefreak> evo is installed by default in gnome
[16:19] <wolfslack> really, ok havent tried to remove it for atleast some versions (since 8.. something). Back then open office got wacked if i touched it.
[16:20] <gnomefreak> wolfslack: there are parts (not sure if one or how many) that will take some packages you want (maybe)
[16:20] <gnomefreak> i also remove bluetooth crap
[16:24] <wolfslack> removing evolution-dataserver-common will remove gnome-session, gnome-applets aso.
[16:25] <wolfslack> which is a shame because evolution is crappy
[16:29] <gnomefreak> yep
[16:33] <mac_v> wolfslack: evolution seems to have gotten better
[16:34] <wolfslack> well its a shame that gnome is creating locking in to evolution if you want the nice ui integration.
[16:35] <wolfslack> google calendar access is read only forexample.
[16:35] <mac_v> wolfslack: actually 'evolution-dataserver-common' doesnt have anything to do with evolution mails per-se
[16:36] <wolfslack> its open source legacy software as i see it. And for some reason they are clinging to it, despite the technological superiority of thunerbird.
[16:36] <mac_v> yeah ,,,legacy ;)
[16:37] <wolfslack> evolutions tasks will integrate with the gnome-gui, so will evolution mail.
[16:55] <bdmurray> fta: as an ubuntu developer you are already a member of bug control so only your "direct" membership is expiring.  You can safely ignore it.
[16:56] <fta> bdmurray, really? last time, it expired for real
[16:59] <bdmurray> fta: hunh, it shouldn't
[17:01] <fta> bdmurray, it's direct membership: https://edge.launchpad.net/~fta/+participation
[17:01] <fta> got it before motu
[17:02] <bdmurray> fta: rigth but if you look at https://edge.launchpad.net/~ubuntu-dev that team is a member of ubuntu-bugcontrol so while your direct membership will expire you'll still be a member of bug control
[17:02] <fta> ok, lets try that );
[17:02] <fta> ;)
[17:03] <asac> very good
[17:03] <gnomefreak> bdmurray: is pulseaudio-module-udev still needed or has it been replaced (lucid
[17:03] <gnomefreak> )
[17:03] <bdmurray> gnomefreak: I don't know
[17:04] <gnomefreak> bdmurray: thanks ill remove it and find out :)
[17:05] <gnomefreak> its replaces pulseaudio-module-hal
[17:13] <fta> asac, did you review micahg's work?
[17:13] <micahg> let me get a pastebin
[17:14] <asac> i probably havent even reached the emails
[17:14] <asac> still 600+ left
[17:15] <fta> i want the session restore back
[17:15] <fta> [reed], ^^
[17:15] <[reed]> ?
[17:15] <[reed]> what's wrong with session restore?
[17:16] <micahg> http://pastebin.com/f5b8c2697 with emails redacted
[17:18] <fta> [reed], each time i restart ff, it starts empty
[17:18] <[reed]> hmm
[17:19] <micahg> [reed]: thanks for the dictionary patch upstream
[17:19] <fta> asac, your patch, i let you review it
[17:20] <asac> mozilla bug 515232
[17:22] <[reed]> micahg: no problem... I didn't know about that bug, or I could have had it fixed upstream a long time ago
[17:22] <[reed]> things like that, please just ping me personally :)
[17:22] <[reed]> especially Linux-specific stuff
[17:22] <micahg> [reed]: asac gave me the fix a while back, but I never had time to go back and test it
[17:22] <asac> micahg: have the full patch file?
[17:22] <asac> that diff is hard to read ;)
[17:23] <[reed]> don't count on asac to ever upstream anything :P
[17:23] <micahg> [reed]: no, I was supposed to upstream, but I had to test
[17:23] <micahg> I wrote one version of it, but it wasn't good enough
[17:23] <micahg> never got around to a second version as it was low priority
[17:24] <micahg> asac: looking
[17:25] <micahg> http://pastebin.com/f3a3b8ee2
[17:27] <asac_> back
[17:27] <asac_> had a busted net
[17:27] <asac_> micahg: ^^
[17:28] <asac_> didnt get anything after "looking"
[17:28] <micahg> asac http://pastebin.com/f3a3b8ee2
[17:28] <gnomefreak> asac_: what package does this come from in debian Debian-exim
[17:28] <gnomefreak> im getting errors on that
[17:30] <asac_> [reed]: can you check bugzilla bug 521780 ... and commit if it doesnt need more review?
[17:30] <[reed]> mozilla bug 521780
[17:30] <[reed]> looks good to me... I'll commit it
[17:30] <asac_> thx
[17:31] <asac_><EMAIL_ADDRESS>[17:31] <asac_> though i dont mind what you use ;)
[17:32] <asac_> also needs to go everywhere i guess ... bad bug not sure why you dont see that in upstream builds
[17:32] <asac_> or .. upstream users
[17:32] <asac_> maybe its really just hitting system extensions
[17:32] <micahg> [reed]: I've got crazy unicode issues with the 3.6b2 I built
[17:32]  * micahg guesses he should try upstream version
[17:34] <asac_> micahg: maybe if you do a hg diff ... the diff looks more similar to the one we previously hadß
[17:34] <asac_> ?
[17:34] <asac_> i have like:
[17:34] <asac_> .hgrc:
[17:34] <micahg> asac, the patch was only rebased
[17:34] <asac_> [diff]
[17:34] <asac_> git = 1
[17:34] <asac_> [defaults]
[17:34] <asac_> diff=-p -U 8
[17:34] <asac_> micahg: yes. but the quilt refresh made it harder to read from what i can tell
[17:35] <asac_> https://bug515232.bugzilla.mozilla.org/attachment.cgi?id=399338
[17:35] <asac_> that one is so simple ;)
[17:36] <asac_> but i think its equivalent
[17:36] <micahg> this is what you gave me for quilt refresh: quilt refresh --diffstat -U8 --no-timestamps
[17:37] <asac_> yeah
[17:37] <fta> [reed], i noticed last week both at work and at home that sessions are broken
[17:37] <asac_> didnt say that you did something wrong
[17:37] <asac_> j9ust that quilt diff seems to suck ;)
[17:37] <micahg> I can't tell the difference between the two aside from the function name included
[17:38] <micahg> and iirc, there's a diff option for that as well
[17:38] <asac_> micahg: the difference is that the git diff keeps the + together where possible
[17:38] <asac_> and the quilt one mixes + and -
[17:39] <micahg> ah, I don;t have an hg checkout
[17:39] <gnomefreak> anyone know why im getting the following in my debian chroots?
[17:39] <gnomefreak> dpkg: unrecoverable fatal error, aborting: syntax error: unknown group 'Debian-exim' in statoverride file
[17:39] <asac_> let me check
[17:39] <gnomefreak> E: Sub-process /usr/bin/dpkg returned an error code (2)
[17:40]  * asac_ pulls latest for moz central
[17:44] <asac> micahg: http://paste.ubuntu.com/314274/
[17:44] <asac> thats what hg made out of my diff
[17:44] <asac> if you want take that ... if not its fine to use what you ahd too
[17:46] <micahg> ok, I can take your patch
[17:46] <micahg> then everything else is fine?
[17:46] <micahg> I can delete the line from the install file?
[17:49] <[reed]> micahg: so, when the next nightly comes out, please test the spelling fix
[17:49] <[reed]> make sure it works
[17:49] <[reed]> :)
[17:54] <micahg> [reed]: ok
[17:54] <micahg> asac: it's ok to delete the line from the .install file though?
[17:56] <micahg> asac: it's ok to delete the line from the .install file though?
[17:58] <micahg> asac_: ^^^
[17:58] <asac_> 18:49 < asac> micahg: yes. thats what landed upstream, so i would say its ok
[17:58] <asac_> ok out for 2 hours or so
[18:59] <armin76> asac: around?
[18:59] <armin76> well, looks like i need to wait for around an hour :P
[18:59] <armin76> or...
[18:59] <armin76> fta: around? :)
[19:11] <fta> armin76, ?
[19:12] <fta> asac, did you review the patch? i want to respin 3.7, it's 3 days behind xul
[19:13] <armin76> fta: asac: nvm
[19:17] <armin76> jftr: systemsqlite+noxport+safebrowsing = yay
[19:18] <[reed]> sqlite's requirement was bumped again, if you all didn't notice
[19:18] <[reed]> <3
[19:19] <[reed]> sqlite requirement, I mean
[19:19] <[reed]> min version
[19:20] <armin76> 3.6.18?
[19:20] <[reed]> 3.6.20, I think
[19:20]  * [reed] looks
[19:20] <[reed]> mozilla bug 524144
[20:18] <micahg> fta: asac: 3.7 daily is fixed
[20:24] <asac> thx
[20:25] <fta> good, respinning
[20:26] <asac> jdstrand: ppa has a new feature that hits us bad ... the builds i uploaded this morning are still not built
[20:27] <asac> because we dont get parallel builds for ppas anymore
[20:27] <jdstrand> :/
[20:27] <asac> this time it was just 3.5 / 1.9.1
[20:27] <jdstrand> asac: I saw you talked about it-- is it getting fixed?
[20:27] <asac> jdstrand: i talked to bigjools
[20:28] <asac> after some talking he seems to be ok with the ratio approach instead of just allowing 1
[20:28] <asac> not sure when he will fix it
[20:29] <asac> he said "maybe in 7 days"
[20:29] <jdstrand> eek
[20:29] <asac> so seems 3.5.5 is tomorrow ... feel free to do some testing ;)
[20:30] <micahg> asac: can you look at bug 476129
[20:30] <jdstrand> asac: ok
[20:40] <fta> not a good time to add lucid to the dailies
[20:45] <armin76> asac: around?
[20:45] <armin76> asac: i have a workaround for sparc
[21:02] <bdrung> asac: how about releasing m-d 0.17.1?
[22:24] <micahg> asac: http://glandium.org/blog/?p=495
[22:26] <[reed]> lulz debian whining
[22:26] <[reed]> why am I not surprised
[22:29] <mconnor> I guess I lack context
[22:32] <[reed]> yeah, it's internal package intricacies with maintainer fields in the debian/control file
[22:32] <[reed]> all boils down to some Debian person hating Ubuntu
[22:32] <[reed]> and glandium just whining about Ubuntu :)
[22:39] <micahg> [reed]: have you seen anything about beta 2 having an issue with unicode?
[22:39] <micahg> 3.6b2
[22:40] <[reed]> unicode in what? just normal web pages?
[22:40] <[reed]> or something specific
[22:40] <micahg> stuff like ... becomes a block with code in it, and after a minute or so reverts to ...
[22:40] <[reed]> I have noticed that some icons on trunk are broken
[22:40] <[reed]> been meaning to file that
[22:40] <micahg> password blocks also look like a unicode card for a minute instead of a dot
[22:40] <[reed]> hmm
[22:40] <micahg> started after upgrade to beta 2
[22:41] <[reed]> password code was just recently touched
[22:41] <micahg> after a minute it's fine
[22:41] <[reed]> ok, let me find that bug
[22:46] <[reed]> mozilla bug 514212
[22:46] <[reed]> can you test builds before and after that landed?
[22:49] <micahg> [reed]: I don't think it's that
[22:49] <micahg> it's any non-ascii character
[22:49] <micahg> it's in the tabs and web [ages as well
[22:49] <micahg> *pages
[22:50] <[reed]> ah
[22:50] <[reed]> hmm
[22:50] <[reed]> well, find a regression range
[22:50] <[reed]> you know how this works :)
[22:54] <fta> micahg, I've got some unicode issues with trunk since last week
[22:56] <mconnor> [reed]: but why does the email address matter?
[22:56] <fta> even in tab or window title when the subject is truncated and the "..."  is a bloc with the unicode id in it
[22:56] <mconnor> it's... an email address
[23:05] <asac> bdrung: do we have anything to release?
[23:06] <bdrung> asac: the rc bug fix
[23:06] <bdrung> asac: therefore as point release
[23:08] <asac> micahg: [reed]: yeah. i dont know what his problem with an ubuntu address as maintainer is
[23:11] <asac> that said, i will revert the icedove address because our mailing list is a mess and we have to moderate all bugs
[23:13] <fta> asac, just added a comment to the ppa queue bug
[23:14] <bdrung> asac: should we change the maintainer for m-d, too?
[23:14] <micahg> [reed]: regression range is from b1 to b2 :)
[23:15] <asac> bdrung: i dont think so.
[23:15] <asac> its team maintained
[23:15] <asac> icedove is not
[23:15] <asac> i made the team the maintainer because at that point someone wanted to take care here
[23:15] <asac> but he disappeared
[23:18] <asac> fta: yes. i think bigjools agreed in the end that the 20% thing i suggested would be a good way
[23:18] <asac> until there is a real "fair scheduling algorithm available"
[23:18] <fta> should be 0%
[23:18] <fta> why waste builders?
[23:19] <fta> and then time
[23:19] <[reed]> micahg: yeah.....
[23:20] <fta> grrr, damn firefox
[23:20] <asac> fta: yes. the thing is that they dont like that a biulder will be blocked for 3 hours. personally i couldnt care less
[23:20] <micahg> [reed]: was just wondering if you saw something
[23:20] <micahg> I can research later
[23:20] <[reed]> that's a huge range ;p
[23:20] <[reed]> need a smaller range
[23:20] <fta> lost my session again
[23:20] <asac> but tried to find a suggestion that might make them feel better
[23:20] <asac> fta: dont close ff ;)
[23:20] <micahg> asac: none of the mozilla builds take 3 hrs AFAIK
[23:21] <fta> asac, if it was better at dealing with upgrades, i would never restart it
[23:24] <asac> hehe
[23:24] <asac> oh
[23:24] <asac> ok
[23:24] <asac> micahg: 3h is for chromium
[23:24] <asac> people filed a bug about "mozilla/chromium" taking all the buildd times
[23:24] <asac> then they started doing stupid things
[23:24] <asac> now i even have to wait ages till security ppa builds finish :(
[23:26] <[reed]> asac: should file a bug to revert that other bug
[23:26] <[reed]> sorry, but browsers are kinda important
[23:26] <micahg> [reed]: I filed a bug about it already
[23:26] <[reed]> bug #?
[23:26] <micahg> bug 478691
[23:27] <asac> [reed]: i already complained in person ... i think in 7 days there will be an improvement
[23:27] <micahg> asac: it seems like for openoffice and chromium they messed up everything else
[23:27] <asac> thats the next launchpad code push
[23:27] <asac> micahg: there are no openoffice dailies
[23:27] <micahg> yeah, but people can push to ppa
[23:27] <micahg> so it was just chromium that did this?
[23:27] <asac> its really just that folks looked at the queue and saw that chromium/mozilla dailies were taking their time
[23:28] <micahg> that's only 4 builds
[23:28] <asac> no
[23:28] <asac> mozill ahas more builds
[23:28] <fta> lots of people are pushing kernels
[23:28] <asac> but not dailies for multiple branches to all releases ;)
[23:28] <asac> i think its just the wrong impression ... my point was that with 3 builders per arch
[23:28] <fta> well, if it's the problem, i'll stop the bot, period
[23:28] <asac> even without mozilla/chromium the queue will be long
[23:29] <asac> fta: riht. thats why i said its just a impression. --- which was wrong
[23:29] <micahg> asac: mozilla daily is 28 builds, with 12+ builders per arch, that should take less than 2 hours
[23:29] <asac> micahg: 3 builders is all that are guaranteed
[23:29] <asac> that was the reason why all this shows up
[23:29] <asac> with 12 builders there is no problem
[23:30]  * micahg wants to add more dailies too :)
[23:31] <asac> so 3 builders are dedicated builders ... then there are 10 builders or so per arch that are owned by QA team ... they usually just hel pout
[23:31] <asac> but the 3 builders are not enough
[23:31] <asac> thats the whole point
[23:31] <[reed]> you all need more machines
[23:32] <[reed]> we have hundreds of build machines
[23:32] <[reed]> and we just make _one_ product
[23:32] <[reed]> :p
[23:32] <asac> true ;)
[23:32] <asac> but ppas previously didnt exist
[23:32] <asac> i mean like 2 years ago there was only archive
[23:33] <asac> https://edge.launchpad.net/builders
[23:33] <asac> Official distributions build status   VS PPA build status
[23:33] <asac> its kind of interesting that the "official builders" are enough
[23:33] <asac> but thats the case
[23:34] <asac> even though we have full imports etc.
[23:34] <[reed]> how do I get my launchpad to always use edge?
[23:34] <asac> [reed]: you need to be a member of launchpad beta
[23:34] <[reed]> can I just join that group?
[23:35] <asac> you need to apply and someone has to admit you.... i am not sure what the procedure is
[23:35] <asac> maybe fta knows?
[23:35] <micahg> https://edge.launchpad.net/~launchpad-beta-testers
[23:35] <micahg> anyone can join
[23:35] <asac> [reed]: try to join that team here: https://edge.launchpad.net/~launchpad-beta-testers
[23:36] <asac> oh its open nowadays
[23:36] <asac> good
[23:36] <asac> in the past it was kind of closed
[23:36] <asac> yeah
[23:36] <asac> so just join the team
[23:36] <[reed]> cool
[23:36] <asac> once you are in there and you dont want edge you can disable it for 2h on the main page
[23:36] <asac> like ... when things are too busted to be usable ;)
[23:37] <asac> https://launchpad.net/
[23:37] <asac> atm its kind of stable ... there were times where i almost shot myself because of major annoyances of beta stuff
[23:37] <micahg> there's actually a link at the bottom of every page now to disable redirect
[23:37] <asac> oh
[23:37] <asac> ;)
[23:37] <asac> good thing
[23:38] <micahg> asac: bugs...http://status.qa.ubuntu.com/qapkgstatus/firefox-3.5
[23:38] <[reed]> cool
[23:38] <asac> at least ffox 3.0 is stable now ;)
[23:38] <asac> http://status.qa.ubuntu.com/qapkgstatus/firefox-3.0
[23:38] <fta> should i kill the bot and redirect all the users to that bug?
[23:39] <micahg> fta: i don't think so, they still get built, right?
[23:39] <micahg> asac: well, it's not in karmic :)
[23:39] <asac> fta: as i said.... i already talked to him
[23:40] <asac> i think in 7 days it will be fixed
[23:40] <asac> most likely by the 20% thing until they feel more comfortable
[23:40] <fta> well, there's no more room for respins, and dailies are now tomorrows
[23:40] <asac> yes. but let it run and see if something changes
[23:41] <asac> if folks complain about the delay send them to bug
[23:41] <asac> if nothing changes, stop the bot
[23:41] <asac> though we wanted to move the mozilla stuff to separate ppas anyway now ...
[23:42] <asac> err last month
[23:42] <asac>  /me fails
[23:42] <asac> armin76: let me know what workaround you found ;)
[23:51] <fta> http://launchpadlibrarian.net/35444376/buildlog_ubuntu-karmic-amd64.xulrunner-1.9.1_<IP_ADDRESS>~hg20091109r26560%2Bnobinonly-0ubuntu1~umd1_FAILEDTOBUILD.txt.gz
[23:51] <fta> took 7 hours just to get that :(
[23:51] <asac> yeah
[23:51] <asac> it was landed
[23:52] <asac> mozilla bug 499498
[23:53] <fta> ok, last answer clearly shows that dailies are no longer welcome
[23:53] <asac> err
[23:53] <asac> i read the mail that it was approved like 1 hour ago
[23:58] <asac> fta: William is not a launchpad developer etc.
[23:59] <[reed]> asac: he claims to be on his wiki
[23:59] <[reed]> :p


[13:02] <bluca> andersson1234: I noticed a small issue with the results reporting - if a job fails and the failed result is attached to the PR, and then I trigger it manually (because it's flaky or I change something in the config), then the job goes back to "pending" in the PR
[13:02] <bluca> but after a few minutes, the previous failed result is attached again
[13:02] <bluca> the new job keeps running and eventually completes, but it's result is not reported back, the previous one stays in the PR result
[13:03] <bluca> this only happens when re-triggering manually via the http api - force pushing to the PR branch doesn't show any issue
[15:39] <andersson1234> bluca: Thanks for reporting this. I'll note it down. Do you consider this a blocker? Or can you work around it with force pushes?
[15:43] <bluca> not a blocker and definitely not urgent
[15:50] <bluca> another question: is it possible to cancel a pending/running job from the http api?
[15:58] <Skia> sadly not yet, but we're working on something there. No ETA though
[16:08] <bluca> no worries, not urgently needed, thanks
[19:52] <bluca> ppc64el jobs seem to be failing to boot the testbed
[19:52] <bluca> happened multiple times
 failure: setup script failed with code 1: /home/ubuntu/autopkgtest/ssh-setup/nova open
[19:52] <bluca> https://autopkgtest.ubuntu.com/results/autopkgtest-noble-upstream-systemd-ci-systemd-ci/noble/ppc64el/s/systemd-upstream/20240304_172916_d4069@/log.gz