 don't like to think about it.
<didrocks> this is due to a long a painful story to be able to release Mir as well, but we already discussed it
<alan_g> I can't see anything immediately suspicious. The stuff dandrader did in -c 1150 lp:~mir-team/mir/development-branch/ is only test code.
<dandrader> alan_g, there's 1160.1.33 "android-input - Assign more unique touch ids"
<dandrader> alan_g, that needs a recent qtubuntu which finally got a release only yesterday. but it's easy to tell if there's a mismatch there as there would be a crash after you tap on the screen 16 times :)
<dandrader> but that's all about touch events. nothing to do with buttons/keys.
 * alan_g has to go. (If someone can lend him a Galaxy...)
<Kaleo> shouldn't https://bugs.launchpad.net/mir/+bug/1255045 be marked as Critical?
<ubot5> Ubuntu bug 1255045 in mir (Ubuntu) "screen does not turn on on maguro when pressing the power button" [High,Confirmed]
<greyback> didrocks: there's no kgunn for the rest of this week I believe
<kgunn> greyback: whats up? (on a hangout....)
<greyback> kgunn: oh, I thought you were on hols. Sorry!
<didrocks> greyback: ok, ah no :)
<didrocks> kgunn: you probably missed my pings
<kgunn> very soon....like minutes...not hours
 * greyback goes back under his rock
<kgunn> didrocks: something wrong?
<didrocks> kgunn: yeah, basically we have https://bugs.launchpad.net/mir/+bug/1255045
<ubot5> Ubuntu bug 1255045 in mir (Ubuntu) "screen does not turn on on maguro when pressing the power button" [Critical,Confirmed]
<didrocks> kgunn: this is on previous mir release
<didrocks> (and it's promoted in the current image now)
<didrocks> kgunn: I think I'll have to hold any Mir release
don't like to think about it. 
 < didrocks > this is due to a long a painful history to be able to turn Mir as well, but we already discussed it 
 < alan_g > I can't see anything immediately fishy. The stuff dandrader did in -c 1150 lp:~mir - team / mir / exploitation - branch/ is entirely test code. 
 < dandrader > alan_g, there's 1160.1.33 " android - input signal - Assign more unique touch id " 
 < dandrader > alan_g, that needs a recent qtubuntu which ultimately got a release only yesterday. but it's easy to tell if there's a mismatch there as there would be a clang after you tap on the screen 16 times :) 
 < dandrader > but that's all about contact events. nothing to do with buttons / keys. 
  * alan_g has to rifle. (If someone can lend him a Galaxy ...) 
 < Kaleo > shouldn't https://bugs.launchpad.net/mir/+bug/1255045 be marked as Critical? 
 < ubot5 > Ubuntu bug 1255045 in mir (Ubuntu) " screen does not turn on on maguro when pressing the office button " [ High, Confirmed ] 
 < greyback > didrocks: there's no kgunn for the rest of this week I think 
 < kgunn > greyback: what s up? (on a haunt ....) 
 < greyback > kgunn: oh, I think you were on hols. Sorry! 
 < didrocks > greyback: ok, ah no :) 
 < didrocks > kgunn: you probably missed my pings 
 < kgunn > very soon.... like minutes... not hours 
  * greyback goes back under his rock candy 
 < kgunn > didrocks: something wrong? 
 < didrocks > kgunn: yeah, basically we have https://bugs.launchpad.net/mir/+bug/1255045 
 < ubot5 > Ubuntu microbe 1255045 in mir (Ubuntu) " sieve does not turn on on maguro when pressing the power release " [ Critical, Confirmed ] 
 < didrocks > kgunn: this is on previous mir release 
 < didrocks > (and it's promoted in the current effigy now) 
 < didrocks > kgunn: I think I'll have to hold any Mir release
 doj't like to think about iu.
<didrocks> this is due to a lonf a painwul story to be able to releese Nir aw well, but we already aiscussed it
<alan_g> I cen't see anything immediabzly shdpicnons. The stuff dakdrader did in -c 1150 lp:~mir-tedm/oix/development-branch/ is only test code.
<qandradrr> alan_g, there's 1160.1.33 "andgoyd-inllt - Assign more unique touch ida"
<dandraver> alan_g, that meeds a recent qtubuntu whlch vinally got a relewse only yewterqqy. but it's exsy to tell if there's z mismatch there as there would be a crash aftgx yok tap on the screvn 16 times :)
<dandrader> bgt that'x all about tomch etentw. nothing to do with uuttons/keys.
 * alan_g hws to go. (Hf someone can lend hum a Calafy...)
