[07:37] <Saviq> elopio, hey, I
[07:37] <Saviq> 've had to tweak the dash emulators a bit in https://code.launchpad.net/~saviq/unity8/drop-filtergrid/+merge/226336
[07:37] <Saviq> elopio, can I please ask you for a sanity check?
[08:34] <Saviq> mhr3, in case you're interested: https://code.launchpad.net/~saviq/unity8/drop-filtergrid/+merge/226415
[08:34] <Saviq> mhr3, I'll do the prelim see all/less and header links now
[08:35] <Saviq> but I've implemented collapsed-rows: 0 there
[08:35] <Saviq> and forceful expansion of single-category scope pags
[08:43] <mzanetti> oh... no more filtergrid :)
[08:52] <Saviq> mzanetti, yeah, we're letting the views do their job for maintaining delegates
[08:53] <Saviq> mzanetti, not sure why we decided otherwise before
[09:06] <mhr3> Saviq, hmm, feel like that cute dog again :/
[09:07] <mhr3> Saviq, i do like the diff stats though ;)
[09:09] <Saviq> mhr3, yeah, so, FilterGrid was something that actually applied a proxy model that limited the number of items in the model
[09:10] <Saviq> mhr3, to collapse it
[09:10] <Saviq> mhr3, but that was stoopid, since *Views just manage delegates themselves if they're out of view
[09:12] <mhr3> sounds simple when you put it that way
[09:12] <mhr3> but looking at the code, it doesn't :)
[09:13] <Saviq> mhr3, all in all, grid/journal/carousel just say "I'm yay high, but if you want to collapse me, then it's foo"
[09:13] <Saviq> mhr3, and GenericScopeView decides when to collapse
[09:14] <Saviq> mhr3, before it was the views themselves doing the expand/collapse (as you saw in your branch, the setFilter() branch that got replaced with grow()/shrink())
[09:17] <mhr3> yeah, all makes sense, i guess it's just that refactoring diffs aren't that easy to read when you're not familiar with all the relevant components
[09:22] <Saviq> mhr3, indeed
[10:18] <seb128> Saviq, bregma: is there a known slowness issue currently on untiy8 desktop? I just installed the daily and going back to the dash or opening an indicator is hanging for like 30 seconds before doing anything
[10:23] <Saviq> seb128, I'd suspect bug #1340086
[10:26] <seb128> Saviq, could be, thanks
[10:27] <Saviq> seb128, I tried pinging boiko and tiagosh about it, but never got a reply
[10:28] <seb128> Saviq, tried as well, let's see
[10:28] <Saviq> seb128, a "workaround" is to get an ofono account on your desktop, I'm not clear on how to do that, though..
[10:31] <tsdgeos> Saviq: so "All" includes "Favorites", i understand in a non favorite "All" scope we have to show the back button to go back, what about a favorite scope that we press in "All"?
[10:31] <tsdgeos> go back to regular dash? or show with the "back" button too?
[10:31] <tsdgeos> i think back button is more predicatble
[10:32] <Saviq> tsdgeos, current design is that you always go back to dash for favourites
[10:32] <tsdgeos> Saviq: even if it's in "ALl"?
[10:32] <tsdgeos> where does it say that?
[10:34] <Saviq> tsdgeos, I might have extrapolated from the comments on https://sites.google.com/a/canonical.com/unity8dash/scopes/dash-overview
[10:35] <Saviq> mikenagle, hey, just realized one thing... if bottom swipe is always meant to bring the overview, we can't open non-favourites above the overview, 'cause then if you bottom-swipe you open another overview... and then another scope, and another overview...
[10:35] <Saviq> tsdgeos, I did ask for that case transition there, never got it though
[10:35] <tsdgeos> the comments section kind of contradicts the main text too
[10:36] <tsdgeos> main text says bottom edge is disabled in "Installed, non favourite scopes opened from the overview screen"
[10:36] <tsdgeos> but then comments say "If they open it from a non favourite, installed scope, they go to the All view."
[10:36] <tsdgeos> i think i like first more
[10:37] <Saviq> tsdgeos, indeed
[10:37] <Saviq> tsdgeos, sounds like comments were earlier than the text at the top
[10:37] <Saviq> tsdgeos, text at top takes precedence of course
[10:38] <Saviq> tsdgeos, btw... not translucent here https://f966f709-a-c881af26-s-sites.googlegroups.com/a/canonical.com/unity8dash/scopes/dash-overview/01_Dash_scopes_nav_full_dark_v7.jpg?attachauth=ANoY7cpwbv7LCcNXKBgQbQooqmxRSUza5vfcPmdnUNhREphFeP9I0Ol_6CkNw5ixwLtTQxvRaJLA3nILmOGgancNaxrIfUkqoye7EgvQJFFTkCABUMCHUAXIAYMQsHaRGoLB17rIBiZ_pEfWL5hr1StfEhTegTWTUnNEx_HIFPORU236CtMZv7XQkt5tL1EOoXdimjnJsfvnC8_wif1IMvigB9WYnR_ZYzcY0qTEODhpwfvHxOctqZnhLsmbf08LMdhR7z9jwXv4YZ
[10:38] <Saviq> PLu9qqARglEYFYw42tLw%3D%3D&attredirects=0 :|
[10:39] <tsdgeos> well
[10:39] <tsdgeos> they can decide what they want
[10:39] <tsdgeos> that's the easy fi
[10:39] <tsdgeos> x
[10:39] <Saviq> yup
[10:44] <mhr3> Saviq, anyone working on the 30second hang?
[10:44] <Saviq> mzanetti, bug #1340632, sounds like live: true isn't good :|
[10:44] <mzanetti> Saviq: not sure if its related yet
[10:44] <Saviq> mhr3, I couldn't get through to boiko or tiagosh :|
[10:48] <MacSlow> What changed in the way unity8 is started (on the desktop)? The shell-UI does no come up anymore and all of a sudden I get is this output on stdout: http://pastebin.ubuntu.com/7779635
[10:53] <mzanetti> Saviq: ok... have 9 apps running now... the launcher doesn't get any more jumpy than the rest of the ui
[10:53] <Saviq> mzanetti, 9 apps *running*
[10:54] <mzanetti> Saviq: ok... have 9 apps recent now... the launcher doesn't get any more jumpy than the rest of the ui
[10:54] <Saviq> mzanetti, I misread the bug probably then
[10:54] <mzanetti> :P
[10:54] <Saviq> mzanetti, so yeah, I think we have a "shell gets slow with many apps open" bug already
[10:54] <mzanetti> yep
[10:54] <mzanetti> well, let me ask back to confirm
[10:55] <mzanetti> I'll handle that bug
[11:02] <Saviq> mzanetti, oh and it was a qtcomp bug...
[11:02]  * Saviq shuts up
[11:02] <mzanetti> Saviq: :)
[11:02] <mzanetti> no worries
[11:02] <Saviq> you probably don't even have live: true in there yet ;)
[11:02] <mzanetti> Saviq: if its landed in trunk we do. We're up to date with trunk atm
[11:02] <Saviq> k
[11:06] <tsdgeos> Saviq: i'm unsure how i'm supposed to find out which "all" scope is each, i mean they are cards, how do i get to know which scope they represent?
[11:07] <Saviq> tsdgeos, probably from uri
[11:07] <Saviq> mhr3, ↑?
[11:07] <tsdgeos> Saviq: mhr3: so we make uri return the scope_id?
[11:07] <Saviq> tsdgeos, rather a canned query
[11:07] <tsdgeos> ?¿
[11:07] <mhr3> yea, it already is
[11:07] <Saviq> tsdgeos, from which we need to take scope_id out
[11:08] <mhr3> but tbh it feels weird that we're using the standard scopes models for the super-special scopes overview
[11:09] <tsdgeos> how do i do that?  and what's a canned query (so i can create it from my fake scope)?
[11:09] <mhr3> tsdgeos, it's scope://[scope_id]?q=query_string&whatev
[11:10] <Saviq> tsdgeos, truth be told, can you not find out from openScope() / gotoScope()?
[11:10] <Saviq> not good
[11:11] <Saviq> tsdgeos, you here?
[11:11] <Saviq> mhr3, TBH I wonder if we should not get rid of openScope / gotoScope, and let the shell open the scope and pass the query to it
[11:11] <tsdgeos> i am
[11:12] <Saviq> mhr3, the "I activate, you come back with a scope" approach mechanism feels shaky
[11:12] <mhr3> Saviq, it's not just the query though, it's department id, filters state, whatever metadata
[11:13] <tsdgeos> Saviq: so you're suggesting i just call activate and the scope will emit gotoscope?
[11:13] <Saviq> mhr3, isn't canned query supposed to have all that?
[11:14] <mhr3> Saviq, yes, sure
[11:14] <Saviq> tsdgeos, for now, yes
[11:14] <Saviq> mhr3, dash will have to become a handler for scope:/// anyway
[11:15] <Saviq> mhr3, you already added processQuery()
[11:15] <tsdgeos> Saviq: damn, this means i have to implement all that in the fake plugin scope :D
[11:15] <Saviq> tsdgeos, or convince mhr3 to what I'm saying above ;)
[11:15] <mhr3> Saviq, true
[11:15] <mhr3> so far i'm not convinced either way
[11:15] <mhr3> give me a reason why is it a good idea
[11:16] <Saviq> mhr3, I feel it's a bit unexpected for us to activate and then get back a scope
[11:16] <Saviq> mhr3, the dash knows about scopes, it should handle them itself
[11:16] <Saviq> mhr3, so it can prepare
[11:16] <Saviq> mhr3, otherwise we'll have to give you the query just so that you pass it back up to us (in the form of a scope)
[11:18] <tsdgeos> honestly in this case i'd just like to have a scope_id i can use
[11:18] <tsdgeos> the only thing i'm going to do is open the scope
[11:18] <mhr3> Saviq, feels like you assume you always know the canned query up front
[11:18] <mhr3> but what if you don't
[11:18] <Saviq> mhr3, when don't I?
[11:18] <mhr3> activating preview action perhaps?
[11:19] <Saviq> mhr3, you can come back to me with "open canned query"
[11:19] <Saviq> and pass the query back
[11:19] <Saviq> mhr3, even easier for you, it can come through url dispatcher
[11:19] <Saviq> mhr3, but really, the button should just come with the canned query
[11:19] <mhr3> true
[11:20] <mhr3> Saviq, but tbh i don't see much of a difference really, if i give you just uris all the time you will anyway have to go and ask something - give me a scope object for this
[11:21] <tsdgeos> ok
[11:21] <Saviq> mhr3, sure, but I will expect it
[11:21] <tsdgeos> let's not change stuff for the moment
[11:21] <tsdgeos> let's do the activate + openscope
[11:21] <Saviq> tsdgeos, yeah, I agree let's go with what we have now
[11:22] <mhr3> Saviq, so it's previews all over again? :)
[11:22] <Saviq> mhr3, anyway, I will need the case where I get the query and you don't know anyway, through url-dispatcher
[11:22] <Saviq> mhr3, what about previews?/
[11:22] <mhr3> Saviq, reminded me of the switch from "maybe you'll get a preview back, maybe not"
[11:23] <mhr3> to.. whatever we have now :)
[11:23] <Saviq> mhr3, yeah exactly ;)
[11:23] <mhr3> Saviq, bottomline, i'm fine if you want it changed, not much of a difference from my pov
[11:24] <Saviq> mhr3, I think there's one important thing that might happen
[11:24] <greyback> Saviq: hey dude, seen bug 1340412 ?
[11:25] <Saviq> greyback, ouch
[11:25] <Saviq> mhr3, is that when there's a canned query for a favourite, I don't think we'll be going back to the dash with it
[11:26] <Saviq> mhr3, at which point you'd in the plugin suddenly have to know where the query came from
[11:26] <Saviq> which I don't think you want to
[11:26] <greyback> Saviq: it was fine about 10 days ago, I don't think I've updated manta since
[11:27] <Saviq> greyback, we'll have to bisect images
[11:27] <Saviq> I
[11:27] <Saviq> 'll try and get some time for it somewhen
[11:28] <mhr3> Saviq, right, as i said, can change, give me new api, can implement it
[11:28] <Saviq> mhr3, k
[11:28] <greyback> Saviq: ta
[11:29] <Saviq> mzanetti, would you have some time to review https://code.launchpad.net/~saviq/unity8/drop-filtergrid/+merge/226415 ?
[11:31] <mhr3> gawd
[11:31] <mhr3> miso      2179  1.5  0.0      0     0 ?        Zsl  11:43   0:43 [unity8] <defunct>
[11:31] <mhr3> started by upstart ^^
[11:31] <mhr3> what's one thing that init daemon is supposed to do?
[11:31] <mhr3> can't be collecting zombies right?
[11:32] <mzanetti> Saviq: yes
[11:32] <MacSlow> Saviq, in the latest jenkins-run of the unity8-combo-button-support branch all notification-related qml- and AP-tests pass... only the unrelated testDashContent fails (https://code.launchpad.net/~macslow/unity8/combo-button-support/+merge/221499)
[11:33] <mhr3> one thing it does do well, is crashing your session if things go wrong
[11:33] <MacSlow> Saviq, I really don't know what more I can do to get it past jenkins
[11:35] <Saviq> MacSlow, "Segmentation fault"
[11:35] <Saviq> MacSlow, qmltestrunner segfaults on you
[11:35] <Saviq> MacSlow, but it's obviously not your fault
[11:35] <Saviq> MacSlow, so it's ok, we'll have to spend some time to fix DashContent outside
[11:36] <MacSlow> Saviq, ok
[11:36] <Saviq> MacSlow, I'll kick jenkins again to see if it's actually triggered by your branch, but I rather doubt it
[11:37] <MacSlow> Saviq, btw... I can't start unity8 on the desktop anymore... not sure if you saw my earlier remark here.
[11:37] <Saviq> MacSlow, wait for it... bug #1340086
[11:37] <Saviq> MacSlow, give it 30s
[11:38] <Saviq> mzanetti, I'm adding tests, almost there, but those can be reviewed separately
[11:38] <mzanetti> ack
[11:38] <MacSlow> Saviq, I gave it several minutes... it just spewed out some errors regarding a scope on the terminal
[11:39] <Saviq> MacSlow, hmm then different
[11:40] <MacSlow> does anybody else see this on their desktop-systems... rfkill spams my kern.log with "input handler enabled/disabled" messages.
[11:40] <Saviq> mhr3, does http://pastebin.ubuntu.com/7779635/ sound like anything interesting to you?
[11:40] <Saviq> MacSlow, try "restart scope-registry" and "restart smart-scopes-proxy"
[11:41] <mhr3> Saviq, saw that somewhere already, restart session
[11:41] <Saviq> oops he just did...
[11:41] <mhr3> auto-restart by upstart iguess ^
[11:42] <Saviq> MacSlow, sounds like you lost your session, according to mhr3 that should've helped with the scopes
[11:42] <MacSlow> Saviq, indeed :)
[11:43] <mhr3> sometimes i wish there was "OMG FIX NOW" severity in lp
[11:43] <tsdgeos> Saviq: any clue what should happen when you press the "Back" button on the non favorite scope i just opened from the overview? Back to overview or dash?
[11:44] <tsdgeos> mhr3: that's what critical should be no?
[11:44] <Saviq> tsdgeos, back to overview
[11:44] <mhr3> tsdgeos, for the cases when critical is not enough :)
[11:44] <tsdgeos> Saviq: ok
[11:44] <Saviq> mhr3, you mean bug #1222705
[11:44] <mhr3> that one exactly
[11:45]  * Saviq bumps
[11:46] <MacSlow> Saviq, mhr3: phew... finally unity8 runs again.
[11:47] <Saviq> mhr3, thanks for the facepalm fix for theme inherit
[11:48] <mhr3> Saviq, lucky guess tbh :)
[11:48] <mzanetti> Saviq: so what's happening in that drop-filtergrid branch is that you only set the height of the normal grid and let the cacheBuffer work, right?
[11:49] <Saviq> mzanetti, yes, we're letting the views do delegate handling
[11:49] <mzanetti> Saviq: which also means that we have more delegates in memory now thought
[11:49] <Saviq> mzanetti, right now result is we're actually creating more (since cacheBuffer is > 0 by default)
[11:49] <mzanetti> Saviq: not saying this is necessarily bad
[11:49] <Saviq> mzanetti, but we can tweak that
[11:49] <mzanetti> but yeah, its changed
[11:50] <Saviq> mzanetti, is why I needed to update autopilot
[11:50] <Saviq> mzanetti, but I think that's fine
[11:50] <Saviq> mzanetti, it should help expansion if the first row of items is created already
[11:50] <mzanetti> I don't really see a big problem either... just wanted to have that discussion...
[11:50] <mzanetti> so yeah, we might want to experiment a bit with the cacheBuffer here still
[11:51] <davmor2> mhr3: there is,  It's called "Is it nearly fixed yet bot" you trigger it with !bug_123456_is_it_nearly_fixed_yet mhr3 and it will ping you every minute till the bug say fix committed :)  you just need to make the bot :D
[11:51] <Saviq> mzanetti, truth be told we might set it to 0
[11:51] <mzanetti> that would match previous behavior, yes
[11:51] <Saviq> mzanetti, not exactly
[11:51] <Saviq> mzanetti, another row still will get created
[11:52] <mhr3> davmor2, uuuuh... i want that bot now :)
[11:52] <mzanetti> Saviq: right... even 0 creates 1 row...
[11:52] <mzanetti> Saviq: I vote for setting it to 0 then
[11:52] <Saviq> mzanetti, k, doing
[11:53] <Saviq> oh no cacheBuffer on VJ
[13:22] <elopio> tsdgeos: I solved the conflicts on my unity branches, and all the tests I touched are now passing.
[13:22] <elopio> can you take another look please?
[13:23] <tsdgeos> i'll try to find time
[13:23] <tsdgeos> tbh all i did was check if it merged or not
[13:26] <Saviq> tsdgeos, focus on the overview, we'll handle this
[13:27] <tsdgeos> ok
[13:28] <Saviq> MacSlow, see, it passed now ;)
[13:28]  * MacSlow does the happy-wiggle-dance
[13:45] <tsdgeos> Saviq: "Long press: Opens scope preview (normal theme)" in the "all" part
[13:46] <tsdgeos> does it replace everything (including the header and the done) ?
[13:46] <tsdgeos> also the normal theme is going to look weird
[13:46] <tsdgeos> i guess yes for the first
[13:46] <Saviq> tsdgeos, yeah, it just slides in as usual
[13:47] <tsdgeos> sad thing it's there's no previewlist to slide in anymore
[13:47] <tsdgeos> i have to add another one :D
[13:47] <Saviq> tsdgeos, well, shouldn't there be one in the overview simply?
[13:47] <tsdgeos> sure
[13:48] <tsdgeos> but before we had one for everything
[13:48] <tsdgeos> i could be using here
[13:48] <Saviq> tsdgeos, yeah, well
[13:48] <Saviq> tsdgeos, truth be told we need a stack
[13:48] <Saviq> tsdgeos, and just push / pop as needed
[13:48] <Saviq> tsdgeos, but I don't want to implement a stack myself...
[13:48] <Saviq> but then bug #1247865 :|
[13:49] <tsdgeos> Saviq: also when it says "normal theme"
[13:49] <tsdgeos> it means "non dark"
[13:49] <tsdgeos> right?
[13:53] <Saviq> tsdgeos, yeah
[13:53] <tsdgeos> that looks really bad
[13:53] <Saviq> tsdgeos, I know ;)
[13:53] <Saviq> tsdgeos, I really disagree with all the dark → light → dark → light transitions all this causes
[13:54] <Saviq> tsdgeos, we should only go "up" to overview and back "down" out of it
[13:55] <Saviq> tsdgeos, but since they didn't explore it all visually
[13:55] <Saviq> tsdgeos, we need to show them :|
[13:55]  * tsdgeos forsees a hud
[13:55]  * tsdgeos wants to ru
[13:55] <tsdgeos> n
[13:56] <tsdgeos> running while sitting is quite hard
[14:02] <Saviq> tsdgeos, I don't think it's going to be as bad
[14:03] <Saviq> tsdgeos, I just think they will have to reconsider this and that
[14:03] <Saviq> tsdgeos, like preview in overview → in dark theme
[14:03] <Saviq> tsdgeos, opening a scope always going back "down" first
[14:05] <mhr3> tsdgeos, iirc previews shouldn't be opened from the overview
[14:05] <Saviq> mhr3, yes, for scopes
[14:05] <tsdgeos> mhr3: well you iirc wrong :D
[14:06] <Saviq> mhr3, https://sites.google.com/a/canonical.com/unity8dash/scopes/dash-overview
[14:06] <tsdgeos> or the document is outdated
[14:06] <Saviq> mhr3, "Long press: Opens scope preview (normal theme)"
[14:06] <Saviq> mhr3, in All
[14:08] <mhr3> hmm
[14:09] <mhr3> iri then i guess
[14:09] <mzanetti> Saviq: would it be possible/ok to make tryDashContent show some corner cases? For instance having one scope that has just one category (so we can see/test its not expandable and expanded by the beginning etc)
[14:09] <mhr3> I Recall Incorrectly ;)
[14:09] <Saviq> mzanetti, I pushed the test for that
[14:10] <Saviq> mzanetti, GenericScopeView::test_forced_category_expansio
[14:10] <Saviq> n
[14:10] <mzanetti> Saviq: yeah, I meant more the try thing
[14:10] <mzanetti> but ok...
[14:10] <Saviq> mzanetti, well, it's there already
[14:10] <Saviq> mzanetti, in tryDash
[14:10] <Saviq> mzanetti, and well, tryDashContent, too, it's the last scope on the right
[14:10] <mzanetti> Saviq: I don't see a scope with just one category there
[14:10] <Saviq> mzanetti, build?
[14:10] <mzanetti> hmm.
[14:10] <mzanetti> me looks again
[14:11] <mzanetti> aha... sorry for the noise
[14:11] <mzanetti> didn't rebuild after pulling indeed
[14:11] <karni> mhr3: can u haz look? http://paste.ubuntu.com/7780376/
[14:11] <karni> mhr3: this is on a precise desktop
[14:12] <mhr3> karni, first, i guess you mean trusty?
[14:12] <karni> mhr3: utopic
[14:12] <karni> mhr3: heh, sorry
[14:13] <Saviq> phablet?
[14:13]  * Saviq smells hardcoding
[14:13] <karni> no, desktop, utopic
[14:13] <karni> http://paste.ubuntu.com/7780381/
[14:13] <mhr3> karni, click related
[14:14] <karni> usually up to date every 3 days or so, I did dist-upgrade today and this happened
[14:14] <mhr3> nothing to do with scopes really
[14:14] <karni> mhr3: even though I see libunity-scopes-dev and unity-plugin-scopes ?
[14:14] <mhr3> yes
[14:19] <Saviq> mhr3, are you "unpacking" background values in customization too? like color:/// gradient:/// ?
[14:20] <mhr3> Saviq, am i unpacking them anywhere?
[14:20] <Saviq> mhr3, well, I'm getting { type: "gradient" } and stuff for the card background
[14:21] <mhr3> Saviq, aaah, right... yea, no i'm not
[14:21] <Saviq> mhr3, I agree that's not ideal...
[14:21] <Saviq> mhr3, so maybe I'll just take care of it here...
[14:24]  * Saviq is spewing branches like crazy today
[14:24] <Saviq> mhr3, https://code.launchpad.net/~saviq/unity8/initial-see-all/+merge/226469
[14:27] <mhr3> Saviq, is setting height to 0 the preferred way to hide something? i thought setting visible to false is better
[14:28] <Saviq> mhr3, doesn't work for things using childrenRect
[14:28] <karni> mhr3: coolio, purging of /opt/click.ubuntu.com/.click/users/ solved the problem
[14:28] <Saviq> mhr3, and also, gradients are children of this component, would be hidden, too
[14:28] <Saviq> mhr3, don't get me wrong, that's not ideal
[14:28] <Saviq> mhr3, that's just the least changes
[14:29] <mhr3> k
[14:29] <mhr3> karni, cool
[14:29] <tsdgeos> Saviq: the card creator doesn't know how to do cards like the ones in the overlay i just realized
[14:29] <mikenagle> saviq - you're dead right but the spec says:  Note, this interaction is disabled on:
[14:29] <mikenagle> Search screen
[14:29] <mikenagle> Preview screen
[14:29] <mikenagle> Installed, non favourite scopes opened from the overview screen
[14:29] <tsdgeos> art + title + overlay with the title centered
[14:30] <mikenagle> saviq, tsdgeos - re the overview spec - you can ignore the comments - they just reflect the conversation that got us to the spec :)
[14:31] <facundobatista> I'm not being able to create properly an emulator instance: http://pastebin.ubuntu.com/7780434/  do you have any idea where I can find logs to see what's going on? (btw, I'm in Utopic)
[14:31] <Saviq> mikenagle, still, I think you'll need to reconsider a few things, ideall with transition videos
[14:31] <Saviq> mikenagle, I really feel like having both dark (overview) and light (everything else) "elements" on the same level is going to be confusing
[14:31] <tsdgeos> mikenagle: ok
[14:31] <Saviq> mikenagle, and since you can only preview scopes in the overview, why not show them in the dark theme?
[14:32] <Saviq> tsdgeos, it does, only we can't change the overlay colour yet
[14:32] <Saviq> tsdgeos, and the "centered text" part I believe is a bug actually ;P
[14:32] <tsdgeos> erg
[14:32] <tsdgeos> ok :D
[14:33] <mikenagle> saviq - the scopes are never dark though - just the space around them is dark. Scopes themselves will be any colour the author/brand needs
[14:33] <mikenagle> saviq (of course a dark branded scope will be dark but you know what I mean :))
[14:33] <tsdgeos> mikenagle: but you are going from "All" to "preview of scope XYZ"
[14:33] <Saviq> mikenagle, I mean that as you long-press a scope in the All category, you'll open a preview for that scope
[14:33] <tsdgeos> "all" is dark
[14:33] <tsdgeos> "preview of scope XYZ" should be dark too
[14:33] <Saviq> tsdgeos, ↑
[14:33] <Saviq> eee
[14:33] <Saviq> mikenagle, ↑↑
[14:34] <Saviq> mikenagle, preview of scope is part of the scopes scope / overview
[14:34] <Saviq> not of the dash
[14:36] <mikenagle> saviq tsdgeos. Gotcha. You might be right. Hard to say without testing. But Esti and I tihnk to keep it light for the time being at least
[14:36] <mikenagle> saviq tsdgeos. As soon as there's a build to look at though, shout and I'll take another look to check I'm not crazy :)
[14:37] <mhr3> Saviq, the see all seems too big
[14:37] <mhr3> Saviq, or its font size too small
[14:38] <Saviq> tsdgeos, something along the lines of http://pastebin.ubuntu.com/7780453/
[14:39] <tsdgeos> Saviq: yeah yeah sorry
[14:39] <tsdgeos> ignore me
[14:39] <tsdgeos> :D
[14:39] <Saviq> tsdgeos, obviously missing overlay colour
[14:39] <tsdgeos> it's just that i think we the centering is not really really centered
[14:39] <tsdgeos> looks a few pixels off
[14:40] <mhr3> Saviq, also, some weirdness - http://imgur.com/J4DT6Fn
[14:40] <tsdgeos> which actually makes sense
[14:40] <tsdgeos> as http://paste.ubuntu.com/7780461/
[14:40] <tsdgeos> has left margin and not right one
[14:40] <mhr3> Saviq, that was after expand + collapse
[14:43] <Saviq> tsdgeos, yup, that's what I thought
[14:44] <tsdgeos> Saviq: yeah adding the margin looks better now
[14:44] <Saviq> mhr3, hmm and not like that with in-header expansion?
[14:45] <Saviq> mhr3, as for sizing, I took what Joshua sent me as "redlines"
[14:46] <mhr3> Saviq, sorry? what do you mean with in-header expansion?
[14:47] <mhr3> as for sizing... ok if design said so...
[14:48] <Saviq> mhr3, that you couldn't get that weirdness before "see all"
[14:48] <Saviq> mhr3, and well, can you repro? I can't
[14:48] <mhr3> Saviq, nope haven't seen that before, but you're right i can't repro it now either
[14:49] <Saviq> shipit!
[14:49] <mterry> kgunn, Saviq: for emergency dialer, two branches need review from our side: https://code.launchpad.net/~mterry/unity8/is-active/+merge/223653 and https://code.launchpad.net/~mterry/unity8/dialer-above/+merge/224947  -- the first is ready to go, I'm fixing a merge conflict in the second right now
[14:49] <mterry> And the second needs a security pass
[14:50] <mterry> mdeslaur, ^ do you or sarnold have time to look at that dialer-above branch sometime?
[14:51] <mhr3> Saviq, btw noticed how horrible does wikipedia logo look on desktop?
[14:51] <Saviq> mhr3, yeah, on cards?
[14:52] <mhr3> Saviq, logo
[14:52] <Saviq> mhr3, so just the W, or WikipediA in the header?
[14:52] <Saviq> mhr3, in any case
[14:52] <Saviq> mhr3, prolly no sourceSize
[14:52] <kgunn> mterry: thanks for the follow up
[14:52] <Saviq> mhr3, initctl set-env -g GRID_UNIT_PX=11
[14:53] <Saviq> doesn't really help ;)
[14:53] <mterry> kgunn, my understanding is that there is a second pass from dialer side for other UI things (like adding a cancel button and going fullscreen and such)
[14:53] <mhr3> Saviq, i need to wait a minute for unity to run again :P
[14:54] <kgunn> mterry: good to know...but nothing stopping us ?
[14:54] <mterry> kgunn, which reminds me...  they'll need https://code.launchpad.net/~mterry/unity8/show-greeter-dbus/+merge/224942 for the cancel support
[14:54] <mdeslaur> mterry: sometime, yes :)
[14:54] <Saviq> mhr3, sudo rm /usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Telephony/qmldir
[14:54] <mterry> kgunn, no, their second pass doesn't stop us from doing our side
[14:55] <mhr3> Saviq, \o/ and yea still looks horrible
[14:55] <Saviq> mhr3, huh! sourceSize is set (albeit * 4 for some reason)
[14:55] <Saviq> mhr3, the icon must be something weird
[14:55] <mhr3> strangely, it's fine on the phone
[14:55] <Saviq> mhr3, told you we can't render SVGs :P
[14:56] <Saviq> mhr3, they all look rather bad
[14:57] <mhr3> wait whaat... is doesn't look good on the phone
[14:57] <mhr3> s/is/it/
[14:57] <mhr3> but i remember it looking fine
[14:59] <mhr3> Saviq, also, they're all pngs :P
[15:00] <Saviq> mhr3, oh now that's interesting
[15:00] <Saviq> mhr3, are they named @30 or something?
[15:00] <Saviq> mhr3, or are they remote?
[15:00] <mhr3> Saviq, yep, remote
[15:00] <mhr3> https://dash.ubuntu.com/imgs/logos/header-logo-wikipedia.png
[15:01] <Saviq> mhr3, that looks fine here, I thought you were asking about the ones in scopes scope
[15:01] <Saviq> well, ok, maybe not really fine, blurred a bit they are
[15:02] <mhr3> they are frickin huge!
[15:02] <mhr3> especially wiki
[15:02] <mhr3> it's not supposed to be that big
[15:03] <Saviq> mhr3, well, pad them!
[15:04] <Saviq> mhr3, how am I supposed to know how big you want them
[15:04] <Saviq> or how aligned
[15:05] <mhr3> i thought they are, but apparently not
[15:05] <mhr3> anyway, not sure why i'm bothering you with that... esti / facundobatista issue
[15:06] <facundobatista> mhr3, sorry?
[15:06] <mhr3> facundobatista, http://imgur.com/xMUwWvn <-- eeek
[15:08] <facundobatista> mhr3, you say it should be smaller?
[15:08] <mhr3> facundobatista, shouldn't it?
[15:09] <facundobatista> mhr3, IMO, the server should provide a bigger enough one, and the client should scale to what's needed... otherwise how do we manage for bigger phones, or tablets, or whatever?
[15:10] <facundobatista> mhr3, I mean, if I rescale it in the server, then may be too small for other clients
[15:12] <facundobatista> mhr3, actually... thinking better about it, the server should provide .svg only, and client present it in the optimal size
[15:13] <mhr3> facundobatista, svg/png doesn't matter really, as you said the resource will be presented on devices with various res, the icons should have padding to look good
[15:14] <mhr3> ie the image should be done in a way to fit the full header height
[15:15] <mhr3> facundobatista, right now they seem to be cropped to content
[15:17] <mhr3> facundobatista, wait, did something happen with the images?
[15:17] <facundobatista> mhr3, what?
[15:17] <mhr3> facundobatista, the ones joshua sent did indeed have padding
[15:17] <facundobatista> let me see
[15:17] <mterry> Do the unity8 qmluitests pass for other people?  I'm seeing an error on test_purchase_text_display
[15:17]  * facundobatista searches joshua's mail
[15:22] <facundobatista> mhr3, I have a mail from joshua from June 26th, with header logos for several scopes
[15:22] <facundobatista> mhr3, is that what you mean?
[15:22] <mhr3> facundobatista, june 16th
[15:23] <mhr3> is the one i'm looking at
[15:23] <facundobatista> mhr3, ah, he then sent another one, updated images
[15:24] <mhr3> facundobatista, then i guess the second one breaks things?
[15:24] <facundobatista> mhr3, probably! I just forwarded it to you
[15:24] <facundobatista> well, it's being sent (the attached zip is 2MB)
[15:25] <facundobatista> mhr3, probably a couple of instructions or conditions should be given to Joshua when he buiilds the images
[15:25] <mhr3> not the first time i see designers sending two email and each is done fundamentally differently
[15:29] <mhr3> facundobatista, yea, they're wrong
[15:29] <facundobatista> :/
[15:30] <mhr3> facundobatista, can you reply to joshua that the logos need to have the padding to fit the entire height of the header?
[15:30] <mhr3> show him http://imgur.com/xMUwWvn to understand the issue
[15:32] <mhr3> although.. that isn't entire height
[15:32] <mhr3> there is a little bit of padding
[15:33] <facundobatista> mhr3, sent
[15:35] <mhr3> yea, 1gu margin on top and bottom
[15:54]  * greyback eow
[16:40] <kgunn> arrgg mterry where u be?
[16:57] <Saviq> enough
[16:57] <Saviq> o/
[18:31] <kgunn> mterry: hey quick little brainstorm about mir & debian deps  in control files
[18:31] <mterry> kgunn, hi
[18:32] <kgunn> so, thinking today our rverse deps all say >=mir version
[18:32] <kgunn> but, as we're about to branch for rtm....that's not gonna work well
[18:32] <kgunn> e.g. chance exists we may need to break abi on server even after branching
[18:33] <mterry> kgunn, you're thinking you want a dep on mir << version+1?
[18:33] <kgunn> but...could end up with 2 diff versions progressing, 1 on stable-rtm and 1 on trunk
[18:33] <kgunn> well...that;s just it...i'm thinking =
[18:33] <kgunn> exact
[18:33] <kgunn> i mean, we never skip building reverse depends anyway
[18:34] <kgunn> so in reality we're saying = even tho control says >=....which >= isn't true (e.g. abi is broken)
[18:35] <kgunn> so i just want to verify my thinking we should change the control files in u-s-c, papi, unity-mir
[18:35] <mterry> kgunn, well it's sort of true, but yeah we should have << next-abi-version
[18:35] <mterry> kgunn, as for addressing two different version tracks...
[18:35] <kgunn> yeah, i thot about that, but that's not true either right ?
[18:35] <mterry> kgunn, how about defining a version prefix that is used for the branch.  Like 4.5.  Then have trunk move past that, doing 5.x and what not.  But ABI breaks on branch can go like 4.5.1, 4.5.2 or whatever?
[18:35] <mterry> kgunn, why wouldn't it be?
[18:36]  * kgunn erases next chat, and goes to read debian again
[18:37] <mterry> kgunn, you could always ABI-version the -dev packages too...  So that you have libmirserver18-dev
[18:37] <kgunn> mterry: right...so we'll end up with interleaving (potentially) mir versions
[18:38] <mterry> kgunn, well we'd ideally avoid interleaving.  You could set the branch to 4.5 and have it live in that namespace forever.  While trunk immediately bumps to 4.6 or something and never looks back
[18:38] <kgunn> e.g. imagine stable goes 0.5, 0.7, 0.9...and trunk goes 0.6, 0.8, 0.10
[18:38] <mterry> kgunn, yeah well don't do that on stable.  Have stable live in 0.X and trunk live in 1.x (like we did for unity8)
[18:39] <kgunn> but if x in 0.x.0 is referencing abi breaks...then what happens if we have a bug fix on stable that breaks abi
[18:40] <mterry> kgunn, right, you just have to "shift down" your expectation of what an abi break is one digit place
[18:40] <kgunn> (its not hypothetical....we just found something that would bump it, had we found it 2 weeks in the future after Beta freeze)
[18:40] <mterry> kgunn, so now if "0.x" is your branch indicator, then "0.x.y" is your abi and "0.x.y.z" is your minor bug fix bumps
[18:41] <mterry> kgunn, and maybe use libmirserver18.x etc
[18:41] <mterry> where 18 is the major version we use for stable
[18:44] <kgunn> mterry: how does that fit or change debian control in rdeps if stable had libmirserver18, 20, 22....and trunk might end up with libmirserver19, 21, 23
[18:44] <kgunn> ?
[18:45] <kgunn> hmm...actually....if its truly ABI...am i worrying about nothing ?
[18:45] <kgunn> the rdeps could really still compile
[18:45] <mterry> kgunn, well I think this whole thing is very similar to unity7 vs unity8.  We give the stable version a major version like...  22.  And then it lives there and we'd have libmirserver22.1 and libmirserver22.2 for ABI bumps
[18:45] <kgunn> only if its server API....then its an issue
[18:46] <mterry> kgunn, any time we need to fork a stable branch, we just freeze the major version it was on (22 or 38) and have trunk move on
[18:53] <kgunn> mterry: is that really by convention ? or a technical rule that breaks some enforcement ?
[18:53] <kgunn> understand its ideal
[18:53] <mterry> kgunn, most of these version rules are by convention
[18:53] <kgunn> ack
[18:54] <mterry> kgunn, but I was just trying to suggest a scheme that would avoid having stable be above trunk but still be able to move inside its own version namespace
[18:54] <kgunn> mterry: i'll pursue the idea of decoupling
[18:56] <mterry> kgunn, other schemes would be fine too if you had a different idea in mind.  But I think (a) your point that we are missing an upper bound on deps is valid -- we should use << next-abi-version and (b) as long as we can have stable and trunk moving in their own abi namespaces, we're good
[18:57] <kgunn> mterry: hmmm, i just can't get around the fact we're trying to tie rdeps to server api bumps basically...
[18:57] <kgunn> i'll keep thinking
[18:57] <mterry> kgunn, isn't that a good thing?
[18:58] <kgunn> mterry: it is, and they're just numbers....
[18:59] <mterry> kgunn, what are you getting at?
[19:00] <kgunn> so in theory it could do that....stable 0.4.0 turns into <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>....and then trunk goes <IP_ADDRESS>, <IP_ADDRESS>
[19:00] <kgunn> or could trunk stay 0.5.0, 0.6.0
[19:00] <kgunn> ....until the next stable
[19:01] <kgunn> so in 0.x.y.z the y means...abi bumps on stable
[19:01] <mterry> kgunn, sure, trunk could keep going crazy until we need to fork again
[19:01] <kgunn> lol
[19:01] <kgunn> mterry: with the hopes that someday we get the server api under control
[19:02] <mterry> kgunn, I'm a big fan of bumping major versions whenever we need.  I think deja-dup is on version 32 or something
[19:02] <mterry> kgunn, well even if server abi doesn't change, doesn't mean that the project version couldn't.  but sure, it would be nice to have that move slower
[19:03] <kgunn> mterry: at the end of the day...there's going to be 2 diff control files as well in each of the rdep projects...trunk for trunk & stable for stable
[19:04] <kgunn> hence my reasoning in the beginning its really an = situation
[19:04] <mterry> kgunn, yup, I don't think there's a way around that which we would find acceptable
[19:04] <mterry> kgunn, no, but we don't want =
[19:04] <mterry> kgunn, because we do actually release the occasional bug fix
[19:04] <mterry> kgunn, we just want >= abi and << abi+1
[19:05] <mterry> kgunn, or really
[19:05] <kgunn> right so with the proposal above we can keep it >=, with trunk staying 0.x.x and stable being 0.x.x.x
[19:05] <mterry> kgunn, regardless of how we split trunk and stable, I still think it's sensible to do <<abi+1 for both
[19:06] <kgunn> mterry: sorry to be thick skulled...but that's not really true...i mean we do really break api on server sometimes too
[19:06] <kgunn> so that wouldn't be completely true
[19:06] <mterry> kgunn, I mean, it's mostly taken care of magically for the binary package dependencies, because the abi is encoded in the package name (so libmirserver18 >= 4 implies that it doesn't match libmirserver19).  But it matters for the -dev packages which don't encode abi in package name
[19:07] <kgunn> so are you saying to ignore the logic and rely on the magic ? ;P
[19:07] <mterry> kgunn, I don't follow your pointn about breaking api on server?  You mean api vs abi?
[19:08] <mterry> kgunn, we could mostly.  -dev dependencies don't care about ABI, just API breaks
[19:08] <mterry> kgunn, but this all is a separate point from how to split the versioning for stable/trunk
[19:08] <mterry> kgunn, I was just proposing a separate nice fix to use <<abi+1 but I think we don't really need that for any of the packages I can think of
[19:09] <kgunn> ok...i'm gonna copy.paste this irc chat and share with cemil/duflu
[19:09] <mterry> We could do it for the -dev packages, but we don't have a versioning scheme for breaking API
[19:10] <mterry> kgunn, I think my takeaway is just to suggest freezing stable's major version and bumping down the ABI position by 1 place so as not to conflict with trunk
[19:23] <kgunn> mterry: one last question...so for libmirserver<somenumber>....assuming stable is mir0.5.y.z, and trunk is mir0.6.y
[19:23] <kgunn> can the number of libmirserver<number> be the same and sage ?
[19:23] <kgunn> oops/sage/safe
[19:24] <mterry> kgunn, well.  the versions like 0.5/0.6 *could* safely be the same too.  Because they'd be in different repositories.  But that way lies massive confusion.  So I'd say the same for the libmirserverXX numbers
[19:25] <kgunn> yeah
[19:25] <kgunn> agreed...i don't like it either
[22:03] <Saviq> mzanetti, if you're around, is there a reason why we don't have a ubuntu-touch package in silo 6?


