[00:36] <darkxst> MrSavage, the extensions thing is caused by bug 1385572
[00:36] <darkxst> MrSavage, I don't know how firefox could crash gnome-shell, I've not seen that
[00:37] <darkxst> do you have a link that reproduces issue?
[00:37] <MrSavage> yeah
[00:37] <MrSavage> it happens with fglrx
[00:37] <MrSavage> https://bugs.launchpad.net/ubuntu-gnome/+bug/1406036
[00:37] <darkxst> I don't have any AMD cards
[00:38] <darkxst> that page seems very slow, but not crashing on NVIDIA
[00:39] <darkxst> does it return to login screen or lock screen? it shouldnt do the first ever
[00:43] <MrSavage> darkxst: login screen
[00:43] <MrSavage> and everything starts up again
[00:43] <darkxst> MrSavage, probably X is crashing then
[00:43] <darkxst> not gnome-shell
[00:43] <MrSavage> oh?
[00:43] <MrSavage> is it because fglrx isn't good for ubuntu-gnome?
[00:44] <darkxst> when gnome-shell crashes, it respawns, but locks the session so you would land at the lock screen
[00:44] <MrSavage> darkxst: do the applications remain?
[00:44] <darkxst> yes
[00:44] <darkxst> fglrx is a mess in general
[00:45] <darkxst> does it crash under Unity?
[01:19] <MrSavage> not sure
[01:19] <MrSavage> @ darkxst
[01:19] <meetingology> MrSavage: Error: "darkxst" is not a valid command.
[02:20] <Noskcaj> darkxst, Should i make a merge for gnome-system-monitor 3.15.3? It's just bugfixes (including the headerbar patch)
[02:49] <darkxst> Noskcaj, wait until the theme fixes are ready
[02:50] <darkxst> it won't get uploaded without those
[08:34] <darkxst> octoquad, pong (from days? ago!)
[08:35] <octoquad> hello? lol
[08:38] <darkxst> heh, have you forgotten what you wanted ;)
[08:38] <octoquad> um, yeah, busy looking at the logs haha
[08:46] <octoquad> ok help out here, I can't remember
[08:47] <darkxst> octoquad, I have no idea what you wanted!
[08:48] <octoquad> oh boy, ok, the only thing I sent recently was daily builds are not getting built since alpha 1
[08:49] <octoquad> I also filed that bug for mutter as well: https://bugs.launchpad.net/ubuntu-gnome/+bug/1407085
[08:49] <darkxst> I know, seeds are broken until the big update lands, probably should fix those since everyone seems to be away on holidays atm
[08:50] <octoquad> Ok, We have Alpha 2 landing in two weeks, I thought some early testing might be useful
[08:50] <octoquad> sorry 3 weeks
 darkxst, you here? (that was from last night?)
