Latest beta (XQuartz 2.7.2_beta4) crashes with Inkscape (stable and trunk)
Hi, recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2: Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914> Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash> I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011). Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected. Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated. Thanks, ~suv
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab. If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =) My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637... On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I found a binary that triggers it. Indeed reverting 7790dc86384cc451ac44663737fde84dd81ad4e1 does make the issue go away, but now the question is why. The change itself seems correct, so now I need to figure out what is wrong under the hood. Thanks, Jeremy On Apr 5, 2012, at 12:43 PM, Jeremy Huddleston <jeremyhu@apple.com> wrote:
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab.
If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =)
My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637...
On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Binary package: download "Inkscape-0.48.2-1-SNOWLEOPARD.dmg" from <http://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/> (32bit Universal (PPC, Intel), built and packaged on Mac OS X 10.5.8) Steps to reproduce: 1) Launch Inkscape.app (it opens with a new, empty document) 2) resize the window -> works ok 3) click once with the mouse pointer on the canvas area -> XQuartz (and Inkscape) crash Quoting from the report in Inkscape's bug tracker: «Inkscape crashes (XQuartz crashes also) when clicking inside the drawing area with the following tools: Select, Node, Zoom, Rectangle, 3D, Circle, Polygon, Spiral, Freehand, Bezier, Calligraphic, Text, Eraser and Eyedropper. Apart from this Inkscape functions normally: I can resize the window, scroll up + down, select the 'fill and stroke' and 'text properties' etc I am even able to click in the drawing area with some of the other tools without it crashing: Tweak, Spray, Fill Bucket, Gradient and the Diagram Connector (which successfully draws connections on the drawing area, they can even be moved around without crashing).» <https://bugs.launchpad.net/inkscape/+bug/972914> hth, ~suv On 05/04/2012 21:43, Jeremy Huddleston wrote:
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab.
If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =)
My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637...
On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
I have a fix. Thanks for the info. --Jeremy On Apr 5, 2012, at 1:15 PM, ~suv <suv-sf@users.sourceforge.net> wrote:
Binary package: download "Inkscape-0.48.2-1-SNOWLEOPARD.dmg" from <http://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/> (32bit Universal (PPC, Intel), built and packaged on Mac OS X 10.5.8)
Steps to reproduce: 1) Launch Inkscape.app (it opens with a new, empty document) 2) resize the window -> works ok 3) click once with the mouse pointer on the canvas area -> XQuartz (and Inkscape) crash
Quoting from the report in Inkscape's bug tracker:
«Inkscape crashes (XQuartz crashes also) when clicking inside the drawing area with the following tools: Select, Node, Zoom, Rectangle, 3D, Circle, Polygon, Spiral, Freehand, Bezier, Calligraphic, Text, Eraser and Eyedropper.
Apart from this Inkscape functions normally: I can resize the window, scroll up + down, select the 'fill and stroke' and 'text properties' etc
I am even able to click in the drawing area with some of the other tools without it crashing: Tweak, Spray, Fill Bucket, Gradient and the Diagram Connector (which successfully draws connections on the drawing area, they can even be moved around without crashing).»
<https://bugs.launchpad.net/inkscape/+bug/972914>
hth, ~suv
On 05/04/2012 21:43, Jeremy Huddleston wrote:
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab.
If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =)
My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637...
On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
The fix is in MacPorts' xorg-server-devel (not yet in xorg-server). I'd appreciate verification that things work as expected when using that server. The fix will be in the next beta/rc release. Thanks. On Apr 5, 2012, at 1:15 PM, ~suv <suv-sf@users.sourceforge.net> wrote:
Binary package: download "Inkscape-0.48.2-1-SNOWLEOPARD.dmg" from <http://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/> (32bit Universal (PPC, Intel), built and packaged on Mac OS X 10.5.8)
Steps to reproduce: 1) Launch Inkscape.app (it opens with a new, empty document) 2) resize the window -> works ok 3) click once with the mouse pointer on the canvas area -> XQuartz (and Inkscape) crash
Quoting from the report in Inkscape's bug tracker:
«Inkscape crashes (XQuartz crashes also) when clicking inside the drawing area with the following tools: Select, Node, Zoom, Rectangle, 3D, Circle, Polygon, Spiral, Freehand, Bezier, Calligraphic, Text, Eraser and Eyedropper.
Apart from this Inkscape functions normally: I can resize the window, scroll up + down, select the 'fill and stroke' and 'text properties' etc
I am even able to click in the drawing area with some of the other tools without it crashing: Tweak, Spray, Fill Bucket, Gradient and the Diagram Connector (which successfully draws connections on the drawing area, they can even be moved around without crashing).»
<https://bugs.launchpad.net/inkscape/+bug/972914>
hth, ~suv
On 05/04/2012 21:43, Jeremy Huddleston wrote:
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab.
If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =)
My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637...
On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
Many thanks for the quick confirmation and fix! I don't have 'xorg-server(-devel)' installed via MacPorts (last time I checked xinit refused to install as non-root, without startup item) and will test with next beta as soon as available. ~suv On 06/04/2012 03:45, Jeremy Huddleston wrote:
The fix is in MacPorts' xorg-server-devel (not yet in xorg-server). I'd appreciate verification that things work as expected when using that server. The fix will be in the next beta/rc release.
Thanks.
On Apr 5, 2012, at 1:15 PM, ~suv <suv-sf@users.sourceforge.net> wrote:
Binary package: download "Inkscape-0.48.2-1-SNOWLEOPARD.dmg" from <http://sourceforge.net/projects/inkscape/files/inkscape/0.48.2/> (32bit Universal (PPC, Intel), built and packaged on Mac OS X 10.5.8)
Steps to reproduce: 1) Launch Inkscape.app (it opens with a new, empty document) 2) resize the window -> works ok 3) click once with the mouse pointer on the canvas area -> XQuartz (and Inkscape) crash
Quoting from the report in Inkscape's bug tracker:
«Inkscape crashes (XQuartz crashes also) when clicking inside the drawing area with the following tools: Select, Node, Zoom, Rectangle, 3D, Circle, Polygon, Spiral, Freehand, Bezier, Calligraphic, Text, Eraser and Eyedropper.
Apart from this Inkscape functions normally: I can resize the window, scroll up + down, select the 'fill and stroke' and 'text properties' etc
I am even able to click in the drawing area with some of the other tools without it crashing: Tweak, Spray, Fill Bucket, Gradient and the Diagram Connector (which successfully draws connections on the drawing area, they can even be moved around without crashing).»
<https://bugs.launchpad.net/inkscape/+bug/972914>
hth, ~suv
On 05/04/2012 21:43, Jeremy Huddleston wrote:
Yeah, I saw some beta4 crash reports come in through Apple's crash reporting system a few days ago, and the one which had useful feedback provided (yes, we do read that field...) mentioned gimp. I was planning to try reproducing it this week, but unfortunately I have no information other than that gimp triggered it and the backtrace which shows it failing in a grab.
If you can tell me what you do to trigger this, it would be helpful. For "clicking on Inkscape's canvas area", do you mean you open a new image in inkscape and just click on it? I'm currently building inkscape and gimp through MacPorts right now, but if you can point me to a binary package that you have that you know triggers it, I'd appreciate using that instead since I actually have quite a few dependencies to build =)
My hunch is that there is some fallout due to something related to this change: http://cgit.freedesktop.org/xorg/xserver/commit/?id=7790dc86384cc451ac446637...
On Apr 5, 2012, at 9:26 AM, ~suv <suv-sf@users.sourceforge.net> wrote:
Hi,
recently we got a bug report for Inkscape 0.48.2 on OS X 10.7.2 (X11 crashes when clicking on Inkscape's canvas area) which seems to be triggered by changes in the latest XQuartz beta release for 2.7.2:
Bug #972914 "[OS X] Crash when clicking inside drawing area" <https://bugs.launchpad.net/inkscape/+bug/972914>
Inkscape's console message:
inkscape-bin: Fatal IO error 35 (Resource temporarily unavailable) on X server /tmp/launch-JR8gbQ/org.macosforge.xquartz:0.
and from the X11.bin crash report:
Thread 3 Crashed: 0 X11.bin 0x00000001000c747e ActivateKeyboardGrab + 104 1 X11.bin 0x00000001000ccb52 GrabDevice + 718 2 X11.bin 0x00000001000849d3 ProcXGrabDevice + 258 3 X11.bin 0x00000001000be4d2 Dispatch + 257 4 X11.bin 0x00000001000275be dix_main + 185 5 X11.bin 0x0000000100011f4f server_thread + 38 6 libsystem_c.dylib 0x00007fff939008bf _pthread_start + 335 7 libsystem_c.dylib 0x00007fff93903b75 thread_start + 13
Full crash report for X11.bin: <https://bugs.launchpad.net/inkscape/+bug/972914/+attachment/2999102/+files/X11.bin_2012-04-03-220711.crash>
I have been able to reproduce the crash (temporarily upgraded to XQuartz 2.7.2 beta4 on OS X 10.7.2) with Inkscape 0.48.2 installed via (up-to-date) MacPorts as well as current trunk builds (Inkscape 0.48+devel r11155) - to make sure it is not related to conflicts with older library versions included in the official package (July 2011).
Reverting to stable XQuartz 2.7.1 solves the issue and Inkscape (stable and trunk) works again as expected.
Any feedback on this (possibly known (?)) conflict with XQuartz 2.7.2 beta4 would be highly appreciated.
Thanks, ~suv
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
On Apr 5, 2012, at 7:23 PM, ~suv <suv-sf@users.sourceforge.net> wrote:
Many thanks for the quick confirmation and fix!
I don't have 'xorg-server(-devel)' installed via MacPorts (last time I checked xinit refused to install as non-root, without startup item) and will test with next beta as soon as available.
Yeah, xinit needs to install a LaunchDaemon to handle some privileged aspects of startup =/
On 06/04/2012 03:45, Jeremy Huddleston wrote:
The fix is in MacPorts' xorg-server-devel (not yet in xorg-server). I'd appreciate verification that things work as expected when using that server. The fix will be in the next beta/rc release.
XQuartz 2.7.2_beta5 (xorg-server 1.12.1) no longer crashes with Inkscape (stable and current trunk) - tested on OS X 10.7.2, MBP 13" with built-in trackpad and external mouse (Logitech). Tests with Wacom tablet (Bamboo Pen&Touch) not yet done. Many thanks for the update! ~suv
On 17/04/2012 08:32, ~suv wrote:
On 06/04/2012 03:45, Jeremy Huddleston wrote:
The fix is in MacPorts' xorg-server-devel (not yet in xorg-server). I'd appreciate verification that things work as expected when using that server. The fix will be in the next beta/rc release.
XQuartz 2.7.2_beta5 (xorg-server 1.12.1) no longer crashes with Inkscape (stable and current trunk) - tested on OS X 10.7.2, MBP 13" with built-in trackpad and external mouse (Logitech).
Tests with Wacom tablet (Bamboo Pen&Touch) not yet done.
Wacom tablet input looks ok too: - works on UI (menu, toolbars, etc) as well as on-canvas (drawing) - cursor is not offset (reported for earlier betas) - pressure sensitivity is fine, too Tested with Inkscape 0.48.2, 0.48.3.1, 0.48+devel r11265 and MyPaint 1.0.0 System: OS X 10.7.2, MBP 13-inch Late 2011, Wacom Bamboo CTH-470 XQuartz 2.7.2_beta5 (xorg-server 1.12.1) ~suv
participants (2)
-
Jeremy Huddleston
-
~suv