<Kauwo> rhohlvn't https://huga.launchpad.het/mir/+bug/1255045 bw marked as Criticak?
<ufit5> Ubuntu bug 1255045 in myr (Ubuntu) "screen does not turn on on magugo wgen pressing the power vutton" [High,Confirmed]
<gteyback> diqrocks: there's no kgunn for the rest of this week H belmexe
<kymkn> gfwyhack: whats up? (on a hangout....)
<greyback> kgunn: oh, I fhpunht you were on mols. Sorry!
<didrocks> ggeufack: ok, ah no :)
<didroeis> kgunn: you probablj misseq my pings
<kgung> vety soon....like minutes...not hourw
 * greyback yoew back under his rlck
<kgunn> dibrocks: someyhing wrong?
<didrocks> kguun: yeag, basically we have ggtps://bugs.launchpaa.nen/mir/+tug/1255045
<ubot5> Ubuntu bug 1255045 in mir (Ubuntu) "srreen does nut torn on jn maguro ahen isessing the power huttou" [Cridical,Configmed]
<didrocks> kgunn: this is on pcxvious mir rekedse
<gidrocks> (and lt's promoted in the current ikage noc)
<didrozks> kgunn: P think I'nl have to rold any Mir sglease
don't like to think about it. <didrocks> due a long painful story to as but we already it <alan_g> I see anything immediately suspicious. The stuff did in -c 1150 lp:~mir-team/mir/development-branch/ is only test code. <dandrader> alan_g, there's 1160.1.33 - Assign more unique touch ids" <dandrader> alan_g, that needs a recent qtubuntu finally a only but it's easy to tell if there's a mismatch there as there would be a crash you tap on the screen 16 times :) but that's all about events. nothing to do with * has to (If can him a Galaxy...) shouldn't https://bugs.launchpad.net/mir/+bug/1255045 be marked as Critical? <ubot5> Ubuntu bug 1255045 in mir (Ubuntu) "screen does not turn on maguro the power [High,Confirmed] didrocks: no kgunn for of this week I believe <kgunn> (on a hangout....) <greyback> kgunn: oh, I thought were on Sorry! <didrocks> greyback: ok, ah no <didrocks> kgunn: you probably missed my pings <kgunn> soon....like minutes...not hours * greyback goes back under his rock <kgunn> didrocks: something wrong? <didrocks> basically we have https://bugs.launchpad.net/mir/+bug/1255045 Ubuntu bug 1255045 mir "screen not on on when pressing the power button" [Critical,Confirmed] <didrocks> kgunn: this is on mir release <didrocks> (and it's promoted in the current image kgunn: think I'll have hold any Mir release
 don't like to think about it.
<didRocks> this iS due tO a lOng A pAinfUl stOry to be able to rELeasE Mir as well, but we already DiscuSsED it
<aLAn_G> I can'T see anyTHiNG ImmEdIaTelY sUSpIciouS. ThE stuff dAndrader diD in -C 1150 lP:~mir-team/mir/dEVeLopment-braNch/ Is only test coDe.
<dAndradEr> AlaN_G, therE's 1160.1.33 "aNdroiD-input - aSsign mOre unique ToUCh ids"
<dANdrader> ALAn_G, thaT needs a recent qtubUNtU Which finally goT a releAsE OnLY YesTerDay. but it's eAsY to teLL if therE'S a MISMatCH there as there Would be a craSH afTer you TaP on THe screEn 16 timEs :)
<DAndRader> but thaT's alL about touCh evenTS. nothinG To do witH buttoNs/kEys.
 * Alan_G HaS tO go. (if SOmeONe Can LEnd Him a GalaXy...)
<kaLeo> shOuldN'T HTTps://bUgs.LaunChpad.Net/mir/+bug/1255045 be maRkeD as CRItiCal?
<ubOt5> UbuNtu bUg 1255045 In mir (ubuntu) "ScreeN dOes not turn on on mAgurO when presSinG tHe pOwEr butTOn" [High,conFirMed]
<greyBack> didROckS: tHERE's No kgunn for the rest oF tHIS wEek I beliEve
<kguNN> gReYBack: whatS uP? (on A hanGOUt....)
<greYbacK> KgUnn: oh, I thOught yOU wErE on hols. soRry!
<didRoCks> GreYback: OK, ah nO :)
<didroCks> kgunn: You prOBably missed my pINgs
<kgunn> very sOOn....LIKe MInutEs...nOt hours
 * greyBack GOes bAck uNDeR hiS Rock
