- Inkscape Users - Inkscape Mailman

Inkscape .4 segfault
by Robert Davis 22 Dec '04

22 Dec '04

Been getting a segfault starting inkscape .4 and also tried a pre .4 that ran fine back in Oct. Using strace I traced it to icons.svg. Rename it and it runs fine. Any idea what might be wrong. Thanks Robert Davis system: Gentoo ~x86 backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 12092)] 0x0812cf67 in sigc::internal::signal_emit2<void, SPObject*, SPObject*, sigc::nil>::emit (impl=0x84321e8, _A_a1=@0xbfffe89c, _A_a2=@0x8432258) at slot_base.h:263 263 { return (!rep_ || !rep_->call_); } (gdb) bt #0 0x0812cf67 in sigc::internal::signal_emit2<void, SPObject*, SPObject*, sigc::nil>::emit (impl=0x84321e8, _A_a1=@0xbfffe89c, _A_a2=@0x8432258) at slot_base.h:263 #1 0x0812ca63 in Inkscape::URIReference::_setObject (this=0x8432248, obj=0x0) at signal.h:1806 #2 0x0812c7db in Inkscape::URIReference::attach (this=0x8432248, uri=@0x8432254) at uri-references.cpp:78 #3 0x080ec5db in sp_gradient_set (object=0x8432370, key=8, value=0x8420e88 "#linearGradient800") at sp-gradient.cpp:389 #4 0x080eec44 in sp_lineargradient_set (object=0x8432370, key=8, value=0x8420e88 "#linearGradient800") at sp-gradient.cpp:1157 #5 0x081012c4 in sp_object_set (object=0x8432370, key=24, value=0x18 <Address 0x18 out of bounds>) at sp-object.cpp:790 #6 0x081013d8 in sp_object_read_attr (object=0x8432370, key=0x82ab05a "xlink:href") at sp-object.cpp:811 #7 0x080ec39e in sp_gradient_build (object=0x8432370, document=0x83b1b80, repr=0x0) at sp-gradient.cpp:296 #8 0x080eebd3 in sp_lineargradient_build (object=0x8432370, document=0x84321f0, repr=0x8432288) at sp-gradient.cpp:1117 #9 0x08100a52 in sp_object_invoke_build (object=0x8432370, document=0x83b1b80, repr=0x8421780, cloned=0) at sp-object.cpp:642 #10 0x08100909 in sp_object_build (object=0x83aee08, document=0x83b1b80, repr=0x18) at sp-object.cpp:589 #11 0x08100a52 in sp_object_invoke_build (object=0x83aee08, document=0x83b1b80, repr=0x8419880, cloned=0) at sp-object.cpp:642 #12 0x08100909 in sp_object_build (object=0x83a40f0, document=0x83b1b80, repr=0x18) at sp-object.cpp:589 #13 0x080f6e9a in sp_item_build (object=0x83a40f0, document=0x18, repr=0x18) at sp-item.cpp:301 #14 0x080f3b55 in sp_group_build (object=0x83a40f0, document=0x18, repr=0x18) at sp-item-group.cpp:124 #15 0x0810c8a0 in sp_root_build (object=0x83a40f0, document=0x18, repr=0x84198c0) at sp-root.cpp:167 #16 0x08100a52 in sp_object_invoke_build (object=0x83a40f0, document=0x83b1b80, repr=0x84198c0, cloned=0) at sp-object.cpp:642 #17 0x080feefa in sp_object_repr_build_tree (document=0x83b1b80, repr=0x84198c0) at sp-object-repr.cpp:70 #18 0x080ca155 in sp_document_create (rdoc=0x0, uri=0x842c5e8 "/usr/local/share/inkscape/icons/icons.svg", base=0x84359f8 "/usr/local/share/inkscape/icons/", name=0x18 <Address 0x18 out of bounds>, advertize=0, keepalive=0) at document.cpp:289 #19 0x080ca779 in sp_document_new (uri=0x842c5e8 "/usr/local/share/inkscape/icons/icons.svg", advertize=24, keepalive=24, make_new=false) at document.cpp:434 #20 0x081e4e56 in sp_icon_image_load_svg (name=0x18 <Address 0x18 out of bounds>, size=10, scale=10) at icon.cpp:369 #21 0x081e4238 in sp_icon_image_load (name=0x842aca0 "sticky_zoom", size=10, scale=10) at icon.cpp:214 #22 0x081e403e in sp_icon_new_full (size=10, scale=10, name=0x842aca0 "sticky_zoom") at icon.cpp:158 #23 0x081e413c in sp_icon_new (size=24, name=0x8432288 "\uffff!C\b \uffff!C\b\2203C\b") at icon.cpp:185 #24 0x081e0fc1 in sp_button_set_action (button=0x842b688, action=0x841bfc0) at button.cpp:253 #25 0x081e0db1 in sp_button_new (size=10, type=24, action=0x18, doubleclick_action=0x0, tooltips=0x83ba060) at button.cpp:204 #26 0x081e1208 in sp_button_new_from_data (size=24, type=24, view=0x18, name=0x8432288 "\uffff!C\b\uffff!C\b\2203C\b", tip=0x18 <Address 0x18 out of bounds>, tooltips=0x18) at button.cpp:329 #27 0x0813dc94 in sp_desktop_widget_init (dtw=0x83b6bb0) at desktop.cpp:906 #28 0x40aaa025 in g_type_create_instance () from /usr/lib/libgobject-2.0.so.0 #29 0x000001ac in ?? ()

