Inkscape crash on creating print marks

Bug #1802457 reported by Eyal Lior
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Undecided
Unassigned

Bug Description

I select an object (a rectangle) and do Extensions>Render>Layout>Printing Marks, then I check any combination of checkboxes and get the crash: "Inkscape encountered an internal error and will close now."

Workaround: start inkscape and then only open the file, then no crash
To reproduce the crash: lunch inkscape by double clicking the file, then the extension will crash when hitting ok

Revision history for this message
Alvin Penner (apenner) wrote :

not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)

- could you attach the svg file you are using?
- which OS?, which version of Inkscape (see Help->About)
- if you are getting a different result depending on how you open the file, then it is likely that you have multiple instances of Inkscape installed or multiple instances of the Python file. could you do a global search to see if there is more than one 'Inkscape.exe' file or more than one 'printing_marks.py' file?

Revision history for this message
Eyal Lior (eyallior) wrote : Re: [Bug 1802457] Re: Inkscape crash on creating print marks

Attached.
Ubuntu 18.04.1 LTS
When I double click an svg, this inkscape opens:
0.92.3 (2405546, 2018-03-11)

Looks like I have 2 versions:
0.92.3 (2405546, 2018-03-11)
0.92.3 (d244b95, 2018-08-02)

However, the workaround is with the same version (0.92.3 (2405546,
2018-03-11). Another thing is that once I've started working on a new file
(copied some objects to a new file, started to work on it) the crash
doesn't happen, so it's probably something in this (attached) file. Select
the business-card on the right and try to add print marks.

Eyal Lior
<email address hidden>
053-5201397 (+972-53-5201397)

On Fri, Nov 9, 2018 at 1:55 PM Alvin Penner <email address hidden> wrote:

> not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
>
> - could you attach the svg file you are using?
> - which OS?, which version of Inkscape (see Help->About)
> - if you are getting a different result depending on how you open the
> file, then it is likely that you have multiple instances of Inkscape
> installed or multiple instances of the Python file. could you do a global
> search to see if there is more than one 'Inkscape.exe' file or more than
> one 'printing_marks.py' file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1802457
>
> Title:
> Inkscape crash on creating print marks
>
> Status in Inkscape:
> New
>
> Bug description:
> I select an object (a rectangle) and do
> Extensions>Render>Layout>Printing Marks, then I check any combination
> of checkboxes and get the crash: "Inkscape encountered an internal
> error and will close now."
>
> Workaround: start inkscape and then only open the file, then no crash
> To reproduce the crash: lunch inkscape by double clicking the file, then
> the extension will crash when hitting ok
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/inkscape/+bug/1802457/+subscriptions
>

Revision history for this message
Alvin Penner (apenner) wrote :

thanks for the file.
On Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11)
and also Inkscape 0.92.3 (0612fd7, 2018-10-23)
I am unable to reproduce the crash. The printing marks are shown in the attached file.

off-topic: however I do get a crash when opening this file in the latest trunk version, so I will report that as a separate bug.

tags: added: bug-migration extensions-plugins
Revision history for this message
grey tomorrow (gtomorrow) wrote :

Hi - thanks for reporting this bug, I've manually migrated it to Inkscape's new bug tracker on GitLab, and closed it here.

Please feel free to file new bugs about the issues you're seeing at http://inkscape.org/report.

Moved to: https://gitlab.com/inkscape/inbox/issues/2068
Closed by: https://gitlab.com/greytomorrow

Changed in inkscape:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.