[00:11] <calc> jono: may be related to the cairo library change
[00:11] <jono> calc, are you aware of the bug?
[00:12] <calc> jono: if you don't have your system set to subpixel hinting does it look properly?
[00:12] <calc> jono: i am aware of a bug with hinting with subpixel yes, cairo made a backwards incompatible change that has made OOo look a bit odd when font hinting is set to subpixel
[00:13] <calc> jono: i'm not certain if it is the same bug you are seeing though
[00:14] <jono> calc, yeah it looks better when I am not using subpixel smoothing
[00:14] <jono> calc, is there a fix for this?
[00:14] <calc> fonts look fine (i think) to me with subpixel full hinting, so i am not sure which subpixel mode is messed up with the new cairo
[00:14] <calc> jono: not that i know of :(
[00:14] <jono> oh that sucks
[00:15] <calc> i think i asked about a fix for this before, but i will email the developer list again to see if anyone has fixed it independently (eg in suse private branch or fedora)
[00:15] <jono> cool :)
[00:15] <calc> sometimes fixes are hidden unintentionally, heh
[00:16] <jono> haha
[00:16] <jono> indeed :)
[00:16] <jono> calc, does this build have the funky new anti aliasing in it, or is that 3.1?
[00:17] <calc> new anti aliasing? i'm not sure i know what you are talking about :)
[00:17] <calc> the builds for a while now (i think intrepid too) have had cairo support for anti aliasing which was broken with cairo 1.7.5 (iirc)
[00:17] <jono> calc, shapes in OOo are going to be anti aliased
[00:18] <calc> ah ok, probably in 3.1 if you read about recently, 3.1 is due out at the end of march if it makes it on time
[00:18] <jono> I think it wasnt turned on by default
[00:18] <jono> cool
[00:18] <calc> 3.1 won't be in official ubuntu until 9.10 but i should have some ppa debs shortly after release
[00:19] <calc> so it looks like i never asked on the developer list and just filed a bug about the cairo incompat issue, so perhaps emailing the developer list will help spur someone who knows more about it get it fixed quickly
[00:22] <jono> calc, cool :)
[00:23] <calc> jono: thanks for reminding me about this bug i think i know which patch adds support for it, so i can more easily search for if there are updates :)
[00:23]  * jono high fives calc :)
[00:25] <calc> the patch i found that took from redhat originally for this to work at all apparently was integrated with OOo 3.0, so not sure what is going on
[00:25] <calc> but i know who to ask :)
[00:27] <calc> and the patch was later removed, hmm, ok emailing list
[00:27] <calc> the patch in ooo-build that is
[00:30] <calc> jono: maybe we will get lucky and have a fix for it for alpha 6 :)
[00:31] <jono> calc, that would be kick ass :)
[00:31] <calc> jono: caolan the redhat OOo guy seems to know quite a bit about gnome programming so may be able to fix it if he doesn't already have a patch for it
[00:31] <jono> :)
[00:33] <calc> jono: did you get my email a while back about fodt?
[00:33] <jono> odt?
[00:33] <jono> fodt?
[00:33] <calc> fodt == flat odt (one big uncompressed odt file)
[00:34] <jono> hmmm I don't think so
[00:34] <calc> ah ok
[00:34] <calc> well fodt might be useful for you for revision control since its just a single large uncompressed xml file
[00:35] <calc> a patch went in about a month ago that fixed the formatting of the file to have line breaks which made it actually usable in rcs situations :)
[00:35] <jono> oh nice :)
[00:36] <calc> jono: if you run into any problems with it be sure to file bugs :) its a feature added by novell so we can probably get fixes fairly quickly
[00:37] <jono> sounds great
[00:37] <jono> thanks dude :)
[00:37] <calc> np :)
[01:00] <maxb> Where is the best channel to ask for help debugging DBus?
[01:01] <calc> maxb: probably either here or a channel on irc.gnome.org
[01:01] <calc> maxb: http://live.gnome.org/GnomeIrcChannels
[01:09] <andreasn> maxb, try #gnome-hackers on irc.gnome.org
[01:10] <maxb> thanks
[01:47] <calc> is the evolution indicator supposed to pop up its window plus the regular top right black indicator?
[01:48]  * calc thinks there is a bug somewhere
[01:49] <andreasn> MacSlow, ping
[01:50] <MacSlow> andreasn, pong
[01:50] <MacSlow> andreasn, dude ... should you not be sleeping at this late hour
[01:50] <andreasn> saw https://wiki.ubuntu.com/NotificationDevelopmentGuidelines
[01:50] <andreasn> ... and are located under /usr/share/icons/Human/scalable/status. Until symlinks or updated icons for other icon-themes are installed using these without the icon-theme being set to Human will fail to display the intended icon. You can still of course use full file paths to .svg/.png/.jpg icons. The afore listed sourcecode-examples show the use of icons.
[01:50] <MacSlow> andreasn, yeah ... I'm still writing content for that
[01:51] <andreasn> shouldn't it be saner to install it into notification things private hicolor?
[01:51] <MacSlow> andreasn, I assume kwwii contacted you regarding this
[01:51] <andreasn> we spoke a bit about it on irc earlier today
[01:51] <andreasn> but he was about to fly away
[01:52] <MacSlow> andreasn, I have no real opinion on that topic... I trust you art/Tango folks to know the best solution for this
[01:52] <andreasn> it's what apps usually do with the icons they install
[01:52] <andreasn> http://live.gnome.org/ThemableAppSpecificIcons/
[01:52] <andreasn> rhytmbox, power-manager, evince, evolution etc,
[01:53] <andreasn> and since hicolor is the lowest common detonator, it will work across whatever icon theme you select
[01:53] <andreasn> including HighContrast n stuff
[01:53] <MacSlow> andreasn, ehm... *tilt*
[01:54] <MacSlow> I'm not the one doing the packaging anyway, so :)
[01:55] <MacSlow> andreasn, I'm doing Python and C# atm ... I'm a bit "bleeding" ;)
[01:55] <andreasn> who does?
[01:55] <MacSlow> I'll raise the issue with kwwii tomorrow
[01:55] <MacSlow> kwwii does it afaik
[01:55] <andreasn> oh, I think he already knows that then
[01:55] <andreasn> as lapo and dobey also bugged him about it on irc :)
[01:55] <andreasn> that's all we do you know :)
[01:56] <MacSlow> :)
[01:56] <andreasn> how have the feedback been so far?
[01:57] <andreasn> from The Internet
[01:57] <MacSlow> mostly positive
[01:57] <MacSlow> negative feedback was mostly due to people not reading anything (or not the full monty)
[01:57] <andreasn> haha
[01:58] <MacSlow> everybody had no clue that sofar every app was using libnotify not according to the spec
[01:58] <MacSlow> not really testing for supported caps of the daemon
[01:58] <MacSlow> people were very fast with pointing fingers at us :)
[05:55] <Hammerhead> Hi all,
[05:55] <Hammerhead>  having an issue installing desktop on a machine with a RAID controller in it.
[05:56] <Hammerhead> error #5 at 52% of install
[05:56] <Hammerhead> 3ware 8600
[05:57] <Hammerhead> Ubuntu see's all the partitions starts the copying process then stops at 52%
[05:57] <Hammerhead> any help would be greatly appreciated.
[05:57] <Hammerhead> I have googled and read the fourms
[05:58] <Hammerhead> i tried the few hints that were out there.......running the install command as root...etc
[05:58] <Hammerhead> to no avail
[07:20] <pitti> Good morning
[07:57] <didrocks> morning pitti o/
[07:58] <pitti> bonjour didrocks, comment vas-tu?
[08:00] <didrocks> pitti: gut
[08:00] <didrocks> pitti: sorry, my German is very poor
[08:01] <didrocks> I always tells this to dholbach. 6 years of German for... nothing :/
[08:01] <didrocks> pitti: and you, how do you do? ;)
[08:02] <pitti> didrocks: "gut" was correct :)
[08:02] <pitti> didrocks: mir geht es gut, danke!
[08:03] <didrocks> pitti: es ist schwierig, mit einem Wort zu täuschen :)
[08:03] <pitti> hehe
[08:34] <didrocks> hey seb128 :)
[08:34] <seb128> hello didrocks
[08:35] <didrocks> seb128: nautilus-sendto is ready (bug #334067). Even if I didn't understand the "Add an evolution plugin to allow sending arbitrary attachments through nautilus-sendto". I see a new entry in evolution plugins configuration, but nothing evident appears
[08:35] <didrocks> seb128: and don't forget gnome-python (bug #327933) when you will have time
[08:35] <seb128> didrocks: right
[08:37] <didrocks> seb128: FYI, I created a new bzr branch for nautilus-sendto, as there was only the init commit in the previous one almost 2 years ago. You can push it to the same location with --overwrite
[08:37] <didrocks> mvo__: thanks for the upload :)
[08:37] <seb128> didrocks: ok
[08:37] <mvo__> cheers didrocks
[08:40] <seb128> hello slomo_, thanks for the glib changes
[08:40] <seb128> slomo_: did you read my gstreamer question yesterday?
[08:41] <slomo_> seb128: yes, i'll do that in the next days
[08:41] <seb128> slomo_: thanks
[08:42] <seb128> didrocks: no sponsoring today due to the freeze which is in effect
[08:43] <didrocks> seb128: as mvo__ sponsored libgtop yesterday, I thought that you can dput the .changes and as we are in Freeze for next alpha, it will just be queued for building until the alpha is realeased
[08:44] <didrocks> released*
[08:44] <seb128> didrocks: no, that's a soft freeze for alphas, uploads are not blocked we just need to be civilized
[08:44] <seb128> didrocks: yesterday was fine for uploads but better to not do changes today while they try to build cds
[08:44] <didrocks> seb128: of course. I thought it was more automatized, but civic rules are right too :)
[08:45] <didrocks> s/right/good
[08:47] <seb128> didrocks: not sure why you would consider blocking uploads as a better technical solution, that would add extra work for people reviewing those items and mean you couldn't get universe fixes, etc in while the CD are being built
[08:49] <didrocks> seb128: I didn't say it was good, civic bahvior is always better. I just thought that because libgtop has been built (https://edge.launchpad.net/ubuntu/+builds?build_text=libgtop&build_state=built) but is no published yet: https://edge.launchpad.net/ubuntu/+source/libgtop
[08:49] <didrocks> (and so, the associated bug is not closed)
[08:50] <seb128> didrocks: you want to look to libgtop2 source?
[08:51] <didrocks> seb128: Not really, I was just wondering why the bug was not closed and so, checked if it was built and published
[08:52] <seb128> didrocks: did you open it on the correct source?
[08:52] <seb128> ie libgtop against libgtop2 component in launchpad
[08:52] <didrocks> hum, you're right, I opened it against libgtop :/
[08:52] <didrocks> sorry...
[08:53] <didrocks> Ok, I reattribute it and push it manually fixed released
[08:53] <didrocks> ok, no black magic though... my bad :/
[09:00] <crevette> hello gents
[09:01] <didrocks> lut crevette
[09:01] <crevette> hey didrocks
[09:02] <seb128> lut crevette
[09:03] <crevette> good morning seb128
[09:39] <davmor2> Guys quick query I got the new gdm theme but I've not got the new backdrop that popey displayed yesterday should it be in on the alpha 5 release candidates or not?
[09:43] <pitti> davmor2: gdm backdrop?
[09:44] <davmor2> pitti: 2 ticks
[09:44] <pitti> davmor2: I'm not aware of anything pending which needs to land, so in theory it should be all in
[09:46] <pitti> davmor2: "2 ticks"?
[09:47] <davmor2> pitti: I have this http://popey.com/~alan/screenshot.png but not this http://popey.com/~alan/background.png
[09:48] <pitti> davmor2: oh, you mean the background should be for the GNOME session, not gdm itself?
[09:48] <davmor2> pitti: I still got intrepids background
[09:48] <pitti> since gdm itself does have that picture
[09:48] <pitti> right
[09:48] <pitti> that's still on the TODO list
[09:49]  * pitti asks kwwii
[09:49] <davmor2> pitti: Okay cool I just wondered as login theme was in but the desktop background wasn't :)
[10:13] <pitti> mvo, seb128: do you think that https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/331564/comments/5 (the FAQ) has sufficient information to do the change, or do we need more info from Mirco?
[10:14] <seb128> pitti: would be a question for mvo_
[10:14] <seb128> I think they discussed it with MacSlow a week ago or so
[10:16] <mvo_> which one?
[10:20] <pitti> mvo_: the compiz default settings changes for notifications, see above bug comment
[10:20] <seb128> mvo_: <pitti> mvo, seb128: do you think that https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/331564/comments/5 (the FAQ) has sufficient information to do the change, or do we need more info from Mirco?
[10:23] <mvo_> interessting, I have not seen this one since hte compiz update, let me try with a new iuser
[10:24] <pitti> neither have I, but David says it's still an issue we need to fix
[10:28] <mvo_> hm, the faq entry looks a bit odd, I will talk to macslow when he is back
[10:28] <pitti> mvo_: ok, thanks
[10:49] <Ng> are notify-osd bubbles supposed to appear over the top panel, or below it?
[10:56] <seb128> Ng: below
[10:56] <seb128> Ng: bug #332094
[10:57] <Ng> seb128: ta
[10:57] <seb128> you're welcome
[11:57] <sabdfl> hey desktop lovers
[11:58] <seb128> hello sabdfl
[11:58] <sabdfl> thanks for joining the call last night seb
[11:59] <seb128> np, I was interested in the discussion and I think that was productive ;-)
[12:14] <geser> is there a way to configure the look of the new notifications? It's easy to miss dark notifications on a dark desktop or on top of an maximized terminal
[12:21] <seb128> MacSlow: can you reply to geser's question?
[12:22] <MacSlow> geser, no you can
[12:22] <MacSlow> geser, they are not themable (color-wise)
[12:23] <MacSlow> geser, well you can always patch it yourself... but it's not meant to be at runtime
[12:24] <geser> MacSlow: is it worth to open a wishlist bug for it?
[12:24] <MacSlow> geser, sure
[12:49] <mvo__> MacSlow: hi, do you know more about https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/331564 ?
[13:16] <MacSlow> mvo__, no ... atm I don't ... and David did a confusion answer related to that stating metacity (although he very likely meant compiz ... metacity does not have any plugins one could configure)
[13:34] <mvo__> MacSlow: yeah, I was confused by this as well :)
[13:45] <MacSlow> mvo__, atm I can't chase those as I'm far behind with the implementation for UIF
[13:47] <mvo__> uif?
[13:57] <seb128> mvo: user interface freeze
[13:57] <mvo> aha
[13:57] <mvo> thanks seb128
[13:58] <seb128> you're welcome
[14:19] <hggdh> seb128, ping
[14:19] <seb128> hggdh: hi
[14:20] <hggdh> hi, seb128. Can you please have a look at the package I proposed for libpst? dholbach has looked at it, and asked for you to give it a spin.
[14:20] <hggdh> seb128, https://bugs.launchpad.net/ubuntu/+source/libpst/+bug/317602
[14:20] <seb128> hggdh: asked where and when?
[14:21] <hggdh> seb128, this morning. I have added in the changes he proposed, but would like to know if you have more
[14:21] <seb128> hggdh: do you have an updated version with the changes?
[14:21] <seb128> hggdh: he didn't subscribe me to the bug so good that you ping on IRC ;-)
[14:21] <hggdh> seb128, no, not yet. You want me to submit it, then you would look?
[14:22] <seb128> yes
[14:22] <hggdh> OK, will do
[14:23] <seb128> thanks
[14:23] <seb128> sorry it's taking a while for the review rounds, etc, everybody is busy
[14:23] <seb128> same for evolution-mapi I'm wondering what's going on there
[14:23] <seb128> james_w: hey ;-)
[14:24] <seb128> james_w: somebody told me you were reviewing this one do you know what's going on?
[14:24] <hggdh> I think we still have some problems on e-mapi...
[14:24] <james_w> seb128: evolution-mapi?
[14:24] <seb128> james_w: yes
[14:25] <james_w> http://revu.ubuntuwire.org/p/evolution-mapi
[14:25] <james_w> package isn't too bad, but needs updating
[14:25] <seb128> oh you guys are still using review for comments
[14:26] <seb128> hum
[14:26] <seb128> is there any motu who could work on getting this package uploaded?
[14:26] <seb128> I was trying to avoid adding that to my todolist, too  much to do already
[14:27] <seb128> but we need that in jaunty and we are past feature freeze, things are not moving quickly
[14:35] <hggdh> seb128, latest libpst is published on https://launchpad.net/~hggdh2/+archive/ppa
[14:36] <seb128> hggdh: oh you have an ical fix there?
[14:37] <seb128> hggdh: e-d-s ical fix I mean rather
[14:37] <seb128> hggdh: does it fix bug #334347 or bug #331428 ?
[14:39] <hggdh> seb128, let me see
[14:42]  * kenvandine[work] is wondering why installing skype has completely broken sound
[14:45]  * kenvandine[work] reboots
[14:49] <seb128> hggdh: not sure why you have makefiles in the debian directory?
[14:54] <seb128> hggdh: otherwise looks good to me
[14:54] <hggdh> seb128, neither am I... I probably did not notice it when I cleaned up the upstream Makefile.am
[14:54] <hggdh> seb128, I will look at it
[14:55] <seb128> the rules seems a bit complicated
[14:55] <seb128> why do you run autotools at build time?
[14:56] <hggdh> because upstream did a basic (and wrong) debianisation, and Makefile.am was creating a lot of cruft for debian
[14:56] <hggdh> so I had to delete the original ./debian (and add in a get-orig-source), and patch Makefile.am/configure.in
[14:57] <seb128> hum
[14:57] <seb128> can you get upstream to fix that? ;-)
[14:57] <hggdh> believe me, this was *not* a package for a first-time packager :-(
[14:58] <hggdh> I contacted them, and got a response like "well, we expect you to adjust it as needed". I was thinking of proposing back to them the finished debdiff
[14:59] <kenvandine[work]> pitti: is your hal bug the reason why i have not audio devices suddenly?
[14:59] <kenvandine[work]> s/not/no
[14:59] <pitti> kenvandine[work]: yes (and sluggish graphics, and no camera/scanner access, etc.)
[14:59] <kenvandine[work]> hahaha
[14:59] <kenvandine[work]> ok
[15:00] <pitti> well, in my defence, I didn't break it :)
[15:00] <kenvandine[work]> i was blaming skype for screwing up my mixer levels or something
[15:00] <pitti> rickspencer3: is our call now or in an hour?
[15:00] <kenvandine[work]> it like broke right after i installed that proprietary crap :)
[15:01] <rickspencer3> pitti: yes. Still available?
[15:01] <pitti> itz all skype's fault!!!!11!!
[15:01] <pitti> rickspencer3: yes, done with firefighting; I need to hurry up the hal build, then I'm done
[15:01] <kenvandine[work]> :)
[15:01] <rickspencer3> pitti:
[15:01] <rickspencer3> sounds good
[15:02] <pitti> done
[15:03] <seb128> hggdh: right, the package is mostly good now though the autotools run is not optimal, we tend to have a patch to do that and have a simple rules
[15:03] <seb128> hggdh: I will not ask you to redo it though, your way works too
[15:04] <hggdh> seb128, I did not know how to get it done in a complete way, guaranteeing that the resulting package could be built from source
[15:05] <seb128> hggdh: what do you mean?
[15:05] <hggdh> if I changed Makefile.in, this would not survive a autoreconf
[15:07] <hggdh> well, I guess I could change Makefile.in and Makefile.am both. Would this be the patch you are referring to?
[15:07] <pitti> rickspencer3: (I'm ready, btw)
[15:09] <kenvandine[work]> pitti: how long before i see the hal update available?
[15:10] <pitti> kenvandine[work]: https://edge.launchpad.net/ubuntu/+source/hal/0.5.12~rc1+git20090204-0ubuntu3
[15:10] <pitti> kenvandine[work]: I bumped up the build score, but buildds are still fairly clogged; should build within the hour, and be on archive.u.c. in two
[15:10] <kenvandine[work]> ah
[15:11] <kenvandine[work]> ok
[15:29] <asac> mvo: anything to test on compiz startup time yet?
[15:30] <mvo> asac: yes, could you please disable all plugins (in ccsm) but decoration and start compiz and give me the timings on the commandline
[15:30] <asac> mvo: err. i think we need more. a) i have hardy on that system ;)
[15:31] <asac> b) ... i dont know :)
[15:31] <mvo> asac: this is just for a baseline test (to see what overhaead the plugins have)
[15:31] <mvo> ccsm should already be installed
[15:38] <davmor2> Guys out of interest with the fusa and mail/coms envelope will you be switching off the pidgin applet ?
[15:58] <davmor2> By the way you can't read the session type on the new login page
[16:11] <dashua> mvo_: Not sure if this is feasible in Jaunty, but I just submitted a report bug #344426
[16:11] <dashua> bug # 334426
[16:12] <dashua> bug #334426
[16:14] <mvo_> dashua: fast sound *good*
[16:15] <mvo_> dashua: I check it out, did you do some profiling how much it helps the startup speed?
[16:15] <dashua> No, I just notice a difference.
[16:16] <dashua> No tests done, yet.
[16:16] <davmor2> does this team deal with ubuntu-gdm-theme or is it better on #ubuntu-devel
[16:33] <mvo_> dashua: thanks, I plan to do something about the speed, so this is very welcome
[16:33] <dashua> mvo_: Np, works well as far as I can see.  It's enabled by default as long as the dependencies are there.
[16:34] <mvo_> dashua: on head or on 0.8 as well? we only have the later
[16:37] <dashua> mvo_: It's post 0.7.8, on libcompizconfig master now
[16:40] <dashua> Hopefully, they will do a plugins release soon and it will be there.
[16:40] <dashua> Not sure how they're going about it.
[16:42] <mvo_> dashua: aha, cool. thanks for this info. I think I will prepare snapshots in the compiz ppa and check it out
[16:42] <dashua> Maybe grab a snapshot of libcompizconfig, compizconfig-pyhon, and ccsm
[16:42] <dashua> Maybe that'll work
[16:42] <dashua> Ah cool
[16:42] <dashua> python*
[16:47] <dashua> mvo_: Ah, you already snapped extras and main.  I didn't see that.
[16:49] <mvo_> dashua: yeah, the new wall move looks so nice :) and 0.8 should be around the corner
[16:50] <dashua> Yeah, that is awesome.
[16:54] <mvo_> didrocks: I looked at the nautilus-sendto merge but it seems it does not merge into hte ~ubuntu-desktop/nautilus-sendto/ubuntu branch. maybe seb128 knows about it (he pushed the initial version it seems)
[16:55] <didrocks> mvo_: exactly, let me a minute to quote what I told to seb128
[16:56] <didrocks> mvo_: [09:37] <didrocks> seb128: FYI, I created a new bzr branch for nautilus-sendto, as there was only the init commit in the previous one almost 2 years ago. You can push it to the same location with --overwrite
[16:57] <didrocks> from what I understood and experienced, --overwrite just remove all data in the branch history and push new ones
[16:57] <mvo_> didrocks: ok, if seb is fine with that, I will do that :)
[16:58] <didrocks> mvo_: oh, btw, if you find what corresponds to "add evolution plugin...": I only see a new plugin in evolution with a checkbox to activate/deactivate it, but don't find what it is used for :)
[17:16] <sabdfl> hey guys, are you using the tag "notifications" for any bugs related to the new notify-osd work?
[17:24] <mpt> mvo_, do you have time for a call now (or sometime today) about update-manager?
[17:25] <mvo_> mpt: either in ~1h or tomorrow morning, does that work for you?
[17:25] <mvo_> (dinner time now)
[17:25] <rickspencer3> pitti: Riddell: asac: ^^^^^^
[17:26] <Riddell> I'm not, easily enough could start doing so
[17:27] <mpt> mvo_, ok, what time do you start tomorrow morning?
[17:28] <mvo_> mpt: 9:00 my time (so 8:00 yours)
[17:28] <mvo_> mpt: I have nothing scheduled in the morning, so anytime that is good for you works for me
[17:28] <mpt> mvo_, ok, I'll call you 10:00 your time, thanks!
[17:30] <mvo_> mpt: thanks
[17:36] <pitti> rickspencer3, sabdfl: ah, so that's the tag, not dxteam? good, will use it from now
[17:37] <davidbarth> pitti: see the wiki page describing the tags in general
[17:37] <davidbarth> pitti: use notifications in every case, but please keep on using 'dxteam' when u expect us to actually work on the fix
[17:41] <Laney> Does the new update-manager behaviour take dist-upgrading with apt(itude) into account when deciding when to launch?
[17:42] <pitti> davidbarth: hm, shouldn't we use assignments for that? but well, works for me
[17:43] <Laney> also I find the new reboot dialog to be suboptimal - I seem to just stumble upon the dialog when doing other things rather than seeing it during the upgrade process
[17:46] <Laney> maybe this is a side-effect of my using docky though
[17:54] <james_w> is anyone else experiencing notify-osd "hanging" and not showing notifications?
[17:54] <james_w> I feel it might be related to showing dialogs, but I'm not sure
[17:55] <jcastro> mine "hangs" when I do the volume or brightness adjustments too quickly, as if there's a lag
[17:55] <jcastro> and then they eventually catch up
[18:03] <Laney> Hmm
[18:03] <Laney> can someone run "for i in $(seq 1 10); do notify-send $i; done" from a shell
[18:04] <Laney> see if you get them all appear
[18:06] <james_w> I didn't get 3
[18:06] <Laney> If I just do it with seq 1 3 then I don't get 2
[18:18] <Laney> wow, how odd
[18:18] <Laney> the missing notification does appear if I change workspace
[18:20] <kenvandine[work]> yay... i have sound again
[18:23] <pitti> kenvandine[work]: \o/
[18:26] <mvo_> didrocks: so seb128 is fine with --override? (just to confirm before I run it)
[18:28]  * kenvandine[work] is a bit afraid to try skype again ... :)
[18:28] <rickspencer3> asac: ArneGoetje: bryce: calc: kenvandine[work]: pitti: regarding sabdfl's question ...
[18:29] <rickspencer3> heno will send us detailed instructions regarding how to tag the bugs so that when we see them, we can quickly tag them
[18:29] <rickspencer3> (just fyi)
[18:30] <kenvandine[work]> rickspencer3: which question?
[18:30] <rickspencer3> kenvandine[work]:  are we tagging bugs with "notifications" properly
[18:30] <kenvandine[work]> oh...
[18:31] <kenvandine[work]> ok
[18:31] <sabdfl> "notifications" means "this has something to do with the new notifications subsystem"
[18:31] <sabdfl> and "dxteam" means "the dx team will work on fixing it asap!"
[18:31] <rickspencer3> kenvandine[work]: you're probably more dialed into this than the rest of us, but we need to get dialed in
[18:31] <kenvandine[work]> ok
[18:31]  * kenvandine[work] has been looking over those today :)
[18:32] <pitti> rickspencer3: ok, thanks
[18:32]  * pitti -> Taekwondo, cu tomorrow!
[18:32] <kenvandine[work]> later pitti
[18:32] <rickspencer3> pitti: thanks for all your help today!
[18:33] <calc> ah ok :)
[18:34] <calc> that reminds me i need to ask seb128 if evolution is supposed to be popping up a separate notification window now
[18:34] <calc> its been doing that on my system since the new notification system appeared (i think)
[18:35] <kenvandine[work]> calc: yeah... we are working on that
[18:35] <rickspencer3> calc: do the windows have buttons on them? Are they notifications with actions, in other words?
[18:35] <kenvandine[work]> i have a patch
[18:35] <kenvandine[work]> calc: you mean in the notification area, right?
[18:36] <calc> ah its bug 331571 i think
[18:36] <kenvandine[work]> yeah
[18:36] <kenvandine[work]> i think we have agreed on the fix now
[18:36] <calc> rickspencer3: real windows with buttons in the middle of my screen
[18:36] <rickspencer3> see, this is exactly what the tag is for
[18:36] <rickspencer3> just go here: https://edge.launchpad.net/ubuntu/+bugs?field.tag=notifications
[18:36] <kenvandine[work]> calc: oh...
[18:37] <rickspencer3> if it's not on the list, it should be, and you can add it to the list by tagging it
[18:37] <calc> rickspencer3: ok
[18:37] <kenvandine[work]> rickspencer3: i am going to add jaunty-uif tags for bugs that need to be done before UIF
[18:37] <rickspencer3> I think it may actually be this one Bug #328596
[18:38] <rickspencer3> which is on the list
[18:38] <rickspencer3> kenvandine[work]: thanks. if we can be proactive about helping the dx team to manage UIF and UIFEs, that would be, uh, helpful
[18:38] <calc> oh it might be, not completely certain
[18:38] <calc> the window it pops up looks like a regular gtk window with a button telling me that i have new mail
[18:39] <rickspencer3> calc: I'm pretty certain that's the bug
[18:39] <calc> 328596 refers to a bubble though?
[18:39] <calc> this is a full window managed window
[18:39] <calc> if i can get it to happen again i can take a screenshot of it
[18:40] <kenvandine[work]> calc: please do
[18:40] <rickspencer3> calc: notify-osd turns notifications with actions into gtk windows
[18:40] <calc> ah ok
[18:40] <rickspencer3> that's why there shouldn't be an action
[18:40] <kenvandine[work]> i bet that is what it is
[18:40] <kenvandine[work]> not sure why you are seeing that though
[18:40] <rickspencer3> in this way, no program will fail
[18:40] <calc> ok
[18:41] <rickspencer3> kenvandine[work]: was there a plugin or something that calc should enable?
[18:41] <calc> fwiw i'm using metacity but do generally get the other black upper right notifications
[18:41] <kenvandine[work]> rickspencer3: no
[18:41] <rickspencer3> calc: yeah, that means the system is working
[18:41]  * kenvandine[work] looks at something
[18:41] <rickspencer3> calc: does OOo offer any notifications?
[18:42] <calc> rickspencer3: not afaik
[18:42] <rickspencer3> k
[18:43] <kenvandine[work]> calc: ah...
[18:43] <kenvandine[work]> yeah... my patch will fix that
[18:43] <calc> kenvandine[work]: great :)
[18:44] <kenvandine[work]> if you have the mail notification plugin enabled and a few things checked under it... you get this
[18:44] <kenvandine[work]> go to the plugins and look at the options
[18:44] <kenvandine[work]> uncheck the icon stuff
[18:44] <kenvandine[work]> which is what my patch does by default
[18:45] <kenvandine[work]> uncheck "Show icon in notification area"
[18:45] <calc> rickspencer3: we might want to mention helping out with the alsainfo thing on the ubuntu wiki at our next meeting, aiui that is to help with PA/ALSA for karmic (?)
[18:45] <calc> kenvandine[work]: ok
[18:46] <rickspencer3> calc: please add it to the agenda for the next team meeting
[18:46] <calc> rickspencer3: ok
[18:47] <calc> kenvandine[work]: so just turn off the master checkbox and it will work?
[18:47] <calc> kenvandine[work]: the one that has two checkboxes underneath it
[18:47] <kenvandine[work]> yes
[18:47] <calc> ok, thanks
[18:47] <kenvandine[work]> which is exactly what my patch does
[18:48]  * kenvandine[work] is ordering his new laptop... T400 :)
[18:49] <calc> kenvandine[work]: thinkpads are cool :) i got a x200
[18:50] <calc> it was between a x200 and t400 for me, i wish the x300 was cheaper since it would have been perfect
[18:50] <calc> i bought the cheapest hd (160gb) and replaced it with a 500gb 7200rpm drive
[19:09] <kenvandine[work]> tedg: anything meaningful here? http://dpaste.com/1485/
[19:10] <tedg> kenvandine[work]: Is it in the state with no Pidgin after that?
[19:13] <kenvandine[work]> tedg: yes
[19:13] <kenvandine[work]> i have a message... the icon is blinking
[19:13] <kenvandine[work]> but nothing showing in the indicator
[19:14] <tedg> kenvandine[work]: Hmm, okay.  That's definitely a bug in the indicator.  Message is on the bus, but somehow it lost it.
[19:16] <kenvandine[work]> ok, what info can i provide on the bug?
[19:17] <kenvandine[work]> tedg: interesting thing to note... i can send a message to it from my other account/box and it still shows up in the indicator
[19:17] <kenvandine[work]> so it is like one message got dropped or something
[19:18] <tedg> kenvandine[work]: Hmm, could you post the log of both?  I wonder if they got the same ID or something.
[19:18] <tedg> kenvandine[work]: IE the full listen-and-print log.
[19:18] <kenvandine[work]> yeah
[19:19] <kenvandine[work]> tedg: the next line (after sending another message) looks like this
[19:19] <kenvandine[work]> ** (process:4132): DEBUG: Indicator Added:          :1.29 2 message
[19:19] <kenvandine[work]> so 2 messages
[19:19] <kenvandine[work]> went from 0 to 2
[19:20]  * kenvandine[work] adds to  bug
[19:21] <tedg> kenvandine[work]: I'll look at it, but he other thing that'd be useful is the debug messages from teh applet.  If you do "killall indicator-applet && /usr/lib/indicator-applet/indicator-applet" and then click the reload button on the dialog that pops up you can get those in a terminal.
[19:23] <kenvandine[work]> tedg: ok... done
[19:23] <kenvandine[work]> next dropped message i will grab the output and post it in the bug
[19:58] <kenvandine[work]> tedg: ok, happened again and i posted the applet output to the bug
[20:00] <xhaker> asac, pitti need your help regarding firefox-3.0 and language-packs i'm seeing bug #222673 again on jaunty
[20:01] <xhaker> There is a new report that confirms it.. bug #333799 is about jaunty
[20:01] <tedg> kenvandine[work]: Hmm, nothing obvious.  Thank you for all the data.
[20:02] <kenvandine[work]> np
[20:53] <asac> xhaker: please paste your chrome.manifest from /usr/lib/firefox-addons/langpack-pt*/
[20:54] <asac> xhaker: its /usr/lib/firefox-addons/extensions/...
[21:24] <asac> bryce: any clue why xev doesnt see Button* events in gtk apps?
[21:25] <bryce> asac: something lower down is either blocking, consuming, or ignoring them - could be kernel level or hal
[21:25] <asac> bryce: hmm. i see it if i dont use -id
[21:25] <bryce> asac: we've got a troubleshooting page set up for these sorts of issues
[21:25] <bryce> http://wiki.ubuntu.com/Hotkeys/
[21:26] <asac> bryce: err. thats not about hotkeys ;)
[21:26] <asac> Mouse clicks
[21:26] <asac> ;)
[21:26] <asac> so just running xev opens a window and you see Button* events when you click
[21:26] <asac> but i dont see any such even in gtk windows
[21:27] <asac> bryce: actually i want a tool to see all x events for a window
[21:27] <asac> do you know anything better than xev?
[21:28] <bryce> no not offhand
[21:29] <bryce> it's possible to set something up to spy on the communication traffic between the xserver and clients; that would probably do it, but might be more trouble than worth to set up
[21:29] <bryce> google on xscope iirc
[21:32] <asac> hmm
[21:33] <bryce> xmond is another similar tool
[21:34] <asac> bryce: not in the archiv?
[21:39] <bryce> hmm, I thought it was; I used it a few months back but you're right apt-cache search doesn't see it
[21:39] <asac> heh
[21:40] <bryce> xmond -> xmon
[21:40] <bryce> http://packages.ubuntu.com/intrepid/xmon
[21:41] <bryce> hmm, seems missing from jaunty
[21:41] <asac> bryce: not avail in jaunty
[21:41] <bryce>       xmon |    1.5.6-2 | http://se.archive.ubuntu.com hardy/universe Packages
[21:41] <asac> !info xmon
[21:42] <asac> bryce: Deleted in jaunty-release  (Reason: (From Debian) RoQA; orphaned for a long time, superceded,...)
[21:42] <bryce> superseded by ...?
[21:42] <asac> pitti: ^^ do we know more?
[21:43] <bryce> asac: well meantime I bet you can snag the dsc from the above page
[21:43] <asac> yeah lets see
[21:43] <bryce> asac: ah xtrace is another such tool
[21:44] <bryce>     xtrace |   0.10.0-1 | http://se.archive.ubuntu.com jaunty/universe Packages
[21:44] <asac> hmm ... somehow the description seems not to match my search terms ;)
[21:46] <bryce> btw, when I was messing with xmond, I found that the X we have in ubuntu disables remote X stuff that xmond needed, so I had to flip off that option.  possibly that would need done with xtrace too
[21:47] <bryce> I think it's the -nolisten flag iirc
[21:47] <bryce> iirc it can be controlled via your /etc/gdm/gdm.conf
[21:47] <bryce> DisallowTCP=true --> false
[21:50] <asac> bryce: so xtrace frooze my X
[21:50] <bryce> sweet
[21:51] <asac> and terminal had splash screen -> reboot
[21:51] <asac> hard reset
[21:51] <asac> xtrace seems to be a wrapper ... maybe it was just a bad coincident
[21:51] <asac> too bad that one cannot filter the wanted events up-front
[21:52] <asac> ok one more try ;)
[21:53] <bryce> yep, like I mentioned, I found xmond to be a bit of trouble to get set up initially, but with sufficient googling and fiddling I got it working.  I wish I had documented the process...  but xtrace is probably different in subtle ways anyway
[21:54] <asac> too bad ... seems it would need something like -f for strae
[21:54] <asac> strace
[21:55] <asac> but doesnt have it :(
[21:55] <asac> now firefox forks away and events are not captured anymore
[21:55] <asac> let me check xmon ;)
[22:00] <asac> hmm. the ui doesnt really look intuitive ;)
[22:00] <bryce> heh
[22:00] <hggdh> seb128, ping
[22:00] <seb128> hggdh: re
[22:01] <hggdh> seb128, libpst was submitted to revu. Would you mind sponsoring it?
[22:01] <seb128> I don't have a revu account
[22:01] <seb128> I will let motu deal with that
[22:01] <hggdh> k
[22:03] <seb128> hggdh: I will make sure they sponsor it though, thanks for the work ;-)
[22:03] <seb128> I've that and evolution-mapi on things I want motu look at this cycle
[22:04] <seb128> didrocks, Laney: ^
[22:04] <hggdh> seb128, welcome. Glad to be able to help
[22:05] <Laney> seb128: You're waving the FFe wand?
[22:05] <seb128> Laney: right, those are non trivial changes but evolution 2.26 can benefit of them so would be good to have them in jaunty
[22:06] <Laney> hggdh: lintian warnings reported by REVU
[22:06] <hggdh> Laney, I know. I just am not sure what to do there
[22:08] <Laney> hggdh: For the first one you need to write something different for each package's long description describing what they do
[22:08] <Laney> for the second I bet you didn't call it XSBC-Original-Maintainer
[22:08] <Laney> oh you did, weird
[22:09] <hggdh> heh
[22:10] <Laney> I'll do a proper review on friday or the weekend
[22:10] <hggdh> meanwhile I will add the descriptions & resubmit
[22:12]  * seb128 is on an evolution bug triaging and filling sprint today
[22:17] <dobey> shouldn't be hard to file bugs against evo. it has plenty to choose from :)
[22:18] <seb128> dobey: well, there is some thousand of those opened upstream so you have to pick new ones ;-)
[22:19] <dobey> heh
[22:19] <seb128> the good thing is that the #evolution guys are responsive, they do IRC debugging if you are around and fix issues quickly
[22:19] <didrocks> seb128: can I help to sponsor a package? :)
[22:19] <seb128> there is too many bugs but it come with a crasher
[22:19] <didrocks> (not tonight but tomorrow, it will be ok)
[22:20] <seb128> didrocks: right, evolution-mapi (new package which is on revu) and libpst (update, sort of new package they changed upstream etc)
[22:20] <seb128> didrocks: you still have gedit-plugins that you can update and upload too
[22:20] <didrocks> seb128: will have a look at them tomorrow
[22:20] <didrocks> seb128: yeah, it's in my backlog, but tonight, I had to do that: www.ubuntu-fr.org
[22:21] <didrocks> and I'm sure you don't want to know how ubuntu-fr's css are :)
[22:21] <seb128> k
[22:21] <seb128> didrocks: no I don't ;-)
[22:21] <didrocks> :-)
[22:21] <didrocks> it's better for you health, you know ^^
[22:21] <didrocks> your*
[22:22] <seb128> right
[22:22] <seb128> brb
[22:46] <xhaker> asac: here you go http://paste.ubuntu.com/123052/
[22:47] <xhaker> asac: this is probably useful too http://paste.ubuntu.com/123053/
[22:54] <asac> xhaker: hmm. so there is no -pt at all
[22:57] <xhaker> asac: yes.. neither en_US
[22:58] <asac> en_US is ok
[22:58] <asac> thats shipped inside firefox/xulrunner itself
[22:58] <asac> xhaker: can you check whether there is more in xulrunner-addons ?
[22:59] <xhaker> nope.. just en-gb and pt-br there
[23:00] <xhaker> i did some dpkg -L on the language-pack* packages I have installed
[23:00] <xhaker> pt-br is inside language-pack-pt
[23:01] <xhaker> not sure where pt-pt should be, probably on this same package no?
[23:03] <asac> no ... should be there too
[23:03] <asac> guess i would need a current export
[23:03] <asac> lets see
[23:07] <soren> 2/win 21
[23:07] <soren> Err... No.
[23:08] <asac> xhaker: when did this start?
[23:09] <asac> just today? or rather one/two weeks ago?
[23:12] <xhaker> asac: I'm not sure, i've been using the English language. installed the pt support about a week ago
[23:16] <asac> xhaker: ok.
[23:59] <seb128> enough work for today time to get some sleep bbl