[00:00] knome: we should discuss the light-locker default settings i think [00:00] currently the timeout for the screensaver is 10mins, and after that, light-locker locks [00:00] that might be considered too short or inconvenient [00:08] should locking be enabled by default? [00:09] does xscreensaver automatically lock with default settings? [00:10] ochosi, i think something like 15-20min is sane [00:10] ochosi, i guess locking is turned on when you have fullscreen stuff open? [00:10] ochosi, also, is there an easy way to temporarily turn that off? (or just l-l-s) [00:11] just l-l-s i guess [00:11] not sure the screensaving-inhibition works currently with parole [00:11] haven't tested tbh [00:12] bluesabre, [00:19] knome, [00:19] ochosi: it should work [00:20] yeah, haven't tested :) [00:20] but i'll test now [00:23] knome, I was going to mark menulibre done. bluesabre did the upstream docs and I added the paragraph to settings-preferences [00:23] bluesabre: didn't work right now [00:23] knome, unless you were thinking we needed more [00:24] jjfrv8, ok, cool. feel free to mark it done, just checking if there's something you think needs more work [00:25] I didn't think so [00:33] ochosi: huh [00:33] well, thats odd [00:33] in case that's any consolation, even vlc fails at that [00:36] and you were playing a video, right? [00:38] yup [00:38] laaaaame [00:38] I'll experiment with it [00:39] heh, yeah, i totally second that ("laaaame") [00:48] knome, I pulled the latest version of docs and when I run 'make' I get a bunch of errors: http://paste.ubuntu.com/7076726/ [00:48] any significance to that? [00:49] Well. [00:49] jjfrv8: Precise? [00:49] affirmative [00:50] basename --help 2>&1 | pastebinit [00:50] http://paste.openstack.org/show/JZCkRK72KUyYG7GOkZmN <--- That's standard. [00:52] 8.17 (2012-05-10) required. [00:52] !info coreutils precise [00:52] coreutils (source: coreutils): GNU core utilities. In component main, is required. Version 8.13-3ubuntu3.2 (precise), package size 2130 kB, installed size 5464 kB === knome_ is now known as knome === slickyma1ter is now known as slickymaster [01:06] jjfrv8: Err, same ones? [01:08] looks like it [01:08] pwd ? And where are you running make? [01:08] Unit193: this is the error I get building th docs.I'm getting a permission error when it attempts to run the translate script -> Unit193 http://pastebin.com/Vx1aV7km [01:08] !team | note that we have a meeting exceptionally *tomorrow*, on wednesday, at 19utc [01:08] note that we have a meeting exceptionally *tomorrow*, on wednesday, at 19utc: bluesabre, elfy, GridCube, jjfrv8, knome, lderan, micahg, mr_pouit, Noskcaj, ochosi, pleia2, skellat, slickymaster, Unit193 [01:09] slickymaster: Looks like it's not set executable. [01:09] most probably I won't be able to make knome. I have to go up north to fix a server [01:10] Oh wait. [01:11] slickymaster, no problem. just pinging that you don't just "forget" [01:11] I'll get the backlogs by the time I get home [01:11] yep [01:11] slickymaster: Pulled from head and it's working here. bzr status ? [01:11] doesn't look like we have anything too important [01:12] UIF on thursday, so last check-up [01:13] Unit193, it says desktop-guide/po/LINGUAS is modified [01:13] That's fine. [01:13] bzr status, that is [01:14] `make` should work if you have that file. [01:14] Ah, nope. I see it. [01:14] Unit193: also pulled from head. bzr status -> http://pastebin.com/td7e4WRP [01:15] knome: So yes, can't exactly build properly on precise. [01:15] slickymaster: bzr revert scripts/ debian/ [01:15] Unit193, you mean, can't precisely build on precise? [01:16] knome: Exactly! Added the dep in debian/control: coreutils (>= 8.20-3ubuntu1) [01:16] (17 is required, but jumps from 13 -> 20) [01:16] bah Unit193, already had rm -r xubuntu-docs/ [01:16] sergio-br2: i think as long as we don't add new icons, but only new sizes of existing icons, it's no problem to update the theme even after UIF [01:16] sergio-br2: so if you wanna work on that, go ahead! [01:16] slickymaster: It's showing chmods on the scripts ls -lh scripts/ to see what I mean. [01:17] ok, thanks [01:18] going to pull knome's revision 139 [01:19] jjfrv8: So yes, back to too old version of basename, you can either ignore those errors or pull the one from saucy (should cause no issues.) [01:20] ok, I was going to ask if I could ignore. It doesn't interfere with what I want to see but I wanted to make sure I wouldn't corrupt things when I pushed. [01:20] jjfrv8: Translations won't work. [01:21] Speaking of which, fi and pt have validation errors. :) [01:21] settings-preferences.xml:294: element guimenuitem: validity error : Element guiicon is not declared in guimenuitem list of po [01:21] ssible children [01:21] 7 in each. [01:21] hr hr. [01:21] i noticed that [01:21] but thought i'd push anyway [01:21] and wonder about that later. [01:22] lderan, you might want to update https://wiki.ubuntu.com/meetingology#Meeting_minutes with #done [01:25] slickymaster: Got yours fixed? [01:26] going to check U [01:26] going to check Unit193 [01:27] (FWIW: http://git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS#n562 ) [01:27] .16 [01:28] knome: It builds in a clean saucy chroot. [01:28] aha. [01:28] why would i need one? [01:29] (It means it's not just my system it works on, just broken in precise) [01:29] :P [01:29] yep, understood that [01:29] not worried about it [01:29] we aren't porting that to precise :P [01:29] Exactly. [01:29] anyway, i'm off for now [01:30] will be back later [01:30] have fun! [01:30] Thus, I'd think his best bet is to ignore or get the saucy coreutils. [01:30] OK, adios. [01:30] yep. [01:30] or run it in a vbox. [01:30] -> [01:30] s/vbox/chroot/ [01:31] can I just ignore, pretty please? [01:31] jjfrv8: It should be alright to ignore, yeah. Just don't break translations. :P [01:32] well, if there's a danger of that, then I'd better get it from saucy [01:32] knome: In case I didn't say, thanks for the merges. [01:32] I think you should be safe, yeah. [01:33] Unit193: are you referring to this paragraph -> xfwm themes - control how your window borders look. To change your xfwm theme, go to

