[02:24] <bluesabre> knome: that's an icon, no reason it should be marked as translatable
[02:24] <bluesabre> will fix that
[08:12] <max12345> hello, I was wondering just how it's decided what software is on distros by default.
[08:16] <flocculant> max12345: this is where *we* start https://wiki.ubuntu.com/Xubuntu/StrategyDocument#Seeds_.26_Composition
[08:20] <max12345> flocculant: ok that's about what I was looking for. Thank you! Can I petition you somewhere to overthink having firefox as default? Because I'd prefer one of the forks after what they've been doing over the last years.
[08:21] <flocculant> well, there is a way to do that - try and find the necessary 
[08:21] <flocculant> because it's not as simple as you saying 'hey can we do this instead?' ;)
[08:23] <flocculant> https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Utopic/Inxi
[08:23] <flocculant> https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/W/DefaultMediaPlayer
[08:23] <flocculant> are two specs - you'd need to do something similar for what you want
[08:24] <flocculant> but - the earliest would be for the X cycle 
[08:25] <flocculant> https://wiki.ubuntu.com/Xubuntu/StrategyDocument covers the basic
[08:26] <max12345> ok... I'll look into it. Thanks again!
[08:33] <Unit193> max12345: Has to be in the repos, and none are.
[08:36] <max12345> Unit193: hm, I can see how that's a problem.
[09:55] <knome> bluesabre, i knew that, i was just kind of letting you know... :P
[12:34] <jjfrv8> flocculant, fyi, I installed wily on my main desktop so I can do some realistic app testing now.
[12:34] <jjfrv8> Restoring my panel after the install with xfpanel-switch worked like a charm :)
[12:34] <jjfrv8> I did have a heck of a time with the install, though. Monitors would go blank and machine would lock up either during install or shortly after reboot.
[12:34] <jjfrv8> It looks like the nouveau drivers were causing my gpu to overheat. Once I managed to get the nvidia driver installed, temp came down and all was well.
[12:34] <jjfrv8> Does that sound possible?
[12:36] <flocculant> mmm 
[12:37] <flocculant> I did have some oddities at cycle start with gpu - mine was the other way around though - been using nouveau :)
[12:37] <flocculant> Not got more than 1 monitor to check that simply here atm
[12:38] <flocculant> and yes - the panel switch tool is \o/ 
[12:38] <jjfrv8> yup
[12:39] <flocculant> excecpting issue noted previously - but that's like complaining that the car's not fast enough when you've previously used a horse :D
[12:39] <jjfrv8> hehe
[12:39] <flocculant> jjfrv8: did you install today? 
[12:40] <flocculant> is the image fixed - not checked yet ... 
[12:40] <flocculant> will do that now 
[12:41] <jjfrv8> sorry, no. I started with yesterday's. That bombed. Tried the 11th, started having the lockups. Went back to beta1 before figuring out driver issue.
[12:41] <flocculant> :(
[12:42] <flocculant> blimey - 40% difference in images between yesterday and now 
[12:44] <flocculant> and it's the weekend so obviously not fixed - I'm an idjit
[13:28] <bluesabre> jjfrv8, flocculant: so the nvidia drivers are working for you guys?
[13:30] <bluesabre> if I try to use any of the nvidia drivers in wily, I can't get anything to display and have to drop to T1 to uninstall
[13:33] <jjfrv8> bluesabre, aye, nvidia driver working here. I did find that the latest version has a different settings gui, with far fewer options.
[13:33] <jjfrv8> so I downgraded to an older version.
[13:33] <bluesabre> fun
[13:34] <bluesabre> I'll need to try to report my issue then
[13:37] <jjfrv8> bbl
[14:07] <flocculant> bluesabre: no - using nouveau 
[14:08] <flocculant> bluesabre: had some bizarreness a while back - random white screen while on desktop 
[15:21]  * bluesabre wants to merge xdg-utils, but there's so many ubuntu changes
[15:26] <bluesabre> looks like most fixes have been upstreamed, so that's good at least
[16:01] <knome> :)
[16:26] <flocculant> bluesabre: so what's the crack with parole - should it really be in 2 ppa's at different versions still? 
[16:57] <bluesabre> flocculant: haven't had much of a chance to look yet, will try to get to that today
[17:03] <flocculant> bluesabre: yep - just wondering mostly - it tried to update today :)
[17:03] <bluesabre> just uploaded a new xdg-utils to -staging... will take a bit to build but contains lots of fixes
[17:05] <bluesabre> http://paste.ubuntu.com/12398952/
[17:08] <flocculant> knome: what's up with the tracker front page?
[17:08] <flocculant> bluesabre: nice :)
[18:06] <bluesabre> micahg: do you think there is anything I should add for https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1495273 before subscribing the release team?
[18:22] <flocculant> bluesabre: this nvidia issue you've got - does the machine use that optimus? 
[18:52] <knome> flocculant, i'm doing the messin' around
[18:53] <knome> flocculant, i'll land something cool tonight there, so just you wait ;)
[19:01] <bluesabre> flocculant: yeah, I've got both nvidia and intel
[19:15] <flocculant> bluesabre: then I've seen people with issues with that 
[19:18] <flocculant> https://launchpad.net/ubuntu/+source/nvidia-prime/+bugs?orderby=-id&start=0
[19:31] <flocculant> knome: you need to set up a temp background so people don't think it's broken http://bit.ly/1NqwufZ
[19:31] <knome> hahah
[19:31] <flocculant> :)
[19:32] <knome> okay, this newly prepared stuff should be ready to go
[19:32] <flocculant> ... 
[19:32] <knome> to the tracker, that is
[19:55] <flocculant> I'll be sure to look tomorrow when I'm awake :)
[19:55] <knome> yep
[19:55] <knome> do that
[19:56] <knome> i hit an unexpected wall, so figuring a way around that
[19:56] <knome> but after that it's all out
[19:58] <bluesabre> releasing things is hard... with the bad xfce certs the release tool dies half-way through
[20:01] <knome> nie
[20:01] <knome> nice too
[20:04] <bluesabre> micahg: went ahead and subscribed the release team to https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1495273
[20:06] <knome> http://tracker.xubuntu.org/#tab-details
[20:08] <bluesabre> you mean the content that no longer seems to exist?
[20:08] <knome> huh?
[20:08] <knome> do a hard refresh...
[20:09] <bluesabre> http://i.imgur.com/fSRyol7.png
[20:09] <knome> looks like you don't have js enabled
[20:09] <bluesabre> syntax errror
[20:09] <knome> ?:P
[20:10] <bluesabre> function open_tab( first_load = false ) {
[20:10] <astraljava> Works For Me™
[20:10] <knome> weird, because everything looks ok to me
[20:10] <bluesabre> chrome no likey
[20:10] <knome> i wonder why...
[20:10] <astraljava> ...on Chrome, too.
[20:10] <knome> hahah
[20:10] <bluesabre> http://i.imgur.com/J7C780J.png
[20:10] <knome> bluesabre, you WILL want to double check the url too
[20:10] <knome> you don't want #details, you want #tab-details
[20:11] <knome> bluesabre, i haven't even touched that part...
[20:11] <knome> bluesabre, it was always there
[20:12] <bluesabre> http://i.imgur.com/Ombp5df.png
[20:12]  * knome double-checks with chrome
[20:12] <knome> ok ok, chromium
[20:13] <knome> yeah, i see that now as well
[20:13] <knome> but it's weird
[20:14] <knome> bluesabre, retry
[20:14] <bluesabre> yay
[20:16] <knome> bluesabre, comments plz?
[20:16] <bluesabre> knome: works
[20:17] <knome> well, i was thinking about comments about the new functionality
[20:17] <bluesabre> pretty cool
[20:17] <bluesabre> I like it
[20:17] <knome> the filters and sort - which you can enable by clicking the column headers
[20:17] <knome> nicks and spec names also link to "show this only"
[20:18] <knome> (while keeping other existing filters and sort)
[20:18] <bluesabre> very cool
[20:18] <knome> well, at least should
[20:18] <knome> and text search is isntant
[20:18] <knome> instant too
[20:18] <bluesabre> mhm
[20:18] <bluesabre> good stuff here
[20:18] <knome> so, now you see why i borked the overview tab
[20:19] <bluesabre> :D
[20:19] <knome> that said, i do need to work on it a bit
[20:20] <knome> considering dumping the burndown there
[20:20] <knome> oh, one thing that doesn't work for now (intentionally) is +teams
[20:20] <bluesabre> its a very good "get your crap done" page, it's helped me quite a bit this cycle
[20:20] <knome> ;)
[20:21] <Unit193> Irssi has a crontab script, I can just 'bluesabre: Get yer crap done.'! :-----D
[20:22] <knome> ..
[20:22] <bluesabre> ... too
[20:22] <bluesabre> :D
[20:22] <knome> Unit193, i'm already sending daily notifications to his email
[21:54] <knome> pleia2, reminder: your turn to schedule next meeting :)
[21:57] <knome> slickymaster, wasn't sure you noticed, but i reworded your work item re: the slideshow translations to "Start the discussion..." since i think the change should be done W+1 (as we discussed), but left the item still open for you to close whenever you feel appropriate
[21:57] <knome> Unit193, krytarik: any reason your core items are still open?
[21:58] <knome> dkessel, what's the status with jenkins now?
[21:59] <knome> lderan, you had any time to think about the qa tracker xml-rpc methods?
[21:59] <knome> lderan, did you look at the pad that flocculant set up?
[21:59] <knome> micahg, any news about shimmer-themes and our packageset?

[22:01] <bluesabre> so pingy!
[22:01] <knome> very
[22:02] <knome> bluesabre, do you have any idea about bug 1332931
[22:02] <bluesabre> knome: its probably a kernel bug
[22:02] <knome> aha
[22:03] <Unit193> Or dbus, yeah, that, dbus.
[22:03] <bluesabre> basically their laptop keeps mashing the switch-monitor key
[22:03] <Unit193> logind.
[22:03] <knome> Unit193.
[22:03] <knome> d.
[22:03] <bluesabre>  /etc/unit193.d/01-xubuntu
[22:07] <Unit193> bluesabre: /usr/lib/unit193, /usr/bin/unit193-browser or /etc/ssl/certs/unit193.pem count?
[22:07] <bluesabre> :D
[22:08] <bluesabre> is unit103-browser just a rebranded firefox with a monster truck?
[22:08] <bluesabre> er unit193-browser
[22:08] <knome> :P
[22:08] <Unit193> Nope.
[22:08] <bluesabre> darn
[22:08] <knome> bluesabre, did you mean "barn" ?
[22:09] <bluesabre> actually yarn, thanks for catching the typo
[22:09] <knome> :P