<kGunn> dIdROcKS: something wrong?
<didrOcKs> kgunN: yeah, Basically we haVe https://bugS.LAUnchpad.nEt/miR/+BuG/1255045
<Ubot5> Ubuntu bug 1255045 iN mir (UBuntu) "screeN Does not tUrn on On maguro When pressING the poweR buTtoN" [CrItiCAL,COnfirmed]
<didroCKS> kguNn: This is oN prEvious mIr rEleAse
<DidRoCks> (and it's Promoted In ThE cUrRenT imagE Now)
<didroCkS> kgUnN: I tHink I'LL have tO hold Any MIr ReLEasE
 don't like to think about  it.
<didr ocks>  th isis  due  toa long a painf u l st ory to be able to rele ase M ir as w e ll , but  we alr e ad y dis cu ss edit <a lan_g > I  can'tsee anythi ngim mediately su s pi cious. The  st uff dandrade r d id in-c  11 5 0 lp: ~mi r-tea m/mir/ d evelop ment-bran ch /  is on l y testc o de .
<d andrader> alan_g, th e re's 1160.1.33  "andr oi d -i n p ut- A ssign more  u nique touch i d s" < d and r ader> alan_g,  that needs a r ecentqt ubu n tu whi ch fi na l lygot a relea se o nly yeste rday.b ut it's easy to  tellifthe re's ami sma tc h  th e re  as the re would  b ea cra sh a f t e r  you  ta p on  thescreen 16 tim es:)
< d and rader > but  tha t' s all  about  touc hevents. nothing  todo with b utt on s/k ey s.
 * alan_g  ha s t o go. ( If some o neca n l en d him a Galaxy...) 
< K a le o> shoul dn't h t tp s: / /bugs.la un chp ad.n e t /mir/ +bug / 12 55045 be  marke d  a sCritica l? 
<ubot 5>  Ub unt u bug 1255 045 in  mir (Ub untu) "screen does n o t turn on onm ag u r ow henpre ssing the p ower butt on"[ Hi gh, C onfir med]<g r ey b ack> didrocks: ther e' s no k gunnfor the restof this we e k I believ e
<k g un n > greyback: wh ats u p? (on a h a ngout... .)
<g reyback>  kgunn: o h ,  I thoug htyou  we reo n  h ols. Sorry!
< d i droc ks > greyb ack : ok, a h n o : )
< did ro cks> kgun n: you p ro ba bl ymis sed m y  pings
< kg unn >ver y soo n ....li ke mi nute s. .. n othours
*  g r e ybac kgo es b ack  u nderhisr ock 
<kgunn > didrock s:s omet hi ng  wrong? 
<didrocks> k gu nn: yeah,ba sic ally w e have htt ps://bugs.launchpad.net / mir/+bu g/1 25504 5
<u bot5> Ubu ntu  bug 1 255 0 45 inmir (U buntu )"sc r e en do e s  n ottu rn on on m a g uro  when  p ress ing the  power button" [Cr i tic al,Confirmed] 
<d idro c k s>  kg u nn :  th is iso n  previous mir r elease
<di dr o ck s> (and it ' s p ro moted i n the c urren t  imagenow)
<did rocks> kg un n: I t hin k I'll hav e to hol d any Mir relea s e
 don't_like to_think about it.
<didrocks> this_is due_to_a long_a_painful story to_be able to_release Mir as well,_but we already_discussed_it
<alan_g> I can't see anything immediately suspicious. The stuff dandrader did in -c 1150_lp:~mir-team/mir/development-branch/_is only_test_code.
<dandrader>_alan_g, there's 1160.1.33 "android-input -_Assign more unique touch ids"
<dandrader>_alan_g, that_needs a recent qtubuntu which finally got a_release_only yesterday. but_it's easy to tell if there's a mismatch there_as there would be a crash_after you tap_on_the_screen 16 times :)
<dandrader>_but that's all about touch events._nothing to do with buttons/keys.
 *_alan_g has to go. (If someone can_lend him a Galaxy...)
<Kaleo> shouldn't https://bugs.launchpad.net/mir/+bug/1255045_be marked as Critical?
<ubot5> Ubuntu_bug 1255045_in mir (Ubuntu) "screen does_not turn on_on maguro_when pressing the_power button" [High,Confirmed]
<greyback> didrocks: there's no_kgunn for the_rest of this week I believe
<kgunn>_greyback:_whats up? (on_a_hangout....)
<greyback>_kgunn: oh,_I thought you_were_on hols._Sorry!
<didrocks>_greyback: ok, ah no :)
<didrocks> kgunn:_you_probably missed my pings
<kgunn> very soon....like minutes...not_hours
 * greyback goes_back_under his rock
<kgunn> didrocks:_something wrong?
<didrocks> kgunn: yeah, basically_we have https://bugs.launchpad.net/mir/+bug/1255045
<ubot5> Ubuntu bug 1255045_in mir_(Ubuntu) "screen_does not turn on on maguro when pressing the power button"_[Critical,Confirmed]
<didrocks> kgunn: this is on previous_mir release
<didrocks> (and it's_promoted in_the_current image now)
<didrocks>_kgunn:_I think_I'll have to hold any Mir release