[00:17] -queuebot:#ubuntu-release- New binary: remmina [riscv64] (jammy-proposed/main) [1.4.23+dfsg-1] (ubuntu-desktop)
[00:35] -queuebot:#ubuntu-release- New binary: php-xmlrpc [riscv64] (jammy-proposed/universe) [3:1.0.0~rc3-2] (no packageset)
[01:01] -queuebot:#ubuntu-release- New binary: oidc-agent [riscv64] (jammy-proposed/universe) [4.2.5-1] (no packageset)
[05:19] -queuebot:#ubuntu-release- New binary: golang-github-muesli-sasquatch [amd64] (jammy-proposed/universe) [0.0~git20210519.30aff9d-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: golang-github-cli-shurcool-graphql [amd64] (jammy-proposed/universe) [0.0.1-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: golang-github-meowgorithm-babylogger [amd64] (jammy-proposed/universe) [1.2.0-2] (no packageset)
[05:20] -queuebot:#ubuntu-release- New binary: golang-github-gabriel-vasile-mimetype [amd64] (jammy-proposed/universe) [1.4.0+dfsg1-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: golang-github-calmh-randomart [amd64] (jammy-proposed/universe) [1.1.0-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: golang-goji [amd64] (jammy-proposed/universe) [2.0.2-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: golang-github-muesli-toktok [amd64] (jammy-proposed/universe) [0.0~git20210519.2b0817e-2] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: libapi-gitforge-perl [amd64] (jammy-proposed/none) [0.007-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: alglib [amd64] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: golang-github-charmbracelet-wish [amd64] (jammy-proposed/universe) [0.1.1-2] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: alglib [s390x] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: alglib [ppc64el] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[05:30] -queuebot:#ubuntu-release- New binary: alglib [arm64] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[05:30] -queuebot:#ubuntu-release- New binary: alglib [armhf] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[06:02] -queuebot:#ubuntu-release- New binary: alglib [riscv64] (jammy-proposed/universe) [3.18.0-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: node-picocolors [amd64] (jammy-proposed/universe) [1.0.0-3] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: node-config [amd64] (jammy-proposed/universe) [<IP_ADDRESS>.g98f2fc9-3] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: komposter [amd64] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: komposter [ppc64el] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[17:32] -queuebot:#ubuntu-release- New binary: komposter [s390x] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: komposter [arm64] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: komposter [armhf] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[18:15] -queuebot:#ubuntu-release- New binary: komposter [riscv64] (jammy-proposed/universe) [0+git20201216+ds-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: libfilezilla [s390x] (jammy-proposed/universe) [0.35.0-1] (no packageset)
[23:23] -queuebot:#ubuntu-release- New binary: libfilezilla [ppc64el] (jammy-proposed/universe) [0.35.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: git-hub [amd64] (jammy-proposed/none) [2.1.1-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: elpa [amd64] (jammy-proposed/universe) [2021.11.001-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New binary: elpa [ppc64el] (jammy-proposed/universe) [2021.11.001-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: elpa [s390x] (jammy-proposed/universe) [2021.11.001-1] (no packageset)
[23:27] -queuebot:#ubuntu-release- New binary: php-parsedown-extra [amd64] (jammy-proposed/none) [0.8.1-1] (no packageset)
[23:31] -queuebot:#ubuntu-release- New binary: libfilezilla [armhf] (jammy-proposed/universe) [0.35.0-1] (no packageset)
[23:32] -queuebot:#ubuntu-release- New binary: libfilezilla [arm64] (jammy-proposed/universe) [0.35.0-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: elpa [arm64] (jammy-proposed/universe) [2021.11.001-1] (no packageset)
[23:37] -queuebot:#ubuntu-release- New binary: elpa [armhf] (jammy-proposed/universe) [2021.11.001-1] (no packageset)
[23:56] -queuebot:#ubuntu-release- New binary: libfilezilla [riscv64] (jammy-proposed/universe) [0.35.0-1] (no packageset)


