assertion hit when running inkscape without DISPLAY set
Bug #167857 reported by
Bryce Harrington
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Fix Released
|
Medium
|
Unassigned | ||
inkscape (Debian) |
Fix Released
|
Unknown
|
|||
inkscape (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Steps to reproduce:
1. ssh into a remote machine that is running X and has
inkscape installed.
2. Try launching inkscape with a file:
$ inkscape mint.svg
(inkscape:19059): Gdk-CRITICAL **:
gdk_display_
(display)' failed
(inkscape:19059): GLib-GObject-
g_object_
This situation really should just produce an error
message, such as happens if you run inkscape alone:
$ inkscape
Nothing to do!
(That's not the most informative error message in the
world... but it's better than an assert...)
Changed in inkscape: | |
status: | New → Confirmed |
Changed in inkscape (Debian): | |
status: | Unknown → Fix Released |
tags: | added: cli |
To post a comment you must log in.
Does it make any difference if you give inkscape the -z option?