[00:41] <bluesabre> Greetings! Is it possible to blacklist a package in the live session?
[00:43] <TheMuso> bluesabre: What do you mean by blacklist?
[00:43] <bluesabre> in xubuntu we ship light-locker as a means to lock one's session
[00:44] <bluesabre> it would be beneficial to not have that package installed in the live session
[00:44] <ochosi> (because the timed locking would lock a user out of the live session)
[00:47] <TheMuso> Um, I thought settings were twekaed  on live boot such that the lock screen isn't enabled... I know that happens for Ubuntu...
[00:47] <TheMuso> tweaked*
[00:49] <TheMuso> Maybe xubuntu needs a script that gets loaded by casper to do this for a live session.
[00:49] <bluesabre> ok, I'll take a look at that
[00:49] <bluesabre> thanks for the suggestion
[00:51] <TheMuso> np
[08:37] <hikiko> hi :)
[08:44] <hikiko> how can I see the current version of a trunk package to add it as a dependency on another pakage's control?
[08:45] <hikiko> most packages in debian control have a version (>= version_number)
[09:00] <seb128> good morning desktopers!
[09:01] <seb128> hikiko, there is no "current version of trunk", you either use ">> current_archive_version", assuming the next upload is going to have your change or you wait for the upload to tweak the version
[09:01] <seb128> hikiko, did you get any designer feedback on the control center UI? I read your comment, the backend requirements shouldn't dictate the UI though...
[09:02] <seb128> mpt, hey, do you think you could have a look/comment on the UI/design of https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.per-monitor-fonts-scale-factor-slider/+merge/205227 (http://imgur.com/cVlLyV0)
[09:07] <hikiko> seb128, I think bregma asked some designer at some point but I will discuss with him again for sure, maybe I have to move the slider on the left
[09:08] <seb128> hikiko, is that setting only about fonts?
[09:08] <Laney> morning chaps
[09:09] <seb128> Laney, hey, how are you?
[09:09] <Laney> seb128: good thanks, although my arms are feeling the pain from climbing :P
[09:10] <hikiko> seb128, no, it's for all ui-components in Unity8/QML apps (Kaleo will know for sure) in Unity7 it's for fonts but since everything is rendered according to the EM size it's for everything...
[09:10] <Laney> might have gone a few too many times lately ...
[09:10] <seb128> hikiko, the label is misleading then
[09:10] <seb128> Laney, hehe, I know the feeling ;-)
[09:13] <Laney> I've been 4 times in 5 days :(
[09:13] <Laney> how are you doing?
[09:13] <seb128> Laney, what do you think about adding ubuntu-schemas to the ubuntu-settings source?
[09:13] <Laney> you mean merging gsettings-...?
[09:14] <seb128> Laney, I'm good thanks
[09:14] <seb128> Laney, yeah, "merging/superseeding"
[09:15] <Laney> yeah if you like, that should be easy to do
[09:15] <seb128> also I don't remember know why you made gsettings-ubuntu-touch-schemas depends on ubuntu-touch-sounds but that's a depends we don't want on the desktop
[09:15] <Laney> I did not
[09:15] <seb128> Laney, yeah, doability is fine, I was wondering if you think it's a good idea ;-)
[09:16] <Laney> https://code.launchpad.net/~laney/gsettings-ubuntu-touch-schemas/no-sounds-dep/+merge/192314
[09:16] <seb128> Laney, hum, sorry, seems like I got that backward, I remember we discussed if the default value should be pulled in
[09:17] <Laney> well, I can think that it mixes up the idea of 'upstream' and 'downstream'
[09:17] <seb128> did I argue in favor of the depends by then?!
[09:17] <Laney> yeah but I think you were convinced in the end
[09:18] <hikiko> seb128, you are right, I didn't replace it when I renamed the fonts_scale_factor to ui_scale..
[09:18] <hikiko> thanks!
[09:18] <seb128> hikiko, yw
[09:19] <seb128> Laney, I sure am convinced :p
[09:19] <Laney> ;-)
[09:19] <mpt> seb128, done
[09:19] <seb128> Laney, well, with daily landing, CI, etc, there is no much downstream/upstream difference nowadays
[09:19] <seb128> mpt, thanks!
[09:20] <Laney> hmm
[09:20] <Laney> It's like ubuntu-settings overrides GNOME stuff but then we also randomly provide schemas for things in there too
[09:20] <Laney> 'this package is vaguely to do with gsettings'
[09:20] <seb128> hikiko, we got design input on the mp, thanks to mpt, please address his comment as well (I'm going to handle the schemas thing)
[09:23] <hikiko> let me see :)
[09:24] <seb128> Laney, ideally regrouping things (like we regrouped themes in icon themes in ubuntu-themes) would be nice
[09:24] <seb128> less sources/projects to handle
[09:29] <hikiko> ok let's move the slider to the left :)
[09:29] <seb128> sil2100, didrocks: hey, would it be easy to put unity-system-settings and unity-control-center under CI train? they have auto commits atm so I guess they are set up in the old autolanding way
[09:31] <didrocks> seb128: should be easy, I guess you just need to tag latest release to avoid having a crazy changelog
[09:31] <sil2100> seb128: it should be relatively fast and easy, we just need to disable the auto-landing and then one tag to have all ok
[09:31] <seb128> didrocks, sil2100: thanks, what sort of tag?
[09:32] <seb128> can you do it/let me know what to do?
[09:32]  * didrocks looks at the code before telling wrong things :)
[09:32] <didrocks> one sec
[09:32] <didrocks> seb128: ok, it's just the package version
[09:33] <seb128> didrocks, sil2100: you have your daily morning call now? feel free to get back to me after it, no hurry there
[09:33] <didrocks> (including the -0ubuntu…)
[09:33] <didrocks> yeah
[09:33] <didrocks> just put that and the bot will only collect after that tag
[09:33] <seb128> ok
[09:33] <seb128> I need a manual commit to push a tag?
[09:34] <didrocks> I think you can push it with --overwrite without a commit, but not garantee
[09:34] <didrocks> no*
[09:34] <seb128> let me try
[09:34] <seb128> I just need to fresh checkout and look at the tags to verify
[09:49] <seb128> didrocks, in fact debcommit -r tagged things already, we should be fine for unity-control-center I think
[09:49] <seb128> $ bzr tags | grep 14.04.3
[09:49] <seb128> 14.04.3-0ubuntu1     12707
[09:50] <seb128> sil2100, ^
[09:50] <didrocks> seb128: great! at worst, it's a big (incorrect) changelog anyway…
[09:50] <didrocks> sil2100: mind putting that one? ^
[09:50] <sil2100> didrocks: you mean, like, disabling from cu2d? ;)
[09:51] <sil2100> (and adding seb as the lander)
[09:52] <seb128> didrocks, sil2100: unity-settings-daemon should good to go as well
[09:55] <didrocks> sil2100: yeah, seb as lander, disabling with the usual parameters
[09:55] <didrocks> seb128: do you mind adding it to the bootcamp spreadsheet?
[09:56] <didrocks> (trying to have a list of our projects)
[09:56] <didrocks> so that later on, you can subscribe, and so on
[09:59] <seb128> didrocks, sil2100: done, l80&81 (inserted bellow g-c-c-unity to keep logical units)
[09:59] <didrocks> thanks!
[09:59] <seb128> yw ;-)
[10:00] <didrocks> sil2100: tell us once done
[10:01] <sil2100> seb128: where can I find unity-system-settings ?
[10:02] <seb128> sil2100, unity-settings-daemon you mean?
[10:02] <seb128> sil2100, https://code.launchpad.net/unity-settings-daemon
[10:03] <seb128> https://code.launchpad.net/~unity-settings-daemon-team/unity-settings-daemon/trunk
[10:04] <sil2100> seb128: ah, those I know already ;) You mentioned something about unity-system-settings in the backlog and I was thinking if I missed anything
[10:04] <seb128> sil2100, my fingers typoed, those projects are too close :p
[10:04] <seb128> sil2100, I mean unity-control-center and unity-settings-daemon
[10:12] <sil2100> seb128, didrocks: reconfigured ;) All should be ok now
[10:12] <seb128> sil2100, meaning I can go through CI train for those now?
[10:14] <seb128> Laney, I was just pondering taking that new gtk-doc or not, quite some changes, good that you went for it, spare me the extra thinking ;-)
[10:14] <Laney> glib depends on it :P
[10:15] <sil2100> seb128: yes
[10:15] <seb128> Laney, yeah, new gdk-pixbuf as well (was looking at this one)
[10:15] <Laney> nod
[10:16] <seb128> Laney, can you +1 https://code.launchpad.net/~seb128/unity-settings-daemon/hidpi-screen-support/+merge/207125 for me? I want to try CI train land u-s-d
[10:17] <seb128> Laney, that patch is already in g-s-d so it should be fine
[10:18] <Laney> seb128: g-s-d in ubuntu?
[10:18] <seb128> Laney, yes, https://launchpad.net/ubuntu/+source/gnome-settings-daemon/<IP_ADDRESS>-0ubuntu3
[10:18] <Laney> ack
[10:18] <seb128> thanks
[10:20] <Laney> done
[10:23] <seb128> thanks
[10:27] <seb128> sil2100, ok, put requests for the 2 new components, let's see how that goes
[10:49] <seb128> didrocks, https://launchpad.net/~ci-train-ppa-service/+archive/landing-005/+sourcepub/3923487/+listing-archive-extra
[10:49] <seb128> didrocks, changelog worked ;-)
[10:49] <didrocks> excellent! :)
[10:49] <didrocks> u-c-c railing the train!
[10:50] <seb128> tjaalton, ^ btw, I think you were interested in new wacom?
[10:50] <seb128> didrocks, and u-s-d! https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+sourcepub/3923493/+listing-archive-extra
[10:50] <didrocks> hehe "niceeeeee" ;)
[10:50] <seb128> ;-)
[10:50] <didrocks> seems people try to challenge the ci train wrapping :)
[10:50] <didrocks>     change the scaling value by writting the
[10:50] <didrocks>     "org.gnome.desktop.interface scaling-factor" gsettings key
[10:51] <didrocks> :)
[10:51] <seb128> ;-)
[11:22] <hikiko> seb128 and Laney could you please get one more look at this:
[11:22] <hikiko> https://code.launchpad.net/~hikiko/gsettings-ubuntu-touch-schemas/scale-factor-for-unity7-unity8/+merge/206240
[11:22] <hikiko> (thanks!)
[11:23] <seb128> hikiko, sure
[11:23] <seb128> though I'm a bit confused at what Laney wants with the packages sources/names atm
[11:23] <hikiko> oh sorry
[11:24] <hikiko> I thought Lane and Laney is the same person :)
[11:24] <seb128> why is picking names always so annoying :p
[11:24]  * Laney hulks out
[11:24] <hikiko> sorry sorry :)
[11:24] <Laney> that is me
[11:24] <Laney> you weren't wrong :P
[11:24] <seb128> hikiko, he is
[11:24] <hikiko> then because he reviewed it already
[11:25] <Laney> seb128: umm I don't want to block you doing what you think is right, it just feels a bit weird is all
[11:25] <Laney> renaming the binary is A-OK as far as I'm concerned
[11:25] <Laney> 'it' being merging the sources
[11:26] <seb128> Laney, I've no strong opinion either way, that's the sort of details I don't care much about
[11:26] <Laney> then my preference is to rename the binary package and ideally the source but probably do that later on
[11:26] <seb128> robert_ancell started on merging sessions, settings, etc in http://code.launchpad.net/~robert-ancell/+junk/ubuntu-session
[11:27] <seb128> but I though moving the gnome-session .session files in there were touch much
[11:27] <seb128> ok
[11:27] <seb128> let's do it easy then
[11:27] <seb128> renaming the binary to "ubuntu-schemas"
[11:27] <seb128> ?
[11:28] <Laney> gsettings-ubuntu-schemas I think
[11:28] <Laney> and the AS one too
[11:29] <seb128> right
[11:29] <seb128> do you want to do it maybe? ;-)
[11:29] <seb128> (if not that's fine, I'm going to have a look next, after landing the new u-c-c and u-s-d)
[11:29] <Laney> could do in a bit perhaps
[11:29] <Laney> just testing glib and dconf
[11:29] <seb128> k, let me know if you start on it
[11:30] <Laney> then I will see about webkit
[11:30] <seb128> I've a few items/updates I started on
[11:30] <seb128> but I'm going to have a look in the afternoon if you don't beat me to it
[11:30] <Laney> hopefully upload that today
[11:30] <Laney> ok
[11:30] <Laney> hikiko: looks ok to me now!
[11:31] <hikiko> :D
[11:31] <Laney> I wouldn't have been so verbose in the description (the bit where you justify int vs float) but it's okay
[11:32] <Laney> also I'm interested in how this will interact with what gnome does
[11:33] <Laney> I suppose config tools will have to write two keys at some point
[11:33] <hikiko> ops sorry
[11:33] <Laney> no worries, it's fine
[11:35] <hikiko> well in unity7 you either change the text-scaling-factor and see the same size in each monitor
[11:35] <hikiko> or you use the ui-scale and you change the scaling per monitor
[11:35] <hikiko> if you only have 1 monitor
[11:35] <hikiko> then I guess it's almost the same
[11:35] <hikiko> for unity7 at least
[11:42] <seb128> bregma, Trevinho_, the new unity with hidpi support is buggy for me, on my external monitors in 1920 resolution the launcher/panel are bigger after the update
[11:42] <seb128> where they should not, that's not an hidpi screen and the old default was fine, the new factor seems wrong
[11:52] <xnox> seb128: what's your dpi? xdpyinfo | grep dots ?
[11:52] <seb128> xnox,   resolution:    96x96 dots per inch
[11:53] <xnox> seb128: that should factor 1...
[11:54] <xnox> seb128: where are these hidpi merge proposals / ppas that I can try?
[12:08] <seb128> xnox, sorry, was dealing with lunch getting ready ;-)
[12:09] <seb128> xnox, https://launchpad.net/~ci-train-ppa-service/+archive/landing-003/
[12:09] <xnox> seb128: burned much?! =)))
[12:09] <seb128> lol, no, it was alright and I'm done eating ;-)
[12:09] <seb128> xnox, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc#gid=21 has the list of vcses
[12:10] <seb128> if you want the code details
[12:10] <xnox> seb128: thanks.
[12:11] <seb128> yw
[12:11] <seb128> looking to https://code.launchpad.net/~brandontschaefer/unity/launcher-high-dpi-dynamic-resize/+merge/203176 they changed the units to be _em values
[12:12] <seb128> but I guess that's already in the code, was just not used before, so the change to review might not be in that list
[12:13] <xnox> seb128: i'm yet to figure out how to do dpi in e.g. plymouth and lightdm.
[12:13] <xnox> seb128: i guess system-wide setting for lightdm should be to autoscale.
[12:14] <seb128> xnox, lightdm runs u-s-d, that sets the autoscale factor for gtk, which should took care of part of the issue
[12:14] <seb128> well, unity-greeter rather than lightdm
[12:15] <xnox> seb128: yes and no, as patterns and logos are rendered at fixed px based offsets and sizes...
[12:15] <seb128> right
[12:16] <xnox> seb128: the grid dots, the bottom left logo, and centered (other monitor logo), frames around text input - should all dpi scale.
[12:16] <xnox> seb128: unless cairo changes it's layout to be dpi-wise rather then pixel wise?
[12:18] <seb128> no, I don't think so
[12:28] <happyaron> seb128: btw, I came back from NUDT this afternoon, will continue ibus work tomorrow
[12:29] <seb128> happyaron, ok, thanks
[12:29] <seb128> happyaron, did the "disable ctrl-space by default" looks fine to you?
[12:29] <happyaron> the patch looks fine, but I'm not able to test it when at NUDT
[12:30] <seb128> happyaron, ok
[12:31] <seb128> happyaron, how is Kylin work looking for feature freeze?
[12:32] <happyaron> seb128: they are mostly focused on cooperation projects with commercial companies, no big action regarding the distro itself.
[12:32] <seb128> ok
[12:32] <seb128> shrug, I could use with bugzilla being up
[12:33] <happyaron> FJ and I will go to a partner's office maybe in next week, for the cooperation project of input method.
[12:33] <seb128> ok
[12:34] <happyaron> and getting a station, which we don't have at our office, :P
[12:34] <seb128> station?
[12:35] <happyaron> I mean a seat in office, dunno which word is proper to describe.
[12:39] <seb128> oh, I see
[12:42]  * desrt yawns
[12:42] <seb128> desrt, good morning!
[12:43] <Laney> gähn
[12:43] <Laney> greetings desrt
[12:43] <Laney> seb128: i'm doing the renames now
[12:43] <seb128> Laney, thanks
[12:43] <desrt> good morning, peeps
[12:43] <seb128> Laney, then we can CI train landing it since u-c-c is there as well now
[12:43] <Laney> want to get the depends there fixed to gsettings-ubuntu-schemas?
[12:44] <seb128> yes please, I should approve that mp you pointed earlier
[12:44] <tjaalton> seb128: yes, updated wacom backend for u-c-c/u-s-d?
[12:44] <seb128> tjaalton, robert_ancell did https://code.launchpad.net/~robert-ancell/unity-control-center/wacom-panel-3.8/+merge/207082
[12:45] <seb128> tjaalton, I guess we need to update the unity-settings-daemon side as well
[12:47] <tjaalton> seb128: yeah i think so. i'll be able to test these next week
[12:47] <seb128> tjaalton, great, thanks, let us know how it goes
[13:46] <xnox> merging acpid and adding unity-settings-daemon support to it...
[13:47] <seb128> xnox, that is using g-s-d?
[13:48] <xnox> seb128: it does nothing if g-s-d is running...
[13:48] <seb128> hum, k
[13:49] <xnox> seb128: it manages powerbutton policy (e.g. what to do) but it should do something on e.g. headless servers, not when there is u-s-d and unity pooping up a dialog "sleep shutdown restart"
[13:49] <seb128> right, I wonder if that's what makes my system shutdown when pressing the power button (rather than opening the dialog)
[13:50] <seb128> (I'm running u-s-d)
[13:50] <seb128> I noticed that some days ago and have it on my "to debug" list
[13:52] <xnox> seb128: upgrade to new acpid, when that builts and let me know.
[13:53] <seb128> xnox, sure, thanks for the letting us know about the issue/update!
[13:54] <xnox> seb128: i'm just franticly going though my outstanding merges list, trying to fix up everything what will be useful in an lts at the moment.
[13:56] <seb128> xnox, yeah, makes sense
[13:56] <seb128> Trevinho, let's move here, the other channel is a bit busy
[13:56] <seb128> Trevinho, I didn't realize you would use the text scaling as an UI scaling
[13:56] <Trevinho> ok
[13:57] <seb128> Trevinho, the key for gtk scalling upstream is "org.gnome.desktop.interface scaling-factor"
[13:57] <seb128> not text-scaling
[13:57] <Trevinho> seb128: that was a late thing we added both for testing and because I thought it's what we wanted as well... I.e. using that value as minmum scaling factor anyway
[13:57] <Trevinho> ouch
[13:57] <Trevinho> ok... I can fix it in a small branch
[13:57] <seb128> thanks
[13:57] <Trevinho> can still we add this to the queue?
[13:57] <seb128> sure
[13:58] <seb128> you just need to edit the gdoc and ask for the silo to be reconfigured
[13:58] <seb128> but I'm fine if that happens in another round, I guess not a lot of people use the text-scaling
[13:58] <seb128> btw that key is set by the a11y -> big text option
[13:58] <Trevinho> yes
[13:59] <Trevinho> in fact that's why I wanted to supprot this as well
[13:59] <seb128> well, the setting says "text"
[13:59] <Trevinho> because for a11y issues having everything scaled up was something better I thought
[13:59] <seb128> not UI :p
[14:00] <seb128> Trevinho, well, personally I've no a11y issue, the default font is just a bit small and I get tired at the end of the day, and since we have no UI for font size I went for the big text one
[14:01] <seb128> but unity really looks not so nice with that scaling factor applid
[14:02] <Trevinho> seb128: yeah, the fact is that things won't scale, at least not everything... SO... I guess we still need to use the text-scaling factor as our base scaling factor if defined, don't you agree?
[14:02] <seb128> Trevinho, it feels wrong to have an option called "big *text*" which increases your launcher and panel
[14:02] <mdeslaur> seb128: seems new compiz is placing new windows across boundaries...is that a known issue?
[14:02] <seb128> mdeslaur, define "across boundaries"?
[14:03] <seb128> I think Trevinho has a fix submitted for decoration issues
[14:03] <mdeslaur> seb128: when I open a terminal on workspace 1, the window gets put at the bottom of the screen with part of it in workspace 3
[14:03] <Trevinho> mdeslaur: on the bottom it happens yes... known issue, I've on my list
[14:03] <seb128> mdeslaur, what Trevinho says then
[14:03] <mdeslaur> Trevinho: ok, cool, thanks
[14:04] <seb128> mdeslaur, you are picky about your desktop, that's good ;-)
[14:05] <mdeslaur> seb128: hehe, yes, I do enjoy it when it works properly :)
[14:05] <mdeslaur> Trevinho: FYI, it also places new windows with the title bar hidden behind the global menu
[14:06] <mdeslaur> probably the same issue
[14:06] <seb128> Trevinho, ok, so those text-scaling scaling-factor <new-setting-by-screen-you-guys-are-adding> confuse me
[14:06] <seb128> Trevinho, I've no real opinion on how things should behave but that seems like bug fix material for after ff if the behaviour is wrong
[14:07] <Trevinho> mdeslaur: mh, that's weird...
[14:08] <mdeslaur> Trevinho: only seeing it with virt-manager though, not sure why
[14:09] <Trevinho> seb128: well, the main thing was to get unity scale up (and down) keeping it working with no regression, and that's what we are doing... But some details still need to be improved.
[14:09] <mdeslaur> Trevinho: ie: switch to a new workspace, open terminal, terminal is correctly placed lower than global menu. Open virt-manager, virt-manager goes beside the terminal, but with titlebar hidden underneath global menu
[14:11] <Trevinho> seb128: mh that scaling factor value gnome has is quite hard to use since it's an integer [0...4294967295]... but... 2 is already scaling of factor 2, so it's too much
[14:11] <Trevinho> seb128: we want scaling factor steps in float
[14:12] <Trevinho> seb128: so, for now I'll just disable the usage of text-scaling-factor
[14:12] <seb128> Trevinho, well, you guys are adding a new setting no?
[14:12] <Trevinho> seb128: yes, but I also would have loved to have gtk apps to scale with us
[14:14] <seb128> Trevinho, well, gtk apps are going to scale by 2
[14:15] <seb128> through u-s-d/scaling-factor
[14:15] <Trevinho> seb128: I guess we'd need to patch gtk then to adapt to our scaling... as we support also scaling 1.5.. or less
[14:15] <Trevinho> and cairo can do that... so it shouldn't be hard (/me hopes)
[14:15] <seb128> Trevinho, there is a reason gtk did int values, it's not going to be that easy
[14:16] <seb128> you can't do half pixels
[14:16] <Trevinho> no, sure...
[14:16] <seb128> 3*1.5=4.5 bog
[14:16] <seb128> Trevinho, well, let's already land the new stuff for ff and then see where we stand/what we can fix/improve
[14:17] <Trevinho> ok
[14:17] <seb128> Trevinho, I'm going to test again new unity with text-scaling to 1, feel free to keep using that key for easy testing until the new settings land
[14:18] <Trevinho> seb128: ok, ah decorations scaling is to-be-fixed in these branches... I already have the code, but I'm pushing that later today
[14:18] <Trevinho> I mean, it's working but window buttons are not so nice...
[14:18] <Trevinho> (another good thing of new decos btw)
[14:22] <Trevinho> seb128: there's one thing that gnome scaling factor seem to cause: gdk display at that point rerturns has wrong geometries...
[14:23] <Trevinho> I mean, they're scaled as well I think
[14:23] <Trevinho> so the launchers, panels have wrong size
[14:23] <Trevinho> should I scale them as well?!? :o
[14:23] <seb128> no idea about that
[14:28] <xclaesse> hm, where is mardy ?
[14:29] <xclaesse> seb128, did you see https://01.org/gsso/ ? is that a fork of ubuntu's SSO ?
[14:29] <seb128> xclaesse, kenvandine mentioned it before
[14:29] <seb128> that's not new
[14:30] <seb128> that's based on the same stack, they "just" replace the qt part by a glib based one
[14:30] <kenvandine> they keep it mostly compatible
[14:31] <xclaesse> oh, that's the rewrite of the qt part for tizen?
[14:31] <kenvandine> yup
[14:31] <xclaesse> I remember mardy told me about that a long time ago
[14:44] <Trevinho> seb128: so yes I've to scale also the monitor sizes to get that scaling factor to work... I don't know if it's something wanted by gdk...
[14:45] <Trevinho> seb128: however, I've moved to use that setting and it works ok
[14:45] <seb128> k
[14:45] <Trevinho> seb128: decorations dragging/resizing is supported in a different branch though, but that can be landed in fe hours
[14:46] <seb128> Trevinho, ok, well up to you guys to handle the landing, bregma has access now I think
[14:46] <seb128> Trevinho, but let me know if I can help
[14:47] <seb128> imho you guys should land that first round of hidpi work
[14:47] <Trevinho> seb128: ok
[14:47] <seb128> so you can move on on landing other features
[14:47] <Trevinho> seb128: this is the MR fyi
[14:47] <Trevinho> https://code.launchpad.net/~3v1n0/unity/hdpi-gnome-scaling-factor/+merge/207217
[14:47] <seb128> like the lock screen
[14:47] <seb128> Trevinho, thanks
[14:47] <bregma> Trevinho, do you ever actually sleep?
[14:47] <Trevinho> bregma: yes... like 6 hours... :)
[14:47] <Trevinho> no, almost 7 actually :D
[14:48] <Trevinho> FFs are always a physical exercise to me... BUt this one is quite relaxed compared to the one in the past... As I've mostly had to help with other's stuff :)
[14:49] <Trevinho> seb128: ops, the MR was wrong.. I didn't set the prereq ;:D
[14:50] <ochosi> bregma: i presume you're too busy today, but in case you'd wanna sponsor light-locker-settings, that'd be awesome! https://bugs.launchpad.net/light-locker-settings/+bug/1281536
[14:50] <ubot2`> Launchpad bug 1281536 in light-locker-settings "[needs-packaging] light-locker-settings" [Wishlist,In progress]
[14:50] <Trevinho> bregma: so, we'd need to get this in the train of Brandon's branches https://code.launchpad.net/~3v1n0/unity/hdpi-gnome-scaling-factor/+merge/207219
[14:54] <bregma> Trevinho, we'd need bschaefer's review of that first, there was a reason we were not using the GTK scaling factor like that and he has the background and information to explain
[14:55] <Trevinho> bregma: he told me the problem was that it's an integer... so we couldn't scale of 1.4 for example
[14:55] <Trevinho> bregma: now, this change doesn' actually does anything but using that integer value adn allowing scaling by 2, 3....
[14:56] <Trevinho> bregma: anyway that's something that we're going to ignore afterwards
[14:56] <Trevinho> bregma: I put that only to have a setting to play with, but... I could get rid of it
[14:56] <Trevinho> the fact is that I would like to land all this stuff asap, to have still time for the next stuff
[14:57] <bregma> Trevinho, we might just have to include it in the next landing, I don't want to restart the AP test run because it takes 3 hours
[14:58] <Trevinho> bregma: ah ok sure
[14:58] <bregma> Trevinho, I notice when I unhide the Launcher now it moved the whole desktop to the right... have you seen that?
[14:59] <Trevinho> bregma: you mean, when you change the option?
[15:00] <Trevinho> bregma: if yes, that's a feature... actually a feature of nautilus itself as there isn't a dock on the left anymore
[15:00] <bregma> I have the Launcher set to autohide, and when I unhide it, the icons I have lying around on the desktop jump to the right, like the whole desktop is moving
[15:01] <bregma> then they jump back when the Launcher hides again
[15:01] <bregma> the indicator ordering is all messed up, too
[15:01] <ochosi> bregma: nvm, Laney seems to be looking at it already (thanks a lot Laney !)
[15:01] <Laney> np
[15:02] <Trevinho> oh, no
[15:02] <Trevinho> bregma: that's with last branches or trunk?
[15:02] <xnox> seb128: new acpid is in release pocket.
[15:02] <seb128> xnox, thanks
[15:02] <seb128> attente_, hey
[15:02]  * Trevinho has not it here
[15:02] <Laney> ochosi: I'm just going to make some minor fixes while uploading, hope that's ok
[15:02] <attente_> seb128, hi
[15:02] <ochosi> Laney: absolutely
[15:02] <bregma> Trevinho, latest landing PPA, but the system may very well be messed up, it's a development machine taht gets that way sometimes
[15:03] <seb128> attente_, I'm having issues with indicator-keyboard tests, maybe you can help me
[15:03] <seb128> attente_, 	public void test_activate_text_entry_settings () {
[15:03] <seb128> attente_, 		stderr.printf ("_service.command = \"%s\"\n", (!) ((!) _service).command);
[15:03] <seb128> attente_, where is that command coming from?
[15:03] <ChrisTownsend> Trevinho: bregma: I have messed up indicator icon ordering with latest landing PPA.  I did not have this with Unity from main.
[15:03] <Trevinho> bregma: yeah, but well.. I'm running that code now and I don't have it here... but, latest merges/remerges might have caused a regression
[15:04] <attente_> seb128, the command is the property in the Service class in the same file
[15:04] <seb128> ChrisTownsend, Trevinho, bregma: oh, I had that as well, tomboy was top right for me, instead of session
[15:04] <ChrisTownsend> bregma: However, I don't see the Launcher unhide issue you describe.
[15:04] <Trevinho> :o
[15:04] <attente_> seb128, when the command is executed, the only thing the service does is set that string and trigger a notify
[15:04] <Trevinho> what it landed?
[15:05] <ChrisTownsend> Trevinho: What do you mean?
[15:05] <attente_> seb128, so during the test, when we spawn something like gucharmap, the test can know, "ok, it was executed", without having to run the actual gucharmap
[15:05] <Trevinho> ChrisTownsend: I dont' know what might have been caused that
[15:06] <ChrisTownsend> Trevinho: Not sure. I'll purge the landing PPA and see if it goes back to normal.
[15:06] <seb128> attente_, ok, I'm overlooking something then, but http://bazaar.launchpad.net/~seb128/indicator-keyboard/use-unity-control-center/revision/272 makes the test unhappy and I don't understand why
[15:07] <attente_> seb128, oh... probably because it's missing the symlink that would call the dbus method
[15:07] <seb128> attente_, oh, in tests/execute
[15:07] <seb128> attente_, thanks
[15:08] <Trevinho> ChrisTownsend: I made a change in libindicator but no ABI/API changed
[15:08] <seb128> attente_, I greped the source, I didn't think there were symlinks for it
[15:08] <seb128> attente_, the mp is coming your way in a few minutes ;-)
[15:09] <attente_> seb128, ok, thanks!
[15:09] <ChrisTownsend> Trevinho: Yeah, with just the landing PPA purged, indicators are back in the correct order, so it's something in one of the MP's.
[15:09] <seb128> Trevinho, it's not libindicator, that landed yesterday
[15:09] <seb128> but I confirm what ChrisTownsend says
[15:09] <Trevinho> oh, wait I see it
[15:10] <Trevinho> it's ups there
[15:10] <Trevinho> let me check what changed
[15:10] <seb128> bregma, ^ you are going to need a new round to land that ppa, you can start adding vcses to the request and ask for a silo reconfigure
[15:11]  * ChrisTownsend Hears bregma groan about having to stop his Autopilot run
[15:11] <Trevinho> uff, yeah I told Brandon to fix an issue last night, but had not the current trunk... so my diff was not the same, and the criss-cross merge made the rest I guess
[15:11] <bregma> ah, Brandon's famous criss-cross merge
[15:11] <Laney> ochosi: You could avoid some of those things in rules by fixing the makefile
[15:12] <Trevinho> let me see
[15:12] <Laney> like `install' lets you specify the permissions directly & I wouldn't install INSTALL and COPYING personally
[15:12] <ochosi> Laney: hmm, sorry, i only helped write the app, the packaging was done by someone else... :/
[15:12] <Laney> other than that, looks good -- I'll sponsor
[15:12] <Laney> sure
[15:12] <Laney> you can pass the message on ;-)
[15:12] <ochosi> thank you very much!
[15:12] <ochosi> i will :)
[15:14] <bregma> Trevinho, if you can get something ready to fix those indicators, I'll add the other stuff to the silo, I don't think we have time for two separate landings
[15:14] <Trevinho> bregma: it's alerady done...
[15:16] <seb128> attente_, ok, that worked, thanks! https://code.launchpad.net/~seb128/indicator-keyboard/use-unity-control-center/+merge/207225
[15:35] <Laney> ochosi: ok, done
[15:36] <ochosi> Laney: you're the best! a big thank-you from the xubuntu community
[15:36] <Laney> yw
[15:36] <ochosi> Laney: very much appreciated, even more so one day before FF...
[15:37] <Laney> I think it'd have been alright anyway as you got the request in in time
[15:37] <Laney> but still
[15:46] <ochosi> Laney: in fact we're having a tough time this cycle, as our uploaders are MIA or really busy with RL. still hoping to get some default-settings stuff and seed-changes merged :/
[15:46] <Laney> ochosi: yeah, it's hard
[15:46] <Laney> best thing is to get the stuff in the queue
[15:46] <ochosi> yeah, but the problem is that we have nobody with even merge-rights to some of our branches
[15:47] <ochosi> so we have like 10 merge-requests pending
[15:47] <ochosi> (all approved by the xubuntu project lead)
[15:47] <ochosi> anyway, i don't wanna whine here, thanks for your help so far :)
[15:48] <ochosi> if you think that sponsors can also be asked to merge stuff, then i'd ask around
[15:48] <Laney> yeah, they should be able to
[15:48] <Laney> just put it all in a bug for ubuntu-sponsors
[15:49] <ochosi> oh, ok
[15:49] <ochosi> will try that then
[15:49] <ochosi> although it's quite optimistic, considering how "late" it is
[15:51] <Laney> that kind of stuff is okay after FF
[15:51]  * Laney beams positivity to ochosi
[15:51] <ochosi> thanks Laney :)
[15:51] <ochosi> much appreciated, really
[16:16] <seb128> Laney, do you want to do the CI train landing for landing the schemas rename? (or do you think we should batch that with the new key/u-c-c changes in a silo later in the week?)
[16:18] <Laney> seb128: either would be fine, could take the rename/dep drop now
[16:18] <seb128> Laney, let me test https://code.launchpad.net/~hikiko/unity-control-center/unity-control-center.per-monitor-fonts-scale-factor-slider/+merge/205227 to see if it's ready for landing
[16:21] <mlankhorst> ok uploading mesa 10.1
[16:22] <Laney> seb128: yeah, getting it all in sooner avoids the need for FFe
[16:23] <seb128> Laney, story of my week :p
[16:23] <Laney> ;-)
[16:23] <seb128> but I'm getting there
[16:23] <seb128> I've a couple of "update panels" for u-c-c I want to do
[16:23] <seb128> but I think otherwise we are good
[16:23] <seb128> well "we" doesn't include unity
[16:23] <seb128> those guys are screwed for ff
[16:24] <mlankhorst> all aboard the ci train :>
[16:25] <attente_> is it too late for me to merge this for FF? https://code.launchpad.net/~attente/indicator-keyboard/ibus-panel
[16:25] <Laney> FF is tomorrow 2100UTC ish
[16:26] <Laney> so no, but ideally get someone to review for you today if possible
[16:26] <Laney> otherwise exceptions can happen ...
[16:27] <attente_> ok, i'll propose it then...
[16:27] <attente_> thanks Laney
[16:28] <seb128> attente_, I can review that tomorrow, so keep hacking on it today if needed
[16:28] <attente_> seb128, ok, it's just that there are two bugs that are haunting it...
[16:28] <seb128> attente_, what impact do they have?
[16:28] <Laney> today allows for iterations
[16:28] <seb128> if it's like "use 100% cpu while it's running" we shouldn't land
[16:28]  * Laney puts the curling on
[16:28] <attente_> lol
[16:29] <attente_> nothing that severe...
[16:29] <seb128> if they are "the menu doesn't always refresh" that's ok
[16:29] <seb128> attente_, I'm asking because desrt mentioned "50 dbus message by keypress" yesterday :p
[16:29] <seb128> or something around those lines
[16:29] <seb128> attente_, well, anyway, your call ;-)
[16:30] <seb128> attente_, I'm giving it a test in a bit
[16:30] <attente_> haha.. yeah..
[16:30] <seb128> joke aside, what are the bugs?
[16:31] <attente_> the menu doesn't always refresh correctly and the radio dot is missing
[16:40] <hikiko> seb128, fixed :)
[16:40] <seb128> hikiko, thanks
[16:42] <seb128> hikiko, the slider gives me a "0.5" value, is that normal?
[16:42] <seb128> hikiko, shouldn't the default be "1"?
[16:42] <pitti> Good morning
[16:43] <hikiko> let me see seb128 because the value we show is not the value we store
[16:44] <hikiko> sec
[16:45] <seb128> pitti, hey, how are you?
[16:46] <seb128> pitti, https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/711549 seems to be back, do you know if that's a known issue/regression (the bug was fixed in udisk maybe udisks2 has the same issue?)
[16:46] <ubot2`> Launchpad bug 711549 in udisks "pressing physical eject button on CD/DVD drive causes icon to remain on desktop after eject" [High,Fix released]
[16:47] <hikiko> seb128, could you pull and check again?
[16:47] <seb128> pitti, I tried to put a DVD in my laptop earlier to debug something else, I've put it back in the box but the mount icon is still there in unity/nautilus since this morning
[16:48] <pitti> seb128: hmm, it hasn't really changed in ages
[16:49] <seb128> pitti, well, I didn't test that in ages, the fix in udisks was working for precise, maybe it never worked for udisks2?
[16:49] <xnox> seb128: that's ok, no new notebooks come with a dvd drive anyway ;-)
[16:49] <pitti> I don't even rememver the fix
[16:49] <pitti> but it's been several years since I actually had a CD drive, but it perhaps also fails with a simulated CD
[16:50] <seb128> pitti, http://launchpadlibrarian.net/68907029/udisks_1.0.2-4_1.0.2-4ubuntu1.diff.gz was the fix
[16:52] <pitti> seb128: ah, I saw the bug mail
[16:54] <pitti> seb128: oh, I see
[16:55] <pitti> seb128: well, it's not really supposed to work that way
[16:55] <pitti> seb128: in quantal or even earlier we enabled kernel-side polling
[16:55] <pitti> so perhaps that broke
[16:56] <pitti> seb128: i. e. if you insert or eject a CD, you should get an event in udevadm monitor
[16:56] <seb128> pitti, ok, all I know is that udisksctl dump lists a DVD that has been ejected since this morning ... but that seems like a debug topic for after ff
[16:57] <pitti> seb128: ok, then it seems kernel polling for eject has been broken
[16:58] <seb128> pitti, do you know how to test that?
[16:58] <seb128> pitti, btw we don't need to discuss/debug it today, I'm happy to open a bug report and follow up in async way/later there, you probably have other things to do at the sprint
[16:58] <pitti> we have that bug report, right?
[16:59] <seb128> which one?
[16:59] <pitti> I thought you meant bug 1281110
[16:59] <ubot2`> Launchpad bug 1281110 in udisks2 (Ubuntu) "cds no longer appear in the device notifier" [Undecided,New] https://launchpad.net/bugs/1281110
[16:59] <seb128> I debugged one earlier where the submitter was saying that nothing happened when inserting a CD
[16:59] <pitti> that's pretty much the same issue
[16:59] <seb128> right
[17:00] <pitti> kernel poling for new/removed media
[17:00] <seb128> I just realized
[17:00] <seb128> I got the prompting this morning
[17:00] <pitti> I suppose if you do that, nothing happens in udevadm monitor -e --udev?
[17:00] <seb128> so I though that was working
[17:00] <Trevinho> seb128: proper scaling using that gnome key is coming to the ppa...
[17:00] <seb128> Trevinho, nice!
[17:01] <seb128> pitti, http://paste.ubuntu.com/6960826/ when inserting the CD
[17:01] <pitti> 7~DISK_MEDIA_CHANGE=1
[17:02] <pitti> oh, that's good
[17:02] <pitti> seb128: and if you press the eject button, do you get an event?
[17:02] <seb128> pitti, http://paste.ubuntu.com/6960832/
[17:03] <pitti> oh, good
[17:03] <pitti> so the kernel/udev parts are working still
[17:08] <seb128> hikiko, thanks, that commit makes the default be 1
[17:09] <seb128> hikiko, speaking about the UI, I guess the "UI Scale:" shouln't have a ":" and be right aligned with the other labels
[17:09] <seb128> hikiko, and the slider should take the same space as the combos
[17:11] <hikiko> mmm I was about to leave, let me fix it quickly and push :)
[17:11] <seb128> hikiko, thanks, and sorry for that
[17:16] <hikiko> fixed :)
[17:16] <seb128> hikiko, thanks!
[17:17] <hikiko> no prob there was a trick I hadnt noticed
[17:17] <seb128> hikiko, have a nice evening!
[17:17] <hikiko> if you check homogeneous it gets automatically the size/padding of the container :D
[17:17] <hikiko> have a good evening everyone + seb128 thanks for the review!
[17:17] <seb128> attente_, ok, https://code.launchpad.net/~attente/indicator-keyboard/ibus-panel/+merge/207240 works fine for me (I've no clue about those IM option so I can only say they look like (and that the normal switching doesnt regress)
[17:18] <seb128> happyaron, ^ can you give an user testing round to that one, as you use IMs ;-)
[17:18] <seb128> attente_, but +1 from me for landing, feel free to push to the branch today, I'm going to do a landing tomorrow my morning with was is in there, if that works for you
[17:20] <attente_> seb128, ok, works for me, i'll try to resolve those issues today though
[17:20] <seb128> attente_, ok, good luck ;-)
[17:20] <attente_> seb128, thanks!
[17:20] <seb128> attente_, we can still do other landings with fixes after ff otherwise, so don't overstress about it
[17:20] <seb128> yw!
[17:35] <seb128> didrocks, sil2100: how can I request a CI train request to be dropped?
[17:35] <seb128> or superseeded
[17:35] <didrocks> seb128: if it's yours, of course :)
[17:35] <didrocks> or one you are the owner
[17:36] <seb128> didrocks, "how"? :p
[17:36] <seb128> yeah, I'm owning that one
[17:36] <didrocks> seb128: you can run merge and clean with "only free silo"
[17:36] <seb128> thanks
[17:36] <xclaesse> seb128, are you going to rebuild all -doc packages to get the new gtkdoc styling? :P
[17:37] <seb128> xclaesse, no way :p
[17:37] <didrocks> seb128: then, for clarity, if you are not going to reuse that line, you should put something in the status field
[17:37] <didrocks> (and maybe some red or green)
[17:38] <seb128> didrocks, "status", the column that says "auto-updated, do not touch"? ;-)
[17:38] <didrocks> seb128: yeah, if you are not going to use that line anymore, you can overwrite it
[17:38] <didrocks> then, you won't be able to reuse it
[17:42] <seb128> didrocks, ok, superseeding l18 by l39
[17:42] <didrocks> robru: mind assigning it? ^
[17:42] <robru> sure
[17:42] <didrocks> thx!
[17:43] <seb128> thanks
[17:44] <robru> seb128, ok, silo 8, please build
[17:44] <robru> hmmm wait
[17:44] <robru> didrocks, prepare job told silo 8, but spreadsheet wont' accept it
[17:45] <didrocks> robru: oh?
[17:45] <didrocks> robru: backend is always right
[17:45] <didrocks> robru: ah, I know, what happened
[17:45] <didrocks> wait for 5 minutes
[17:45] <didrocks> and retry
[17:46] <robru> ok
[17:46] <didrocks> robru: as the silo has just been freed, it's not synced back
[17:46] <didrocks> robru: and I changed the sync from 1 min to 5 minutes
[17:46] <didrocks> (to pull for backend update)
[17:46] <didrocks> to see if it relaxes the spreadsheet issues
[17:46] <seb128> 8 is the one I just cleaned
[17:46] <didrocks> in addition to my optimization
[17:46] <robru> seb128, yeah, because its clean, the backend assigned it again ;-)
[17:46] <didrocks> robru: tomorrow, I'll put it back to 1 min
[17:47] <didrocks> we'll see if the spreadsheet goes crazy again
[17:47] <robru> didrocks, ugh, now it just says line 18 is silo ready
[17:48] <didrocks> argh
[17:48] <didrocks> yeah, it reassign
[17:48] <didrocks> so we have a race in that case :)
[17:48] <robru> didrocks, so i have to manually switch that?
[17:48] <didrocks> yeah, using the force free silo (admin only)
[17:48] <didrocks> in the spreadsheet menu
[17:48] <didrocks> then assign the other line
[17:48] <robru> didrocks, i just moved the info down to line 39 ;-)
[17:49] <didrocks> robru: works as well :)
[17:49] <didrocks> the hidden column? :p
[17:49] <robru> seb128, ok, go for build now
[17:49] <robru> didrocks, yeah
[17:49] <didrocks> cheating!
[17:49] <didrocks> :)
[17:49] <seb128> robru, didrocks: thanks
[17:49] <didrocks> robru: seb128: just put something in the status column of line 18 and change the background color please
[17:50] <robru> didrocks, on it
[17:50] <didrocks> like "superseeded" and green or red :)
[17:50] <didrocks> thanks!
[17:59] <Trevinho> new mesa landed in trusty-proposed breaks unity builds
[17:59] <Trevinho> we can't build unity now due to
[17:59] <Trevinho> Package xcb-dri3 was not found in the pkg-config search path.
[17:59] <Trevinho> Perhaps you should add the directory containing `xcb-dri3.pc'
[18:00] <Trevinho> not today... not today! :/
[18:00] <didrocks> Trevinho: do you have some time to help me with my decorator bug? :)
[18:00] <seb128> mlankhorst, ^
[18:00] <Trevinho> didrocks: mh, not sure... let me know though :)
[18:00] <didrocks> Trevinho: so, as seb128 told you, I have different close/minimize/maximize icons on the decoration than when it's maximized
[18:01] <mlankhorst> ?
[18:01] <didrocks> I reseted /org/gnome/desktop/interface/icon-theme and /org/gnome/desktop/interface/cursor-theme
[18:01] <Trevinho> mlankhorst: see failures at https://launchpadlibrarian.net/166779034/buildlog_ubuntu-trusty-amd64.unity_7.1.2%2B14.04.20140219.2-0ubuntu1_FAILEDTOBUILD.txt.gz
[18:01] <didrocks> and restarted compiz
[18:01] <didrocks> and no
[18:01] <didrocks> so, I guess there is a bug that we don't read the same key from the decoration than when rendering the panel
[18:01] <seb128> mlankhorst, I guess some .pc got a Requires xcb-dri3 but the -dev shipping the .pc didn't get its depends updated?
[18:01] <didrocks> but then, which key? :p
[18:01] <Trevinho> didrocks: mh, I'm always using the same default gtk theme...
[18:01] <didrocks> what do I have on my user account which is so special (it's not a system issue, it doesn't happen on a guest account)
[18:02] <Trevinho> looking in standard paths: ~/.local/share/themes -> ~/.themes ... /usr/share/themes...
[18:02] <didrocks> Trevinho: gtk-theme='Ambiance'
[18:02] <mlankhorst> Trevinho: yeah but I see missing Nux/Nux.h there..
[18:02] <Trevinho> mlankhorst: that's because pkg-cofnig fails
[18:02] <didrocks> Trevinho: nothing in  ~/.local/share/themes -> ~/.themes
[18:02] <seb128> didrocks, try to strace -f compiz 2>&1 | grep theme?
[18:02] <didrocks> let's try
[18:02] <seb128> Trevinho, do you know how are the images for the decoration called?
[18:02] <Trevinho> mlankhorst: basically the pkg-confg gl fails, then all fails
[18:03] <Trevinho> look for xcb-dri3 on that log
[18:03] <mlankhorst> oh that
[18:03] <seb128> mlankhorst, something Requires dri3 but doesn't have a depends on the corresponding dev I guess
[18:03] <didrocks> http://paste.ubuntu.com/6961165/
[18:03] <mlankhorst> seb128: yeah so it would seem
[18:03] <didrocks> so, nothing specific to my directory
[18:04] <Trevinho> mlankhorst: thanks, please consider this high prio... we've features to land :)
[18:04] <Laney> mlankhorst: libgl1-mesa-dev
[18:04] <seb128> mlankhorst, you are on it? ff is tomorrow and that's blocking unity landings
[18:04]  * didrocks retries
[18:04] <seb128> didrocks, try to grep for didrocks?
[18:04] <mlankhorst> seb128: I really have to go in a few minutes :/
[18:04] <seb128> didrocks, to see what it reads from you user dir
[18:05] <Laney> mlankhorst: If it's just that then I can do that upload now
[18:05] <seb128> mlankhorst, you can't let trusty broken, if you prefer I can delete your update from today ... or Laney can fix it if you are confident that's going to work
[18:05] <mlankhorst> Laney: egl needs that update too, I'll try to push a fix
[18:05] <seb128> get to love the pre-ff issues
[18:05] <didrocks> oh
[18:06] <didrocks> [pid 19718] access("/home/didrocks/.local/share/themes/Ambiance/unity/close.png", F_OK <unfinished ...>
[18:06] <seb128> didrocks, that would do it ;-)
[18:06] <didrocks> ah no
[18:06] <didrocks> doesn't exist
[18:06] <seb128> :-(
[18:06] <Laney> mlankhorst: yeah I got it
[18:06] <Laney> laney@iota> rgrep GL_PC_REQ_PRIV | grep \.pc                                                                          ~/temp/mesa-10.1.0~rc1
[18:06] <Laney> src/mesa/gl.pc.in:Requires.private: @GL_PC_REQ_PRIV@
[18:06] <Laney> src/egl/main/egl.pc.in:Requires.private: @GL_PC_REQ_PRIV@
[18:06] <seb128> didrocks, you can -e open in the strace
[18:06] <mlankhorst> Laney: sec I'll try to finish building it locally..
[18:07] <Laney> okey dokey
[18:07] <Laney> I actually don't know of an automated tool that checks for this
[18:07] <Laney> that'd be interesting
[18:07] <Trevinho> didrocks: that's weird...
[18:08] <mlankhorst> not sure why libgl1-mesa-dev depends on x11proto-dri2-dev
[18:08] <Trevinho> didrocks: mhmh... it's like that it doesn't fail for that file, then it uses the cairo-generated buttons (maybe)?
[18:09] <didrocks1> ok, it killed all my terminal after restarting compiz too many times :p
[18:10] <didrocks1> Trevinho: once you will be a little bit less busy, I would appreciate looking at that with you, old unity got the default icons, metacity is getting the default icons as well, only your new decorations are taking something else :)
[18:10] <didrocks1> Trevinho: but I'll let you land features first, that's something that just needs to be fixed before release :)
[18:10] <mlankhorst> Laney: pushed, should hopefully fix all issues
[18:10] <Laney> ok
[18:10] <seb128> mlankhorst, thanks
[18:10] <mlankhorst> if not I'm away until tomorrow morning :-)
[18:11] <seb128> mlankhorst, have fun, and let's hope that fixes the unity build
[18:11] <Trevinho> didrocks1: if it can help...
[18:11] <Trevinho> http://bazaar.launchpad.net/~unity-team/unity/trunk/view/head:/unity-shared/DecorationStyle.cpp#L318
[18:11] <Trevinho> and the weird thing is that both the panel and the decorations share the same codepath...
[18:11] <Trevinho> different textures, but same "look for this file" codepath
[18:12] <didrocks1> Trevinho: yeah, there is clearly a bug somewhere :)
[18:12] <mlankhorst> nice part is undoing the same thing for mesa lts-trusty backport ;-)
[18:12] <didrocks1> Trevinho: it's not different textures, it's really different icons :p
[18:12] <Trevinho> didrocks1: is GTK_DATA_PREFIX set for you there?
[18:12] <mlankhorst> if I disable dri3 support entirely the backport to precise is a lot easier..
[18:12] <seb128> didrocks1, did you strace -f -e open and try to grep on e.g png?
[18:12] <didrocks1> Trevinho: I saw that, I don't think so, but I'll look in a clean session
[18:13] <didrocks1> seb128: well, that's what killed my session, I'm under metacity launched from a tty
[18:13] <didrocks1> so, I'll look tomorrow morning
[18:13] <seb128> didrocks1, k
[18:13] <didrocks1> to ensure I have the right env variables
[18:13] <seb128> reminds you of the good old time right? ;-)
[18:13] <didrocks1> not sure we have the same definition of "good" :)
[18:13] <didrocks1> but yeah, it's like a flashback
[18:13] <didrocks1> I should thanks Trevinho ;)
[18:13]  * Trevinho done that for you
[18:14] <Trevinho> :D
[18:14] <Laney> hey, welcome to the cool style session
[18:14]  * didrocks1 hugs Trevinho :)
[18:14] <Trevinho> I thought you loved the flashbacks... so... there's a special easter egg for didrocks user
[18:14] <didrocks1> heh
[18:15]  * didrocks1 will grep unity new code to look for if username == didrocks
[18:15] <Trevinho> ah didrocks1 I see the fosdem page has not been updated (not that I care much)...
[18:15] <seb128> Trevinho, bregma: hopefully https://launchpad.net/ubuntu/trusty/+source/mesa/10.1.0~rc1-1ubuntu2 does it for the unity build
[18:15] <didrocks1> Trevinho: yeah, it will take weeks apparently :p
[18:15] <didrocks1> but I sent all infos
[18:15] <Trevinho> that would be too clear... It's a new kind of coding: "whitespace encoding"...
[18:15] <didrocks1> heh
[18:15] <Trevinho> tabs, space... like 0 and 1...
[18:16] <mlankhorst> and i was really aiming not to break unity this time :P
[18:16] <didrocks1> anyway, see you tomorrow guys!
[18:16] <Trevinho> cheers didrocks1
[18:16] <seb128> didrocks1, night!
[18:17] <Trevinho> seb128: should we wait to rebuild or is it already there?
[18:18] <bregma> I'm watching the rebuilds
[18:18] <Trevinho> mlankhorst: thanks btw
[18:19] <seb128> Trevinho, bregma: you need to wait that rmadison -s trusty-proposed shows the new binary
[18:20] <seb128> which should be less than half an hour
[18:20] <mlankhorst> take a cup of coffee, or 2, watch your favorite movie ;-)
[18:20] <bregma> the more coffee I drink the longer everything seems to take
[18:20] <Trevinho> unfortunately these are not the days we can, but i would love to :)
[18:25] <ochosi> Laney: as per your suggestion, i submitted a bugreport. not that i expect that you process this, but for the future: is this okay for merging/uploading or would you expect more/other infos? https://bugs.launchpad.net/ubuntu/+source/xubuntu-default-settings/+bug/1282154
[18:25] <ubot2`> Launchpad bug 1282154 in xubuntu-default-settings (Ubuntu) "update default settings for trusty" [Undecided,New]
[18:42] <Sarvatt> Trevinho: https://launchpad.net/ubuntu/trusty/+source/mesa/10.1.0~rc1-1ubuntu3 is what you want to look for btw, there were more dependencies missing
[18:42] <seb128> Sarvatt, thanks
[18:43] <Trevinho> Sarvatt: ah
[18:43] <Trevinho> bregma: ^
[18:43]  * bregma sighs
[18:45] <seb128> bregma, Trevinho: well, the previous one might be enough for unity
[18:45] <Trevinho> let's try... :)
[18:45] <Trevinho> we need to make unity to fail in a better way in these cases though
[18:45] <Trevinho> or well instruct cmake to do so
[18:46] <seb128> yeah, well handling build nicety is for another day I guess
[18:46] <seb128> let's focus on landing features for this week
[18:47] <bregma> I haven't seen 10.1.0~rc1-1ubuntu2 land yet, it's till waiting to build
[18:47] <seb128> bregma, on what archs?
[18:48] <bregma> nm, I see it now
[18:49] <bregma> rmadison was not telling me, but I see it on launchpad
[18:50] <seb128> what did you rmadison for?
[19:19]  * desrt caved in
[19:20] <desrt> We appreciate your business at dell.ca. We will send an e-mail confirmation of your order to<EMAIL_ADDRESS>within 2 business days.   That last diff was so large with all the test changes, I overlooked the l_debug line
[22:03] <mterry> robert_ancell, fixed
[22:11] <robert_ancell> mterry, did you see the following comment?
[22:11] <mterry> robert_ancell, nope!
[22:11]  * mterry reads
[22:12] <mterry> robert_ancell, eh, the start session call includes XDG_GREETER_DATA_DIR in it
[22:12] <mterry> robert_ancell, we match pretty loosely, but it at least confirms that the dir was created/passed to the session
[22:12] <robert_ancell> mterry, yeah, it's no a biggie. Just wondered if you'd noticed
[22:12] <mterry> robert_ancell, I mean that the call includes XDG_GREETER_DATA_DIR in the test notify line
[22:13] <mterry> robert_ancell, I had.  But I didn't want to bother doing the .*/username thing again.  I just wanted to confirm it existed
[22:13] <mterry> so left it as TRUE/FALSE
[22:13] <robert_ancell> mterry, I just ran make check here. some tests need updating e.g. test-additional-config
[22:14] <mterry> hmm..  Maybe I didn't merge from trunk?  Everything passed for me and jenkins...
[22:14] <robert_ancell> hang on, let me try some more
[22:14] <robert_ancell> this is a fresh checkout
[22:15] <robert_ancell> mterry, ah, the chown is failing under test
[22:15] <robert_ancell> mterry, we don't fake it
[22:16] <mterry> robert_ancell, right, I did sudo make check.  I thought it was understood that tests were run as root?
[22:16] <robert_ancell> mterry, no, they can run as a normal user
[22:16] <mterry> I see...
[22:17] <mterry> robert_ancell, the chown calls are in test-runner, which doesn't run under libsystem, right?
[22:17] <mterry> robert_ancell, my new ones weren't the only chown calls in there, so I figured it was assumed that root was running it
[22:17] <robert_ancell> mterry, it does. If I make chown return 0 they work, except for the LIST-SHARED-DATA-DIRS call which now can't check the permissions easily
[22:17] <robert_ancell> yeah, not sure what that was added for previously
[22:18] <mterry> robert_ancell, to make the home dirs of the other users correct permission wise
[22:18] <robert_ancell> ah, we only do the existing chown if getuid() == 0
[22:19] <robert_ancell> mterry, tell you what, let's just land it and I'll make a new MP to get the tests working as non-root again
[22:19] <mterry> robert_ancell, but this instance isn't optional.  Wait, test-runner is run under libsystem?  I didn't think so... it's called directly from the test-* scripts
[22:20] <robert_ancell> mterry, yes, you're right
[22:20] <mterry> robert_ancell, and the existing chown call in there isn't guarded by getuid()...  which call are you looking at?
[22:21] <robert_ancell> mterry, the one in src/session.c
[22:21] <mterry> robert_ancell, oh sure, in the source itself
[22:21] <mterry> robert_ancell, but there is another call in test-runner.c for chowning fake user dirs.  I assumed that implied test-runner needed root
[22:21] <mterry> robert_ancell, I wasn't sure how to get the functionality I needed without either running under libsystem or being root
[22:22] <robert_ancell> mterry, yeah, let's solve it later. It's not a huge problem
[22:26] <robert_ancell> mterry, all tests are passing for me except for test-shared-data-dirs-autologin
[22:26] <robert_ancell> it only lists one shared data dir created
[22:27]  * mterry looks again
[22:28] <robert_ancell> mterry, the test expects a "lightdm" directory to exist, but I can't see why that should be
[22:28] <mterry> robert_ancell, the greeter's session creates it (which is desired, as the greeter may want it to stuff temporary files like camera photos before shunting them to the proper user dir)
[22:29] <mterry> robert_ancell, I didn't add the variable printout to greeter session starts in scripts though
[22:29] <mterry> robert_ancell, figured that it was largely uninteresting usually.  It was more important to test the various session cases
[22:29] <robert_ancell> mterry, why not use a normal cache dir? It's not really a shared dir if it's only shared with itself
[22:30] <mterry> robert_ancell, this way it's on the same partition and is guaranteed to stay across reboots and such
[22:30] <mterry> robert_ancell, could use greeter's HOME too I suppose
[22:30] <mterry> robert_ancell, but everything in the same place seemed nice
[22:30] <robert_ancell> mterry, yeah, there are existing locations for things like this
[22:30] <mterry> robert_ancell, because on phone right now HOME is cleared after every boot
[22:31] <mterry> robert_ancell, (greeter's HOME that is)
[22:31] <robert_ancell> mterry, the test failure http://paste.ubuntu.com/6962479/
[22:31] <mterry> robert_ancell, we could change that, but it's easier if we just poke a hole for lightdm-data directory
[22:32] <mterry> robert_ancell, yeah that test shouldn't have the lightdm directory, since the greeter isn't involved.  Not sure how my tests or jenkins let that slide
[22:33]  * mterry runs tests again
[22:33] <robert_ancell> mterry, jenkins doesn't run the tests
[22:33] <mterry> robert_ancell, ah that explains that
[22:33] <mterry> robert_ancell, but anyway.  All the existing locations I didn't like (they all are cleared after boot)
[22:33] <mterry> on phone anyway
[22:34] <mterry> it's debatable whether we should keep greeter's HOME but if we can avoid doing it, all the better
[22:34] <robert_ancell> mterry, ok
[22:35] <robert_ancell> mterry, you can share between greeters with that directory anyway, so I guess it makes sense
[22:35] <mterry> robert_ancell, oh god.  A user takes photos with one greeter, then reboots and uses another greeter?  And then logs into a user?  I hate lightdm use cases
[22:36] <mterry> Not that that's much different than using HOME
[22:36] <robert_ancell> no
[22:36] <robert_ancell> (it's not)
[22:37] <mterry> robert_ancell, for me, test-unity-compositor-fallback keeps failing in 'make check' but not when I manually run the test.  Does that make any sense?  (don't think it's related to my changes)
[22:37] <robert_ancell> mterry, yeah it's being unreliable for me but I don't think it's related either
[22:38] <robert_ancell> this is why jenkins isn't running the tests
[22:38] <mterry> robert_ancell, well, test that failed for you is updated
[22:38] <mterry> (it failed for me too)
[22:38] <mterry> Must have been focusing on the other new test and forgot to rerun the autopilot one
[22:38] <robert_ancell> mterry, approved, thanks for the patience!
[22:39] <mterry> robert_ancell, np, thanks for the stickler reviews  :)


[00:48] <MICROburst> how can I specify the system locale in a yaml file? Using "locale: en_DK.UTF-8" does not work.
[01:17] <minimal> MICROburst: you mean in user-data? In theory, yes, that should work, I use it myself. However you haven't indicated with cloud-init version you are using, which distro (and version of that), and which cloud-init datasource
[07:54] <MICROburst> minimal: I'm using debian bullseye and testing. I did not put it below user-dara since I would like to have it set system-wide. Is it required to list locales-all in the packages section?
[10:40] <yuvi> Hey, can I talk to anyone here, I'm trying to understand some basic things and google isn't helpful
[10:44] <aciba> yuvi: Hello, I can try to help
[13:46] <smoser> ananke: if you're still around...
[13:46] <smoser> a couple of weeks ago i looked at the cloud-initramfs-tools package in ubuntu for a overlayroot issue.
[13:47] <ananke> I'm here, thanks for responding! I'm right now not sure where to report this issue. Debian's bug tracker has it, but there seems to be no action
[13:48] <ananke> I've been able to work around the missing flock (and other missing tools such as sed/rm/grep), but right now I'm stumped by missing wait-for-root. Debian's packages do not include it in initramfs-tools
[13:48] <smoser> if i recall correctly, debian's is very out of date compared to ubuntu.  They grabbed it, made a change or two (again, from memory, i disagreed with), and then really never synced in changes.
[13:50] <smoser> https://paste.opendev.org/show/bYpMFNvCIqqz0Bm3YDIX/
[13:50] <ananke> I'm baffled by their changes honestly. They took out tools from the hooks file
[13:51] <smoser> it doesn't surprise me that growroot would "mostly work" without flock , espeically in the initramfs.
[13:51] <smoser> it was racy, and worked for *years* reliably before it started misbehaving (probably some udev or kernel thing changed timing)
[13:51] <ananke> lack of flock seemed to result in fatal failure, but lack of rm/grep/sed didn't
[13:52] <smoser> initramfs-tools is a mess in that regard. as are all initreamfs creation packages i'm aware of.
[13:53] <smoser> you have a module that says "i need program x". the initramfs script runs, it fails, and then the tool goes on.
[13:53] <smoser> the only way you know about the error is when it fails or if you happened to look at logs.
[13:53] <ananke> so I'm wondering what can be done at this point. is wait-for-root available in ubuntu?
[13:57] <ananke> and the changes to /usr/share/initramfs-tools/hooks/growroot they did were baffling. their 0.18.debian8 version included more tools (rm, readlink, sed, grep), but 0.18.debian11 removed them
[13:58] <ananke> I wish debian had a bit friendlier bug tracker, rather this mailing list approach
[14:11] <smoser> i'd be happy to take a patch to "upstreaM" cloud-initramfs-tools that identified that growpart depends on sed,awk, grep
[14:12] <smoser> but even then, its non-trivial because the busybox versions are sufficient, and you don't want to cause a copy of "the real sed" if busybox is present with that.
[14:13] <smoser> and ubuntu's busybox-initramfs *does* have those https://paste.opendev.org/show/bXSm70ar2pG8FQgZnnY4/
[14:17] <smoser> hm.. reading https://manpages.ubuntu.com/manpages/bionic/en/man8/initramfs-tools.8.html i guess maybe growroot should/could set BUSYBOX=Y ? i dont know.
[14:17] <ananke> I'm going to do some testing on vanilla debian 11, using the official AMI, and see if I can replicate the issue there
[14:17] <smoser> oh, one question
[14:18] <smoser> why do you need it / want it in the initramfs ?
[14:21] <ananke> smoser: I personally do not care where it's located. my org is using official Kali images in AWS, which are impacted by this problematic change. Kali seems to be using upstream directly from Debian
[14:21] <smoser> and that makes sense...
[14:21] <ananke> the problem is simple: you make an ec2 instance with that kali AMI, you apply the updates (including that package), and then try to grow the disk. your instance will fail to boot
[14:22] <smoser> if i had a lot of time that i had nothing to do with, then i might try to get cloud-initramfs-tools to be a proper upstream (not a native package on ubuntu) and then get that into debian and have ubuntu just sync from debian.
[14:22] <ananke> looking at the debian bug report, this likely affects anybody else using virtualization images
[14:22] <smoser> and i think if i worked hard at that, it could get done in 6 montsh of calendar time.
[14:23] <ananke> yeah, that doesn't seem like a good ROI :)
[14:25] <ananke> if it wasn't for the fact that it used to work just fine, I wouldn't be diving so deep in it. if I don't find a good fix, and ideally get somebody to accept it upstream (Kali, or Debian), then we'll have to keep integrating that fix for the foreseable future. We very much rely on our images being small, and deploying them with larger disk size. rinse & repeat for thousands of users
[14:25] <smoser> for sure, i wouldnt want to do that.
[14:25] <smoser> here is what i'd suggest:
[14:28] <smoser>  * start working from the ubuntu version https://git.launchpad.net/cloud-initramfs-tools
[14:28] <smoser>  * add some way to copy grep sed awk as you showed
[14:28] <smoser>  * suggest debian pull from that.
[14:29] <smoser> if you hyave a relationship with kali, you  might just suggest they remove cloud-initramfs-tools from their packages
[14:30] <ananke> thank you
[14:32] <ananke> so that brings up a good point, which I haven't considered yet: growing the root filesystem doesn't need to be done with initramfs
[14:33] <ananke> so one potential way would be to remove cloud-initramfs-growroot package, and redo initramfs? I can test that
[14:39] <ananke> hah, it worked on debian 11. removed the package, shut it down, increased disk size, started it up. cloud-init was able to grow the filesystem on boot. I personally don't care how early in the boot process that filesystem is grown, so who knows - this may be our best option for right now
[14:41] <ananke> I'll do some more testing this afternoon, gotta take kids to the dentist. thanks again!
[14:42] <smoser> the only reason that it was done in the initramfs was because > 10 years ago, there was no option
[14:42] <smoser> if your kernel is nerwer than something like 3.18 you can do it while the filesystem is mounted.
[14:43] <smoser> *3.18* seriously.
[14:43] <ananke> I vaguely recall doing online resizing back in 2.4 or 2.6 series
[14:45] <ananke> either way, that may be a good stop gap measure for us, so any images we create now will be resizable in the near future, regardless of updates. Part of my issue was timing: I have to roll out few new images this/next week, and any kind of fix would need to survive whatever upstream rolls out
[15:18] <smoser> ananke: yeah, filesystem resize is older than that. but 'ptupdate' (partition update) was new in 3.8.
[15:19] <smoser> 3.8 becomes 10 years old next month .
[15:37] <minimal> anake: "growing the root filesystem doesn't need to be done with initramfs" - that was the recently I commented "I've never seen growpart run in an initramfs before" yesterday ;-)
[15:37] <minimal> s/the recently/why/
[15:38] <minimal> ananke: ^^^
[16:10] <smoser> kids
[16:34] <meena> smoser: whew
[16:37] <meena> OpenBSD and NetBSD still use the initramfs hack. online growfs for UFS/FFS2 has been in FreeBSD for… a long time. but different FFS flavours have somewhat diverged in the past 30 years…
[17:10] <meena> I wanted to… borrow Puppet's facter code for is_virtual, and promptly found a bug
[18:38] <ananke> smoser: yeah, re-reading partition table was notoriously problematic with linux. one often had to try different tools to eventually get it to acknowledge changes: blockdev --rereadpt, sfdisk -r, hdparm, partprobe, etc.
[18:41] <ananke> funny enough, just few weeks ago I came across a phantom problem, when building our images would fail because a block device was not found. the culprit? we still don't know why, but for some reason, that particular day executing 'partprobe' on EC2 instances would result in /dev/<insert nvme device> to disappear for less than 1 second. that was enough to cause our process to fail, because right after
[18:41] <ananke> partprobe we were trying to use dd against it
[18:43] <ananke> never happened before, we've had that process in place for months, running on various instances. that day it stopped working. we put in gratuitous waits, and re-ordered few things to avoid that issue, and by the time we were done testing the fix, the problem went away
[18:47] <minimal> ananke: yeah recently I wanted to remove parted package (for partprobe) as a dependancy of the Alpine cloud-init package...then I found Busybox blockdev didn't work reliably for cc_disk_setup lol
[19:02] <smoser> ananke: fwiw, running 'udevadm settle' usually fixes things.  the problem with it is that most of the time so would 'sleep 1'. so it is very easy to say "oh, the fix is to run udevadm settle" and then you'll actually see it "fixed". but that is very likely no different than adding 'sleep 1'
[19:02] <smoser> s/very likely/possibly/
[19:04]  * meena wonders if that's how udevadm is implemented
[19:19] <minimal> I run without udev (and therefore without "udevadm settle") on some systems ;-)
[19:21] <meena> alias "udevadm settle" "sleep 1"
[19:23] <minimal> meena?
[19:23] <falcojr> I'm assuming it was a joke...otherwise I'm very worried XD
[19:23] <minimal> oops, meena: no need, cc_disk_setup only runs udevadm if it is present
[19:24] <minimal> falcojr: are you referring to me?
[19:24] <falcojr> no, the alias
[19:27] <meena> falcojr: mostly a joke, yes. mostly ;)
[19:30] <meena> five minutes in a ruby pry session, and i have forgotten half of python again
[19:34] <minimal> MICROburst: your response re your locale problem wasn't clear. Where exactly are you specifying the "locale:"?
[20:28] <xtalkme> Good evening all, I am trying to debug the cloud-init module cc_puppet, because of the following error.
[20:28] <xtalkme> cloudinit.url_helper.UrlError: HTTPSConnectionPool(host='raw.githubusercontent.com', port=443): Max retries exceeded with url: /puppetlabs/install-puppet/main/install.sh (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:997)')))
[20:28] <xtalkme> A local wget works fine, certficate is valid enabled debugging on logger_cloud-init but no luck.
[20:28] <xtalkme> Any tips where to look ?
[20:32] <MICROburst> minimal: below "timezone:" (not indented, if you meant that)
[20:39] <minimal> MICROburst: I meant where as in if it is not in user-data (you said) then where exactly have you specified it?
[20:39] <minimal> in /etc/cloud/cloud.cfg ? somewhere else?
[21:16] <MICROburst> minimal: virt-install ...     --cloud-init user-data=../etc/${NAME}.yaml
[21:17] <MICROburst> thought you were talking about the users section in the file...
[21:17] <minimal> MICROburst: so you *are* providing user-data, your earlier response said "I did not put it below user-data"
[21:19] <minimal> so did you check if the /etc/default/locale file was updated by cloud-init?  That's the file cc_locale changes for Debian
[21:20] <minimal> do you also have the Debian locales package installed?
[21:31] <smoser> xtalkme: 2 options
[21:31] <smoser> 1. cloud-init/python is not looking for certs the same place as wget is
[21:32] <smoser> 2. when cloud-init tried the clock was not right
[21:33] <smoser> to do the same request with cloud-init, something like:
[21:36] <smoser> https://paste.openstack.org/show/bvAqYfyonGtxNQFytU3e/
[21:37] <smoser> if that works at the same time wget works, then i think its clock related or (just thought of this), you're behind some sort of closed portal
[21:38] <smoser> your https request to github is going to some local page and https is crying about that.
[21:44] <minimal> https://raw.githubusercontent.com/puppetlabs/install-puppet/main/install.sh is defined in cc_puppet.py so that's where the url portions referenced above come from
[21:45] <minimal> the "local page" is actually the non-scheme, non-host part of that url
[21:55] <xtalkme> smoser Thanks did not think about time as a issue. Will have a look at that. And with closed portal i guess you mean something like a wifi portal ?
[22:02] <xtalkme> smoser when i import the urlhelper, i get the same error, time seems correct.
[22:19] <xtalkme> minimal not sure what you mean with the "Local page"?
[22:19] <xtalkme> smoser certifi.where() also seems to return the expected location for its certificates: '/etc/ssl/certs/ca-certificates.crt'
[22:28] <xtalkme> r = requests.get("https://raw.githubusercontent.com/puppetlabs/install-puppet/main/install.sh", verify=False) works so i guess something certificates...
[22:40] <xtalkme> The issue is on 22.04 but not on 20.04, both using 22.4.2 but different python versions
[22:51] <MICROburst> minimal: the locales-all package was not added to the list. I'll test this...
[22:58] <meena> https://github.com/canonical/cloud-init/pull/1957
[22:58] -ubottu:#cloud-init- Pull 1957 in canonical/cloud-init "add function is_virtual to distro/FreeBSD" [Open]
[23:01] <minimal> xtalkme: I was referring to smoser's reference to "some local page"
[23:23] <MICROburst> minimal: No success: /etc/default/locale -> LANG=C.UTF-8 and should be LANG=en_DK.UTF-8 -- log file claims "invalid locale", however "localectl set-locale LANG=en_DK.UTF-8" works
[23:27] <minimal> MICROburst: have you turned on debugging for cloud-init and then looked in /var/log/cloud-init.log to see what it shows for cc_locale?
[23:28] <minimal> actually, hang on, is there such as thing as en_DK? Danish English?
[23:29] <minimal> oh there is, first I've ever seen it mentioned, wow
[23:30] <minimal> so you have the "locales" Debian package installed?
[23:30] <meena> minimal: best locale in the world.
[23:30] <minimal> probably ;-)
[23:30] <meena> minimal: gives you english language stuff with a sensible time and date format
[23:31] <minimal> meena: sensible time/date format? you mean like en_GB and en_IE?
[23:34] <meena> minimal: i don't know what those look like, but en_US is incomprehensible.
[23:34] <minimal> MICROburst: cc_locale on Debian doesn't run "localctl", it runs "update-locale" or "locale-gen"
[23:34] <meena> date on my system with LC_TIME=en_DK.utf-8 gives: 2023-01-12T23:34:27 GMT
[23:35] <minimal> meena: well you're in Ireland now, you should be using en_IE ;-)
[23:35] <meena> minimal: true
[23:35] <minimal> it's like en_GB but with Euros not Pounds lol
[23:36] <meena> https://gist.github.com/79424923d80e70213ceef8084b61222f
[23:36] <minimal> MICROburst: both those commands come from the "locales" package which is why I asked you earlier if you had it installed
[23:37] <MICROburst> minimal: locales-all IS installed
[23:37] <minimal> MICROburst: for the 2nd time, I didn't ask you about locales-all, I asked about locales
[23:37] <minimal> they are 2 different packages
[23:38] <MICROburst> minimal: package 'locale' is installed too.
[23:39] <minimal> so perhaps test manually if the "update-locale" and "locale-gen" commands work as that's what cloud-init is using
[23:40] <minimal> meena: you're using those settings? ;-)
[23:41] <meena> minimal: i have no idea. I assume the system knows what it's doing. I set this via the GUI.
[23:42] <meena> this makes me wonder if there's ga_IE?
[23:42] <minimal> meena: so your part of Ireland is using Danish Krone for currency? lol
[23:43] <meena> damn, forgot about that bit
[23:43] <minimal> yupe, there is ga_IE indeed
[23:43] <MICROburst> minimal: "update-locale" and "locale-gen" do not have an impact on /etc/default/locale
[23:44] <minimal> though you're not in a Gaeltacht are you?
[23:44] <meena> minimal: very close to one
[23:44] <minimal> MICROburtst: I'm looking at the cloud-init distro/debian.py functions for locale handling and they do not use localctl (apart from keymap), they use either update-locale or locale-gen
[23:45] <meena> several people in my partner's family speak Irish, and my daughter is learning it from them, too, i hope. She's certainly learning more Irish than Bosnian.
[23:45] <minimal> and if yuo have debugging enabled in cloud-init you could then see the exactly commands run by cloud-init when trying to set the locale for you
[23:46] <minimal> meena: did 1 year of Irish decades ago and forgotten most of it
[23:47] <MICROburst> minimal: I'm using 'localectl ..." on shell to check. The .yaml file contains "locale: en_DK.UTF-8" -- So what do I need to change?
[23:47] <minimal> MICROburst: so you're using a command to test things that the cloud-init code does not use
[23:47] <meena> minimal: https://glitch.social/@meena/108444208010644055
[23:49] <minimal> MICROburst: look at cloudinit/distros/debian.py for the definition of LOCALE_CONF_FN and also at the get_locale and apply_locale functions in there
[23:51] <MICROburst> minimal: I can use for testing whatever I want - I has to work, since the system is installed. cloud-init has to set up things according to the .yaml file(s). I looked in /etc/default/locale as you recommended earlier - still "LANG=C.UTF-8"
[23:52] <minimal> MICROburst: "I can use for testing whatever I want" - as cloud-init does not use the localectl command then whether it works or not is irrelevant as cloud-init does not use it
[23:52] <minimal> or more specifically, cloud-init on Debian does not use it
[23:53] <MICROburst> minimal: So why is /etc/default/locale unchanged? - What do I need to put in user-data ... yaml?
[23:54] <minimal> I assume that file is unchanged because of the "invalid locale" you mentioned earlier
[23:54] <minimal> but I'm guess as you haven't shown any output from cloud-init.log when debugging is enabled
[23:58] <minimal> as the current contents of the /etc/default/locale file don't match the specified locale in your user-data then cloud-init should be running "locale-gen en_DK.UTF-8" and I assume that is what is failing
[23:58] <minimal> but I'm guessing whereas seeing the relevant excerpt from cloud-init.log would give specific information


