[00:27] <thumper> gah...
[00:27] <thumper> I hate it when apport makes a public bug a dupe of a private one
[00:27] <thumper> especially a private one I can't see
[00:38] <jbicha> thumper: as a workaround you can ask in #ubuntu-bugs for a specific bug to be publicized
[00:38] <thumper> jbicha: thanks
[00:40] <micahg> jbicha: I thought the SONAME bump was being reverted for cogl
[00:44] <micahg> jbicha: per the bug cogl 1.9.10 was going to revert the bump, so why upload now?
[00:45] <jbicha> micahg: the soname for 1.9.8 was cogl9, after that upload, the clutter devs bumped it again to cogl10 & then I complained so they reverted that change
[00:45] <jbicha> cogl5 is currently in the archives so they've been making lots of changes this cycle
[00:46] <micahg> jbicha: ah, ok
[00:46] <bjsnider> it was already up to 10?
[00:46] <bjsnider> wow
[00:46] <jbicha> well it's better than gjs which doesn't bother changing their soname
[00:47] <bjsnider> they must bump the soname every time they add something to the changelog
[00:49] <jbicha> every tarball release where the API was changed
[00:50] <bjsnider> they change the api alot, must mean they aren't satisfied with it
[00:51]  * micahg is glad someone else is dealing with gjs/gnome-shell at this point :)
[00:57] <Sarvatt> bjsnider: welcome to intel driver pain in your desktop packages, git master or bust :)
[01:01] <lifeless> is network-manager not meant to remember passwords now ?
[01:03] <Sarvatt> lifeless: certainly does here
[01:03] <lifeless> hmm
[01:03] <lifeless> well, it isn't here :(
[01:03] <Sarvatt> i just switched to another ap and rebooted an hour ago
[01:04] <lifeless> and when I select edit on the network connectin in 'edt connections' it says 'Error initializing editor\nNo agents were available for this request.'
[01:05] <micahg> jbicha: I think you just need libgl1-mesa-dev on arm* as well
[01:05] <micahg> jbicha: but you should verify that with janimo
[01:06]  * micahg can actually try it in a chroot
[01:06] <Sarvatt> something wrong with the last mesa upload? we didnt touch libgl1-mesa-dev, just egl
[01:09] <Ursinha> thumper, which bug is it?
[01:10] <Sarvatt> micahg: yeah GL_PACK_INVERT_MESA is in gl
[01:11] <Sarvatt> micahg: actually mesa-common-dev
[01:12] <micahg> Sarvatt: right, but libgl1-mesa-dev pulls that in on all the other archs
[01:12]  * micahg guesses technically it would just be better to add mesa-common-dev explicitly
[01:12] <Sarvatt> but you dont need libGL.so, mesa-common-dev might be more correct (but could be wrong)
[01:31] <thumper> hi Ursinha, sorry didn't notice
[01:31] <thumper> I should file a bug about quassel not keeping urgency
[01:31] <thumper> although I do wonder if it is Qt or just Quassel
[01:36] <thumper> Ursinha: sorry, can't find the bug now :(
[01:49] <broder> cyphermox: do you have a ppa for oneiric with backported fixes for bug #869635 yet? i think i'm getting hit at least by the modemmanager bug, so i may set one up if not
[01:49] <ubot2`> Launchpad bug 869635 in wpasupplicant "long delay at shutdown/reboot - network-manager doesn't close correctly" [Undecided,Confirmed] https://launchpad.net/bugs/869635
[01:49] <jbicha> my computer can't do hw virtualization so I don't know if I can run an arm chroot
[01:49] <TheMuso> jbicha: HW virt has nothing to do with emulating arm.
[01:49] <TheMuso> hw virt only helps with running x86 VMs.
[01:50] <jbicha> so it doesn't need kvm?
[01:50] <broder> jbicha: i think you just need to install qemu-user-static
[02:21] <jbicha> broder: I installed that and ran sudo sbuild-createchroot --keyring=/etc/apt/trusted.gpg --arch=armhf precise /build/chroot/precise-armhf-sbuild http://ports.ubuntu.com/ubuntu-ports/
[02:21] <jbicha> but I get Failure trying to run: chroot /build/chroot/precise-armhf-sbuild mount -t proc proc /proc
[02:27] <jbicha> chroot: failed to run command `mount': No such file or directory
[02:48] <broder> jbicha: huh. i've never tried with sbuild-createchroot. i always use mk-sbuild
[02:58] <jbicha> I was just using http://wiki.debian.org/sbuild
[02:59] <broder> jbicha: i'm running it now to make sure it still works, but i think `mk-sbuild --arch=armhf precise` will work with no other options
[03:00] <broder> once you have qemu-user-static installed so that you can run armhf binaries
[03:01] <jbicha> that command is a bit shorter, trying that now
[03:02] <broder> mk-sbuild also has a --eatmydata option if you're into that
[03:56] <broder> does the HUD any time i tap alt quickly enough, regardless of other keypresses? it seems to if i press alt-left arrow or alt-right arrow quickly enough (for back/forward in chrome), which is really irritating
[04:00] <broder> ah, yes. bug #934610. /me subscribes
[04:00] <ubot2`> Launchpad bug 934610 in unity "HUD - Typing a key combination (e.g. Alt-x) fast enough triggers the HUD" [High,Confirmed] https://launchpad.net/bugs/934610
[04:00] <DBO> broder, unrelated...
[04:00] <DBO> can I get glxinfo from you
[04:01] <DBO> I need to collect enough samples to get a feel for driver support for a new unity feature...
[04:01] <broder> sure: http://paste.ubuntu.com/882762/
[04:03] <broder> DBO: that's my desktop. i can get you my laptop, too, if i ever manage to unbreak apt
[04:04] <DBO> broder, the laptop is of higher interest to me
[04:04] <DBO> though I find it odd your nvidia card is not getting GL 4.0 support
[04:04] <DBO> still we only care about 3.0
[04:04] <broder> it's a pretty crappy card
[04:05] <DBO> 9500 GT is plenty fast for what I need
[04:05] <DBO> in fact its downright overkill
[04:05] <broder> i just don't know if i should expect the card itself to have GL 4.0, but i don't really know what i'm talking about when it comes to this sort of thing
[04:06] <DBO> broder, its mostly a driver support issue
[04:06] <broder> huh, ok
[04:06] <DBO> still, 32 stream units 8.8 billion texels/sec fill rate
[04:06] <DBO> you should be able to kill the effects
[04:12] <broder> DBO: do you know if checkbox or ubuntu friendly or something is getting glxinfo data? that might be a better source of broad data than asking me :)
[04:12] <DBO> no idea really
[04:13] <DBO> even if it were I dont know if I would have access
[04:13] <broder> you could talk to ara
[04:13] <DBO> yeah I was hoping to luck upon someone with a G45 chip tonight
[04:13] <DBO> that would seal me requirements quite nicely
[04:14] <broder> that's...intel g45?
[04:14] <DBO> yeah
[04:15] <DBO> sometimes called the x4500
[04:15] <DBO> or GMA4500
[04:15] <DBO> sometimes HD is tacked on the end
[04:15] <DBO> all the same thing for what I care about
[04:15] <broder> how does this look: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
[04:16] <broder> err, hmm, that laptop has a...G45 audio codec, i think?
[04:16]  * micahg has that same chiupset
[04:17] <DBO> thats perfect
[04:17] <DBO> give me that
[04:17] <DBO> glxinfo
[04:18] <broder> micahg: can you get it? i don't have precise installed on that machine at present
[04:19]  * micahg installs mesa-utils
[04:22] <micahg> DBO: http://paste.ubuntu.com/882776/
[04:22] <DBO> oh thats *perfect*
[04:22] <DBO> I can just make the cutoff opengl 3.0 support
[04:22] <DBO> no custom rules
[04:23] <DBO> I love it
[04:23] <DBO> thank you micahg
[04:23] <micahg> DBO: you're welcome
[04:24] <jasoncwarner_> hey RAOF saw your name against the lightdm corruption after boot...how is that going?
[04:24] <jasoncwarner_> robert_ancell: ^^
[04:26] <DBO> jasoncwarner_, still getting that annoying white box thingie?
[04:26] <jasoncwarner_> DBO..yeah
[04:26] <DBO> awesome...
[04:27] <jasoncwarner_> though the above is a bit different...but yes, getting the white box thingy for sure
[04:27] <ajmitch> DBO: fwiw, I saw that today
[04:27] <jasoncwarner_> DBO: any idea yet on that one? makes me soooooo angry ;)
[04:27] <DBO> no
[04:27] <ajmitch> assuming it's the same white box, thumper thought it probably was :)
[04:27] <DBO> jasoncwarner_, does it block inputs?
[04:28] <jasoncwarner_> DBO: block input? no, I can do my normal computing stuff, just have this stupid white box over everything including teh dash and launcher etc
[04:28] <DBO> oh oh oh oh I know what
[04:28] <DBO> open uhm
[04:29] <DBO> the on screen keyboard
[04:29] <DBO> that should render above the dash
[04:29] <DBO> does that also render above the white box?
[04:30] <jasoncwarner_> i don't have the whtie box at the moment, but as soon as I do, I'll test that
[04:30] <jasoncwarner_> (shoudln't be long now..rebooted about an hour ago ;) )
[04:32] <DBO> wish I thought of that a while ago
[04:32] <DBO> that will immediately point to the problem area
[04:33] <RAOF> jasoncwarner_: I've been firefighting other things.  I'll kick into that now.
[04:33] <DBO> RAOF, isn't that as simple as clearing the framebuffer?
[04:34] <RAOF> DBO: No; not if you want a seamless transition.
[04:35] <DBO> RAOF, oh... ok :P
[04:35] <RAOF> DBO: There isn't a modeset between lightdm and the regular session; it's not X not having anything to draw after a modeset, it's what unity-greeter has drawn to the root window going mad after unity-greeter quits.
[04:36] <RAOF> Oh, huh.  I thought we couldn't advertise GL 3.0 without S3TC compression support.  Apparently we do!
[04:37] <DBO> RAOF, it's GL
[04:37] <DBO> lying is never out of the question
[04:38] <RAOF> Heh.
[04:38]  * RAOF is not at all surprised that the nvidia 9600 doesn't support GL 4.0; it's not a DX11 part.
[04:40] <RAOF> DBO: By the way, the Intel sandybridge chips *also* support GL 3.0 on Precise.  Just on the off-chance you're hoping 3.0 support implies a certain level of performance :)
[04:41] <DBO> RAOF, I am hoping that 3.0 implies newer nvidia/amd or sandybridge
[04:41] <DBO> but not any older intel
[04:41] <DBO> I believe that is correct
[04:42] <RAOF> I think that's correct, too.
[04:42] <RAOF> What effect are you trying to do?
[04:47] <Sarvatt> hopefully nothing that requires GLX_ARB_create_context
[04:48] <DBO> Sarvatt, actually we are simply using the 3.0 as an evil performance cutoff
[04:49] <DBO> since apparently running a small benchmark on a users machine is evil...
[04:49] <Sarvatt> DBO: every time you start a unity session or something? that would be evil :P
[04:50] <DBO> pfft it would take like 20ms
[04:50] <DBO> render a couple frames into an FBO
[04:50] <DBO> time it
[04:50] <DBO> done
[04:50] <RAOF> That seems like a reasonable solution.
[04:51] <DBO> yeah considered evil...
[04:51] <RAOF> Although perhaps not *during* boot.
[04:51] <DBO> nah was going to do it on the first alt-tab
[04:51]  * RAOF was thinking storing it as configuration, and doing it on first boot.
[04:51] <DBO> that would not account for hardware upgrades
[04:51] <DBO> driver improvements
[04:51] <RAOF> Match up to GL renderer string, and you can cache it.
[04:52] <DBO> or us just improving the performance of the effect
[04:52] <DBO> lord knows we are doing an expensive effect that maybe some smart mathy person can make cheaper
[04:52] <Sarvatt> if gl version string isnt' the same, retest?
[04:52] <RAOF> Would require a package upgrade, which can trivially trigger a re-benchmark.
[04:54] <RAOF> Can we argue with whoever said benchmarking to determine what level of effects should be attempted? :)
[04:54] <DBO> yeah...
[04:54] <DBO> still...
[04:54] <DBO> it was implied to be evil!
[04:54] <DBO> brb
[04:54] <RAOF> Doing it in a hot-path isn't going to be a particularly awesome move, but you don't *have* to do it in a hot path :)
[04:55] <DBO> actually
[04:55] <DBO> bed now
[04:55] <DBO> cheers
[04:56] <RAOF> G'night!
[04:56] <RAOF> Dear universe: why isn't there an IDE that uses autofoo as its project description.
[04:58] <Sarvatt> would be funny if querying the cached gl version string took more time than doing the benchmark though, could totally see that :)
[04:59] <jalcine> RAOF: lol good question.
[05:01] <RAOF> Sarvatt: Eh, they're already querying the GL vendor string as a part of startup; that info is free.
[05:47] <BigWhale> Good Morning.
[05:48] <ritz> pretty funny, In fedora 18 the scrollbar reminds me more of ubuntu than anything else
[06:04] <pitti> Good morning
[06:08] <Ursinha> morning
[06:26] <didrocks> good morning
[06:36] <pitti> didrocks: bonjour
[06:36] <pitti> didrocks: ca va?
[06:36] <didrocks> guten morgen pitti
[06:37] <didrocks> I'm fine, thanks! And you?
[06:38] <pitti> quite well indeed!
[06:38] <pitti> didrocks: I don't dare asking you my question..
[06:40] <didrocks> pitti: hum, what question? :)
[06:40] <pitti> didrocks: what do I need to reset in unity to get your alt fix?
[06:41] <didrocks> pitti: euh, nothing normally, just logging out/in after upgrading should be fine
[06:41] <didrocks> not working for you?
[06:41] <didrocks> (working well here and confirmed on the french forum)
[06:41] <pitti> it still neither works in terminal nor firefox
[06:41] <didrocks> hum…
[06:41] <pitti> I got unity 5.6.0-0ubuntu3 yesterday evening, and have booted this morning
[06:41] <didrocks> I wonder if you don't have a keybinding blocking
[06:42] <didrocks> (a compiz one)
[06:42] <didrocks> unity --reset, but that will reset all your compiz keybindings
[06:42] <pitti> probably ok, I can restore them
[06:46] <didrocks> keep me posted
[07:19] <pitti> doctor appointment, bbl
[07:20] <didrocks> pitti: FYI, on alt + keys, seems that daniel and you still have it not working, so we are looking into it
[07:26] <broder> didrocks: this may be related to pitti's issue, but alt-f10 doesn't work for me. expected or part of the same bug?
[07:27] <broder> (nothing happens, and some percentage of the time compiz seems to lock up entirely)
[07:47] <didrocks> broder: you mean, it doesn't show the appmenu for you?
[07:51] <pitti> broder: I had that once yesterday, but a second try didn't reproduce
[08:52] <seb128> hey
[08:54] <pitti> bonjour seb128
[08:56] <seb128> hey pitti, wie gehts?
[08:56] <pitti> gut, danke! und dir? (I'm in my 1-on-1)
[08:57] <seb128> pitti, gut, danke! (heh, finish, my 1:1 is supposed to be in 3 minutes :p)
[09:06] <pitti> seb128: he's all your's; sorry for running over :)
[09:06] <seb128> pitti, no worry, I've time it's my start of day ;-)
[09:06] <seb128> it's for jasoncwarner_ that it's starting being late :p
[09:06] <pitti> nice, dpkg -P python-gobject now is only held back by four packages
[09:07] <pitti> I filed a debian bug for python-zeitgeist (didn't want to introduce a delta for this)
[09:07] <pitti> update-manager and system-config-printer-gnome need porting to GI
[09:07] <pitti> (or s-c-p dropped, rather)
[09:07] <pitti> and python-gst0.10 is only due to sessioninstaller and rhythmbox
[09:07] <pitti> at some point we want to make these work with GI gst
[09:08] <BigWhale> Greetings.
[09:09] <pitti> oh, the rb dependency is obsolete
[09:09] <rickspencer3> hey didrocks
[09:09] <mvo> pitti: is it just python-gobject -> python-gi?
[09:09] <didrocks> hey hey rickspencer3
[09:10] <rickspencer3> so, when I rebooted, the super key didn;t work
[09:10] <didrocks> then opened an app?
[09:10] <rickspencer3> I opened the dash manually, then it worked
[09:10] <didrocks> and super key works?
[09:10] <seb128> didrocks, do you want me to look for a rope for you?
[09:10] <rickspencer3> didrocks, sort of
[09:10] <pitti> mvo: no, update-manager-core actually has a few "gobject" imports
[09:10] <pitti> mvo: once that's ported, we can switch
[09:10] <rickspencer3> didrocks, when xchat was busy, it wouldn't work
[09:10] <didrocks> seb128: sometimes, I wish people would directly annoy dx, yeah :)
[09:11] <didrocks> rickspencer3: interesting, one sec
[09:11] <rickspencer3> seb128, in my defense, I asked didrocks already if he wanted me to check it out ;)
[09:11] <rickspencer3> so, it wasn't a randome ping
[09:11] <didrocks> rickspencer3: can you please add and +1 on bug #953089?
[09:11] <ubot2`> Launchpad bug 953089 in unity-distro-priority "Unity 5.6: Super key doesn't start the dash" [Medium,Fix committed] https://launchpad.net/bugs/953089
[09:11] <rickspencer3> didrocks, yeah
[09:11] <didrocks> rickspencer3: then, I'll ping duflu about it
[09:11] <pitti> didrocks: I think you need an IRC autoresponder /(unity|alt|super).*bug/ -> "please ask in #unity"
[09:12] <rickspencer3> anything else I can do to help, let me know
[09:12] <didrocks> pitti: well, if only upstream was answering on their channel :/
[09:12] <pitti> mvo: and gtk as well, of course
[09:13] <mvo> pitti: oh, let me check
[09:14] <mvo> pitti: that is the old DistUpgrade/DistUpgradeViewGtk.py we actually need it like this to support lucid->precise upgrades
[09:14] <pitti> mvo: I moved all packages which use GI to python-gi yesterday
[09:14] <mvo> pitti: or am I missing something?
[09:14] <chrisccoulson> good morning everyone
[09:14] <pitti> mvo: well, almost all, there were three which I sent a debian bug for
[09:15] <pitti> mvo: ah, I see
[09:15] <pitti> mvo: well, it's fine; we don't _need_ to drop it in 12.04 yet
[09:15] <chrisccoulson>  whoever is on precise and running firefox could probably switch to the firefox-next PPA now, to start testing the first post-release update for 12.04 ;)
[09:15] <pitti> mvo: I just did that dependency cleanup yesterday so that it's easier to see what's left to do
[09:15] <pitti> mvo: I figure we can drop the static bits in 12.10?
[09:15] <mvo> pitti: indeed, we can't as its still needed for the upgrade, once 12.04 is out we can drop it
[09:15] <pitti> mvo: perfect
[09:15] <mvo> pitti: great, thanks for the double-check!
[09:16] <pitti> so s-c-p won't be ported, but I figure we'll use the GNOME upstream printing UI in 12.10
[09:17] <pitti> mvo: I think I already tried moving the gst bits in sessioninstaller to GI, but the gst GIR is not working very well
[09:17] <pitti> anyway, no need to spend vast amount of effort on this now
[09:18] <pitti> mvo: btw, any chance we can look at bug 950676 this week?
[09:18] <ubot2`> Launchpad bug 950676 in apt "lucid->precise upgrade failure due to gir1.0->gir1.2 conflicts" [High,New] https://launchpad.net/bugs/950676
[09:20] <mvo> pitti: yes!
[09:20] <BigWhale> killall -9 unity ; unity & should be sufficient after an upgrade, right?
[09:21] <BigWhale> ok, unity --replace is needed
[09:24] <broder> didrocks: i expect alt-f10 to maximize the window, but it doesn't
[09:26] <broder> aha! apparently i'm supposed to retrain myself to use super-up. didn't notice that before - must not have done a unity --reset yet
[09:27] <didrocks> broder: alt-f10 doesn't maximize, it's supposed now to open the appmenu
[09:29] <broder> didrocks: yep, got it. i was having problems immediately after upgrading, so i checked ccsm and alt-f10 was still listed as being the maximize. since then i've done a unity --reset, and it's now showing super-up
[09:29] <broder> so it seems like i was left without a functioning maximize shortcut immediately after upgrading, which seems suboptimal
[09:29] <didrocks> broder: yeah, compiz isn't great for migrating settings unfortunatly
[09:29] <chrisccoulson> chop the last 4 words from that sentence ;)
[09:29]  * chrisccoulson trolling
[09:30] <chrisccoulson> :-)
[09:30] <broder> seems like it might be worth just coming up with some condition where it's reasonable to reset the settings on upgrade. maybe first time you login to the ubuntu session or something?
[09:31] <seb128> hey chrisccoulson, how are you?
[09:31] <chrisccoulson> hi seb128. i'm good thanks, but a bit tired. how are you?
[09:32] <seb128> chrisccoulson, lucky you, you can troll without being trolled back, I can't remember having hit any firefox bug this cycle :p
[09:32] <chrisccoulson> heh
[09:32] <seb128> chrisccoulson, same here, good but tired, I'm working on it through coffee though ;-)
[09:32] <chrisccoulson> yeah, it's fairly solid atm
[09:32] <chrisccoulson> and i even run nightly builds :)
[09:33] <seb128> chrisccoulson, time for you to tackle your g-s-d login measurement workitem then! ;-)
[09:33] <chrisccoulson> yeah, i'll do that later. just getting firefox 12 beta stuff ready :)
[09:33] <chrisccoulson> (already)
[09:33] <seb128> chrisccoulson,  is 12 the one which will have some ui changes?
[09:34] <chrisccoulson> seb128, what sort of changes? it looks fairly similar to the current version here
[09:34] <seb128> chrisccoulson, dunno, I read some article online which stated they were looking at changing the ui, how tabs are rendered and a few other things
[09:34] <chrisccoulson> oh, the theme refresh
[09:35] <chrisccoulson> no, that hasn't happened yet
[09:35] <chrisccoulson> if that happens, then it won't be before firefox 14, seeing as nothing has landed on trunk yet
[09:35] <seb128> ok
[09:35] <seb128> chrisccoulson, didn't they want to change the startpage as well?
[09:35] <pitti> didrocks: so, unity --reset destroyed all my settings, but alt+left/up are still broken in ffox and weechat :/
[09:36] <chrisccoulson> i'm not sure what's going on with the startpage. i thought they were going to have a home tab, which would be the access point to the app store
[09:36] <pitti> anyway, will deal with this later on, need to run to the supermarked quickly
[09:36] <chrisccoulson> but i don't really know what is happening with that just yet
[09:36] <didrocks> pitti: yeah, duflu found another place where it can causes this
[09:36] <seb128> chrisccoulson, ok, nothing fancy in 12 yet then ;-)
[09:36] <didrocks> pitti: so maybe another today
[09:36] <chrisccoulson> what happens to the startpage is probably going to be driven by the requirements of https://wiki.mozilla.org/Web_Apps_integration
[09:37] <seb128> chrisccoulson, is mozilla trying to turn my browser into an OS? ;-)
[09:37] <chrisccoulson> lol
[09:38] <seb128> and I can't even say "I will stay on the lts", you will bring the new crack there for us :p
[09:38] <chrisccoulson> i really want to provide our own branded local startpage, so that we benefit from some of the features of the upstream startpage
[09:38] <chrisccoulson> as it stands, we will miss out on features that are accessed via the upstream startpage
[09:39] <seb128> right
[09:39] <seb128> chrisccoulson, btw did you get anywhere about the search entry not respecting your local for searches?
[09:39] <seb128> or rather google not respecting your locale
[09:39] <chrisccoulson> not yet. that reminds me, i need to email someone at google about that
[10:06] <rickspencer3> wow, unlucky day for me :/
[10:07] <seb128> rickspencer3, what happened?
[10:07] <rickspencer3> I did a dist-upgrade yesterday, eveyrthing was fine
[10:07] <rickspencer3> booted this morning, got a disk check ... then unity didn't quite finish loading
[10:07] <rickspencer3> this is on my workstation
[10:07] <rickspencer3> I did a hard reboot
[10:07] <rickspencer3> I suppose I should have ssh'ed in and gotten logs and stuff
[10:07] <rickspencer3> dang
[10:08] <rickspencer3> worked perfectly this time :)
[10:08] <rickspencer3> brb
[10:33] <tkamppeter> pitti, hi
[10:33] <pitti> hello tkamppeter
[10:34] <tkamppeter> pitti, I have committed cups-filters 1.0.5 now. Canb you upload it to Debian and Ubuntu? It fixes all PostScript printer problems.
[10:34] <pitti> tkamppeter: nice! so did it help to reduce the PS level?
[10:36] <pitti> tkamppeter: I'll have a look at debian bug 663564, and then uplaod
[10:36] <ubot2`> Debian bug 663564 in cups-filters "cups-filters: 'make clean' leaves some object files over" [Normal,Open] http://bugs.debian.org/663564
[10:36] <pitti> tkamppeter: that's also something which sohuld go upstream
[10:38]  * desrt yawns
[10:42] <tkamppeter> pitti, reducing of the PS level did not help. The solution was adding certain workaround code to deactivate some PS features which the interpreters do not like.
[10:42] <seb128> desrt, hey, wth, waking up at the middle of the night now? ;-)
[10:42] <desrt> can't sleep :)
[10:42] <tkamppeter> pitti, The "make clean" issue and some improvement on texttopdf will come in 1.0.6.
[10:42] <pitti> hey desrt
[10:43] <pitti> tkamppeter: ah, so should I leave this bug alone for now?
[10:43] <tkamppeter> pitti, please upload 1.0.5 as it is now, as the bugs it fixes are of high importance.
[10:43] <pitti> ack
[10:43] <desrt> pitti: good morning
[10:43] <desrt> seb128: how's glib?
[10:44] <desrt> i notice you did a subtle increase of the priority on my XUL bug :)
[10:44] <seb128> desrt, glib is just building, I cleared night backlog first
[10:45] <desrt> sounds good.  looks like no new crisis for me overnight
[10:45] <seb128> desrt, XUL> no, I just added an Ubuntu component to the bug and make it match the upstream settings
[10:46]  * desrt notices some nice new gnome upgrades and wonders if it's jbicha or ricotz
[10:47] <desrt> remind me again: what is the dpkg equivalent for cat /var/lib/dpkg/info/${pkgname}.list?
[10:49] <seb128> desrt, dpkg -L binary?
[10:50] <desrt> thanks
[10:50] <desrt> looks like the new gnome-shell upload has problems :(
[10:50] <seb128> desrt, what sort of problems?
[10:51] <desrt>     JS ERROR: !!!     message = '"missing ; before statement"'
[10:51] <desrt>     JS ERROR: !!!   Exception was: SyntaxError: missing ; before statement
[10:51] <desrt>     JS ERROR: !!!     lineNumber = '12'
[10:51] <desrt>     JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/misc/config.js"'
[10:51] <desrt>     JS ERROR: !!!     stack = '"@/usr/share/gnome-shell/js/ui/main.js:15
[10:51] <desrt> these sort
[10:51] <seb128> urg
[10:51] <desrt> const HAVE_NETWORKMANAGER = @HAVE_NETWORKMANAGER@;
[10:51] <desrt> oof.
[10:51] <seb128> hum
[10:52] <desrt> i'm not a javascript genius or anything... but that looks more like automake than javascript :)
[10:52] <seb128> desrt, so interesting, new cogl got uploaded and binaries got rejected
[10:52] <seb128> I guess that's because it failed to build on armel and somebody figured it should build everywhere or nowhere ;-)
[10:52] <desrt> what does it mean for binaries to be rejected?
[10:52] <seb128> desrt, that they will never reach you
[10:53] <desrt> curious
[10:53] <desrt> how is that related?
[10:53] <seb128> desrt, related to what?
[10:53] <desrt> the gnome-shell failure
[10:53] <seb128> oh, I'm not speaking about your bug
[10:53] <desrt> ah.  okay
[10:53] <desrt> i though you had an explanation :)
[10:53] <seb128> desrt, rather commenting on the "new gnome upgrades"
[10:54] <seb128> desrt, we were > < that close to get the new clutter in :p
[10:54] <seb128> desrt, which meant the new gnome-shell in
[10:54] <desrt> oh
[10:54] <seb128> it's just that armel ruined your party
[10:54] <desrt> so now i have a new ultra-high priority bug :)
[10:54] <desrt> got a log?
[10:54] <seb128> desrt, https://launchpadlibrarian.net/96702927/buildlog_ubuntu-precise-armel.cogl_1.9.8-0ubuntu1_FAILEDTOBUILD.txt.gz
[10:55] <desrt> did you report that already?
[10:55] <seb128> desrt, jbicha used https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/941617
[10:55] <ubot2`> Launchpad bug 941617 in clutter-1.0 "FFe: Update clutter/cogl to 1.9" [Wishlist,Confirmed]
[10:56] <seb128> desrt, oh, upstream, dunno if he did
[10:56] <desrt> ahh
[10:56] <desrt> no arm builds for ppa, i'm guessing
[10:56] <seb128> desrt, no
[10:56] <jbicha> good morning
[10:57] <desrt> jbicha: good morning
[10:57] <seb128> hey jbicha, how are you?
[10:57] <desrt> jbicha: bad gnome-shell upload? :(
[10:58] <seb128> desrt, hum, glib with your cancellable patches failed to build
[10:58] <desrt> ah.  it's a good morning for everybody
[10:58] <desrt> seb128: test failures?
[10:59] <seb128> desrt, http://pastebin.ubuntu.com/883085/
[10:59] <desrt> seb128: you applied one patch and forgot the other
[10:59] <seb128> desrt, bah, some days I hate quilt
[11:00] <seb128> desrt, sorry about that
[11:00] <desrt> :)
[11:00] <desrt> no worries.  only increased my heart rate for 1 minute :)
[11:00] <seb128> I had both but I ls >> serie (forgot the 's')
[11:00] <desrt> ahh
[11:01] <desrt> hum
[11:01] <desrt> most curious!
[11:01] <desrt> ./cogl/cogl.c:#ifndef GL_PACK_INVERT_MESA
[11:01] <desrt> ./cogl/cogl.c:#define GL_PACK_INVERT_MESA 0x8758
[11:02] <jbicha> desrt: do you have an ARM chroot? I tried to make one yesterday but I was getting memory errors
[11:02] <desrt> jbicha: i have an arm system, in fact
[11:03] <desrt> jbicha: the fix here is quite obvious, though
[11:03] <seb128> desrt, mhr3: btw the libgee warning issue is fixed after yesterday's "rebuild with current vala" update
[11:03] <desrt> jbicha: the code that uses GL_PACK_INVERT_MESA was originally added to cogl.c with this #ifndef business above
[11:03] <jbicha> http://irclogs.ubuntu.com/2012/03/14/%23ubuntu-desktop.html#t01:05
[11:03] <desrt> the code was later moved to cogl-framebuffer.c
[11:03] <mhr3> seb128, awesome, thx
[11:04] <desrt> but the #ifndef didn't follow it
[11:04] <desrt> the #ifndef just needs to be moved over
[11:05] <seb128> pitti, \o/ syncdaemon bug
[11:05] <pitti> just pushed the fix upstream
[11:05] <pitti> seb128: with that I'm on par with you again!
[11:05] <seb128> pitti, ;-)
[11:05] <pitti> actually no, I uploaded a fix in ubuntu-defaults-builder this morning
[11:05] <pitti> so, +1
[11:06] <seb128> pitti, I've 3 fixes lined up for upload
[11:06]  * pitti sighs
[11:06] <seb128> pitti, you need to get an extra 2 this afternoon :p
[11:06] <desrt> jbicha: checking what's the deal with the mesa headers on ARM
[11:06] <desrt> clearly there is some expectation that this symbol may not exist
[11:07] <desrt> jbicha: have you reported the bug upstream yet?  i can do so, with a patch, if you like
[11:08] <jbicha> desrt: no, I had assumed I was missing some build-depends, thanks
[11:08] <desrt> jbicha: seems quite unlikely
[11:08] <seb128> chrisccoulson, don't feed the trolls! (reading your -discuss reply)
[11:09] <chrisccoulson> heh :)
[11:09] <chrisccoulson> i love feeding the trolls!
[11:09] <seb128> ;-)
[11:10] <desrt> jbicha: recent bug.  happened on feb 25
[11:15] <desrt> jbicha: https://bugzilla.gnome.org/show_bug.cgi?id=672038
[11:15] <ubot2`> Gnome bug 672038 in general "Move the fallback define for GL_PACK_INVERT_MESA" [Normal,Unconfirmed]
[11:15] <desrt> this actually looks vaguely like a mesa bug....
[11:16] <desrt> but i don't know enough to say
[11:16] <desrt> because in the mesa headers you see this:
[11:16] <desrt> #ifndef GL_MESA_pack_invert #define GL_PACK_INVERT_MESA               0x8758 #endif
[11:16] <desrt> and later on, this:
[11:16] <desrt> #ifndef GL_MESA_pack_invert #define GL_MESA_pack_invert 1 #endif
[11:16] <desrt> if those were in the other order, this would to working fine
[11:17] <jbicha> desrt: have you test built on ARM yet?
[11:17] <desrt> nope
[11:17] <desrt> let me do that.
[11:17] <desrt> i think it may take a while
[11:18] <desrt> my arm system isn't the zippiest thing :)
[11:20] <seb128> desrt, ok, so glib seems to work fine for me, you have another chance to stop me before I upload it :p
[11:20] <desrt> seb128: i didn't find any problems either
[11:20] <seb128> desrt, ok, let's upload
[11:21] <glatzor> hello mvo, i committed some fixes to the aptdaemon branch
[11:22] <seb128> glatzor, hey
[11:23] <desrt> jbicha: test-building now
[11:23] <jbicha> desrt: Timo attached almost the same patch to the Ubuntu bug :)
[11:23] <chrisccoulson> hmmm, i make the same assumption in firefox as dbusmenu is making for bug 953562
[11:23] <ubot2`> Launchpad bug 953562 in glib2.0 "dbusmenu assumes GDBus cancellation is reliable (and it's not)" [High,Fix committed] https://launchpad.net/bugs/953562
[11:23] <desrt> jbicha: the problem is pretty obvious
[11:24] <seb128> chrisccoulson, so you should be happy with the new upload ;-)
[11:24] <desrt> devscripts has the worst recommends list of anything in the entire archive :p
[11:25] <desrt> at least it doesn't install postfix anymore :)
[11:25] <glatzor> hey seb128 ! how are you?
[11:26] <seb128> glatzor, I'm thanks, how are you?
[11:26] <desrt> *** parse error
[11:26] <glatzor> seb128, fine. except that I have to leave for work now :/ :)
[11:26] <seb128> glatzor, ok, ttyl!
[11:26] <seb128> desrt, ?
[11:27] <desrt> 07:26 < seb128> glatzor, I'm thanks, how are you?
[11:27] <seb128> ups, "good" ;-)
[11:27] <desrt> so i looked at the background thing last night, btw
[11:27] <desrt> it's not as easy as all that
[11:28] <desrt> mostly because lightdm does its image loading in a thread (as not to block the main UI thread when switching users)
[11:28] <desrt> and gnomebg is not threadsafe
[11:28] <desrt> seb128: hey.  hold the press on your glib upload.
[11:28] <desrt> (unless it's too late)
[11:28] <seb128> desrt, not too late
[11:29] <desrt> i have another few patches for you :p
[11:29] <seb128> desrt, the log ones?
[11:29] <desrt> ya
[11:29] <seb128> desrt, yeah, I noticed in git, both are needed?
[11:29] <desrt> there are 3, actually
[11:29] <desrt> although the one that's not in the bug is a windows fix
[11:29] <desrt> and very embarassing :)
[11:30] <seb128> desrt, I don't care about win bugs for Ubuntu uploads :p
[11:30] <seb128> desrt, the buffer size one?
[11:30] <desrt> ya
[11:30] <desrt> pretty hilarious
[11:30] <seb128> yeah, "don't care" ;-)
[11:30] <desrt> "allocate an 80 bytes buffer"
[11:30] <desrt> "now read a 100 bytes string into it"
[11:30] <desrt> ...2 lines apart
[11:31] <seb128> desrt, ok, I'm uploading that dbusmenu fix for now, I will do another upload later today or tomorrow, I've some packaging stuff to fix, I will include the log stuff then
[11:32] <desrt> cool
[11:40] <didrocks> pitti: so, the additional alt fixes seems to work without any regression I spotted
[11:40] <didrocks> pitti: will take my chance and upload it
[11:40] <pitti> \o/
[11:40]  * pitti hugs didrocks
[11:41]  * didrocks hugs pitti back
[11:43] <desrt> didrocks: my god...
[11:43] <desrt> didrocks: this caching code you added to gnomebg
[11:43] <desrt> INSANE
[11:43] <didrocks> desrt: hum, really? vuntz acked it for my defense :p
[11:44] <desrt> the num_monitor thing is really really difficult to understand
[11:44] <desrt> and possibly broken too
[11:44] <desrt> since it assumes that a particular monitor number will always exist at the same geometry position
[11:45] <desrt> jbicha: cogl test build is looking good... it's past the compiling and onto the docs
[11:45] <didrocks> desrt: hum, the unicity is done on num monitor/geometry transformation/resolution
[11:46] <desrt> didrocks: so consider that i have a 'span' configuration with monitor 0 (1920x1200) on the left and monitor 1 (same) on the right
[11:46] <desrt> then i change the order
[11:47] <desrt> the filenames should probably encode the relative position of each monitor -- not just its number
[11:48] <desrt> and for completeness, also the total resolution of the desktop (since that could theoretically have an impact in the span case as well)
[11:48] <desrt> unless you have a reason to believe i am wrong :)
[11:48]  * desrt has never seen it actually do the wrong thing
[11:50] <didrocks> desrt: I don't see how the span configuration changes things? As there is a support for only one wallpaper per monitor from what I know of?
[11:50] <didrocks> the wallpapers can't span across monitors, isn't it?
[11:50] <desrt> yes.  they can.
[11:50] <desrt> that's the 'spanned' option
[11:51] <didrocks> desrt: oh really? Never noticed the option. So in this case, you're right, encoding the relative position and total resolution would be needed
[11:52] <desrt> didrocks: i'm sort of wondering why you bother with the monitor number at all
[11:52] <desrt> didrocks: it seems in the 'spanned' case i end up with a file like so:
[11:52] <desrt> 0_6_3840_1200_3243108fa99adb7361797c9c64f0021d
[11:52] <desrt> ie: the total resolution of both monitors
[11:52] <didrocks> desrt: the monitor was added at the end of the review
[11:52] <didrocks> from a french man leaving in Grenoble :)
[11:52] <desrt> which means the monitor number thing is ... not really used, i guess
[11:52] <desrt> ahh
[11:52] <desrt> vuntz added that part?
[11:52] <didrocks> the idea was "maybe one day, we will support multiple wallpapers"
[11:53] <desrt> *headdesk*
[11:53] <didrocks> don't remember if I added them or he did TBH
[11:53] <didrocks> quite 2 years old :)
[11:53] <didrocks> but remember that was added at the end
[11:53] <didrocks> triggered an offset issue
[11:53] <didrocks> and then fixed :)
[11:53]  * desrt was trying to make sense of GnomeBG yesterday for adding to lightdm (so we can have slideshows supported)
[11:54]  * didrocks tries to grab the bug reference
[11:54] <didrocks> desrt: but yeah, not having the monitor number prevent this case (which isn't used today)
[11:55] <desrt> https://bugzilla.gnome.org/show_bug.cgi?id=608419
[11:55] <ubot2`> Gnome bug 608419 in libgnome-desktop "Caching wallpaper resize to avoid some CPU cycle at startup" [Enhancement,Resolved: fixed]
[11:55] <desrt> in any case, i don't think it matters too much
[11:55] <desrt> i've stopped trying for now :)
[11:55] <desrt> getting GnomeBG into lightdm would be ... much less trivial than i expected
[11:56] <desrt> and there are more important things to do :)
[11:56] <desrt> jbicha: the cogl build is working
[11:56] <didrocks> agreed :)
[11:57] <didrocks> well, changing the monitor side, if they have exactly the same resolution and you use "spanned" wallpaper
[11:57] <didrocks> the probability is quite low :)
[11:57] <desrt> not really
[11:58] <desrt> when you hook up two new monitors for the first time there's a 50/50 chance that they end up the right way around
[11:58] <didrocks> hum, really? I remember digging into the glib monitor doc for that purpose
[11:58] <didrocks> and I thought it was quite clear from there that the number were preserved
[11:59] <desrt> yes.  that's exactly the problem :)
[11:59] <desrt> the number is preserved -- so it used to be in the order (0 1) and now it's in the order (1 0)
[11:59] <didrocks> I meant, the number per monitor
[12:00] <didrocks> like, the monitor tagged 0 will always be 0 :)
[12:00] <didrocks> or you mean, when you switch them?
[12:00] <desrt> yes.  exactly
[12:00] <desrt> maybe i plug in the monitor physically on the right side and it becomes 0 and the desktop decides it is the one on the left
[12:00] <didrocks> ah yeah, in this case, even if the resolution is different on both, you will get the bug
[12:00] <didrocks> hum, tricky :)
[12:01] <desrt> well, i'm not sure
[12:01] <desrt> because there is another bug that seems to prevent that, as mentioned :)
[12:01] <desrt> in the span case, it seems that only monitor number 0 is ever seen
[12:01] <desrt> with the total resolution of the entire desktop appearing in the cache filename
[12:01] <desrt> which is.. unexpected :)
[12:01] <didrocks> indeed :)
[12:02] <desrt> caching is also never done for slideshows
[12:02] <desrt> and it could be...
[12:02] <didrocks> yeah, that's in a FIXME in the code, or TODO :)
[12:02] <desrt> ie: cache the scaled source images
[12:02] <desrt> before blending
[12:02] <didrocks> one after another
[12:02] <didrocks> we need to think about the cleanup though
[12:02] <desrt> ya....
[12:03] <didrocks> I'm still very surprised by the speed we gained with that
[12:03] <didrocks> quite unexpected
[12:03] <desrt> scaling is not cheap
[12:03] <desrt> well, actually
[12:03] <desrt> the clever thing to do would be to scale on the GPU
[12:03] <didrocks> indeed :)
[12:04] <desrt> but i guess that might not work if you can't upload the original image as a texture because it's too large
[12:04] <desrt> or if you're in a software-only situation
[12:04] <didrocks> it's not like the GPU is totally unfamiliar with this kind of operations :)
[12:04] <didrocks> large FBO support is better, so maybe in few years
[12:04] <cyphermox> yo/sup
[12:04] <didrocks> (apart from cheap netbooks)
[12:05] <desrt> heh
[12:05] <desrt> i totally pictured you writing that patch on your cheap netbook :)
[12:05] <didrocks> desrt: no, it was on my cheap laptop! :)
[12:05] <didrocks> desrt: even if it's totally true that most of the time, I do my GNOME patches on my netbook (while travelling)
[12:05] <didrocks> but not this one though ;)
[12:06] <didrocks> oh wait
[12:06] <didrocks> yeah I refactored it for gnome3 on my netbook
[12:06] <didrocks> while doing Annecy->Lyon ;) so yeah, half true :)
[12:07] <desrt> ugh
[12:07] <desrt> annoying unity issue: go into a terminal and hold down alt+a
[12:07] <dupondje> Could somebody give https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/931397 a look?
[12:07] <ubot2`> Launchpad bug 931397 in xorg-server "Xorg crashes with AutoAddDevices "false"" [High,Confirmed]
[12:07] <desrt> watch the appmenu flicker....
[12:08] <didrocks> desrt: yeah, this one is tracked
[12:08] <didrocks> desrt: (TBH, we have more annoying issues, but shhhhh ;))
[12:09] <desrt> didrocks: i found a really really cool one yesterday :)
[12:09] <didrocks> if it's cool, I'm all hears :)
[12:09] <desrt> http://imgur.com/uGhcd
[12:10] <desrt> that's what happens if you write a program that repeatedly opens/closes a window quickly
[12:10] <desrt> seems the code that dynamically adds/removes the icon for the window to the dash has some race in it
[12:11] <didrocks> huho, scary
[12:11] <didrocks> please ping DBO about it
[12:11] <didrocks> (what's this train icon?)
[12:11] <desrt> it's a custom gnome-terminal profile i have called 'spadina'
[12:11] <desrt> that sshs me to my linode (also called 'spadina')
[12:12] <didrocks> makes sense :)
[12:12] <desrt> spadina is a street in downtown toronto.  it has streetcars on it.
[12:12] <desrt> they kinda look like that :)
[12:12]  * desrt needed an icon *shrug*
[12:12] <didrocks> ah ok, got it!
[12:12]  * didrocks still waiting for thunderbird to restart
[12:12] <didrocks> (approx. 2min here)
[12:12]  * didrocks looks at chrisccoulson meanwhile
[12:12] <desrt> http://people.csail.mit.edu/hasinoff/spadiners/510-streetcar.jpg
[12:14] <didrocks> desrt: the picture looks accurate
[12:17] <dupondje> cnd: You have any status on https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/931397 ?
[12:17] <ubot2`> Launchpad bug 931397 in xorg-server "Xorg crashes with AutoAddDevices "false"" [High,Confirmed]
[12:20] <desrt> DBO: hey
[12:20] <desrt> DBO: http://imgur.com/uGhcd happens if you run http://fpaste.org/79H2/ for a little while
[12:21] <desrt> even after you quit the program...
[12:21] <desrt> and unity tends to be using a lot of CPU at that point as well (and doesn't go back down)
[12:21] <desrt> restarting unity fixes both issues
[12:24] <seb128> dupondje, hey, I recommend you use #ubuntu-x for xorg issues
[12:25]  * dupondje joins :) thx
[12:34] <desrt> seb128: thanks for the gio-symbols catch
[12:34] <seb128> desrt, yw ;-)
[12:39] <tkamppeter> pitti, patch for debian bug 663564 is applied to the upstream BZR of cups-filters now, so will be available in 1.0.6.
[12:39] <ubot2`> Debian bug 663564 in cups-filters "cups-filters: 'make clean' leaves some object files over" [Normal,Open] http://bugs.debian.org/663564
[12:41] <didrocks> tkamppeter: hey, did you get the time to look at why I can't print anymore btw? :)
[12:58] <jbicha> seb128: can you approve cogl & gjs from the new queue?
[13:00] <seb128> jbicha, done
[13:01] <tkamppeter> didrocks, this is a known bug, thew update to the new gutenprint does not update your PPD.
[13:01] <tkamppeter> didrocks, for the time being, run
[13:02] <tkamppeter> sudo cups-genppdupdate
[13:02] <didrocks> tkamppeter: thanks! Will try that :)
[13:16] <desrt> jbicha: fixed build has been fired off, i guess?
[13:20] <seb128> desrt, cogl? it built and got newed already
[13:20] <desrt> oh.  that was fast.
[13:21] <desrt> i guess the builders are not loaded down for the day yet :)
[13:21] <seb128> desrt, seems like builders are more powerful that your arm device ;-)
[13:21] <seb128> desrt, well, archive builders are usually fine
[13:21] <seb128> desrt, the lag is often on ppa builders
[13:21] <desrt> ah.  didn't realise PPA was a different set
[13:21] <desrt> i thought they used the same x86(64) ones
[13:21] <seb128> desrt, the ppa ones are virtual buildders with a limit set of archs
[13:21] <desrt> and just the arm ones were for archive-only
[13:22] <seb128> desrt, archive buildders are real hardware builders :p
[13:22] <desrt> :)
[13:22] <seb128> desrt, https://launchpad.net/builders btw
[13:22] <desrt> i was just looking for that
[13:22] <desrt> didn't it used to be called soyuz?
[13:23] <desrt> aw crap.  unity crashed again -- in a really interesting way
[13:23] <seb128> no, "soyuz" is the launchpad codename for the buildds part
[13:23] <seb128> it redirects to launchpad.net/launchpad nowadays though
[13:23] <desrt> i can still type into IRC and my screen is updating (i see my music player ticking off seconds)
[13:23] <desrt> but i can't interact with any chrome (like moving windows)
[13:23] <desrt> nor can i change the focus
[13:23] <seb128> *fun*
[13:24] <desrt> good old compiz restart fixes all :)
[13:24] <desrt> we still have lpia builders?  fascinating.
[13:25]  * desrt thought those were done
[13:25] <pitti> tkamppeter: ah, great
[13:25] <seb128> desrt, yeah, and seems people still use it :p
[13:26] <seb128> desrt, the ppa stats have "lpia 	1 	4 jobs (1 hour 40 minutes) "
[13:26] <desrt> there's only one... so i'm guessing it's only used for some special-cases?
[13:26] <seb128> desrt, likely for people still running builds on ubuntu version where lpia was supported
[13:26] <seb128> not sure, that would be a lamont's question ;-)
[13:27] <seb128> or maybe just "in case we would need one a day for a reason"
[13:27] <desrt> ah.  good call.
[13:28] <desrt> ah nice.  jbicha did a fixed gnome-shell upload
[13:28] <desrt> didrocks: The following packages will be REMOVED: unity
[13:29] <desrt> The following packages will be upgraded: unity-common
[13:29] <didrocks> desrt: you are on amd64?
[13:29] <desrt> yup...
[13:29] <desrt> that's not supposed to happen anymore, right?
[13:29] <didrocks> desrt: seems the unity-common in i386 is published
[13:29] <didrocks> and the unity package built on amd64 for you not
[13:29] <didrocks> desrt: hum, no, it's supposed to happen still :)
[13:29] <desrt> ah.  okay.
[13:29] <desrt> so the usual "don't blindly dist-upgrade" :)
[13:30] <didrocks> exactly!
[13:30] <desrt> sorry for the bug
[13:30] <didrocks> no worry ;)
[13:30] <didrocks> at least, you asked before telling yes :p
[13:31]  * desrt runs apt-get with -y from now on for extra fun
[13:31] <didrocks> tip of the day: add --force-yes as well :)
[13:31] <desrt> is that for the "Yes, I really mean to destroy my system" prompt? :)
[13:31] <didrocks> ;)
[13:32] <didrocks> (btw, when compiz crash, it's normal you can still type on IRC and the screen refreshes by Xorg)
[13:32] <didrocks> but as you told, you can't switch the focus
[13:32] <didrocks> and of course, no chrome
[13:32] <desrt> well, there was chrome
[13:32] <desrt> i just couldn't interact with it
[13:32] <desrt> like dragging the title bar did nothing
[13:32] <didrocks> chrome, like window decoration?
[13:32] <desrt> ya
[13:32] <didrocks> ah interesting, that shouldn't happen indeed :)
[13:33] <tkamppeter> pitti, can you upload CUPS to Debian and Ubuntu? It has important fixes on the IPP backend.
[13:33] <desrt> i don't know if it was a crash as much as a weird sort of lockup
[13:33] <didrocks> well, lockup, if compiz is still running, freeze the screen most of the time, no more refresh
[13:33] <desrt> ya.  that's why i was surprised
[13:36] <pitti> tkamppeter: ok, sure; still fighting with the kfreebsd FTBFS, I'll have another look at this; my first attempt didn't succeed
[13:40] <pitti> tkamppeter: building now
[13:44] <jibel> what is the key to enable/disable the display of the content of ~/Desktop on the desktop ?
[13:45] <seb128> jibel,
[13:46] <seb128> org.gnome.desktop.background show-desktop-icons
[13:48] <jibel> seb128, thanks, that's also the key to bug 953089 \o/
[13:48] <ubot2`> Launchpad bug 953089 in unity-distro-priority "Unity 5.6: key bindings doesn't work on empty workspace" [Medium,Fix committed] https://launchpad.net/bugs/953089
[13:48] <jibel> when show-desktop-icons is disabled, no keybinding work
[13:49] <seb128> hum
[13:49] <seb128> why do people do stuff like that?!
[13:50] <seb128> still a bug, but yeah, stupid options keep bitting us
[13:53] <jibel> it also breaks refresh of the title in the menu bar
[13:54] <seb128> jibel, right, we should not let people turn that off
[13:54] <seb128> jibel, I'm pondering forcing the option under unity
[13:56] <jibel> seb128,is it on or off after an upgrade from oneiric ?
[13:56] <seb128> jibel, it was always on in any ubuntu version
[14:22] <didrocks> seb128: not in une though
[14:23] <didrocks> (sorry, catching up, was building the list for priority on top of priority to prioritize more bugs)
[14:23] <s9iper1> huats:  are you there
[14:23] <s9iper1> ?
[14:23] <didrocks> so maybe une -> natty -> oneiric -> precise
[14:23] <s9iper1> found a bug related to you i guess
[14:24] <didrocks> but it was the default key, so should be migrated to the new default after update/login
[14:26] <cyphermox> didrocks: seb128: pitti: are you guys running the new n-m/n-m-g from ~ubuntu-desktop ppa? I'd upload today if possible
[14:27] <pitti> cyphermox: ah, I'm not; seems I missed the announcement/ping for that
[14:27] <didrocks> cyphermox: I added the ppa this morning, but didn't get a chance to reboot yet
[14:27]  * pitti upgrades
[14:27] <seb128> cyphermox, I didn't restart yet, will do in a bit
[14:28] <cyphermox> thanks guys
[14:32] <huats> s9iper1: I am
[14:32] <huats> but not sure I'll be able to answer you
[14:33] <huats> just query me in private
[14:33] <huats> I'll answer it once I'llbe able (tonight)
[14:59]  * desrt does the happy-cogl dance
[15:00] <desrt> jbicha_: looks like the gnome-shell lg crasher is fixed with the latest upload
[15:02] <jbicha_> desrt: upload? you mean the gnome3 ppa or what?
[15:02] <desrt> yes.  i'd imagine so.
[15:03] <cnd> dupondje, no status to report
[15:03] <jbicha_> wow, yeah it works here too now, I did pull from the Debian packaging & rebuilt a few things....
[15:04] <cnd> dupondje, why are you running with auto add devices as false?
[15:05] <seb128> jbicha_, I promoted the cogl binary and retried builds
[15:05] <seb128> jbicha_, clutter builds I mean
[15:06] <dupondje> cnd: seems like its a required setting for bumblebee
[15:06] <cnd> dupondje, what's bumblebee?
[15:07] <dupondje> nvidia optimus implementation.
[15:07] <cnd> why would it be required for it?
[15:07] <dupondje> http://www.bumblebee-project.org/
[15:08] <dupondje> Not sure why its needed btw.
[15:09] <cnd> dupondje, where do you see anything that says it is needed?
[15:11] <dupondje> https://github.com/Bumblebee-Project/Bumblebee/blob/master/conf/xorg.conf.nouveau
[15:12] <dupondje> the bugreporter is the main dev of Bumblebee btw
[15:34] <chrisccoulson> i'm disappointed that the troll didn't respond to my email on the gwibber thread
[15:44] <pitti> didrocks: rebooted with new unity, and there's still a problem
[15:44] <pitti> cyphermox: new nm/nm-applet from PPA, working fine for WPA2 and system-wide connection
[15:44] <cyphermox> pitti: thanks
[15:45] <cyphermox> WPA2 I'm using too, testing WPA2 ad-hoc as a replacement for the WPA ad-hoc fubar
[15:45] <didrocks> pitti: :/ we kill latest opportunities though
[15:45] <didrocks> works well here, but since yesterday
[15:45] <pitti> didrocks: now that my Alt key is fully working, what do I annoy you with now?
[15:45] <didrocks> (weechat in a terminal)
[15:46]  * pitti hugs didrocks, SCNR
[15:46]  * didrocks hugs pitti too
[15:46] <pitti> working well in weechat and firefox again!!
[15:46] <didrocks> stop doing that to my little heart!
[15:46] <didrocks> :)
[15:46] <didrocks> phew ;)
[15:55] <jbicha> chrisccoulson: I was wondering why you wanted to break my Flash plugin, but it turns out I just needed to update my partner sources.list to precise
[15:56] <chrisccoulson> jbicha, it's all part of a larger conspiracy :)
[15:57] <jbicha> the conspiracy that the partner repo stays empty most of the development cycle? or the one involving Gwibber?
[16:07] <jbicha> hmm, clutter fails on armel & armhf too https://launchpadlibrarian.net/96782888/buildlog_ubuntu-precise-armhf.clutter-1.0_1.9.14-0ubuntu1_FAILEDTOBUILD.txt.gz
[16:12] <pitti> Sweetshark: is bug 906402 still required for precise?
[16:12] <ubot2`> Launchpad bug 906402 in graphite2 "[MIR] graphite2" [Undecided,Incomplete] https://launchpad.net/bugs/906402
[16:13] <Amoz> jbicha, you're my hero <3
[16:13] <Sweetshark> pitti: no, IMHO.
[16:14] <Amoz> and everyone else working on gnome 3.4 for official repos
[16:15] <pitti> Sweetshark: ah, good; could you please close the bug then, saying that/why it's not needed any more?
[16:16] <Sweetshark> pitti, jibel_: I still cant reproduce bug 916868 -- I just did a complete upgraded from a virgin oneiric install.
[16:16] <ubot2`> Launchpad bug 916868 in libreoffice "package libreoffice-common 1:3.5.0~beta2-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 134 (dup-of: 915271)" [Undecided,New] https://launchpad.net/bugs/916868
[16:16] <ubot2`> Launchpad bug 915271 in libreoffice "package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty" [Critical,Fix released] https://launchpad.net/bugs/915271
[16:16] <jbicha> desrt: the clutter failure is upstream too, right?
[16:16] <Sweetshark> jibel, jibel_: Is it possible to run jenkins with debug=70000?
[16:27] <jibel> Sweetshark, sure. first thing tomorrow
[16:28] <Sweetshark> jibel: great! that helps me a bunch. thanks!
[16:33] <didrocks> cyphermox: seems I stil have network :)
[16:36] <cyphermox> didrocks: great
[16:36] <cyphermox> I'll upload this after lunch I think
[16:36] <cyphermox> others tested this as I fit in two extra bug fixes on top
[16:36] <didrocks> cyphermox: yeah, I tried wired and wifi and both are fine here
[16:37] <didrocks> nice :)
[16:37] <cyphermox> anyone tried 3G? (though I did, and I know it works)
[16:37] <cyphermox> I just ordered 4 new 3G devices to help with testing, and slowly build up my box of pain
[16:37]  * didrocks doesn't have a 3G card support in the computer
[16:38] <cyphermox> didrocks: don't worry about it
[17:12] <pitti> good night everyone!
[18:03]  * didrocks waves good evening
[18:05] <mterry> Is anyone else having trouble clicking on scrollbar grips this past week?
[18:12] <dobey> mterry: if you mean overlay-scrollbar, i've always had problems with that.
[18:12] <mterry> dobey, I do mean o-s, but I've only had recent problems.  It goes away too quickly
[18:14] <dobey> ah
[18:15] <dobey> mterry: the fade-out time seems fine here. i have also been experiencing some of my mouse clicks being ignored all over the place, though
[18:16] <mterry> dobey, no, not that.  It just goes away before I can get to it
[18:17] <dobey> mterry: it doesn't pop up where your mouse is?
[18:18] <mterry> dobey, well, it does, but kind of to the right, as expected.  When I try to move over to it, it goes away
[18:18] <seb128> mterry, do you use a pad?
[18:18] <seb128> mterry, or any touch device?
[18:18] <mterry> seb128, laptop touchpad
[18:18] <seb128> mterry, it's https://bugzilla.gnome.org/show_bug.cgi?id=672009
[18:18] <ubot2`> Gnome bug 672009 in gtk "gtk 3.3.18, menu items are not highlighted on mouseover with pads devices" [Normal,New]
[18:19] <seb128> mterry, gtk missing enter events on touch devices
[18:19] <dobey> huh
[18:19] <seb128> likely a side effect of the xinput 2.2 smooth scrolling work
[18:19] <seb128> there is a small testcase with a gtkbutton on the bug
[18:19] <seb128> it only gets the first enter event not the next ones
[18:19] <seb128> works fine if you use a mouse
[18:19] <mterry> seb128, ah, I'm opening an email on d-d-l from you now that sounds related  :)
[18:19] <seb128> it's something xinputish
[18:20] <mterry> eh, not quite
[18:20] <seb128> mterry, yeah, the email is gtk doing a slightly incompatible change in their abi
[18:20] <dobey> yeah, i'm not on my laptop
[18:20] <seb128> which is another "fun" issue
[18:20] <mterry> seb128, but cool, good to know it's a known issue anyway
[18:21] <seb128> mterry, still hacking on unity-greeter? as much as I love smooth animation I think it's time you stop investing on that to tackle some bugs ;-)
[18:23] <mterry> seb128, no, done with that.  I got as far as I cared to with GTK+.  Expect a release tomorrow.  Now I'm fixing up quickly's tutorial.  And then hopefully bugs (though I'll probably give deja-dup bugs a priority unless you've got something you care about)
[18:23] <mterry> Oh, happy pi day btw!
[18:24] <mterry> :)
[18:24] <seb128> lol, "pi day"
[18:24] <seb128> mterry, we have plenty on the milestoned list ;-)
[18:26] <dobey> how is 14/03/2012 == pi?
[18:26] <dobey> silly 'mericans
[18:27] <chrisccoulson> dobey, right, i thought exactly the same: https://twitter.com/#!/chrisccoulson/status/179955372759584769 ;)
[18:28] <dobey> heh
[18:28] <chrisccoulson> i like Laney's suggestion
[18:28] <dobey> yeah
[18:28] <chrisccoulson> 22/7 ;)
[18:28] <dobey> although, 3.333... isn't really pi either
[18:29] <dobey> not that i oppose the consumption of pie on any day
[18:30] <micahg> dobey: your math is off :P
[18:30] <dobey> eh?
[18:30] <micahg> 22/7 != 3.333
[18:31] <dobey> uh
[18:32] <dobey> ah right
[18:32] <dobey> anyway, it's not pi
[18:32] <micahg> 22/7 =~ 3.14285 which is closer than 3.14 as was pointed out on slashdot
[18:34] <micahg> π =~ 3.14159
[18:34] <dobey> heh, "slashdot"
[18:34] <dobey> i know what pi is
[18:36] <xclaesse> jbicha, argh gnome-shell does not start anymore
[18:36] <dobey> and pi number of days into the existence of earth, it was still a big ball of plasma
[18:36] <xclaesse> jbicha, since the cogl/clutter update
[18:38] <xclaesse> jbicha, I have a backtrace if you want
[18:41] <xclaesse> jbicha, https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/955347
[18:41] <ubot2`> Launchpad bug 955347 in cogl "Crash in gnome-shell" [Undecided,New]
[18:57] <soaringsky> hey, last December it was mentioned that you guys want a dedicated gnome shell distro
[18:57] <soaringsky> I made ugr last year, but had to stop due to health issues
[19:18] <soaringsky> seb128: ^^
[19:21] <seb128> soaringsky, hi, yes?
[19:21] <seb128> soaringsky, talk to jbicha and ricotz maybe, they maintain the gnome-shell stack
[19:22] <seb128> soaringsky, it's just lacking a few extra volunteers to work on it and make a proper derivative like xubuntu etc
[19:22] <soaringsky> jbicha: ricotz: ^^
[19:22] <soaringsky> seb128: yeah, I have those volunteers
[19:22] <seb128> great, so wait for jbicha to ping back ;-)
[19:23] <soaringsky> seb128: I was almost to that point last year, but I got really sick. now I'm starting to get better and working on ugr again
[19:24] <seb128> soaringsky, ok, great, I never understood the ugr stuff, like why doing a separate project rather than an official variant
[19:24] <seb128> but if both efforts can be merged that would be great
[19:25] <soaringsky> seb128: I couldn't start it out as an official variant. I had to start somewhere
[19:25] <soaringsky> seb128: I wrote the initial preview in two days. I never could have became official in that time
[19:26] <seb128> well, let's not argue on that ;-)
[19:26] <seb128> seems there is enough people interested to do an official variant
[19:26] <seb128> so that's great
[19:26] <soaringsky> seb128: but my goal has always been to become Gubuntu :)
[19:32] <dobey> isn't ~/.config/user-dirs.dirs supposed to get sourced on log-in so those things env up in the ENV?
[19:32] <seb128> dobey, no
[19:32] <ogra_> hmpf
[19:32] <seb128> dobey, glib has an api giving you those folder which parses the file IIRC
[19:33] <dobey> seb128: so one is just supposed to parse the file?
[19:33] <dobey> i know glib has api
[19:33] <ogra_> so who decided to make gcalctool unresizable but also make it wrap the stuff in the top pane ?
[19:33] <dobey> but python doesn't
[19:33] <ogra_> that really doesnt fly if you have a long addition to do
[19:34] <jbicha> xclaesse: yes I know it's broken, there are several uploads, you can use the gnome3 ppa if you don't want to wait
[19:35] <jbicha> soaringsky: well it doesn't start as official, ask Lubuntu about how long that took
[19:35] <seb128> jbicha, that's why you use breaks usually ;-)
[19:35] <seb128> dobey, the point is that you should be using glib
[19:35] <jbicha> but an important first step is getting as much as possible in Ubuntu's official repositories
[19:35] <soaringsky> jbicha: ik, thats why I started unofficial
[19:36] <dobey> seb128: unfortunately that's not so much an option for this. the whole cross-platform thing and all
[19:36] <dobey> seb128: so i guess i have to implement parsing that file
[19:36] <xclaesse> jbicha, so gnome-shell 3.3 is going to precise soon?
[19:36] <seb128> dobey, right, if you don't want to use standards libs I guess you have to do things yourself
[19:36] <jbicha> seb128: could you approve mutter for 386 & amd64 from the new queue?
[19:36] <soaringsky> jbicha: yeah, I have a few minor things like cantarell and shell tweaks. then its just the metapackage
[19:37] <dobey> seb128: what i *want* to do is not relevant :)
[19:37] <jbicha> soaringsky: cantarell is in Ubuntu, I think shell tweaks should be a packaged extension if you need them
[19:37] <seb128> dobey, glib works fine under other platforms you support, you could use it
[19:38] <seb128> dobey, and if some Xsession script was exporting the xdg dir in the environment that wouldn't help you on other platforms anyway
[19:38] <dobey> seb128: feel free to convince people who make that decision. and good luck with that.
[19:38] <dobey> seb128: no, but it would make my life easier on linux
[19:38] <seb128> well you have to implement the parsing anyway
[19:38] <dobey> because os.environ.get() is a lot less code
[19:38] <seb128> so you can as well use it accross platforms
[19:39] <soaringsky> jbicha: oh, cool. I don't have more than a handful of my own packages. everything else is already in repos
[19:39] <seb128> jbicha, done
[19:40] <seb128> jbicha, bah, clutter ftbfs on armel
[19:40] <seb128> desrt, ^
[19:40] <seb128> https://launchpadlibrarian.net/96782888/buildlog_ubuntu-precise-armhf.clutter-1.0_1.9.14-0ubuntu1_FAILEDTOBUILD.txt.gz
[19:40] <seb128> "/usr/bin/install: will not overwrite just-created `/build/buildd/clutter-1.0-1.9.14/debian/tmp//usr/lib/arm-linux-gnueabihf/pkgconfig/clutter-glx-1.0.pc' with `clutter-glx-1.0.pc'"
[19:40] <seb128> wth?
[19:41] <seb128> desrt, that was just a fyi seems you watch the new gnome-shell landing
[19:42] <jbicha> seb128: yeah, I did mention it failed but I don't really have the ability to fix arm failures :(
[19:43] <ricotz> jbicha, seb128, hi
[19:43] <seb128> hey ricotz
[19:43] <soaringsky> jbicha: back in the day when gnome-shell was young, we had a lot of version in compatability issues with shell extensions. is that still the case?
[19:43] <xclaesse> jbicha, I see gnome3 ppa also has totem 3.3, that won't be merged into main I guess?
[19:44] <ricotz> i dont have time to look into it, but this is caused by my arm patch to unify the pkg-config file name
[19:44] <jbicha> soaringsky: my personal opinion is that we shouldn't bother packaging extensions, but point people to extensions.gnome.org
[19:44] <soaringsky> jbicha: ok
[19:44] <jbicha> ricotz: ah, what happens if we don't use that patch?
[19:44] <ricotz> seb128, jbicha, the x11 backend installs a clutter-glx.pc too which should be work around somehow
[19:45] <seb128> jbicha, just drop the patch, if there is an issue and some user try to run gnome-shell on arm they will complain
[19:45] <seb128> it's not like your armel gnome-shell userbase was big
[19:45] <ricotz> jbicha, dropping it might be fine if all rdepens have caught up to use clutter.pc instead of a backend specific one
[19:46] <seb128> it's maybe desrt only :p
[19:46] <seb128> ricotz, jbicha: if that's not the case you will know soon with rebuilds
[19:46] <jbicha> ricotz: ok, I'll drop it and if it's needed we can add it again later
[19:46] <ricotz> seb128, some rdepends arent really handling gl vs gles2
[19:47] <ricotz> jbicha, ok
[19:47] <ricotz> jbicha, i guess doko will complain if it breaks
[19:48] <soaringsky> jbicha: extensions.gnome.org looks great. I'll probably code a quick app that has that site embedded
[19:48] <xclaesse> jbicha, ok FYI adding the gnome3 ppa and gnome-shell 3.3, the crash is fixed :)
[19:48] <jbicha> soaringsky: you should talk to GNOME about that
[19:48] <desrt>  /usr/bin/install: will not overwrite just-created `/build/buildd/clutter-1.0-1.9.14/debian/tmp//usr/lib/arm-linux-gnueabihf/pkgconfig/clutter-glx-1.0.pc' with `clutter-glx-1.0.pc'
[19:48] <jbicha> xclaesse: yes, it's a temporary problem in the normal archives
[19:49] <desrt> seb128: highly curious
[19:49] <seb128> jbicha, next time please make cogl breaks gnome-shell
[19:49] <desrt> seb128: looks like a packaging problem more than anything else?
[19:49] <seb128> desrt, read scrollback, it's ricotz's fault
[19:49] <soaringsky> jbicha: k, thanks. do you know of any way to have extensions installed by default?
[19:49] <seb128> desrt, or don't read scrollback
[19:49] <seb128> desrt, unping, nothing for you, it's being addressed, just keep the "gnome-shell on its way" info ;-)
[19:52]  * desrt is very very tired
[19:54] <jbicha> soaringsky: Debian enables the alternative status menu (aka "don't hide the shut down button") by default
[19:54] <jbicha> http://packages.qa.debian.org/g/gnome-shell-extensions.html
[19:57] <soaringsky> jbicha: ty
[19:58] <desrt> THOSE BASTARDS
[19:58] <desrt> how dare they modify our perfect UI
[19:59] <desrt> who do they think they are?!
[20:26] <chrisccoulson> desrt, perhaps you need to hit them with a trademark stick like some other projects do? That will stop people from modifying your perfect UI ;)
[20:27] <chrisccoulson> actually, i shouldn't put ideas in to peoples heads
[20:32] <dobey> chrisccoulson: but then they'll have to ship it as goneme instead of gnome
[20:50] <thumper> hi people
[20:50] <thumper> I have a really annoying problem that effectively stops me being able to use a vt
[20:51] <thumper> I get a bucketload of "iwlwifi 0000:05:00.0: GF was set with SGI:SISO" sent to standard out on the vt
[20:51] <thumper> anywhere from 10 to 20 / second
[20:51] <thumper> can't use gdb with that going on