2 2

Build errors in CVS
by Trent Buck 22 Dec '04

22 Dec '04

I just tried to build Inkscape from CVS for the first time in a couple of weeks. I noticed the following Debian-specific problems: - AFAICT, python-dev and libperl-dev are now build dependencies; they should be added to the Build-Depends line in debian/control. - After building, dh_strip attempts to strip an ar archive, causing packaging to fail. From the build log: $ dpkg-buildpackage -rfakeroot [...] dh_installmime dh_link dh_strip strip: debian/inkscape/usr/lib/inkscape/plugins/stcstnTn/DynaLoader.a: Invalid operation dh_strip: command returned error code 256 make[2]: *** [binary-arch] Error 1 make[2]: Leaving directory `/alt/foo/pkg/cvs/inkscape/WORKING/inkscape' make[1]: *** [buildpackage] Error 2 make[1]: Leaving directory `/alt/foo/pkg/cvs/inkscape/WORKING/inkscape' -- -trent Look -- a diversion! It's shiny! -- Daniel Stone

2 1

outputting gradients
by Ben Crowell 21 Dec '04

21 Dec '04

>Gradients without transparency are doable in PS level 3, but we output >only level 2 so far. Fixing this would require an expert in PS because >level 3 differs significantly from previous levels. However, I don't >think it's worth the trouble, because transparency is not possible >even in level 3. It is however possible in PDF starting from version >1.4, so we better spend the same resources on supporting PDF instead. >For now, the best alternative that I know of is to import Inkscape SVG >into Scribus and save as PDF 1.4. Thanks for the rapid reply! Scribus actually didn't work on the example I tried. It didn't render the gradients correctly, and it also munged the fonts I was using (made Vera into a monospaced font). I guess I can render everything as png instead of pdf. (Pdftex can accept either as input.) Is anybody working actively on direct PDF output? The inability to output gradients to PS or PDF is a serious limitation that will probably be enough to prevent an awful lot of users from using Inkscape. Maybe my perceptions and priorities are different from other people's but it surprises me that people would be working on, e.g., Perl and Python extensions when a really basic feature like this is not yet implemented. Maybe it's just the nature of OSS: developers want to work on stuff that interests them personally, so that determines which features get added.

5 5

Satisfied user
by Alan Horkan 21 Dec '04

21 Dec '04

Thought I'd share this comment from a new satisfied Inkscape user: http://slashdot.org/comments.pl?sid=133308&cid=11135973

3 2

Textbox
by Imre Vida 21 Dec '04

21 Dec '04

Hi i've only recently discovered Inkscape and found it very promising. However, there is a feature that i miss a lot: the possility to define a frame for text with 1) dynamic line wrapping and 2) "local" formating options (e.g to mix various types of fonts, to use bold, italic, superscripts, subscripts in the text etc.). I have looked at the list of requested features and i found several related entries (e.g. 863325, 1084658 and 1080623) some of them dating back to last year. But there seems to be very little response to these requests. Without this feature inkscape is not a real alternative for me, unfortunately. Do you plan to implement such a feature? thanks imre

4 3

-users -developers test please ignore
by vellum 20 Dec '04

20 Dec '04

1 0