[00:16] -lugito:#lubuntu-devel- [T93: Theme lists pages] Paintface07 (Kevin Kondratuk) commented on the task: https://phab.lubuntu.me/T93#1596
[00:21] -lugito:#lubuntu-devel- [T93: Theme lists pages] Paintface07 (Kevin Kondratuk) commented on the task: https://phab.lubuntu.me/T93#1597
[00:36] -lugito:#lubuntu-devel- [rLISTSHTML4b1612f98758: remove standalone stylesheet, since it can't be referenced externally.  This…] Paintface07 (Kevin Kondratuk) committed: https://phab.lubuntu.me/rLISTSHTML4b1612f98758
[02:12] -lugito:#lubuntu-devel- [rNMTRAYPACKAGINGdbac91e98062: Reverted previous commit] wxl (Walter Lapchynski) committed: https://phab.lubuntu.me/rNMTRAYPACKAGINGdbac91e98062
[02:17] <wxl> has anyone had a case where debuild -S doesn't invoke signing?
 Happens every time when sponsoring
 Use -k
[02:18] <wxl> is that a debsign switch?
 And a debuild one
 But the docs for the relevant debsign switch apply
[02:19] <wxl> i have a DEBSIGN_KEYID in ~/.devscripts tho
 Beat it over the head a couple more times?
 XD