[01:35] <ulysses> So something in the core of my Ubuntu Mate install for the Pi 3B just won't see audio devices
[01:35] <ulysses> Not through bluetooth, the headphone jack, nothin'
[01:35] <ulysses> Not HDMI or anything
[01:35] <ulysses> I've tried a lot to get it to play nice, but it just won't, any ideas what this issue is coming from?
[02:39] <sean__> 123
[02:40] <sean__> What is this place all about?
[07:51] <everett> Hey everyone! I'd like to change from mate to LXDE.. I'm on the RPi 3B
[07:51] <everett> How would I go about doing this?
[08:06] <ubuntu-mate> could anyone let me know how to install a VPN on a live bootable USB stick?
[08:06] <ubuntu-mate> running ubuntu 16.04?
[10:15] <weiys> kjs
[10:31] <alkisg> ubuntu-mate: why don't you install mate to a usb stick instead?
[10:31] <alkisg> (instead of using a live usb stick)
[11:01] <mate|8574> hallo
[11:01] <mate|8574> wie gehts?
[11:01] <diogenes_> es gehets
[11:01] <mate|8574> du bist ubuntu arbeiter?
[11:02] <mate|8574> ich bin neu hier ,,ich weiss nicht
[11:02] <diogenes_> nein, warum?
[11:02] <mate|8574> ich habe ein problem mit mein ubuntu
[11:03] <mate|8574> ich kann nicht chrome installiert
[11:03] <mate|8574> und mozila is sehr langsam
[11:03] <diogenes_> was ist die problem?
[11:03] <diogenes_> mit installiren
[11:04] <mate|8574> ja, genau
[11:05] <diogenes_> Versuche dies
[11:05] <diogenes_> !de | mate|8574
[11:06] <diogenes_> Wenn das nicht hilft, komm zurück
[11:06] <mate|8574> okay, verstehe
[11:06] <mate|8574> vielen dank,,,schon wochnende :)
[11:07] <diogenes_> bitte
[13:23] <mate|74347> Hello
[15:41] <Noobuntu> Hi everyone.
[15:42] <alkisg> Hello
[15:42] <Noobuntu> I have a few questions about Ubuntu-Mate 17.10
[15:43] <Noobuntu> I was just wondering if anyone knew how to change the hotkey for the built in drop down terminal from F12 to F2.
[15:45] <Noobuntu> I worked with Yakuake on past distros, and I'm just used to that key for my terminal. It's not a deal breaker, but it would be nice :)
[15:47] <Noobuntu> Any help would be most welcome :)
[15:49] <diogenes_> Noobuntu, did you check keyboard shortcuts settings?
[15:50] <Noobuntu> I don't think I did. I'm still getting used to Ubuntu MATE. I just installed it yesterday. One sec. Also, one last question: what shell does Ubuntu MATE use? I'd like to install a tweak tool that's  a bit more robust than the default MATE tweaks.
[15:52] <Noobuntu> I have the CTRL ALT T for a terminal, and I know that one, but it's not the drop down. I'm not seeing one for Tilda here.
[15:53] <diogenes_> sorry I use a different de so can't help
[15:54] <Noobuntu> Oh, don't worry about it. Do you know what shell Ubuntu MATE 17.10 uses by chance? Is it GNOME? I heard Ubuntu's new stuff is switching from unity to GNOME, but I'm a linux n00b, so I want to make sure.
[16:01] <Noobuntu> Got it! I had to go into Tilda's preferences.
[18:37] <dart> Good day
[18:38] <dart> I am getting a java script error after updating Ubuntu mate for the Raspberry pi 3 can you guys help thank you
[18:39] <dart> this happens on the Welcome screen
[18:42] <dart> I guess everybody is in church have a nice day y"all
[20:54] <sylvie_> Hello! Is there an indicator on ubuntu Mate that tells me when there are updates for ubuntu mate?
[20:56] <sylvie_> I know how to actively look for updates and install them, but I want to be informed when there are new ones.
[20:57] <tespi> you should get a prompt from time to time when there's updates to be installed
[20:57] <sylvie_> ...without having to hit "check for updates".
[20:58] <tespi> right
[20:58] <sylvie_> I thought so too, but I dont get any.
[20:58] <sylvie_> very weird
[20:58] <tespi> you can check your settings
[20:58] <tespi> maintenance -> updates
[20:58] <tespi> and the updates tab from that
[20:59] <sylvie_> for me personally it makes no difference but I want to give ubuntu mate to a friend who is not technical at all. she has to be prompted when there are new updates.
[20:59] <sylvie_> I check what you wrote...
[21:02] <sylvie_> well, I cannot find an equivalent in my language. But in the settings for the updates it says that the update check is performed daily.
[21:03] <sylvie_> and it says that there are a lot of updates to be done.
[21:03] <sylvie_> yet I see no notification in the system tray.
[21:04] <sylvie_> or anywhere outside the update program really.
[21:04] <alkisg> sylvie_: if you run `software-properties-gtk`, and check NOT to install updates automatically but show them instead, you'll get a dialog when there are updates
[21:04] <alkisg> Not an applet, but a dialog.
[21:06] <sylvie_> alkisg,  so my friend will have to be at the computer when the updates are announced? The notification will disappear after a certain time, right?
[21:06] <alkisg> It's not a notification. It's a dialog that stays open until you click and choose what you want to do with it
[21:07] <sylvie_> oh, good!
[21:07] <sylvie_> so I have to run `software-properties-gtk` in a terminal to check that?
[21:08] <sylvie_> oh!
[21:08] <sylvie_> got it
[21:08] <sylvie_> I was there before
[21:08] <alkisg> Yes. So the dialog is like this: https://4.bp.blogspot.com/-rwD_pKFvz1s/WWCbHtxkyfI/AAAAAAAAAZs/Bn2uGxyI5_AQo0V5CisfEngDFLc_Eu5QQCLcBGAs/s1600/software-update-1.png
[21:09] <sylvie_> I see
[21:11] <sylvie_> in my update settings it says that it looks for updates daily. Security updates are downloaded and installed immediately. Other updates are to be displayed instantly.
[21:12] <sylvie_> so is the theory.
[21:12] <alkisg> Sounds good
[21:12] <sylvie_> :-)
[21:12] <sylvie_> all well and good, but I not get notifications for new updates even it if stetes that I should do so.
[21:13] <sylvie_> I just never realized because I check for updates manually anyway.
[21:13] <sylvie_> maybe I reboot...
[21:14] <sylvie_> will be back in a minute
[21:17] <sylvie_> back again
[21:17] <sylvie_> rebooted
[21:18] <sylvie_> but no dialog concerning updates so far...
[21:19] <kernal> sudo apt update && sudo apt upgrade
[21:20] <sylvie_> kernal, I know how to do upgrades. I want to give ubuntu mate to a non technical friend and she has to ne notified when there are new updates.
[21:20] <sylvie_> kernal, so I am searching for a method of notification.
[21:21] <sylvie_> seems I never noticed that I did not get notified on my laptop because I usually look for updates manually.
[21:21] <kernal> when there are update, you will get notified
[21:22] <sylvie_> i just checked. There are several updates pending. But no notification.
[21:22] <sylvie_> I rebooted.
[21:22] <sylvie_> still no notification
[21:22] <sylvie_> Maybe I misconfigured something and do not remember.
[21:24] <kernal> in the Software & Updates program / Updates tab / what is selected for 'When there are other updates' ?
[21:25] <sylvie_> translates as "display immediately"
[21:26] <sylvie_> and the check for updates seems to be done daily
[21:26] <kernal> I've got dislapy weekly, and once a week I get a dialog to install the latest updates
[21:26] <sylvie_> security updates are set to be downloaded and installed immediately
[21:26] <sylvie_> hm...
[21:27] <sylvie_> well, thanks for telling me!
[21:27] <sylvie_> :-)
[23:59] <Guest89778> fuck


