[00:01] <RAOF> Ok.  While f-spot does a test-build it's time for coffee!
[00:29] <RAOF> Hurray for thorough testing.  What's that stupid align editor doing?
[01:38] <RAOF> I wonder if anyone will notice that the f-spot display gets corrupted if you use the “adjust colours” tool directly after the “straighten” tool.
[02:18] <Quickard> I can not log in to ubuntu because I can not see nor enter anything into the user accounts window
[02:18] <Quickard> any idea's?
[02:21] <RAOF> Are you running Lucid?
[02:23] <Quickard> no
[02:24] <RAOF> Then I suggest getting help in #ubuntu, or on ubuntuforums.org.
[02:26] <RAOF> rickspencer3: Good evening to you :)
[02:26] <rickspencer3> hiya RAOF
[02:26] <rickspencer3> how are you this morning?
[02:26] <RAOF> Pretty good.
[02:27] <RAOF> I think I've *almost* nailed this f-spot view-mode bug.
[02:27] <RAOF> And then I shall go out and have lunch at a nice local café.
[02:28] <rickspencer3> RAOF, this is great news
[02:28] <rickspencer3> RAOF, has pitti set up an intro call for the three of us?
[02:28] <RAOF> He has not, no.  Unless that's hit my inbox in the last 1/2 hour.
[02:51] <lifeless> RAOF: you've moved already? :P
[02:53] <RAOF> lifeless: There *are* nice cafés in Cammeray, you know :P
[02:54] <RAOF> Is it wrong to want *another* 3GB of ram for this laptop? :)
[02:56] <RAOF> Ok.  I know where the problem is, I know how to trigger it, I know how to work around it.  Time for luncheon!
[02:57] <rickspencer3> "Luncheon"?
[02:57] <rickspencer3> I guess he will be luncheoning with the Queen?
[03:07] <bryceh> rickspencer3, it's like a truncheon but yummier
[03:07] <rickspencer3> lol
[03:13] <TheMuso> lol
[03:31] <Nafai> Is anyone else getting "Maximum Number of Clients reached" in ~/.xsession-errors and can't start any more X apps?
[04:07] <RAOF> Sing Ho! for the life of a disposed Gdk.Pixbuf!
[04:10] <kenvandine> RAOF, hey... any more luck with f-spot?
[04:10] <RAOF> This build should resolve the final bug.
[04:10] <RAOF> (That I know of)
[04:11] <RAOF> There's an important difference between returning a modified copy of the input variable and returning a new object that's a modified copy of the original :)
[04:12] <RAOF> This is actually an f-spot bug that that's displayed much more prominantly by view mode editing.
[04:13] <RAOF> Oooh.  Make that two bugs.
[04:17] <RAOF> Again, there's an important difference between modifying the argument and modifying a copy :)
[04:22] <RAOF> kenvandine: I'll strip the debugging out of this patch and send you a debdiff?
[04:28] <kenvandine> cool
[04:38] <RAOF> Where would you like the debdiff?
[04:39] <RAOF> kenvandine: ^^^
[04:39] <kenvandine> email?
[04:40] <RAOF> Ok.
[04:43] <RAOF> Sent.;
[05:01] <crimsun> interesting. The date-time applet (wrong name, probably) updates correctly for daychange, but the date picker in the calendar fails to
[05:59] <kenvandine> RAOF, awesome work on f-spot
[06:00] <kenvandine> RAOF, can you also add forward and back navigation buttons?
[06:00] <kenvandine> like is in the library browse mode?
[06:00] <kenvandine> if you open it in view mode, with multiple photos
[06:01] <kenvandine> it is a real pain to switch
[06:04] <RAOF> kenvandine: That's a good point.
[06:04] <kenvandine> it should be easy to add
[06:04] <kenvandine> the other problem... which is much hard
[06:04] <kenvandine> +er
[06:04] <kenvandine> is undo :)
[06:04] <RAOF> Yeah.
[06:05] <RAOF> I probably can, but I've context-switched to why apw's .33 drm backport kernel fails for me.
[06:05] <kenvandine> not sure that is reasonable to solve right now
[06:05] <kenvandine> ok
[06:06] <RAOF> Undo might be a bit much to aim for before beta.
[06:06] <kenvandine> yeah, i figured
[06:06] <kenvandine> the nav stuff should be easy, i would think
[06:07] <RAOF> Yeah.
[06:07] <kenvandine> f-spot doesn't have any notion of undo now
[06:07] <RAOF> Right.  Just multiple versions.
[06:08] <RAOF> Didn't I read where f-spot was going to transition to GEGL?
[06:08] <RAOF> That'd pick up undo by default, but *certainly* wouldn't be beta-1 worthy ;)
[06:09] <kenvandine> i hadn't heard that :)
[06:09] <RAOF> Maybe I'm making it up :)
[06:09] <RAOF> It'd be good, though!
[06:09] <kenvandine> it would
[06:09] <kenvandine> and it makes sense
[06:10] <RAOF> It'd be nice if f-spot had a better story to tell about RAW photos, too, but again that's a hard problem, I think.
[06:12] <RAOF> Ok.  The nouveau problem was because I suck, and had a mismatched libdrm.
[06:19] <tjaalton> umm, so our gdm is completely separate from debian?
[06:20] <tjaalton> it doesn't support $USERXSESSIONRC like debian does
[06:20] <czajkowski> keep failing on a Karmic upgrade http://paste.ubuntu.com/388087/
[06:22] <tjaalton> ok it's bug 475090
[07:15] <didrocks> good morning
[07:17] <RAOF> Aloha, didrocks
[07:21] <didrocks> hey RAOF
[07:21]  * didrocks RAOF hey
[07:21] <didrocks> ;)
[08:09] <pitti> Good morning
[08:09] <pitti> kermiac: right, because it previously copied the wrong keybinding to the compiz part of the settings; sorry for that
[08:10] <pitti> RAOF: I'm about to send a mail for the interview; at which time (UTC) are you available, so that I can check for some reasonable overlaps?
[08:11] <pitti> RAOF: would probably be good in your early morning/my late evening, so that Rick can participarte as well
[08:12] <RAOF> Is tomorrow morning the appropriate soonness?
[08:12] <RAOF> If so, 8am would be fine; that'll be less uncomfortable for you & Rick.
[08:14] <RAOF> Mmm. Evolution doesn't much like trying to build a search folder for all the launchpad bugs I've touched :)
[08:15] <pitti> RAOF: sounds fine; thanks!
[08:16] <pitti> RAOF: is that 2000 UTC?
[08:17] <RAOF> I think it's 2100UTC?
[08:18] <RAOF> I'm UTC+11, so 800 will be... 1900UTC.
[08:18] <RAOF> Don't mind me, I'm a mathematician. :/
[08:18] <pitti> ah, good; thanks!
[08:18] <pitti> that's 8 pm here, which is nice for seb128 and me
[08:20] <RAOF> Ahem.  No, I was right the first time.  2100UTC
[08:20]  * RAOF is having real difficulties doing 8 - 11 mod 24
[08:22] <pitti> RAOF: that gets very close to the next confcall of Rick's; can we do 2030 UTC?
[08:23] <RAOF> That will be 7:30 here.  I can do that.
[08:25] <RAOF> I'm going to head out for a brisk walk before it gets dark; I'll be back later.  2030UTC is ok.
[08:26] <pitti> RAOF: ok, google call invitation sent; thanks!
[08:26] <pitti> RAOF: have a good night then
[08:26] <pitti> and sleep well!
[08:34] <kermiac> pitti: no problem, just making sure you were aware... I added a comment to the bug report for anyone else who might be effected. I like the keybinding & am finding it very useful :)
[08:35] <kermiac> ty for the fix :)
[08:43] <seb128> hello
[08:43] <didrocks> hey seb128 ;)
[08:43] <pitti> bonjour seb128
[08:43] <seb128> nothing like starting the day by waiting for a 15 min fsck routine check
[08:43] <pitti> seb128: how are you?
[08:44] <seb128> lut didrocks, pitti
[08:44] <didrocks> you are how? not missing the Olympics Games?
[08:44] <pitti> seb128: heh, extra coffee break? :-)
[08:44] <seb128> pitti, good thanks ;-)
[08:44] <seb128> didrocks, a bit but not missing sleep at least ;-)
[08:44] <didrocks> heh :-)
[08:44] <seb128> how are you guys doing?
[08:44] <mvo> hey seb128
[08:44] <seb128> hey mvo
[08:45] <didrocks> hum fine thanks. Real sunny day at last \o/
[08:46] <seb128> bah
[08:46] <seb128> pitti, good timing, 2 calls during my swimming class :-(
[08:47] <seb128> I guess I will have to cancel today
[08:49] <pitti> seb128: oops; we can move them
[08:49] <pitti> seb128: can you please add your swimming classes to the calendar?
[08:49] <seb128> pitti, no that's ok
[08:49] <seb128> I somewhat hurt my wrist
[08:50] <seb128> so maybe not forcing on it today will be good
[08:50] <pitti> seb128: we can move them later; I'm sure RAOF wouldn't mind getting up a bit later
[08:50] <RAOF> pitti: Absolutely true!
[08:50] <seb128> will add those to the calendar
[08:54] <didrocks> seb128: btw, I've found the commit to the strange Alt + 7 behavior: http://git.gnome.org/browse/metacity/commit/?id=0f805bfdfb46e6739912df042f628ca9913b433c
[08:54] <seb128> didrocks, good job
[08:54] <didrocks> seb128: I'm just puzzled why it just not fetch Alt + alt gr + è on an azerty keyboard
[08:56] <seb128> dunno
[08:56] <huats> morning guys !
[08:56] <seb128> keybindings are a mystery to me
[08:56] <seb128> lut huats
[08:56] <pitti> bonjour huats!
[08:56] <huats> guten morgen pitti !
[08:56] <didrocks> seb128: ok, I was hoping you had some clue about keybindings. I'll ask on #gnome-hackers so. Thanks :)
[08:56] <didrocks> salut pitti
[08:56] <huats> (notice the right spelling :))
[08:56] <didrocks> s/pitti/huats
[08:57] <seb128> didrocks, sorry but no ;-)
[08:57] <seb128> good idea
[09:25] <chrisccoulson> good morning everyone
[09:26] <ara> morning chrisccoulson
[09:26] <chrisccoulson> hi ara
[09:26] <seb128> hey chrisccoulson
[09:26] <seb128> how are you?
[09:26] <didrocks> hey chrisccoulson and ara
[09:26] <chrisccoulson> hey seb128, yeah, good thanks
[09:26] <chrisccoulson> how are you?
[09:26] <chrisccoulson> hey didrocks
[09:26] <seb128> good!
[09:26] <seb128> I had a good night of sleep
[09:26] <seb128> went to be early yesterday
[09:26] <seb128> what about you?
[09:27] <chrisccoulson> yeah, it was difficult to do anything last night ;)
[09:27] <chrisccoulson> i had a fairly early night
[09:28] <chrisccoulson> bah, no sound again this morning
[09:29] <seb128> wfm
[09:29] <pitti> hey chrisccoulson
[09:29] <seb128> I've to change the output in the capplet between dock station and laptop though
[09:29] <seb128> which is confusing and not nice user experience
[09:29] <pitti> chrisccoulson: you should have an invitation email for a short intro confcall this evening
[09:30] <chrisccoulson> seb128 - i get a load of errors in my syslog occasionally when i boot, and sound doesn't work until i've rebooted again
[09:30] <chrisccoulson> hey pitti, just looking at that now
[09:52] <bratsche> Morning!
[09:53] <pitti> hey bratsche
[09:54] <didrocks> hey bratsche
[10:01] <chrisccoulson> seb128 - i'm still ok to upload these string changes from tedg aren't i?
[10:02] <chrisccoulson> (i was hoping to do that last night)
[10:02]  * pitti hears string changes and does o_O
[10:02] <chrisccoulson> heh
[10:02] <pitti> to indicators?
[10:02] <chrisccoulson> pitti - tedg suggested some string changes for gdm, gpm, gnome-session and gnome-panel, to make suspend/shutdown terminology consistent everywhere
[10:04] <pitti> can these still be pushed into GNOME, or is it too late for 2.30?
[10:04]  * pitti is afraid of breaking lots of translations
[10:04] <chrisccoulson> pitti - it's too late for 2.30
[10:04] <seb128> chrisccoulson, oh yes
[10:04] <seb128> pitti, too late
[10:04] <chrisccoulson> seb128 - you uploaded the gnome-session change already didn't you?
[10:05] <chrisccoulson> (but that one doesn't touch upstream code)
[10:05] <seb128> chrisccoulson, yes, you told me to do it no?
[10:05] <seb128> it does
[10:05] <seb128> the inhibit strings
[10:05] <chrisccoulson> seb128 - oh, ok
[10:05] <chrisccoulson> well, i can do gpm and hopefully gdm this morning if everyone is ok with that
[10:06]  * chrisccoulson checks he can upload gdm
[10:07] <chrisccoulson> i can forward tedg's changes to the gnome bugzilla anyway, and they can consider those for next cycle
[10:07] <seb128> please do
[10:07] <seb128> yes
[10:19] <chrisccoulson> deskbar-applet is painfully slow to build
[10:20] <seb128> why do you build this one?
[10:20] <didrocks> s/fully slow to build// :)
[10:20] <chrisccoulson> seb128 - there's a new version in the sponsor queue
[10:21] <chrisccoulson> it hangs around for a long time building the documentation
[10:33] <seb128> RAOF, hey
[10:34] <seb128> RAOF, did you have a good day?
[10:35] <RAOF> seb128: Yeah.  I beat f-spot into submission, I've checked that the .33 drm backport kernel will fix nouveau, and poked at gjs's build failure on armel.
[10:36] <seb128> RAOF, nice! is f-spot ready for upload now?
[10:36]  * seb128 would like to cross that for beta-1 work items
[10:37] <RAOF> kenvandine would like some extra navigation on the view mode, which makes sense and should be fairly easy; that *could* be added later.
[10:39] <seb128> RAOF, ok let's do that later
[10:39] <seb128> if we have something we can use land that first step
[10:39] <seb128> we can always update as needed
[10:39] <RAOF> Yeah.
[10:39] <seb128> can you hand me a patch or update?
[10:39] <RAOF> I'll attach a debdiff to the bug.
[10:40] <seb128> thanks
[10:40] <RAOF> kenvandine has it, too.
[10:40] <didrocks> pitti: oh, the dvd was the guilty one! http://people.canonical.com/~ubuntu-archive/component-mismatches.txt. I don't see any advantage to put it as an app on the dvd too as we already have OOo. I mean, the CD should be basically langpack + "featured" apps if we want to be coherent (there is still the issue of some featured apps are in universe)
[10:41] <pitti> didrocks: yes, agreed; would you mind dropping it there?
[10:41] <pitti> (just a seed change)
[10:41] <didrocks> pitti: sure
[10:41] <didrocks> pitti: I upload the new metapackage too, right?
[10:41] <pitti> didrocks: not for the DVD
[10:41] <pitti> just the seed change is enough
[10:42] <didrocks> pitti: oki, the DVD metapackage is built automatically or is there other reasons?
[10:42] <huats> chrisccoulson, thanks for the deskbar applet sponsoring :)
[10:42] <pitti> didrocks: I don't think it uses a metapackage
[10:42] <chrisccoulson> huats - you're welcome
[10:42] <pitti> didrocks: I believe the CD build scripts just pull the seeds, similar to "live"
[10:42] <didrocks> pitti: oh ok, thanks for the info :)
[10:43] <huats> if someone can give a look at https://bugs.edge.launchpad.net/ubuntu/+source/pessulus/+bug/513316
[10:43] <huats> it would be great :)
[10:45] <asac_> mvo: there?
[10:46] <mpt> good morning mvo
[10:46] <RAOF> seb128: bug #484888
[10:47] <seb128> RAOF, you rock, thanks
[10:47] <mvo> hey asac_
[10:47] <mvo> mpt: good morning
[10:50] <mpt> mvo, what's on the schedule for today? :-)
[10:54] <mvo> mpt: icons and reviews
[11:00] <seb128> RAOF, would it be hard to have the sidebar with edit selected in the combo on by default?
[11:01] <mpt> mvo, great, I'm chasing down some icons
[11:05] <seb128> mpt, hi
[11:05] <seb128> mpt, can you reply to the comment on bug #531486
[11:05] <seb128> can -> could
[11:05] <seb128> mpt, thanks ;-)
[11:05] <mpt> seb128, sure thing
[11:08] <RAOF> seb128: It defaults to the previously selected view.  It would probably be pretty easy to change that, though, if you wanted.
[11:10] <mpt> seb128, done.
[11:10] <seb128> mpt, thanks
[11:10] <seb128> RAOF, ok, commented on the bug
[11:10] <seb128> RAOF, that can wait for your tomorrow anyway
[11:10] <seb128> RAOF, 'night
[11:11] <RAOF> Night!
[11:12] <lool> pitti: LP #463471: see my last comment, it is in case it's important to have identical log entries after upgrades
[11:12] <lool> I don't personally care strongly; whoever is familiar with the rsyslog switch can comment
[11:13] <pitti> lool: ah, I see; reopened then
[11:13] <pitti> (as wishlist)
[11:18] <chrisccoulson> it seems plenty of people are opting to not use the indicator-applet, and using the fallback status icons
[11:18] <chrisccoulson> people are still reporting issues with gpm
[11:18] <chrisccoulson> and someone just e-mailed me a 2MB video showing an issue
[11:18] <seb128> chrisccoulson, I don't think that's what happens really
[11:19] <seb128> I guess it's rather most user dropped the useless indicator message previous cycles
[11:19] <chrisccoulson> yeah, possibly
[11:19] <seb128> which is used for new indicators now
[11:19] <seb128> I want to force re-add it on upgrade
[11:19] <seb128> will do that today when I do the string update too
[11:19] <chrisccoulson> i'll have to speak to tedg later about fixing the fallback so it works properly
[11:19]  * hyperair fights back the urge to yell 'I told you so!'
[11:20] <seb128> hyperair, told about what?
[11:20] <hyperair> seb128: about indicator applet suckiness.
[11:20] <seb128> it doesn't suck
[11:20] <seb128> it's not suitable for everything yet
[11:20] <seb128> but I don't see how ie bluetooth is less of a good experience now
[11:21] <hyperair> i.e. it sucks for stuff that deviates slightly from your typical gtk+ application that needs that icon.
[11:21] <seb128> right
[11:21] <seb128> which is why we rolled back the layout indicator
[11:21] <hyperair> which indicator was that?
[11:21] <seb128> but your comment is not really constructive either
[11:22] <seb128> gnome-settings-daemon
[11:22] <seb128> when you have several layout configured
[11:22] <seb128> you get a label in the notification area to show the current one
[11:22] <seb128> and switch between those by clicking
[11:22] <hyperair> seb128: how constructive would you have me put it? i requested tooltips, but the answer is maybe we'll consider it next cycle.
[11:22] <seb128> I don't see tooltips being useful for it bluetooth
[11:22] <seb128> it, ie
[11:23] <hyperair> seb128: just adding tooltip support (especially for those large custom tooltips would shut me up about appind.
[11:23] <seb128> you all special case on the music player case
[11:23] <hyperair> bluetooth is a special case on its own.
[11:23] <seb128> tooltips are not really nice though
[11:23] <hyperair> there's no way you can mistake the bluetooth icon for anything else
[11:23] <hyperair> absolutely no way
[11:23] <vish> seb128: volume applet needs tooltips too , was useful :)
[11:23] <hyperair> everything that uses bluetooth uses the same icon.
[11:24] <seb128> vish, how hard is it to press the mouse button when you are over there
[11:24] <hyperair> but it is very easy to wonder what some other icons are, e.g. update-notifier
[11:24] <seb128> the volume info is directly in the icon too
[11:24] <vish> but that doesnt display the % and tooltips were used by transmission , and several other apps
[11:25] <seb128> anyway I'm not designer and I don't want to argue about those
[11:25] <vish> ;)
[11:25] <seb128> I find tooltip getting in the way
[11:25] <seb128> and having to click one time not being that much extra efforts
[11:25] <seb128> so it works for me
[11:25] <hyperair> seb128: take a good look at the liferea icon, and honestly tell me whether you'll be able to figure out that that globe is liferea without a tooltip.
[11:26] <Ng> hyperair: that's not an argument for tooltips, that's an argument for liferea to get a better icon
[11:26] <seb128> hyperair, I don't think tooltip are made to explain you what a software is
[11:26] <hyperair> Ng: it's an argument that not all icons are intuitive, and it's not logical to expect everyone to be able to agree that one icon means something.
[11:26] <seb128> you can as well understand that by clicking on the icon and see what is in the menu
[11:26] <Ng> there's a perfectly standard icon for RSS
[11:26] <vish> Ng: but liferea displays the unread items.. we either bring the info to the dropdown , that would be nice
[11:27] <hyperair> vish: liferea changes its icon when there are unread items. that's enough for me really =\
[11:27] <vish> unread in the tooltips*
[11:27] <vish> hyperair: but it changes back once you read one folder ;)
[11:27] <hyperair> vish: oh it does?
[11:27] <vish> yup
[11:27] <hyperair> hmm
[11:28] <seb128> well the indicators are not made to be a replacement for everything anyway
[11:28] <vish> hyperair: the unread icon changes back to no new and the tooltips have the info
[11:28] <seb128> some things should not in the notification area to start with
[11:28]  * vish hides
[11:29] <seb128> the new system is nice and work well for ie sound, bluetooth, messages, etc
[11:29] <hyperair> seb128: i'm curious, how does gpm handle showing the remaining battery time?
[11:29] <seb128> not so well for custom apps trying to do random cracks
[11:29] <Ng> you could argue that liferea was a messaging indicator thing, but I suspect most rss users have so many unread things that it would make the messaging indicator impossible to use ;)
[11:29] <seb128> hyperair, the icon should be clear and you have the info the menu one click away
[11:29] <seb128> if you need the exact %
[11:29] <hyperair> seb128: and is this menu updated in real time?
[11:29] <seb128> well, as often as the tooltip was
[11:30] <seb128> not sure if that's real time
[11:30] <hyperair> seb128: i'm saying that if i leave open the menu, does it update?
[11:30] <seb128> of polling every 30 seconds
[11:30] <seb128> it should, I've not tried if it works
[11:30] <hyperair> hmm okay
[11:30] <hyperair> what about the exact %?
[11:30] <seb128> the menu has the % and time
[11:30] <hyperair> ah
[11:30] <hyperair> then that's fine
[11:30] <seb128> ;-)
[11:31] <hyperair> i still don't understand why tooltips are considered not desirable to have
[11:31] <hyperair> it's almost as if you're testing user understanding of the icons.
[11:32] <seb128> I never used tooltip as a way to understand the icons
[11:32] <seb128> and I don't think software writers used them this way
[11:32] <hyperair> seriously?
[11:32] <seb128> the tooltip usually have infos
[11:32] <hyperair> what about toolbar icons?
[11:32] <seb128> like the current playing song for rhythmbox
[11:32] <seb128> it doesn't tell you the icon is about rhythmbox
[11:32] <hyperair> do you instantly know what X toolbar icon does, despite having seen that icon for the first time in your life?
[11:33] <seb128> or that clicking on it will let you stop or play
[11:33] <seb128> no, I usually understand by clicking on it and seing what it does
[11:33] <hyperair> and that's dangerous.
[11:33] <seb128> like you never learn how the banshee icon works from the tooltip
[11:33] <hyperair> what if that icon meant rm -rf /? =p
[11:33] <seb128> or that you can change volume by mouse whell
[11:33] <hyperair> or some equally destructive command.
[11:33] <seb128> would that icon tell you by tooltip?
[11:34] <seb128> whoever write that icon would make sure the tooltip say a nice thing
[11:34] <seb128> ;-)
[11:34] <hyperair> currently playing song tells me a lot
[11:34] <hyperair> it tells me that the icon belongs to a media player that is currently running.
[11:34] <seb128> it doesn't tell you what apps is that
[11:34] <seb128> and how to interact with it
[11:34] <hyperair> it sits in the notification area.
[11:34] <hyperair> that's well enough indication
[11:34] <seb128> and "show rhythmbox ui" in the menu doesn't tell you that?
[11:35] <hyperair> you have to click on it.
[11:35] <seb128> well you open the menu and see what it has
[11:35] <seb128> how hard is it compared to a tooltip?
[11:36] <hyperair> seb128: one more click.
[11:36] <hyperair> say i want to look for one specific icon in a whole bunch of icons i don't recognize due to a changed icon theme.
[11:36] <seb128> well I can navigate the news one with one click and left, right
[11:36] <seb128> or will be able to keyboard navigate the menus in lucid
[11:36] <hyperair> hmm that will be useful, yes.
[11:36] <seb128> I find that easier to use
[11:37] <seb128> at least for me who knows the icons and what they are
[11:37] <hyperair> what about click-to-open which now needs me to click, select a menu entry and click that?
[11:37] <seb128> and don't need the manuel displayed in a tooltip to teach me :p
[11:38] <hyperair> the last time i assumed someone could read the text on the buttons of nautilus-share's dialog, i got blasted on a bug report for being a bastard, idiot and elitist.
[11:38] <seb128> I don't say the system is perfect
[11:38] <seb128> but most things are controls
[11:38] <hyperair> going by that logic, assuming people can understand icons could probably get you accused of the same thing.
[11:38] <seb128> not launchpad for opening apps
[11:38] <seb128> again the music player is a special case
[11:38] <seb128> launchpad -> launcher
[11:38]  * hyperair thought launchpad.net for a moment
[11:40] <hyperair> seb128: assuming all tooltips can be shoved into the first menu item, then how about shoving the now playing song into the first menu item as well?
[11:41] <seb128> there is a patch waiting for me to upload doing that
[11:41] <seb128> will be in lucid today
[11:41] <seb128> jpeterson did that change yesterday
[11:41]  * hyperair looks for qense.
[11:41] <hyperair> hmm he's not around.
[11:45]  * hyperair wonders what vish thinks about this
[11:46] <vish> hyperair: that was what i said earlier ;) , the tooltips need to be in the menu as well :)  [not just removed] but obviously having the tooltip is quicker
[11:46] <vish> s/as well/atleast
[11:46] <seb128> do you use tooltips that often?
[11:46] <vish> yup
[11:46] <seb128> for things like battery and volume the icon is usually fine enough for me
[11:46] <vish> power/volume/
[11:46] <vish> :)
[11:46] <seb128> and one click is not to much to get the detail
[11:47] <seb128> well battery has level and color
[11:47] <hyperair> i like to know exactly how much battery i have remaining
[11:47] <vish> seb128: well its an extra step , just because we didnt have time to fix it
[11:47] <hyperair> and i actively monitor it
[11:47] <hyperair> because i need to know when i need to start huntign for power sockets
[11:47] <hyperair> and how many hours i need to stretch my battery on for (i move around with my laptop, turn it on for lectures)
[11:48] <hyperair> those icons don't provide me that level of information
[11:48] <hyperair> but i suppose i'm fine with clicking.
[11:48] <hyperair> it's just a little harder with a touchpad.
[11:48] <seb128> use fn-f3
[11:49] <hyperair> wtf is fn-f3?
[11:49] <seb128> or whatever key your laptop has to display the battery info
[11:49] <hyperair> huh?
[11:49] <hyperair> there's such a key?
[11:49] <vish> ohh  , just found new shortcut
[11:49] <hyperair> my laptop has no such key.
[11:49] <seb128> my netbook and laptop have one
[11:49] <hyperair> my ideapad from lenovo doesn't.
[11:49] <seb128> try the fn-f<n> keys ;-)
[11:49] <vish> hyperair: no Fn hey?
[11:49] <hyperair> vish: many fn keys, none for displaying battery info
[11:50] <vish> hmm, weird , i didnt know either , just found that one ;)
[11:50] <hyperair> vish: i make it a point to study all the fn keys before buying any laptop.
[11:50] <hyperair> vish: there are a few must-have keys like media keys, touchpad key, and separate bluetooth/wifi kill keys
[11:50] <hyperair> and webcam key as wel
[11:51] <vish> hyperair: well many didnt work when i installed Ubuntu ;p , but worked in Windows ;)
[11:51] <hyperair> heh
[11:51] <hyperair> that's because of proprietary drivers
[11:51] <hyperair> seb128: so what does this fn-f3 show you?
[11:51] <vish> it was probably fixed recently
[11:51] <vish> hyperair: power info
[11:51] <bigon> kenvandine: I saw you uploaded new empathy version, but you use my debian revision :( (-1 instead of -0)
[11:51] <hyperair> seb128: gnome-power-manager? or some proprietary UI bypassing linux?
[11:51] <seb128> hyperair, a notify osd tooltip with battery infos
[11:51] <hyperair> O_o
[11:51] <hyperair> i see.
[11:52] <seb128> it's a gpm thing
[11:52] <seb128> need to go for lunch
[11:52] <seb128> bbl
[11:56] <chrisccoulson> wow, the day is flying by. nearly lunch time already
[11:57] <didrocks> chrisccoulson: I just grab my first coffee of the day :)
[11:57] <hyperair> wow the day has flown by. nearly the end of the day already ;-)
[11:57] <chrisccoulson> didrocks - how do you survive?
[11:57] <chrisccoulson> i've had 2 today :)
[11:58] <chrisccoulson> i'm actually finding that i'm drinking less coffee now
[11:58] <chrisccoulson> but that's probably because my chair is so comfortable that i don't want to get up and walk to the coffee machine ;)
[11:59] <didrocks> chrisccoulson: being excited by my job is enough ;)
[11:59] <chrisccoulson> didrocks - yes, there is that as well :)
[12:05] <pitti> less coffee -> good!
[12:05] <pitti> compensate with more sleep
[12:09] <ogra> pitti, that can have bad impact on IRC communications ... (if your head falls on the kbd)
[12:38] <seb128> james_w, hi, are you there to help me with a bzr packaging issue?
[12:39] <james_w> hi seb128
[12:39] <seb128> hey
[12:39] <vish> seb128: can we get Bug #530769 fixed for lucid? there is a patch as well , and i confirmed with the design team too
[12:40] <vish> s/patch/branch with fix
[12:40] <seb128> vish, will look at it, assign to the canonical desktop team maybe for now?
[12:40] <Laney> what makes stuff move from /usr/share/gnome/help/xxx to help-langpack?
[12:40] <vish> ok,  ty
[12:40] <seb128> james_w, so my issue is with lp:ubuntu/indicator-sound
[12:41] <seb128> james_w, that has a configure where lp:indicator-sound doesn't, which I supposed it's something kenvandine added by error
[12:41] <seb128> james_w, but the effect is that bzr-buildpackage revert the tarball configure to the bzr one
[12:41] <seb128> james_w, I tried to bzr del configure in lp:ubuntu/indicator-sound
[12:42] <seb128> james_w, but then it deletes it from the unpacked dir too
[12:42] <seb128> james_w, how do I tell those to let configure alone and use the tarball one?
[12:43] <james_w> what operation are you doing?
[12:43] <james_w> just bzr-buildpackage?
[12:43] <james_w> and no, Ken didn't add it by error, it's supposed to be there, which is why deleting it doesn't work
[12:44] <seb128> james_w, yes, bzr-buildpackage
[12:44] <seb128> well rather
[12:44] <seb128> bzr get lp:ubuntu/indicator-sound
[12:44] <seb128> cd indicator-sound
[12:44] <seb128> bzr merge lp:indicator-sound
[12:44] <seb128> dch -v 0.1.2-0ubuntu1 "update"
[12:44] <seb128> bzr-buildpackage
[12:44] <seb128> in a nutsheel
[12:44] <james_w> that's where you've gone wrong :-)
[12:44] <seb128> nutshell
[12:45] <seb128> oh?
[12:45] <james_w> you have to use "bzr merge-upstream --version 0.1.2 indicator-sound-0.1.2.tar.gz lp:indicator-sound"
[12:46] <seb128> urg
[12:46] <james_w> where the tarball can be on http:// or whatever
[12:46] <seb128> my workflow works fine usually
[12:46] <seb128> ie last time I workarounded by copying the configure from the tarball to bzr
[12:46] <james_w> it sucks that plain bzr merge doesn't work, but kind-of does, but bzr doesn't provide us the hook points we need to do that properly
[12:47] <didrocks> (merge-upstream for the win :))
[12:47] <seb128> well we do use merge for every dx usually
[12:47] <seb128> which kind of work
[12:47] <james_w> and bzr merge-upstream and bzr merge are kind-of different operations anyway
[12:47] <seb128> it's just weird it only does that weird configure change there
[12:47] <james_w> yeah, merge-upstream for new upstream tarballs
[12:47] <seb128> shouldn't it take the diff between upstream bzr and packaging one
[12:48] <seb128> and apply that to the tarball?
[12:48] <seb128> not discussing that I should use your syntax
[12:48] <seb128> even if it's harder to type and error prone
[12:48] <seb128> where bzr-buildpackage get the tarball for me using the watch etc
[12:48] <james_w> I'm going to implement watch file support
[12:48] <james_w> it's just not there yet
[12:48] <seb128> but I would still like to understand why my workflow lead to this configure downgrade
[12:49] <james_w> one day it will be "bzr merge-upstream; bzr commit"
[12:49] <didrocks> james_w: \o/
[12:49] <mpt> mvo, in your inbox should be an icon and a merge request
[12:49] <james_w> the rule is that what is in bzr is the same as what would be in the unpacked source
[12:50] <seb128> $ bzr merge-upstream --version 0.1.2 ../indicator-sound_0.1.2.orig.tar.gz lp:indicator-sound
[12:50] <seb128> Using distribution lucid
[12:50] <seb128> bzr: ERROR: Unable to find the tag for the previous upstream version, 0.1.1, in the branch: upstream-0.1.1
[12:50] <mpt> mvo, michaelforrest and chaotic are working on implementing "Featured" as a separate part of the lobby screen. Any navigation gotchas they need to be aware of?
[12:50] <seb128> bah
[12:50] <james_w> it doesn't unpack the tarball or anything, it just puts it there for dpkg-source to get the md5sum.
[12:50] <seb128> bzr hates me
[12:50] <didrocks> seb128: you should tag one rev to upstream-0.1.1 for the initial use (I guess james_w will explain you better than I)
[12:50] <james_w> grabbing it now to have a look
[12:51] <seb128> james_w, thanks
[12:51] <james_w> didrocks: this one should already have it done
[12:51] <didrocks> james_w: oh really?
[12:51] <james_w> I assume so
[12:51] <james_w> my guess is that the last upstream release was merged with bzr merge, not merge-upstream
[12:51] <seb128> it was
[12:51] <didrocks> james_w: btw, should I still use your branch from portland or can I switch back to lucid bzr?
[12:52] <seb128> as said I used the workflow I described before until now
[12:52] <seb128> I just usually copy the configure from the tarball
[12:52] <mvo> mpt: ok, thanks
[12:52] <seb128> to workaround the issue
[12:52] <james_w> right
[12:52] <seb128> but I figure I would try to get that issue fixed today ;-)
[12:52] <didrocks> seb128: if you want, I can setup a wiki page for us (update the previous one) for the merge-upsteam workflow (not complicated)
[12:52] <mvo> mpt: featured> I talked to him and did some small fixes
[12:52] <seb128> or to learn what I'm doing wrong
[12:52] <mpt> mvo, ok, cool
[12:53] <james_w> seb128: ok, I was wrong, this has never been set-up correctly
[12:53] <seb128> didrocks, I don't think there is anything specific to us there but yeah having documentation on that would be welcome
[12:53] <james_w> seb128: let me walk you through fixing it up
[12:53] <seb128> james_w, thanks
[12:53] <james_w> first, we set the tag that it is looking for to something close
[12:53] <james_w> bzr tag upstream-0.1.1 -r tag:indicator-sound-0.1.1
[12:54] <james_w> then try the command again
[12:54] <james_w> this should work, but conflict the debian/ directory
[12:55] <seb128> james_w,
[12:55] <seb128> Text conflict in configure
[12:55] <seb128> 1 conflicts encountered.
[12:55] <james_w> ok
[12:55] <seb128> The new upstream version has been imported.
[12:56] <james_w> so
[12:56] <seb128> I guess I can copy the tarball configure and bzr resolve?
[12:56] <james_w> this is a bit fiddly
[12:56] <james_w> that would work
[12:56] <seb128> but? ;-)
[12:56] <james_w> you can do it with bzr revert, but you need to give it a revision-id that is a little tricky to find
[12:57] <seb128> you have better? ;-)
[12:57] <james_w> nothing, you just came up with an easier way :-)
[12:57] <seb128> ok good
[12:57] <seb128> rickspencer3, hey
[12:58] <rickspencer3> hi seb128
[12:58] <pitti> hey rickspencer3
[12:58] <rickspencer3> hi pitti
[12:58] <pitti> rickspencer3: I added intro calls for Chris* to the calendar and sent invitations, FYIU
[12:59] <pitti> s/U$//
[12:59] <pitti> hope these are okay with you?
[12:59] <didrocks> hey rickspencer3
[12:59] <rickspencer3> hi Did
[12:59] <rickspencer3> didrocks, that is
[13:02] <seb128> james_w, ok, diff.gz looks clean now, thanks!
[13:02] <james_w> seb128: nice
[13:02] <james_w> seb128: sorry for the confusion
[13:03] <seb128> np
[13:03] <seb128> thanks for the rocking work you do ;-)
[13:03] <james_w> I promise it will all be super-slick one day
[13:03] <seb128> I'm looking forward an updated version using watch for getting the tarball and version :p
[13:03] <james_w> I will make you love it one way or another!
[13:03] <seb128> lol
[13:04] <james_w> yeah, it's not actually that much work
[13:04] <didrocks> yeah, merge-upstream is really rocking already. It makes a very clean bzr visualise tree :)
[13:04] <james_w> I just didn't get round to it before FF
[13:04] <james_w> maybe I can sneak it in ;-)
[13:04] <seb128> didrocks, I don't use bzr visualise but good to know ;-)
[13:05] <james_w> I bet seb uses bzr qlog
[13:05] <seb128> heh!
[13:06] <seb128> speaking of log I should try to convince bzr guys that bzr | less by default makes sense
[13:06] <seb128> it's default in git and very handy
[13:06] <seb128> bzr log | less
[13:06] <seb128> when doing bzr log
[13:06] <james_w> yep
[13:07] <james_w> or at least an easy config option ;-)
[13:07] <didrocks> seb128: I'll heavily +1 one this if you open the discussion
[13:19] <vish> Ng: just out of curiosity , why did you split the branding page?
[13:20] <Ng> vish: to reduce the amount of data the wiki server had to spit out to all the interested passers by from reddit/slashdot
[13:20] <Ng> vish: it was one of several things I did to stop the service from failing
[13:21] <vish> ah, that was why wiki was unusually lagging _more_  today :/
[13:21] <seb128> bah, bzr get from lp seems to hang now
[13:22] <james_w> seb128: service issue
[13:22] <seb128> james_w, which means "known and being worked"? ;-)
[13:23] <james_w> I assume so
[13:23] <seb128> ok, thanks
[13:26] <djsiegel1> hey seb128
[13:28] <djsiegel1> seb128: desktop workspace arrangement still 1x2 (instead of 1x4), and type-to-filter search on compiz window scale is not enabled.
[13:41] <vish> djsiegel1: did you test in guest session? is shows 1x4 , probably the user's default is not being touched
[13:41] <vish> s/is/it
[13:41] <djsiegel1> vish: ah ok
[13:41] <djsiegel1> actually
[13:41] <djsiegel1> on a freshly imaged machine it's 1x2
[13:42] <vish> oh , well , here in a guest session it is 1x4.. not sure how
[13:43] <seb128> djsiegel1, hey
[13:43] <seb128> hum weird, the default layout was 1x4 there
[13:43] <seb128> I will check that
[13:44] <seb128> didrocks, do you have some time to look at 3 small things?
[13:44] <seb128> didrocks,
[13:44] <seb128> 1- https://launchpad.net/bugs/530769
[13:44] <didrocks> seb128: sure, I'm in parallel mode right now, but if I can spread them during the day, no pb :)
[13:44] <seb128> 2- desktop workspace arrangement still 1x2 (instead of 1x4) (could you see if it's wm dependant)
[13:44] <seb128> 3- type-to-filter search on compiz window scale is not enabled.
[13:45] <didrocks> seb128: ok, on them :)
[13:45] <djsiegel1> thanks dudes!
[13:45] <didrocks> just what is type-to-filter?
[13:45] <didrocks> y/w djsiegel1
[13:45] <seb128> djsiegel1, ^ didrocks is going to look at those, we will the ones you mentioned done today
[13:45] <didrocks> when you have apps in expose mode, you type the name to filter them?
[13:46] <seb128> didrocks, the scale view in compiz displays the open windows on a sort of expose mode
[13:46] <seb128> didrocks, the filter let you keyboard type to search in the title of those
[13:46] <seb128> so you can keyboard navigate
[13:46] <didrocks> seb128: ok, make sense, will look at it :)
[13:46] <didrocks> thanks :)
[13:46] <seb128> it's only an option to activate in the compiz scale options I think
[13:46] <djsiegel1> didrocks: "scale window title filter" in compizconfig,  http://use-case-mapper.canonical.com/specifications/0AedmWmwP3lllZDltMzhiZF85NWdrMmN4bWMz/use_cases/2_
[13:47] <djsiegel1> no, not that
[13:47] <djsiegel1> https://wiki.ubuntu.com/OneHundredPaperCuts/Spec/495641
[13:47] <didrocks> djsiegel1: ok, thanks :)
[14:05] <Cedric25> no new sound theme ?
[14:05] <seb128> no
[14:08] <seb128> didrocks, seems 1- was decided to just not do it
[14:08] <didrocks> seb128: oh ok, one less WI \o/
[14:09] <seb128> didrocks, ;-)
[14:09] <didrocks> seb128: thanks for the notice, just saw the bug comment :)
[14:09] <seb128> np
[14:26] <mpt> mvo, should bugs like bug 531895 be filed just against the particular package, or against app-install-data-ubuntu as well?
[14:30] <mvo> mpt: package is ideal, you can add a task for app-install-data if you want
[14:30] <mpt> ok, ta
[14:30] <mvo> mpt: but it does not have a override mechanism at this point to add categories
[14:30] <mvo> we could add it, but the prefered fix is the upstream desktop file
[14:30] <mpt> ok
[14:30] <mpt> asac, can you take care of that one? Or is there someone else in particular who I should bug about it?
[14:40] <nigelb> I was about to poke someone about #rhythmbox in gimpnet, but I guess seb already took care of it :)
[14:49] <seb128> nigelb, I did
[14:49] <nigelb> I saw :)
[14:49] <nigelb> it was nice of you to step in immediately
[14:56] <pedro_> kenvandine, hello there, just wondering if you are aware of bug 521693
[14:57] <kenvandine> pedro_, yeah... that's a dupe :)
[14:57] <kenvandine> i'll mark it
[14:57] <kenvandine> pedro_, desktopcouch is busted
[14:58] <pedro_> kenvandine, ah ok, thanks!
[15:12] <LaserJock> didrocks: is there a specific size limit for UNE?
[15:12] <didrocks> LaserJock: for the image, you mean?
[15:13] <LaserJock> didrocks: yeah
[15:14] <pitti> the usual 700 MB
[15:14] <pitti> actually, 700 MiB, I believe
[15:14] <pitti> yes, indeed
[15:14] <didrocks> right, it should be MiB :)
[15:15] <LaserJock> I just wondered considering it's not usually installed via CD if maybe 1GB would be the limit
[15:20] <pitti> LaserJock: we still don't want it grow too fat; netbooks don't have infinite disk/ram either
[15:21] <dobey> 700 Men in Black?
[15:22] <pitti> dobey: always remember using correct units -- http://xkcd.com/394/ :)
[15:24] <seb128> chrisccoulson, still having gpm and gdm on your list for strings changes?
[15:24] <chrisccoulson> seb128 - yeah, that's still on my list
[15:24] <dobey> pitti: it doesn't really matter until I can have a HellaByte drive :)
[15:25] <seb128> chrisccoulson, thanks
[15:25] <LaserJock> pitti: I just wondered if the 700MB would be a hard limit like it is for CDs
[15:26] <pitti> LaserJock: it is an .iso after all
[15:26] <rickspencer3> pitti, LaserJock
[15:26] <rickspencer3> the answer is "yes"
[15:26] <rickspencer3> 700mg limit
[15:26] <LaserJock> pitti: when I did the Edubuntu .iso it went from 300MB to 3.5 GB, that was painful
[15:26] <pitti> I don't know CD media which are that light
[15:26] <rickspencer3> (assuming you are talking about UNE)
[15:27] <LaserJock> but I hear the Edubuntu team has kicked butt and got it down to like 1.5GB or so
[15:27] <vish> hehe , rickspencer3 taking too many pills ;)  " 700mg Limit"
[15:27] <dobey> http://www.makehellaofficial.blogspot.com/
[15:27] <pitti> I'd reckon that a normal CD is much heavier, more like 20 g
[15:27] <dobey> 20 g? for a cd?
[15:27] <rickspencer3> very funny
[15:27] <pitti> (with cover)
[15:27] <dobey> what's it made out of? unobtanium?
[15:28] <djsiegel1> kenvandine: can you please file a bug about needing new colors for those themes and assign otto greenslade?
[15:28] <pitti> rickspencer3: you know http://xkcd.com/394/, don't you? :-)
[15:28]  * rickspencer3 looks
[15:28]  * rickspencer3 reads xkcd instead of working
[15:28] <kenvandine> sure
[15:29] <rickspencer3> 1000Bytes during leap years
[15:29] <rickspencer3> :)
[15:29] <LaserJock> I thought xkcd was considered "professional development" or something ;-)
[15:30] <pitti> LaserJock: sure it is! http://xkcd.com/413/
[15:31] <kenvandine> djsiegel1, done... bug 531958
[15:31] <djsiegel1> kenvandine: thanks so much
[15:31] <kenvandine> djsiegel1, i marked it as high since today is UI freeze :)
[15:31] <kenvandine> i bet today is a fun day for UX :-D
[15:34] <jcastro> kenvandine: are you going to rebrand the gwibber theme as well?
[15:34] <kenvandine> jcastro, i hope
[15:34] <kenvandine> oh yeah... i should file a bug for that too
[15:34] <kenvandine> djsiegel1, should i do that and assign it to otto as well?
[15:34]  * kenvandine figures he can knock them both out at the same time
[15:34] <djsiegel1> kenvandine: can it be the same bug, affecting two projectS?
[15:34] <djsiegel1> or separate bug?
[15:34] <kenvandine> sure
[15:34]  * kenvandine does so
[15:35] <kenvandine> djsiegel1, done
[15:38]  * pitti closes his ~ 10th bug today, slowly catching up with seb128
[15:39]  * seb128 stop playing video games and go back to work
[15:39] <seb128> bah
[15:39] <seb128> sabotage!
[15:40] <pitti> seb128, rickspencer3: btw, I watched movies and listened to music all day and night! (fluendo testing...)
[15:40] <seb128> the lucid bug pages has been broken
[15:40] <pitti> seb128: MUAHAA
[15:40] <pitti> seb128: yes, I know; just pinged bdmurray about it
[15:40] <pitti> it stops at 2010-01-06
[15:40] <seb128> that was your plan to beat me?
[15:40] <pitti> nah
[15:40] <rickspencer3> pitti, great
[15:40] <seb128> that's a lame one :p
[15:40] <rickspencer3> and?
[15:40]  * seb128 hugs pitti
[15:40] <pitti> we are down to 716 bugs, that's hilarious
[15:41]  * pitti hugs seb128
[15:41] <seb128> rickspencer3, pitti: fluendo codecs works fine there
[15:41] <seb128> I played music in rhythmbox and totem
[15:41] <seb128> and edited tags in rhythmbox too
[15:41] <seb128> no issue
[15:41] <pitti> rickspencer3: I waited until I hit the first bug, and starved and died of insomnia
[15:41] <pitti> 's ok?
[15:41] <pitti> j/k
[15:41] <pitti> works fine here
[15:42] <seb128> ;-)
[15:42] <pitti> rickspencer3: I didn't try pitivi, though
[15:42] <seb128> pitti, I talked about it to upstream yesterday
[15:42] <seb128> the "break pitivi" was a pitivi bug
[15:42] <seb128> they fixed it in git yesterday
[15:42]  * pitti likes the "was"
[15:42] <pitti> ah, great
[15:43] <seb128> they also plan to get 0.3.4 out in the next days
[15:43] <seb128> so I recommend we do update to that and evaluate what to do based on it
[15:43] <pitti> *nod*
[15:43] <pitti> ok, quick break before the phone call mania starts
[15:44]  * didrocks has his IRC like a christmas party today: lot of hilights in all channels
[15:45] <pitti> didrocks: the secret is /nick didhidden
[15:45] <didrocks>  /nick Imnotthere :)
[15:45] <rodrigo_> kenvandine, pitti: https://bugs.edge.launchpad.net/libubuntuone/+bug/531971
[15:48] <kenvandine> rodrigo_, thx
[15:49] <seb128> mvo, there?
[15:50] <mvo> seb128: yes
[15:51] <seb128> mvo, so question for you
[15:51] <LaserJock> kenvandine: so I'm still confused as to if gwibber should be starting up now, the bug you mentioned the other day hasn't gone anywhere, do I just need to be patient or is there another bug?
[15:51] <seb128> mvo, you remember add-indicator-applet.py
[15:52] <seb128> mvo, we need to force run it on upgrade to lucid
[15:52] <seb128> mvo, what would you do? just create a new gconf key and keep the logic?
[15:53] <mvo> seb128: that was/is in gnome-panel, right?
[15:53] <mvo> seb128: let me have a quick look to refresh my memory
[15:53] <seb128> mvo, yes
[15:54] <seb128> also you create the gconf-default in the postinst
[15:54] <seb128> should that one be cleaned on upgrade in some way?
[15:55] <kenvandine> LaserJock, it is being worked
[15:55] <seb128> oh the postrm do it
[15:55] <mvo> does the same thing needs to run? or one that adds more applets (I assume the later)
[15:55] <kenvandine> LaserJock, just not an easy bug to fix :/
[15:55] <seb128> mvo, the same thing
[15:55] <kenvandine> LaserJock, sorry
[15:55] <mvo> seb128: new key that includes the distro name I think. so that on the next release we do not need to come up with yet anther key
[15:55] <seb128> mvo, the applet used to be that <no comment> (which means "useless" or whatever) message indicator
[15:56] <seb128> mvo, now it has all the appindicators too
[15:56] <seb128> mvo, which means many user dropped the <no comment> message indicator one
[15:56] <seb128> and don't understand why they don't get icons for it
[15:56] <seb128> ie
[15:56] <seb128> bluetooth
[15:56] <seb128> gpm
[15:56] <seb128> rhythmbox
[15:56] <seb128> sound
[15:56] <seb128> etc
[15:56] <seb128> so I think we ought to put it back there again
[15:57] <LaserJock> kenvandine: I don't mind waiting, I just hadn't seen any activity so I didn't know if I should ping somebody or be patient
[15:58] <dobey> is anyone else using lucid with a notification area instead of indicator applet?
[16:09] <mvo> seb128: right, I think a new gconf key is the answer. if we are reasonable sure that we need to only run it once, just any key will go
[16:09] <mvo> do
[16:09] <mvo> otherwise I would suggest to include the distro name
[16:09] <seb128> ok
[16:09] <seb128> I will do it by renaming the key
[16:10] <seb128> let's come with a better solution to do such things next cycle
[16:10] <mvo> ok
[16:10] <seb128> I will register a spec for it
[16:10] <seb128> "dealing with user config changes on upgrade"
[16:10] <seb128> we need a tool to run in user sessions to do that sort of changes
[16:10] <seb128> mvo, thanks
[16:14] <mvo> cheers, no problem
[16:25] <dobey> hey guys
[16:25] <dobey> what should Vcs-Bzr: be to point at the lp:ubuntu/source branch?
[16:25] <seb128> nothing
[16:26] <dobey> ok
[16:26]  * dobey removes Vcs-Bzr then
[16:27] <Keybuk> seb128: why doesn't gnome-screensaver ever unlock anymore?
[16:29] <Keybuk> it just sits at Checking... with a spinning mouse cursor
[16:30] <vish> Keybuk: Bug #524860
[16:31] <vish> Keybuk: killing the keyring , lets you get back to session
[16:31] <seb128> Keybuk, gnome-keyring bug
[16:31] <Keybuk> ah ok, cool
[16:32] <Keybuk> do you need any info on it?
[16:38] <seb128> Keybuk, not for now
[16:38] <seb128> Keybuk, the bug seems to have enough info it just need somebody to look at the code now
[16:38] <seb128> I will do that next week if upstream doesn't reply
[17:03]  * Nafai has to restart X again :(
[17:18] <didrocks> seb128: djsiegel1: so, closing the first papercut as invalid? (I tried to add a list with _list, but it's not working as well). 2. (num of ws) is done, does it have a bug associated? 3. (scalefilter) is i  compiz-fusion-plugins-extra, not compiz. so, not sure we can include it
[17:20] <seb128> didrocks, 1- yes
[17:20] <seb128> didrocks, 2- what component did you change?
[17:20] <seb128> didrocks, 3- oh that's different code not an option in what we use?
[17:20] <didrocks> seb128: only metacity is needed, when switching to compiz, it's refreshed
[17:20] <seb128> didrocks, ok good
[17:20] <didrocks> seb128: not sure when we don't switch and there is an upgrade on the fly
[17:20] <pitti> Nafai: frozen?
[17:21] <chrisccoulson> pitti - was your gdm change yesterday intended to fix the "text VT over X" issue?
[17:21] <didrocks> seb128: about 3. no. I tried to enable it first, and after fighting with it, just grepped the source for scalefilter and don't find it in compiz, but only in the other package which is another source, apparently
[17:22] <Nafai> pitti: No, I keep getting this after a while: "Maximum number of clients reachedError: Can't open display: :0.0", so I can't start new applications
[17:23] <seb128> didrocks, ok
[17:23] <pitti> chrisccoulson: only for subsequent X startups, not the first one
[17:23] <seb128> djsiegel, ^ no luck for scalefilter, it's coming from -extras in universe and we don't want to install extra by default
[17:23] <pitti> chrisccoulson: i. e. for launching guest session or user switching
[17:23] <pitti> Nafai: o_O
[17:23] <chrisccoulson> pitti - ah, ok. it works for that, but i still get it on startup
[17:23] <seb128> Nafai, leak somewhee
[17:24] <Nafai> yeah, not sure how to figure out where
[17:24] <pitti> chrisccoulson: right, me too
[17:24] <Nafai> I can't run things like xlsclients or so because they get the same answer :)
[17:24] <pitti> Nafai: does it increase over time after a reboot, i. e. when it still works_
[17:24] <pitti> _
[17:24] <pitti> bah, what happened to my question mark
[17:25] <pitti> oh
[17:25] <LaserJock> didrocks: hey, is this X-GNOME-FullName bug affected by UI freeze?
[17:25] <LaserJock> I just thought of that this morning
[17:25] <didrocks> LaserJock: hum, theorically yes…
[17:26] <pitti> LaserJock: which bug? I fixed the menus yesterday, I thought
[17:27] <didrocks> pitti: for n-l not showing them
[17:27] <pitti> didrocks: n-l doesn't use gnome-menus?
[17:27] <didrocks> pitti: no…
[17:27] <pitti> ok, your bug then
[17:27] <LaserJock> pitti: no, that's what I'm trying to fix
[17:27] <pitti> but why would it be affected by UIF?
[17:27] <LaserJock> well, if people are doing screenshots, the app names will change
[17:28] <pitti> you don't change strings, you just fix them to actually be displayed?
[17:28] <didrocks> pitti: it doesn't show X-GNOME-FullName, so that change the UI
[17:28] <pitti> LaserJock: that's fine, I think
[17:28] <LaserJock> ok
[17:28] <LaserJock> that's what I wasn't sure of
[17:28] <Sarvatt> Nafai: can you pastebin the output of xlsclients?
[17:28] <Nafai> Sarvatt: Sure
[17:28] <LaserJock> I won't be changing any translations, just the actual "what you see"
[17:29] <Sarvatt> you arent the first person i've heard run into that but i dont see how you're getting >256 clients
[17:29] <Nafai> Sarvatt: This is what I have right now: http://paste.ubuntu.com/388402/
[17:30] <Nafai> Yeah, I definitely don't have that many windows open
[17:30] <seb128> Sarvatt, it's probably a software leaking clients
[17:30] <seb128> like indicator-applet
[17:30] <seb128> could it be the fallback thing?
[17:30] <seb128> Nafai, do you plan a lot to make indicator fallback to notification area?
[17:30] <pitti> Nafai: what are these "exe" things?
[17:31] <Sarvatt> Nafai: are you using the nvidia blob by any chance?
[17:31] <didrocks> seb128: hum, in fact, 2. is more complicated when you don't switch between metacity and compiz. I'm first updating the default for metacity and see if I need to write something on compiz side
[17:31] <Nafai> I haven't been doing any testing recently
[17:31] <Nafai> Sarvatt: Yes, I am using the nvidia drivers
[17:31] <seb128> didrocks, I'm pretty sure the default was already correct for compiz
[17:31] <Nafai> pitti: Uh, good question
[17:31] <Nafai> How do I map a window id to a process?
[17:32] <seb128> Nafai, xprop -id?
[17:33] <Nafai> Ah
[17:33] <Nafai> That is a new chromium plug-in that I have recently installed
[17:33] <Nafai> I'll uninstall it and find out
[17:33] <Sarvatt> I think the problem nvidia blob/flash related
[17:34] <Sarvatt> is*
[17:34] <Nafai> quite possible
[17:37] <seb128> bryceh, didrocks: is xorg known to crash down on coming back from user switching on intel?
[17:38] <Sarvatt> chromium, flash, and the nvidia blob are a common theme in everyone i've seen having the exhausting clients problem at least
[17:39] <Nafai> well, I'm using all 3
[17:39] <Sarvatt> will have to dig through the chromium bug tracker to see if i can find anything when i get some time
[17:40] <didrocks> seb128: just tried on my hw with an intel driver, no crash but it didn't asked my 1st user password, which is… frightening :)
[17:41] <bryceh> seb128, it would not be surprising if it does that, but it's not a universal issue.  Maybe some hardware/driver specific glitch
[17:41] <bryceh> seb128, probably worth re-testing when we get the new drm stuff
[17:41] <seb128> bryceh, ok, it does it on both my d630 and mini
[17:41] <bryceh> supposedly a lot of bugs get fixed with the new drm
[17:41] <seb128> bryceh, is that in lucid? I did upgraded both boxes today
[17:41] <bryceh> seb128, should be in by the kernel freeze
[17:42] <bryceh> seb128, apw has a ppa with it I think
[17:42] <seb128> ok thanks
[17:42] <didrocks> seb128: that's strange, I upgrade one hour ago and I get it on the mini :/
[17:42] <seb128> I will try to check that
[17:42] <seb128> didrocks, why is that strange that you get it too?
[17:43] <chrisccoulson> brb, session restart
[17:43] <didrocks> seb128: oupss, *don't* get it (see my first comment ^)
[17:43] <seb128> didrocks, I get it when opening a guest session and closing it
[17:44] <seb128> didrocks, that worked this time, doesn't happen every time
[17:44] <didrocks> seb128: ok, I tried only a real user switching
[17:44] <didrocks> weird
[17:44] <didrocks> seb128: and with a real user, do you have too the "not asking the password for first user" when back?
[17:45] <seb128> didrocks, no
[17:47] <didrocks> seb128: did you use "switch from user <foo>" or did you directly pick a name? (it only happens for me when I pick a name on the menu)
[17:48] <seb128> didrocks, switch from user
[17:48] <seb128> but I don't want to crash my box now by playing too much with user switching
[17:48] <seb128> I will try again later
[17:49] <didrocks> ok, I just put a note somewhere to check that again, but it's reproduceable systematically for me
[17:50] <mpt> mvo, how's it going
[17:50] <mpt> ?
[17:57] <Sarvatt> chrisccoulson: btw if you didnt notice the lid close hang should be fixed in the -15 kernel, had any luck with it?
[17:57] <chrisccoulson> Sarvatt, i've not had a change to try it yet
[17:57] <chrisccoulson> will do that later though, thanks
[17:58] <Sarvatt> seb128: do you see any drm errors in dmesg when it happens? can you vt switch still?
[17:59] <rickspencer3> pitti, chrisccoulson I'm setting up the conference line now
[18:00] <pitti> on my way
[18:00] <seb128> rickspencer3, should I join?
[18:00] <rickspencer3> seb128, sure
[18:01] <seb128> Sarvatt, I will have to check for drm errors but I can't vt switch
[18:01] <rickspencer3> d'oh
[18:01] <rickspencer3> I don't have my leader code handy
[18:01] <rickspencer3> hold on
[18:01] <LaserJock> didrocks: this bug could be rediculously easy to fix if I'm right, stay tuned :-)
[18:01] <didrocks> LaserJock: sweet \o/
[18:04] <LaserJock> didrocks: \o/
[18:05] <LaserJock> didrocks: so uh, yeah. s/gmenu_tree_entry_get_name/gmenu_tree_entry_get_display_name/ does wonders ;-)
[18:05] <didrocks> LaserJock: so, it's using gmenu finally? I guessed you told the other it wasn't?
[18:06] <LaserJock> didrocks: I was looking for gmenu stuff in the wrong file
[18:06] <didrocks> LaserJock: sweet ;)
[18:06] <LaserJock> didrocks: gmenu is used in launcher-menu but not in launcher-application
[18:07] <LaserJock> didrocks: so do you want this? we don't patch upstream, but upstream is on 0.3 so I'm not sure where to put it
[18:08] <LaserJock> didrocks: rather, where do you want this? I'm pretty sure you want it ;-)
[18:08] <didrocks> LaserJock: well, I can patch upstream (for 0.1 release)
[18:08] <didrocks> yes, I want it \o/ ;)
[18:08] <didrocks> LaserJock: so, attach it to the bug and I'll make a new liblauncher release
[18:08] <didrocks> (for 0.1)
[18:08] <LaserJock> k
[18:09] <didrocks> thanks for your work, I guess my categorisation of "not so hard to patch" was not that bad :p
[18:11] <LaserJock> heh
[18:16] <Sarvatt> I actually like having the cursor during boot, putting the spinner in the middle of the ubuntu logo gives me something to do :)
[18:19] <LaserJock> didrocks: ok, patches for liblauncher 0.3 and 0.1 are in the bug report now
[18:19] <didrocks> LaserJock: sweet, I have a lot to do. So, I'll probably release a new liblauncher version tomorrow
[18:20] <LaserJock> didrocks: great. I'm just happy I was able to actually figure a non-packaging bug out :-)
[18:20] <didrocks> LaserJock: that will really rock to have comprehensive name again :)
[18:20] <LaserJock> didrocks: gwibber looks way better
[18:20] <didrocks> LaserJock: heh \o/
[18:20] <didrocks> yeah ;)
[18:22] <mvo> mpt: merging ui changes
[18:22] <rickspencer3> pitti, seb128, chrisccoulson i got dropped by the bridge :/
[18:22] <rickspencer3> no respect ;)
[18:23] <rickspencer3> can you guys just carry on and ping me if you need something from me?
[18:23] <seb128> lol
[18:23] <seb128> ok
[18:23] <pitti> rickspencer3: ack
[18:24] <LaserJock> didrocks: http://laserjock.us/files/UNE.png :-)
[18:26] <didrocks> LaserJock: indeed, that's a change :)
[18:27] <mpt> mvo, any progress on the "Themes & Tweaks" plumbing?
[18:28] <djsiegel> seb128: ok, too bad :)
[18:30] <LaserJock> didrocks: are Favorites actual copies of the .desktop or are they "linked"?
[18:30] <didrocks> LaserJock: favorites are just a gconf key IIRC
[18:31] <didrocks> LaserJock: you can have a look at the ubuntu-netbook-default-settings package
[18:33] <mvo> mpt: none, sorry. busy with the new design merges/fixes and the ratings stuff
[18:36] <mvo> mpt: and we need a UI freeze exception, I will file the needed report in some minutes
[18:36] <mpt> mvo, I totally forgot about the "fonts" Debian section. Maybe we can use that to fix the ttfm problem, if someone can fix bug 490401 and bug 490405.
[18:37] <LaserJock> didrocks: I was thinking of trying bug #283914 for my next trick, seem reasonable?
[18:38] <didrocks> LaserJock: it's a little bit harder I think, but can be interesting :)
[18:38] <didrocks> LaserJock: do not hesitate if you need any help tomorrow
[18:41] <LaserJock> didrocks: alright, I'm off for today to get real work done. I'll see what I can do with it this evening
[18:55] <chrisccoulson> heh :)
[18:56] <pitti> chrisccoulson: right, so in that way vala is pretty much like flex
[18:57] <chrisccoulson> pitti - yeah, i think so
[18:57] <chrisccoulson> i thought we were originally going to need it for tracker, but that was only because i was building from git
[18:57] <pitti> chrisccoulson: hm, it was you who provided a fix to make it build
[18:58] <chrisccoulson> pitti - i think i remember that, but i think there are new failures now
[18:58] <jcastro> pitti: ok so vino and hplip are all that's left. I'll poke smithj when he's around for hplip. Any burning issues or are we going to make it?
[18:58] <chrisccoulson> i'll check the changelog
[18:58] <pitti> chrisccoulson: still all the d-bus tests
[18:59] <pitti> jcastro: last time I checked, hlip had no usable patch; is there a new one now?
[18:59] <chrisccoulson> hmmm, i wonder why they broke again then
[18:59] <jcastro> pitti: no he hasn't gotten back to you yet on that, I'll poke him asap
[18:59] <chrisccoulson> i can try and take another look at that, but my vala knowledge is lacking a little ;)
[18:59] <pitti> chrisccoulson: I can have a look as well
[19:00] <chrisccoulson> or i could ping juergbi about it
[19:00] <pitti> chrisccoulson: in fact, I have nothing urgent to do right now, I'll have a look
[19:00] <chrisccoulson> pitti - thanks :)
[19:00] <pitti> (unless you want to and are at it, of course :) )
[19:00] <mvo> mpt: fonts section - indeed
[19:01] <jcastro> pitti: fyi Nafai made the changes you want to vino
[19:01] <pitti> jcastro: yes, I saw; thanks (still on my list)
[19:01] <jcastro> or at least attached new patches, heh
[19:02] <mvo> mpt: it contains fontforge as well but not ttf-sil-gentium that is in x11
[19:03] <pitti> chrisccoulson: vala bindings> those should mostly be static .vapi files; they are only needed when running vala, not for shipping .vapi files in packages
[19:03] <pitti> chrisccoulson: they are by and large annotated C .h files
[19:03] <mpt> mvo, right, that's what bug  490406 and bug 490401 are about, respectively
[19:03] <chrisccoulson> pitti - so, shipping bindings isn't good justification for having vala in main then?
[19:04] <pitti> chrisccoulson: it's not necessary, at least; you can just drop the .vapi files into the libfoo-dev, and be done with it
[19:04] <chrisccoulson> pitti - cool, that's good then
[19:04] <pitti> chrisccoulson: if you have vala code which you want to build during package build, then you need it of course
[19:04] <chrisccoulson> it would still be nice to make the test suite work though, else nobody is watching for real failures
[19:05] <pitti> but for upstreams which produce releases that build .vala -> .c at "make dist" time, it's not necessary
[19:05] <pitti> chrisccoulson: exactly
[19:05]  * pitti <- test suite addict
[19:05] <chrisccoulson> especially if we're going to be shipping more C files generated with vala
[19:05] <mvo> mpt: aha, ok - will you update the fonts matching rules in the .menu file?
[19:06] <mvo> mpt: fixing the sections for lucid should be trivial
[19:06] <mvo> mpt: we just need to make sure we target the bugs to not forget about it
[19:06] <mpt> mvo, sure, I could do that, but not today :-)
[19:06] <mvo> mpt: ok, no problem
[19:07] <chrisccoulson> tedg - there's still an issue with the fallback GtkStatusIcon in indicator-application (I can't remember whether I mentioned it already)
[19:07] <chrisccoulson> basically, gpm users are seeing a flashing tray icon without the indicator applet
[19:07] <tedg> chrisccoulson: On login?
[19:08] <chrisccoulson> it seems to be because it periodically calls app_indicator_set_menu to update the menu structure
[19:08] <chrisccoulson> and that creates a new fallback timer
[19:08] <chrisccoulson> which toggles the icon visibility when it  fires
[19:08] <tedg> chrisccoulson: Hmm, okay.
[19:08] <tedg> chrisccoulson: I hadn't heard that one.
[19:08] <chrisccoulson> tedg - i keep getting lots of reports in gpm
[19:09] <chrisccoulson> and people e-mailing me with 2MB videos now too ;)
[19:09] <tedg> chrisccoulson: Ah, okay.
[19:09] <tedg> chrisccoulson: That one will probably have to be a tomorrow thing though :-/
[19:09] <chrisccoulson> tedg - no worries, i just wanted to make sure you were aware of it
[19:12] <pitti> chrisccoulson: I hope it's something simple like relying on a local session dbus and not launching it itself; it fails the same way in Debian
[19:12] <chrisccoulson> pitti - yeah, that would make sense
[19:15] <chrisccoulson> right, baby time :)
[19:15] <chrisccoulson> bbl
[19:16]  * kenvandine might have a fixed desktopcouch to upload... brb after testing
[19:17] <pitti> chrisccoulson: hm, fails the same way locally
[19:21] <asac> mpt: thanks. micah has committed the fix - will check with him if there is something else on his list before next upload
[19:22] <mpt> thanks asac, I saw and was impressed by the quick fix
[19:22] <asac> yeah me too ;)
[19:22] <mpt> There are other easy categorization bugs if anyone's interested. ;-) https://launchpad.net/ubuntu/+bugs?field.tag=metadata
[19:23] <asac> had connectivity issues today and had a separate irssi open which didnt highlight your ping ;)
[19:23] <asac> but then it was just fixed
[19:51] <pitti> chrisccoulson: hah! it's fakeroot
[20:16] <pitti> chrisccoulson: (fixed package uploaded, will send to Debian)
[20:16] <chrisccoulson> pitti - excellent. i will have a look later at how you fixed it ;)
[20:16] <pitti> chrisccoulson: run make check under LD_PRELOAD= to circumvent fakeroot :)
[20:17] <jcastro> mdeslaur: your changelog in virtmanager mentioned a problem with python and libappindicators, anything I can do to help?
[20:18] <mdeslaur> jcastro: it's related to bug #530138
[20:19] <mdeslaur> jcastro: once that gets fixed, I can fix virt-manager
[20:19] <jcastro> mdeslaur: ok
[20:25]  * Amaranth wonders what'll happen the first time someone tries to shove an arbitrary widget into a menu and complains
[20:26] <mclasen> Amaranth: its just the wrong api...
[20:27] <dobey> Ampelbein: i've already shoved arbitrary widgets in menu items... but no complaints, it did what i expected/wanted it to do :)
[20:27] <Amaranth> dobey: ignored them?
[20:28] <dobey> Amaranth: ignored what? i didn't have anything to complain about
[20:28] <Amaranth> dobey: Right, did it ignore the widget?
[20:28] <dobey> no
[20:28] <dobey> the widget worked fine
[20:29] <dobey> but i wasn't trying to do interactivity
[20:29] <Amaranth> how did it forward an arbitrary gtk widget over dbus?
[20:29] <dobey> how did what?
[20:29] <dobey> i didn't use dbus
[20:29] <Amaranth> libappindicator
[20:30] <dobey> i wasn't using indicators
[20:30] <dobey> i was sticking arbitrary widgets inside a GtkMenuItem
[20:30] <Amaranth> dobey: which is not what we were talking about :)
[20:31] <dobey> eh? one sentence, and it mentioned nothing about appindicator. only about sticking arbitrary widgets in a menu
[20:32] <dobey> eh, anyway... back to writing a crapload of code
[20:34] <dobey> hrmm
[20:35] <dobey> i wonder why my card reader doesn't even show up in gnome-device-manager
[20:35] <chrisccoulson> gnome-device-manager is using hal isn't it?
[20:35] <dobey> i don't know
[20:35] <dobey> i just know i can't mount SD CF etc... cards from my reader
[20:36] <dobey> my ipod shuffle works ok
[20:36] <dobey> but my phone won't mount either
[20:36] <dobey> though my pre does show up in gnome-device-manager
[20:37] <dobey> well, a mass storage device shows up
[20:38] <dobey> and my Prē shows up in computer:///, until i tell the phone to go into disk mode
[20:38] <dobey> then it disappears :(
[20:42] <dobey> it doesn't even work in media sync mode where it emulates an ipod
[20:42] <dobey> :(
[20:45] <pitti> RAOF: good morning!
[20:47] <RAOF> pitti: Good mornininging!
[20:48] <didrocks> good morning RAOF :)
[20:48] <RAOF> dobey: That ipod mode of the prē has to be one of the stranger engineering hacks I've seen :)
[20:49] <RAOF> didrocks: And a fine morning to you, too.
[20:49] <didrocks> well, evening actually ;)
[20:50] <seb128> hey RAOF
[20:51] <pitti> bah, my computer took "UI freeze" a little too seriously
[20:51] <dobey> RAOF: i don't care, because i don't put music on my phone, but I do want to pull photos off it and stuff.
[20:51] <pitti> seb128: sorry, had to reboot; will get to NEW right now
[20:51] <dobey> of course, i would also very much like to read the data on all my SD cards
[20:51] <pitti> my computer decided that it's a good idea to suspend when I Ctrl+Alt+F7 back to X from a VT, or between X sessions
[20:51] <pitti> and suspend causes freezes :/
[20:52] <seb128> pitti, ok
[20:53] <pitti> let's see whether we can get this built in 9 minutes
[20:54] <pitti> seb128: meh, seems to hate me; "starts in 4 seconds" for two minutes now
[20:55] <seb128> kick it ;-)
[20:55] <pitti> ah, building
[20:55]  * kenvandine has a working desktopcouch!
[20:56] <kenvandine> whew...
[20:56] <didrocks> pitti: heh
[20:56] <RAOF> Yay!  Gwibber will work again!
[20:56] <kenvandine> yay!
[20:56] <didrocks> kenvandine: working = starting on dbus demand ? :)
[20:56] <kenvandine> yeah
[20:56] <kenvandine> and not crashing
[20:57] <didrocks> that's a good idea :)
[20:58] <kenvandine> usually good :)
[20:58] <pitti> seb128: light-themes binNEWed into main, right in time for publisher; so go ahead with the u-artwork
[20:58] <kenvandine> unfortunately the patch reverts part of what they wanted to fix in 0.6.2
[20:58] <kenvandine> but at least this isn't a regression
[21:00] <seb128> pitti, rickspencer3, RAOF: I will be a few minutes late
[21:00] <rickspencer3> seb128, ack
[21:00] <seb128> I want to land the ubuntu-artwork update now
[21:00] <rickspencer3> I *just* finished my class
[21:00] <rickspencer3> setting up the bridge in moment
[21:00] <pitti> seb128: that's fine, you know the intro :)
[21:01] <Nafallo> ehrm. guys... the theme is broken?
[21:02] <Nafallo> it tries to use 'Light' as Controls, but it should be 'Radiance'
[21:02] <Nafai> I don't yet have the theme :(
[21:02] <Nafallo> or am I missing something?
[21:02] <Nafallo> same for window borders
[21:04] <seb128> Nafallo, you must be using a ppa with beta work or something
[21:04] <seb128> Nafallo, the lucid theme is name radiance
[21:04] <Nafallo> seb128: naah. catched the binary directly via LP + gdebi. in my theme selector I had "Light" and "Dark" turn up?
[21:05] <seb128> Nafallo, those are ubuntu-artwork themes
[21:05] <seb128> the theme you grabbed is a gtk one
[21:05] <seb128> go in details
[21:05] <rickspencer3> pitti, RAOF I'll try dailing in again
[21:06] <rickspencer3> the bridge is just not working well today :(
[21:06] <Nafallo> seb128: ah. so I need update of that deb as well... got it. I only took specific debs as they built ;-)
[21:06] <Nafai> is the new theme available in lucid?
[21:07] <kenvandine> Nafai, the crank is turning :)
[21:07] <Nafai> yay
[21:07] <seb128> Nafallo, ok, I will check there is no bug, thanks
[21:08] <seb128> Nafallo, right, radiance is buggy, I will fix
[21:08] <seb128> ambiance should work
[21:08] <seb128> hum no
[21:08] <seb128> I will fix both
[21:08] <seb128> thanks for earlier catching
[21:09] <Nafallo> no worries :-)
[21:19] <rickspencer3> seb128, pitti, RAOF are you guys done talking?
[21:19] <seb128> no
[21:19] <rickspencer3> ok
[21:20] <rickspencer3> let me know if you have questions etc
[21:20] <rickspencer3> I can call in again if needed
[21:20] <seb128> pitti suggests moving to IRC
[21:20] <rickspencer3> kenvandine, how is gwibber working now (well desktopcouch) but you know
[21:20] <kenvandine> well!
[21:20] <rickspencer3> fixed or reverted?
[21:20] <kenvandine> and i just uploaded a fixed desktopcouch
[21:20] <kenvandine> sort of
[21:20] <rickspencer3> ok
[21:20] <kenvandine> reverted the dbus only getPort call in desktopcouch
[21:21] <rickspencer3> I'll dist-upgrade tonight
[21:21] <rickspencer3> get that new theme and all
[21:21] <rickspencer3> and hopefully gwibber will work ;)
[21:21] <rickspencer3> thanks kenvandine
[21:21] <kenvandine> but dc still has the fixes that makes it start up nicely by gwibber
[21:21] <kenvandine> and in the session too :)
[21:21] <kenvandine> i might get a gwibber uploaded tonight with the autostart stuff
[21:21] <rickspencer3> nice
[21:21] <kenvandine> and some other nice bug fixes
[21:22]  * kenvandine has been waiting to test !
[21:22] <kenvandine> rickspencer3, so chad still needs to fix the replication problem
[21:22] <rickspencer3> uh
[21:22] <kenvandine> but as long as gwibber starts dc, recplication will be fine
[21:22] <rickspencer3> replicatin problem?
[21:22] <kenvandine> apps that just call the python api to desktopcouch
[21:23] <kenvandine> it starts desktopcouch without starting the replication services
[21:23] <kenvandine> the reason all this got broken was they were trying to fix that
[21:23] <seb128> Nafallo, fixed version uploaded
[21:23] <kenvandine> so it always started all the needed stuff
[21:23] <kenvandine> but then hit these dbus threading issues
[21:23] <kenvandine> so i reverted  part of it
[21:23] <RAOF> So, back on IRC...
[21:24] <kenvandine> rickspencer3, so now desktopcouch starts nicely, but still only starts replication if you call it via dbus
[21:24] <kenvandine> which gwibber does for now
[21:24] <kenvandine> rickspencer3, but if photobomb uses dc, and you run it before gwibber... it would start dc without starting replication
[21:24] <Nafallo> seb128: yepp, saw. waiting for it to build :-)
[21:25] <kenvandine> it's a problem they know they need to fix.. but it isn't a new problem
[21:25] <Nafallo> building now ;-)
[21:25] <kenvandine> so at least reverting that part gets gwibber working... and desktopcouch to work at all
[21:26] <RAOF> The tasks I've got lined up immediately are: polishing the f-spot edit-in-view mode patch, and reviewing the status of the apw's drm backport kernel.  After that, there's investigating the gjs FTBFS on armel and bug #435805
[21:26] <seb128> RAOF, cf other channel
[21:28] <Nafallo> seb128: built and confirmed fixed. thanks for the quick response :-)
[21:28] <seb128> Nafallo, thank you for the testing and sorry about think to the ppa before checking ;-)
[21:28] <Nafallo> heh
[21:29] <rickspencer3> kenvandine, ack
[21:29] <rickspencer3> (on the replicattion not being started bug)
[21:33] <chrisccoulson> prepare for everyone asking "what happened to my terminal!"
[21:33] <chrisccoulson> ;)
[21:33] <seb128> lol
[21:33] <seb128> the new settings don't look good?
[21:35] <chrisccoulson> they look quite good
[21:35] <seb128> good ;-)
[21:36] <rickspencer3> pitti, RAOF f-spot status?
[21:36] <rickspencer3> so we have editing by no save or undo now?
[21:36] <RAOF> Yes.
[21:37] <pitti> you can always take a screenshot *cough*
[21:37] <RAOF> Heh!
[21:37] <rickspencer3> pitti, grrr
[21:37] <RAOF> We have editing that works as in the main library view.
[21:37] <rickspencer3> ok
[21:37] <rickspencer3> so by editing, to be clear, I mean "editing without import"
[21:37] <RAOF> Anything that you can *cancel* in there has a sort of poor-man's undo in the fact that you get a large preview and can hit the cancel button.
[21:37] <rickspencer3> which you say is what you have added
[21:38] <rickspencer3> yeah, that's not undo though
[21:38] <rickspencer3> we need to do this classy
[21:38] <pitti> RAOF: does it apply changes in-place, or do you have to save?
[21:38]  * pitti assumes the latter
[21:38] <RAOF> pitti: Oh, no.  It's instant apply, in place.
[21:38] <pitti> but the absence of undo wouldn't be so bad if you could just re-load the original again
[21:38] <pitti> eww
[21:38] <RAOF> Yeah.
[21:38] <rickspencer3> heh
[21:38] <pitti> RAOF: doesn't that kind of suck for large images?
[21:39] <pitti> or, for that matter, reduces the quality further and further with every operation?
[21:39] <RAOF> Yes for the quality.
[21:39] <RAOF> I'll grab some large images to test on; given that it's destructive editing, I've been using some fairly small throwaways.
[21:40] <rickspencer3> RAOF, ok
[21:40] <rickspencer3> form the users perspective we need
[21:40] <rickspencer3> the ability to do edit edit undo
[21:40]  * pitti goes into a dark corner, weeps a bit, and comes back
[21:40] <rickspencer3> and cancel without saving
[21:41] <RAOF> rickspencer3: Given edit, edit, undo, how many edits should undo revert?  Just the last one?
[21:41] <rickspencer3> no
[21:41] <rickspencer3> like 20
[21:41] <rickspencer3> at least
[21:41] <RAOF> So you can hit undo 20 times and undo the last 20 edits?
[21:42] <rickspencer3> yes
[21:42]  * RAOF *will* need some large images to test for non-suckyness.
[21:42] <rickspencer3> like a normal app
[21:42] <RAOF> Ok.
[21:42] <kenvandine> hehe
[21:42] <kenvandine> normal :)
[21:42] <rickspencer3> ok, like a "good" app then
[21:42] <rickspencer3> RAOF, is this even feasible?
[21:43] <RAOF> I think it is, yes.
[21:44] <rickspencer3> RAOF, would it be easier to patch eog?
[21:44] <RAOF> All the editors return edited copies of the image; if all else fails we can just keep a stack of old copies.
[21:44] <RAOF> I'm unfamiliar with the eog codebase, and what we'd need to patch into eog.
[21:44] <rickspencer3> desrt suggested this may be a workable approach
[21:44] <pitti> RAOF: would it be possible to only keep them in memory and introduce a "save" button? or would that turn the entire code upside down?
[21:44] <rickspencer3> ok
[21:45] <RAOF> pitti: I'm pretty sure it'll be quite easy to introduce a save button.
[21:45] <rickspencer3> RAOF, and that would come with an undo stack?
[21:46] <RAOF> Actually, it could well.
[21:46] <rickspencer3> by like storing copies of the image in tmp or something?
[21:46] <RAOF> Right, or even in-memory.
[21:47] <RAOF> Because the code gets notified in a nice central place of changes to the image; for the main library view, that delegates writing out to the main DB class, for the view mode it writes straight to file.
[21:47] <RAOF> Delegating handling the changes out to a save/undo button widget would be quite clean, I think.
[21:47] <rickspencer3> RAOF, you sound confident that you can solve this is in a sane manner
[21:47] <RAOF> And doable.
[21:47] <RAOF> I *think* so :)
[21:48] <rickspencer3> this seems like a good opportunity to get a bit into our work item tracking as well
[21:48] <rickspencer3> perhaps pitti would be willing to work with you to define some work items so we can track them with our burndown chart?
[21:48] <RAOF> Ok.  I've seen pitti's burndown page, but don't really know where the data is pulled from.
[21:49] <pitti> RAOF: that's the one mini-session I'd like to have with you (and possibly with chrisccoulson as well)
[21:49] <RAOF> :)
[21:49] <pitti> we can do it right now if you want; chrisccoulson, would you be up for a mini-session about work items? (some 10 minutes)
[21:50] <pitti> s/right now/after the f-spot discussion/
[21:50] <rickspencer3> ok
[21:50] <chrisccoulson> pitti - i could probably do it on IRC (i've got baby at the moment)
[21:50]  * rickspencer3 feels better about f-spot
[21:51] <pitti> chrisccoulson: oh, please do care about your baby first then
[21:51] <pitti> chrisccoulson: yes, IRC
[21:51] <chrisccoulson> pitti - should be fine
[21:52] <pitti> chrisccoulson, RAOF: perhaps I can ask you about reading https://wiki.ubuntu.com/WorkItemsHowto first? and then we can discuss some details, on the example of f-spot
[21:56] <kenvandine> james_w, what causes this error?
[21:56] <kenvandine> bzr: ERROR: Unable to find the tag for the previous upstream version, 0.1.2, in the branch: upstream-0.1.2
[21:56] <kenvandine> there is a branch for 0.1.2
[21:56] <kenvandine> s/branch/tag
[21:56] <asac> 22:54 < ogra> thats not supposed to be on the images though
[21:56] <asac> 22:54 < asac> thats language-support-writing-*
[21:56] <asac> 22:54 < ogra> its a bug in the design of langpack interaction with oo.o ... but apparetnly not easily fixable
[21:56] <asac> 22:54 < ogra> right, writing aleays pulls in hyphenation or thesaurus
[21:56] <asac> topic: openoffice getting pulled in when adding language
[21:56] <asac> ArneGoetje: ^^
[21:56] <asac> is that fixable?
[21:58] <RAOF> pitti: Ok.  That seems understandable.
[21:58] <ccheney> asac: hmm
[21:58] <kenvandine> anyone else know what causes that error with bzr merge-upstream?
[21:58] <didrocks> kenvandine: do you have a tag named "upstream-0.1.2"
[21:58] <didrocks> ? :)
[21:58] <kenvandine> no
[21:58] <pitti> chrisccoulson: please read it tomorrow, adn tend to your family; good night!
[21:58] <asac> ccheney: know why ooo thesaurus etc. need to be a depend?
[21:58] <kenvandine> didrocks, i think it creates a branch with that name
[21:58] <kenvandine> and looks for the tag in there
[21:58] <ccheney> asac: which package exactly?
[21:58] <didrocks> kenvandine: so, you need it in the last revision of your packaging branch
[21:58] <kenvandine> there is a tag for 0.1.2
[21:59] <pitti> RAOF: ok, great; so, we could set up a new blueprint for that, or just extend the one that already has the f-spot work item
[21:59] <asac> ccheney: for example language-support-writing-de
[21:59] <didrocks> kenvandine: this tag has to be in the packaging branch
[21:59] <kenvandine> didrocks, it's there
[21:59] <pitti> RAOF: let's do the latter for simplicity
[21:59] <ccheney> asac: no i mean which OOo package
[21:59] <asac> ccheney: pulls in ooo -thesaurus etc.
[21:59] <didrocks> kenvandine: upstream-0.1.2 ?
[21:59] <kenvandine> humm
[21:59] <didrocks> kenvandine: can you show me the branches?
[21:59] <kenvandine> no...
[21:59] <asac> ccheney: openoffice.org-thesaurus-de, openoffice.org-thesaurus-de-ch, openoffice.org-hyphenation, openoffice.org-hyphenation-de
[21:59] <kenvandine> didrocks, lp:ubuntu/ido
[21:59] <pitti> RAOF: so let's add them to https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-default-apps
[21:59] <ccheney> asac: i was told those language-support-* packages were going away entirely and that i should drop the | depends on them
[21:59] <ccheney> asac: if that isn't true then that is why there is a bug now
[21:59] <kenvandine> those tags all get created automatically
[21:59] <pitti> RAOF: they should be added to the ubuntu-10.04-beta-1 section
[22:00] <didrocks> kenvandine: not the first :)
[22:00] <pitti> RAOF: do you want to do this yourself, to get the hang of it?
[22:00] <RAOF> Yeah.
[22:00] <didrocks> kenvandine: or if someone just used bzr merge
[22:00] <kenvandine> didrocks, previous uploads worked
[22:00] <ccheney> asac: but for eg openoffice.org-l10n-de i haven't updated OOo yet so it still has a depends | on the language pack
[22:00] <pitti> RAOF: they shuold be "[raof] f-spot provide save button and drop instant saving: TODO" <- in that format
[22:00] <didrocks> kenvandine: the tag isn't there, that means merge-upstream wasn't done or pushed
[22:01] <kenvandine> ok, adding that tag fixed it
[22:01] <pitti> RAOF: then they'll appear on http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html an hour later
[22:01] <ccheney> asac: for openoffice.org-dictionaries i already updated it for the supposed deprecation of language-*
[22:01] <didrocks> kenvandine: it was a normal merge
[22:01] <pitti> RAOF: you can keep http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html#raof open in a tab to have a reminder :)
[22:01] <didrocks> kenvandine: so, yeah, just add the tag and you're all set :)
[22:01] <kenvandine> oh... no
[22:01] <asac> ccheney: so what needs to be done to fix this? ;)
[22:01] <kenvandine> that's no good
[22:01] <pitti> RAOF: (you don't have any WIs right now, thus the link won't work yet; but it will once you get WIs)
[22:01] <kenvandine> it removed the debian dir :)
[22:01] <ccheney> asac: i assume for language-* to go away if it is supposed to
[22:02] <didrocks> kenvandine: right, that's because of the previous merge :/
[22:02] <ccheney> pitti: any ideas about the issue asac is seeing?
[22:02] <asac> ccheney: and if -writing- stays?
[22:02] <didrocks> kenvandine: so, bzr revert debian/
[22:02] <didrocks> (update debian/changelog manually for this time)
[22:02] <didrocks> and commit
[22:02] <didrocks> check that the upstream-… tag is there too
[22:02] <pitti> ccheney, asac: sorry, what's the problem?
[22:02] <ccheney> asac: well if language-* isn't really going away although being told it was then openoffice.org-dictionaries needs to add it back, but i need clarification as to what to do... already been told to remove it once
[22:03] <pitti> we recently had a bug that language-support-* for non-English languages got seeded
[22:03] <pitti> which caused OO.o to be pulled in
[22:03] <asac> pitti: was told that installing language pulls in openoffice ... seems language-support-writing- depends on ooo-thesaurus etc.
[22:03] <asac> pitti: hmm. so seeding is fixd and maybe the language-selector still installs it?
[22:04] <pitti> asac: yes, but they have alternative dependencies to language-support-writing-en
[22:04] <pitti> asac: l-s does that at runtime, not in the CD
[22:04] <kenvandine> didrocks, thx
[22:04] <ccheney> pitti: erm iirc you to told me to remove those when the next i needed to do an upload anyway, which i eventually did for openoffice.org-dictionaries source
[22:04] <ccheney> pitti: which is why it appears to now be pulling in OOo
[22:04] <pitti> ccheney: I though that all but l-s-en was obsolete indeed
[22:05] <pitti> ArneGoetje: so which of the language-support-* are still relevant then?
[22:05] <ccheney> if it is obsolete we need to remove them from the archive, right? :)
[22:05] <pitti> right
[22:05] <asac> ok if thats transitional i am happy ... lets wait for ArneGoetje to confirm the status and whats the idea
[22:05]  * ccheney hopes he did not come off as accusatory, just wanting to make sure i was not missing something important :)
[22:05] <pitti> coudl also be that I mixed it up and only language-support-translations-* was obsolete
[22:06] <didrocks> kenvandine: you're welcome
[22:06] <pitti> ccheney: right, I think I mixed it up somehow
[22:06] <ccheney> pitti: ping me when it is clarified, updating openoffice.org-dictionaries is trivial and doesn't take much build time
[22:06] <asac> yeah ... all fine. waiting a bit longer before filing a bug or something
[22:06] <pitti> ccheney: ah, I think only language-support-translations-* got killed, not _all_ language-support-*
[22:07] <ccheney> pitti: ok
[22:07] <pitti> ccheney: so, I think we need to add the | language-support-writing-$LANG back
[22:07] <ccheney> oh ok
[22:07] <pitti> ccheney: let's wait for ArneGoetje to confirm, but I think that's it
[22:07] <pitti> but I still don't see _what_ pulls in OO.o
[22:08] <pitti> Recommends: openoffice.org (>= 1.0.3) | openoffice.org-writer | language-support-writing-en
[22:08] <pitti> all packages I'm looking at have this
[22:08] <pitti> I think I discussed with ogra some days ago
[22:08] <pitti> and germinate didn't tell us eitehr
[22:08] <pitti> you really need to boot a livefs and try to purge openoffice, and see what holds it bin
[22:08] <pitti> s/bin/in/
[22:08] <pitti> asac: ^
[22:08] <ccheney> pitti: something like openoffice.org-thesaurus-hu would
[22:09] <pitti> ccheney: it could only be -en
[22:09] <ccheney> pitti: oh ok
[22:09] <pitti> we don't seed any other language-support-*
[22:10] <pitti> ccheney, asac: but again, what _is_ the problem? current armel netbook images don't have OO.o
[22:10] <pitti> the reason for that was seeding language-support-de and friends, which got fixed
[22:11] <ccheney> yea i don't see what could be causing it either
[22:11] <pitti> well, what is "it"?
[22:11] <ccheney> pulling in of OOo via language-support-en
[22:11] <pitti> I think ogra's problem a few days ago was that the full oo.o was on the armel netbook images
[22:11] <pitti> but that was fixed
[22:11] <ccheney> pitti: i meant from what you said, yea i don't see an issue there
[22:12]  * ccheney doesn't know the details of the current issue other than OOo is somehow pulled in according to asac :)
[22:12] <pitti> yes, and I'm curious where
[22:12] <ccheney> i haven't uploaded anything relating to OOo in a few weeks
[22:12] <pitti> certainly not into http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-live/20100303/
[22:13] <ccheney> 15:57 < asac> topic: openoffice getting pulled in when adding language
[22:13] <ccheney> asac: so this isn't an issue with the cd but when you are adding a language via the selector?
[22:13] <pitti> ah
[22:13] <pitti> yes, that'd make sense
[22:14] <ccheney> if so then the issue probably is when someone installs a language it pulls in the thesaurus package like hu which has a direct dependency now, needs to be fixed apparently as pitti mentioned
[22:14] <pitti> ccheney: right, those would need alternative language-support-writing-$LANG deps then
[22:14] <ccheney> yea just need to restore the old control file probably :)
[22:14]  * ccheney bbiab 10m
[22:14] <pitti> ccheney: hyphenation looks ok to me
[22:15] <pitti> ccheney: so does thesaurus
[22:15] <pitti> ccheney: ok, seems you know which package is affected then; sorry for the misguiding about dropping the deps then
[22:15] <TheMuso> Good morning.
[22:15] <pitti> hey TheMuso!
[22:17] <didrocks> I guess it's more than time to go to bed for some relaxing :)
[22:17] <didrocks> good morning TheMuso
[22:19] <asac> ccheney: pitti: thats what is was told yes (on install, not by default)
[22:19] <tedg> Heh chrisccoulson, how's bug 531493?  I'm just checking to make sure it makes string freeze :)
[22:19] <pitti> asac: ok, thanks for confirming; so I guess it's the missing alternative deps then
[22:19] <asac> ccheney: do you want a bug?
[22:20] <asac> ccheney: against what package?
[22:20] <chrisccoulson> tedg - seb128 is working on a gdm upload, which will have the change in (it's already in bzr)
[22:21] <tedg> chrisccoulson: Cool, thanks!
[22:21] <asac> chrisccoulson: thanks for confirming the event ;)
[22:21] <pitti> RAOF: oh, please add the other bits as well (like f-spot: provide undo); was there something else?
[22:21] <chrisccoulson> hey asac, how are you?
[22:22] <davidbarth> chrisccoulson: ping; hey seb128 mentioned you may know about upcoming patches for liboos
[22:22] <davidbarth> liboobs that is
[22:22] <chrisccoulson> upcoming patches? what for?
[22:22] <pitti> kenvandine, RAOF: I moved the other f-spot work item from kenvandine to RAOF; RAOF, do you have kenvandine's work?
[22:23] <davidbarth> chrisccoulson: to get oobs_self_config_get_user to work; always returns null here
[22:23] <chrisccoulson> oh, i didn't know about that. milanbv would know about that though
[22:23] <kenvandine> pitti, he does
[22:23]  * kenvandine hugs RAOF
[22:24] <pitti> great, thanks
[22:24] <seb128> davidbarth, chrisccoulson: I didn't say chrisccoulson would know about that specific issue, I said to maybe ask him
[22:24] <seb128> he's the one who did the most work on g-s-t there recently
[22:24]  * RAOF is always happy to participate in hugs ;)
[22:24]  * pitti hugs RAOF
[22:24]  * seb128 hugs RAOF
[22:24]  * desrt doesn't know what's going on but hugs RAOF anyway
[22:25] <kenvandine> :)
[22:25]  * chrisccoulson hugs seb128, RAOF, kenvandine and pitti
[22:25]  * RAOF hugs pitti, kenvandine & seb128 using the extra arm he's had installed for precisely this purpose.
[22:25] <pitti> RAOF: yay, your first WI! http://people.canonical.com/~pitti/workitems/canonical-desktop-team-ubuntu-10.04-beta-1.html#raof
[22:25] <pitti> RAOF: o_O
[22:25]  * didrocks hugs everyones and waves goodbye for true this time :)
[22:26]  * pitti follows didrocks's wise decision and gets to bed as well; I'm falling off my chairt
[22:26] <RAOF> pitti: Well, it was either that or to improve my ski-boxing ;)
[22:26] <pitti> lol
[22:27] <pitti> RAOF: I added "undo" as well; please feel free to add others that I forgot
[22:27]  * pitti waves goodnight
[22:27] <davidbarth> seb128, chrisccoulson: ok thanks
[22:28] <RAOF> pitti: Good night!
[22:28] <kenvandine> good night pitti
[22:29] <seb128> 'night pitti
[22:29] <chrisccoulson> davidbarth - OOI, what are you using liboobs for?
[22:30] <davidbarth> chrisccoulson: a patch for about-me, to let the user update its realname from there
[22:31] <chrisccoulson> ah, ok
[22:33] <ccheney> asac: yea file a bug against openoffice.org-dictionaries to add the language-suppport-writing-* back and milestone it for the next one
[22:33] <ccheney> asac: i'll try to get to it in the next few days, but will make sure it is done by the milestone in any case :)
[22:34] <chrisccoulson> davidbarth, i can perhaps look at liboobs tomorrow if it can wait that long
[22:38] <davidbarth> chrisccoulson: don't worry, i've taken the -dbg package and i'm tracing through it atm; worst case, i'll make a patch ;)
[22:46] <asac> ccheney: bug 532262
[22:46] <ccheney> asac: ok