[08:28] <tsdgeos> Saviq: in https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1511072 you linked the bug to itseldf
[08:49] <Saviq> tsdgeos, oops
[08:54] <tsdgeos> frozen scopes :/ https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1511063
[08:56] <tsdgeos> Saviq: we did disable the crash generation on ota7 right? so this can't be a "it's crashing but getting the info", no?
[08:57] <Saviq> tsdgeos, well, it's disabled by default, but doesn't mean people can't enable it
[08:58] <tsdgeos> right
[09:04] <tsdgeos> Saviq: would that be the "App crashes and errors" in System Settings->Diagnostics?
[10:07] <Saviq> tsdgeos, power back up? and yes, that'd be that setting
[10:07] <tsdgeos> Saviq: yep, poewr back up
[10:07] <Saviq> tsdgeos, I just realized something... we should probably update the dash header to match uitk 1.3?
[10:08] <Saviq> hmm or can we
[10:08] <Saviq> and the splash header, thought we were using UITK there...
[10:09] <tsdgeos> Saviq: it's done on the sdk13 branches
[10:10] <Saviq> hmm hmm
[10:10] <Saviq> tsdgeos, I've silo 21, with both sdk13 and qtquick24 branches, both dash and the default splash screen have the thick header bar
[10:10] <Saviq> in dash I don't think we can get rid of it straight away because we have the horizontal pills there
[10:11] <tsdgeos> ah the thick bar is different too?
[10:11] <tsdgeos> i checked the height is smaller
[10:11] <tsdgeos> didn't realize the thick bar changed
[10:11] <Saviq> yeah it's gone
[10:11] <tsdgeos> it's weird the splash screen doesn't adjust though
[10:11] <tsdgeos> since we actually use the sdk thing in there
[10:11] <Saviq> splash is also higher
[10:12] <Saviq> so we must be doing something to it
[10:12] <Saviq> tsdgeos, anyway, next landing, won't block that silo for it
[10:12] <tsdgeos> oki
[10:12] <Saviq> but we can't say we have that bug fixed when that lands
[10:12] <popey> Saviq, just noticed on latest image, open contacts and messaging (and other apps) the splash is inconsistent with the app. See http://people.canonical.com/~alan/screenshots/device-2015-10-29-101145.png vs http://people.canonical.com/~alan/screenshots/device-2015-10-29-101200.png
[10:12] <popey> is that known?
[10:13] <Saviq> popey, bug #1508363
[10:13] <Saviq> popey, workin' on it
[10:13] <popey> okay
[10:15] <Saviq> cimi, looks like the new shape branch added an overlay background to the store card https://owncloud.sawicz.net/index.php/s/0afe9e8a599ef8fef2f2a105e9db357d#//screenshot20151029_111418354.png
[10:15] <Saviq> that cleared with design?
[10:15] <cimi> Saviq, let me see
[10:16] <cimi> Saviq, nope that's new
[10:16] <cimi> not intended
[10:17]  * cimi investigates
[10:19] <mzanetti> Saviq, hey, I've a fix for the issue that kgunn found (windows storage saves 0,0,0,0)
[10:19] <mzanetti> should I propose a new branch or push it to panel-button-fixes?
[10:20] <Saviq> mzanetti, push
[10:20] <mzanetti> ack
[10:20] <Saviq> mzanetti, or well,
[10:20] <mzanetti> :)
[10:20] <Saviq> mzanetti, depends where it fits ;)
[10:20] <Saviq> mzanetti, we'll have a u8 rebuild in silo 21 for sure
[10:20] <mzanetti> yes, it does fit there
[10:20] <mzanetti> question was really how the silo state is
[10:21] <mzanetti> ok. just running some tests and will push in a minute
[10:24] <Saviq> cimi, did design ack https://owncloud.sawicz.net/index.php/s/0afe9e8a599ef8fef2f2a105e9db357d# ? that's full-width video on tablet
[10:26] <cimi> Saviq, I think the ubuntu store might specify overlay color but never worked? :)
[10:26] <Saviq> cimi, it specifies one with 0 alpha IIRC
[10:26] <Saviq> cimi, to get around it
[10:26] <cimi> ah ok let me see
[10:27] <Saviq> cimi, anywhere I can try preview sharing?
[10:27] <cimi> Saviq, there are no scopes done I think
[10:27] <cimi> Saviq, I'd like to have one too so we can see it live
[10:28] <Saviq> cimi, tryPreview works, at least?
[10:28] <cimi> mmm either that or previewSharing
[10:28] <Saviq> ack
[10:28] <cimi> don't remember let me see
[10:29] <cimi> yeah PreviewSharing
[10:30] <Saviq> doesn't look like much... pstolowski, on that note, how do scopes know if a feature like preview sharing is supported? or is it ok because if it isn't, we just ignore it?
[10:30] <Saviq> (I mean in different versions of the dash)
[10:32] <Saviq> tsdgeos, ok, so since we'll need a rebuild anyway, can I ask you to make the splash screen use new header?
[10:32] <tsdgeos> Saviq: yes, having a look
[10:32] <pstolowski> Saviq, they don't know it. if it not available, shell will just ignore unknown attributes. in general you're expected to be running up-to-date phone i guess
[10:33] <cimi> Saviq, I am just using UbuntuShapeOverlay with overlayColor: cardData["overlayColor"], while before we were reading overlayColor.r,g,b,a
[10:33] <Saviq> pstolowski, as long as they work...
[10:33] <cimi> Saviq, might be something in UITK
[10:33] <cimi> or I can workaround with opacity: cardData["overlayColor"].a MAYBE
[10:34] <Saviq> pstolowski, what I mean is, when we introduce an incompatible change, we can't let scopes use it until a new framework is defined
[10:34] <Saviq> pstolowski, otherwise you can install a scope that won't work
[10:35] <mzanetti> Saviq, pushed
[10:35] <Saviq> mzanetti, ack, tx
[10:35] <Saviq> mzanetti, +test?
[10:35] <pstolowski> Saviq, yes, absolutely
[10:36] <Saviq> pstolowski, so long as older phones will just ignore it, fine
[10:36] <Saviq> pstolowski, but before we make any changes like that public, we need to determine what's what
[10:38] <mzanetti> Saviq, yes, added atest too
[10:38] <Saviq> mzanetti, great
[10:39] <Saviq> cimi, if you can, please do, but find out what's going on and check if/file a bug in uitk
[10:39] <cimi> Saviq, for overlay right? no focus thingy
[10:41] <Saviq> cimi, yes
[10:44] <Saviq> mzanetti, when you close an app, focus not going to the next window is known, right?
[10:45] <mzanetti> hmm... not really... need to check if ltinkl has that fixed, he was mocking around with focus
[10:45] <Saviq> reboot
[10:46] <Saviq> no external screen either, just messing about with maximizing dash in windowed mode
[10:48] <Saviq> mzanetti, noticed, also, that minimize clears the maximize state
[10:49] <Saviq> mzanetti, i.e. maximize → minimize → launcher should be maximized, but is restored
[10:49] <mzanetti> really
[10:49] <mzanetti> that was intentional
[10:49] <mzanetti> ah no
[10:49] <mzanetti> that was with close in between
[10:49] <mzanetti> yes launcher always restores so far
[10:49] <Saviq> still, maximize should be stored along with geometry on close, IMO
[10:50] <Saviq> until you restore manually, it should always be maximized
[10:51] <mzanetti> hmm... indeed
[10:51] <mzanetti> Saviq, ack, will fix, but in a new branch
[10:51] <Saviq> mzanetti, sure
[10:54] <Saviq> dandrader, any pointer on testing the upsidedown fix? is there no bug for it?
[10:56] <dandrader> Saviq, this is actually a bug fix
[10:56] <Saviq> dandrader, I know, just wondering how to test it fixes ;)
[10:56] <dandrader> Saviq, bug description should say it
[10:56]  * dandrader looks
[10:57] <Saviq> right, bug not linked
[10:57] <Saviq> ah bug #1478637
[10:57] <Saviq> dandrader, ↑
[10:57] <Saviq> it was linked to the superseded branch
[10:58] <dandrader> Saviq, that's the one
[10:58] <dandrader> Saviq, and Nexus 7 is the device
[10:58] <Saviq> yup
[11:01] <dandrader> Saviq, fixed the bug title
[11:01] <Saviq> dandrader, yeah, Josh's branch doesn't fix the bug, though, I wonder if the fix for rotating external screen causes that
[11:02] <ltinkl> Saviq, the bug when focus is lost when you either minimize or close an app is fixed in my branch
[11:02] <ltinkl> Saviq, or should be :)
[11:02] <Saviq> ltinkl, ack
[11:03] <dandrader> Saviq, wonderful :). bitrotting at its best
[11:03] <dandrader> Saviq, looking into it
[11:03] <ltinkl> Saviq, also when you focus/activate a minimized window from the spread
[11:04] <Saviq> kk
[11:08] <Saviq> dandrader, fix for desktop doesn't matter, it's as if the branch didn't really change anything, landscape apps always go to Landscape, not InvertedLandscape
[11:08] <Saviq> dandrader, except the power-button workaround no longer works, either ;)
[11:09] <Saviq> dandrader, FWIW the branch is waiting for your vote anyway, since it was resubmitted https://code.launchpad.net/~unity-team/unity8/new_fix_upsidedown/+merge/275683
[11:09] <dandrader> Saviq, I don't get it. this bug fixes an issue that appears exclusively on the nexus 7 builtin display
[11:09] <Saviq> dandrader, oh and yeah, card for tests for this is good
[11:09] <Saviq> dandrader, yes
[11:09] <dandrader> Saviq, when you are on tablet stage
[11:10] <Saviq> dandrader, yeah, ignore my "desktop" comment, doesn't really bring anything into the discussion
[11:10] <Saviq> was just grasping at straws
[11:13] <Saviq> dednick, how can I verify bug #1475678?
[11:13] <tsdgeos> Saviq: ok, it's not as trivial as i thought, there's a PageHeadStyle.qml "copied with large modifications from Ubuntu UI Toolkit's Ambiance's theme" in our source code
[11:14] <Saviq> tsdgeos, sounds about right
[11:14] <dednick> Saviq: erm, kinda a pain to do. i did it by logging when the client switched buffers
[11:14] <tsdgeos> Saviq: so i'm going to work on it but may still want to land it since maybe i don't get it done today :D
[11:14] <dednick> but need to modify code
[11:14] <Saviq> tsdgeos, waiting for a few other bits, so we'll see
[11:15] <Saviq> dednick, wonder if I could get scenegraph to tell me in a small qml app
[11:16] <Saviq> greyback_, how difficult to turn on scenegraph logging?
[11:16] <Saviq> greyback_, to test whether it's rendering or not (thinking occlusion here)
[11:16] <dednick> Saviq: oh, yeah probably can
[11:16] <dednick> should just be a env var
[11:17] <Saviq> QSG_RENDERER_DEBUG=render
[11:17] <Saviq> let's try tha
[11:17] <Saviq> t
[11:17] <greyback_> Saviq: QSG_VISUALIZE=changes can go nice visual
[11:17] <Saviq> greyback_, well, I've to put the app in the back ;)
[11:18] <greyback_> Saviq: ah, I hadn't read up
[11:18] <greyback_> yeah, QSG_RENDER_TIMING=1 is similar
[11:19] <Saviq> ok, worky
[11:20] <Saviq> mzanetti, /me has a worry about mterry's isTouchApp... if we start displaying non-touch apps in launcher/dash unconditionally, dropping that line from the .desktop file will get your app around lifecycle
[11:21] <mzanetti> Saviq, well would also not allow to launch it in staged mode, no?
[11:22] <mzanetti> just display a message that this app can only be used in with external screen etc
[11:23] <mzanetti> but I see your concern, yes. will talk with mike about it when he comes on
[11:23] <Saviq> tx
[11:26] <dednick> when you use PropertyChanges and a Transition to animate a value change in a state, does the property always change to its final value before starting the animation? ie changing from 0 -> 10 goes: 10, 0, 1, 2, 3...10
[11:27] <dednick> mzanetti: ^ ?
[11:27] <mzanetti> I've seen that before too...
[11:28] <mzanetti> but don't remember what it was. I think I had been fiddling with the order of transitions/propertyactions
[11:28] <mzanetti> it's not always like that, but easy to get into that state
[11:33] <Saviq> dednick, sounds wrong
[11:34] <Saviq> mzanetti, one more thing came to mind... what happens in unity8-desktop-session-mir... if we stop filtering on touch, we'll show all .desktop files, and they won't run
[11:35] <mzanetti> Saviq, shouldn't they run eventually?
[11:36] <Saviq> mzanetti, maybe, eventually, not in the PD timeframe ;)
[11:36] <mzanetti> Saviq, well, the only thing we can do there is to add yet another key like: X-Ubuntu-Touch-Legacy
[11:36] <mzanetti> and filter on both
[11:37] <mzanetti> so the ones we support already would need to be patched for this key
[11:37] <Saviq> mzanetti, yeah I'm starting to think we'll need that
[11:37] <Saviq> mzanetti, well, that defaults to false, which means we don't need to change, we only need to add to new, legacy apps
[11:37] <mzanetti> yes
[11:37] <Saviq> mess :
[11:37] <Saviq> :/
[11:38] <Saviq> but what can you do
[11:38] <mzanetti> yes... not sure if it's worth it tbh
[11:38] <mzanetti> is unity8-desktop-session-mir something we officially support for endusers?
[11:38] <Saviq> it definitely is worth it, otherwise people who install desktop session will get all the apps that they can't run
[11:38] <Saviq> people don't ask ;)
[11:38] <Saviq> but will complain
[11:43] <tsdgeos> Saviq: pushed something that looks quite good to me, can you have a look?
[11:43] <tsdgeos> code is still not totally optimal as there's some copied stuff but much less than before
[11:44] <Saviq> tsdgeos, ack
[11:46] <Saviq> ok, time for a rebuild
[11:47] <Saviq> tsdgeos, looks fine IMO
[11:47] <Saviq> tsdgeos, got a conflict in the removal of PageHeadStyle.qml, but that's likely bzr being dumb again, silo should be fine
[11:48] <tsdgeos> Saviq: sorry i forgot to push use_quick_24
[11:48] <tsdgeos> i had merged it in there since otherwise there's a "you changed this file that is now removed" conflict
[12:09] <Saviq> tsdgeos, well, silo built fine so you made it in time
[12:09] <Saviq> tsdgeos, was conflict for me because I merged on top of quick_24
[12:10] <tsdgeos> k
[12:17] <tjaalton> any ideas who to blame when with scale factor 2 the external-monitor-only display mode is corrupted, this is in both vivid & wily at least
[12:18] <tjaalton> only the top-left part of screen is normal, then moving windows around leave traces on rest of desktop
[12:19] <tjaalton> I've only intel gfx to test with
[12:20] <tjaalton> so is it compiz/unity or intel dri driver, or..
[12:23] <greyback_> bregma: any ideas for tjaalton?
[12:24] <tjaalton> the laptop panel needs to have scale factor 2, external 1
[12:25] <bregma> any scale factor >= 2 will cause weird and bizarre problems in any GTK-based software
[12:25] <tjaalton> oh
[12:25] <tjaalton> is that documented somewhere?
[12:25] <tjaalton> and why is it selectable :)
[12:25] <tjaalton> some oem projects use that as the default...
[12:25] <tjaalton> on some models
[12:25] <tjaalton> which is also a trigger for some crashers it seems
[12:26] <bregma> I believe I may have opeened bugs somewhere a few years ago
[12:26] <bregma> it first manifested as running videos "full screen" in totoem would only be a quarter of the screen
[12:26] <bregma> I'm not sure where in the stack any of that happens
[12:26] <bregma> maybe Trevinho has an idea
[12:27] <Trevinho> tjaalton: it's nautilus issue
[12:27] <Trevinho> tjaalton: kill it and reload, it should fix it.
[12:27] <Trevinho> seb128: ^
[12:28] <tjaalton> Trevinho: ah
[12:32] <seb128> Trevinho, tjaalton, see #ubuntu-desktop backlog from 9:57 utc
[12:33] <tjaalton> seb128: hehe, what a coincidence :)
[12:34] <seb128> tjaalton, or same people applying nag on different groups ;-)
[12:34] <tjaalton> that too
[12:46] <mterry> greyback_, what editor do you use?
[12:47] <greyback_> mterry: QtCreator mostly
[12:47] <mterry> hmph
[12:48] <greyback_> mterry: since you understand the problem, could you look at https://code.launchpad.net/~unity-team/qtmir/1510571.ms-timestamp-compression/+merge/276112 and compare with your own approach?
[12:48] <greyback_> dednick proposed something equivalent to your fix
[12:48] <Saviq> mterry, hey, time for a quick mumble with mzanetti and me re: isTouchApp?
[12:48] <mterry> greyback_, so the line ending issue in that branch I submitted?  My editor (gedit) inserted a newline character at the end of the file.  But doesn't render it.  vi doesn't render it or let me delete it.  Nor does QtCreator (I can delete it, but it will insert it again when saving).  I don't know how you got your file in that state.  I'm going to have to hexedit to get it back
[12:49] <greyback_> mterry: nah, don't bother, it's not worth that kind of trouble
[12:49] <mterry> Saviq, sure
[12:50] <Saviq> mterry, greyback_, files should have a newline at the end, but that should show up everywhere, maybe it's just \r or something?
[12:50] <Saviq> mterry, ok, we're there
[12:51] <mterry> Saviq, no it's ascii 12
[12:54] <Saviq> bad gedit
[12:58] <mterry> Saviq, no... it's enforcing that files have a newline at the end.  As is QtCreator here.  I don't know how greyback_ made the file
[12:59] <Saviq> ;)
[12:59] <greyback_> wasn't me, blame dednick
[12:59] <greyback_> he's the vi guy. There's tab chars in there too
[13:01] <mterry> greyback_, speaking of, comparing the two branches, I think the outcome is the same.  dednick just makes the ulong type more "c++" by using a 'duration' type which knows how to convert to other time types.  So that's nice I guess
[13:01] <mterry> Seems better than my branch
[13:01] <dednick> my branch rules
[13:01] <dednick> :)
[13:02] <mterry> dednick, :)
[13:02] <dednick> sorry, i had the branch for awhile waiting to propose. didnt know it was causing an issue at the time.
[13:03]  * mterry shakes fist at dednick
[13:04] <mterry> These branches have had me looking at the API for these C++ time types...  And I love the specified sizes.  milliseconds is at least 45 bits.  microseconds at least 55 bits.  /me can't wait for the 55 bit processors of the future
[13:09] <dednick> yeah, it's a bit odd
[13:12] <greyback_> gotta love the C++ specs, types are defined "at least" bits
[13:15] <greyback_> mterry: if you're happy with dednick's branch, please +1 it and I'll do the test
[13:15] <greyback_> rest
[13:18] <mterry> dednick, I'm testing your branch to double confirm it fixes the problem in my u8 branch that noticed this.  That way you can tick off the manually-tested checkbox  :)
[13:21] <dednick> mterry: ta
[13:28] <mterry> dednick, looks good
[13:51] <dandrader> Saviq, fixed lp:~unity-team/unity8/new_fix_upsidedown
[13:51] <Saviq> dandrader, great, thanks
[13:59] <ltinkl> mzanetti, updated https://code.launchpad.net/~lukas-kde/unity8/activateWindows/+merge/275706
[13:59] <mzanetti> yep, saw it, thanks
[14:05] <Saviq> greyback_, shall I add https://code.launchpad.net/~unity-team/qtmir/1510571.ms-timestamp-compression/+merge/276112 to silo?
[14:05] <Saviq> 3...
[14:05] <Saviq> 2...
[14:05] <Saviq> 1...
[14:05] <Saviq> adding
[14:07] <greyback_> Saviq: yes
[14:07] <greyback_> just testing on device now
[14:07] <Saviq> greyback_, ok, building in silo, too
[14:17] <Saviq> /food
[14:30] <attente> Saviq: how can a client check if it should be using single-surface mode or not?
[15:02] <Saviq> attente, today, anything that has X-Ubuntu-Touch=true in its .desktop file needs to launch single-surface
[15:03] <Saviq> attente, we'll allow multi-window for the browser at some point in the near future, and for Xmir, but that's multi-window, not multi-surface, menus, tooltips etc. will need to be single-surface for now
[15:03] <attente> Saviq: isn't that used for unity 8 desktop too though?
[15:03] <Saviq> attente, that's still single-surface today
[15:03] <Saviq> attente, we don't really have window management in unity8 yet
[15:03] <attente> but at some point in the future we have to differentiate, right?
[15:04] <Saviq> attente, yes, at that point the app will likely get a hint in what usage scenario the device is working in, what input methods are available etc.
[16:51] <dandrader> dednick, looks like https://code.launchpad.net/~nick-dedekind/qtmir/lp1475678.surface-occlude/+merge/273426 is missing a prerequisite
[16:52] <dandrader> dednick, lp:~mterry/qtmir/no-touch-no-lifecycle
[16:53] <Saviq> dandrader, no need
[16:54] <dednick> dandrader: if you mean because it's in the unity8 branch, it was just to get to to bind together in the silo
[16:54] <dandrader> dednick, Saviq, It won't compile without it because of unity-api
[16:54] <Saviq> dandrader, that doesn't really mean it's a prerequisite in qtmir
[16:55] <tsdgeos_> Saviq: mzanetti: greyback_: https://code.launchpad.net/~aacid/unity8/dash_backgroud_source_size_rework/+merge/276157
[16:55] <Saviq> dandrader, if unity-api gets rebuilt without no-lifecycle for some reason
[16:55] <Saviq> dandrader, it will build
[16:55] <dandrader> Saviq, yes. but's not the current situation
[16:55] <Saviq> dandrader, but that doesn't mean the qtmir branch has the other as prerequisite, you could say the opposite just as well
[16:56] <Saviq> dandrader, and then, if it happens, we'd need to resubmit again
[16:58] <dandrader> Saviq, the fact is it won't build with the branches mentioned in the checklist. So it should at least mention in the checklist what it needs to build
[17:00] <Saviq> dandrader, truth is the unity-api branches shouldn't be prerequisites either
[17:01] <Saviq> because the only conflicting change there is the changelog, which could be solved easily by having the same change in both
[17:01] <Saviq> but I wasn't fast enough saying that to dednick before he already resubmitted :P
[17:02] <dednick> :)
[17:04] <dandrader> dednick, Saviq so here's the thing: I'm building those branches on my N7 to test them. the *only* way I can do it is by manually merging lp:~mterry/qtmir/no-touch-no-lifecycle on top of dednick's one.
[17:04] <dandrader> becasue unity-api and unity8 also got rebased
[17:05] <Saviq> dandrader, right, I can agree mentioning those in description would be usefuly
[17:05] <Saviq> -y
[17:06] <dednick> dandrader: in which one? qtmir or unity8
[17:06] <Saviq> dandrader, but they kind-of-are, since qtmir/occlude → unity8/occlude → unity8/lifecycle → qtmir/lifecycle ;)
[17:07] <Saviq> dandrader, but sure, I agree, not ideal
[17:07] <dandrader> I know this is just bureaucracy now since all people involved know the situation, but better not make an habit of it. this can get out of hand...
[17:07] <dednick> well i just added it to the mp list
[17:08] <Saviq> dandrader, luckily it's not often we land two unity-api changes in one silo
[17:08] <Saviq> dandrader, and we only made it prereq because they actually conflicted
[17:08] <Saviq> (unity8, that is)
[18:10] <dandrader> mzanetti, ping
[18:12] <mzanetti> dandrader, hey
[18:14] <dandrader> mzanetti, John Lea is tesing the mouse edge push, playing with parameters. But he's suffering with the slow mouse and asked for a way to adjust its speed. was thinking about adding a gsettings option for it so that we apply a multiplier for the relative movement we get from mir. that's as a temporary measure until mir's mouse relative movement has acceleration applied
[18:14] <dandrader> mzanetti, what do you think?
[18:15] <mzanetti> dandrader, what's the ETA on the proper solution?
[18:15] <dandrader> mzanetti, was going to aske anpok about it. but he didn't reply to my ping yet
[18:15] <dandrader> *ask
[18:16] <mzanetti> dandrader, well, you could certainly just put together a testing silo for John with that hack... whether we should land it or not, really depends on anpok's answer
[18:17] <dandrader> mzanetti, so far I'm doing old school and providing debian packages in a .zip + instructions :)
[18:18] <mzanetti> hehe, well, still, for testing that's probably ok... does the mouse have any acceleration atm?
[18:18] <mzanetti> because even if you double the speed, without some progressive acceleration he won't get the real feeling
[18:18] <dandrader> mzanetti, no. that interim solution would just serve to adjust speed. no acceleration at all
[18:18] <dandrader> mzanetti, right
[18:19] <mzanetti> I'd say it depends on him. if he wants to test it right now and is ok with no accel, give him some dpkg's but let's try to get the proper solution prioritized for the landing
[18:21] <dandrader> mzanetti, or, conversely, land the mouse edge push without the fine tuning and only do so once we get proper mouse acceleration from mir
[18:22] <dandrader> mzanetti, maybe it's not worth doing the fine tuning with the mouse the way it is today...
[18:22] <mzanetti> yes, works for me too
[18:22] <mzanetti> that's a good point
[18:41] <anpok> real feel .. hmm
[18:42] <anpok> i even got some push back because the mouse is now too fast.. with libinputs acceleration
[18:43] <anpok> brb swithcing networks
[21:00] <mterry> Saviq, I see you added the timestamp branch to silo 21.  I'll add my shutdown dialog branch back in too then
[21:01] <Saviq> mterry, right, should've done that
[21:02] <ltinkl> mterry, I committed the timezone fixes to the wizard, can you please rebuild the oobe silo? thx
[21:03] <mterry> ltinkl, rebuilding now
[21:40] <mterry> ltinkl, looks like I need to update my branch from trunk.  will do that in a bit and rebuild
[22:17] <mterry> ltinkl, updated my branch and rebuilt the silo.  seems to be building fine so far
[22:17] <ltinkl> mterry, great, thx :)