[06:10] <deef> i already asked for my problem with my BQ M10, which doesn't connect to some WIFI networks, but nowhere I can find something pointing at the problem
[06:11] <deef> anyone with the same problem over here?
[07:25] <kaisoz> hi there :)
[07:25] <duflu> deef: Yes there's a regression in OTA-11 and OTA-12 that makes it fail to connect to some networks that have long passwords (like mine). It's fixed in OTA-13. Or to work around it start on OTA-10 to set up your wifi before upgrading
[07:27] <MCMic> duflu: How good news I noticed there is a wifi I can’t connect to, maybe it’s this bug I’ll have to try this with OTA-13
[07:28] <duflu> Yeah if you flash your device with --revision=NNN where NNN is the build number of OTA-10 for your device then you can work around it. Then upgrade to newer OTAs without problem
[07:29] <duflu> OTA-13 is due next week in theory \o/
[07:35] <duflu> "Expected 2016-08-24" https://launchpad.net/canonical-devices-system-image/+milestone/13
[08:03] <robinhero> duflu, this was the expected ETA, but they postponed OTA-12 with one week, and the will postpone OTA-13 with one week too. there's no official release date, but it will be the first-second week of September
[08:04] <duflu> robinhero: Yes I said "due" and the page says "Expected", which has not been updated to reflect any delays. But delays are normal
[08:25] <zzarr> how do I install Qt 5.6 in a schroot?
[08:32] <zzarr> do I install landing 024?
[09:25] <deef> maybe a silly question but how do i install OTA 10 starting from OTA 12?
[09:25] <deef> or downgrade in other words?
[09:28] <popey> deef: system-image-cli has command line options to do that directly on the device
[09:28] <popey> deef: or ubuntu-device-flash can do it from the pc
[09:28] <davmor2> deef: why?
[09:29] <deef> my new bq m10 ubuntu touch OTA 12 does not connect to my wifi at home, elsewhere it does
[09:29] <deef> this is a known issue apparently in 11 and 12
[09:30] <popey> you could move to the rc-proposed channel
[09:30] <deef> so I have to use 10 to connect to my wifi
[09:30] <popey> which is newer, and apparently fixes the issue
[09:30] <popey> rather than go backwards
[09:30] <deef> how do I do that popey?
[09:30] <popey> system-image-cli has an option to change channel too :)
[09:30] <deef> (quite new into linux sysadmin)
[09:32] <popey> on the device, in the terminal, do this:- (however, this will move you to the daily builds channel which may break - they generally don't and aren't for end users)
[09:32] <popey> you could switch back to the stable channel once OTA-13 is out though
[09:33] <popey> sudo system-image-cli --switch ubuntu-touch/rc-proposed/bq-aquaris-pd.en
[09:33] <popey> that's what my m10 is running
[09:35] <deef> ok i ' try that one popey
[09:35] <duflu> deef: Note that using rc-proposed is less stable than the 'stable' channel. If you want a fix for the stable channel you need to start with OTA-10 and configure wifi before upgrading
[09:36] <duflu> Hmm, although in this case it's both less 'stable' and less buggy
[09:37] <iolc_observing> Morning guys, ive managed to get boot started on the port I'm working on but seem to be snagging somewhere near the lxc container and also getting adbd working. I'd really love to just get adbd working at the moment. Could anybody give me a little help please?
[09:38] <popey> john-mcaleely: ^ do we have anyone who could help?
[09:38] <john-mcaleely> popey, the best bet is ondra. I think he is doing the august-holiday thing at the moment
[09:39] <popey> ah
[09:40] <john-mcaleely> iolc_observing, popey, maybe abeato would also know how to get adbd alive?
[09:40] <john-mcaleely> but if not, it's wait for ondra, I htink
[09:40] <iolc_observing> thanks guys
[09:41] <abeato> iolc_observing, are you using the development adbd?
[09:42] <iolc_observing> yes
[09:42] <deef> duflu: can you give me the command to go to OTA 10?
[09:42] <duflu> deef: Just a sec
[09:43] <iolc_observing> I have it showing in lsusb but no adb
[09:44] <deef> duflu: ok thx!
[09:44] <duflu> deef: Is it frieza or coller?
[09:44] <duflu> cooler
[09:44] <duflu> Oh, same command either way
[09:44] <duflu> deef: OTA-10 is stable image #2 so:   ubuntu-device-flash --revision=2 touch --channel=ubuntu-touch/stable/bq-aquaris-pd.en ....
[09:45] <yutio> Hey guys I'm new here.. I would like to port ubuntu-touch for a board namd ham.(Lenovo Zuk Z1)It runs Qcomm SD 801 and Adreno 330..(like nexus 5 I guess) .. It has official cyanogen support too.
[09:46] <zzarr> I have some issues with OTA-12 as well (came in OTA-11) I have to click the hotspot slider many times before the icon appears
[09:46] <zzarr> and some times the phone hangs after I have ended a call
[09:46] <iolc_observing> here's my latest dmesg http://paste.ubuntu.com/23069643/
[09:47] <abeato> iolc_observing, maybe you will need to modify adb related jobs in /etc/init/
[09:48] <abeato> iolc_observing, trying to make sure http://paste.ubuntu.com/23069657/ gets executed in all cases
[09:48] <mardy> jgdx: hi! is the ubuntu-system-settings not installable on s390x? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-090/+build/10637500
[09:49] <yutio> Can you guys get me started
[09:49] <yutio> That porting guide is somewhat vague
[09:50] <iolc_observing> Thank you abeato
[09:51] <abeato> iolc_observing, do you have access to recovery image? a trick we use some times is to write stuff in the filesystem while starting ubuntu, then check what was written from recovery
[09:52] <iolc_observing> Yes, i do have access to recovery
[09:53] <abeato> iolc_observing, so that is an option too :) , you just have to mount userdata to see what was written
[09:53] <iolc_observing> brilliant, thank you
[09:54] <abeato> np
[09:58] <abeato> iolc_observing, taking a look at your dmesg output it seems that it is not finding adbd:
[09:58] <abeato> [    9.852160] init: Failed to spawn adbd main process: unable to execute: No such file or directory
[09:58] <abeato> make sure it is executable
[09:58] <abeato> and check the path
[10:01] <iolc_observing> abeato: thank you
[10:02] <deef> cannot install ubuntu-device-flash due to lock, ... howto avoid that one?
[10:02] <abeato> yutio, what would you like to know?
[10:06] <duflu> deef: You system is doing a background update. You just need to wait a while and then it will work
[10:06]  * duflu -> weekend
[10:06] <ogra_> abeato, thats not the init you are looking for (thats the android one)
[10:07] <ogra_> (we explicitly removce the in-container binary before container startup to avoid clashes with the ubuntu adbd, but not the init.rc lines for it, so that message is normal)
[10:09] <abeato> ogra_, oh, right, forgot that.  iolc_observing, that message seems to be normal ^^
[10:09] <ogra_> iolc_observing, you need to change the /etc/init/android-tools-adbd.conf job on the filesystem and chane the "start on" line (try making it "start on startup" or some other early job)
[10:12] <iolc_observing> awesome, thank you ogra_
[10:21] <iolc_observing> thanks for the help guys, really appreciate it. All the Best
[10:47] <mcphail> Are the bluetooth connectivity fixes scheduled for OTA13 already in rc-proposed?
[10:59] <popey> mcphail: do you have a bug ?
[11:08] <mcphail> popey: yes - I'm one of the unluck many on the "can't connect to car bluetooth" megabug
[11:09] <mcphail> https://bugs.launchpad.net/bugs/1435040
[11:14] <mardy> seb128: hi! Is System Settings installable on s390x?
[11:14]  * popey wants to know what phone mardy has which is powered by s390x
[11:14] <popey> and what the battery life is like
[11:14] <mardy> seb128: I cannot build OA for s390x in yakkety, it looks like a dependency is missing: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-090/+build/10637500
[11:15] <popey> mcphail: doesn't look fixed
[11:15] <mardy> popey: BQ s390x edition, battery life is good, it lasts more than one minute when fully charged ;-)
[11:16] <mcphail> popey: hokay. Ta. I'll try to be patient!
[11:16] <popey> :)
[11:16] <popey> mcphail: poke pmcgowan when he's about, he knows status of all things
[11:17] <mcphail> popey: it's fine. Was just wondering whether to risk a reflash just now or await updates
[11:17] <mcphail> popey: if we get working bluetooth _and_ owncloud calendar sync in OTA13 I'll be chuffed
[11:26] <kal_cividFajdida> hi, es posible instalar #ubuntu-touch en un huawei? donde descargary algun manual para instalar?
[11:30] <oSoMoN> Mirv, do you happen to have a working yakkety machine/VM ?
[11:31] <oSoMoN> I’d like to test something for bug #1613258 but I can’t install a yakkety VM, the installer keeps crashing
[11:42] <mcphail> Hmm. Did a wipe/reflash to OTA12 (having been lurking on OTA10.5) and I can't phablet-shell to my device. I'm getting "Permission denied (publickey)" on my client and "error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key" in /var/log/auth.log on the device. Am I doing something wrong? I have the correct pubkey in the authorized_keys file in /home/phablet/.ssh
[11:42] <Mirv> oSoMoN: plenty. couldn't you just build in a silo?
[11:43] <oSoMoN> Mirv, well I don’t wanna test a fix, I want to test whether a simple oxide webview can be displayed by qmlscene
[11:44] <popey> mcphail: it has a popup these days on the device to allow phablet-shell access
[11:44] <popey> you may need to disable / re-enable dev mode
[11:44] <popey> and have it unlocked when you try to shell in
[11:44] <mcphail> popey: yes -allowed the popup
[11:44] <popey> (to see it)
[11:44] <popey> hm, odd
[11:44] <mcphail> I'll try disable/reenable
[11:45] <Mirv> oSoMoN: oh right, you'll need proposed then, I don't want to upgrade to that but I've lxc here that is such
[11:47] <Mirv> oSoMoN: not 100% sure if then in lxc I get everything in identical way, but sure enough it does not start: http://pastebin.ubuntu.com/23070058/ - it does not exit at that point, just hangs in there without displaying anything. eg a QtWebkit browser however works
[11:47] <mcphail> nope. Still denied. Do I need to "android-gadget-service enable ssh" to get phablet-shell working? I don't think I had to in the past
[11:47] <oSoMoN> Mirv, that looks very similar to the webbrowser-app build failure, which seems to confirm it’s a bug in oxide
[11:48] <oSoMoN> thanks for testing!
[11:48] <Mirv> oSoMoN: you're welcome!
[11:54] <robinhero> guys, where can I find the Camera config files? I'd like to delete it
[11:54] <robinhero> I thought it is there: .local/share/
[11:55] <robinhero> but can't find it
[12:00] <robinhero> found it, it is under .config/com.ubuntu.camera
[12:05] <seb128> mardy, check on #ubuntu-ci-eng, they have been deleting binaries on s390x because upstart is missing which makes u-a-l and others missing as well
[12:06] <mardy> seb128: thanks
[12:06] <seb128> yw
[12:07] <seb128> mardy, btw I confirmed the desktop only account facebook/win is too small thing on yakkety, unsure if you saw my comment on the bug
[12:07] <mardy> seb128: yes, unfortunately I cannot test it because I get an oxide crash...
[12:07] <seb128> hum, k
[12:40] <mcphail> popey: solved the phablet-shell issue. Looks as if DSA keys are now disbaled by default on the _client_ 16.04 machine. Time to update my keys on 100000 servers...
[12:48] <kaisoz> I'm having a look to this bug from the band-aids project
[12:49] <kaisoz> https://bugs.launchpad.net/band-aids-uphone/+bug/1378814
[12:49] <kaisoz> I would like to work in this bug...is this going to be fixed?
[12:50] <alecu> kaisoz: due to the age of the bug, it sounds like nobody is working on it.
[12:50] <alecu> pete-woods: do you know who worked in the UI side of infographics?
[12:51] <alecu> pete-woods: kaisoz wants to cut his teeth on some simple tasks, so he's looking at bugs in band-aids-uphone
[12:52] <pete-woods> alecu: right, I can't remember the guy's name, but he doesn't work at Canonical any more
[12:52] <popey> mcphail: ahhh, that's an issue I had on my home server too!
[12:53] <alecu> kaisoz: so yes: please assign it to you, and mark it as in progress
[12:53] <alecu> kaisoz: it does sound like a good place to start
[12:53] <kaisoz> awesome!
[12:53] <kaisoz> thanks alecu :)
[12:54] <alecu> kaisoz: I know that pete-woods worked on the backend of infographics, so please ping me or him if you need any help.
[12:54] <kaisoz> perfect :)
[12:54] <kaisoz> thx!!!
[12:55] <pete-woods> kaisoz: I did some refactoring work on the early QML code for the infographics, but I think the code has changed hands several times since then
[12:55] <pete-woods> so it might not look like anything I was familiar with
[12:56] <kaisoz> ok
[12:57] <kaisoz> thx for the info :)
[12:57] <kaisoz> I'll have a look at the code and let you know if I need some help :)
[13:03] <kaisoz> have to go, see u later!! :)
[13:43] <mcphail> I've flashed rc-proposed, and my wifi connection doesn't seem to be getting DNS. How can I debug this?
[13:43] <mcphail> I can ping and access sites by address, but not by name
[13:59] <pmcgowan> awe, ^^
[14:01] <awe> mcphail, there's a longstanding bug that sometimes dnsmasq may not respond properly to dns queries when switching from WiFi to mobile data ( or visa versa )
[14:01] <mcphail> awe: can i poke it back into life?
[14:01] <awe> it should just start working by itself
[14:02] <awe> mcphail, what device are you running?
[14:02] <mcphail> awe: krillin (bq4.5)
[14:02] <mcphail> awe: had it on wifi for an hour with no connection
[14:02] <mcphail> awe: back to 36 -> instantly worked
[14:02] <mcphail> 3G*
[14:03] <mcphail> Back to wifi -> nada
[14:03] <awe> that's odd.  so the phone showed it was connected to your AP, but no DNS
[14:03] <awe> and it never recovered...
[14:03] <awe> have you tried another AP for comparison?
[14:04] <mcphail> awe: don't have access to another just now, but selected "forget network" and readded with no improvement
[14:04] <awe> if this is reproducible, then the best bet is to file a bug and start capturing the details there...
[14:04] <awe> mcphail, do you have other devices working with the same AP?
[14:04] <mcphail> awe: yes - everything else working OK
[14:05] <awe> is this is a new AP?
[14:05] <awe> or was your phone working fine with it, and then started acting up?
[14:05] <mcphail> awe: new for the phone, as it is a reflash today. Was working OK this morning before the flash
[14:05] <mcphail> awe: was on OTA 10.5 at that point, though
[14:06] <awe> but rc-proposed, right?
[14:06] <mcphail> awe: rc-proposed since the flash, yes
[14:06] <awe> AFAIK, there's been nothing related to dns released, but I'll go ahead and flash my krillin to check
[14:07] <mcphail> awe: thanks!
[14:07] <awe> the last NM release we made, fixed a specific issue with WPA passwords
[14:07] <awe> ( unless someone else has been playing around with dnsmasq )
[14:07] <awe> pmcgowan, ^^???
[14:07] <awe> ;)-
[14:08] <pmcgowan> awe, dont think so, will look
[14:08] <awe> k
[14:09] <pmcgowan> 10.5 was a long time ago though
[14:18] <mcphail> Hmm. Working now. That's about 20 minutes from when I switched back to wifi
[14:22] <mcphail> And it has failed again...
[14:23] <pmcgowan> mcphail, bug #1270189
[14:23] <pmcgowan> awe, anything to grab for that?
[14:24] <pmcgowan> mcphail, thats a very old bug, although perhaps somehow made worse with recent nm upgrade
[14:24] <awe> pmcgowan, doubtful
[14:24] <awe> the only thing we touched recently was the timeout for passwords
[14:24] <mcphail> pmcgowan: don't think that would explain why name resolution keeps switching on and off
[14:25] <pmcgowan> awe,  he went from 10 to 12, so never ran on 11 if I understand it
[14:25] <awe> pmcgowan, I'll flash an image, but in the middle of something else right now
[14:25] <mcphail> pmcgowan: I had name resolution for a minute there, but then it stopped working again as I was browsing
[14:25] <pmcgowan> awe, so this is first experience using nm 12
[14:25] <pmcgowan> 1.2
[14:25] <awe> mcphail, have you checked from the command line
[14:25] <awe> this could be browser related
[14:26] <mcphail> awe: yes
[14:26] <mcphail> awe: can ping <IP_ADDRESS> but not any names
[14:26] <mcphail> awe: for a moment, though I _could_ ping names when the browser was working
[14:26] <mcphail> awe: then both stopped
[14:26] <awe> mcphail, intermittent DNS isn't something I've seen before
[14:27] <awe> so again, I'll try and reproduce as soon as I have a moment to do so
[14:27] <awe> I need to reflash my krilling
[14:27] <awe> it'd be helpful if/when you get a chance
[14:27] <awe> to see if this occurs with all APs, or just a specific AP
[14:27] <awe> and then as mentioned above, file a bug
[14:28] <mcphail> awe: I probably won't be near another AP I can connect to for a couple of days, but I'll try then
[14:28] <awe> davmor2, have you seen any issues with WiFi DNS with recent proposed images?
[14:28] <awe> mcphail, ok
[14:29] <davmor2> awe: nope
[14:29] <awe> k
[14:30] <mcphail> I'm going to go out to pick up the kids from school. Will see if I pass any public APs on the way
[14:30] <awe> k
[14:31] <davmor2> awe: I've seen it if a page is still loading and I move out of range and it flips to modem then nothing loads in browser, unless you close the session and reopen but that is a real pain to reproduce
[14:32] <davmor2> awe: that is a proper racy issue that might happen one in a thousand times
[14:32] <awe> davmor2, sure.. . in this case, it's not flipping, it's working, then not working, then working
[14:32] <awe> all on WiFi
[14:33] <davmor2> awe: yeap don't think I've seen that in a very long time
[15:14] <mcphail> I passed a supermarket on the way to the school. I could log on to their wifi captive portal (was redirected to the logon page) but I didn't want to give them my credentials to get beyond the portal. Don't know if that meant I got DNS or not, though. Certainly, it had a name in the address bar
[15:15] <mcphail> I'm quite happy to make this rw and install dig/traceroute/whatever you think could help debugging
[15:18] <Pixel_> hello
[15:20] <Pixel_> i have a sdl2 game, does anyone know if gamepad support is available?
[15:21] <Pixel_> it's pretty simple, i need to control the game with a game controller
[15:21] <mcphail> Pixel_: I'd guess it should be. bschaefer did the SDL code and would probably know
[15:21] <popey> as I said on telegram, you wont have access to the joystick devices
[15:21] <popey>  /dev/js0 etc
[15:21] <popey> (I have tried this already)
[15:22] <mcphail> :(
[15:22]  * bschaefer reads backlog
[15:22] <Pixel_> popey,  :(
[15:22] <bschaefer> yup
[15:22] <bschaefer> for sdl2
[15:22] <bschaefer> o
[15:22] <bschaefer> well last time i tried joysticks it worked on mir... but
[15:22] <bschaefer> they talk directly to the devices (not mir)
[15:23] <Pixel_> it also works with libertine
[15:23] <Pixel_> but i need it for Fishy Shooter
[15:24] <bschaefer> well popey has tested more then i have :) but i've not tried on U8
[15:24] <bschaefer> only on a mir demo server like a year or so ago
[15:25] <Pixel_> ok then, i guess i'll open a bug report
[15:25] <popey> i have a multi-mode joystick, it works in keyboard mode, but not in js mode, not tested recently but I dont think anything has changed recently
[15:25] <popey> also didn't you make this video? https://www.youtube.com/watch?v=eM9vDDc29P8
[15:25] <popey> "Ubuntu Phone keyboard, mouse, gamepad test
[15:25] <popey> Popescu Sorin
[15:25] <bschaefer> i mean SDL2 does the joystick on its own
[15:25] <popey> "
[15:25] <popey> :)
[15:25] <popey> Pixel_: happy to test a click if you want
[15:25] <bschaefer> theres no mir code that does this since SDL2 does all the talking to the joysticks/gamepads
[15:25] <popey> i have a bunch of controlers here
[15:26]  * bschaefer only has one
[15:26] <bschaefer> but theres a
[15:26] <bschaefer> Pixel_, in SDL2/tests
[15:26] <bschaefer> theres a controller test
[15:26] <bschaefer> you can use as well
[15:26] <bschaefer> but you said it works on libertine (x11)
[15:26] <bschaefer> soo hmm
[15:26] <bschaefer> that is strange
[15:26] <Pixel_> popey, i did, but it only shows that the gamepad is powered (leds are on :P)
[15:27] <popey> does the latest fishy have joystick support?
[15:27] <bschaefer> Pixel_, you should test testjoystick if you can (in SDL2/tests/testjoystick)
[15:27] <Pixel_> popey, yes
[15:27] <bschaefer> as all that does is joysticks
[15:27] <Pixel_> only for left/right dpad keys
[15:28] <Pixel_> and you need to plug the game controller before starting the game :>
[15:28] <Pixel_> bschaefer, i have a cheap gamepad :D and sdl2 complains that is unknown or something
[15:28] <bschaefer> o ... dang well
[15:29] <Pixel_> bschaefer, i installed steam, configured the game controller and exported the configuration
[15:29] <Pixel_> still nothing
[15:29] <popey> xbox360 is the one to test
[15:29] <popey> its well supported
[15:29] <Pixel_> export SDL_GAMECONTROLLERCONFIG="03000000ff110000313300001:b9,back:b8,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:b6,righttrigger:b7,"
[15:29] <Pixel_> popey, yep, xbox, ps
[15:29]  * bschaefer tested with xbox360 and it worked a bit ago :(
[15:29] <popey> check dmesg
[15:30] <popey> app probably trying to talk to /dev/js0 or /dev/joystick or something
[15:30] <bschaefer> but sadly, this would be 100% sdl2 issue (vs mir/u8) likely?
[15:30]  * bschaefer checks source code
[15:31] <Pixel_> bschaefer, SDL_NumJoysticks() returns 1
[15:31] <Pixel_> but SDL_IsGameController(0) returns false
[15:32] <bschaefer> Pixel_, but this controller works 100% fine on X11 SDL2?
[15:32] <Pixel_> bschaefer, mine, nope :D it's the same on X11
[15:33] <Pixel_> it worked well with sdl 1.2
[15:33] <Pixel_> i am not sure what changed in 2.x
[15:33] <bschaefer> Pixel_, this is how they add joysticks :| http://paste.ubuntu.com/23070509/
[15:33] <bschaefer> they iterate through 32 devices and check if its a supported joystick i assume
[15:33] <bschaefer> soo it seems to detect that its a joystick
[15:33] <bschaefer> but
[15:34] <bschaefer> it might not be pulling correctly or assuming something incorrect (data its polling out of device)
[15:34] <bschaefer> annd it does some ioctl stuff... with the device
[15:34] <bschaefer> Pixel_, but yeah this is a bug for SDL2
[15:34] <bschaefer> and you should write down what game controller you have
[15:35] <bschaefer> in a bug report (https://bugzilla.libsdl.org/)
[15:35] <Pixel_> it's a cheap controller :d "Serioux"
[15:35] <bschaefer> Pixel_, sdl1.2 ---> sdl2 is a huge difference a lot of things were re-written
[15:35] <Pixel_> http://s1emagst.akamaized.net/products/63/62645/images/img116305_24062009172323_350x350_dpoe.jpg
[15:36] <bschaefer> Pixel_, you can always dig around in SDL2/src/joysticks/linux/*.c to figure out *where* its failing
[15:36] <Pixel_> bschaefer, yeah :D btw.. the controller worked in steam big picture
[15:36] <bschaefer> but i assume that device isnt supported for some assumptions on SDL2s part
[15:36] <Pixel_> it said that it never heard of it and i should upload the configuration but it worked
[15:36] <bschaefer> steam uses X11 not SDL2 yet :(
[15:36] <bschaefer> (steam client wise)
[15:36] <Pixel_> oh :D
[15:37]  * bschaefer hopes one day :)
[15:37] <Pixel_> hehe :D
[15:37] <bschaefer> Pixel_, but you can see the check if its a joystick is a little low level: http://paste.ubuntu.com/23070515/
[15:37] <Pixel_> that would be nice :)) i can turn my tablet into a game console
[15:37] <bschaefer> they are talking directly to the device
[15:37] <bschaefer> which is ... usually not good for multiple device support :)
[15:39] <bschaefer> but if its showing up as a joystick it must be the polling of data out of the device thats failing (soo its like half supported)
[15:40] <Pixel_> bschaefer, canonical should send Ryan a tablet or a phone LOL :P
[15:40]  * bschaefer did the SDL2 porting for mir :)
[15:40] <bschaefer> though still needs some work
[15:41] <Pixel_> bschaefer, thanks for help, i have to go out for a while now
[15:41] <bschaefer> Pixel_, np! Good luck with that!
[16:44] <dobey> mcphail: that sounds like you did not get DNS. That is, all DNS lookups resolve to the captive portal IP
[16:45] <dobey> mcphail: if you could get around the portal by just typing IPs though, it sounds like they didn't built the portal very well :)
[16:59] <kaisoz> hi there
[17:01] <dobey> hi
[17:17] <Elleo> bschaefer: should SDL2 work with the SDL_WINDOW_OPENGL flag on mobile platforms? having a quick poke around with the urho3d engine which should support GLESv2, but I get errors from the mir backend about it being unable to get a valid egl pixel format when trying to create the SDL window
[17:18] <bschaefer> yeah it should
[17:18] <bschaefer> Elleo, IIRC theres an issue with it trying to use actual gl vs gles
[17:18] <bschaefer> but i thought i disable-video-opengl
[17:18] <bschaefer> for armhf
[17:19] <Elleo> bschaefer: ah, urho3d bundles its own copy of SDL that gets built with it, so I probably need to do that for its build too
[17:19] <bschaefer> o possibly yeah
[17:19] <bschaefer> you could also attempt to LD_PRELOAD=/other/sdl2/lib
[17:19] <bschaefer> (as long as they didnt break ABI or anything crazy with theirs)
[17:24] <Elleo> bschaefer: okay, will have a play; I think they statically link SDL into their engine, so I'd guess the LD_PRELOAD stuff wouldn't be an option
[17:25] <bschaefer> o that wouldnt be good
[17:25] <bschaefer> Elleo, you could check
[17:25] <bschaefer> ldd
[17:25] <bschaefer> just in case :)
[17:25]  * bschaefer isnt sure if thats open source but if it is you can attempt to set the configure flag --disable-video-opengl
[17:33] <Pixel_> bschaefer, hey :D managed to make SDL2 detect my gamepad :>
[17:33] <bschaefer> Pixel_, nice!
[17:33] <bschaefer> what was the issue?
[17:33] <Elleo> bschaefer: yeah, it's open source, I've got it building without opengl now
[17:34] <bschaefer> nice, hopefully that was the issue!
[17:34] <bschaefer> Elleo, since on armhf sdl2 just checks in gl/gl.h or w/e exists
[17:34] <bschaefer> it just checks the header to enable opengl support
[17:34] <bschaefer> which it gets installed with the .... (some package forgot)
[17:35] <Pixel_> bschaefer, the bindings
[17:35] <Pixel_> bschaefer, so i added     SDL_GameControllerAddMapping("03000000ff1100003133000010010000,serioux,a:b2,b:b3,y:b1,x:b0,start:b9,back:b8,leftstick:b10,rightstick:b11,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpleft:h0.8,dpdown:h0.4,dpright:h0.2,leftx:a0,lefty:a1,rightx:a2,righty:a3,lefttrigger:b6,righttrigger:b7,");
[17:36] <bschaefer> o the first part was wrong?
[17:36]  * bschaefer has no clue what that binding really does :)
[17:36] <bschaefer> besides config (i assume some device id?)
[17:36] <bschaefer> or header for the bytes
[17:37] <Pixel_> bschaefer, so SDL2 detects the gamepad, but doesn't know the bindings, configuration? the buttons layout
[17:37] <Pixel_> from what i understand
[17:37] <Pixel_> i had to use steam big picture to generate the GUID?
[17:37] <bschaefer> that makes sense, the only difference i see between then one you pasted was the
[17:37] <bschaefer> 03000000ff110000313300001001000
[17:37] <bschaefer> vs 03000000ff110000313300001
[17:38] <Pixel_> https://wiki.libsdl.org/SDL_GameControllerAddMapping
[17:38] <bschaefer> o you add some more
[17:38]  * bschaefer doesnt know much about joysticks :)
[17:38] <Pixel_> same here :)
[17:38] <Pixel_> i'm a graphic designer btw :))
[17:38] <Pixel_> i code for fun
[17:38] <bschaefer> o nice!
[17:38] <Pixel_> i'm not a coder
[17:38] <bschaefer> well that makes sense to need the GUID to read from the device
[17:39] <bschaefer> sdl2 kind of has a very hacky joystick support (reading the code)
[17:39] <bschaefer> but idk if theres a good joystick device library anyway
[17:39] <Pixel_> hehe :D
[17:39] <bschaefer> (evdev/libinput)
[17:39] <bschaefer> soo :)
[17:40] <Pixel_> when i "cat /dev/input/event13" and press the keys on the gameplad
[17:40] <Pixel_> i see stuff on the screen :))
[17:41] <bschaefer> nice!
[17:41] <Pixel_> like some ascii stuff
[17:41] <Pixel_> probably that's the gamepad
[17:41] <bschaefer> cat should just print the bytes that are coming in
[17:41] <Pixel_> yep
[17:41] <bschaefer> annd sdl2 will interpret that into actual *data8
[17:41] <bschaefer> *data* that you can set to BUTTON_X etc
[17:42] <Pixel_> um.. now let's try on the phone :D
[17:42] <Pixel_> brb
[17:49] <Pixel_> nope :/
[17:50] <Pixel_> oh well :D i have to run again
[19:18] <Elleo> bschaefer: http://i.imgur.com/eJSsJxH.jpg <-- works! thanks :)
[19:18] <bschaefer> o thats awesome!
[19:18] <bschaefer> happy that fixed it!
[19:22] <strixdio> Any opinions whether I should get a Nexus 5 or a OnePlus 3? Not sure which is likely to be supported longer.
[19:59] <dobey> strixdio: well the oneplus3 doesn't have a working port yet at all i don't think
[20:00] <dobey> strixdio: just don't try to buy whichever nexus 5 i try to buy
[21:22] <SebthreeBQM10HD> hi
[21:38] <mimecar> hi SebthreeBQM10HD
[22:04] <SebthreeBQM10HD> mimecar, hi
[22:45] <my123> hi
[23:32] <mcphail> I am _so_ close to getting a background IRC service working...
[23:34] <mcphail> I've got a quasselcore service running on the phone, which does not die on screen-off. The quassel client on the store can connect to it, but by gosh it is a clunky arrangement
[23:35] <mcphail> I can read messages on the device, but can't seem to send
[23:38] <Acou_Bass> mcphail: thats cool to know ;D i saw the quassel client in store and it looks nice
[23:39] <mcphail> Acou_Bass: it needs a bit of polish. No way to configure connections etc from the client
[23:39] <Acou_Bass> ahh hmm
[23:41] <mcphail> If anyone wants to play with it, you can download it from http://themcphails.uk/quasselcore.njmcphail_0.1_armhf.click . You need to run it on your phone (it will never "launch" - just keeps spinning) then connect and configure from a client on your PC. After that, you can install the quassel app from the store and connect to it. Really clunky...
[23:42] <mcphail> mcphail_quassel: ping
[23:44] <Acou_Bass> sadly my nexus 4 is running sailfish right now or id love to give it a test ;P
[23:44] <mcphail> Traitor! ;)
[23:45] <Acou_Bass> BUT one of the reasons i switched is because ubuntu lacked a good IRC client... so your work may change that xD


[04:05] <RAOF> Bah!
[04:06] <RAOF> What's the sensible way to get a mainline kernel building on the -fPIC-all-the-things default yakkety gcc?
[06:23] <i915> anybody know how the /proc/irq/xxx/  affinity_hint  and node files work? I get the rest of the files under /proc/irq quite important for controlling what cpu get what interrupts in a multiprocessor enviorment
[06:24] <i915> So curious on those 2 files node sounds like some cluster thing for cpu's affinity_hint not sure what the heck that is smp_affinity ,smp_affinity_list are quite important
[06:57] <apw> i915, smp_affinity is literally a bitmap of whihc cpus can handle a specific incoming interrupt ... _list is that in human
[07:02] <apw> RAOF, you need to apply the fix for -fpie to the main Makefile, which is what mainline-build-one does
[07:02] <i915> I know this i am talking about affinity_hint  and node files?
[07:02] <apw> oh your last line wasn't very clear
[07:03] <i915> what are those 2 file for
[07:03] <RAOF> apw: I found passing -fno-pic which makes it *almost* build. Where's mainline-build-one so I can steal?
[07:03] <RAOF> Also, good morning and commiserations.
[07:03] <RAOF> May your bees be extra comforting today.
[07:03] <apw> RAOF, you don't want that really, you want to git log Makefile in yakkety and take the -fPIE patch there
[07:06] <RAOF> Hm. I apparently haven't pulled yakkety in approximately 100MB worth of time.
[07:07] <apw> i915, affinity_hint is a hint from the device driver as to where the irqs are best handled
[07:07] <apw> i915, it appears to be set in specific drivers where that driver knows about the h/w
[07:12] <apw> i915, node appears to be which numa node the device is associated, which i would interpret as meaning
[07:12] <apw> i915, the nearest memory node for incoming/outgoing data
[07:13] <RAOF> apw: I can't seem to find any relevant patch to Makefile in kernel.ubuntu.com/ubuntu/ubuntu-yakkety.git:master? That's where it's meant to be, right?
[07:14] <apw> RAOF, UBUNTU: SAUCE: (no-up) disable -pie when gcc has it enabled by default
[07:14] <apw> is the one i mean
[07:14] <apw> c863674de4911d8fb7643d5dfe4e5063b052bfe5
[07:16] <RAOF> I have clearly messed up my git somehow; I can see that commit, but not in the history of yakkety/master. Oh well.
[07:16] <RAOF> Thanks!
[07:18] <apw> RAOF, master-next is always better, beacuse raisons
[07:18] <RAOF> I'll try to remember that in future.
[07:29] <i915> anybody out there know much about the mei-me driver and what all this Management Engine Interface (Intel(R) MEI  stuff is good still don't get  what this host an Me interface is for. Seems like a remote management tool but whats the point we have so many why build it in as an LKM or something internal to the ubuntu kernel
[08:01] <apw> i915, the linux interface to the mei is all about letting the OS configure the remote management interfaces and the like
[08:01] <apw> i915, the specific features are per chipset though so you would have to look at the chipset docs on what all you can change
[08:18] <i915> ya doesn't seem like a major deal why not just remote desktop vnc over to the machine at that point or ssh over
[08:22] <apw> management interfaces are for when the machine is broken enough that those don't work
[08:25] <i915> O i can kind of see in that case but 90% of the time you probably want to be physically there because the problem could be hardware related at that point or a complete shut down
[08:26] <apw> with a management interface you don't have to be there, which machines the machine doesn't have to be where you are
[08:26] <i915> And what happens if the mei-me driver gets cooked then your screwed anyway unless its built into the bios
[08:26] <apw> the driver is not for operational purposes, those are independant, it is to allow configuration before failure
[08:26] <i915> in which case your only cooked if the bios or computer is completely off even more rare
[08:27] <i915> I don''t think i completely get it then is it for remoting in to fix a problem or shutting down gracefully with certain configurations?
[08:28] <apw> the pysical device is for analysis and fixing remote, the kernel driver is to let the host
[08:28] <apw> OS ocnfigure the device to define its actions and abilities
[08:29] <i915> and what exactly is the purpose of the mei-me LKM driver if not for controlling the remote management process
[08:33] <i915> So its like host machine your at issues commands to the target machine running mei-me LKM which sets the actions and abillities the target machine uses in case of  mei-me crashing or other really bad issues happening so the host can still remote
[08:34] <i915> there is got to be some fail safe with this so if the mei-me module crashes there still some default that allows one to remote manage it right. Do i have this right now?
[08:34] <apw> i915, no you talk to those interfaces "remotely" usually over the network.  the interface locally is only use to configure the local device
[08:34] <i915> And if i do then the management stuff is part of the bios or some fix place in memory that all computers have available for it
[08:34] <apw> so you can cange config without rebooting into bios
[08:35] <i915> Still your screwed if the NIC goes down
[08:35] <apw> its a separate thing mostly hidden from the host
[08:35] <apw> it uses the nic directly in a more reliable way
[08:36] <i915> ok so this is to change bios settings without shutting down and F10/12,...etc
[08:37]  * apw wanders off
[08:37] <i915> bottom line if the NIC is down or no network connectivity then there is nothing you can do
[17:52] <Larry__Tate> Is there any way to know when the next kernel release will occur?
[17:54] <Larry__Tate> And if the fix for this bug will be included: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492
[17:54] <apw> Larry__Tate, there is an SRU announce list which has dates posted
[17:55] <Larry__Tate> Ok, any chance you can point me to where that is located? I've searched but come up empty...
[17:56] <apw> kamal, ^
[17:56] <apw> Larry__Tate, that fix looks to be in 4.4.0-25.44 and later, so in this current cycle
[17:58] <Larry__Tate> apw that is good news.
[18:02] <kamal> Larry__Tate, apw: yes, that fix is in the kernel sitting in -proposed right now.  we do expect to release this coming Monday.
[18:03] <Larry__Tate> Whew. That is good news. Thanks, kamal, apw!
[18:04] <Larry__Tate> Just out of curiosity, is the only way to find a release date to scroll through the entire mailing list for the kernel team?
[18:05] <Larry__Tate> Ah, never mind guys. I just saw that there was a specific list for announcements. Thanks again.
[18:26] <i915> curious anybody know about this node file in /proc/irq i think it has to do with NUMA node but how is any of this different then SMP_affinity files ?
[19:02] <apw> smp_affinity is about processor affinity, numa is about memory affinity
[19:03] <apw> it is possible to have cpuless and memoryless nodes which are separate
[19:19] <i915> so what does the /proc/irq/xxx/node tell you or modify for you that smp_affinity cann't?
[19:20] <i915> it always has 0 for me
[19:22] <apw> the memory affinity ... which is separate to cpu affinity
[19:22] <i915> what what does memory affinity actually set or tell you i guess
[19:24] <i915> if its memory less or  cpu less what does that mean for an irq doesn't make much sense to me. nodes seem like the same thing as  a collection of cpu that you control with the bitmask
[19:31] <apw> i915, a node is a collective object that contains 0 or more cpus and 0 or more memory
[19:31] <apw> normally cards are assoicated with a numa domain, in a small machine there may well only be one (called 0)
[19:33] <i915> by cards what do you mean mobo , memory cards , pci expresses ...?
[19:34] <i915> and what does a node have to do with irq settings irq are only like hardware interrupts to a cpu so its only worth anything if cpu is associated to a node for an irq to be of any uses that and memory in the first place
[19:41] <apw> i am talking about perpipheral cards, pci whatever.  an interrupt coming in needs to be routed to a cpu and the io it performs needs memory to land in.  these two affinities define where those two are
[19:42] <apw> they will in the normal case be the same, but they may not