[02:14] <RAOF> robert_ancell: Yo yo!  I know you've got a r600+ radeon card - have you noticed rendering problems in unity recently - the title bar being mostly-invisible, only the shadows of notify-osd showing?
[02:15] <robert_ancell> RAOF, sure have
[02:15] <RAOF> Any idea when they started?
[02:16] <robert_ancell> a week or two ago?
[02:17] <RAOF> Hah.  And it's unity only, right?
[02:18] <robert_ancell> I haven't tried anything else, but my guess would be yes
[02:18]  * RAOF has just tried classic + compiz, and that works.
[02:18] <RAOF> Right.  So, there's a problem.
[02:18] <robert_ancell> the window title one is the particular one I've noticed, occurs when opening new windows, clicking the top of the screen seems to redraw it right
[02:25] <TheMuso> Yay! Multi-arch breaks unity builds, due to a dbus header file being in a different place. :)
[02:29] <RAOF> TheMuso: I think that's fixed with the most recent dbus upload?
[02:29] <TheMuso> RAOF: Will check, but I updated this morning...
[02:29] <RAOF> It was post-this-morning.
[02:30] <TheMuso> Ok hasn't come through yet.
[02:30]  * TheMuso updates his local mirror...
[02:31] <TheMuso> Anyway, have symlinked the file for now, so things work again.
[02:33] <RAOF> Ok.  Unity's doing something screwy with transparency it seems.
[02:35] <RAOF> Urgh.  What's annoyingly worse is that mesa master explodes into a thousand shards.
[02:49] <TheMuso> heh
[02:50] <bcurtiswx> is the Ubuntu font still UbuntuBeta?
[03:04] <IanLiu> I have fixed a bitesize bug, but I'm having troubles pushing it. I'm following the instructions from http://unity.ubuntu.com/getinvolved/#coding . Any tips?
[03:05] <IanLiu> The command I'm executing is "bzr push lp:ian-liu88/unity-place-applications/fix-for-bug-736471"
[03:06] <stgraber> you seem to be missing a ~
[03:06] <stgraber> try with: bzr push lp:~ian-liu88/unity-place/applications/fix-for-bug-736471
[03:06] <stgraber> or rather: bzr push lp:~ian-liu88/unity-place-applications/fix-for-bug-736471
[03:14] <IanLiu> stgraber: I will try, thanks!
[03:14] <IanLiu> stgraber: it worked ;-)
[03:24] <IanLiu> The "Getting Involved" also mentions to "Propose a Merge". I've found the Merge proposal form, but I'm having some doubts on how to use it. Is the "Target branch" my new branch?
[03:25] <RAOF> HAH!
[03:26] <RAOF> robert_ancell: Would you be a dear and go to compizconfig settings manager→Blur Windows and disable “alpha blur”?  I suspect that will resolve the graphical glitches.
[03:27] <RAOF> robert_ancell: No rush, just when there's an appropriate context switch.
[03:27] <robert_ancell> RAOF, hmm, blur windows appeared to be disabled
[03:27] <RAOF> Oh.
[03:28] <RAOF> I wonder why it is enabled here.  Have I enabled it locally, I wonder?
[03:34] <RAOF> Well, that's annoying.  ‘unity --reset’ doesn't re-enable blur.
[03:37] <micahg> robert_ancell: are you planning to arrange a release exception for webkit 1.4.0?
[03:38] <robert_ancell> micahg, is it released yet?
[03:38] <micahg> robert_ancell: no, but I'm told it
[03:38] <micahg> s coming with GNOME 3
[03:39] <robert_ancell> Yes, as soon as it's released will do the paperwork
[03:39]  * micahg wanted to make sure it's on the release team's radar since it'll be a very last minute update
[03:41] <micahg> which reminds me, I need to get a microrelease exception for webkit, but I'll do that later
[03:41] <micahg> robert_ancell: thanks
[03:41] <robert_ancell> micahg, np, it will be nice when we have the release..
[03:42] <micahg> robert_ancell: indeed, unfortunately, kov couldn't commit to no ABI/API breaks, but said there were none planned
[03:43] <micahg> at least webkit looks like it's taken care of, now I need to worry about getting xul-1.9.2 dropped :-/
[04:52] <LLStarks> raof, is blur default now?
[04:53] <RAOF> LLStarks: No, it isn't.
[05:01] <LLStarks> the blur appears quite spotty under the expo
[06:57] <chrisccoulson> wow, am i the first one awake in europe for a change?
[06:57] <chrisccoulson> good morning everyone
[07:02] <TheMuso> chrisccoulson: Seems so.
[07:08] <pitti> Good morning
[07:10] <pitti> bryceh: I think we should use the last "path: error: .*" line of DKMSBuildLog.txt for this?
[07:11]  * pitti sighs -- unity hasn't crashed for two weeks, and with the last update it all went horribly unstable again :/
[07:11] <TheMuso> pitti: Yeah, trying to test some merged in branches with nux/unity today and have had a horror of a time.
[07:15]  * TheMuso realized that he didn't try unity trunk...
[07:15]  * TheMuso goes and builds.
[07:18] <chrisccoulson> good morning pitti
[07:19] <pitti> hey chrisccoulson
[07:19] <pitti> how are you?
[07:19] <chrisccoulson> pitti - i'm good thanks, although a little tired. how are you?
[07:20] <pitti> I'm fine, we had a nice weekend
[07:22] <pitti> chrisccoulson: woke up too early again?
[07:23] <chrisccoulson> pitti - yeah, my daugher woke several times during the night, and i thought that would mean she would sleep in ;)
[07:23] <chrisccoulson> but she woke up at the usual time
[07:41] <TheMuso> Well well well, with a branch of some a11y signal fixes for nux, we finally have a somewhat accessible launcher. :)
[07:41] <TheMuso> No quicklists yet, but I can navigate the launcher with orca and hear the application names, and launch them. :)
[07:42] <RAOF> Sounds like an important milestone!  Rockin!
[07:43] <TheMuso> Yeah, it certainly is. I am now going to take some time tomorrow to move my primary work environment to unity.
[07:43] <TheMuso> I'll just put all the most commonly used aps on the launcher, and launch everything else from a nautilus window/a terminal for now.
[07:45] <RAOF> alt-f2 isn't a11ied?
[07:46] <TheMuso> No, and the dash isn't yet either, tahts more work.
[07:46] <TheMuso> Next cycle I'd say.
[07:46] <RAOF> Eep.
[07:46] <pitti> TheMuso: nice to hear about the progress there! do you think this should change the current plan of defaulting to 2d if a11y is enabled?
[07:46] <pitti> ah, ok
[07:46] <pitti> so seems not
[07:46] <RAOF> Incidentally, how's gnome-do on the a11y front, and how can I test it?
[07:46] <TheMuso> pitti: No, unless you are willing to put up with the missing bits, productivity would be severely crippled for anyone not willing to work around things.
[07:47] <TheMuso> RAOF: Don't know, never tried it.
[07:47] <pitti> TheMuso: right
[07:47] <TheMuso> So yeah, default to GNOME for some a11y profiles.
[07:47] <RAOF> It's made of custom GTK stuff, so I'm not sure whether it's inherited the default GTK a11y.
[07:47] <TheMuso> RAOF: The easiest way to see if its likely to be accessible is to run accerciser, and look at the application accessibility hierarchy.
[07:48]  * RAOF adds that to his todo.
[07:51] <didrocks> good morning
[07:51] <RAOF> OMG it's didrocks!
[07:52] <didrocks> RAOF: run run ;)
[07:52] <pitti> bonjour didrocks, ca va? had a nice long weekend?
[07:53] <didrocks> pitti: Guten Morgen pitti. yeah, I'm fine, the week-end was nice (even if not enough snow to ski). You?
[07:53] <TheMuso> pitti: And, I think I might want to switch back to the standard gtk window decorator for accessibility profiles as well, because the unity window decorator window switcher is not accessible, even though it is derived from the gtk window decorator codebase...
[07:55] <TheMuso> Unless bug 724093 gets fixed soon.
[07:55] <ubot2> Launchpad bug 724093 in compiz "unity-window-decorator: When switching between windows, Orca does not speak the title of the focused window." [High,Triaged] https://launchpad.net/bugs/724093
[07:55] <TheMuso> grrr another unity window decorator crash...
[07:55]  * RAOF builds from nux trunk so opening the dash isn't a compiz death sentence.
[07:56] <TheMuso> COmpiz 0.9 still feels raw to me.
[07:59] <chrisccoulson> it does for me too
[07:59] <chrisccoulson> it keeps locking up whilst i'm not at my machine
[07:59] <chrisccoulson> i was going to blame RAOF because i thought X was locking up, but it's actually compiz ;)
[08:00] <RAOF> I'll let you in on a secret: it's entirely possible that's the fault of the X stack ;)
[08:00] <chrisccoulson> lol
[08:01] <chrisccoulson> RAOF, it does start working again if I kill -9 compiz and start metacity
[08:01] <RAOF> Ah.
[08:01] <chrisccoulson> but often, restarting compiz will just make it crash until i reboot
[08:01] <RAOF> Then I don't think that's the X stack's fault.
[08:02] <RAOF> The typical “X causes compiz to lockup” would be a pageflipping snafu where compiz is sitting around in D state waiting for the swap to complete.
[08:26] <fta2> pitti, http://people.ubuntu.com/~fta/apport-kernel.png
[08:27] <pitti> fta2: heh, fun -- that looks like a bug in the kernel package hook; how did you get to this?
[08:27] <pitti> i. e. was it the first question?
[08:28] <pitti> (and is this natty?)
[08:28] <fta2> pitti, no, one of the last, if not the last
[08:28] <fta2> natty
[08:28] <pitti> what did you answer?
[08:28] <fta2> default
[08:28] <fta2> when i filed bug 736667
[08:29] <ubot2> Launchpad bug 736667 in linux "P5Q-PRO kernel OOPs: NETDEV WATCHDOG: eth0 (ATL1E): transmit queue 0 timed out" [Undecided,New] https://launchpad.net/bugs/736667
[08:30] <pitti> hm, doesn't happen here :/
[08:30] <duanedesign> I hade that happen to me
[08:30] <pitti> fta2: do you get the same empty question with "DISPLAY= ubuntu-bug linux"? (that will use the CLI frontend)
[08:30] <duanedesign> fwiw :)
[08:31] <fta2> pitti, I had a valid DISPLAY at that time
[08:31] <pitti> fta2: I know
[08:31] <pitti> fta2: I just wonder if that's some bug in the GTK UI or in the hook
[08:31] <pitti> fta2: it could also be weird characters which the dialog fails to render
[08:33] <fta2> in cli, it seems ok
[08:43] <pitti> fta2: can you pastebin the entire dialog?
[08:49] <duanedesign> pitti: here is what i got. http://paste.ubuntu.com/583232/
[08:50] <pitti> duanedesign: do you know which of the questions you got an empty dialog for?
[08:54] <fta2> pitti, as i said, iirc, it was the last one, before the apport UI with the summary
[08:55] <pitti> fta2: the "Testing the upstream kernel can help isolate issues.."?
[08:55] <fta2> i think i saw that one
[08:55] <fta2> but that was friday..
[08:58] <fta2> is the retracer dead?
[09:05] <rodrigo_> morning
[09:06] <duanedesign> hello rodrigo_
[09:13] <rodrigo_> hi duanedesign
[09:23] <pitti> hey rodrigo_, bonjour seb128
[09:23] <seb128> hey pitti
[09:23] <seb128> how are you?
[09:23] <rodrigo_> hi pitti, seb128
[09:23] <pitti> seb128: I'm great, thanks! nice and sunny weekend
[09:23] <seb128> same here ;-)
[09:30] <seb128> hum, GNOME guys are thinking to switch their tarballs to tar.xz
[09:30] <seb128> is soyuz handling the format?
[09:32] <pitti> seb128: I don't know; worth checking in a PPA, I guess
[09:48] <fta2> pitti, is the retracer dead? (been waiting for 2h+ for a retrace)
[09:48] <pitti> fta2: possibly, let me check
[09:49] <pitti> fta2: yep, will fix in a bit
[09:50] <fta2> thanks
[09:56] <pitti> fta2: restarted (udev failed to upgrade in the chroots)
[10:46] <duanedesign> pitti: was able to reproduce the problem. Itwas after the window asking to test newer kernel versions.
[10:49] <duanedesign> pitti: strange. I can not reproduce it by running:  ubuntu-bug linux
[10:50] <duanedesign> it has to be triggered by a kernel issue
[11:24] <chrisccoulson> pitti, swt-gtk 3.6.2 has webkit support
[11:24] <pitti> chrisccoulson: wohooo!
[11:24] <chrisccoulson> i'm just testing that this morning
[11:24] <chrisccoulson> perhaps that's worth a FFe if i can get it to work ;)
[11:37] <seb128> pitti, if you have some time and want to review https://code.launchpad.net/~vorlon/glib/multiarch/+merge/54143 that would be appreciated
[11:38] <seb128> well extra eyes on that are welcome
[11:38] <pitti> seb128: I don't know much about it either, I guess we should just build and test it locally?
[11:39] <seb128> pitti, don't bother much that was in case you had some opinions or comment about it
[11:40] <pitti> seb128: I looked at it, but nothing that jumps out on me
[11:40] <seb128> ok, same here
[11:40] <pitti> quite ugly, though
[11:40] <seb128> I guess slangasek tested it and it doesn't break glib
[11:40] <pitti> (this cries for more abstraction/automation)
[11:41] <seb128> so let's go for it and see if things break
[11:41] <pitti> seb128: gio modules are mainly gvfs, I take it? I. e. URLs like gphoto:// or ssh:// ?
[11:42] <seb128> gvfs uri handling for gio yes and dconf
[11:42] <seb128> those are the obvious ones
[11:42] <pitti> seb128: want me to test it with gphoto? or are you already?
[11:43] <seb128> unity has some magic has well for application running and matching but I'm not sure how to test those, they improve reliability for some cases that's not technically required
[11:43] <seb128> pitti, if you want to do it feel free
[11:43] <pitti> I guess that requires changes to gvfs as well, then, as it ships /usr/lib/gio bits/
[11:43] <pitti> ?
[11:43] <seb128> I'm about to go for lunch, I will build glib and test when I'm back
[11:43] <pitti> seb128: can do in a bit (still busy with something)
[11:43] <pitti> seb128: ok, sounds good; will build it in the background
[11:44] <seb128> pitti, right, it seems we will need patches for everything installing a .so in that dir
[11:45] <seb128> pitti, well slangasek added a fallback to read the old dir so technical that will not break
[11:45] <seb128> but still
[11:45] <pitti> seb128: ah, his latest changelog says "include /usr/lib/gio/modules as a fallback directory for compatibility"
[11:45] <pitti> right
[11:45] <seb128> do you know when that will land in Debian? seems that will add some extra delta otherwise
[11:45] <pitti> so, testing then
[11:46] <pitti> I don't
[11:46] <pitti> I think we are trailblazing here
[11:46] <seb128> ok, I will chat with steve when he's online
[11:46] <pitti> but the dpkg/apt/debhelper stuff is all in (or at least in git)
[11:46] <pitti> it hasn't been officially announced in Debian yet
[11:47] <seb128> ok
[11:49] <seb128> is anybody there on 10.10?
[11:50] <pitti> 10.10, what's that?
[11:50] <pitti> (SCNR)
[11:51] <serious__sam> yes
[11:52] <seb128> could you check if exec like in evolution-alarm-notify.desktop there?
[11:52] <seb128> it's in /etc/xdg/autostart
[11:53] <seb128> is the version 2.28 or 2.30 in the url?
[11:54] <seb128> ok, lunch time, I will read the scrollbar when I' back
[11:54] <seb128> be back in a bit
[11:56] <fta2> pitti, still no retrace...
[11:57] <pitti> fta2: they are running now; they have some catch-up to do since they were down over the weekend
[11:57] <fta2> ok
[14:06] <dobey> pitti, seb128, kenvandine, mterry: anyone care to sponsor https://code.launchpad.net/~dobey/ubuntu/natty/ubuntuone-control-panel/release-0-9-2/+merge/54081 please? :)
[14:06] <seb128> dobey, can do, I'm patch pilot today
[14:06] <dobey> seb128: ok great. thanks!
[14:08] <mterry> seb128, you are?  sponsor https://bugs.launchpad.net/ubuntu/+source/libgda4/+bug/722079 too please!  :)
[14:08] <ubot2> Launchpad bug 722079 in libgda4 "When installing Anjuta in Natty Alpha libsqlite3.so is missing" [Low,Triaged]
[14:08] <seb128> mterry, that one should be in the desktop set?
[14:08] <seb128> hey mterry
[14:08] <mterry> seb128, srsly?  main won't have anything left!
[14:08] <seb128> lol
[14:08] <seb128> it's a GNOME lib...
[14:08] <mterry> k, will ping cjwatson
[14:08] <seb128> thanks
[14:09] <seb128> dobey, btw ubuntuone-client-gnome ship libubuntuone.a and .la in the g-s-d directory, would be nice to clean
[14:09] <seb128> mterry, how are you btw? had a nice weekend?
[14:10] <dobey> seb128: oh right. i'll look into rming those as well
[14:10] <seb128> dobey, thanks
[14:11] <rickspencer3> chrisccoulson, hey, around at all?
[14:11] <seb128> didrocks, there is a new zg in debian if you want to sync it
[14:11] <chrisccoulson> rickspencer3, yep
[14:11] <seb128> hey rickspencer3
[14:11] <rickspencer3> hi chrisccoulson, hi seb128
[14:11] <chrisccoulson> hi :)
[14:11] <rickspencer3> so, flash is really really crashy on my desktop
[14:12] <rickspencer3> are other folks reporting bugs on this?
[14:12] <rickspencer3> it also seems to be playing video better, though
[14:12] <chrisccoulson> rickspencer3, yeah. are you on amd64 or i386?
[14:13] <didrocks> seb128: if you have time/want to go for it, do not hesitate, I'll go for it over the week otherwise :)
[14:13] <seb128> didrocks, well it's just a sync, I can do it ;-)
[14:13] <didrocks> seb128: thanks :)
[14:14] <mterry> seb128, yeah, it was fine.  I've been a little under the weather though
[14:14] <rickspencer3> chrisccoulson, i386
[14:15] <chrisccoulson> rickspencer3, it doesn't give you the option of submitting a crash report does it?
[14:15] <rickspencer3> chrisccoulson, no
[14:15] <chrisccoulson> in any case, when i saw flash crashing, the backtrace was just full of flash :(
[14:15] <chrisccoulson> which means it needs to go to adobe really ;)
[14:15] <rickspencer3> yeah, I figured it was all in upstream binary goo
[14:16] <chrisccoulson> there's not much we can do about crashes in the flash plugin, other than hope they fix it (or point to a problem in firefox)
[14:16] <kamstrup> seb128, didrocks: if you're talking zeitgeist 0.7.1 then I think that's a pretty safe bet. There are only slight tweaks in the Python client API (which we don't use) and then a very slight sql tweak to make it forward compatible with the upcoming 0.8 (which we'll prolly have for Oneiric, so forward compat is nice)
[14:16] <seb128> kamstrup, ok thanks
[14:16] <chrisccoulson> rickspencer3, i need to figure out why crash reporting is broken though. i guess it's the same bug that breaks it in chromium too
[14:17] <rickspencer3> chrisccoulson, ok, I was checking to see if I was the only one
[14:17] <chrisccoulson> rickspencer3, no, we seem to get quite a lot of reports recently
[14:17] <rickspencer3> ok
[14:17] <chrisccoulson> rickspencer3, it might be worth attaching gdb to the plugin-container process before it crashes though, just to make sure it is in the flash plugin
[14:17] <chrisccoulson> i'm on amd64 here, so i can't do that
[14:17] <tedg> seb128, You might consider backporting this to Maverick (thought it'd be in appmenu-gtk there) bug 717162
[14:18] <ubot2> Launchpad bug 717162 in libdbusmenu "quodlibet UI freeze in Unity after accessing its menu" [High,Confirmed] https://launchpad.net/bugs/717162
[14:18] <chrisccoulson> i get the wonders and joys of nspluginwrapper instead
[14:18] <rickspencer3> chrisccoulson, sounds like a good afternoon project for me
[14:18] <rickspencer3> will do
[14:18] <chrisccoulson> thanks
[14:20] <seb128> tedg, yeah, I doubt the indicator-appmenu is used a lot in 10.10 but seems worth backporting still
[14:20] <tedg> seb128, I used it ;-)
[14:20] <tedg> seb128, It'd be in use by anyone using netbook edition.
[14:21] <seb128> right
[14:21]  * tedg reminisces about the olden days when Ubuntu had editions
[14:23] <dobey> when the web was the real web, and small furry creatures from alpha centauri were real small furry creatures from alpha centauri
[14:25] <kenvandine> ugh, that is annoying... every time i open a document in LO i get an ubuntuone notification that it is uploading a .lock file
[14:25] <kenvandine> and then when i quit i get it again
[14:26] <kenvandine> that might be annoying enough to make me turn off syncing of my Documents dir
[14:26] <seb128> not sure why syncdaemon needs to tell you it's uploading using a notification bubble to start with
[14:26] <seb128> it's annoying in quite some situations
[14:26] <kenvandine> yeah
[14:27] <seb128> it's not because you triage things and clean a bit that you want to get notified every time you store a change
[14:27] <seb128> or delete a file
[14:27] <seb128> or move one
[14:27] <kenvandine> i can see notifying for new shares, etc
[14:27] <tedg> seb128, Because people don't trust the syncdaemon as it's been flaky.  So they associate not having trust with needing more information.
[14:27] <seb128> notify-osd is not informations, it's spam ;-)
[14:28] <kenvandine> hehe
[14:28] <kenvandine> i guess it would spam me on every auto-save too
[14:28] <tedg> On man's spam is another man's miracle meat.
[14:28] <seb128> just give an obvious way to open the control panel to see what's going on
[14:28] <kenvandine> yum, spam
[14:34] <dobey> kenvandine: hrmm. the lock files should just be ignored
[14:34] <kenvandine> dobey, well how should u1 decide what to hide?
[14:36] <dobey> kenvandine: there is a blacklist in the code, to ignore certain file patterns. like vim swp files
[14:37] <kenvandine> i would think .lock would be included :)
[14:37] <dobey> yeah i thought it was
[14:38] <kenvandine>  .~lock.MoM 2011-03-01.odt#
[14:38] <kenvandine> whacky filename
[14:38] <dobey> actually, it would be neat if .lock files were handled by not syncing them, and locking changes to the associated file, on the server
[14:38] <kenvandine> indeed
[14:39] <dobey> so that other changes don't happen elsewhere while you're editing something
[14:39] <dobey> oh, well, .~lock is probably not ignored yet :)
[14:39] <dobey> wonder why it has the ~
[14:49]  * ari-tczew checks interesting merges available for natty.
[15:05] <pitti> didrocks: hey
[15:05] <pitti> didrocks: I have some time now to tackle bug 723782
[15:05] <ubot2> Launchpad bug 723782 in gnome-session "Finalize gnome-session fallback detection" [Medium,New] https://launchpad.net/bugs/723782
[15:05] <pitti> didrocks: I can backport and test that d-bus session name property now
[15:05] <didrocks> pitti: oh, I should have warned you last week that with latest loicm's change, it's not needed anymore
[15:06] <pitti> didrocks: you actually told me it's not necessary any more, but the bug is still open, so that's what I wanted to discuss with you now :)
[15:06] <didrocks> pitti: if we keep the checks in compiz and in the helper tool in sync
[15:06] <didrocks> which is the case right now :)
[15:06] <didrocks> hope that we can keep it like that
[15:06] <pitti> didrocks: so is it totally obsolete, or we can work around it, or would it still be useful then?
[15:07] <pitti> IOW, should we just close the bug, or would having it be an enhancement?
[15:09] <didrocks> pitti: I *think* we should close it and avoid adding a big regression right now. Then, testing to ensure that we don't drop the user on some corner cases in a "no panel" session is needed
[15:09] <didrocks> (which means, compositor, but no panel)
[15:09] <didrocks> that can be ensure by keeping the testing tool opengl tests in unity_support_tool and the test from the start in the unity plugin initialization in sync
[15:10] <pitti> didrocks: i. e. with the dbus property we wouldn't need to duplicate the code and run the tests twice?
[15:11] <didrocks> pitti: the tests will be run twice anyway, as it seems some people try to run unity even if it's not supported (with the "unity") command
[15:11] <didrocks> pitti: so, a test rather than a crash is in order at unity startup :)
[15:12] <pitti> didrocks: as long as this test gets reasonably cheap..
[15:12] <pitti> didrocks: anyway, so I'll close the bug then, to get it off the radar?
[15:12] <tedg> pitti, seb128, So are you guys planning on taking the upower and gpm patches here?  It doesn't make sense to take the indicator-session one without those.
[15:12] <tedg> bug 578542
[15:12] <ubot2> Launchpad bug 578542 in gnome-power-manager "resuming from S3 wrongly prompts for password" [Low,In progress] https://launchpad.net/bugs/578542
[15:12] <didrocks> pitti: yes, please :)
[15:13] <didrocks> pitti: the tests are cheaps, it's reading in an array
[15:13] <didrocks> pitti: and the array is initialized once opengl is initialized
[15:13] <pitti> tedg: looking
[15:13] <tedg> pitti, seb128, Some helpful discussion on them: http://lists.freedesktop.org/archives/devkit-devel/2011-March/date.html
[15:13] <Amaranth> didrocks: what tests are you doing?
[15:13] <didrocks> Amaranth: look at unity_support_tool
[15:13] <Amaranth> didrocks: initializing GL and checking for supported extensions isn't all that cheap
[15:13] <pitti> tedg: ah, "Adding an argument to Sleeping signal"?
[15:13] <Amaranth> didrocks: Oh, that doesn't segfault anymore? :)
[15:14] <tedg> pitti, Yup
[15:15] <Amaranth> didrocks: I don't seem to have a unity_support_tool anymore, didn't nux ship that?
[15:15] <pitti> tedg: will have a look and discuss with hughsie; as this changes the d-bus API, I won't apply it in Debian/Ubuntu only
[15:15] <tedg> pitti, Okay, it seems like he approves on the mailing list.
[15:15] <tedg> pitti, But good to double check.
[15:15] <tedg> I think that it's solving it in the right way.
[15:16] <tedg> Though, it seems that gss should listen for the signal not gpm.  But, that's a minor optimization :-)
[15:16] <didrocks> Amaranth: /usr/lib/nux/unity_support_test
[15:16] <didrocks> Amaranth: talk to jay, he told that checking the extensions wasn't more expensive once opengl is activated. I think he knows a little on opengl so that I can trust him
[15:17] <seb128> tedg, seems a pitti thing, I will let him handle it
[15:18] <Amaranth> didrocks: Oh, sure, checking extensions is free once opengl is initialized
[15:19] <Amaranth> hrm, I seem to be stuck in a situation that makes compiz crash without triggering an apport dialog
[15:20] <Amaranth> weird, and it just stopped doing that
[15:25] <seb128> rodrigo_, hey
[15:25] <rodrigo_> hey seb128! :)
[15:25] <seb128> rodrigo_, so one frequent issue users get in nautilus is that they right click on a directory, do open with and pick an application and associate the folder mimetype with the software they used
[15:26] <seb128> rodrigo_, we used the patch from https://bugzilla.gnome.org/show_bug.cgi?id=637264 to make less easy to run into the issue
[15:26] <ubot2> Gnome bug 637264 in File and Folder Operations "The 'Remember this application for ..." option changes the default for both files and folders" [Normal,Resolved: obsolete]
[15:26]  * rodrigo_ looks
[15:27] <seb128> rodrigo_, that's sort of a workaround though (just toggle the default value), the issue is fixed in GNOME3 as well, cosimoc said he would welcome a 2.32 patch that hides the checkbox for directories though
[15:27] <seb128> rodrigo_, do you think you could work on that?
[15:27] <rodrigo_> ok
[15:27] <rodrigo_> is there a LP bug for it?
[15:29] <seb128> rodrigo_, bug #662194
[15:29] <ubot2> Launchpad bug 662194 in nautilus "Nautilus: 'Remember this application for ..." option should be made inactive by default" [Low,Fix released] https://launchpad.net/bugs/662194
[15:29] <rodrigo_> ok
[15:30] <seb128> rodrigo_, I've reopened and assigned it to you
[15:30] <seb128> rodrigo_, thanks
[15:30] <rodrigo_> ok thanks
[15:31] <seb128> rodrigo_, thank you! ;-)
[15:31] <jcastro> bugs with GNOME3 from the PPA should be filed on  ... ?
[15:31] <rodrigo_> jcastro, good question :)
[15:31] <jcastro> aha, I knew I would stump someone
[15:32] <seb128> jcastro, they should not be filed ;-)
[15:32] <davmor2> jcastro: bugzilla gnome of course :D
[15:32] <seb128> jcastro, there is no ppa bug tracker
[15:32] <rodrigo_> so far, people have been sending mail to me directly
[15:32] <jcastro> right
[15:32] <seb128> jcastro, code issues should be filed upstream , packaging ones mentioned here
[15:32] <jcastro> and the mailing list looks like lp build announcements
[15:32] <jcastro> maybe just using the mailing list? I mean, it's there already
[15:33] <jcastro> seb128: also, is there a way out for people if they decide to not use it
[15:33] <mterry> jcastro, ppa-purge?
[15:33] <jcastro> because from looking at the packages, if I use natty, and I want to try gnome3, and it upgrades a ton of stuff
[15:34] <seb128> jcastro, what mailing list?
[15:34] <jcastro> mterry: ok, I can add that to the instructions
[15:34] <jcastro> seb128: gnome3-team@lists.launchpad.net
[15:34] <seb128> jcastro, oh the gnome3 team one on launchpad?
[15:34] <jcastro> yeah
[15:34] <seb128> jcastro, yeah they can use that
[15:34] <seb128> I'm not sure anyone is reading it
[15:34] <seb128> or subscribed
[15:34] <seb128> but seems the right location
[15:34] <seb128> we can check the list every now and then
[15:34] <seb128> jcastro, downgrade ... I wouldn't recommend it
[15:35] <mterry> I'm subsucribed
[15:35] <jcastro> mterry: I want to avoid "I tried this PPA and now my gnome is totally hosed wether it's 2.x or 3.x!"
[15:35] <seb128> like GNOME3 will migrate your users datas to gsettings etc
[15:35] <mterry> seb128, but it won't delete old stuff
[15:35] <seb128> there is no easy roll back
[15:35] <jcastro> right, so really, this isn't "try gnome3!" this is a bit of a commitment?
[15:35] <seb128> no, you will just go back to the settings you had before upgrading
[15:35] <jcastro> ok
[15:35] <seb128> downgrade are not handled packaging wise either
[15:35] <seb128> it's likely that ppa-purge will fail on conflicts etc
[15:36] <seb128> like Replaces: are not made for going this way
[15:36] <seb128> you can downgrade but I would said it's not something a normal user will be able to deal with
[15:59] <mterry> I'm giving another global call if anyone wants to leave comments on my in-progress core-dev application.  https://wiki.ubuntu.com/mterry/CoreDev
[16:01] <seb128> mterry, when is your meeting?
[16:01] <mterry> seb128, haven't formally put myself in yet.  Was waiting for a few comments
[16:01] <seb128> mterry, ok, I will do that tomorrow then ;-)
[16:02] <mterry> sweet
[16:16] <seb128> mterry, btw if you get borred and are interest it could be nice to make appmenu-gtk work on gtk3 if we can
[16:16] <seb128> interested
[16:27] <pitti> good night everyone! have to leave a bit early today
[16:28] <desrt> pitti: cheerio
[16:29] <desrt> seb128: i have a new respect
[16:29] <desrt> seb128: it turns out i have fat fingers for packaging
[16:29] <seb128> hey desrt, new respect for who? ;-)
[16:29] <desrt> seb128: for you :)
[16:29] <seb128> lol
[16:30]  * desrt tried to repackage gnome-screensaver and failed spectacularly
[16:30] <desrt> the ..90->..91 transition is brutal
[16:30] <desrt> lots of vendor patches no longer applying, packaging broke in various other ways
[16:30] <desrt> i wanted to kill bzr by the end of it :)
[16:31] <desrt> you should produce (and blog?) a 'packaging for ubuntu with bzr' cheetsheet... after some googling i wasn't able to find one
[16:31] <desrt> basically the tips you gave me on IRC the other day, but expanded a bit
[16:32] <desrt> for example, i wasn't ever able to rediscover that command you told me that looked at the apt database to determine the bzr repository that the packaging for a specific source package was kept in and check it out with an appropriate name
[16:32] <seb128> desrt, debcheckout?
[16:32] <desrt> ya.  that one.
[16:32] <desrt> all of the tutorials i found skipped it
[16:33] <desrt> in any case, it seems like there are a lot of tricks that you know that are not easy to discover
[16:35] <desrt> i had another question too: i was working in my checked out repository
[16:35] <seb128> well the desktop team workflow is mainly on http://wiki.ubuntu.com/DesktopTeam/Bzr
[16:35] <desrt> and i removed a vendor patch because it was no longer required
[16:35] <desrt> then i did a bzr bd
[16:35] <desrt> but it complained that files were missing
[16:35] <seb128> but yeah we should really try to converge with standard ubuntu practices and have things documented
[16:35] <desrt> it seemed like the only way to fix that was to commit the file removal
[16:35] <desrt> which i didn't want to do because i was still working
[16:36] <seb128> how did you delete it?
[16:36] <desrt> rm
[16:36] <seb128> yeah, don't do that
[16:36] <desrt> ya.  i learnt my lesson :)
[16:36] <desrt> bzr is not very forgiving in this case
[16:36] <seb128> usually modern packages use quilt and you just have to comment it in the series
[16:36] <desrt> ya...
[16:36] <desrt> that's another thing
[16:36] <desrt> i need to learn to use quilt
[16:36] <seb128> otherwise bzr del it and bzr revert before commiting ;-)
[16:36] <desrt> i had to update some vendor patches by hand... NOT FUN
[16:37] <seb128> you know about edit-patch?
[16:37] <desrt> nope.
[16:37] <seb128> it's from mvo
[16:37] <desrt> i'll go learn about it now :)
[16:37] <seb128> it's an "give me a shell where I can edit my patch and update the diff with what I do there when I exit 0"
[16:37] <seb128> which abstract the patch system
[16:37] <seb128> like it can be cdbs-simple-patchsys or quilt
[16:37] <seb128> it will wrap the commands for you
[16:37] <desrt> see?  neither edit-patch or debcheckout are mentioned in this wiki page you just gave me :)
[16:37] <seb128> just give you the shell to work
[16:38] <seb128> yeah, we need to update that documentation ;-)
[16:38] <desrt> ahh
[16:38] <desrt> this is like that other command you told me
[16:38] <desrt> to extract the tarball and toss the debian/ directory in and throw me into it
[16:38] <seb128> bzr bd-do ?
[16:38] <desrt> yup
[16:38] <seb128> right
[16:38] <desrt> similar idea, i guess
[16:38] <seb128> you usually want to do bzr do-do to get in the unpacked source
[16:39] <seb128> then edit-patch <somepatch>
[16:39] <seb128> then exit 0 twice
[16:39] <desrt> i guess i can recursively use edit-patch from there
[16:39] <desrt> yup
[16:39] <desrt> well, i guess you might need to do several edit-patch
[16:39] <seb128> right
[16:39] <seb128> well I tend to exit 0 and call up bzr bd-do again
[16:39] <desrt> does that record a commit when you're done?
[16:39] <seb128> just to make sure I don't exit != 0 by error and trash my work
[16:39] <desrt> or just leave the changes in-tree?
[16:40] <seb128> that just let the changes in the checkout without commiting
[16:40] <seb128> well I tend to ctrl-D
[16:40] <desrt> doesn't the shell always exit 0 by default?
[16:40] <desrt> or does it use the exit status of the previous command?
[16:40] <seb128> and if the previous command didn't return 0 and you ctrl-D you migh just drop your changes :p
[16:40] <desrt> gotcha
[16:40] <seb128> it uses the exit status of the previous command
[16:40] <desrt> that's ... annoying
[16:40] <seb128> well in fact the unpacked dir is still in ../build-area
[16:41] <seb128> so you can go back there and restore things
[16:41] <desrt> including the modified debian/
[16:41] <seb128> if you don't run bzr bd-do again which wipes it with a fresh unpack
[16:41] <desrt> you guys need to switch to rpm :)
[16:41] <desrt> ((never thought i'd say that))
[16:41] <seb128> well that has nothing to do with the packaging format ;-)
[16:41] <seb128> it's just a vcs workflow
[16:41] <desrt> right.  of course.
[16:41] <desrt> apt, dpkg, etc are much better
[16:42] <seb128> the "real" ubuntu recommended way is full source checkouts
[16:42] <desrt> and all the support infra for building deb is awesome
[16:42] <desrt> but..... you guys do it perfectly backwards
[16:42] <desrt> have the source package at the toplevel with a debian/ directory
[16:42] <seb128> it's just annoying to have to checkout 10 years of history of the full source when you want to update a changelog
[16:42] <desrt> rpm does it the other way.... upstream source gets unpacked into a subdir of the package dir
[16:43] <desrt> seb128: so upstream source in the same bzr as the packaging, you mean?
[16:43] <seb128> yes
[16:43] <seb128> bzr get lp:ubuntu/gconf-editor
[16:43] <seb128> or whatever source
[16:43] <desrt> yes.  i suppose that would be quite annoying.
[16:43] <seb128> those are autoimport for most sources
[16:43] <desrt> for people like me who only work with half a dozen packages or so, it's not so bad
[16:43] <seb128> but some are manually maintained source
[16:43] <desrt> but for someone who is doing new software every single day... that would get annoying
[16:44] <seb128> like it's very handy for things which are upstream on launchpad like dx work
[16:44] <seb128> you can bzr get lp:ubuntu/indicator-something
[16:44] <seb128> cd indicator-something
[16:44] <desrt> oh.  that's something else i wanted to ask about
[16:45] <desrt> do i have to worry about this pristine-tarball business?
[16:45] <seb128> bzr merge lp:indicator-something -r 123
[16:45] <seb128> and bzr bd
[16:45] <seb128> no you don't
[16:45] <desrt> due to the separated nature of the packaging
[16:45] <desrt> just sucks the tarball from the source url...
[16:45] <seb128> right
[16:46] <desrt> i noticed that there is a neat little utility in there that is good at finding random source tarballs :)
[16:46] <seb128> bzr bd-do will typically fetch the source from the archive if available or use the watch file
[16:46] <desrt> i forget what it is called, but it started running when i was having connectivity troubles at one point
[16:59] <bcurtiswx> gstreamer install failed.. http://paste.ubuntu.com/583393/
[17:05] <seb128> kenvandine, ^
[17:05] <seb128> kenvandine, it's your recent change it seems
[17:06] <seb128> pitti, you noticed there is a new pygobject upstream tarball I guess? (just pointing in it case you didn't)
[17:44] <seb128> didrocks, I can't run gconf-editor from unity, known issue?
[17:45] <seb128> well, alt-f2 gconf-editor enter doesn't run anything
[17:45] <seb128> rather
[17:45] <didrocks> seb128: no, not a known one. Someone referenced xkill though
[17:45] <didrocks> when you press enter, do you wait for the model to be synced?
[17:45] <didrocks> (I mean, is the first item showing gconf-editor)
[17:48] <seb128> didrocks, could be that not, it works now
[17:48] <seb128> weird
[17:49] <seb128> oh, come on!
[17:49] <seb128> kenvandine, !!!
[17:49] <seb128> where is ken?
[17:50] <kenvandine> seb128, ?
[17:50]  * kenvandine looks
[17:50] <seb128> kenvandine, I got like 15 duplicates of that gst conflicts in my inbox nox
[17:50] <seb128> now
[17:51] <seb128> kenvandine, can you please fix it before every single natty user send a bug? ;-)
[17:51]  * bcurtiswx runs to submit bug report!
[17:51]  * bcurtiswx then runs
[17:52] <kenvandine> hehe, indeed
[17:53] <kenvandine> seb128, i used Breaks
[17:53] <seb128> kenvandine, you screwed the version then I guess ;-)
[17:53] <kenvandine> which afaik is the right thing to do...
[17:53] <seb128> or the name
[17:53]  * bcurtiswx was banking on control file typo
[17:54] <kenvandine>  -good
[17:54] <kenvandine> Breaks: gstreamer0.10-plugins-bad (<< 0.10.21-1ubuntu5)
[17:54] <kenvandine>  -bad
[17:54] <kenvandine> Breaks: gstreamer0.10-plugins-good (<< 0.10.28-0ubuntu2)
[17:54] <dpm> seb128, re: bug 729631, it seems not to be fixed for me. Do you see the day of the week and month in French on your desktop's date & time indicator?
[17:54] <ubot2> Launchpad bug 729631 in indicator-datetime "Date label on the indicator is partially untranslated" [Low,Fix released] https://launchpad.net/bugs/729631
[17:54] <bcurtiswx> one version too high?
[17:55] <bcurtiswx> no no, nvm
[17:55] <Sweetshark> pitti: could you clue me in on https://bugs.launchpad.net/ubuntu/+source/libreoffice-l10n/+bug/729727 ? I can reproduce the errors in the last two comments.
[17:55] <ubot2> Launchpad bug 729727 in libreoffice-l10n "[natty] Invalid liblucene2-java Conflicts in packaging" [Undecided,Fix released]
[17:55] <kenvandine> looks right to me
[17:55] <kenvandine> wtf!
[17:55] <bcurtiswx> Sweetshark, <pitti> good night everyone! have to leave a bit early today
[17:56] <seb128> dpm, it's showing "lun, 21 mars, 18:56" for me now
[17:56] <Sweetshark> bcurtiswx: oh, ups! thanks for the headsup
[17:56] <bcurtiswx> Sweetshark, np :)
[17:57] <cdbs> dbarth: You sent me a mail?
[17:57] <dpm> seb128, weird, it's "Mon, 21 de Mar, 18:56" for me, thanks for checking
[17:57] <cdbs> dbarth: I replied to it, will contact you after half-an-hour here for more details. Right now I g2g
[17:57] <seb128> kenvandine, not sure, check with mvo, but I usually use Replaces when there is a file replaced
[17:58] <kenvandine> oh... from the docs this was one of the exact use cases it said to use Breaks for
[17:58] <kenvandine> mvo, ^^
[17:58] <kenvandine> and it worked installing from my local repo
[18:00] <seb128> it seems to deconfigure it but not uninstall
[18:00] <mterry> seb128, what's the deal with bug 739575 ?
[18:00] <ubot2> Launchpad bug 739575 in apr-util "Bad path in libapr-util-1.la" [Undecided,New] https://launchpad.net/bugs/739575
[18:01] <seb128> mterry, -> slangasek on #ubuntu-devel
[18:04] <kenvandine> seb128, so you think i should just change those to Replaces to make sure everyone gets unbroken?
[18:06] <seb128> Conflicts,Replaces
[18:06] <seb128> yes
[18:06] <kenvandine> both?
[18:06] <seb128> yes
[18:06] <kenvandine> Conflicts worked, but produced noise on upgrade
[18:06] <kenvandine> ok
[18:06] <seb128> Conflicts will tell it both version should not be installed together
[18:06] <seb128> Replaces will make sure you don't get file conflicts
[18:11] <mvo> kenvandine: sorry, was at dinner and now I leave to play some hockey, could you email me the question please?
[18:18] <kenvandine> seb128, uploaded
[18:19] <seb128> kenvandine, thanks
[18:28] <cyphermox> does anybody have time for a review? --> https://code.launchpad.net/~mathieu-tl/gnome-media/lp737029/+merge/54072
[18:30] <ari-tczew> cyphermox: short URLs in DEP3 rulez ;)
[18:31] <cyphermox> ari-tczew, ah, certainly you mean the gnome one, ;)
[18:31] <ari-tczew> cyphermox: headers in your patch :>
[18:48] <didrocks> chrisccoulson: complaining about weird bug reports: https://bugs.launchpad.net/bugs/739539 ? :)
[18:48] <ubot2> Launchpad bug 739539 in gchildcare "Can just log in to Classic Desktop with no effexts otherwise get just empty screen with wallpaper only" [Undecided,New]
[18:51] <kenvandine> hey didrocks, i have a gnome-session related question if you have a moment
[18:51] <kenvandine> really about doing things in an app on SIGTERM
[18:52] <didrocks> kenvandine: hum? SIGTERM is directly directed to the app
[18:52] <kenvandine> if i want to do some purging of db records and a vacuum on a sqlite db on shutdown, is it safe to do that on SIGTERM
[18:53] <kenvandine> like if it takes 30s one time, will it kill it hard?
[18:53] <didrocks> kenvandine: if you are registered with the session
[18:53] <didrocks> kenvandine: and are reactive on ping (so multi-threaded)
[18:53] <didrocks> you won't be SIGKILL*ed* by gnome-session
[18:54] <kenvandine> ok
[18:54] <kenvandine> what do i have to do to make sure i am registered?
[18:54] <didrocks> kenvandine: do you have sm-… options on --help?
[18:55] <kenvandine> no
[18:55] <didrocks> so you are not :)
[18:55] <kenvandine> bummer
[18:55] <didrocks> kenvandine: best thing is to take an easy exemple, like gedit
[18:55] <kenvandine> ok
[18:55] <kenvandine> this is for gwibber, users are really starting to suffer from massive sqlite dbs
[18:55] <didrocks> otherwise: http://www.google.fr/url?sa=t&source=web&cd=1&ved=0CBwQFjAA&url=http%3A%2F%2Flive.gnome.org%2FSessionManagement%2FGnomeSession&rct=j&q=gnome-session%20sm&ei=7Z6HTbGuLYv24Qa_sfSLCQ&usg=AFQjCNEba-dg-9CvbDiiHIsUUsrobGBe5Q
[18:56] <didrocks> grr, don't know why google doesn't want to copy me the inner linj :)
[18:56] <kenvandine> :)
[18:56] <didrocks> yeah, that should be ok :)
[18:56] <didrocks> dinner time now!
[18:56] <kenvandine> later
[18:56] <kenvandine> thx
[18:56] <didrocks> later
[18:56] <didrocks> yw ;)
[18:56] <dpm> hi tedg, have you had the chance to look at your schedule for your session on https://wiki.ubuntu.com/UbuntuAppDeveloperWeek? I'm trying to wrap up the timetable and there are only a few slots free
[19:00] <tedg> dpm, Can I get the 20 slot on 14 Apr?
[19:05] <dpm> tedg, sure! If this looks ok to you, then we're set -> https://wiki.ubuntu.com/UbuntuAppDeveloperWeek/Timetable
[19:06] <tedg> dpm, Looks good!
[19:06] <dpm> tedg, awesome, thanks tedg!
[19:32] <cdbs> dpm: Wait, can I claim one slot there?
[19:33] <cdbs> dpm: okay, unping, it appears others are doing the sessions I'd have done
[19:33] <dpm> cdbs, if you've got a session you think it might be interesting for application developers, sure! What were you thinking of?
[19:33] <cdbs> dpm: about the one of introducing PyGI
[19:35] <dpm> cdbs, no worries. Is there another topic you'd like to talk about? Or perhaps pick up one of the proposed sessions?
[19:36] <cdbs> dpm: No leave it, looks like I'll be busy in other work that week, would be difficult to get 1 straight hour out
[19:36] <dpm> ok, no worries
[20:34] <bcurtiswx> kenvandine, do you use nautilus for ssh/sftp?
[20:34] <kenvandine> bcurtiswx, yes
[20:35] <bcurtiswx> does that crash unity for you?
[20:35] <bcurtiswx> kenvandine, ^^
[20:36] <kenvandine> bcurtiswx, wow... it does
[20:36] <kenvandine> i don't recall that happening before
[20:37] <kenvandine> and i use it pretty regularly
[20:37] <bcurtiswx> well at least i feel better it's not just me
[20:37] <kenvandine> fie a bug and i'll "me too it"
[20:38] <bcurtiswx> anyway i can catch that crash to put in the bug report?
[20:49] <mterry_> bcurtiswx, it doesn't appear in /var/crassh?
[20:49] <mterry_> crash even
[20:50] <bcurtiswx> mterry, ah right, i never look there :X lemme check right now
[20:52] <bcurtiswx> mterry_, nope nothing in there :-X, checked the compiz crash, was from the 16th.
[20:54] <bcurtiswx> mterry_, if you use sftp/ssh from nautilus you may be able to confirm the crash.. just use sftp/ssh in nautilus and unity will crash
[20:54] <bcurtiswx> specifically in my case i had to input a password
[20:54] <bcurtiswx> checked the keyring crash file, nothing recent in it tho
[20:55] <mterry_> bcurtiswx, i'm in a weird state, in classic gnome, right now
[20:55] <mterry_> can't easily switch to unity
[20:55] <bcurtiswx> mterry_, OK np :)
[20:55] <bcurtiswx> kenvandine, do you have a crash file in /var/crash ?
[20:56] <bcurtiswx> from unity, specifically
[20:59] <mterry_> bcurtiswx, crashes you'll see there will likely be in the compiz binary, as unity is just an in-process plugin
[20:59] <mterry_> unless we're talking the unity-panel-service or the unity-window-decorator
[21:00] <bcurtiswx> mterry_, yup i've checked all crash files that would come close to unity/compiz and nothing recent
[21:00] <mterry_> k
[21:04] <kenvandine> bcurtiswx, nope... no compiz crash file
[21:04]  * kenvandine waves on the way out :)
[21:04] <bcurtiswx> kenvandine, k thx. enjoy your afternoon/evening
[21:26] <htorque> seiflotfy: hi, zeitgeist-datahub seems to become a zombie process early in the session start (seeing this on two systems) - is this a known issue?
[21:31] <seiflotfy> htorque, can u come on #zeitgeist an report that so the maintainer can catch on it
[21:55] <chrisccoulson> hi jasoncwarner
[21:55] <chrisccoulson> i recreated your right-click bug btw ;)
[21:55] <chrisccoulson> (and there's a pretty easy reproducer for that too)
[21:56] <jasoncwarner> nice
[21:56] <chrisccoulson> if you open the dash and then click back in the firefox window, the context menu is always messed after that
[21:57] <chrisccoulson> (until you focus another window)
[22:00] <jasoncwarner> oh really? hmm
[22:00] <jasoncwarner> chrisccoulson: wonder if that makes the firefox global menu disappear as well...which is something else I'm seeing but can't get to recreate...
[22:01] <chrisccoulson> jasoncwarner, you mean that it stops appearing in the panel>
[22:01] <chrisccoulson> ?
[22:01] <jasoncwarner> chrisccoulson: yeah
[22:02] <chrisccoulson> jasoncwarner, i bet that's bug 718926
[22:02] <ubot2> Launchpad bug 718926 in bamf "Some apps don't integrate to appmenu after having their windows closed" [High,Triaged] https://launchpad.net/bugs/718926
[22:02] <chrisccoulson> that's pretty bad, we could do with getting somebody to look at that
[22:02] <chrisccoulson> i'm not sure if it's on anyones radar
[22:02] <jasoncwarner> I'll check
[22:02] <jasoncwarner> chrisccoulson: lets see if we can get it on someones ;)
[22:03] <jasoncwarner> chrisccoulson: care to talk to didrocks about that?
[22:03] <chrisccoulson> jasoncwarner, yeah, sure
[22:03] <jasoncwarner> thanks