[02:20] <wxl> siiiiiiiiiiiiiiiiigh
[02:21] <wxl> ugh even using -k doesn't work
[02:21] <wxl> wth
 What's the error?
[02:24] <wxl> that's the funny thing.. nothing
 ?
[02:34] <wxl> had to --force-sign it
[02:35] <wxl> perhaps because it's UNRELEASED
[02:35] <wxl> at least that's what the manpage suggests
[02:35] <wxl> that jive with your understanding?
 @wxl [<wxl> perhaps because it's UNRELEASED], Uhh, yeah, that's why!
[02:35] <bashfulrobot> This sounds fun.
 :)
 UNRELEASED = this won't be released as is
 UNRELEASED = don't bother signing
[02:36] <wxl> but you can't dput without signing, no?
 You don't dput UNRELEASED
[02:36] <wxl> so what do you do?
 Change from UNRELEASED ;)
[02:37] <wxl> aw jeez
[02:37] <wxl> i blame @HMollerCl
[02:39] -lugito:#lubuntu-devel- [rNMTRAYPACKAGING24f0cb9aebb5: fixed distribution] wxl (Walter Lapchynski) committed: https://phab.lubuntu.me/rNMTRAYPACKAGING24f0cb9aebb5
 BAD
 debian/files needs to stay ignored
 :)))
