inkscape crashed with SIGSEGV in sp_event_context_item_handler()

Stacktrace:
 #0 sp_event_context_item_handler (event_context=0x0, event_context@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>, item=0x4f275f0, item@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>, event=0x622dec0, event@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>) at event-context.cpp:958
 No locals.
 Cannot access memory at address 0x7fff80845ad8
StacktraceTop: sp_event_context_item_handler (event_context=0x0, event_context@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>, item=0x4f275f0, item@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>, event=0x622dec0, event@entry=<error reading variable: Cannot access memory at address 0x7fff80845ad8>) at event-context.cpp:958
ThreadStacktrace:
 .
 Thread 3 (LWP 11608):
 #0 0x00007fcfee3413cd in ?? ()
 No symbol table info available.
 .

Tested with latest version of inkscape (trunk) and no error is found. I expect it's been fixed. Should we push for a fix for 0.48?

Crash not reproduced based on the provided steps (assuming "text zone" is referring to "Flowed text" - it remains unclear to me whether the reporter switched tools in-between or not, though either way the crash was not reproducible in my tests), with
- Inkscape 0.48.3.1, 0.48.4 and 0.48+devel r12388 on OS X 10.7.5 (tested with builds using either of the two available GTK+ backends on this platform, with various versions of the dependencies)
- Inkscape 0.48.4 on Ubuntu 13.04 (VM, 64bit)
- Inkscape 0.48.3.1 and 0.48+devel r12383 on Ubuntu 12.10 (VM, 64bit)
- Inkscape 0.48+devel r12388 (PPA) on Ubuntu 12.04 (VM, 64bit)
(all tests have been done with default (new) preferences for each launch)

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?

The fact that the bug can't be reproduced by bug triagers doesn't mean it's fixed!
We could close it 'invalid' if the reporter confirms that the issue doesn't occur anymore on the same computer, or if it can't be reproduced after a significantly longer testing period.
But for now, I suggest we revert the status to 'new'.

David: Is this still happening with 0.91 or 0.92?

Closing because this cannot be reproduced and there has been no response for several years.

If you still have a similar issue, uninstall and make sure there are no leftover files, then install the latest version of Inkscape. If the issue still exists, please file a new bug at https://gitlab.com/inkscape/inbox. Thank you!

Closed by: https://gitlab.com/Qantas94Heavy