Martin Owens wrote: > (…) I expect it's been fixed. Should we push for a fix for 0.48?
@Martin - just curious (because I fail to understand): how do you know what exactly to push (aka backport (?)), if you "expect" a so far not reproduced nor confirmed crash to be fixed in a code base which has seen quite a huge amount of changes wrt to the stable release branch? Could you attach the proposed backported patch for <lp:inkscape/0.48.x>? > status: New → Invalid Why? If this is a legitimate bug report for Inkscape 0.48.4, why close it as 'Invalid'? If not (i.e. there is no actual bug in the stable release 0.48.4 based on the provided data in this report) - then why proposing to push (aka backport (?)) some undeclared changes from trunk to fix an apparently invalid issue in 0.48.4? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194452 Title: inkscape crashed with SIGSEGV in sp_event_context_item_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1194452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
