[00:28] robert_ancell: bschaefer: all layout is done using vector sources, so it's easy to generate svg out of that i believe. It's just well - getting dimention sizes of how would we want it to be rendered. === thumper-afk is now known as thumper === Zachary_DuBois|A is now known as Zachary_DuBois === FJKong_AFK is now known as FJKong [04:18] xnox, trusty-desktop-amd64+mac.iso gives me ubi-usersetup failed with exit code 2. that's so unfriendly. [04:20] xnox, i'm also curious how that made it past CI testing [05:31] Good morning === Ursinha is now known as Ursinha-afk [09:03] morning! [09:04] hello :) [09:05] hey hikiko & pitti [09:05] wie gehts? [09:05] hey Laney, guten Morgen [09:05] good morning desktopers! [09:05] Laney: gut, danke! [09:05] bonjour seb128 ! [09:05] hey Laney hikiko pitti, how are you? [09:05] hi seb128 Laney pitti :) [09:05] good seb128 you? [09:06] hikiko, I'm good thanks [09:06] seb128: ma main est un peu malade (je doit aller au médecin maintenant), mais bon [09:06] hey seb128 [09:06] Laney, so changing to build u-s-s on all archs was not the best idea, it's blocked on i-n which is blocked on unity8 now [09:06] prima, danke [09:06] pitti, oh, qu'est-ce que tu as fait ? [09:06] heh [09:07] seb128: not sure yet; probably ganglion burst open again when I was doing pushups improperly [09:07] I guess the goal is to unwind the stack [09:07] Laney, I force merged back to trunk even if it's in proposed [09:07] but there are hacks like faux packages that can be employed if necessary [09:07] right, Colin was on it [09:07] nod [09:07] he forced britney into thinking unity8 is available on archs where it's not [09:09] seb128, we finally decided to add a checkbox quickly in u-c-c and try to implement this: https://wiki.ubuntu.com/BrightnessAndDisplays#Displays until friday (but since the second change is quite big and might not be in 14.04) could you get a look at my checkbox? (here: https://code.launchpad.net/~hikiko/unity-control-center/u-c-c.checkbox-for-app-scaling/+merge/211681)? [09:11] hikiko, I had on screen, how come it's so much code? [09:11] hikiko, like why do you need to use gnome_rr apis, isn't that supposed to just write gsettings keys? [09:12] seb128, I needed to add a custom gsetting too [09:12] why?! [09:12] https://code.launchpad.net/~hikiko/gsettings-ubuntu-touch-schemas/gsettings-ubuntu-touch-schemas.selected-monitor/+merge/211680 [09:12] because I needed to store the selected monitor [09:12] why? [09:12] those settings are not by monitor [09:12] the checkbox does the following: [09:12] when is checked [09:13] it sets the scaling-factor and the text-scaling-factor to some values that when multiplied they give the ui-scale factor [09:13] of the selected monitor [09:14] so that the menus and launcher etc have the same size with the window contents === Ursinha-afk is now known as Ursinha [09:14] in the selected monitor [09:14] so what happen when you select another monitor in the UI? === davidcalle_ is now known as davidcalle [09:15] the new monitor's check button is checked, the new monitor's name is saved and the scaling-factor and text-scaling-factor of the desktop are set according to the ui-scale [09:16] next time you open u-c-c you will see the new monitor checked [09:16] unless if [09:16] shrug, that seems really complicated logic, did design suggest that? [09:16] the scaling/text-scaling have been changed from outside u-c-c [09:17] can you open a bug with explain the logic? that needs a ffe/uife anyway, and to me that's just too complex [09:17] seb128, we discussed with mpt and we found this solution: https://wiki.ubuntu.com/BrightnessAndDisplays#Displays [09:17] but since we practically have 2 days [09:17] and in uds we were asked to add a checkbox just to have the feature there [09:17] right [09:17] we decided to do the checkbox [09:17] I'm fine with the checkbox [09:18] and then do the big change [09:18] that has a button for using the selected display [09:18] but not with that magic logic and new key and whatsoever [09:18] that seems more sensible to me [09:18] I ve started the second design too [09:18] seb128, if I only had the checkbutton [09:18] and someone checked it for monitor N or changed it from the outside [09:19] there is no "for monitor N" [09:19] those settings are not by monitor [09:19] I know what you mean [09:19] the checkbox is "scaling 2 on/off, for all monitors" [09:19] I didnt explain it well [09:20] IRC might not be the best place [09:20] no the checkbox should do the following: [09:20] please open a bug with the logic described [09:20] ok :) [09:20] we need it for the ffe/uife anyway [09:20] thanks [09:28] shrug, why are unstable users not updating [09:29] the top report of e.u.c daily trusty issues is still that xfdesktop4 issue that was fixing 17 days ago [09:30] hi all, I am having some issue with my ubuntu-raring-minimal if I launch a vncserver and connect to it I keep getting failed to start session "gnome" logout. I have xubuntu installed though [09:34] larsu, charles_: Can one of you please approve https://code.launchpad.net/~mitya57/indicator-applet/unparent-label/+merge/208174? Having a hacky fix is better than having that applet totally broken. [09:35] Laney, did you try https://code.launchpad.net/~binli/unity-control-center/1291862/+merge/211258 again? [09:35] I'm going to put a landing with some of my fixes, I'm pondering including that or not [09:36] Laney, also if you want to review/ack https://code.launchpad.net/~seb128/unity-control-center/users-prompt-when-needed/+merge/211596 ... it's the bug I was talking to desrt about yesterday [09:36] oh I forgot, let me do that in a minute [09:36] thanks [09:39] how come g-c-c upstream doesn't have that password bug? [09:39] it looks like it would from the code [09:39] anyone able to explain why boot is slow slowe in trusty, the desktop seems to be consuming a load more boot time if one can believe this data: http://ci.ubuntu.com/bootspeed/machine/1/amd64/ [09:40] mitya57: that's a gtk bug, no? I don't think any other container has this check [09:40] which wouldn't make sense, gtk_widget_set_parent() unsets the old parent anyway [09:41] ah it doesn't [09:41] interesting... then the other containers are doing it wrong?! [09:44] Laney, see the bugzilla I pointed in the description? [09:44] Laney, desrt's comment on it [09:44] Laney, I think they had it on 3.8, they refactored the code (in a buggy way in 3.10) [09:44] ah yes [09:44] the call I moved is before the case for them [09:45] so it's just ignored [09:45] larsu: Yes, it doesn't, and fails with assertion error with the current code. [09:45] hey larsu [09:46] mitya57: shouldn't entry->image have the same problem? [09:46] cking, hum, https://jenkins.qa.ubuntu.com/job/bootspeed-trusty-desktop-amd64-acer-veriton-01/98/artifact/11/bootchart.png has a long python process eating cpu and io for like 40 seconds [09:46] hi ochosi [09:47] cking, lot of "utah-done.py" running in sequence as well [09:47] cking, seems buggy CI infra to me [09:47] larsu: I can do the same with entry->image, but I didn't see any problems with that. [09:47] seb128, OK, I'll report that back to CI [09:47] thanks [09:47] I.e. all icon-only indicators are working. [09:47] cking, thanks [09:47] hi all, I am having some issue with my ubuntu-raring-minimal if I launch a vncserver and connect to it I keep getting failed to start session "gnome" logout. I have xubuntu installed though [09:47] larsu: not sure you received my note from yesterday about your latest indicator-sound patch (if not, i can quickly re-summarize) [09:48] mitya57: this makes this bug even more mysterious. I hesitate to approve a fix I don't understand [09:48] Tazmain, hey, try #ubuntu for user questions [09:49] ochosi: please summarize again, there were a lot of pings for me last night [09:49] ochosi, hey, oh, did I reply to you with the spec link yesterday? [09:49] seb128: yup, you did :) in case i didn't thank you for it, thanks now! [09:49] larsu: Maybe it's indicator-appmenu's bug that the label has non-NULL parent, and for other indicators it's just not the case. [09:50] ochosi, lol, thanks ;-) [09:51] larsu: In any case, there is zero harm from unparenting, as it doesn't change anything for indicators that already do it right. [09:51] larsu: so, you basically re-added a functionality that was in indicator-sound before, if i recall correctly, i.e. showing another icon (red speaker) when sound is muted but there is playback. that's the context. [09:52] larsu: the problem is, that the icon-name for "blocked" state is not part of the spec for soundmenu, and you went with "audio-volume-muted-blocked-panel" [09:52] larsu: so while this is not a problem in itself, it breaks existing icon-themes (incl. ubuntu-mono), because the icon used to be called "audio-volume-muted-blocking-panel" [09:53] (not the small diff between "blocked" and "blocking") [09:53] ochosi, note that the spec has a name, it uses "audio-volume-muted-panel" [09:53] https://wiki.ubuntu.com/Sound#Title [09:54] seb128: yeah, but that icon-name is there as a fallback in larsu's patch [09:54] seb128: and it's actually a bit wrong, that's the normal "muted" state. the special "red icon" is for the blocked state [09:55] i guess the idea in the spec was to make a difference between normal "muted" state and "muted-blocking"/"muted-blocked" state [09:55] mitya57: we can't say it doesn't change anything, as we don't fully understand where the bug is coming from. Also, there might be more side-effects. I'll have a look in a bit [09:56] ochosi, right, I was just commenting on your statement that the name is not part of the spec [09:56] ochosi, we should get the spec updated to have the right name if the one used is wrong [09:56] e.g talk to mpt about that ;-) [09:57] ok :) [09:57] ochosi: I thought I just used the icon name from the old code... [09:57] larsu: weird... check ubuntu-mono, it has only *-blocking-* [09:57] and elementary-xfce (which i'm maintaining) also has always only had that icon name [09:58] in conclusion: are you sure it wasn't "blocking" before? (it used to work here) [09:58] ochosi, the ubuntu-mono icon seems blue, not red? [09:58] larsu: Thanks a lot. FWIW, there is a link to a code that creates that label in one of the comments. [09:58] the current icon works [09:58] but it comes from humanity [09:58] not ubuntu-mono [09:58] ochosi: ah! It only has blocking, but pulls in blocked from Humanity [09:58] and that's the one we want iirc [09:59] larsu, ochosi: the spec says "red speaker", the blocking one is blue [09:59] the one from ubuntu-mono is blue [09:59] seb128: I think I'd want the blue one in red [09:59] but we should probably ask mpt again [09:59] seb128: I approved that sound mp [09:59] ochosi: thanks for bringing this up. Man, our icons are a mess :-/ [09:59] larsu, right [10:00] I was just going to say that [10:00] with icons -> themes [10:00] and +1 for using blocking if it's red [10:00] because the one we are using atm doesn't match the muted icon [10:00] which looks a bit weird [10:00] that's what I'm thinking [10:00] e.g x against --- [10:00] larsu: yeah, i know... it has taken me *ages* to get elementary-xfce (which originated from the same source as humanity obviously) into shape [10:01] i wouldn't mind helping you guys out with humanity, but then again it feels so useless as your new icon theme will come... [10:01] right, that's why I've been holding off as well [10:01] +1 [10:01] but it's always such a pain to sort things out [10:01] we should fix obvious bugs where we spot them though [10:02] well in this case it's a simple fix [10:02] somebody with icon drawing skills needs to blue->red [10:02] you don't even have to go the long way and "sort things out" :) [10:02] (a) fix the icon (b) fix my patch [10:02] (e.g not me, I've no clue how to do that :p) [10:02] seb128: i can do that if you want [10:02] ochosi, that would be nice [10:02] though why is this icon blue atm? [10:02] mpt, do you know? [10:02] i guess someone designed it that way because they liked it :p [10:03] (not specifically because it makes sense) [10:03] so yeah, if you want to make it red, please do [10:03] mpt: http://i.imgur.com/CRAcGg5.png [10:03] then we can update the indicator to use that one [10:03] hah, the one from humanity has a really different style [10:04] doesn't look very nice/consistent [10:04] right, it looks buggy [10:04] ok, i'll quickly fix that for you... [10:04] mpt: we're using the red one right now, but assume the blue one would be more correct if it were red [10:04] mpt: do you agree? [10:04] ochosi, thanks [10:04] larsu, I like that program (the icon library) ;-) [10:04] seb128: me too :) [10:04] seb128: btw, is it packaged? [10:05] I'm still running it from some old source version [10:05] I don't think so (or in a ppa only), it should [10:05] same here [10:05] it runs fine from srcdir [10:05] it could be a bit faster in switching icon themes :) [10:05] seb128: how/where do you want it? [10:06] ochosi, merge proposal against lp:ubuntu-themes would be best if you can do that [10:06] and: you only need that icon once btw, it's the same in -dark and -light obviously [10:06] ok [10:06] thanks! [10:06] that'll take a while, my connection suuuucks :) [10:06] (note: the icon is finished already, pulling and pushing will probably take 10x longer ;)) [10:08] any other icons that need fixing now that i'm at it? [10:08] not that I know [10:08] larsu, do you know of any? [10:08] (you should really just merge ubuntu-mono and humanity...) [10:08] ochosi, just curious, what did you use to fix it? inkscape? [10:08] seb128: yup [10:09] this was extremely simple, as you only need to change the color [10:09] (yeah, we should ... but as you and larsu said, spending time on that feels pointless since we get a new theme) [10:09] you could theoretically edit the xml directly as well [10:09] ochosi: I think Humanity and ubuntu-mono have different license/copyright. [10:09] true, it just pains me to see the mess :D [10:10] suru-icon-theme is the new theme for touch btw [10:10] I hope that comes to desktop as well [10:11] seb128: no I don't [10:11] ochosi: thanks [10:13] seb128: yep, those are beautiful (kudos again, tiheum!) [10:14] in fact it wouldn't be too hard to port those panel/indicator icons for the desktop... [10:14] i mean of suru-icon-theme [10:14] ochosi, looking through ubuntu-mono in the icon library software, I don't see any other obvious candidate for fixing [10:14] right, it's a bit late now for this cycle though [10:15] seb128, https://bugs.launchpad.net/unity-control-center/+bug/1294578 here it is [10:15] Launchpad bug 1294578 in Unity Control Center ""Match the display settings" checkbox" [Undecided,New] [10:15] I hope it helps... [10:15] hikiko, thanks [10:16] seb128: ok [10:16] yeah, i understand it's late for that [10:18] hikiko: why would I ever want to have this checkbox turned off? [10:19] (I hope I'm not starting a discussion you guys already had earlier) [10:19] lol larsu [10:19] because those are desktop settings [10:20] larsu, seb128: ok, here you go: https://code.launchpad.net/~ochosi/ubuntu-themes/audio-volume-blocking/+merge/211694 [10:21] ochosi, thanks! [10:21] np [10:21] hikiko: what? If I understand correctly, I'll have mismatched scaling for titlebars and window contents when the checkbox is unchecked, right? [10:21] the user might change them from any other program or from u-c-c when he selects larger fonts or when in multimonitor if he plugs a monitor let's say a projector and he needs to check the laptop's monitor while the projector is still plugged to see something or for any reason [10:22] larsu, it depends... [10:23] if it's unchecked because you checked something else or modified a scaling factor outside ucc yes [10:23] what is monitoring those settings to uncheck the checkbox? [10:23] seb128: you have a few more broken symlinks in ubuntu-mono btw [10:23] or do you check whether the scaling factors are the same when I arrive in the settings panel? [10:24] I use a gsetting for the selected-display [10:24] seb128: specifically in ubuntu-mono-dark/status/22/ [10:24] when the selected-display is the current monitor [10:24] ochosi, if you want to fix those as well feel free ;-) [10:24] I check if ui-scale == scaling-factor * text-scaling-factor +- error (very small rounding error) [10:24] if this is not the case [10:25] some factor was modified so I uncheck it [10:25] seb128: yeah, there are a few more in -light... [10:25] larsu, that's not the final widget [10:25] mpt did a much better design [10:25] we just decided to add something that works before 14.04 release [10:26] and then improve it [10:26] but it seems to work fine in multimonitor [10:26] seb128: the main problem seems to be that whoever added the new indicator-keyboard icons must've also removed the old keyboard icon (input-keyboard) from the icon-theme, leaving behind broken symlinks... [10:27] Laney, did you mean to review/+1|-1 that 1 liner for the account panel, or did you just glance over it and prefer to let for robert_ancell? [10:27] I mean you see no inconsistencies like: a button is checked when settings dont match the desktop or things like that [10:27] hikiko: I don't know. It seems overly complicated to me and I can't imagine ever wanting a different scaling factor for title bars and window contents [10:27] hikiko: thanks for clearing it up, though [10:27] seb128: I didn't look into it, seems fine to me but you may want to wait for desrt [10:28] Laney, ok, thanks for testing the sound one! [10:29] larsu, if you have different ui-scale for each monitor since the scaling-factor and text-scaling-factor are for the whole desktop they won't always match your unity display settings [10:29] so the user should choose in which monitor he wants the "perfect" match [10:29] (same scaling) [10:30] that's what the checkbox does [10:30] if your monitors are a retina a laptop screen and a projector [10:30] and they all use a different ui-scale factor [10:31] you have to decide which monitor's ui-scale you want to have in gnome apps and set the scaling-factor and the text-scaling-factor of the whole desktop tou match that [10:31] sorry :) I dont know if I make it more clear or more complicated now :p [10:32] hikiko: you totally did thanks. I understand the problem, but don't like the solution [10:32] me neither :) [10:32] we ll change it after release [10:32] and I'm a bit surprised that gnome's scaling-factor is per desktop and not per monitor [10:32] hikiko: I also don't like mpt's proposed solution... [10:32] yes :/ all scaling factors :/ [10:33] larsu, then we can discuss it further before I submit a branch for it [10:33] but we need to merge the checkbox [10:33] to have the feature [10:33] as we promised [10:33] I mean after we test it ofc [10:34] ochosi, do you plan to send another merge request to fix some of the symlink issues? Just wondering if I should line up your other fix for landing yet or wait for another fix to come [10:40] hikiko: btw, it crashes when I run it http://paste.ubuntu.com/7119084/ [10:41] seb128: yes, pushing already [10:41] Laney, did you install the gsetting? [10:41] yes, look at the bt [10:41] seb128: is it a problem that it was done on top of the soundmenu-icon fix? [10:41] sec [10:42] ochosi, no, not a problem [10:42] ochosi, thanks [10:42] I think that you should look into using glib functions rather than malloc/strcpy [10:42] yes, will fix [10:43] I'm replacing them right now, I forgot it :p [10:43] seb128: MR done [10:46] ochosi, thanks [10:50] seb128: well happy to be able to give something back for all the great support and helpin out this cycle! :) [10:51] (guess now i have to stop looking at ubuntu-mono or i'll start fixing it...) === vrruiz_ is now known as rvr [10:52] ochosi, ;-) [11:05] crap, the glib autopkgtest failed [11:06] :-( [11:19] Laney, fixed [11:20] jibel: oh, env problem? [11:20] Laney, the old rule: when it fails run it again until is passes [11:20] O_O [11:20] I was trying to reproduce it :P [11:21] but, good... I suppose [11:22] seb128, I ll remove the code that sets the primary monitors settings from ucc [11:22] you are right on that [11:22] this should be done by unity [11:22] Laney, apparently gdbus-threading crashed on previous run [11:23] hikiko, unity-settings-daemon probably rather, that's what applies e.g the resolution [11:23] jibel: yep [11:23] +1 seb128 [11:23] I am removing it [11:23] hikiko, btw I like Laney's suggestion of a button === jjardon__ is now known as jjardon [11:24] the only problem is that you have 0 feedback of what is selected/not [11:24] not that the checkbox is the super widget [11:24] :p [11:24] the opposite [11:24] but at least shows something [11:24] jibel: The ubuntu-sso-client one fixed itself too on another run [11:24] all good fun [11:24] Laney, yes, that's pitti-matic at work [11:26] we should just run all tests more than once and only consider a failure if they fail every time :P [11:29] hikiko: I guess it's not 'selected' if you have the buttons, but rather an operation which is performed [11:29] 'run this algorithm now' === MacSlow is now known as MacSlow|lunch [11:48] Laney, I ve fixed the branch, I think that if you try now it will be ok [11:56] hikiko: yeah, it doesn't crash [11:56] so it's totally unclear what that checkbox does [11:57] The design has a "Scale for window contents:" header that we probably want here [11:57] & I still prefer the button idea [11:57] thanks for working on this btw [11:58] ok, it's easy to add the label, I'm not sure that the button does the same thing because the checkbox shows the selection, that's why i prefer the checkbox [11:59] I'll add the Scale.. label as a first step :) [11:59] It doesn't, we're arguing that the current behaviour is complicated and confusing [12:02] I don't disagree on that, I know that the checkbox is not the best widget, I just think that from button and checkbox the checkbox is slightly "better" because it makes clear that only one monitor is selected and which one is this [12:02] bregma, Trevinho ^^ have you seen what Laney suggests? what do you think? [12:03] hikiko, I don't think the checkbox work, for the reason I pointed on the bug [12:03] hikiko, if I select another monitor it's going to show unchecked, but yet the scaling is still active, it's just based on computation from another screen [12:03] no, [12:04] if you select another monitor [12:04] the last monitor selected [12:04] will be used [12:04] that's buggy [12:04] what if I select another monitor to turn it off? [12:04] no, that's what we want [12:04] or to change the resolution [12:04] but I don't want to use scaling from that one [12:04] then you just wont check the button [12:04] it wont be checked by default [12:05] right [12:05] if it's not checked, it makes me thing there is no scaling active [12:05] when there is [12:06] seb128, hikiko: ihmo we should just use one single monitor-idependent "use max scaling across monitors for everything"... That is imho the easiest way to achive sacalability withouth touching things too much [12:06] +1 [12:07] Trevinho, seb128 could you run it? [12:07] hikiko, let me build it [12:07] i think the checkbutton is doing what it should [12:07] you just select the monitor [12:07] and when you move the ui slider [12:07] you see the content scale too [12:07] when unchecked [12:08] you move the slider and the content doesnt scale [12:08] it's very simple i think [12:08] expect that the GTK scaling is not by monitor [12:09] so having the checkbox changing according to the selected monitor is just weird [12:09] it also doesn't solve the conflicts with the accessibility text scaling setting [12:10] seb128, all these are not solved by the button either and are not solved by the current design [12:10] we have to plan a better approach [12:10] hikiko: the fact is... +app_checkbox_activation_deactivatio doesn't need to do anything but changing the setting. As I told you this change must be done in unity itself [12:10] that button is just a partial solution [12:10] Trevinho, the 1st time yes [12:11] hikiko: no, unity will do that [12:11] but then if you plug a projector [12:11] hikiko, well, first thing I really dislike adding yet another gsettings key [12:11] ok [12:11] hikiko: I mean, what UCC only have to do is to change a gsettings key, unity will handle the rest. [12:11] The button idea is meant to be a less confusing way of doing the same thing [12:12] Trevinho, and next time you start ucc [12:13] how would you know which monitor is selected [12:13] to show the buttons checked or unchecked [12:13] the checkbox doesn't convey that info properly imho [12:14] hikiko: if we go for "use the max available scaling", we don't need to know anything [12:14] yes but this doesnt help if you have a projector and a retina and need to swap between them [12:14] hikiko, it's not clear why changing monitor or checking the box for another monitor uncheck the one you had for the first one [12:15] nothing says "only one monitor can be checked at time" [12:15] or "checking that is going to uncheck oher non selected status" [12:15] seb128, +1 I could add labels for that [12:15] A combo would convey it slightly better, but that's also not ideal [12:15] hikiko, if you want to say "the setting apply to <...>" you should have a combo that let you select the monitor [12:15] Why not just using a combo box for selecting wich monitor is the "target"? [12:15] ha [12:15] cool [12:15] that's a good idea :) [12:15] hikiko, same as the "launcher placement" [12:16] yeah [12:16] Trevinho, stop stealing my suggestions :p [12:16] so I ll have a combo on the right with all monitors [12:16] I SAID IT FIRST! [12:16] and choose 1? [12:16] lol [12:16] seb128: ah, I didn't read it, but it just seemed the more natural thing to me :) [12:16]