[00:01] <ochosi> gottcode: for me it depends on what widget has focus, if the entry has focus, i cant resize
[00:01] <gottcode> ochosi: interesting, for me I can resize even with the entry having focus
[00:04] <ochosi> ali1234: works now!
[00:04] <ali1234> natch :)
[00:05] <ochosi> ali1234: is that really how it's supposed to look? http://www.zimagez.com/zimage/screenshot-12052013-010458am.php
[00:05] <ochosi> (that separator in the top right is expanded)
[00:05] <ali1234> yeah pretty much
[00:05] <ali1234> i dunno about that...
[00:06] <ochosi> the rest seems fine i guess
[00:06] <ochosi> i gotta say i already love that app
[00:06] <ochosi> nice work on that
[00:06] <ali1234> yeah that's wrong
[00:06] <ali1234> let me check the stuff
[00:07] <ochosi> gottcode: hmm, i'm using the ochosi/tabwin branch (although that shouldn't really make a difference for this case)
[00:07] <ali1234> ochosi: can you check in the settings editor what is going on there?
[00:08] <ochosi> sure, one sec
[00:08] <ali1234> hmm
[00:09] <ali1234> this is kind of weird
[00:09] <ali1234> it's actually wrong in my settings
[00:09] <ochosi> but it looks ok?
[00:09] <ali1234> that plugin does not have the "expand" (bool) key at all
[00:10] <ali1234> for me it's not expanded, for you it is
[00:10] <ali1234> i guess if the key is missing it does something random
[00:10] <ali1234> this is probably a bug in xfce4-panel, not setting a default
[00:10] <ochosi> how long do you have your panel?
[00:10] <ali1234> 1920 pixels
[00:10] <ochosi> and your config
[00:10] <ochosi> oh wait, no, not sure that was changed in 4.10
[00:10] <ochosi> only the windowlist got the expand dropped i think...
[00:11] <ochosi> hm, no, i think it did change in 4.10
[00:11] <ochosi> before expand was one of the options in the dropdown, not a bool
[00:11] <ali1234> well this config is not old
[00:12] <ali1234> however when i made it i might have reused some of the items already present from the default config
[00:12] <ochosi> hm
[00:12] <ali1234> which would explain it probably
[00:12] <ochosi> default config of xubuntu or of xfce upstream?
[00:12] <ali1234> yeah the leftmost and rightmost ones are both like this
[00:12] <ali1234> and xubuntu default config
[00:13] <ochosi> hm, strange
[00:13] <ali1234> anyway, the trick here is to just make sure that we don't ship buggy configs :)
[00:13] <ochosi> http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/raring/view/head:/etc/xdg/xdg-xubuntu/xfce4/panel/default.xml#L88
[00:14] <ochosi> crap
[00:14] <ochosi> that's it ^
[00:18] <ali1234> yeah
[00:18] <ali1234> i just pushed a fixed config
[00:18] <ali1234> just a matter of toggling expand on each one and saving it again
[00:19] <ochosi> yup
[00:19] <ali1234> i wonder why it defaults to expanded for you but not for me
[00:19] <Noskcaj-school> bluesabre: The pexpect update request is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729518
[00:20] <bluesabre> fantastic, thanks Noskcaj-school!
[00:20] <Noskcaj-school> I should get to that once i've adopted a few of gottcode's packages that are orphaned in debian
[00:21] <bluesabre> awesome
[00:21] <ochosi> ali1234: no idea really
[00:36] <gottcode> I'm off, talk to you all later
[00:38] <ochosi> seeya gottcode 
[03:38] <ali1234> and fixed
[03:39] <ali1234> so... how do you think about this? : i've patch indicator-sound-gtk2 to load it's own dbus service instead of the gtk3 one, by changing the dbus name
[03:39] <ali1234> this means that stuff like music players won't appear in the menu
[03:39] <ali1234> however you will be able to change the volume
[03:40] <holstein> you think it'll be a 50/50 split?
[03:41] <Unit193> dpkg-divert it. :P
[03:41] <ali1234> you lost me
[03:42] <Unit193> Basically, it moves that file, tells dpkg that indicator-sound's file is at $newlocation, and installs it's own file there.
[03:42] <ali1234> yeah, that's no good
[03:42] <ali1234> that will break unity
[03:42] <Unit193> Only when -gtk2 is installed.
[03:42] <ali1234> yes
[03:43] <ali1234> another possibility is detect when the gtk3 service is running, and then kill it
[03:43] <ali1234> actually
[03:44] <ali1234> if we start up the other service before the panel and indicators load it should work
[03:44] <Unit193> 1. Somewhat kidding, hence the ":P"  2. In theory, -gtk2 can't be used in unity.
[03:45] <ali1234> i think that's actually a better idea
[03:45] <ali1234> i wonder how to achieve it though
[03:46] <ali1234> system("/usr/share/blah/indicator-sound-service") ... maybe
[03:47] <Unit193> I went back to precise and raring packages, personally.
[03:47] <Unit193> (Updated to gtk3 today, reverted.)
[03:47] <ali1234> yeah the thing is that people don't know how to do that
[03:47] <ali1234> and i'm tired of listening to the whining
[03:48] <Unit193> Oh, it's not a fix by any means!  Yeah, if we can't backport, would be best for sure.
[03:48]  * Unit193 shuts up, then. :)
[03:54] <ali1234> hmm... best fix
[03:55] <ali1234> make the gtk2 indicator export both interfaces
[03:55] <ali1234> though i doubt it will work with players anyway
[04:11] <ali1234> right, fix is in mah ppa
[04:11] <ali1234> let's see if it builds
[04:14] <ali1234> https://launchpad.net/~a-j-buxton/+archive/indicator-sound-gtk2
[04:15] <ali1234> Unit193: so does eg rythmbox appear in the sound menu with the raring package installed on saucy?
[04:16] <Unit193> ali1234: VLC does, yes.
[04:17] <Unit193> 0.8.5.0-0ubuntu2.1
[04:17] <Unit193> So, that'd be precise.
[04:18] <ali1234> huh... wow
[04:18] <ali1234> it works even with my patched version
[04:18] <ali1234> it must not care what the dbus name is
[04:18] <ali1234> and just look for the interface name
[04:18] <ali1234> incredible
[04:19] <Unit193> Nice.
[04:19] <ali1234> unbelievable
[04:19] <ali1234> patch is 4 lines btw
[04:20] <Unit193> Hah, nice...  So, think the standard is interface name?
[04:20] <ali1234> i guess it must be
[04:21] <ali1234> com.canonical.indicator.sound isn't on the bus, com.canonical.indicator.sound-gtk2 is, and gmusicbrowser is in the sound menu
[04:22] <ali1234> so i think this might actually be SRU worthy
[04:22] <ali1234> it shouldn't break anything, and it doesn't even have reduced functionality
[04:36] <skellat> ali1234: Do you have good news for LP Bug 1208204 before I write the reply discussing why there is no infrastructure for a 13.10.1 and that if people think the fix is so simple they are encouraged to submit patches & debdiffs?
[04:37] <ali1234> skellat: sure, it's fixed
[04:37] <ali1234> ppa will build in 20 minutes or so hopefully
[04:38] <skellat> Excellent
[04:38] <skellat> No need to wander down the BOFH road then with the commentators on that bug then
[04:38] <ali1234> i don't even understand why it works
[04:38] <ali1234> but it works
[04:39] <skellat> ali1234: If it successfully builds, would you be willing to please put this on the Thursday meeting agenda for discussion?
[04:39] <ali1234> i don't know how to do that
[04:40] <ali1234> also that's today
[04:40]  * skellat is on the other side of the Atlantic from ali1234 where it is still late Wednesday night
[04:40] <ali1234> so... what do you want to discuss about it?
[04:41] <ali1234> i mean it's a 4 line patch... it's nothing to do with xubuntu really
[04:41] <ali1234> it's the indicator that is broken
[04:41] <ali1234> getting it SRU'd will be a matter of convincing ubuntu-desktop it's a good idea (which shouldn't be too hard)
[04:41] <skellat> Just so that we go through the motions for the folks complaining and Look Like We're Taking Official Notice & Action
[04:42] <ali1234> ok, sure
[04:42] <skellat> This should be the link for editing the agenda page: https://wiki.ubuntu.com/Xubuntu/Meetings?action=edit&editor=text
[04:43] <skellat> Your LP login credentials would be needed
[04:45] <ali1234> done
[04:46] <skellat> Merci beaucoup
[04:46] <skellat> Thank you 
[04:48] <skellat> ali1234: I look forward to a wonderful discussion that will be mostly for the record so we can throw a link in the comments to that bug so people can read it and hopefully stop whining as their plea has been attended to
[04:48] <skellat> :-)
[07:03] <astraljava> Hey guys, anyone on trusty with their daily machine yet? Worth upgrading? I
[07:04] <astraljava> sorry, I was mainly thinking about the indicator plugin, getting the volume applet working etc.
[07:06] <Noskcaj> astraljava, I'm on it, no major changes yet. You could always just enable my gtk3 indicator ppa
[07:06] <astraljava> Noskcaj: Thanks, that sounds like a plan, actually.
[07:20] <Unit193> astraljava: Or if you read up a bit, there's a 4 line patch to get the gtk2 ones.
[07:25] <astraljava> Unit193: Yeah, I just noticed. :) Oh well, got it up already. It's missing an icon, but I don't really care cause I know it's there. Thanks, Noskcaj!
[07:42] <astraljava> Interesting, that last update seems to have made the system a tad snappier. Wonder why.
[07:56] <Unit193> What got pulled in?
[07:58] <astraljava> I can't remember anymore, updates had been sitting in there for a few days until I rebooted just now.
[08:00] <astraljava> libido3-0.1-0, avahi-daemon and friends, linux-image-3.11.0-14-generic et al.
[08:05] <ali1234> micahg: i have a trivial fix for the gtk2 indicator
[08:05] <ali1234> it's a debdiff at the moment
[08:08] <ali1234> thing is, i can't figure out who to send a MR to
[08:09] <Unit193> ali1234: Can't attach to the bug report and subscribe sponsors?
[08:09] <ali1234> i could, but would that cause the bug to get fixed "upstream"?
[08:09] <ali1234> does upstream even exist?
[08:09] <ali1234> nobody seems to know...
[08:10] <ali1234> the ppa build btw: https://launchpad.net/~a-j-buxton/+archive/indicator-sound-gtk2
[08:11] <Unit193> https://launchpad.net/indicators-gtk2 only upstream I know of for gtk2, but I've not tracked it much.
[08:11] <astraljava> Yeah my understanding is nobody maintains the gtk2 versions anymore, but I could be wrong. It's been a while since I've heard anything about that stuff.
[08:11] <Unit193> astraljava: Not far off at least.
[08:11] <ali1234> somebody must maintain it - it got uploaded to saucy
[08:13] <Unit193> Just copied on up (and fixed control file)
[08:13] <Unit193> https://launchpad.net/ubuntu/saucy/+source/indicator-sound-gtk2/+changelog
[08:15] <ali1234> mr_pouit: you know anything 'bout this?
[09:58] <slickymaster> good morning all
[10:01] <slickymaster> knome: ping
[11:17] <ali1234> knome: i fixed the gtk2 indicator you know...
[11:17] <ali1234> i got tired of all the complaining
[11:17] <ali1234> in the end it took about 2 hours
[11:20] <ochosi> ali1234: you definitely should've started working on xubuntu 6 months ago already...
[11:20] <ali1234> i started working on it the same day i started using it :)
[11:22] <ali1234> you're right though. i should have known the writing was on the wall for gnome-panel
[11:22] <ali1234> a year ago or more
[11:23] <ochosi> yeah, well unless you're a fan of the mate/cinnamon idea
[11:23] <ali1234> mate is too big a project
[11:23] <ochosi> how do you want me to send you the panel-config btw?
[11:23] <ochosi> yeah, it's huge...
[11:23] <ali1234> panelconfig.py save ochosi.tar.bz2
[11:23] <ali1234> then send me the bz2 any way you want
[11:24] <ochosi> and much of it seems to be s/gnome/mate/
[11:24] <ochosi> yeah, i've already created the bz2
[11:24] <ali1234> yeah, i really don't like when people go crazy on the source with sed... it just makes problems
[11:24] <ochosi> i was wondering how you want it (email, pastebin)
[11:24] <ali1234> the consort project had a better idea... just fork the stuff that you actually want to change
[11:24] <ali1234> sadly that was abandoned
[11:24] <ali1234> email is fine
[11:26] <ochosi> ok, sent
[11:27] <ali1234> heh, yeah, description metadata should be added
[11:27] <ali1234> i guess description.txt and maybe screenshot.png inside the bz2
[11:28] <ochosi> sounds good!
[11:28] <ochosi> could you please try my panel layout?
[11:28] <ali1234> also it needs to scan /usr/share/panelconfigs or something
[11:28] <ochosi> cause it uses the relative-width feature of the panel
[11:29] <ochosi> and i wonder whether that works on other resolutions
[11:29] <ochosi> (mine is 1280x800)
[11:29] <ali1234> it looks kind of messed up
[11:29] <ochosi> :/
[11:29] <ali1234> maybe it's supposed to be like that
[11:29] <ochosi> i was afraid that absolute coordinates are saved
[11:30] <ali1234> nah... it should never use absolute
[11:30] <ali1234> just one panel right?
[11:30] <ochosi> | Panel1 (40% width) | Panel2 (20%) | Panel3 (40%) |
[11:30] <ali1234> oh, i see
[11:30] <ochosi> Panel1=whiskermenu
[11:30] <ochosi> Panel2=clock
[11:30] <ochosi> Panel3=indicators, tray
[11:31] <ali1234> panel 3 isn't big enough for all my indicators
[11:31] <ali1234> how do you switch between windows??
[11:32] <ochosi> i use plank
[11:32] <ochosi> although not for window-switching
[11:32] <ochosi> i only use tabwin for that
[11:32] <ochosi> actually plank is there for other ppl who use my computer, i use kb-shortcuts mostly
[11:33] <ali1234> can we patch screenshot tool to use an image host that doesn't require a password, like imagebin or imgur?
[11:33] <ochosi> yeah, we should...
[11:34] <ochosi> screenshooter is really a nice tool, but the zimagez-aspect sucks 
[11:34] <ali1234> or maybe even U1
[11:35] <ochosi> true
[11:35] <ochosi> (or dropbox)
[11:35] <brainwash> u1 does not require a password?
[11:35] <ali1234> http://imagebin.org/index.php?mode=image&id=280675
[11:35] <ali1234> brainwash: not every single time, no
[11:35] <brainwash> so you mean the login process?
[11:36] <ochosi> ali1234: that looks about right, was it like that when you loaded it?
[11:36] <ali1234> yeah
[11:36] <ochosi> ok, cool
[11:36] <ochosi> or wait, who were you answering now? :)
[11:37] <ali1234> you :)
[11:37] <ochosi> ok, good
[11:37] <ali1234> brainwash: dunno what you mean...
[11:37] <ali1234> with U1 you login once and it's remembered forever... you can share files on the dbus api
[11:37] <ochosi> yeah, i had to set my password for zimagez to something very unsafe in order to make the submitting-process less annoying..
[11:37] <brainwash> I mean you need an account for u1, but it's optional for zimagez, or?
[11:38] <ali1234> brainwash: it's not optional with the screenshot tool, it demands you enter your password every single time you want to share an image
[11:39] <knome> slickymaster, pong
[11:39] <ochosi> ali1234: how hard would you say is it to add more sources to the screenshooter?
[11:39] <ochosi> morning knome 
[11:39] <ali1234> no idea
[11:39] <brainwash> save the password?
[11:39] <ali1234> brainwash: thing is though, i don't want yet another account
[11:39] <ochosi> brainwash: yeah, securely...? distribution-independent? ...
[11:39] <knome> good day ochosi 
[11:39] <slickymaster> morning knome
[11:39] <slickymaster> knome: can you please merge https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/ubuntu-manual-tests/+merge/197801 and update the tracker?
[11:40] <brainwash> plain text only visible to the user? like the mail watcher plugin?
[11:40] <slickymaster> knome: it's a simple fix, just a mere grammar correction
[11:40] <knome> slickymaster, i'll do that.
[11:40] <ochosi> brainwash: hmpf, yeah, i think that was the reason there is no option to save the password...
[11:41] <slickymaster> knome: another thing, I've already made https://bugs.launchpad.net/bugs/1256910 and I'll propose a merge tonight, but as elfy is recovering can you review it?
[11:42] <brainwash> ochosi: or keep in the memory for like 10min (timestamp)?
[11:42] <ochosi> brainwash: yeah, i think at the moment the problem is that the screenshooter isn't under development
[11:43] <knome> slickymaster, review what? the merge when you've done it?
[11:43] <brainwash> ochosi: but ali1234 is our secret weapon :)
[11:44] <knome> slickymaster, 197801 merged and pushed to tracker
[11:44] <slickymaster> knome: yeah, I will propose it to merge tonight. I'm not able to do it at work because I'm behind a proxy
[11:44] <ochosi> brainwash: indeed ;)
[11:44] <knome> slickymaster, sure, but was that what you were asking?
[11:44] <slickymaster> knome: yes
[11:44] <knome> mm, sure, i can do it
[11:45] <knome> though ochosi or bluesabre would be better persons to review if it's correct
[11:45] <slickymaster> I'll ping then
[11:45] <knome> i can then merge and push
[11:45] <slickymaster> knome: okie dokie. thanks
[11:45] <knome> we have a meeting today at 19UTC
[11:45] <bluesabre> knome: going to miss said meeting
[11:46]  * ochosi probably too...
[11:46] <brainwash> ali1234: will the changes for the smooth greeter/desktop transition get merged automatically at some point or do the patches need to be backported before trusty gets released?
[11:46] <ochosi> it's dinner-time here and we're invited, so...
[11:46] <ali1234> brainwash: they should get merged in 4.11
[11:46] <ali1234> only xfwm4 is still waiting for stuff to get merged
[11:46] <knome> bluesabre, ochosi: see what slickymaster just asked though, maybe you can help with that
[11:46] <brainwash> ali1234: ok
[11:46] <ochosi> yeah, not sure we get xfwm4 4.11 in trusty
[11:46] <ali1234> owever it will need a distropatch to enable MONITOR_ROOT_PIXMAP
[11:47] <ochosi> the greeter and the desktop will be fixed more or less automatically
[11:47] <bluesabre> slickymaster: let me know when you do your merge request :)
[11:47] <brainwash> so xfwm will not be upgraded to 4.11 for trusty?
[11:48] <slickymaster> bluesabre: of course, no problem
[11:48] <ochosi> brainwash: i'm not sure, probably not (i would be in favor though)
[11:48] <ochosi> don't think we've really discussed xfwm4 for trusty
[11:48] <bluesabre> are there any xfwm4 branches that add touch events to the wm?
[11:48] <knome> no, i don't think we did
[11:49] <knome> is olivier the only one who can/will/won't approve to xfwm?
[11:49] <ali1234> no, nick seems to be running the show now
[11:50] <ochosi> olivier hasn't been around for ages
[11:50] <ochosi> nick is basically the xfce project leader and reviews/merges code for all core-components
[11:51] <ochosi> he's also the one who has contributed to all parts of xfce (well, like guys before him did, e.g. JPohlmann)
[11:52] <knome> ochosi, ok, so basically we could get patches in via nick
[11:52] <bluesabre> olivier ocassionally appears on the MLs to shoot down xfwm4 suggestions
[11:52] <bluesabre> :)
[11:52] <ali1234> yeah, he's plain wrong on that one btw
[11:52] <knome> bluesabre, ssshhhh, this is a logged channel :P
[11:52] <ochosi> "occasionally" = once
[11:52] <ochosi> once a year
[11:52] <bluesabre> #undo
[11:52] <ochosi> knome: yes
[11:52] <knome> ok, that's good enough for me
[11:52] <knome> what do we want in?
[11:52] <knome> is it relesae-critical?
[11:53] <knome> or is it just something that would be "nice to have"
[11:53] <ochosi> well for the greeter-transition, there is something we wanna cherry-pick
[11:53] <knome> okay
[11:53] <ali1234> well my stuff is all features, cosmetic bugfixes, and memory leak fixes
[11:53] <ochosi> feature-wise, there's zoom for xfwm4
[11:54] <ochosi> and the new tabwin which introduces mouse-click events and much nicer theming support
[11:54] <knome> i don't know if the features are something we want to argue about (unless we want them really badly), but bugfixes and memory leak fixes should get in
[11:54] <ochosi> (mouse-click events are nice for touchscreens)
[11:54] <bluesabre> +1
[11:54] <knome> i guess
[11:54] <knome> that's not the primary target group for xubuntu though
[11:55] <ali1234> zooming is a killer feature
[11:55] <ochosi> yeah, i wasn't explaining that specifically for xubuntu
[11:55] <ochosi> ali1234: +1
[11:55] <ali1234> so many people told me they miss compiz zooming
[11:55] <ochosi> knome: i was just explaining it in general cause ppl might wonder why mouse is important in alt-tab
[11:55] <ali1234> no other WM except kwin has zooming at all... and in kwin it sucks
[11:56] <ochosi> also, the patch for zoom is really small...
[11:56] <knome> features are a slippery slope to get in
[11:56] <knome> fixes we should push nick to merge
[11:57] <ochosi> well the question with the fixes is whether they get backported to 4.10
[11:57] <ochosi> if not, we'd need xfwm4 4.11
[11:57] <knome> yep
[11:57] <ali1234> he was positive about accepting all my stuff
[11:57] <ali1234> it's just a matter of getting around to it
[11:57] <ochosi> yeah, i'm sure he'll merge it
[11:58] <knome> if he was... then let's do it :P
[11:58] <ochosi> he just told me so a few days ago
[11:59] <ali1234> ochosi: can i commit your panel config on the repo?
[11:59] <knome> ok, i'm off
[11:59] <knome> see you later
[12:00] <ochosi> ali1234: sure, thanks!
[12:03] <ali1234> ok, pushed
[12:04] <slickymaster> brainwash: did you get to test https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1163886/comments/45
[12:04] <ali1234> ochosi: just out of interest... why did you use 3 panels like that?
[12:05] <slickymaster> I haven't been able to test it just yet. Planning on doing it this afternoon
[12:09] <ochosi> ali1234: otherwise it's impossible to keep the clock absolutely centered
[12:09] <ali1234> ah, i see, yes
[12:09] <ochosi> it's a bit silly, i agree
[12:09] <ochosi> bluesabre and me were thinking about creating a container-plugin for something like that at some point
[12:09] <ali1234> gnome-panel 3 has something a bit like that
[12:09] <ochosi> yeah
[12:10] <ochosi> i don't know how they do it though
[12:10] <ali1234> it uses relative positioning, but each panel has three independent areas
[12:10] <ochosi> i mean the thing is that xfce panel is extremely flexible
[12:10] <ochosi> ah nice
[12:10] <ochosi> that's a cool idea
[12:10] <ali1234> so it works like your 3 panel setup, except it's all one panel
[12:10] <ochosi> doesn't even sound like it's extremely hard to code
[12:10] <ali1234> probably not at all
[12:10] <ochosi> btw, i always wanted window-titles in xfwm4 to have an option for absolute centering...
[12:11] <ochosi> very trivial patch, but that one was shot down by olivier :p
[12:11] <ali1234> biggest challenge would be adding the required GUI changes
[12:11] <ali1234> absolute centering?
[12:12] <ali1234> nope, do not want :)
[12:15] <ochosi> well currently it depends on the amount of buttons in the decoration whether the title is really centered
[12:15] <ochosi> that's kinda odd, no?
[12:16] <ali1234> no
[12:17] <ali1234> http://ubuntuone.com/4YlgAZNtOhGhD5gsq4pBWg
[12:18] <ali1234> this window would look funny if the title was absolute centered
[12:18] <ali1234> in my opinion anyway...
[12:19] <ochosi> yeah, i know, small windows are very the absolute centering craps out
[12:19] <ochosi> but somehow other wms also manage it
[12:19] <ochosi> i guess they set a treshold width
[12:19] <ali1234> yes, but on large windows you can't really tell it's not absolute centered anyway
[12:20] <ali1234> i guess you can if you have a clock in the center top panel :)
[12:20] <ochosi> exactly ;)
[12:20] <ochosi> also
[12:21] <ochosi> i thought xfwm4 had a center-snap feature (doesn't seem to work now for some reason)
[12:22] <ali1234> what is center snap?
[12:22] <ochosi> taking a window and dragging it to the center-top of the screen it'll snap on horizontally being centered
[12:23] <ochosi> at least i do remember this feature, maybe i'm just misremembering things
[12:23] <ali1234> like when you drag a window to the top and it maximizes?
[12:23] <bluesabre> never saw that feature
[12:23] <ali1234> hmm... i might implement windows 7 side snapping :)
[12:24] <ochosi> if you mean tiling, that's already there
[12:24] <ali1234> trouble is it conflicts with workspace switching
[12:24] <bluesabre> ali1234: the side snapping is already there
[12:24] <bluesabre> ah
[12:24] <bluesabre> true
[12:24] <ochosi> :)
[12:24] <ali1234> doesn't work for me
[12:24] <ochosi> which is why you have to deactivate workspace-switching for it to work ;)
[12:24] <bluesabre> you can also attach it to keyboard shortcuts in the window manager settings
[12:25] <ochosi> (it doesn't look as cool as in compiz though)
[12:25] <bluesabre> you can disable multiple workspaces or disable workspace wrapping
[12:26] <bluesabre> (you can always right-click the titlebar and move it or drag with the workspaces panel plugin
[12:26] <ali1234> cool... bound it to the keyboard
[12:26] <ochosi> well one option would be to add a modifier for one of those actions
[12:26] <ochosi> but alt is already taken
[12:27] <ali1234> alt+numpad for each side
[12:27] <ali1234> needs top-left etc so i can have 4 windows :)
[12:28] <ochosi> true
[12:28] <bluesabre> yeah, thats the one thing I'd like to steal from kde
[12:29] <ochosi> hard to do for the mouse though
[12:29] <ochosi> unless you just bind it to a "corner-area"
[12:29] <ali1234> bluesabre: or unity :P
[12:37] <bluesabre> ah :)
[12:39] <ochosi> how does unity/compiz do it? alt-drag window to a corner?
[12:43] <ali1234> everything is configrable
[12:43] <ali1234> by default you just drag it to the edge
[12:43] <ali1234> you have to push against the edge to change workspace
[12:46] <brainwash> slickymaster: works, commenting the mentioned line disables the banner in the software-center
[12:47] <slickymaster> brainwash: I'll confirm you that, this afternoon :)
[12:51] <brainwash> slickymaster: so it looks like some packages have been upgraded in trusty (until now those new package versions were only offered by the gnome3 ppa)
[12:53] <brainwash> ochosi, ali1234: most of the time indicator-application-service fails to start -> "no watchers, service timing out."
[12:55] <slickymaster> brainwash: https://lists.ubuntu.com/archives/ubuntu-desktop/2013-December/004358.html
[12:55] <slickymaster> got run for now
[12:55] <slickymaster> bbç
[12:55] <slickymaster> bbl
[14:29] <slickymaster> knome, bluesabre, https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/mugshot/+merge/197873 at your disposal for review
[15:58] <ali1234> brainwash: meaning?
[15:58] <ali1234> you're not supposed to run the services manually - they use dbus activation
[15:59] <ali1234> that means they get started when something needs them. if nothing starts using the dbus interface within some time limit, you see that message
[16:01] <brainwash> ali1234: the question is, why does it fail?
[16:01] <ali1234> i don't know. where do you see that message, and when?
[16:01] <brainwash> x session log
[16:02] <brainwash> when the indicator plugin gets loaded I assume
[16:02] <ali1234> ok. and ... do you have any actual problems with appindicators?
[16:02] <ali1234> it could simply be that you don't have any appindicators so it is shutting down naturally
[16:02] <brainwash> yes, nm-applet reverts to notification icon and sync indicator does not show up at all
[16:03] <ali1234> sync indicator is not an appindicator
[16:03] <brainwash> so both, app and sync, sometime to not start
[16:03] <brainwash> sometimes do not start
[16:03] <ali1234> ok, so you found the reason why they don't start...
[16:04] <ali1234> this is a known bug, however
[16:04] <brainwash> it is?
[16:04] <ali1234> yes
[16:04] <brainwash> xfce specific?
[16:04] <ali1234> no
[16:04] <brainwash> works all the time in unity
[16:05] <ali1234> and what happens if you restart the panel?
[16:07] <ali1234> what is probably happening is that all the indicators start at once and spam out dbus, and so they don't connect fast enough
[16:07] <ali1234> we can work around this by putting in a small delay in the indicator-plugin
[16:07] <brainwash> restarting the panel did not help once so far
[16:09] <brainwash> ok, worth testing I guess
[16:12] <ali1234> put a sleep(5) in indicator_load_indicator() in indicator.c
[16:12] <ali1234> actally don't do that
[16:12] <ali1234> put usleep(5000);
[16:42] <elfy> Unit193: welcome to that team - you do know I'll pester you I hope :)
[16:47] <slickymaster> hi elfy
[16:48] <slickymaster> how have you been recovering?
[16:48] <elfy> hi slickymaster 
[16:48] <elfy> slowly
[16:48] <slickymaster> hopefuly everything will go well
[16:48] <elfy> :)
[16:49] <slickymaster> don't know if you saw it https://code.launchpad.net/~slickymaster/ubuntu-manual-tests/mugshot/+merge/197873 is already ready for review
[16:49] <elfy> I noticed it - but that's all 
[16:49] <elfy> thanks though :)
[16:50] <slickymaster> np
[16:50] <slickymaster> ;)
[16:52] <elfy> slickymaster: do you know if nosckaj's PPA is ready at all?
[16:54] <slickymaster> I think so. He added pexpect to it and as far as I know things didn't got borken
[16:54] <slickymaster> broken ^^
[16:54] <elfy> ok - I'll try and get to look at that tomorrow hopefully
[16:55] <slickymaster> will you be able to attend today's meeting?
[16:55] <elfy> hoping to 
[16:56] <slickymaster> it's probably better if you rest now, even though I would guess that you are sick of so much resting :)
[16:56] <elfy> well - I've managed about 4 or 5 hours sleep in the last few days
[16:57] <slickymaster> well, I won't bother you, so you can rest a bit
[17:04] <slickymaster> elfy: do you think https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1255835 should be included in https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=%22InstallationMedia:+Xubuntu%22&orderby=-importance&field.status:list=NEW&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPL
[17:06] <elfy> link fails 
[17:06] <elfy> slickymaster: ^^
[17:08] <slickymaster> elfy: https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1255835 should be included in http://bit.ly/18bwkqM
[17:08] <elfy> I guess so - needs tag is all
[17:09] <elfy> or not 
[17:09] <elfy> not sure why it's not there and I'm not really in the fram of mind to work it out :)
[17:10] <slickymaster> elfy: I'n added the xubuntu tag, so a new query will probably retrieve it also
[17:11] <Orioa> does anyone know if they are working on the login screen bug for the newest version of xubuntu so that you are able to change the background
[17:16] <ochosi> Orioa: what exactly do you mean?
[17:18] <Orioa> i mean there is a known issue with xubuntu with being able to change the login background
[17:18] <Orioa> in the newest version
[17:20] <holstein> you mean, with the login manager?
[17:20] <Orioa> yeah
[17:21] <holstein> i would check upstream with the project then
[17:21] <Orioa> i have tried ubuntu tweak replacing the link to wallpaper in the gtk.greeter. conf file even try to change the file format nothing works
[17:21] <ochosi> Orioa: the xubuntu greeter should pick up the wallpaper set by xfce's desktop manager
[17:22] <ochosi> (i.e. xfdesktop)
[17:22] <ochosi> the wallpaper in /etc/lightdm/lightdm-gtk-greeter.conf is the fallback
[17:22] <Orioa> were would i find that file if you don't mind
[17:22] <ochosi> what file?
[17:22] <slickymaster> elfy: sorry for that, it seems that we crushed ourselves. I've already 'retagged' with xubuntu
[17:22] <Orioa> (i.e. xfdesktop
[17:23] <holstein> Orioa: /etc/lightdm/litghdm-gtk-greeter.conf is the location
[17:24] <Orioa> ive try changing it there but it does not work
[17:24] <holstein> Orioa: how did you change it? maybe its an issue with your code
[17:25] <ochosi> Orioa: i'm not sure why you wanna know the location of the config-file, because you can use desktop-settings to change the wallpaper... (~/.config/xfce/xfconf/xfce-perchannel-xml/xfce4-desktop.xml)
[17:25] <Orioa> were it says desktop background i changed the link there
[17:25] <ochosi> holstein: did you not read my comment from before?
[17:25] <Orioa> not on the desktop but the log in window
[17:25] <ochosi> Orioa: those two should be identical
[17:26] <ochosi> as soon as you set a wallpaper in xubuntu, it's also used in the greeter for your user
[17:26] <holstein> ochosi: which comment, specifically
[17:26] <Orioa> its not working that way sorry
[17:26] <ochosi> holstein: the coment that that file is only the fallback
[17:26] <Orioa> for one i would like to have a different wallaper for them and the only wallaper on login screen is black
[17:26] <holstein> ochosi: i was just responding to "where is the file"
[17:27] <holstein> i'll keep quiet
[17:27] <Orioa> so if that file is only the fallback what one do i change
[17:28] <ochosi> Orioa: ok, first things first, let's head over to #xubuntu, because this is the development channel, not the support channel (and you're seeing a bug)
[17:28] <Orioa> k
[17:29] <Orioa> how do i get there
[17:29] <ochosi> is this the first time you use irc? :)
[17:29] <ochosi>  /join #xubuntu
[17:29] <Orioa> no but not all to familar with it yet but learning
[17:30] <ochosi> sure, no worries
[17:31] <Orioa> ok im there
[18:02] <slickymaster> i'm off now
[18:15] <knome> hey people,
[18:15] <knome> meeting in 45mins
[18:16] <skellat> knome: ACK
[18:38] <Noskcaj> morning everyone
[18:40] <Noskcaj> gottcode, What are the Qt5 build dependancies of you packages? I'm trying to upload peg-e through pkg-games and adopt 4 other packages
[18:42] <gottcode> Noskcaj: shouldn't libqt5-dev handle it all?
[18:43] <Noskcaj> that's not a package in debian or ubuntu
[18:44] <gottcode> ah, I see. what about qtbase5-dev?
[18:45] <Noskcaj> That's what i tried. I'll paste the error i get for you to have a look
[18:45] <Noskcaj> (it only happens in a chroot, whatever is needed is on my PC)
[18:46] <Noskcaj> Also, can you recommend a watch file? I've only got a working one using your github releases
[18:47] <gottcode> Never made a watch file before, actually. :)
[18:47] <gottcode> Since it's all my stuff, I figured out the barest amount to package them.
[19:00] <knome> #startmeeting Xubuntu community meeting
[19:00] <meetingology> Meeting started Thu Dec  5 19:00:05 2013 UTC.  The chair is knome. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[19:00] <knome> who's here for the meeting (or otherwise hanging out?)
[19:00] <knome> !team | Meeting time!
[19:00] <jjfrv8-work> o/
[19:00] <pleia2> o/
[19:00] <slickymaster> o/
[19:00] <ali1234> o/
[19:00] <knome> #topic Items carried on
[19:01] <knome> #subtopic Open action items from previous meeting 
[19:01] <knome> #action knome to prepare the website for the desktop of the week 
[19:01] <meetingology> ACTION: knome to prepare the website for the desktop of the week
[19:01] <knome> TBD
[19:01] <knome> #action micahg to talk to barry about python2.7/3 situation 
[19:01] <meetingology> ACTION: micahg to talk to barry about python2.7/3 situation
[19:01] <knome> micahg, ?
[19:02] <knome> micahg, "#action micahg to talk to barry about python2.7/3 situation"
[19:02] <skellat> o/
[19:02] <ochosi> o/
[19:02] <knome> micahg-work, is that done, or shall we carry on?
[19:02] <micahg-work> WRT 14.04, python 2.7 is staying in main, so we're good
[19:02] <knome> okay, i guess if we're good, then that's a good thing ;)
[19:02] <knome> #undo
[19:02] <meetingology> Removing item from minutes: <MeetBot.items.Action object at 0x16dcf90>
[19:02] <knome> #topic Team updates
[19:03] <knome> Team, please use #info and #action as appropriate.
[19:03] <Noskcaj> o/
[19:03] <knome> ochosi, updates?
[19:03] <ochosi> #info ochosi is testing getting rid of gnome-icon-theme in 14.04 to reduce overhead
[19:04] <knome> that's ++
[19:04] <ochosi> #info Everyone can test that by using the shimmer daily PPA (bluesabre put up trusty packages today)
[19:04] <knome> https://launchpad.net/~shimmerproject/+archive/daily
[19:04] <skellat> #info skellat is satisfied with testing whiskermenu via no-change backport to 12.04 and is willing to vote on a proposal to make it default
[19:05] <ochosi> thanks knome 
[19:05] <ochosi> gottcode, the author of whiskermenu is also here, if you have questions
[19:06] <skellat> #info skellat has made no-change backport versions available in ppa:skellat/tests for those willing to try whiskermenu who are not yet on trusty
[19:06] <knome> we can either 1) vote if we want to make whiskermenu default and then reconsider further actions or 2) build up a full proposal of the new panel layout (which is ought to change), including how whiskermenu is integrated, and vote on that as a whole
[19:06] <knome> https://launchpad.net/~skellat/+archive/tests
[19:06] <knome> i'm preferring 2)
[19:07] <ochosi> hm, quick question, who of you has tried whiskermenu so far?
[19:07] <skellat> o/
[19:07] <knome> not yet, but but.. i've seen screenshots!
[19:07] <jjfrv8-work> o/ in Precise
[19:07] <ali1234> i've tried it briefly. it's not something i would use.
[19:08] <ali1234> (and so i can't really comment on whether it's good or bad)
[19:08] <Noskcaj> I tried it and prefer it, but try to stick to the default desktop so i'm not using it now
[19:08] <knome> since i don't use menus, i don't know how i would "test" whiskermenu in a daily environment..
[19:08] <ochosi> ali1234: well you know the difference between the standard menu and whiskermenu feature-wise
[19:08] <slickymaster> I haven't tried, but like knome I saw screenshots
[19:08] <elfy> ochosi: I've used it a bit and fin dit fine 
[19:08] <jjfrv8-work> It's my default now
[19:08] <ochosi> knome: you can bind it to a shortcut and use it instead of appfinder to launch apps
[19:08] <Unit193> I didn't try it because it didn't look like something I would prefer, I'll try it at some point.
[19:08] <knome> i know the difference as well, and i generally have no exceptions to include it
[19:08] <ochosi> ok
[19:08] <knome> ochosi, i don't use appfinder either ... :)
[19:09] <elfy> well we need to decide whether our users would find it useful then 
[19:09] <knome> ultimately, even if we included whiskermenu in the default panel layout, people can get the normal menu back
[19:09] <Unit193> Nor do I, except to function as xfrun.
[19:09] <ochosi> well fine, despite this not being a formal voting process, i got some feedback, i think i can do the panel-proposal
[19:09] <elfy> not on whether we do - especially if some of us don't use menus at all
[19:09] <skellat> :-)
[19:09] <knome> and with the possible patch/app done by ali1234, we might be able to make panel layout editing easier
[19:10] <knome> ali1234, can you #info the progress on that?
[19:10] <ochosi> yup, that's very true
[19:10] <knome> because i think we want that documented...
[19:10] <ali1234> #info ali1234 made a tool to easily change panel layouts: https://github.com/ali1234/panel-switch/
[19:11] <elfy> sorry - can't sit here - have fun
[19:11] <ali1234> #info command line only at the moment, but it does the job. needs someone to design a gui
[19:12] <ochosi> ali1234: wanna set up a page in the xubuntu wiki for that?
[19:12] <knome> i think that's a cool idea.
[19:12] <ali1234> not really, but if you create it, i'll fill in the details
[19:12] <knome> i can create that
[19:12] <knome> #action knome to create a wikipage for panel layout switcher
[19:12] <meetingology> ACTION: knome to create a wikipage for panel layout switcher
[19:12] <knome> just remind me after the meeting and i'll get that item done right now
[19:13] <knome> other updates?
[19:13] <skellat> I'm ready for the agenda item
[19:13] <skellat> I hope ali1234 is too
[19:13] <knome> heh, sure
[19:13] <knome> let's move forward
[19:13] <knome> #topic Announcements
[19:13] <knome> anybody have any?
[19:14] <knome> okay.
[19:14] <knome> #topic New and emerging items
[19:14] <Noskcaj> Maybe that whiskermenu 1.2.2 is out, will be in ubuntu some time this week. parole 0.5.4 is also out, once again will be uploaded soon
[19:15] <knome> yeah, new versions will be landing in trusty for a long time to go
[19:15] <knome> #subtopic Fixing the Gtk2 sound indicator in Saucy, in a way that can be SRU'd (ali1234) 
[19:15] <skellat> If I may speak first to this sound indicator issue
[19:15] <knome> go ahead
[19:16] <skellat> We already have at least one user, Richard Elkins, actually advocating on our -devel mailing list that users switch away to Mint.  The bug comments have been getting a bit out of hand with people complaining that this is "a simple fix" yet not putting forward patches or debdiffs.
[19:16] <skellat> I'm very thankful for the work ali1234 has done.
[19:16] <skellat> And I defer to him to explain it at this time.
[19:17] <ali1234> ok... so first let me explain why it is broken
[19:17] <ali1234> the indicator is in two parts: the bit that draws the menu, and the dbus backend that communicates between the menu and pulseaudio, music players etc
[19:18] <ali1234> the indicator obviously cmes in gtk2 and gtk3 versions. they both come with a backend service, which is launched on dbus activation. both versions of the backend have the same dbus name, so what happens in practice is you always get the gtk3 version of the backend
[19:18] <ali1234> this working in raring, but the backend was completely rewritten in saucy, so this no longer works
[19:18] <ali1234> the "simple fix" posted on the bug comments isn't really a fix at all: it will break many things
[19:19] <ali1234> so i finally got annoyed enough to look into fixing it properly, and it turned out to be very easy
[19:19] <knome> ok, how do we get this in? :>
[19:20] <ali1234> all that is required is to change the dbus name so that the gtk2 indicator asks for a different dbus name, ie "com.canonical.indicator.sound-gtk2" instead of "com.canonical.indicator.sound"
[19:20] <ali1234> this turns out to be a 4 line patch
[19:20] <knome> does that fix the issue for xubuntu, but doesn't break the same thing for other flavors?
[19:20] <ali1234> i had initially thought this wouldn't work, because music players wouldn't know to use the different dbus name, but it turns out for some reason this is not an issue and it works fine
[19:20] <ochosi> knome: i guess we need to do a debdiff or something and then get a sponsor to SRU it?
[19:21] <ali1234> this fixes the problem for anyone using the gtk2 indicator still, and does not affect any other flavours at all
[19:21] <skellat> ali1234: Would a suitable sponsor be available to navigate this through the SRU process?
[19:21] <ali1234> i don't see why not
[19:21] <ali1234> i have a debdiff, and a ppa with the fixed package
[19:21] <knome> that's the the social requirements
[19:21] <knome> skellat, want to run through those with ali1234?
[19:22] <knome> skellat, (and then the sponsorship queue)
[19:22] <micahg-work> if it's that small, I can certainly sponsor it
[19:22] <knome> ok, cool
[19:22] <ochosi> well 4 lines? :>
[19:22] <knome> that's huge ;)
[19:22] <ochosi> s/if// ;)
[19:22] <micahg-work> I like 4 line patches :)
[19:22] <ali1234> i'm not sure whether to do it through a MR against "gtk2 indicators"
[19:23] <ali1234> it needs fixing in trusty and saucy
[19:23] <micahg-work> don't you need 2 MRs though?
[19:23] <ali1234> micahg-work: yes, but only because i had to change the packaging as well as the code
[19:23] <knome> ali1234, except that we're looking to handle the issue differently in trusty (gtk3 indicators support)
[19:23] <ali1234> and they are done in different repos i think... but i can't figure out how this stuff is managed
[19:23] <micahg-work> well, doesn't the service name need to change as well?
[19:23] <ali1234> knome: if the gtk2 indicator will still be in the repos, then i want it to work, even if we don't use it
[19:24] <knome> ali1234, sure, fix approved ;)
[19:24] <ali1234> micahg-work: the service and indicator are all in the same package
[19:24] <micahg-work> ah, ok
[19:24] <ali1234> let me show you the debdiff...
[19:24] <ali1234> micahg-work: http://paste.ubuntu.com/6526233/
[19:25] <ali1234> so basically it changes the service name in both halves of the indicator, and then adjusts the packaging so that the service file is included (normally it isn't because it would conflict with the gtk3 one, as they would have the same name)
[19:27] <micahg-work> ok
[19:27] <micahg-work> I can do this Sat night (can't do it right now as I need to compare some stuff and it'll take a bit more than just a test build)
[19:28] <knome> micahg-work, do you need the formal SRU progress followed by that, or will you just handle it?
[19:28] <ali1234> that comment in debian/rules should probably also go, since it's no longer true
[19:28] <micahg-work> ali1234, lines 30-32 of the paste need a space in the pattch
[19:28] <ali1234> this is why i'd rather do a MR against a upstream repo :)
[19:28] <micahg-work> knome, if someone can fill in the paperwork for the bug, that would help, I can upload to trusty/saucy once I verify the packaging piece
[19:28] <knome> micahg-work, cheers
[19:29] <knome> skellat, since you are familiar with both the issue and the SRU process, would you be willing to help ali1234 file the paperwork?
[19:29] <micahg-work> ali1234, that's fine, but all this should be going away in trusty anyways, right?
[19:29] <skellat> knome: Yes
[19:29] <knome> skellat, thanks!
[19:29] <ali1234> micahg-work: maybe for xubuntu but i think lubuntu still uses it?
[19:29] <micahg-work> skellat, just assign the saucy (if it exists) + default tasks to me
[19:29] <knome> #action skellat and ali1234 to look at the SRU progress for indicator-sound-GTK2
[19:29] <meetingology> ACTION: skellat and ali1234 to look at the SRU progress for indicator-sound-GTK2
[19:30] <ali1234> i mean theoretically the gtk2 indicators should have gone away a long time ago
[19:30] <micahg-work> (it might already be assigned to me)
[19:30] <knome> #action micahg-work to SRU indicator-sound-GTK2
[19:30] <meetingology> ACTION: micahg-work to SRU indicator-sound-GTK2
[19:30] <knome> do we need to go through something else about this?
[19:31] <skellat> Just note that we need to review progress next week as well as somebody pinging the bug thread on -devel with an update.
[19:32] <knome> #action team to review indicator-sound-GTK2 progress next week and send an update to the mailing list
[19:32] <meetingology> ACTION: team to review indicator-sound-GTK2 progress next week and send an update to the mailing list
[19:32] <knome> #nick team
[19:32] <knome> is there other items that we should go through, or should we schedule the next meeting and then wrap this one?
[19:33] <knome> pleia2, you still slept the meeting!
[19:33] <knome> #subtopic Schedule next meeting
[19:33] <knome> #info Next meeting Dec 12, 19UTC
[19:33] <knome> #undo
[19:33] <meetingology> Removing item from minutes: <MeetBot.items.Info object at 0x16ca9d0>
[19:33] <knome> #info Next meeting Thursday Dec 12, 19UTC
[19:33] <knome> #endmeeting
[19:33] <meetingology> Meeting ended Thu Dec  5 19:33:47 2013 UTC.  
[19:33] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/xubuntu-devel/2013/xubuntu-devel.2013-12-05-19.00.moin.txt
[19:33] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/xubuntu-devel/2013/xubuntu-devel.2013-12-05-19.00.html
[19:33] <knome> ta
[19:33] <pleia2> I was here :) just didn't have much to say
[19:34] <knome> so slept! :P
[19:34] <pleia2> :P
[19:36] <knome> minutes are up
[19:36] <micahg-work> ali1234, thanks for figuring that out
[19:37] <Noskcaj> gottcode, the error i'm getting is http://paste.ubuntu.com/6526181/
[19:38] <Noskcaj> Which of your packages (that are in debian) don't use qmake?
[19:38] <gottcode> Only whiskermenu.
[19:39] <ali1234> knome: reminder about wikipage for panel-switcher :)
[19:39] <Noskcaj> ok. Then i really need to find what is breaking everything's build with qt5
[19:39] <knome> ali1234, https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Trusty/PanelLayoutSwitcher
[19:39] <knome> ali1234, just fill in the parts that seem appropriate.
[19:39] <ali1234> right-o
[19:45] <Unit193> pleia2: Yep, same here.
[19:46] <knome> yeah, boring meeting :d
[19:46] <gottcode> Noskcaj: tetzle also requires libqt5opengl5-dev, nothing else does
[19:46] <knome> well we didn't have many issues on the agenda.
[19:47] <Noskcaj> gottcode, I had that too. 
[19:47] <Unit193> http://goo.gl/6qj0qr
[20:00] <Unit193> Wouldn't it be better to use xdg.BaseDirectory.xdg_config_home in panel-switcher?
[20:02] <gottcode> Noskcaj: Looks like you also need the qt5-default package as a build dep to tell qtchooser which qmake to actually use
[20:09] <Noskcaj> thanks gottcode, it works. I'll try and do some uploads later today
[20:10] <gottcode> Glad I could help
[20:12] <Noskcaj> Why do you include .exe files in the source?
[20:14] <Noskcaj> The only other issues are every binary needs a manpage, and Some keywords in the .desktop would be nice
[20:16] <gottcode> The exe files are only used under Windows, in Linux you can just recommend jhead for lossless JPEG rotation
[20:16] <gottcode> Makes it easier for other people to make their own Windows builds of the game
[20:19] <Noskcaj> ok, i'll make a custom tarball to remove that
[20:38] <ali1234> brainwash: so apparently the way indicators work changed again, this might be why you have missing indicators
[20:42] <Noskcaj> gottcode, On linux, would i be safe to delete the whole tools/ folder or should i jut remove the windows binaries?
[20:43] <gottcode> Noskcaj: safe to delete the tools folder
[20:50] <Unit193> forestpiskie: Hey, if you get to bug me about -qa, do I get to bug you about QA?  https://launchpad.net/~unit193/+archive/xfce ;)
[20:52] <ali1234> Unit193: why?
[20:52] <ali1234> Unit193: (why xdg.BaseDirectory.xdg_config_home?)
[20:52] <ali1234> oh, you mean instead of the hard coded path to ~/.config?
[20:53] <ali1234> if so, then yes, probably
[20:54] <ali1234> it's currently only a proof of concept :)
[20:54] <Unit193> Sure, was thinking in theory you can move that, but I've never seen it done.
[23:15] <ochosi> ali1234: crap, really? indicators work differently *again* in trusty?
[23:16] <ochosi> i'm starting to think we should just improve the xfce4-soundmenu plugin...
[23:16] <ochosi> and drop all that indicator-madness for good
[23:17] <brainwash> really? some of them just start via autostart now
[23:17] <ochosi> well ali1234 said so a few hours ago
[23:17] <ochosi> (i just returned now)
[23:18] <brainwash> I will do some testing tomorrow
[23:19] <brainwash> but most of the time the appindicator service does not start for me
[23:19] <brainwash> it complains that there are no watchers
[23:20] <ochosi> yeah, well i have no idea what's happening in trusty, i just quoted
[23:21] <brainwash> looks almost like I'm the only one actually testing trusty and some of the new features/fixes :D
[23:21] <ochosi> i think there are more ppl, probably you're just talking too much to me ;)
[23:22] <knome> i think it's still a bit slow on the trusty testing
[23:22] <knome> will pump up once we get to the alphas
[23:23] <ochosi> true that