[08:11] <robert_ancell> seb128, hey
[08:12] <seb128> hello robert_ancell
[08:12] <seb128> how was your start of week there?
[08:12] <robert_ancell> seb128, question about uploading gnome updates...  Now I am MOTU can I just directly upload stable GNOME packages? e.g. Cheese
[08:12] <seb128> busy looking at the sponsor bugs ;-)
[08:12] <seb128> robert_ancell, yes
[08:13] <seb128> robert_ancell, only in universe though which is limited for GNOME
[08:13] <robert_ancell> seb128, but as long as they're in universe and in GNOME FTP then ok?
[08:14] <seb128> well, usually it's not gnome ftp but part of GNOME
[08:14] <seb128> ie following freezes
[08:14] <seb128> we don't want to upload random new crack now
[08:14] <seb128> but yes
[08:14] <seb128> if you are not sure ask there, I've been mandated to grant desktop exceptions
[08:15] <lifeless> robert_ancell: as a MOTU you /can/ upload anything that is a) in universe b) meets policy to be uploaded given the archive state.
[08:15] <robert_ancell> lifeless, thanks, I was just checking on what is considered in the GNOME freeze exception, I wasn't sure if it extended to universe
[08:16] <lifeless> same basic policy
[08:16] <robert_ancell> seb128, question 2:  What do I do about UNRELEASED versions in bzr? Manually updated them?
[08:16] <seb128> robert_ancell, dch -r?
[08:16] <lifeless> different teams for approvals [the universe team has motus as well as the main team]
[08:16] <seb128> or change to karmic by hand if you want
[08:17] <robert_ancell> seb128, In this case I should just set it to Karmic and then do the upload - dch -r is only useful for sponsoring others packages?
[08:17] <seb128> whatever you prefer, I usually change to karmic with my text editor
[08:17] <seb128> but I think pitti for example use dch -r
[08:18] <seb128> there is not one true way there
[08:18] <seb128> just make sure you have karmic in the changelog ;-)
[08:19]  * robert_ancell just uploaded his first ubuntu packages... Will wait for the angry emails tomorrow about breaking stuff :)
[08:22] <seb128> robert_ancell, ;-)
[08:22] <didrocks> good morning o/
[08:22] <seb128> brb session restart after weekend upgrade
[08:24] <asac> hi
[08:24] <didrocks> hey asac
[08:26] <asac> hi didrocks
[08:29] <robert_ancell> seb128, perhaps we should update the versions script - it only shows packages on the cd, it should probably show packages in main?
[08:30] <robert_ancell> gtg, see you guys tomorrow
[08:31] <seb128> re
[08:31] <seb128> ok didn't go as expected, I had to reboot
[08:31] <didrocks> oh :/
[08:31] <huats> morning everyone
[08:31] <huats> morning seb128
[08:32] <didrocks> good morning huats
[08:32] <seb128> lut didrocks huats
[08:32] <didrocks> seb128: hey o/ I hope there will still be some updates to do this evening to avoid feeling useless ;)
[08:32] <seb128> didrocks, I hope not
[08:33] <huats> +1 for me :)
[08:33] <huats> seb128: I can do some today... if there are any
[08:33] <seb128> today is already late for updates
[08:33] <seb128> so I expect so to be uploaded earlier rather than later
[08:33] <seb128> so -> those
[08:34] <seb128> another quick sessionr restart and I'm starting on sponsoring
[08:35] <didrocks> seb128: at least, I'll upload simplecommeubuntu-9.10~prerc this evening ;)
[08:35] <seb128> didrocks, good ;-)
[08:36] <seb128> I will let you guys know if there is updates left
[08:36] <seb128> but I expect I will go quickly through those
[08:36] <seb128> especially that robert_ancell did a good bunch already
[08:36] <seb128> and not everybody will roll a .1
[08:36] <seb128> you are welcome to work on the universe ones though
[08:36] <seb128> there is less hurry for those
[08:37] <didrocks> seb128: ok, keep us in touch so :)
[08:38] <seb128> will do
[08:38] <tgpraveen> Bug #446146 any chance of getting this in karmic final itself. it's fix commited  just need to be released
[08:40] <seb128> wrong channel to ask about linux
[08:40] <seb128> it's not really a desktopish component
[08:58] <asac> its a bit related to NM ;)
[08:58] <asac> pitti has the same problem ;)
[09:00] <asac> kenvandine: gwibber is in sad state today ;)
[09:00] <asac> does not start here
[09:03] <pitti> Good morning
[09:03] <pitti> seb128: hm, so Robert's patch wasn't applied to 2.28 branch
[09:03] <seb128> pitti, the gvfs one?
[09:04] <pitti> yes
[09:04] <pitti> ah, robert is already gone (sorry, I'm late today again)
[09:04] <pitti> UNRELEASED is not just for sponsoring..
[09:05] <seb128> right, but the discussion was rather on how you change it to markic
[09:05] <seb128> dch -r, manual edit, etc
[09:05] <pitti> ah
[09:35] <lool> pitti: Did you intend to revert r1588 in ubuntu.karmic r1589?
[09:35] <pitti> lool: yes, I did; I just failed to commit it separately, sorry
[09:35] <lool> Thanks
[09:35] <pitti> lool: we removed French on amd64 because of overflow, but now we kicked rss-glx (which was never meant to be on the CD)
[09:36] <lool> Ack; we don't have it in UNR anyway
[09:42] <pitti> asac: epiphany pulls in seed and gnome-js-common; do we need them in main? (MIR)
[09:43] <asac> pitti: no ... the idea is to drop ephy plugin from seahorse-plugins
[09:43] <asac> so everything can go down
[09:43] <asac> if you want rather ephy and all stuff in main, let me know
[09:43] <asac> seb128: ^^ ?
[09:43] <pitti> asac: it's a b-dep of epiphany
[09:43] <asac> pitti: yes. but ephy is universe now ... its just in main because of seahorse-plugins pulling in afaict
[09:43] <seb128> I though epiphany was in universe now?
[09:44] <pitti> http://people.canonical.com/~ubuntu-archive/component-mismatches.txt
[09:44] <asac> seb128: yeah. seahorse-plugins is holding it
[09:44] <seb128> asac, right, the seahorse-plugins one is to fix, do you want to do the update and fix that too?
[09:44] <pitti> ok, so shall I demote epy then?
[09:44] <seb128> there is a 2.28.1 tarball
[09:44] <seb128> pitti, yes please
[09:44] <asac> seb128: update to latest upstream? yes. i have to move to xulrunner-1.9.1
[09:44] <asac> pitti: i thought that happened a while back already
[09:44] <seb128> asac, thanks
[09:44] <andreasn> mpt, what e-mail do you use for gnome bugzilla? just wanted to check I added the right one
[09:45] <asac> pitti: on friday you showed me a mismatch of ephy getting pulled in by seahorse
[09:45] <asac> pitti: so if now seed etc are in mismatch means that ephy was promosted probably because of that
[09:45] <asac> pitti: ok. so i will upload new seahorse plugins without the epiphany part ... and fixed xulrunner-1.9 -> 1.9.1 ...
[09:46] <pitti> asac: thanks
[09:46] <asac> thats also the last xulrunner-1.9 rdepend from what micagh from mozillateam researched .... so i will verify that this is really the case and then ask for permission to get rid of ffox-3.0 and xul 1.9
[09:46] <asac> pitti: ^^
[09:47] <asac> that would involve putting ffox-3.0 transitional packages in a firefox-3.5 upload
[09:47] <pitti> yay
[09:47] <asac> good.
[09:47] <asac> i will check now the rdepends in sources/packages and then proceed with those two tasks
[09:47] <asac> hopefully fixing the last RC issues in ffox too at that time
[09:54] <mpt> andreasn, myrealbox, but I'm not getting notifications a.t.m.
[09:55] <andreasn> oh
[09:55] <andreasn> I cc:ed you on the gnome-policykit bug
[10:04] <dpm> seb128, just a quick note to let you know I imported all policykit-1-gnome upstream translations into LP as discussed some days ago. Sorry it took me so long.
[10:04] <seb128> dpm, thanks!
[10:05] <dpm> yw
[10:05] <dpm> seb128, another question, can yo
[10:06] <dpm> seb128, another question, can you tell me a bit more about gdmsetup and its Ubuntu-specific translations? I'm the upstream gdm translator and the Ubuntu-specific strings were already translated upstream and imported into LP, so I had no need to translate them in LP
[10:06] <seb128> dpm, weird
[10:07] <seb128> dpm, could it be that somebody commited the launchpad po there?
[10:07] <seb128> with strings which are not upstream too?
[10:08] <dpm> seb128, no, the translations are marked as green in LP, so they're the same as the imported ones
[10:08] <seb128> what strings are you look at exactly?
[10:09] <dpm> seb128, the gdmsetup ones, let me have a look...
[10:10] <dpm> seb128, this one, for example -> https://translations.edge.launchpad.net/ubuntu/karmic/+source/gdm/+pots/gdm/ca/107/+translate
[10:12] <dpm> the French team doesn't seem to have any strings changed in LP, either: https://translations.edge.launchpad.net/ubuntu/karmic/+source/gdm/+pots/gdm/fr/+translate?start=0&batch=10&show=changed_in_launchpad&field.alternative_language=&field.alternative_language-empty-marker=1&old_show=all
[10:13] <seb128> gdm-2.28.0$ grep "_Show the screen for choosing who will log in" * -r
[10:13] <seb128> debian/patches/09_gdmsetup.patch:+                    <property name="label" translatable="yes" comments="Radio option to set login screen to prompt for user">_Show the screen for choosing who will log in</property>
[10:13] <seb128> po/ca.po:#~ msgid "_Show the screen for choosing who will log in"
[10:13] <seb128> $
[10:13] <seb128> dpm, ^
[10:13] <seb128> dpm, what you say doesn't make sense
[10:14] <seb128> dpm, could it be that launchpad doesn't consider it as an upstream string changed since it's not in the upstream po there?
[10:15] <seb128> dpm, I'm sure those strings are not in the upstream git codebase
[10:18] <dpm> seb128, LP considers the package as "upstream", it doesn't detect the tarball strings. By looking at http://l10n.gnome.org/POT/gdm.master/gdm.master.ca.po, I see:
[10:18] <dpm> #~ msgid "_Show the screen for choosing who will log in"
[10:18] <dpm> #~ msgstr "_Mostra la pantalla per a seleccionar qui entrarà"
[10:18] <dpm> So the string was marked as obsolete at some point upstream
[10:18] <seb128> dpm, right, cf my grep, it's the only po where the string is listed
[10:19] <seb128> dpm, could it be that somebody used the ubuntu po and gettext marked it obsolote?
[10:19] <seb128> obsolete
[10:19] <seb128> since it's not in the upstream source
[10:20] <dpm> seb128, I'm not sure, but it's certainly possible. So gdmsetup is an Ubuntu-only app?
[10:21] <seb128> dpm, yes
[10:21] <dpm> seb128, do upstream ship no setup tool at all, or still the old graphical setup tool?
[10:22] <seb128> dpm, https://bugzilla.gnome.org/show_bug.cgi?id=587750
[10:22] <seb128> dpm, they don't ship any configuration tool
[10:22] <seb128> it would make no sense to have an ubuntu tool if upstream had one
[10:22] <dpm> seb128, that clears things up. Thanks a lot
[10:22] <seb128> dpm, you're welcome
[10:31] <tseliot> seb128: it looks like I'll have to extend my patch: https://bugzilla.gnome.org/show_bug.cgi?id=598287
[10:33] <seb128> tseliot, hum ok, not really important for karmic since we have tap on click on now
[10:34] <tseliot> seb128: did you re-enable it?
[10:34] <seb128> tseliot, still a nice thing to fix but nothing urgent
[10:34] <seb128> tseliot, yes, tape on click is on by default now
[10:34] <seb128> the no taping while typing too
[10:35] <tseliot> seb128: can you drop my patch from the package then?
[10:35] <seb128> tseliot, will do
[10:35] <tseliot> it looks like the function which detects the availability of buttons is not very reliable
[10:35] <tseliot> seb128: ok, thanks
[10:35] <seb128> you're welcome
[11:01] <kklimonda> seb128, pitti, could you tak a look at bug 444005? as there won't be a 1.76 release soon (most likely never - devs will jump straight to 1.80) there are few bugs that should be fixed in 1.75.
[11:02] <seb128> kklimonda, I'm too busy in GNOME 2.28.1 too look at that software
[11:02] <seb128> you will need to find somebody else interested
[11:02] <kklimonda> at least both crashes, a potential data loss would be nice too. a removal of --auth argument is a wishlist.
[11:02] <pitti> kklimonda: opened a tab for it; will have a look later today, thanks
[11:03] <kklimonda> seb128, no problem - I'll keep looking.. ok, i don't have to anymore :)
[11:28] <seb128> pitti, do you want to do the gpm 2.28.1 update?
[11:28] <pitti> seb128: can do
[11:28] <seb128> danke
[11:28] <pitti> seb128: I'm currently debugging bug 451613 which is the last of my RC bugs
[11:29] <pitti> seb128: this will still take me a bit, but this afternoon I can deal with updates/sponsoring/torrent
[11:29] <seb128> pitti, I don't expect any torrent but thanks ;-)
[11:29] <seb128> pitti, .
[11:29] <seb128> ups
[11:29] <pitti> seb128: bug 444005 I meant
[11:29] <seb128> pitti, .1 traditionally doesn't get tarballs for everything
[11:30] <seb128> oh right
[11:30] <seb128> anyway I did catch up on updates out of gpm now
[11:30] <seb128> so let's get lunch before having new tarballs coming
[11:56] <mac_v> mvo: hi , is there already a bug in synaptic where the cpu usage increases during checking for updates?
[12:04] <seb128> chrisccoulson, we were just speaking about you ;-)
[12:04] <seb128> chrisccoulson, hey btw
[12:04] <chrisccoulson> hey seb128
[12:04] <chrisccoulson> i hope you were saying nice things about me ;)
[12:04] <chrisccoulson> lol
[12:04] <seb128> chrisccoulson, <slangasek> oh gar, why am I now getting a 'low disk space' pop-up every 30 seconds? :P
[12:04] <pitti> hey chrisccoulson, good afternoon!
[12:05] <seb128> chrisccoulson, I was just saying that you were looking about such things
[12:05] <chrisccoulson> hey pitti
[12:05] <seb128> not sure if you still have interest for that though
 although, I'd rather he fix my crashing gnome-settings-daemon first :)
