[07:11] <tsdgeos> slowest internet ever
[07:11] <tsdgeos> 0.5MB
[07:11] <tsdgeos> going to reboot the router
[07:21] <tsdgeos> meh, still slow
[07:21] <tsdgeos> :/
[07:59] <Cimi> tsdgeos, hola :)
[08:00] <tsdgeos> Cimi: ciao
[08:00] <Cimi> :)
[08:00] <Cimi> tsdgeos, do you know anything about vertical journal?
[08:00] <tsdgeos> Cimi: lots of things
[08:00] <Cimi> tsdgeos, cool!
[08:02] <Cimi> tsdgeos, it feels like there is one small bug in the cardcreator that was setting maybe a wrong implicitheight
[08:03] <Cimi> tsdgeos, but then the card is clipped by the container where is put
[08:04] <Cimi> actually no, there is sth weird here
[08:46] <dandrader> tsdgeos, do you get this failure with unity8 trunk? http://paste.ubuntu.com/8477914/
[08:46] <tsdgeos> yes
[08:46] <tsdgeos> you don't have to fix that one
[08:51] <tsdgeos> mzanetti: i did publish https://code.launchpad.net/~aacid/unity8/fixleftlaunchergreetertodash/+merge/236829 again
[08:51] <tsdgeos> mzanetti: if you care to reapprove :D
[08:51] <tsdgeos> dandrader: and you can have a look at fix_left_swipe_temp_scope_overview agian
[09:04] <mzanetti> tsdgeos: yeah... given that I'm a bit stuck with setting up the next silo atm I'd prefer to also have mterry a look at this
[09:04] <tsdgeos> ok
[09:05] <mzanetti> i.e. have to do some rtm releases before we can release to utopic again. otherwise they drift too much
[09:05] <tsdgeos> yep
[09:10] <Cimi> tsdgeos, I linked a branch to https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362160
[09:11] <Cimi> tsdgeos, but the result is still clipped maybe because of the margin in ResponsiveVerticalJournal
[09:13] <tsdgeos> Cimi: well ResponsiveVerticalJournal is supposed to clip, no?
[09:14] <Cimi> tsdgeos, but the bug seems to complain that it clips
[09:14] <tsdgeos> well, they should not use a ResponsiveVerticalJournal then
[09:15] <Cimi> tsdgeos, anyway, that branch should fix the bug
[09:16] <Cimi> https://code.launchpad.net/~unity-team/unity8/fix-card-implicitHeight/+merge/236833
[09:16] <tsdgeos> Cimi: the CardVJ will "clip" at 35gus
[09:16] <tsdgeos> after that you can expand it
[09:16] <tsdgeos> it's how it works
[09:17] <Cimi> tsdgeos, there is something more
[09:17] <Cimi> tsdgeos, if you take that branch and change 35 to more, it still clips
[09:17] <tsdgeos> welll
[09:17] <tsdgeos> then that's a bug
[09:17] <Cimi> tsdgeos, because inside ResponsiveVerticalJournal.qml
[09:17] <Cimi> tsdgeos, there is VerticalJournal
[09:18] <Cimi> tsdgeos, and I think those margins are problematic
[09:18] <Cimi> first of all, if I change them all is blank
[09:26] <Cimi> tsdgeos, on desktop, height is 234, implicitHeight 234.66666
[09:26] <Cimi> tsdgeos, looks like height is floor of implicitHeight?
[09:27] <Cimi> shouldn't it be ceil?
[09:28] <tsdgeos> Cimi: noone cares :D
[09:28] <tsdgeos> i mean you're missing 0.6 pixels?
[09:28] <Cimi> tsdgeos, seems like at least
[09:28] <tsdgeos> i don't think this is your problem
[09:28] <tsdgeos> but sure, you can find where we do this and add a ceil instead of direct asssignment
[09:29] <Cimi> tsdgeos, might be qt?
[09:29] <tsdgeos> qt what?
[09:29] <tsdgeos> you're assigning a float to an int
[09:29] <tsdgeos> it obviously gets cut
[09:29] <Cimi> height is realk
[09:30] <Cimi> real
[09:30] <dandrader> mzanetti, is there a technical reason for tst_Launcher have several UT.UnityTestCase  instead of just one?
[09:30] <mzanetti> dandrader: yes
[09:30] <mzanetti> dandrader: I want to restart it
[09:31] <mzanetti> dandrader: they have different init() functions
[09:31] <mzanetti> etc
[09:31] <dandrader> mzanetti, you want to restart what?
[09:31] <tsdgeos> Cimi: but not collapsedHeight/expandedHeight
[09:31] <mzanetti> dandrader: like the component gets destructed and recreated between those
[09:32] <dandrader> mzanetti, launcher?
[09:32] <mzanetti> yes
[09:32] <mzanetti> iirc. it's bee a while
[09:32] <Cimi> tsdgeos, right
[09:32] <mzanetti> but I remember I did this on purpose
[09:32] <Cimi> tsdgeos, why we did int?
[09:33] <tsdgeos> Cimi: bug?
[09:33] <tsdgeos> interneeeeeeeeeeeeeeeeeeeeeeeeeeeet come on :'(
[09:33] <Cimi> tsdgeos, will add that to the branch
[09:33] <Cimi> tsdgeos, :)
[09:33] <Cimi> tsdgeos, how come internet is slow?
[09:33] <tsdgeos> my isp is crap
[09:34] <Cimi> tsdgeos, mine is 125Mb/12Mb... all is fine... until one day suddenly dies for an hour
[09:34] <Cimi> tsdgeos, I had more issues with fiber this year than my previous 10 with adsl
[09:35] <Cimi> it is equally annoying...
[09:35] <tsdgeos> vesar: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1369644
[09:35] <Cimi> don't you have LTE in barca?
[09:36] <tsdgeos> i don't
[09:37] <tsdgeos> and my phone doesn't support it either
[09:37] <Cimi> I commented on that bug
[09:38] <vesar> tsdgeos, so you're looking for what should be the notification of a new screen shot for the user?
[09:38] <tsdgeos> vesar: yes
[09:38] <Cimi> vesar, I vote for an entry in notification center! I commented on the bug
[09:38] <tsdgeos> well AlbertA is :D
[09:38] <vesar> tsdgeos, is there some video of the current one?
[09:39] <tsdgeos> vesar: AlbertA said he'd record a video, but i don't see a link
[09:39] <tsdgeos> he's probably still asleep thoguh
[09:39]  * tsdgeos asks mup
[09:39] <tsdgeos> time:04h39-0500
[09:39] <tsdgeos> yeah :D
[09:39] <tsdgeos> vesar: but basically is a white fadein+out afaik
[09:40] <Cimi> vesar, is a white rectangle fading overlay
[09:43] <Cimi> tsdgeos, http://i.imgur.com/ad7wOGO.png
[09:44] <Cimi> tsdgeos, this is with using real... looks like bottom margin should be required
[09:46] <tsdgeos> where?
[09:51] <tsdgeos> Cimi: ↑
[09:51] <Cimi> tsdgeos, under the card journal
[09:51] <Cimi> tsdgeos, coldplay card
[09:52] <tsdgeos> looks good to me
[09:52] <Cimi> tsdgeos, overlaps
[09:52] <tsdgeos> e?
[09:52] <Cimi> tsdgeos, it should be clipped
[09:52] <tsdgeos> what overlaps?
[09:52] <tsdgeos> ah fuck
[09:52] <tsdgeos> right
[09:52] <Cimi> tsdgeos, it goes over the category
[09:52] <tsdgeos> the line thing
[09:52] <Cimi> xmag is your friend :)
[09:52] <tsdgeos> it's so subtle
[09:53] <Cimi> indeed
[09:53] <Cimi> I had to use xmag
[09:53] <Cimi> lp:~unity-team/unity8/fix-card-implicitHeigh
[09:53] <Cimi> t
[09:57] <Cimi> tsdgeos, what should be the right behaviour?
[09:58] <Cimi> tsdgeos, that card being clipped by the category?
[10:00] <tsdgeos> give me a sec
[10:01] <vesar> AlbertA, would you have a video of the current screenshot notification? https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1369644
[10:17] <tsdgeos> Cimi: how do you get to there? search in music?
[10:17] <Cimi> tsdgeos, no
[10:17] <Cimi> tsdgeos, just have few artists
[10:18] <tsdgeos> uf
[10:18] <Cimi> tsdgeos, yeah...
[10:18] <tsdgeos> Cimi: that screenshot is actually weird
[10:19] <tsdgeos> since the divider is anchored at the bottom
[10:19] <Cimi> tsdgeos, u can use scope tool
[10:19] <tsdgeos> should not be before it
[10:19] <Cimi> tsdgeos, http://paste.ubuntu.com/8478282/
[10:19] <Cimi> tsdgeos, just do this in app scope
[10:20] <tsdgeos> Cimi: do where? in override category?
[10:21] <tsdgeos> yes
[10:21] <tsdgeos> ok
[10:22] <tsdgeos> Cimi: what i see there is clipping, not what you showed me
[10:23] <Cimi> tsdgeos, are u running my branch?
[10:23] <tsdgeos> which one?
[10:24] <Cimi> tsdgeos, here is noty clipped
[10:24] <Cimi> tsdgeos, https://code.launchpad.net/~unity-team/unity8/fix-card-implicitHeight/+merge/236834
[10:24] <Cimi> tsdgeos, latest revision
[10:32] <tsdgeos> Cimi: we need this http://paste.ubuntu.com/8478346/
[10:39] <Cimi> tsdgeos, yes I KNOW ADDING MARGIN THERE HELPS... BUT IT IT CORRECT?
[10:39] <Cimi> ops caps lock
[10:39] <tsdgeos> Cimi: why do you think it is not?
[10:40] <Cimi> or we want to clip?
[10:40] <Cimi> tsdgeos, or we want to add padding somewhere else
[10:40] <tsdgeos> why would you want to clip?
[10:40] <Cimi> margin
[10:40] <tsdgeos> Cimi: that doesn't add padding anywhere, that fixes a bug
[10:41] <Cimi> tsdgeos, but is rowspacing also, or more?
[10:41] <tsdgeos> seb128: any chance we show wifis by power on the welcome wizard? it is kind of boring having to find my wifi from the 30 i get :D
[10:41] <Cimi> we could use units.gu(2)
[10:42] <tsdgeos> Cimi: we could use other stuff
[10:42] <tsdgeos> and it would be wrong
[10:42] <tsdgeos> this is right
[10:42] <tsdgeos> read the code
[10:42] <Cimi> ok
[10:42] <tsdgeos> and tell me why you think it's wrong
[10:43] <seb128> tsdgeos, that's a question for Cimi, he's the one working on the wizard
[10:44] <tsdgeos> Cimi: can we show the wifis sorted by power in the wiizard?
[10:46] <Cimi> tsdgeos, nope
[10:47] <Cimi> tsdgeos, this is a question for Wellark
[10:48] <Cimi> tsdgeos, with your code, the line clip: parent.height != implicitHeight will basically always be true
[10:48]  * tsdgeos keeps the redirection
[10:49] <tsdgeos> Wellark: can we show the wifis in power order in the welcome wizard?
[10:49] <Cimi> tsdgeos, wizard, indicators, system settings, they all get the model from dbus
[10:49] <tsdgeos> Cimi: rihgt, that needs fixing
[10:49] <Cimi> tsdgeos, we just display what unitymenumodel gives us
[10:49] <Cimi> tsdgeos, so is a backend thing
[10:50] <Cimi> tsdgeos, together with the bug that super annoys me, connecting on an access point jumps it at top of the list
[10:50] <tsdgeos> Cimi: or could move the margins out
[10:50] <Cimi> tsdgeos, so you basically see it disappearing when you tap it
[10:51] <tsdgeos> or just add rowSpacing below
[10:51] <tsdgeos> or replace it with parent.implicitheight
[10:51] <tsdgeos> that one actually makes more sense i guess
[10:52] <Cimi> tsdgeos, if I play with the margins inside VerticalJournal, the journal disappears :/
[10:52] <tsdgeos> don't play with them then D:
[10:52] <Cimi> hah
[10:57] <Cimi> tsdgeos, maybe adding padding in both expanded and collapsed height inside CardVerticalJournal?
[10:57] <Cimi> works the same
[10:58] <tsdgeos> Cimi: this is not padding
[10:59] <tsdgeos> this is making it right
[10:59] <tsdgeos> if VJ tells you it wants to be 100px height, and then you add a bottomMargin and topMargin of rowSpacing/2, you need to add rowSpacing to its height
[11:00] <tsdgeos> doing it anywhere else than RVJ is wrong
[11:00] <tsdgeos> do you understand what i mean?
[11:02] <Cimi> tsdgeos, I do now
[11:02] <Cimi> tsdgeos, so we need to change clipping I suppose
[11:03] <tsdgeos> yeah
[11:03] <tsdgeos> clip: parent.height != parent.implicitHeight
[11:03] <tsdgeos> or move it up to the parent
[11:03] <tsdgeos> and make it
[11:03] <tsdgeos> clip: height != implicitHeight
[11:03] <tsdgeos> i guess
[11:03] <tsdgeos> the second would actually make a bit more sense
[11:04] <Cimi> tsdgeos, != or < ?
[11:05] <tsdgeos> can use < but it will never should be >
[11:07] <Cimi> tsdgeos, it should clip if height is set smaller than implicitHeight?
[11:07] <Cimi> tsdgeos, if is the same or bigger, clip is not required, right?
[11:07] <tsdgeos> right
[11:08] <Cimi> tsdgeos, pushed, you can reapprove
[11:10] <tsdgeos> Cimi: can you give the branch a better commit log?
[11:10] <tsdgeos> since it also fixes RVJ height now
[11:11] <Cimi> tsdgeos, done
[11:12] <Wellark> Cimi, tsdgeos: hello
[11:12] <Wellark> sorry, what?
[11:12] <Cimi> redone
[11:12] <Wellark> you want to show the wifi accesspoints ordered by strength?
[11:12] <Wellark> negative.
[11:12] <Wellark> if you have 20 access points near by and your own is not the strongest one then it will be a PITA trying to find you access point
[11:13] <Wellark> if it's a full list, then it must be ordered by SSID name
[11:13] <Wellark> the indicator will limit the number of access points in the indicator menu to the five or something strongest ones
[11:13] <Wellark> and they will be ordered by strength
[11:14] <Wellark> but the system-settings and the welcoming wizard are showing the full list so, sorry, no ordering by strength
[11:14] <Wellark> tsdgeos, Cimi: what is the use case you are trying to fix?'
[11:16] <tsdgeos> Wellark: i can't find my wifi :D
[11:17] <tsdgeos> because i have 20 access points searching is horrible
[11:17] <tsdgeos> Wellark: as an example i just setup a windows 8 laptop for my family and my wifi was correctly at the top on the windows8 wecolme wizard
[11:21] <Wellark> tsdgeos: you do know the name of your wifi, right?
[11:21] <Wellark> so going throuh an alphabetical list should not be so hard? ;)
[11:22] <Wellark> tsdgeos: sure, what about your neighbor that comes to your house and wants to use his wifi when he sets up his win8
[11:22] <Wellark> and then he has no other way than actually looking through _all_ of the access point names trying to find which one is his
[11:23] <Wellark> as they are ordered totally arbitrary by strength
[11:23] <Wellark> people look for specific name
[11:23] <Wellark> when they want to connect to a wifi network
[11:23] <Wellark> if it would not matter which one they take
[11:23] <Wellark> then it would be perfectly OK to order by strength
[11:23] <tsdgeos> strength is not arbitrary
[11:23] <tsdgeos> but whatever
[11:23] <tsdgeos> i'm not going to convince you
[11:24] <tsdgeos> every single device i have does it the way i say
[11:24] <tsdgeos> but you're right :)
[11:25] <Wellark> tsdgeos: yes. and I have been trying to use "those other devices" in an envinment with dozens of accesspoints around
[11:25] <Wellark> and they all _suck_
[11:25] <tsdgeos> like my house
[11:25] <tsdgeos> where i get 20 networs
[11:25] <tsdgeos> it doesn't suck
[11:26] <tsdgeos> it's awesome i don't have to swipe down trying to find my network
[11:26] <tsdgeos> and wondering why if it's the only one with 100% power and all others are 10% is not on the top
[11:26] <Wellark> well, you are just lucky that your wifi has the strongest signal around
[11:26] <tsdgeos> but as said, you're right, everyone else got it wrong
[11:26] <Wellark> tsdgeos: good :)
[11:26] <tsdgeos> end of discussion
[11:28] <seb128> tsdgeos, you should rather talk to mpt/designers about that
[11:32] <Wellark> tsdgeos: I was talking about full list of access points. nothing would stop the wizard from having a default of five strongest access points and then provide means to see the full list
[11:33] <mpt> Meanwhile, jounih was just complaining to me about the networks jumping around in the list, which they inevitably do if they’re sorted by strength
[11:34] <Wellark> mpt: yes. when you select an access point the list should be scrolled up
[11:34] <Wellark> which the u-s-s does not do either atm
[11:35] <Wellark> mpt: oh, you commented on the "ordered by strength"
[11:35] <Wellark> yes
[11:35] <Wellark> so imagine being in a conference center during some major evet
[11:35] <Wellark> *event
[11:35] <Wellark> with dozens and dozens of access points
[11:35] <Wellark> and having the full list ordered by strength
[11:36] <Wellark> it would go all over the place before you can pinpoint the one you actually want to connect with
[11:36] <Wellark> and once the ordering changes you have to start all over again from the top
[11:37] <Wellark> mpt: so, that what jounih is seeing is because the wizard nor the system-settings is scrolling the list back to the top when an access point is selected for connection
[11:37] <Wellark> dunno if we have a bug about that..
[12:15] <mpt> Wellark, yes, I suggested that it should stay where it is until it’s actually finished connecting
[12:27] <mpt> Wellark, it’s bug 1349371
[12:42] <Wellark> mpt: can't really do that..
[12:42] <Wellark> mpt: maybe after Washington?
[12:43] <mpt> Do I have a piece of paper taped to my back that says “I am an engineering manager”? :-)
[12:44] <mpt> I design things. If you say “we need a simpler solution by X date”, I can do that  … But that bug is currently Low, so apparently it doesn’t need fixing at all before RTM
[12:46] <Wellark> mpt: well, you asked for it ;)
[12:48] <mpt> I did no such thing
[12:57] <Cimi> alecu, hola! what do I need for that? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1267184 from you side?
[12:59] <alecu> Cimi: is this about the launcher or the dash icons?
[12:59] <Cimi> alecu, everything :)
[12:59] <Cimi> alecu, I don't know what info we receive from the backend
[13:00] <Cimi> alecu, whatever is missing, basically
[13:01] <alecu> Cimi: ok, regarding the launcher animation, I think all the code is in place in the scope, and there's some sample code of how the client for that would work.
[13:02] <alecu> Cimi: by the launcher I mean the animation as shown in the video here: https://sites.google.com/a/canonical.com/unity8dash/scopes/store/3-previews
[13:02] <alecu> Cimi: now, regarding icons in the dash, I don't think there's code in the scope for that yet
[13:03] <alecu> Cimi: is all of this supposed to be in for rtm, right?
[13:03] <Cimi> alecu, I read ota 2
[13:03] <Cimi> alecu, but I am ready now to work on it...
[13:04]  * alecu just notices the ota-2 tag :P
[13:11] <alecu> ok, found it
[13:11] <alecu> Cimi: http://bazaar.launchpad.net/~ubuntuone-control-tower/unity-scope-click/trunk/files/head:/scope/tests/fake_launcher/
[13:12] <alecu> Cimi: that's a "fake launcher" I've used for testing the click scope
[13:12] <alecu> Cimi: it listens to the dbus signals from click scope, telling it when an app has been started installing
[13:12] <alecu> and for the progress of installation
[13:13] <alecu> and it gets notified when the click package installation has been completed, giving it the app_id that the launcher will need to launch the app
[13:13] <alecu> when starting it gives the launcher a title and the url of an icon
[13:14] <alecu> Cimi: but
[13:15] <alecu> big but...
[13:15] <alecu> we planned this a few months ago, when we decided that we wouldn't be doing the Installation Manager for rtm.
[13:15] <alecu> I think we still need to work on the Installation Manager at some point
[13:17] <alecu> that means that the progress api will need some changes
[13:18] <alecu> but I think it's ok for you to start on the visual parts of the launcher animations and filling up, and then we can adapt it when (and if!) we change the backend. I think the changes should be minimal.
[13:19] <alecu> Cimi: if it's ok with you, let's do a hangout tomorrow to talk a bit more about this.
[13:33] <tsdgeos> vesar: ping
[13:34] <vesar> tsdgeos, yo
[13:34] <tsdgeos> vesar: who would be better to install a ppa on a phone and hand it over to JMulholland and friends so they can have a look?
[13:35] <vesar> tsdgeos, well I think I'm the best person to do that around here.
[13:36] <vesar> tsdgeos, just give me the instructions and I can do it
[13:36] <tsdgeos> vesar: ok, let me sync up with a few people and i'll send you an email or ping you here
[13:37] <vesar> tsdgeos, very good
[13:37] <tsdgeos> pstolowski: can you merge feeds with the new release?
[13:37] <tsdgeos> vesar: thanks :)
[13:37] <vesar> tsdgeos, no probs
[13:37] <pstolowski> tsdgeos, will do
[13:58] <Cimi> alecu, ok
[14:21] <ted> dednick, Do you have a bug number for the "unknown" text in the media widget of indicator sound?
[14:22] <ted> dednick, Want to dup one to it.
[14:23] <dednick> ted: no. it shouldnt be there anymore though
[14:23] <dednick> ted: i mean, you shouldn't get unknown
[14:23] <ted> dednick, Apparently in a version of rtm it is.
[14:24] <dednick> ted: i c. no. there's no bug
[14:24] <ted> dednick, What component should I mark it fixed release on? :-)
[14:24] <dednick> ted: unity8
[14:26] <ted> dednick, bug 1376221
[14:26] <dednick> ted: ya
[14:28] <mzanetti> mterry: hey ho. tsdgeos fixed it. mind giving it a look too (esp last comment) https://code.launchpad.net/~aacid/unity8/fixleftlaunchergreetertodash/+merge/236829
[14:29] <mterry> tsdgeos: aw thanks!
[14:29] <mterry> mzanetti, will do
[14:31] <mzanetti> mterry: ok. thanks. will put it to the next silo
[14:35] <tsdgeos> paulliu: https://code.launchpad.net/~aacid/unity8/fixleftlaunchergreetertodash
[14:36] <paulliu> tsdgeos: ok. thanks. Let me try it.
[14:38] <cwayne> mzanetti: any idea when the next silo will exist?
[14:38] <mzanetti> cwayne: what are you waiting on?
[14:38] <mzanetti> cwayne: currently the "next" can refer to 4 :D
[14:39] <cwayne> mzanetti: the card-visual-tweaks branch
[14:39] <mzanetti> cwayne: ack, worst case, will be the 4th
[14:39] <mzanetti> cwayne: we are lagging behind with rtm releases
[14:39] <cwayne> mzanetti: aren't we all :)
[14:39] <mzanetti> cwayne: have to do 3 rtm releases now, then we'll continue with utopic ones
[14:39] <mzanetti> cwayne: but, the next spreadsheet row contains that branch already
[14:40] <tsdgeos> mzanetti: mterry: one of the two top approve https://code.launchpad.net/~aacid/unity8/fixleftlaunchergreetertodash/+merge/236829
[14:41] <mzanetti> done
[14:41] <mterry> the bot hadn't commented yet  :)
[14:41] <cwayne> mzanetti: ah i'd missed that, thanks
[15:46] <sil2100> mterry: hey! I just wanted to poke you about the unlock-screen issues we've been seeing - do you know the reasons for why sometimes it's failing to unlock the screen during smoketesting?
[15:47] <mterry> sil2100, https://code.launchpad.net/~mterry/unity8/retry-unlock/+merge/236167 hasn't landed yet...
[15:47] <mterry> sil2100, that may help
[15:47] <mterry> sil2100, oh wait, smoketesting?
[15:47] <mterry> sil2100, like actual human on device testing?
[15:47] <sil2100> No no
[15:47] <sil2100> mterry: the autopilot smoketesting ;)
[15:48] <mterry> sil2100, oh yeah then the above branch might help.  It's possible there's a race between booting and trying to unlock
[15:48] <sil2100> Oh, a loop
[15:48] <sil2100> ACK ;)


