| === chihchun_afk is now known as chihchun | ||
| === chihchun is now known as chihchun_afk | ||
| === JanC_ is now known as JanC | ||
| === chihchun_afk is now known as chihchun | ||
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| === JanC is now known as Guest38106 | ||
| === JanC_ is now known as JanC | ||
| duflu | Some numbers to end the week on... | 09:50 |
|---|---|---|
| duflu | https://docs.google.com/spreadsheets/d/1RbTVDbx04ohkF4-md3wAlgmxbSI1DttstnT6xdcXhZQ/pubchart?oid=1566479835&format=interactive | 09:50 |
| greyback | duflu: thanks for taking on the subpixel bits for me | 09:57 |
| greyback | and nice chart | 09:58 |
| duflu | greyback: No problem. I needed some smaller tasks to end the week cleanly | 09:59 |
| greyback | duflu: adding the set-subpixel feature was a good idea too | 10:00 |
| greyback | I can see us exposing that in settings | 10:00 |
| duflu | greyback: For some reason I was imagining a GUI for it a long time and forgot the API didn't exist | 10:00 |
| duflu | Not sure if we've got output events wired up to that yet | 10:01 |
| greyback | duflu: I'm not sure of the value of surface output event, aside from saying "hey, you're not on this screen" | 10:01 |
| greyback | IMO the client can then read what it wants from the screen/display config | 10:01 |
| duflu | greyback: It lets you abstract things about the outputs (like the most appropriate refresh rate or scale, which might not match any one real output) | 10:02 |
| greyback | uhh, I meant, "hey, you're *now* on this screen" | 10:02 |
| duflu | Anyway, gotta run | 10:02 |
| greyback | duflu: if you say so. That sounds pretty special | 10:02 |
| greyback | duflu: have a nice weekend! | 10:02 |
| duflu | greyback: vsync now relies on it :) | 10:02 |
| duflu | Bye | 10:03 |
| === chihchun is now known as chihchun_afk | ||
| aquarius_ | alf_: are you the person I should talk to if I have repowerd questions? :) | 12:22 |
| alf_ | aquarius_: sure, what's up? | 12:22 |
| aquarius_ | alf_: basically, I'd like to temporarily prevent the screen on an ubuntu phone from being locked (either by timeout or by power-button press), but I'd also like to be notified somehow when the power button *is* pressed. | 12:24 |
| aquarius_ | I could just stop repowerd, but then it stops monitoring the power button, and so I can't listen for its d-bus signals. But I don't know how to tell repowerd to ignore power button presses and not lock the screen | 12:25 |
| alf_ | aquarius_: it's not possible to tell repowerd to ignore the power button. However, repowerd gets the original power button signals from the com.canonical.Unity.PowerButton service which is implemented by unity-system-compositor. | 12:28 |
| alf_ | aquarius_: so you could stop repowerd and listen on the PowerButton interface | 12:29 |
| aquarius_ | oh! repowerd doesn't actually monitor the button itself? | 12:29 |
| aquarius_ | that would explain why I can't find the code that does it then :) | 12:29 |
| aquarius_ | so I could, temporarily, stop repowerd and then listen for signals on com.canonical.unity.powerbutton | 12:30 |
| aquarius_ | and then later restart repowerd | 12:30 |
| alf_ | aquarius_: right, you will get Press and Release signals. Note, however, that you will not get a LongPress signal, since it's repowerd that emits that. | 12:31 |
| aquarius_ | that's fine | 12:32 |
| aquarius_ | excellent! thank you very much | 12:32 |
| alf_ | aquarius_: you are welcome | 12:32 |
| elopio | good moning AlbertA! are you ready for today? | 15:04 |
| AlbertA | elopio: sure what time again? | 15:06 |
| AlbertA | ahh 11, ok | 15:06 |
| elopio | AlbertA: yes, in two hours, thanks. I'll set up the hangout and make the announcements. Let me know if I can help you with something. | 15:10 |
| alan_g | bschaefer: workspace-example is ready for breaking again | 15:15 |
| bschaefer | alan_g, excellent! | 15:15 |
| bschaefer | ooo fancy shortcut intro | 15:17 |
| bschaefer | huh ... i need to figure out how to reproduce this our get some debugging messages... as going from workspace 1 ---> 2 and the window that *should* be on 2 isnt there | 15:19 |
| bschaefer | but going from 3 ---> 2 and it shows up | 15:19 |
| bschaefer | huh ... this is just really strange when it gets in this state | 15:21 |
| * bschaefer attempts to reproduce | 15:21 | |
| alan_g | --window-management-trace is my favourite debugging tool | 15:22 |
| * alan_g just needs to cut the excessive and unnecessary verbosity | 15:22 | |
| bschaefer | o yeah forgot about that | 15:23 |
| * bschaefer adds that and sees if maybe some key is stuck down | 15:23 | |
| * alan_g should have found keys U7 doesn't eat | 15:24 | |
| bschaefer | huh miral doesnt seem to like it when i close it with ctrl+alt+del | 15:29 |
| bschaefer | twice in a row its caused just a black screen that I couldnt recover from | 15:29 |
| alan_g | ctrl+alt+BkSp? | 15:29 |
| bschaefer | o yeah backspace | 15:29 |
| bschaefer | [2017-02-17 07:26:26.824675] miral::Window Management: for_each_workspace_containing window=@æ^BÄX^? | 15:29 |
| bschaefer | that looks strange? | 15:29 |
| bschaefer | [2017-02-17 07:26:27.062148] miral::Window Management: for_each_workspace_containing window=pÇ^BÄX^? | 15:29 |
| alan_g | It does. Log it I'll fix the logging. | 15:30 |
| bschaefer | alan_g, at some point, one window gets stuck on all workspaces | 15:30 |
| bschaefer | but i wasnt sure if ctrl was stuck down (doesnt seem like it) | 15:30 |
| alan_g | Odd | 15:30 |
| alan_g | I've not seen that (yet) | 15:31 |
| bschaefer | yeah ... i need a way to reproduce it, it seems to be meta + alt f1/f2 with two windows then taking a window from f1 and meta + ctrl onto f2 | 15:31 |
| * bschaefer will attempt to reproduce it a bit better | 15:31 | |
| attente | does mir have vulkan support? | 15:36 |
| alan_g | bschaefer: you're commenting on a superseded version of the MP | 15:37 |
| bschaefer | thought i clicked on the new one | 15:39 |
| bschaefer | o a second time | 15:39 |
| bschaefer | alan_g, found a way to reproduce | 15:39 |
| bschaefer | alan_g, hopefully *thats* a correct way to reproduce | 15:43 |
| bschaefer | hmm you dont need to hold the hot key down, but i seem to be able to reproduce it 100% of the time now | 15:46 |
| bschaefer | annd dont need to do any alt + meta stuff in the beginning | 15:49 |
| * bschaefer re-writes reproduction | 15:49 | |
| greyback | attente: not yet, camako was working on it but I think pulled onto other things | 15:55 |
| bregma | attente, camako can correct me if I'm wrong, but Mir out of the box does not yet have WSL support for obtaining a Vulkan context when using Mir, it's currently EGL-only | 15:55 |
| camako | attente, at some point it worked, but needed presentation chain API to be published... In the mean time, there has been a lot of Vulkan work in Mesa. Now that presentation chain support has been published in Mir, I need to refresh the Mesa patch for Vulkan. | 15:58 |
| AlbertA | elopio: do you have a hangout link so I can setup? | 16:38 |
| elopio | AlbertA: https://hangouts.google.com/call/hmcpgwejwff3znwobjy77snwzie | 16:39 |
| elopio | and anybody else from the team who wants to join ^ | 16:39 |
| AlbertA | kgunn: ^ ? | 16:49 |
| * alan_g wonders what it is | 16:50 | |
| * kgunn also wonders | 16:55 | |
| AlbertA | alan_g: it's an ubuntu-on-air session | 16:55 |
| kgunn | AlbertA: i may hop on a ho with willcooke here in a second....but i'll at least join irc | 16:55 |
| willcooke | kgunn, just getting near to wrapping here I think, won't be much longer | 16:56 |
| elopio | thanks a lot AlbertA :) | 17:44 |
| AlbertA | elopio: np | 17:59 |
| alan_g | bschaefer: another iteration of workspaces-example ready for breaking | 18:04 |
| === JanC is now known as Guest50386 | ||
| === JanC_ is now known as JanC | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!