[02:33] <chrisccoulson> ooh, pretty please say it is still marked as incompatible: https://plus.google.com/u/0/108611501090787019364/posts/MQ6CPFX3jme :)
[02:33]  * chrisccoulson has fingers crossed
[06:28] <pitti> Good morning
[06:28] <pitti> tkamppeter_: ah, nice
[06:33] <didrocks> good morning
[06:34] <pitti> hey didrocks
[06:34] <tkamppeter> pitti, hi
[06:35] <didrocks> good morning pitti
[07:13] <pitti> didrocks: would you mind uploading nux to precise for bug 754565? then we can release the SRU
[07:13] <ubot2> Launchpad bug 754565 in unity "Regression: shift+click on a launcher icon to open a new application instance gone" [Medium,In progress] https://launchpad.net/bugs/754565
[07:13] <pitti> didrocks: also, do we actually need teh unity task there, too?
[07:13] <didrocks> pitti: hum, but there was no test for it
[07:14] <pitti> didrocks: hm, interesting case -- it went through SRU verification, but no formal test
[07:14] <didrocks> pitti: I mean, no test that will ensure that the quicklist regression won't happen again
[07:14] <pitti> and there's already an upstream release out there
[07:14] <pitti> would be nice to have a test for this, of course
[07:16] <didrocks> pitti: the nux part is already in ubuntu btw, before the final release
[07:16] <didrocks> pitti: the unity part is still not reviewed, because of no test
[07:16] <pitti> didrocks: oh? but we have an SRU for that
[07:16] <didrocks> pitti: the nux part should be rather fix released, fixing
[07:16] <didrocks> hum, really?
[07:16] <pitti>        nux | 1.14.0-0ubuntu1 |       oneiric | source
[07:16] <pitti>        nux | 1.16.0-0ubuntu1 | oneiric-proposed | source
[07:16]  * didrocks just checked dates
[07:16] <pitti> which points to that bug
[07:16] <pitti> but we don't have 1.16 in precise
[07:17] <didrocks> pitti: let me check
[07:18] <didrocks> pitti: ok, so this particular fix for nux is already in oneiric (not proposed)
[07:18] <didrocks> pitti: the milestone says "SRU1" because it was planned to have the unity fix for SRU1
[07:18] <didrocks> which didn't happen
[07:19] <didrocks> pitti: are we ok pushing nux to precise? are the alpha1 iso already done?
[07:19] <pitti> didrocks: so https://launchpad.net/ubuntu/+source/nux/1.16.0-0ubuntu1 points to a wrong bug then?
[07:19] <didrocks> pitti: yeah, my script collects "fix committed" regarding the milestone
[07:19] <pitti> didrocks: no, not done yet, but these will most likely be the final images
[07:19] <pitti> so uploading it tomorrow would be better
[07:19] <didrocks> pitti: as upstream didn't set it to "fix released", it's been collected again, fixing it
[07:19] <pitti> didrocks: so should I remove 1.16 from oneiric-proposed then?
[07:20]  * pitti doesn't know what to do with this then
[07:20] <didrocks> pitti: no, 1.16 fixes some rendering issues that are interested (and a potential crash)
[07:21] <didrocks> pitti: I think it's been tested for long enough in -proposed to be pushed in both oneiric and precise
[07:21] <pitti> ok; right, a lot of people regression-tested it by merely using it for a long time
[07:21] <didrocks> pitti: sorry for the confusion, I was thinking about another fix the "first time quicklist isn't active", which is a hot topic
[07:22] <didrocks> pitti: yeah, that's why I think it's fine for this one
[07:22] <didrocks> pitti: but, then, we are blocking any SRU fix to have usptream tests
[07:22] <didrocks> (as we need to push in precise)
[07:22] <didrocks> pitti: should I push something like 1.16.0-0ubuntu2 in precise? (it's still the old uploads when I though you were copying the package)
[07:23] <pitti> yes, that works
[07:23] <didrocks> ok, will do tomorrow then!
[07:23] <pitti> merci!
[07:23] <didrocks> de rien :)
[08:44] <rodrigo_> morning
[08:55] <didrocks> good morning rodrigo_
[08:56] <rodrigo_> hi didrocks
[09:00] <pitti> hey rodrigo_, how are you?
[09:00] <rodrigo_> hi pitti
[09:16] <seb128> hey
[09:23] <pitti> bonjour seb128
[09:23] <seb128> hey pitti, how are you?
[09:24] <pitti> seb128: quite fine, thanks! was happy that nothing blew up over the night
[09:24] <seb128> ;-)
[09:24] <pitti> bug 898040 really sucks, but nothing we can fix for a1
[09:24] <ubot2> Launchpad bug 898040 in ubiquity "Ubiquity crashed while installing Lubuntu Precise (dup-of: 894768)" [Undecided,Incomplete] https://launchpad.net/bugs/898040
[09:24] <ubot2> Launchpad bug 894768 in linux "Installation randomly fails with: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 621, in copy_file targetfh.write(buf) IOError: [Errno 22] Invalid argument " [High,Triaged] https://launchpad.net/bugs/894768
[09:24] <seb128> pitti, yeah, I see that you are fighting with this one since yesterday
[09:25] <seb128> is that a kernel bug then?
[09:25] <pitti> actually already way before that :)  yes, kernel bug
[09:29] <didrocks> salut seb128
[09:29] <seb128> lut didrocks, ca va ?
[09:30] <didrocks> seb128: ça va ça va, et toi?
[09:30] <seb128> ca va bien ;-)
[09:30] <didrocks> needing a reboot, brb
[09:33] <pitti> seb128: can you think of any visible change in precise that we sohuld mention for a1?
[09:33] <pitti> I have rhythmbox, apport crash reporting, and admin->sudo now
[09:35] <seb128> pitti, let me think, but I guess out of those you mentioned no, we had no dx uploads at all, no GNOME update, no lightdm update
[09:35] <pitti> right
[09:35] <pitti> just loads of fixes
[09:35] <pitti> seb128: ok, thanks
[09:35] <seb128> yw
[09:44] <seb128> RAOF, we are in 2011 ;-) (your new unity tests are copyrighted 2010 ;-)
[09:47] <pitti> we should _so_ write tests for correct copyright headers!
[09:48] <pitti> RAOF: but if you still haven't adapted to 2011, don't bother any more; start with 2012 right away :)
[09:51] <Sweetshark> pitti: we had tests like that in OpenOffice.org once. They broke whenever you changed something (even the copyright year) ....
[09:52] <Sweetshark> pitti: luckily, we will never use those tests again in LO 'officially'. even better we use the two other test suites that actually make sense by now.
[09:54] <pitti> bbl
[10:07] <zyga> does anyone know how to stop automount on oneiric?
[10:23] <seb128> doh, I can see the rickspencer3's whip on us :p
[10:23] <rickspencer3> hi seb128 ;)
[10:23] <rickspencer3> no whip cracking
[10:23] <seb128> hey rickspencer3 ;-)
[10:28] <pitti> hey rickspencer3
[10:28] <rickspencer3> hiya pitti
[10:29] <pitti> oh, rickspencer3 assigning a bunch of bugs :)
[10:29] <rickspencer3> sorry pitti
[10:29] <rickspencer3> I figured you weren't busy enough
[10:30] <pitti> rickspencer3: no need to be sorry, appreciated
[10:33] <rickspencer3> hmmm?
[10:34] <rickspencer3> pitti, seb128 for a bug in indicator-power ... who do I assign that to?
[10:34] <rickspencer3> Dx Team, tedg, someone else?
[10:34] <seb128> rickspencer3, ted
[10:35] <pitti> rickspencer3: jjardon seems to do most of the commits
[10:35] <seb128> pitti, he stopped contracting for dx around UDS
[10:35] <seb128> so ted is a better choice
[10:35] <seb128> he will dispatch if needed
[10:35] <seb128> I think
[10:35] <pitti> ah
[10:36] <seb128> rickspencer3, it's that the bug you pointd on #ayatana you can probably assign it to TheMuso
[10:36] <rickspencer3> seb128, I did both ;)
[10:37] <seb128> he fixed a few of the "indicators don't have a11y description" bugs already I think
[11:11] <pitti> rickspencer3: I mangled bug 891688 enough now; it's mostly cosmetical, so I just debugged it, sent it to upstream, and unassigned
[11:11] <ubot2> Launchpad bug 891688 in util-linux "mount -o remount always appends options to /etc/mtab even if they already exist" [Medium,Triaged] https://launchpad.net/bugs/891688
[11:11] <rickspencer3> thanks pitt
[11:11] <rickspencer3> pitti, thanks pitti ;)
[11:38] <seb128> pitti, the gnome-control-center datetime panel under unity doesn't use libgweather (just for info)
[11:38] <pitti> seb128: oh, what does it use then?
[11:38] <seb128> pitti, it does use http://geoip.ubuntu.com
[11:38] <seb128> i.e same as ubiquity
[11:39] <pitti> seb128: so it ships a snapshot of that database then?
[11:39] <seb128> pitti, no, you need to be online for it to work I think
[11:39] <seb128> he does online queries
[11:39] <pitti> I thought I changed my time zone in the plane back then
[11:39] <seb128> well you probably add different tz defined and stored and switched between those?
[11:40] <seb128> the completion thing is using geoip for sure, I've been looking at some of the bug with mterry previous cycle
[11:40] <pitti> I added Orlando on the flight there
[11:40] <seb128> but maybe they do cache some of the datas
[11:41] <seb128> pitti, well I'm unsure about the map
[11:41] <seb128> pitti, but the "add a location" in the second tab is using the geoip stuff
[11:41] <seb128> I would guess that the text entry on the first tab does the same
[11:42] <seb128> pitti, what I'm sure is that it doesn't use libgweather, we had that discussion when they designed the datetime stuff, they prefered to use the geoip database
[11:43] <pitti> seb128: ok, thanks for letting me know
[11:43] <seb128> well that was a "for info" in any case, nothing important
[11:43] <seb128> yw ;-)
[12:24] <rodrigo_> mvo, https://code.launchpad.net/~rodrigo-moya/system-service/fix-877088/+merge/83932
[12:32] <didrocks> hum, bzr regressed tarmac badly in precise
[12:32] <didrocks> API changes it seems
[12:33]  * didrocks had to reinstall the older bzr for now
[12:38] <mvo> rodrigo_: thanks a bunch! I check it out (in a phnecall currently)
[12:38] <rodrigo_> mvo, ok, no hurry, moving to other stuff now, so take your time :)
[12:38] <mvo> ok
[12:59]  * rodrigo_ lunch, bbl
[13:23] <seif> didrocks, which gedit will u guys be using
[13:23] <seif> ?
[13:38] <didrocks> seif: 3.2 probably
[13:38] <didrocks> we try to stay on a stable platform for the LTS
[13:54] <seif> didrocks, hmmmmmm
[13:54] <seif> didrocks, my latest plugin (the dash) works against trunk
[13:55] <seif> did not try against 3.2
[13:55] <seif> although wait
[13:55] <seif> i am using 3.2
[13:55] <seif> shit
[13:55] <seif> hehehe
[13:55] <seif> its working
[13:55] <seif> anyhow it went upstream to 3.3 now
[13:58] <didrocks> seif: nice! :)
[13:58] <didrocks> seif: it's not the datasource right, it's a independent plugin?
[14:01] <seif> yeah
[14:01] <seif> the datasource is in gedit
[14:01] <seif> its a softdependency
[14:01] <seif> just compile gedit against zeitgeist
[14:01] <seif> :)
[14:15] <didrocks> yeah, that's what we have :)
[14:15] <didrocks> seif: not quite sure how to get your dashboard though
[14:17] <didrocks> seif: just opening gedit doesn't give me anything weirdly, there
[14:19] <seif> didrocks, there is a plugin
[14:19] <seif> wait
[14:19] <seif> let me pull it for you
[14:19] <didrocks> seif: indeed, the datasource one
[14:42] <dobey> desrt: ping; can you accept my joining ~upstream on launchpad? :)
[14:43] <desrt> dobey: granted :)
[14:43] <dobey> thanks
[14:46] <dobey> huzzah; now lp:glib points at the right thing and isn't 2.5 years old
[14:47] <desrt> oh.  this problem again.
[14:48] <pedro_> kenvandine, when you have some time, may you please have a look to bug 304889 ?
[14:48] <ubot2> Launchpad bug 304889 in telepathy-idle "Does not use system proxy settings" [Medium,Confirmed] https://launchpad.net/bugs/304889
[14:48] <kenvandine> pedro_, sure
[14:48] <pedro_> kenvandine, thanks!
[15:17] <dobey> can we ship gnome 2.32 as the version for precise?
[15:18] <seb128> dobey, no?
[15:22] <desrt> dobey: I LOVE IT
[15:22] <dobey> desrt: gnome 2.32?
[15:22] <desrt> the idea of shipping it for precise
[15:23] <dobey> stable platform where things actually work, ftw.
[15:24] <desrt> gnome needs to shake things up from time to time to keep y'all on your feet
[15:24] <desrt> can you blame us?
[15:24] <dobey> upstreams being inconsiderate pain in my side, ftl.
[15:27] <mdeslaur> rodrigo_: sorry about that
[15:28] <rodrigo_> mdeslaur, no problem :)
[15:28] <mdeslaur> rodrigo_: I apparently lack caffeine this morning :P
[15:28] <rodrigo_> :D
[15:35] <seb128> seif, didrocks: gedit version> that's not really decided, we default to stay on 3.2 but we said we would visit mid-cycle standalone softwares to see which ones we would benefit from upgrading and pick a few useful ones most like
[15:35] <seb128> seif, didrocks: things like eog, gedit, etc are good candidates for things we might be able to upgrade if there is a good reason to do so
[15:36] <seif> there are no big canges from 3.2 to 3.4
[15:37] <seif> didrocks, do u use gedit urself
[15:37] <seif> ?
[15:38] <seif> didrocks, git@github.com:seiflotfy/gedit-dashboard.git
[15:38] <seif> use the dashbaor dbranch
[15:38] <seif> my plgun is in there
[15:38] <seb128> seif, well, we are waiting to see what comes in the cycle
[15:38] <seif> my plugin :P
[15:38] <dobey> seif: get a bigger keyboard, or smaller fingers ;)
[15:38] <seif> it should be pushed upstream today
[15:39] <didrocks> seb128: hum, but this is not in the gedit we have,  isn't it? so let's wait to see if we upgrade :)
[15:39] <seif> dobey, will do
[15:39] <seb128> seif, like when gtk gets the shell menu thing application will start using the api, we need to see how that fits with unity, we need also to make sure we will upgrade gtk before considering gedit
[15:39] <seif> oki doki
[15:39] <seif> my patch works on 3.2 though
[15:39] <seif> :P
[15:39] <seb128> didrocks, right, I was just replying to "<didrocks> seif: 3.2 probably"
[15:39] <seif> i have gedit 3.2 installed and i use my plugin with it
[15:39] <seif> dobey, sir yes sir
[15:39] <seb128> didrocks, seif: well in this case it seems it's easier to just backport the patch since that should work fine
[15:40] <seif> yeppers
[15:40] <seif> :)
[15:55] <nessita> hello everyone! /me is back from holidays :-)
[15:55] <nessita> seb128: hi there :-) is there anything else I need to do to bug #891192?
[15:56] <ubot2> Launchpad bug 891192 in ubuntu "Please sponsor the proposed qt4reactor packaging branch" [Undecided,New] https://launchpad.net/bugs/891192
[15:57] <didrocks> hey nessita!
[15:57] <nessita> hey didrocks! how is it going?
[15:58] <seb128> hey nessita
[15:58] <didrocks> nessita: I'm fine, thanks. Yourself? how were your holidays?
[15:58] <seb128> nessita, no, you just need somebody motivated to do review and sponsoring, I've to admit I stayed away from it because it has qt in the name and I've no clue about qt
[15:59] <nessita> seb128: but the one doing the review has to review the source code? I though the review was about packaging only
[16:00] <seb128> nessita, no, but better to make sure that the stuff build and works as it should ;-)
[16:00] <nessita> didrocks: my holidays were great! I'm very happy I took them, I realized I needed them more that I thought
[16:00] <nessita> seb128: I see. Anyone in particular you recommend for me to chase? :-)
[16:00] <didrocks> nice :)
[16:07] <seb128> nessita, try mdeslaur maybe, he's patch pilot today
[16:07] <seb128> nessita, https://www.google.com/calendar/embed?src=6k1e5rq45m1bdqq0n1ge3oqaok@group.calendar.google.com&ctz=Europe/Berlin&gsessionid=OK
[16:08] <seb128> nessita, or mterry tomorrow if that doesn't work with mdeslaur today
[16:09] <nessita> seb128: thanks :-)
[16:09] <seb128> nessita, yw ;-)
[16:40] <seb128> kenvandine, hey, did you see bug #886056?
[16:40] <ubot2> Launchpad bug 886056 in empathy "Cannot respond to friendship requests from Empathy" [High,Confirmed] https://launchpad.net/bugs/886056
[16:43] <kenvandine> yup
[16:44] <kenvandine> i am going to add that
[16:45] <kenvandine> i think friday i am going to spend hacking on tp-indicator, so probably have it done then
[16:48] <lool> Hey there
[16:49] <lool> gnome-desktop FTBFSes on armhf due to missing libs on the linker command:
[16:49] <lool> .libs/gnome-desktop-thumbnail.o: In function `gnome_desktop_thumbnail_factory_generate_thumbnail':
[16:49] <lool> /build/buildd/gnome-desktop-2.32.1/libgnome-desktop/gnome-desktop-thumbnail.c:881: undefined reference to `floor'
[16:50] <lool> we have a 2.x source package, but there are 3.x sources available, are these not ok to include in Ubuntu for some reason?  (I know we're in freeze of course)
[16:53] <lool> Ok, I see there's a gnome-desktop3 source; will update the gnome-desktop watch file
[16:54] <micahg> lool: that's due to this change: http://mail.gnome.org/archives/desktop-devel-list/2011-August/msg00236.html
[16:55] <lool> Likely indeed
[16:56] <seb128> kenvandine, thanks, can you comment on the bug saying you will work on it?
[16:56] <lool> still some sources to port from libgnome-desktop-dev
[16:56] <lool> banshee gnome-desktop-sharp2 gnome-launch-box gnome-mag gnome-python-desktop icewm libdesktop-agnostic libslab mistelix unity
[16:56] <lool> surprized about unity though
[16:56] <seb128> lool, is there any reason armhf is any different from other archs there or did we just didn't test rebuild since?
[16:56] <seb128> lool, gnome-desktop is gtk2, gnome-desktop3 is gtk3
[16:56] <lool> seb128: I don't think it differs on this, probably would appear on other arches
[16:57] <seb128> lool, the world is not going to be ported to gtk3 in a year, I guess we will keep both for a while ;-)
[16:57] <lool> seb128: Yup; the number of source packages to port is relatively small it seems
[16:58] <seb128> lool, well, one is enough, you probably remember gtk1 and gnucash ;-)
[16:58] <lool> haha
[16:58] <lool> seb128: unity is staying gtk2 for LTS?
[16:58] <seb128> lool, no, unity is gtk3 since oneiric
[16:58] <mdeslaur> @pilot out
[16:59] <seb128> lool, what keep gtk2 on the CD is basically firefox and libreoffice (and some small stuff like openssh, xdg-user-dirs, etc)
[16:59] <mdeslaur> gah
[16:59] <seb128> mdeslaur, wrong channel :p
[16:59] <mdeslaur> seb128: yes :P
[16:59] <seb128> mdeslaur, did you help nessita btw? ;-)
[16:59] <mdeslaur> seb128: I took a look, but I'm not sure about the licensing issue there.
[17:00] <nessita> mdeslaur: what do you mean?
[17:00] <lool> seb128: Hmm unity bdeps on both libgnome-desktop-dev, and libgnom-desktop-3-dev, ?
[17:01] <mdeslaur> nessita: I'm not enough of a licensing expert, someone will need to see if we can ship qt4reactor which is MIT with twisted which is MIT and pyqt which is GPL
[17:01] <seb128> lool, seems like a packaging bug, blame didrocks :p
[17:01]  * lool phones didrocks immediately
[17:02] <seb128> ;-)
[17:02] <didrocks> what what? :)
[17:02]  * didrocks backlogs
[17:02] <seb128> didrocks, you have a call
[17:02] <lool> didrocks: unity bdeps on both libgnome-desktop-dev, and libgnom-desktop-3-dev,
[17:02] <seb128> didrocks, pick up the phone, it's lool, he's unhappy ;-)
[17:02] <nessita> mdeslaur: any idea who can know about that?
[17:02] <didrocks> lool: oh, how rude! :)
[17:02]  * didrocks checks
[17:03] <mdeslaur> nessita: I was just trying to figure that out :)
[17:03] <mdeslaur> nessita: I was told to ask in #ubuntu-release
[17:03] <pitti> good night everyone!
[17:03] <nessita> mdeslaur: joining so I can learn as well :-)
[17:03] <didrocks> hum hum, indeed
[17:03] <seb128> 'night pitti
[17:03] <nessita> bye pitti!
[17:03] <didrocks> pitti: have a good night pitti :)
[17:04] <didrocks> lool: ok, fixed :)
[17:05] <lool> didrocks: thanks  :-)
[17:06] <didrocks> lool: yw, but 2 is better than none, isn't it? :)
[17:07] <seb128>  /msg didrocks, the trick to get lool back doing desktop work is working
[17:07] <seb128> ups :p
[17:07] <lool> hehe
[17:07] <didrocks> seb128: writing to me in english? hard to believe :p
[17:07] <seb128> ;-)
[17:49] <micahg> can someone look into this please: https://bugs.launchpad.net/bugs/897952, I'm happy to provide more info
[17:49] <ubot2> Launchpad bug 897952 in dbus "dbus-daemon uses a large amount of CPU" [Undecided,New]
[17:50] <micahg> between that an zeigeist, I'm running at least 1 CPU all the time
[17:50] <micahg> s/CPU.core/
[17:54] <didrocks> have a good night everyone!
[17:58] <seb128> micahg, can you use dbus-monitor to see what is spamming the bus?
[17:59] <seb128> micahg, could be bug #774071 (indicator-datime)
[17:59] <micahg> checking
[17:59] <ubot2> Launchpad bug 774071 in indicator-datetime "Indicator-datetime-service renders 100% CPU usage" [High,Fix released] https://launchpad.net/bugs/774071
[17:59] <seb128> like if that's that usually killing indicator-datetime stop the issue
[18:03] <lool> I pushed a gnome-desktop FTBFS fix to the bzr branch for after A1
[18:03] <seb128> lool, thanks
[18:04] <dobey> btw, is glib 2.31 coming in anytime soon, or are we sticking on 2.30 for P?
[18:04] <seb128> dobey, it will come after a1
[18:05] <dobey> seb128: darn. there will be a LOT of FTBFS at that point then
[18:05] <seb128> dobey, why?
[18:05] <dobey> seb128: it removes some API that was deprecated
[18:05] <seb128> no way
[18:05] <dobey> particularly, g_thread_init
[18:06] <seb128> you probably build with G_DISABLE_DEPRECATED?
[18:07] <dobey> seb128: no, there's no g_thrad_init in http://git.gnome.org/browse/glib/tree/glib/gthread.h
[18:07] <micahg> seb128: I don't have indicator-datetime running, still looking at dbus-monitor
[18:07] <seb128> dobey, it's in glib/deprecated/etc/...
[18:08] <seb128> dobey, they moved the included in a deprecated dir
[18:08] <dobey> oh
[18:09] <dobey> ok
[18:16] <micahg> seb128: seems to be a lot of calls to the volume monitor
[18:16] <seb128> who is doing those?
[18:16] <seb128> do you use gnome-system-monitor or nautilus?
[18:16] <seb128> nautilus --quit?
[18:17] <micahg> did that, no help, how do I decode stuff like :1.93
[18:18] <seb128> oh
[18:18] <seb128> did you dbus-monitor --session?
[18:19] <micahg> nope :)
[18:19] <seb128> try that one rather, it's usually the session bus that gets spammed
[18:19] <seb128> to find what has the id, run d-feet
[18:20] <seb128> they are listed on the left, if you select it you have the binary on the right
[18:21] <micahg> seb128: zeitgeist
[18:21] <seb128> there you go ;-)
[18:21] <seb128> it's mhr3's fault! or seif's or kamstrup's one
[18:21] <seb128> micahg, what sort of requests does it do?
[18:22] <seb128> dbus-monitor should tell you
[18:22] <micahg> yep, killing zeitgeist ended the assault on my CPU :)
[18:23] <mhr3> micahg, what version is that?
[18:23] <micahg> seems to be lots of calls for volume monitor and vfs
[18:23] <micahg> 0.8.99~alpha1-1ubuntu2
[18:23] <mhr3> micahg, dbus-monitor/bustle log would be extremely useful
[18:23] <mhr3> +new bug opened with those :)
[18:25] <micahg> mhr3: will do, thanks
[18:30] <seb128> chrisccoulson, m_conley: do you know how to debug the tb notifications? the "you received <nn> new email" notify-osd bubbles often have a crazy counter, like I receive 5 email and the bubble states I received 19639 ones
[18:30] <seb128> it's correct at some other times, so it's not always off count
[18:30] <m_conley> seb128: holy smokes that's a big count
[18:30] <seb128> well the number seems random
[18:30] <m_conley> seb128: I think chrisccoulson knows that code a bit better...
[18:30] <seb128> just got a 60k one ;-)
[18:31] <seb128> m_conley, he said he never looked at the notification code the other day
[18:31] <m_conley> seb128: oh, wait, hold on
[18:31] <seb128> *shrug*, I guess none of you know that code then ;-)
[18:31] <m_conley> seb128: you're talking about libnotify - sorry, was confusing that with Messaging Menu
[18:31] <seb128> yeah
[18:31] <m_conley> seb128: yes, I sort of know that code - though it's been a few months
[18:32] <m_conley> seb128: actually, there's a guy working on fixing up our notifications right now - his name is irving, and you can find him in #maildev on irc.mozilla.org.
[18:32] <seb128> is there any debug info I can get that would be useful for a bug report? I guess that a bug "the count in the bubble is crazy" wouldn't be very useful by itself
[18:33] <m_conley> seb128: unforunately, no - that code isn't rigged for debugging / logging.  :/
[18:39] <micahg> mhr3: bustle-dbus-monitor output is > 60MB already
[18:39] <mhr3> micahg, no need to run it for 5 minutes :)
[18:39] <micahg> mhr3: ah, I thought I had to wait for it to complete
[18:40] <mhr3> micahg, nope, you just ctrl+c it after a couple of seconds
[18:41] <seb128> micahg, it's like dbus-monitor, it will never complete, it just keeps logging while it's running ;-)
[18:42] <mhr3> micahg, out of curiosity do you have any unusual devices connected to your computer?
[18:42] <micahg> seb128: right, I finally realized that
[18:42] <micahg> mhr3: nope, just headphones ATM
[18:43] <mhr3> micahg, interesting, also the cpu is consistently 100% when you run zg?
[18:44] <seb128> mhr3, it seems zg spam the bus enough that dbus is using 100% cpu :p
[18:44] <mhr3> seb128, didn't i say that the new zg is actually a stress test for dbus-daemon? :)
[18:45] <seb128> ;-)
[18:45] <seb128> mhr3, it's a feature right?
[18:45] <micahg> mhr3: one core is
[18:46] <micahg> 20% zeitgeist/80%dbus-daemon
[18:46] <micahg> bug 898305
[18:46] <ubot2> Launchpad bug 898305 in zeitgeist "zeitgeist-daemon is flooding dbus" [Undecided,New] https://launchpad.net/bugs/898305
[18:47] <seb128> lol
[18:47] <seb128> mhr3, does that mean that zg efficiency is higher than the dbus one? ;-)
[18:48] <seb128> like it's consuming less than dbus for the same trafic? ;-)
[18:48] <micahg> it's 1:5 actually :)
[18:48] <mhr3> seb128, sure, it's all kinds of awesome ;P
[18:51] <mhr3> micahg, any chance to find out what process owns :1.158?
[18:51] <micahg> mhr3: sure
[18:52] <micahg> are these IDs consistent across reboots?
[18:53] <mhr3> nope
[18:53] <micahg> ugh, what about session log out?
[18:53] <mhr3> no
[18:53] <micahg> too late then :)
[18:54] <mhr3> if the process died meanwhile the answer is also "no"
[18:55] <micahg> would you like another output file?
[18:56] <seb128> the id of the clients should have changed if they didn't restart no?
[18:59] <mhr3> micahg, one more thing, does zg output something if you run it via terminal?
[18:59] <micahg> yes
[18:59] <mhr3> like constantly something?
[19:00] <micahg> no, just something at startup ~20 lines
[19:00] <micahg> I can pastebin or attach to the bug
[19:01] <mhr3> micahg, pastebin pls
[19:01] <mhr3> there probably won't be anything interesting in that case...
[19:01] <mhr3> seb128, i'm afraid it's an issue deeper in the stack
[19:02] <micahg> http://paste.ubuntu.com/755241/
[19:02] <mhr3> seb128, apps using GVolumeMonitor coming to mind?
[19:03] <mhr3> yea, nothing interesting really
[19:09] <lool> is there a gtk3 / gnome3 gtk2-engines?
[19:10] <seif> micahg, can u print out dbus-monitor stuff for zeitgeist
[19:10] <seif> ?
[19:10] <seif> micahg, what apps do u have open right now
[19:10] <micahg> seif: if you tell me how :)
[19:11] <micahg> seif: unity-3d, d-feet, xfce4-terminal
[19:12] <nessita> mdeslaur: I had to reboot at some point, did you have any feedback re: qt4reactor package/licensing?
[19:12] <mdeslaur> nessita: no, no feedback yet about licensing
[19:13] <mdeslaur> nessita: i wouldn't worry too much about it though, licensing is probably ok
[19:13] <mdeslaur> nessita: I didn't get past that step, could you ask the next patch pilot to actually look at your package?
[19:14] <nessita> mdeslaur: I will, tomorrow. Thanks :-) (I'm worried since we're kinda blocked on that package in order to package some QT stuff)
[19:15] <seif> mhr3, what is the best dbus-monitor command to monitor all zeitgeist traffic
[19:15] <seif> ?
[19:15] <mdeslaur> nessita: twisted didn't want to bundle it because of licensing issues, but it may be ok since it's in a separate package but someone better qualified than me should make that decision
[19:16] <nessita> mdeslaur: right, thanks!
[19:17] <seif>      micahg r u running zeitgeist right now?
[19:17] <micahg> yes
[19:17] <seif> ok good
[19:23] <seif> micahg,                                     dbus-monitor "interface='org.gnome.zeitgeist.Monitor'"
[19:23] <seif> type that into a terminal and give me the output in 5 minutes
[19:23] <seif> (is zeitgeist still overusing ur cpu?)
[19:23] <micahg> yes, it's constant
[19:25] <seif> did u run the command i told you
[19:25] <micahg> it's running now, only one thing so far
[19:25] <seif> hmmmmmmmmmmmm
[19:26] <seif> hmmmmmmmm
[19:26] <seif> micahg, can u do killall zeitgeist-datahub
[19:26] <micahg> no change except for a little more debug output
[19:27] <seif> fuck
[19:27] <seif> i fear unity could be requesting constantly from zeitgeist
[19:27] <seif> -.-
[19:29] <seif> micahg, try                                dbus-monitor "interface='org.gnome.zeitgeist.Log'"
[19:29] <seif> if its going batshit crazy then we can trace it from here
[19:30] <micahg> seif: same issue with Xfce
[19:31] <micahg> and only 1 thing with that second dbus-monitor query
[19:32] <seif> micahg, what do u mean by same issue with xfce
[19:32] <seif> ?
[19:33] <micahg> seif: I get the same CPU spike with xfce, it's not just with uniyt
[19:33] <micahg> *unity
[19:34] <seif> micahg, ok one more thing 1) killall zeitgeist-daemon   2)  cp -r .local/share/zeitgeist to .local/share/zeitgeist-backup 3) zeitgeist-daemon --replace
[19:35] <mhr3> micahg, pls run just `python -c "from gi.repository import Gio, GLib; ml = GLib.MainLoop(); vm = Gio.VolumeMonitor.get(); print vm.get_volumes(); ml.run()"`
[19:35] <mhr3> and see if it uses 100% cpu
[19:37] <micahg> mhr3: no
[19:37] <micahg> seif: it's no longer eating up CPU
[19:39] <mhr3> micahg, so my command actually fixed it? :)
[19:39] <micahg> mhr3: no, I think it's seif
[19:39] <seb128> lool, no
[19:39] <mhr3> micahg, make sure by restarting session :)
[19:40] <micahg> was just going to ask if I could at this point
[19:40] <seb128> lool, well not by default for gtk, we have one (unico) for our theme
[19:40] <seb128> lool, gtk is only using css theming
[19:41] <lool> seb128: I see there are newer GNOME upstream releases of it, that's why I was wondering
[19:41] <micahg> mhr3: heh, it's back :)
[19:41] <mhr3> micahg, try my cmd
[19:41] <lool> seb128: I guess I'll just backport the FTBFS fix for gtk2-engines rather than move to the latest one
[19:41] <seb128> lool, no
[19:41] <seb128> lool, the theming got totally reworked in gtk3
[19:41] <seb128> lool, they moved from their old engine and gtkrc to css themin
[19:42] <seb128> theming
[19:42] <lool> there's a 2.91 gtk-engines upstream http://ftp.gnome.org/pub/GNOME/sources/gtk-engines/2.91/
[19:42] <micahg> mhr3: nope, still high
[19:42] <seb128> lool, the goal I think is to not need engines but give enough flexibility over css
[19:42] <seb128> lool, right, that's around the time they landed the css work ;-)
[19:42] <lool> 2.90.3 says  - Port to GTK+ 2.90 (thanks to Bastien Nocera and others)
[19:42] <seb128> lool, which deprecated the need for it
[19:43] <lool> ok, might be worth packaging the latest gtk2 version of it I guess
[19:43] <mhr3> micahg, :(
[19:43] <seb128> lool, well, I think we have the current one
[19:43] <seb128> lool, 2.91 was for gtk3 at a time where gtk3 didn't have css
[19:44] <seif> micahg, what did i miss
[19:44] <seif> mhr3, what did i miss
[19:44] <mhr3> seif, the universe almost collapsed
[19:44] <micahg> seif: your thing fixed it for the session only, when I logged out and back in, I had the same issue
[19:44] <seif> what why
[19:45] <mhr3> micahg, can i get you to attach also a half-second of dbus-monitor to the bug?
[19:45] <seif> micahg, ok then do the same thing but instead of restarting zeitgeist log in and out again or restart the session
[19:45] <micahg> straight dbus-monitor?
[19:45] <mhr3> micahg, yep
[19:47] <seif> micahg, today i will have nightmares if we dont know what the problem is
[19:47] <seif> lol
[19:48] <mhr3> micahg, your night is gonna suck then :)
[19:49] <micahg> seif: nope, session restart brings it back
[19:49] <seif> that makes no sense -.-
[19:50] <seif> mhr3, where do we try to access the volumes
[19:50] <mhr3> seif, sorry that was for you ^^
[19:50] <lool> seb128: Ok, so 2.9x ones are useless now and we'll keep it as it is until gtk2 dies?
[19:50] <seb128> lool, that's my understanding yes
[19:51] <lool> Ok
[19:51] <micahg> which is at least 2 more years :)
[19:52] <mhr3> lool, so how often people accidentally ping you when they laugh? :)
[19:52] <micahg> mhr3: attached
[19:53] <mhr3> micahg, thx
[19:53] <lool> That happens more often than for mhr3
[19:53] <mhr3> lool, i can imagine :)
[19:53] <seb128> mhr3, oh, you should ask how often people ping him when they want to know about the libreoffice online version :p
[19:53] <seif> micahg, can u do "find / -name 'zeitgeist'" or me
[19:53] <seb128> lool, I'm disappointed that googling for "lool" return libreoffice stuff before you btw!
[19:54] <lool> seriously
[19:54] <lool> they've displaced me
[19:54] <lool> I used to be one the first page of results for lool -- rightfully so!
[19:54] <lool> but now everyone says lool for lol
[19:54] <lool> these young people
[19:55] <seb128> yeah, you should just sue them for it!
[19:55] <lool> I'll install one of these high-pitch noise producer on my webpage
[19:56] <seb128> ;-)
[20:00] <seb128> 'night
[20:01] <micahg> seif: did you want all the permission denied entries as well?
[20:02] <mhr3> micahg, try something crazy - eject the cd you have in your cd drive :)
[20:02] <RainCT> CD drive? What's that?
[20:02] <micahg> mhr3: heh, that did it :)
[20:02] <mhr3> RainCT, something we didn't account for when developing zeitgeist ^^
[20:03] <RainCT> mhr3: I don't even have one :P
[20:03] <mhr3> let me try if i can reproduce this
[20:03] <micahg> ooh, it's so quiet now :)
[20:03] <seif> micahg, wont hurt
[20:03] <micahg> seif: we found the issue, it's the CD in the drive
[20:04] <seif> micahg, lol
[20:04] <mhr3> micahg, that was audio cd right?
[20:04] <micahg> mhr3: indeed
[20:05] <mhr3> micahg, was it playing or something, or just sitting there?
[20:05] <micahg> just sitting there AFAIk
[20:06] <seif> mhr3, the storagem onitor is not implmented yet
[20:06] <seif> what is the problem
[20:06] <mhr3> micahg, well there's some odd interaction between gvfs and zg, but i have no idea why, we're not trying to read it
[20:07] <seif> the only thing though would try that is the storage-monitor.py
[20:07] <RainCT> seif: Bluebird
[20:08] <RainCT> seif: I did implement USB and stuff, just network was missing iirc
[20:09] <mhr3> seif, if you have audio cd, try to reproduce it
[20:09] <mhr3> i dont have any here
[20:12] <RainCT> mhr3: can't reproduce it with an external DVD reader
[20:13] <seif> mhr3, what do u think the issue is
[20:24] <lool> I've commited a FTBFS fix for gtk2-engines in lp:~ubuntu-desktop/gtk2-engines/ubuntu for upload after A1
[21:17] <chrisccoulson> hi m_conley and seb128
[21:17] <chrisccoulson> sorry, went out to the christmas market :)
[22:03] <chrisccoulson> bah, the tabbar is totally broken in todays firefox nightly
[22:04] <chrisccoulson> i suppose that's not too bad, having not had a real problem for several months
[22:15] <AlanBell> anyone know about the global menu?
[22:15] <AlanBell> and indicators for that matter
[22:20] <JanC> AlanBell: know what about hem?
[22:22] <TheMuso> AlanBell: Yes, what about them?
[22:25] <AlanBell> just wondering about them all being tickboxes when read by orca
[22:26] <AlanBell> everything is "$name tickbox not ticked"
[22:32] <TheMuso> AlanBell: I'm aware of it, and I'm on it.
[22:32] <TheMuso> AlanBell: Fixing that as part of my work to allow for extra info to be spoken about network names in network-manager etc.
[22:35] <AlanBell> cool, thanks
[22:37] <TheMuso> np