[02:42] <wxl> ughhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
[02:43] <wxl> and remove build/?
 Yes
[02:44] -lugito:#lubuntu-devel- [rNMTRAYPACKAGINGdebedb60843a: fix gitignore] wxl (Walter Lapchynski) committed: https://phab.lubuntu.me/rNMTRAYPACKAGINGdebedb60843a
 Ooo, sorry wxl
[02:50] <wxl> hey at least there's a changelog entry :)
[03:02] <guiverc2> wxl, ack 1812594 (lxlock) will aim to test today
[03:03] <wxl> @kc2bez did you figure out how to test those other thingies?
[04:36] -lugito:#lubuntu-devel- [T90: Bionic locker should be light-locker] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T90#1598
[04:37] -lugito:#lubuntu-devel- [T26: Define and Implement Default Settings for Touchpad] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T26#1599
[04:40] <guiverc> wxl, you just beat me..
[04:40] <wxl> neener neener neener :)
[04:42] <kondrak> yo folks, anyone know who I can talk to about getting these updated styles applied to the mailing lists? https://phab.lubuntu.me/T93  (sorry for being a broken record)
[04:42] -lugito:#lubuntu-devel- [Wishlist, Open] Theme lists pages: https://phab.lubuntu.me/T93
[04:43] <kondrak> I'm new and don't know who I should be working with :)
[04:43] <wxl> oh i could install them
 wxl: tag you're it no tagbacks :)
