[00:13] <mekius> Anyone know if pata_via is going to be reenabled in the Ubuntu kernels in the near future?
[00:24] <mekius> If anyone is around, how is it determined whether to load ide-generic?  We have a chipset which doesn't work with the via28xxx module, but loading ide-generic makes the drive appear.  ide-generic is obviously not ideal, but at least it works.  Shouldn't this load if no other module loads for a piece of hardware?
[00:24] <mekius> This is why I ask about pata_via since I'm assuming it will autoload
[00:32] <Kano> hi, could somone fix the powerpc build of 2.6.24? it did not find a modules file
[07:25] <kraut> moin
[16:58] <tseliot> BenC are you there?
[16:59] <tseliot> I'm trying to get the nvidia driver to work with DKMS however the compilation fails
[17:00] <tseliot> here are the two files I had to add to debian/ :
[17:00] <tseliot> http://albertomilone.com/ubuntu/nvidia-kernel-source.postinst
[17:00] <tseliot> http://albertomilone.com/ubuntu/nvidia-kernel-source.prerm
[17:00] <tseliot> and this is the modified debian/rules:
[17:00] <tseliot> http://albertomilone.com/ubuntu/rules
[17:01] <BenC> tseliot: it fails to compile in the postinst?
[17:01] <tseliot> yep
[17:02] <BenC> what's the failure message?
[17:02] <tseliot> this is the command which the dkms should execute:
[17:02] <tseliot> echo "MAKE[0]=\"export IGNORE_XEN_PRESENCE=1; make -C /usr/src/nvidia-${nv_drv_choice}/ -f Makefile.kbuild SYSSRC=/usr/src/linux-headers-${flavours} KBUILD_PARAMS="-C /usr/src/linux-headers-${flavours}" module\""
[17:03] <tseliot> if you need the exact error I can log out, install the generated driver and reproduce the problem
[17:03] <BenC> I can't really help you without knowing what the actually error is
[17:03] <tseliot> ok, I'll be right back with the error
[17:35] <tseliot> BenC here is what happens when I install nvidia-kernel-source
[17:35] <tseliot> Unpacking nvidia-new-kernel-source (from .../nvidia-new-kernel-source_100.14.23+<IP_ADDRESS>_i386.deb) ...
[17:35] <tseliot> Setting up nvidia-new-kernel-source (1:100.14.23+<IP_ADDRESS>) ...
[17:35] <tseliot> Adding Module to DKMS build system
[17:35] <tseliot> Doing initial module build
[17:35] <tseliot> Error! Bad return status for module build on kernel: 2.6.22-14-generic (i686)
[17:35] <tseliot> Consult the make.log in the build directory
[17:35] <tseliot> /var/lib/dkms/nvidia/100.14.23/build/ for more information.
[17:35] <tseliot> Installing initial module
[17:35] <tseliot> Error! Could not locate nvidia.ko for module nvidia in the DKMS tree.
[17:35] <tseliot> You must run a dkms build for kernel 2.6.22-14-generic (i686) first.
[17:35] <tseliot> Done.
[17:35] <tseliot> now I'll paste the real error from the log
[17:37] <tseliot> DKMS make.log for nvidia-100.14.23 for kernel 2.6.22-14-generic (i686)
[17:37] <tseliot> Mon Dec 17 18:34:23 CET 2007
[17:37] <tseliot> make: Entering directory `/usr/src/nvidia-100.14.23'
[17:37] <tseliot> make: Nothing to be done for `/usr/src/linux-headers-2.6.22-14-generic'.
[17:37] <tseliot> NVIDIA: calling KBUILD...
[17:37] <tseliot> make CC=cc -C modules
[17:37] <tseliot> make: Entering an unknown directory
[17:37] <tseliot> make: *** modules: No such file or directory.  Stop.
[17:37] <tseliot> make: Leaving an unknown directory
[17:37] <tseliot> NVIDIA: left KBUILD.
[17:37] <tseliot> nvidia.ko failed to build!
[17:37] <tseliot> make: *** [module] Error 1
[17:37] <tseliot> make: Leaving directory `/usr/src/nvidia-100.14.23'
[17:38] <tseliot> BenC this is all it says. Ideas?
[17:38] <BenC> ok, next time, use pastebin :)
[17:38] <tseliot> sure :P
[17:39] <BenC> -C modules
[17:44] <tseliot> BenC ok this is the only line of the new error
[17:44] <tseliot> make: *** modules: No such file or directory.  Stop.
[17:46] <BenC> well, it's doing -C in the wrong place
[17:48] <tseliot> the nvidia kernel source package should put the content of the former nvidia source tarball into /usr/src/nvidia-100.14.23
[17:50] <tseliot> BenC here is the content of that folder:
[17:50] <tseliot> http://pastebin.com/m6c3fa512
[17:52] <tseliot> BenC and here's the content of the dkms.conf:
[17:52] <tseliot> http://pastebin.com/d769a1430
[18:00] <mekius> Hi, anyone here able to tell me why the pata_via driver is not included in the kernel?  Also is there an easy way to build a single module without rebuilding the entire kernel so we can just package this module?
[18:05] <rtg_> mekius: hardy? 'CONFIG_PATA_VIA is not set' might just be  an oversight.
[18:06] <mekius> rtg_: On gutsy kernel, 2.6.22-14
[18:07] <mekius> I have read there were issues with it during dapper/edgy, but haven't found any info on it from feisty/gutsy
[18:07] <mekius> I saw some updates to it as recent as 2.6.22-6
[18:07] <rtg_> mekius: dunno. you'll have to rebuild the kernel and experiment with it.
[18:07] <mekius> ok, I will try it out
[18:08] <rtg_> mekius: just so you know, the earliest opportunity to get it enabled by default will be for Hardy.
[18:08] <mekius> Yes, I assumed was the case
[18:08] <mekius> I have 3 VIA chipsets to test against, so I'll be able to provide some testing data
[18:09] <mekius> Hopefully all goes well as we are having issues with a chipset that isn't supported by the old pata driver and ide-generic doesn't load by default to cover it
[18:18] <mekius> rtg_: Is there anywhere that I could read why the module was disabled?
[18:18] <cheguevara> damn the new linux-restricted-modules-2.6.24 FTBFS again
[18:18] <rtg_> mekius: perhaps search LP? BenC was dealing with pata stuf f last time.
[18:19] <mekius> rtg_: I work for gOS and have contacts at VIA who I'm trying to get to be more open and write their drivers in the community, so any information on what is broken would be good :)
[18:19] <mekius> rtg_: OK, I'll look around
[18:19] <BenC> mekius: I believe there is a bug about this...the libata-pata driver doesn't work as well as the ide driver, or something along those lines
[18:20] <tseliot> BenC: any ideas? The nvidia-new-kernel-source package I made seems to contain the same files as Mandriva's equivalent nvidia-dkms package...
[18:21] <BenC> mekius: I believe we disabled the pata-via driver because it was getting broken when host-protected-area was being ignored
[18:21] <mekius> BenC: Ok, I will dig around, just unfortunate since we have some newer hardware and they are begging for it to be supported heh.
[18:22] <BenC> tseliot: sounds to me like the proper vars aren't getting passed to the underlying build
[18:22] <mekius> BenC: Do you know if anyone has attempted to fix these issues, or will they still exist if I build it manually?
[18:23] <mekius> BenC: I'll look around launchpad, like I said I saw an update in 2.6.22-6 for it, but nothing after that
[18:23] <mekius> Also some misc updates before that revision as well
[18:24] <BenC> mekius: sad part is, that was disabled because of feisty, and it seems we never tried re-enabling it to see if it was still broken
[18:24] <BenC> so it may work, we just don't know
[18:25] <rtg_> mekius: if you saw updates in 2.6.22.Y, then they are also upstream.  You might try the current 2.6.24-rc kernel.
[18:25] <tseliot> BenC: yes, I know, but how are those variables passed in the official debian/rules you made?
[18:25] <mekius> BenC: Well I can test with a few chipsets and report back.  I will let you know how well it works.
[18:25] <mekius> BenC: I realize that testing is hard without the hardware around :)
[18:26] <BenC> tseliot: check the rules file, I don't recall off the top of my head
[18:26] <mekius> rtg_: Is that in the Hardy repo?
[18:26] <rtg_> mekius: yep, but you'll have to enable the CONFIG option.
[18:26] <BenC> mekius: any testing you can provide is very much appreciated
[18:27] <rtg_> mekius: I can build a CONFIG_PATA_VIA in about 20 minutes one if you want to test.
[18:27] <mekius> rtg_: Sry, I'm not all that familiar with Ubuntu, I do this when I install the package?
[18:28] <mekius> BenC: Can do, I need to test anyway, so might as well try to get this working upstream :)
[18:29] <mekius> rtg_: Does it just run make menuconfig during install if I set evn var CONFIG=true?
[18:29] <rtg_> mekius: um, its a little more involved then that. gimme a few minutes....
[18:29] <mekius> rtg_: ok, thx
[18:33] <tseliot> BenC: this is the line you use in your rules:
[18:33] <tseliot> $(ROOT_CMD) make -C $(builddir)/$$i/nv-new -f Makefile SYSSRC=/usr/src/linux-headers-$$i KBUILD_PARAMS="-C /usr/src/linux-headers-$$i SUBDIRS=$(builddir)/$$i/nv-new" module;
[18:35] <BenC> tseliot: I have to be honest, I've never worked with dkms, so I don't know how to set it up to pass those vars down to the sub-build
[18:35] <BenC> tseliot: mdomsch would be the guy to talk to
[18:36] <tseliot> BenC: I really appreciate your honesty. I'll go bug mdomsch then ;)
[19:08] <rtg_> mekius: http://people.ubuntu.com/~rtg/linux-image-2.6.24-2-generic_2.6.24-2.3_i386.deb-pata-via
[19:09] <mekius> gah, browser tries to load it heh
[19:10] <mekius> wget :)
[19:38] <mekius> rtg_: Is that just a .deb then?
[19:39] <rtg_> mekius: yes. download it, then 'sudo dpkg -i linux-image-2.6.24-2-generic_2.6.24-2.3_i386.deb-pata-via'
[19:39] <mekius> yeah
[19:41] <reynaldo> rtg_ hi, can I stole you a minute?
[19:41] <rtg_> reynaldo: yes?
[19:42] <mekius> rtg_: going to take a bit of work since i need to install it via a chroot into the system I installed onto the harddrive.  Is this going to cause conflicts with the modules in the linux-ubuntu-modules package?
[19:43] <rtg_> mekius: you need to be on bare metal in order to install a kernel. A chroot isn't gonna test your VIA disk problems.
[19:44] <rtg_> mekius: and no, the modules installed are completely separate.
[19:45] <mekius> rtg_: well what i'll do is install the kernel to the hard drive and then reboot to the hard drive, only option :/
[19:45] <mekius> can't get booted into the hard drive copy, well maybe if i could load ide-generic in the initrd
[19:45] <mekius> if this doesn't work, i'll try that
[19:45] <rtg_> mekius: I see. then that may be the only way.
[19:46] <mekius> rtg_: Yeah, I'm having all kinds of fun, can't you tell :)
[19:46] <rtg_> mekius: yep - its a bitch when your base drivers don't work.
[19:48] <mekius> indeed
[19:48] <rtg_> reynaldo: I don't have a Freenode registered nick. You'll have to use email.
[19:49] <mekius> ide-generic is so slow too, took over an hour to install heh
[19:51] <rtg_> mekius: one of the features I hope our installer guys figure out is a way to blow an ISO onto a USB drive. It really speeds things up.
[19:51] <reynaldo> rtg_: ok, sending it over, thanks a lot.
[19:52] <mekius> rtg_: :)
[19:54] <mekius> rtg_: wish me luck heh
[19:55] <rtg_> mekius: hopefully it won't trash your drive, which is a real possibility with the protected area stuff.
[19:55] <mekius> rtg_: Just a test system, no important date
[19:55] <mekius> data*
[19:57] <rtg_> mekius: I would expect to work on a fresh install, but an upgrade from a driver that honors HPA to a driver that does not is surely gonna trash something.
[19:57] <mekius> rtg_: I think it's booting :D
[19:58] <mekius> still waiting for it, but it has made it farther then before
[19:58] <kylem> rtg_, BenC, i was going through old photos and thought you might like this: http://www.flickr.com/photos/__kyle/2117175970/in/set-72157603479056297/
[19:59] <mekius> rtg_: So the new driver doesn't support something important is what you are saying?
[19:59] <mekius> rtg_: Well it booted fine without destroying anything :D
[19:59] <mekius> rtg_: This is good news for me heh
[19:59] <rtg_> kylem: man, that seems like awhile ago.
[20:00] <kylem> http://www.flickr.com/photos/__kyle/2116459477/in/set-72157603479056297/
[20:00] <kylem> it was. ;-)
[20:00] <BenC> kylem: sweet
[20:00] <BenC> it was only a little more than 6 months ago
[20:00]  * BenC loved the "Follow Me" truck
[20:01] <BenC> I have the other side to the dueling cameras photo
[20:02] <mekius> rtg_: Did you see any updates to pata_via since 2.6.22-14?
[20:02] <rtg_> mekius: can you paste the 'lspci -vvnn' output in http://paste.ubuntu-nl.org/. Lets be sure its doing what we think.
[20:02] <mekius> rtg_: I didn't find anything while searching
[20:02] <mekius> rtg_: ok
[20:03] <rtg_> mekius: I haven't been looking at the .22 tree since we stopped Gutsy development.
[20:03] <mekius> ok
[20:04] <mekius> hmm, ok, we may have some issues, can't gurantee they are due to this module exactly, but definitely having problems
[20:04] <BenC> http://www.flickr.com/photos/__kyle/2117196194/in/set-72157603479056297/
[20:05] <BenC> kylem: ^^ it's not too often you get to see what you'll look like in 40 years :)
[20:05] <rtg_> mekius: for example?
[20:05] <kylem> hehe
[20:05] <rtg_> BenC: yuk, yuk.
[20:05] <mekius> Well getting a lot of graphics corruption, might be due to files not being read of the disk?
[20:05] <mekius> happens when i moved windows mostly
[20:06] <rtg_> mekius: that could be VIA agp.
[20:07] <rtg_> mekius: its unlikely to be a disk issue.
[20:07] <mekius> Well we are using openchrome drivers, so maybe an incompatibility :/
[20:08] <mekius> rtg_: paste.ubuntu-nl.org/48573
[20:11] <rtg_> mekius: looks right. the 0581 PCI device ID is specifically supported.
[20:12] <reynaldo> rtg_: sent, thanks again.
[20:15] <reynaldo> BenC: hi there ben, gently pinging again. still waiting for your answer. I understand you must be _uterly_ bussy but I just dont want you to forget or even worst, to think I forget about it.
[20:16] <BenC> reynaldo: I'll catch it in the morning. Sorry it's taking so long
[20:17] <BenC> wtf
[20:17] <BenC> I can't see what is causing this:
[20:17] <BenC> dpkg-genchanges: warning: duplicate files list entry for package xorg-driver-fglrx (line 23)
[20:17] <BenC> that's while building lrm on i386...can't reproduce it locally
[20:18] <reynaldo> BenC: no need to be sorry, we are all just trying to help ;) thanks again!
[20:25] <mekius> rtg_: Ah, might be due to the via drm driver getting loaded
[20:26] <rtg_> mekius: it does sound like a graphics issue.
[20:26] <mekius> yeah, i'll try to unload it, but the terminal is hosed heh
[20:26] <mekius> having to type blind
[20:28] <mekius> Good thing I know how the tab completion behaves like the back of my hand :0
[20:28] <mekius> :)
[20:33] <mekius> rtg_: Is is possible to build and distribute the pata_via module in a seperate package
[20:34] <rtg_> mekius: yes, but you'll have to tell me what the advantages are.
[20:34] <mekius> rtg_: Hmm, seems to only get corrupted when shaped windows come into play
[20:34] <rtg_> mekius: I think its the only driver that supports you PCI IDs
[20:35] <mekius> rtg_: Well we would just use it on our machines for now
[20:35] <mekius> I've only tested it on the one machine
[20:35] <mekius> i can test on another quick and see how that does
[20:36] <mekius> Have another notebook with 1106:0571
[20:51] <somerville32> rtg_, did you apply my patch?
[20:53] <rtg_> somerville32: this one? http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=c0bb64a179acfab520ef9050eb712afd715f6866
[20:54] <somerville32> No, the one about the userspace typedefs being hidden behind #ifdef __KERNEL__
[20:57] <rtg_> somerville32: did you send it to the kernel team mailing list 'cause I don't see it (which doesn't mean I might not have deleted it by accident)
[20:58] <somerville32> rtg_, Yes I did send it
[20:58] <somerville32> but I forgot to set the subject line
[20:59] <rtg_> somerville32: did you ever see it appear? The SPAM filter might have eaten it.
[21:00] <somerville32> I'll check the archive
[21:00] <somerville32> It is in the archive
[21:00] <somerville32> https://lists.ubuntu.com/archives/kernel-team/2007-December/001946.html
[21:01] <mekius> rtg_: Do you think we'll have issues shipping pata_via or would my test here prove that it works ok?
[21:03] <rtg_> mekius: I would like to see at least a couple of unique PCI IDs tested. I need to research just what the issues were, 'cause if they were HPA then there might be some update issues.
[21:04] <mekius> rtg_: Ok, I will try to test on a couple more computers today and get back to you.  They should all have different VIA IDE controllers
[21:04] <mekius> Two are laptops, one's a desktop.
[21:04] <mekius> I'll have to double check, the others might be using sata
[21:04] <rtg_> mekius: send the results to the kernel team list so it gets a little wider distribution.
[21:04] <mekius> Ah ok, will do
[21:13] <somerville32> rtg_, Did you find the e-mail?
[21:15] <mekius> rtg_: Where can I find the list info?
[21:15] <rtg_> somerville32: yes. I think I postponed dealing with it until I saw what happened upstream. However, its simple enough I'll go ahead and apply it (after build testing). If it causes on the next rebase it'll be simple enough to fix.
[21:16] <somerville32> rtg_, Will you be able to upload today?
[21:17] <rtg_> somerville32: no. its not likely until after the the 1st. Canonical is pretty much shut down all of next week.
[21:17] <somerville32> The 1st of January?
[21:17] <rtg_> somerville32: yes.
[21:17] <rtg_> mekius: https://lists.ubuntu.com
[21:17] <somerville32> rtg_, I needed the fix for Alpha 2.
[21:17] <mekius> rtg_: thx
[21:18] <rtg_> somerville32: its already too late. Alpha2 is being baked this week.
[21:19] <somerville32> Then I guess I'll just have to patch xfce4-battery-plugin for now
[21:19] <mekius> rtg_: If I verify that it works for a few devices would it be able to go into the Hardy alphas?
[21:20] <rtg_> mekius: Alpha3 https://wiki.ubuntu.com/HardyReleaseSchedule
[21:21] <mekius> rtg_: k
[21:29] <tseliot> BenC: I just wanted to let you know that thanks to mdomsch and to your help I got DKMS + NVIDIA to work!!!
[21:36] <BenC> tseliot: excellent
[21:41] <tseliot> BenC: I was successful but I had to edit the dkms.conf manually.
[21:42] <tseliot> However I can't seem to escape the dollar sign as I usually do
[21:42] <tseliot> this command in the debian/rules
[21:42] <tseliot> echo "MAKE[0]=\"make module KERNDIR=/lib/modules/\$kernelver IGNORE_CC_MISMATCH=1 SYSSRC=\$kernel_source_dir\"" >> $(CURDIR)/debian/dkms.conf
[21:42] <tseliot> becomes:
[21:42] <tseliot> MAKE[0]="make module KERNDIR=/lib/modules/\ernelver IGNORE_CC_MISMATCH=1 SYSSRC=\ernel_source_dir"
[21:43] <tseliot> and I don't know why $kernelver becomes \ernelver
[21:43] <tseliot> even if I escape the dollar sign with \$ i.e. \$kernelver
[21:45] <rtg_> tseliot: try $(kernel_source_dir) 'cause I think its a make macro.
[21:48] <tseliot> rtg_: mdomsch told me not to expand the variable
[21:49] <rtg_> tseliot: ok, then how about $$kernelver and $$kernel_source_dir
[21:51] <tseliot> rtg_: I get this:
[21:51] <tseliot> MAKE[0]="export IGNORE_XEN_PRESENCE=1; make -C modules /usr/src/nvidia-100.14.23/ -f Makefile.kbuild SYSSRC=/usr/src/linux-headers-2.6.22-14-generic KBUILD_PARAMS=-C
[21:51] <rtg_> tseliot: ok, I don't know enough about the layers of shell scripts and make files.
[21:52] <tseliot> neither do I. thanks for trying ;)
[22:39] <tseliot> rtg_, BenC: I solved it!
[22:39] <tseliot> $$""kernelver
[22:39] <tseliot> $$ gives $
[22:39] <tseliot> however $$kernelver is interpreted as a variable and it's not escaped
[22:40] <tseliot> $$""kernelver means $ + nothing + kernelver
[22:40] <tseliot> yay!


[11:22] <rick_h_> morning all
[11:22] <frankban> morning rick_h_
[11:40]  * frankban lunches
[12:14] <rick_h_> frankban: did you take a peek at the updates to the charm from hazmat? Can those be landed? (around the proxy settings)
[12:16] <frankban> rick_h_: yes I reviewed the branch. hazmat mentioned he want to wait for further live tests/qa before landing those. I assured my availability to do a charm release after those changes are landed
[12:17] <rick_h_> frankban: ah ok, missed the waiting stuff. I added a card to tracking on that for now thanks
[12:17] <frankban> rick_h_: thanks
[12:20] <hazmat> frankban, there are some fixes post the initial pull request, let me update
[12:21] <hazmat> nevermind there in the merge proposal
[12:22] <hazmat> frankban, should i go ahead and just merge to  lp:~juju-gui/charms/trusty/juju-gui/trunk ?
[12:22] <hazmat> or do you want a separate mp targeting that branch first
[12:24] <frankban> hazmat: please go ahead and merge it into the dev branch, I'll work on a charm release in the afternoon
[12:25] <hazmat> ugh.. i forget how slow bzr is ;-)
[12:26] <frankban> heh, the charm repo is pretty big also
[12:27] <rick_h_> luca: do you have hover over info for https://bugs.launchpad.net/juju-gui/+bug/1360169
[12:27] <mup> Bug #1360169: Hover overs are missing from most of the interface <juju-gui:Triaged> <https://launchpad.net/bugs/1360169>
[12:27] <rick_h_> luca__: oh, guess this was going on yesterday, it got caught up in my email backlog and seemed longer than that
[12:31] <hazmat> frankban, done
[12:32] <frankban> hazmat: thanks
[12:34] <rick_h_> frankban: after that gui charm release feel like helping wrap up MV this week?
[12:35] <frankban> rick_h_: sure no problem
[12:35] <rick_h_> frankban: awesome
[12:35] <rick_h_> hazmat: charmworld seems chugging along happier today. Is your stuff all set?
[12:57] <hazmat> rick_h_, yup. all good, thanks
[14:13] <frankban> hazmat: charm released
[14:14] <hazmat> frankban, danke
[14:14] <hazmat> er. grazie ;-)
[14:15] <frankban> :-)
[14:18] <hatch> yaaaaaaawwwwnnnnn
[14:18] <hatch> morning all
[14:18] <urulama> good morning, hatch :)
[14:18] <rick_h_> morn
[14:20] <hatch> so glad to be back at work...needed a break from the holiday haha
[14:37] <rick_h_> frankban: hatch up for a pre-standup chat?
[14:37] <kadams54> hatch: per your comment on PR#523… can you point me to the HTML for the boolean checkboxes? I found some style rules for .config-field.boolean in juju-inspector.less, but am failing to find the corresponding HTML.
[14:37] <hatch> rick_h_: frankban sure just lemme grab my coffee, 2 mins
[14:38] <frankban> rick_h_: sure
[14:38] <rick_h_> frankban: hatch ok, meet you in the standup room
[14:42] <hatch__> rick_h_:  technical difficulties, trying again
[14:42] <hatch__> kadams54: service-configuration.partial or something
[14:43] <kadams54> Thanks, I did look at that but wasn't 100% sure it was the right place. I'll comment further on the PR.
[14:59] <rick_h_> jujugui call in 2
[14:59] <rick_h_> jujugui kanban away please
[15:14] <hatch> lol
[15:14] <hatch> what's martins nick?
[15:15] <rick_h_> mhilton and he's not in here atm
[15:15] <hatch> ahh ok I see in the other channel
[15:18] <hatch> kadams54:  is there a website somewhere which outlines 'why' your approach works? I think my feelings will be assuaged if I can read up on this technique vs the more commonly known single element one
[15:18] <hatch> the css is quite a bit more complex so I'm worried about future dev coming in and not knowing what's going on
[15:18] <kadams54> hatch: http://code.stephenmorley.org/html-and-css/styling-checkboxes-and-radio-buttons/
[15:19] <kadams54> Covers both approaches
[15:19] <hatch> I should really look into how google does the paper elements stuff
[15:19] <hatch> they have some really cool radio/checkboxes
[15:21] <kadams54> I can do some digging into that…
[15:23] <hatch> kadams54:  ok so how about if you just put a comment in the css with this url to explain the technique?
[15:23] <kadams54> hatch: sounds good.
[15:24] <kadams54> I was thinking I could also add classes to the s which could also clarify their purpose.
[15:24] <hatch> ahh yeah that could also help
[15:25] <hatch> it is pretty cool though
[15:26] <kadams54> hatch: so… paper cheats.
[15:27] <kadams54> hatch: it ditches <input> all together in favor of a combination of
s and a <canvas>.
[15:27] <hatch> animated gifs?
[15:27] <kadams54> Hah, no.
[15:27] <hatch> oh haha, really?
[15:27] <hatch> interesting....
[15:28] <hatch> kadams54:  probably because styling inputs on mobile is le'stupid and canvas is going to be pixel perfect every time
[15:28] <kadams54> hatch: https://gist.github.com/kadams54/5e52c25281b364f97b8f
[15:28] <kadams54> I think they only use canvas for the ripple effect that happens when you toggle a button.
[15:28] <kadams54> All the more traditional stuff is all
s
[15:29] <kadams54> They seem to rely heavily on aria markup to make up for the lack of semantic markup.
[15:29] <hatch> I think that the ripple is just layered on top of whatever it's containing
[15:29] <kadams54> http://www.polymer-project.org/components/paper-radio-button/demo.html
[15:30] <hatch> we should use these heh
[15:30] <hatch> so pretttttyyyy
[15:30] <kadams54> hatch: Yeah, the ripple is the canvas. The button itself is just two
s, .offRadio and .onRadio.
[15:30] <kadams54> .onRadio gets a "fill" class when active.
[15:30] <hatch> interesting
[15:30] <hatch> well in any effect, I've +1'd it
[15:30] <kadams54> I suspect the animation is just CSS transitions
[15:31] <kadams54> Not sure how I feel about ditching basic HTML elements all together.
[15:31] <hatch> yeah - I'm guessing that's because of mobile
[15:32] <hatch> styling input elements on mobile is really poorly supported
[15:34] <kadams54> More so than on desktop?
[15:34] <kadams54> I mean, we're already basically hiding the native element and then either sticking in a background image or styling some s to take its place.
[15:35] <kadams54> Largely because desktop browsers vary pretty widely in how (or in the case of Safari, even if) they support styling form elements.
[15:35] <hatch> yeah because you have to remember that there are about 1M different browsers on android
[15:35] <hatch> and that most are complete garbage and don't get updated....ever
[15:35] <kadams54> *sigh*
[15:36] <hatch> it's better now with chrome on android
[15:36] <hatch> but I'm guessing that there are a lot of people who are still using the default browser
[15:36] <hatch> no whatever free phone they 'bought' :P
[15:42] <rick_h_> jujugui make sure you get your travel filed. I think I approved everyone that requested. If you've not please do that and let me know if you hit issues
[15:42] <hatch> oh crap I forgot heh thanks
[15:42] <hatch> rick_h_:  my flights when searching on flights.google changed $700 in one day
[15:42] <hatch> they went back down again
[15:42] <hatch> but I was like....wth
[15:42] <rick_h_> hatch: then file now :P
[15:43] <hatch> lol
[15:43] <rick_h_> I thought I approved yours :P
[15:43] <hatch> you did, I just guessed on the price because of that
[15:43] <hatch> (it's down again)
[15:43] <hatch> BUY BUY BUY
[15:44] <hatch> ehh but the flights suck....
[15:47] <hatch> jujugui, just confirming, the airport is BRU ?
[15:54] <rick_h_> mhilton: did you find the invite for leankit?
[15:54] <rick_h_> mhilton: make sure to check the spam folder
[15:54]  * rick_h_ finds email to make sure he didn't typo the email addr
[16:04] <kadams54> jujugui: looking for a second review/QA on https://github.com/juju/juju-gui/pull/523
[16:06] <kadams54> rick_h_: ready to chat about constraints when you are.
[16:07] <rick_h_> kadams54: k, on the phone atm but can chat later. Not sure when this one will be over
[16:51] <urulama> jujugui: bye, have fun
[16:51] <rick_h_> urulama: have a good night
[17:05] <rick_h_> kadams54: call is over, want to chat now or after lunch?
[17:06] <kadams54> Just getting ready to grab lunch, so after?
[17:06] <rick_h_> kadams54: rgr
[17:06]  * rick_h_ goes to lunch
[17:10] <Makyo> jujugui need some reviews and QA: https://github.com/juju/juju-gui/pull/527 (turned out way easier than I initially made it)
[17:11] <kadams54> Makyo: I'll take a look
[17:12] <Makyo> kadams54, thanks, will look at yours as well.
[17:27] <hatch> lazyPower:  noone wants to answer your AU question :)
[17:27] <hatch> probably because the answer would suck lol
[17:31] <hatch> ok reviews done, conflicts resolved.....now to qa again
[17:49] <Makyo> kadams54, good catch, I should've noticed that.
[17:49] <kadams54> Makyo: np
[18:01] <hatch> jujugui fyi chrome's latest update adds a complex 'ssl warning' page like FF has had for a while - it's now a multi step process to dismiss
[18:01] <rick_h_> hatch: :(
[18:02] <hatch> very
[18:05] <hatch> jujugui in testing my branch after pulling in the latest develop changes I can no longer place a unit on a 'root container' - is this to be expected?
[18:05] <hatch> I don't recall this limitation so - bug?
[18:07] <rick_h_> hatch: hmm, seems like it. Can you git biset from where you're at on that one please?
[18:07] <hatch> yep on it, will report back
[18:07] <rick_h_> hatch: ty much
[18:07] <hatch> could have been a bad conflict resolution here as well..
[18:13] <rick_h_> kadams54: back from lunch?
[18:13] <kadams54> Yup
[18:13] <rick_h_> kadams54: standup hangout?
[18:13] <hatch> https://bugs.launchpad.net/juju-gui/+bug/1364549
[18:13] <mup> Bug #1364549: Cannot destroy services with no deployed units <juju-gui:New> <https://launchpad.net/bugs/1364549>
[18:13] <kadams54> rick_h_: joining
[18:41] <hatch> rick_h_:  https://bugs.launchpad.net/juju-gui/+bug/1364558
[18:41] <mup> Bug #1364558: Unable to place an unplaced unit on root container <juju-gui:New> <https://launchpad.net/bugs/1364558>
[18:43] <rick_h_> hatch: k thx
[18:47] <rick_h_> Makyo: hatch either of you QA kadams54 branch so it can land?
[18:47] <hatch> Makyo:  did according to the pr
[18:47] <Makyo> Yes +1
[18:47] <rick_h_> Makyo: ah, looks like you did, can you add a little more on that qa note per our friday chat the other week
[18:48] <rick_h_> kadams54: and this can shipit then?
[18:48] <Makyo> Ah, sure
[18:48] <rick_h_> Makyo: ty much
[19:03] <kadams54> rick_h_: yup
[19:13] <hatch> lunching
[20:20]  * rick_h_ runs away for today night all
[20:23] <hatch> cya rick_h_
[22:18] <hatch> jujugui lf a review and qa on https://github.com/juju/juju-gui/pull/524 plz and thanks (before something else lands and causes more conflicts :P )
[22:21] <hatch> rick_h_:  any preference to my next card?
[23:03] <huwshimi> Morning
[23:14] <hatch> morning huwshimi
[23:22] <hatch> huwshimi:  if you have some time today it would be awesome if you could review and qa https://github.com/juju/juju-gui/pull/524
[23:23] <huwshimi> hatch: Sure!
[23:24] <hatch> thanks - the code is pretty cryptic without the whole thing in your head so really the important parts are that it qa's properly :)
[23:24] <huwshimi> hatch: OK no problems :)
[23:25] <hatch> I hope we have some time after 1.0 to do some refactoring on this now that we know how it's supposed to work
[23:25] <hatch> we can dramatically simplify it with a rewrite ....er....refactor.....er.....enhancement :P
[23:28] <hatch> huwshimi:  also your travel should have been approved (assuming you filed for it) rick said this morning just fyi
[23:28] <huwshimi> yep, just about to confirm my flight
[23:28] <hatch> it's going to take me 16H
[23:28] <hatch> how about you? :)
[23:29] <huwshimi> 28
[23:30] <huwshimi> Might be 33 on the way back
[23:31] <hatch> jeesh
[23:33] <hatch> huwshimi:  you must be really high up in your airliner frequent flyer program :)
[23:53] <rick_h_> hatch: either one of the bugs (unable to place on a root container, add to my canvas not working in MV) or the limiting options based on provider or the ecs conflict work needed.
[23:53] <hatch> rick_h_:  the add to canvas in mv is not a bug....at least I couldn't reproduce it
[23:53] <rick_h_> hatch: frankban is taking up one of the issues (limiting based on provider or ecs/conflict stuff) so might see what card is taken in the morning
[23:53] <hatch> yeah that'll work
[23:53] <rick_h_> hatch: so it works for you? You see unplaced units or machines start to appear?
[23:54] <hatch> machines appear
[23:54] <rick_h_> oh heh yea I guess it does. wtf
[23:54] <hatch> I'm also not sure about the closing the inspector help text thing....what does that mean?
[23:54] <rick_h_> awesome then, yay
[23:54] <hatch> :)
[23:55] <rick_h_> hatch: so every time you close/reopen the inspector by clicking on a service you get that help text
[23:55] <rick_h_> I think that after you dismis it, it should stay dismissed
[23:55] <rick_h_> I figured that's more a UX front thing that we could get huwshimi or kadams54 or someone to peek at
[23:55] <hatch> sure
[23:55] <hatch> one more
[23:55] <hatch> q
[23:56] <rick_h_> shoot
[23:56] <hatch> machines should not have roll over hover states - don't we want to allow them to drop on machines?
[23:56] <hatch> I have an unplaced unit, I drop it on a machine, it asks me to create a container....etc etc etc
[23:56] <rick_h_> hatch: sure, but right now the roll overs completely hide the create machine. I was thinking that what we could do is enforce the clicking of the machine first
[23:56] <huwshimi> was just about to ask the same question :)
[23:56] <rick_h_> and then you can drop on root container
[23:57] <rick_h_> but right now no one notices the create machine/container header because as soon as you drag you run over machines and they get bright big color changes
[23:57] <rick_h_> I talked to ale/luca about it this morning and they're pondering things but we agreed to start out by trying to hide the hover grey background change
[23:57] <rick_h_> at least then all options are treated equal
[23:57] <rick_h_> and there's less moving bits to distract you
[23:58] <hatch> hmm interesting...
[23:58] <hatch> ok thanks for clearing those up :)
[23:59] <rick_h_> np, happy to entertain other ideas
[23:59] <hatch> I have none, I just didn't think it was an actual issue, but I see now how it could be
[23:59] <huwshimi> rick_h_: Maybe could you add a few more details to the card, just so whoever picks it up knows what to do?
[23:59] <rick_h_> heh, it's a case of it bugged the heck out of me in QA so I made noise to UX :P
[23:59] <rick_h_> huwshimi: sure thing


 vorlon rebuilt qtbase anyway, even after that discussion
 https://matterbridge.lubuntu.me/eec22203/mp4.mp4
 @mitya57
 can't rebuild against openssl 1.1.1 any more as 3 is in release pocket :/
 mitya, your patch in salsa causes qtbase to FTBFS
 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4734/+sourcepub/13037210/+listing-archive-extra
 .obj/qsslkey_openssl.o: in function `QSslKeyPrivate::fromEVP_PKEY(evp_pkey_st*)':
 ./src/network/ssl/qsslkey_openssl.cpp:96: undefined reference to `q_EVP_PKEY_get_base_id(evp_pkey_st const*)'
 collect2: error: ld returned 1 exit status
 make[4]: *** [Makefile:621: ../../lib/libQt5Network.so.5.15.2] Error 1
 make[4]: Leaving directory '/<<BUILDDIR>>/qtbase-opensource-src-5.15.2+dfsg/src/network'
 Ok, I will fix that.
 But are there any issues when the current Qt is built against new OpenSSL and running also with new?
 The previous bug happened only when build-time and run-time versions didn't match
 I see that Fedora switched to OpenSSL 3.0 without any patch for Qt.
 Yes, some parts of KDE still fail to fetch from remote servers: e.g. things from store.kde.org (re @mitya57: But are there any issues when the current Qt is built against new OpenSSL and running also with new?
 The previous bug happened only when build-time and run-time versions didn't match)
 Those some things that broke before don't now
 Can you check if there are any error messages in stderr?
 Ok, I will upgrade my VM again to the proposed version and check
 Thank you.
 https://matterbridge.lubuntu.me/dce23707/file_3605.jpg
 @mitya57 ^
 Thanks. This should be solved by my patch if I make it build successfully.
 Thank you
 Will you mind if I upload new version to your PPA for testing? (re @RikMills: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4734/+sourcepub/13037210/+listing-archive-extra)
 Not at all. Please do
 Done.
 🤞
 Still FTBFS. I will make another attempt later today.
 No problem. I will ask if the proposed version can be removed for now
 Ok. that unfortunate rebuild is removed
 Uploaded version 3
 Fingers crossed again....
 s390x is already building examples, so looks like it will build
 When amd64 is available, I will test
 Thanks :)
 Looking good so far :D
 discover/knewstuff etc now work
 plasma weather widget can now get locations and forecasts
 @mity57 I currently have gear 21.12.0 building in proposed, so don't want to collide a qtbase upload with that just yet
 Ok. Will you make an upload yourself when you think time has come?
 ok if I upload this later? With some additional attribution of the patehjes etc to you 😉
 I am fine doing that. As said, there will be credit to you in the changelog (re @mitya57: Ok. Will you make an upload yourself when you think time has come?)
 Sure. Patch is based on upstream work, so no need to add attribution :)
 Ok . Many many thanks are due and given here then 👍
 I may as well land it from that ppa. Bonus is I can start the build now.


[04:02] <pitti> Good morning
[04:02] <TheMuso> Morning pitti.
[04:03] <pitti> hey TheMuso, how are you?
[04:03] <TheMuso> pitti: Not too bad thanks, yourself?
[04:03] <pitti> TheMuso: pretty good, thanks!
[04:03] <pitti> looking forward to Orlando
[04:03] <TheMuso> Yeah me too.
[04:03] <TheMuso> Not so much the weather, or the travelling, but everything else, yes.
[04:08] <jbicha> what's wrong with the weather?
[04:11] <TheMuso> Well this time last year in Orlando, it was rather hot and humid.
[04:11] <TheMuso> SO I am expecting something similar.
[04:13] <jbicha> hmm, 80s/high 20s, yeah that's a bit warm
[05:08] <pitti> RAOF: if you have some time for SRUs, can you please look at my apport upload? I'm catching up with the other queues
[05:08] <RAOF> pitti: Certainly.
[05:11] <pitti> agateau: please reupload appmenu-qt SRU with a bug reference
[05:20] <pitti> RAOF: all queues clear now, except for apport
[05:20] <pitti> binutils and software-properties need to wait
[05:21]  * micahg thinks pitti is having a weird version day
[05:21] <pitti> ?
[05:21] <micahg> 0.6.14-1git1ubuntu1, 4.24.0-0ubuntu2b1
[05:21] <pitti> oh, for unity? I didn't want to use -ubuntu3, as this shouldn't (need to) go into the VCS
[05:21] <pitti> it's like a binNMU
[05:22] <micahg> pitti: shouldn't the VCS be a record of what was in the archive though?
[05:22] <pitti> it is, the source didn't change
[05:22] <pitti> powerpc was busted
[05:33] <RAOF> pitti: apport looks good; accepted.
[05:33] <pitti> RAOF: thanks
[05:37] <micahg> pitti: makes sense I guess
[05:55] <pitti> jbicha: new mutter regressed on armel (FTBFS)
[06:14] <Sweetshark> Morning Desktoppers!
[06:14]  * Sweetshark is a case of "senile Bettflucht" today (have fun with google translate on that one) ...
[06:24] <pitti> hey Sweetshark
[06:25] <pitti> Sweetshark: not even sure what that means exactly :)
[06:34] <Sweetshark> pitti: wikipedia knows ;)
[06:35] <pitti> Sweetshark: ah, hehe
[06:42] <TheMuso> ?c
[07:06] <GunnarHj> pitti: Good morning, Martin, and thanks for the upload of the a-s branch at bug 868346 to oneiric-proposed. Seems like the powerpc binaries won't be built until tomorrow.
[07:06] <ubot2> Launchpad bug 868346 in lightdm "Language selector broken in Ubuntu" [Medium,In progress] https://launchpad.net/bugs/868346
[07:06] <GunnarHj> pitti: Robert has commented on the lightdm MP, and he asks for your second opinion. I have responded with a branch update and a comment.
[07:15] <chrisccoulson> w00t, i have internets today
[07:16] <RAOF> No internets yesterday?
[07:16] <pitti> hey chrisccoulson
[07:16] <chrisccoulson> hi pitti, how are you?
[07:16] <pitti> pretty well, thanks!
[07:16] <chrisccoulson> RAOF, no, i had no connection (other than my 3G) for the whole day yesterday
[07:16] <pitti> oh, and no didrocks to remind me about the meeting reminder
[07:17] <chrisccoulson> it was still broken at 2am this morning
[07:17] <pitti> I wonder if it's worth having a meeting today in the first place, with half of the crew being on travel/at sprint, and we see each other all next week
[07:17] <RAOF> chrisccoulson: Boo, hiss.
[07:24] <RAOF> You know what?  I shouldn't have bothered with starting a deja-dup backup to Ubuntu One.  My ADSL2+ pipe just doesn't have the bandwidth to make it fun.
[07:27] <RAOF> pitti: I think one of my replies to the techboard is sitting in moderation.  Could you please give it a prod if it is?
[07:27] <pitti> sure
[07:28] <RAOF> Ta muchly.
[07:28] <pitti> RAOF: done
[07:30] <RAOF> I guess the tech board agenda page is wrong, too; it's unlikely that the next meeting is on 2011/10/20 ;)
[07:31] <pitti> that was the last one indeed
[07:33] <chrisccoulson> pitti - are you able to kill builds? (eg, https://launchpad.net/ubuntu/+source/firefox/8.0~b4+build1-0ubuntu1/+build/2865778)
[07:33] <chrisccoulson> that's been hung for 5 days
[07:33] <pitti> chrisccoulson: no, only IS can do that
[07:33] <chrisccoulson> ah
[07:34] <pitti> chrisccoulson: if you could ping #is ?
[07:34] <chrisccoulson> pitti - sure, just done that now
[07:52] <htorque__> hello everyone! if the update manager's changes window opens like this: http://i.imgur.com/SCstI.png - against which package should i report a bug (or look for an existing one)?
[07:53] <pitti> htorque__: update-manager seems right
[07:53] <htorque__> so this is no gtk issue?
[07:54] <RAOF> Probably easier to start by assuming it's an update-manager problem; if it's a gtk issue it's easy to reassign.
[07:54] <htorque__> ok, thanks guys!
[07:57] <pitti> RAOF: do you have a minute to review my pygobject oneiric-proposed upload?
[07:57] <pitti> quite a few people wait for that
[07:57] <RAOF> Didn't we already upload pygobject to proposed?
[07:57] <pitti> RAOF: yes, that one is in -updates now
[07:57] <RAOF> There's a new and shiny one? :)
[07:58] <pitti> the oneiric version starts being a nice debian/patches/00git_*.patch collection :)
[07:58] <pitti> at least we are getting everything upstream, experimental/precise have zero patches
[07:58] <pitti> RAOF: yes, now with 50% more love!
[07:59] <pitti> you can even put the love into variants, and those into arrays
[07:59] <pitti> my_love_array = [GLib.Variant('l', '♥')]
[08:00] <RAOF> :)
[08:00] <pitti> hmm, that seems to be a font bug -- '♥ ' with an extra space looks even shinier
[08:00]  * RAOF needs to fix his IRC bouncer's unicode handling
[08:00] <pitti> RAOF: oh, you don't get them properly?
[08:01] <RAOF> Yeah, I think I don't have the locale set.
[08:01] <pitti> how were you ever able to read my shiny ¡ɐıןɐɹʇsnɐ ƃuıuɹoɯ pooƃ then?
[08:02] <RAOF> Because I recently moved my IRC bouncer to the cloud :)
[08:03] <pitti> oha
[08:03] <pitti> mine runs on my colo server
[08:03] <pitti> RAOF: so you have an EC2 something now?
[08:03] <RAOF> I'm trying out the CanoniStack
[08:05] <RAOF> Hm.  At what point did it become 7pm?
[08:05] <RAOF> Curse, you, orbital tilt!
[08:05] <micahg> RAOF: about 8 hours ago for me :)
[08:56] <czajkowski> morning
[09:59] <didrocks> good morning
[10:00] <rodrigo_> am I in?
[10:02] <ricotz> rodrigo_, looks like so
[10:29] <didrocks> pitti: hey, how are you?
[10:29] <pitti> bonjour didrocks
[10:29] <pitti> didrocks: how's Orlando?
[10:29] <didrocks> pitti: foggy
[10:29] <didrocks> but it was better yesterday afternoon
[10:30] <didrocks> let's wait for a few days and crossing fingers :)
[10:30] <didrocks> otherwise, nothing release changed
[10:30] <didrocks> really*
[10:31] <didrocks> pitti: I had a question about your unity rebuild for powerpc, it's not possible to just have a give back on powerpc for the -proposed pocket? (just curious)
[10:31] <pitti> didrocks: it's more complicated
[10:31] <pitti> didrocks: I didn't see that powerpc FTBFSed, so I did the usual routine of copying to precise and oneiric-updates
[10:31] <pitti> copying to precise needs to happen first (LP quirk)
[10:31] <pitti> but then the failed powerpc build started again on precise
[10:31] <pitti> during that you can't copy to -updates
[10:31] <pitti> and precise succeeded
[10:32] <didrocks> ah, ok, make sense :)
[10:32] <pitti> so I now had a precise powerpc build for the oneiric SRU
[10:32] <didrocks> yeah, quite not trivial
[10:32] <pitti> and this was totally wrecked
[10:32] <pitti> the only real way to fix this was a new source upload, sorry
[10:32] <pitti> powerpc is busted, libgnome-desktop3 is not installable for some reason, and I don't know why
[10:32] <didrocks> oh no worry, was just interested in why it was needed :)
[10:32] <pitti> the porter chroots have no -proposed
[10:32] <didrocks> urgh, not good
[10:33] <pitti> and I didn't find a powerpc FTBFS which caused thsi
[10:33] <pitti> https://launchpad.net/ubuntu/oneiric/+builds?build_text=&build_state=failed&arch_tag=powerpc
[10:33] <pitti> the very first -proposed FTBFS there is already due to the libgnome-desktop3 installability
[10:33] <pitti> so, NFC about that one :(
[10:35] <didrocks> pitti: "the porter chroots have no -proposed", you mean, you can't log on adare for instance, get a chroot there and apt-get install the deps to be able to see what's wrong?
[10:35] <pitti> didrocks: correct
[10:35] <pitti> in -updates everythign is fine
[10:36] <didrocks> waow
[10:36] <pitti> well, at least apt-get install doesn't complain
[10:36] <didrocks> it will block a lot of updates…
[10:36] <didrocks> yeah
[10:36] <pitti> it might very well be a binary in universe or so
[10:36] <didrocks> hum, how come? you mean the binary would have been incrr
[10:36] <didrocks> incorrectly copied to universe?
[10:36] <pitti> perhaps
[10:37] <pitti> I really don't know
[10:37] <pitti> and I don't feel like sitting down for hours trying to debug this, since frankly, I effing don't care about powerpc
[10:37] <didrocks> yeah, those install issues are quite a pain, not sure if soyuz can be better in detecting that and trying to recursively install deps so that we can have more insight just looking at logs
[10:37] <didrocks> indeed
[10:37] <chrisccoulson> heh, +1000 about not caring about powerpc
[10:38] <didrocks> seems we don't ship anymore /usr/share/applications/nautilus-folder-handler.desktop
[10:39] <didrocks> causing bug #876788
[10:39] <ubot2> Launchpad bug 876788 in nautilus "Many users upgrading from 11.04 or eariler will be unable to open trash; flash drives & if using Classic session places in nautilus" [Undecided,New] https://launchpad.net/bugs/876788
[10:40] <didrocks> seems we don't have any desktop file providing this anymore
[10:40] <didrocks> I guess it's because nautilus 3 dropped the "show desktop option"
[10:40] <didrocks> and so don't need a --no-desktop one
[10:41] <didrocks> (desktop file)
[10:53] <didrocks> running nautilus %U seems to DTRT
[11:04] <rodrigo_> can anyone replicate https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/878486 ?
[11:04] <ubot2> Launchpad bug 878486 in gnome-settings-daemon "gsd-printer crashed with SIGABRT in __kernel_vsyscall()" [Medium,In progress]
[12:07] <chrisccoulson> hmm, i think it might be time to restart my session
[12:07] <chrisccoulson> it's only lunchtime, and it already feels like it's been filled with glue
[12:18]  * rodrigo_ lunch
[12:22]  * kenvandine heads out to get a flu shot before risking ubuflu, be back in a bit
[12:40] <pitti> dpm: just saw Kenneth's mail about getting full -base oneiric langpacks this week
[12:41] <dpm> hi pitti
[12:41] <pitti> dpm: I disabled the cronjob and told https://translations.launchpad.net/ubuntu/oneiric/+language-packs to get me a full export
[12:41] <pitti> dpm: but the next automatic one will only arrive on Friday, right?
[12:41] <pitti> and I'll be on holiday then
[12:41] <pitti> dpm: would it be possible to kick off an export now?
[12:42] <pitti> dpm: alternatively I can manuall fake one by taking the last full and yesterday's delta tarball
[12:42] <pitti> depending on how recent we want this to be
[12:44] <dpm> pitti, yeah, the next one will be available on Friday. Let me see if a Launchpad losa can arrange an export for us. I think that'd be less work for you.
[12:44] <pitti> dpm: it's not much work to generate a merged one
[12:44] <pitti> I have a script for it
[12:44] <pitti> but it wouldn't be the latest and greatest translations
[12:45] <dpm> pitti, let me ask on #launchpad for someone to arrange the export, and if they haven't come back to us in ~1h, let's go for the merged one. What do you think?
[12:45] <pitti> dpm: sounds great
[12:47] <dpm> ok, asked on #launchpad
[12:54] <pitti> dpm: cheers
[13:01] <cyphermox> good morning@
[13:04] <dpm> pitti, translations full export running. If nothing breaks in the meantime, it should be available in ~16 hours time
[13:04] <pitti> dpm: yay, thanks
[13:04] <dpm> np :)
[13:55] <mitya57> Can somebody help me?
[13:56] <mitya57> I just received a mail from Launchpad
[13:56] <mitya57> On 2011-10-25 12:03z (1 hours 43 minutes ago), you uploaded a file with Hausa (ha) translations for nautilus in Ubuntu Oneiric package "nautilus" to Launchpad.  We were unable to import the file because of errors in its format:  Line 7165: Unsupported plural case number.
[13:56] <mitya57> Line 7165 of that file is "#~ msgstr[6] ""
[13:58] <jbicha> I merged webkit 1.6, is there a particular time of day it's better to push that into the repositories?
[14:03] <CarlFK> mitya57: whats line 7166?   (maybe the reject line starts at 0)
[14:05] <mitya57> CarlFK: 7166: #~ "<b>Irin Zane:</b> %s (%s)\n"
[14:06] <mitya57> All lines from 7088 are commented out
[14:07] <mitya57> And I didn't change anything related to translations in this upload
[14:08] <cyphermox> mitya57: translations get merged with LP too
[14:10] <mitya57> cyphermox: I know, of course, but I'm just wondering what's the case of this error
[14:10] <cyphermox> heh, check line 7165? :)
[14:10] <cyphermox> nevermind, I see it up
[14:12] <mitya57> Anybody can find it @ http://launchpadlibrarian.net/83650335/ha.po
[14:17] <cyphermox> mitya57: afaict it should have failed parsing before that
[14:18] <cyphermox> nplurals=2 in headers, you should only have up to two entries for msgstr[x]... that said, it also shouldn't crash because that's all commented out :)
[14:18] <dobey> right
[14:19] <dobey> what cyphermox said. 6 > 2, and so there's a problem :)
[14:19] <mitya57> Should I acknowledge "ha"-translationteam?
[14:20] <mitya57> BTW, 5 also > 2, why it doesn't like *that* line?
[14:25] <cyphermox> mitya57: clearly there's a bug there in what parses the po file
[14:28] <cyphermox> mitya57: I wouldn't worry *too* much about the error message, but still file a bug against launchpad for the error, possibly with that ha.po file attached
[14:28]  * mitya57 is reporting a bug
[14:35] <mitya57> cyphermox: https://bugs.launchpad.net/launchpad/+bug/319243 explains the situation
[14:35] <ubot2> Launchpad bug 319243 in launchpad "KeyError for excessive plural forms" [Medium,Fix released]
[14:35] <mitya57> Launchpad doesn't support >= 6 plural forms (starting with 0)
[14:36] <mitya57> And it tries to load them even if they're commented (to show them in "Suggestions")
[14:38] <cyphermox> ah, interesting
[14:38] <cyphermox> well, now we know
[14:39] <cyphermox> as for the rest, it remains "wrong" to keep 27 different plural forms, but that's just something to bring up upstream for them to clean up their po files
[14:42] <dobey> well, it's not wrong, if the language has 27 different plural forms
[14:42] <dobey> but i'm pretty sure Hausa doesn't, given the header stating it only has 2 :)
[14:56] <cyphermox> d'oh, he's gone
[14:56] <cyphermox> https://bugs.launchpad.net/launchpad/+bug/319243 would have benefited a re-open I guess
[14:56] <ubot2> Launchpad bug 319243 in launchpad "KeyError for excessive plural forms" [Medium,Fix released]
[14:57] <cyphermox> actually nevermind, I just fail at parsing the bug description
[15:14]  * jbicha looks for a sponsor for webkit 1.6...
[15:31] <cyphermox> seb128: what would be the best way to deal with an extra patch I'd like to add to e-d-s 3.2.1-0ubuntu1 (to fix POP delete-after-days); just upload 3.2.1-0ubuntu2 to -proposed?
[15:31] <seb128> cyphermox, yes
[15:31] <seb128> cyphermox, is the bug a regression from the current sru?
[15:32] <cyphermox> that's just going to superseded it
[15:32] <cyphermox> no, it's something else on top of it
[15:32] <cyphermox> it was broken in 3.2.0 too
[15:32] <seb128> how long is the sru in?
[15:32] <cyphermox> that's why people lost email on pop accounts, it defaulted to delete after 7 days, I discussed it with mbarnes and the default is changed to 0
[15:32] <seb128> either you wait for the new one to move to updates
[15:32] <cyphermox> 6 days now
[15:32] <seb128> or reactivate the counter with a new one
[15:33] <pitti> hey seb128
[15:34] <seb128> hey pitti, how are you?
[15:34] <pitti> seb128: pretty well, thanks! how is the sprint going?
[15:34] <seb128> pitti, quite good so far
[15:34] <seb128> doing a lightdm SRU hacking session with robert_ancell and agateau at the moment
[15:35] <pitti> nice!
[15:36] <seb128> pitti, good SRU work today btw
[15:36] <seb128> nice to see those pygobject and nautilus bugs fixedf
[15:36] <pitti> thanks; got these nautilus patches reviewed, and some pygobject fixes
[15:37] <seb128> saw that ;-)
[15:37] <ricotz> hello
[15:38] <seb128> do we have sometime who feels like working on bug #873334
[15:38] <ubot2> Launchpad bug 873334 in lightdm "the upstart job is missing support for 'text' command" [Low,Triaged] https://launchpad.net/bugs/873334
[15:38] <ricotz> pitti, hi :), the mutter update has the same issue last time, it includes a debian-changes patch which reverts the former one
[15:39] <ricotz> *as last time
[15:39] <seb128> bug #864174 as well
[15:39] <ubot2> Launchpad bug 864174 in lightdm "boot hangs waiting for lightdm after purging gdm (wrong default-display-manager)" [High,Won't fix] https://launchpad.net/bugs/864174
[15:39] <pitti> ricotz: argh
[15:39] <seb128> (it seems prerm in gdm screw the default)
[15:40] <ricotz> pitti, would you be so kind and bump these ppa builds? https://launchpad.net/~xorg-edgers/+archive/ppa/+builds
[15:41] <ricotz> https://launchpad.net/~xorg-edgers/+archive/ppa/+builds?build_text=&build_state=pending
[15:41] <pitti> ricotz: done
[15:42] <ricotz> pitti, thank you
[15:42] <pitti> seb128: can do 873334, feel free to assign to me
[15:42]  * pitti bbl
[15:43] <seb128> pitti, danke
[15:46] <desrt> seb128: you're missing an awesome meeting!!
[15:47] <seb128> desrt, oh, what a shame!!!
[15:49] <jbicha> seb128: are any of 3.3 updates safe or should we wait to discuss next week?
[15:49] <seb128> jbicha, wait for next week
[15:50] <seb128> we don't know if they will depends on i.e new glib or new GTK in a month time and if that would conflict with decision we will take
[15:50] <jbicha> ok, no problem
[15:56] <jbicha> so mutter ftbfs on arm but I don't have a clue how to handle arm build failures
[15:58] <ogra_> not differently to any other build failures i would propose
[15:58] <ogra_> read the logs, identify the issue, google for a patch, if you dont find one, file a bug and notify ubuntu-arm and linaro
[15:58] <ricotz> jbicha, hi, it includes a debian-changes patch which is probably the reason
[15:59] <jbicha> ricotz: thanks
[15:59] <jbicha> ogra_: well I don't have any Ubuntu-capable ARM hardware to verify whether something works
[16:00] <ogra_> jbicha, but you can read logs :)
[16:00] <ricotz> jbicha, if you are looking for an update gconf 3.2.1 would be nice (when it gets released)
[16:00] <ogra_> eventually it might end up in #ubuntu-arm, but its always helpful for us if the dev does at least some research in advance
[16:01] <ricotz> you can set up a builder using qemu too
[16:01] <ogra_> jbicha, and i'm fighting hard with the management to get at least one arm device into every team
[16:01] <jbicha> my primary laptop has stupid Intel no-hardware-virtualization
[16:01] <ogra_> so someone in -desktop should eventually be able to help doing a test build
[16:02] <ogra_> up to then you have us (ubuntu-arm)
[16:02] <jbicha> ricotz: yes, I'm waiting for gconf 3.2.1 too
[16:04] <ogra_> we're also trying to get public arm PPAs ready since a while, sadly now armhf came up which steals the buildds dedicated for this
[16:05] <ogra_> once thats bootstrapped there should be public arm PPAs though, so you can do testbuilds yourself
[16:05] <ricotz> ogra_, nice, this sounds great
[16:06] <ogra_> ricotz, yeah, sounded great over a year ago already ... sadly life in arm land is slow ...
[16:07] <ogra_> (we should move to "leg" that should be able to _run_ faster :P )
[16:07] <Laney> everyone wants that gconf
[16:07] <Laney> banshee chewing the cpu is trés annoying
[16:07] <ogra_> Laney, well, i wish it would chew cpu here
[16:07] <ogra_> it sadly doesnt get that far on arm
[16:07] <Laney> i heard :(
[16:08] <Laney> is it mono or banshee that broke?
[16:08] <ogra_> tomboy and f-spot work in tests
[16:08] <ogra_> so i would say either banshee itself or some special function the others dont use
[16:09] <Laney> did you try banshee 2.2.0 w/mono 2.6 (natty)?
[16:09] <ogra_> i think NCommander and GrueMaster tried a lot of combos
[16:10] <Laney> try the muinshee interface
[16:10] <Laney> that should have a lot less gtk (to see if it's the custom widgetry)
[16:11] <ogra_> Bug 857299 btw
[16:11] <ubot2> Launchpad bug 857299 in banshee "banshee window remain white on startup on armel" [High,Confirmed] https://launchpad.net/bugs/857299
[16:29] <bjsnider> ricotz, i think gconf 3.2.1 is being released today
[16:29] <bjsnider> and it fixes at least 2 bugs
[16:32] <ricotz> bjsnider, yeah, but there isnt a tarball yet
[16:41] <pitti> good night everyone!
[16:43] <dobey> night pitti
[16:44] <dobey> mterry: can you get my two oneiric-proposed proposals into oneiric-proposed (at least uploaded and waiting for archive admin to approve)?
[16:44] <achiang> has anyone heard of a bug where moving your mouse to the left edge of the desktop causes the screen to go blank?
[16:44] <achiang> running unity in oneiric
[16:44] <achiang> didn't see anything in a quick search in LP
[16:46] <dobey> that sounds extremely weird
[16:47] <achiang> does the fact that synergy is running, and that the 2nd panel is on the left edge have anything to do with it?
[16:48] <mterry> dobey, ok.  The two "slow music store link" ones?
[16:51] <dobey> mterry: yep. libu1 and banshee; the banshee one also fixes a more severe issue where banshee ends up going nuts, if there is no network
[16:53] <achiang> seb128: ^^
[16:54] <seb128> no I didn't
[16:55] <achiang> seb128: any clues on how to start debugging?
[16:56] <seb128> no idea, maybe #ubuntu-x guys have an issue or the xorg logs
[16:56] <seb128> seems like it could be a video driver bug
[16:56] <achiang> seb128: ah, ok. should have started there, thanks
[16:58] <seb128> yw
[17:28] <zyga> hi, where does LANGUAGE get set?
[17:28] <zyga> somehow my language is set to chinese and I cannot change it in the language selector applet
[17:28] <zyga> (it is grayed out)
[17:28] <zyga> out)
[17:31] <dobey> zyga: usually you pick it when logging in
[17:31] <dupondje> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/868032 => could somebody check this one ?
[17:31] <ubot2> Launchpad bug 868032 in nautilus "nautilus progress window marked skipped, not managed by gnome-shell" [Low,Confirmed]
[17:31] <zyga> dobey, in lightdm?
[17:31] <zyga> dobey, where?
[17:31] <dupondje> seems like its caused by a patch in ubuntu only
[17:32] <dobey> zyga: there is a gear icon next to your name i think, you click on that and choose language, iirc
[17:32] <zyga> dobey, I just did, I could select my session, not language though
[17:32]  * zyga logs out to check again
[17:32] <cyphermox> zyga: no need
[17:33] <cyphermox> it's not there
[17:33] <dobey> oops
[17:41] <dobey> oh i guess it's not there :(
[17:41] <dobey> and is supposed to be an indicator thing at the top of lightdm i suppose, but also not there
[17:42] <cyphermox> zyga: what's greyed out in language-selector, the language list at the top?
[17:42] <zyga> cyphermox, yes
[17:42] <zyga> it's highly unintuitive
[17:42] <zyga> I managed to drag english to the top
[17:42] <cyphermox> quite unusual
[17:43] <cyphermox> ok
[17:43] <cyphermox> that should be enough
[17:43] <zyga> chinese was at the top and I did not know how to move it down
[17:45] <zyga> anyway, I could _not_ change language in lightdm
[17:46] <dobey> zyga: yeah, that is apparently a rather horrible regression in oneiric :(
[17:48] <zyga> dobey, I don't mind it being missing that much, I just did mind chinese :)
[17:48] <zyga> LANGUAGE is confusing to be honest
[17:48] <zyga> it seems to be crashing xchat-gnome here
[17:56] <mterry> dobey, heyo.  a couple things about your u1ms patches
[17:57] <dobey> mterry: hey
[17:57] <mterry> dobey, (1) the libubuntuone patch doesn't apply cleanly to oneiric.  Easy to fix, but looks like it was originally made on a different version of the source
[17:57] <dobey> eh?
[17:57] <dobey> it applies here
[17:58] <dobey> hrmm
[17:58] <dobey> i'll look, and yes it's easy to fix if it doesn't
[17:59] <mterry> dobey, had to apply this patch to the tree: dobey, (2) after both patches, starting Banshee with a long do
[17:59] <mterry> whoops
[17:59] <mterry> dobey, this patch: http://pastebin.ubuntu.com/719040/
[17:59] <mterry> dobey, (2) after both patches, starting Banshe with a u1ms URL does not switch to the music store after startup
[18:00] <dobey> sigh
[18:01] <mterry> will make those comments on the merges too, for posterity
[18:01] <dobey> yeah
[18:01] <dobey> banshee is not fun
[18:02] <dobey> i was having that issue as well in testing, as there seems to be a race within banshee itself
[18:02] <mterry> :-/
[18:03] <dobey> i could repeat it easily even. while i was testing, i added a logging call to another part of the banshee code, to help debug. when i did that, it started working right. then i removed that added call and it continued to work correctly :(
[18:04] <dobey> so i really have no idea why it's not switching, exactly. stupid heisenbug race inside banshee :(
[18:05] <mterry> dobey, does it do that before your patches?
[18:06] <dobey> mterry: currently in oneiric, loading a u1ms:// url will take at least 10 seconds after banshee is started, to happen. so it simply isn't there because it's way after it would occur
[18:07] <mterry> dobey, I see, "working through obscurity"  :)
[18:07] <dobey> mterry: but current banshee is weird, because if you click and link, and banshee opens, and you hit play or something, it will just seemingly randomly switch to the u1ms view
[18:49] <mterry> @pilot out
[18:49] <mterry> whoops
[19:27] <mterry> tremolux, today, all the for-purchase apps lost their icons in software-center.  :-/
[19:28] <tremolux> mterry: hrm, yes, I see that  :/
[19:30] <tremolux> mterry: I'll look into this, thank you for the head's up!
[19:31] <dobey> mterry, tremolux: what airline are you guys taking to orlando? i don't recognize "b6" :)
[19:32] <tremolux> dobey: JetBlue, but..."b6"??
[19:33] <tremolux> mterry: if you click into the description page for one of the apps, does the icon appear (after a short moment?)
[19:33] <dobey> tremolux: yeah, i was looking at the canonical wiki page that lists everyone to see who was arriving the same time as i, and saw your flight numbers were "b6 432" or something like that
[19:33] <mterry> tremolux, yeah
[19:34] <mterry> tremolux, but even after doing that, the main page doesn't update to show the icon
[19:34] <mterry> ("main page" == "welcome/dashboard thing")
[19:35] <tremolux> mterry: yep, but if I restart s-c, it does for me
[19:36] <mterry> tremolux, yup, you're right
[19:36] <tremolux> mterry: (initial guess) seems like the icons were updated on the server side for some reason, and so the cache was no longer valid
[19:36] <tremolux> mterry: and the new UI isn't good about handling an updated cache in the main screen
[19:36] <mterry> tremolux, this was around the time that I noticed we have new books for purchase (which, btw, don't appear as newer than the other packages, though I'm 99% confident they are)
[19:37] <mterry> tremolux, so I could easily believe updated server-side cache
[19:47] <tremolux> mterry: yep, looking in my cache I can see the icon names are all new...hrm
[19:49] <achiang> hi, if one is using ccm and has disabled "bring to front on click".... how do you actually bring the window to the front after that? :)
[19:49] <mterry> achiang, alt-tab?

[19:49] <achiang> mterry: i guess the old behavior was alt-click
[19:50] <jbrett> achiang is asking because I asked him in another channel. :)
[19:50] <mterry> achiang, there are a few patches against compiz adding alt-click in LP
[19:50] <achiang> mterry: ah, nice! so currently known to not work?
[19:50] <mterry> achiang, yeah
[19:51] <achiang> mterry: do you happen to have the bug # handy? then jbrett can go subscribe
[19:51] <jbrett> mterry: is that by design, or a bug?
[19:52] <mterry> achiang, jbrett: bug 881329 and bug 880672
[19:52] <ubot2> Launchpad bug 881329 in compiz "Alt+click should raise with raise-on-click disabled" [Undecided,New] https://launchpad.net/bugs/881329
[19:52] <ubot2> Launchpad bug 880672 in unity "Clicking panel should raise maximised window with raise-on-click disabled" [Undecided,New] https://launchpad.net/bugs/880672
[19:52] <mterry> jbrett, likely a bug
[19:52] <achiang> mterry: woot, thanks
[19:52] <mterry> an overlooked use case
[19:52] <jbrett> mterry: thx!
[20:05] <dobey> hrmm
[20:19] <jbrett> wow, this whole global/galactic menu thing really sucks, especially with focus-follows-mouse turned on.
[20:20] <jbrett> by the time I navigate across my screen to get to the menu bar, I've usually inadvertently passed over some other window, so I get the wrong menu.
[20:20] <jbrett> double-lose..
[20:37] <mterry> jbrett, yeah, focus-follows-mouse is rough.  I think there are existing bugs/thoughts on solving it.  But I don't know those bug numbers off hand like I did the alt-click ones
[20:37] <jbrett> https://bugs.launchpad.net/unity/+bug/674138
[20:37] <ubot2> Launchpad bug 674138 in unity ""Global" appmenu breaks sloppy focus" [Low,Won't fix]
[20:37] <jbrett> :)
[20:37] <mterry> there ya go
[20:38] <jbrett> looks like the only way to make it usable for now is "apt-get purge appmenu\*" :(
[20:39] <jbrett> I'm trying really hard not to just disable stuff I dislike at first (like the GM), as I assume there was some thought and effort put into it, and once I get over the "this isn't the same as what I'm used to" stage, I might actually like it :)
[20:39] <jbrett> but I'm not finding another way around this one, if it's marked "won't fix"..
[20:54] <desrt> ronoc: yo
[20:54] <ronoc> desrt, hey
[20:54] <ronoc> https://bugs.launchpad.net/ubuntu/+source/unity/+bugs?search=Search&field.importance=Critical&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed
[20:55] <desrt> 'debian it not work good on my PC'
[22:20] <m4n1sh> I keep getting "totem-playlist.h:65:2: error: unknown type name 'GtkVBox'" everytime I try to build totem
[22:20] <m4n1sh> anyone else getting it
[22:20] <m4n1sh> is this something to do with dependency not being correct?
[22:24] <RAOF> m4n1sh: Is that in a build chroot?  It sounds like a missing #include, missing dependency, or (least likely) GtkVBox being removed after deprecation.
[22:25] <m4n1sh> RAOF: not doing on a chroot
[22:25] <m4n1sh> doing it in a clean vm
[22:26] <m4n1sh> did a build-dep totem
[22:26] <m4n1sh> and then installed valac and libzeitgeist-dev to enable a plugin which is a soft-dep
[22:26] <m4n1sh> RAOF: I got this version from ubuntu's version
[22:27] <m4n1sh> I guess there is a downstream patch
[22:27] <RAOF> Possibly, but that seems strange.
[22:28] <m4n1sh> nope. not available
[22:28] <m4n1sh> initially it failed to build on oneiric
[22:28] <m4n1sh> so i tried on a clean chroot using pbuilder
[22:28] <m4n1sh> failed
[22:28] <m4n1sh> and then now trying in a vm
[22:29] <m4n1sh> apt-get build-dep should install all the dependencies
[22:29] <jbicha> are you using any PPAs? it's totem you're trying to build, right?
[22:31] <m4n1sh> jbicha: yes
[22:31] <m4n1sh> not using any PPA on a fresh vm
[22:32] <jbicha> which version of totem?
[22:32] <m4n1sh> the one present in oneiric
[22:32] <m4n1sh> got it using apt-get source
[22:32] <m4n1sh> output where it fails
[22:32] <m4n1sh> http://paste.ubuntu.com/719251/
[22:33] <m4n1sh> jbicha: if I remember, you take care of totem
[22:35] <jbicha> m4n1sh: not exactly, but I did do the last upload a week ago; I'm not sure what's wrong with your setup
[22:36] <jbicha> do you know how to use sbuild or pbuilder?
[22:36] <m4n1sh> yes
[22:36] <m4n1sh> I did that too
[22:36] <m4n1sh> failed
[22:36] <m4n1sh> that is what troubling me
[22:36] <m4n1sh> doing it in a clean chrooted environment should be fine
[22:39] <RAOF> It's just built successfully for me.
[22:40] <m4n1sh> :(
[22:41] <jbicha> m4n1sh: ask your computer's manufacturer for a refund! ;)
[22:42] <m4n1sh> jbicha: :)
[22:42] <m4n1sh> there is a package named libtotem-plparser-dev
[22:42] <m4n1sh> jbicha: is this the cause of the problem?
[22:43] <m4n1sh> grr. it is already installed
[22:43] <jbicha> m4n1sh: you can compare with the build logs at https://launchpad.net/ubuntu/+source/totem/3.0.1-0ubuntu7.1
[23:31] <dobey> m4n1sh: do you have the build flag enabled which disables the usage of deprecated APIs in GTK?
[23:31] <m4n1sh> dobey: nope
[23:31] <m4n1sh> now I checked. it works fine in chrooted environment
[23:31] <m4n1sh> but not on my dev machine
[23:32] <dobey> m4n1sh: are you *sure* about that? it sounds like your problem is exactly that
[23:32] <m4n1sh> I have gnome2 enabled too
[23:32] <m4n1sh> dobey: but I also had it running on a fresh oneiric install
[23:32] <m4n1sh> inside a vm
[23:32] <dobey> m4n1sh: no CFLAGS env var set or anything?
[23:32] <m4n1sh> nope
[23:32] <m4n1sh> got a fresh oneiric vm
[23:32] <m4n1sh> apt-get build-dep totem
[23:33] <m4n1sh> and got 2 more -dev packages
[23:33] <m4n1sh> and tried building
[23:33] <m4n1sh> failed
[23:36] <RAOF> dobey: Is GtkVBox deprecated?
[23:36] <m4n1sh> it does show in Gtk3
[23:36] <dobey> yes
[23:36] <bryceh> bugs #876711<PHONE_NUMBER>32 873191  are all broken brightness functionality, mostly starting around a couple weeks ago.  anyone recognize that offhand?  known gnome-power-manager issue?
[23:36] <ubot2> Launchpad bug 876711 in xserver-xorg-video-intel "Screen brightness resets to minimized when screen turns off" [Medium,Confirmed] https://launchpad.net/bugs/876711
[23:37] <RAOF> Ah, I clearly need to revise my Gtk :)
[23:37] <m4n1sh> RAOF: dobey: install the package libgtk-3-dev and check  /usr/include/gtk-3.0/gtk/gtkvbox.h
[23:38] <m4n1sh> I hope this is the correct dev package
[23:38] <dobey> m4n1sh: check it for what? it's there, but it's deprecated
[23:38] <m4n1sh> dobey: then what is the -dev package for gtk?
[23:38] <dobey> m4n1sh: what do you mean?
[23:39] <m4n1sh> means totem is dependent on gtk
[23:39] <m4n1sh> libgtk-3.0
[23:39] <dobey> VBox is deprecated
[23:39] <m4n1sh> so to compile totem
[23:39] <m4n1sh> gtk's development headers need to be there
[23:39] <dobey> yes, and apparently is using deprecated API
[23:39] <dobey> yes, and you had the totem-dev package installed without the gtk-dev package?
[23:41] <m4n1sh> ?
[23:41] <m4n1sh> didnt understand
[23:42] <dobey> you had the totem development stuff installed, but it didn't pull in the ones that totem depends on (ie gtk+)?
[23:43] <m4n1sh> yes
[23:43] <m4n1sh> i installed totem build-deps
[23:53] <RAOF> Mmmmm.  Non-deterministic kernel panics on boot.  This laptop really has had a bad week. :(


[02:00] <seb128> could somebody review unity-gtk-module in the trusty SRU queue? it was uploaded with gtk, which got approved, but they would need to go together for the fix to be fully functionnal
[02:00] <seb128> until then nothing is buggy, but the bugfix can't be verified
[02:00] <seb128> (need to go to the office, bbiab)
[08:26] <Riddell> anyone care enough about ppc64el to investigate okteta build failure? https://launchpad.net/ubuntu/+source/okteta upstream disclaims liability https://bugs.kde.org/show_bug.cgi?id=338032
[08:40] <xnox> Riddell: a bit cryptic =) why would ld exit 1, if it only issued a warning and not an error. I think infinity and/or doko might find ^ interesting
[09:46] <doko> Riddell, where is the error? apparently it did build
[09:48] <Riddell> doko: launchpad says it didn't https://launchpad.net/ubuntu/+source/okteta/4:4.13.97-0ubuntu1/+build/6233320
[09:51] <doko> ahh, latest upload was trusty
[09:54] <doko> Riddell, please can you address upstream, that explicit linking with -lc on linux is not necessary?
[10:09] <popey> infinity: when should 12.04 users expect to get a prompt to go to 14.04? (.1)
[10:12] <mlankhorst> I thought the EOL notification was already there
[10:13] <mlankhorst> or do you mean 12.04.1 or below?
[10:14] <elfy> mlankhorst: I think popey refers to the upgrade to 14.04.1 notification from 12.04
[10:16] <popey> i am talking about people running 12.04 on their machines, update manager not offering an upgrade to 14.04*
[10:16] <popey> i have seen multiple reports over the last few days people saying they're not getting offered the upgrade
[10:23] <Riddell> doko: is that the cause of the problem?
[10:24] <doko> Riddell, I don't think so, but explicit libc linking is almost always wrong on linux
[10:43] <infinity> popey: Soon.
[11:11] <doko> Riddell, workaround uploaded
[11:11] <Riddell> oh?
[11:13] <Riddell> I see it, thanks doko
[11:49] <bluesabre> Since 14.04.1 is now out and we're not doing any more respins, can we release this one to trusty now?  https://bugs.launchpad.net/ubuntu/trusty/+source/lightdm-gtk-greeter/+bug/1331871
[13:28] <shadeslayer> cjwatson: any luck with parted?
[14:11] <shadeslayer> cjwatson: live-build needs this patch http://paste.ubuntu.com/7961448/
[14:19] <shadeslayer> oh, apparently happens in 2 placess
[14:21] <shadeslayer> http://paste.ubuntu.com/7961528/ seems more appropriate
[14:26] <Riddell> unless anyone objects I plan to force override the ubuntu-release-upgrader test in pykde4 since I've no idea where it comes from http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pykde4
[14:30] <shadeslayer> Riddell: comes from http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/ubuntu-release-upgrader/utopic/files/head:/debian/tests/
[14:31] <Riddell> yeah, what the heck is nose-test ?
[14:32] <shadeslayer> checks if ubuntu-release-upgrade has a nose
[14:32] <shadeslayer> presumably that's why it fails
[14:32] <Riddell> but how does it smell?
[15:03] <cjwatson> shadeslayer: out of meetings now and resuming debugging.  it's proving annoyingly annoying to extract debug info
[15:03] <shadeslayer> :(
[15:04] <cjwatson> and I had to start by fixing parted builds from git
[15:04]  * shadeslayer fixed live build meanwhile
[15:04] <shadeslayer> silly variables I tell you
[15:04] <cjwatson> I think I have to fix something else for you to have it use live-build from your PPA
[15:05] <cjwatson> oh, but you're using your own imager
[15:05] <cjwatson> meh, whatever
[15:05] <shadeslayer> yep
[15:05] <shadeslayer> worked around for now
[16:04] <Riddell> I've removed kubuntu-active from the crontab file in ubuntu-cdimage, can someone update the crontab accordingly on the cdimage builder?
[16:08] <cjwatson> Riddell: done
[16:08] <cjwatson> \o/
[16:13] <Riddell> thanks cjwatson
[18:20] <stgraber> any SRU team member around for a very quick review that's critical for 12.04.5?
[18:21] <stgraber> (the ltsp kernel enablement patch had to be updated again, I really need to add that to whatever procedure we have for HWE kernels...)
[18:21] <jibel> mlankhorst, could you have a look at bug 1351262 ? it's blocking 12.04.5 alternate
[18:22] <jibel> stgraber, ^ RC bug
[18:22] <stgraber> jibel: ah great, another one...
[18:23] <stgraber> infinity, bdmurray, arges, SpamapS, ScottK: any of you around for a quick review of ltsp in the precise unapproved queue?
[18:24] <arges> stgraber: i'll take a look
[18:24] <stgraber> arges: thanks!
[18:24] <stgraber> arges: the diff should basically be s/saucy/trusty/g
[18:25] <SpamapS> stgraber: It's probably time for me to lay down my AA/SRU hat. Haven't touched a package in Ubuntu in a year. :-/
[18:26] <arges> stgraber: no bug associated with this?
[18:26] <stgraber> arges: nope, just copy/paste from last time and apparently we didn't back then :)
[18:26] <stgraber> arges: the test case is relatively simple "are the ubuntu alternate images busted? yes/no" :)
[18:27] <arges> stgraber: ok accepted...
[18:27] <stgraber> arges: and I'll release the update to -updates as soon as it's published in -proposed so I can kick new images (though as jibel said above, those images are also busted for another reason at the moment...)
[18:27] <stgraber> arges: thanks!
[18:27] <arges> np
[18:31] <stgraber> jibel: I've got a couple other fires to work on first so hopefully mlankhorst will show up soon enough to take care of this, otherwise I'll look into it when I'm done with the rest :(
[18:32] <stgraber> I suspect what we want to figure out is how is this enablement stack different from what we did in saucy and then change whatever's different so things work again
[18:33] <infinity> SpamapS: I can drop you from the teams, if you're not using them anymore.
[18:33] <stgraber> or maybe I can get infinity to look into bug 1351262 for me? :)
[18:35] <infinity> SpamapS: Dropped from SRU and AA.  If you ever find the time and motivation to come back, let me know.
[18:36] <infinity> stgraber: I can look, I make no promises about the result of said looking.
[18:36] <stgraber> infinity: that's already way more than I can do at the moment, so I'll take anything :)
[18:37] <SpamapS> infinity: thanks.
[18:37] <infinity> Hrm.  So, that should be reproducible on a chroot, one would think.
[18:37] <infinity> Shouldn't need a full install run to play with that.
[18:37] <ScottK> Wow.
[18:37] <ScottK> A wild SpamapS appears.
[18:37]  * ScottK waves
[18:37] <SpamapS> Aye, unfortunately it's just to clear up that I'm not here. ;)
[18:41] <ScottK> Yes, unfortunately.
[18:57] <stgraber> ubuntu server is ready for testing
[19:15] <mlankhorst> stgraber: ??
[19:15] <mlankhorst> jibel: not again?
[19:16] <mlankhorst> jibel: last time it was due to glamor-egl pulling in the wrong depends can you see what package it is this time?
[19:18] <mlankhorst> jibel: https://launchpadlibrarian.net/162352830/glamor-egl-lts-saucy_0.5.1-0ubuntu4.2~precise1_0.5.1-0ubuntu4.2~precise2.diff.gz was the fix for saucy
[19:20] <infinity> mlankhorst: Oh good, maybe you have some idea what's going wrong. :P
[19:21] <jibel> mlankhorst, I looked at that bug from 6 months ago but it's different
[19:21] <mlankhorst> infinity: probably if you can get me a verbose apt-get log
[19:21] <mlankhorst> jibel: maybe looks like a similar theme
[19:21] <jibel> infinity, for reference it was bug 1278737
[19:21] <jibel> mlankhorst, this time it is not an upgrade to trusty but the installation of precise
[19:22] <mlankhorst> jibel: yeah but it's not that bug, I've seen it in a saucy seed
[19:22]  * jibel digs deeper into launchpad
[19:23] <mlankhorst> unfortunately I don't know if a bug was opened about it, but the fix at the time (really workaround) was for apt-get to see the libgl1-mesa-glx-lts-trusty first, so it would try to use that instead of libgl1-mesa-glx unrenamed
[19:24] <infinity> mlankhorst: Do you recall how this magic was done?
[19:25] <infinity> cjwatson: Do you have any recollection of... Any of this?
[19:26] <mlankhorst> infinity: no we got lucky that glamor-egl-lts-saucy was the first package to request libgl1-mesa-glx, so we could add the workaround to it
[19:30] <mlankhorst> infinity: but if you can get me a verbose apt-get debug log I should be able to see if we could fix it this time
[19:35] <infinity> mlankhorst: Without downloading a CD and trying myself, the verbosity in the d-i log there is the same for you as it is for me.
[19:35] <infinity> mlankhorst: And you might have more luck debugging on the fly than I would, if you grab an ISO and play.
[19:38] <mlankhorst> infinity: oh last time it happened when preparing one of the iso's
[19:39] <mlankhorst> infinity: I sit ok if I look at it tomorrow morning?
[19:39] <mlankhorst> near bed time for me
[19:40] <mlankhorst> I sit -> is it
[20:06] <stgraber> respinning ubuntu alternate for ltsp now
[20:07] <stgraber> everything else is either already built and ready to test or still building and will show up in the next few minutes
[20:11] <jibel> what does this version means in a conflict: Conflicts: libgl1-mesa-glx (>= 0~) ?
[20:11] <mlankhorst> jibel: non-virtual package
[20:11] <jibel> ok
[20:23] <stgraber> infinity: bug 1353086
[20:24] <stgraber> infinity: looking around, shouldn't that d-i be moved to -updates?
[20:25] <infinity> stgraber: Oh, was it not yet?
[20:26] <infinity> stgraber: Yes.  Yes it should.
[20:26] <infinity> stgraber: I can do that now, if you haven't already,.
[20:26] <stgraber> infinity: go ahead
[20:26] <infinity> stgraber: DOne.
[20:26] <stgraber> I'll then monitor and respin alternates and server once it's published
[20:27] <infinity> stgraber: So, alternates and server will need a retry after that publishes.
[20:27] <infinity> stgraber: Jinx.
[20:27] <infinity> stgraber: Probably also worth double-checking the current state of proposed and making sure you don't care about anything else. :P
[20:27] <infinity> Err, like livecd-rootfs.
[20:27] <infinity> So... Everything needs to rebuild.
[20:28] <jibel> meh it failed on 20140805.2 :(
[20:28] <infinity> And base-files...
[20:28] <infinity> And grub...
[20:28] <infinity> Whee.
[20:28]  * infinity releases a bunch of stuff.
[20:28] <stgraber> oh, fun
[20:29] <stgraber> that's probably why I opened that pending-sru tab for this morning, then got distracted...
[20:29] <infinity> stgraber: parted might be interesting too, but I'll let you dig into that and decide.
[20:31] <stgraber> infinity: yeah, parted sounds like a win and it's basically the last useful moment to accept it for precise (well, except people using netboot images)
[20:33] <infinity> stgraber: No verification, on it, sadly.
[20:33] <stgraber> yeah, I'll verify it real quick
[20:34] <infinity> stgraber: Thaty 96-day-old ubiquity might want love as well.
[20:34] <infinity> Though, it seems the fix wasn't really a fix, so meh.
[20:35] <stgraber> infinity: yeah, I looked at the bug report and then decided to skip it
[20:35] <infinity> (not broken either, mind you)
[20:39] <elfy> infinity: hi - quick question, we're (Xubuntu) down apparently for 12.04.5 but we don't want to be - does removing from the testing tracker stop .5 building or do we need to do something else?
[20:40] <elfy> or is it too late in fact
[20:41] <infinity> elfy: Talk to stgraber.
[20:41] <elfy> stgraber: ^^
[20:41] <infinity> elfy: If you weren't using HWE stacks (were you?), there's no real reason for you to do the point release.
[20:41] <infinity> elfy: If you were, though, you don't really want to leave your users with the "current" precise ISO being unsupported.
[20:41] <elfy> apparently we weren't
[20:42] <stgraber> elfy: hi
[20:42] <elfy> infinity: yea understood
[20:42] <infinity> Yeah, you weren't.  Just double-checked.
[20:42] <stgraber> elfy: ok, so I'll remove any build you have and that'll be it. Thanks for letting me know.
[20:42] <infinity> So, no particular reason you would *have* to do the release.  If you don't want to, easier for everyone involved.
[20:43] <elfy> awesome - thanks chaps :)
[20:43] <shadeslayer> cjwatson: is the cronjob working for Kubuntu Plasma 5? I don't see ISO's for today
[20:43] <stgraber> Just marked the world as disabled as we're expecting a mass respin in about 30min
[20:43] <infinity> Looks like it was just ubuntu, edubuntu, and mythbuntu doing HWE stacks in precise.  We really need to fix that in trusty.
[21:13] <cjwatson> shadeslayer: I don't think it's time yet
[21:17] <skellat> stgraber: queuebot just mentioned that it is spinning up a .5 for Xubuntu.  elfy still wanted that nuked.
[21:17]  * elfy really should take that off ignore now and again :(
[21:17] <elfy> thanks skellat
[21:22] <stgraber> skellat: if you look at the tracker you'll noticed they're not there
[21:23] <elfy> thanks stgraber :)
[21:23] <skellat> stgraber: That works.
[21:26] <bdmurray> infinity: is it time to change meta-release-lts yet?
[21:32] <infinity> bdmurray: If nothing's come up since that update-manager upload went in, we're probably good.
[21:33] <stgraber> starting the mass respin now (parted just appeared on ftpmaster so we should now have everything)
[21:35] <bdmurray> infinity: I'll have a look around launchpad and see if I find anything
[21:43] <infinity> bdmurray: Alright.  I'm not personally aware of anything, so if you don't find any more waving red flags, go ahead and make the switch.
[21:44]  * infinity is going to have a siesta to make up for the lack of sleep last night.
[21:45] <tgm4883> infinity: not sure who to tell, but Mythbuntu isn't doing any more 12.04 releases
[21:49] <stgraber> tgm4883: ok, so no 12.04.5 for you then?
[21:49] <tgm4883> stgraber: correct
[21:50] <stgraber> ok, there's already a respin in progress, I'll let it finish and just remove you from the tracker afterwards
[21:50] <tgm4883> sounds good, thanks
[22:22] <xnox> stgraber: infinity: cjwatson: do i need to compile new wubi for 12.04.5?
[22:25] <stgraber> xnox: if you had to do that for 12.04.4, then I guess so, yes
[22:27] <xnox> stgraber: is it just me, or some kind of ubuntu/precise images ftbfs? I'm getting ftbfs emails.
[22:28] <xnox> stgraber: we also need to build the precise wubi livefs image, and i don't see it on the iso tracker nor a recent build for it.
[22:28] <stgraber> xnox: I did trigger a wubi build earlier
[22:29] <stgraber> and I have another one currently building
[22:29] <stgraber> http://cdimage.ubuntu.com/precise/wubi/
[22:30] <xnox> oh, right. i was looking at the wrong wubi ( http://cdimage.ubuntu.com/wubi/ )
[22:30] <xnox> silly me, that one stopped in raring or whenever. should be cleaned up i think.