=== c74d is now known as Guest69891
=== c74d is now known as Guest21943
=== c74d is now known as Guest24227
=== c74d is now known as Guest22062
[08:28] <mlankhorst> o/
[08:28] <willcooke> hi mlankhorst
[08:28] <willcooke> So folks - we have a problem
[08:28] <willcooke> Xmir on the N7 using EGL causes reboots of the device
[08:28] <willcooke> It works fine and dandy on my x86 laptop
[08:29] <willcooke> and it's stable on my BQ phone too
[08:29] <mlankhorst> and SW mode doesn't ignore the alpha channel if you specify XRGB format :/
[08:29] <mlankhorst> willcooke: it's stable now with the separate thread for flipping disabled right? before it was slightly unstable?
[08:29] <willcooke> So we need some help to trouble shoot this ASAP - it's getting to be quite important
[08:30] <willcooke> mlankhorst, on my N7 with the Xmir binary from your website I can cause a reboot by simply trying to resize the window
[08:30] <willcooke> *every time*
[08:30] <mlankhorst> I mean on the BQ phone
[08:30] <willcooke> ah, right - I'll need to update my phone to the latest bin.  please hold :)
[08:31] <mlankhorst> if it was stable before don't worry
[08:31] <willcooke> oki - still interested to see if I have similar problems - hopefully not
[08:31] <mlankhorst> but I was getting corruption when I moved flipping to a separate thread.. still wish there was a way to do so..
[08:39] <willcooke> mlankhorst, latest Xmir binary on phone doesn't update the screen,  I just have the LO splash screen
[08:41] <mlankhorst> oke :/
[08:47] <willcooke> mlankhorst, is there a hacky workaround for the transparency issue if we need it?
[08:48] <willcooke> I'm thinking that I can use -sw mode if I have to - as long as it's not see-through  :)
[08:48] <mlankhorst> I tried, need to understand how the initial background is blanked better..
[08:48] <willcooke> oki
[08:48] <mlankhorst> -sw mode has no -2x support or rotation
[08:55] <willcooke> mlankhorst, can live without it
=== tsdgeos_ is now known as tsdgeos
=== c74d is now known as Guest98318
=== anpok_ is now known as anpok
=== c74d is now known as Guest22949
=== c74d is now known as Guest11852
=== c74d is now known as Guest37999
=== alan_g is now known as alan_g|lunch
=== marcusto_ is now known as marcustomlinson
=== alan_g|lunch is now known as alan_g
=== marcusto_ is now known as marcustomlinson
[15:22] <micahf> hey, i'm having trouble with multitouch in chrome on 14.10
=== sil2100_ is now known as sil2100
[15:23] <micahf> two finger gestures work so-so (scroll, pinch zoom), but i can only get one touch event!
[15:23] <micahf> i'm using a lenovo x220t convertable laptop
[15:24] <micahf> the thing is, in ubuntu 13.10, I was able to use multitouch events with an acer w700 and aura builds of chrome
[15:24] <micahf> i've done lots of searching and am baffled!!!
[15:25] <micahf> maybe this has nothing to do with Mir!!!
[15:25] <ogra_> most likely :)
[15:26] <ogra_> perhaps someone in #ubuntu-x has a clue
[15:26] <micahf> ogra_: thanks :)
[15:26] <micahf> ah, x is running on top of mir in 14.10?
[15:27] <ogra_> no
[15:27] <ogra_> Mir isnt used at all in a default install
[15:27] <ogra_> only in the desktop-next builds
[15:27] <micahf> ohhh :) got it!
[15:27] <micahf> ah, i will avoid those builds for now!
[15:27] <micahf> good luck with them though
[15:27] <ogra_> (on phones/tablets it has always been the default though)
[15:29] <micahf> ogra_ is there a way to install desktop-next along side desktop-now
[15:29] <micahf> (it's probably not called "desktop-now", but you know what i mean)
[15:30] <ogra_> i dont think thats safe, no
[15:30] <ogra_> you could try desktop-next in live mode i think
[15:30] <ogra_> juts from usb stick
[15:30] <micahf> ogra_ yeah that sounds much safer.  it's especially unsafe because I only have one computer and am traveling at the moment
[15:37] <davmor2> ogra_ juts from a usb stick......man you must be the hide and seek champ.......that or it's the worlds biggest usb stick ;)
[15:38] <ogra_> every usb stick juts, no ?
[15:39] <davmor2> yeah but not every usb has an ogra_ jutting from it :)
[15:40] <ogra_> haha
[17:19] <racarr> Morning!
[17:23] <greyback_> racarr: greets! Mind checkout out my comment here: https://code.launchpad.net/~mir-team/qtmir/port-to-event-2.0/+merge/248067
[17:24] <greyback_> suspect a merge went bad somewhere
[17:26] <racarr> greyback_: So this branch seems to revert thementioned branches?
[17:26] <racarr> Weird...thanks
[17:26] <racarr> will get on it after breakfast
[17:26] <greyback_> racarr: yeah, but it screws up the history, files appear deleted & recreated
[17:27] <greyback_> I wasn't able to fix that
[17:28] <racarr> greyback_: I think there isn't a way to fix it right
[17:28] <racarr> that is the "history"
[17:29] <racarr> anything else is a rebase...
[17:29] <racarr> well so I mean there are various ways
[17:29] <racarr> but not encouraged?
[17:32] <racarr> greyback_: e.g. the only thing I know todo ismerge the other branches and resolve --take-other
[17:32] <greyback_> worth a shot I guess
[17:32]  * greyback_ has to run for a bit
[17:33] <racarr> bye :)
[17:54] <racarr> Has anyone ever seen a valgrind invalid read in "readdir"
[17:55] <racarr> https://jenkins.qa.ubuntu.com/job/mir-vivid-amd64-ci/963/console
[17:55] <racarr> (can search for readdir in the full log)
=== alan_g is now known as alan_g|EOD