[04:43] <kondrak> I only have one done, but I'd like to make sure it's gonna work before I do the rest.
[04:43] <wxl> waiiiiiiiiiiiiit
[04:43] <wxl> can mailman actually handle css?
[04:43] <kondrak> maybe?
[04:44] <wxl> i fear if it does it might be backend, which would suck
[04:44] <kondrak> could be, simon pasted the templates though, and it looked like we had control over the <head> tag content.
[04:45] <guiverc> :O  wxl..  fyi, I instaled 18.04.1 on vbox, does ctrl+alt+L work on vbox; it's not doing anything on my vbox 18.04.1 with rm'd file ; but lock-screen from menu works, the rm'd file re-creates itself on login
[04:45] <wxl> did for me chris
 @wxl [<wxl> can mailman actually handle css?], Look at Xubuntu's
[04:46] <wxl> @tsimonq2: they might have had to RT their way to it
[04:46] <wxl> in which case NOT IT
 oh gawd okay XD
[04:46] <kondrak> it seems like they did it the same way I did.
 See, there we go
[04:46] <wxl> chris: `grep ~/.config/lxsession/Lubuntu/desktop.conf lock`
[04:47] <kondrak> I think these styles are more responsive though :)
 Your modifications are DEFINITELY an improvement though
[04:48] <wxl> yeah no place to put css
[04:48] <wxl> rt it is
[04:48] <wxl> love you bye
[04:48] <guiverc> wxl, "lock manager/command=lxlock"  (typed, not copy/pasted)
[04:48] <kondrak> wxl: this is the template I've "finished": https://phab.lubuntu.me/source/lists-html/browse/master/templates/lubuntu-council-list-info-template.html
[04:49] <wxl> guiverc: that's the problem. the test case suggests deleting the whole file and logging out and back in again
[04:49] <guiverc> i did delete, a couple of times, logout, login and the file is there again..
 @wxl [<wxl> yeah no place to put css], Uhh, dude, it's literally a whole HTML file, you can put a CSS file in there :)
 I say try to deploy it and see what happens
 OR
 We just refer to an external stylesheet
 OR
[04:50] <wxl> ew
[04:50] <guiverc> rm again, stat (file not found), logout, login, stat (ascii text)
 Inline CSS
[04:50] <kondrak> can't refer to external stylesheet.  I just used <style> tags...
[04:51] <kondrak> (at least with https on phab or github)
[04:51] <kondrak> I already tried that
[04:51] <wxl> The page you saved contains suspicious HTML that could potentially expose your users to cross-site scripting attacks. This change has therefore been rejected. If you still want to make these changes, you must have shell access to your Mailman server.
[04:51] <wxl> See FAQ 4.48.
[04:51] <wxl> Page Unchanged
[04:51] <wxl> ***** RT IT IS *****
 Waaaaaaaaaaaaat
 Eew
[04:51] <kondrak> wussa RT?
[04:51] <guiverc> wxl, shall i comment fully on lp.bug.thingy?
[04:52] <wxl> https://wiki.list.org/DOC/4.48%20How%20can%20I%20change%20the%20HTML%20or%20.txt%20templates%20used%20by%20my%20mailing%20lists%3F
[04:52] <wxl> @guiverc: please
[04:52] <guiverc> :))
[04:53] <wxl> that has got to be the wrong faq
[04:58] <kondrak> wxl: RT = "real terminal"?  lol
[04:58] <wxl> rt.ubuntu.com
[04:58] <wxl> see also #canonical-sysadmin
[04:59] <wxl> you can email<EMAIL_ADDRESS>to create a ticket to the sysadmins. could tell them you want to install it and cc the lubuntu-council and we'd approve it and they'd do it
[04:59] <wxl> problem, though: untested. we really need a mailman instance to try it in
[04:59] <wxl> it should be pretty default, so you could do it in a virtual machine
[05:00] <kondrak> Ok, no problem.  If it's going to be this big of a deal to request it, I can try to setup a more robust test.
[05:01] <kondrak> Let's see how deep this rabbit hole goes!  :P
 Did I hear that @teward001 has a mailman instance?
[05:02] <wxl><EMAIL_ADDRESS>[05:03] <wxl> seriously though. virtualbox.
<EMAIL_ADDRESS> Uhh, no, QEMU
 It's the best thing since VirtualBox