[14:58] <alkisg> highvoltage, stgraber: hi, I started getting CC'ed to the<EMAIL_ADDRESS>again, could you please remove me from that list once more?
[15:00] <stgraber> alkisg: done
[15:19] <alkisg> Nice!


 file file_9369.mp4 too big to download (3986368 > allowed size: 1000000)
 Forwarded from LinyxAdministration:


[00:59] <Greenfrog> on a restart my panel changed from black to white and the k gear was replaced with three dots and the > symbol, any ideas how to change it back?
[01:00] <Greenfrog> the add widgets panel is also white
[01:03] <Greenfrog> its just difficult for me to read
[02:09] <Guest5317> \password
[02:21] <valorie> Greenfrog: what version?
[02:21] <valorie> for awhile the plasma symbol (what you're seeing) replaced the KDE gear
[02:21] <valorie> but that was awhile ago
[02:22] <valorie> and it didn't last long
[02:22] <Greenfrog> ok was distracted for a min
[02:22] <Greenfrog> 18.04
[02:23] <Greenfrog> thats ok now, i dunno how i fixed it but a reboot
[02:23] <Greenfrog> now the panel wont auto hide
[02:23] <Greenfrog> it was working now not
[02:24] <valorie> huh
[02:24] <valorie> dunno
[02:24] <Greenfrog> ha, me either :)
[02:25] <Greenfrog> its just odd that many quirks show up after reboot
[02:25] <Greenfrog> i have chosen windows can hide, etc...no change
[02:28] <Greenfrog> ok, i guess i'll live with it for now
[03:27] <Greenfrog> nevermind, everything was fixed by a reboot. sorry to say
[03:28] <Greenfrog> i was told by a linux user to never reboot linux, but apparently that isnt true anymore
[03:44] <valorie> is it bluetooth?
[03:44] <valorie> if so you might have to turn on bluetooth
[03:45] <valorie> !bluetooth
[03:53] <valorie> hmmm
[03:54] <valorie> I don't know anything beyond what's in the link
[03:54] <valorie> I don't use it for my computer; just my phone
[03:57] <valorie> it should work, yes
[03:58] <valorie> I would try it both ways
[03:58] <valorie> from the computer
[03:58] <valorie> and from the mouse
[06:00] <Olivierhome-M> Good morning
[10:02] <BluesKaj> Hi folks
[17:15] <electronorbitals> I booted into kubuntu once using a live usb but had to cancel the installation because of a lack of free space then I rebooted it after making enough free space I couldnt boot into kubuntu using the same usb I've written the iso over and over again without any change but when I wrote elementary os iso it booted up after that I stll couldnt boot into kubunto the error was
[17:16] <electronorbitals> I'd like to know what happened
[22:56] <TMHD> Hello