[12:05] <seb128> too ;-)
[12:05] <chrisccoulson> they shouldn't appear every 30 seconds - every 10 minutes at the most
[12:05] <chrisccoulson> ah
[12:05] <mvo> mac_v: there is/was such a bug with update-manager, I suspect its something to do with the theme in use, but I have not investiagted
[12:05] <seb128> chrisccoulson, well, apparently he clicks on ignore and get a dialog 30s later
[12:06] <mac_v> mvo: ah , just found one > is this the bug , Bug #355355
[12:06] <chrisccoulson> seb128 - that behaviour definately doesn't sound right - i'll speak to him later and try and figure out whats going on
[12:06] <seb128> chrisccoulson, thanks
[12:08] <mvo> mac_v: do you have more info on it? is it theme dependant? does it matter if compiz or metacity is used?
[12:09] <mac_v> mvo: human theme just got a bug regarding this ...i'm testing it , checking if it has something to do with the murrine engine being used
[12:09] <mac_v> will see if there us any change
[12:09] <mac_v> is*
[12:11] <mvo> mac_v: I have a idea what is causing it, its not a trivial fix if it turns out to be what I think it is
[12:15] <mac_v> mvo: nope  , doesnt seem theme dependant , i tried a different engine and still x org cpu usage raises ... and your idea is? ;)
[12:16] <mvo> mac_v: i think its the drawing code for the individual progresses, I have a look later today (got some other things with higher priority first)
[12:18] <mac_v> sure its no hurry , just wanted to check :)
[12:20] <asac> pitti: augeas needs to be promoted too for puppet ... i asked for getting symbol tracking or a specific shlibs version in the package in the MIR - besides from that its ok. i will check if zul can do that swiflty. otherwise will probably upload on my own
[12:24] <pitti> asac: I did, I mentioned in the bug
[12:25] <tjaalton> there doesn't seem to be a bug about gdm not being able to be restarted from a vt?
[12:26] <pitti> tjaalton: hm, it's not? WFM
[12:27] <asac> ok read that mail now. thx
[12:27] <pitti> sudo stop gdm; sudo start gdm
[12:27] <asac> will prod zul
[12:27] <tjaalton> pitti: it'll just flash the screen rapidly for a few seconds, then stop and no gdm running after that
[12:28] <seb128> tjaalton, you don't have one running?
[12:28] <tjaalton> seb128: nope
[12:29] <seb128> ok, so I don't know
[12:29] <seb128> works here
[12:35] <tjaalton> seb128, pitti: uh oh.. binary driver fail on my part, ie. a false alarm ;)
[12:36] <pitti> hm, I often get Firefox complaining "sorry, restoring session failed", and clicking on "restore" works just fine..
[12:37] <asac> pitti: any errors in tools -> error console?
[12:37] <asac> also try set extensions.logging.enabled to true and see if you get any errors on terminal if you end up in this situation
[12:43] <pitti> asac: odd that it isn't known yet; anyway, I'll file a bug (it happens pretty often for both me and also my wife)
[12:43] <pitti> asac: there are three errors
[12:44] <asac> pitti: do you see "restart required " in tools -> addons all the time?
[12:44] <pitti> asac: no, I don't
[12:45] <asac> hmm. ok. then its not the bug i am currently fixing. please file a bug with those errors you see please
[12:45] <asac> bug 446257
[12:45] <asac> pitti: ^^
[12:46] <pitti> asac: *nod*, that's it
[12:46]  * pitti subscribes
[12:46] <asac> pitti: please post the errors you see there. thx
[12:47] <pitti> yay, fixed my last RC bug
[12:47] <asac> lucky you :/
[12:47] <seb128> asac, I do get restart all the time when greasemonkey get screwed
[12:47] <asac> but usually there is something new whenever you think you are done
[12:47] <seb128> which is basically after every xulrunner upgrade
[12:47] <asac> seb128: yes. tahts your bug.
[12:47] <asac> and i know it
[12:47] <asac> upstream just didnt like my fix ;)
[12:47] <asac> which was hacky indeed
[12:48] <pitti> asac: hm, closing and reopening the console seems to wipe errors; next time it happens I'll immediatley look and copy
[12:48] <seb128> asac, oh, so you found a real bug, it's not my install being weird ;-)
[12:48] <pitti> asac: something new> yeah, already happened three times in the last two weeks :)
[12:50] <asac> seb128: https://bugzilla.mozilla.org/show_bug.cgi?id=521780
[13:00] <seb128> pitti, good work on the gvfs bug ;-)
[13:00] <pitti> seb128: merci
[13:01] <asac> Errors were encountered while processing: /var/cache/apt/archives/libequinox-osgi-java_3.5.1-0ubuntu6_amd64.deb
[13:01] <asac> E: Sub-process /usr/bin/dpkg returned an error code (1)
[13:01] <asac> what is equinox?
[13:01] <asac> ;)
[13:01] <asac> oh seems eclipse related
[13:02] <asac> guess i know someone to ask
[13:02] <pitti> seb128: do you get bug mail piped straight to your brain nowadays?
[13:03] <asac> seb holds back technical innovation wrt bug streaming ... i always knew it
[13:03] <seb128> lol
[13:04] <seb128> pitti, no, but I'm subscribed to gvfs bugzilla and I'm polling on emails to get new tarballs today
[13:35] <kenvandine> asac, any tips on what is wrong?
[13:40] <sweettie> hee hello everyone
[13:40] <sweettie> im looking for some help.
[13:40] <sweettie> (with my desktop)
[13:40] <seb128> sweettie, hi, try #ubuntu for user questions
[13:41] <sweettie> txs
[13:45] <asac> kenvandine: sorry i lost context. on what?
[13:45] <kenvandine> gwibber
[13:45] <asac> let me try
[13:46] <asac> kenvandine: http://paste.ubuntu.com/296810/ that what i am getting
[13:46] <asac> the UI never shows up
[13:46] <kenvandine> humm
[13:46] <asac> kenvandine: http://paste.ubuntu.com/296811/
[13:46] <kenvandine> do you have facebook configured?
[13:46] <asac> there is dbus problem
[13:46] <kenvandine> ok
[13:47] <asac> kenvandine: yes. facebook
[13:47] <kenvandine> looks like it is failing to fire up the daemon
[13:47] <kenvandine> is the daemon running?
[13:47] <kenvandine> i bet it is already running and hung
[13:47] <asac> yes
[13:47] <kenvandine> which is that damn facebook bug
[13:47] <asac> probably
[13:47] <asac> kenvandine: well. i think i didnt really start it until this morning
[13:47] <asac> but let me kill it
[13:48] <kenvandine> for some reason, sometimes it hangs on a connection to facebook and never times out like it should
[13:48] <asac> kenvandine: yeah. there it is
[13:48] <kenvandine> it is better with pycurl than it was with urllib2
[13:48] <asac> kenvandine: are we using pycurl now?
[13:48] <kenvandine> but ryan can't seem to figure out why it fails to timeout
[13:48] <kenvandine> cause it was more reliable with facebook
[13:48] <kenvandine> only the facebook module is using it
[13:49] <kenvandine> it failed frequently with urllib2
[13:49] <kenvandine> just never times out
[13:49] <kenvandine> ryan spent weeks on that... and got nowhere
[13:49] <kenvandine> it is more reliable with pycurl, but still fails to timeout sometimes
[13:49] <asac> kenvandine: facebook.py stillin includes urllib
[13:49] <kenvandine> yeah, but not urllib2
[13:50] <asac> on lp:gwibber
[13:50] <kenvandine> it isn't using it for the connection
[13:50] <kenvandine> there was some other reason for it
[13:50] <kenvandine> url parsing or something
[13:51] <kenvandine> gwibber/microblog/support/facelib.py
[13:51] <asac> kenvandine: where is the call done?
[13:51] <asac> ah
[13:51] <seb128> gnomefreak, hey, nobody else is getting your gnome-panel issue, we have thousand of bugs happening only on one broken config, we can't mark those blockers
[13:51] <kenvandine> both urllib2 and pycurl supposedly force some timeout so this can never happen
[13:51] <kenvandine> but they both have the same problem, only with facebook
[13:52] <kenvandine> asac, if you have any insight... i am sure ryan would jump for joy :)
[13:52] <kenvandine> ryan was threatening disabling facebook all together
[13:52] <kenvandine> but facebook is far to popular :/
[13:53] <gnomefreak> seb128: understood i would really love to know where to start to figure it out. it seems like this bug is giving me a alsa bug as well due to killall gnome-panel
[13:53] <asac> kenvandine: he uses httplib.HTTP ... in api there only is HTTPConnection
[13:54] <asac> http://docs.python.org/library/httplib.html
[13:54] <seb128> gnomefreak, could you summarize the bug there?
[13:54] <kenvandine> asac, oh...
[13:55] <asac> kenvandine: is that an alias?
[13:55] <kenvandine> dunno
[13:55] <kenvandine> i would think this would just blow up
[13:55] <asac> http://paste.ubuntu.com/296816/
[13:55] <kenvandine> so perhaps
[13:55] <gnomefreak> seb128: going to look at bug
[13:55] <asac> let me try if i get timeouts with just 1 second ;)
[13:55] <kenvandine> cool
[13:56] <kenvandine> asac, oh
[13:56] <kenvandine> that isn't used
[13:56] <kenvandine> that is for photo uploads
[13:56] <kenvandine> which gwibber doesn't do
[13:57] <asac> hehe
[13:57] <kenvandine> part of the library he embedded
[13:57] <asac> ok found the curl call
[13:57] <kenvandine> in the Facebook class
[13:58] <gnomefreak> not a bad option to add ;)
[13:58] <kenvandine> hehe... lets make facebook work better first :)
[13:58] <kenvandine> asac, so i think c.perform() never returns
[14:00] <asac> kenvandine: http://paste.ubuntu.com/296823/
[14:00] <asac> that works for me
[14:00] <asac> i got a timeout
[14:00] <asac> when using 1
[14:01] <kenvandine> yeah, he was able to get timeouts
[14:01] <kenvandine> but
[14:01] <kenvandine> sometimes on the facebook connection he doesn't
[14:01] <kenvandine> and could never figure out why
[14:01] <asac> http://paste.ubuntu.com/296826/
[14:01] <asac> kenvandine: well. atm there is no timeout set at all
[14:01] <kenvandine> there is a default
[14:01] <asac> kenvandine: so lets use that one instead of nothing
[14:01] <asac> yes. the default is the socket timeout of system i guess
[14:01] <kenvandine> well, he said there is
[14:01] <asac> and thats probably 120 seconds or even 5 minutes
[14:01] <kenvandine> he played around with different values
[14:02] <gnomefreak> seb128: you wanted me to ad dmore to summry on bug or you wanted me to do it here?
[14:02] <kenvandine> that is way too high
[14:02] <seb128> gnomefreak, can you summarize it there?
[14:03] <asac> kenvandine: so in other http libs i know its always the system default for socket/dns
[14:03] <asac> thats far too high
[14:03] <asac> so we should definitly set something there
[14:04] <asac> kenvandine: also we should set CONNECTTIMEOUT
[14:04] <kenvandine> it would be good to do that too
[14:04] <kenvandine> but connecting isn't where the problem was
[14:04] <kenvandine> but it looks like setting the timeout to something lower should do what we want
[14:04] <asac> http://paste.ubuntu.com/296830/
[14:04] <kenvandine> maybe it just never thinks it is done with the download
[14:05] <asac> kenvandine: thats what i would suggest
[14:05] <kenvandine> dunno... i have never looked at it... just know ryan spent weeks on it :)
[14:05] <asac> kenvandine: does gwibber loop every X seconds?
[14:05] <kenvandine> 5m
[14:05] <kenvandine> is the default fresh
[14:05] <kenvandine> otherwise it just has a mainloop and threads
[14:05] <asac> kenvandine: so why does gwibber frontend get no reply? because its polling on demand or because the main thread is just blocked?
[14:05] <kenvandine> so if a call takes 5m, it causes havoc
[14:06] <kenvandine> main thread is blocked
[14:06] <asac> kenvandine: thought thats in a separate thread?
[14:06] <asac> what operation is done in main thread? the full http call?
[14:06] <kenvandine> well, the microblog operation is in a separate thread
[14:06] <kenvandine> which shouldn't block the main thread
[14:07]  * seb128 grrrr at bzr and pitti
[14:07] <kenvandine> the exception you got was from scheduling operations with the microblog backend
[14:07] <kenvandine> which is what is blocked
[14:08] <kenvandine> moving that scheduling to the backend would help allot
[14:08] <kenvandine> planned for lucid :)
[14:08] <asac> kenvandine: so scheduling involves initiating a connecting?
[14:08] <asac> or does it block until the previous work was done?
[14:08] <kenvandine> yeah, something has to connect to it currently
[14:08] <kenvandine> when it connects, it calls the scheduler to schedule the default operations
[14:08] <kenvandine> which doesn't really make sense
[14:09] <kenvandine> the backend should have that logic
[14:09] <kenvandine> there was some debate about that, like the guy writing the cli interface
[14:09] <kenvandine> i think he wanted to be able to control that a little more from the client
[14:09] <kenvandine> we are going to move all that out of the client for lucid
[14:09] <asac> i dont get what is done in the thread ,)
[14:09] <kenvandine> hehe
[14:09] <asac> does it just update db and stuff there?
[14:09] <kenvandine> performing the operations
[14:10] <asac> and does all the io in the main thread?
[14:10] <kenvandine> calling the microblogging services, etc
[14:10] <kenvandine> the main thread just dispatches
[14:10] <asac> what is that compared to what __call__ does?
[14:10] <kenvandine> the main thread isn't what blocked your call
[14:11] <asac> the main thread is the one processing dbus, isnt it?
[14:11] <kenvandine> the client was calling the microblogging stuff
[14:11] <asac> shouldnt it be returning stuff?
[14:11] <asac> kenvandine: oh. so the client directly calls into the other non-main thread?
[14:11] <kenvandine> imo it should be processing all of that
[14:11] <kenvandine> i think so
[14:11] <gnomefreak> seb128: im not sure what more i can add or change to be anymore helpful. I am adding the alsa bug link to bug report
[14:11] <kenvandine> which we want to prevent
[14:11] <kenvandine> so moving more of that logic out to the backend
[14:11] <asac> is dbus actually multi-threwading ready?
[14:11] <seb128> gnomefreak, do you get the issue at every session start? does it happen in a guest session?
[14:11] <kenvandine> will keep the client from ever calling those
[14:12] <kenvandine> asac, perhaps not... i really don't know
[14:12] <asac> hehe
[14:12] <kenvandine> ryan did most of that... and i know he was getting very angry :)
[14:12] <asac> kenvandine: ok. so the facebook threads handles network for facebook and also is responsible for processing dbus?
[14:12] <asac> ok
[14:12] <kenvandine> yeah
[14:12] <kenvandine> at least that is my understanding
[14:12] <kenvandine> which is kind of crappy
[14:12] <asac> whats our dbus timeout?
[14:12] <asac> does the UI at least do async dbus ?
[14:13] <asac> hmm
[14:13] <asac> oh no
[14:13] <asac> it doesnt
[14:13] <asac> now i know
[14:13] <kenvandine> it does for somethings
[14:13] <asac> kenvandine: can i send python a signal so it dumps backtraces for all threads?
[14:13] <asac> i know i could do something like that for java
[14:13] <kenvandine> i haven't seen a way
[14:14] <kenvandine> that would be very cool though :)
[14:14] <asac> kenvandine: what i am trying to understand is whats the perfect tune for those timeouts
[14:14] <kenvandine> asac, understand
[14:15] <asac> so if dbus sends a call ... and has a timeout of 10 seconds... and that synchronously calls the facebook server
[14:15] <asac> then we need to use a timeout lower than the dbus call
[14:15] <asac> which can be quite short i guess
[14:15] <kenvandine> we don't set a timeout
[14:15] <kenvandine> so it is the default
[14:15] <asac> kenvandine: for dbus you mean?
[14:15] <kenvandine> yeah
[14:15] <asac> The default timeout in dbus-daemon is 25 seconds at the time of
[14:15] <asac> writing.
[14:16] <asac> http://osdir.com/ml/svn-commits-list/2009-10/msg00110.html
[14:16] <asac> ok let me run this with a really short timeout for a while and see if the UI breaks completely.
[14:16] <asac> kenvandine: so ... but still gwibber forntend seems not to like those timeout exceptions
[14:16] <asac> thought we tackled that ;)
[14:16] <asac> timeout exceptions == dbus timeouts
[14:17] <kenvandine> not really... we tackled the biggest culprit for needing those timeouts
[14:17] <asac> ok
[14:17] <asac> the nameownerchange
[14:17] <kenvandine> the exception handling needs to be factored in, which is too big of a beast to tackle for karmic
[14:17] <kenvandine> yeah
[14:17] <kenvandine> that solved a ton of problems
[14:17] <asac> ok let me see how crazy gwibber UI goes if facelib always times out
[14:17] <kenvandine> so part of the refactoring for lucid will include lower level exception handling
[14:18] <kenvandine> hehe
[14:18] <kenvandine> asac, the real key though is to commit the timeout and get it to the users
[14:18] <kenvandine> we went days without reproducing that bug
[14:19] <asac> well.
[14:19] <kenvandine> it was very hit and miss... like certain behaviors on facebook servers
[14:19] <asac> i can simulate what happens on timeout ;)
[14:19] <kenvandine> yeah
[14:19] <kenvandine> i think that shouldn't break the ui
[14:19] <asac> so first thing that happens is that authorization fails
[14:19] <kenvandine> it will just show up in the error stream
[14:19] <asac> and then it gives up
[14:19] <kenvandine> that blows...
[14:19] <kenvandine> makes you re-auth
[14:19] <asac> now i need to somehow make this so it doesnt bail out on authoriization
[14:20] <asac> kenvandine: how many calls does it do for authorization?
[14:20] <kenvandine> i think only one
[14:20]  * kenvandine doesn't know the facebook code though
[14:20] <asac> kenvandine: want to like do 3 times normal and then 1 second to see what happens if content pulling times out
[14:20] <kenvandine> if you hit it too many times facebook disables you and makes you re-auth anyway
[14:30] <rickspencer3> hey all, what's the word on the street?
[14:30] <seb128> hey rickspencer3
[14:30] <rickspencer3> bonjour seb128
[14:30] <seb128> still looks good I would say
[14:31] <seb128> I've been running the indicator message during the weekend and now wait for ted ;-)
[14:32] <rickspencer3> good
[14:32] <seb128> am I the only one to not notice new messages because the icon change is to subtle there?
[14:32] <rickspencer3> seb128, probably not
[14:32] <chrisccoulson> seb128 - you're not the only one ;)
[14:32] <rickspencer3> I saw lots of uploads, not not too many bug reports today
[14:32] <seb128> it sort defeat the purpose of the indicator
[14:32] <pitti> hey rickspencer3, good moring
[14:32] <seb128> I've also issue that pidgin get autokicked out of the launcher list
[14:32] <pitti> "morning" even
[14:33] <rickspencer3> hi pitti
[14:33] <seb128> and that missing control and piding conflict if you run empathy and switch back to pidgin
[14:33] <rickspencer3> hmmm
[14:33] <rickspencer3> seb128, are there bug #s for those?
[14:33] <seb128> ie if you use the session menu status pidgin displays a "you connected from an another client, closing those accounts"
[14:34] <seb128> rickspencer3, not sure I wanted to check with ted before file bugs
[14:34] <rickspencer3> k
[14:34]  * rickspencer3 runs bughugger
[14:38] <gnomefreak> seb128: i need to re enable log in screen but cant find it in gconf do you know the path off hand to do that? i want to make sure of something
[14:39] <seb128> gnomefreak, login screen?
[14:39] <seb128> gnomefreak, use gdmsetup to change the option?
[14:39] <gnomefreak> seb128: will try
[14:40] <gnomefreak> seb128: thanks that should work
[14:40] <seb128> gnomefreak, you can also use a guest session from the session menu
[14:41] <gnomefreak> seb128: i made new user, needed one anyway. but log out than in with new user made it work but that was after logging out with panel working for most part.
[14:42] <dobey> seb128: hey
[14:43] <seb128> hi dobey
[14:43] <dobey> how's it going?
[14:43] <seb128> busy with GNOME 2.28.1 updates but good otherwise
[14:43] <seb128> you?
[14:44] <dobey> alright. i did bug #453328 on friday, but doesn't look like it's been sponsored yet...
[14:46] <seb128> dobey, I will have a look, not surprising since most canonical people don't work during weekend
[14:46] <seb128> hey tedg
[14:46] <dobey> yeah
[14:47] <tedg> Good morning seb128
[14:47] <seb128> pitti, could you have a look to the debdiff on bug #455181 when you have a moment? it's trivial but syncs would bypass the queue
[14:47] <seb128> tedg, so I've several issues with your components, can you tell me which are known?
[14:47] <seb128> tedg, the pidgin launcher get quick off regularly, I think that's when I reboot with pidgin running, does it make sense?
[14:49] <seb128> tedg, I also tried empathy and went back to pidgin, but now when I change my status in indicator session it says an another client has connected and pidgin disconnect
[14:49] <seb128> tedg, I guess mission control is running and indicator session change the status there which conflict with the pidgin one
[14:50] <seb128> tedg, and the indicator applet icon change it to subtle but you probably have bugs about that
[14:50] <tedg> seb128: Uhm, no it should blacklist itself when rebooting.
[14:50] <tedg> seb128: That doesn't make sense :)
[14:50] <seb128> should?
[14:50] <tedg> shoudln't.
[14:50] <seb128> ok
[14:51] <seb128> there is a bug there and an annoying one
[14:51] <tedg> Yeah, so you can recreate it then?
[14:51] <seb128> I got it twice since friday so it's easy to trigger
[14:51] <seb128> can we just turn the code which dynamically drop launch off for karmic?
[14:51] <cassidy> seb128, thanks for the forwarded crash reports. I fixed a bunch of them; fixes will be in 2.28.1
[14:51] <tedg> Sure.
[14:51] <seb128> tedg, well I think it has been after session restarts or reboots
[14:52] <seb128> cassidy, I've seen, thanks for the good work, maybe I will find empathy good enough to use it next cycle ;-)
[14:52] <tedg> seb128: It is odd though, I don't understand what could be causing it.
[14:52] <cassidy> seb128, :p
[14:52] <seb128> tedg, is the code useful for something?
[14:52] <pitti> seb128: replied
[14:52] <tedg> seb128: I wonder if one of those cases we're getting a "disable" signal from Pidgin.
[14:52] <cassidy> seb128, are you going to ship 2.28.1 ?
[14:52] <seb128> cassidy, if you roll a tarball today yes
[14:52] <cassidy> I will
[14:52] <cassidy> deadline is today so...
[14:53] <seb128> cassidy, just to not be only a troll what make we switch back to pidgin this weekend is that empathy handle very poorly disconnects
[14:53] <tedg> seb128: Well, the idea was that you could remove lauchers by removing the feature in Pidgin.  The harder part is determining when you've removed the feature in Pidgin.
[14:53] <seb128> cassidy, ie you don't even have a try again button is the list, so once your internet is back you have no way out of closing it and starting empathy again to reconnect
[14:53] <seb128> and it seems to never retry by itsefl if you wait
[14:53] <cassidy> seb128, Empathy should rely on network manager
[14:54] <seb128> cassidy, I never disconnected from the network it's just the gateway which was down
[14:54] <Laney> I've found that Empathy tries to reconnect *too much* if I move to another machine
[14:54] <Laney> keeps stealing the connection back
[14:54] <cassidy> seb128, MC tries to reconnect using an exponential backoff iirc
[14:55] <seb128> pidgin has a "retry" next to the error in the buddy list
[14:55] <seb128> so when you know you have fixed your network you can retry
[14:56] <seb128> I might not have waited long enough
[14:56] <cassidy> seb128, seems a good thing to have. Please open a bug suggesting to add such button
[14:56] <seb128> cassidy, will do
[14:56] <cassidy> thx
[14:56] <seb128> thank you for all the work you are doing ;-)
[14:57] <seb128> tedg, ok, I don't fancy to reboot my box now to try that indicator thing again, I should try in a vm
[14:57] <Laney> can someone have a look at the ndesk-dbus sync? 454273
[14:57] <seb128> tedg, is the mission control fight with pidgin when empathy not running known?
[14:57] <tedg> seb128: When you reboot, is the timestamp on the file when you logout, or when you log back in?
[14:58] <tedg> seb128: It's somewhat inevitable with us supporting both clients.
[14:58] <seb128> tedg, I will have to check
[14:58] <seb128> tedg, well, you could look if empathy is running before changing the mission control status
[14:58] <seb128> tedg, or not change it if pidgin is running
[14:59] <tedg> seb128: We couldn't check that before because Empathy wasn't registered on the bus.  But, I didn't check that in Karmic.
[14:59] <seb128> tedg, and pidgin?
[14:59] <tedg> seb128: Well, it is possible that someone would want to run Pidgin and Empathy simultaniously.
[14:59] <tedg> seb128: I don't think we can be exclusive like that.
[15:00] <seb128> well I expect you will rather run in cases where mission control is running for some reason and pidgin is used as im rather than in cases where 2 im are running
[15:01] <tedg> Ah, cool.  Empathy is on the bus now.  With the object "EmpathyMoreThanMeetsTheEye" :)
[15:01] <tedg> To be honest.  My plan is to use Empathy for Jabber and Pidgin for other protocols.
[15:01] <seb128> your plan as an user?
[15:01] <tedg> Empathy's IRC support is just too bad.
[15:01] <tedg> Yes.
[15:02] <seb128> why do you insist on using an IM client for IRC ;-)
[15:02] <seb128> install xchat-gnome
[15:02] <tedg> XChat is just too ugly.
[15:02] <seb128> that's why we have the -gnome version
[15:03] <tedg> I wonder if we're getting registered with Mission Control as a client because we're using libempathy.  When in reality, we shouldn't be a client at all.
[15:04] <cassidy> seb128, https://bugs.edge.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/451984 would be good to have btw
[15:05] <tgpraveen> seb128: cassidy that bug requiring a "retry" option to be present is already filed and also there were some comments on how it should be done iirc
[15:07] <seb128> cassidy, looking
[15:10] <seb128> pitti, ^ could you have a quick look to the telepathy-gabble debdiff too, same reason, it's a sync request
[15:10] <seb128> pitti, thanks!
[15:12] <pitti> seb128: replied (ack'ed); do you want to process those syncs yourself, or need help?
[15:12] <seb128> pitti, I'm doing those but thanks
[15:13] <pitti> seb128: ok; I'll update gpm now, and then debug bug 425411
[15:13] <seb128> pitti, ok thanks
[15:13] <pitti> unless you have something more urgent
[15:13] <seb128> pitti, I'm handling updates and sponsoring mostly good now
[15:13] <pitti> I'll do some sponsoring tonight as well
[15:13] <seb128> pitti, so if you can keep waiving things I upload in we are on track ;-)
[15:13] <pitti> hehe, thanks
[15:14]  * seb128 hugs pitti
[15:14]  * pitti hugs back seb128, great work
[15:14] <seb128> cassidy, telepathy-gabble update synced
[15:15] <cassidy> seb128, thanks
[15:15] <seb128> cassidy, thank you for pointing it ;-)
[15:17] <slomo> seb128: hi, until when is it possible to sync NEW packages to universe? :) and what's your oppinion on the gst-plugins-good0.10 sync?
[15:17] <seb128> slomo, hey, I did backport the gst changes earlier today
[15:18] <seb128> I didn't sync because we have local changes and the gudev change is a bit late in cycle now
[15:18] <seb128> I did took the debdiff from you update yesterday and applied it to karmic though
[15:18] <slomo> seb128: ok, thanks :)
[15:18] <seb128> slomo, NEW, I don't think it's possible, is the NEW queue public now?
[15:19] <seb128> slomo, btw do you know if somebody is working the bug #597198?
[15:19] <seb128> gnome bug #597198
[15:20] <seb128> slomo, it gets quite some duplicates
[15:22] <slomo_> seb128: *sigh* the network here is really bad
[15:22] <slomo_> seb128: no, i meant, is it possible to get a NEW package into karmic at this point?
[15:22] <slomo_> seb128: i would need boost1.39 or boost1.40 (parallel installable with the current 1.38 in karmic)
[15:22] <seb128> slomo_, can't you just upload to universe? you are still motu no?
[15:23] <slomo_> seb128: sure, but i don't need any changes over the debian package :) and i don't know if it could still get accepted
[15:24] <seb128> slomo_, we can't sync from NEW and I can't sync things directly now anyway due to the freeze in action for karmic
[15:24] <seb128> syncs would bypass the review queue
[15:24] <seb128> so if you want it in karmic feel free to upload a fake sync and wait for review
[15:24] <seb128> or open a bug and subscribe r-t to it
[15:25] <slomo_> seb128: it's accepted in debian, the "NEW" part was meant for ubuntu :)
[15:25] <seb128> oh ok
[15:25] <seb128> could you open a bug and subscribe the motu r-t to it?
[15:27] <slomo_> seb128: sure
[15:27] <seb128> slomo_, thanks
[15:27] <seb128> slomo_, btw did you get my ping about this subtitle bug?
[15:27] <seb128> slomo_, gnome bug #597198
[15:28] <seb128> slomo_, it's getting quite some duplicates, do you know if it's being worked
[15:28] <pitti> slomo_, seb128: you need a new boost in universe?
[15:28] <pitti> I object to a new package in main at this point, but sync to universe is fine
[15:28] <pitti> (in main because of the version duplication)
[15:28] <seb128> pitti, it's for universe if I understood slomo_ correctly
[15:29] <slomo_> pitti: yes
[15:31] <pitti> sounds fine then
[15:32] <seb128> pitti, ok, should we just sync it then?
[15:32] <pitti> sure
[15:32] <slomo_> ok, do i still need to file a bug? launchpad is slow here, i'm still not at "enter bug" *sigh*
[15:32] <seb128> ok, I will do that in a bit if nobody else does it before then
[15:32] <slomo_> ok, thanks :)
[15:32] <seb128> I closed my rookery session for now and I've a slughish internet due to download
[15:33] <seb128> slomo_, which source do you need synced?
[15:33] <slomo_> seb128: "boost1.40"
[15:33] <slomo_> 1.39 would work too though
[15:33] <seb128> what is the difference?
[15:34] <Laney> if you're doing syncs....
[15:34] <slomo_> many bugfixes :)
[15:34]  * Laney whistles
[15:35] <slomo_> seb128: but no bugfixes that affect me, so i don't care... it would be better to sync boost1.40 ;)
[15:35] <seb128> no, I'm doing GNOME updates right now
[15:35] <seb128> slomo_, ok
[15:35] <seb128> pitti, do you think you can do the sync? I've having latency issues due to rsync run
[15:35] <slomo_> seb128, pitti: great, thanks :)
[15:35] <pitti> sure; slomo_, which package?
[15:35] <seb128> pitti, just a sync-source -b slomo boost1.40
[15:35] <slomo_> pitti: "boost1.40"
[15:36] <seb128> pitti, thanks
[15:36] <pitti> oops, seems there are pending syncs in the queue
[15:36] <Laney> yeah looks like it hasnt been done for a while
[15:36] <seb128> Laney, what? syncs?
[15:37] <Laney> right
[15:37] <Laney> we had a banshee one for a few days
[15:37] <Laney> hmm, was done, just that LP is lagging
[15:37] <pedro_> aagg
[15:37] <seb128> hey pedro_
[15:37] <seb128> pedro_, what?
[15:38] <pedro_> kenvandine, do you know of any way to kill the gwibber daemon from the ui when you quit the application?
[15:38] <pedro_> seb128, hello dude
[15:38] <pedro_> nothing just gwibber annoying me
[15:38] <pedro_> if i quit the application i'm still getting messages on the notification bubbles
[15:38] <kenvandine> pedro_, no... but i really want to do that
[15:38] <seb128> seems lot of people there are web2 addicts and run gwibber ;-)
[15:38] <kenvandine> but it isn't as trivial as you would think
[15:38] <pedro_> if i quit the application is because i don't want to receive those anymore
[15:38] <seb128> I manage to open facebook in firefox once a week now
[15:38] <seb128> I still have to learn ;-)
[15:39] <pedro_> seb128, facebook is way weird to use the first weeks
[15:39] <pedro_> too many options and crazy stuffs
[15:40] <pedro_> kenvandine, alright guess 'kill' would solve it for now
[15:40] <pedro_> found bug 439767
[15:41] <dobey> ugh
[15:42] <dobey> (as in ugh, why would you want to close the daemon)
[15:42] <dobey> :)
[15:43] <slomo_> seb128: for the subtitle bug, i'll take a look at it tomorrow. is that new after my decodebin2 changes?
[15:43] <seb128> slomo_, no
[15:43] <seb128> slomo_, thanks
[15:44] <seb128> or I don't think so let me check
[15:45] <seb128> slomo_, right first bug was opened before the changes
[15:45] <slomo_> thanks
[15:46] <rickspencer3> kenvandine, pedro_, seb128 - if we wanted to make such a change to gwibber, we could do it after Karmic releases, right? as it is in universe and all
[15:46] <popey> uhm, was there a discussion about how notify can tell you stuff you dont want to know, as soon as you power up the machine? e.g. I found out the forumla one result because someone tweeted it. I opened up my laptop on Sunday evening and had no way to stop the notification before it appeared. Do we really want notify to default on?
[15:47] <seb128> rickspencer3, in lucid you mean right?
[15:47] <seb128> rickspencer3, when karmic is switched stable it's for universe too
[15:47] <rickspencer3> seb128, no, I mean in Karmic
[15:47] <rickspencer3> but I thought universe for a stable release had much lower bar for updates
[15:47] <seb128> right, for srus it has
[15:47] <pedro_> rickspencer3, well an sru is always welcome, i woudn't put a lot of efforts into that now
[15:48] <seb128> I'm not the one granting exceptions there though
[15:48] <rickspencer3> hehe
[15:48] <seb128> if the update doesn"t add a new option or string
[15:48] <pitti> slomo_: boost1.40 synced/source NEWed
[15:48] <seb128> ie doesn't break string freeze
[15:48] <rickspencer3> probably best to channel resources into Lucd atm
[15:48] <seb128> right
[15:48] <pedro_> yup
[15:48] <rickspencer3> well ... really, fix bugs in Karmic this week
[15:48] <dobey> popey: notifications for things from twitter/etc.. that aren't @you seems broken to me
[15:48] <rickspencer3> quiting the daemon seems more a feature request than a bug
[15:49] <rickspencer3> but my point is, I would rather work on crashers, and if it turns out this quiting the daemon thing is a serious pita for users, we can sru that easily, as it's just a universe app
[15:49] <popey> dobey: this wasnt @me
[15:49] <slomo_> pitti: perfect, thanks :) how/when will someone look at the NEW queue?
[15:50] <pitti> slomo_: every day usually (archive days), but feel free to poke me when they built and it's urgent for you
[15:50] <dobey> popey: right, i presumed it wasn't. i'm just saying it sounds like a bug to me. getting notifications of every single tweet/dent/fbupdate is going to be annoying
[15:50] <slomo_> pitti: ok, tomorrow is early enough... thanks again :)
[15:50] <popey> dobey: thats less of a concern to me, I am more bothered that I can't turn it off
[15:51] <dobey> popey: i'm pretty sure you can turn it off
[15:51] <popey> dobey: i was just sat down to watch the F1, I'd stayed away from news/irc/radio, and then up pops someone telling the whole world the result in my notify
[15:55] <dobey> popey: i understand your pain
[16:13] <rickspencer3> kenvandine, have empathy sounds not been uploaded?
[16:13] <rickspencer3> https://bugs.edge.launchpad.net/ubuntu/+source/empathy/+bug/400485
[16:13] <rickspencer3> seems to be fixed for me
[16:14] <seb128> rickspencer3, TheMuso did an upload to fix that bug
[16:15] <rickspencer3> or it just that there are two still missing?
[16:15] <seb128> rickspencer3, why do you ask if it's working?
[16:15] <rickspencer3> seb128, because the bug is New, but seems that sounds started for me some days ago
[16:15] <rickspencer3> the bug is targeted, so wanted to know if there was still work for it
[16:16] <seb128> rickspencer3, see recent comments there
[16:16] <seb128> seems message-sent-instant and phone-outgoing-calling are not there
[16:16] <seb128> that's why it has been reopened
[16:16] <seb128> and phone-hangup too
[16:16] <seb128> but the freedesktop sound theme doesn't have those
[16:16] <seb128> so I guess it's not something which will change before karmic now
[16:17] <seb128> the theme has sounds for new messages and users login in and out
[16:17] <seb128> I guess that's what most users need
[16:17] <rickspencer3> ok, Iid like to take it off the list, but I can't set to invalid until I can assign it to Lucid I guess :(
[16:17] <seb128> pitti, do you have any opinion about http://git.gnome.org/cgit/gnome-settings-daemon/commit/?id=ee29f7a34a56808a558b9114ce499c47cbe35972?
[16:18] <seb128> rickspencer3, what list? I though that low bugs were not on any list
[16:19] <seb128> pitti, it's the only change out of translation updates in the g-d-s update
[16:19] <seb128> pitti, not sure if that's something that would work well with your change or that we should get now or just ignore
[16:20] <rickspencer3> seb128, I track everything that's targeted, though I don't expect anything but High+ to be fixed
[16:21] <rickspencer3> if it's targeted though, that assumes that the assignee still wants to work on it
[16:21] <seb128> rickspencer3, unassign it?
[16:21] <rickspencer3> meh
[16:21] <rickspencer3> I already wasted too much time on it, but good to understand what's up ;)
[16:21] <seb128> rickspencer3, I've no good reply for your isue
[16:21] <seb128> issue
[16:21] <rickspencer3> it's a launchpad thing
[16:21] <seb128> the bug is valid and can't be closed
[16:22] <seb128> right
[16:22] <rickspencer3> I don't want to close it, just untarget it
[16:22] <seb128> you can't
[16:22] <rickspencer3> right, that's what I was venting about
[16:22] <rickspencer3> but it's not a problem really
[16:23] <james_w> you need to mark it "Won't Fix" to untarget it
[16:23] <rickspencer3> it's just me being overly tidy
[16:23] <rickspencer3> james_w, right, at which point users go crazy because I won't fixed a valid bug
[16:23] <rickspencer3> or upstreams sometimes too ;)
[16:23] <james_w> just leave a comment saying that it is "Won't Fix" only for karmic tracking
[16:24] <seb128> james_w, there is no other task
[16:24] <james_w> it will be fixed later, and maybe even for karmic
[16:24] <rickspencer3> james_w, we've been down this path :)
[16:24] <james_w> seb128: the untargetted task reappears when you wont-fix the targeted one
[16:24] <rickspencer3> in any case, let's just drop it, and focus on real issues that we can fix before Thyr
[16:24] <rickspencer3> Thursday even
[16:24] <seb128> james_w, you don't expect us to note those bugs manually and go over after karmic+1 opening to open new tasks?
[16:24] <james_w> you don't need to
[16:25] <seb128> are you sure it reopen the untargetted task?
[16:25] <james_w> YES!
[16:25] <seb128> hum
[16:25] <seb128> we had the case on an empathy bug the other day and I don't think it did
[16:30] <pitti> seb128: oh, I think it makes sense; it's the remaining case of confusion which we have for gdm keyboard layout I think
[16:32] <seb128> pitti, it's changing the same code as your patch and you know how to test those change, do you think you could do the update?
[16:32] <pitti> seb128: yes, can do
[16:32] <seb128> pitti, thanks!
[16:39] <dobey> Amaranth: compiz is working again! hooray! :)
[17:45] <seb128> cassidy, https://bugzilla.gnome.org/show_bug.cgi?id=593086 seems to be a frequent issue
[17:45] <seb128> cassidy, do you know if anybody is looking at it?
[17:45] <seb128> cassidy, see the number of duplicates on bug #408530
[17:48] <cassidy> seb128, we already looked at it and have no clue of what the problem could be :(
[17:48] <seb128> cassidy, could you ask for logs, details or something?
[17:48] <cassidy> seb128, I'd be interested to know if it still happen in 2.28.1 though as it COULD be a side effect of another bug we fixed
[17:48] <seb128> ok
[17:48] <seb128> roll 2.28.1 and I will get you testing ;-)
[17:48] <cassidy> so let me know if you have dup with this version
[17:48] <cassidy> seb128, distchecking atm :)
[17:49] <seb128> cassidy, cool!
[17:49] <seb128> cassidy, will do
[17:49] <seb128> it's going to be late for karmic if it's not fixed though
[17:51] <cassidy> yeah :\
[17:51] <cassidy> it's a nasty one
[17:57] <and471> mpt: hi
[17:57] <and471> mpt: I was wondering whther you could give me a quick answer on this bug? https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/455327
[18:04] <mpt> and471, done (short answer: modal with no title)
[18:05] <and471> mpt: okay thanks
[18:05] <pitti> kenvandine: can you please have a look at bug 437828 and check whether we want/need this?
[18:05] <pitti> kenvandine: (please just reply on the bug)
[18:07] <mac_v> seb128: hi , why is this a icon theme bug ? Bug #454013 , the reporter has said that the documentation doesnt match
[18:07] <kenvandine> pitti, ok
[18:07] <seb128> mac_v, I didn't read carefully the bug I though he was complaining about the icon used there
[18:07] <seb128> mac_v, feel free to close the bug
[18:07] <seb128> mac_v, you can't expect the documentation to adapt dynamically to your theme
[18:08] <mac_v> seb128: or is it a documentation bug?
[18:08] <mac_v> oh ok ;)
[18:09] <mac_v> seb128: but seems the docs havent been updated since the humanity theme was used , the trash can was never used in humanity theme , i suspect the docs still use the human theme
[18:09] <seb128> mac_v, the documentation is probably upstream one and use the gnome theme
[18:10] <mac_v> seb128: ah , so the Ubuntu docs havent been updated , so it would be a bug in which package?
[18:11] <seb128> mac_v, you don't expect us to patch every package documentation to have ubuntu screenshots do you?
[18:11] <mac_v> seb128: aernt the docs supposed to do that? they need to be updated accordingly
[18:11] <seb128> lol
[18:11] <mac_v> ;p
[18:11] <seb128> mac_v, there is screenshots for like 15 locales in every package
[18:12] <seb128> mac_v, it would be one month of work every cycle for the desktop team or something to do that
[18:12] <seb128> thousand of screenshots to distro patch
[18:12] <mac_v> hehe...
[18:12] <seb128> you are not being realistic there
[18:13] <chrisccoulson> i thought mac_v just volunteered to patch all the screenshots there ;)
[18:13]  * mac_v hides
[18:13] <chrisccoulson> lol
[18:13] <didrocks> even for a book, it's difficult to redo everytime all screenshots :)
[18:13] <seb128> and didrocks can tell ;-)
[18:13] <didrocks> oh yes ^^
[18:14] <chrisccoulson> didrocks - if your book has lots of screenshots, then i might understand it :)
[18:14] <didrocks> especially this time, I suffered a lot for post-beta theme changes :/
[18:14] <didrocks> chrisccoulson: approx. 300 images (130 from softwares and games)
[18:15] <didrocks> so, let's say 100+ to change every 6 monthes :)
[18:15] <chrisccoulson> that's quite a bit of work ;)
[18:15] <didrocks> indeed :)
[18:16] <mac_v> seb128: i'm not sure what to close the bug as! the reporter's request is reasonable , users do get confused when different icon themes are used in the help screenshots... but surely it is a tough task for the docs team to update the docs... not sure what to do :(
[18:17] <seb128> mac_v, you can start by asking in which documentation he saw those
[18:17] <mac_v> hmm , ok
[18:17] <seb128> if that's in the empathy package we are not going to change it
[18:18] <seb128> changing binaries in a source is lot of work
[18:18] <seb128> and it would require changing screenshots for all locales there
[18:18] <seb128> if that's in the ubuntu documentation you can reassign as a wishlist there
[18:18] <seb128> it sort of sucks but we don't have the manpower nor the tools to do easy screenshot changes
[18:19] <seb128> didrocks, chrisccoulson: you can pick any update not done yet and work on it if you want
[18:19]  * seb128 is away for sport and dinner, bbl
[18:19] <seb128> I will do sponsoring and some updates later
[18:19] <chrisccoulson> seb128 - no problem. i'll have a look at some updates in addition to the milestoned bugs as well
[18:22] <seb128> chrisccoulson, oh right, maybe start with the g-s-d bugs ;-)
[18:22] <seb128> I think pitti said he would do the update though
[18:22] <seb128> so check with him before starting on it if you want to do that one
[18:22] <pitti> I did
[18:22] <pitti> oh, did I forget to upload? darn
[18:22] <and471> mvo: I have just done some work in my branch fixing my bugs (merge please :-] ) https://code.launchpad.net/~rugby471/software-center/software-store-andrew
[18:22] <seb128> see ;-)
[18:22] <pitti> argh, I got distracted after testing
[18:22] <didrocks> seb128: ok, I'll try to tackle some :)
[18:23] <pitti> seb128, chrisccoulson: g-s-d 2.8.1 pushed and uploaded
[18:23] <chrisccoulson> seb128 - yeah, i'll start with g-s-d bugs. i can't recreate slangasek's issue though. i think i'll have to give him a special build to get more info about what is happening
[18:24] <chrisccoulson> pitti - thanks:)
[18:29] <pitti> chrisccoulson: can I ask you a favor? Would you mind to commit my patch in https://bugzilla.gnome.org/show_bug.cgi?id=596897 ? It just got approved
[18:30] <chrisccoulson> pitti - yeah, can do
[18:32] <didrocks> taking gnome-themes
[18:36] <pitti> good night everyone
[18:36] <kenvandine> later pitti
[18:37] <mvo> and471: cool, looking
[18:38] <chrisccoulson> pitti - done
[18:40] <chrisccoulson> pitti - would you mind closing the bug? (i can commit to GIT, but i can't edit gnome bugs) ;)
[18:41]  * chrisccoulson really needs to request those permissions
[18:41] <didrocks> good night pitti
[18:41] <mvo> and471: hm, after the merge I have two on_database_rebuild_handler s in my app.py - could you please have a look?
[18:43] <and471> mvo: really? I didn't touch that...
[18:43] <mvo> and471: maybe some sort of merge conflict?
[18:44] <and471> hmm. give me a sec
[18:45] <and471> mvo: actually could you just use the app.py that you had before the merge, I haven't made any changes to it
[18:45] <and471> mvo: or manually add the changes I made today
[18:47] <cassidy> seb128, released!
[18:47] <cassidy> seb128, http://lists.freedesktop.org/archives/telepathy/2009-October/003944.html
[18:49] <dobey> mpt: do you still have the oauth-login.log to correspond to bug #450386 ? it seems apport or something stripped the attachment (or failed to attach it)
[18:58] <dobey> i guess not
[19:32] <dobey> crap crap crap
[19:33] <dobey> guess i have to do another upload
[20:27] <asac> seb128: there? do you have this "restart required" behaviour atm?
[21:00] <seb128> asac, there now
[21:01] <seb128> asac, no
[21:01] <asac> ;) ok
[21:01] <asac> thx
[21:01] <seb128> asac, it seems to happen mostly after xulrunner updates
[21:01] <asac> seb128: how do you fix it?
[21:01] <seb128> and I usually clean things by hand because I need greasemonkey to work
[21:01] <asac> what cleaning exactly are you doing?
[21:01] <seb128> rm ext* in the profile directory
[21:01] <asac> yeah ok thats the hard way ;)
[21:01] <seb128> I don't know how any other
[21:02] <asac> seb128: for you its perfect way ;)
[21:02] <seb128> and greasemonkey is the only non standard thing I use
[21:02] <seb128> so it's easy enough ;-)
[21:05] <seb128> kenvandine, do you work on the empathy update?
[21:06] <seb128> kenvandine, I was starting on it and noticed your bug
[21:06] <kenvandine> seb128, yup
[21:06] <seb128> ok
[21:06] <seb128> I will find something else to do
[21:06] <kenvandine> just pushed :)
[21:06] <kenvandine> you can sponsor it :)
[21:06] <seb128> don't forget to close the bugs pending I did forward a bunch upstream which got closed
[21:06] <seb128> ok looking
[21:06] <kenvandine> it fixed quite a few bugs :)
[21:06] <seb128> yeah, shame that nobody forwarded crashes earlier
[21:07] <kenvandine> i had to update the patches slightly
[21:07] <seb128> I forwarded some 6 a week ago and they fixed most of those
[21:07] <kenvandine> cool... thx!
[21:07] <seb128> thank you for the update ;-)
[21:08] <seb128> I'm still pondering dropping the toggle change ;-)
[21:08] <seb128> but I guess I will not since it's a design choice and late now anyway
[21:08] <seb128> I'm wondering how trivial it would be to have a gconf key for that one
[21:10] <kenvandine> probably not hard
[21:10] <kenvandine> just add a gconf looking with an if statement
[21:10] <kenvandine> for lucid we should split that code up, so we can have different behavior for the icon and the indicator
[21:10] <kenvandine> hold off sponsoring that
[21:11] <kenvandine> looking at the symbols
[21:16] <kenvandine> seb128, there was a symbol added
[21:17] <seb128> kenvandine, that's ok, addition are fine we just don't want breakages
[21:17] <kenvandine> yeah
[21:17] <kenvandine> i added it to debian/libempathy30.symbols
[21:17] <kenvandine> and pushed
[21:17] <seb128> oh ok
[21:17] <seb128> updating and starting a new build
[21:24] <seb128> chrisccoulson, pitti: you guys should real sort your lack of bug edit or git commit rights
[21:26] <seb128> wth
[21:27] <seb128> something is putting my screen on sleep after one minute since I updated
[21:31] <chrisccoulson> hey seb128
[21:31] <chrisccoulson> yeah, i definately need to sort out my bug edit rights for gnome ;)
[21:31] <seb128> hello chrisccoulson
[21:37] <seb128> didrocks, thanks for the updates you did!
[21:40] <seb128> kenvandine, libempathy-gtk28.symbols
[21:40] <chrisccoulson> heh, i really should do some updates tonight!
[21:40] <seb128> + empathy_location_manager_dup_singleton@Base 2.28.1-1ubuntu1
[21:40] <seb128> + empathy_location_manager_get_type@Base 2.28.1-1ubuntu1
[21:40] <seb128> kenvandine, is that normal you didn't add those?
[21:40] <seb128> chrisccoulson, ;-)
[21:40] <kenvandine> i didn't see that
[21:40] <kenvandine> humm
[21:41] <seb128> kenvandine, it's in the build log there
[21:41] <seb128> and in the symbols diff between libraries
[21:42] <kenvandine> it's not in my log... weird
[21:42] <kenvandine> i only had the libempathy30 one
[21:43] <kenvandine> please add them :)
[21:43] <seb128> ok
[21:44] <kenvandine> thx
[21:49] <seb128> Amaranth, hey, I think one of the recent changes is borking compiz focus there
[21:50] <seb128> often when opening and closing a new dialog, like a text editor from a command line and close it the focus doesn't goes back where it was
[21:51] <rickspencer3> seb128, huh, that is easy for me to reproduce right in xchat-gnome
[21:52] <rickspencer3> only if I use the mouse to close the dialog
[21:52] <rickspencer3> so Alt+I, C opens the Connect dialog, and Alt-C closes it, focus back to main window
[21:52] <rickspencer3> but
[21:53] <seb128> I do use the mouse in those case because ctrl-w doesn't close gedit
[21:53] <rickspencer3> so Alt+I, C opens the Connect dialog, close by clicking with mouse, nothing has focus
[21:53] <seb128> it just close the document which is open but let gedit on screen
[21:53] <seb128> so could be the same yes, let me play a bit with it
[22:07] <Amaranth> seb128, rickspencer3: I can't seem to reproduce either one of those
[22:07] <seb128> Amaranth, open a g-t, gedit txt, type, close using the wm button
[22:07] <rickspencer3> Amaranth, hmm, i can repro seb128's
[22:07] <seb128> the focus doesn't go back to your command line
[22:08] <rickspencer3> seb128, your's repros when you use Alt-F4 as well, at least for me
[22:08] <seb128> and I'm using basic compiz standard profile with no change
[22:08] <Amaranth> I randomly have focus switch to mouse focus when opening and closing terminals
[22:08] <Amaranth> But I've had that forever and it's very random
[22:08] <seb128> I get it every single time today
[22:08] <Amaranth> meaning it seems like click to focus is off
[22:08] <Amaranth> Which is also what happens when you don't run a WM
[22:08] <seb128> so it probably started with the upgrades you did before the weekend
[22:09] <rickspencer3> yes, it happens every time for me, but I have no idea when it started
[22:09] <Amaranth> I don't think we even had any focus changes :/
[22:09] <seb128> Amaranth, right, if the cursor is over the other dialog I can type
[22:09] <seb128> but the decoration is not drawed as focussed either
[22:10] <rickspencer3> uh, this repros everwhere for me
[22:10] <chrisccoulson> seb128 - i had to update the patch for bug 409621 at the weekend, as the upstream one we uploaded last week didn't fix the issue. not sure if you want to sponsor that when you have some spare minutes?:)
[22:10] <rickspencer3> New mail message in evo for example
[22:10] <seb128> chrisccoulson, will do thanks
[22:10] <chrisccoulson> thanks!
[22:13] <Amaranth> seb128: so in that case it seems compiz is still running but perhaps the X window stack and the compiz one have gotten out of sync or something
[22:13] <Amaranth> No clue
[22:13]  * Amaranth stabs X
[22:16] <seb128> Amaranth, I get the issue in a guest session too
[22:17] <Amaranth> hmm, seems typing in gedit is the important part to reproduce
[22:21] <Amaranth> ah, not typing, the unsaved changes window
[22:21] <Amaranth> So perhaps after the modal window closes we try to give focus back to the parent but it parent is gone
[22:22] <seb128> I don't have an unsaved changes dialog
[22:22] <seb128> I do save my changelog changes before closing
[22:22] <seb128> (I'm doing package updates today)
[22:22] <Amaranth> hrm
[22:23] <Amaranth> I can only trigger it if I have that dialog open up
[22:23] <seb128> I get it in reliable way in a guest session
[22:23] <Amaranth> if I open an existing file, edit it, and save the focus is fine
[22:23] <seb128> did you try there?
[22:23] <Amaranth> no
[22:23] <Amaranth> I fear it's caused by the fix to make windows not move up when closed though
[22:23] <seb128> open a command line, gedit, click on the corner button
[22:23] <seb128> the command line decorator is uncolored
[22:24] <seb128> ie it doesn't get the focus back
[22:24] <seb128> I don't need to touch the keyboard or edit
[22:24] <rickspencer3> Amaranth, what seb128 said
[22:24] <rickspencer3> it's totally reliably for me to repro
[22:26] <seb128> Amaranth, I can try to roll back that change if you want
[22:26] <Amaranth> sure enough, guest session reproduces without typing at all
[22:26] <Amaranth> hmm, it also happened on VT switch...
[22:26]  * Amaranth starts backing out commits
[22:48] <Amaranth> Yeah the changes to fix windows moving on close are the only ones in core that seem to even be capable of causing this
[22:48] <Amaranth> I got pulled away so I haven't tested yet though
[22:48] <seb128> Amaranth, do you want me to try without that one?
[22:49] <Amaranth> seb128: well there are two commits for it
[22:49] <Amaranth> one that fixed that problem and a second that fixed minimizing windows after that one went in
[22:49] <seb128> well I can drop the patches from the package and rebuild easily
[22:49] <Amaranth> I'm worried about the second (one line) fix
[22:49] <Amaranth> it's not patches in our package
[22:49] <seb128> oh ok
[22:50] <seb128> let me know if you have a diff to try though
[22:51] <Amaranth> well if these commits are the cause we can't just back them out
[22:52] <seb128> ok
[22:52] <Amaranth> so I'll probably have to talk to cornelius1 about it if I can't figure it out
[22:52] <seb128> do you have a webgit diff or something for those?
[22:52] <seb128> so I can try without them and tell you if that works
[22:52] <seb128> or can look to that one?
[22:52] <Amaranth> http://git.compiz.org/compiz/core/patch/?id=8dcfbb256322565228cbcda5230de95343887fac and http://git.compiz.org/compiz/core/patch/?id=0a28ca484a8a72060b580e0ccc75ea20f3ddab1a
[22:52] <Amaranth> you have to back them out in that order
[22:53] <seb128> ok
[22:54] <Amaranth> I'm building with the first one backed out now
[22:55] <seb128> I forget that you need to install kde to build compiz
[22:55] <seb128> I will try first then ;-)
[22:57] <Amaranth> seems more people are using karmic now
[22:57] <Amaranth> getting more bug reports :P
[22:58] <seb128> hey robert_ancell
[22:58] <robert_ancell> seb128, hey
[22:59] <seb128> it's weird to see you so earlier since the dst change ;-)
[22:59] <robert_ancell> seb128, yeah, I keep going in the evenings - "where is everyone?"
[23:01] <robert_ancell> seb128, bug 443312 - is that marked appropriately to use the Debian version?
[23:02] <seb128> robert_ancell, syncs are fine but you need to add a debdiff to the bug since those can't be synced without bypassing the freeze now
[23:02] <robert_ancell> and is that included in the exception?
[23:02] <seb128> ie people who do review need to have a debdiff on the bug
[23:02] <seb128> yes, it should be fine to update as long as it's a bug fix version
[23:05] <seb128> robert_ancell, not sure if updates like the gnome-games one are worth doing
[23:05] <Amaranth> ok so it's not that first commit...
[23:06] <robert_ancell> seb128, the -extra-data or the main package?
[23:06] <seb128> robert_ancell, gnome-games
[23:06] <robert_ancell> seb128, why not?
[23:06] <seb128> reading the news summary on the ftp list, it's only clutter aisleriot changes
[23:06] <seb128> and some translations
[23:06] <seb128> do we use clutter for aisleriot now?
[23:06] <robert_ancell> yes
[23:06] <robert_ancell> and it's pretty buggy
[23:07] <seb128> oh ok
[23:07] <seb128> I didn't realize that we needed clutter to play card game now
[23:07] <robert_ancell> oh, no aisleriot is using the non-clutter version - I was thinking on gnometris
[23:07] <robert_ancell> of
[23:07] <seb128> right
[23:08] <seb128> so the update is pretty useless for us, better to focus on ones fixing bugs
[23:08] <robert_ancell> what about the translations?
[23:08] <Amaranth> seb128: it's that second commit I linked to
[23:08] <seb128> but if we run out of useful ones we can still look at those
[23:08] <seb128> robert_ancell, I doubt they will travel to rosetta and back to language packs before the freeze now
[23:08] <seb128> but I might be wrong, I didn't check this cycle
[23:09] <Amaranth> So right now the choice is a cosmetic error (without that commit) or a focus issue (with it)
[23:09] <seb128> it was taking several days to have an import export rounds previous cycle
[23:09] <robert_ancell> seb128, how do you debdiff a Debian package?
[23:09] <seb128> robert_ancell, debdiff current.dsc update.dsc
[23:09] <seb128> ie apt-get source on karmic
[23:09] <seb128> dget the debian.dsc
[23:09] <seb128> and debdiff both
[23:09] <rickspencer3> Amaranth, is there a bug report for the specific cosmetic issue?
[23:10] <rickspencer3> the focus issue is very annoying
[23:10] <seb128> yes
[23:10] <seb128> and agreed with rick, we should fix the focus one
[23:10] <rickspencer3> btw, Amaranth you rock, thanks for tracking this down so quickly
[23:11] <rickspencer3> well, I'd like to see the bug # before we pass judgment too quickly ... but focus problems can have bad problems for people who can't use mice for whatever reason
[23:11] <rickspencer3> so accessibility-wise, focus problems are pretty evil
[23:11] <seb128> I can use the mouse but it's totally breaking my workflow
[23:12] <seb128> and I expect I'm not the only one expecting to be back to the command line when closing an editor
[23:12] <seb128> rickspencer3, bug #444836
[23:14]  * TheMuso pricks up his ears.
[23:25] <rickspencer3> Amaranth, seb128 so the compiz patch is supposed to keep this from happening:
[23:25] <rickspencer3> http://dking.dk.funpic.de/BUG1.png
[23:25] <rickspencer3> ?
[23:26] <rickspencer3> I can't even tell what the issue is, but this seems an unsupported compiz effect, right?
[23:26] <chrisccoulson> rickspencer3 - when you press the close button, the window jumps up by about the width of the title bar
[23:27] <seb128> not sure if that's happening in the default config, I didn't notice it there but in some case you are the dialog shitfting on closing
[23:27] <seb128> are -> have
[23:28] <rickspencer3> does this seem an incredibly minor issue?
[23:28] <rickspencer3> or am I missing something?
[23:28] <seb128> it seems minor to me yes
[23:28] <rickspencer3> ok, so breaking focus breaks accessibility, so that's a major issue for sure ;)
[23:29] <rickspencer3> Amaranth, so you can safely revert that patch?
[23:30]  * rickspencer3 hates making changes this close to release
[23:30] <rickspencer3> even little things make me nervous ;)
[23:30]  * TheMuso notes that a lot of blind/vision impaired users using speech will not likely use compiz.
[23:36] <robert_ancell> seb128, there are literally no changes in gucharmap 2.28.1 except for the version bump.  They really like to make releases...
[23:39] <seb128> robert_ancell, ok, don't bother with it then
[23:39] <robert_ancell> seb128, yeah, I'm really having to look to find anything worth updating here
[23:42] <seb128> robert_ancell, I'm doing the libsoup update now if you didn't start
[23:42] <robert_ancell> seb128, looking at gnome-terminal
[23:42] <seb128> robert_ancell, chrisccoulson just said he started on it
[23:43] <chrisccoulson> i have:)
[23:43] <seb128> whoever do an update could you tell it on the channel too?
[23:43] <seb128> the versions page updates only every half an hour
[23:43] <seb128> it gives margin to duplicate work too
[23:45] <robert_ancell> TheMuso, are you doing mousetweaks?
[23:46] <seb128> robert_ancell, you can do eog if you want
[23:47] <robert_ancell> seb128, ok, I got to the bottom of the versions list.  You guys all need to go to sleep so there's some left for me :)
[23:47] <seb128> robert_ancell, I'm done after the libsoup one
[23:48] <TheMuso> robert_ancell: Mousetweaks done, gok done, orca done.
[23:48]  * robert_ancell wants to integrate versions into LP...
[23:48] <seb128> TheMuso, hey, not sure how busy you are today but if you could sponsor robert_ancell's updates during your day
[23:49] <TheMuso> robert_ancell: If/when gnome-media pops up, feel free to do it, and prod me for sponsoring. I have other things that I want to look at today, so am happy for someone else to do that.
[23:49] <TheMuso> seb128: Yeah I can do that.
[23:49] <seb128> slangasek want to try to roll images early european time tomorrow
[23:49] <robert_ancell> TheMuso, ok, will do
[23:49] <TheMuso> But yeah happy to sponsor
[23:49] <seb128> so it would be nice to have those built earlier
[23:49] <TheMuso> seb128: I saw that.
[23:49] <seb128> TheMuso, thanks
[23:50] <TheMuso> np
[23:50] <robert_ancell> what feed are people using to see new packages come in?  I'm following the announce list which seems to be behind the tarballs which are behind what you are tracking
[23:50] <TheMuso> robert_ancell: gnome-ftp list
[23:50] <TheMuso> I was the same at the beginning, using the annoucne list, but seb128 suggested gnome-ftp, which is much more useful.
[23:50] <robert_ancell> ftp-release-list?
[23:50] <seb128> yes
[23:51] <seb128> not every maintainer write an announce email
[23:51] <seb128> and sometime they do hours after the upload
[23:51] <TheMuso> Sorry, I was referring to the mailbox I have it going into. :)
[23:51] <Amaranth> rickspencer3, seb128: The cosmetic thing is not as important for using compiz but users were for some reason freaking out about it
[23:51] <seb128> the ftp list is the one true way ;-)
[23:51] <rickspencer3> :(
[23:51] <rickspencer3> Amaranth, what do you think is the right thing to do?
[23:51] <Amaranth> People kept telling me how terrible compiz was
[23:51] <seb128> Amaranth, I would not say freaking out but yeah, it got several duplicates
[23:52] <Amaranth> rickspencer3: Wait until tomorrow so I can try to fix or talk to cornelius1 about it
[23:52] <rickspencer3> personally, I never noticed it, did I have the wrong plug in?
[23:52] <seb128> if we have to pick the focus issue or the cosmetic one pick the cosmetic one
[23:52] <seb128> we can sru the cosmetic issue after karmic if required
[23:52] <Amaranth> of course
[23:52] <rickspencer3> Amaranth, I think we are past the point of going forward on fixing issues
[23:52] <rickspencer3> I would suggest that we role back the change and wait for a fix after we release
[23:52] <rickspencer3> make sense?
[23:53] <Amaranth> rickspencer3: eh, not really...
[23:53] <rickspencer3> (note that our RC is in three days!)
[23:53] <Amaranth> If we have a fix tomorrow and it's small and obviously correct...
[23:53] <seb128> well, if the fix is a one liner and we can get it tomorrow I think it's fine to get it
[23:53] <seb128> what Amaranth said
[23:53] <Amaranth> If we have a fix tomorrow and it's a 200 line diff on the other hand, skip it
[23:53] <seb128> we are still getting GNOME 2.28.1 updates
[23:53] <rickspencer3> hmmm
[23:53] <seb128> they have many bug fixes, I don't see that one much different
[23:54] <rickspencer3> I'll log a bug on the focus issue, and target it
[23:54] <seb128> thanks
[23:54] <Amaranth> alright, thanks
[23:54] <Amaranth> marked as High, of course
[23:54] <Amaranth> otherwise I'll lose it in the flood of New
[23:54] <rickspencer3> I don't want to forget about it until the last minute
[23:54] <rickspencer3> Amaranth, assign to you?
[23:54] <Amaranth> sure
[23:56] <Amaranth> So looking at this diff it seems to be what I originally thought, the compiz window stack and the X one are out of sync
[23:57] <Amaranth> I can toss in a function to force them to sync up again as a worst case fix
[23:57] <Amaranth> s/function/function call/


[01:30] <dazza5000> anyone able to help me troubleshoot a calendar autopilot test?
[01:30] <dazza5000> the test fails because it thinks the day on my computer is yesterday
[01:31] <dazza5000> but the calendar app selects the correct day for today
[01:31] <dazza5000> and when I run the commands in python outside of the test they give the correct date
[01:39] <dazza5000> this test
[01:39] <dazza5000> autopilot3 run calendar_app.tests.test_monthview.TestMonthView.test_monthview_go_to_today_prev_year
[01:39] <dazza5000> gives this
[01:39] <dazza5000> testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: 22 != 21
[01:40] <dazza5000> datetime.now() gives 2015-03-22 20:40:24.686199
[01:41] <dazza5000> but the test is getting 21 as the result somehow
[16:08] <elopio> I had to join using the webchat.
[16:08] <elopio> for some reason, I can't connect to freenode with quassel.
[16:09] <elopio> if I don't reply quickly, it's because I have no notifications.
[16:16] <paulliu> elopio: hi.. So I'm wondering why fake-apps doesn't start on the AP test for shell-rotation.
[16:18] <paulliu> elopio: and why we use fixtures to start unity8? Can we use ApplicationLifeCycleTestCase with environments set for the fake-sensor?
[16:19] <paulliu> elopio: Currently we copy the code from ApplicationLifeCycleTestCase, but it doesn't work as we expect.
[16:26] <elopio> hello paulliu. brendand, you are taking a look at the fake apps, right?
[16:28] <brendand> elopio, i am
[16:28] <brendand> elopio, right now unity8 doesn't start for some reason
[16:29] <elopio> brendand: that's nice, because you and paulliu have more working hours together (I think). It would be great if you two pair to investigate.
[16:30] <elopio> paulliu: we prefer fixtures over inheritance, because when you inherit test cases things get messy.
[16:30] <paulliu> brendand: why it doesn't start?
[16:30] <elopio> composition is clearer.
[16:30] <paulliu> elopio: ok..
[16:30] <paulliu> brendand: I mean, why unity8 doesn't start?
[16:31] <elopio> paulliu: if there's something useful from a test case setup, you can wrap that in a fixture and share it in both tests.
[16:31] <brendand> paulliu, i don't know yet. it seems to work ok in other tests
[16:31] <paulliu> elopio: ok.. just curious why we don't re-use the code.
[16:32] <elopio> paulliu: I wonder, do your life cycle tests work? is it only on the rotation tests that you get errors?
[16:32] <paulliu> brendand: hmm. you should adb reboot and it might work again.
[16:32] <paulliu> elopio: yes. Life cycle tests works find. It did start the apps.
[16:33] <paulliu> elopio: So I'm wondering if we make some weirdness by start unity8 in different ways.
[16:33] <paulliu> elopio: Just as brendand said, the unity8 might stop launching after you run the test several times. but adb reboot fixes it.
[16:34] <paulliu> elopio: also, the launched unity8 acts weird. If I touch the screen anywhere, it pops the on-screen-keyboard.
[16:35] <paulliu> elopio: In other tests, I'm able to interact with unity8 by touching the screen.
[16:36] <elopio> paulliu: brendand: yes, take a look at the launch_unity in the base UnityTestCase. That's different from the LaunchUnityWithSensors fixture.
[16:37] <elopio> ideally, we should turn the launch_unity in UnityTestCase into a fixture LaunchUnity. And use that fixture from LaunchUnityWithSensors.
[16:40] <elopio> paulliu: the thing with the osk is weird. I can't imagine what might be causing it, but it needs to be fixed too. Unity should be launched as close as possible to a simple initctl start unity8.
[16:42] <elopio> brendand: let me know if you need an extra hand. For now I'll leave you two to it and take a look at the errors I introduced in the new autopilot version :(
[16:56] <dazza5000> does anyone know how to get an ubuntu phone in the US?
[16:58] <teward> dazza5000: i don't think you can - not offered yet last I heard
[16:58] <dazza5000> how about unofficially though?
[16:59] <elopio> dazza5000: there are some places still selling nexus 4.
[16:59] <dazza5000> where?
[16:59] <elopio> http://www.amazon.com/LG-Google-Unlocked-International-Version/dp/B00D94OAPU/ref=sr_1_2?s=wireless&ie=UTF8&qid=1427129945&sr=1-2&keywords=nexus+4
[17:00] <dazza5000> are most people using the 4 to test with?
[17:01] <elopio> dazza5000: we test with it and with the bq phone. I'm not sure which one has more testers.
[17:09] <brendand> elopio, the rotation test seems to use process_helpers.restart_unity and other tests use launch_unity from the base class
[17:10] <brendand> elopio, the latter does something with the mir socket, which might make a difference
[17:19] <dobey> sigh
[17:20] <elfy> good afternoon quality channel peoples
[18:01] <elopio> jibel: the phonedations team will work on nitz to get the clock hour right from your phone carrier. That sounds like a good addition at the end of the wizard test, check that the clock is right.
[18:01] <elopio> jibel: what should I do to propose the addition?
[18:30] <dazza5000> good afternoon elfy
[19:30] <balloons> dazza50002, howdy
[19:30] <elfy> balloons: !!!
[19:30] <elfy> :)
[19:30] <balloons> hey elfy! final beta week, you excitied?
[19:31] <elfy> well ...
[19:31] <elfy> it might be a milestone for you - but down here in the mines - we've already done some :p
[19:31] <dazza50002> hi all
[19:31] <balloons> elfy, I added you to the mail since you spoke up :-)
[19:31] <dazza50002> Need to figure out how to login using yaaic
[19:32] <elfy> mail?
[19:32] <elopio> barry: meeting again.
[19:32] <elfy> balloons: oh - see it now :p
[19:33] <elfy> I tend to only post that stuff on xub-dev list specifically for our peeps
[19:33] <elfy> balloons: but ... http://iso.qa.ubuntu.com/qatracker/milestones/336/builds for the general page :)
[19:34] <balloons> mmm.. indeed
[20:06] <Letozaf_> balloons, hi
[20:10] <balloons> Letozaf_, hello hello
[20:10] <Letozaf_> balloons, howzit ?
[20:10] <balloons> excellent, yourself?
[20:10] <Letozaf_> balloons, fine, thanks :)
[20:10] <Letozaf_> balloons, I have an issue : http://<IP_ADDRESS>:8080/job/generic-mediumtests-utopic/2393/testReport/junit/calendar_app.tests.test_dayview/TestDayView/test_default_view/
[20:10] <Letozaf_> balloons, cannot find how to solve it
[20:11] <Letozaf_> balloons, it's about week day
[20:11] <Letozaf_> balloons, on calendar app, can you help or should I ask someone else?
[20:13] <dobey> is there a way in autopilot to do a "wait until object is available, *then* tap it" sort of operation?
[20:14] <dobey> because adding time.sleep() everywhere kind of sucks
[20:14] <veebers> dobey: you can use wait_select_single
[20:15] <veebers> dobey: fyi: http://developer.ubuntu.com/api/devel/ubuntu-14.10/python/autopilot/api/autopilot.introspection.html#autopilot.introspection.ProxyBase.wait_select_single
[20:19] <balloons> Letozaf_, looking
[20:20] <Letozaf_> balloons, thanks
[20:20] <dobey> veebers: hmm, trying that
[20:27] <balloons> Letozaf_, dare I ask, does this work locally?
[20:29] <Letozaf_> balloons, no :( but this happens only on Sundays today the test passes :)
[20:29] <balloons> Letozaf_, right that was my first thought
[20:29] <Letozaf_> balloons, suppose it has to do with the firs day of the week stuff
[20:29] <balloons> it's a locale thing
[20:29] <balloons> yes I agree
[20:29] <balloons> which we should have accounted for already
[20:30] <balloons> perhaps check the logic in the test? Or it's a bug in the app itself.
[20:30] <Letozaf_> balloons, to me looks like an app bug
[20:30] <balloons> This is definitely week 12, so week 11 would be for the week to start on monday
[20:31] <Letozaf_> balloons, If yesterday I ran now.strftime("%U") in python shell I got 12
[20:33] <Letozaf_> balloons, In Italy the first day of the week is sunday
[20:34] <dobey> Today is Boomtime, the 9th day of Discord in the YOLD 3181
[20:36] <balloons> Letozaf_, right. I would file a bug against calendar app and see what mihir says
[20:36] <Letozaf_> balloons, ok thanks I will
[20:36] <dobey> Letozaf_: i'm guessing the locale is not set correctly in the tests perhaps?
[20:37] <Letozaf_> dobey, no Calendar app should display 12 as week number instead it displays 11
[20:38] <Letozaf_> dobey, the test is right, it's Calendar app that in Italy has got the wrong week number
[20:38] <balloons> it's the ultimate revenge, blame the app and be correct!
[20:38] <elfy> LOL
[20:39] <dobey> if the week start is on monday, and it's the sunday prior, the 11 is correct, in that locale, no?
[20:39] <Letozaf_> dobey, in Italy the first week day is Sunday :)
[20:40] <dobey> in most of the world it is
[20:40] <Letozaf_> dobey, :)
[20:42] <dobey> so, if i have a dialog in qml, and in the ap test i'm doing dialog.wait_until_destroyed() for that object, and then take a screen shot after it's been destroyed, shouldn't the screen shot *not* have that dialog in it?
[20:48] <veebers> doeby, assuming you're waiting for the right thing to be destroyed it shouldn't be in the screenshot
[20:48] <veebers> dobey: did wait_select_single help you out btw?
[20:49] <veebers> dobey: also, feel free to ask these autopilot questions in #ubuntu-autopilot too :-)
[20:49] <dobey> yes i think so
[20:50] <dobey> too many channels already :)