[05:04] <wxl> kondrak: you down with virtual machines?
[05:04] <kondrak> wxl: yeah, it's no problem.  I'll have a crack at it.  Probably after I get some sleep though :P  Yeah, I do all the virtuals and containers :D
[05:04] <wxl> ok, good
[05:06] <kondrak> I'll try to add whatever I can to the repo for a test rig so the next person has an easier time.
[05:11] <lubu-qa> wxl, i rebooted 18.04.1 vm & same result .. I'm updating the 18.04 vm  (I hadn't done that as wasn't mentioned except your last comment)   [guiverc in a different room]
[06:13] <lubu-qa> wxl; you'll have to read lp.1812594 update (full-upgrade took ages)... but :(    `lxlock` is not installed, and `whereis lxlock` produces no results...
[08:57] <guiverc> thanks apt-ghetto :)   don't have a brain injury (motorcycle injury); simple stuff just never occurs to you
[09:02] <apt-ghetto> guiverc: Absolutely no problem. I am glad, that you invest time in testing.
[10:18] <kc2bez> wxl: guiverc I started on that last night but work called with issues so I didn't get to update you. Some of the types may not be practical to test which is fine (probably none of us have a hd-dvd). I will try to get back to it tonight.
 @tsimonq2 [Did I hear that @teward001 has a mailman instance?], not mine
 @wxl [<wxl><EMAIL_ADDRESS>lol
 @tsimonq2 [Did I hear that @teward001 has a mailman instance?], twas merely me derping with mailman to understand the internals better then I accidentally broke my vps
 ... why?
 I also have DNS over TLS and DNS over HTTPS servers too so :P
[12:23] -lugito:#lubuntu-devel- [rLIBFMQTPACKAGINGba535b4af8dd: Fix updated symbols] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rLIBFMQTPACKAGINGba535b4af8dd
 which was the web page to connect to irc?
 http://webchat.freenode.net/?channels=%23lubuntu
[13:12] <guiverc2> HMollerCl - do you mean https://wiki.ubuntu.com/IRC/ChannelList
 This?
[13:13] <guiverc2> (I added support channel links to that page.. not for dev channels though)
 @aptghetto [This?], nope, this https://webchat.freenode.net/ thanks anyway
 but @N0um3n0 look at https://wiki.ubuntu.com/IRC/ChannelList we need to add the others
 @HMollerCl [but @N0um3n0 look at https://wiki.ubuntu.com/IRC/ChannelList we need to add the …], True, it's already set in our "first steps."
 wxl: re: https://phab.lubuntu.me/w/support/ … I would like to swap places with you as point of contact for mailing list.
[13:38] -lugito:#lubuntu-devel- [rCALAPACKAGING98dd461cc2b2: Refresh patch] apt-ghetto (apt-ghetto) committed: https://phab.lubuntu.me/rCALAPACKAGING98dd461cc2b2
[13:41] <wxl[m]> Do it
 @kc2bez FYI: I had to refresh one patch in the calamares package on ci/unstable
[14:51] <kc2bez> Thanks for letting me know. I noticed [ade] was back. Was the change precipitated from a recent git commit?
 Yes, https://github.com/calamares/calamares/commit/3bd73a97ce0bdf80bb749a14e58a19f45e9e14d6
 wxl: I think I found the problem why some icons are different. The scanner and printer icons in 16x16 are what we see in the menu. Not sure if that is correct or not. Not sure if that is an icon-theme, xdg or lxqt definition though.
[14:52] <kc2bez> Thanks @aptghetto
 wxl: and the icons for sacnner and printer (and discover) we see in the menu are not the same we see in /usr/share applications
[16:36] <wxl> @HMollerCl what about `find / -type f -name *icon* 2>/dev/null` wgere icon is the name of the icon file in the desktop file? maybe run it through `grep`, i.e. for png or svg if the list is too long. that will give us a list of possible candidates
 I did something similar to that
 the point is, menu is populated with icons from 16x16 folder
 I'm not sure if that is the standard and if that can be easily changed
[17:43] <wxl> if we make our own 16x16 folder (like we had tried to do before with other folders) can we override?
 good point, haven't tried that, will do
 nope, but reading carefully, I'm more convinced it has to be a theme.
[17:49] <wxl> well then that agrees with your idea that we need to do a theme
 "Icons and themes are looked for in a set of directories. By default, apps should look in $HOME/.icons (for backwards compatibility), in $XDG_DATA_DIRS/icons and in /usr/share/pixmaps (in that order).... .In each of these directories themes are stored as subdirectories. A theme can be spread across several base directories by having
[17:51] <wxl> it's that last sentence that seems like such a great notion.. and is so difficult to implement XD
 now I'm impressed
 I copied ePapirus theme to ~/.icon
 then coppied (overwriting) the 22x22/scanner.svg to 16x16/scanner.svg and the colorful icon I saw in 22x22 folder was converted to gra
 gray
 grey
[18:05] <wxl> wth
[18:09] <wxl> @tsimonq2: https://mastodon.technology/web/statuses/102535660248373955
 Get them in here
[18:11] <wxl> "please come to our irc channel so we can tell you we're struggling to get the right icons in the menu and can't be bothered with such trivialities of porting a whole window manager to a new and not generally ready-for-prime-time display server"
[18:12] <wxl> it was an ostentatious claim, unless you've got someone working on it
 It's being "worked" on :P
[18:13] <wxl> uhhh huh
[18:13] <wxl> show me the repo
[18:13] <wxl> or it didn't happen
 "repo or it didn't happen" XD
 See, about that, I have it "locally"
[18:14] <wxl> then make it public
[18:14] <wxl> heck, you might even get some people helping
[18:14] <wxl> yeeesh
[18:14] <wxl> i can imagine it now.. repo goes public.. "oh there's a README. that's cool."
 oh there's a readme.  it says 'You Failed'.  I don't like this software.
 *shot*
 just kidding ;)
 wxl: woked!!!
 a theme in ~./icons
 with only this 3 changes, things looks a loot better: printer, scanner, help-about
 but, it worked nice in ~/.icons but didn not in XDG_DATA_DIRS/icons aka (usr/share/Lubuntu/icons)
 but that's maybe because usr/share is in the same level as /usr/share/Lubuntu so it doesn't override
[18:40] -lugito:#lubuntu-devel- [rMANUAL428364e27655: Add back to default file] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL428364e27655
 wxl: My Question is, could we only add icons to a theme? This would be copy .svg in the papirus icon directory?
[19:07] -lugito:#lubuntu-devel- [rMANUAL7747ea931806: Add multimonitor dials for brightness] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL7747ea931806
[19:13] <wxl> @HMollerCl only one way to find out :)
 I know we can, my question is if we should, because we will put files in directories created by papirus-icon-theme
[19:20] <wxl> we could make a new theme
 Making a new theme? But why?
 but only for 3 menu icons
[19:21] <wxl> desperation
 about lxqt, skanlite, printer
 those 3 icons are monocolor in papirus and monocolor icons doesn't work well with our dark panel/light window combination
[19:23] <wxl> we can't find any other way to override them
 Kvantum?
 @wxl [<wxl> we can't find any other way to override them], somehow we can find a way to blame Simon :P
 loljk
[20:15] <wxl> somehow? pfffht
 @teward001 [somehow we can find a way to blame Simon :P], noU
 @tsimonq2 [noU], well I mean I already placed blame on you so...
 :P
[20:26] -lugito:#lubuntu-devel- [rMANUALd8dc8c1e93c2: pluralize screenshots section] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALd8dc8c1e93c2
[21:32] <wxl> so who can i train to be our new bug triager?
 wxl: created an issue in papirus ghithub. Maybe is better if they add the, Then we only have the problem with "about-lxqt" whic uses help-about, we could change that(?) https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/issues/1835
[22:04] <wxl> that seems a good idea
[22:04] <wxl> i bet we could convince lxqt similarly
 lxqt could use their own icon
 the "helix"
[22:05] <wxl> yep
[22:05] <wxl> suggestion: add a screenshot to that issue
[22:05] <wxl> since you don't know what the icon ends up being. i'm sure they can identify it
 There was another member that coudl speak German, right? Who was it? do you think we shoudl make a german irc/telegram?
[22:14] <wxl> i think it would be good for ANY language
 @aptghetto you're the man I was thinking
 wxl: https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/issues/1835
[22:58] -lugito:#lubuntu-devel- [T95: Better Menu Icons] hmollercl (Hans P. Möller) commented on the task: https://phab.lubuntu.me/T95#1600
[23:22] -lugito:#lubuntu-devel- [rMANUAL6d62ce705b56: Add && to Appendix C] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL6d62ce705b56
[23:51] -lugito:#lubuntu-devel- [rMANUAL809a803173c4: Add Pipe with example] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL809a803173c4


[10:49] <wolf|work> morning
[10:54] <rick_h_> morn
[11:48] <cmaloney> morning
[12:08] <_stink_> yo
[12:14] <wolf|work> -yo
[13:12] <cmaloney> up down up down spin spin spin up
[13:14] <rick_h_> heh yea pretty much
[13:19] <wolf|work> O_o There's a "spin" on your control pad?
[13:22] <cmaloney> wolf|work: I'm old-school like that.
[13:23] <cmaloney> http://s49.photobucket.com/user/isucamper/media/dotcp.jpg.html
[13:23] <cmaloney> http://s49.photobucket.com/user/isucamper/media/troncp.jpg.html
[13:51] <brousch> There is an interesting job in Durango, CO, so I looked at the cost of living difference. This was unexpected http://www.bestplaces.net/cost-of-living/grand-rapids-mi/durango-co/50000
[13:51] <brousch> Durango is 43% more expensive than Grand Rapids.
[13:52] <brousch> Housing is 207% more expensive in Durango.
[13:57] <cmaloney> That doesn't surprise me
[13:57] <cmaloney> MI is a bargain
[13:57] <cmaloney> I think the only places that have cheaper housing are West Virginia
[13:59] <wolf|work> brousch: really surprised that you were surprised
[13:59] <brousch> But 200%?
[14:02] <wolf|work> over Grand Rapids?
[14:03] <wolf|work> You can probably find places in Michigan were houses are 200% over Grand Rapids :-p
[15:31] <greg-g> will durango still have a high cost of living after that toxic spill?
[15:33] <cscheib> I wouldn't say Michigan as a whole is really all that cheap, like many states, we have cheap areas, and particularly expensive areas... just not silicon valley expensive
[17:46] <jcastro> MI Rocks
[17:47] <jcastro> if you go to like, mountain view or any of the valley places
[17:47] <jcastro> it's like, millions and millions of dollars
[17:47] <jcastro> for a tiny ranch
[17:48] <jcastro> If I had to live in the valley there's no way I could afford a house there
[17:49] <greg-g> see also: Greg moving to Petaluma, but still being priced out
[17:50] <jcastro> ooh, kyle rankin lives there
[17:50] <jcastro> btw, I tried to get a sprint close to there but the prices were just too much
[17:50] <jcastro> so we could have had martinis again
[17:51] <rick_h_> jcastro: you should drive down to chicago with us. Can ride down with jrwren and I :)
[17:51] <jcastro> rick_h_: I just came from there
[17:52] <rick_h_> jcastro: ah cool
[17:56] <jcastro> rick_h_: is your sprint next week?
[17:56] <rick_h_> jcastro: 31st
[20:40] <cmaloney> Things I hate: forgetting the percent for date +%F