[01:51] <jbicha> GunnarHj: howdy, I opened LP: #1762889
[01:51] <ubot5`> Launchpad bug 1762889 in pkgbinarymangler (Ubuntu) "dh_translations doesn't strip .desktop files when more than 1 pot target with meson" [Undecided,New] https://launchpad.net/bugs/1762889
[01:55] <GunnarHj> jbicha: As I wrote in a comment on that libgweather commit, it's worse than that. dh_translations does not do anything, so AFAICT we need to keep all those debian/rules entries for now for all packages with > 1 domain.
[01:55] <jbicha> just a moment…
[01:58] <jbicha> ok, I see. I'm reverting the libgweather commit
[01:58] <GunnarHj> jbicha: Good. But your idea in that bug looks interesting.
[01:58] <jbicha> I um never noticed the _translations.tar.gz before and I didn't realize there is supposed to be a .pot inside it
[01:59] <GunnarHj> The setup is pretty complex... I think I have learned a lot of it the past few months.
[06:39] <didrocks> good morning
[06:57] <duflu> Hi didrocks
[07:12] <oSoMoN> good morning desktoppers
[07:13] <duflu> G'day oSoMoN
[07:13] <oSoMoN> hey duflu
[07:17] <didrocks> hey duflu, oSoMoN
[07:17] <oSoMoN> salut didrocks
[07:39] <seb128> good morning desktopers
[07:39] <seb128> hey didrocks oSoMoN duflu
[07:39] <duflu> Hi seb128
[07:43] <didrocks> hey seb128
[07:44] <seb128> how is everyone today?
[07:46] <didrocks> rather good, but tiring night with little one coughing
[07:46] <didrocks> you?
[07:46] <seb128> oh :(
[07:46] <seb128> the kids being sick is never ending :/
[07:47] <didrocks> never *ever*
[07:48] <seb128> I'm fine but that cold is rather annoying, nose is really blocked and I don't sleep well and need to use tissues every few minutes
[07:48] <seb128> it's a bit better today so hopefully I get over it before the w.e
[07:50] <oSoMoN> salut seb128
[07:52] <didrocks> seb128: crossing fingers!
[07:57] <duflu> seb128, life was good until I started trying to debug Totem again. Then not so good
[07:58] <seb128> :/
[07:59] <duflu> koza, seb128, jibel, the meeting time is wrong again. Should be 1 hour from now but Google thinks it is now. Anything to discuss?
[07:59] <seb128> duflu, calendar says jibel is off today
[07:59] <seb128> willcooke is in London
[07:59] <seb128> I don't have anything to discuss
[08:00] <seb128> should we skip?
[08:00] <duflu> seb128, koza, yes skipping. I'm off outside for a couple of minutes in that case
[08:01] <duflu> And then there was willcooke. Good morning
[08:01] <seb128> duflu, ttyl!
[08:01] <seb128> hey willcooke
[08:01] <willcooke> moin
[08:01] <seb128> duflu, we probably want to discuss 5.49 (or 50) for SRU/.1 but that be after 18.04 is out
[08:01] <willcooke> seb128, did you already ask duflu about that bug we talked about in the meeting?
[08:01] <Laney> yo
[08:02] <seb128> willcooke, not yet, we were talking bluetooth
[08:02] <willcooke> ack
[08:02] <seb128> hey Laney, what's up?
[08:02] <willcooke> what ho Laney
[08:02] <Laney> hey seb128 willcooke
[08:02] <didrocks> hey hey willcooke, Laney
[08:02] <willcooke> hi didrocks
[08:02] <Laney> hey didrocks!
[08:02] <Laney> did my first ever "jog" yesterday evening
[08:02] <Laney> now my legs hurt
[08:03] <didrocks> did you stretch afterward?
[08:03] <Laney> a bit
[08:03] <Laney> it ended at the pub so I stretched my arm at least ;-)
[08:03] <didrocks> ahah, and mouth as well I guess :)
[08:03] <Laney> could do more I guess
[08:04] <didrocks> especially after jogging :p
[08:04] <Laney> going to do the park run on saturday, wanted to check if I was going to die ...
[08:04] <willcooke> duflu, seb128 do you guys want to join the HO or nothing to talk about?
[08:05] <didrocks> Laney: how long will it be?
[08:05] <seb128> beer is good for re-hydrating
[08:05] <seb128> willcooke, oh, we just agreed to skip before you joined, we though you were on your way to London and we didn't have anything to discuss
[08:06] <seb128> willcooke, also <seb128> duflu, we probably want to discuss 5.49 (or 50) for SRU/.1 but that be after 18.04 is out
[08:06] <Laney> didrocks: it's 5k
[08:06] <didrocks> is there an equivalent in gtk2 of gtk3-demo-application? I thought there was, can't find the name back (I know there is gtk-demo, but the example is better to check busy cursor and such)
[08:06] <seb128> willcooke, also dufl_u pointed out that the meeting should be an hour later but the calendar shows it for now, DST still not fully sorted out :/
[08:06] <seb128> (I don't know if that's right and both slots wfm)
[08:07] <didrocks> Laney: I would say you will suffer for the last 1.5-2km ;) but it's still doable for a noob :p
[08:07] <Laney> heheh
[08:08] <Laney> tkamppeter: hi, are you going to fix pstotext for that bug?
[08:08] <duflu> And morning Laney
[08:10] <duflu> seb128, I think maybe you missed the last BT meeting. We decided there to look at 5.49+ after 18.04. And I mentioned it in a bug or two too
[08:10] <willcooke> just had a quick chat with koza
[08:10] <willcooke> and will be heading to London in a mo
[08:11] <duflu> koza, are you really online?
[08:14] <dupondje> https://gitlab.gnome.org/GNOME/mutter/issues/81 seems we have working patches :D
[08:14] <ubot5-ng> GNOME bug 81 in mutter "hybrid GPU: one screen stays black in mutter 3.28" (comments: 19) [Opened]
[08:14] <ubot5`> Error: Gnome bug 81 could not be found
[08:17] <seb128> willcooke, ok oh, koza didn't reply on the channel so we though he was not around ... next time
[08:17] <seb128> dupondje, did they made it to .1?
[08:17] <willcooke> nw, we just had a chat about life, the universe and everything
[08:17] <seb128> :)
[08:18] <willcooke> running the skype snap on 18.04 segfaults mutter
[08:18] <seb128> that's nice
[08:22] <seb128> willcooke, did you apport/whoopsie report it?
[08:22] <didrocks> there is not anymore gtk2 widget factory app, correct?
[08:22] <duflu> Problems with Skype sound familiar
[08:23] <willcooke> seb128, https://launchpad.net/bugs/1762954
[08:23] <ubot5`> Ubuntu bug 1762954 in snapd (Ubuntu) "Running the skype snap under the Wayland session crashes the whole session" [Undecided,New]
[08:23] <seb128> didrocks, not that I know
[08:23] <seb128> willcooke, you don't get a report in /var/crash?
[08:23] <didrocks> damn, I will need to create a simple app with busy cursor it seems… thanks seb128
[08:23] <seb128> didrocks, :/
[08:24] <dupondje> seb128: will see :) Dunno when they will tag .1?
[08:24] <duflu> seb128, no news is good news. There's still time: https://gitlab.gnome.org/GNOME/mutter/blob/master/NEWS
[08:24] <seb128> dupondje, they were supposed to do that on monday but some components are late
[08:24] <duflu> Also https://gitlab.gnome.org/GNOME/mutter/blob/gnome-3-28/NEWS
[08:24] <willcooke> seb128, hm, I think I do, but it didnt upload it.  Should I just attach it to the bug?
[08:24] <dupondje> I just confirmed the patch works, so lets hope :)
[08:24] <seb128> willcooke, please don't, just use ubuntu-bug on it
[08:25] <seb128> ubuntu-bug .crash
[08:25] <seb128> dupondje, great
[08:42] <willcooke> seb128, done that as a new bug, LP: #1762960
[08:42] <ubot5`> Launchpad bug 1762960 in gnome-shell (Ubuntu) "Running classic snaps crashes wayland session" [Undecided,New] https://launchpad.net/bugs/1762960
[08:42] <willcooke> I'll tidy up the old one, and sort out the dupes later, need to get on the train now
[08:43] <seb128> willcooke, thanks
[08:43] <willcooke> will try and get a table on the train
[08:43] <willcooke> see you in a bit
[08:45] <seb128> duflu, good to have a reliable way to trigger one of those xwayland segfaults! ^
[08:47] <duflu> seb128, I checked yesterday and there are relatively few Xwayland crashes compared to gnome-shell crashes. The numbers don't align
[08:47] <duflu> I updated the main bug about it
[08:48] <seb128> k
[08:48] <duflu> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1505409
[08:48] <ubot5`> Ubuntu bug 1505409 in GNOME Shell "gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]" [Critical,Confirmed]
[09:02] <didrocks> oSoMoN: do you mind testing out https://github.com/ubuntu/communitheme-snap-helpers/pull/3? It should fix GTK2 support. You have instructions to test the snap directly (you need to restart your session though to have the change taking into effect)
[09:02] <ubot5-ng> ubuntu bug (Pull request) 3 in communitheme-snap-helpers "Ensure GTK2 application are themed" (comments: 1) [Open]
[09:08] <oSoMoN> didrocks, sure, testing now
[09:10] <oSoMoN> didrocks, that fixes the theming of gtk2 apps, very nice!
[09:11] <oSoMoN> I'll comment on the PR
[09:12] <didrocks> thanks!
[09:13] <didrocks> so, only 2 issues remain :)
[09:13] <didrocks> for those interested: https://github.com/ubuntu/gtk-communitheme/issues/325#issuecomment-380383969
[09:13] <ubot5-ng> ubuntu bug 325 in gtk-communitheme "Evince has a totally invisible gui with the snap theme" (comments: 7) [Bug, Confirmed, Open] - Assigned to didrocks (Didier Roche)
[09:13] <ubot5`> Ubuntu bug 325 in seahorse (Ubuntu) "no icon" [Medium,Invalid] https://launchpad.net/bugs/325
[09:13] <didrocks> I'll fix evince directly (opening a bug, and such), for the snaps, I'll need to talk to jdstrand
[09:16] <didrocks> well, it's going to be in abstractions/gnome for the proper fix, so, I'll need to talk there to jdstrand as well for evince :)
[09:20] <willcooke> Weee.  I'm on the new train direct to Blackfrirars!
[09:21] <willcooke> duflu, I have an xwayland crash file, do I just attach it?
[09:21] <duflu> willcooke, no, please run ubuntu-bug
[09:21] <willcooke> (on mobile data, might lag/drop out)
[09:21] <willcooke> kk
[09:21] <duflu> We can't retrace them by hand
[09:23] <duflu> What's new about the new train?
[09:24] <willcooke> LP:#1754693 looks like the same bug but I'll log this one anyway, just in case
[09:25] <willcooke> It's a brand new route which goes pretty much door-to-door for me.  They reused some old tunnels under kings cross to link two lines and the new service started last week.  Brand new trains too
[09:27] <willcooke> duflu, lp: #1762971
[09:27] <ubot5`> Launchpad bug 1762971 in xorg-server (Ubuntu) "Running classic snaps crashes wayland session" [Undecided,New] https://launchpad.net/bugs/1762971
[09:28] <duflu> willcooke, That's interesting. It's crashed in swrast. Did you notice slow rendering or high CPU?
[09:28] <duflu> Or is it a VM?
[09:28] <willcooke> It's a real machine
[09:28] <willcooke> I'll crash it again and see if I hear fans spin up
[09:29] <duflu> I've been ignoring all xorg* crashes because my inbox and mornings are overloaded already. I wonder if this is a common one
[09:31] <willcooke> Nothing too unusual.  skype used some cpu, then it froze, then apport used some cpu and then it locked up
[09:31] <willcooke> then it restarted
[09:31] <duflu> willcooke, it's the Xwayland process supposedly using software rendering
[09:32] <willcooke> now I cant get to my ttys
[09:35] <duflu> willcooke, need to wait for the retrace
[09:38] <duflu> willcooke, yeah I think bug 1754693 is indeed the same. So good news: It's not using swrast -- that's just wrong when you're lacking debug symbols
[09:38] <ubot5`> Error: Launchpad bug 1754693 could not be found
[09:40] <duflu> Maybe https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca
[09:41] <seb128> duflu, it's easy to retrace locally or to download the coredump and use gdb on it on another bionic/amd64 system
[09:41] <duflu> Yeah, if the symbols match
[09:41] <seb128> if the machines are bionic update they use the same binaries, it usually works
[09:42] <seb128> tjaalton, ^ is that bug known by you?
[09:47] <duflu> I can't find any other instances other than those mentioned above
[09:48] <seb128> well it's bionic, not our default session, and some specific snaps
[09:48] <seb128> so not a surprised not that of a common combo
[09:52] <seb128> chrisccoulson, I guess you know that tb is older in bionic that in other pockets?
[09:53] <LocutusOfBorg> hurray for glib2!
[09:53] <LocutusOfBorg> but...       + cherry-pick per-desktop overrides from GNOME #786496
[09:53] <LocutusOfBorg>         Allison confirmed the patches will be committed to glib soon
[09:53] <ubot5`> Gnome bug 786496 in general "Replace custom override schema with per-desktop override" [Normal,New] http://bugzilla.gnome.org/show_bug.cgi?id=786496
[09:53] <ubot5-ng> bugzilla.gnome.org bug 786496 in general "Replace custom override schema with per-desktop override" [Normal, New] - Assigned to gnome-shell-maint
[09:53] <ubot5`> bug 786496 in Redshift "Redshift don't work with Dual Screen on Linux" [Undecided,Fix released] https://launchpad.net/bugs/786496
[09:53] <LocutusOfBorg> are we sure this is still the case?
[09:53] <LocutusOfBorg> I don't see much activity on upstream tracker
[09:53] <seb128> I doubt it's still the case, he just copied the old changelog entry
[09:54] <LocutusOfBorg> what about a prod in upstream tracker?
[09:54] <LocutusOfBorg> or merging in Debian the patch, so we go back in sync...
[09:56]  * willcooke prepares to enter the new tunnels.  They're probably haunted.
[10:01] <Laney> LocutusOfBorg: There is no way those patches are going into Debian, they need to come via upstream
[10:02] <seb128> LocutusOfBorg, the bug tracker is open, you can try nagging
[10:02] <seb128> Allison is not likely going to land those, she stopped working on glib afaik
[10:02] <Mirv> jbicha: yes to shotwell 0.28.2, landing via a ticket
[10:02] <seb128> but other maintainers might be wanting to review/land it
[10:04] <Laney> our team should still have an interest in seeing those patches merged imo
[10:05] <seb128> I think it does have one
[10:05] <seb128> but we have little leverage over upstream there
[10:05] <seb128> you are probably the person in the team who did the most glib upstream contributions, I don't think we have annoying on the path to be comaintainer
[10:06] <seb128> annoying->anyone
[10:10] <Laney> it was my impression that di_drocks was in charge of making sure they went upstream in the end
[10:10] <seb128> well, there is only so much he/we can do :/ j_bicha tried to nag earlier in the cycle and got ignored
[10:11] <seb128> if you have idea/suggestions on what else we can try I'm happy to get some
[10:11] <Laney> ask Phillip
[10:11] <seb128> I guess we can try pinging again, doesn't hurt (unless people get annoyed to be nagged too much)
[10:16] <Laney> I'll have a word with him
[10:17] <seb128> thx!
[10:23] <duflu> Heh. Now I'm bisecting software and hardware to find a bug
[10:23] <duflu> that's new
[10:25] <seb128> how does that work?
[10:26] <mgedmin> first you draw a line in chalk around the middle of your laptop, then you get a big axe ...
[10:27] <duflu> seb128, I think it will involve moving my HDD from the new desktop back into the old one
[10:27] <seb128> ah
[10:27] <seb128> mgedmin, :)
[10:31] <duflu> To dinner and beyond
[10:36] <seb128> willcooke, retraced confirmed your xwayland issue is bug #1754693
[10:36] <ubot5`> bug 1754693 in xorg-server (Ubuntu) "Xwayland crashed with SIGABRT in st_renderbuffer_delete()" [High,Confirmed] https://launchpad.net/bugs/1754693
[10:47] <jbicha> I think one problem was that I asked about the glib patches too late in the GNOME release cycle. Since their cycle just started now, it's a better time
[10:47] <jbicha> good morning
[10:47] <seb128> hey jbicha
[10:48] <seb128> well they could have reviewed or replied "looks good but better for next cycle"
[10:48] <seb128> rather than just ignoring it
[10:51] <Mirv> jbicha: shotwell 0.28.2 in unapproved queue now
[10:51] <jbicha> thanks :)
[10:55] <willcooke> thanks seb128
[11:34] <GunnarHj> Hi Laney, aren't those options in e.g. dh_strip predefined somehow in the Debian packaging system? We'd need a custom option. (Struggled with it the other day without success.)
[11:36] <GunnarHj> Laney: If you know what it would look like in init(), I'd need some handholding for that part.
[11:39] <Laney> GunnarHj: laney@nightingale> ~/temp/pkgbinarymangler-136/dh_translations --domain=foo
[11:39] <Laney> domain is foo
[11:39] <Laney> https://paste.debian.net/1019708/
[11:41] <GunnarHj> Laney: Thanks! I'll give that a try. (Tonight or tomorrow.)
[12:23] <oSoMoN> kenvandine, hey, can you retry https://launchpad.net/ubuntu/+source/libreoffice/1:6.0.3-0ubuntu1/+build/14746085 ? that looks like a flaky test (it failed once in my PPA build, too)
[12:27] <seb128> oSoMoN, is that ok if somebody else retry? :)
[12:30] <seb128> oSoMoN, I assumed it was and did click the button
[12:31] <oSoMoN> seb128, thanks :)
[12:31] <seb128> yw!
[12:59] <jdstrand> didrocks: hey, can you create a forum topic for https://bugs.launchpad.net/bugs/1762993. the requested change is simple but it goes against the snapd design. I think it is going to need some justification and discussion (with a possibly different outcome) with the snapd team
[12:59] <ubot5`> Ubuntu bug 1762993 in snapd (Ubuntu) "snaps can't load communitheme theme" [Undecided,New]
[13:13] <willcooke> seb128, do you know if I have to have fingerprint hardware to get some UI to appear in settings for configuring fingerprints?
[13:13] <willcooke> or Trevinho if you're around ^
[13:14] <tjaalton> seb128: oops, missed your ping.. no, it's not
[13:31] <kenvandine> seb128, did you get a chance to test that gedit snap i sent?
[13:40] <didrocks> jdstrand: I'll open one, have you looked at the apparmor one for evince by any chance?
[13:41] <andyrock> seb128: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1761841/comments/3
[13:41] <ubot5`> Ubuntu bug 1761841 in update-notifier (Ubuntu) "[UIFe] Notification for livepatch are not shown." [Medium,In progress]
[13:41] <andyrock> I was thinking about the same
[13:43] <youpi> hello, on launchpad I have pushed a branch containing a commit that --fixes lp:1234 , is that enough or should I also click "Propose for merging" explicitly?
[13:50] <jdstrand> didrocks: I saw it. I don't have any objections. going to swing back around to it later
[13:51] <didrocks> jdstrand: thanks! FYI, I just had a testrun installing the package in a VM and everything works as expected
[13:51] <jdstrand> cool
[13:53] <kenvandine> didrocks, can you respond to https://github.com/ubuntu/snapcraft-desktop-helpers/issues/107
[13:53] <ubot5-ng> ubuntu bug 107 in snapcraft-desktop-helpers "GDM screen did not change" (comments: 0) [Open]
[13:53] <ubot5`> Ubuntu bug 107 in Baz (deprecated) "Please enhance baz changelog to support additive changelogs" [Medium,Invalid] https://launchpad.net/bugs/107
[13:54] <kenvandine> didrocks, i'm assuming that's because he's not on 18.04
[13:54] <didrocks> kenvandine: no, it's expected. It's not because one user is changing his theme that it will change gdm one
[13:55] <didrocks> so, basically, the instructions is the same than going to vanilla one
[13:55] <didrocks> I'll answer there and ask for some help updating the general instructions :)
[13:55] <kenvandine> thx
[13:58] <didrocks> mvo: jdstrand: https://forum.snapcraft.io/t/snap-using-themes-in-other-snaps/4946 FYI, tell me what you think
[14:08] <seb128> youpi, you need to propose for merging, referencing to a bug is only going to make the bug mention the branch but not list it as proposed for merging/needing a review
[14:10] <seb128> andyrock, good point but some UIs display need to display the NoDisplay item, e.g the gnome-control-center notifications panel to let you turn off the livepatch notifications if you want
[14:10] <seb128> andyrock, unsure we did the required work for livepatch to be listed there yet, but if we didn't we should (I think it's a key to add to the .desktop)
[14:12] <youpi> seb128: ok, thanks
[14:13] <seb128> kenvandine, I though it was not needed since when I said I didn't manage to test yet you said you did it and it was translated fine, which I though validated the testing
[14:13] <seb128> willcooke, I would expect you do need to hwd yes
[14:14] <willcooke> thx seb128
[14:16] <seb128> willcooke, yw!
[14:16] <didrocks> doko: I think we only need a finale ack on bug #1759540
[14:16] <ubot5`> bug 1759540 in ubuntu-report (Ubuntu) "[MIR] ubuntu-report: send telemetry data to ubuntu server" [Undecided,New] https://launchpad.net/bugs/1759540
[14:17] <didrocks> g-i-s is acked on my side (and this is the dep)
[14:17] <kenvandine> seb128, that's ok, i was hoping for a review to go with it :)
[14:18] <kenvandine> https://github.com/ubuntu/snapcraft-desktop-helpers/pull/106
[14:18] <ubot5-ng> ubuntu bug (Pull request) 106 in snapcraft-desktop-helpers "LD_PRELOAD bindtextdomain to load translations from multiple paths" (comments: 0) [Open]
[14:18] <seb128> kenvandine, I had it to my list, probably for tomorrow at this point though
[14:18] <kenvandine> cool, thx!
[14:18] <seb128> yw!
[14:23] <Trevinho> morning
[14:23] <kenvandine> hey Trevinho!
[14:23] <seb128> willcooke, https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/panels/user-accounts/um-user-panel.c#L858
[14:24] <Trevinho> hey kenvandine
[14:24] <seb128> good morning Trevinho
[14:24] <Trevinho> willcooke: you need to have hardware, but... you can fake it
[14:24] <Trevinho> willcooke: however I think you do have hardware
[14:24] <Trevinho> don't you  have a *60 gen thinkpad?
[14:24] <Trevinho> hi seb128
[14:24] <Trevinho> how are you?
[14:25] <seb128> Trevinho, having a rather annoying cold, I keep using tissues and my nose is blocked :/ but ok otherwise
[14:25] <seb128> Trevinho, you?
[14:25] <Trevinho> seb128: oh, so bad.... you should go a bit more in tropical countries :-D
[14:25] <willcooke> Trevinho, using a new machine I borrowed from OEM
[14:25] <Trevinho> seb128: allright
[14:26] <Trevinho> willcooke: ah, as I think in your x260 (isn't that yours?) you could use the driver I did
[14:26] <willcooke> Trevinho, yeah OEM have asked me to show them what the UI looks like, on this $OEM laptop without a fingerprint reader
[14:26] <willcooke> :)
[14:26] <willcooke> no biggy
[14:26] <willcooke> it can wait
[14:27] <willcooke> I'm sat with the guys here, so thought I would show them
[14:27] <willcooke> andyrock, https://usercontent.irccloud-cdn.com/file/NvbrIW3B/image.png
[14:27] <Trevinho> willcooke: mh, I can create a fake driver for fprintd that work by, for example, using a combination
[14:27] <Trevinho> I did like that but it was hacky and I've trashed it
[14:27] <willcooke> andyrock, via jamiebennett.  Seems to have translated itself in to German?!
[14:28] <willcooke> Trevinho, meh, dont worry about it
[14:54] <andyrock> willcooke: I guess it's a problem in translations
[14:54] <andyrock> mmm
[14:54] <andyrock> not sure what's happening tbh
[14:59] <willcooke> it's german on my machine as well :)
[15:00] <Laney> the en_GB translations have german in them
[15:00] <Laney> msgunfmt /usr/share/locale-langpack/en_GB/LC_MESSAGES/software-properties.mo
[15:02] <dupondje> FYI: https://gitlab.gnome.org/GNOME/mutter/merge_requests/75 this fixes black screens/wayland crashes with dual screen setups :) So it will be in 3.28.1 :)
[15:02] <ubot5-ng> GNOME bug (Merge request) 75 in mutter "native: Disable the use of KMS modifiers by default" (comments: 0) [Merged]
[15:05] <Laney> they look fixed though https://translations.launchpad.net/ubuntu/bionic/+source/software-properties/+pots/software-properties/en_GB/+translate?batch=10&show=all&search=Sign+In so probably the next langpack update will sort it out
[15:31] <andyrock> Laney: thx!
[15:49] <willcooke> didrocks, I've installed tweak tool for reasons, and I notice that the ubuntu-dock and ubuntu-indicators extensions are marked as off.  Is that known/a real problem?
[15:50] <didrocks> willcooke: it's known (and it's the case since the beginning)
[15:50] <didrocks> basically every extension that is part of a mode is off
[15:50] <didrocks> my long long proposal and patches for GNOME Shell fixes it
[15:50] <didrocks> but no review since october and weekly pings…
[15:50] <didrocks> (and multiple resubmit on gitlab and such)
[15:51] <didrocks> willcooke: that's https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/1
[15:51] <ubot5-ng> GNOME bug (Merge request) 1 in gnome-shell "Better mode extension support: status sync and disabling." (comments: 0) [Opened]
[15:51] <didrocks> and I had patches for Tweaks, chrome shell to use the new API
[15:51] <didrocks> (the chrome extension)
[15:51] <didrocks> they are all waiting on G-S though ^
[15:52] <willcooke> thanks didrocks
[15:53] <didrocks> yw, sad this isn't properly reviewed :(
[15:53] <willcooke> if you've got join messages on, that guys gonna have a fun time in this channel :) ^
[15:53] <willcooke> looks like they saw wisdom
[16:41] <tkamppeter> Laney, hi
[16:42] <Laney> hi tkamppeter
[16:42] <tkamppeter> It seems that Poppler hangs on a test chain which ends up in old and unmmaintained pstotext which is needed by dhelp to display the RFCs.
[16:44] <tkamppeter> Laney, I have tried to follow the hint of the Ghostscript warning, patching pstotext to use "-dREALLYDELAYBIND", but Ghostscript fails with it.
[16:45] <tkamppeter> Seems that the Ghostscript guys have already pulled out this feature and forgot to remove this workaround.
[16:45] <Laney> I guess that it doesn't require much maintenance since it worked up until recently
[16:45] <Laney> Proabably pstotext needs fixing to not use this removed feature
[16:46] <tkamppeter> The removal looks complicated as there are PostScript files which contain DELAYBIND.
[16:48] <tkamppeter> Laney, OCR written in PostScript and this uses DELAYBIND.
[16:49] <Laney> I mean if it's needed then this is a ghostscript bug after all isn't it
[16:49] <Laney> Back in a bit
[16:50] <tkamppeter> Laney, probably then I better look into patching DELAYBIND support back into Ghostscript and reporting a bug on dhelp upstream to prepare for removal of DELAYBIND.
[17:52] <willcooke> night all
[18:50] <Laney> tkamppeter: I was a little bit confused since just echo | pstotext fails
[18:51] <Laney> that's a blank ps file which probably doesn't have this DELAYBIND thing in it
[19:00] <tkamppeter> Laney, pstotext is partially written in PostScript, it runs ghostscript with PS files which come with pstotext, these contain DELAYBIND.
[19:01] <tkamppeter> I already contacted Ghostscript upstream on that. the DELAYBIND deprecation was actually taken back in 9.23 and the gs guy told me with which patch it was done.
[19:02] <tkamppeter> Laney, I backported that patch and as the return of DELAYBIND is incompatible with -dSAFER I patched the -dSAFER out of pstotext.
[19:02] <tkamppeter> But now I get another error (https://paste.ubuntu.com/p/j7TMTfM7wd/), showed it to the gs guy and he said:
[19:03] <tkamppeter> I really feel that holding onto backwards compatibiility with a utility last updated 14 years ago isn't always going to be in our best interests......
[19:04] <tkamppeter> As I do not know programming in PostScript I do not know how to fix pstotext.
[19:05] <tkamppeter> Laney, I wonder why the upload of Poppler triggers the test of a documentation-only package. Does Poppler depend on this package which provides all RFCs? Does Poppler need this?
[19:06] <tkamppeter> Laney I also wonder why the failure only occurs now, I have updated gs to 9.22 two months ago.
[19:09] <Laney> tkamppeter: doc-rfc depends on poppler, thus triggers its tests which use pstotext
[19:09] <Laney> apparently it doesn't depend on ghostscript directly otherwise it would have been triggered then
[19:10] <Laney> and sorry that we have to maintain ancient stuff; that's the way of distros sometimes
[19:10] <Laney> There is a proper way to get it removed - analyse everything that uses it and make it stop doing that one way or another
[19:17] <tkamppeter> Laney, pstotext is probably missing an autopkgtest, otherwise Ghostscript had triggered it in the first place.
[19:18] <tkamppeter> Laney, I have no real idea how to fix that without causing a big impact on the LTS.
[19:19] <tkamppeter> Laney, stepping back to gs 9.21, reintroducing its bugs and removing 9.22s new features is bad in that stage of an LTS, also creates an ugly epoch.
[19:21] <tkamppeter> Laney, Writing a wrapper script named pstotext around (well-maintained) filters of the cups-filters package resembling the command line of the original pstotext could cause problems as the output will for sure not be the same.
[19:44] <tkamppeter> Laney, pstotext is only used by dhelp, by nothing else.
[20:05] <ximion> jbicha: since I can't upload to Ubuntu, would you upload the appstream package, now that the FFE is approved?
[20:07] <jbicha> ximion: could you go to https://launchpad.net/~ximion/+archive/ubuntu/appstream/+edit enable all architectures and then do a test rebuild as requested?
[20:07] <ximion> I did, but it doesn't automatically rebuild stuff in the PPA
[20:07] <jbicha> right, you need to do a new upload
[20:07] <ximion> I'll do a no-change upload later to trigger new builds
[20:07] <jbicha> thanks
[20:07] <jbicha> I'm just trying to keep the Release Team happy :)
[20:09] <jbicha> does asgen need to be the same version?
[20:10] <tkamppeter> Laney, my suggestion is to patch dhelp to use Ghostscript's ps2txt and to modify the autopkgtest of doc-rfc to use ps2txt instead of pstotext then, too. The the need of pstotext in the whole distro is eliminated and pstotext can get removed.
[20:13] <tkamppeter> Laney, doc-rfc and dhelp need to depend on Ghostscript and not on pstotext any more.