User1: Have fun :)
User2: bryceh, are you still around?
User2: RAOF, or are you around?
User1: I am, yes.
User1: User2 What can I do you for?
User2: RAOF, would you be able to upload a new utouch-qml package for me?
User1: Sure.
User2: I need it in before feature freeze, and it's not in the utouch package set yet...
User2: bzr branch lp:utouch-qml/ubuntu
User2: uscan
User2: bzr bd -S
User2: sign and upload
User2: I suppose the uscan should be uscan --download-current-version
User1: It should indeed :)
User2: RAOF, you'll need bzr-builddeb installed
User2: alternatively, I can upload a prebuild package somewhere for you to sign
User2: prebuilt*
User1: I see that no-one's in a position to review your XI 2.1 protocol series :/
User2: RAOF, upstream on the mailing list?
User1: Yeah.
User2: whot will be
User2: he's already emailed me to let me know he will review them soon
User2: just got a bit of work to get out of the way
User2: we're in pretty good communication
User1: Huzzah!
User2: I don't know if anyone else is going to review though
User1: It only really needs whot's review, right?
User1: I guess Daniel's would be valuable, too.
User1: Man, X input doesn't have a very high bus factor :/
User2: yeah, daniels would be nice but I think whot is the real gatekeeper
User1: You seem to have a bunch of 'libutouch-qml-doc: non-standard-file-perm usr/share/doc/utouch-qml/html/bc_s.png 0664 != 0644' lintian warnings in that package.
User2: hmmm, I've not seen those warnings before
User2: it's likely due to doxygen
User1: Yeah, likely.
User2: well, it's definitely due to doxygen
User2: I'll try and rebuild from scratch to see if I get those warnings
User1: Is there any easy way to test this?
User2: RAOF, do you have a multitouch device?
User1: BAH!  bluetooth is broken, so my magic touchpad won't work.
User2: synaptics perhaps?
User1: Got a synaptics here; how can I tell if it's sufficeiently multitouch?
User2: you can install qt4-qmlviewer
User2: then run qmlviewer examples/eventprinter/eventprinter.qml
User1: Ah.  When I say "synaptics", what I actually mean is "Alps GlidePoint"
User2: heh
User2: nope, won't work
User2: (yet)
User2: I've found that linux 3.0.0-7 works, but bluetooth doesn't work before that and hid-magicmouse (for the magic trackpad) doesn't work in 3.0.0-8
User2: something else I need to track down...
User2: RAOF, I only get the one lintian warning about the embedded javascript library
User2: which is also a doxygen issue
User2: doxygen likes to ship a version of jquery that is different than the upstream version
User2: so you can't do the "correct" thing and symlink to the upstream version
User1: Hm.  This is possibly a pkgbinarymangler bug.  All those pngs have been touched by optipng.
User2: what's optipng?
User1: The thing we use to squeeze ever tinier slivers of CD space out of packages.
User1: It's a png optimiser that pkgbinarymangler runs.
User2: I'm guessing it's only invoked when it's installed
User2: cause I don't have it installed
User1: Indeed.
User1: pkgbinarymangler hooks into dpkg somewhere.
User2: I'll install it and see if that makes it occur
User2: then we'll know for sure
User2: nope, that still didn't do it
User2: oh, I don't have pkgbinarymangler installed
User2: well, the pngs were modified, but still no lintian warnings
User2: so I don't know why you're seeing them
User1: Anyway, looks sufficiently good; uploaded.
User1: Hm.  Maybe my sbuild setup is slightly strange.
User2: cool, thanks again!
User2: are you all dist-upgraded?
User1: Yeah.
User1: I lost my libgl1-mesa-glx:i386 :(
User2: ummm, ok?
User2: was it near and dear to your heart?
User1: Terribly!
User1: Or, rather, it was near and dear to my wine.
User1: God knows when ia32-libs was last updated.
User1: It'll work once libc is fixed again.
User2: I thought ia32-libs was going to go away
User1: Yeah, but it doesn't look like it will for oneiric.
User1: But you *can* install the i386 version of mesa, which does basically everything you want from multiarch, anyway :)
User2: cool
User1: Oh, whoops.  You can as long as you've got a multiarch'd libpciaccess, such as I've got here :)
User3: RAOF, is your system still using 20gb of ram per process?
User1: User3 Still?  To what do you refer?
User3: you said all your ram is used up because x clients grab huge amounts of it
User3: but i guess the problem has been resolved
User1: That may have been compiz going mad?
User4: tjaalton, hi, i hope you dont forget about libx11
User5: User4 nope
User5: was FF today?
User5: so it seems
User5: I'll do that and some other merges then
User4: tjaalton, yes, FF is today ;), thanks
User1: User5 While we're in the upload-before-FF games, could you please test the -ati in alioth?  I'd test it locally, but my ati machine has spent the past 6 hours updating and still isn't finished.
User5: User1 oops, same problem here too. my test build is still on natty, though it would only take ~1h to update i guess
User5: I only have an old firegl though
User1: Ok.  This HD 5450 should finish updating *sometime* soon, I guess :)
User5: is hd6xxx supported yet?
User1: Should be.
User1: Although I think that might depend on the exact value of xxx.
User5: good, I could buy a hd6450 based card, passively cooled and only ~50EUR
User1: User5 Gah.  It's EOD here.  Could you please test -ati and upload if it's sane?
User1: I have no idea when my test box will be available to actually test on :/
User5: User1 yeah, can do
User5: hmm, not enough space on disk, best to just reinstall the sucker then. faster too
User6: Sarvatt, User1 are there any plans to put the new X in xorg-edgers?
User6: 1.11
User5: either that or a separate ppa, or both
User5: since the idea was to stage the stack in a ppa and then push it to P when it opens
User5: oh nice, alpha3 installer crashed
User5: User6 can you test the -ati from git? could be that i'm unable to install oneiric to test it myself
User6: User5 I can probably do that later today
User6: User5 you're talking about our git repository, right?
User5: User6 yes, today is FF so it should be uploaded today as well
User6: User5 what? Wasn't it on August 17?
User5: nope, 11th
User5: https://wiki.ubuntu.com/OneiricReleaseSchedule
User6: you're right and I'm already late with some uploads...
User5: synced libxfont 1.4.4-1 to oneiric
User7: tjaalton, User1 ati's version shouldn't be 6.14.99 though
User7: 6.14.3~
User5: right, it could end up being 6.14.4?
User7: http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=2fca40ea65d9f2a6f8451c324bb4b82786f34f76 they do that every release
User5: "bump"
User5: User7 do you have ati gear to test it on? I've yet to hit the store so it could take hours still for me to get a current card
User7: nothing on oneiric, no. any idea when the cutoff is?
User5: today is FF
User7: yeah when today I mean
User5: ah, dunno
User5: synced -siliconmotion
User5: merged xterm
User7: with my luck oneiric upgrades are broken with everyone shoving crap in
 * Sarvatt checks