[08:50] <darkxst> octoquad, at this point testing 3.12 is pretty useless
[08:50] <octoquad> haha yes, I wanted to ask you about the daily builds
[08:50] <darkxst> ok
[08:50] <octoquad> alright, noted. I'll just focus on bug reports for the time being
[08:51] <darkxst> testing with core3.14 ppa would be best for now
[08:51] <darkxst> since that will land before A2
[08:51] <octoquad> ok
[08:54] <darkxst> and your focus bug is probably an upstream bug, can you file it on bugzilla.gnome and link it to that report
[09:07] <octoquad> ok
[09:10] <darkxst> why do you need to disable window action anyway?
[09:10] <octoquad> Sublime
[09:10] <darkxst> what is that?
[09:11] <darkxst> like the text editor?
[09:11] <octoquad> I have an auto-alignment plugin to align variable assignments. Yes Sublime Text
[09:11] <darkxst> what does that have to do with window action?
[09:11] <darkxst> or is the keybinding just conflicts?
[09:13] <octoquad> it was a keybinding conflict: CTRL+ALT+A
[09:13] <octoquad> oh, wait, it's for a linting plugin
[09:13] <octoquad> I am able to jump to symbol definitions with ALT+Click
[09:14] <octoquad> And I think Super is bound to something else as well.
[09:14] <darkxst> first shouldnt be a problem, second probably is
[09:17] <octoquad> Plus Super and Holding the mouse over any part of the window will move it. I think that's maybe why I set it to disabled, because I don't need to capture and move a window with super + click. I think this was back when I was using raring, and I forgot it was set to disabled. Only after adding the staging ppa I encountered this problem.
[09:17] <darkxst> octoquad, you can set it to anything in dconf-editor
[09:17] <darkxst> that would atleast workaround your issue probably
[09:19] <octoquad> Oh, it's not train smash at the moment, I have it on Super just for staging ppa at the moment. I thought filing a bug earlier on would be beneficial in case it is present in future releases.
[10:12] <darkxst> octoquad, the disabled bit needs to be fixed upstream, I would look into it but somehow ended up deciding to port gjs to the new spidermonkey
[10:13] <darkxst> and that is turning out to be fun/epic
[10:14] <octoquad> hehe
[10:14] <octoquad> I've filed it upstream, just can't figure out how to link it in the launchpad bug report
[10:15] <darkxst> but in general I should have more time to work on upstream stuff, now Noskcaj is helping out with lots of packaging
[10:15] <octoquad> oh that's cool, thanks Noskcaj :)
[10:15] <darkxst> octoquad, click "Also affects Project" and plug in the URL
[10:16] <octoquad> That's were I am stumped, it has no URL field only a project field to choose from
[10:16] <octoquad> where*
[10:16] <darkxst> oh select mutter
[10:16] <darkxst> then next page will give you a URL field
[10:17] <octoquad> I wasn't sure if Continue would just link mutter and not give me the option submit a link to the upstream bug report.
[10:17] <octoquad> thanks I have added it.
[10:17] <octoquad> This page needs an update lol: https://wiki.ubuntu.com/Bugs/Watches
[10:18] <darkxst> octoquad, anyone can update wiki pages, so go ahead ;)
[10:19] <octoquad> I know :)
[10:20] <darkxst> octoquad, it probably not too surpising? that most of the people who actually know this stuff, are not referring too/looking or checking wiki pages
[10:21] <octoquad> yup, I was thinking about "Documentation Testing". Using a fresh install of an OS and following the guides to ensure the instructions are correct for the supported versions of the OS.
[10:23] <darkxst> though a fresh install "should" be pretty straight forward
[10:24] <darkxst> the wiki is a mine field of outdated docs for slightly side cases
[10:28] <octoquad> When it comes to documentation, especially around newer versions of a distribution, on each cycle the last release wiki pages would be cloned and adjusted to that specific release. This is slightly more overhead, but it's more relevant rather than generic. If a release has reached EOL, those pages would be archived.
[10:31] <darkxst> octoquad, sure, but the doc teams are quite seperated from the dev teams
[10:32] <darkxst> and the main ubuntu wiki team apparently dislikes flavour participation
[10:33] <octoquad> wow, ok, I thought it would be encouraged!
[10:33] <octoquad> So how does affect Ubuntu Gnome?
[10:33] <octoquad> Do we need our own documentation system then?
[10:33] <darkxst> we have out our ubuntu-gnome wiki pages
[10:34] <darkxst> that is not a problem, but the main ubuntu wiki  pages are somewhat
[10:35] <darkxst> s/out our/our own/
[10:37] <octoquad> :)
[10:37] <octoquad> haven't heard back from Ali yet. Must be super busy or taking a break...
[10:38] <darkxst> octoquad, too many projects and real life issues
[10:39] <darkxst> and he doesnt like IRC, I normally just SMS him ;)
[10:41] <darkxst> ^^ and that is also why we need people to step up and take over various teams. Ali is TL for so many teams I have lost count!
[10:42] <octoquad> yeah, it sounds like a lot of work
[10:42] <octoquad> well, we contribute what we can you know
[10:45] <darkxst> octoquad, yes, there have been a few people (including you) in the last cycle that have got more involved
[10:45] <darkxst> the few few cycles it was lots of offers of help and then nothing
[10:46] <darkxst> but we do need to (I think) get to the point where each team has an independant TL
[10:46] <darkxst> and in the case of QA probably 3 people handling the different areas
[10:46] <darkxst> bugs, release, testing
[19:33] <Noskcaj> darkxst, Is enough of 3.14 in vivid to start uploading 3.15 to the staging PPA?
[22:28] <darkxst> Noskcaj, I think once bug 1399047 lands, we can copy the last remaining 3.14 bit to gnome3 and then start on 3.15 in -staging
[22:28] <Noskcaj> ok
[22:29] <Noskcaj> Any idea when that will get sponsored?
[22:29] <darkxst> when the -desktop team get back from holidays I imagine
[22:29] <Noskcaj> Because i'll have no internet access 10th-24th
[22:31] <darkxst> ok, i'll be able to fix any issues, if it doesnt happen before then
[22:31] <Noskcaj> ty
[22:32] <darkxst> also would be a good time to switch to git packaging branches when we start on 3.15
[22:33] <Noskcaj> Sounds good, but then i have to learn git
[22:33] <darkxst> yes you will!
[22:35] <darkxst> the basics are not to far different from bzr
[22:41] <darkxst> and git buildpackage provides most of the debian specific features that bzr has