[13:24] <lukjad86> Hi, #ubuntu-doc ?
[13:25] <lukjad86> Are there any launchpad users who can give me a hand here?


[06:58] <ara> morning!
[11:01] <davmor2> morning all
[13:12] <fader_> Good morning folks
[13:49] <ara> morning fader_
[13:49] <davmor2> morning fader_ cr3
[14:30] <bladernr> morning all (though I should have said it earlier... it's 9:30 now...
[14:31] <davmor2> bladernr: morning
[14:38] <fader_> bladernr: yo
[14:39] <bladernr> hola...
[14:39] <bladernr> I think I may need to go out for lunch today: http://www.youtube.com/watch?v=TVLEB0lv1rw&feature=player_embedded
[14:41] <davmor2> bladernr: that's just wrong
[14:41] <bladernr> I don't know that I disagree, but I really have to try one... I like to live dangerously
[14:42] <davmor2> bladernr: you like to live life in the fat lane ;)
[14:43] <bladernr> that's it... but I figure, if I eat one of those, and have nothing else but water for the rest of the day, I should be fine ;-)
[14:44] <davmor2> haha
[14:44] <bladernr> I made one of these last year... took me a week to eat it though: http://www.bbqaddicts.com/blog/recipes/bacon-explosion/
[15:02] <r00tbert> hi
[15:02] <davmor2> r00tbert: hello
[15:02] <r00tbert> just installed the ubuntu 10.04 beta2 server iso
[15:02] <r00tbert> and recognized an error
[15:03] <r00tbert> wanted to set up a cloud and have 2 ethernet interfaces
[15:03] <r00tbert> and the installer mixed up the network configuration of eth0 and br0
[15:04] <davmor2> hggdh: ^ server stuff is you right?
[15:07] <hggdh> davmor2: right
[15:07] <r00tbert> is this problem already addressed or what should I do to contact the devs?
[15:07] <hggdh> r00tbert: I am not sure this is addressed already. It might be a good idea to test with the daily ISO, and open a bug if it keeps occurring
[15:08] <r00tbert> ok
[16:33] <ara> persia, are you moderator of devel-permissions mailing list?
[16:34] <persia> Maybe?
[16:34]  * persia tries to find out
[16:34] <persia> In general, I avoid being a mailing-list moderator, so I hope not, but I'Ll check.
[16:35] <persia> ara: I'm not.  The current list of moderators is shown at the bottom of https://lists.ubuntu.com/mailman/listinfo/devel-permissions
[16:37] <ara> persia, thanks
[16:40] <persia> ara: In my experience, he usually does batch moderation several times a day, so it oughtn't be too long.
[16:40] <ara> persia, finally I subscribed :D
[16:41] <persia> ara: That works too, and then you get to know about all the changes.
[16:53] <nerdy_kid> my virtual terminals are crooked...
[16:54] <nerdy_kid> i can see the login text near the bottom corner of my screen
[16:54] <nerdy_kid> using NVIDIA gefore8600M
[16:59] <davmor2> nerdy_kid: are you using the nouveau driver or the nvidia binary?
[16:59] <nerdy_kid> nvidia latest
[16:59] <nerdy_kid> i had it fixed, but i just got a grub update today which screwed it back up again
[17:00] <nerdy_kid> davmor2
[17:01] <davmor2> nerdy_kid: grub shouldn't effect it unless you manually modified grub
[17:02] <nerdy_kid> davmor2 it was broke to start with, i was messing with the resulution and i got it to behave by setting GRUB_GFXMODE to 640x480.
[17:02] <nerdy_kid> this doesnt work any more.
[17:03] <nerdy_kid> ive heard im supposed to use the vesa framebuffer for plymouth with nvidia cards?  cause im not using it.....
[17:05] <davmor2> ah in that case you are probably better off asking on #ubuntu+1
[17:05] <nerdy_kid> hmm ok thanks :)
[23:07] <plars> anyone here done an upgrade test from karmic->lucid recently?
[23:08] <plars> I know there are a lot of variables wrt packages installed, speed of machine, etc.  Just curious ballpark figure of how long it took to run


