/srv/irclogs.ubuntu.com/2012/07/16/#ubuntu-x.txt

mlankhorstfeeling a bit sick, but good morning :)08:36
mlankhorstcan someone re-upload libdrm? I fixed the arm build failure08:56
seb128mlankhorst, there?15:03
mlankhorstyeah15:25
seb128mlankhorst, hey15:25
mlankhorstheya15:26
seb128mlankhorst, https://bugs.launchpad.net/ubuntu/precise/+source/xorg-server/+bug/1021517 seems a regression in the recent precise SRU15:26
ubottuLaunchpad bug 1021517 in xorg-server (Ubuntu Precise) "Xorg-server crashes reproducible with GIMP usage" [High,Confirmed]15:26
seb128which got pushed to -security as well15:26
mlankhorstoh fun15:26
seb128mlankhorst, can you or somebody else from here have a look soon?15:26
seb128mlankhorst, comments mention it depends of the trackpad status (like they get it when doing fn-f8)15:26
seb128see the most recent comments15:27
mlankhorstyeah seems likely that it was from 10.3 update, bit weird it would only show now though15:29
seb128mlankhorst, it doesn't only show now15:29
seb128mlankhorst, we started the bug was filed on 2012-07-0615:29
seb128ups15:29
seb128-we started15:29
seb128mlankhorst, I guess you guys didn't monitor the new bugs after the SRU?15:30
jcristauno apport gdb trace or anything?15:30
mlankhorstseb128: I guess those people didn't test -proposed, more likely15:31
seb128jcristau, only https://launchpadlibrarian.net/109601036/XorgLogOld.txt :-(15:32
jcristauyeah not quite as useful15:32
mlankhorstI'll see if I can make a new shiny backtrace15:32
seb128not sure why we don't get apport report for xorg, I guess the xserver handler block it15:33
jcristaumaybe with those binaries addr2line would work, but i'm not going to download that..15:33
mlankhorstI'll create a new bt if I can reproduce15:33
mlankhorstworks here :\ bug is useless without backtrace15:46
mlankhorstoh there we go15:48
seb128mlankhorst, you got it?15:53
mlankhorstseb128: hm nope, was a sigpipe which is valid15:53
mlankhorstmight be old xf86-input-synaptics15:54
seb128mlankhorst, the bug got some pretty responsive users, you can perhaps give them hint to get the stacktrace?15:56
jcristauthe bug already has a pointer to https://wiki.ubuntu.com/X/Backtracing15:57
seb128ok15:58
seb128mlankhorst, jcristau: I get the bug here, let me try that15:58
mlankhorstseb128: oh i just put some qs on the bug15:59
seb128easy to get for me "gsettings set org.gnome.settings-daemon.peripherals.touchpad touchpad-enabled false"15:59
seb128well I just gor an xorg segfault this way in a guest session15:59
mlankhorstok16:01
mlankhorstriught that works16:01
seb128_hum, something the kernel didn't like16:05
mlankhorstseb128_: seems i can reproduce it, but I'm going to lay down now, not feeling so well16:05
seb128_mlankhorst, ok16:05
seb128hum, again16:09
seb128mlankhorst, sorry I might have missed what you said, but get better!16:09
mlankhorstseb128: its no problem to get the bt tomorrow, already had one16:10
seb128mlankhorst, should we hand over that to bryceh or RAOF while you get better?16:11
mlankhorstit's just something that got my throat quite good, should be over in a day I hope :)16:15
seb128mlankhorst, jcristau: backtrace on https://bugs.launchpad.net/gimp/+bug/1021517/comments/5816:16
ubottuLaunchpad bug 1021517 in xorg-server (Ubuntu Precise) "Xorg-server crashes reproducible with GIMP usage" [High,Confirmed]16:16
seb128bryceh, ^ when you are up, it's a segfault and seems a regression from the recent SRU,security update to precise16:18
mlankhorstit was before the security update so definitely the dix changes in 10.4, maybe cnd would know from the backtrace16:21
mlankhorstif not with a bit more work anyone could find out what's going wrong :)16:21
seb128mlankhorst, right, it's likely 10.316:23
seb128cnd, ^16:23
cndI'll take a quick look16:26
seb128cnd, thanks16:27
seb128cnd, you can do that today? it's an xorg segfault regression easy to trigger which made it in a security update of the current lts, i.e not great to have, we should address it16:35
brycehheya16:35
seb128bryceh, hey16:35
seb128bryceh, how are you? happy monday :p16:35
brycehseb128, a bit invalid... threw out my back yesterday while wrestling my son into a pair of pants16:37
seb128bryceh, :-(16:37
cndmlankhorst, seb128: interesting, it's obviously input related, but I have no idea16:38
cndmlankhorst, it was in the latest update?16:38
cndmlankhorst, when you said changes in 10.4, did you mean 11.4?16:38
cndoh wait, nm16:38
cnd-0ubuntu10.416:38
cndmlankhorst, the attached X log says -0ubuntu10.316:38
cndI may be restating things we already know :016:38
cndmlankhorst, seb128: so my initial thoughts are that I haven't heard of such a bug before based on upstream activity16:38
cndand we need to do some deep dive debugging to figure it out, unless we can find a specific commit or patch that affects things16:38
cndif you can figure out *what* is going wrong, I can help figure out how to fix it16:38
seb128cnd, it's trivial to trigger for me, run gimp, create an image, turn touchpad off (that's my latitude e6410 laptop config)16:39
seb128cnd, I'm happy to test versions but report timing makes it pretty likely the issue is in ubuntu10.316:40
seb128cnd, I turn off the pad with gsd by doing the gsettings command I put it comment #5816:40
seb128cnd, let me know if I can be useful in debugging16:41
brycehseb128, have you tested 10.2 to verify that the bug isn't reproducible there?16:41
brycehactually, come to think of it I was just yesterday using gimp on a machine that has 10.2 loaded and it did not crash16:43
seb128bryceh, yes, downgrading to xserver-xorg-core (2:1.11.4-0ubuntu10.2) fixes it16:43
seb128ok, upgrading to 0ubuntu10.3 and the bug is back16:46
seb128it segfault on first click in gimp after turning the touchpad off16:46
seb128so16:46
seb128bryceh, cnd, mlankhorst: we need an upload to fix that today or tomorrow, do you think debugging the issue and fixing is a reasonable way out or should we look at reverting the ubuntu10.3 changes?16:46
seb128or do you want to look at fixing it for a bit and after $time go to fallback plan to revert?16:47
cndseb128, I'm sort of sprinting with the kernel team16:51
cndI didn't bring a second laptop16:51
cndso I can't today16:51
cndand I'm also not really *supposed* to be helping debug X stuff, since I have other day job stuff16:51
cndI know that mlankhorst is quite capable of that :)16:51
cndif he can't get to it for some reason, then I can try to step in16:51
cndseb128, I could probably reproduce it, but I can't debug it easily without a second machine at least16:51
cndthat's the blocker for me for today16:51
cndbut again, I need to focus on other work, and try to be a resource for determining a proper fix after the root cause has been identified16:51
cndseb128, it's that critical of an issue?16:51
cndseb128, we'd have to figure out what needs reverting first16:51
cndthe specific patch or commit would help16:51
seb128cnd, mlankhorst is unwell and went to bed16:52
seb128cnd, well, it's "xorg segfault when using gimp" which got introduced in a SRU,security update in the LTS, so it's an high importance issue yes16:52
seb128cnd, xorg closing might mean work and datas lost16:53
seb128cnd, but if you are busy no worry, I'm trying to estimate our easier way out16:53
brycehseb128, the 10.3 change set introduces six patches which fix one bug, which is also a crasher.  Reverting seems feasible and maybe lowest risk solution.16:53
mdeslaurbut wasn't 10.3 to fix a regression introduced in 10.2? :)16:54
seb128pick your least bad regression :p16:54
brycehmdeslaur, hrmm, well the 10.2 fix was to make touchpad work on macbookair16:56
mdeslaurwhich was incomplete and causing xephyr to segfault16:57
seb128well, xephyr to segfault is better than xorg to segfault16:57
mdeslaurso, it's pick the least evil of regressions :)16:57
brycehmdeslaur, right what I mean is that if we rolled that back too, then we would get into a state where nothing is crashing, just that macbooks have broken touchpads16:59
mdeslaurhrm, I agree, not ideal16:59
cndbryceh, seb128: the bug fixed by 10.3 is a much lesser evil than an X server crash17:00
brycehseb128, cnd if you'd like, I can take the action to revert the 10.3 and 10.2 changes17:02
seb128ok, at this point it's easier "we believe the easier way out is to fix the bug and we give it a few hours"17:02
seb128easier->either17:02
seb128or "let's revert and give us time then to figure what is wrong"17:02
seb128bryceh, what do you think?17:02
sbeattiebryceh: well, if we revert one or both, we should probably revert from the -security pocket as well.17:04
brycehseb128, it looks to me like reverting the patches from 10.2 and 10.3 would be the way to go, until this is better understood.17:07
seb128bryceh, great, can you get that done today and coordinate with sbeattie,mdeslaur to get the rollback in -security as well?17:08
brycehseb128, certainly17:08
seb128bryceh, then mlankhorst and cnd can probably investigate the segfault tomorrow17:08
seb128bryceh, thanks17:09
mlankhorstcnd: ^17:11
mlankhorstbut yeah it's fine if it gets reverted for now17:11
brycehsbeattie, I'm thinking just comment out the patches in question rather than doing a literal rollback to 10.1... sound right?17:11
mlankhorstsbeattie: the bug was filed before the security sru got released..17:12
sbeattiebryceh: yes, that's fine.17:12
mlankhorstso I don't thin kit had anything to do with it17:12
mlankhorstI'm not going to object to a rollback for now though :)17:13
cndthe bug would result in the touchpad doing wonky things if you have disable trackpad while typing and you use it a bit, and then it starts to act like extra touches are on the touchpad when more than one touch is used17:14
cndIIRC17:14
cndthe bug can also occur just by doing suspend/resume cycles17:14
cndbut it's stil not a crasher17:14
cndbryceh, I thought the 10.2 was ok?17:14
cndso just reverting the 10.3 changes would be good enough17:14
cndseb128, correct?17:14
cndbtw, I have really terribly high latency here17:14
cndwifi is terrible17:14
seb128cnd, right, 10.2 is correct (but it had a xephyr segfault issue)17:15
mlankhorstseb128: not just xephyr17:15
mlankhorstxorg-server under some conditions as well17:15
mlankhorstit's mentioned in the changelog, but xephyr was the easiest way to trigger it (sorry really slow today)17:16
brycehcnd, right; 10.3 attempted to fix the regression caused by 10.2.  10.2 itself was an attempt to fix a touchpad activation issue.17:17
cndbryceh, I don't think I'll be much use today between the sprint, wifi instability, and lack of machines, so if you can take care of the revert please do17:18
mlankhorstso yeah rollback to 10.117:18
mlankhorst+ security fix17:18
brycehcnd, yep I'll take care of the revert17:18
mlankhorstthanks bryceh :)17:18
cndok17:19
brycehmlankhorst, 10.4 added 516-dix-dont-emulate-scroll-events-for-non-existing-axes.patch which I'm guessing we'd like to keep?17:19
mlankhorstbryceh: I don't know, it should be in -proposed atm, not sure though if it is17:20
cnd+1 :)17:20
mlankhorstif not just comment it out again17:21
brycehok17:21
mlankhorstbryceh: I updated some drivers in xorg today btw to x1.13rc117:22
mlankhorstlikely going to need to touch all of them17:22
mlankhorstsince xaa was removed17:22
brycehsbeattie, btw the security patch 509 probably should have been numbered 228.  The comments in debian/patches/series are confusing but generally 5xx we were using just for the input frankenserver bits17:27
brycehI'll fix the comments so this is clearer17:28
seb128bryceh, btw do you know why apport doesn't trigger on xorg segfaults?17:28
seb128bryceh, is that a known issue,being worked?17:28
brycehseb128, yes it's a known issue discussed at UDS.  I believe RAOF has the action item to work on it.17:30
seb128bryceh, ok, thanks, I will check with him, if we had that we would probably have noticed that one earlier through errors.ubuntu.com17:30
brycehseb128, it's not that they're not being triggered, but that they trigger only in some cases17:30
seb128bryceh, well, that gimp segfault doesn't trigger it17:31
seb128it might turn out to be a good testcase ;-)17:31
brycehthe xserver has it's own crash handling code, which we had to bypass to make it work with apport, and it's always been a bit flaky17:31
sbeattiebryceh: ah, okay. kees was the one who handed it to me, so I'd assumed he'd gotten the numbering correct.17:31
sbeattiebryceh: anyway, let me know and I can shepherd things through the -security pocket.17:32
brycehsbeattie, yeah no prob, it's our fault that the sections weren't labeled clearly17:33
brycehsbeattie, ok, 1.11.4-0ubuntu10.6 uploaded18:08
sbeattiebryceh: thanks.18:22
keesbryceh, sbeattie: oh, whoops. sorry about that patch numbering. I missed that note :(19:33
=== yofel_ is now known as yofel

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