/srv/irclogs.ubuntu.com/2015/10/08/#ubuntu-mir.txt

=== chihchun_afk is now known as chihchun
RAOFOn the plus side, I'm maybe a third of the way into making QtMir handle multiple bufferstreams.05:33
=== chihchun is now known as chihchun_afk
RAOFOh, yeah.05:49
RAOFLots of QSimulcrumOfStl, but it's all slightly worse.05:49
RAOFAlthough I guess CoW is pretty cool.05:50
anpok_simulcrum?05:54
RAOFSumulcrum?05:59
RAOFSimulcrum?05:59
anpok_Q?05:59
RAOFMy standard misspelling of simulacrum.05:59
RAOFhttps://www.wikiwand.com/en/Simulacrum05:59
RAOFFor those not familiar with the obscure brand of English I sometimes spout.06:00
anpok_oh I thought of something like simula cruft..06:00
anpok_which didnt really fit06:00
dufluRAOF: Recently discovered Qt logging doesn't understand std::string, but instead requires construction of QString from std::string first. That was odd06:11
anpok_test06:41
=== marcusto_ is now known as marcustomlinson
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
alan_ggreyback: does the CI failure mean anything to you? It doesn't seem related and I've not reproduced (but not tried to set up identical environment yet). https://code.launchpad.net/~alan-griffiths/qtmir/test-harness-for-MirWindowManager/+merge/26736910:00
greybackalan_g: looks unrelated yes. Something else is broken in CI10:01
=== chihchun is now known as chihchun_afk
Saviqhey guys, there's an email thread on phone ML, someone's having issues with DPI not being reported by QScreen, so likely it's not set by... and now the question - by what? graphics driver?11:24
Saviq(the subject is "help with touchscreen configuration...")11:25
Saviqtvoss, you might know ↑11:27
greybackSaviq: qtmir/qtubuntu supply it if they can, but they don't currently. Qt will calculate it from physical and logical screen size11:28
greybackwhich again may not be accurate11:28
greybackI think I may have improved the situation in the multimonitor work actually11:29
greybackah no, it was there before11:29
Saviqgreyback, still, those values should come from the graphics driver, if they're bad, not much we can do (other than saying: ok, these are dumb, we'll just invent some values that make more sense)11:29
Saviqgreyback, can you please reply on the ML?11:30
greybacksure11:30
=== alan_g is now known as alan_g|lunch
* guest42315 EWWWW mailing lists 11:34
anpokoh11:57
anpokbut we dont calculate the physical size through the touchscreen..11:59
=== alan_g|lunch is now known as alan_g
ogra_how would you "calculate" that ?12:02
anpoki believe we get that info from hwc..12:03
ogra_you dont know how physically big a pixel actually is12:03
ogra_could be 0.01mm or could be 3cm ...12:03
anpokwell as already said hwc provies dpi in both directions .. I thought the above was related to touch screens.12:06
anpok.. and so far I havent found a single touch screen driver that provides that info..12:07
ogra_right12:15
ogra_usually you get the resolution boundaries only12:15
ogra_(for touch)12:15
ogra_and if you are lucky an offset12:15
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
seb128is anyone looking at landing mir 0.16.1 to wily to fix the current build issue?13:48
guest42315uuu mir 0.1813:54
alan_gseb128: I thought 0.16.1 landed a while ago. What is "the current build issue"?13:55
seb128alan_g, it landed in vivid-overlay, not wily13:55
seb128alan_g, and the build issue is basically what is described in the fix, http://bazaar.launchpad.net/~mir-team/mir/0.16/revision/295113:56
alan_gOh, I thought that was duel landed (before FF).13:56
seb128CI team changed dual landing to go to the ppa for wily rather than the archive13:56
seb128so maybe that's where it went13:57
seb128in which case somebody need to copy it over to wily13:57
alan_gI though 0.16.1 was before that, but I expect you're right that it didn't.13:58
alan_gvogons: can anyone clarify^^?14:00
kgunnalan_g: seb128 is this the mesa build fix ?14:02
seb128kgunn, yes14:02
kgunnthat was actually 16.2 i thot14:02
kgunnwhich didn't quite make it14:02
kgunni bet14:02
kgunnon the hairy edge14:02
* alan_g wonders if https://bazaar.launchpad.net/~mir-team/mir/0.17/revision/3005 would be useful too?14:02
alan_gkgunn: we haven't done a 16.2 (yet)14:03
seb128kgunn, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/5473299/+listing-archive-extra14:03
seb128kgunn, that suggests it's 0.16.114:03
alan_g"Copied from ubuntu wily"14:04
seb128https://launchpad.net/ubuntu/+source/mir14:05
alan_gseb128: so in answer to your original question: no. ;)14:14
seb128k14:14
seb128can we get something assigned to sort that out? ;-)14:14
kgunnseb128: do you need it in a rush ?14:15
seb128kgunn, no, but this week or next I guess14:15
seb128before wily is out14:15
kgunneh14:16
alan_gseb128: do you want a fix for lp:1503450 too?14:16
alan_gOr is 16.1 enough?14:16
kgunnalan_g: yeah, wondering, should we just punch mir0.17 in as the final for wily ?14:17
seb128bug #:150345014:18
alan_gkgunn: if someone can get us a FFE14:18
seb128bug #150345014:18
ubot5`bug 1503450 in Mir "mesa FTBFS due to missing Requires in mirclient" [High,Fix committed] https://launchpad.net/bugs/150345014:18
seb128I think that would be worth including14:18
alan_gSo we either cherry pick -c 3005 to make 16.2 or add wily to the current "duel" release of 0.1714:21
seb128dual landing don't land to the distro anymore though14:22
seb128but you can probably pocket copy over14:22
alan_gseb128: ack.14:23
kgunnyep, doubles testing altho vs risk of mir0.17 hitting some bumps and taking longer14:25
alan_galf: opinion? ^^14:33
alfkgunn: alan_g: Can we release to wily independently? That is land in overlay (v+w) first, then try for wily, and if we have problem we can think about 0.16.2?14:38
kgunnalf: we should do dual landing regardless...yes, and then try to poke the whole thing into wily with FFE14:40
kgunnalf: so mzanetti currently has his phone in the state where is will not screen blank14:41
kgunnwith the ota7 candidate14:41
kgunnis there any debug to be had ?14:41
kgunnbasically this bug https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/150214514:42
ubot5`Ubuntu bug 1502145 in unity-system-compositor (Ubuntu) "rc-proposed r140, krillin: screen does not blank after timeout expires" [Undecided,Confirmed]14:42
alfkgunn: not really, I guess we could get a backtrace, but previous backtraces in this situation didn't provide any info (everything seemed normal). I need to find a way to reproduce this, so I can run with a special USC build with extra logging to figure out what's going on (e.g. if some other process has asked USC to keep the screen on, or there is some strange bug in USC)14:43
kgunnalf: do you have a special usc available ? since mzanetti is trying to repro he may as well load it14:45
alfmzanetti: ^^ Any information about how you got into this state? Any other apps open etc14:45
alfkgunn: No, I wanted to build one but was too busy with the release14:46
mzanettialf, no... just doesn't turn off any more ever since I did an OTA last night14:46
alfmzanetti: so it doesn't turn off consistently or is this a one-off?14:46
anpoksomething like powerd-cli list/stats..14:46
mzanettiand for faenil that seems to be the case too since monday (I didn't do the update earlier because I was travelling)14:46
mzanettialf, consistently, sometimes it even turns itself on and doesn't go off any more14:47
alfmzanetti: ok, which device is this?14:47
alfmzanetti: I guess pressing the power button turns the screen off, right?14:47
mzanettialf, krillin, yes power button works14:48
alfmzanetti: how do I flash OTA7 on the phone?14:49
alfmzanetti: I mean to which revision in the stable channel does it correspond? The latest stable?14:50
kgunnalf: latest rc-proposed14:51
kgunnwell....14:51
kgunnlandings are open (but damn close)14:51
alfmzanetti: kgunn: I wonder if there is a difference in flashing clean vs updating... perhaps there could be an incompatibility in settings when updating14:51
alfmzanetti: ah, one thing to try...14:52
alfmzanetti: gsettings get com.ubuntu.touch.system activity-timeout14:53
alfmzanetti: and gsettings get com.ubuntu.touch.system dim-timeout14:53
mzanettialf, this is the OTA-7 channel ubuntu-touch/rc/bq-aquaris.en14:53
mzanettialf, it will become stable when we finally release it14:53
alfmzanetti: ack14:54
mzanettialf, should be *very* similar to rc-proposed atm, but that is opened for new landings again14:54
mzanettiso rc-proposed might have additional stuff on top already14:54
kgunnyeah but nothing landing frmo us14:55
alfmzanetti: when you get the chance please get the gsettings mentioned above15:00
alfmzanetti: I want to check if we are ok on the settings side of things15:01
mzanettioops. missed that... getting it now15:01
mzanettialf, uint32 6015:01
mzanettiand uint32 4515:02
alfmzanetti: ok, these look sensible15:03
mzanettiso far can't repro on mako15:03
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== alan_g is now known as alan_g|EOD
mhall119does Mir recognize mouse-wheel scrolling and pass it on to Unity 8?18:12
mhall119I have a bluetooth mouse connected to my N4, and it all works except the scroll wheel18:12
=== dandrader is now known as dandrader|afk
=== \b is now known as benonsoftware
anpokmhall119: it should19:48
anpokmhall119: https://code.launchpad.net/~lukas-kde/qtmir/wheelEvent/+merge/27315019:51
mhall119anpok: ok, so it's not landed yet, but the implementation has been done19:53
=== dandrader|afk is now known as dandrader

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!