Created attachment 81293 [details] Please find output of lspci -v, dmesg and Xorg.0.log attached. X crashes when trying to create an object with more than three characters in a previously saved Pure Data patch (version 44.3-2 and pd-extended 43.4-1). An intel gpu is required to reproduce this bug. The Pure Data devs claim this is a distribution bug or a bug in X. I'm using Arch Linux (xorg-server 1.14.1 and xf86-video-intel 2.21.9) but this is also experienced in Ubuntu 13.04: http://sourceforge.net/p/pure-data/bugs/1075/ This bug has also been reported in the Arch Linux bugtracker: https://bugs.archlinux.org/task/35830 STEPS TO REPRODUCE: Open a previously saved patch, create object box, type four characters. The fourth will crash X.
It looks more like an input driver bug. Can you please attach gdb and grab a symbolic backtrace (will require installing debug symbols)?
Created attachment 81334 [details] backtrace of xorg-server (gdb) I compiled xorg-server and xf86-video-intel with debug symbols and ran them through gdb. I hope that's what you meant, I've never used gdb before.. An educational evening. Please find the full output attached.
Thanks, that was very useful. commit c88d911d4209a8ede5ec705ad925383c69182977 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Jun 24 14:30:00 2013 +0100 sna: Initialise gc->ops->PolyPoint for miWideDash The miWideDash may also call PolyPoint rather than emit spans, so make sure that we correctly prepare sna_poly_point before calling mi*. Reported-by: Tobias Brodel <toby.jamesjoy@gmail.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=66104 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
The bug is marked as fixed. What has been fixed? Is the fix already committed and what will be the revision to checkout in order to patch a system affected by the bug? Thank you very much
Yes, that commit id is when the fix landed in the upstream repository and was released with xf86-video-intel-2.21.11.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.