[04:06] <jbicha> I wonder why nautilus doesn't like appindicator today...  fatal error: libappindicator/app-indicator.h: No such file or directory
[04:40] <TheMuso> jbicha: has the header moved?
[05:46] <BigWhale> Good morning ...
[07:06] <GunnarHj> pitti: Good morning, Martin!
[07:07] <GunnarHj> pitti: Urgent MP: https://code.launchpad.net/~gunnarhj/ubuntu/precise/language-selector/dropped-function/+merge/91770 (language installation broken)
[07:07] <didrocks> good morning
[07:14] <RAOF> didrocks: Good morning!
[07:14] <didrocks> hey RAOF :)
[07:14] <RAOF> How be you?
[07:14]  * RAOF may also have an ulterior motive; namely https://code.launchpad.net/~raof/gnome-control-center/install-gcm-on-demand/+merge/91767
[07:15] <RAOF> :)
[07:17] <didrocks> RAOF: it's quite cold here, otherwise I'm fine, thanks! :)
[07:18] <RAOF> Yeah, I hear Europe's under a kilometre of ice these days.
[07:18] <didrocks> a kilometre, at least! :)
[07:19] <didrocks> (nicely done on g-c-c-!)
[07:19] <didrocks> and you, how are you?
[07:19] <RAOF> I'm pretty good.
[07:19] <RAOF> I'll be better once that g-c-c stuff lands; asynchronous programming in C?  Why did anyone think that was a good idea? :)
[07:21] <didrocks> RAOF: do you want it to land today as well?
[07:21] <RAOF> I don't really mind if it hits the archive today.
[07:22] <RAOF> It doesn't block anything, it just fixes a bug :)
[07:22] <RAOF> Actually... maybe I should check if someone's filed a bug that this fixes!
[07:23] <didrocks> yeah :)
[07:23] <RAOF> Someone might have noticed that the calibrate button doesn't work :)
[07:27] <didrocks> heh
[07:29] <RAOF> There we go.  Now with bug-closing goodness.
[07:31] <didrocks> awesome, I'll merge it today :)
[07:33] <pitti> Good morning
[07:33] <pitti> GunnarHj: sorry about that, uploading now
[07:33] <tkamppeter> pitti, hi
[07:34] <pitti> tkamppeter: guten Morgen
[07:34] <tkamppeter> pitti, I have updated all patches, removed the upstream-merged ones and added a lot of new ones.
[07:35] <tkamppeter> pitti, now I have only a build problem.
[07:35] <didrocks> guten morgen pitti
[07:35] <tkamppeter> pitti, when Linking commandtoescpx it says
[07:35] <pitti> hey didrocks
[07:36] <tkamppeter> pitti, ../cups/libcups.so: undefined reference to `fmod'
[07:36] <pitti> tkamppeter: seems like the Makefiles are missing an -lm ?
[07:37] <tkamppeter> pitti, yes, when I updated patches I have seen that upstream has pulled a -lm at some place. Will try to edit that patch so that it re-introduces that -lm, after that report an upstream bug.
[07:38] <pitti> tkamppeter: danke
[07:50] <tkamppeter> pitti, it works, that was the actual problem. Now you replace-COMMONLIBS-by--lpthreads patch also explicitly adds -lm, as it seems that upstream has newly added the use of fmod(). The problem is not of upstream, but of your patch. Upstream probably has -lm in COMMONLIBS. So the patch simply needed updating to the state of CUPS 1.5.2. There are no real new dependencies, as libm is a standard library. I will commit this change.
[07:52] <pitti> tkamppeter: ah, thanks
[08:04] <chrisccoulson> good morning everyone
[08:05] <didrocks> hey chrisccoulson!
[08:05] <chrisccoulson> hi didrocks, how are you?
[08:06] <didrocks> chrisccoulson: I'm fine, thanks, and you, how are you?
[08:06] <chrisccoulson> didrocks, yeah, not too bad thanks
[08:26] <tkamppeter> pitti, CUPS 1.5.2 is ready for upload to Debian and Ubuntu. Can you upload quickly, as larsu wants to apply a patch to CUPS and so he needs the up-to-date state of the package.
[08:27] <pitti> tkamppeter: uh, lots of new patches
[08:27] <pitti> tkamppeter: yes, can do
[08:28] <tkamppeter> pitti, thanks.
[08:28] <pitti> tkamppeter: btw, is there a solution for the texttops problem? do you want to add a simple wrapper filter?
[08:29] <tkamppeter> pitti, I think the wrapper filter would be a good idea. It is not included yet, but to the upload anyway so that larsu can do his patch and also several other bugs get fixed.
[08:29] <pitti> *nod*
[08:29] <pitti> tkamppeter: that would be in cups-filters anyway, not in cups
[08:30] <tkamppeter> pitti, this was my thought now, too.
[08:48] <pitti> E [07/Feb/2012:08:48:25.231185 +0000] [cups-deviced] PID 28781 (usb) crashed on signal 11!
[08:48] <pitti> tkamppeter: hmm, I had hoped that the new version would magically fix that crash, but seems it doesn't :/
[08:49] <pitti> tkamppeter: (since you updated the USB patches)
[08:49] <tkamppeter> pitti, was that crash there before?
[08:49] <pitti> tkamppeter: yes, in the previous version as well
[08:49] <pitti> it happens in the test suite
[08:50] <seb128> hey
[08:50] <pitti> hey seb128
[08:50] <seb128> pitti, hey pitti, wie gehts?
[08:50] <didrocks> salut seb128
[08:50] <pitti> tkamppeter: uploading now, as that isn't a regression (but at some point we need to fix it)
[08:50] <seb128> pitti, it's meeting reminder day!
[08:50] <pitti> seb128: oh, thanks!
[08:50] <seb128> lut didrocks
[08:50] <tkamppeter> pitti, I do not get the crash, as you seem to get it reproducibly, can you investigate it and find out its cause? Thanks.
[08:51] <pitti> seb128: udisks2 1.91.0 in PPA FYI
[08:51] <seb128> pitti, great
[08:51] <pitti> tkamppeter: yes, when I run "make check", it has 19 instead of the 18 expected errors, and the extra one is that segfault
[08:52] <tkamppeter> pitti, I do not have the segfault as during build there does not happen any apport pop-up.
[08:52] <pitti> tkamppeter: no, it's not caught by apport as it's a local program, not a system one
[08:56] <pitti> tkamppeter: argh, messed up the Debian upload; need to wait a bit and upload again (just FYI, no action necessary from you)
[08:59] <rye> hi, me again with a weird unity sound indicator behavior when there is no artwork for the music - http://ubuntuone.com/5QOE36HE3Mp1MXTqKkMvP0
[09:00] <rye> can somebody check this on their machine / precise, before I submit a bug
[09:07] <jibel> rye, bug 927733
[09:07] <ubot2> Launchpad bug 927733 in indicator-sound "Mouse on coverart flushes the sound menu" [High,Triaged] https://launchpad.net/bugs/927733
[09:08] <rye> hm, it was kind of completely different to what I was searching on launchpad :)
[09:09] <rye> jibel, thank you!
[09:09] <jibel> rye, yw
[10:07] <didrocks> smspillaz: hey, how are you?
[10:08] <slomo> tjaalton: hey, any news on the patch to add the headers, etc to gst-plugins-bad?
[10:08] <slomo> tjaalton: i'd like to get it in debian soonish if possible
[10:09] <pitti> seb128: so it seems we'll get most of gnome 3.4 after all
[10:09] <seb128> pitti, hum, "after all"? we get basically what we decided at UDS
[10:09] <seb128> pitti, i.e we avoided gnome-session, gnome-settings-daemon, gnome-control-center, etc
[10:09] <pitti> seb128: hm, I thought we'd use gnome 3.2 plus glib/gtk 3.4, plus maybe some control-center backports
[10:09] <seb128> we update the platform and standalone applications
[10:09] <pitti> but seems I misunderstood
[10:10] <slomo> tjaalton: as you might've noticed i've uploaded new gstreamer packages to debian/experimental yesterday, would be a good idea to get these into ubuntu too
[10:10] <seb128> pitti, oh, well we said we would see how things go but ideally we would update all the libs and standalone softwares (gedit, eog, evince, etc)
[10:11] <Chipaca> morning, all. Yesterday morning when I arrived at work I updated and everything was fine. Yesterday evening before leaving I updated again, and now lightdm is all white, and my unity 2d looks like http://ubuntuone.com/3XHDN8BHZNLl66wwmRWdPm ; 3d unity is even worse (no panel, no nothing)
[10:11] <pitti> seb128: let's hope nautilus doesn't cause trouble (new gvfs, etc.)
[10:11] <seb128> pitti, they didn't get too crazy and they are close of their freeze so I extended a bit for i.e nautilus where the ratio fixes,crazyness was in the fixes favor by far
[10:11] <tjaalton> slomo: yes, on my plate. I'll finish it today
[10:11] <Chipaca> (i've updated just now having arrived at work again and things are still the same)
[10:11] <pitti> seb128: *nod*
[10:11] <slomo> tjaalton: thanks :) which part? the patch or getting the new packages in ubuntu?
[10:11] <seb128> pitti, shouldn't, they will be feature and ui frozen by their next tarballs and nothing crazy is coming
[10:12] <tjaalton> slomo: the patch at least
[10:12] <seb128> tjaalton, will you do the gstreamer0.10 and base syncs? they should be direct syncs I think
[10:13] <tjaalton> seb128: I can do that yes
[10:13] <seb128> tjaalton, thanks
[10:13] <slomo> tjaalton: ok :) for the new packages, this probably makes sense to get into ubuntu because these will most likely be the last gstreamer 0.10 releases (there's new core, base, good, bad, ugly)
[10:13] <tjaalton> slomo: great
[10:14] <tjaalton> slomo: so, my diff has libgstreamer0.10-plugins-bad-dev and the .install file for it. you wanted some shlibs forcing too?
[10:15] <slomo> tjaalton: yes
[10:15] <Chipaca> who should I poke to get this back to a reasonably non-broken state?
[10:16] <slomo> tjaalton: force it to =${binary:Version} or if you can to >=${binary:Version}, << ${nextUpstreamVersion}
[10:16] <seb128> Chipaca, can you pastebin a .xsession-errors from the unity-3d session?
[10:16] <seb128> Chipaca, well pastebin, u1 share
[10:16] <seb128> Chipaca, whatever suits you to make it available to others ;-)
[10:16] <Chipaca> seb128: i've got to turn off lightdm, turn on gdm, and change session from there
[10:16] <Chipaca> seb128: still useful?
[10:17] <seb128> Chipaca, well your current session will do
[10:17] <Chipaca> ok, this is unity 2d
[10:17] <seb128> let's see what is there to start
[10:18] <Chipaca> http://ubuntuone.com/7eNCeBFs9WAS7YexssdP0r
[10:18] <Chipaca> man, i love it when our stuff just works :)
[10:18] <tjaalton> slomo: ok, so if -dev Depends (= ${binary:Version}), stuff built against it will get the same deps?? kinda confused here, never done this before :)
[10:20] <slomo> tjaalton: no, you need to pass some parameter to dh_makeshlibs
[10:20] <tjaalton> slomo: ah, ok
[10:20] <slomo> tjaalton: look at gstreamer0.10's debian/rules for example
[10:20] <tjaalton> thanks
[10:21] <slomo> tjaalton: DEB_DH_MAKESHLIBS_ARGS_$(gst_lib)
[10:21] <tjaalton> I'll have a look
[10:21] <slomo> tjaalton: the -V parameter is what you need
[10:21] <seb128> Chipaca, ok, seems like you gdk pixbuf loaders are broken
[10:21] <seb128> Chipaca, did you have an upgrade issue
[10:21] <seb128> Chipaca, sudo apt-get -f install? does it say everything is ok?
[10:21] <Chipaca> seb128: no
[10:22] <Chipaca> seb128: sudo apt-get -f install says everything is ok
[10:22] <Chipaca> rickspencer3: morning!
[10:22] <rickspencer3> hi Chipaca
[10:23] <Chipaca> rickspencer3: ou est-ce bon matin maintenant?
[10:23] <seb128> Chipaca, can you run gdk-pixbuf-query-loaders and see what it says?
[10:23] <rickspencer3> Chipaca, bonjour à vous aussi
[10:23] <seb128> rickspencer3, salut
[10:24] <seb128> Chipaca, gdk-pixbuf-query-loaders | grep png
[10:24] <Chipaca> seb128: http://ubuntuone.com/7JehtyjeMecNl4wCjx0aDN
[10:24] <seb128> does that list libpixbufloader-png.so?
[10:24] <Chipaca> seb128: a bunch of 'em
[10:25] <seb128> Chipaca, hum, that seems correct...
[10:25] <seb128> Chipaca, does "eog /usr/share/themes/Ambiance/gtk-3.0/assets/scrollbar_handle_vertical.png" work?
[10:26] <Chipaca> seb128: no
[10:26] <seb128> Chipaca, what does it say?
[10:26] <Chipaca> seb128: Unrecognized image file format
[10:26] <seb128> wth...
[10:26] <seb128> Chipaca, what arch is that?
[10:26] <seb128> i386 or amd64?
[10:27] <Chipaca> i386
[10:27] <Chipaca> feh of the image works fine
[10:27] <seb128> "feh"?
[10:27] <Chipaca> this probably explains why gnome-screenshot didn't work for taking the above screenshot
[10:27] <Chipaca> zomg fast imlib2 image viewer i favor :)
[10:27] <seb128> well that's what your .xsession-errors says
[10:27] <seb128> gnome-session[2192]: Gtk-WARNING: Theme parsing error: gtk-widgets.css:1413:73: Couldn't recognize the image file format for file '/usr/share/themes/Ambiance/gtk-3.0/assets/scrollbar_handle_vertical.png'
[10:27] <seb128>  
[10:27] <seb128> it seems your png loader is borked
[10:28] <seb128> ls -lh /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
[10:28] <seb128> Chipaca, ^
[10:28] <Chipaca> -rw-r--r-- 1 root root 18K Feb  6 15:23 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
[10:28] <Chipaca> should I reinstall libgdk-pixbuf2.0-0 just in case?
[10:29] <seb128> not yet
[10:29] <seb128> I would like to figure what is wrong before workarounding it
[10:29] <seb128> others might hit the same bug
[10:29] <Chipaca> ok
[10:29] <seb128> Chipaca, so "gdk-pixbuf-query-loaders /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so" doesn't return an error?
[10:30] <Chipaca> seb128: doesn't look like it, looks like info about the loader
[10:30] <seb128> Chipaca, what about on /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
[10:30] <seb128> ls -l /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so as well
[10:30] <tjaalton> slomo: with the package revision or just upstream?
[10:30] <Chipaca> -rw-r--r-- 1 root root 5.5K Jan 25 15:05 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
[10:31] <Chipaca> seb128: also, info about the loader
[10:31] <seb128> Chipaca, $ strace eog /usr/share/themes/Ambiance/gtk-3.0/assets/scrollbar_handle_vertical.png 2>&1 | grep loaders
[10:31] <seb128> well or any png
[10:31] <Chipaca> ugh, image/vnd.adobe.svg+xml. Hate that mimetype.
[10:31] <seb128> I just pick that one because it was in your .xsession-errors
[10:31] <Chipaca> going...
[10:32] <seb128> Chipaca, do you have a /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache does it list libpixbufloader-png.so?
[10:32] <Chipaca> full trace is at http://ubuntuone.com/0ix5qyokrxTmQNzTO3vg5b
[10:32] <slomo> tjaalton: ideally it would be -V "libgstreamer-plugins-bad0.10-0 (>= binaryVersion) libgstreamer-plugins-bad0.10-0 (<< nextUpstreamVersion)"
[10:32] <slomo> tjaalton: you have to calculate/get the versions from somewhere though
[10:32] <tjaalton> slomo: yeah I got it
[10:33] <Chipaca> seb128: no actual loaders listed (just the cache -- maybe the cache is busted?)
[10:33] <Chipaca> 5819  open("/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache", O_RDONLY|O_LARGEFILE) = 8
[10:33] <seb128> Chipaca, that seems to be it
[10:33] <Chipaca> that file is empty
[10:33] <seb128> Chipaca, can you "sh -x /var/lib/dpkg/info/libgdk-pixbuf2.0-0\:i386.postinst"
[10:33] <seb128> well under sudo
[10:34] <Chipaca> that output stuff, and now i have a non-empty cache
[10:34] <seb128> ok :-(
[10:34] <seb128> Chipaca, I guess eog etc will work now
[10:34] <Chipaca> and now eog works
[10:34] <Chipaca> yep
[10:34] <seb128> ok
[10:34] <seb128> so your cache got screwed for a reason
[10:34] <seb128> but the postinst worked so it's not buggy
[10:34] <seb128> Chipaca, thanks, I'm not sure how that happened but I will watch for other reports
[10:35] <Chipaca> it's not really a cache if the system doesn't work without it, is it? :)
[10:35] <Chipaca> (but that's a longer conversation, for another day)
[10:35] <seb128> well, gtk tend to trust caching too much
[10:35] <seb128> i.e they don't go check if the datas are actually accurate
[10:35] <Chipaca> it's an easy trap to fall into -- we suffer the same thing often :)
[10:36] <seb128> ;-)
[10:36] <seb128> Chipaca, well anyway sorry for the issue, your system should be back now
[10:36] <Chipaca> seb128: anyway, thank you.
[10:36] <seb128> you're welcome!
[10:36] <Chipaca> if only getting suspend and xrandr to work again were this straightforward :)
[10:38] <rickspencer3> pitti, hey, got a sec?
[10:38] <pitti> hey rickspencer3
[10:38] <rickspencer3> I tried your little trick with rasing an import error in /usr/share/pyshared/gi/_gobject/constants.py
[10:38] <rickspencer3> but I think I did it wrong
[10:39] <pitti> rickspencer3: well, basically anything which damages the file will do it, so it's quite hard to get it wrong :)
[10:39] <rickspencer3> from gi.repository import Gtk
[10:39] <rickspencer3> caused the exception to be thrown :/
[10:39] <pitti> rickspencer3: whoops -- it's /usr/share/pyshared/gobject/constants.py
[10:40] <pitti> sorry if I gave you the other path
[10:40] <rickspencer3> :)
[10:42] <rickspencer3> thanks pitti
[10:42] <rickspencer3> basically, desktopcouch :/
[10:42]  * rickspencer3 nukes
[10:44] <tjaalton> slomo: so something like http://paste.ubuntu.com/832447/ ?
[10:45] <seb128> RAOF, hey, the new colord in debian, do you plan to sync it? ;-)
[10:45] <slomo> tjaalton: probably, but there's a debian/control.in ;) does it work as expected?
[10:45] <rickspencer3> Chipaca, may I assume that there is no gir for dekstopcouch?
[10:46] <tjaalton> slomo: hah, good point. I'll build test it
[10:46] <Chipaca> rickspencer3: I think that is a safe assumption
[10:48] <pitti> gir1.2-desktopcouch-1.0 - Glib-based API for Desktopcouch
[10:48] <pitti> ^ rickspencer3
[10:50] <rickspencer3> dang it!
[10:50] <rickspencer3> oh well
[10:53] <pitti> seb128: hm, gnome-games reintroduced a clutter dependency on arm, causing FTBFS; but I guess jbicha is going to fix it
[10:54] <seb128> pitti, I guess so, I can have a look this afternoon if he's not around
[10:55] <RAOF> seb128: Yeah, I do plan to sync it, but a couple of days stewing in sid first won't hurt it :)
[10:55] <seb128> RAOF, ok ;-)
[10:56] <RAOF> I also plan to sync mono; it's bugfixy, and it passes more ARM tests than the current archive version.
[10:57] <seb128> cool
[11:06]  * rickspencer3 kicks Gtk + Python
[11:06] <rickspencer3> no way to get the xid for a widget in Python?
[11:06] <pitti> no
[11:07] <pitti> introspectability doesn't go that far, I'm afraid
[11:07] <pitti> at least not right now
[11:07] <pitti> rickspencer3: oh, hang on, I mixed that up
[11:08] <rickspencer3> pitti, it's okay, I understand
[11:08] <pitti> rickspencer3: you can get the xid, it's GdkX11.Window.get_xid(), as in C
[11:08] <rickspencer3> Gtk doesn't care about me anymore
[11:08] <rickspencer3> what the, huh?
[11:08]  * rickspencer3 tries
[11:08] <pitti> rickspencer3: what doesn't work is using it to set a transient window
[11:08] <pitti> sorry, it's GdkX11.X11Window.get_xid()
[11:09] <pitti> (counterpart to gdk_x11_window_get_xid ())
[11:09] <rickspencer3> pitti, how would I do that for a widget?
[11:09] <rickspencer3> drawing_area. ???
[11:11] <pitti> hm, how did you do it before?
[11:11] <pitti> there should be a way to get the GdkWindow for a GtkWidget
[11:11] <rickspencer3> drawing_area.get_window().xid
[11:11] <pitti> gtk_widget_get_window ()
[11:11] <rickspencer3> I can do drawing_area.get_window()
[11:11] <pitti> right, so perhaps your_object.get_window().get_xid() ?
[11:11] <rickspencer3> tried it
[11:11] <rickspencer3> :/
[11:11] <rickspencer3> and Google is coming up empty
[11:12] <rickspencer3> I get it, Gtk doesn't want me to use it anymore, I can take a hint
[11:12] <rickspencer3> ;)
[11:12] <Riddell> pitti: I'm going out, not sure how long for but I've got exhaustion and need to relax I hope to be around for the team meeting later, please text or phone me if the world explodes
[11:12] <pitti> Riddell: ok, but should be fine
[11:14] <rickspencer3> I bet if replace the pygame surface with a webkit surface, I'll be able to go faster anyway
[11:15] <rickspencer3> I'll just need to implement some collision detection and such
[11:15] <rickspencer3> thanks for the help pitti
[11:15]  * rickspencer3 lunch -> exercise
[11:20] <pitti> rickspencer3:
[11:20] <pitti> XXXX dialog_bugreport XID 67108867
[11:20] <pitti>         print 'XXXX dialog_bugreport XID', self.w('dialog_bugreport').get_window().get_xid()
[11:20] <pitti> rickspencer3: however, you must do "from gi.repository import GdkX11"
[11:20] <pitti> rickspencer3: I suppose that's your missing bit
[11:24] <rye> hello, i was just asked about whether it is possible to unmap F10 from unity menu. I mapped the menu to F12 but global menu is still being activated and displayed during F10  keypress
[11:25] <rickspencer3> pitti, thanks that worked
[11:26]  * rickspencer3 back to lunch ;)
[11:50] <ronoc> mvo, hey, so by just creating a proxy and watching for the packagekit address the service is not launched. how can i force the package kit dbus interface to come up
[11:55] <smspillaz> didrocks: hi
[11:55] <smspillaz> didrocks: sorry about the late reply, I was just out for a walk
[11:55] <didrocks> smspillaz: no worry at all!
[11:55] <smspillaz> whats up ?
[11:56] <didrocks> smspillaz: I don't have the compiz commit handy for handling configuration, but I just want to change a key (whatever the previous value was) to a new value
[11:56] <didrocks> smspillaz: I remember the file name, but not the syntax
[11:59] <ronoc> glatzor,  hey, so by just creating a proxy and watching for the packagekit address the service is not launched. how can i force the package kit dbus interface to come up
[11:59] <ronoc> glatzor, i'm working on the package kit port of the session indicator
[12:04] <ronoc> for the even
[12:05] <smspillaz> didrocks: its the same as the ini syntax
[12:05] <smspillaz> so
[12:05] <smspillaz> - s0_foo_bar = baz
[12:05] <smspillaz> + s0_foo_bar = frobber
[12:05] <didrocks> smspillaz: yeah, but my question was: is it possible to do it, whatever the previous value was?
[12:06] <smspillaz> didrocks: oh, sorry yeah it is
[12:06] <smspillaz> if you just do
[12:06] <smspillaz> +s0_foo_bar = baz;
[12:06] <smspillaz> it will replace the old one unconditionally
[12:07] <didrocks> smspillaz: oh that works? awesome :)
[12:07] <smspillaz> http://wiki.compiz.org/Development/zero-nine/Upgrades
[12:07] <didrocks> smspillaz: thanks!
[12:07] <didrocks> ah, and a wiki page now :)
[12:07] <didrocks> thanks again smspillaz ;)
[12:07] <smspillaz> we've had that for a while, I should link it somewhere
[12:07] <smspillaz> sure, let me know if you have any troubles
[12:08] <didrocks> sure
[12:10] <tjaalton> slomo: ok it should be fine now, though I don't see an shlibs file for the dev package in the package..
[12:10] <slomo> tjaalton: then it's wrong :) it should be in the runtime package though, not the -dev package
[12:11] <tjaalton> slomo: oh ok, yes it has one
[12:11] <slomo> tjaalton: content?
[12:11] <tjaalton> libgstbasevideo-0.10 0 gstreamer0.10-plugins-bad
[12:11] <tjaalton> libgstsignalprocessor-0.10 0 gstreamer0.10-plugins-bad
[12:11] <slomo> tjaalton: wrong then :)
[12:12] <slomo> tjaalton: +DEB_DH_MAKESHLIBS_ARGS_libgstreamer0.10-plugins-bad-dev += -V "libgstreamer-plugins-bad0.10-0 (>= $(gst_version)) libgstreamer-plugins-bad0.10-0 (<< $(gst_patch_next))"
[12:12] <slomo> tjaalton: this should be DEB_DH_MAKESHLIBS_ARGS_libgstreamer0.10-plugins-bad-0 or something like that
[12:12] <slomo> tjaalton: it's not for the -dev package
[12:12] <tjaalton> yeah..
[12:13] <tjaalton> getting close though, it had all sort of fail in it :)
[12:15] <ronoc> mvo, I can't test this as I can find a way to bring up the packagkit interface - update-manager is stalling on "waiting for service to start' when i try to do an update
[12:24] <sil2100> I never thought it would be so hard to find some people willing to test out that packages - but I finally found one person
[12:24] <seb128> didrocks, btw desrt rolled a new dconf tarball yesterday, want to do the update?
[12:25] <seb128> sil2100, what packages?
[12:25] <sil2100> And it seems indeed the black rectangle artifacts are fglrx related
[12:25] <sil2100> seb128: new comiz + unity packages with the new ABI from tarballs from smspillaz
[12:26] <sil2100> I asked someone from my team to test it on an nvidia card and those artifacts were not present
[12:26] <sil2100> I already reported it to Jay yesterday
[12:26] <seb128> sil2100, weird, should be easy enough to find people to test crack packages, I'm surprised nobody on #ubuntu-unity for example stepped up to do it
[12:26] <didrocks> seb128: oh? I just cherry-picked the fix and did the tarball
[12:26] <seb128> didrocks, he rolled one yesterday evening
[12:26] <didrocks> sil2100: the question is the same than in my email, did you get those artifact with previous compiz or unity?
[12:26] <sil2100> didrocks: no, I didn't
[12:27] <sil2100> didrocks: my unity and compiz from upstream (as well as the one with HUD) work correctly
[12:27] <seb128> didrocks, I guess it means "yes" you will do the update? ;-)
[12:27] <didrocks> seb128: I'm afraid I just worked for nothing :)
[12:27] <didrocks> he didn't tag the vcs!
[12:27] <seb128> didrocks, blame desrt!
[12:27] <sil2100> One problem that I noticed in both my case and the other tester is:
[12:27] <sil2100> The panel is transparent ;)
[12:27] <tjaalton> slomo: http://paste.ubuntu.com/832521/
[12:27] <didrocks> sil2100: so, it means that this should be fixed before we roll out the new update
[12:27] <seb128> oh it's not the first time, I had to ping him about that already this cycle
[12:28] <didrocks> sil2100: or that the workaround is not working anymore
[12:28] <sil2100> didrocks: I informed Sam, and he told me to poke Jay - so I did
[12:28] <didrocks> seb128: ahah, I totally blame desrt :)
[12:28] <didrocks> sil2100: can you please file 2 bugs?
[12:28] <seb128> didrocks, yeah, me too!
[12:28] <sil2100> didrocks: ACK ;)
[12:28] <didrocks> sil2100: you can tag them <new_vession>_rc1 please :)
[12:28] <didrocks> sil2100: (against compiz)
[12:28] <didrocks> sil2100: also, I'm interested, unity is not just a rebuild for the new ABI?
[12:29] <sil2100> didrocks: ok, that's what I wanted to ask ;) How should I version those packages
[12:29] <slomo> tjaalton: almost good... now only put the shared libraries into a different package... libgstreamer-plugins-bad0.10-0 for example. and not in the main plugins package
[12:29] <didrocks> sil2100: normally, the versionning I pushed on the vcs should be fine
[12:29] <sil2100> didrocks: I was using the upstream branch for unity + fix for the ABI you gave me
[12:29] <tjaalton> slomo: alright
[12:29] <didrocks> sil2100: just on the bug report, use the "rc1" tag :)
[12:29] <didrocks> sil2100: did you try with current tarball?
[12:29] <didrocks> sil2100: the 5.2 I pushed to precise
[12:29] <didrocks> (just to have one moving ground)
[12:30] <sil2100> didrocks: I'll do an update again right now and rebuild, to make sure it happens in the most recent version
[12:30] <sil2100> Since I'm not sure if there have been any new commits from Friday
[12:30] <didrocks> sil2100: so, you used 5.2, isn't it?
[12:31] <didrocks> sil2100: please, only try with released unity version
[12:31] <didrocks> we don't want to mix compiz and unity updates
[12:31] <didrocks> we got some issues in the past with that :)
[12:31] <sil2100> didrocks: I was using unity from lp:~ubuntu-desktop/unity/ubuntu
[12:32] <didrocks> sil2100: ok, sounds good! :)
[12:32] <sil2100> didrocks: is that the right one? ;)
[12:32] <didrocks> + the additional fix
[12:32] <sil2100> Ok
[12:32] <didrocks> yeah
[12:32] <sil2100> Yes
[12:32] <sil2100> Since without the ABI fix, unityshell wasn't working at all
[12:32] <sil2100> ;)
[12:32] <didrocks> yeah, that's why I pushed a branch for you
[12:32] <didrocks> for the ABI rebuild :p
[12:32] <didrocks> sil2100: ok, so…
[12:33] <didrocks> sil2100: let me repush a branch for 5.2
[12:33] <didrocks> (remove the previous one
[12:34] <didrocks> sil2100: you didn't have to change anything from my packaging btw?
[12:35] <sil2100> didrocks: no, not really - I just added a new changelog entry so that it mentions the ABI fix
[12:35] <didrocks> sil2100: wasn't it the case?
[12:36] <didrocks> sil2100: ok, getting a branch for you, one sec :)
[12:37] <didrocks> "build-dep on latest compiz-dev and libcompizconfig0-dev for ABI break"
[12:38] <mvo> ronoc: do you have python-aptdaemon.pkcompat installed?
[12:39] <didrocks> sil2100: lp:~didrocks/unity/ubuntu-compiz0.9.7 for the unity branch, should be what you need now :)
[12:39] <didrocks> sil2100: so, to sum up
[12:39] <didrocks> please file those 2 bugs against compiz, tagged 0.9.7-rc1
[12:39] <didrocks> reply to my email (mentionning it's a regression on ATI) and CC sam, jay and thumper
[12:40]  * didrocks hopes we can get some compiz to test as soon as possible
[12:40] <sil2100> So filing them against compiz, not unity, right?
[12:40] <didrocks> sil2100: sounds ok? ^
[12:40] <didrocks> yeah, compiz for now
[12:40] <didrocks> (as unity didn't change)
[12:40] <didrocks> then, if it triggers a bug in unity, we will retarget
[12:40] <sil2100> Right indeed
[12:41] <didrocks> thanks sil2100 :)
[12:41] <sil2100> No problem ;) This is all a bit confusing to me still, but now I think I know more or less what's going on
[12:47] <didrocks> sil2100: heh, do not hesitate to ping me if you have any question :)
[12:47] <didrocks> sil2100: I hope that we can get a public testing ppa tomorrow
[12:47] <didrocks> but for that, the fglrx issue has to be worked on
[13:25] <sil2100> didrocks: should I only fill those bug on lp or also on the compiz main bugtracker?
[13:25] <didrocks> sil2100: no, only on lp right now (there is no more upstream bug tracker)
[13:25] <didrocks> pgraner: hey, I was wondering if you had any chance to test the unity package in the ppa with the crash fix?
[13:27] <pgraner> didrocks, sure did, it worked
[13:27] <pgraner> didrocks, was just about to ping you
[13:27] <didrocks> pgraner: ah nice! So I'll push that to precise today :)
[13:27] <didrocks> thanks for testing
[13:27] <pgraner> didrocks, no worries
[13:35] <cyphermox> morning
[13:37] <didrocks> hey cyphermox
[13:38] <cyphermox> hey didrocks
[13:43] <tjaalton> slomo: http://paste.ubuntu.com/832603/
[13:44] <tjaalton> slomo: also http://paste.ubuntu.com/832605/ (don't mind the header..)
[13:46] <slomo> tjaalton: there's a 0.10 too much in the package name in the shlibs file
[13:46] <tjaalton> oh
[13:46] <tjaalton> ah, right
[13:47] <slomo> tjaalton: the breaks/replaces should be for a fixed version (i.e. the version before the libraries got their own package)
[13:48] <slomo> tjaalton: the 0.10 in the package name in control.in could be replaced by @GST_API@ or something like that
[13:48] <slomo> tjaalton: other than that this looks good :)
[13:48] <tjaalton> yeah I'll fix those
[13:53] <ronoc> mvo, now I do :)
[13:54] <ronoc> mvo, should that not be in the distro by default
[13:55] <mvo> ronoc: if we use it, then yes :) i.e. when the first dependency gets added to it we will pull it in
[13:56] <ronoc> mvo, ok cool, let me be the first dependency
[13:57] <tjaalton> slomo: http://paste.ubuntu.com/832617/
[14:00] <ronoc> mvo, how do i kick this off then, an update through update-manager ?
[14:00] <ronoc> updating sources at the moment but no sign of that address on the system bus
[14:00] <tjaalton> slomo: what packages were those that could be synced?
[14:01] <slomo> tjaalton: i don't know, gstreamer0.10 gst-plugins-{base,good,bad,ugly}0.10 maybe... i think everything except good and bad can be synced, these two need manual merging
[14:02] <slomo> tjaalton: why do you use GST_DEB_ABI instead of GST_ABI?
[14:02] <mvo> ronoc: hmmm
[14:03] <tjaalton> slomo: GST_ABI is 0.10, GST_DEB_ABI is 0.10-0
[14:03] <ronoc> mvo, maybe a restart
[14:03] <ronoc>  ?
[14:04] <tjaalton> slomo: gst_deb_abi=$(gst_abi)-0
[14:04] <mvo> ronoc: meh, given that u-m is not using the compat layer you may well run into that problem that its not firing events in this case on the PK side, only on the aptdaemon side :(
[14:04] <mvo> ronoc: I will need glatzor to confirm when he is around, but let me poke at the souce a bit
[14:04] <mvo> ronoc: in what branch is your code?
[14:04]  * ronoc fetches branch
[14:10] <tjaalton> slomo: oh, now I notice there's a new patchlevel in -bad.. it'll break the patch
[14:10] <tjaalton> let me merge it first..
[14:23] <m4n1sh> didrocks: https://launchpad.net/activity-log-manager/0.9/0.9.0
[14:23] <m4n1sh> done with it finally
[14:23] <didrocks> m4n1sh: ah thanks! I was wondering if you forgot to push it this morning :)
[14:23] <m4n1sh> seif wanted to do some changed
[14:23] <m4n1sh> it was failing to build too
[14:23] <m4n1sh> plus updating README, a gazillion other files, checking 100 times if all builds are fine
[14:23] <didrocks> m4n1sh: ok, thanks! I'll upload it soon :)
[14:24] <seif> m4n1sh: i will push some final changes tonight
[14:24] <seif> didrocks: ^
[14:24] <m4n1sh> seif: will do another release soon
[14:24] <didrocks> ok :)
[14:24] <m4n1sh> seif: atleast let people test it
[14:24] <didrocks> let's push it that one first!
[14:24] <m4n1sh> time is pretty less
[14:24] <m4n1sh> yes
[14:24] <didrocks> yeah
[14:24] <m4n1sh> plus i18n is also left
[14:25] <m4n1sh> testing to make sure that it doesnt crash is the most imp thing
[14:29] <m4n1sh> didrocks: when uploaded, ping me
[14:29] <m4n1sh> blog post on the way
[14:31] <didrocks> m4n1sh: I'm on other stuff right now, but will try to do it today
[14:31] <m4n1sh> sure
[14:31] <m4n1sh> mail me or ping either
[14:31] <m4n1sh> mail works better
[14:31] <m4n1sh> manishsinha - at- ubuntu
[14:33] <didrocks> will do!
[14:33] <didrocks> thanks :)
[14:35] <ronoc> mvo, lp:~cjcurran/indicator-session/migrate-to-new-apt-api/
[14:42] <mvo> ronoc: thanks, I'm looking over it now and it appears the PK compat layer is not doing any signal emiting if the application that triggered the activity is talking to the aptdaemon API instead of the PK api, that is of course rather suboptimal
[14:43] <ronoc> mvo, oh that does not help
[14:44] <mvo> ronoc: yeah, sorry for that - so the requirements are still the same as last cycle, right? react if transaction finished and show reboot required if need and show available updates (if there are any), correct?
[14:45] <ronoc> mvo, ideally i would like to know / care about if the user is notified about new updates via command line (through apt-get), update manager, software centre ...
[14:45] <ronoc> mvo, yes
[14:45] <ronoc> mvo, at start up i need to check if updates are available
[14:46] <ronoc> mvo, and be sensitive to when that status changes
[14:46] <mvo> ronoc: ok, I think the options we have are to extend the PK compat layer to emit the right signals for the status changes
[14:46] <mvo> ronoc: the initial "what is available" should work already, right?
[14:47] <ronoc> mvo, i haven't tested it because in that bug glaztor mentions that i should wait for that signal before checking
[14:47] <ronoc> mvo, this is as far as i got
[14:48] <ronoc> mvo, i know that there was an issue before whereby i was slowing down the startup because i instantly was checking if updates are available
[14:49] <ronoc> mvo, should i wait a few minutes before checking
[14:50] <ronoc> mvo, therefore using packagekit glib lib i will check via pkclient
[14:50] <mvo> ronoc: that is what e.g. update-notifier was doing, it was using a g_timeout_add_seconds(60 or 90) call (can't remember the exact time)
[14:50] <ronoc> mvo, ok cool
[14:50] <ronoc> mvo, just to be make sure and using pkclient is fine to do this
[14:52] <mvo> ronoc: I would really like to double check with glatzor about this, could you mail him and CC me maybe? just to make sure there is no conceptual problem that I overlooked
[14:52] <ronoc> mvo, will do
[14:53] <mvo> thanks!
[14:55] <ronoc> mvo, does Sebastian work for us ?
[14:55] <ronoc> can't seem to find him in the dir
[14:56] <mvo> ronoc: no, he is a contributor
[15:19] <mandel> when executing 'gsettings list-recursively org.gnome.system.proxy' I'm getting org.gnome.system.proxy.http enabled false, does that mean that the system is not using the proxy?
[15:20] <mandel> rodrigo_, hello!
[15:20] <mandel> rodrigo_, do you know anything about the above ^
[15:21] <rodrigo_> mandel, we don't use that key anymore, you should check the actual 'host' key, if it's set, we use the proxy, if not, no proxy for httrp
[15:22] <mandel> ack
[15:29] <jbicha> good morning
[15:32] <seb128> hey jbicha, how are you?
[15:36] <seb128> pitti, do you want to update gvfs and gio-networking? ;-)
[15:37] <pitti> seb128: yep, can do; adding to TODO
[15:37] <seb128> pitti, thanks
[15:37] <pitti> bbl, supermarket
[15:38] <seb128> pitti, bug #811049 should be fixed by the gvfs update
[15:38] <ubot2> Launchpad bug 811049 in gvfs "gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try()" [Medium,Fix committed] https://launchpad.net/bugs/811049
[16:00] <jbicha> hmm maybe Ubuntu 12.04 will have a startup sound after all
[16:01] <seb128> jbicha, why?
[16:02] <chrisccoulson> oh, you're referring to the request for a sound theme designer?
[16:17] <jbicha> seb128: http://design.canonical.com/2012/02/ubuntu-sound-theme-design/
[16:19] <rye> hello again, is it possible to remove the "show desktop" from window switcher in unity3d?
[16:19] <seb128> jbicha, bah :-(
[16:19] <seb128> rye, no
[16:20] <rye> seb128, is it known why somebody needs to switch to desktop from alt-tab? Asking to make a weighted statement in case I file a bug
[16:21] <jbicha> rye: ctrl+alt+d?
[16:21] <seb128> rye, it was a much requested feature, being able to easily access you desktop
[16:21] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, seb128, tkamppeter, pedro_, desrt, agateau, Ursinha: meeting reminder in 9 mins
[16:21] <Ursinha> pitti, roger that
[16:22] <rye> seb128, hm, interesting. well, for some reason i keep confusing the xterm icon with desktop icon :-/
[16:22] <seb128> rye, https://bugs.launchpad.net/unity/+bug/924472 is a request to make it configurable
[16:22] <ubot2> Launchpad bug 924472 in unity "Add option to hide 'Show Desktop' in switcher" [Low,Confirmed]
[16:23] <seb128> rye, change one of the icons in your theme?
[16:25] <dobey> rye: you're using xterm instead of gnome-terminal?
[16:27] <rye> dobey, no, gnome-terminal, when i used terminator it was worse, i keep looking at the shapes
[16:28] <dobey> oh
[16:28] <dobey> what is the show background icon? just a rectangle with a purple area?
[16:28] <rye> hm, my screenshot tool broke
[16:28] <seb128> dobey, no, a preview of the default background
[16:29] <rye> ** WARNING **: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11. Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell was not provided by any .service files
[16:29] <seb128> with a white rectangle around a while bar
[16:29] <kenvandine> dobey, rb-ubuntuone is missing a dep on python-dirspec
[16:29] <seb128> rye, they are probably in your Images dir
[16:29] <dobey> kenvandine: it is? hrmm, ok
[16:29] <seb128> rye, the keybinding take screenshots and store them without showing the dialog since the update
[16:30] <rye> seb128, hm, is it supposed to? the Error looks not really nice
[16:30] <seb128> rye, or run gnome-screenshot -i
[16:30] <dobey> doh
[16:30] <Riddell> hi
[16:30] <seb128> rye, yes, the error is "normal", it tries to talk to gnome-shell first then fallback to the old way
[16:30] <seb128> hey Riddell, how are you?
[16:30] <pitti> jasoncwarner, Sweetshark, bryceh, chrisccoulson, didrocks, tremolux, Riddell, kenvandine, cyphermox, mterry, seb128, tkamppeter, pedro_, desrt, agateau, Ursinha: meeting time
[16:31] <seb128> rye, it should probably be quiet about it though
[16:31] <mterry> Heyo
[16:31] <Riddell> generally good but today I'm tired
[16:31] <seb128> pitti, hey
[16:31] <chrisccoulson> hi :)
[16:31]  * kenvandine waves
[16:31] <didrocks> hey
[16:31] <Ursinha> o/
[16:31] <pitti> hello everyone
[16:31] <pitti> an official welcome to Ursinha to the first Desktop team meeting with her!
[16:32] <Riddell> hi Ursinha!
[16:32] <Ursinha> \o/
[16:32] <didrocks> hey Ursinha
[16:32] <mterry> :)
[16:32] <pitti> Ursinha: FYI, we recently agreed to only have a meeting on request, so we actually don't have one on many Tuesdays
[16:32] <Ursinha> hey guys
[16:32]  * mterry waves
[16:32] <Ursinha> pitti, ah, cool
[16:32]  * agateau waves
[16:32] <seb128> oh, a mterry, hey
[16:32] <pitti> so, as you know, next thursday is THE DAY OF RECKONING
[16:32] <pitti> err, I mean
[16:32] <pitti> feature freeze
[16:33] <pitti> and http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html is still impressively large
[16:33] <pitti> so I'd like to go over a subset of specs with you to see what's on track and what's to be deferred
[16:34] <pitti> want me to start, or any general comments/questions?
[16:34] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-default-apps
[16:34] <pitti> one outstanding item here is to re-evaluate banshee
[16:35]  * desrt builds vala stuff out-of-tree
[16:35] <pitti> did anyone hear about the status of banshee-GTK3?
[16:35]  * desrt watches it not break
[16:35] <desrt> party!
[16:35] <seb128> desrt, ;-)
[16:35] <pitti> we landed the RB music store for GTK 3 yesterday, for the record
[16:35] <pitti> seb128, Laney ^
[16:35] <seb128> pitti, I didn't, check with Laney maybe?
[16:35] <desrt> seb128: actually, i'm almost more excited about the ACLOCAL_PATH fixes
[16:35] <desrt> those were in .2 but nobody ever packaged .2 so we didn't get to benefit
[16:35] <Laney> dobey already proposed a branch to remove it
[16:35] <pitti> the other is remmina/freerdp, which is currently blocked on a MIR and a new remmina release, but I think that's still on track
[16:35] <seb128> desrt, I'm glad the new version is working and built ;-) (btw middle of the meeting)
[16:36] <pitti> (even if it's a little late)
[16:36]  * desrt stfu
[16:36] <pitti> Laney: "remove"?
[16:36] <Laney> from banshee
[16:36] <seb128> Laney, the question was banshee on gtk3
[16:36] <seb128> not the store ;-)
[16:36] <kenvandine> pitti, yup, i'm filing bugs now :)
[16:36] <Laney> oh, I only sasw the immediately preceding line
[16:36] <seb128> Laney, i.e is banshee going to go gtk3 this cycle still?
[16:37] <Laney> i am not aware
[16:37] <pitti> we got a new Mono today which is said to work slightly better on ARM
[16:37]  * Sweetshark stumbles in a bit late and scans backlog.
[16:37] <Laney> directhex was at fosdem so perhaps he spoke to someone
[16:37] <pitti> anyway, just wanted to mention it
[16:37] <Laney> might be an idea to ping him in #-devel
[16:38] <pitti> ^ done so
[16:38] <rye> dobey, show desktop, terminal and terminator - http://ubuntuone.com/4SWNVankmjHeqBhi7jA7RK
[16:38] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-multi-monitor
[16:38] <pitti> that's primarily a question for bryceh, will ping him out of band
[16:38] <pitti> (I don't think he's online)
[16:38] <seb128> that one is going to be an eastern meeting thing
[16:38] <pitti> this seems to be a huge collection of "opportunity bugs"
[16:38] <pitti> so I guess it'll be half-done and should stay fornow
[16:38] <pitti> and also is bug fix-ish to a large degree
[16:39] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-text-free-boot
[16:39] <pitti> this is basically untouched so far
[16:39] <pitti> seb128: do you happen to have heard from Robert about this one?
[16:39] <pitti> it seems a likely candidate for moving to Q at this point
[16:39] <pitti> jasoncwarner_: ^ perhaps you can ask during the Eastern meeting?
[16:39] <seb128> pitti, not so much, he might be working on it but I doubt it will land this cycle
[16:40] <pitti> seb128: thanks
[16:40] <pitti> ok, let's defer that to Eastern meeting
[16:41] <pitti> moved to Q for now
[16:41] <seb128> the hard part there will be to make sure vt switch works great an all driver
[16:41] <seb128> likely not something we can test,fix this cycle
[16:42] <pitti> actually -- parts of it are simple bug fixes, moved back for now
[16:42] <seb128> but yeah, check with ROAF or robert_ancell
[16:42] <pitti> seb128: it's "text free", not "flicker free"
[16:42] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-desktop-polish
[16:42] <pitti> cyphermox, didrocks: ^
[16:42] <seb128> pitti, sorry I was thinking about desktop-p-lock-screen for those switch comments
[16:42] <pitti> I think we should keep it
[16:43] <cyphermox> pitti: getting somewhere with fixing the flashing of nm-applet :)
[16:43] <pitti> seb128: yes, getting to that (but yes, that's definitively Q at this point from my POV)
[16:43] <didrocks> agreed, it should be kept
[16:43] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-gwibber-3.4
[16:43] <pitti> kenvandine: ^
[16:44]  * pitti fixes the work items, there is no "alpha-3"
[16:44] <kenvandine> hehe
[16:44] <kenvandine> thx
[16:44] <kenvandine> the actionbox might not happen, which is blocking one of my WIs
[16:44] <kenvandine> i'll bug njpatel about that again
[16:44] <pitti> kenvandine: ok; feel free to postpone parts of it
[16:45] <kenvandine> otherwise it is in good shape
[16:45] <pitti> kenvandine: thanks
[16:45] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-lock-screen
[16:45] <pitti> at this point, I think with Robert's limited time, text-free-boot seems more important and has a better chance of being finished
[16:45] <pitti> objections to moving this to Q?
[16:46] <didrocks> seems the right thing to do
[16:46] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-quickly
[16:46] <pitti> mterry, didrocks: ^
[16:47] <didrocks> the lens template is still on track
[16:47] <pitti> my gut feeling is that the python3 parts sound hard?
[16:47] <didrocks> but will happen after FF
[16:47] <didrocks> I guess it's mostly done, mterry?
[16:47] <pitti> we still are missing quite a bunch of libs there, don't we?
[16:47] <didrocks> oh python3
[16:47] <mterry> Python3 isn't happening for P
[16:47] <didrocks> no :)
[16:47] <pitti> do we support py2 still, too?
[16:47] <mterry> Yeah
[16:47] <didrocks> we have ETOOMANY3 transition :)
[16:47] <pitti> mterry: ok, can you please postpone?
[16:48] <mterry> pitti, sure
[16:48] <pitti> mterry: BTW, we can get xid
[16:48] <pitti> mywidget.get_window().get_xid()
[16:48] <pitti> and import gi.repository.GdkX11 (won't work without it)
[16:48] <pitti> ah, it's "done" already, nevermind
[16:49] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-thunderbird-enhancements
[16:49] <pitti> chrisccoulson: ^
[16:49] <chrisccoulson> hi :)
[16:49] <pitti> chrisccoulson: is that being worked on by you or upstream?
[16:49] <pitti> the eds integration?
[16:49] <chrisccoulson> pitti - m_conley_away is currently working on that
[16:50] <pitti> gets a little tight for FF, though? but I guess we'll get new tbird versions after that anyway
[16:50] <pitti> chrisccoulson: so, should we keep or move to Q?
[16:50] <chrisccoulson> yeah, that's true
[16:50] <chrisccoulson> we should keep this one :)
[16:51] <pitti> ack
[16:51] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-zeitgeist
[16:51] <pitti> didrocks: ^ this seems well on track, but a few new features, too?
[16:52] <didrocks> pitti: yeah, I'm just pushing gnome-activity-journal right now
[16:52] <didrocks>  /!\ it's really "raw"
[16:52] <pitti> ok, so on track?
[16:52] <didrocks> but from my testing, some features are working
[16:52] <didrocks> yeah
[16:52] <pitti> thanks
[16:52] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-control-center-cleanup
[16:53] <pitti> that's a big one
[16:53]  * seb128 hides
[16:53] <pitti> we'll almost certainly have to drop stuff
[16:53] <pitti> for my part, I propose we'll keep language-selector for P instead of the region panel
[16:53] <pitti> the underlying plugin support is ready
[16:53] <kenvandine> my WI on that is trivial, i'll just knock that out today
[16:54] <pitti> but the current WIP branch doesn't do ibus configuration and we still need to sort out teh fontconfig bits
[16:54] <pitti> so it woudl still be quite a regression
[16:54] <tjaalton> slomo: http://paste.ubuntu.com/832840/
[16:54] <Sweetshark> yes, slightly OT: grekh contributed a furst few patches to LibreOffice. Awesomeness abound! ;)
[16:54] <kenvandine> scratch that, i'll do it along with the sound panel upload when it is ready
[16:54] <Sweetshark> ups
[16:54] <seb128> pitti, there is no so much there
[16:54] <seb128> pitti, we can probably drop those
[16:54] <seb128> [robert-ancell] discuss upstream dropping the screen capplet (2.6 of the google doc spec): INPROGRESS
[16:54] <seb128> well it's being discussed
[16:54] <mterry> The interesting changes for the power panel (hibernation/certification) should be postponed
[16:54] <seb128> so it's basically DONE, we didn't say we would land that
[16:55] <seb128> mterry, what about "[mterry] change the power capplet to add checkboxes to enable,disable suspend and hibernate (2.3):"
[16:55] <pitti> mterry: yes, I agree
[16:55] <seb128> and "|mterry] add a "show battery in the top bar" option to the power capplet (2.3):"
[16:55] <mterry> Oh, I can knock that out before next thursday.  /me makes note
[16:55] <pitti> seb128: I. e. we'll keep the screen capplet as it is, or we'll drop it?
[16:55] <mterry> except, should say "menu bar"  :)
[16:55] <seb128> pitti, keep it as it is
[16:55] <seb128> mterry, thanks, both changes?
[16:56] <pitti> seb128, mterry: can I ask you to update the blueprint while I go on and annoy others? :-)
[16:56] <mterry> pitti, yup
[16:56] <mterry> seb128, hm?
[16:56] <pitti> cheers
[16:56] <seb128> pitti, yes
[16:56] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-mozilla-upgrade-experience
[16:56] <pitti> chrisccoulson: ^
[16:56] <pitti> chrisccoulson: seems the plugin upgrade one works fairly well now?
[16:57] <chrisccoulson> pitti - yeah, we can close that
[16:57] <pitti> chrisccoulson: IMHO the current "plz restart me" notification is quite fine, do you think we should still work on this for p?
[16:57] <chrisccoulson> pitti - no, i don't think we need to change that for p. it would be nice to have one for plugin updates, but that's a fairly trivial task
[16:58] <pitti> chrisccoulson: so the first five are "postpone", and you add a new WI for plugins?
[16:59] <chrisccoulson> pitti - oh, the plugin one is the first item
[16:59] <pitti> chrisccoulson: ah, I see; can you please postpone/update the others?
[16:59] <chrisccoulson> yeah, sure
[17:01] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-one-conf
[17:01]  * pitti sees didrocks burst out in tears
[17:01] <mterry> :)
[17:02] <pitti> I think we can leave it for P now, for some parts which didrocks might get to in his CFT?
[17:02] <didrocks> pitti: i did some, but other teams postponed their work
[17:02] <didrocks> so I have little hope TBH :/
[17:03] <didrocks> but yeah, if I can have time at the eow
[17:03] <didrocks> I can maybe hope for ubiquity integration
[17:04] <sil2100> I'm just testing the troublesome packages on the open radeon drivers
[17:04] <seb128> sil2100, we are in a meeting
[17:04] <sil2100> Ah, ok, sorry ;)
[17:04] <pitti> https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-unity-greeter
[17:04] <seb128> sil2100, use #ubuntu-unity maybe, it's rather a topic for that channel anyway
[17:05] <mterry> So the greeter has a few features on the table
[17:05] <pitti> mterry: a messaging indicator for the greeter!?
[17:05] <mterry> pitti, heh, yeah
[17:05] <mterry> That's likely to be postponed
[17:05] <pitti> what's that all about anyway?
[17:05] <mterry> I'm finishing up my branch to fix the lightdm parts necessary to get the keyboard indicator back
[17:05] <pitti> . o O { it's by far not "light"dm any more, it's back to a full GNOME session :) }
[17:05] <mterry> So the keyboard indicator will make it
[17:05] <pitti> right, that was almost in, and only a couple of fixes away
[17:05] <mterry> pitti, well, the greeter is the heavy part
[17:06] <pitti> cyphermox: ^ what about the network indicator?
[17:06] <mterry> pitti, yeah, but I've been in test-writing hell, augmenting the fake X server
[17:06] <pitti> I guess that'd need some adaptions, as we e. g. shouldn't have per-user connections in the greeter, only system-wide ones
[17:06] <cyphermox> pitti: considering dropping that, in fact\
[17:06] <mterry> pitti, the messaging indicator is just a little icon next to names if the user's messaging indicator in their session is blue
[17:06] <cyphermox> the actual benefit isn't for the vast majority of users
[17:07] <pitti> cyphermox: right, that's what I thought, too
[17:07] <cyphermox> (e.g. vast majority probably using only one user on their system, or if not they probably don't need special networks to login either)
[17:07] <pitti> you can configure it just fine in ubiquity and the running session
[17:07] <cyphermox> I'll go ahead and update it
[17:07] <pitti> cyphermox: update == drop?
[17:07] <cyphermox> yes
[17:08] <pitti> ok, that was my list
[17:08] <pitti> thanks everyone
[17:08] <pitti> I know it's annoying, but I rather keep track of it early than going through the FFE bureaucratics
[17:08] <pitti> and I at least like to know what's going on :)
[17:09] <pitti> AOB?
[17:09] <kenvandine> pitti, indeed
[17:09] <slomo> tjaalton: i
[17:09] <slomo> tjaalton: i'm done for today, please write me a mail with the patch :) slomo@debian.org for example
[17:10] <tjaalton> slomo: ok, sure
[17:10] <seb128> pitti, thanks
[17:10] <didrocks> thanks everyone ;)
[17:10] <pitti> dobey: NB that python-dirspec is in universe, needs a MIR
[17:10] <pitti> so, thanks everyone!
[17:11] <dobey> pitti: i already did the mir, it should be approved and move over once something depends on it
[17:11]  * mterry notes that he will do a MIR sweep this week
[17:12] <pitti> dobey: ah, thanks
[17:13] <dobey> https://bugs.launchpad.net/ubuntu/+source/dirspec/+bug/913908
[17:13] <ubot2> Launchpad bug 913908 in dirspec "[MIR] dirspec" [Undecided,Fix released]
[17:13] <pitti> dobey: right, rb-u1 does now, so that part is done
[17:13] <pitti> dobey: nice, that was fast :)
[17:13] <dobey> pitti: yeah, though i see it is depwait on it now
[17:14] <didrocks> mterry: no MIR sweep! You will again assign some to me :)
[17:14] <dobey> rhythmbox-ubuntuone is depwait on python-dirspec, that is
[17:15] <mterry> didrocks, you want some?  can do
[17:15] <didrocks> mterry: be warned! you will have the gnome-activity-journal soon :)
[17:16] <didrocks> m4n1sh: speaking of which, uploaded ^
[17:16] <dobey> pitti: how do i resolve that? :)
[17:16] <mterry> :)
[17:16] <didrocks> seif: m4n1sh: so polishing now? (it's still a bit rough ;)). I tried some features that worked. However, there are tons of gtk warning on the CLI and make clean remove configure and other files (seems to be linked to make distclean) :/
[17:17] <RainCT> didrocks: Hey. Shouldn't that upload have been activity-log-manager?
[17:17] <pitti> mterry: hm, why is it fix released? it's still in universe
[17:17] <pitti> dobey: ^ FYI
[17:17] <seif> didrocks: i am on it
[17:17] <seif> didrocks: will fix the treeview stuff
[17:17] <didrocks> RainCT: is it diferent?
[17:17] <didrocks> different*
[17:17] <didrocks> seif: thanks
[17:17] <mterry> pitti, don't know.  doko uploaded it...
[17:18] <pitti> promoting again
[17:18] <RainCT> didrocks: yeah, activity-log-manager is the privacy thing, gnome-activity-journal shows you what you did each day (and is still in python)
[17:18] <pitti> mterry, dobey: ok, promoted; that should resolve the depwait
[17:18] <dobey> pitti: so i should just click retry now then?
[17:19] <pitti> dobey: no, not yet, needs a publisher run
[17:19] <didrocks> RainCT: urgh, sorry, will fix that
[17:19] <pitti> dobey: did it fail, or is it depwait?
[17:19] <dobey> pitti: depwait
[17:19] <pitti> dobey: that'll resolve itself
[17:19] <dobey> ok
[17:19] <dobey> thanks
[17:21] <m4n1sh> didrocks: activity-log-manager and gnome-activity-journal are separate apps :)
[17:21] <m4n1sh> didrocks: hey. cool
[17:22] <m4n1sh> didrocks: if you have time, can you look into src/Makefile.am CLEAN, DISTCLEAN and MAINTAINERCLEAN sections
[17:22] <didrocks> m4n1sh: ok :)
[17:22] <m4n1sh> maybe I have something messed up
[17:28] <m4n1sh> didrocks: how many binary packages did you create? I suggest two
[17:28] <m4n1sh> one for standalone and other for integration one
[17:28] <didrocks> m4n1sh: you mean, one for the cc-panel?
[17:28] <didrocks> can be, if zg is going to be used in other env
[17:28] <m4n1sh> yup
[17:29] <m4n1sh> in case it is not compiled with --with-ccpanel
[17:29] <m4n1sh> it gives only a single desktop file and alm executable
[17:29] <m4n1sh> and when compiled with --with-ccpanel
[17:29] <m4n1sh> 2 deskto files
[17:29] <m4n1sh> one executable
[17:29] <m4n1sh> and one .so file
[17:30] <m4n1sh> didrocks: .so can be in -common package, one for executable and it's desktop file, and one for  .so file and it's deskop file
[17:30] <didrocks> m4n1sh: it's a little bit too much for a small package like that :)
[17:30] <m4n1sh> yes
[17:30] <m4n1sh> I am just suggesting
[17:30] <didrocks> m4n1sh: well, if it's not compiled with --with-ccpanel, people can redo the packaging
[17:30] <m4n1sh> you know packaging better
[17:31] <didrocks> we are not gentoo :)
[17:31] <m4n1sh> lol
[17:31] <m4n1sh> but atleast make sure that the standalone executable is not installed by default
[17:32] <didrocks> oh?
[17:32] <didrocks> any reason it shouldn't ?
[17:32] <m4n1sh> it is not needed
[17:32] <didrocks> ok
[17:32] <m4n1sh> the ccpanel integration needs only .so file
[17:32] <m4n1sh> and the corrosponding desktop file
[17:32] <didrocks> ok, will separate like that then
[17:32] <m4n1sh> yup
[17:33] <m4n1sh> g-c-c integration one needs .so file and data/alm-ccpanel.desktop
[17:33] <didrocks> ok thanks :)
[17:33] <m4n1sh> didrocks: you might want to check it out before uploading
[17:33] <m4n1sh> by building in your local chroot and installing it manually
[17:34] <didrocks> m4n1sh: hum, that's already what I'm doing for every packages I have
[17:35] <m4n1sh> I am not a great packager, just learnt basics
[17:35] <didrocks> I think I can deal with my packages, but thanks :)
[17:35] <m4n1sh> seif: you need to work on the UI part and removing the glib warning. you are the treeview geek
[17:35] <seif> dude i know
[17:35] <m4n1sh> before 13th
[17:35] <seif> i am finishing something here quickly
[17:35] <m4n1sh> or else we will miss feature freeze
[17:35] <seif> i need to finish it before friday :P
[17:35] <m4n1sh> as UI improvements as not bug fixes
[17:40] <pitti> good night everyone!
[17:40] <desrt> didrocks: your defaults stuff is working now?
[17:40] <desrt> pitti: cheerio
[17:41] <didrocks> desrt: yeah, working wonderfully! thanks :)
[17:42] <seb128> 'night pitti
[17:42] <didrocks> have a good night pitti
[17:42] <desrt> didrocks: did i see you volunteering in a bug to write some documentation? :)
[17:42] <didrocks> desrt: I was afraid it was going to turn out like that :)
[17:42] <didrocks> desrt: ok, will do!
[17:42] <desrt> :D
[17:44] <seb128> hum, bug #927826
[17:44] <ubot2> Launchpad bug 927826 in unity "When a folder bookmarked in Nautilus is deleted, it doesn't disappear in the Unity quicklist inmediatelly" [Low,New] https://launchpad.net/bugs/927826
[17:44] <seb128> I wonder if nautilus or unity is to blame ;-)
[17:45] <didrocks> saw that one, not really sure TBH :)
[17:48] <tkamppeter> pitti, still there?
[17:49] <seb128> tkamppeter, he said good night a bit earlier
[17:49] <tkamppeter> seb128, thanks, so I will ask him tomorrow.
[17:50] <nessita> hello all! any advice who I can ask about GLib.spawn_async segfaulting on an updated precise install?
[17:50] <seb128> hey nessita
[17:50] <nessita> hola seb128 :-)
[17:50] <seb128> nessita, stacktrace? usually pitti if that's a pythonish issue, you can try desrt if that's a glib issue
[17:52] <nessita> seb128: hum not sure if this is in the python side or glib
[17:52] <nessita> perhaps I should try the same code snippet on C, right?
[17:52] <seb128> nessita, can you share a testcase or pastebin a stracktrace?
[17:52] <seb128> nessita, ideally yes
[17:53] <seb128> but maybe share your python code and a stacktrace to start?
[17:53] <nessita> seb128: the code snippet I'm running is http://pastebin.ubuntu.com/832910/, let me paste the output of strace
[17:53] <nessita> output of strace  is: http://pastebin.ubuntu.com/832911/
[17:54] <seb128> nessita, sorry by stacktrace I meant gdb bt
[17:54] <nessita> seb128: can do that, let me try
[17:55] <nessita> seb128: got the segfault in gdb, besides bt you want something else?
[17:55] <nessita> gdb bt: http://pastebin.ubuntu.com/832916/
[17:57] <desrt> seb128: did you ever get a chance to look at the dconf write-on-login stuff?
[17:57] <seb128> desrt, not yet, will do after feature freeze
[17:57] <desrt> (pitti's blog post just brings this back into my mind)
[17:57] <seb128> nessita, hum, quite some python code and no symbol in there...
[17:57] <seb128> desrt, http://pastebin.ubuntu.com/832910/ do you see anything wrong in there? ;-)
[17:58] <nessita> seb128: right, I may need to install the dbg packages to debug further...
[17:58] <nessita> desrt: besides the seg fault that code is triggering :-P
[18:00] <desrt> i like it!
[18:01] <desrt> it's the environment
[18:01] <desrt> drop the envp= argument and it stops crashing
[18:01] <desrt> (note that it's not necessary to do this: the current environment is already used by default)
[18:01] <nessita> desrt: wow...
[18:02] <nessita> desrt: why would passing the env make it segfault?
[18:02] <desrt> well, that's the next question :)
[18:02] <nessita> ah :-)
[18:03] <desrt> oh
[18:03] <desrt> os.environ in python is a dictionary
[18:03] <desrt> g_spawn_async() wants an array of 'KEY=VALUE' strings
[18:03] <nessita> desrt: uuuhhhhh...
[18:04] <desrt> i'm guessing something is implicitly arrayifying the dictionary (which probably results in a list of the keys, without values) and passing that
[18:04] <nessita> right
[18:04] <nessita> desrt: the crash makes sense now
[18:04] <nessita> desrt: thanks * a lot *
[18:04] <desrt> still shouldn't crash :/
[18:04]  * desrt will try to reproduce it in a more simplified situation and figure out who is crashing
[18:05] <nessita> desrt: well, it glib is asuming that a = char will be in the string, it may crash
[18:05] <desrt> nessita: no problems :)
[18:05] <nessita> if* glib is...
[18:05] <desrt> nessita: indeed
[18:05] <desrt> the backtrace seems to imply that the crash is happening in python-land though
[18:05] <nessita> seb128: THANKS you saved me like tons of debugging time (already a day debugging this)
[18:05] <desrt> so that may not be the whole story
[18:05] <nessita> desrt: need me to fill a bug or something?
[18:06] <desrt> nessita: i'm not sure which component is to blame, so i'll keep digging
[18:06] <nessita> desrt: thanks a lot, let me know if I can help somehow
[18:06] <seb128> nessita, thanks to desrt
[18:06] <desrt> will do
[18:06] <nessita> seb128: I did, but you redirected me to him ;-)
[18:06] <seb128> ;-)
[18:07] <seb128> desrt is always a sure bet ;-)
[18:18]  * didrocks waves good evening
[18:19] <desrt> didrocks: g'night
[18:19] <didrocks> have a good evening desrt!
[18:20] <desrt> nessita: fascinating.  it looks like this bug is specific to GLib.spawn_async()
[18:21] <nessita> desrt: I feel special!
[18:21] <desrt> nessita: the binding for some useful functions in glib (not gobject, gio) are hard-written because they don't have gobject-introspection support at that level
[18:21] <desrt> and there is a bug in this particular hand-written code
[18:22] <nessita> what are the chances for me hitting that...
[18:22] <desrt> 100% now that it's done ;)
[18:22] <nessita> lol
[18:22] <seb128> mterry, btw what happened to the unity-greeter post a2 release?
[18:23] <mterry> seb128, I'm waiting for the designer folks to demo the latest scrolling/look-and-feel to Mark for sign off.  didn't want to push something then have to change it immediately.  let me ping them
[18:24] <seb128> mterry, no hurry I was just wondering if you were blocked on something, I think better to land what is in if we can an do another upload later with the remaining stuff like keyboard
[18:24] <mterry> seb128, yar, I'm not blocking on keyboard.  That doesn't require any unity-greeter side changes anyway (except to uncomment the calls to lightdm)
[18:26] <seb128> mterry, ok
[18:26] <desrt> didrocks: hey!  stop working!
[18:27] <didrocks> desrt: I know, I had to fix something :)
[18:29] <desrt> nessita: bug is here, in case you are interested in following it (although it doesn't affect you anymore): https://bugzilla.gnome.org/show_bug.cgi?id=669594
[18:29] <ubot2> Gnome bug 669594 in general "bug in gspawn sequence-of-strings checking" [Normal,Unconfirmed]
[18:29] <nessita> desrt: great, thanks!
[18:32]  * didrocks really runs now
[18:59]  * desrt wonders when seb128 is going to go back from EST to CEST
[18:59]  * desrt hopes never
[19:00] <dobey> kenvandine: hrmm; switched to ItemType.GENERIC_SECRET instead of ITEM_GENERIC_SECRET in gwibber, and still no accounts showing up. did they show up for you after that?
[19:01] <kenvandine> dobey, no... that was what i told you :)
[19:01] <kenvandine> it still didn't work
[19:01] <dobey> ah ok
[19:01] <kenvandine> but it got further
[19:01] <dobey> got further?
[19:01] <kenvandine> i think there is a type not exposed
[19:02] <kenvandine> in the gir
[19:02] <kenvandine> gnomekeyring gir problem
[19:02] <kenvandine> i think
[19:02] <dobey> hrmm
[19:02] <dobey> *** glibc detected *** python: malloc(): memory corruption (fast): 0x0a8a9ba0 ***
[19:02] <dobey> fun times :(
[19:02] <kenvandine> like it gets a struct of an unknown type
[19:02] <kenvandine> for the results
[19:02] <desrt> more pygi issues?  i love it!
[19:08] <dobey> nice; yay gtk/glib/pygi :(
[19:10] <dobey> man i really do not like trying to debug memory issues in things which i apparently can't run under valgrind
[19:34] <dobey> oh yay. it's crashing in gnomekeyring :)
[19:34] <dobey> kenvandine: is gwibber-accounts doing funky multiprocess/threading insanity?
[19:39] <BigWhale> dobey, wait until you see what is gwibber doing now.. :>
[19:56] <czajkowski> evening
[19:56] <czajkowski> anyone on 12.04 know why print screen has stopped working?
[19:56] <czajkowski> I can hear the camera click noise but nothing happens
[19:57] <BigWhale> oh true
[19:57] <BigWhale> the click and the flash are here
[19:57] <BigWhale> but no save dialog ... bummer
[19:59] <desrt> nessita: thanks for the report.  it's fixed now.
[20:00] <nessita> desrt: so fast? awesome
[20:00] <desrt> nessita: will be a while before the fix is in the distro, i imagine
[20:00] <nessita> right
[20:01] <desrt> seb128 could probably be convinced to make a vendor patch for it, but i doubt it's necessary since it's very easy to avoid the problem
[20:02] <kenvandine> dobey, there is some blocking going on in the dispatcher that causes a problem for gwibber-accounts
[20:03] <kenvandine> but BigWhale and i are making the threading not suck now
[20:03] <kenvandine> rahter... suck less
[20:04] <dobey> kenvandine: i wonder if that's what is causing the crashing i'm seeing
[20:04] <BigWhale> kenvandine, hey now! It won't suck at all. :>
[20:05] <kenvandine> BigWhale, nah, it'll suck less :)
[20:05] <kenvandine> it is still python threads
[20:05] <BigWhale> you have a point there
[20:05] <BigWhale> :>
[20:07] <kenvandine> BigWhale, i think my branch is working now
[20:07] <kenvandine> 10m and no crashes
[20:08] <kenvandine> and no blocking trying to launch gwibber-accounts while doing a refresh
[20:08] <BigWhale> do push :)
[20:08] <BigWhale> my record is still 2m42s :>
[20:08]  * kenvandine removes break points before pushing :)
[20:09] <seb128> desrt, nessita: I will let pitti deal with it, he handles pygobject
[20:10] <kenvandine> BigWhale, pushed
[20:11] <kenvandine> BigWhale, in fact, i think it has been over 20m and no crashes :)
[20:11] <kenvandine> the ultimate test (besides not crashing) is opening gwibber-accounts during a refresh
[20:12] <BigWhale> I have a conflict ... wtf? I'll just rename .OTHER
[20:13] <kenvandine> now that the service is much more async, the debug logging is a bit of a disaster
[20:13] <BigWhale> kenvandine, we just have to make another logger for the threads
[20:13] <BigWhale> so it is easier to track
[20:13] <kenvandine> another added benefit here is the messages don't hit the client in one massive chunk
[20:14] <BigWhale> sort of easier
[20:14] <BigWhale> yeah they come in batches now
[20:14] <kenvandine> they trickle in more, so the model gets updated in smaller chunks and less likely to hang the UI
[20:15] <BigWhale> my UI is black?!
[20:15] <kenvandine> real    29m49.896s
[20:15] <kenvandine> and crash :(
[20:15] <BigWhale> still?
[20:15] <BigWhale> damn
[20:16] <kenvandine> no references to dee or gee
[20:17] <kenvandine> there is all the libicu stuff though
[20:17] <BigWhale> When python crashes it crashes hard. :>
[20:39] <dobey> kenvandine: so uh, do the plugins get created in threads?
[20:40] <Sweetshark> jasoncwarner_: ping?
[20:40] <kenvandine> dobey, yes
[20:40] <kenvandine> istantiated inside a thread
[20:41] <dobey> kenvandine: i guess that's the problem then. and i'm surprised it doesn't crash sooner than me clicking "Add' in the accounts dialog
[20:41] <Sweetshark> !seen jasoncwarner_
[20:41] <ubot2> I have no seen command
[20:41] <dobey> how does one grab the gdk lock these days?
[20:42] <dobey> Sweetshark: i guess it'll be a couple hours before he pops up still
[20:42] <Sweetshark> dobey: k
[20:45] <dobey> so dealing with threads and gtk+ in python these days is probably more of an atrocity than normal i guess?
[20:47] <kenvandine> dobey, we are trying to figure that stuff out now
[20:47] <kenvandine> dobey, the service plugins don't get instantiated from gwibber-accounts though
[20:47] <kenvandine> it gets the properties over dbus
[20:47] <kenvandine> which is what is hanging for you now
[20:47] <dobey> kenvandine: the gui does.
[20:48] <dobey> no, it's not hanging. well, the existing accounts loading might be hanging i guess
[20:48] <kenvandine> i don't think so...
[20:48] <dobey> what i'm getting is a crash
[20:48] <dobey> when the gui for adding an account is initialized
[20:48] <dobey> and it's crashing when it calls gnomekeyring
[20:48] <dobey> i commented out the gnomekeyring bit, and it doesn't crash
[20:48] <jasoncwarner_> Sweetshark: hey man
[20:48] <dobey> in the statusnet plug-in
[20:49] <kenvandine> the plugin doesn't get loaded but the gtk module for it does
[20:49] <dobey> right
[20:49] <dobey> and those are in threads?
[20:49] <dobey> or no?
[20:49] <kenvandine> no
[20:49] <kenvandine> those aren't
[20:49] <dobey> then why is gnomekeyring crashing there?
[20:49] <kenvandine> no idea
[20:50] <dobey> anyway, my branch is updated and pushed
[20:50] <dobey> if you run gwibber-accounts from it, and try to add a statusnet account, it crashes :(
[20:50] <Sweetshark> jasoncwarner_: have a minute?
[20:50] <jasoncwarner_> sure
[20:55]  * bryceh waves
[21:03] <jbicha> seb128: are you still around?
[21:03] <seb128> jbicha, yes
[21:04] <jbicha> seb128: libgdata only adds symbols, it's not removing anything or bumping the soname so maybe it doesn't need to be tested in the PPA first?
[21:04] <seb128> jbicha, why do you want to update it?
[21:05] <jbicha> seb128: newer gnome-documents needs it
[21:05] <seb128> hum ok
[21:13] <mterry> seb128, heyo.  After FF when I'm supposed to be doing bug fixes, if you see the occasional system settings bug that needs investigating, feel free to assign to me
[21:14] <mterry> Not that you wouldn't anyway, but just saying  :)
[21:14] <seb128> mterry, hey, system settings like gnome-control-center?
[21:14] <mterry> yar
[21:14] <mterry> seb128, since we're a little undermanned there
[21:14] <seb128> mterry, sure, can do ;-)
[21:14] <seb128> mterry, thanks for suggesting it!
[21:15] <seb128> mterry, otherwise I try to keep http://status.qa.ubuntu.com/reports/ubuntu-desktop/precise.html filed
[21:15] <seb128> so feel feel to pick stuff there and assign them to you
[21:16] <mterry> seb128, ah yes.  :-/  That damned list that never goes down
[21:16] <mterry> I like how rls-p-tracking bugs are on same page now
[21:16] <seb128> mterry, you can blame chrisccoulson, he spams it from firefox testsuit issues :p
[21:17] <seb128> mterry, but I've also something to do with it, I'm taking care of refilling it in case somebody gets bored and want to grab a bug, it would be a shame if the list was empty in that case ;-)
[21:54] <dobey> kenvandine: can we ship crashy gtk3 gwbiber-accounts for feature freeze, and then fix it afterward? ;)
[21:55] <kenvandine> we can always request a FFE
[21:55] <kenvandine> don't know if we'll get it :)
[21:55] <dobey> right
[21:56] <dobey> i'd like to fix the layout issues, but it's hard when keyring is crashing :(
[21:56] <dobey> i wonder if it's crashing because of threads or because libgnomekeyring is broken
[21:57] <kenvandine> i think it is libgnomekeyring being broken
[21:57] <kenvandine> but i can't prove it
[21:58] <RAOF> libgnomekeyring will die if you try to access it from anything but the main thread.
[21:59] <RAOF> This is a stupid behaviour change a couple of releases ago; it used to work fine.
[22:02] <kenvandine> gwibber-accounts itself isn't doing any threading
[22:04] <seb128> RAOF, it's not a behaviour change as it, they started using libdbus which has that issue
[22:04] <RAOF> Well, from the point of view of all my keyring-using apps it *was* an annoying behaviour change :)
[22:05] <seb128> indeed
[22:05] <seb128> I remember the cycle where it landed the "fun" it was to debug
[22:05] <seb128> kenvandine probably remembers as well :p
[22:05] <dobey> well, just because everything locked up solid using 100% cpu doesn't mean it was a behavior changes ;)
[22:05] <kenvandine> grr
[22:05] <kenvandine> too well
[22:05] <kenvandine> haha
[22:05] <dobey> yes we remember it well
[22:06] <kenvandine> dobey, so accounts doesn't use threads, but there is code in there that uses the gwibber.microblog.util.keyring module
[22:06] <kenvandine> which does the global locking stuff
[22:06] <dobey> global locking as in GIL?
[22:06] <kenvandine> perhaps since this is executed independently, it should be copied for accounts use
[22:07] <kenvandine> that was the fix for that 100% cpu use
[22:07] <dobey> oh no
[22:07] <dobey> it's nasty ctypes hack
[22:07] <seb128> cyphermox, I've dupped the bug you reassigned to libappindicator from bug #903200
[22:07] <ubot2> Launchpad bug 903200 in libappindicator "underscore in network names disappear when entering more networks" [Medium,Triaged] https://launchpad.net/bugs/903200
[22:07] <seb128> cyphermox, it should maybe be tracked for precise
[22:08] <kenvandine> dobey, yup... worked great :)
[22:08] <kenvandine> pitti rocked it!
[22:08] <kenvandine> :-D
[22:08] <kenvandine> so that helps for the service
[22:08] <kenvandine> but we really don't need that for accounts
[22:09] <chrisccoulson> i'm so glad that my messaging indicator isn't changing colour for bug mail now :)
[22:10] <dobey> kenvandine: hrmm, i don't see where accounts is using it
[22:10] <kenvandine> dobey, magic
[22:10] <kenvandine> look in the gtk modules
[22:10] <jasoncwarner_> RAOF bryceh TheMuso anything for meeting? https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-02-07
[22:11] <kenvandine> dobey, oh
[22:11] <kenvandine> it isn't :)
[22:11] <kenvandine> so that should rule out hacks and threading issues
[22:11] <TheMuso> jasoncwarner_: Not from me.
[22:11] <dobey> well, i wouldn't rule anything out yet :)
[22:11] <kenvandine> dobey, hehe :)
[22:12] <RAOF> jasoncwarner_: Nor from me.
[22:12] <dobey> for all i know there's an "import oh.hi.multiprocessing" hidden somewhere :-/
[22:12] <kenvandine> dobey, not in my branch :)
[22:12] <kenvandine> we are killing that shit with a very big axe
[22:13] <dobey> heh
[22:13] <kenvandine> looks like killing off the use of pycurl too
[22:13] <dobey> maybe merging the two branches just fixes it then ;)
[22:13] <dobey> though i'm sure there's conflicts, and i really don't want to deal with that
[22:14] <dobey> well, first problem; why is it not even loading the accounts
[22:14] <dobey> wtf.
[22:15] <kenvandine> dobey, when i tried that the other day, it wasn't getting a valid result from the keyring
[22:15]  * kenvandine needs to run, be back in a couple hours
[22:15] <kenvandine> :)
[22:16] <bryceh> heya jasoncwarner_
[22:17] <jasoncwarner_> hey bryceh feeling better?
[22:17] <bryceh> jasoncwarner_, pitti had asked about the multimonitor spec this morning; to answer, yes, the work items really just bugs we want to focus on, not anything FF-critical
[22:18] <bryceh> jasoncwarner_, still not 100% but back to work and drinking fluids
[22:19] <bryceh> jasoncwarner_, I meant to do another run through to test the bugs specific to unity last week, but got sidetracked into other bugs and didn't get to it
[22:19] <bryceh> jasoncwarner_, the remaining X bugs on that blueprint are mostly intricate/difficult things that may not fit in this cycle but I'd like to keep working on them and hopfully get a few knocked off
[22:20] <bryceh> working on an arrandale-specific dp/docking station MM issue today
[22:21] <jasoncwarner_> bryceh: thanks...how is mm and projectors looking right now? saw tim tweet some frustrtaions about projectors last night (haven't gotten specifics yet)
[22:21] <bryceh> hmm, missed that
[22:22] <bryceh> jasoncwarner_, again, I haven't had a chance to do a run through of all the tests again like I did pre-christmas so can't give an accurate comparison yet.  However judging from the bug queue things don't look too bad
[22:23] <bryceh> either that, or folks haven't been reporting bugs ;-)
[22:25] <achiang> micahg: does firefox depend on libnss? it's not listed explicitly in the dependencies but i'm wondering if i'm missing something...
[22:25] <micahg> achiang: no, it uses an internal copy
[22:27] <achiang> micahg: ok, thanks. (and isn't that against policy?)
[22:28] <micahg> achiang: well, it's updated every 6 weeks and for any CVEs, so it's manageable
[22:28] <achiang> micahg: got it, thx
[23:24] <jbicha> hmm, the new gnome-documents looks bad in Ambiance but I guess I'll push anyway
[23:24] <jbicha> can't very well report bugs for problems that aren't in Ubuntu yet