User7: i'll start an upgrade on my hd5770 machine to test it out, looks like only ubuntuone and multiarch are busted
User7: User6 i wasnt planning on putting 1.11 in edgers until october probably, is ati asking for it or something?
User5: crap, forgot that pbuilder works now, should probably try the builds first
User5: I'm removing the silly locales from libx11
User5: hum, can't see any reason not to grab xkeyboard-config 2.3-1 from experimental
User8: do you know who's taking care of CVE-2011-2895 for ubuntu?
User9: User8 ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2895)
User5: User8 is it the libxfont one?
User8: yes
User5: I synced it to oneiric, other versions are not done yet
User8: i was wondering if there was some sort of test case or something
User7: kees: any idea about the above?
User5: hmm dunno. mdeslaur, do you know ^?
User5: :)
User5: echo
User7: ah whoops, sorry if I pinged the wrong person :)
User8: that code hasn't changed in forever anyway, so it doesn't look like a risky cherry-pick
User10: let me look, one sec
User10: User8 I don't see any test cases for the security fix
User8: thanks for checking
User5: meh, xkeyboard-config failed to build, have to check it later.. gone for ~3h ->
User7: tjaalton, User1 an hour stress testing the ati checkout in git with no problems, ship it :)
User7: of course theres a new bugfix today
User6: User5 I don't think I'll be able to test -ati today
User6: ah, good, Robert tested it
User5: User7 cool, and I got a new HD6450 ready for testing :)
User5: dh_autoreconf: (intltoolize -c -f && autoreconf -vfi) (intltoolize -c -f && autoreconf -vfi) failed to to execute: No such file or directory
User5: what the hell
User5: not even the debian branch builds
User5: of xkeyboard-config
User7: its the override_dh_autoreconf section in the rules screwing it up
User5: hum yes, obviously, but why
User5: removing '--' made it build, but dunno if it does what it's supposed to do
User5: apparently it does
User5: User6 what are those -updates blobs for?
User7: User4 so can I just pull in oneiric wayland packages to natty directly in edgers?
User7: mesa needs it
User5: xkeyboard-config uploaded.. now how do I create that ati tarball with pristine-tar..
User4: Sarvatt, already have
User5: ha, created it
User7: User4 ah we need ubuntu3
User7: User4 and it has to be ubuntu3whatever~natty
User4: Sarvatt, 3 doesnt have any relevant changes, but i can upload it
User7: or else the build dep wont get satisfied by ubuntu3~edgers~natty being lower than ubuntu3
User4: building against ubuntu2 is fine
User4: ah
User4: i see what you mean
User11: hmm, looks like something is screwy with the intel apport hook transition - see bug #824023
User7: i can add a hook to fix it in mesa but seems easier to just reupload the ubuntu3 wayland and be done with it
User9: Launchpad bug 824023 in xdiagnose (Ubuntu) "package xdiagnose (not installed) failed to install/upgrade: trying to overwrite '/usr/share/apport/apport-gpu-error-intel.py', which is also in package xserver-xorg-video-intel 2:2.14.0-4ubuntu7.2 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/824023
User11: tjaalton, do we need to add a conflicts or something in xdiagnose to the -intel driver to ensure the upgrades occur in proper order?
User4: Sarvatt, uploading 3 wont help with the next mesa build it will the same problem
User7: not if you do ubuntu3edgers~natty
User4: mhh, right
User4: on sec
User4: one sec
User7: they changed the PPA docs to recommend using XubuntuYppa1 instead of XubuntuY~ppa1 and it makes lots of sense so you dont have to change build deps on everything
User5: User11 seems like it
User4: Sarvatt, this of course will break the upgrade path
User7: which upgrade path? the one already broken in edgers by everything being newer than the next release? :P
User5: User11 Replaces: xserver-xorg-video-intel (<= 2:2.14.0-4ubuntu7.1),
User5: User11 there's your problem :)
User11: tjaalton, ah, what should that be?  Conflicts?
User11: oh, 7.2 aha
User5: User11 use (< $version_thats_not_going_to_get_in_natty) :)
User11: yep
User5: like (< 2:2.15)
User4: Sarvatt, right, but still in this case it is a copy from oneiric which should be replaced by the original one, anyway i will upload it
User4: ;)
User5: btw, oneiric is totally broken on the HD6450 with -ati
User11: 2:2.14.0-4ubuntu8 should be sufficient, no?
User5: lets see if the snapshot changes anything, though I think it's kernel at fault
User5: User11 yeah
User7: User5 pci id?
User7: which caicos is it?
User5: User7 well, it loads but gfx totally corrupted. and can't get the id since I can't log in :P (and no sshd yet)
User7: nomodeset time
User5: ah, right
User5: with nomodeset it just hung with a blinking cursor
User5: wait, it was just the keyboard that stopped working during boot, until I reconnected it
User7: User4 debhelper 8.1.2ubuntu2 is enough for wayland on natty, we had the multiarch stuff backported to it before 8.1.3 (sorry if ya already were fixing it)
User5: 1002:6779
User7: hrm "support" for that was there, anything in your dmesg from the old boots in /var/log/kern.log hopefully?
User5: oh yes
User4: Sarvatt, sorry, uploaded again
User7: User4 thank you thank you :)
User5: http://pastebin.com/7eJaQhiQ
User7: User4 btw i'm hoping to have xserver 1.11 in there way sooner than expected (like in the next week or so), rememebered ya asking about it
User4: oh, nice
User7: User5 disable the intel IGP in the bios
User5: User7 no such thing
User7: its the SDP right? sure there is
User5: this is an old Asus P5K board
User7: oh
User5: rock solid :)
User5: i'll build 3.1rc1 tomorrow to try
User5: ati uploaded
User5: looks like apart from the pending xserver merge we got every new upstream version uploaded in time :P
User7: User5 do you have cryptsetup installed? is radeon in your initrd?
User5: User7 this is a fresh natty install, upgraded to oneiric, without cryptocrap
 * tjaalton grabs a sierra nevada
