[00:00] ok, I'll take a picture tomorrow [00:00] seriously... :) [00:00] I have a photo cube to take nice white background photos! [00:00] anyway, have some house things to do with the husband now, bbiab :) [00:00] ooh ooh! [00:00] hf with house [00:01] you didn't like today's computing knome? [00:01] the apostrophe put me off [00:01] lol [00:01] ok this rewording works for me [00:01] i'm just goofing off next, let's see if anything comes out of it [00:03] knome, that would be overreaching [00:03] meh "we" [00:04] besides the 'we' isnt' that too juch [00:04] *much [00:05] yeah.. [00:05] I would stick to what we have [00:05] reworded as is nowe [00:05] * now [00:05] wfm [00:05] as i said, didn't know if anything would come off that [00:05] that's a start, and we can improve as we go [00:06] ok, I'll fix the typo, also, correct the keepass issue and push it [00:06] of course [00:06] still time for 16.04 which is obviously the next big target [00:06] exactly [00:06] by then you'll be the next doc lead :P [00:07] you wish :P [00:08] lol [00:12] knome, pushed up to revision 283 [00:12] goodie [00:12] damn, forgot to update the translation templates [00:12] doing it now :P [00:13] heh [00:14] done [03:37] ochosi: pushed updated light-locker-settings, in case you were interested :) [04:08] ochosi: almost have the next xfpm patch (without the light-locker enable checkbox) done... should have it ready tomorrow morning, evening latest [04:08] bedtime now, bbl [04:08] G'nighty. [06:08] bluesabre: https://bugs.launchpad.net/ubuntu/+source/gmusicbrowser/+bug/1223808 was that fixed/important/anything worth looking at? It's marked expired. [06:08] Launchpad bug 1223808 in gmusicbrowser (Ubuntu) "gmbrc misses line to activate albuminfo-plugin" [Undecided,Expired] [06:08] Going to presume that it was fixed upstream. [09:16] bluesabre: oh, so it's ok to set rm_conffile for our custom light-locker.desktop? if yes, is 15.04.3~ correct, or just 15.04.3? [09:18] bluesabre: and is there some enabled/disabled switch? [09:28] ochosi: even more comments by b3nmore in the xfpm report =S [09:28] he really likes to debug this [09:29] but I feel more and more like just ignoring that :/ [09:31] well, I've subscribed cavalier [09:31] yeah, but frankly, you can't dump such a huge pile of **** on someone else like that [09:32] with the encyclopedic size of that bugreport, i'm not sure anybody will be able to follow through [09:32] right, I will tell him to focus on the last comments which focus on light-locker [09:32] and finally, welcome to my world [09:35] heh, this power management thing is still haunting us, there is no escape :) [09:36] one more thing i might try is building the power-manager without the whole DPMS crap [09:36] because in the suspend logic it forces the display to shut off [09:36] and that seems to match some of the bugreports [09:36] ah, yes, we need some test builds with deactivated feature [09:36] features [09:36] that would help a lot [09:37] theoretically that shouldn't be an issue, cause it only happens in very specific cases, but i'm not sure, maybe the logic is flawed there [09:37] can you reproduce any of those black-screen bugs? [09:37] no.. I haven't even tested this once, cause I only test xubuntu on a desktop pc [09:38] well that doesn't make you the prime debugger, does it..? :D [09:39] yeah, I mainly try to gather all the needed info and test results from other users [09:40] the core issue (xfpm ignores settings) can be fixed by moving some of the lls logic to xfpm (already done in vivid) [09:40] but this new light-locker madness, mmh, and these unexpected results [09:41] I really should test this myself [09:42] I assume you and bluesabre do run xubuntu on a laptop, right? I'm not saying that you should test this stuff 24/7, but you could theoretically [09:43] in case we find a fix or something that helps [09:44] I mean theoretically test this once in a while :) [09:44] yeah, but for now suspend is really broken here, the xfpm-lls patch needs to be finalized first [09:45] you mean in vivid? [09:45] yes [09:45] oh, ok then [09:45] I thought that it was already done [09:46] but I've only tested if the sliders work [09:46] and the check boxes [09:48] the logind-logic part that lls did isn't implemented yet [10:58] bluesabre: just a quick question, have you uploaded Greybird1.5 to vivid already? asking because we need that ubiquity-panel-bg.png so i can propose my MR http://bazaar.launchpad.net/~ochosi/ubiquity/xubuntu-panel-bg/revision/6244 [10:59] i was considering putting it into xubuntu-artwork, but then again it doesn't really matter if ppl don't have greybird installed, it'll just fall back to the default ubiquity panel bg [11:00] Unit193: fixed upstream [11:02] ochosi: not uploaded yet, was waiting for numix, can do so though [11:03] no worries, i'll get the catfish patch into numix now and then do a releaes [11:03] release [11:03] then you can do the upload [11:04] cool [11:05] bluesabre: Figured it was something silly, listed on harvest. Trying to use the harvest interface, it used to be decent but now is rather useless. :/ [11:07] yeah, I think that was around the time that my sponsored package/debdiff completely trashed encoding in gmb, so I disconnected a bit :) [11:14] bluesabre: just tagged Numix 2.5.1 [11:14] so you're on [11:14] woot [11:14] btw, it sucks a tiny bit that our theme-packages don't reflect the actual version numbers of the themes, but still follow the old shimmer-themes model [11:15] but well, i guess as long as the greybird version is smaller than the shimmer-themes version, there's not too much we can do [11:15] Same source package still. [11:15] ^ [11:16] ochosi: should I pull snapshots of the other themes as well? [11:18] not sure anything happened with any other theme [11:18] i personally haven't pushed fixes to them in quite a while [11:18] bluebird and albatross both have updates [11:18] right [11:19] i haven't tested those at all [11:19] i mean you can update them if you want, but it's not really like those themes are in a good place right now [11:19] several in fact, last releases were in August and March respectively [11:20] https://github.com/shimmerproject/Bluebird/commits/master looks healthy-ish for gtk 3.14 [11:20] Albatross too [11:21] want to tag those releases so they're not completely broken in vivid? [11:21] looking healthy means you've tested them recently on vivid? [11:22] nope, only that "fixes for gtk 3.14. add missing button states" [11:22] yeah, but that's only the tip of the iceberg of what needs to be done for 3.14 [11:22] sounds better than when they were last tagged with 3.12/3.10 support [11:22] that is what i originally thought would be okayish, but then realised how much more work it would be and decided to drop support [11:22] ok [11:23] i'll quickly test [11:23] sweet jesus... [11:23] ok, bluebird is definitely not in a usable state [11:23] Either way, it's less broken than what it is now? [11:23] indicators are totally broken [11:23] Half broken anyway. :P [11:24] all menus have transparent background in bluebird [11:24] so that one is definitely unusable [11:24] hah, not only that. [11:24] even the open-file dialog is transparent [11:24] lol [11:24] Pics? :D [11:24] greybird and numix only, it is then [11:25] http://i.imgur.com/xCD12Oo.png [11:25] My goodness. [11:25] thats pretty awful [11:26] albatross looks a bit better [11:26] but still, broken indicators [11:26] i guess that one would be a tiny bit less work to fix up [11:26] but still... [11:26] maybe we can get some basic support before 15.04 [11:27] but I'll drop them to suggests in this upload [11:27] maybe [11:27] but honestly i don't have time for this [11:27] so unless someone else steps up, i'll have to retire them [11:28] i can take a quick peek at ali1234's orion work [11:29] ok, so orion looks okayish there [11:30] some padding issues and i guess some patches from greybird haven't been ported yet [11:30] ali1234: plans to fix that ^ up? if so, i wouldn't mind shipping orion in 15.04 [11:37] ochosi: did you move the bright theme? not seeing it in the greybird release tar [11:38] nope, it's still there: https://github.com/shimmerproject/Greybird/tree/master/xfce-notify-4.0_bright [11:38] the release tars are autogenerated by github, so if something is wrong, blame them [11:39] weird [11:39] you're right, it's not there [11:39] don't ask me why [11:39] oh crap [11:40] the tag is one commit before the notification theme was added [11:40] * ochosi facepalms [11:40] haha [11:40] i guess i could rewrite the git history (although that's considered evil) [11:41] greybird-1.5.1.1 [11:41] ;) [11:41] nah, give me a minute here [11:44] nasty ochosi has force-updated the tag [11:45] bluesabre: so it should be fine now [11:54] ochosi: running a test build now and will upload in a bit [12:00] uploaded (with typo!) [12:00] shimmer-themes (1.9.2-0ubuntu1) vivid; urgency=medium [12:00] * New theme releases (Greybird:1.5.1, Numix:2.5.1) [12:00] * debian/greybird-gtk-theme.install: [12:00] - Install new Greybird-bright notification theme [12:00] * debian/control: Drop Bluebird and Orion to Suggusts [12:00] stupid Suggusts [12:01] enjoy [12:02] lol [12:03] oi ochosi [12:05] bah knome, great idea rewriting the all "Keeping safe..." chapter [12:05] ? :D [12:05] now there's 74 extra strings to be translated :P [12:05] ;) [12:05] hmph. [12:05] * slickymasterWork blames knome entirely [12:16] bluesabre: that's suggusting! [12:16] :p [12:17] That's suggestive. ;) [12:17] ok, thanks, so i'll file the MR [12:18] ochosi, see -offtopic [12:18] ok, going to do non-xubuntu stuff for a while, bbl [12:37] knome: done [12:39] ta [12:39] slickymasterWork, you're now in the xubuntu-website team [12:40] \o/ [12:40] slickymasterWork, eg. when you log in to the xubuntu website, you have access to change all the content on the fly [12:40] thanks [12:40] i know i don't have to say it, but use the privilege responsibly and most importantly, DON'T MESS THE SITE UP :) [12:41] I'll try my best not to knome, but I can't promise you nothing :) [12:41] ;) [12:42] replace every instance of "help" with "tarantulas" [12:42] "to get tarantulas with Xubuntu try the Desktop Environments category of the forums" [12:43] lol, or link it to some boring literature bluesabre [12:43] :) [12:43] bluesabre, omg :P [12:43] slickymasterWork: in that case, http://open.knome.fi/ [12:43] :P [12:44] bluesabre, thanks! [12:44] that's one of the top candidates bluesabre [12:44] lol [12:44] i never tried to be a exciting read [12:44] so i guess that counts as compliment [12:44] joking aside, it is good content [12:44] * slickymasterWork whistles [12:46] heh [12:46] i hope so [12:47] knome, later on I'll need a quick how to [12:47] slickymasterWork, sure [12:48] found it -> Pages [12:48] ;) [12:48] it's rather simple, isn't it? [12:48] yeaps [13:01] bluesabre, i'm in favour of the tarantula thing [13:01] ^ [13:02] ^ [13:03] :D [13:03] :( [13:04] * bluesabre considers adding tarantulas to the next meeting agenda [13:04] silly people.. [13:05] generally [13:10] bluesabre: did you integrate the lls logind switches for lock-on-suspend in the light-locker patch? [13:10] for xfpm-settings i mean [13:50] bbl [16:09] pleia2: just a quick reminder, please don't forget to schedule our next community meeting! [16:15] wasn't it knome who was going to run it ochosi? [16:16] oh, i just read on the meeting page that pleia2 is to schedule the next meeting [16:16] since i wasn't there, i was relying on that #action [16:16] but ofc i'm fine with knome running it [16:16] knome: just a quick reminder, please don't forget to schedule our next community meeting! [16:16] there you go, done [16:16] :) [16:18] ochosi, no, pleia2 said she'd do it [16:18] slickymasterWork, ^ [16:18] i've pinged you both anyway, so nvm [16:18] :) [16:19] sorry then knome, I was still with http://irclogs.ubuntu.com/2015/01/14/%23xubuntu-devel.html#t22:32 in mind :P [16:20] ochosi, you might have an idea for the question in #xubuntu [16:21] so the staging site is nearer and nearer ready to be published [16:33] nice [16:36] meeting scheduled, thanks for the reminder [16:36] np and ty [16:39] heh pleia2, that's my mother birthday [17:54] almost surprised by my latest bug so far [17:54] move it one to something else [17:55] bbl [18:12] pleia2: I started playing about with that poll pad btw, got 3 bits to it atm [18:12] cool, I'll have a look [18:13] right at the bottom [18:13] that's good [18:13] s/Unit/Robot though, just to be clear [18:14] :) [18:14] :) [18:15] I guess the thing is to give people time to look and then suggest changes - then just go for it [18:16] anything is better than what we have now probably [18:16] yeah [18:16] I'll add it to the agenda now [18:16] thanks [18:17] ok [18:33] ali1234: if you get time and/or interest could you have a look at bug 1412060 [18:33] bug 1412060 in pulseaudio (Ubuntu) "Indicator sound fails to start with Asus Xonar" [Undecided,New] https://launchpad.net/bugs/1412060 [21:12] oh hey ali1234 [21:13] (and yeah, in case you were hiding from me, keep hiding, cause i'll ask you about orion again...) [21:13] evening ochosi [21:13] hey there elfy [21:13] hi [21:13] what about orion? [21:13] i tested your branch, looks good so far [21:13] there are still a few commits missing [21:14] i skipped the ones that were later reverted :P [21:14] i can point those out to you though if you want [21:14] sure [21:14] this one is important: https://github.com/shimmerproject/Numix/commit/c119f55afee8adbc38a2d71b5f1ff44c5b50a60e [21:15] and there is some flashing in the popover, let me see how i fixed that in greybird... [21:15] what's a popover? [21:16] that's the menus that look like comic speech bubbles [21:16] e.g. gnome-calculator has that [21:16] oh, those :( [21:16] (of the apps we are shipping) [21:16] so add that line, it'll take care of that: https://github.com/shimmerproject/Greybird/commit/f4a479bb010cca1051cc9f7bab9c6e53179b16fe#diff-967752fff150bcb489813608b67c3e60R1421 [21:17] oh yeah, transitions [21:17] yup [21:17] and there are still nasty checkboxes in the menus [21:18] how does this css work btw? [21:18] best to sync your gtk-widgets-assets with greybird, i fixed that there [21:18] what's the priority rule? [21:18] i already did that [21:18] yeah, but then i fixed greybird some more [21:18] https://github.com/shimmerproject/Greybird/commit/19624df20674a679c86952a533bfca5074b0fc39 [21:19] i think i need a specific example for your question [21:19] are there competing/duplicate styles? [21:19] if i write * { transition: none !important; } will it disable all transitions globally? [21:19] afaik the one that comes later in the code overrides the previous one [21:20] hm, right. with !important that might override everything [21:20] do elements have default styles? [21:20] but i'm not using that at all [21:20] if i supply a completely empty css file what happens? [21:20] not sure, adwaita might have (it's now baked into gtk3 as default) [21:20] then you get adwaita [21:20] as before you would've gotten raleigh [21:20] lucky for you, adwaita is fairly close to orion [21:20] you know how css works in browsers right? [21:21] the most specific rule wins [21:21] well, this is not the same css (at least not yet) [21:21] yeah, that should also work here, at least i was presuming that when saying the later one counts [21:21] i was assuming you had two identical rules [21:21] that would be silly :) [21:22] well, i said i need an example, i thought that made it clear i had no idea what you were talking about :) [21:22] but the problem is that a generic rule like * {} will always be the least specific [21:23] if adwaita is built in, then which rule wins, the built in ones or a completely generic one like * {} [21:23] do the built in styles automatically have lowest priority? [21:23] that would be the sensible thing but this is gtk we are talking about [21:24] i think whatever you put in the theme wins, but tbh i haven't started out with a blank theme in ages... [21:24] yeah, that would be the most sensible and what i assumed so far [21:25] but yeah, as you said, this is gtk [21:36] ali1234: not sure what other commits you might be missing. since you renamed some of them, it might be best if you yourself skim greybird for missing ones [21:37] the catfish one would be useful, but you can use the one i wrote for Numix, it's shorter than Greybird's and should do it for Orion [21:37] looking through the theme there's a lot of rules that look... pointless [21:37] * ochosi shrugs [21:38] we're working on a SASS rewrite, that'll clean up the code big time [21:38] so far, it has just grown when people tried to fix stuff [21:38] so basically, with every gtk3 release since gtk3.6 [21:49] weee, corner-tiling in xfwm4 [21:51] knome: I already added the meeting to the calendar so now there are 2 :) [21:51] hmm.. [21:51] (I added it when I scheduled the meeting) [21:51] wonder why i didn't see that [21:52] deleted the other one [21:52] guess i should make calendars are synced from now on [21:52] hehe [21:52] anybody else hate when images in planet ubuntu span over the content area? [21:54] yeah, I told the community team to make the code we're using for planet be in a public place so we could submit patches against it to fix things like that, mhall119 said he'd work on it [21:54] this exists, but we can't do MPs on it I think https://code.launchpad.net/~canonical-isd-hackers/ubuntu-website/light-planet-theme2 [21:55] we surely can [21:55] oh ok [21:55] but doing it the right way is an arts of itself [21:55] or creating a branch that lets us do a merge proposal, to put it other way.. [21:55] he said "I'm asking the web-team to get this put into a proper LP project so we can start taking those patches popey mentioned" [21:55] so I wasn't sure [21:56] right [21:56] anyway, you can technically create a MP for any branch in LP [21:56] if you know how to do it [21:56] that's not the problem :) [21:56] well, first problem was finding that link :) [22:06] knome: I'd have to read planet Ubuntu for that. [22:15] ochosi: finally something works -> last comment in "the" xfpm report [22:25] brainwash: you mean late-locking? [22:26] ochosi: yes, we need to stay on vt7 the whole time, and only switch to vt8 on resume [22:26] Yes. [22:26] Unit193: ? [22:26] otherwise strange things will happen [22:27] yeah, this method was just previously criticised for not being "safe enough", otherwise i guess we'd have set it as default all along [22:27] and yeah, as you pointed out, a direct call for late-locking might be needed [22:29] mmh, won't this even make logind-handle-lid-switch=true obsolete? [22:30] which is our fix for the blank screen bug [22:31] well, not really, since late-locking is an option, not compulsory [22:31] and it did work for many people, just not for all [22:32] it does work, but the implementation is incomplete in xfpm/lls [22:33] meaning some use cases are broken [22:36] why would you create a Member of Parliament? [22:36] * sidi lurks back into the darkness. [22:36] ochosi: so, late-locking needs to be re-implemented, similar to how it reacts to the logind dbus suspend/resume signals [22:37] ochosi: some way to ensure that it 1) locks the user session 2) switches to the greeter screen [22:37] but not in 1 step [22:42] bluesabre: can you do the packaging for bug 1292290 (trusty, maybe utopic)? [22:42] bug 1292290 in xfce4-settings "Window manager keybindings don't work after reboot" [Medium,Confirmed] https://launchpad.net/bugs/1292290 [22:44] we just need to pick this http://bazaar.launchpad.net/~xubuntu-dev/xubuntu-default-settings/trunk/view/543/etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml [22:44] and sync this update xml to trusty/utopic [22:45] there were no other changes, only my keybind fixes [22:46] I'll write the SRU then [23:07] ochosi: will be working on that tonight [23:09] Ach dangit. What did you folks decide on ubiquity? I want to get rid of this ubiquity/ directory already. :P [23:09] xfdesktop good enough? [23:09] lol [23:10] whatever works at this point... if xfdesktop can work, let's do what it takes to make it so [23:10] Unit193, you can do merge proposals for both options [23:10] well i heard feh would have some pros. [23:10] like not being able to access the deskop [23:10] +t [23:10] knome: "Double" the work, so not really looking to do that. [23:10] brainwash: will take care of that probably tonight, go ahead and document the SRU [23:10] Unit193, i know, i was just kidding. [23:11] Unit193: if we have the xfdesktop fix, let's take that route :) [23:11] bluesabre: Fantastic, want a diff to review before I do something with it? [23:11] we'll need a month to merge it into ubiquity proper anyway ;) [23:11] yes please [23:12] y'all keep me busy :) [23:12] of course [23:12] consider what the situation would be like if we didn't have somebody with upload rights [23:12] ugh. [23:14] bluesabre: http://paste.openstack.org/show/CXWFBGiAJGtUvka8KtCS/ [23:14] bluesabre: Keep in mind, any comments on style are good, I don't know python a lick. [23:17] knome: yeah, i'm still trying not to remember what that was like... [23:17] ochosi: We can reenact it. [23:17] Unit193: ok, you start by filing a MR against ubiquity! [23:17] ;) [23:17] * Unit193 stabs ochosi. [23:18] * ochosi bleeds and says "aaaaaaarggh..." [23:18] (with which i'm ofc referring to the famous castle of "aaaaaaarggh...") [23:18] :P [23:19] https://www.youtube.com/watch?v=ZlIz0q8aWpA (it's aramaic! ofc!) [23:24] Unit193: looks good [23:28] Oh right, what's that bug number? [23:28] Unit193: linked to v-bugs blueprint [23:29] Alright, hit a page on the wiki and the error message is "No tienes permisos para editar esta página." [23:30] not logged in? [23:31] Right, but I'm still in America, you'd think it'd give me a message I could read. :P [23:32] No necesitas editar esta página [23:32] Unit193: wait, you did read that! you were even able to write it in here [23:34] haha [23:37]