/srv/irclogs.ubuntu.com/2015/09/10/#ubuntu-unity.txt

=== maclin1 is now known as maclin
tsdgeosmzanetti: are we landing any more branch on the overlay? or first doing the branch killing?07:52
tsdgeosbecause we're starting to stockpile again :D07:52
mzanettitsdgeos, next ones will go to trunk again... let me check if the one that sync landed by now07:53
mzanettiit was QA'd last night07:53
mzanettioh dear... hangs in proposed somewher07:54
tsdgeos:A07:57
=== davidcalle_ is now known as davidcalle
mzanettiI fail to understand those adt logs08:07
mzanettiseems to fail for qtmir and unity808:08
mzanettibootest says it can't do some apparmor things, whatever that means...08:08
MirvTrevinho is great at spamming my bug folder :D09:38
TrevinhoMirv: yeah, I had to fire my script to keep things in sync09:39
TrevinhoMirv: and.... Well I didn't do that for compiz (yet) as there was 2600 bugs to fix... and it wasn't the case :)09:39
Mirv:)09:40
=== jzheng is now known as jzheng_afk
=== nudtrobert1 is now known as nudtrobert
=== alan_g is now known as alan_g|lunch
=== cwayne-afk is now known as cwayne_
=== MacSlow is now known as MacSlow|lunch
=== alan_g|lunch is now known as alan_g
mzanettidandrader, there's a test failure in that silo 27: https://launchpadlibrarian.net/216844866/buildlog_ubuntu-wily-amd64.qtmir_0.4.6%2B15.10.20150910-0ubuntu1_BUILDING.txt.gz13:39
dandradermzanetti, ok13:41
mzanettilet me know when to re-kick the build13:42
dandradermzanetti, can you remove https://code.launchpad.net/~gerboland/qtmir/multimonitor/+merge/269906 from that silo?13:43
dandradermzanetti, so that we can land the critical bug fix it contains13:43
dandradermzanetti, and I guess it wouldn't hurt to add those qtubuntu ones as well: https://code.launchpad.net/~dandrader/qtubuntu/noQtSensors-lp1481389/+merge/267198 and https://code.launchpad.net/~dandrader/qtubuntu/provideMirConnection/+merge/26932013:45
dandraderthey're pretty harmless13:46
mzanettitsdgeos, ah, so it's because it's empty ("")?13:56
=== MacSlow|lunch is now known as MacSlow
tsdgeosmzanetti: yep13:59
mzanettitsdgeos, right... makes sense. approved13:59
mzanettidandrader, silo building, including those qtubuntu branches14:13
dandradermzanetti, thanks!14:13
mzanettioops. missed the one to remove14:14
mzanettiwill redo14:14
=== dandrader_ is now known as dandrader
=== dandrader is now known as dandrader|afk
=== alan_g is now known as alan_g|afk
tsdgeoshate it when this happens15:10
tsdgeoscall deleteLater on an objcet and doesn't get deleted15:10
tsdgeos:'(15:10
tsdgeosfound out why!15:21
tsdgeosneed to be careful when reimplementing ::event15:23
=== alan_g|afk is now known as alan_g
=== dandrader|afk is now known as dandrader
dandradermzanetti, what's the next step for silo 027?16:34
=== alan_g is now known as alan_g|EOD
=== dandrader is now known as dandrader|afk
mzanettidandrader|afk, you walk through the branches in there and verify that the linked bugs are fixed and the promised features are working.17:32
mzanettidandrader|afk, then you walk through the testplans: https://wiki.ubuntu.com/Process/Merges/TestPlans/QtMir17:32
mzanettidandrader|afk, can't find one for QtUbuntu. Make sure related functionality isn't broken17:33
mzanettiwhen you're happy with the results, go here and leave a comment that you've tested it and on what device/image: https://requests.ci-train.ubuntu.com/#/ticket/32817:34
mzanettidandrader|afk, for example, like this: https://requests.ci-train.ubuntu.com/#/ticket/28517:34
mzanettidandrader|afk, test at least on rc-proposed, if things could be different for wily, test both17:35
=== dandrader|afk is now known as dandrader
kgunnmzanetti: i don't mind helping to test silo27, that's multimonitor right ?18:26
slangasekmzanetti: hi, kgunn pointed me your way regarding this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1278780/comments/819:23
ubot5Ubuntu bug 1278780 in apport (Ubuntu) "apport takes too long to write crash report, appears to lock up phone" [High,Triaged]19:23
dandradermzanetti should be past his EOD by now19:28
slangasekdandrader: I imagine so; IRC is a decent messaging service though :)19:31
kgunnand he's known to have the problem of not being able to stay away19:36
dandraderslangasek, problem is, he will be back only next Tuesday :(19:39
dandraderkgunn, and there's that as well :)19:39
kgunnah dang...forgot he was taking some days19:43
kgunnslangasek: what is your idea btw19:43
slangasekkgunn: so the basic idea is, can we make the crash handler faster for critical components (such as the system compositor or unity8 shell) by having those programs register a custom SIGSEGV handler that unmaps video buffers (for example) and re-raises19:50
slangasekkgunn: I don't know if this is safe to do from inside a signal handler, it depends on how the mapping/unmapping is handled; and I don't know if the video memory is a large enough part of the process's address space to make a difference19:51
slangasekbut I thought it was an idea worth exploring19:51
kgunnyeah, the video memory might be the booger19:52
slangasekbecause ultimately, the kind of behavior we've heard described - UI locking up for a minute while the crash handler runs - does sound like it's taking an unreasonably long time for what it /ought/ to be doing19:52
=== dandrader is now known as dandrader|afk
pmcgowankgunn, I just got https://bugs.launchpad.net/canonical-devices-system-image/+bug/149156620:42
ubot5Ubuntu bug 1491566 in Canonical System Image "Shell not responsive after an incoming SMS" [Critical,Confirmed]20:42
pmcgowanadded the logs, its still in the stuck state20:42
pmcgowandandrader|afk, ^20:42
=== dandrader|afk is now known as dandrader
dandraderpmcgowan, still have the device in that state?21:12
dandraderpmcgowan, https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/comments/2621:14
ubot5Ubuntu bug 1491566 in Canonical System Image "Shell not responsive after an incoming SMS" [Critical,Confirmed]21:14
dandraderso unity8.log shows a log of input events but I can't tell whether those events are *all* from before unity8 became unresponsive or not. What I want to know there is whether it still logs input events *after* it becomes unresponsive21:16
dandraderI didn't realize that when I posted the original instructions. Rectified it only in comment #2621:17
dandradersame goes for unity-system-compositor.log21:18
pmcgowandandrader, there was nothing logged after the system froze21:19
pmcgowanalso see stack trace I added21:19
pmcgowanI just restarted lightdm a few mins ago21:19
dandraderoh :(21:19
pmcgowanwell wanted to get my messages :(21:19
pmcgowandandrader, touching the screen I see the touch driver but nothing else get active21:20
dandraderalf is the one intereseted in the stack  traces. but I can tell they're not all that interesting as you didn't have debug symbols21:20
dandraderpmcgowan, what do you mean by "I see the touch driver"?21:21
pmcgowandandrader, a process called mtk-tpd21:22
dandraderpmcgowan. so no new messages came to unity8.log or unity-system-compositor.log when you touched the screen while the device was unresponsive?'21:22
pmcgowandandrader, correct, if I tail the logs nothing new21:23
dandraderpmcgowan, that's a very important bit of info, it's worth commenting that in the bug report21:23
pmcgowanwill do21:23
dandraderbregma, do you recall what tool we can use to monitor events coming out of evedev files?21:33
dandraderevemu-tools21:39

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