User7: User5 you can do a sudo mv /lib/plymouth/renderers/drm.so{,.bak} to get the desktop up for now, i dont know how to disable a single plymouth backend at runtime :P
User5: heh, thats ok, I don't need the box
User5: might just build the new kernel first to see if it helps
User5: ok, EOD for me
User7: way past that eh? :P
User5: yeah, indeed
User7: User1 err, they're talking about reverting the vblank patch and reintroducing the compiz hangs on all intels again on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814325
User9: Launchpad bug 814325 in linux (Ubuntu Natty) (and 1 other project) "fuzzy and corrupted display with update in natty-proposed (affects: 1) (heat: 18)" [High,Triaged]
User6: User5 to keep drivers updated during the stable release cycle
 * tseliot -> offline
User5: User7 oops, right. I thought it was the one which fixed dualscreen setup.. still, would be too bad to revert that
User7: User11 do you have natty on that arrandale?
User11: Sarvatt, no, oneiric
User11: (and wayland *grin*)
User7: if you have any spare time, could ya try installing the 2.6.38-11 kernel from natty-proposed and seeing if you can reproduce this with the script on comment 12? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814325
User9: Launchpad bug 814325 in linux (Ubuntu Natty) (and 1 other project) "fuzzy and corrupted display with update in natty-proposed (affects: 1) (heat: 24)" [High,Triaged]
User1: User7 I suspect that maybe http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/5423 will be the fix for that.
User1: Well, the two patches in that thread.
User7: User1 sorry about that ping earlier, I misread and thought they were reverting the compiz fix and in the process of my net dying 3 times forgot to mention that
User1: That's ok.  You're welcome to ping me while I'm safely asleep :)
ubuntu-x
Ubuntu IRC