[10:58] <Iamthehuman1> Hello and big thanks for the awesome Ubuntu Studio .. enjoying it every day for 19 days and running
[10:59] <Iamthehuman1> I think I got the same bug as someone had... after reboot the settings in alsamixer are not what they were when the computer was restarted
[10:59] <Iamthehuman1> I'll try and grep it out to see if I can find the other human with the similar problem from the log
[11:01] <Iamthehuman1> nope, wrong recollection, rgh had a problem with the plug state of the 3.5mm plug.
[11:03] <Iamthehuman1> This distro is great! Love it! Love you who make this happen!
[11:04] <Iamthehuman1> Summer is almost gon.. OCTOBER IS COMING SOON YEAY!
[11:06] <Iamthehuman1> So I have a time-effort-cost inexpensive workaround. Hit "favourites"-button of my laptop to open Yakuake (a nice dropdown terminal), ctrl-r, write "als", press enter and change the settings (once after a reboot)
[11:07] <MauroGaspari[m]> Iamthehuman1: I had the same issue and was able to fix it
[11:07] <Iamthehuman1> grepping
[11:07] <MauroGaspari[m]> I remember as I was trying to do alsa restore, i was monitoring the logs and it complained about this file /var/lib/alsa/asound.state
[11:07] <MauroGaspari[m]> so I backed it up, deleted it, rebooted and the issue was gone for me
[11:09] <Iamthehuman1> I see in the logs 'sudo alsactl store' ... I haven't used this command at all. I'm just used to alsa settings being saved and loaded from the default
[11:09] <Iamthehuman1> I mean there is a default alsa state and that usually gets restored automatically, but for some reason has gone slightly broken on my computer
[11:10] <MauroGaspari[m]> Yes It was very annoying for me as every time I rebooted, I got wrong volumes and that was due to alsa. easy to workaround but was very happy when I managed to fix it, with the help of our awesome OvenWerks
[11:11] <Iamthehuman1> Danke für Hilfeeeee OvenWerks!
[11:15] <Iamthehuman1> MauroGaspari[m]: Thanks for your input ... I'ma hang around if if someone knows more precisely what's gone broken. I'm going to go add some documentation to my intrawiki
[11:22] <Iamthehuman1> Documented.. I'm looking at /var/lib/alsa/asound.state ... so if I move this file elsewhere for safekeeping, power up all my interfaces and reboot it will likely rebuild it
[11:23] <MauroGaspari[m]> the command I was running when I noticed the issue in the logs, was alsactl restore
[11:25] <Iamthehuman1> now I think I could do one of those famous under-one-minute system backups with Timeshift and just see what happens, but then again I suspect this may be a different bug
[11:27] <Iamthehuman1> All Linuxen should have Timeshift, it is the resident "gonna save your ass if that change to the system went wrong"-program
[11:30] <Iamthehuman1> yeah.. 'alsactl help' mentions /var/lib/alsa/asound.state is the default state-file
[11:30] <Iamthehuman1> I'm going to try running 'sudo alsactl store' and reboot now
[11:31] <Iamthehuman12> here goes..
[11:46] <Iamthehuman1> Running 'sudo alsactl store' didn't affect... the alsamixer readings have to be manually adjusted
[11:48] <rgh> I got something similar and it turns out that it goes wrong when using jack and the pulse bridge (studio controls)
[11:49] <rgh> for me it's only the headphone plug switch though, the rest are fine
[11:50] <Iamthehuman1> so the autosave and autoload state are a bit borked in ALSA when running the JACK and the pulse bridge..
[11:53] <Iamthehuman1> When I power up and run alsamixer, the selected card is my Samson 49 midi conttroller, which is a bit odd, as it has no audio outputs
[14:14] <liver[m]> Hello everybody! I'm a linuxaudio from 15 years or more, my very first distro was UbuntuStudio, after many others experiences (KxStudio and QianaStudio) I'm back now... I love the bet on Plasma-Desktop... and I'm trying to understand StudioControls (I was used to Cadence). Thanks for the job!
[14:18] <david_parker[m]> Hi everyone! I'm a new user of Ubuntu Studio. I have a CompSci degree and am a software / web developer. I've got experience using Ubuntu Server, Fedora Desktop, Ubuntu desktop and Rasberry Pi Debian (I forget what that one's called exactly). Looking forward to playing with UbuntuStudio!
[14:41] <MauroGaspari[m]> david_parker: Óliver hello and welcome! I am glad you are enjoying Ubuntu Studio. For non support related chat, may I suggest you this room? #ubuntu-studio-offtopic:matrix.org
[14:41] <MauroGaspari[m]> You can keep both open, we just like keep this one for support questions. Thanks and welcome again! :)
[16:00] <liver[m]> Hi! any of you use a Contour ShuttlePro v2 with kdenlive and Ardour? I have an issue... I was able to get it to work with kdenlive after $ sudo usermod -a -G input user... in Ardour I created an udev file (I copied from Ardou github) and my ShuttlePro worked in Ardour but stops working with kdenlive. I'm not a familiar with udev files, but I think that if I include something in the udev file I can fix it.
[16:00] <liver[m]> the udev file says this:
[16:00] <liver[m]> SUBSYSTEM=="usb", ATTRS{idVendor}=="0b33", ATTRS{idProduct}=="0030", MODE="660", GROUP="audio"
[17:14] <Eickmeyer[m]> > <@olivermusico:matrix.org> Hi! any of you use a Contour ShuttlePro v2 with kdenlive and Ardour? I have an issue... I was able to get it to work with kdenlive after $ sudo usermod -a -G input user... in Ardour I created an udev file (I copied from Ardou github) and my ShuttlePro worked in Ardour but stops working with kdenlive. I'm not a familiar with udev files, but I think that if I include something in the udev file I can fix it.
[17:14] <Eickmeyer[m]> > the udev file says this:
[17:14] <Eickmeyer[m]> > SUBSYSTEM=="usb", ATTRS{idVendor}=="0b33", ATTRS{idProduct}=="0030", MODE="660", GROUP="audio"
[17:14] <Eickmeyer[m]> You might try asking in #kdenlive:kde.org and/or #ardour:libera.chat
[17:15] <dikonoor> Hi , I have a query related to automated installation of Ubuntu 20.04. I have been using a preseed file and the following file. This has been working fine with Ubuntu 18.04 but not with 20.04:
[17:15] <dikonoor> virt-install -n $(VM_NAME) -r 4096
[17:15] <dikonoor> 	--os-type=linux
[17:15] <dikonoor> 	--os-variant=ubuntu18.04
[17:15] <dikonoor> 	--disk $(VM_DISK),device=disk,bus=virtio,size=100,sparse=true,format=raw -w network=default,model=virtio
[17:15] <dikonoor> 	--noautoconsole
[17:15] <dikonoor> 	--location $(ISO_FULLPATH)
[17:15] <dikonoor> 	--nographics
[17:15] <dikonoor> 	--initrd-inject=./preseed.cfg
[17:15] <dikonoor> 	--extra-args="ks=file:/preseed.cfg ksdevice=enc1"
[17:16] <Eickmeyer[m]> !paste | dikonoor
[17:16] <Eickmeyer[m]> dikonoor: That's offtopic for this room, try in #ubuntu.
[17:17] <dikonoor> Thanks Eickmeyer. Let me try #ubuntu.


[01:45] <guiverc> has jammy daily been built with proposed?  (I gather yes)
[01:50]  * guiverc convinced yep..