[00:06] <RAOF> robert_ancell: Aha!  Looks like the tests were right, but my xserver implementation was relying on uninitialised memory.
[00:59] <lifeless> RAOF: oh hai
[01:00] <lifeless> RAOF: pointer needed to whomever does battery stuff
[01:00] <RAOF> lifeless: What particularly about battery stuff?  Colin King would be our resident "please don't chug electrons" expert.
[01:00] <lifeless> I'm on battery
[01:00] <lifeless> been on it for an hour
[01:01] <lifeless> applet shows 'Charged' and no timer.
[01:01] <RAOF> Aha.
[01:01] <RAOF> So many ways this could be wrong :)
[01:01] <lifeless> power control panel says
[01:01] <lifeless> 'using battery power - 1h33m remaining'
[01:01] <RAOF> Is anything else on your panel updating?
[01:01] <lifeless> I want the timer back in the applet :)
[01:02] <lifeless> if I change volume the volume icon in the panel changes
[01:02] <RAOF> The problem would either be in indicator-power or unity panel; probably therefore in indicator-power.
[01:03] <RAOF> The changelog suggests that kenvandine would be your man!
[01:03] <lifeless> kenvandine: yo ^
[01:10] <RAOF> tedg would also be indicated for indicators, but he's not here :)
[06:07] <pitti> Good morning
[06:08] <pitti> Riddell: btw, I bought a DisplayPort/HDMI -> DVI adapter to use my new laptop with my old monitor (unless you want to replace your monitor anyway)
[06:10] <RAOF> Unless you need an active connector, the DP→DVI cable should be of negligable cost :)
[06:10] <pitti> yes, it was some 20 EUR
[06:24] <RAOF> pitti: What's the likelyhood of a MIR or two going through at this stage?  I presume it's on the low side.
[06:25] <pitti> RAOF: pretty much depends on what it is for and the kind of package
[06:25] <pitti> we can't avoid some, but we of course want to reduce them to a minimum
[06:25] <RAOF> It'd be for google-test and libgtest-xorg; if we want some extra build-time tests in the Xserver.
[06:26] <pitti> that seems fine
[06:26] <pitti> more tests are always good
[06:28]  * RAOF will have to get onto that, then.
[06:35] <didrocks> good morning
[06:36] <robert_ancell> pitti, I'm writing a regression test for bug 877766 - it appears that the root user can have chdir rejected. a) WTF?!  b) do you know of other cases I should test for
[06:36] <ubot2`> Launchpad bug 877766 in lightdm "lightdm login fails with NFS home and strict (mode 0700) permissions" [Medium,Triaged] https://launchpad.net/bugs/877766
[06:36] <robert_ancell> does that mean you literally can't cd from bash on a system like this?
[06:41] <pitti> robert_ancell: yes, NFS usually uses root_squash
[06:41] <pitti> so root can't do anything
[06:41] <pitti> which absolutely makes sense for a remote fs :)
[06:42] <robert_ancell> pitti, so the kernel knows everything about the filesystem, but it doesn't let the root user know?
[06:42] <pitti> robert_ancell: I think having a test case with a 0700 home dir, and perhaps an ecryptfs one, sounds good; it's a relatively strong case and checks that you don't make too many assumptions about the home dir, especially before PAM unlocking
[06:43] <pitti> robert_ancell: I think it's more like that the NFS server doesn't accept "root" as a remote user
[06:43] <robert_ancell> pitti, oh, I see
[06:43] <pitti> robert_ancell: it's not unlike ssh -- as root on the client you don't automatically have access to all user accounts on a remote server
[06:44] <robert_ancell> so it should only be chdir/read/write that are affected?
[06:44] <pitti> now, NFS allows root more than ssh does
[06:44] <pitti> robert_ancell: as root you can still handle world-readable/writable files
[06:44] <pitti> and dirs
[06:44] <pitti> but as root you are effectively "nobody" on NFS
[06:44] <robert_ancell> aha
[06:44] <pitti> (that's literally the account it uses, I think)
[06:45] <robert_ancell> I was reading the docs on this but it was a little jargony
[06:45] <pitti> I used NFS in my university, but it's been a while
[08:36] <Riddell> pitti: DisplayPort/HDMI -> DVI connector does me no good for a VGA monitor
[08:37] <pitti> Riddell: ah, sure :) I had assumed you used DVI
[08:42] <RAOF> You *can* get DP→VGA connectors, but they're active and so cost quite close to a new (crappy) monitor.
[08:42] <seb128> hey
[08:43] <pitti> hey seb128
[08:43] <seb128> hey pitti, how are you?
[08:43] <pitti> seb128: quite fine, thanks!
[08:44] <pitti> seb128: FYI, retracer crashed again today, on the dupe confusion
[08:44] <pitti> I have some time now, so I'm dissecting this more thoroughly instead of just restarting it
[08:44] <seb128> pitti, ok, I untagged a bug yesterday evening and restarted them
[08:44] <pitti> ah, that's fine
[08:44] <seb128> well them -> the amd64 one
[08:46] <pitti> bug 942891 is a broken one it stumbled over
[08:46] <pitti> and it's quite similar to the other ones
[08:47] <BigWhale> Hmmm am I the only one that noticed a weird behavior with changing /etc/hosts and dnsmasq?
[08:59] <seb128> pitti, is apport known to be broken btw?
[08:59] <pitti> seb128: broken how?
[08:59] <seb128> pitti, it writes 0 byte root owned files there
[08:59] <seb128> not very useful...
[08:59] <pitti> seb128: if you don't have whoopsie installed, yes
[08:59] <seb128> shouldn't it depends on it?
[09:00] <pitti> seb128: bug 942326
[09:00] <ubot2`> Launchpad bug 942326 in apport "Apport creating 0 byte crash files" [High,Fix committed] https://launchpad.net/bugs/942326
[09:00] <pitti> already fixed in trunk
[09:00] <pitti> seb128: no, just get along with not having it
[09:00] <seb128> pitti, thanks ;-)
[09:00] <pitti> I need this freeze to end :)
[09:00]  * seb128 installs whoopsie
[09:00] <pitti> seb128: oh, you are one bug ahead of me!
[09:01] <seb128> hehe!
[09:01] <pitti> hm, 6 fixes staged in apport trunk
[09:01] <seb128> pitti, weird that none of your rebuilt from yesterday are listed there
[09:01] <pitti> it still amazes me how much time I spend on fixing bugs in a bug reporting program..
[09:02] <seb128> is the list clever enough to filter stuff that actual have a receiving side on launchpad ?
[09:02] <pitti> seb128: so I guess it's clever enough to only count bugs which have a task for that source?
[09:02] <seb128> rather than just .changes numbers?
[09:02] <seb128> pitti, seems so
[09:02] <didrocks> phew, alt-tap fix now in unity/ppa :)
[09:02] <pitti> I don't know how that works, it's bdmurray's baby
[09:02] <pitti> seb128: anyway, for this morning's rebuild round I changed the syntax, in any case
[09:02] <seb128> pitti, well in any case I've a few fixes in unapproved but I don't think it goes to 6
[09:03] <seb128> I need to keep working ;-)
[09:03] <seb128> didrocks, lut, nice!
[09:03] <seb128> I'm running staging here today
[09:03] <seb128> I didn't notice any difference with 5.4 yet ;-)
[09:03] <didrocks> seb128: salut ;)
[09:03] <didrocks> seb128: please update, there are some cases where alt-tab was stuck
[09:04] <seb128> ok
[09:04] <didrocks> ok, we won a lot of keywords against the ubuntu: branch, as planned :/
[09:04] <seb128> the hud still doesn't give back the focus to the app :-(
[09:04]  * didrocks dig and move them to the right target
[09:04] <didrocks> seb128: yeah, I know…
[09:04] <didrocks> still on the priority list
[09:05] <seb128> and the notify-osd color stuff is still not fixed
[09:05] <seb128> didrocks, keywords -> I plan to send the GNOME one to GNOME, to get them commited and wait .91
[09:05] <seb128> didrocks, not sure they are worth adding a patch before .91
[09:06] <didrocks> seb128: hum, no distro-patch?
[09:06] <seb128> didrocks, you can let the GNOME ones to me if you want
[09:06] <didrocks> seb128: well, it's fine, I can handle them
[09:06] <didrocks> I can stage some for the defaults, and report upstream
[09:06] <seb128> didrocks, well, distro patch if you want, but it seems work over what's useful, at least no upload for those please
[09:06] <seb128> didrocks, ok, your call, thanks ;-)
[09:06] <didrocks> seb128: oh, I'll just stage them, no worry :)
[09:07] <seb128> pitti, btw either you misread or count changed by we are tie it seems ;-)
[09:10] <pitti> seb128@ubuntu.com has 191 fixes
[09:10] <pitti> martin.pitt@ubuntu.com has 190 fixes
[09:10] <pitti> seb128: that's on http://reports.qa.ubuntu.com/reports/bug-fixing/precise-fixes-report.html
[09:10] <pitti> oh, fun -- http://reports.qa.ubuntu.com/reports/bug-fixing/canonical-desktop-team-precise-fixes-report.html has 195 for both of us
[09:11] <seb128> right, I look at the desktop list
[09:11] <seb128> desktop team for the win in any case, we secured the first 3 places I think ;-)
[09:14] <pitti> it's also interesting that kirkland has more fixes than most canonical employees; community FTW: )
[09:14] <seb128> ;-)
[09:19] <seb128> waouh
[09:19] <seb128> new webkit built in the ppa \o/
[09:19] <seb128> the ldflag seems to have helped
[09:20] <micahg> seb128: which flag did you use?
[09:21] <seb128> micahg, -Wl,--no-keep-memory
[09:21] <micahg> ah, ok
[09:21] <pitti> nice
[09:41] <chrisccoulson> good morning everyone
[09:45] <seb128> chrisccoulson, hey, how are you?
[09:48] <jibel> Sweetshark, I reopen bug 916291
[09:48] <ubot2`> Launchpad bug 916291 in libreoffice "failed to upgrade from Oneiric to Precise: ERROR: Cannot determine language! - exit status 134" [High,Confirmed] https://launchpad.net/bugs/916291
[09:48] <jibel> Sweetshark, it is still a problem with daily upgrade testing
[09:48] <chrisccoulson> hi seb128. i'm good thanks
[09:48] <chrisccoulson> how are you?
[09:49] <seb128> chrisccoulson,  I'm good, a bit tired though
[09:49] <chrisccoulson> seb128, yeah, i know that feeling :)
[09:49] <seb128> ;-)
[09:50] <chrisccoulson> wow, precise-fixes-report makes it look like i don't do anything useful ;)
[09:50] <seb128> updated to the current unity from the ppa, glad that they fixed the alt tap stuff, my go to ws1 ws2 ws3 are alt based and I kept opening the hud before
[09:51] <seb128> chrisccoulson, heh, we have quite some desktop bugs waiting for you if you want to pick it up ;-)
[09:51] <seb128> chrisccoulson, but don't worry, I'm sure everybody appreciate having a working uptodate firefox and tb ;-)
[09:51] <chrisccoulson> seb128, i still have quite some firefox bugs too, like dropping the libgnome requirement :(
[09:51]  * seb128 hugs chrisccoulson
[09:51] <chrisccoulson> i'm going to do that one today though
[09:51] <pitti> seb128: these retracer crashes are indeed quite interesting, I did an analysis in bug 943117 (you don't need to read if you aren't interested, of course)
[09:51] <ubot2`> Launchpad bug 943117 in apport "retracer crashes on wrong duplication" [Medium,In progress] https://launchpad.net/bugs/943117
[09:51]  * chrisccoulson hugs seb128
[09:52] <seb128> pitti, oh, I'm interested, looking ;-)
[09:52] <pitti> seb128: just look at the last comment, the previous ones are boring analysis
[09:53] <chrisccoulson> hmmm, i'm really liking mercurial patch queues :)
[09:54] <seb128> interesting
[09:54] <seb128> chrisccoulson, how do they work?
[09:55] <pitti> seb128: so, we currently assert on "new bug is a dupe of A with address sigs and a dupe of B with symbolic sigs"
[09:55] <chrisccoulson> seb128, it's basically just quilt
[09:55] <pitti> seb128: (the cautious approach)
[09:55] <chrisccoulson> it's designed to allow you to break up work in to multiple patches
[09:55] <pitti> seb128: but so far all of the bugs I looked at actually turned out that A was a dupe of B which we didn't originally detect as such"
[09:55] <chrisccoulson> seb128, https://developer.mozilla.org/en/Mercurial_Queues
[09:56] <seb128> chrisccoulson, thanks
[09:56] <chrisccoulson> although, you don't need an extension now. it's built in to newer versions of mercurial
[09:56] <seb128> pitti, why do you need to stop on those? worth cases we have a dup not marked as such and 2 master bugs for the same issue?
[09:56] <seb128> pitti, doesn't seem worth stopping the retracers on?
[09:56] <pitti> seb128: well, that's the bug
[09:56] <seb128> ok
[09:57] <pitti> seb128: I originally added this when we introduced address sigs, to ensure that we don't process a thousand bugs with a flawed algorithm
[09:57] <pitti> seb128: but now that we have some experience/trust with it, we can be more bold, I think
[09:57] <seb128> right
[09:57] <pitti> and consider either capable of identifying dupes
[09:57] <pitti> s/either/both/
[09:58] <seb128> do you know why they didn't get detected as dup from the start if their signature match?
[09:58] <seb128> or is that only the symbol sig matching?
[09:58] <pitti> seb128: yes, I wrote in the bug -- neither of the sigs matched
[09:58] <seb128> i.e not the address sig?
[09:58] <pitti> seb128: it's the third bug which matches the address sig of A and symbolic sig of B
[09:58] <seb128> oh ok, right, I see
[09:58] <pitti> seb128: but both address and symbolic sig of A != B
[09:59] <pitti> seb128: that's what I called "interesting"
[09:59] <seb128> it's a bit of a special case, I'm surprised it happens so often in practice
[09:59] <chrisccoulson> mvo, around?
[09:59] <seb128> glatzor, hey
[09:59] <pitti> seb128: well, most cases actually were because I changed the symbolic sigs in the middle -- still remember the __add_sse24() stuff?
[09:59] <pitti> seb128: that doesn't seem to be the case in this synaptic crash, though
[10:00] <seb128> pitti, yeah I remember those
[10:00] <pitti> seb128: so most of the fallout was that the dupe DBs got inconsistent because we changed the symbolic algorithm
[10:00] <pitti> but still I think it's reasonably safe to just make all three duplicates
[10:00] <seb128> +1
[10:01] <pitti> which will cancel out the noise from each other's approach
[10:01] <pitti> seb128: effectively that's what we did manually anyway -- we looked at the log's assertion message and manually duped
[10:01] <pitti> (at least that's what I did)
[10:02] <seb128> I didn't because I was unsure what to do with those, I just called you for you help ;-)
[10:02] <seb128> pitti, thanks for the explanations
[10:02] <seb128> and +1 from me for just dupping things in those cases
[10:03] <pitti> what a brain tangler
[10:05] <mvo> chrisccoulson: yes, but in a call
[10:05] <mvo> pitti: what synaptic crash? I fixed one this morning
[10:05] <chrisccoulson> mvo, sure, no problem. i can wait until you're finished :)
[10:05] <pitti> mvo: bug 936677
[10:05] <ubot2`> Launchpad bug 936677 in synaptic "synaptic crashed with SIGSEGV" [Medium,In progress] https://launchpad.net/bugs/936677
[10:06] <pitti> mvo: but I'm mostly talking about the apport  retracer duplicate identification
[10:08] <mvo> chrisccoulson: if you write the question here I can think about it during the call in a background thread
[10:09] <chrisccoulson> mvo - is there a "correct" way to enable extra software channels (such as partner). say, for example, i want to offer the adobe flashplugin from the partner repo to users the first time they go to youtube
[10:09] <chrisccoulson> i looked at what apturl does, but that seems a little bit hacky
[10:09] <chrisccoulson> and it doesn't look like software-center does it either
[10:10] <micahg> chrisccoulson: um, you might have a policy issue with that  unless you're only doing it if partner is enabled
[10:10] <chrisccoulson> micahg, we would enable partner
[10:10] <micahg> chrisccoulson: you can't do that AIUI without explicit consent
[10:11] <chrisccoulson> micahg, yes, i'm well aware of that already
[10:11] <mvo> chrisccoulson: you could call sofware-center it has code for this, I don't think the code is extracted to something else
[10:12] <chrisccoulson> mvo, hmm, i tried looking in software-center already. mind pointing me in the right direction? :)
[10:12] <chrisccoulson> i'd like to try and do this without running software-center if possible, and it's pretty easy for me to display the eula in firefox already
[10:12] <micahg> chrisccoulson: also, why not just encourage people to enable the HTML5 trial?
[10:13] <chrisccoulson> micahg, how?
[10:13] <micahg> that is if youtube is the use case
[10:13] <micahg> youtube.com/html5
[10:13] <chrisccoulson> micahg, how do you encourage users who have gone to youtube to do that?
[10:14] <micahg> I'll have to test that next time I have a VM up, I think youtube might actually do that already
[10:14] <chrisccoulson> it didn't the last time i tried it
[10:14] <micahg> you could just show a link to enable the trial the same way you'd ask to enable partner
[10:14] <chrisccoulson> in addition to the fact that a lot of video's still don't work with it
[10:15] <micahg> ah, if some videos don't work, I guess that's not a universal solution
[10:15] <chrisccoulson> micahg, adding website specific hacks to the plugin finder doesn't seem like a great solution
[10:15] <chrisccoulson> in fact, that would probably be more work
[10:17] <rickspencer3> dobey, et al. is there documentation somewhere for how I should import desktopcouch into a python app with goi these days?
[10:17] <micahg> chrisccoulson: sorry, that's what I thought you were doing ;)
[10:19] <pitti> rickspencer3: are there significant API differences when you move to gir1.2-desktopcouch-1.0?
[10:19] <rickspencer3> pitti, I doubt it
[10:19] <rickspencer3> pitti, the problem is I can't figure out how to write the import statements :(
[10:20] <rickspencer3> from desktopcouch.records.server import CouchDatabase
[10:20] <rickspencer3> from desktopcouch.records.record import Record
[10:22] <rickspencer3> this is the last thing I need to do before quickly.widgets is ported to GOI, which I need to finish in order to get the package onto seb128's computer
[10:22] <pitti> >>> from gi.repository import Couchdb
[10:22] <pitti> >>> Couchdb.Database
[10:22] <pitti> <class 'gi.repository.Couchdb.Database'>
[10:22] <pitti> that seems to be the first one
[10:22] <rickspencer3> thanks pitti
[10:23] <seb128> rickspencer3, salut ;-)
[10:23] <pitti> rickspencer3: I can't find anything resembling a Record class, though
[10:23] <rickspencer3> pitti, I can stumble around some more iPython
[10:23] <pitti> rickspencer3: "Couchdb" has {get,set}_record_type() methods in the Document class
[10:24] <pitti> rickspencer3: good luck!
[10:24] <rickspencer3> ooh, that sounds ugly
[10:24] <rickspencer3> maybe I should just dump couchgrid and write sqlitegrid instead
[10:25] <pitti> given that we don't love couchdb any more, that might be nice indeed :)
[10:26] <rickspencer3> let me see how hard this is to port
[10:26] <rickspencer3> I've been meaning to do a sqlite implementation anyway
[10:28] <AfC> "we don't love couchdb anymore"?
[10:28] <AfC> (not trolling, just asking)
[10:30] <pitti> the U1 team stopped using it for their services, and evolution-couchdb was dropped a while ago
[10:30] <pitti> as apparently it was too hard to make it do what we need to
[10:35] <Sweetshark> jibel: k, thx
[10:37] <czajkowski> Sweetshark: your bug yesterday re removing open suse from a bug was done for you, had to get webops to remove it
[10:38] <Sweetshark> czajkowski: thx, saw it.
[10:38] <tkamppeter> pitti, hi
[10:38] <Amoz> hi guys, latest precise, gnomeshell power-indicator isnt updating values
[10:39] <pitti> hello tkamppeter
[10:39] <Amoz> upower --dump shows the battery is at 94% right now, but the indicator says 100%
[10:39] <seb128> Amoz, did you open a bug?
[10:39] <Amoz> where does the indicator get it values from, or how can I debug it?
[10:40] <Amoz> seb128, potential duplicate #934233
[10:40] <tkamppeter> pitt, you have got my mails from yesterday? I have found a solution for the trigger problem and applied it to CUPS, ready for upload after beta1.
[10:40] <Amoz> reporter says the indicator displays it as charing although he undocked it
[10:40] <seb128> Amoz, I guess you need http://git.gnome.org/browse/gnome-shell/commit/?id=8bcbf3030f1c6c3088d4aa2b921d5d7031828ce9
[10:40] <tkamppeter> pitti ^^
[10:41] <Amoz> seb128, that could be something
[10:41] <Amoz> seb128, restarting gnomeshell updates the values it seems
[10:41] <pitti> tkamppeter: yes, I got it, thanks!
[10:42] <seb128> Amoz, well try that patch
[10:42] <tkamppeter> pitti, have you any idea on bug 936629? Ghostscript accessing /proc/XXX/auxv and being stopped by AA?
[10:42] <ubot2`> Launchpad bug 936629 in cups "Printing fails after printing first document " [Undecided,Incomplete] https://launchpad.net/bugs/936629
[10:42] <pitti> no, not yet
[10:43] <tkamppeter> pitti, should I assign it to you?
[10:44] <pitti> tkamppeter: I have the mail in my mbox, but sure
[10:45] <tkamppeter> pitti, OK.
[10:45] <dpm> hi desktop folks! bamfdaemon has just crashed on me and I'm getting a bunch of duplicate entries in the launcher. Is there a way to restart it, other than logging out and back into the session?
[10:46] <seb128> dpm, run "unity"
[10:46] <seb128> or compiz --replace
[10:46] <seb128> dpm, hey btw ;-)
[10:48] <dpm> [...]
[10:48] <dpm> unity-panel-service: no process found
[10:48] <dpm> Initializing unityshell options...done
[10:48] <dpm> Segmentation fault (core dumped)
[10:48] <dpm> bummer
[10:49] <dpm> hey seb128, how's it going?
[10:49] <seb128> dpm, well, you can run it again, run "unity" from a vt if needed
[10:49] <dpm> it seems the second time around it worked
[10:49] <seb128> dpm, busy but good ;-) how are you?
[10:49] <dpm> seb128, it seems we're all the same :)
[10:51] <seb128> jbicha, hey
[10:53] <Amoz> seb128, looks like the patch won't apply, the code it's replacing doesn't look the same in the patch and in my power.js
[10:53] <seb128> Amoz, ok, well I guess gnome-shell's code needs updating in some way for g-s-d 3.4 anyway
[10:53] <seb128> same reason as described on this bug
[10:53] <seb128> the signals changed
[10:54] <seb128> you should open a bug on launchpad if there is not already one
[10:54] <Amoz> seb128, depends if you think 934233 is a dup
[10:54] <seb128> no idea, could be, I don't use gnome-shell
[10:54] <seb128> nor work on it
[10:54] <Amoz> I'll open a new one then
[10:54] <seb128> what I know is that it needs to be updated for gsd changes
[10:54] <Amoz> thank you
[10:54] <seb128> yw
[10:56] <jbicha> seb128: good morning
[10:56] <seb128> jbicha, how are you?
[10:56] <seb128> jbicha, Amoz was reporting that the gnome-shell battery indicator doesn't update as it should, do you know if that's a known issue?
[10:57] <seb128> jbicha, it probably needs an update for the g-s-d signal changes (I pointed a commit from trunk but it doesn't apply to 3.2 it seems)
[10:58] <jbicha> seb128: I've been running gnome-shell 3.3.90 this week, maybe new gnome-shell will land in precise next week?
[10:59] <Amoz> ooh, new gnome-shell yes please
[10:59] <seb128> jbicha, you tell me, you should know better
[11:00] <seb128> jbicha, I'm neither using it nor working on it ;-)
[11:00] <Amoz> jbicha, wasn't you saying the we only should update some packages and stay on 3.2?
[11:00] <micahg> the new gnome-shell will clutter up precise ;)
[11:00] <seb128> ok, no way then
[11:00] <jbicha> lol
[11:00] <seb128> brb, need to restart my session
[11:01] <BigWhale> speaking of batteries, I powered my laptop at 0915, not it's 1201 and I still have more than an hour of batteries left.
[11:01] <jbicha> Amoz: I was just reporting what the current status was, since seb128 did the gnome-control-center/g-s-d update, things have changed a bit
[11:03] <Amoz> ok
[11:05] <seb128> re
[11:05] <seb128> jbicha, hey, no joking, the new clutter is lot of changes we can't do that at the end of the cycle
[11:05] <jbicha> seb128: someone in #ubuntu+1 yesterday said they had problems with indicator-power's battery indicator too
[11:06] <seb128> jbicha, that was fixed a week ago or so
[11:06] <seb128> jbicha, maybe their mirror is not uptodate or they didn't restart since the update?
[11:07] <jbicha> maybe
[11:07] <jbicha> seb128: if you don't think clutter should be updated, you should comment at bug 941617
[11:07] <ubot2`> Launchpad bug 941617 in clutter-1.0 "FFe: Update clutter/cogl to 1.9" [Wishlist,In progress] https://launchpad.net/bugs/941617
[11:08] <seb128> jbicha, I will
[11:08] <seb128> jbicha, sorry but it would be crazy, they did ton of changes and refactoring this cycle and ricotz said another cogl soname change was still coming at least
[11:08] <Amoz> is there anything I can do?
[11:09] <seb128> Amoz, sleep? walk? eat? ;-)
[11:09] <seb128> Amoz, or what was the question? ;-)
[11:09] <jbicha> seb128: that's why it was waiting until next week when the cogl soname bump would land
[11:09] <Amoz> seb128, about the power-indicator =)
[11:09] <seb128> jbicha, well I'm not in the r-t but that seems crazy
[11:09] <Amoz> should i file a bug?
[11:09] <seb128> Amoz, yes, I told you that before ;-)
[11:10] <Amoz> oh sry then
[11:11] <seb128> Amoz, no worry
[11:12] <Amoz> ;)
[11:15] <Amoz> help me out here, a good summary, "power-indicator not updating due to faulty signal connectors" ?
[11:26] <Amoz> seb128, I can set it to confirmed as well?
[11:26] <Amoz> it's reported at #943183
[11:26] <seb128> Amoz, if you reported it no, the reporters shouldn't confirm their own bug
[11:26] <Amoz> ah
[11:26] <seb128> that defeat the purpose of having 2 status otherwise
[11:26] <Amoz> true
[11:55] <apol_> hi, I am improving kubuntu's software center to submit information to the rnr service
[11:55] <apol_> now when I send a request I get an error saying: "Authorization Required"
[11:55] <apol_> can somebody give me a hint about what's going on?
[12:11] <seb128> apol_, hi, you might want to ask on #software-center
[12:13] <apol_> seb128: I asked there but nobody answered... anyway, I'll be patient :P
[12:22] <didrocks> pitti: hey, when you get a chance, can you try pressing alt on your unity 5.4 with a gtk3 (or firefox/thunderbird) app?
[12:22] <didrocks> pitti: tell me if you see the menus in the tope panel :)
[12:22] <didrocks> (trying to see if it's a 5.6 regression)
[12:28] <rye> didrocks, i can't
[12:28] <rye> :)
[12:28] <rye> but that's 5.6
[12:28] <chrisccoulson> didrocks, i don't see a menu with 5.4
[12:28] <didrocks> rye: ah, I need someone with 5.4 :)
[12:28] <rye> and i have 5.4
[12:29] <didrocks> chrisccoulson: ok, you are not using the unity-team ppa, right?
[12:29] <rye> 5.4.0-0ubuntu3 to be precise -> no menu
[12:29] <didrocks> ok :)
[12:29] <chrisccoulson> didrocks, i am. but i haven't updated yet
[12:29] <didrocks> thanks for confirming
[12:29] <chrisccoulson> i'm still on 5.4 ;)
[12:29] <rye> didrocks, is there a bug i can +1 ?
[12:29]  * didrocks put on the priority list
[12:29] <didrocks> https://bugs.launchpad.net/unity/+bug/943194
[12:29] <ubot2`> Launchpad bug 943194 in unity "[regression] Pressing alt doesn't show the menu title bar in top panel" [Critical,Triaged]
[12:30] <didrocks> do any of you have a gtk2 app installed by any chance?
[12:30] <rye> hm, nautilus and xterm works, xchat/firefox/thunderbird, i guess that's gtk2
[12:31] <didrocks> firefox, thunderbird don't for me
[12:31] <rye> xchat/firefox/thunderbird do not
[12:31]  * rye needs to wake up, it's 2PM
[12:31] <didrocks> :)
[12:32] <didrocks> rye: xchat doesn't work then?
[12:32] <didrocks> (this one is gtk2)
[12:32] <rye> didrocks, xchat-gnome is gtk2, right
[12:32] <didrocks> ok, great :)
[12:32] <didrocks> thanks again
[12:33] <rye> gtk3 apps have the menu on alt, gtk2 don't
[12:33] <didrocks> hum
[12:33] <didrocks> gnome-terminal doesn't here
[12:33] <didrocks> chrisccoulson: same for you? gtk3 apps work?
[12:33]  * didrocks is getting confused
[12:33] <chrisccoulson> didrocks, yeah, seem to
[12:33] <didrocks> ah
[12:33] <didrocks> so a regression
[12:38] <chrisccoulson> not sure why it's broken in some apps and not others
[12:38] <seb128> chrisccoulson, gtk2 against gtk3?
[12:39] <chrisccoulson> seb128, i don't think that should be relevant. we have our own code in firefox / thunderbird for handling this: http://bazaar.launchpad.net/~extension-hackers/globalmenu-extension/trunk/view/head:/extensions/globalmenu/components/src/uGlobalMenuBar.cpp#L494
[12:39] <seb128> ok
[12:39] <chrisccoulson> yeah, i just tested it, and we never even see the alt keypress
[12:39] <chrisccoulson> so, definitely not my bug :)
[12:40] <chrisccoulson> *phew*
[12:47] <didrocks> chrisccoulson: and alt + F in gnome-terminal?
[12:47] <didrocks> chrisccoulson: does it open the menu?
[12:48] <chrisccoulson> didrocks, yeah. and it works for firefox too
[12:48] <didrocks> ok, seems a regression only in gnome-terminal
[12:48] <chrisccoulson> it's just showing the menubar with the alt key which is broken in firefox
[12:49] <chrisccoulson> didrocks, and, as expected, it works if i turn off the shortcut for the HUD
[12:49] <didrocks> chrisccoulson: care to comment on the bug? ;)
[12:52] <chrisccoulson> didrocks, done
[12:52] <didrocks> thanks :)
[13:16] <ritz> lol
[13:16]  * ritz wrong window, sorry 
[13:26] <seb128> hey ritz
[13:26] <ritz> seb128, hi  :)
[13:26] <ritz> bonjour
[13:26] <seb128> bonjour ;-)
[13:31] <pitti> didrocks: indeed I don't
[13:33] <pitti> didrocks: not in firefox, but it does seem to work in g-terminal
[13:33] <pitti> didrocks: it also works in empathy
[13:33] <didrocks> pitti: yeah, there is clearly a regression, thanks! Marking as blocking the release
[13:34] <pitti> didrocks: that's teh precise unity, I'm not running PPA ATM
[13:34] <didrocks> pitti: yeah, that was what I looking for, confirmatino it's a regression, thanks! :)
[13:34] <didrocks> confirmation*
[13:58] <dobey> rickspencer3: you shouldn't use desktopcouch in any more. hopefully we'll be ready to ship u1db in 12.10 though
[14:16] <desrt> good morning, hackers!
[14:18] <pitti> hey desrt
[14:23] <cyphermox> good morning
[14:28]  * Sweetshark slurps his afternoon tea.
[14:28] <Sweetshark> desrt, cyphermox: morning!
[14:32] <cyphermox> pitti: can you look again at checkbox in oneiric proposed queue, hopefully we got it right this time ;)
[14:34] <seb128> cyphermox, hey, how are you?
[14:35] <pitti> hey cyphermox
[14:35] <pitti> cyphermox: yes, will do
[14:35] <BigWhale> indicator-weather is crashing horribly all the time ...
[14:38] <cyphermox> hey seb128, doing alright
[14:39] <seb128> cyphermox, the LDFLAGS stuff seem to have worked, webkit built in the ppa just fine (where previous version wouldn't build on i386)
[14:39] <seb128> cyphermox, just for info
[14:39]  * Sweetshark is confused. Should we make our UDS travel planning already or shall we delay?
[14:41] <cyphermox> seb128: cool
[14:42] <cyphermox> seb128: using both or just one
[14:42] <cyphermox> Sweetshark: delay, afaik
[14:42] <cyphermox> Sweetshark: anyway, I tried yesterday morning and the registration form was borked
[14:42] <seb128> cyphermox, just one
[14:42] <cyphermox> or the day before, ykwim
[14:43] <cyphermox> seb128: cool. so we have potentially a bit of room for improvement :)
[14:43] <Sweetshark> cyphermox: thx
[14:44] <seb128> cyphermox, ;-)
[14:44] <cyphermox> pitti: are you familiar with the procedure for debugging an issue such as the nm-applet 10Hz polling? would it be useful if I blog about my findings on how to match these poll calls to potential things to look at in Gtk apps? :)
[14:45] <pitti> cyphermox: I'm not really familiar how to map a poll() call in strace back to a piece of C
[14:45] <pitti> cyphermox: it took me three hours and tons of printf() statements in notify-osd to figure it out (but I believe that was an exceptionally hard case
[14:45] <cyphermox> pitti: what I found seems to be very specific to Gtk but I think I've seen a pattern
[14:46] <pitti> since it was deep within a rather unexpected library
[14:46] <cyphermox> perhaps it doesn't map to other things than nm-applet but I'll write this down in a blog post for planet, in case somebody else can use it
[14:46] <pitti> that sounds useful indeed
[14:47] <cyphermox> this specific poll was matching very closely to g_idle_add() and g_timeout_add() calls
[14:47] <pitti> cyphermox: that would certainly be the most obvious candidate
[14:47] <cyphermox> the issue ultimately isn't caused by it, but it helps a lot in finding the root cause
[14:48] <pitti> if you have a timeout_add with the same frequency, and the wakeups change if you change that timeout_add, you got it
[14:48] <cyphermox> yup
[14:49] <seb128> cyphermox, desrt might be a good person to ask if he has an idea about what in gtk could do that 10Hz polling
[14:49] <seb128> desrt, hey ^
[14:49] <cyphermox> seb128: already solved, really
[14:49] <desrt> seb128: sup
[14:49] <seb128> oh ok
[14:49] <seb128> desrt, unping
[14:49]  * desrt goes back to sleep
[14:49] <seb128> desrt, ;-)
[14:49] <cyphermox> hehe
[14:50] <cyphermox> seb128: it was an issue in NM with updating properties in libnm-glib
[14:50] <cyphermox> I'm about to upload the fix, just looking if there are other things I can bundle with it
[15:05] <gatox> hi, i'm having problems when i try to change between desktops, ctrl+alt+arrows is not working... dows anyone knows if that issue already exist or i should create it?
[15:14] <rickspencer3> dobey, noted
[15:14] <rickspencer3> I deleted couchgrid from quickly.widgets
[15:14] <dobey> cool
[15:24]  * kenvandine fights with evolution, again... 
[15:25] <kenvandine> constantly prompting for a password for my google calendars... force-shutdown doesn't fix it like usual
[15:25] <pitti> yeah, I often get that as well
[15:25] <pitti> I usually let the window just sit there behind firefox and get out of my eyes
[15:25] <kenvandine> usually a --force-shutdown fixes it for a while
[15:26] <kenvandine> today it isn't... grrrrr
[15:26] <dobey> just remove your google calendars from evolution
[15:26] <dobey> et voila, fixed! :)
[15:26] <kenvandine> dobey, that is the main reason why i use evolution!
[15:26] <dobey> although
[15:26] <dobey> i have never had this problem
[15:26] <kenvandine> i want my schedule in the indicator
[15:26] <pitti> but having gcal there is kind of the point :)
[15:27] <kenvandine> without that i should just switch to thunderchicken
[15:27] <kenvandine> :)
[15:27] <dobey> i was being facetious
[15:27] <kenvandine> dobey, as usual
[15:27] <kenvandine> dobey, so that never happens to you?
[15:27] <dobey> nope
[15:27] <dobey> and i have hosted google calendar in evo even
[15:28] <dobey> it's the only one i have in there though
[15:28] <dobey> since it's the only calendar in google i actually care about
[15:28] <dobey> at least for the moment
[15:29] <dobey> but i've never had e-d-s go crazy with the password dialog, no
[15:29] <dobey> kenvandine: maybe your gnome-keyring-daemon broke?
[15:30] <kenvandine> i have 2 google accounts and 6 google calendars in evo
[15:30] <kenvandine> empathy and gwibber never have auth problems
[15:30] <kenvandine> so i can't imaging it is the keyring daemon
[15:31] <kenvandine> and... it is usually triggered by the evo alarm
[15:32] <dobey> hmm
[15:32] <dobey> that's odd
[15:33] <kenvandine> dobey, indeed
[15:33] <kenvandine> in fact, it has reliably been triggered by the alarm
[15:33] <kenvandine> dobey, do you have that enabled?
[15:34] <dobey> afaik
[15:34] <dobey> maybe not though
[15:34] <kenvandine> although right now it happened right at boot
[15:34] <kenvandine> and not fixable
[15:34] <dobey> well i don't have an evolution-alarm-notify.desktop in ~/.config/autostart
[15:34] <kenvandine> i really can't believe the abuse i take from evolution
[15:35]  * kenvandine disables that
[15:35] <dobey> 24836 ?        SLl    0:02  \_ /usr/lib/evolution/3.2/evolution-alarm-notify
[15:35] <dobey> it's running
[15:35] <dobey> *shrug*
[15:35] <kenvandine> oh... it is by default i think
[15:35] <dobey> yeah
[15:36] <dobey> but complex things are complex, so i wanted to verify it was in fact running
[15:36] <pitti> seb128: yay, bug 943117 fixed and confirmed to work on the synaptic crash
[15:36] <ubot2`> Launchpad bug 943117 in apport "retracer crashes if a bug has multiple master bugs" [Medium,Fix committed] https://launchpad.net/bugs/943117
[15:37]  * pitti thoroughly despises this duplication logic now
[15:38] <mdeslaur> kenvandine: I have a bug open for your evolution issue: #917282
[15:38] <mdeslaur> kenvandine: It drives me _insane_ also
[15:38] <kenvandine> today after rebooting killing it and logout/in didn't help... it was consistently immediately failing
[15:39] <kenvandine> i just disabled it and logged out
[15:39] <kenvandine> now it seems fine again
[15:39] <kenvandine> disabled the alarm
[15:39] <kenvandine> it is like when that thing starts it hoses somethign
[15:52] <desrt> tedg: hey
[15:53] <desrt> tedg: is it safe to keep around dbusmenumenuitem instances for extended periods of time?
[15:58] <tedg> desrt, safe?
[15:58] <tedg> desrt, I mean, they shouldn't eat kittens.
[15:58] <desrt> tedg: for example, holding onto a GtkTreeIter is generally not safe
[15:59] <desrt> because if some rows get added, it may go stale
[15:59] <kenvandine> yum
[15:59] <desrt> if ihave a dbusmenumenuitem (and assuming it doesn't get deleted itself) then will it always refer to the same item?
[15:59] <tedg> desrt, No, a dbusmenu item won't go stale itself, but it might end up in a state where it's not in the tree.  (parent gets free'd)
[15:59] <desrt> right
[15:59] <tedg> desrt, Yes
[15:59] <desrt> okay.  sounds good.
[16:00]  * desrt puts DbusmenuMenuitem inside HudItem
[16:00] <desrt> this is the new activate() setup
[16:00] <desrt> did you get a chance to build the docs from yesterday?
[16:01] <chrisccoulson> wow, libsm is absolutely hideous
[16:02] <desrt> chrisccoulson: what did you think 'SM' stood for, anyway?
[16:02] <chrisccoulson> ;)
[16:03] <desrt> chrisccoulson: it may interest you to know that gtk3 recently grew SM support via GtkApplication
[16:03] <chrisccoulson> desrt, yeah, but that means switching to gtk3 ;
[16:03] <chrisccoulson> i need this to work with gtk2 as well, without depending on libgnome :)
[16:03] <desrt> chrisccoulson: use eggsmclient, then
[16:04] <desrt> it's a bit of copy/paste code that everyone uses to avoid having to deal with libsm
[16:04] <desrt> and works fine with gtk2
[16:04] <chrisccoulson> desrt, https://bugzilla.mozilla.org/show_bug.cgi?id=694570#c5 :(
[16:04] <ubot2`> Mozilla bug 694570 in Startup and Profile System "Stop using libgnome and libgnomeui on Linux" [Normal,New: ]
[16:05] <desrt> oh christ
[16:05] <desrt> find out who wrote eggsmclient and ask for an exception
[16:05] <desrt> rewriting it because of some licence issues... ugh
[16:06] <chrisccoulson> i think vuntz was going to take care of that
[16:06] <chrisccoulson> not sure if anything happened yet though
[16:06] <desrt> danw carlosgc chpe mclasen alexl and amigadave
[16:07] <desrt> one of those works for canonical
[16:07] <desrt> you'll find the rest of them on #gtk+ :)
[16:08] <desrt> + * Inspired by various other pieces of code including GsmClient (C)
[16:08] <desrt> + * 2001 Havoc Pennington, GnomeClient (C) 1998 Carsten Schaar, and twm
[16:08] <desrt> + * session code (C) 1998 The Open Group.
[16:08] <desrt> party time
[16:08] <chrisccoulson> by process of elimination, i guess that amigadave works for us :)
[16:08] <desrt> chrisccoulson: yes :p
[16:09] <desrt> anyway.. danw is the original person who landed the code
[16:09] <desrt> best talk to him
[16:09] <chrisccoulson> thanks
[16:22] <ricotz> seb128, hello
[16:23] <ricotz> seb128, did you told pitti and thought more about gstreamer0.11 ?
[17:15] <pitti> didrocks: hm, I haven't seen a proper release note about the HUD in the weekly meetings; who would be best to come up with a three-line summary what it is?
[17:16] <didrocks> pitti: I think I can do it
[17:16] <didrocks> pitti: can it be tomorrow morning? (in a meeting right now and have to run just after)
[17:19] <pitti> didrocks: yes, sure; I made up something on https://wiki.ubuntu.com/PrecisePangolin/TechnicalOverview for now, but it can certainly be improved
[17:19] <didrocks> pitti: I'll tomorrow morning :)
[17:19] <pitti> "    There is a new way to quickly search and access any desktop application's menu, called the "HUD". Press the Alt key and enter some letters and words, and it will show the corresponding entries, including some fuzzy matching.
[17:19] <pitti> "
[17:24] <seb128> pitti, you can probably borrow some text from http://www.markshuttleworth.com/archives/939
[17:25] <seb128> pitti, like "In 12.04 LTS, the HUD is a smart look-ahead search through the app and system (indicator) menus." "It’s smart, because it can do things like fuzzy matching, and it can learn what you usually do so it can prioritise the things you use often. It covers the focused app (because that’s where you probably want to act) as well as system functionality;"
[17:25] <seb128> didrocks, ^
[17:32] <pitti> good night everyone!
[17:34] <seb128> gord, 'night
[17:36] <kenvandine> good night pitti
[17:41] <gord> seb128, stop trying to tab complete normal words :P
[17:41] <seb128> lol
[17:42] <seb128> but, tab is so awesome, that should work :p
[17:42] <gord> there is an irssi addon that lets you do it, its great, but soo lazy ;)
[17:58] <didrocks> have a good night everyone
[18:17] <dupondje> Do you need to be in a particular group to be able to add printers in the system settings (gnome3) ?
[18:18] <seb128> dupondje, not sure but you need cups-pk-helper installed
[18:20] <dupondje> ok that worked :)
[18:20] <dupondje> now getting the print tasks to work :(
[18:23] <dupondje> Inactief - Tree connect failed (NT_STATUS_ACCESS_DENIED) hmz
[18:47] <dupondje> seems like gnome doesn't ask samba password for printing
[19:00] <Sweetshark> pitti: openoffice.org_3.3.0-7ubuntu7 is on chinstrap for sponsoring, please have a look at the debdiff.
[19:01] <Sweetshark> pitti: it dropping the report-builder dep.
[20:12] <desrt> tedg: good afternoon.  more dbusmenu questions :)
[20:34] <tedg> desrt, Don't ask to ask, just ask ;-)
[20:34] <desrt> tedg: how do i know if a menuitem is a submenu?
[20:34] <desrt> other than it having children
[20:34] <tedg> desrt, There's a property on it
[20:35] <desrt> DBUSMENU_MENUITEM_CHILD_DISPLAY_SUBMENU seems to be documented as "this may or may not exist"
[20:35] <tedg> desrt, It always exists if there are children
[20:35] <desrt> good enough answer
[20:37] <Sweetshark> Oracle says: LibreOffice: Best Office killer yet
[20:37] <Sweetshark> https://plus.google.com/u/0/101094190333184858950/posts/ADv1yBgnc4r
[20:39] <desrt> Sweetshark: so i was talking to some mozilla guys the other day
[20:39] <desrt> and we were wondering: when is libreoffice going to do a firefox?
[20:40] <desrt> it: take the huge bloated stuffed-with-features codebase and make a product with a radically reduced scope?
[20:42] <mdeslaur> rendering it useless for 80% of its userbase?
[20:51] <seb128> mterry, btw if you get bored nautilus bug #925503
[20:51] <ubot2`> Launchpad bug 925503 in nautilus "nautilus segfaults in gtk_ui_manager_new_merge_id()" [High,Triaged] https://launchpad.net/bugs/925503
[20:51] <seb128> is getting quite some dups as well
[20:51] <seb128> since you were on a nautilus segfault fix mood it seems ;-)
[20:53] <johan> hi seb128, around?
[20:53] <seb128> johan, hey, yes
[20:53] <johan> I'm curious about a warning I get when running my application under precise
[20:53] <johan> LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
[20:53] <seb128> tedg, ^
[20:54] <johan> tedg: traceback http://pastebin.ubuntu.com/862503/
[20:55] <johan> seb128: I also get this when importing gio; ** WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
[20:55] <johan> seb128: python -c "import gio" to reproduce
[20:56] <seb128> johan, that's one is bug #918607
[20:56] <ubot2`> Launchpad bug 918607 in glib2.0 "Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'" [Medium,Triaged] https://launchpad.net/bugs/918607
[20:56] <seb128> johan, the dbusmenu one maybe cyphermox has a clue, nm-applet was triggering it a lot, I think there is a bug about it but I can't find it
[20:58] <tedg> johan, Could you install the dbusmenu ddebs and rerun that bt?
[20:59] <tedg> I've got a guess, but I'd rather know :-)
[21:01] <cyphermox> johan: if you reuse the same menuitems in a dbusmenu as well, and the menuitem is hidden; when you try to remove it that "Trying to remove" error will show up. that's what I was running into with nm-applet
[21:01] <cyphermox> I mean, using the same menuitem/menu in a dbusmenu and elsewhere
[21:08] <johan> sure, give me a few more minutes
[21:08] <dupondje> noticed something weird with LibreOffice
[21:08] <dupondje> printing to a Windows Printer that requires auth fails in LibreO
[21:08] <dupondje> it never asks password
[21:09] <dupondje> while for example printing from evince gives a auth popup
[21:09] <Sweetshark> desrt: we wont pull a firefox. we are already stripping out abstractions that are slowing us down, but we are not yet getting incompatible. see also: http://sweetshark.livejournal.com/1550.html
[21:10] <dupondje> Sweetshark: you have an idea on that printing issue ? :)
[21:12] <Sweetshark> the libreoffice online and libreoffice android efforts will need a streamlined interface (and a quicker startup), but we wont force feed that down the throat of the userbase. Once it is evolved into a stage that people want that on the desktop too, they will get it.
[21:12] <Sweetshark> dupondje: on precise?
[21:12] <dupondje> yea
[21:13] <Sweetshark> hmm, no. dont know that one yet from the to of my head, but with 800 open issues in launchpad you sometimes lose track a bit ;)
[21:14] <Sweetshark> anyway, gotta run ...
[21:14] <dupondje> héhé :D
[21:18] <johan> how do I install ddebs again?
[21:19]  * johan found https://wiki.ubuntu.com/DebuggingProgramCrash
[21:24] <desrt> wow.  people still have livejournals.
[21:25] <johan> tedg: tedhttp://pastebin.ubuntu.com/862544/
[21:25] <johan> tedg: sorry, this is the right; http://pastebin.ubuntu.com/862544/
[21:27] <johan> cyphermox: I do a bit of magic to avoid duplication between a the items in a toolbar menu button and a normal menu
[21:28] <chrisccoulson> desrt, which mozilla guys were you talking to?
[21:28] <chrisccoulson> did you ask them to come to UDS? ;)
[21:28] <desrt> no
[21:28] <desrt> shall i? :)
[21:28] <chrisccoulson> heh
[21:28] <chrisccoulson> desrt, you should suggest it ;)
[21:30] <johan> tedg: let me know if you want more information about my application in the crash scenario or test a patch
[21:37] <kenvandine> ricotz, do you have a bzr branch for folks in gnome3 ppa?
[21:38] <ricotz> kenvandine, sorry, no
[21:38] <kenvandine> ricotz, no worries
[21:38] <kenvandine> :)
[21:38] <kenvandine> i can get iut
[21:38] <kenvandine> iut
[21:38] <kenvandine> damn!
[21:38] <kenvandine> it
[21:38] <kenvandine> :-D
[21:39] <ricotz> alright ;)
[21:44] <tedg> johan, Thanks!
[21:47] <dupondje> somebody knows a program that uses gtk printing ?
[21:49] <seb128> dupondje, you can try picking any gtk application on the ubuntu desktop I guess
[21:49] <seb128> dupondje, gedit, eog, evince, ...
[21:50] <dupondje> hmz k :)
[21:50] <dupondje> seems its really a libreoffice bug then :(
[21:50] <seb128> what is the issue?
[21:51] <dupondje> I print to a printer that is shared on a win 7 pc
[21:51] <dupondje> password protected
[21:51] <dupondje> but printing in libreoffice doesn't ask the password, so printing fails
[21:51] <seb128> does it work from i.e gedit?
[21:51] <dupondje> yep, gedit asks password after sending the print task
[21:52] <seb128> yeah, libreoffice bug then
[21:52] <dupondje> and a quite crap one :) not able to print from a office application :D
[21:52] <ricotz> dupondje, are you using the printing-dialog of libreoffice?
[21:53] <ricotz> you can switch between native and LibO dialogs in settings
[21:54] <ricotz> (or at least this is suppose to be possible)
[21:58] <seb128> ricotz, hey, sorry I was away when you pinged earlier
[21:58] <seb128> ricotz, no, I didn't deal with gstreamer0.11 yet but it's on my list ;-)
[21:59] <dupondje> hmz lets see
[21:59] <ricotz> seb128, i see -- yeah, i was hoping to draw pitti into it too
[21:59] <ricotz> ;)
[21:59] <seb128> ricotz, you pinged too later for that, try earlier tomorrow ;-)
[22:00] <seb128> pitti is starting early to he finishes early as well
[22:01] <dupondje> seb128: I disabled LibreOffice dialogs, but that doesn't change a thing
[22:01] <dupondje> not to the dialog :p not to the bug
[22:01] <ricotz> seb128, jbicha, the clutter/cogl is targetting in favor of gnome-shell, but if g-s introduces new deps like the new gnome-keryring lib gcr 3.3.90 this might get a blocker
[22:01] <ricotz> seb128, gnome-keyring was decided to keep it on 3.2.x?
[22:02] <seb128> ricotz, yes, rather because it was quite some work and some changes for no good reason than because it was an issue
[22:02] <stgraber> I'm sure we have gtk experts in the room, right?
[22:02] <seb128> no we don't
[22:03] <stgraber> :)
[22:03] <seb128> we have mostly people slackers who like to drink coffee and chat on IRC ;-)
[22:03] <seb128> having an issue?
[22:03] <stgraber> kind of, gtk main loop issues in ubiquity
[22:03] <seb128> ricotz, I doubt we will want the new cogl, clutter anyway
[22:03] <stgraber> am I wrong to assume that calling Gtk.main_quit() is going to decrement Gtk.main_level()?
[22:04] <seb128> desrt, ^
[22:04] <stgraber> I have a bit of code in ubiquity that I could summarize as:
[22:04] <stgraber> while Gtk.main_level() != 0: Gtk.main_quit()
[22:04] <ricotz> seb128, i guess a lot of people want it ;)
[22:05] <seb128> sorry that's the sort of stuff I never looked at, I don't had to deal with main_level ;-)
[22:05] <desrt> stgraber: yes
[22:05] <stgraber> and that's giving me an infinite loop because apparently in this case, calling main_quit() doesn't decrement main_level() (or from what I can see, exit at all)
[22:05] <seb128> ricotz, yeah, the world is like that, there is enough people that want anything you can suggest doing
[22:05] <desrt> stgraber: the main level is the number of nested mainloops
[22:05] <desrt> main_quit() doesn't instantly quit a mainloop.  it just marks the outer-most one to stop running when it is returned to
[22:05] <seb128> ricotz, I'm sure there is enough people who would like ubuntu to stop being active as well
[22:06] <seb128> ;-)
[22:06] <seb128> enough->lot
[22:06] <ricotz> seb128, alright, still this stuff is getting some testing and it doesnt interfere with unity
[22:07] <stgraber> desrt: hmm, ok, then I have to figure out why my main loop doesn't want to die when I tell it to ...
[22:08] <ricotz> seb128, but cogl is a bit happily bumping sonames lately which made it harder to actually begin with it
[22:08] <seb128> ricotz, it's still lot of work and we are almost a month after feature freeze
[22:08] <seb128> ricotz, also somebody needs to ensure that all the rdepends are fine with it, like our champlain version for example
[22:09] <ricotz> seb128, that's right, all the currently untouched things needs to be rebuild maybe in gnome3 ppa
[22:10] <ricotz> jbicha, ^
[22:10] <seb128> ricotz, built and runtime tested
[22:11] <stgraber> desrt: the case I have in ubiquity is a user moving between entries in a list, changing the selection exits the main loop, jump into some obscure debconf code, then start the main loop again
[22:11] <stgraber> desrt: doing that very quickly (as in, just keeping your "up" key pressed) leads in a case where the main loop doesn't want to quit
[22:12] <stgraber> desrt: any idea on how I'd debug this? (sadly redesigning the whole thing isn't on the agenda for 12.04 as weird as the whole concept might be)
[22:51] <dupondje> damn want to report libreoffice bug and apport-bug crashes now :p