Confirmed on a Wacom Cintiq. Took a few iterations to find all the places in device-manager.cpp that Inkscape potentially dereferences a NULL device, but I've got a build which at least *starts* Inkscape and seems to handle basic functions (with the pen as well), in ppa:waveform/firmware. I'd be interested to hear if this fixes things for others as well (if so, I'll get the SRU ball rolling). To test:
sudo add-apt-repository ppa:waveform/inkscape sudo apt install inkscape There are currently builds for plucky and noble in that PPA; I can add one for oracular, if required (I'll need to do this anyway for SRU at some point). Also, the builds are for Intel and ARM architectures -- let me know if other archs are required for testing. On the subject of whether the bug is in Inkscape, Gdk, or Wayland, I had a quick look at what Gimp does in this area (given it's a similar user of Gdk, and wasn't crashing on the tablet). It seems everywhere it obtains a device list, it then checks each entry doesn't de-reference to NULL before using it, so maybe this is a bug in Inkscape after all? The Gdk docs didn't shed much (or any) light on whether all entries in the list could be dereferenced, although it certainly does seem an odd choice for an API to return a list in which certain entries can be effectively useless or invalid. Anyway, many thanks to Jerome for an excellent bug report -- it certainly makes things easier when there's a full backtrace and analysis to boot! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2079921 Title: inkscape crashes when started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/2079921/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