Settings ManagerWindow Manager

. In the Style tab, select a new theme to change the window borders appearance. [01:37] If that's one of the lines breaking it. :P [01:39] that one is settings-preferences.xml:94 [01:40] but in that paragraph there's no 'Element guiicon' [01:40] I'm confused :P [01:41] slickymaster: No, look at the po file. [01:47] Unit193: I haven't found settings-preferences.xml:294 in po file, also [01:49] wait, I'm looking at the wrong version of the docs [01:51] Unit193: are you sure it's settings-preferences.xml:294 ? [01:52] http://paste.openstack.org/show/tLdVNGxSWvkwH4neLpvx [01:52] slickymaster: It's in the po, not the actual xml file. [01:54] I've just downloaded the po file from LP and settings-preferences.xml: ends at 138 [01:54] Unit193: yes, and I've been referring to the po all the time [01:55] thing is I'm not getting any line settings-preferences.xml:294 in the po file [01:55] slickymaster: Right, it merges into an xml file, so it's not going to be exactly there, unless you merge it in too. [01:56] besides that soltution, can you think of anything else to catch those errors? [01:57] s/soltution/solution [01:59] Normally grep, but I don't see it. [01:59] bah, I'll leave it for tomorrow [02:00] Unit193: I'm off, I'll have a early morning and a lot of miles to drive [02:01] cy tomorrow [02:01] Alrighty, g'night. [02:01] night, slickymaster [02:02] jjfrv8: Anything else I can help you with? [02:02] s/else // [02:02] Unit193, don't think so. thanks for what you've done. [02:02] Breaking your build? :) [02:02] :) [02:04] I think I'll just avoid running make on the real copy of my changes before I push [02:05] Remember: bzr status/diff is your friend, make shouldn't be a problem. [02:08] ok. I'm off too. I'll see what other damage I can do tomorrow. [02:09] Heh, saaame to the breakage. Working on breaking more of it now. :P === yofel_ is now known as yofel === Guest1184 is now known as Noskcaj [07:12] ty knome [08:02] morning everyone [08:02] morning ochosi [08:03] hey elfy [08:03] how's it going? [08:03] could be worse :) [08:04] sun's out at least \o/ [08:05] bluesabre: just exactly what do you want people to test in menulibre [08:05] hehe, same here [08:05] and if you say everything - look for it during the Unreal Unicorn cycle ... [08:07] ochosi: nice to see things merging [08:08] yeah, actually our progress-graph would look really clean and nice if it weren't for the linked bugreports [08:08] I'm a bit concerned with this keyboard EN issue though - as far as I can see anyone in the UK will install and have a buggared keyboard layout [08:09] ochosi: lol - looks ok on the qa blueprint :p [08:10] bug 1284635 [08:10] bug 1284635 in console-setup (Ubuntu) "Keyboard layout changes after login" [High,Incomplete] https://launchpad.net/bugs/1284635 [08:12] right, but i already mentioned that what you see in the greeter is only the locale, not the keyboard layout [08:12] those two are theoretically completely independant [08:12] yea - I'm not concerned about that - but about the fact that it's wrong :) [08:12] I'm not saying it's something we can fix [08:12] or should [08:12] did you set it to en_US in ubiquity? [08:13] (i mean: when installing) [08:13] no [08:13] so you set the keyboard layout to UK when installing [08:14] and it was ok in the running session, but not in the greeter? [08:18] lol [08:18] no - it's fine in the greeter [08:19] say you set password to test# - works in greeter, login and sudo something and the keyboard will be doing test/ instead [08:19] pretty sure that ali1234 and lderan confirmed it [08:20] so you have to go to settings - where layout is set to US and change it - pita [08:22] yeah, that blows [08:22] so it really is filed against the correct package [08:23] yup confirmed it [08:23] ochosi: I don't know if it's the right package [08:24] well, at least it isn't the greeter, which was what concerned me most [08:24] bdmurray didn't change it - I'd guess he'd know [08:24] because that'd mean we'd have to fix it [08:24] yea :) [08:26] if nothing else we'll need to make sure it's on the known issues list [08:27] when I get the time I'll check lubuntu and kubuntu as well for it [08:28] yeah, that'd be good [08:28] * elfy suspects it will be fine in kubuntu and possibly not in lubuntu [08:30] bbl [08:30] sounds plausible to me [08:36] I've noticed some problems with Japanese keyboard on 13.10+gtk3 indicator plugin - the keyboard does not do anything when I switch the language. [08:36] but ibus keyboard switcher (in systray) seems to work fine. [08:48] andrzejr_: what method of kb-layout switching does not work? indicator-keyboard? [08:49] elfy: you could try whether installing indicator-keyboard fixes things for you. if so, we can consider either 1) installing that to make sure things work for everyone by default or 2) at least recommending that as a simple solution in our "known issues" section [09:03] hmmmmmm..... google aura anyone? [09:07] 35 [09:08] http://www.phoronix.com/scan.php?page=news_item&px=MTYyNzM [09:08] "...it's running great on Xubuntu 14.04 LTS with the major exception being the HiDPI support." [09:09] more and more people will complain about the missing HiDPI support, can we address this somehow? [09:24] what is HIDPI support? [09:25] support for displays with high resolution [09:25] like the macbook pro retina [09:25] yes and what does it mean? [09:25] which is 13'' but has very high resolution [09:25] so the elements on the screen seem very tiny [09:25] unless you bump stuff like DPI, which can lead to fuglyness [09:26] yeah, some next-gen apple technology [09:26] :D [09:26] so what are we supposed to do about it? [09:26] brainwash: i don't think we have a good way of addressing that now, the main issue being gtk2's lack of support for it [09:26] usually gtk would take care of it somehow [09:26] or that's what gtk3 should do [09:27] gtk3 is somewhat worse at handling different DPI than gtk2 [09:27] we can only make sure the "shell" (i.e. panels etc) scale appropriately when manipulating a single variable [09:27] would be best to just look at what ubuntu did for unity to support that [09:27] right, I'm just a bit concerned that more people will avoid Xfce and use something else instead [09:28] (part of it was the indicator-change to support icon-names, because they also scale it up by a factor of 2 i think) [09:28] yeah, but HiDPI is still a bit of a corner case (right, bluesabre ? :)) [09:28] 14.04 is LTS :P [09:29] fonts in gtk2 scale correctly with dpi, unless you set override dpi [09:29] yeah, but it's not just fonts [09:29] e.g. xfwm4's window controls would also have to scale [09:30] right. nothing else scales at all, anywhere [09:30] yup [09:30] I was able to reproduce the indicator plugin blank window problem, if you continue using the "close" button, it will work fine until you use "X" to close the window [09:30] and in gtk3 the fonts don't even follow dpi [09:30] possibly a problem of different ways of setting dpi and xfce4-settings not accounting for it? [09:31] brainwash, reproduces here as you said [09:32] wickz: 14.04 right? [09:32] brainwash, yes [09:32] want to add another comment to the report? [09:33] brainwash, I thought I had tried that several time but now it won't give me back anything but a blank window [09:34] yeah, something is odd here, should be fixable now that we know how to trigger the faulty behavior [09:35] can you try something else please? create an empty file on the desktop and then cut&paste it into some folder (thunar) [09:36] brainwash, will do... [09:37] just pasted your entry above into the comment [09:37] thanks [09:38] so the file will stay visible on the desktop after the cut&paste event -> visual glitch [09:40] yes, it does [09:40] you can even continue to perform file operation (context menu) [09:40] like deleting the file [09:40] delete the file from thunar? [09:40] via the glitched icon on the desktop [09:40] no, desktop [09:41] and it will disappear from thunar [09:41] yes, as you say [09:41] thanks for confirming [09:42] glitched icon remaiins on desktop [09:45] When I trash the glitced icon: Error trashing file No such file or directory [10:07] Unit193: so xfce4-session should have the line "Recommends: xscreensaver | light-locker"? [10:07] light-locker is already present in the seed, so it won't pull xscreensaver then, right? [10:13] bug 1291019 [10:14] bug 1291019 in xfce4-session (Ubuntu) "xflock4 still uses xscreensaver by default" [Undecided,Confirmed] https://launchpad.net/bugs/1291019 [10:32] elfy: I dunno, the simple things? [10:32] add a launcher [10:33] add a directory, add a launcher to that directory; do they show up? [10:33] click "hide from menus", is that launcher now missing? [10:33] click it again, do you see it again? [10:33] :) [11:00] good morning everyone. I still had a little trouble logging on with the latest kernel, went to the earlier one to get on and decided to try the new one and got on finally, I did mt usual updat/dist-upgrade, skipped upgrade but i'm back on the latest kernel and so far all is working fine. This is just an FYI for brainwash but others might wan t to know, just trying to be helpful. [11:01] sorry for the spelling and space bar things [11:45] ochosi, lderan, knome: https://bugs.launchpad.net/ubuntu/+source/light-locker-settings/+bug/1291324 [11:45] Launchpad bug 1291324 in light-locker-settings (Ubuntu) "[needs-packaging] light-locker-settings 1.0.1" [Undecided,Confirmed] [11:48] ochosi, knome: I've pinged the folks over at #ubuntu-devel as well [11:49] ok [11:54] bluesabre: any idea how to resolve the light-locker-settings - power-manager conflict? both set the screen suspend timings and are not in sync [11:56] maybe detect if xfpm is running (and handling dpms) [11:56] and if yes, show some informative message [11:57] bug 1290737 [11:57] bug 1290737 in light-locker-settings (Ubuntu) "Switch off (dpms) time maybe overwritten by xfce power manager" [Undecided,Confirmed] https://launchpad.net/bugs/1290737 [11:59] xfpm saves the timings for bat and a/c, so it may override the settings even after session start -> delaying light-locker would not help in this case [12:12] gotta run, bbl [12:12] ochosi, knome, lderan: pitti uploaded it [12:12] :) [12:13] nice [12:15] \o/ [12:29] cool [12:29] that was quick, thanks bluesabre [12:29] brainwash: frankly, xfpm [12:30] brainwash: frankly, xfpm's timeout settings dont do anything here [12:30] if they did influence the X11 screensaver we wouldn't have had to include those settings in light-locker-settings [12:30] dpms settings [12:31] yeah, those were included so it wouldn't be too weird, setting one setting here and another there [12:32] anyway, now that you reported a bug about it, we could theoretically put it in as bugfix [12:32] it's not my report :) [12:34] so an informative message would be OK? [12:34] check for xfpm, show message [12:35] a message that tells the user to use the xfpm settings dialog [12:35] nah, that's annoying [12:35] if he want to change the dpms settings [12:36] yeah, if you want the more sophisticated distinction that xfpm makes (on ac,batt) you have to use that and simply set the light-locker-settings thing to never [12:36] it should be overridden anyway [12:36] because it's only set and session-start [12:38] we know that, but the average xubuntu does not [12:38] well those that see the conflict (who knows how many) will hopefully make sense of it [12:39] not sure what else to say, mapping 4 settings to 1 doesnt make sense either [12:39] ideally xfpm will handle all of this again [12:41] ok, can you please add some comment to the report to clarify the situation [12:41] I assume that it is a "low" priority bug then [12:42] light-locker-settings is not bound to stay in its current form... [12:42] yeah, already wrote one, havent hit save yet :) [13:03] ochosi, I don't really know my way around github. do you have a link you could point me to so I could get the svgs for the new whiskermenu icons? [13:05] jjfrv8: which ones do you need? [13:06] and do you need them in svg, png [13:06] the lock and log-out icons? [13:06] ochosi, 16x16 png [13:07] lock, logout, yeah [13:07] ochosi, ^^ [13:10] jjfrv8: ok, coming up... [13:11] note that the 16px icon is slightly different from the 24px icon used in whiskermenu [13:11] (the logout-icon) [13:12] will it look enough the same that ppl won't know the diff when we show it in the docs? [13:13] ochosi, as long as it is "the same icon", it's okay [13:13] different sizes vary anyway, nothing we can do about that [13:13] lock icon: http://bazaar.launchpad.net/~xubuntu-art/xubuntu-artwork/trusty/download/head:/locked.png-20130125111841-yl4a77lk07r0je0d-7644/locked.png [13:13] knome: the 16px variant hasn't been added to the darker variant yet [13:14] in elementary-xfce it has a light grey background (the logout icon), in the -darker variant a dark grey background [13:14] it's the same icon though [13:14] if you give me until tomorrow, i can do the 16px version of the -darker version too [13:14] or maybe later tonight [13:14] that would be cool [13:15] sure, no problem [13:15] yeah, np, tomorrow works [13:15] who do i ping? you or jjfrv8? [13:15] either works for me [13:15] thanks, ochosi [13:15] as you wish/prefer [13:15] the lock icon is the same btw, so you can already use that one [13:15] i have no preference except "ping soembody" :) [13:15] hehe [13:15] ok [13:16] i'll probably just ping you both then ;) [13:17] works [13:17] re: lock icon, easier to drop them in at the same time [13:18] knome, should have another MP for you shortly. updated links to xfce docs for ristretto and parole and some other minor changes to guide-default-apps [13:18] ok, well anyway, you h62;9;cave the [13:18] [13:18] crap, whatever happened to my ssh connection [13:18] it's somehow garbled [13:18] jjfrv8, yeah, cool [13:19] jjfrv8, i merged all the pending stuff yesterday, as you probably noticed [13:19] anyway, you have the link now to lock [13:19] yup, thanks [13:31] nice, all xubuntu-related packages in the sponsors queue were uploaded today [13:31] (there were 5) [14:12] knome: just pushed the 16px version to -darker/actions/16/system-log-out.svg on github, can you do the honours of converting it to png for the docs yourself? [14:12] ochosi: I'll check that indicator-keyboard thing [14:12] i'll wait a bit longer until i refresh xubuntu-artwork with that [14:12] thanks elfy [14:13] though ... [14:13] how do I put in the password when the keyboard's not set up properly ;) [14:20] you'll figure it out ;) [14:20] ochosi: so ... [14:21] it fails in Lubuntu too [14:22] add them to the affects-list [14:22] hey micahg [14:23] ochosi, i can [14:23] ty [14:24] hi ochosi [14:24] * micahg is disappearing in a little bit [14:24] I still need to look at your stuff [14:26] ochosi: frankly I'm not sure I can be bothered - I'm more likely to believe that it'll end up being exactly the same on April 18th [14:27] installing kubuntu now [14:27] then that'll be all the official flavours [14:30] the bug got marked as incomplete way back - added information he wanted [14:35] micahg: yeah, those -default-settings merges would be nice! [14:36] elfy: right, i'm not saying i can fix that bug for you, but i'd like to see whether we can at least offer a workaround [14:36] if the keyboard indicator helps (it can also be added/shown in the greeter if necessary), we can add it [14:47] back later for the meeting [15:06] ochosi, jjfrv8: icons updated in docs [15:09] knome: the po files grow fat in the last two hours :P [15:11] Finnish untranslated -> 160; Portuguese unstranslated -> 108 (still ahead :P) [15:24] slickymasterWork, i know, but LP hasn't imported my .po file [15:24] slickymasterWork, i don't translate via rosetta, i edit the .po file directly and then push [15:24] I think I'll start to use that method, also [15:43] slickymasterWork, it's a bit easier to translate like that, yeah [15:44] slickymasterWork, poedit is a good editor and has sane shortcut keys, so unless you have to check something (like the exact translated string) you can advance pretty fast [15:45] knome: just a question though. working directly in the .po file, do we have to break the translated strings to match the original, or can it be a continuous string and afterwards LP will deal with it and correctly format it? [16:38] slickymasterWork, poedit will show it as one string, "breaking" in the files is automatical [16:42] ochosi, so who can approve me to the whisker menu finnish translators group? [16:50] ok knome, thanks [16:51] Whisker portuguese translation is absolutely lousy [17:05] knome, slickymasterWork: https://www.transifex.com/projects/p/xfce4-whiskermenu-plugin/ [17:14] thanks ochosi [17:14] gotta run now, work meeting :P [17:14] -> [17:37] ochosi: so now I've installed all the official flavours the 2 not affected are ubuntu and kubuntu [17:48] right but have you tested the keyboard-indicator at all? [17:48] ochosi, i didn't ask that... :P [17:50] knome: i guess you can leave a message there in transifex and whoever is admin can approve you [17:54] ochosi: not yet - only just got in from work - kubuntu was installing while I was out ;) [17:54] elfy: ah, hehe [17:54] so how did you like the other flavors? [17:54] anything that did strike you? [17:55] other than being able to use the password :p [17:55] I've not looked at all today - all I was doing was checking this kbd issue [17:56] but ... I like kubuntu as much as I always did, and ubuntu is still unity ... and lubuntu I've never liked ... [17:56] huhu [17:56] for names - read DE [17:57] just installed a new xubuntu - installing indicator [18:01] ochosi: nothing that indicator-keyboard does to help, the keyboard plugin does the job [18:01] keyboard-plugin? [18:02] you mean the xfce keyboard plugin? [18:02] yea [18:02]