[05:53]  * ccheney is back from moving :)
[05:54] <ccheney> got ~ 95% of his stuff moved now, just have a few things to pick up and cleaning left
[07:27] <Amaranth> ccheney: Cleaning will take as long as moving
[07:33] <pitti> Good morning
[07:35] <Amaranth> good morning
[07:42] <didrocks> good morning pitti
[07:42] <mac_v> superm1: hi... this bug is not valid in Ubuntu , > Bug #442717
[07:42] <didrocks> hey Amaranth, mvo :)
[07:44] <mvo> hey didrocks!
[07:45] <mac_v> mvo: hi , regarding Bug #438843 , there seems to be a wrong icon name used for education category icon
[07:46] <Amaranth> mvo: software-center is awesome, btw :)
[07:46] <Amaranth> Was using it today to setup a new install, very slick
[07:47] <mac_v> +1 ^
[07:47] <mvo> mac_v: indeed, the screenshot indicates that. its the accessories icon that is wrong btw. but i wonder if its wrong in the menus as well - it is correct on my system
[07:47] <mvo> Amaranth: thanks .)
[07:49] <hyperair> does anyone notice that the mouse acceleration can't be set/changed?
[07:52] <mac_v> mvo: mat's screenshot was from an old version of the theme , we have corrected it  , so now they wont look same, but the education is still is using the wrong icon > http://launchpadlibrarian.net/33014702/Screenshot-Ubuntu%20Software%20Center.png
[07:53] <mvo> mac_v: and the panel menu at the same time shows the right icon?
[07:53] <mac_v> since the icons now look different , it might seem like there is no problem , so just wanted to remind :)
[07:53] <mac_v> yup
[07:53] <mac_v> hmm.. let me check again
[07:55] <Amaranth> we're down to 182 bugs in compiz that need to have something done with them (new, confirmed, triaged but not wishlist)
[07:55] <Amaranth> and 17 bugs fixed by getting a new snapshot and package updates :)
[07:55] <Amaranth> probably soon it will be 19
[07:59] <mac_v> mvo: ah! ha.. it was a theme bug only... i got education category confused with science... its not a Software center bug... there was actually a bug in the gnome-panel where the wrong icon is used for accessories , so thats what caused this
[07:59] <mvo> Amaranth: cool, sounds like its time for a new snapshot :)
[08:00] <Amaranth> mac_v: Where did my disabled bluetooth icon go? :)
[08:00] <Amaranth> mvo: I think it's almost release time
[08:00] <mvo> mac_v: ok, thanks. the code that reads the icons is very similar to the panel so if a icon is wrong there, its probably wrong in the panel as well
[08:00] <Amaranth> mvo: The plugins are all setup in the proper packs and there is a new splash image
[08:02] <mac_v> mvo: gnome-pane bug > Bug #421695
[08:02]  * mvo nods
[08:02] <mac_v> Amaranth: hm... ? there is an icon in Humanity for disabled too , it seems bluetooth doesnt use the disabled icon but rather doesnt display the icon... is that what you mentioned?
[08:02] <mvo> mac_v: could you close/commen ton #438843 then?
[08:03] <mac_v> ah ok
[08:03] <Amaranth> mac_v: No, when I disable bluetooth I used to get a blue logo with a little red X on it
[08:04] <Amaranth> mac_v: Now I get the same icon as enabled
[08:04]  * hyperair grumbles about the mouse acceleration refusing to be set
[08:04] <mac_v> Amaranth: the disabled will be transparent , we dont use 'x' anywhere else for disabled but rather toggle transparencies
[08:05] <Amaranth> mac_v: hrm
[08:05] <Amaranth> mac_v: So now I can't tell if it's wasting power or not
[08:05] <Amaranth> The icon sticks around when disabled so you can enable it again
[08:05] <mac_v> Amaranth: hmm... ok , so i'll make it more transparent ;)
[08:06] <Amaranth> mac_v: Perhaps make it use the Humanity-Dark bluetooth icon when disabled?
[08:06] <Amaranth> and vice versa
[08:06] <Amaranth> almost invisible but not quite
[08:07] <mac_v> Amaranth: hmm... even easier ;)  i'll check out which works better...  could you file a bug for this? otherwise the release team doesnt want icons changed
[08:10] <Amaranth> mac_v: bug 442867
[08:11] <mac_v> Amaranth: thanks
[08:12] <mac_v> mvo: check out > http://thorwil.wordpress.com/2008/05/09/popup-scrollbar-concept-demo/ can we use this for software store scrollbar?
[08:12] <didrocks> didn't it involve to patch gtk, IIRC?
[08:13] <mac_v> i think so
[08:13] <mac_v> but something to consider for future... too late for karmic
[08:13] <mac_v> i guess
[08:13] <mvo> I think I have seen this before ... macos?
[08:13] <didrocks> exactly. I was a big fan of his work when he presented it :)
[08:14] <mac_v> mvo: thorwil
[08:14] <Amaranth> Doesn't require gtk patches, he implements his own widget
[08:14] <mvo> yeah, too late for karmic :/
[08:14] <Amaranth> Not too accessible either
[08:15] <Amaranth> That is fixable but having one app do it differently would be bad
[08:15] <mac_v> Amaranth: i dont think accessibility is a problem , its just a new concept ,, so looks different
[08:15] <Amaranth> mac_v: No, I mean it doesn't implement any ATK interfaces
[08:15] <Amaranth> So it is literally not accessible
[08:16] <mac_v> Amaranth: ah.. yeah ... why i asked for software center is , we could use it as a testing ground to push into gnome3
[08:19] <Amaranth> Well since software-store is python you could port the code over easily enough
[08:19] <mac_v> mvo: is there anyway we could push this for karmic? [if mpt likes the idea]
[08:20] <Amaranth> Then just fix it up to implement the current scrollbar API perfectly, be accessible, and implement a couple of the changes mentioned in the bug report (single click jumps a page, don't make the arrows disappear if you move your mouse off the scrollbar for a second)
[08:20] <didrocks> I think that's way too intrusive to change it for karmic
[08:20] <Amaranth> mac_v: I would consider this too intrusive if you brought it up a month ago, tbh
[08:21] <mvo> mac_v: the scrollbars? for karmic? no
[08:21] <mac_v> oh , ok...
[08:21] <Amaranth> mac_v: I was making a bit of a joke saying it would be easy, read my big long list there :)
[08:22] <mac_v> Amaranth: ;p it would be easy once didrocks and mvo get on it ;)
[08:22] <mac_v> but anyways for the future
[08:23] <Amaranth> mvo: I'd say if we have no 0.8.4 release by Wednesday we should just do a new snapshot and cherry pick from there
[08:32] <mvo> ok
[08:39] <seb128> good morning there
[08:39] <didrocks> hey seb128, did you have a good long week-end? :)
[08:39] <seb128> hey didrocks, too short but good, and you?
[08:40] <didrocks> seb128: very good, but too short too (OWF, then 1er samedi du libre and finally gobal jam). So, no rest at all!
[08:41] <seb128> busy didrocks ;-)
[08:41] <seb128> how was samedi du libre?
[08:41] <didrocks> seb128: fine, as usual :) but there was the OSCD in the same place (http://act.osdc.fr/osdc2009fr/)
[08:42] <didrocks> I attended to some conferences in the meanwhile. couchdb one specifically.
[08:42] <al-maisan> Good morning!
[08:42] <didrocks> hi al-maisan
[08:43] <al-maisan> hello didrocks :)
[08:58] <chrisccoulson> good morning everyone
[08:59] <seb128> hey chrisccoulson
[08:59] <chrisccoulson> hey seb128, how are you?
[08:59] <seb128> good thanks, you?
[09:00] <chrisccoulson> yeah, quite good, i slept a lot over the weekend!
[09:01] <seb128> weekends are good to get extra sleep you don't get otherwise ;-)
[09:01] <chrisccoulson> yeah, definately!
[09:01] <pitti> hey seb128, hey chrisccoulson
[09:02] <chrisccoulson> hey pitti, did you have a good weekend?
[09:02] <seb128> hello pitti, had a good weekend?
[09:02] <lool> mvo: Hey, just FYI I was taking a look at apt over the WE and the Vcs-Bzr contents didn't match archive
[09:02] <pitti> was pretty exhausting actually
[09:02] <seb128> pitti, how was the moving, not feeling your muscle too much since? ;-)
[09:02] <lool> mvo: The changes from 0.7.23.1ubuntu1 were in a 0.7.24.1ubuntu1 in Bzr
[09:02] <pitti> we drove down to my sister (6 hours) to help her moving, worked the entire Saturday from 7 to 21, Sunday from 7 to 15, and then drove back home
[09:03] <chrisccoulson> that's a lot of hours;)
[09:04] <seb128> too many bug emails during the weekend
[09:04] <seb128> 1106 since friday
[09:04] <Amaranth> It's not me this time!
[09:04] <chrisccoulson> heh, i can imagine, now everyone is testing the beta
[09:04] <seb128> I will spend my morning reading bug emails again, *shrug*
[09:05] <chrisccoulson> this gtk issue is a nasty one ;)
[09:05] <seb128> chrisccoulson, did you open a bug upstream about this one?
[09:05]  * Amaranth can't believe the polkit-gnome bug was closed NOTABUG upstream
[09:05] <chrisccoulson> seb128 - i've just done it now
[09:05] <seb128> chrisccoulson, well not really no since it's easy to workaround
[09:05] <seb128> but still would be nice to get fixed this week
[09:05] <Amaranth> mvo: btw, someone in #ubuntu+1 had dpkg segfault while upgrading libc6
[09:05] <chrisccoulson> i pinged mclasen about it last night, and he knew about it already
[09:06] <Amaranth> mvo: Their system was pretty much dead after this
[09:06] <seb128> can you add "csw" to the whiteboard?
[09:06] <chrisccoulson> yeah, can do
[09:06] <Amaranth> mvo: I told them to leave it on and perhaps talk to you to see if there is any information you can get off it before he tries to fix it
[09:06] <mvo> lool: oh, bad. let me check that
[09:07] <mvo> Amaranth: urgh, dpkg segfaults are usually faulty memory or something like this
[09:07] <mvo> usually ...
[09:07] <Amaranth> mvo: Yeah I figured it was either a one in a million bug or cosmic radiation :)
[09:08] <Amaranth> mvo: I think he may have given up, he isn't in #ubuntu+1 anymore
[09:09] <mvo> lool: I correct the branch now, for karmic its lp:~ubuntu-core-dev/apt/karmic
[09:09] <mvo> lool: the stuff in ubuntu had too much churn, I wanted to wait with that for the next cycle
[09:09] <didrocks> seb128: I think, you should blame the global jam considering the bug triaging overload :)
[09:09] <mvo> lool: I fixed the vcs-bzr header now
[09:11] <lool> mvo: Ok thanks
[09:13] <seb128> didrocks, ;-)
[09:19] <chrisccoulson> seb128 - did you see that vuntz fixed the gnome-keyring issue?
[09:19] <seb128> chrisccoulson, yes
[09:19] <seb128> I will backport that after cleaning my bugmails
[09:19] <chrisccoulson> thanks
[09:20] <seb128> you're welcome, thank you for all your bug work ;-)
[09:20] <seb128> half of the bugs files are duplicates, shrug
[09:21] <seb128> I'm wondering what component is responsive for the background not refreshing correctly after opening the calendar from the clock applet
[09:21] <seb128> seems we get quite some bugs about it
[09:22] <seb128> I would tend to blame gtk csw
[09:22] <Amaranth> no no
[09:22] <Amaranth> seb128: you mean the shadow stays?
[09:22] <seb128> Amaranth, yes
[09:22] <Amaranth> seb128: one moment
[09:23] <chrisccoulson> that one is quite annoying too, but i wasn't sure what was causing it
[09:23] <Amaranth> seb128: dupe them to bug 428783
[09:23] <seb128> Amaranth, thanks
[09:23] <Amaranth> fixed on wednesday :)
[09:23] <seb128> will mvo upload all your fixes today?
[09:24] <mpt_> glatzor, hi, thanks so much for that list of error messages
[09:24] <Amaranth> seb128: No, wednesday :)
[09:24] <Amaranth> seb128: Figure we'll just roll them all up with getting a new upstream snapshot, less work for mvo
[09:24] <seb128> Amaranth, well wednesday was frozen
[09:24] <Amaranth> seb128: I mean 2 days from today :)
[09:25] <seb128> ah ok, why not before?
[09:25] <mpt_> glatzor, when you have time, it would be cool if we could go through them one at a time to work out when they happen, how to prevent them, how to reword them, etc
[09:25] <Amaranth> Although nothing in current compiz bzr depends on the upstream fixes except turning constrain_y back on
[09:25] <Amaranth> Which we were going to do even if we didn't get the proper fix for small screens
[09:26] <Amaranth> seb128: I guess if he wants to upload a package today bzr is ready
[09:26] <seb128> mvo, ^
[09:26] <Amaranth> that'll fix 7 bugs, anyway
[09:26] <mvo> seb128, Amaranth: thanks, I can do that
[09:26]  * seb128 hugs mvo
[09:27] <seb128> Amaranth, thanks for all the work you do you compiz ;-)
[09:28] <Amaranth> d'oh I forgot to push one but I have other changes in my local copy now
[09:28] <Amaranth> oh well, that one can wait
[09:29] <seb128> bug #342980 is weird too
[09:30] <Amaranth> seb128: I can't reproduce :/
[09:30] <seb128> the current comment the user has it 100% of the time
[09:30] <Amaranth> Oh, that guy is having the shadow issue
[09:31] <Amaranth> The actual bug is about gnome-panel not being redrawn anymore when you do something to it while it is set to not expand
[09:31] <seb128> oh ok
[09:32] <chrisccoulson> Amaranth - i've seen windows not updating until i resize them on my system
[09:32] <Amaranth> And various other windows apparently but I haven't seen this bug since early alphas and it's impossible to reliably reproduce
[09:32] <chrisccoulson> quite often, but maybe that's due to my nvidia card;)
[09:33] <Amaranth> I've got some new nvidia hate
[09:33] <Amaranth> I can't use compiz on my old laptop
[09:33] <Amaranth> The same system I used compiz on for years
[09:33] <seb128> pitti, have you seen bug #442115?
[09:34] <pitti> seb128: ugh, looking
[09:34] <pitti> seb128: ah, maxb pinged me about that on Friday; I'll ask him for some more info
[09:34] <seb128> pitti, thanks
[09:36] <Amaranth> seb128: upstream can reproduce that one and are as stumped as I am :/
[09:37] <seb128> Amaranth, hum, ok
[09:37] <seb128> hate apport dpkg install bugs
[09:38] <seb128> mvo, could you have a look to bug #441308 and tell me if the reassign is right?
[09:38] <seb128> I don't get why it was assigned to gdm to start
[09:38] <Amaranth> seb128: On a positive note that's probably the last "omg this crap is broken" bug reported for compiz :)
[09:38] <seb128> Amaranth, ;-)
[09:38] <Amaranth> everything else is things not quite doing the right thing or crashes :P
[09:39] <mvo> seb128: yep, right - couchdb bug
[09:39] <seb128> mvo, thanks
[09:40] <seb128> mvo, thanks
[09:40] <mvo> np
[09:40] <mvo> np
[09:40] <Amaranth> hehe
[09:41] <mvo> seb128: sadly apt is sometimes dumb when it comes to this .(
[09:42] <mvo> assigning i mean
[09:43] <seb128> hum
[09:43] <seb128> bug #441167, anybody has a clue about what is pam mount?
[09:46] <mvo> no, sorry
[09:46] <geser> !info libpam-mount
[09:47] <seb128> geser, that far I guessed what I lack is how it can breaks gdm installation
[09:47] <geser> hmm
[09:53] <mac_v> seb128: hi... i'm facing an odd bug... when i click on a button , i cannot click the button again unless i move the pointer... making it hard to do multiple clicks on the same button... is this a purposeful move?
[09:53] <Amaranth> mac_v: known
[09:53] <chrisccoulson> mac_v - known issue
[09:53] <seb128> mac_v, known gtk bug with several duplicates
[09:54] <mac_v> ah.. thanks all ... anyone know the bug# ? :)
[09:54] <chrisccoulson> bug 441905
[09:54] <mac_v> awesome
[10:02]  * maxb wakes up; Hi pitti - need to get myself in to work now, but say anything you'd like me to check and I'll be able to do some debugging at my lunchtime in a few hours.
[10:03] <pitti> maxb: I replied to the bug; first thing is to check whether hal picked it up properly
[10:03] <maxb> X is doing the write thing, so I would think so.
[10:03] <geser> seb128: just a wild guess, could it be that the "su gdm" calls in gdm.postinst trigger it? the dpkg output doesn't unfortunately tell which user password it asks for
[10:03] <maxb> I will check the bug though
[10:04] <seb128> geser, could be, those calls are problematic anyway we will need to rework that
[10:04] <seb128> gconftool uses gconf which uses dbus and we got cases where it breaks
[10:04] <seb128> using dbus-launch would workaround some of the issues
[10:05] <pitti> gconftool can't write the files directly?
[10:05] <pitti> dbus-launch in a postinst doesn't sound like a robustification..
[10:06] <Amaranth> ooh, that reminds me, I forgot to file a bug
[10:06] <Amaranth> my gdm had a .gvfs directory that not even root could touch
[10:06] <Amaranth> so when gdm postinst tries to chown -R /var/lib/gdm it dies on that one
[10:07] <chrisccoulson> Amaranth - i was just about to mention the same issue there, as hggdh had a similar upgrade failure too
[10:07] <seb128> right, several users got that too
[10:08] <seb128> it's a fuse design thing
[10:08] <seb128> I think the gdm user should be tweaked to not be in the fuse group to avoid those
[10:08] <seb128> pitti, gconftool doesn't write to files it talks to gconfd
[10:09] <pitti> $ id gdm
[10:09] <pitti> uid=114(gdm) gid=121(gdm) Gruppen=121(gdm)
[10:09] <pitti> hm, it's not?
[10:09] <seb128> pitti, but right I think I will make the postinst write the .xml on disk directly or something
[10:09] <seb128> pitti, oh, we don't really on the fuse group membership nowdays do we?
[10:09] <pitti> seb128: we'd need to support both merged and broken-out format, though, no?
[10:09] <Amaranth> seb128: gconftool has a --direct option
[10:09] <Amaranth> --direct                                       Bypass server, and access the configuration database directly. Requires that gconfd is not running.
[10:09] <Amaranth> oh, dang
[10:10] <pitti> oh, yay
[10:10] <chrisccoulson> i don't know what spawns a gvfs daemon in the GDM session. i've never seen one yet
[10:10] <seb128> Amaranth, "requires that gconfd is not running"...
[10:10] <Amaranth> no, gdm is still running so it's gconfd is too
[10:10] <Amaranth> yeah, thus 'dang' :P
[10:10] <pitti> can't it be killed?
[10:10] <seb128> I'm wondering if we should just drop a .gtkrc there
[10:10] <pitti> or, rather
[10:10] <pitti> _if_ it's running, call gconftool
[10:10] <pitti> if it isn't, call it with --direct
[10:11] <Amaranth> pitti: but gconftool needs to be called with dbus-launch if it's running which is the problem to begin with, isn't it?
[10:11] <pitti> (there should be an --auto-direct option which does that..)
[10:15] <geser> but either way gconftool needs to be called with su as user "gdm", right? if it's really the su call which triggers this bug seb128 is looking at it won't help
[10:16] <seb128> right
[10:16] <seb128> which is why I think we should look at using a gtkrc or writting the .xml file directly
[10:23] <SiDi> asac: hi there, are you around?
[10:25] <asac> yes
[10:26] <SiDi> i wanted to talk to you about theming issues in firefox and thunderbird
[10:26] <SiDi> which are very annoying for xubuntu since they're particularly obvious with our theme :)
[10:26] <SiDi> the first problem is that one, asac:https://bugzilla.mozilla.org/show_bug.cgi?id=478632
[10:27] <SiDi> we cooked a workaround that turns this blue url into a slightly ligther one than the theme's text color, so that it works with bright and dark themes
[10:28] <asac> https://bug478632.bugzilla.mozilla.org/attachment.cgi?id=377665
[10:28] <asac> that one?
[10:28] <SiDi> since upstream seems to have several solutions but to not have chosen which one to use so far, i'd like to have my workaround used as a patch
[10:28] <SiDi> ours is here http://paste.ubuntu.com/286054/
[10:28] <SiDi> 65 is a bit too light, its really a low contrast
[10:28] <SiDi> 75 works slightly better :)
[10:28] <asac> so your approach is the same as the upstream patch ...
[10:29] <SiDi> yeah
[10:29] <SiDi> but they dont know which to apply yet, and its obvious it wont land before 3.6/3.7, so not in karmic
[10:29] <SiDi> and if we cant have it fixed in the firefox package we'll have to do a xubufox package just for that, which is overkill :]
[10:30] <asac> SiDi: the bug seems to be dropped from the folks radar. re-raising this might help
[10:30] <SiDi> (unless firefox supports default userChrome.css via XDG? BUt i still think it would be quite dirty since it would work only for the default theme)
[10:30] <asac> at best we would have something they committed
[10:30] <asac> for cherry-pick ... taking something with r- will cause troubles
[10:30] <asac> on my side
[10:30] <SiDi> r-?
[10:30] <asac> SiDi: what about #14 ?
[10:31] <asac> SiDi: r- == review-
[10:31] <asac> -> aka not good enough
[10:31] <SiDi> #14 is ok but we have no idea how to provide such a link color...
[10:31] <SiDi> i read the source to try to find it out but i still didnt find
[10:32] <SiDi> and, firefox 3.0 was using a lighter text color than the name, it wasnt using a link color, actually
[10:32] <Amaranth> mvo: we're not up to at least 12 bugs being fixed by getting a new compiz snapshot or an 0.8.4 release :)
[10:37] <SiDi> asac: so, what should i do? :/
[10:37] <asac> SiDi: that url link color is coming from our gtk theme?
[10:38] <SiDi> apparently its coming from the preferences in firefox
[10:38] <mvo> Amaranth: nice!
[10:38] <SiDi> there is a mysterious "use system colors", asac, but i didnt find what name i should give to it in my gtkrc
[10:38] <Amaranth> mvo: 2 more probably coming in the next hour or so
[10:38] <SiDi> and it still forces to change the firefox package to enable this option by default, anyway
[10:39] <asac> SiDi: the use_system_colors is for websites only afaik
[10:40] <SiDi> i asked in the report how to define such a link color in the themerc
[10:41] <SiDi> in case i dont get any answer, asac, will it be possible to add the above workaround to ubufox's overlay.css or to the firefox package?
[10:41] <asac> i would say no. it got a review-
[10:41] <asac> why does that work?
[10:42] <asac> .ac-url-text is the url text in the awesome bar?
[10:42] <SiDi> its the text of the url
[10:42] <SiDi> putting it to the normal color with a lower opacity makes it readable when selected and when not selected, regardless of the theme
[10:42] <SiDi> because it'll use the theme's colors and not a hardcoded #00f
[10:43] <SiDi> i don't understand why they changed that in firefox 3.5 anyway
[10:43] <SiDi> its not like the link itself is "more" clickable than the rest of the list item
[10:44] <asac> well. in ffox 3 there were also complains that its not readable in dark theme iirc
[10:44] <Amaranth> SiDi: URLs are always blue and always underlined. This is a law or something.
[10:45] <Amaranth> 13
[10:45] <asac> SiDi: you have a screen with your workaround for dark and for normal?
[10:45] <SiDi> Amaranth: this one isnt underlined, and usually you underline links that can be clicked :)
[10:45] <SiDi> asac: sec
[10:46] <Amaranth> SiDi: Oh, I don't have firefox installed anymore so I was going on memory
[10:47] <SiDi> i got to restart firefox for the screenshots, brb
[10:48] <slomo> seb128: hi, did you get my mail? :)
[10:49] <seb128> slomo, hey, yes I was just about to sync those and gstreamer0.10
[10:49] <mvo> Amaranth: ok, I check back on it after lunch then - I'm busy with software-center anyway :)
[10:50] <Amaranth> mvo: oh we don't have a release today I don't think
[10:50] <Amaranth> mvo: But I suspect the number of bugs just an upstream pull fixes will get to 20 by the time we update if things keep going at this rate :)
[10:51] <mvo> Amaranth: amazing
[10:52] <SiDi> http://imagebin.ca/img/LKSlnTlN.jpg asac
[10:52] <SiDi> on the right, without the workaround, on the left, with
[10:52] <SiDi> Default ubuntu and xubuntu themes
[10:52] <asac> SiDi: please attach to the bug
[10:52] <SiDi> sure
[10:52] <asac> SiDi: please use the same opacity suggested by michaels patch
[10:52] <asac> 0.75
[10:53] <SiDi> aw, gotta restart ff again then
[10:53] <seb128> slomo, do you have string changes in gnome-codec-install?
[10:53] <SiDi> asac: i need to go soon, so i'll do that tonight, sending myself an email reminder
[10:53] <SiDi> can we quickly look into the thunderbird bug?
[10:53] <slomo> seb128: gnome-codec-install only has a new warning in ubuntu, right? mvo or someone else should merge it then ;)
[10:55] <seb128> slomo, right, but the new version changelog seems to indicate string changes, we are past string freeze for karmic now
[10:55] <Amaranth> SiDi, asac: Didn't we use this in 3.0? I remember my awesomebar turning green
[10:55] <slomo> seb128: oh, there are no string changes but only new/fixed translations
[10:55] <asac> SiDi: i posted your screen now to the bug
[10:56] <SiDi> Amaranth: in 3.0 it was looking like it looks now with the workaround, yeh
[10:56] <SiDi> i dont know if it was an ubuntu patch or upstream behaviour though
[10:56] <SiDi> asac: cheers; i'll add more screenies tonight with all the solutions and different themes
[10:56] <asac> Amaranth: all i remember is that 3.0 wasnt better than 3.5 for dark theme
[10:56] <asac> i think the "green" was removed for final
[10:56] <asac> but i am not so sure atm
[10:56] <SiDi> for the thunderbird issue we have, it's a bug in the background color used for frame titles in _some_ of the tabs of the preferences dialog
[10:56] <seb128> slomo, ok cool, thanks
[10:57] <SiDi> its a really crazy bug, and we spent like 2 hours trying to figure it out. probably a theming issue in XUL
[10:57] <asac> SiDi: what bug id is tbird?
[10:57] <seb128> slomo, btw do you look to the g-c-i bugs in launchpad? there is several crash ones and some other issues apparently
[10:57] <seb128> https://launchpad.net/ubuntu/+source/gnome-codec-install/+bugs
[10:57] <SiDi>      https://bugs.launchpad.net/xubuntu-artwork/+bug/439398
[10:57] <SiDi> its that, there is the link to the upstream report i made
[10:58] <SiDi> http://launchpadlibrarian.net/32940044/Capture-6.png
[10:58] <asac> SiDi: please check tbird 3.0 from daily ppa
[10:58] <asac> its close to zero likelyhood that anything will be fixed in tbird 2
[10:58] <SiDi> we can live with the menu colors not being perfect, but the one in the preferences dialog is quite harsh
[10:58] <asac> tbird 3 should be like ffox 3.5
[10:58] <SiDi> we got a css hack that "fixes" it
[10:59] <SiDi> it turns the dark grey into a lightgrey that is the background color of windows
[10:59] <seb128> bah
[10:59] <SiDi> so its perfectly readable
[10:59] <asac> SiDi: we cannot deploy css hacks as those are hard to make sensitive wrt what theme you are using
[10:59] <seb128> pitti, seems the i386 retracers is stucked since thursday
[10:59] <asac> so you can change tbird to be better by default, but not everywhere
[10:59] <SiDi> (it works for all themes that i know of, though :p)
[10:59] <seb128> pitti, ie log not updated but still "running"
[11:00] <pitti> seb128: oh, I just checked the other ones, but didn't touch the running ones; so let's kill it?
[11:00] <seb128> pitti, should I just stop and restart it or do you want to have a look
[11:00] <pitti> seb128: please just restart
[11:00] <seb128> ok
[11:00] <seb128> doing that now
[11:00] <asac> SiDi: i need to see the css hack then ;)
[11:00] <asac> and an explain why it works everywhere
[11:00] <SiDi> http://paste.ubuntu.com/286053/ here it is
[11:00] <SiDi> So, there are 2 bugs actually. THe title of the frames has a dark grey background
[11:01] <SiDi> we identified it as the bg[NORMAL] from our GtkMenu style
[11:01] <SiDi> the hack replaces it with the color used as background for dialogs
[11:02] <SiDi> its not exactly the same one as in tab pages, but the color is sufficiently near for it to work when the label is inside a tab page. and its the same color for the labels that are not in tab pages (of course thunderbirds preferences have both cases...)
[11:02] <SiDi> the part with background:transparent !important is because otherwise we have 2 nice black squares on the left and right sides of the label
[11:03] <SiDi> i couldnt identify them, they're not matching with anything in the dom structure of the dialog
[11:04] <SiDi> can you point me to the tb3 PPA please? cant find it
[11:05] <SiDi> asac: i suppose there are ways to put this hack in a thunderbird plugin that we could seed in xubuntu?
[11:09] <SiDi> (i got the ubuntu-mozilla-daily PPA but dont see the packages
[11:09] <SiDi> anyway i must go right now, talk to you later asac
[11:13] <SiDi> asac: its fixed in tb 3.0
[11:14] <SiDi> so that'd be a ugly hack for karmic only, but a ugly hack that seems to work quite well
[11:18] <mat_t> asac: after clean install and latest updates my Mini 9  does not have wireless anymore :(
[11:18] <mat_t> asac: is this a known issue, or should I file a bug?
[11:20] <davmor2> mat_t: known bug ask Keybuk he'll throw half a dozen bugs at you.
[11:21] <mat_t> davmor2: thx :)
[11:22] <seb128> slomo, do you have any idea about bug #442157?
[11:24] <asac> mat_t: wl?
[11:24] <asac> mat_t: does your device show up in the applet? or just nothing?
[11:25] <slomo> seb128: yes, i had this too one time... no idea why it happend but pulseaudio died for some reason :)
[11:25] <seb128> slomo, shouldn't it fallback to something else if pulseaudio is not running?
[11:26] <geser> pitti: thanks for fixing that keyboard variant bug
[11:26] <pitti> geser: works for you as well now?
[11:27] <slomo> seb128: yes, i really don't know what the problem was :) can it be reproduced by this guy?
[11:27] <geser> pitti: yes, both on my notebook and my desktop. No more resetting the keyboard configuration once after gnome login anymore :)
[11:27] <pitti> \o/
[11:27] <seb128> slomo, dunno I will ask on the bug
[11:29] <seb128> ok, it took me the morning but I'm done reading weekend backlog
[11:29] <seb128> chrisccoulson, alex fixed the gtk issue, that was quick ;-)
[11:30] <seb128> let's backport those gnome-keyring and gdk changes
[11:30] <chrisccoulson> seb128 - yeah, i just checked my mail:)
[11:30] <chrisccoulson> that was definately quite fast ;)
[11:30] <Amaranth> mvo: That guy with the dpkg segfault is around again if you want me to ask him for anything
[11:31] <seb128> oh nice the gtkmm debian maintainer woke up we will be able to sync those updates too ;-)
[11:32] <Amaranth> seb128: any idea what we're going to do with polkit-gnome not getting focus? bug 433851 was closed upstream as NOTABUG
[11:32] <Amaranth> I've put a workaround in compiz for now but metacity (and every other WM) needs a workaround too if we don't put robert_ancell's patch in
[11:32] <seb128> Amaranth, no, wms are you area no? ;-)
[11:34] <Amaranth> davidz says we need a new WM hint for "system modal" dialogs to properly fix this
[11:34] <Amaranth> But I don't think we can wait 2 years
[11:36] <seb128> right, that's something we need to address for the lts
[11:36] <seb128> though having compiz workarounding is a first good step for karmic ;-)
[11:36] <seb128> is there any reason we could push quickly for the new hint?
[11:37] <Amaranth> I dunno, lmurray (kwin dev) seems to be working on an update to this spec right now so I could talk to him
[11:44] <Amaranth> seb128: He says it's an app bug :P
[11:44]  * Amaranth goes in circles for a bit
[11:45] <Amaranth> There is a simpler patch we could do to bypass focus stealing prevention though, I'll talk to robert_ancell about it
[11:45] <Amaranth> Should only be a line or two of code instead of an interface change
[11:45] <seb128> ok good, thanks
[11:45]  * seb128 lunch
[11:46] <seb128> be back in half an hour
[11:46] <mat_t> asac: nope, nothing
[11:47] <mat_t> asac: the whole "wireless" section seems to be gone
[11:49] <mat_t> asac: 3G works fine though
[11:57] <asac> mat_t: lsmod | grep wl
[11:57] <asac> is wl driver loaded?
[11:57] <asac> also ifconfig -a .... does "wl0" or something show up there?
[11:57] <Amaranth> So it appears kwin is cheating with polkit-kde too
[11:58] <Amaranth> makes me feel less bad about what I'm about to suggest :P
[12:05] <mvo> Amaranth: hrm, I missed him, I was at lunch
[12:06] <Amaranth> Is it too late to do http://www.realistanew.com/random/polkit-bling.png ?
[12:06] <thekorn> Hi, I think I found a bug in gnome's 'open file' dialog in karmic and I would like to know where to report it,
[12:07] <Amaranth> it's totally fake, you can still use the rest of the desktop
[12:07] <Amaranth> but it gives the impression that this dialog is something you need to deal with
[12:07] <Amaranth> and all I had to do was turn on one compiz plugin and add match rules to 4 or 5 of them
[12:08] <thekorn> the file open dialog is just not generating thumbnails for image and video files,
[12:08] <thekorn> but when I open a folder containing an image with nautilus before this thumbnails are correctly generated
[12:13] <seb128> thekorn, do we really want the filechooser to spend time doing that? that's sort of expensive
[12:16] <Amaranth> also http://www.realistanew.com/random/polkit-bling2.png <--we can't actually do blur though ;)
[12:17] <thekorn> seb128: ah, ok. so it's not a bug and it is working as expected
[12:17] <seb128> I don't know
[12:17] <seb128> it would be a gtk fileselector bug to open upstream rather
[12:17] <seb128> ie I don't know if that's a design decision or a bug and it's so low priority that nobody in the ubuntu team will look at it anyway
[12:18] <thekorn> maybe it's because the filechooser does not have an async interface/method for this
[12:18] <seb128> you can look for upstream bugs though
[12:19] <Amaranth> seb128: so is it too late to make compiz look like one of those screenshots? :)
[12:19] <seb128> I would say it's late yes
[12:19] <seb128> but other people might have different opinions
[12:19] <thekorn> seb128: thanks will ask/report about this upstream
[12:19]  * Amaranth will not tell the Design Team
[12:19] <seb128> you can try asking mvo and pitti what they think
[12:19] <seb128> thekorn, thanks
[12:20] <Amaranth> seb128: Really it's kind of a waste without the mouse and keyboard grabs
[12:20] <mac_v> mpt_: ^ could that be done for policky kit in karmic ;)
[12:20] <mac_v> policy*
[12:20] <Amaranth> mac_v: no no, compiz is doing that, right now, on my computer
[12:20] <Amaranth> I enabled one extra plugin and changed a bunch of match rules
[12:21] <Amaranth> the blur is not doable for real though, just wanted to see what it would look like
[12:21] <mac_v> Amaranth: nevermind , others then  ;p ...i want that... how did you do it?
[12:21] <mac_v> no need blur , but just the darkening
[12:21] <thekorn> hmm, thumbnails where never generated while browsing in the filechooser, I guess I just get confused because the default image icon in the new theme looks similar to the 'icon not found'-icon
[12:22] <Amaranth> mac_v: I added match rules to winrules, decoration, loginout, and place to make the window always centered, always on top, no decoration, and faded
[12:22] <Amaranth> oh, and not movable
[12:23]  * mpt_ reads up
[12:23] <mac_v> Amaranth: i'v tried that...didnt work for me... but what is the window match?
[12:23] <Amaranth> mac_v:  | (class=Polkit-gnome-authentication-agent-1 & type=Dialog)
[12:23] <Amaranth> add that to the end of the logout matches
[12:24] <Amaranth> decorator needs to be !(class=Polkit-gnome-authentication-agent-1 & type=Dialog)
[12:24] <Amaranth> the rest are just (class=Polkit-gnome-authentication-agent-1 & type=Dialog)
[12:25] <mac_v> ah! , i was using wrong class *face palm*
[12:25] <mac_v> works like a charm... Amaranth thanks :)
[12:25] <Amaranth> That's as close as compiz can get to a "system modal" window like gksu, only thing missing is the mouse and keyboard grabs
[12:25] <Amaranth> I think for karmic we probably just want to make polkit-gnome _work_
[12:25] <Amaranth> for lucid we can make it pretty
[12:26] <mpt_> Amaranth, seb128, mac_v: I don't want PolicyKit alerts (at least, not those from the Ubuntu Software Center) to be system-modal. As far as I'm concerned that's one of PolicyKit's great advantages over gksu.
[12:27] <Amaranth> ok, that kills that
[12:27] <mac_v> hehe ;p
[12:27] <Amaranth> can't do them per app calling it :P
[12:28] <mpt_> Just modal to the parent window, and therefore taking focus whenever you try to focus the parent window.
[12:28] <Amaranth> mpt_: but that part probably isn't happening either
[12:28] <Amaranth> upstream rejected it and it's an API change
[12:29] <mpt_> So maybe I should comment in the b.g.o bug report
[12:29] <Amaranth> That would be good
[12:29]  * mac_v likes the gksu way ;)
[12:34]  * Amaranth made the gksu way not suck with compiz so is kind of attached as well :)
[12:36] <mat_t> asac: ok trying that
[12:37] <asac> mat_t: whats the problem on 435109 ?
[12:38] <asac> i mean ... is there really an issue in nm-applet?
[12:38] <asac> feels like its just a mapping issue in theme
[12:38] <asac> mac_v: ^^ ?
[12:38] <mat_t> bug #435109
[12:38] <mat_t> hm, no bugbot
[12:38] <asac> yeah sry
[12:38] <asac> nm uses nm-device-wwan
[12:39] <mat_t> asac: in Human theme, the panel indicator for 3G connection is using the icon from notify-osd set
[12:39] <asac> yes. but seems its just a bogus link ... or something
[12:39] <asac> nm-device-wwan is mapped to the wifi icon
[12:39] <mat_t> asac: I'm not sure what's happening here - kwwii should look into it
[12:40] <mac_v> asac: mat_t: yeah , human theme lacks that icon... Humanity has one ;)
[12:40] <asac> like: notify-send -i nm-device-wwan test
[12:40] <mac_v> mat_t: that icon seems to be a new addition...
[12:40] <mat_t> asac: notify-osd icons are now in a separate package, so they should never appear anywhere outside of the notification bubble
[12:40] <mat_t> mac_v: ^
[12:41] <mac_v> mat_t: yes , but since human lacks the icon.. it seems to fallback to the available icon
[12:41] <asac> mat_t: dont get confused. i just used notify-send to quickly see the mapping for nm-device-wwan
[12:41] <mac_v> mat_t: asa workaround , you can add Humanity ad the inherits
[12:41] <mat_t> hm, that would be hi-color?
[12:41] <mac_v>  as a *
[12:42] <asac> anyway. thats a theme issue for sure.
[12:42] <mac_v> asac: any progress on the wwan/adhoc signal icons?
[12:42] <mac_v> as in > new names
[12:43] <mat_t> asac: mac_v: ok, so we're missing the correct icon in the human theme then
[12:43] <asac> could be. maybe we just have a bad link
[12:44] <mac_v> mat_t: you can add Humanity as the inherits in Human
[12:44] <mac_v> since Humanity is now the default
[12:44] <mat_t> asac: who could check if the link is correct?
[12:44] <asac> /usr/share/icons/Humanity/status/24/nm-device-wwan.svg /usr/share/icons/Humanity/status/22/nm-device-wwan.svg
[12:44] <asac> those are wrong
[12:44] <asac> lrwxrwxrwx 1 root root 17 2009-09-25 11:36 /usr/share/icons/Humanity/status/22/nm-device-wwan.svg -> nm-signal-100.svg
[12:44] <asac> lrwxrwxrwx 1 root root 17 2009-09-25 11:36 /usr/share/icons/Humanity/status/24/nm-device-wwan.svg -> nm-signal-100.svg
[12:45] <mac_v> asac: huh?
[12:46] <asac> mac_v: those are wrong, right?
[12:46] <mac_v> asac: those have been corrected , in Humanity
[12:46] <asac> e.g. there is no tower yet
[12:46] <mat_t> asac: OK, let's park that for now - when kwwii is back tomorrow I will ask him to look through all n-m icons in Human and Humanity and see which links are broken or which icons are wrong or missing
[12:46] <asac> ok
[12:46] <asac> mac_v: is that fix uploaded?
[12:46] <asac> i havent upgraded today
[12:47] <mac_v> asac: lool has to update humanity... its not updated yet i believe
[12:47] <mpt_> Amaranth, btw, why did you say "this is a bit of a security issue"?
[12:47] <mat_t> asac: so that we don't have two parallel threads of conversation
[12:48] <asac> mat_t: sure. i feel i am off the hook ;)
[12:48] <Amaranth> mpt_: Because the window appears on top and depending on your theme it may be hard to tell it doesn't have focus
[12:48] <mpt_> Amaranth, ah, good point
[12:48] <mat_t> asac: The design team will be responsible if the icons are wrong, so it's probably the best thing to do :)
[12:48] <Amaranth> mpt_: so you type "mypassword" and press enter and wonder why people on IRC are ssh'ed into your comptuer
[12:48] <Amaranth> computer*
[12:48] <mpt_> indeed
[12:48] <asac> ;)
[12:48] <asac> mat_t: thanks!!
[12:49] <asac> :-P
[12:49] <mpt_> (how did you know my password was "mypassword"???)
[12:49] <mat_t> asac: np, thank you
[12:49] <Amaranth> hehe, I had to fight myself to not put my actual password there
[12:49] <mac_v> asac: for now , the nm-device-wwan and the nm-device-adhoc  icons are in color , i'v not done the greyscale version ... /me waiting for the new signal names :)
[12:49] <mac_v> icon names*
[12:52] <mat_t> asac: btw, grep wl doesn't return anything
[12:53]  * mat_t -> lunch
[12:56] <asac> mat_t: sudo modprobe -v wl
[13:01] <lool> asac: The planned update is in my PPA
[13:02] <lool> mac_v: Did you see the report that the bluetooth disabled icon is not good with latest humanity?
[13:02] <mac_v> lool: which one? the one Amaranth just filed?
[13:02] <lool> mac_v: https://lists.ubuntu.com/archives/ubuntu-devel/2009-October/029281.html
[13:02] <asac> lool: /usr/share/icons/Humanity/status/22/nm-device-wwan.svg where does that link point to?
[13:02] <lool> asac: It's a file here
[13:03] <asac> ok. i assume its right then
[13:03] <Amaranth> lool: yeah, I told mac_v and filed the bug shortly after that :)
[13:04] <lool> asac: http://people.canonical.com/~lool/nm-device-wwan.svg
[13:04] <lool> Amaranth: Thanks
[13:04] <mac_v> lool: asac: i'm repeating again ;) the device-wwan is still in color... asac hasnt yet confirmed the new icon name to be used for signal strengths in the wwan and adhoc...
[13:04] <mac_v> so when asac lets me know the new names i'll be doing greyscale icons for those signals too
[13:05] <asac> mac_v: and without signal strength we cannot fix this?
[13:05] <lool> mac_v: Please provide them separately to me (e.g. list of files to copy from tip) when you have them as I'm not pushing a new snapshot of tip to get them
[13:05] <mac_v> asac: you are making me do the icons twice :(
[13:06] <mac_v> lool: sure
[13:06] <mac_v> asac: now , i'd have to do them in greyscale and then again , for the new names ;p
[13:07] <asac> mac_v: we definitly need a icon without signal strenght as just a few devices support signal strength
[13:07] <asac> so its not duplicated.
[13:07] <didrocks> asac: I saw you synced epiphany-webkit (I was at OWF, helping on Canonical booth, that's why I wasn't available). No more worked needed there?
[13:07] <asac> didrocks: we synched epiphany-browser
[13:07] <asac> seb128: can you bin-NEW seed?
[13:07] <seb128> asac, yes
[13:08] <asac> (seed == package needed for epiphany-browser)
[13:08] <asac> thx
[13:08] <seb128> I know what seed is, it's one of the js used by GNOME ;-)
[13:08] <asac> didrocks: i think all should be fine minus some bin_NEWing
[13:08] <didrocks> asac: ok, perfect :)
[13:08] <seb128> asac, newed
[13:08] <asac> great.
[13:11] <mac_v> asac: hm... so , i'm not sure what to do :(  so the devices without signal strength will use color version  :/  since you are using the device icon in the notification area... you can just make the devices without signals to use the nm-wwan-signal-100 instead
[13:11] <Amaranth> "one of the js" is the sad part :/
[13:11] <lool> mac_v: Do you have an ETA for the bluetooth and signal strength levels fixes?
[13:12] <lool> mac_v: e.g. tonight, tomorrow, etc.
[13:12] <lool> I'm away at the end of the week (thursday-sunday) so would like to plan for it asap
[13:12] <mac_v> lool: bluetooth , in a few mins... but signal strength not until asac
[13:12] <mac_v> mentions the names
[13:12] <lool> k
[13:12] <asac> mac_v: dont assume the signal strength is coming for sure
[13:12] <lool> Do we have a bug for the signal strength icons?
[13:13] <asac> no its a wishlist upstream
[13:13] <asac> for 3g
[13:13] <mac_v> lool: no , no bug yet , since asac is oscillating  ;)
[13:13] <asac> mac_v: so we are using colored icons for wired too?
[13:13] <asac> should be pretty much the same
[13:13] <asac> wired -> tray vs. app == wwan -> tray vs. app
[13:14] <mac_v> asac: no  , no colored for wired... i have hacked them ,as a i mentioned earlier 16/22/24px
[13:14] <asac> yeah. same hack should work for wwan too?
[13:14] <mat_t> asac: FATAL: Module not found
[13:15] <mac_v> asac: it should... but i was hoping you'd get new icon names ;p
[13:15]  * mat_t feels he's in Mortal Kombat
[13:15] <mac_v> lol
[13:15] <asac> mat_t: yeah... install linux-restricted-modules  ... not sure why jockey doesnt pull that in for you.
[13:15] <asac> pitti: ^^
[13:15] <mat_t> asac: ok, thx!
[13:15] <asac> pitti: he is using mini 9 (or 10?) ... and linux-restricted-modules is not installed
[13:15] <mat_t> pitti: Finish Him!
[13:15] <asac> even though he needs "wl" (i would think)
[13:16] <asac> pitti: is that missing device id?
[13:16] <asac> mat_t: thats UNR or plain karmic?
[13:16] <mat_t> plain K
[13:16] <asac> mat_t: check if installing the package from above helps
[13:16] <mat_t> asac: fresh install with all updates
[13:16] <mat_t> ok
[13:16] <asac> yeah
[13:18] <asac> mac_v: point is ... even if we get signal strenght we wont use that for devices that dont support it so we still need the wwan hack
[13:18] <mat_t> asac: it's telling me there's no such package 0_o
[13:18] <mac_v> asac: i thought : linux-restricted-modules is deprecated in favour of DKMS packages.
[13:18] <asac> mat_t: linux-restricted-modules-generic
[13:18] <mat_t> ok
[13:18] <asac> no clue ;)
[13:18]  * mat_t tries
[13:19] <asac> maybe its really shipped somewhere else.
[13:19] <mac_v> asac: argh!... so , symlink then for wwan to nm-signal-100 ;p since its gonna be the same icon ;)
[13:19] <asac> mac_v: nm-signal-100 -> wifi
[13:20] <asac> idea was to not put any color in the "none siganl wwan"
[13:20] <asac> but since you dont use any color at all i dont know
[13:20] <mac_v> asac: the nm-device-wireless is a color icon
[13:20] <asac> the icon lool posted looks a bit too similar to wireless imo
[13:20] <asac> the tower is there, but not big enough
[13:21] <asac> my suggestion was the tower in high color ... just with different count of rings
[13:21] <asac> mac_v: using the same icon for wwan and wifi is wrong
[13:21] <asac> http://people.canonical.com/~lool/nm-device-wwan.svg
[13:21] <asac> thats the one lool posted ... its != wifi ... but the diff is not really recognizable for teh untrained eyes imo
[13:21] <mac_v> asac: could you do one thing... check out $bzr branch lp:humanity and suggest something
[13:22] <asac> mac_v: the icon from above is from that branch afaik
[13:22] <asac> 14:21 < asac> http://people.canonical.com/~lool/nm-device-wwan.svg
[13:22] <mac_v> asac: yeah , ok
[13:22] <mac_v> asac: but when the lock is overlayed  , this is the only possible difference that can be done
[13:23] <mac_v> asac: mat_t suggests to use the same icon for both wwan and wifi
[13:23] <asac> mac_v: there is no lock for wwan ... only technology (the letters U, G, E, H)
[13:23] <pitti> asac, mat_t: l-r-m is gone; what are you trying to do?
[13:23] <asac> pitti: wl driver is not there for him
[13:23] <asac> pitti: which was in restricted in the past
[13:24] <asac> not sure where its now
[13:24] <pitti> bcmwl-kernel-source nowadays
[13:24] <mac_v> asac: even for that overlay , we need separate space , since we are using greyscale icons
[13:24] <asac> pitti: ok. if thats not installed its a jockey bug?
[13:24] <seb128> pitti, ArneGoetje: do you know about recent languagepack breakages?
[13:25] <asac> mat_t: bcmwl-kernel-source install this then
[13:25] <lool> asac: I'd like to close humanity issues relatively fast; we're way too late for icon theme updates IMO, so a simple to implement solution would be great
[13:25] <mat_t> asac: thanks!
[13:25] <lool> We can get nicer icons in lucid and give more thoughts to the visuals
[13:25] <mac_v> mat_t: asac: the both of you decide what needs to be done... for the wireless / wwan icons ;)
[13:25] <pitti> mat_t: jockey does not list the driver for you? If not, please do "ubuntu-bug jockey-gtk" and point me to the number (this will collect all the info I'm interested in)
[13:25] <asac> lool: right. but having a wwan icon == wifi is  wrong
[13:25] <asac> mac_v: use the current hicolor wwan icon
[13:25] <asac> make it beautiful and thats find
[13:26] <asac> fine
[13:26] <pitti> seb128: bug 442742 ?
[13:26] <mat_t> mac_v: ok, can we wait with that decision till tomorrow? We'll be discussing it today
[13:26] <asac> ok
[13:26] <mat_t> pitti: ok
[13:26] <mac_v> mat_t: lool wants to update this in Ubuntu... so i'll leave it as is for now , and we can decide before next update
[13:27] <asac> mat_t: imo the currently suggested wwan icon doesnt make it because its too similar to wifi: http://people.canonical.com/~lool/nm-device-wwan.svg
[13:27] <lool> mat_t: Please, no delaying anymore
[13:27] <asac> mat_t: /usr/share/icons/hicolor/22x22/apps/nm-device-wwan.png ... that should be used
[13:27] <asac> as a .svg
[13:27] <mac_v> asac: as i said , since it is greyscale , we can not do it similar to the icons kwwii had done , we can not do an overlay E ,H ,G
[13:28] <asac> and if we need signal strength it can just have more/less rings later
[13:28] <seb128> pitti, yes
[13:28] <mac_v> and make it visible
[13:28] <pitti> seb128: on my list of things to look at; I have a suspicion, but need to confirm
[13:28] <seb128> pitti, I know about the bug I was just wondering if somebody is working on it
[13:28] <seb128> pitti, ok thanks
[13:28] <mat_t> asac: do you know what users will find this information valuable (difference between wwan and wifi)? Is this something that would affect casual folks in any way?
[13:28] <asac> mac_v: if it helps, please ignore all the signal strength and technology features i mentioned.
[13:29] <lool> mac_v: Please keep it simple to get it done faster
[13:29] <mac_v> asac: without the E , G , H ... you mean?
[13:29] <asac> mac_v: yes. you want to know if you are on wifi/wlanb
[13:29] <seb128> pitti, should it be assigned to somebody or should we add a comment saying that somebody will look at the issue?
[13:29] <asac> mac_v: yes. ignore all that. i will push that back upstream
[13:29] <asac> we will have that in lucid
[13:29] <mac_v> asac: ok
[13:29] <pitti> seb128: what, the langpack issue? I will
[13:29] <seb128> pitti, yes, thanks
[13:30] <seb128> pitti, we got several random bugs on different applications which seem dup of this one
[13:30] <seb128> hey pedro_
[13:30] <mac_v> asac: so you are sure  , there will be no lock icon overlay? because mat_t showed me that the lock overlay is used for wwan too
[13:30] <asac> mat_t: so if installing that helps please do what pitti suggested so we can add your device id to the jockey package
[13:30] <asac> mac_v: the lock icon overlay is used, but only for vpn.
[13:31] <asac> not the one used by wifi
[13:31] <mac_v> let me get you the image
[13:31] <pedro_> bonjour seb128
[13:31] <asac> e.g. wifi == can have two locks -> encryption lock (top left), vpn lock (bottom right)
[13:31] <mat_t> asac: doing it right now
[13:31] <asac> everything else can have vpn lock ...
[13:31] <pitti> mat_t: do you have the "bcmwl-modaliases" package installed?
[13:31] <pitti> asac: ^ that's where the aliases are, FYI (they aren't hardcoded in jockey)
[13:31] <mat_t> pitti: #44306
[13:31] <mat_t> sorry
[13:32] <mat_t> #443062
[13:32] <asac> k
[13:33] <mat_t> pitti: I do
[13:34] <mac_v> asac: http://launchpadlibrarian.net/32742972/Wireless-icons.png , see the lock is used in the drop down menu too , for encrypted [apart from vpn]... so this is the best we can do ,
[13:34] <mac_v> for wwan^
[13:35] <mac_v> previously i have the tower taller for wwan :/
[13:35] <asac> mac_v: there is no wwan on that screen at all
[13:35] <asac> its all wireless
[13:35] <asac> aka wifi
[13:35] <mac_v> asac: the ubuntu-battersea , that was the wwan icon when mat_t took the snapshot , it had the taller tower
[13:35] <asac> the one for "ubuntu-Lambeth" should just be the same like "Ubuntu"
[13:36] <asac> mac_v: thats all wifiu
[13:36] <asac> wifi
[13:36] <mac_v> asac: no... that was the wwan icon :(
[13:36] <asac> well. it might be that that was the wwan icon
[13:36] <asac> but its never used with that lock
[13:36] <asac> thats an artificially crafted thing
[13:36] <asac> wwan entries in the menu will not even have an icon
[13:37] <mac_v> asac: i dont think mat_t crafter it ;p
[13:37] <asac> then that was a theme bug
[13:37] <asac> the screenshot clearly shows only WIFI entries
[13:37] <mac_v> asac: i dont have a wwan nearby , so i cant test it myself :(
[13:37] <asac> no sign of any 3g
[13:37] <asac> mac_v: wwan nearby?
[13:38] <asac> wwan doesnt need to be nearby
[13:38] <asac> thats the whole idea
[13:38] <mac_v> in my area*
[13:38] <asac> wwan is something completely different
[13:38] <asac> believe me
[13:38] <asac> that screen is not wwan
[13:38] <mac_v> just a sec
[13:38] <asac> its a mixup of icons for wifi i am sure
[13:38] <pitti> mat_t: replied
[13:39] <mat_t> pitti: ok
[13:39] <seb128> mac_v, hey
[13:39] <asac> mac_v: this is a old screen ... but see the "Mobile Broadband" http://people.canonical.com/~asac/nm08-applet/gsm-connected2.png
[13:39] <mac_v> asac: the icon you see in mat_t's screenshot , was the icon i did for wwan specifically, i used a taller tower since you had mentiond , but seeing that it overlaks the lock for that icon too , i reduced the size and made a different tower
[13:39] <seb128> mac_v, bug #421695 can you look to the recent comment?
[13:40] <asac> mac_v: yes. but that icon will never be overlayed with the lock that is in the screenshot
[13:40] <asac> its clearly a crafted thing
[13:40] <mac_v> asac: then how did mat_t get the screenshot... you have to ask mat_t ...
[13:41] <asac> i dont know. he might have replaced the FULL signal wifi icon
[13:41] <asac> to test
[13:42] <mac_v> asac: he didnt realize the icon was a wwan icon , i recognized and changed it > Bug #439261
[13:42] <mac_v> mat_t: ^
[13:42] <asac> imo the icon i showed you made by kwwii for upstream is the right approach
[13:42] <asac> whatever you do with the tower on left side it will be too similar
[13:42] <asac> at least thats my guess
[13:42] <mac_v> asac: yes , but using greyscale we cant do it :(
[13:42] <asac> but i am not an artist
[13:43] <asac> mac_v: the only reason we needed colors there is because we didnt have 5 stages ... maybe you can make zero, one, two, three, three-strong-lined
[13:44] <asac> 4 stages actually
[13:44] <mac_v> asac: what stages? i dont understand? you mean signal strengths?
[13:44] <asac> yes
[13:44] <mac_v> ah
[13:45] <asac> or zero, one, two, three lines ... and three lines with strong middle point of tower
[13:45] <asac> there must be some way ;)
[13:45] <mac_v> asac: but what about the bug mat_t reports? where there is the lock overlayed for encrypted?
[13:46] <mat_t> asac: surely 4 steps is enough, no?
[13:46] <mat_t> 0, weak, med, strong, full
[13:46] <asac> current code uses 5 ... but i think we can live with 4
[13:47] <asac> e.g. current code == in some patch we had in the past for a custom image
[13:47] <mat_t> asac: uhm
[13:47] <mac_v> asac: thats the main problem , the lock overlay for encryption.. and also for vpn lock , so that tiny area is all we can use for a tower :(
[13:47] <asac> for wwan there is no lock for encryption
[13:47] <asac> only the vpn lock
[13:47] <asac> but that must work with _all_ device types
[13:47] <mat_t> pitti: ok, so I installed the kernel package, how do I make my wireless work again? :)
[13:48] <pitti> mat_t: did jockey display it after apt-get update?
[13:49] <mac_v> other wise the tower can be one the other side , right and the signals on the left :/
[13:49] <mac_v> asac: but that wouldnt look good :(
[13:49] <pitti> mat_t: You can reboot, or I can give you a sequence of commands which should enable it on the fly (what jockey does); what do you prefer?
[13:50] <mat_t> pitti: reboot will mean less work for both of us ;)
[13:50] <mac_v> asac: the vpn lock is the same as the encryption lock...
[13:50] <asac> it cant be the same
[13:50] <asac> it must be at the bottom right corner
[13:50] <asac> and your theme must look ok with that
[13:51] <mac_v> asac: that cant be done , since the lock must be separate from the icon ,,we cant keep lock at the bottom.. previously i had a key for encryption... mat_t didnt like it and had it reverted to lock
[13:51] <asac> mac_v: so the vpn overlay will only be in tray
[13:51] <mat_t> pitti: aah, great. Works now.
[13:51] <asac> not in the menu
[13:51] <mat_t> pitti: thank!
[13:51] <mat_t> s!
[13:51] <mac_v> asac: yup
[13:51] <asac> maybe its smartest to keep the lock golden
[13:52] <mac_v> hehe ;)
[13:52] <asac> well. better than having some indistinct sauce
[13:52] <mac_v> asac: but UX ,wants panel icon greyscale... so its a small price to pay
[13:53] <mat_t> mac_v: the problem now is that the icons are back to pale grey
[13:53] <asac> price == to not display that you are connected to VPN? thats rather expensive price
[13:53] <mac_v> mat_t: huh? the icons havent yet been updated :/
[13:53] <mat_t> mac_v: I've got a fresh install here
[13:54] <mac_v> mat_t: those are the old icons , it hasnt yet been updated
[13:54]  * mac_v points mat_t to lool  ;)
[13:54] <mat_t> mac_v: ok, before any update, we need to see what the changes will be. Mark saw the current icons and wasn't happy at all
[13:54] <mat_t> which didn't surprise me :)
[13:55] <mac_v> mat_t: i cant do anything when no one updates the icons :/ so who ever is unhappy its not my fault... all i can do is correct them
[13:56] <mat_t> mac_v:  sure, it's not your fault - we just need to structure the approach a bit :)
[13:56] <pitti> anyone on current karmic, if you close your lid (suspend) and reopen, do you get right back into the session or to the screensaver lock dialog?
[13:56]  * mat_t tries
[13:57] <mat_t> pitti: ss lock
[13:57] <pitti> mat_t: thanks; works for me as well
[13:57] <mat_t> :)
[13:59] <mat_t> mac_v: ok, so for now the only change that should happen is to make the icons darker. Then we'll move from there.
[13:59] <mat_t> We need to address one issue at a time
[13:59] <seb128> pitti, the "suspend after n minute inactive" is said to be buddy according to user comments
[13:59] <mac_v> mat_t: its already done... pls talk to lool  , he needs to update them
[14:00] <seb128> pitti, other cases should lock screen correctly now
[14:00] <mat_t> mac_v: cool, thanks :)
[14:00] <pitti> seb128: the latest response (Bart) said it wouldn't lock for him after lid opening; I asked him for further info
[14:00] <seb128> pitti, oh ok, that one is probably an user config issue
[14:02]  * mat_t goes back to his other work...
[14:05] <lool> mat_t: The update is pending in my PPA
[14:06] <lool> mat_t: If anything else needs updating, please point me at a patch to include; I'm not taking a wholesale update from lp:humanity anymore
[14:06] <lool> mat_t: See my email to ubuntu-devel from this WE for instructions
[14:08] <mat_t> lool: that's cool. The problem we were having is that we didn't know what the update is going to include. Since we'll be held responsible as a team, we need to know
[14:08] <lool> mac_v: If the updates are in my PPA or in 0.4.1, please consider pointing people at that instead of pointing them at me  :-)
[14:09] <lool> mat_t: I don't know whether your stuff is in it either
[14:09] <mac_v> lool: fixed the bluetooth issue Amaranth reported also... i'm not changing anything else until there are bug reports
[14:09] <lool> mat_t: What I can tell you is that the last upstream snapshot I took is 0.4.1 with over 100 revs since the previous one; I couldn't review them all, which is why it's not in karmic yet
[14:09] <mac_v> lool: they are the updates in ppa and 0.4.1 ;)
[14:09] <lool> mac_v: Where can I get it?
[14:10] <mac_v> lool: just pushed the latest rev
[14:10] <mac_v> lool: only the bluetooth disabled icons are changed
[14:11] <mat_t> lool: ok, let's go with the update and we'll go from there. Any future changes to stuff like panel icons we need to know about in advance.
[14:11] <mat_t> mac_v: ^
[14:11] <Amaranth> james_w: What's a sponsor check? You need mvo to ack the change?
[14:11] <lool> mat_t: Yeah I need to know too
[14:11] <mat_t> :)
[14:11] <Amaranth> (removing compiz-fusion-plugins-unsupported)
[14:11] <mac_v> seb128: hi... sorry for the late response about the accessories icon... hmm... ok , sounds good
[14:11] <james_w> Amaranth: you are not a MOTU, so sponsoring is required
[14:12] <seb128> mac_v, ie we can keep what we have now?
[14:12] <mat_t> thanks lool
[14:12] <james_w> Amaranth: I realise that it seems a bit redundant here, but I'd rather stick to the process
[14:12] <Amaranth> hehe
[14:12] <mac_v> seb128: i dont see , why not. sounds reasonable
[14:12] <lool> mat_t: The plan is 0.4.1 + zoom icons + bluetooth disabled icon + fixed index.themes
[14:12] <Amaranth> mvo: can you comment on bug 440731?
[14:12] <seb128> mac_v, ok thanks
[14:12] <lool> mat_t: 0.4.1 includes a load of updates from last week and the new humanity-dark
[14:13] <mat_t> lool: ok
[14:13] <lool> mat_t: You can try it out in my ppa, except for bluetooth-disabled
[14:13] <mat_t> lool, what's your ppa?
[14:13] <lool> asac, mac_v: So is anything pending for wwan/wireless?
[14:13] <lool> mat_t: ppa:lool/ppa
[14:13] <mat_t> thx
[14:14] <mat_t> pitti: still getting a system beep on battery low 0_o
[14:14] <mac_v> lool: wwan and wireless i'm not changing... since asac mentions there wont be a lock but mat_t shows screenshots with a lock... so unless there are bug reports + screenshots .. not changing stuff without knowing the problem ... its literally groping in the dark :)
[14:15] <mvo> Amaranth: in a call currently, but I will do that
[14:15] <mat_t> mac_v: ok
[14:15] <Amaranth> mvo: alright, thanks
[14:15] <pitti> mat_t: is that done from the BIOS?
[14:16] <mat_t> pitti: no idea, how do I check?
[14:16] <pitti> there might be a setting in the bios setup?
[14:16] <mat_t> pitti: I haven't changed anything in bios since Jaunty
[14:16] <lool> asac: ^ see mac_v's comment; let me know if you need a humanity-icon-theme update to close such a bug
[14:16] <pitti> mat_t: and you didn't get the sound in jaunty?
[14:17] <mat_t> pitti: nope, neither in Hardy
[14:17] <mat_t> which was preinstalled
[14:17] <pitti> hm; I have absolutely no idea about that, I'm afraid
[14:17] <mat_t> hm, ok
[14:17] <Amaranth> maybe we're using a part of the BIOS we weren't before?
[14:17] <mat_t> would be good if someone could confirm the bug
[14:17] <pitti> we need strace for sound
[14:18] <lool> mac_v: Just FYI, the zoom icons are barely visble with Dust
[14:18] <pitti> but without pcspk nor snd_pcsp I wouldn't know what else could produce beeps
[14:18] <lool> mac_v, mat_t: Just pushed humanity-icon-theme 0.4.1-0ubuntu1~dooz4 with all planned changes to my PPA
[14:19] <Amaranth> I think be the end of the week 30 bugs will be fixed in compiz :)
[14:19] <pitti> Amaranth: you rock
[14:19] <mat_t> thanks lool
[14:19] <Amaranth> no no, only something like 8 of them are me
[14:19]  * mvo hugs Amaranth
[14:19] <mac_v> lool: just out of curiosity whats "~dooz4" supposed to mean ;)
[14:22] <lool> mac_v: ~ is used to make sure people update to the karmic version when it appears; dooz is just a random string to not collide with ubuntu version numbers or other PPAs
[14:22] <lool> digit is revision
[14:23] <mac_v> lool: yeah the ~ i knew.... lol , i thought "dooz4" was short for something
[14:24] <lool> It's just my domain name
[14:24] <asac> lool: we need a humanity update as the current wwan icon == wifi icon. mac_v said he changed that already (like the svg you posted)
[14:25] <asac> but its not complete. mac_v still has to put the greyscale hack in there similar to what he did for wired
[14:25] <mvo> Amaranth: a snapshot is needed, right? to get the full-fixes-love
[14:25] <asac> besides from that i am out of this discussion
[14:26] <Amaranth> mvo: yeah just the stuff in bzr will fix 6 bugs but a new snapshot (of every part, not just core) will fix 14 more
[14:26] <Amaranth> then I have another packaging fix but I've screwed up my bzr repo :P
[14:26] <asac> lool: so yes. at least we need to cherry pick the current wwan changes.
[14:26] <asac> its currently  (as in archive) the same icon, which is unacceptable
[14:27] <mvo> Amaranth: do you have some bugnumbers to add to the changelog? git log seems to not inlcude them :/
[14:27] <mac_v> asac: mat_t explicitly told me not to make the icons look very different... so i dont know what to do :(
[14:28] <Amaranth> mvo: We've been marking them :)
[14:28] <Amaranth> one second, giant launchpad URL
[14:29] <lool> asac: Could you check the package in my PPA and tell me if anything is missing it?
[14:29] <asac> mac_v: well. as long as it is different its ok (even though i dont like it). but current karmic theme uses the same as nm-signal-100
[14:29] <Amaranth> mvo: https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bugs?field.status:list=INPROGRESS
[14:29] <lool> +in
[14:29] <Amaranth> mvo: everything fixed upstream is marked In Progress and has a link to the git commit that fixed it
[14:29] <mac_v> asac: that will change ;)
[14:30] <asac> lool: your theme package is still not build. i will check after __late__ lunch ... which i am going to do now
[14:32] <lool> asac: the previous build is ok
[14:32] <lool> asac: good lunch
[14:32] <mac_v> lool: i see the zoom problem with dust , we can fix it later with the next batch of bugs ;)
[14:34] <lool> mac_v: Well I don't intend to roll a bunch of humanity-icon-theme uploads
[14:34] <lool> In fact I only intend to roll one unless more serious issues popup
[14:34] <lool> So if you like to fix them, I can consider merging that now or later today
[14:34] <mac_v> lool: i thought you pushed the upload just now? if you didnt i can fix the zoom now itself
[14:34] <lool> mac_v: I pushed to my PPA
[14:34] <lool> Not to karmic
[14:34] <mac_v> lool: oh ok
[14:35] <mvo> Amaranth: I commited the changelog that closes all the bugs testing now
[14:36] <Amaranth> mvo: alright, cool
[14:36] <lool> mac_v: There's a slight conflict between your use of bug states and mine
[14:36] <mac_v> lool: example?
[14:36] <lool> mac_v: I see you made a bunch of bugs in humanity-icon-theme (the source package in ubuntu) fix committed
[14:37] <lool> But you did that when the changes were committed in bzr
[14:37] <mac_v> lool: yup , i thought that was the right way
[14:37] <mac_v> once fixed upstream , mark as committed right?
[14:37] <lool> mac_v: Well you should mark them as fix committed in the _upstream project_ instead
[14:38] <lool> mac_v: That is: click Also affects project, select Humanity, and mark is fix committed there
[14:38] <mac_v> :)
[14:38] <lool> mac_v: When you release a humanity tarball, mark all the fix committed bugs there as fix released
[14:38] <lool> fix committed/fix released in ubuntu is for packagers
[14:38] <mac_v> lool: hmm... oh ok
[14:39] <lool> mac_v: You dont need to do it for all bugs
[14:39] <lool> mac_v: I mean, what the packagers need is a list of bugs fixed in your lastest tarball since the previous one
[14:39] <lool> But I dont care whehter there's an upstream task on all of the ubuntu bugs
[14:39] <mac_v> lool: yeah , got it
[14:40] <lool> (And vice-versa: pretty much all upstream bugs are ubuntu bugs but they shouldn't be copied all the time)
[14:40] <lool> mac_v: Cool thanks
[14:40] <lool> mac_v: Do you know about bzr commit --fixes
[14:40] <lool> mac_v: You can mark a bug as fixed in bzr with it, and that will link the bug to the bzr branch where it's fixed
[14:40] <mac_v> lool: i use commit but havent used --fixes
[14:40] <mvo> Amaranth: anything else I should wait for? looks ready to me
[14:41] <lool> mac_v: e.g. bzr commit -m 'Fix bluetooth disabled icon' --fixes lp:1234
[14:41] <lool> mac_v: That's just nice tohave
[14:41] <Amaranth> mvo: nah, we've got the really awesome bits already
[14:41] <mac_v> lool: oh ok... i usually just do > bzr commit -m 'Fix bluetooth disabled icon"   but didnt know about fixes... nice to know thanks :)
[14:41] <Amaranth> mvo: from this point on I suspect it'll just be polish unless someone figures out the windows not redrawing sometimes thing
[14:42] <mac_v> lool: should it be lp:#1234 or just lp:1234
[14:42] <Amaranth> mvo: have to get a FFe though, right?
[14:42] <mvo> Amaranth: no, should not be needed, its strictly fixes AFAICS in the diff
[14:43] <huats> Helo everyone !
[14:43] <Amaranth> mvo: yeah
[14:43] <lool> mac_v: I think the latter works, not sure about former
[14:43] <Amaranth> people who use projectors won't want to kill me anymore, I'm happy :)
[14:43] <ara> hello guys
[14:43] <ara> in latest karmic images, if live is started in Spanish (or karmic is installed in Spanish), the ubuntu main menu appears in Engilsh (Applications, Places, System). The rest (including submenus of those) appear correctly in Spanish. Is that known? If not, which package should i be filling a bug against?
[14:43] <mac_v> lool: ok thanks :)
[14:44] <pedro_> ara, bug 442742
[14:44] <ara> pedro_, gracias :)
[14:44] <pedro_> ara, por nada ;-)
[14:45] <Amaranth> Hey I know what that means :)
[14:45] <Amaranth> (that's about it though)
[14:45] <pedro_> heh hey Amaranth
[14:45] <Amaranth> howdy
[14:49] <seb128> asac, will you do the gnome-bluetooth 2.28.1 update?
[14:52] <superm1> mac_v, did you even review my patch?
[14:53] <mac_v> superm1: i saw the patch , but for Ubuntu , it is not required
[14:53] <superm1> and don't you see a difference in now a "priority" to work on something (its wishlist for the project)?
[14:54] <superm1> i wrote a patch, and although it isn't needed for the default situation, but the work is done for the situation it would be needed
[14:54] <mac_v> superm1: it can be filed against Xubuntu or Mythbuntu , but not in ubuntu
[14:54] <superm1> *we use the ubuntu archive*
[14:54] <mac_v> superm1: then you'd have to ask mvo
[14:55] <mac_v> superm1: sorry for the confusion then :)
[14:55] <superm1> mvo, would you be able to review said patch then?
[14:55] <Amaranth> mvo does too much, I think :)
[14:55] <mvo> superm1: what is the bug number again
[14:55] <mvo> Amaranth: my SO thinks the same :)
[14:56] <superm1> mvo, bug 442717
[14:58] <mvo> superm1: looking now
[15:00] <Amaranth> superm1: I would think you would want update-notifier to stand out very much
[15:00] <mvo> superm1: thanks, looks good - technically it needs a UI freeze exception for this, at least for mythubuntu and xubuntu (not sure who else disables auto-open mode)
[15:00] <Amaranth> superm1: We don't use it anymore because it doesn't say "hey! look at me!" enough but you seem to want to make it say that even less :)
[15:01] <superm1> mvo, afaik it's just us and xubuntu.  i'm the POC for mythbuntu changes.  i'll check with cody on xubuntu make sure he's cool with it
[15:02] <ccheney> Amaranth: longer for unpacking, heh
[15:02] <Amaranth> ccheney: oh, of course
[15:03] <Amaranth> ccheney: If you're completely unpacked in less than a month I'll be surprised :)
[15:03] <Amaranth> But that's less important really
[15:03] <mvo> superm1: great, thanks. if cody is ok I'm happy to upload it
[15:03] <superm1> mvo, k
[15:03] <Amaranth> I use moving as a chance to figure out how much I really use something. If it doesn't get unpacked after a month and it isn't something I need to hold on to (memories, legal stuff, etc) it gets tossed
[15:04] <ccheney> Amaranth: yea i told my wife we are going to sort everything as it is unpacked and throw out useless stuff
[15:04]  * ccheney thinks probably about 25% of the stuff (at least) is useless
[15:05] <Amaranth> Every time I move 25% of my stuff is useless :P
[15:05] <ccheney> we managed to fill the entire entry way and dining room with bags of stuff, we moved most of it ourselves so didn't use the large boxes, just grocery bags
[15:05] <ccheney> Amaranth: move a few more times then :)
[15:06] <Amaranth> ccheney: I'm down to barely enough stuff to make an apartment lived in :P
[15:06] <ccheney> Amaranth: hehe :)
[15:08] <asac> seb128: yes.
[15:08] <seb128> asac, thanks
[15:08] <asac> seb128: i have to fix something on packaging side too
[15:09] <asac> ok back to lunch for a few more minutes ;)
[15:11] <mvo> Amaranth: compiz is uploaded, I have not updated the plugin and libcompizconfig stuff yet, maybe I wait for robert for that
[15:12] <mvo> need to attack some software-center bugs too
[15:12] <Amaranth> mvo: alright
[15:12] <Amaranth> mvo: can you comment on that -upsupported package bug real quick?
[15:12] <Amaranth> err, -unsupported
[15:12] <mvo> Amaranth: sure, sorry
[15:14] <mvo> Amaranth: I assume #compiz-dev is cool with that request?
[15:14] <mvo> Amaranth: if its doing more harm than good, I'm fine with removing it
[15:14] <Amaranth> mvo: the name of the package should make their stance clear ;)
[15:14] <mvo> :)
[15:14] <mvo> commented
[15:28] <Amaranth> arg
[15:28] <Amaranth> defaulting to NO_NEW_FAIR_SLEEPERS apparently causes some pretty bad problems
[15:28] <Amaranth> probably applications that fork and expect their child to finish before they run again
[15:43] <slomo> seb128: were there any gstreamer related bugs related to decoding something already? :)
[15:43] <mvo> mpt_: what is your prefered way if I want your input on a certain software-center bug - subscribe you? ping you here? I'm currently looking at #442992
[15:43] <mvo> mpt_: but there will be more, I'm sure :)
[15:45] <mpt_> mvo, looking
[15:45] <seb128> slomo, nothing obviously due to the recent change no, nor really issue
[15:45] <mac_v> lool: hi , pushed the zoom icons edit , they will now be visible in Dust theme too
[15:45] <mpt_> mvo, huh, I never realized that
[15:45] <seb128> slomo, there is quite some bugs about mkv not playing and subtitle issues though
[15:46] <mvo> mpt_: I thought we talked about it
[15:46] <Amaranth> dang, compiz FTBFS on armel
[15:46] <mvo> mpt_: we have the option to sort by popularity, relevance of the result (or what xapian thinks about this ;) or alphabetic
[15:46] <mpt_> mvo, what do you think of sorting the results alphabetically for now?
[15:47] <rodrigo_> kenvandine: ping me when you're in, please
[15:47] <slomo> seb128: are those mkv/subtitle bugs new? could you give me some urls? :)
[15:48] <kenvandine> hey rodrigo_
[15:48] <kenvandine> what
[15:48] <kenvandine> 's up?
[15:48] <rodrigo_> hey kenvandine
[15:48] <seb128> slomo, https://bugzilla.gnome.org/show_bug.cgi?id=591706
[15:48] <rodrigo_> kenvandine: oh, just saw on FB you're sick, are you?
[15:48] <mpt_> mvo, but then, in <https://wiki.ubuntu.com/SoftwareCenter#Search keyword greylist> I've suggested that greylisted words should affect sort order of results ... hmmmm
[15:49] <kenvandine> sort of... but working
[15:49] <pitti> hey kenvandine
[15:49] <kenvandine> hey pitti
[15:49] <pitti> kenvandine: oh, get well soon!
[15:49] <mvo> mpt_: it will have funny results as well, if someone search for something like "zip" (bad example) then the sorting will be funny
[15:49] <kenvandine> pitti, caught h1n1 from my daughter :/
[15:49] <seb128> slomo, https://bugs.edge.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/426421
[15:49] <mpt_> mvo, make that <https://wiki.ubuntu.com/SoftwareCenter#Search%20keyword%20greylist> :-)
[15:49] <rodrigo_> kenvandine: ah, ok, don't want to give you more work, but I just wanted to tell you about 2 bugs (with branches submitted for merging) that need to get into karmic
[15:49] <kenvandine> so not feeling terrible... but super contageous
[15:49] <mvo> mpt_: or anything where the most appropriate result starts with a char from the end of the alphabet
[15:49] <slomo> seb128: thanks
[15:49] <pitti> kenvandine: so that's your immunization strategy? :-)
[15:49] <mpt_> mvo, "funny" in what way?
[15:49] <rodrigo_> kenvandine: statik told me to poke you, so let me know if I should poke someone else
[15:49] <kenvandine> hehe
[15:49] <kenvandine> i guess so
[15:50] <kenvandine> sure
[15:50] <kenvandine> rodrigo_, are they in the sponsor queue?
[15:50] <pitti> kenvandine: if it's any consolation, the normal flu is said to be much worse..
[15:50] <kenvandine> pitti, yeah, i know
[15:50] <kenvandine> and i got that shot :)
[15:50] <rodrigo_> kenvandine: I think so, pitti approved the nomination
[15:50] <kenvandine> but the vaccine for h1n1 isn't available yet... so now i got it
[15:50] <kenvandine> rodrigo_, bug numbers?
[15:51]  * kenvandine assumes one of them is tomboy
[15:51] <rodrigo_> kenvandine: https://bugs.edge.launchpad.net/ubuntuone-servers/+bug/435904 and https://bugs.edge.launchpad.net/evolution-couchdb/+bug/415297
[15:51] <rodrigo_> kenvandine: yes, and the other is couchdb-glib/evo-couchdb
[15:51] <Amaranth> oh, compiz build failure is bonobo failure
[15:51] <Amaranth> dpkg: error processing /var/cache/apt/archives/libbonoboui2-dev_2.24.1-1ubuntu1_armel.deb (--unpack):
[15:51] <Amaranth>  trying to overwrite '/usr/share/gtk-doc/html/libbonoboui', which is also in package libbonoboui2-common 0:2.24.2-1ubuntu1
[15:52] <mvo> mpt_: well, unexpected, say you search for something that starts with "z" - when you get a couple of hits, it may well be down the list (not even on the screen)
[15:52] <seb128> Amaranth, when did you get that and where?
[15:52] <kenvandine> pitti, both of those bugs rodrigo_ mentioned were marked as fix commited by you on the 30th
[15:52] <Amaranth> seb128: armel buildd got that while building compiz
[15:52] <slomo> seb128: ok, the first one is a known problem :)
[15:53] <kenvandine> but not uploaded yet?
[15:53] <mvo> mpt_: I don't have a good example word at this point, but I think you get the idea? a solution would be list headings to change the sorting, but we don't have those
[15:53] <slomo> seb128: second one could be, that no video decoder for that file is available for example
[15:54] <mvo> mpt_: a good example is probably "terminal" - if sorted alphabetically gnome-terminal will be way down
[15:54] <mac_v> tgpraveen: pls dont mark bugs for Humanity-UNR... ! its not a theme ;p it needs to be deleted
[15:54] <mpt_> mvo, maybe for now we should sort by xapian ordering? Then for 2.0 we could introduce column headers and a "Relevance" column etc
[15:54] <mvo> mpt_: I can do a gconf key (or something like this) so that you can play with the different sort modes
[15:55] <mac_v> tgpraveen: also , Humanity-Dark , only has icons for dark panel ;) the rest are the same icons from Humanity
[15:55] <pitti> kenvandine: hm, not really sure why I did that; please set them back to triaged if they aren't in the ubuntu packaging bzr yet
[15:55] <mvo> mpt_: ok, I will make the order configurable (under the hood) and let you play with it. I found xapian ordering not that great (because usually our data is not great, xapian makes the best of it). then you can play and see
[15:56] <tgpraveen> mac_v: oh ok
[15:56] <kenvandine> pitti, ok
[15:56] <kenvandine> rodrigo_, i will make sure they go through the right pipes :) thx for pointing them out
[15:56] <rodrigo_> kenvandine: thanks! :)
[15:56] <pedro_> kenvandine, hello, are you tracking the libindicate bugs? i've seen a few empathy crashes related to it
[15:56] <pedro_> which i've assigned to there
[15:57] <rodrigo_> hey pedro_!!
[15:57] <pedro_> hola rodrigo_!
[15:57] <pedro_> rodrigo_, when is the couch db talk?
[15:57] <rodrigo_> pedro_: still happy for the football game? :D
[15:57] <rodrigo_> pedro_: next saturday, not sure what time
[15:58] <pedro_> rodrigo_, biggest smile on my face the whole weekend, yes ;-)
[15:58] <kenvandine> pedro_, i am tracking the empathy bugs
[15:58] <kenvandine> specifically related to libindicate :)
[15:58] <rodrigo_> pedro_: yeah, you sounded really excited on FB :D
[15:58] <mpt_> mvo, are application names more heavily weighted than descriptions?
[15:58] <kenvandine> pedro_, so please feel free to assign them to me so i don't over look them
[15:58] <kenvandine> i expect to spend my afternoon working on those
[15:58] <mvo> mpt_: yes
[15:59] <mvo> mpt_: but the whole weighting is not perfect, it did not get a lot of balancing at this point
[15:59] <pedro_> kenvandine, ok great, will do it :-)
[15:59] <mvo> mpt_: name is 10x more value than description, but if the description contains it often enough...
[16:00] <mpt_> mvo, yeah, this kind of thing is hard to test. :-)
[16:02] <tgpraveen> kenvandine: did u get a chance to test muissed calls storeage in indicator?
[16:02] <seb128> slomo, looking to recent bugs there is not too many issues that I can see there
[16:02] <kenvandine> no, i don't think we can address that for karmic
[16:03] <kenvandine> too late in the cycle
[16:03] <kenvandine> tgpraveen, oh... test..
[16:03] <kenvandine> tgpraveen, no... i will test it today
[16:03] <kenvandine> i think it will stick around
[16:03] <kenvandine> but the question is what to do if the other end already hung up
[16:04] <kenvandine> i think we need to look at the work flow for answering calls for lucid
[16:04] <kenvandine> too many clicks right now for incoming calls
[16:04] <Amaranth> mvo: so from this point we're only doing cherry picking from upstream compiz stuff, right?
[16:05] <Amaranth> Hopefully in 4 days I'll be able to do it myself so I want to make sure I'm clear on this
[16:06] <Amaranth> Well, 4 days plus however long the wait it to get it all setup so... probably not for karmic I guess
[16:08] <tgpraveen> kenvandine: k. i would like to help in that . which team would be involved in that process?
[16:09] <tgpraveen> ubuntu-desktop? or something else
[16:11] <mvo> mpt_: you can test the dfferent search sortings in trunk/ if you run "SOFTWARE_CENTER_SEARCHES_SORT_MODE=xapian ./software-center"
[16:11] <mvo> mpt_: (r361)
[16:11] <mpt_> thanks mvo
[16:11] <kenvandine> tgpraveen, desktop and design
[16:13] <mvo> mpt_: music is a good word for testing
[16:13] <mpt_> ok
[16:14] <mvo> or music player etc
[16:14]  * mvo goes back to real bug fixing
[16:14] <mvo> (well, real == crash)
[16:15] <mpt_> :-)
[16:15] <lool> mac_v: Thanks; pushed in ~dooz5 to my ppa
[16:16] <mvo> and a bugreport about "free software" being used bug #442882
[16:17] <lool> eh
[16:18] <mvo> and bug #442310
[16:18] <mvo> look like I need to do triage more often, loads and loads of NEW bugs :(
[16:23] <mpt_> mvo, I'll take care of those two ;-)
[16:23] <mvo> thanks mpt_
[16:25] <and471> mvo: hi (I am rugby471 btw, changed my nick)
[16:25] <mvo> hey and471
[16:26] <and471> mvo: I have a question about software-store's translation infrastructure
[16:26] <mvo> mpt_: uh, sorry - but I need some UI love for #441961 - the issue is that the package comes from a untrusted repository (e.g. a PPA) and so "shadows" a regular package.
[16:26] <mvo> and471: sure
[16:26] <and471> mvo: in the POTFILES.in you have a list of files needed to be translated, some have a prefix of [python] et.c
[16:27] <and471> what command do you use with xgettext to get these little declarations to work, they just give errors for me
[16:27] <and471> mvo: ^
[16:29] <and471> mpt_: hi
[16:29] <mvo> intltool-extract should do that
[16:29] <mpt_> hello and471
[16:29] <mvo> the magic is all done by distutils-extra
[16:29] <and471> mvo: ah ok
[16:30] <and471> mvo: there is no command to create the .pot file?
[16:30] <mvo> and471: python setup.py build_i18n shoud do it
[16:31] <and471> mvo: thanks
[16:32] <mvo> seb128: I suppose you have no idea aobut bug #441870 ? looks scary and deep inside theads+glib+gio
[16:33] <seb128> mvo, looking
[16:34] <seb128> mvo, no, but having the retracing would be useful
[16:35] <seb128> bah, retraced crashed on "IOError: [Errno socket error] [Errno 104] Connection reset by peer"
[16:35] <seb128> restarting
[16:35] <mvo> seb128: thans
[16:42] <seb128> pedro_, the "can't click several times on a button" is a gtk bug fixed now
[16:43] <seb128> pedro_, #441905
[16:44] <pedro_> seb128, nice will point the users there then, thanks!
[16:44] <seb128> you're welcome
[16:44] <seb128> hey rickspencer3
[16:44] <rickspencer3> hi seb128
[16:44] <kenvandine> pitti, evolution-couchdb and couchdb-glib are both ready for upload, bug 415297
[16:44] <didrocks> hello rickspencer3 :)
[16:44] <rickspencer3> hi didrocks
[16:45] <kenvandine> pitti, and tomboy is ready, bug 435904
[16:46] <kenvandine> rodrigo_, any idea when the unicode issues on the server will be resolved?
[16:46] <james_w> kenvandine: hey, I'm still having trouble with couchdb as I'm unable to build it in my build chroot
[16:46]  * kenvandine would like tomboy syncing
[16:46] <kenvandine> james_w, weird
[16:46] <james_w> kenvandine: the sponsor bug is assigned to me, I guess I should fix that so it doesn't block on me?
[16:46] <kenvandine> any changes since i last touched it?
[16:46] <james_w> oh, it's not couchdb's fault
[16:47] <kenvandine> james_w, but changes since it was last uploaded?
[16:47] <kenvandine> the snapshot i was working on got uploaded
[16:48] <james_w> bug 439499
[16:49] <kenvandine> ah... i hadn't seen that
[16:52] <andreasn> asac, I apologize, but as always, I've forgotten if it's Thunderbird beta releases or daily builds who have a ppa in launchpad
[16:53] <pitti> kenvandine: looking
[16:53] <kenvandine> pitti, thx
[16:55] <asac> andreasn: daily
[16:55] <asac> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa
[16:56] <andreasn> asac, thank you, there was a issue with the default (I think) xubuntu theme, so I thought I should point the developer to 3.0
[16:56] <asac> thx
[16:56] <asac> tbird 2 wont receive any fixes in this direction - fortunately
[16:56] <asac> ;)
[16:59] <mvo> mpt: wb
[16:59] <Amaranth> wow, I think I can finally close bug 99740
[16:59] <mpt> hm, Karmic upgrade is no worky
[17:00] <mvo> mpt: oh? what is not working?
[17:00] <Amaranth> only took 2.5 years...
[17:00] <rodrigo_> kenvandine: already solved, just submitted a branch to fix it
[17:00] <mpt> mvo, just Update Manager saying it could only do a partial upgrade, then not doing anything at all because of a dependency cycle in openoffice.org
[17:01] <mvo> Amaranth: oh, what commit is  that?
[17:01] <mpt> ah, here we are: "E: Couldn't configure pre-depend openoffice.org-core for openoffice.org-filter-binfilter, probably a dependency cycle."
[17:01] <mpt> (that's from Synaptic)
[17:01] <mvo> mpt: hrm, bad - I got a report about that before :/
[17:01] <Amaranth> mvo: unredirect fullscreen windows hasn't caused that problem since before jaunty, afaik
[17:01] <mpt> mvo, as in a bug report? If not, what information should I provide when reporting it?
[17:02] <mvo> mpt: yes, there is a open bug about this
[17:03] <mvo> bug #442651
[17:04] <mpt> mvo, if I get exactly the same error in Synaptic, it's not an update-manager bug then, is it?
[17:04] <Amaranth> mvo: err, I mean legacy fullscreen support
[17:04]  * Amaranth gets more caffeine
[17:04] <mvo> mpt: its a libapt/openoffice bug, it needs some love to figure out who is the one to blame (probably both ;)
[17:05] <mpt> ok, guess I'm stuck running Ubuntu Jauntmic for now
[17:07] <Amaranth> mpt: Or just remove openoffice.org-filter-binfilter then install again after upgrading :)
[17:09] <mpt> hey, that works
[17:11] <mpt> "[/] Do you want to upgrade glibc now?"
[17:11] <mpt> W T F
[17:12] <Amaranth> mpt: Hope it doesn't segfault :)
[17:12] <Amaranth> Wait, was that a dialog?
[17:14] <mpt> Amaranth, yes, The Joys Of DebConf
[17:14] <mvo> mpt: oh? it should not ask this in gui mode :/
[17:14] <mvo> mpt: oh well
[17:14] <mvo> maybe we should get rid of it afterall...
[17:15] <mvo> and471: if you want a (hopefully) quick target, bug #439621 would be one :)
[17:15] <lool> pitti: Hey was checking the seeds and I see desktop is seeding gnome-icon-theme and not humanity-icon-theme; perhaps you want to fix that either by adding humanity or by replacing gnome-icon-theme with it?
[17:15] <and471> mvo: sorry I cannot do a lot of work now, I have to start my revision :-(
[17:15] <mpt> mvo, the best part is that it has a "Help" button that says "Running services and programs that are using WTF need to be restarted, otherwise they might not be able to do worple or flotsit any more...", and goes on like that for another couple of paragraphs, ending with "If you want to interrupt the upgrade now and continue later, please Answer No to the question below", when there is neither (a) a question below or (b) a No button
[17:16] <and471> mvo: regarding that bug, it is due to the new gtk theme I think
[17:16] <mpt> mvo, maybe that debconf prompt is coming up only because I'm using Synaptic, and wouldn't come up with update-manager?
[17:19] <mvo> and471: no problem :)
[17:19] <mvo> mpt: yeah, it should be supressed when u-m is running
[17:20] <mvo> lool: re bug #439420 - what kind of magic do I have to do to the window to make it maximize with maxiums?
[17:21] <Amaranth> lool: iirc gnome-icon-theme gets used if even hicolor doesn't have an icon, doesn't it?
[17:28] <lool> Amaranth: EPARSE
[17:28] <lool> Amaranth: The stack is Humanity > GNOME > hicolor IIRC
[17:28] <Amaranth> lool: I thought it was Humanity > hicolor > gnome because of some GTK+ trickery
[17:29]  * Amaranth tries to find email
[17:29] <seb128> Amaranth, hicolor is the fallback theme
[17:29] <seb128> gnome is used before it
[17:30] <lool> Right sorry
[17:30] <lool> Inherits=gnome,hicolor
[17:31] <Amaranth> huh, maybe I was thinking of the name fallbacks
[17:32] <lool> Well there's a gtk+ fallback too
[17:32] <lool> but it comes last IIRC
[17:32] <lool> Fallback themeis gnome
[17:33] <Amaranth> Right, so it's Humanity > gnome > hicolor > gnome...
[17:33] <Amaranth> seb128 is the one that brought this whole thing up back in 2006 (yay gmail)
[17:34] <seb128> Amaranth, by then they dropped the gnome fallback IIRC
[17:34] <Amaranth> perhaps
[17:34] <seb128> it broke the theming for everything which installed an icon in gnome when using themes not using gnome
[17:34] <lool> seb128: Dont we still have that as a debian/patches/ thing?
[17:35] <seb128> yes
[17:35] <seb128> 015_default-fallback-icon-theme.patch
[17:35] <seb128> -								  NULL,
[17:35] <seb128> +								  "gnome",
[17:35] <lool> Right
[17:35] <Amaranth> yay I'm not going crazy :)
[17:36] <seb128> Amaranth, how so?
[17:36] <Amaranth> I remembered we had that :)
[17:38] <lool> /c/
[17:39] <Amaranth> *sigh*
[17:39] <Amaranth> compiz FTBFS on every arch
[17:39] <seb128> Amaranth, I've fixed libbonoboui I will retry compiz in one hour or so
[17:39] <Amaranth> holy crap, one guy has opened the same bug 3 times because it hasn't been fixed in the last week
[17:40] <Amaranth> "We are almost in the final release and this bug still persist"
[17:40] <Amaranth> *headdesk*
[17:54] <mac_v> Amaranth: lol , bug# ?
[17:54] <Amaranth> eh, gone already
[18:33] <pitti> bye everyone, time for Taekwondo
[20:29] <yuriy> pitti: I've been debugging the apport-kde hanging problem. I think the issue may be that the common apport ui code uses sys.exit(0) which doesn't give the UI a chance to clean up properly (though I am a bit confused on that point, because I don't think it actually exits on those)
[20:29] <yuriy> pitti: not that that's causing the hang, but that it causes another crash which prevents me from fixing the hanging properly
[20:44] <yuriy> pitti: nevermind, that's not it
[21:12] <chrisccoulson> wb seb128
[21:12] <seb128> hey chrisccoulson
[21:15] <chrisccoulson> seb128 - would you mind ACK'ing bug 391664? (i think sistpoty subscribed you to it)
[21:16] <seb128> there is a newer version upstream now
[21:16] <seb128> but update ack from me it was probably in the middle of the thousand weekend emails
[21:17] <chrisccoulson> i didn't realise there was a new upstream version now
[21:17] <chrisccoulson> i only packaged 1.12.1 at the weekend ;)
[21:18] <seb128> ok, feel free to upload this one or to do the new update
[21:19] <chrisccoulson> thanks. i'll have a look at the new one later. it depends on gnome-python-extras first though
[21:26] <asac> hey ... how can i force ubuntu-bug to continue even if package is not "genuine" ?
[21:28] <dobey> asac: do the same magic we do for ubuntuone-client in the apport hook
[21:31] <seb128> asac, set APPORT_REPORT_THIRDPARTY
[21:31]  * dobey *hugs* the crashdb magic
[21:31] <asac> thx
[21:32] <asac> seb128: doesnt work :(
[21:32] <asac> o wait
[21:32] <asac> it works ;)
[21:32] <seb128> ;-)
[21:32] <asac> should be documented somewhere in ubuntu-bug :)
[21:32] <asac> manpage
[21:33] <seb128> indeed
[21:33] <seb128> or maybe it's kept secret to not have users to abuse it ;-
[21:33] <seb128> :-)
[21:33] <chrisccoulson> heh, i didn't know that existed either ;)
[21:34] <asac> comes handy if you improve your hook in a package you prepare for upload and want to test ;)
[21:34] <asac> wasted now like 15 minutes of my time ;)
[21:41] <rickspencer3_> seb128, what do you think of changing "New Session..." to "Switch User..." in Session Indicator?
[21:42] <seb128> rickspencer3_, tricking, I would be in favor of the change but translators have barely translated "New session..." now and I think it's late to break all translations again now
[21:42] <rickspencer3_> seb128, hmmm
[21:42] <rickspencer3_> well ... New Session ... doesn't make much sense, and it's an important feature
[21:43] <seb128> how come nobody woke up about that before?
[21:43] <seb128> I though that was a design decision so I didn't say anything...
[21:43] <rickspencer3_> seb128, never mind, it's already fix commited :/
[21:44] <rickspencer3_> I just need to move it out
[21:44] <seb128> fix commited?
[21:44] <seb128> we are going to break all translations now?
[21:44] <rickspencer3_> seb128, because the user list menu was rolled back
[21:44] <rickspencer3_> seb128, yes
[21:44] <chrisccoulson> i see some people are confused about how they're meant to shut down their machines now, with no power icon next to the session-applet
[21:44] <chrisccoulson> it's not obvious where to go switch the machine off any more
[21:44] <seb128> chrisccoulson, there is a bug open about that
[21:45] <chrisccoulson> i haven't seen the bug yet, but i've seen people asking how they're meant to shut down in the forums
[21:46] <rickspencer3_> chrisccoulson, yes, this is not good
[21:46] <rickspencer3_> will be hard to discover that, will have to fix it in Lucid for sure
[21:46] <chrisccoulson> yeah, it's definately confusing. i only know where it is because i use it every day ;)
[21:47] <seb128> bug #443029
[21:47] <chrisccoulson> ah, thanks :)
[21:47] <seb128> rickspencer3_, in lucid? you mean it's going to stay this way with no icon for karmic?
[21:48] <rickspencer3_> seb128, so far as I know
[21:48] <seb128> :-(
[21:48] <rickspencer3_> I'm working on it, but can't promise
[21:48] <rickspencer3_> seb128, btw, it looks like "New Session..." used to be "Switch User..." so may already be translated
[21:49] <chrisccoulson> that was the case in the old applet
[21:49] <seb128> rickspencer3_, usually when a string is dropped the translations are dropped too, ie adding it back later doesn't bring those back automagically
[21:49] <rickspencer3_> hmm
[21:49] <rickspencer3_> seb128, ok
[21:49] <rickspencer3_> well, it is what it is
[21:49] <seb128> somebody will need to fish for those
[21:49] <seb128> well, if you want to change it please do it early
[21:49] <seb128> and notify ubuntu-translators
[21:50] <rickspencer3_> seb128, right, I'm working on it as fast as I can
[21:50] <seb128> and perhaps dpm or somebody can help by reapplying jaunty strings for all locales or something
[21:50] <seb128> it should not be too complicated to do but take some time
[21:50] <rickspencer3_> kenvandine, ^
[21:51] <kenvandine> so doable
[21:51] <seb128> rickspencer3_, would be better to be somebody who knows about translations and how to push those to rosetta
[21:51] <kenvandine> yeah... not me
[21:51] <seb128> ie ArneGoetje or dpm for example
[21:51] <seb128> if they have some free slot for that...
[21:51] <rickspencer3_> right, but kenvandine will rolling out the change
[21:52] <rickspencer3_> ArneGoetje is on European time atm
[21:52] <kenvandine> rickspencer3_, i can apply the patch now or wait fora  thursday release?
[21:52] <kklimonda> chrisccoulson: can you take a look at bug 444005 in the next few days? It's nothing urgent but would be great to fix it before release.
[21:52] <rickspencer3_> kenvandine, the key thing is we need to line up translations
[21:52] <kenvandine> yeah, the patch is easy
[21:53] <kenvandine> there will be an indicator-session release on thursday
[21:53] <seb128> so
[21:53] <seb128> - get the change early in karmic
[21:53] <seb128> - email ubuntu-translators
[21:53] <seb128> - tweak rosetta to help translations to catch up if possible
[21:53] <chrisccoulson> kklimonda - yeah, i could do when i get some time
[21:53] <seb128> 3- might not be required, each translation team can probably do that and we can have a look later to the one which didn't manage to do the update
[21:55] <rickspencer3_> kenvandine, any chance you could look at https://bugs.edge.launchpad.net/ubuntu/+source/indicator-session/+bug/443029
[21:55] <rickspencer3_> why did this get hung up, and how hard would it be to fix?
[21:56] <kenvandine> humm
[21:56] <kenvandine> surely not hard to add an icon there, assuming folks agree we want to do that
[21:57] <rickspencer3_> kenvandine, ok, checking with Dx
[22:26] <SiDi> asac: hi there. i finally found out how to use that link-color... GtkWidget::link-color = "# ... "
[22:27] <SiDi> There apparently arent any side effects... i still hope they'll change firefox to use something more obvious though
[22:29] <SiDi> As for my issues in Thunderbird they seem mostly fixed in TB3, so all i need is to have some kind of workaround for it till TB2 is replaced
[22:54] <asac> /bin/bash: line 1: 21329 Aborted                 g-ir-compiler Epiphany-2.28.gir -o Epiphany-2.28.typelib
[22:54] <asac> is that a build depends issue?
[22:55] <asac> SiDi: good. does that change only the link-color for the awesome bar?
[22:57] <SiDi> asac: its the only place where it seems to be used
[22:58] <SiDi> but i had to change it for all gtkwidgets, cause this one is a GtkLabel anyway. So i made sure the color would work on white backgrounds too;
[22:58] <asac> SiDi: maybe you can use something more specific?
[22:58] <asac> not GtkWidget ... but rather GtkLabel? or so?
[22:58] <SiDi> and at least it avoids us having to patch firefox :)
[22:58] <SiDi> asac: any text using that color would be a GtkLabel anyway :)
[22:59] <asac> but why use GtkWidget then?
[22:59] <SiDi> well, for instance, if an app uses link-color for links in labels and buttons
[22:59] <SiDi> i wont be able to prevent my change from affecting this app's labels
[22:59] <SiDi> so its better if all its link look coherent
[22:59] <SiDi> and if the color works well with both bright and dark backgrounds
[22:59] <mclasen> asac: the same style property is used in labels and link buttons (and elsewhere)
[23:00] <SiDi> since i cant affect only firefox's awesome bar, i make sure to find a value that's meant to work everywhere in our theme
[23:01] <asac> SiDi: yeah
[23:01] <asac> SiDi: just wondered if it would mess the main html area
[23:01] <SiDi> nope
[23:01] <SiDi> apparently the "use system values" doesnt work with  xfce
[23:01] <SiDi> i suppose it works only with gnome, or even not at all :d
[23:01] <SiDi> and i dont think anyone ever used it anyway
[23:02] <asac> if that works its good ;)
[23:02] <asac> at best get that in all dark upstream themes somewhere
[23:02] <mac_v> rickspencer3_: kenvandine: for the shutdown icon , you also need to consider which icon to use? since the rest of the panel is greyscale icons... its better to use a greyscale one for that too
[23:02] <asac> SiDi: use system values - as i said is for the html area afaik
[23:02] <rickspencer3_> mac_v, ok
[23:02] <SiDi> asac: yeh, i meant that i didnt notice any difference in html pages with that enabled and my change setup
[23:02] <rickspencer3_> I've asked ivanka and dbarth to engage and tell us what to do
[23:02] <asac> SiDi: check out preferences -> content -> colors ...
[23:03] <asac> SiDi: there is a "Allow users to select their own colors ..." checkbox
[23:03] <asac> thats what the pref is about.
[23:03] <asac> not about the xul widgets etc.
[23:03] <asac> SiDi: err ... the checkbox above reads "use system colors" ;) ... so rather that
[23:03] <asac> but still same place
[23:04] <SiDi> asac: its the option i talk about :)
[23:04] <SiDi> s/talk/am speaking/
[23:05] <mac_v> rickspencer3_: ok.. thanks
[23:05] <mac_v> :)
[23:05] <asac> k
[23:07] <SiDi> asac: so, about thunderbird, would you accept putting my "fix" in thunderbird2's CSS, till thunderbird3 is released?
[23:08] <asac> SiDi: if that fix does not cause regressions for other themes we can check that
[23:09] <seb128> hey robert_ancell
[23:09] <robert_ancell> seb128, hey
[23:09] <seb128> had a good week end?
[23:10] <bratsche> Hi robert_ancell and seb128
[23:10] <robert_ancell> yeah, long weekends are great :)
[23:10] <robert_ancell> hi bratsche
[23:10] <seb128> hey bratsche
[23:11] <SiDi> asac: i think it should be ok with 99.9% of the themes... the last 0.01% would be unusable anyway, this thing aside :]
[23:12] <asac_> 00:07 < SiDi> asac: so, about thunderbird, would you accept putting my "fix" in thunderbird2's CSS, till thunderbird3 is released?
[23:12] <asac_> 00:08 < asac> SiDi: if that fix does not cause regressions for other themes we can check that
[23:14] <bcurtiswx> Themuso: are you available to talk about ubuntu-sounds?
[23:14] <SiDi> [00:12] <SiDi> asac: i think it should be ok with 99.9% of the themes... the last 0.01% would be unusable anyway, this thing aside :]
[23:15] <SiDi> ie, a theme designed to have diametrically opposed window backgrounds and notebooktab backgrounds could have problems with the fix, but it wouldnt work without anyway
[23:15] <SiDi> meh.
[23:16] <asac_> sorry connect issues
[23:16]  * SiDi pings asac_ 
[23:16] <asac_> 00:12 < asac_> 00:07 < SiDi> asac: so, about thunderbird, would you accept putting my "fix" in thunderbird2's CSS, till  thunderbird3 is released?
[23:16] <asac_> 00:12 < asac_> 00:08 < asac> SiDi: if that fix does not cause regressions for other themes we can check that
[23:16] <SiDi> [00:15] <SiDi> [00:12] <SiDi> asac: i think it should be ok with 99.9% of the themes... the last 0.01% would be unusable anyway, this thing aside :]
[23:16] <SiDi> [00:15] <SiDi> ie, a theme designed to have diametrically opposed window backgrounds and notebooktab backgrounds could have problems with the fix, but it wouldnt work without anyway
[23:17] <asac_> i am still here ;)
[23:17] <asac_> !test
[23:17] <asac> SiDi: so show me the fix ;)
[23:18] <seb128__> re
[23:19] <SiDi> http://paste.ubuntu.com/286565/
[23:19] <bcurtiswx> seb128: yes i got your reply, im trying to contact themuso in here.. no reply yet
[23:19] <SiDi> thats a userChrome.css
[23:19] <SiDi> ofc it can be added to thunderbird's theme CSS file directly
[23:19] <seb128__> bcurtiswx, ok
[23:21] <SiDi> asac: the second part of the fix fixes the wrong background in the frame titles inside the prefs dialog... the first part fixes a stupid bug in the same frames, but around the titles... you'll see what i mean if you check the display tab of thunderbird's preferences with/without the fix, and with a dark theme such as dust
[23:23] <TheMuso> bcurtiswx: Yes I am. Sorry got caught up with reading email.
[23:24] <bcurtiswx> TheMuso: bug #400485
[23:24] <bcurtiswx> you may be able to enlighten on how to get that bug fixed before Karmic FInal
[23:24] <TheMuso> bcurtiswx: Ok will look at it.
[23:25] <maxb> compiz: - turn constrain_y back on (LP: #82654)      --- didn't we turn it off to fix another bug?
[23:25] <bcurtiswx> TheMuso: thx
[23:28] <SiDi> asac?
[23:29] <maxb> Amaranth, robert_ancell : Can I call your attentions to bug 82654 vs. bug 221698 ?
[23:29] <asac> SiDi: have to check that. at best open bug, attach and assign that to me
[23:29] <robert_ancell> maxb, yes?
[23:30] <SiDi> asac: sure.
[23:30] <maxb> 82654 has just been fixed by reverting the fix to 221698
[23:30] <maxb> I'm binging you two as uploaders of the updates concerned :-)
[23:31] <robert_ancell> maxb, ah, yes, there should be a better fix in compiz 0.8.4 but Amaranth knows more about it
[23:32] <maxb> Hmm. Is that targetted for Karmic?
[23:32] <SiDi> asac: good night
[23:32] <SiDi> thanks again for reviewing this stuff :)
[23:32] <maxb> Whether it is or, not, I think it would be better to not regress 221698 on a temporary or permanent basis
[23:32] <robert_ancell> maxb, yes, as soon as it is released
[23:33] <maxb> I wonder what I should do to the bugs.
[23:34] <maxb> 221698 is currently broken again, but apparently it is 82654 which needs followup action
[23:34]  * maxb is tempted to reopen both
[23:36] <robert_ancell> maxb, they really are the same bug as far as I can tell - they are both caused by being able to move/resize windows under panels
[23:37] <maxb> Not really. 221698 is objecting to compiz' blocking of moving windows off the top of the screen for no particularly clear reason
[23:38] <chrisccoulson> yay, Amaranth is going for MOTU :)
[23:38] <Laney> woop woop
[23:51] <chrisccoulson> i've just had some spam with asac's e-mail address as the subject. how strange!
[23:56] <asac_> hmm
[23:56] <asac_> great ;)
[23:56] <asac_> what did i try to sell you?
[23:57] <asac_> *sigh* ... cannot push to bzr launchpad ... TOO MANY SSH CONNECTIONS :/
[23:57] <chrisccoulson> asac - apprarently you're a canadian pharmacy trying to sell me high quality meds!
[23:57] <chrisccoulson> lol
[23:58] <chrisccoulson> i've had a lot of spam the last few days!