appears to be a duplicate of
https://bugs.launchpad.net/inkscape/+bug/1671691
I would suggest trying the fix proposed at:
https://bugs.launchpad.net/inkscape/+bug/1671691/comments/7
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
could you attach the svg file you are using, for testing purposes?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1687817
Title:
Inkscape 0.92.1-1 always reverts display units to px
I believe that if you make sure that all the text is in a single group,
then it will work normally. In other words, do not ungroup the text.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
similar to Bug #1671059 ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1687817
Title:
Inkscape 0.92.1-1 always reverts display units to px
Status in Inkscape:
New
Status in
not reproduced on Windows 10, Inkscape 0.92.1 r15371
could you attach the svg file that you are saving, so that we can see
whether the problem is occurring during saving or loading the file?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
crash not reproduced on Windows XP, Inkscape 0.91+devel r14129 (May 8
2015)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1429127
Title:
Inkscape crash on select all same type
- confirmed on Windows 7, 32 bit, Inkscape 0.91 r13725 (Jan 30 2015)
- with no object selected, click on the menu item Edit-Select Same-Object
Type or Edit-Select Same-Stroke Style
- as far as I can tell, the crash does not occur if no object has ever been
created. It seems to occur after
@Kirby, you might wish to consider reading the entire thread above,
since there have been a number of very interesting points raised,
indicating that the 'correct' answer is not entirely clear cut.
In any event, this has been fixed in the Inkscape trunk, which is the
development version. The fix
two comments:
1. It looks as if this is a Cairo issue. The fill part of the text
is being rendered using a call to cairo_show_glyphs. The stroke part of
the text is being rendered using calls to cairo_stroke and
cairo_glyph_path. These calls are executed in libcairo-2.dll. They
originate in
sorry, I should have mentioned that you can modify these defaults to be
whatever you want:
- first create a text object with the defaults you like, for example fill but
no stroke.
- go to File-Inkscape Preferences
- then go to Tools-Text
- click on This tools own style
- click on 'Take from
confirmed on Windows XP, Inkscape rev 12093.
when viewing the pdf in Adobe Reader the separation seems to depend quite a bit
on the zoom level.
The problem appears to be related to the fact that this text has both
Fill and Stroke defined. Normally when you draw text in Inkscape, it
will
if you are running Windows 7 and if you get a message that says
Python.exe has stopped working, then see Bug 656938 (for example
comment 13 in that report). This is a packaging issue, as far as I can
tell.
I would suggest trying to install uniconvertor 1.1.5 from
to another machine running with a HP 1200 'all-in-one' printer.
is this machine also running Ubuntu?
it would be extremely helpful to know which version of Inkscape. Please
go to the Inkscape menu item 'Help About Inkscape' to get this info.
--
You received this bug notification because you
- are both of these printers all-in-one printers?
- are either or both of these printers configured to use borderless printing ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1075705
14 matches
Mail list logo
