[00:32] <RAOF> Man, writing upstart rules is super-easy.
[00:32] <RAOF> Now I just need to figure out the proper dbus-monitor incantation I want.
[00:39] <broder> RAOF: http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-routing-match-rules :)
[00:52] <jasoncwarner_> RAOF and robert_ancell :0 glad to see both of you ! I have a lightdm-that-might-be-an-x question
[00:55] <jasoncwarner_> RAOF and robert_ancell , so I got my fancy new x220 (intel, of course) and everything is working great now...after some tweaking
[00:56] <jasoncwarner_> but on the unity-greeter screen, my mouse has HUGE amounts of lag on it...I can't really move it around...
[00:56] <jasoncwarner_> not sure how to debug it and get you both some useful information
[00:58] <robert_ancell> jasoncwarner_, anything in the -greeter.log file in /var/log/lightdm?
[00:58]  * jasoncwarner_ looking
[00:58] <robert_ancell> jasoncwarner_, also, once logged in can you run 'dm-tool add-nested-seat' and see if the same problem occurs?
[01:00] <jasoncwarner_> robert_ancell: what should I be looking for in the greeter log?
[01:00] <robert_ancell> anything looping around?
[01:00] <robert_ancell> i.e. hundreds of lines of something?
[01:01] <jasoncwarner_> robert_ancell: no, nothing like that...
[01:01] <jasoncwarner_> dm-tool, should I just run that and then reboot?
[01:02] <robert_ancell> no, it will pop up a nested X window with a login screen
[01:02] <robert_ancell> which is running everything the same as normal, except it uses the Xephyr X server instead of the normal one
[01:03] <jasoncwarner_> do you know package name ot install for xephyr?
[01:03] <robert_ancell> jasoncwarner_, apt-get install xserver-xephyr
[01:03] <jasoncwarner_> thanks, installing...
[01:04] <jasoncwarner_> thanks,,, robert_ancell
[01:04] <jasoncwarner_> it does not happen in the dm-tool
[01:04] <jasoncwarner_> mouse moves fine
[01:07] <jasoncwarner_> robert_ancell: guessing X then...
[01:07] <robert_ancell> that suggests an X problem.  It could be gnome-settings-daemon or something like that though
[01:08] <robert_ancell> the next step is to log out, and then go to a text terminal and run top and see if anything is acting up
[01:08] <robert_ancell> (I'm assuming it always occurs?)
[01:09] <jasoncwarner_> robert_ancell: yeah, it has always happened ... "always" being, 'since I got this computer yesterday...every time on this comp"
[01:09] <jasoncwarner_> I'll log out now and check top...be back in a few
[01:09] <robert_ancell> at least it's consistent
[01:13] <jasoncwarner_> hey robert_ancell I just tried to shutdown/restart from the greeter
[01:13] <jasoncwarner_> #1 - the box wasn't themed with a GTK style...it was base GTK
[01:13] <jasoncwarner_> #2 - nothing worked? couldn't restart and couldn't power down...
[01:13] <robert_ancell> do you have a /etc/lightdm/unity-greeter.conf?
[01:14] <jasoncwarner_> robert_ancell: rebooting again...will check in a sec
[01:15] <jasoncwarner_> robert_ancell: I hate writing this, and I don't know how you'll feel reading it (RAOF either)
[01:15] <jasoncwarner_> but when I went to a tty and then back to unity-greeter
[01:16] <jasoncwarner_> the mouse just started working fine
[01:16] <jasoncwarner_> and then when I rebooted...it seemed to work fine
[01:16] <jasoncwarner_> that is my def of "magic" :)
[01:16] <robert_ancell> oh yay
[01:16] <robert_ancell> um, so problem solved right?
[01:16] <robert_ancell> :)
[01:17] <jasoncwarner_> :) that would be an awesome note in the release notes: if laggy mouse, do this ;)
[01:17] <jasoncwarner_> btw
[01:17] <jasoncwarner_> i do have a unity-greeter.conf file
[01:18] <robert_ancell> jasoncwarner_, does it sound like bug #828112?
[01:18] <ubot2`> Launchpad bug 828112 in unity-greeter "Password field feedback slow at times" [Medium,Incomplete] https://launchpad.net/bugs/828112
[01:21] <jasoncwarner_> robert_ancell: I think it resembles, that but not exactly.
[01:21] <jasoncwarner_> though, when I am having the problem, yes, the password field does have lag as well
[01:22] <robert_ancell> could you put your notes on that bug and note the mouse was also a sympton
[01:24] <jasoncwarner_> robert_ancell: will do
[01:29] <jasoncwarner_> robert_ancell: lag is back after reboot
[01:29] <jasoncwarner_> and, yes, it was solved simply by this
[01:29] <jasoncwarner_> CTRL+ALT F2
[01:29] <jasoncwarner_> CTRL+ALT F7
[01:29] <jasoncwarner_> no lag after that
[01:29] <jasoncwarner_> rebooting again...
[01:31] <jasoncwarner_> robert_ancell: could it be gnome-settings-daemon related?
[01:32] <jasoncwarner_> I am getting pretty consistent crashes with g-s-s
[01:32] <jasoncwarner_> and that might be why I don't have a GTK theme on the shutdown dialog?
[01:32] <robert_ancell> I'm just speculating, but both the indicators and g-s-d could run all sorts of things that unity-greeter has no control over
[01:33] <TheMuso> The sound indicator runs pulse for one...
[01:35] <jasoncwarner_> I imagine if g-s-s fails to load I would have quite a few problems...and g-s-s crashes each and every boot for me.
[01:35] <jasoncwarner_> so perhaps...
[01:35] <jasoncwarner_> https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838502
[01:35] <ubot2`> jasoncwarner_: Error: <Bugtracker.plugin.Launchpad instance at 0x8d65a2c> bug 838502 not found
[02:20] <jasoncwarner_> robert_ancell: after rebooting quite a few times,I think that bug you linked before and mine are probably the same
[02:21] <jasoncwarner_> the op prob just didn't move his mouse to see it not moving
[02:21] <robert_ancell> jasoncwarner_, oh good.  Is it coming back again?
[02:21] <jasoncwarner_> yeah
[02:21] <robert_ancell> yeah, that was my guess too
[02:23] <jasoncwarner_> robert_ancell: did you see my above? I can get it to go away with switching to TTY and back again
[02:23] <jasoncwarner_> and when I lock my screen and go to switch user (which brings me back to unity-greeter)
[02:23] <jasoncwarner_> I get it as well
[02:23] <robert_ancell> RAOF, ^ does that sound remotely X related?
[02:24] <robert_ancell> My first guess is video drivers with VT switching, or some sort of power management issue (i.e. idle checking)
[02:25] <jasoncwarner_> robert_ancell: I'm on intel on this machine...
[02:35] <RAOF> robert_ancell: That could be X related; VT switching drops drm master, and switching back regains it, which might mean that if it failed the first time then VT switching could re-enable acceleration?
[02:36] <robert_ancell> RAOF, anythink we could check to confirm that?
[02:36] <RAOF> robert_ancell: /var/log/Xorg.0.log would contain information to confirm or deny that hypothesis.
[02:36] <robert_ancell> jasoncwarner_, ^^
[02:37] <jasoncwarner_> RAOF: what should I be looking for int aht log?
[02:38] <RAOF> jasoncwarner_: Well, pastebinning it would be good.  The drmOpenDevice lines would be part of the bit.
[02:40] <jasoncwarner_> RAOF: http://pastebin.com/HwtT0JZn
[02:41] <RAOF> Well, that doesn't contain what I'd expect.
[02:42] <RAOF> Oh!  Compiz is being really slow?  Can you check your top output?  I've had a problem where something's spamming the dbus, and dbus-daemon has high CPU usage, and because the panel is in the compositor that means that _everything's_ slow.
[02:42] <RAOF> (I think in my case it was because indicator-datetime was endlessly trying to enumerate all my calendars)
[02:43] <RAOF> VT switching could possibly halt compiz for long enough to unwedge things.
[02:44] <jasoncwarner_> RAOF: my top didn't show compiz being slow...I'll reboot and look again...but remember, switching to a VT seems to clear it all up...I'm not sure I'll be able to see it...
[02:44] <jasoncwarner_> oh...I'll log in remotely to see if it is there
[02:48] <jasoncwarner_> RAOF: ok...I'm actually goign to finish these three emails from my TODO first...been all day and I haven't gotten 'em done...be back in a bit
[02:49] <RAOF> jasoncwarner_: No problem :)
[02:49] <RAOF> robert_ancell: Have you played around with dbus-monitor?  I can't seem to get it to display anything but signals, and I want to trace method calls instead.
[02:50] <robert_ancell> RAOF, no, sorry
[02:51] <stgraber> RAOF: system or session bus? and do you need the content of the call of just interface, path and function name?
[02:51] <broder> RAOF: you can't use dbus-monitor to get method calls by default
[02:51] <RAOF> stgraber: System bus, and I really just want to know _when_ it gets called.
[02:52] <RAOF> broder: Ah, well now my results make sense :)
[02:52] <stgraber> RAOF: sorry can't help much with system bus unless you can tell your client that it's at another location than /run/dbus/system_bus_socket
[02:52] <stgraber> (I wrote a dbus proxy as part of my work on arkose which logs everything that goes through it)
[02:53] <broder> RAOF: if you put http://pastebin.ubuntu.com/679351/ at /etc/dbus-1/system-local.conf and then do pkill -HUP dbus-daemon, you'll be able to see them
[02:53] <RAOF> broder: Can I mess with the system bus config to make that work?
[02:53] <broder> but that completely compromises the integrity of anybody that's depending on dbus for security :)
[02:53] <broder> e.g. NM
[02:54] <RAOF> Well, it's just for local debugging, so that's fine.
[02:54] <robert_ancell> RAOF, does it make sense to disable TCP connections in lightdm by default for security reasons (Bug #838152)
[02:54] <ubot2`> Launchpad bug 838152 in lightdm "hard-coded "-nolisten tcp"" [Low,Triaged] https://launchpad.net/bugs/838152
[02:55] <RAOF> robert_ancell: Not listening on TCP is certainly the correct default.
[02:55] <robert_ancell> RAOF, ta
[02:56] <RAOF> It's something that you might want to offer as an option, though.
[03:13] <broder> RAOF: fwiw, i think there are less heavyhanded ways of enabling limited eavesdropping, but i've never been able to get them to work
[03:14] <RAOF> broder: Nyargh!  Is there a *more* heavyhanded way of enabling eavesdropping?  I've dumped that in, and can see _other_ method calls, but not the ones that I'm interested in!
[03:15] <broder> hmm..that's not a problem i've had before
[03:15] <broder> are you sure the calls are actually getting made?
[03:15] <RAOF> Ah, there we go.
[03:15] <RAOF> Apparently you need to restart d-feet before that'll work.
[03:16] <RAOF> Oh, yeah!  The dbus reload probably needs that, doesn't it.
[03:16] <broder> huh, weird
[03:18] <RAOF> I wasn't expecting getting dbus-monitor to work to be the most difficult part of this :)
[03:20] <RAOF> Writing upstart rules is plesantly easy.
[03:21] <randrums> https://plus.google.com/115895054477394715961/posts/84KCPX2xgUh
[03:22] <DBO> ping RAOF
[03:23] <DBO> so good news bad news time
[03:23] <DBO> good news: the signal for figuring out when a resume happens works
[03:23] <DBO> bad news: recreating the FBO's doesn't fix the corruption issue
[03:44] <RAOF> DBO: Hm.  That's non-good.
[03:44] <DBO> so looking at it more carefully
[03:44] <DBO> what I observe is this
[03:44] <RAOF> DBO: I thought you'd previously tested and found that to work?
[03:45] <DBO> it did in nux
[03:45] <DBO> I was assuming that would transfer over...
[03:45] <DBO> (we had the inverse problem last cycle, nux was corrupted and compiz wasn't)
[03:45] <DBO> so my observations seem to be as follows:
[03:46] <DBO> 1) the FBO, without being reloaded, actually pants fine (contents are uncorrupted when painted into)
[03:46] <DBO> 2) painting the texture the fbo is bound to onto another fbo works fine
[03:46] <DBO> 3) painting the compiz FBO onto the backbuffer somehow fails terribly
[03:47] <DBO> which really makes me wonder, why do the nux fbo's paint just fine
[03:47] <RAOF> Because magic.
[03:47] <RAOF> Presumably :)
[03:48] <DBO> I have a screenshot
[03:50] <DBO> RAOF, http://i.imgur.com/TFOXc.png
[03:50] <DBO> see how the corruption is a predictable pattern
[03:50] <DBO> I suspect somehow the driver is blending the FBO onto the backbuffer with an incorrect format
[03:50] <RAOF> That looks like it's likely to be tiling-related.
[03:51] <DBO> tiling?
[03:51] <RAOF> Given that it occurs on what looks like tiling-sized blocks.
[03:52] <RAOF> Textures aren't linear in memory, at least not if you want it to be fast.
[03:52] <DBO> oh
[03:52] <DBO> is that done automatically by the driver?
[03:52] <RAOF> They're tiled into crazy patterns so that the multi-bar memory controllers are used maximally.
[03:52] <RAOF> Yeah, that's done by the driver.
[03:53] <DBO> maybe an error in the fixed function pipe
[03:53] <DBO> (sam, he's silly like that)
[03:54] <DBO> obviously unity blends fine
[03:54] <RAOF> But it's a fertile source of bugs in the kernel/DDX/mesa layers, at least for the free drivers.
[03:54] <DBO> and functionally, it too is painting FBO's
[03:55] <RAOF> Yeah, if Unity's doing shadery things and compiz is using fixed-function that could be different, I guess.
[03:56] <DBO> well I mean painting the contents of an FBO shouldn't be functionally different than painting a texture
[03:56] <DBO> which still works fine
[03:56] <RAOF> DBO: Will you still be around in ~20 minutes?  I'd like to relocate back from this cafe to home.
[03:57] <DBO> yes
[03:57] <RAOF> Ta.
[03:57] <RAOF> Catch you in 20.
[04:23] <RAOF> DBO: Back.
[04:23] <DBO> welcome back RAOF
[04:26] <DBO> RAOF, if you got any ideas that would be great...
[04:26] <DBO> RAOF, is the backbuffer tiled?
[04:26] <RAOF> *Everything* is likely to be tiled; back buffer, front buffer, textures, the whole enchilada.
[04:26] <RAOF> Because it's like a 300% performance win.
[04:27] <DBO> hmmm
[04:27] <RAOF> (Well, not exactly, but it's a huge performance win)
[04:27] <DBO> I hope we dont have to recreate the GL context to get around this
[04:27] <RAOF> In fact, from what I gather from nouveau the nv5x+ cards don't actually handle *untiled* surfaces.
[04:27] <DBO> that would kind of suck
[04:28] <RAOF> That would rather suck, yes.
[04:28] <RAOF> Can you recreate the backbuffer or something?  Like, swap out the composite overlay window?
[04:34] <DBO> I dont think so
[04:34] <DBO> maybe?
[04:35] <RAOF> That might be something to try, if some tiling bit isn't getting reset properly across suspend.
[04:36] <DBO> wow
[04:37] <DBO> I just realized that the opengl plugin in compiz creates a shader in the most crazy ass fashion
[04:37] <DBO> im betting if we change how we paint this thing
[04:37] <DBO> that will fix it
[04:38] <RAOF> Hah!
[04:38] <RAOF> Always it is with the craaaazy compiz!
[04:47] <jbicha> robert_ancell: good work on unity-greeter today, fixed 2 of my bugs!
[04:49] <jbicha> my indicators are in a crash-loop, it's "fun" to see the appmenu appearing and reappearing
[04:57] <jbicha> are there any logs I can look at it to see what's breaking with my indicators?
[05:23] <robert_ancell> jbicha, :)
[05:23] <pitti> Good morning
[05:25] <jbicha> pitti: good morning
[05:25] <kenvandine> good morning pitti
[05:26] <pitti> hey guys, how are you?
[05:30] <TheMuso> Morning pitti.
[05:30] <RAOF> Hey pitti
[05:31] <pitti> so, interesting release night..
[05:34] <kenvandine> pitti, how is the release looking?
[05:34] <pitti> was respun during the night due to a pretty serious bug with GPT partitions
[05:46] <didrocks> good morning
[05:47] <pitti> bonjour didrocks
[05:48] <RAOF> Oh, no!  It's didrocks!  Quick, hide! :)
[05:52] <didrocks> guten morgen pitti
[05:52] <didrocks> RAOF: not fast enough! :-)
[05:57] <didrocks> the more I see bug report, the more I will be in favor to revert Ctrl + Del to simply Del. The trash is there for fat fingers…
[05:57] <jasoncwarner_> didrocks: I agree with that..
[05:58] <pitti> and now crtl+del is harder to do than shift-del, which immediately removes it..
[05:59] <pitti> this was one of these rather pointless changes which destroy the habits learned in years *sigh*
[05:59] <jasoncwarner_> pitti didrocks change it to just DEL? makes most sense to me.
[06:00] <didrocks> can do it if you both agree :)
[06:00] <didrocks> and +1 with pitti's remark, it's harder that shift + del, which is some kind of hilarious :)
[06:00] <didrocks> than*
[06:00] <pitti> didrocks: we'd need to update the GNOME documentation for that, too, though
[06:01] <didrocks> pitti: indeed, so, opening/find a bug and subscribe the doc team to it? (I think there is no patch to the doc for all the indicator/systray removal anyway)
[06:01] <pitti> not sure whether it's in gnome-user-guide or nautilus help or both
[06:02] <didrocks> I can have a look, will do that after the cjk landing
[06:03] <didrocks> pitti: so, a bunch of package will land with real cjk support (there was a first attempt one ok ago while I was on vacation if i understood correctly), but this time, the correct patches will land
[06:03] <pitti> just saw the confirmation in the bug, nice to hear!
[06:03] <didrocks> this touches apt-xapian-index, zg-extension, sotware-center and unity
[06:04] <didrocks> jasoncwarner_: FYI ^
[06:04] <didrocks> pitti: ok, will land today if all go well :)
[06:04] <jasoncwarner_> didrocks: saw that....big change...lots of testing needed
[06:04] <didrocks> jasoncwarner_: indeed
[06:05] <didrocks> jasoncwarner_: what was missing from the first round was the rebuild of the index once cjk is there
[06:05] <jasoncwarner_> didrocks: ah...cool...thanks
[06:05] <jasoncwarner_> once this gets in then, back to oneconf? ;)
[06:08] <didrocks> jasoncwarner_: I finished the first round of oneconf in parrallel, it's now working with software-center gtk3 :)
[06:09] <didrocks> still missing some speedup improvment (caching and stuff) that I made for the gtk2 version, but it's usable (the whole software-center gtk3 needs some speedups anyways)
[06:58] <jbicha> didrocks: I'll take care of making sure the Ubuntu docs say just Delete
[06:58] <didrocks> jbicha: I'm writing a script for that, will be way easier :)
[06:58] <jbicha> it's not in that many places, is it?
[06:59] <didrocks> jbicha: it's in gnome-user-guide FYI, I just run a script to do the sed and such
[06:59] <didrocks> jbicha: yeah, but there are the translations ;)
[06:59] <jbicha> didrocks: the real docs are in ubuntu-docs, gnome-user-docs is currently just a copy from Debian, it's unclear whether we want to maintain a diff there
[07:00] <didrocks> jbicha: if I press F1 on nautilus, it's gnome-user-docs which is used, isn't it?
[07:01] <jbicha> didrocks: yes that will need to be patched too, thanks :-)
[07:01] <didrocks> jbicha: I'm patching this one (and so, add the tool for regenerating the patch for easier use), can you take care of ubuntu-docs, please?
[07:02] <jbicha> didrocks: actually can you correct the nautilus help link to point to ghelp:ubuntu-docs instead of gnome-user-docs?
[07:02] <jbicha> gnome-user-docs isn't installed by default
[07:03] <jbicha> I thought Nautilus shipped its own help but it just piggybacks on the system help since it's Core
[07:06] <didrocks> jbicha: you're right, it's not installed by default
[07:06] <didrocks> weird, it's in main, maybe for the dvd?
[07:06] <jbicha> didrocks: upgraders will still have it & it's pulled in for users who install gnome shell
[07:07] <jbicha> for Natty, we heavily modified gnome-user-docs instead of just using ubuntu-docs so it was installed in Natty
[07:09] <RAOF> pitti: You're our resident PolicyKit maestro, right?  In bug #837851 it seems that policykit hates colord running as not root; is there a way to tell PolicyKit that it's ok for the colord user to check whether $USER has authorisation on its interfaces?
[07:09] <ubot2`> Launchpad bug 837851 in colord ""Color" tool in GNOME System Settings only recognizes my webcam as color-manageable device" [High,Confirmed] https://launchpad.net/bugs/837851
[07:09] <didrocks> jbicha: ah, makes sense then, now everything is in ubuntu-docs? I should not touch gnome-user-docs then
[07:09] <jbicha> didrocks: yes, it's just easier to keep gnome-user-docs in sync with Debian for now
[07:10] <didrocks> jbicha: ok, I remove my script then :)
[07:10] <didrocks> jbicha: adding an ubuntu-docs task and assign to you, ok?
[07:11] <jbicha> didrocks: that's fine, we were thinking about pushing a new ubuntu-docs update this weekend
[07:11] <RAOF> pitti: Specifically, colord asks polkit, as the colord user, whether $USER is authorised to perform the actions, and polkit only allows root to query whether someone else is authorised to perform an action (presumably for security purposes).
[07:11] <didrocks> jbicha: but that means that we will have to patch every application to reference ubuntu-docs rather than gnome-user-docs?
[07:13] <jbicha> didrocks: there aren't that many apps that use g-u-d, but gnome-control-center probably does
[07:13] <didrocks> jbicha: ok, let's try to change it for nautilus first
[07:14] <chrisccoulson> good morning everyone
[07:15] <pitti> hey chrisccoulson
[07:15] <chrisccoulson> hi pitti, how are you?
[07:15] <didrocks> jbicha: so, basically, now it's ghelp:gnome-help#… should it be ghelp:ubuntu-help#… ?
[07:15] <didrocks> good morning chrisccoulson
[07:15] <chrisccoulson> hi didrocks
[07:15] <pitti> chrisccoulson: pretty well, thanks!
[07:15] <pitti> RAOF: (will get to you, still stuck in release juggling and CD testing in parallel)
[07:15] <RAOF> pitti: No problem!
[07:18] <chrisccoulson> hmmmm, i just did apport-bug compiz, and apport seems to have frozen :/
[07:18] <jbicha> didrocks: yes, when we push the new ubuntu-docs we'll have to change it again though because the new url will be help:
[07:18] <jbicha> instead of ghelp:
[07:19] <didrocks> jbicha: ok, let's do that change once you pushed the new ubuntu-docs package, ok?
[07:19] <didrocks> jbicha: I'll just push the Ctrl + Del -> Del
[07:20] <jbicha> didrocks: yes the other isn't ready yet
[07:33] <pitti> RAOF: so, polkit
[07:33] <pitti> RAOF: right, I'm afraid the 'ownuser || uid==0" check is hardcoded, so that you can't spy on other uers
[07:33] <pitti> users
[07:34] <RAOF> That seems like a misfeature.
[07:34] <pitti> so for this we'd need a provision to mark a particular system user as being able to do the same
[07:34] <RAOF> Right, that was what I was thinking.
[07:34] <pitti> or a particular program
[07:34] <pitti> like, this privilege could become a polkit privilege
[07:35] <pitti> (recursivity FTW)
[07:35] <RAOF> org.freedesktop.polkit.check_authorisation :)
[07:35] <RAOF> Hm, no.  That wouldn't work; it needs to be a per-action thing.
[07:36] <RAOF> You want the colord user to be able to check whether $USER is authorised for org.freedesktop.colord.*, but not anything else.
[07:36] <RAOF> So, an extension to the action semantics could do this.
[07:36] <pitti> RAOF: what does colord do if it cannot check this?
[07:36] <RAOF> Refuses to add the device, so the cups and g-s-d integration fail.
[07:37] <pitti> asked the other way round, what are the default permissions on org.freedesktop.colord.* ?
[07:37] <RAOF> at_console
[07:37] <pitti> I'm not entirely sure why it asks a particular user's permissions to add devices to cups, as cupsd is a system service
[07:37] <pitti> RAOF: eww
[07:37] <RAOF> Yeah, I'm not sure if cups is actually going to work *at all*
[07:38] <pitti> colord uses polkit _and_ at_console?
[07:38] <pitti> at_console is an ancient hack for programs which don't use polkit
[07:38] <RAOF> Sorry, I couldn't remember the polkit name for at_console.  It's default-deny, allow for active user.
[07:38] <pitti> ah, ok
[07:38] <RAOF> Ah, allow_active.
[07:40] <RAOF> Will allow_active allow cupsd access?
[07:40] <pitti> no
[07:40] <pitti> cupsd is not on any console
[07:40] <Sweetshark> Morning all!
[07:40] <pitti> the consolekit stuff only works for actual sessions, not for system daemons
[07:40] <pitti> hey Sweetshark
[07:40] <Sweetshark> pitti: libreoffice_3.4.2-2ubuntu3 for upload on chinstrap
[07:41] <pitti> RAOF: another option would be to actually stop using polkit, and control this with d-bus policy
[07:41] <RAOF> pitti: Yeah, thought so.  So, cupsd isn't going to work even once I fix the session stuff.
[07:41] <pitti> RAOF: i. e. allow calling the API from root (that'll cover cupsd) and at_console
[07:42] <pitti> cf. my comment about at_console being deprecated, though
[07:42] <pitti> RAOF: yet another alternative is to let colord run as root, and lock it down with an apparmor profile
[07:42] <RAOF> pitti: That would be reasonably easy, and a transitional plan while fixing polkit.
[07:43] <pitti> RAOF: depends on how much patching is involved to remove all the polkit checks from colord
[07:43] <RAOF> Although running as root _still_ won't fix cupsd, right?
[07:43] <RAOF> pitti: colord has a --no-polkit option.
[07:43] <pitti> RAOF: but I guess it could be factored out, and the functino would only ask polkit if geteuid() == 0
[07:43] <pitti> and otherwise just allow it
[07:43] <pitti> then we put a d-bus policy in front of it
[07:44] <pitti> that patch should even be upstreamable
[07:44] <pitti> RAOF: ah, that sounds promising, too
[07:44] <RAOF> It wouldn't need to be a patch at all; we can just build colord without policykit support.
[07:45] <pitti> you'd need to patch the d-bus policy, but that's relatively simple
[07:45] <RAOF> Yeah, I'm pretty sure I know how to do that.
[07:45] <pitti> some of the interfaces might be save for everyone to call
[07:46] <pitti> and the ones that aren't should be removed from context="default" and added to <policy at_console="true">
[07:46] <pitti> and again to <policy user="root">
[07:46] <pitti> to cover g-s-d (first) and cupsd (second)
[07:47] <pitti> RAOF: /etc/dbus-1/system.d/NetworkManager.conf does that, for example
[07:47] <RAOF> Great.
[07:48] <RAOF> And then, a patch to polkit to allow doing this there.
[07:52] <pitti> and a patch to its policy to allow access to root users, not just allow_active
[07:52] <pitti> RAOF: ^ that's easy to do, I can help you with that once it becomes relevant
[07:52] <pitti> (man pklocalauthority)
[07:52] <pitti> something like
[07:53] <pitti> [allow access to cups]
[07:53] <pitti> Identity=unix-user:root
[07:53] <pitti> Action=org.fd.colord.whatever
[07:53] <pitti> ResultAny=yes
[07:54] <didrocks> pitti: when you get a second: bug #838623. Do you need a bug/FFe for activating the CJK support? (it was supposed to already be activated, it wasn't the case though)
[07:54] <ubot2`> Launchpad bug 838623 in software-center "FFe, UIFe: bring back OneConf to Software-Center" [Medium,In progress] https://launchpad.net/bugs/838623
[07:54] <pitti> didrocks: no, bug fix
[07:55] <didrocks> ok, thanks :)
[07:55] <pitti> everything is supposed to work in CJK :)
[07:56] <RAOF> Oh, there isn't an <allow_root>yes</allow_root> specifier in the actions.  That's kinda strange.
[07:56] <didrocks> pitti: indeed :)
[07:56] <RAOF> Let's play with dbus policy!
[07:57] <pitti> RAOF: not in the .policy files, no; that needs to go into pklocalauthority
[07:59] <RAOF> The strange corners you find in polkit!
[08:00] <kamstrup> didrocks: don't sweat over dee - we don't need it really, all required things are distropatched by ken, it's just so that other distros can ship gwibber without cherry picking extra api from trunk :-)
[08:01] <didrocks> kamstrup: I know, was just kidding :-)
[08:01] <kamstrup> didrocks: phew, i wouldn't wanna upset you already after my second day back ;-)
[08:02] <didrocks> kamstrup: it's never too late to upset me, seems that's dx paradigm ;-)
[08:10] <rodrigo_> morning
[08:23] <rodrigo_> kamstrup, did you get someone to upload jhbuild?
[08:24] <kamstrup> rodrigo_: I poked lool (as he was the original maintainer afaik), but he was not overly keen on jumping in :-)
[08:24] <rodrigo_> kamstrup, ok, I can do a merge proposal then
[08:25] <rodrigo_> what's the jhbuild version you need?
[08:25] <rodrigo_> hmm, there's only 2.32.4 from last December in download.gnome.org
[08:26] <kamstrup> rodrigo_: that's also the one :-)
[08:26] <rodrigo_> that's the one you need?
[08:50] <chrisccoulson> jasoncwarner_, enjoying your new laptop? ;)
[08:51] <jasoncwarner_> chrisccoulson: yes, yes I am
[08:52] <chrisccoulson> excellent :)
[08:52] <jasoncwarner_> and, chrisccoulson , glad you are here! :) I had a question for you. I just installed aurora build of FF
[08:52] <jasoncwarner_> and the menu and ubuntu theme went away
[08:52] <jasoncwarner_> anyway to get those back?
[08:52] <chrisccoulson> i really want to buy a new laptop, but i fear that jo might end my life if i spend money on one, when we're meant to be saving for our own house ;)
[08:52] <chrisccoulson> hmmm, the menu disappeared entirely, or appears in it's own window?
[08:53] <jasoncwarner_> chrisccoulson: it is just not in the global menu position. I would like to renable that because it takes up precious screen realestate on the smaller monitor! :)
[08:53] <jasoncwarner_> chrisccoulson: just tell her for hte good of your relationship you need a new laptop
[08:53] <chrisccoulson> jasoncwarner_, you could try reporting a bug with apport-bug, as the new apport hook i wrote attaches lots of useful information which might save me asking lots of quetions :)
[08:53] <jasoncwarner_> and then watch how quickly a good relationship can go bad ;)
[08:53] <chrisccoulson> heh
[08:54] <jasoncwarner_> chrisccoulson: I think the menu is the new firefox "we don't enable third party libraries anymore" stuff
[08:54] <jasoncwarner_> it says it will be renabled when it is "compatible"
[08:54] <chrisccoulson> jasoncwarner_, this is a build from the firefox-aurora PPA isn't it?
[08:54] <jasoncwarner_> whatever that means
[08:54] <jasoncwarner_> yes
[08:54] <chrisccoulson> jasoncwarner_, yeah, apport-bug firefox might help me figure out what's wrong :)
[08:55] <jasoncwarner_> ok..
[08:55] <chrisccoulson> it should let you report a bug from the PPA
[08:55] <chrisccoulson> and it will be useful to find out if the new hook works from there :)
[08:55] <jasoncwarner_> what about the ubuntu theme? can that be reenabled as well?
[08:55] <jasoncwarner_> stock firefox isn't exactly pretty :/
[08:56] <chrisccoulson> jasoncwarner_, we only shipped with the stock firefox theme before (it just inherits colours from our theme)
[08:56] <jasoncwarner_> this "every new release of firefox breaks all the plugins" thing is getting old...
[08:56] <jasoncwarner_> I highly doubt all those plugins are broken
[08:57] <jasoncwarner_> would like to be able to override and try it out anyway
[09:00] <chrisccoulson> jasoncwarner_, did you manage to report a bug?
[09:00] <jasoncwarner_> on a call...do it in a bit...I'll let you know...
[09:00] <chrisccoulson> thanks
[09:01] <jbicha> jasoncwarner_: don't you use https://addons.mozilla.org/addon/add-on-compatibility-reporter/ ?
[09:11] <chrisccoulson> jbicha, that won't ever work for the globalmenu-extension
[09:11] <chrisccoulson> if it's incompatible, forcing it on will likely just make it crash
[09:13] <jasoncwarner_> chrisccoulson: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/838671
[09:13] <ubot2`> Ubuntu bug 838671 in firefox "Auroa PPA does not work with global menu" [Undecided,New]
[09:14] <chrisccoulson> jasoncwarner_, ah, silly me. i need to refresh the aurora branch with the latest version of the extension ;)
[09:14] <pitti> Sweetshark: oh, you apparently built with -sa; I'll edit the sources.changes in-place to drop the tarballs
[09:14] <chrisccoulson> i should have checked that already
[09:14] <chrisccoulson> https://launchpadlibrarian.net/78687096/Extensions.txt
[09:14] <zen_monkey> nights, how can i report an issue with gnome-settings-daemon from the gnome3-team?
[09:15] <pitti> Sweetshark: oh, or was this done for libreoffice_3.4.2.orig-ext-human-updates.tar.gz? i. e. is that one new?
[09:15] <zen_monkey> it's seriously hogging cpu... lappy will melt :D
[09:15] <pitti> Sweetshark: I'll try whether uploading only this will work
[09:16] <pitti> Sweetshark: uploaded
[09:16] <chrisccoulson> jasoncwarner_, i'll push the latest version and respin the build
[09:18] <chrisccoulson> jasoncwarner_, oh, were you actually using a custom theme before btw?
[09:18] <chrisccoulson> https://launchpadlibrarian.net/78687110/Themes.txt shows that the default is enabled, but you have an incompatible theme installed in your profile
[09:18] <jasoncwarner_> yeah...I was...
[09:18] <Sweetshark> pitti: Yes, I had too build with -sa: there is one new tarball *-ext-human-updates (I hope you didnt drop that one ...)
[09:19] <pitti> Sweetshark: no, that's the one I kept :)
[09:19] <Sweetshark> *relieved*
[09:21] <chrisccoulson> jasoncwarner_, the theme seems to work on a current nightly with addon compatibility checking disabled
[09:21] <chrisccoulson> jasoncwarner_, https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
[10:11] <chrisccoulson> jasoncwarner_, i'm respinning the aurora builds now, so you should get an update in a few hours
[10:11] <chrisccoulson> wow, i've reported 3 bugs this morning. i think that's the most i've reported in ages ;)
[10:21] <didrocks> pitti: small pygi question, how do you handle out parameter for basic types, like GtkMenuPositionFunc (x and y) ?
[10:22] <pitti> didrocks: normally, when you just simply call them, they are part of the return tuple
[10:22] <pitti> but in this case these are out values of a callback
[10:23] <pitti> didrocks: in theory, the callback should just return them, but I don't know whether anyone did that before
[10:23] <didrocks> pitti: ok, let's have a try then ;)
[10:31] <didrocks> pitti: interestingly, it seems to work for y, but not for x… I try adding random parameters, it doesn't complain…
[10:31] <ronoc> pitti, hey ! do you know a way to query if the guest session is disabled on a system ? I could not see anything obvious on d-feet
[10:31] <pitti> didrocks: with somethign as complex and unusual as correctly marshalling out arguments for callbacks I'd not be surprised if it's buggy..
[10:32] <pitti> ronoc: hm, that's a question for robert_ancell
[10:32] <pitti> ronoc: I'm not familiar with how lightdm handles that, I'm afraid
[10:32] <ronoc> pitti, sure no probs
[10:33] <didrocks> pitti: yeah, confirm, only y is working, where should I open a bug, can get a minimal reproduceable testcase
[10:33] <pitti> didrocks: https://bugzilla.gnome.org/enter_bug.cgi?product=pygobject
[10:34] <didrocks> pitti: thanks!
[10:34] <pitti> didrocks: does that block you?
[10:34] <pitti> didrocks: I used popup_for_menu() in computer-janitor, but with a None callback, so I didn't notice that
[10:34] <didrocks> pitti: not, it's just a little bit uglier (the popup menu will appear where the cursor is)
[10:34] <pitti> yeah, that seems to be a reasonable default (menu where you click)
[10:35] <didrocks> so, not a blocker, just a polish
[10:35] <pitti> right
[10:35] <didrocks> that's not the behavior of what I was using: gtkMenuToolButton
[10:35] <didrocks> it position the button above or below
[10:35] <didrocks> but this button has two part: the button itself and the dropdown to show the menu
[10:35] <didrocks> in mpt's spec, it's only one button (https://wiki.ubuntu.com/SoftwareCenter#oneconf)
[10:36] <didrocks> so trying to polish this with a regular button which shows the popupmenu
[10:46] <didrocks> ok, it works on the minimum "not reproducer" :/
[10:47] <didrocks> pitti: oh I get it, it's because I was on my secondary screen, and so x was outside my monitor and so, it sticks on the monitor border
[10:48] <didrocks> so in a nutshell, it works, I just have the get the absolute coordinate
[10:48] <pitti> nice!
[10:48] <pitti> didrocks: so the callback just returns the actual return value and all the out values in order?
[10:49] <didrocks> pitti: indeed, and you just have to not list them as args of the method of course :)
[10:49] <pitti> right
[10:49] <pitti> nice
[11:21] <jasoncwarner_> pitti: just sent you my bootcharts for today...now I'm going to bed! have to get up around 5 for a call :/
[11:34] <rodrigo_> hmm, I don't get any mail when packages in the queue are accepted (or rejected, don't know), is that normal?
[11:57] <Sweetshark> pitti, jasoncwarner_: tommorrow morning I wont be on IRC as I will fly to http://wiki.documentfoundation.org/Hackfest2011
[11:57] <jasoncwarner_> Sweetshark: ok, thanks. have fun and crack some heads ;)
[11:58] <jasoncwarner_> Sweetshark: see if you can get any traction on simplifying the UI! :)
[11:58] <Sweetshark> jasoncwarner_: yep
[11:58]  * jasoncwarner_ notes that he sounds like a broken record sometimes
[11:59] <Sweetshark> jasoncwarner_: Christoph will be there too ...
[11:59] <jasoncwarner_> nice...when are you back?
[11:59] <Sweetshark> jasoncwarner_: I fly back on sunday.
[12:00] <jasoncwarner_> Sweetshark: ok...we'll catch up next week. cheers. have fun...
[12:00]  * jasoncwarner_ going to bed for real this time...
[12:05] <pitti> jasoncwarner_: ok, we need some further mods for that
[12:10]  * rodrigo_ -> lunch
[13:47]  * didrocks has a super small testcase working, but returning the same coordinate in pressing enter or clicking on the mouse doesn't do the same thing in software-center O_o
[13:50] <ronoc> pitti, is mvo on holidays ?
[13:51] <pitti> ronoc: yes
[13:55] <stgraber> didrocks: hey, for Edubuntu we're customizing the big-friendly-button of unity. Apparently diverting /usr/share/unity/4/launcher_bfb.png does the trick for the 3d version but not for the 2d one. Do you happen to know the equivalent?
[14:00] <didrocks> stgraber: I guess that agateau used the vendor-logo or something like that, but he should fix it for using the same
[14:00] <didrocks> agateau: FYI ^^
[14:00] <stgraber> agateau: bug 838829
[14:01] <ubot2`> Launchpad bug 838829 in edubuntu-artwork "[UIFe] Big friendly button not customized in Unity 2d" [Medium,New] https://launchpad.net/bugs/838829
[14:01] <stgraber> agateau: I'm fine diverting another file if needed but I guess using the same icon for both versions would be better :)
[14:01] <agateau> stgraber: is it for Natty or Oneiric
[14:01] <agateau> ?
[14:01] <stgraber> agateau: Oneiric
[14:01] <agateau> stgraber: : I sent an email to design and dx asking if everyone agreed on using distributor-logo... it seems I was ignored :/
[14:02] <didrocks> agateau: stop using standard icons! :)
[14:03] <agateau> didrocks: heh, my mistake, won't happen again :)
[14:03] <didrocks> hope so! :-)
[14:05] <agateau> stgraber: I think bug 838829 should be reassigned to unity-2d (or at least marked as "also affect")
[14:05] <ubot2`> Launchpad bug 838829 in edubuntu-artwork "[UIFe] Big friendly button not customized in Unity 2d" [Medium,New] https://launchpad.net/bugs/838829
[14:06] <stgraber> agateau: Sure, I can change that to "Make unity-2d use the same bfb icon as unity". Will I have that done by beta2?
[14:06] <agateau> stgraber: I think so
[14:06]  * agateau starts a branch
[14:11] <stgraber> agateau: should I assign that bug to you?
[14:11] <agateau> stgraber: please do
[14:14] <Daviey> GRRRRR.. who bound Alt+a ? :(
[14:22] <Daviey> How do you change keybindings in unity?
[14:28] <pitti> Daviey: bound to what?
[14:28] <pitti> Daviey: these days, in ccsm I think
[14:29] <pitti> but Alt+A doesn't do anything here, it gets into the application here
[14:29] <pitti> it's not supposed to be bound to anything
[15:03] <oier> I have seen that there is some kind of alt+' switcher but in my ccsm unity plugin I don't see any switcher tab to activate or configure it
[15:04] <oier> am I missing an update or a package?
[15:24] <tedg> pitti, Hey, what is the machine that has the archives on it that we can grep through?  I can't remember its name.
[15:24] <pitti> tedg: people.canonical.com? that's lillypilly
[15:24] <pitti> tedg: it's not about "Label Empty", is it?
[15:25] <tedg> pitti, I don't think so...
[15:25] <pitti> tedg: ok; I subscribed you to a bug, but it's debugged nwo
[15:25] <tedg> Ah, okay.  I forgot to start up my mail this morning, so it's still downloading :-)
[15:41] <didrocks> rebooting on unity-2d, brb
[15:42] <chrisccoulson> g'ah, trying to build the lightning source package is painful in oneiric
[15:42] <chrisccoulson> just the source
[15:42] <chrisccoulson> it takes nearly 15 minutes with bzip compression
[15:42] <chrisccoulson> and i have to do it 4 times :(
[15:45] <kenvandine> chrisccoulson, that sounds painful
[15:45] <didrocks> chrisccoulson: thunderbird-bin doesn't integrate to the session isn't it? (I always have it running and so, the gnome-session dialog)
[15:47] <chrisccoulson> didrocks, i'm not too sure what you're asking
[15:47] <didrocks> chrisccoulson: when I quit my session, I almost always have the "thunderbird-bin doesn't respond" dialog
[15:47] <didrocks> chrisccoulson: even if I closed the thunderbird window before
[15:49] <chrisccoulson> hmmm, i've not seen that before. in any case, there is no integration at all on the default install (for tbird or firefox), because libgnome isn't on the CD
[15:49] <chrisccoulson> so you won't see that dialog normally ;)
[15:50] <didrocks> chrisccoulson: I get it almost everytime
[15:50] <chrisccoulson> does thunderbird actually appear to close?
[15:53] <didrocks> chrisccoulson: the -bin is still their, but there is no more window
[15:54] <chrisccoulson> ah, ok
[15:54] <chrisccoulson> any chance of attaching gdb to the process?
[15:54] <chrisccoulson> i've seen a shutdown hang before
[15:57] <didrocks> rebooting with new gnome-session
[15:57] <didrocks> chrisccoulson: sure, will do that (probably tomorrow)
[15:57] <chrisccoulson> thanks
[16:09] <Daviey> pitti: sorry, missed your response. Seems that Alt+a is now doing 'similar' behaviour to alt+tab.. showing a preview rather than icons tho.
[16:09] <pitti> Daviey: hm, that's supposed to be Alt+`
[16:09] <pitti> njpatel, didrocks ^
[16:09] <Daviey> pitti: Hmm, yes - showing the same thing on both shortcuts for me
[16:10] <Daviey> a real pain the butt for irssi users :)
[16:10] <pitti> ok, that sounds like a bug
[16:10] <didrocks> Daviey: do you have unity trunk?
[16:10] <Daviey> didrocks: no, oneiric up-to-date
[16:10] <pitti> Daviey: at least it's not meant to behave like this, so it's fixable :)
[16:10] <Daviey> pitti: hurray!
[16:10] <didrocks> Daviey: ok, so, there is a change right now about it
[16:10] <Daviey> I am such a noob, i'm not quite sure what to raise it against.
[16:10] <didrocks> Daviey: normally, now, it tries to detect the key above the tab
[16:11] <pitti> Daviey: raising it against #ubuntu-desktop is not a bad start :)
[16:11] <didrocks> Daviey: I just pushed unity, it will be available in a few hours
[16:11] <Daviey> lol
[16:11] <pitti> didrocks: how is it supposed to detect where a key is located?
[16:11] <pitti> didrocks: my ` key is in the lower left corner of the keyboard..
[16:11] <Daviey> webcam + OCR?
[16:11] <pitti> above the Tab key is +/= for me
[16:11] <didrocks> yeah, webcam is required now  :)
[16:11] <Daviey> heh
[16:12] <didrocks> pitti: some low level xkeyboard API
[16:12] <didrocks> to have the ranges, and such
[16:12] <didrocks> mutter is doing the same btw
[16:12] <pitti> didrocks: that sounds crazy and bug prone
[16:12] <Daviey> didrocks: For the impatient, is there a PPA with trunk?
[16:12] <pitti> I've heard several people now who have that on totally unexpected keys
[16:12] <didrocks> pitti: there is a shortcut anyway, it seems the keycode is 45
[16:12] <didrocks> Daviey: no, there isn't
[16:12] <didrocks> pitti: for gnome-shell
[16:12] <didrocks> or unity?
[16:12] <pitti> unity, I suppose
[16:13] <didrocks> pitti: it was an hardcoded key before
[16:13] <pitti> didrocks: that sounds better
[16:13] <didrocks> worked only on US config
[16:13] <pitti> didrocks: how on earth is software supposed to be able to figure out how my keyboard is physically arranged?
[16:14] <didrocks> pitti: is it better to get the current state which is Alt + Altgr + è on a french keyboard, for instance?
[16:14] <pitti> Can't it be Alt+Tab and Ctrl+Tab or so?
[16:14] <didrocks> pitti: mutter is doing the same for a release already, I just saw that the unity guys went the same path (avoid random keys)
[16:14] <pitti> hardcoded is the opposite of random?
[16:14] <didrocks> and as they ignored modifier, it resulted in Daviey's bug, where A is mapped
[16:15] <didrocks> pitti: random in term of layout on the keyboard?
[16:15] <didrocks> pitti: Alt + Tab is already used, isn't it?
[16:15] <pitti> didrocks: Alt+Tab is hardcoded as well, isn't it?
[16:16] <didrocks> pitti: yeah, but on all keyboards, it's approximately at the same place
[16:16] <didrocks> anyway, it's not mentionned anywhere, not in the changelog, in any bug
[16:16] <didrocks> I just saw the change because I'm looking at unity trunk
[16:16] <pitti> didrocks: so using ctrl+tab for the "other" switcher would be a lot more predictable?
[16:17] <didrocks> pitti: that's a question for DBO and design I guess
[16:17] <pitti> how do you want to document/explain to people how to find the other switcher?
[16:17] <pitti> "Alt+some key on your keyboard, we can't tell you what it is" :)
[16:18] <DBO> you mean "alt + key above tab"
[16:18] <DBO> ?
[16:18] <didrocks> pitti: again, it's not a question for me :) I'm not even supposed to be aware about it…
[16:18] <pitti> DBO: except that it's not :)
[16:18] <DBO> pitti, how do you figure?
[16:18] <pitti> DBO: the key above tab is =/+ for me, and it doesn't do anythign with compiz
[16:19] <didrocks> pitti: it's in the incoming release
[16:19] <DBO> pitti, are you running trunk?
[16:19] <pitti> DBO: no, current oneiric
[16:19] <DBO> yeah you need trunk, the key detection works
[16:19] <DBO> I had several people do testing
[16:19] <DBO> you can too if you want
[16:19] <DBO> there is a test program in unity trunk you can run
[16:19] <DBO> it will tell you what the key above tab is on your layout
[16:20]  * pitti branches lp:unity
[16:20] <pitti> DBO: so no need to report all the bugs from e. g. Daviey?
[16:20] <pitti> we'll test that program from trunk instead?
[16:20] <DBO> yes just run the program
[16:21] <DBO> test-keyutil
[16:21] <DBO> in the tests directory
[16:21] <DBO> if it prints out a key that is not your key above tab
[16:21] <DBO> it failed
[16:21] <DBO> so far, it has not failed
[16:21] <pitti> ah, I guess I need to configure/make etc. first?
[16:21] <pitti> ah, no configure
[16:22] <pitti> didrocks: is there a trick how to only build tests/test-keyutil from a trunk checkout?
[16:22] <didrocks> pitti: mkdir build
[16:22] <didrocks> cd build
[16:22] <didrocks> cmake ..
[16:22] <didrocks> then, I guess cd tests && make
[16:22] <didrocks> (instead of make in the root dir)
[16:24] <desrt> arghghgh
[16:24]  * desrt spends the last two days chasing a ghost
[16:24] <DBO> pitti, sorry, didn't mean to leave you hanging
[16:24] <didrocks> DBO: did you saw that the keycode can always be 49 btw?
[16:24] <didrocks> DBO: that's why I read on some other code ;)
[16:24] <DBO> desrt, in the end, it's revealed that you are the ghost
[16:25] <didrocks> desrt: ghost window? :-)
[16:25] <desrt> DBO: i see kernel bugs?
[16:25] <DBO> desrt, I think you do
[16:25] <DBO> didrocks, what?
[16:25] <desrt> can everyone download and run a test program for me?
[16:25] <desrt> http://bugzilla-attachments.gnome.org/attachment.cgi?id=195399
[16:26] <Daviey> DBO: If you need helping testing something, please do let me know :)
[16:26] <desrt> it should print out a bunch of dots on your screen.  at some point, the dots should stop.
[16:27] <DBO> Daviey, what keyboard layout do you use?
[16:27] <didrocks> DBO: see the comment on http://git.gnome.org/browse/mutter/commit/?id=4ea00e102b6afe25e2b84f9def2f44da1b4953c6
[16:27] <DBO> desrt, it does this in a window, right?
[16:27] <desrt> DBO: it's a console program...
[16:28] <desrt> its interaction with you is limited to putchar('.'); fflush();
[16:28] <Daviey> DBO: Oddly, English (US) atm
[16:28] <Daviey> DBO: i do have an Xmodmap rebinding # to the button below Esc tho.
[16:28] <desrt> depending on your luck, the crash could happen immediately or after a thousand or so iterations
[16:28] <desrt> i've had to run it for as much as 5 minutes before
[16:29] <DBO> Daviey, do what pitti is doing
[16:29] <pitti> still building here
[16:29] <pitti> apparently cmake generates broken Makefiles which don't work with parallel building :(
[16:29] <Daviey> pitti: Are you building trunk unity for amd64?
[16:29] <pitti> Daviey: yes
[16:29] <DBO> I do -j4 constantly pitti
[16:30] <didrocks> pitti: it works with parallell building here (thanksfully)
[16:30] <Daviey> pitti: for the lazy, are you able to scp them somewhere?
[16:30] <pitti> it still seems to build the world, even when running make in tests/
[16:30] <pitti> Daviey: sure
[16:30] <didrocks> but still takes 30 minutes just for unity
[16:30] <Daviey> thanks.
[16:30] <DBO> didrocks, I am making it longer by adding more test applications
[16:30] <DBO> sorry!
[16:30] <didrocks> DBO: what, you do test? where is the snow? :)
[16:31] <pitti> Daviey: http://people.canonical.com/~pitti/tmp/test-keyutil-amd64
[16:31] <pitti> Key above Tab is grave
[16:31] <pitti> well, what I thought
[16:32] <pitti> I suppose that's based on the standard physical layout of a keyboard, not my real keyboard :)
[16:32] <pitti> but I guess I'm a bit of a special case here
[16:33] <pitti> DBO: &
[16:33] <pitti> DBO: and when I switch to German layout, it still says the same
[16:33] <DBO> pitti, what?
[16:33] <pitti> sorry, that was meant to be a ^
[16:34] <DBO> pitti, I honestly have no idea if that is right for you or not
[16:34] <pitti> DBO: anyway, Alt+` was workign for me, so I guess Daviey's output is more interesting
[16:34] <pitti> DBO: http://www.kinesis-ergo.com/images/kb_adv-pro_met720x471.jpg is my keyboard
[16:34] <DBO> pitti, okay screw that
[16:35] <didrocks> pitti: what is the keycode for reference,
[16:35] <pitti> but as there is no way to find out about the physical layout of a keyboard, I guess that's the next best thing
[16:35] <pitti> DBO: I'm not worried about my case
[16:35] <pitti> DBO: I'm worried about Daviey's
[16:35] <pitti> DBO: but it seems there is no point in reporting Daviey's bug now, when that got changed in trunk after all, right?
[16:35] <pitti> didrocks: for what?
[16:35] <didrocks> +=
[16:36] <DBO> pitti, what layout does your keyboard report itself as?
[16:36] <pitti> DBO: US
[16:36] <Daviey> pitti: sorry, before i exec this - what is it? :)
[16:36] <pitti> Daviey: don't worry, just an alias for rm -r
[16:36] <Daviey> oh good
[16:36] <pitti> Daviey: no, it just prints out a list to stdout, nothing more
[16:37] <didrocks> pitti: I meant, the keycode of the key += (the one above the Tab)
[16:37] <DBO> didrocks, his keyboard is lying to the xserver
[16:37] <DBO> clearly that wont work
[16:37]  * Daviey trusts pitti :)
[16:37] <pitti> KeyPress event, serial 36, synthetic NO, window 0x4200001,
[16:37] <pitti>     root 0xbe, subw 0x0, time 40499628, (150,16), root:(766,853),
[16:37] <pitti>     state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
[16:37] <didrocks> yeah, it won't work then :)
[16:37] <Daviey> pitti: http://pb.daviey.com/0QFc/
[16:37] <pitti> "Key above Tab is numbersign"
[16:38] <pitti> Daviey: does that sound true?
[16:38] <Daviey> pitti: blame me for that, Xmodmap.
[16:38] <DBO> so its true for you Daviey?
[16:38] <Daviey> $ cat ~/.Xmodmap
[16:38] <Daviey> keycode 49=numbersign
[16:38] <Daviey> keycode 94=dead_tilde
[16:38] <Daviey> remove Lock = Caps_Lock
[16:39] <desrt> DBO: did it crash yet?
[16:39] <Daviey> I can retest without that, if it helps test this?
[16:39] <didrocks> pitti: and for your question about discoverability, this is another way than the arrow to show the instances FYI
[16:39] <DBO> desrt, oh sorry I forgot to run it with everything else
[16:39] <desrt> s'ok :)
[16:39] <desrt> didrocks: can you test too, maybe?
[16:40] <didrocks> desrt: sure
[16:40] <DBO> desrt, didn't crash
[16:40] <DBO> but
[16:40] <DBO> stopped printing dots
[16:40] <desrt> DBO: the stopping is the crashing
[16:41] <desrt> can you give me your uname -r?
[16:41] <DBO> 3.0.0-9-generic
[16:41] <desrt> thanks
[16:41] <desrt> apt-cache policy for libc, too?
[16:41] <didrocks> desrt: same here, same kernel
[16:42] <didrocks> 2.13-17ubuntu2
[16:42] <desrt> thanks
[16:42] <DBO> desrt, same as didrocks
[16:43] <DBO> desrt, it prints a different number of dots each time if that helps
[16:43] <pitti> Daviey: would be interesting to confirm, anyway, I guess
[16:43] <desrt> DBO: it's a race... it happens by random chance
[16:43] <desrt> we're on eglibc these days, right?
[16:43] <DBO> pitti, you jelly of my key above tab code?
[16:44] <pitti> DBO: "jelly"?
[16:44] <DBO> sorry... too much reddit lately
[16:44] <DBO> you dont like the key above tab stuff?
[16:44] <pitti> DBO: my original question was debugging Daviey's issue of Alt+A, which is certainly unexpected
[16:45] <pitti> and then we found that trunk uses a different approach than what's in oneiric right now
[16:45] <pitti> so I guess the original bug is moot now
[16:45] <DBO> more or less
[16:45] <pitti> I still think Ctrl+Tab might be a little easier to document/explain/be more robust, but as long as it doesn't grab letters any more, I'm fin e:)
[16:46] <DBO> pitti, ctrl+tab is used by other applications
[16:46] <DBO> and you cant switch from alt-tab to ctrl-tab without the switcher going away
[17:05] <Daviey> pitti: http://pb.daviey.com/1Cbb/
[17:05] <Daviey> unmodified layout.
[17:09] <Daviey> (incidently, without my modified layout alt+a works again)
[17:18] <desrt> DBO, didrocks; can you try again with -static?
[17:18] <DBO> desrt, sure
[17:19] <desrt> annoyingly, static linking appears to solve the problem for me
[17:19] <DBO> same
[17:19] <desrt> which prevents me from checking old libc versions with new kernels
[17:19] <desrt> puts more weight on chances of it being a libc bug, though
[17:22] <desrt> time for a libc bug, methinks
[18:13] <kenvandine> pitti, are you still around?
[18:25] <pitti> kenvandine: again, yes (was at dinner)
[18:25] <kenvandine> pitti, nm... unping :)
[18:26] <pitti> heh
[18:28] <dbarth> Amaranth: see https://bugs.launchpad.net/nux/+bug/838693
[18:28] <ubot2`> Ubuntu bug 838693 in compiz "Add support for GL-ES" [Undecided,New]
[18:29] <Amaranth> dbarth: so the compiz changes are 59 files changed, 2330 insertions(+), 2934 deletions(-)
[18:29] <Amaranth> and that's just compiz, not even including compiz-plugins-main
[18:30] <Amaranth> yay for removing more code than added, I guess :)
[18:30] <dbarth> Amaranth: woops
[18:30] <dbarth> oh right, smspillaz mentioned the plugin rewrite you had to do
[18:30] <Amaranth> haven't rewritten any plugins yet, just ported them all
[18:31] <dbarth> well, yeah, in that case it's a significant distro-patch
[18:38]  * didrocks waves goodnight
[19:00] <DBO> its 3PM and all is quiet in the desktop team
[19:00] <pitti> it's 9 pm, and my wife gets angry :)
[19:00] <pitti> FTR, pygobject 2.90 uploaded \o/
[19:31] <pitti> good night everyone!
[19:33] <bryceh> pitti, night
[19:33] <cyphermox> night pitti
[22:33] <dupondje> Seems like network-manager-openvpn is broken
[22:33] <dupondje> it does not change default route to the vpn tunnel, even if wanted


[00:02] <vorlon> or looks like maybe this code isn't honoring no_proxy :/
[00:12] <vorlon> cjwatson: ^^ since there were no logs from your auto-sync runs I'm guessing this is what you mean by "stopped it before it did anything"; looks like the proxy has some wrong config that blocks ftp.debian.org, I've filed an RT for this
[00:58] -queuebot:#ubuntu-release- New binary: openjdk-21 [amd64] (lunar-proposed/universe) [21~1ea-1] (no packageset)
[01:04] -queuebot:#ubuntu-release- New binary: openjdk-21 [s390x] (lunar-proposed/universe) [21~1ea-1] (no packageset)
[04:14] -queuebot:#ubuntu-release- New binary: openjdk-21 [armhf] (lunar-proposed/universe) [21~1ea-1] (no packageset)
[04:52] -queuebot:#ubuntu-release- New: accepted openjdk-21 [amd64] (lunar-proposed) [21~1ea-1]
[04:52] -queuebot:#ubuntu-release- New: accepted openjdk-21 [s390x] (lunar-proposed) [21~1ea-1]
[04:52] -queuebot:#ubuntu-release- New: accepted openjdk-21 [armhf] (lunar-proposed) [21~1ea-1]
[04:52] -queuebot:#ubuntu-release- New: accepted sccache [armhf] (lunar-proposed) [0.3.3-1]
[05:31] -queuebot:#ubuntu-release- New binary: mailman-hyperkitty [amd64] (lunar-proposed/universe) [1.2.0-1] (no packageset)
[05:31] -queuebot:#ubuntu-release- New binary: ruby-vips [amd64] (lunar-proposed/universe) [2.1.4-1] (no packageset)
[07:38] -queuebot:#ubuntu-release- Unapproved: accepted libmbim [source] (jammy-proposed) [1.28.0-1~ubuntu20.04.1]
[07:49] -queuebot:#ubuntu-release- Unapproved: accepted libqmi [source] (jammy-proposed) [1.32.0-1ubuntu<IP_ADDRESS>]
[07:51] -queuebot:#ubuntu-release- Unapproved: accepted modemmanager [source] (jammy-proposed) [1.20.0-1~ubuntu22.04.1]
[07:56] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (kinetic-proposed) [5.9.3+dfsg-1ubuntu1.1]
[07:57] -queuebot:#ubuntu-release- Unapproved: accepted net-snmp [source] (jammy-proposed) [5.9.1+dfsg-1ubuntu2.3]
[08:05] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (kinetic-proposed) [<IP_ADDRESS>]
[08:15] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (kinetic-proposed) [1:43.0-1ubuntu2]
[08:16] -queuebot:#ubuntu-release- Unapproved: accepted nautilus [source] (jammy-proposed) [1:42.2-0ubuntu2]
[08:19] -queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [source] (kinetic-proposed) [2.74.3-0ubuntu1]
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted gnome-characters [source] (kinetic-proposed) [43.1-0ubuntu1]
[08:34] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (kinetic-proposed) [2.06-2ubuntu12.1]
[08:37] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (jammy-proposed) [2.06-2ubuntu7.1]
[08:48] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (jammy-proposed) [1:22.04.10]
[08:48] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (focal-proposed) [1:<IP_ADDRESS>]
[08:53] -queuebot:#ubuntu-release- Unapproved: accepted libunwind [source] (bionic-proposed) [1.2.1-8ubuntu0.1]
[08:54] -queuebot:#ubuntu-release- Unapproved: accepted libunwind [source] (focal-proposed) [1.2.1-9ubuntu0.1]
[09:02] -queuebot:#ubuntu-release- Unapproved: accepted edk2 [source] (focal-proposed) [0~20191122.bd85bf54-2ubuntu3.4]
[09:05] -queuebot:#ubuntu-release- Unapproved: mesa (jammy-proposed/main) [22.0.5-0ubuntu0.2 => 22.2.5-0ubuntu0.1~22.04.1] (core, i386-whitelist, xorg)
[09:37] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-15 [amd64] (jammy-proposed) [15.0.0-1~ubuntu<IP_ADDRESS>]
[09:37] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-15 [armhf] (jammy-proposed) [15.0.0-1~ubuntu<IP_ADDRESS>]
[09:37] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-15 [s390x] (jammy-proposed) [15.0.0-1~ubuntu<IP_ADDRESS>]
[09:37] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-15 [arm64] (jammy-proposed) [15.0.0-1~ubuntu<IP_ADDRESS>]
[09:37] -queuebot:#ubuntu-release- New: accepted spirv-llvm-translator-15 [ppc64el] (jammy-proposed) [15.0.0-1~ubuntu<IP_ADDRESS>]
[09:44] -queuebot:#ubuntu-release- Unapproved: rejected libdrm [source] (jammy-proposed) [2.4.113-2~ubuntu<IP_ADDRESS>]
[09:47] -queuebot:#ubuntu-release- Unapproved: accepted libdrm [source] (jammy-proposed) [2.4.113-2~ubuntu<IP_ADDRESS>]
[10:39] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-15 [s390x] (kinetic-proposed/universe) [15.0.0-1~ubuntu<IP_ADDRESS>] (no packageset)
[10:48] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-15 [ppc64el] (kinetic-proposed/universe) [15.0.0-1~ubuntu<IP_ADDRESS>] (no packageset)
[10:50] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-15 [arm64] (kinetic-proposed/universe) [15.0.0-1~ubuntu<IP_ADDRESS>] (no packageset)
[10:50] -queuebot:#ubuntu-release- New binary: spirv-llvm-translator-15 [armhf] (kinetic-proposed/universe) [15.0.0-1~ubuntu<IP_ADDRESS>] (no packageset)
[11:19] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi (kinetic-proposed/restricted) [6-0ubuntu4 => 8-0ubuntu1~22.10] (raspi)
[11:23] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi (jammy-proposed/restricted) [6-0ubuntu3 => 8-0ubuntu1~22.04] (raspi)
[11:35] -queuebot:#ubuntu-release- Unapproved: dotnet6 (kinetic-proposed/universe) [6.0.112-0ubuntu1~22.10.1 => 6.0.112-0ubuntu1~22.10.2] (no packageset)
[11:41] -queuebot:#ubuntu-release- Unapproved: accepted dotnet6 [source] (kinetic-proposed) [6.0.112-0ubuntu1~22.10.2]
[12:24] <cjwatson> vorlon: Yeah, I stopped before that point.  Note that you can poke at the proxy configs yourself to some extent, lp:canonical-is-internal-proxy-configs
[13:20] -queuebot:#ubuntu-release- New binary: poppler [amd64] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[13:21] -queuebot:#ubuntu-release- New binary: poppler [s390x] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[13:22] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[13:29] -queuebot:#ubuntu-release- New binary: poppler [armhf] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[13:31] -queuebot:#ubuntu-release- New binary: poppler [arm64] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[14:05] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (bionic-proposed) [<IP_ADDRESS>]
[14:08] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (jammy-proposed) [<IP_ADDRESS>]
[14:09] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (focal-proposed) [<IP_ADDRESS>]
[14:27] -queuebot:#ubuntu-release- New binary: poppler [riscv64] (lunar-proposed/main) [22.12.0-1] (desktop-core, i386-whitelist, ubuntu-server)
[14:36] <LocutusOfBorg> bryceh, hello, I see you are merger of nginx... Its under my name now, because of my perl rebuild, please take care of it :D
[14:54] <LocutusOfBorg>  atf-sh | 0.21-6build2 | lunar/universe   | amd64, arm64, armhf, ppc64el, riscv64, s390x
[14:54] <LocutusOfBorg> who did remove it again on i386?
[14:56] <LocutusOfBorg> oh... atf-sh is not in the set
[15:10] -queuebot:#ubuntu-release- New: accepted mailman-hyperkitty [amd64] (lunar-proposed) [1.2.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [arm64] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [ppc64el] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [s390x] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [amd64] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [riscv64] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted poppler [armhf] (lunar-proposed) [22.12.0-1]
[15:10] -queuebot:#ubuntu-release- New: accepted ruby-vips [amd64] (lunar-proposed) [2.1.4-1]
[15:38] -queuebot:#ubuntu-release- New binary: poppler [i386] (lunar-proposed/main) [22.12.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[15:40] -queuebot:#ubuntu-release- New binary: poppler [amd64] (lunar-proposed/main) [22.12.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[15:41] -queuebot:#ubuntu-release- New binary: poppler [s390x] (lunar-proposed/main) [22.12.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[15:42] -queuebot:#ubuntu-release- New binary: poppler [ppc64el] (lunar-proposed/main) [22.12.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[15:48] -queuebot:#ubuntu-release- New binary: poppler [armhf] (lunar-proposed/main) [22.12.0-1ubuntu1] (desktop-core, i386-whitelist, ubuntu-server)
[16:29] <athos> Hi, ubuntu-archive! Could any archive admin please take a look at LP: #1931913 and LP: #1931315?
[16:29] -ubottu:#ubuntu-release- Launchpad bug 1931913 in php-slim (Ubuntu) "Please drop shaarli (and associated components) from impish" [Undecided, New] https://launchpad.net/bugs/1931913
[16:29] -ubottu:#ubuntu-release- Launchpad bug 1931315 in php-laravel-framework (Ubuntu) "Please drop php-laravel-framework (and movim and other associated components)" [Undecided, New] https://launchpad.net/bugs/1931315
[16:30] <athos> these are about remobing php-slim and php-laravel-lumen-framework from lunar-proposed
[17:05] <jbicha> bdmurray: could you copy gjs/jammy, mozjs102/jammy mozjs102/kinetic from the security-proposed PPA to -proposed as requested at bug 1993214 ?
[17:05] -ubottu:#ubuntu-release- Bug 1993214 in mozjs102 (Ubuntu) "[jammy] Update gjs to 1.74 using mozjs102 102.3" [Undecided, Confirmed] https://launchpad.net/bugs/1993214
[17:05] <jbicha> oh, you're not an AA but maybe you have permissions?
[17:11] <bdmurray> jbicha: I don't think I have the permissions for that
[17:16] <jbicha> bdmurray: do I need someone who is both SRU + AA to do that?
[17:24] -queuebot:#ubuntu-release- New binary: designate-tlds [amd64] (lunar-proposed/none) [0.1.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: git-delete-merged-branches [amd64] (lunar-proposed/none) [7.3.1-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: golang-github-mdlayher-packet [amd64] (lunar-proposed/none) [1.1.0-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: python-littleutils [amd64] (lunar-proposed/none) [0.2.2-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: sphinxcontrib-ditaa [amd64] (lunar-proposed/none) [1.0.1-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: git-credential-oauth [amd64] (lunar-proposed/none) [0.1.5-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: jupyter-comm [amd64] (lunar-proposed/none) [0.1.2-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: sway-notification-center [amd64] (lunar-proposed/none) [0.7.2-1] (no packageset)
[17:24] <vorlon> jbicha: no, anyone with upload rights who can also read the security-proposed ppa can issue a copy-package command
[17:24] -queuebot:#ubuntu-release- New binary: golang-github-achannarasappa-term-grid [amd64] (lunar-proposed/none) [0.2.4-2] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: rust-fehler [amd64] (lunar-proposed/none) [1.0.0-1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New: accepted designate-tlds [amd64] (lunar-proposed) [0.1.0-1]
[17:24] -queuebot:#ubuntu-release- New: accepted git-delete-merged-branches [amd64] (lunar-proposed) [7.3.1-2]
[17:24] -queuebot:#ubuntu-release- New: accepted rust-fehler [amd64] (lunar-proposed) [1.0.0-1]
[17:24] -queuebot:#ubuntu-release- New: accepted sway-notification-center [amd64] (lunar-proposed) [0.7.2-1]
[17:24] -queuebot:#ubuntu-release- New: accepted git-credential-oauth [amd64] (lunar-proposed) [0.1.5-2]
[17:24] -queuebot:#ubuntu-release- New: accepted sphinxcontrib-ditaa [amd64] (lunar-proposed) [1.0.1-1]
[17:24] -queuebot:#ubuntu-release- New: accepted golang-github-achannarasappa-term-grid [amd64] (lunar-proposed) [0.2.4-2]
[17:24] -queuebot:#ubuntu-release- New: accepted golang-github-mdlayher-packet [amd64] (lunar-proposed) [1.1.0-2]
[17:24] -queuebot:#ubuntu-release- New: accepted python-littleutils [amd64] (lunar-proposed) [0.2.2-2]
[17:24] -queuebot:#ubuntu-release- New binary: rust-fehler [ppc64el] (lunar-proposed/universe) [1.0.0-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New: accepted jupyter-comm [amd64] (lunar-proposed) [0.1.2-2]
[17:25] -queuebot:#ubuntu-release- New binary: git-credential-oauth [arm64] (lunar-proposed/universe) [0.1.5-2] (no packageset)
[17:25] -queuebot:#ubuntu-release- New: accepted git-credential-oauth [arm64] (lunar-proposed) [0.1.5-2]
[17:25] -queuebot:#ubuntu-release- New: accepted rust-fehler [ppc64el] (lunar-proposed) [1.0.0-1]
[17:25] -queuebot:#ubuntu-release- New binary: git-credential-oauth [armhf] (lunar-proposed/universe) [0.1.5-2] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: git-credential-oauth [s390x] (lunar-proposed/universe) [0.1.5-2] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: sway-notification-center [armhf] (lunar-proposed/universe) [0.7.2-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: git-credential-oauth [ppc64el] (lunar-proposed/universe) [0.1.5-2] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: sway-notification-center [ppc64el] (lunar-proposed/universe) [0.7.2-1] (no packageset)
[17:26] -queuebot:#ubuntu-release- New binary: sway-notification-center [arm64] (lunar-proposed/universe) [0.7.2-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: rust-fehler [armhf] (lunar-proposed/universe) [1.0.0-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: rust-fehler [arm64] (lunar-proposed/universe) [1.0.0-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- Unapproved: mozjs102 (kinetic-proposed/main) [102.3.0-1 => 102.6.0-0ubuntu<IP_ADDRESS>] (i386-whitelist) (sync)
[17:28] -queuebot:#ubuntu-release- New sync: mozjs102 (jammy-proposed/primary) [102.6.0-0ubuntu<IP_ADDRESS>]
[17:29] -queuebot:#ubuntu-release- New binary: freefilesync [amd64] (lunar-proposed/universe) [11.26-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- Unapproved: gjs (jammy-proposed/main) [1.72.2-0ubuntu1 => 1.74.0-0ubuntu1] (desktop-core, desktop-extra, i386-whitelist, mozilla) (sync)
[17:30] <jbicha> vorlon: I ran the copy commands. I want mozjs102 (NEW) to go into jammy main so I think I need an AA for that part
[17:32] -queuebot:#ubuntu-release- New binary: freefilesync [ppc64el] (lunar-proposed/universe) [11.26-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: freefilesync [arm64] (lunar-proposed/universe) [11.26-1] (no packageset)
[17:35] <vorlon> jbicha: yes
[17:36] -queuebot:#ubuntu-release- New binary: dials [amd64] (lunar-proposed/universe) [3.12.1+dfsg3-2] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: rust-fehler [riscv64] (lunar-proposed/universe) [1.0.0-1] (no packageset)
[17:39] -queuebot:#ubuntu-release- New: accepted dials [amd64] (lunar-proposed) [3.12.1+dfsg3-2]
[17:39] -queuebot:#ubuntu-release- New: accepted freefilesync [arm64] (lunar-proposed) [11.26-1]
[17:39] -queuebot:#ubuntu-release- New: accepted git-credential-oauth [s390x] (lunar-proposed) [0.1.5-2]
[17:39] -queuebot:#ubuntu-release- New: accepted rust-fehler [armhf] (lunar-proposed) [1.0.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted sway-notification-center [arm64] (lunar-proposed) [0.7.2-1]
[17:39] -queuebot:#ubuntu-release- New: accepted sway-notification-center [ppc64el] (lunar-proposed) [0.7.2-1]
[17:39] -queuebot:#ubuntu-release- New: accepted freefilesync [amd64] (lunar-proposed) [11.26-1]
[17:39] -queuebot:#ubuntu-release- New: accepted rust-fehler [arm64] (lunar-proposed) [1.0.0-1]
[17:39] -queuebot:#ubuntu-release- New: accepted sway-notification-center [armhf] (lunar-proposed) [0.7.2-1]
[17:39] -queuebot:#ubuntu-release- New: accepted freefilesync [ppc64el] (lunar-proposed) [11.26-1]
[17:39] -queuebot:#ubuntu-release- New: accepted rust-fehler [riscv64] (lunar-proposed) [1.0.0-1]
[17:40] -queuebot:#ubuntu-release- New: accepted git-credential-oauth [armhf] (lunar-proposed) [0.1.5-2]
[17:40] -queuebot:#ubuntu-release- New: accepted git-credential-oauth [ppc64el] (lunar-proposed) [0.1.5-2]
[17:41] -queuebot:#ubuntu-release- New binary: dials [ppc64el] (lunar-proposed/universe) [3.12.1+dfsg3-2] (no packageset)
[17:42] -queuebot:#ubuntu-release- New binary: git-credential-oauth [riscv64] (lunar-proposed/universe) [0.1.5-2] (no packageset)
[21:06] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[21:13] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [<IP_ADDRESS> => <IP_ADDRESS>] (ubuntu-desktop, ubuntu-server)
[21:14] -queuebot:#ubuntu-release- Unapproved: rejected update-notifier [source] (bionic-proposed) [<IP_ADDRESS>]
[21:18] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (bionic-proposed) [<IP_ADDRESS>]
[21:20] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.18]


[17:33] <redwolf> o/
[17:34] <redwolf> krytarik, are you happy now? :)
[17:34] <tsimonq2> o/
[17:34] <krytarik> redwolf: Yep, rather - thanks. :)
[17:35] <redwolf> :D
[17:35] <redwolf> you got merged!
[17:35] <krytarik> redwolf: He didn't notice that I forgot to put a '#' in front of the bug report number, that is. :P
[17:35] <redwolf> :)
[17:37] <krytarik> And he doesn't seem to have used the '--fixes' option on committing it either - which leaves the bug status unchanged.
[17:37] <redwolf> yes
[17:38] <krytarik> Otoh, now I know why so many bug reports are still open while they are actually fixed. :P
[17:38] <krytarik> (Happened with ianorlin's one too.)
[17:38] <krytarik> Anyway, like I said, 'rather'. :)
[17:44] <krytarik> redwolf: Btw, do you know if gilir works on releasing it for 15.10 still?
[17:44] <redwolf> O.o
[17:44] <redwolf> LXQt you mean?
[17:44] <krytarik> Nope, the updated default settings.
[17:45] <krytarik> And hah! :D
[17:45] <redwolf> lol
[17:45] <redwolf> I think so, let me check the version numbers, but I think it's in.
[17:47] <krytarik> https://launchpad.net/ubuntu/+source/lubuntu-default-settings - for reference.
[17:51] <redwolf> ta
[17:55] <redwolf> krytarik, the prior version was 0.43
[17:55] <redwolf> it seems the beta 2 has 0.44 so yes
[18:00] <krytarik> redwolf: That's the one in the Daily PPA though.
[18:04] <redwolf> yes, I'm not really sure. I'm in lazy mode again to check the branches now :D
[18:04] <redwolf> but I think so, like my last modifications, very very close to UI Freeze but they're in


 Does anyone know how to pentest Cisco VPN?
 what vpn standard?
 I'm sorry for your loss, @KMyers
 Don't be
 Hey whos going to the Southeast Linux Festival June 9-11?
 @KMyers for one
 Yup, I still have a free seat
 your time table excludes me
 oh man, debugging PHP is awesome with xdebug.  I never knew you could do that!
 so not be going
 *might
 Linode is going to be there, i hope i can get some free Linux VPS servers! haha i wish.
 <3 linode
 someone please test this and tell me if you can detect any lag? https://risk.adamoutler.com/index2.php
 just play with the controls
 I'm asking because it's sending a lot of data and performing calculations on each keystroke to update the entire box on the right.
 @KMyers that's my comcast over wifi
 I usually use QOS on my router and keep my speed well below that.
 so that during netflix or something, there's plenty of speed to go around without noticing issues


[01:00] <slangasek> blkperl: ah, lost track of that, sorry - let's see
[01:03] <slangasek> blkperl: note that triaging the bug doesn't guarantee anyone is going to work on it
[01:18] <blkperl> slangasek: thanks, i know but triaged gives at little more visibility
[01:18] <blkperl> so hopefully it will get some more attention
[01:20] <bkerensa> Ok ladies and gents :) nathwill_afk will be your captain... I am grabbing a zipcar and going for a trip :) seeya sunday
[02:00] <nathwill> and suddenly we're without a captain
[17:30] <bkerensa> ;p
[18:51] <bkerensa> oh there is the captain nathwill
[18:51] <bkerensa> :D
[18:53] <bkerensa> nathwill: you going to use prezi tomorrow?
[19:07] <tgm4883> bkerensa, apparently you offended him
[19:07] <bkerensa> tgm4883: it happens ;p
[19:08] <tgm4883> so what are the happenings for tomorrow?
[19:18] <bkerensa> tgm4883: :P we will be having beer
[19:18] <bkerensa> ^
[19:24] <bkerensa> tgm4883: we will be doing upgrades/installs/socializing
[19:24] <bkerensa> nathwill will give a review of our work as a LoCo in 12.04 and what our plans are for 12.10
[19:24] <tgm4883> we have 12.10 plans?
[19:24] <bkerensa> there will be music... maybe dancing.... and beer... and for those brave enough pac man afterwards
[19:25] <bkerensa> tgm4883: We have ideas that will likely roll into plans but yes
[19:25] <tgm4883> any sweet demos?
[19:25] <bkerensa> nathwill is going to be doing some new stuff in the next cycle to help grow us and I will be to
[19:26] <bkerensa> tgm4883: I am not totally sure on the content of nathwills presentation :) I just know he has been working on it since yesterday
[19:26] <bkerensa> he hopes to use it in his application for membership so I expect it will be quality
[19:26] <bkerensa> tgm4883: if your interested you could demo Ubuntu TV?
[19:27] <bkerensa> we will have a projector on-site and you could grab the ppa
[19:27] <bkerensa> :D
[19:27] <bkerensa> if not I will likely have it available on a laptop
[19:27] <bkerensa> tgm4883: oh and there will be a giveaway :)
[19:28] <tgm4883> I don't think there will be much available to demo for Ubuntu TV
[19:28] <bkerensa> tgm4883: just the lenses mostly
[19:28] <tgm4883> yea
[19:28] <bkerensa> we could possibly show people how HUD works and also there is this good comparison video of Gnome3 vs. Unity with HUD
[19:29] <tgm4883> I could demo my mythtv lens, but I'd have to bring a bit of a setup to do so
[19:30] <tgm4883> err, s/lens/scope/
[19:30] <tgm4883> It's more likely I'll just be working on it though
[19:33] <bkerensa> tgm4883:  and just in I will also be giving away to copies of the newest Ubuntu Book which will ship to winners in June
[19:33] <bkerensa> :D
[19:33] <bkerensa> tgm4883: you should demo it
[19:33] <bkerensa> :D
[19:34] <bkerensa> I know nothing about mythbuntu
[19:34] <tgm4883> hmm
[19:34] <tgm4883> I'll think about it
[19:34] <tgm4883> I'd likely just bring a VBox VM and need some hardware to run it on
[19:39] <bkerensa> tgm4883: well Ubuntu Oregon has a "LoCo" owned Laptop
[19:40] <bkerensa> hopefully in the future here we will also have a 1U server for events and demos and then also a HD tv for booth etc
[19:40] <bkerensa> or even a monitor
[19:45] <bkerensa> bbl
[21:55] <blkperl> bkerensa: do you have raw stats on ubuntu oregons impact?
[21:56] <blkperl> it would be cool if we could associate ourselves on launchpad with Ubuntu Oregon and then datamine it
[22:59] <bkerensa> blkperl: I do not its hard to aggregate such data right now but we had discussed tagging any bugs we work on with something like "ORLOCO"
[22:59] <bkerensa> that way we could actually put together more solid stats
[22:59] <bkerensa> blkperl: I needed to talk to you btw
[22:59] <bkerensa> :)
[23:07] <blkperl> bkerensa: ok pm? or tomorrow?
[23:07] <bkerensa> blkperl: nvm :) tomorrow
[23:08] <bkerensa> nathwill: so I talked to mythmon and he works at OSL's noc
[23:08] <bkerensa> he said open a ticket but it should be "fine"
[23:08] <bkerensa> we just need to get clearance from the main guy :)
[23:08] <bkerensa> then we can deliver the server and bring it online :P
[23:16] <nathwill> sweeet
[23:17] <bkerensa> nathwill: I went in today to "see what they had"
[23:18] <bkerensa> and they pointed to a full cabinet
[23:18] <bkerensa> and were like "which one do you like"
[23:18] <bkerensa> :D
[23:18] <bkerensa> ticket is now in with OSU OSL for Colocation... Now we just need two SATA's
[23:19] <bkerensa> nathwill: blkperl was wondering if we have any raw stats about Ubuntu Oregon's impact.... we should work on that
[23:19] <bkerensa> maybe a wiki page?
[23:28] <nathwill> bkerensa, yeah, we should put together some page to track things
[23:28] <nathwill> one thing we need to start doing is making sure to register all activities on loco.ubuntu.com
[23:29] <nathwill> that way people can subscribe to activities, and we can do later analysis on activity levels, etc.
[23:29] <nathwill> :D
[23:29] <nathwill> we need to return the favor and see what ways free geek could use our help
[23:29] <nathwill> let them pick an area they're short on assistance, and we'll rally some support
[23:32] <bkerensa> https://wiki.ubuntu.com/OregonTeam/Statistics
[23:32] <bkerensa> nathwill: I already volunteered you :P
[23:33] <nathwill> bkerensa, that's good, i love numbers :D
[23:33] <bkerensa> nathwill: I told Darren who is their Edu Coordinator that when I return from UDS that you and I would be in touch to see about teaching some classes
[23:33]  * bkerensa was going to offer a bash scripting class and perhaps Juju class
[23:33] <nathwill> bkerensa: tomorrow, let's chat about some ways we can measure impact
[23:33] <nathwill> and dude, i'd be super interested in that
[23:33] <bkerensa> nathwill: indeed we need to improve our processes
[23:34] <bkerensa> nathwill: yeah... they have wanted me/us to teach classes but this winter was not a fun time to trek to FG all the time
[23:34] <bkerensa> :D
[23:34] <nathwill> bkerensa: FG?
[23:34] <bkerensa> FreeGeek
[23:34] <bkerensa> :D
[23:35] <nathwill> aha
[23:39] <bkerensa> slangasek: with this new box we could use it for packaging
[23:39] <bkerensa> so if we do a joint BSP/Jam we wont have to utilize AWS
[23:41] <slangasek> bkerensa: are you going to be running VMs on the box?
[23:41] <bkerensa> slangasek: thats the plan
[23:41] <slangasek> cool
[23:41] <bkerensa> so we can isolate resources for more then one thing
[23:42] <bkerensa> slangasek: I  just put a ticket in with OSL but I ran it by them and it doesnt seem like colo is going to be a issue
[23:42] <bkerensa> I informed them that the box would also be available to Debian PDX folk to further Debian projects locally


[12:21] <geser> bdrung: was the only reason you changed the lp: #xxx in debian/changelog to LP to look equal to the other entries? (u-d-t commit 874)
[12:21] <bdrung> geser: yes
[12:27] <bdrung> geser: should i setup a daily build of ubuntu-dev-tools?
[12:28] <bdrung> tumbleweed: ^
[12:40] <tumbleweed> bdrung: yeah why not (now that we have a test suiet, that'd be great)
[12:40] <bdrung> tumbleweed: the question is where who should own the PPA?
[12:41] <bdrung> tumbleweed: ubuntu-dev?
[12:41] <tumbleweed> that doesn't sound ideal. I have no problem with you owning it, otherwise a dedicated team?
[12:42] <bdrung> tumbleweed: didicated team? proposals?
[12:43] <tumbleweed> udt-dailies / udt-developers
[12:44] <find> do u know what can i join ubuntu term?
[12:46] <ari-tczew> find: join what?
[12:48] <find> translate
[12:55] <dpm> find, which language do you want to translate into?
[12:55] <dpm> you can find the team for your language here:
[12:55] <dpm> https://translations.launchpad.net/+groups/ubuntu-translators
[12:56] <tumbleweed> dpm: whois suggests china. find: https://wiki.ubuntu.com/Translations/Contact/Teams (#ubuntu-cn-translators?)
[12:56] <dpm> ubuntu-l10n-zh-cn
[12:56] <find> OK,i go to see it,thank u very much
[12:57] <dpm> find, np, you can go to https://launchpad.net/~ubuntu-l10n-zh-cn and you'll find how to contact them there
[13:00] <bdrung> tumbleweed: {debupstream}~~bzr{revno} as debian version?
[13:00] <tumbleweed> ~~ seems overkill but fine.
[13:01] <find> i am find it already,thank u very much
[13:02] <bdrung> tumbleweed: it should be lower than {debupstream}~maverick and {debupstream}~ppa
[13:02] <bdrung> ok, changing to one ~
[13:03] <tumbleweed> I tend to use ~daily+bzr{revno}
[13:03] <bdrung> tumbleweed: let's see if it works: https://code.edge.launchpad.net/~udt-developers/+recipe/daily
[13:04] <bdrung> tumbleweed: that's even better
[13:09] <happyaron> Should I file sync request when Debian has a new version of a package?
[13:10] <Laney> it will be autosynced if the package is a) not modified in Ubuntu and b) has been uploaded to unstable
[13:10] <Laney> otherwise yes sync if it can and should be synced
[13:11] <coolbhavi> happyaron, yes but make sure you follow https://wiki.ubuntu.com/SyncRequestProcess
[13:11] <happyaron> thank you, :)
[13:46] <sagaci> so if one wanted to get a new package into ubuntu, the most sensible way (in the majority of cases) is to go through Debian, right?
[13:47] <sagaci> and ubuntu packaging is mostly maintaining stuff rather than introducing new packages, in a nutshell
[13:49] <Laney> yes that is fair to say
[13:50] <sagaci> thanks, trying to get my head around some of it
[13:51] <happyaron> AFAIK, debian ftp-master says they won't accept new package from NEW before squeeze is out.
[13:51] <Laney> not true
[13:52] <happyaron> they randomly accept some packages, but no guarantee.
[13:53] <Laney> there are never guarantees, but i have asked for several packages to be accepted and they always have
[14:40] <bdrung> tumbleweed: shouldn't ubuntutools/test/test_help.py be in ubuntutools/test_help.py?
[14:42] <bdrung> tumbleweed: why should we add 'a1' to the version number if the target is UNRELEASED?
[14:43] <bdrung> tumbleweed: http://paste.debian.net/103007/
[14:48] <tumbleweed> bdrung: you could say that about all te test suites. a1 is like ~1 in python terms. Aah nice. BTW if you run it with python2.7 it'll tell you when it's skipping things.
[14:50] <bdrung> tumbleweed: you still don't explain why you add 'a1'? why should the version modified?
[14:52] <tumbleweed> off-topic for that branch, I just saw that code and thought, if we are determining the version from the changelog, we should differentiate prereleases. Doesn't really matter at all, though.
[14:54] <bdrung> tumbleweed: i am against this change. the daily will have an other version anyway
[14:56] <tumbleweed> bdrung: reverted
[14:58] <bdrung> tumbleweed: get-build-deps runs sudo
[14:58] <tumbleweed> as do a few others
[14:59] <bdrung> tumbleweed: that let's the test fail and shouldn't be for --help
[15:00] <tumbleweed> yes. I've blacklisted most of the others, I'll sort it out now.
[15:06] <surfzoid> Hi folk
[15:06] <surfzoid> is "grub-reboot" have an GUI/FE ?
[15:07] <surfzoid> because i just finish to wrote one :-) http://surfzoid.free.fr/freevbsoft/RebootInFE/
[15:14] <aboudreault> hi, is Karmic still supported for security updates?
[15:18] <bdrung> aboudreault: yes
[15:18] <aboudreault> it's 2 years the non-lts support?
[15:19] <ebroder> 18 months
[15:19] <aboudreault> I see
[15:20] <aboudreault> thanks
[15:53] <bdrung> tumbleweed: 404main: sys.exit(0) only if sys.argv[1] in ('help', '-h', '--help')
[15:53] <bdrung> merge-changelog:sys.exit(0) -> sys.exit(exit)
[16:16] <lostern> What are the environment variables that are used to search include and lib dirs?
[16:19] <lostern> Never mind, I should have looked in the gcc man page first.
[16:20] <RoAkSoAx> dude!! /win 3
[16:21] <RoAkSoAx> lol
[16:55] <hakermania1> 199 people in room :)
[16:58] <bdrung> hakermania1: and 299 in #ubuntu-dev
[16:59] <bdrung> #ubuntu-devel
[17:00] <hakermania1> bdrung: Haha, coincidence :)
[17:01] <udienz> Dang.. my bad.. i've uploaded dsc reather than debdiff :)
[17:02] <coolbhavi> udienz, saw that this morning :)
[17:02] <bdrung> tumbleweed: please let me know once one of your two branches is ready for merge
[17:03] <udienz> coolbhavi, hehehe, i'm so sleepy this day.. and also my connections is very bad
[17:04] <coolbhavi> udienz, :)
[17:05]  * udienz uploading now
[17:05] <udienz> bug 692457
[17:07] <ebroder> apw: --verbose
[17:07] <bdrung> udienz: you could drop ".dcs" from the debdiff name next time
[17:10] <udienz> bdrung, ok, my bad.. :) i was very confused this day, last "dsc" files uploaded 5 times transfered to lp with 3kbps :(
[17:10] <udienz> all errors
[17:12] <hakermania1> udienz: You take several errors: http://revu.ubuntuwire.com/p/ttf-indonesian Why you let it like this and you don't correct them?
[17:12] <udienz> hakermania1, license problem.
[17:13] <udienz> upstream author doesn't reply my emails
[17:13] <hakermania1> udienz: :/
[17:15] <udienz> hakermania1, how about your package?
[17:15] <hakermania1> udienz: Waiting for 3rd review :)) No errors at all :)
[17:23] <bdrung> udienz: you should subscribe ubuntu-sponsors again.
[17:24] <udienz> bdrung, Done
[17:31] <tumbleweed> bdrung: thanks, btw you changed indentation of line 117 of 404main during the tab -> space conversion. I guess I'd better look for more of those
[17:34] <bdrung> tumbleweed: thanks for detecting
[17:34] <tumbleweed> code after an exit() is suspicious :P
[17:35] <bdrung> tumbleweed: fix pushed
[17:37] <bdrung> tumbleweed: can you get your config-681693 branch ready for merge?
[17:41] <tumbleweed> bdrung: looking at it. test-help should be mergeable, waiting for your ACK
[17:42] <bdrung> tumbleweed: merge-changelog:sys.exit(0) -> sys.exit(exit)
[17:42] <tumbleweed> add-patch needs manpage, setup.py + copyright entries, and a BLACKLIST entry
[17:43] <bdrung> tumbleweed: tell that mvo
[17:43] <tumbleweed> thanks
[17:44] <bdrung> tumbleweed: can setup.py create symlinks?
[17:45] <tumbleweed> well, it's python, it can do anything. Don't know of any distribute mechanism for doing them though.
[17:46] <ari-tczew> could someone look on bug 540514 ? I really don't understand what's the problem
[17:47] <bdrung> ari-tczew: you can ask for build log or the malformed control file
[17:48] <coolbhavi> bdrung, +1 and isnt the original maintainer field in source stanza?
[17:49] <ari-tczew> bdrung: why? Version: 2.4.8-2ubuntu1
[17:58] <tumbleweed> bdrung: I pushed a fix. config-681693 looks ok to me. There's also import-bfd-681693 (the beginning of one branch per script)
[18:00] <bdrung> tumbleweed: pushed?
[18:00] <tumbleweed> bdrung: test-help r886
[18:01] <bdrung> k, got it now
[18:09] <bdrung> tumbleweed: merged (not yet pushed)
[18:10] <tumbleweed> thanks. I'll be picking away at more scripts
[18:20] <bdrung> tumbleweed: pushed
[18:21] <tumbleweed> bdrung: aah, thanks. I forgot about the related BD changes
[18:23] <bdrung> tumbleweed: re config branch: my three points are still open: 1) what speaks against using Logging.warning instead of printf?
[18:24] <tumbleweed> bdrung: oh, didn't push r914, pushed.
[18:27] <bdrung> tumbleweed: you use logger instead of ubuntutools.logger
[18:29] <bdrung> tumbleweed: can we please use only one?
[18:29] <tumbleweed> now I understand the confusion last night, I thought you meant logging :P
[18:29] <bdrung> tumbleweed: i failed in configuring logging to look like  ubuntutools.logger
[18:31] <tumbleweed> yeah no need to build of logging if it's more complex than reinventing it
[19:16] <bdrung> tumbleweed: so you can throw logging out again and use ubuntutools.logger
[19:16] <bdrung> (which doesn't require to be initialised)
[19:17] <tumbleweed> bdrung: yeah I'm busy with it
[19:17] <bdrung> tumbleweed: btw, our daily build is up and running: https://code.edge.launchpad.net/~udt-developers/+archive/daily
[19:25] <tumbleweed> bdrung: ok, there we are (r916). BTW I looked at add-patch, it's not ready to be install (breaks with quilt, haven't tried anything else). I'll prod mvo when he turns up
[19:29] <ari-tczew> could anyone look on changes in https://launchpad.net/ubuntu/+source/libhdhomerun/20100828-0ubuntu1
[19:29] <ari-tczew> for me it looks like horrible bad sponsorship
[19:30] <ari-tczew> d/copyright changed, lack of mention in d/changelog
[19:33] <tumbleweed> ari-tczew: looks like it went from an ubuntu-only package to a debian sync, and back to the ubuntu one
[19:33] <ebroder> Probably means the sync was wrong
[19:34] <ari-tczew> omg...
[19:34]  * ari-tczew guess that procedures and policies are only for community, not stricte Canonical developers.
[19:35] <ari-tczew> tumbleweed, ebroder: what's next with that package? merge is available.
[19:36] <tumbleweed> ari-tczew: if the fork is intended to be permanent, it should be sync black-listed.
[19:37] <ari-tczew> I see very good flow of information...
[19:40] <ebroder> ari-tczew: It looks like superm1 is the primary maintainer for that package. Which makes sense since he does a lot of Mythbuntu stuff. Maybe you should try to get in touch with him since he seems to have fairly clear intentions around the package
[20:36] <bdrung> tumbleweed: merged and pushed
[20:38] <tumbleweed> bdrung: two more scripts in separet branches, I'll do a couple more now.
[20:41] <bdrung> tumbleweed: these tools needs to be converted to PEP8: requestsync, ubuntu-build, ubuntutools/lp/udtexceptions.py, ubuntutools/requestsync/*.py - do you want to do it?
[20:41] <bdrung> tumbleweed: pushed again
[20:46] <tumbleweed> ack-sync looks good. OK I'll convert those.
[20:47] <bdrung> tumbleweed: you can do it directly in trunk
[20:50] <bdrung> tumbleweed: BACKPORTPACKAGE_LPINSTANCE in import-bfd branch
[20:56] <tumbleweed> the cost of getting distracted
[20:57] <tumbleweed> both pushed
[20:59] <bdrung> tumbleweed: merged import-bfd
[21:03] <bdrung> tumbleweed: the indentation of optParser should be improved (lp-set-dup)
[21:03] <tumbleweed> bdrung: the alternative is to split long strings (line length)
[21:04] <bdrung> tumbleweed: what do you prefer?
[21:06] <tumbleweed> bdrung: I change style as appropriate (also see the heavily-indented bits of the config-parsing code.
[21:11] <bdrung> tumbleweed: the lines are too long even with the short indentation.
[21:12] <bdrung> tumbleweed: the scripts need PEP8 conversion
[21:15] <tumbleweed> bdrung: can you clarify both of those? Which lines, which scripts?
[21:15] <bdrung> tumbleweed: the script you where you converted tabs to spaces
[21:15] <bdrung> http://www.python.org/dev/peps/pep-0008/
[21:16] <bdrung> tumbleweed: see Maximum Line Length example
[21:16] <tumbleweed> bdrung: yes, my editor is configured to highlight long lines. I just did a pure tab-to-space conversion.
[21:17] <tumbleweed> I decided to tidy them up in a second pass
[21:18] <bdrung> tumbleweed: k, that's a good idea (too see the tidy process)
[21:56] <hakermania> if any reviewer has time please take a look at wallch at REVU thx in advance! http://revu.ubuntuwire.com/p/wallch
[22:00] <superm1> ari-tczew, afaik everything should be documented in bzr for changes
[22:05] <bdrung> tumbleweed: pushed
[22:06] <bdrung> tumbleweed: "debian_srcpkg = ubuntutools.requestsync.mail.getDebianSrcPkg" -> wrong indented
[22:08] <tumbleweed> bdrung: least bad option
[22:09] <tumbleweed> pylint can drive you mad btw, it always complains about *something* :)
[22:13] <bdrung> tumbleweed: i know. i fix only some of the complains
[22:39] <bcurtiswx> would someone be able to explain this error to me? src/Makefile.am: object `empathy-accounts-dialog.$(OBJEXT)' created both with libtool and without
[23:00] <bdrung> tumbleweed: merged lp-set-dup-681693
[23:08] <RAOF> bcurtiswx: I've not seen that error before, but it *looks* like you've got a rule which generates empathy-accounts-dialog.(o? so?), which libtool will also be generating, and it's complaining.
[23:09] <bdrung> tumbleweed: should i move libapt-pkg-perl, libwww-perl, python-magic, python-soappy from recommends to depends?
[23:09] <RAOF> I'd guess therefore that something is defining a rule for empathy-accounts-dialog.so, since that's what libtool should be generating.
[23:10] <bcurtiswx> RAOF, hmm, weird, because one of my patches requests a function from it and doesn't see it, so i added it to recognize it
[23:11] <RAOF> bcurtiswx: Care to pastebin the Makefile.am?
[23:11] <bcurtiswx> RAOF, yeah I can.  Gimme a sec
[23:14] <bdrung> tumbleweed: we should write the dependencies for every script directly into the scripts
[23:26] <bcurtiswx> RAOF, seems ive found some other things.  I will get back to ya later :)
[23:26] <RAOF> bcurtiswx: Heh.  No problem.
[23:46] <tumbleweed> bdrung: I think recommends is probably correct for them. Of course it's helpful if scripts can print what they are missing rather than die horribly, but that's a biggish job.