test ignore
by vellum 20 Dec '04

20 Dec '04

1 0

Re: applying a common style Re: [Inkscape-devel] Re: Font size after scaling?
by vellum 20 Dec '04

20 Dec '04

vellum said: > On Thu, 16 Dec 2004 22:11:16 +1100, vellum <kaver@...45...> wrote: > > However, with non-uniform scaling all hell breaks loose. > > First. Scaling vertically changes the font size as I would expect. However > > if I then try to change the font size to the original size then the font > > dialog font size is correct but the screen presentation is not. bulia said: > Yes, because non-uniform scaling cannot be expressed via font size > change. Thus it is factored into two parts, as I explained. When you > reset font size to original, you remove only the uniform component of > the scale; the non-uniform one remains. I think this is logical. ... > So, can you just explain the final result you're trying to achieve? 1. I want to be able to turn a piece of text that has been scaled uniformly or non-uniformly, back to its original state. ie. as it was written. OK. Your changes allow this to be done with uniformly scaled text. So my original problem is solved. However, I do not understand what is happening with non-uniform scaling, and it worries me that it simply may be giving the wrong result. The simplest case is where the text is stretched or compressed with no vertical change. The present code changes the font size. Why? I just cannot find anywhere that this is the correct result. As far as I can see the font size should be the same after as before. XaraX1 operates in the way that I see as correct. It shows two windows for a text object. 1. The font size. 2. The Aspect Ratio which is Width/Height as a percentage. The AR is 100.00 for any font size as initially written. With non-uniform scaling. The new font size is shown and the AR goes >100 or <100% depending on the scaling. When a piece of text is reselected the new AR and the font size are shown. It is straightforward to set the AR to 100 and the font size to your original font size and you get the original sized text back. Inkscape cannot not do this. With horizontal stretching or compressing. With Xarax1 there is no change in font size no matter how much the text width is changed. This is consistent with font size based on letter height. With Inkscape the font size changes with the text width. I think this is wrong. I do not know the details of what the programs are doing but Xarax seems consistent with > > David Bergs idea of "A button "set as 100%" for height and width will then > > adjust the font-size according to the skewed/streched width or the height > > respectively. I think this way all needs are served ;)" seems like a good > > one. Perhaps this could also go in the font dialog ultimately. I would leave skewed text further down the priority list since I ceratinly do not use it routinely and nobody else has chimed in with this as a need or problem. If I can get non-uniform scaling sorted I'll be happy. > > P.S. Perhaps you noticed the bug: the font size reported in the > statusbar in selector for a text object is wrong (unchanged) after > scale. This is completely unrelated to the above discussion. Just > deselect and reselect it again to see the correct font size. yes. vellum

1 0

outputting gradients
by Ben Crowell 19 Dec '04

19 Dec '04

Bulia wrote: >Personally, I would much prefer to have standard system-wide >high-quality SVG->PDF and PS->SVG converters that we could use, >without having to code them into Inkscape. Such a modular approach >would be the best for everyone. The idea that every single design app >must import and export all common formats is, IMHO, a harmful >misconception originated on proprietary platforms where each app has >to be self-sustaining and cannot count on cooperation from other >programs. We can save a lot of resources by not following this model. >I see no problem in having to run Inkscape files through Scribus or >some other converter [1] when I need PDF, provided it is as >cross-platform as we are and produces good output. I agree with you in principle that it might be good design to have a whole different piece of software whose job was SVG->PS or SVG->PDF. However, as far as I can tell, Scribus isn't going to fill that role, and I'm not aware of any other project that will. Scribus isn't cross-platform, it has no command-line interface AFAICT, at the moment it does not do a very good job on SVG->PDF, and I don't see any signs that they consider it to be part of their core mission to act as an automatic behind-the-scenes SVG->PDF converter that other programs can use library-fashion. To me, it would be much more logical for such functionality to be in Inkscape, rather than Scribus; but then, that's easy for me to say, since I don't have the C++ skills or the time that would be needed to do the necessary work on Inkscape :-)

2 1

outputting gradients
by Ben Crowell 19 Dec '04

19 Dec '04

This bug http://sourceforge.net/tracker/index.php?func=detail&aid=984043&group_id=93… refers to a problem with outputting gradients to postscript. Is there any workaround for this problem? I'm trying to produce PDF output, and have been doing it by doing a Save As, followed by epstopdf.

2 1