[10:32] <davmor2> evand: ping
[10:54] <CIA-1> ubiquity: cjwatson * r2697 ubiquity/.bzrignore: ignore debian/*.debhelper.log
[12:33] <CIA-1> casper: cjwatson * r520 casper/ (debian/changelog debian/control scripts/casper):
[12:33] <CIA-1> casper: Remove bad-and-wrong setting of PATH to include directories under /root;
[12:33] <CIA-1> casper: now that grep links to more libraries than before, this broke a number
[12:33] <CIA-1> casper: of things. Requires initramfs-tools (>= 0.92bubuntu5) because this
[12:33] <CIA-1> casper: doesn't work with klibc chroot.
[12:35] <CIA-1> casper: cjwatson * r521 casper/debian/changelog: releasing version 1.136
[13:15] <CIA-1> ubiquity: cjwatson * r2698 ubiquity/ (4 files in 2 dirs): (log message trimmed)
[13:15] <CIA-1> ubiquity: Automatic update of included source packages (limited to those packages
[13:15] <CIA-1> ubiquity: where ubiquity code already expects newer versions): apt-setup
[13:15] <CIA-1> ubiquity: 1:0.37ubuntu2, partconf 1.27, partman-auto 78ubuntu1, partman-auto-loop
[13:15] <CIA-1> ubiquity: 0ubuntu15, partman-base 121ubuntu3, partman-basicfilesystems 60ubuntu1,
[13:15] <CIA-1> ubiquity: partman-basicmethods 39ubuntu1, partman-efi 17ubuntu1, partman-ext3
[13:15] <CIA-1> ubiquity: 52ubuntu1, partman-jfs 26ubuntu1, partman-newworld 19ubuntu1,
[13:18] <CIA-1> ubiquity: cjwatson * r2699 ubiquity/ (bin/ubiquity-wrapper debian/changelog debian/control):
[13:18] <CIA-1> ubiquity: KDE frontend: Use kdesudo-kde4 for now, and adjust ubiquity-wrapper to
[13:18] <CIA-1> ubiquity: look for it in /usr/lib/kde4/bin/ (LP: #247537).
[13:28] <CIA-1> ubiquity: cjwatson * r2700 ubiquity/debian/changelog: releasing version 1.9.1
[14:26] <evand> davmor2: pog
[14:26] <evand> pong*
[14:28] <davmor2> evand: just a quicky on wubi It's having issues with the intrepid cd because it only fits on a dvd.  So rather than installing from the drive it's downloading it instead.
[14:29] <evand> ok
[17:48] <CIA-1> partman-base: cjwatson * r102 ubuntu/ (4 files in 2 dirs):
[17:48] <CIA-1> partman-base: Add partman/early_command hook to run arbitrary commands immediately
[17:48] <CIA-1> partman-base: before partitioning (LP: #239348).
[17:54] <CIA-1> installation-guide: cjwatson * r429 ubuntu/ (debian/changelog en/appendix/preseed.xml): Document partman/early_command.
[19:06] <cjwatson> evand: bug 231727 - could we change partman-target not to erase /boot?
[19:06] <cjwatson> I think it probably makes sense given the special ways in which people use /boot, and the expected range of problems is probably quite small
[19:09] <evand> ok
[19:09] <evand> on it
[19:19] <evand> cjwatson: http://paste.ubuntu.com/26722/ - is that roughly what you had in mind?
[19:21] <cjwatson> sounds about right. why unlink rather than rm -f?
[19:22] <cjwatson> (unlink is rather new-fangled as a command as opposed to a system call, and rm -f is probably more portable and certainly more usual)
[19:22] <evand> ah, thanks
[19:23] <evand> ok, I'll just commit the rest then
[19:23] <cjwatson> yep, go for it
[19:24] <CIA-1> partman-target: evand * r726 ubuntu/ (debian/changelog finish.d/clear_partitions):
[19:24] <CIA-1> partman-target: Don't clear boot. It makes sharing a boot partition impossible and
[19:24] <CIA-1> partman-target: other distributions use sufficiently different kernel names anyway.
[19:24] <CIA-1> partman-target: (LP: #231727)
[21:30] <CIA-1> ubiquity: evand * r2701 ubiquity/ (configure configure.ac): Bump to 1.9.2


[20:30] <veebers> Morning team
[22:28] <veebers> babbageclunk: would you have a free moment today? wallyworld tasked me with adding --agent-stream to upgrade-juju, want to make sure I'm going down the right path (will need a facade vers bump I believe)
[22:29] <babbageclunk> veebers: sure
[22:30] <babbageclunk> veebers: want to hangout about it?
[22:30] <veebers> babbageclunk: sure! I'll just grab a drink of water, use the standup HO?
[22:31] <babbageclunk> veebers: yup yup


[02:34] <xubuntu03w> hi, i have question on lock screen, each time when i click 'lock screen', then the computer turns black on the screen. I want to know how to fix this problem..thanks!
[02:35] <xubuntu03w> The computer will not be able to reply after the black screen, can only be restarted.
[02:38]  * defender99zu3 bows to all the nice people.
[02:38] <defender99zu3> I have a question about logging into Xubuntu without a monitor. Anyone around to give me a hand?
[04:37] <xubuntu13w> hi does anyone know where ro get the xubuntu stickers? the site they link to doesnt have them
[04:40] <xubuntu13w> i need one for mainly the windows key, and maybe powered by xubuntu. i found knockoffs, but i want the official design
[04:59] <pleia2> hm, I wonder where we are still linking to them, maybe a blog post
[05:03] <krytarik> I figured they might have just checked the one provider we do feature currently - and didn't find what they wanted which also isn't said that they have.
[12:33] <xubuntu90i> join
[12:33] <knome> you are already here.
[12:34] <xubuntu90i> xubnutu is very good Operating System
[13:00] <nailyk> Hi all. I have a weird issue on my xubuntu 16.04.05. (my gaming OS). While running some games (recently) like need for speed undercover (through wine) & super crate box (in steam),
[13:00] <nailyk> it is like the up arrow is keept pressed.
[13:01] <nailyk> (I never tested thoses games before).
[13:01] <nailyk> I check almost all the hardware parts (even if other games play just fine) but have no clue what could be checked to solve this. Any advices please ?
[13:09] <Spass> hello nailyk, do you have any controller plugged in when you play nfs? did you try to reconfigure keys in game options? which wine version are you using?
[13:10] <nailyk> I was not able to get into any menus as the game is unusable. I did unplugged all my game controllers. Only keyboard, mouse remain on USB. I also ubplugged any bluetooth controllers just in case.
[13:11] <nailyk> I do not think it is related to wine version as the steam game does the same. And, TBH I have no idea as I just run the game with right clic, run into wine :)
[13:16] <Spass> you can try asking on channels for linux gamers, like #gamingonlinux and #steamlug
[13:22] <nailyk> I will. But I was wondering how I can debug that. I tried showkeys but it mostly show only key press/release
[14:16] <nailyk> Funny, I do not have any gamepad plugged, but running a jscal -c /dev/input/js0 solved the issue. I guess it somehow still use the calibration when I had plugged my gamepad.
[15:42] <Spass> yeah, that seemed like a gamepad related issue, that's why I asked about it, great that you solved it
[23:48] <clayton> is anyone actually online in this irc channel?
[23:53] <Unit193> Yep.


[01:29] <TheMuso> c
[09:27] <fabbione> BenC: are you still around?
[09:37] <Administrator> is the kernel_panic acpi issue already fixed in 2.6.17 ( acpi_hw_low_level_read ) bug 61848?
[07:24] <JanC> is bug #63134 being worked on by somebody?
[07:24] <JanC> https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/63134
[07:24] <JanC> people with via epia based multimedia systems are complaining  :)
[07:26] <tfheen> no, it unfortunately won't be fixed.
[07:26] <tfheen> (for edgy)
[07:31] <JanC> someone mentions a (possible?) fix in comment #5
[07:32] <tfheen> that just means "something in Debian's kernel is different"
[07:33] <JanC> comment #5 is about a fedora kernel  :)
[07:33] <JanC> something about commenting out "quirk_via_abnormal_poweroff"
[07:34] <tfheen> oh, true.
[07:34] <tfheen> no idea what that is, and it's just too close to release to put in a new kernel anyway.
[07:34] <mjg59> It's a patch that we also carry
[07:34] <mjg59> No idea why it causes that problem, though
[08:57] <matt132123> hi there everyone
[08:58] <matt132123> i'd like your advice about how i go about submitting a bluetooth patch. is it something i could suggest here, or would it have to go directly to the bluez team?
[08:59] <zul> well its probably not going to go into edgy now but if its a kernel side then open a bug in launchpad and we will have a look if its userland talk to the bluez team
[09:10] <matt132123> yeah, it's def kernel side, in drivers/bluetooth/hci_usb.c
[09:10] <zul> send me the patch and ill have a look
[09:16] <matt132123> is it just a case of doing a diff, or do i have to do something else? (I've never made a real patch before)
[09:16] <zul> basically its a diff
[09:17] <zul> do you have a reference for your patch?
[09:20] <matt132123> i don't know what one is, so i guess not. this is just something i always had to do when i compiled a new kernel on gentoo to get my hardware recognised. i never actually reported it as a bug or anything as i thought it would go away with time (it was a new model usb dongle), but it hasn't
[09:21] <zul> you can send me your file and i can create a patch
[09:22] <matt132123> this is a diff against the 2.17.10 kernel as included in edgy.
[09:22] <zul> send it to<EMAIL_ADDRESS>[09:23] <matt132123> oh right, will do. i just tried to send it via irc, but i don't think it's working. (you have to excuse my ignorance, this is also the first time i've used irc)
[09:24] <matt132123> it's a tiny diff, i'll paste it in here...
[09:24] <matt132123> 97a98,100
[09:24] <matt132123> >       /* Cellink BTA-3120 */
[09:24] <matt132123> >       { USB_DEVICE(0x0c10, 0x0000) }
[09:24] <matt132123> >
[09:24] <zul> no please email me it
[09:25] <matt132123> ok, fair enough
[09:25] <JanC> this sounds like a very trivial fix  :)
[09:26] <matt132123> it is! hence even i can work out how to fix it!
[09:30] <matt132123> ok ,emailed it
[09:30] <zul> yeah got it thanks
[09:31] <matt132123> might be trivial, but we all have to start somewhere right?!
[09:35] <JanC> I think it's just telling a driver that it also works with other hardware than intended
[09:36] <JanC> so it's easy to fix, but might be *very* useful for users of that hardware
[09:40] <matt132123> yeah, it just  adds the device to the end of a list of a handful of other devices. but i'm not entirely sure why it should need to be added like this - as far as i know, the model  right next to it (the 3100) works out of the box. well, it's on the list of supported hardware anyway. as far as i know they both use the same chipset, which is hci compliant, and therefore should be picked up  by the driver. mystery.
[10:48] <matt132123> so what's next with that patch? do i have to do something else to get it merged into the official kernel source?
[10:53] <zul> nope..i create the patch for ubuntu and submit to BenC
[11:20] <matt132123> cool. does that mean it'll only ever go as far as ubuntu kernel then? or does it all get merged upstream eventually?
[11:24] <zul> it might get merged upstream