[02:05] <hyperair> okay, so my X suddenly won't start after i alt+sysrq+k'd out of a guest session.
[02:05] <hyperair> dafuq
[02:13] <hyperair> [ 49505.951] (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13].
[02:13] <hyperair> [ 49505.951] (EE) intel(0): Failed to claim DRM device.
[02:13] <hyperair> hooray


[14:32] <nashville> whats up guys is there a way to make this thing autowipe lvm during install
[14:32] <nashville> like if i was trying to do a drive that had been installed with maas before and still make it work
[16:54] <nashville> after maas installs a node and the node goes back down and comes back up then first boot to the hdd and it just reboots over and over anyone seen this?
[17:01] <nashville> sure is quiet in here today...
[17:02] <nashville> where you at kiko
[17:07] <lazyPower> nashville: is this during enlistment or during provisioning?
[17:08] <nashville> its after everything is done the machine should boot up to operating system (hdd) and come up but instead it boots to hdd and then reboot
[17:28] <lazyPower> nashville: ah, i've seen this but it was transient in my setup
[17:29] <nashville> i am trying to change my preseed file as i think its not installing grub right
[17:29] <nashville> i have a pretty intense partition scheme
[17:30] <lazyPower> yeah, i'm not going to be much help, thats deeper into maas than i have gotten nashville :( sorry i wasn't able to help
[17:32] <nashville> its cool lazypower i appreciate your input
[17:45] <nashville> preseed is powerful but kinda a bear to learn
[18:24] <nashville> ok think i got it
[19:45] <nashville> ok how about if a node is talking about can get the preseed file
[19:45] <nashville> and giving a working link
[20:14] <nashville> anyone have any info on using maas with usernames and passwords instead of ssh keys
[20:15] <nashville> i have some lines for that in my preseed but doesnt seem to work
[21:10] <nashville> ok i have a real problem i dont know why i havent seen this yet
[21:22] <nashville> if i install a node and then reboot it delete it from the webapp and try again from the getgo i get an error about the preseed file cant be loaded
[21:23] <nashville> if anyone has any advice im at the end of my rope (and contract)