- Inkscape Devel - Inkscape Mailman

svn 11251 dumps core
by inkbottle 07 Apr '06

07 Apr '06

Here is a reproducible crash on svn revision 11251. My 12-year old found this crash running .43 on FC4. I reproduced the problem on FC5 at the tip of svn, rebuilt inkscape debug and produced a stack trace from the core file. The crash is caused reliably in the following way. Enter some text. Zoom in on the text, or make it big enough to work with easily. The text I used was "This is some text". Select the text tool. use that tool to select,say, the initial T. Change the size of the text to something else noticeably different, it doesn't matter what. The T changes size appropriately. Then place a gradient on the text string as a whole. Now select, say, the s in 'some' with the text tool. Change the size of that s to any other size. Poof! inkscape dumps core, and vanishes. Here is the gdb backtrace. It is a bit beyond me at the moment. This has something to do with text, gradients and, from the backtrace, selection and styles. I'm hoping someone can make more sense of the backtrace than I. (gdb) where #0 0x005ec402 in __kernel_vsyscall () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #1 0x00e22159 in raise () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #2 0x00e236e3 in abort () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #3 0x082d1ca8 in inkscape_segv_handler (signum=11) at inkscape.cpp:375 #4 <signal handler called> #5 0x08648c53 in Inkscape::UI::Widget::SelectedStyle::update (this=0xa74e800) at ui/widget/selected-style.cpp:893 #6 0x086495e1 in ss_selection_changed (data=0xa74e800) at ui/widget/selected-style.cpp:46 #7 0x08649618 in ss_selection_modified (selection=0xa6affc0, flags=11, data=0xa74e800) at ui/widget/selected-style.cpp:52 #8 0x0838d6da in sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>::operator() (this=0xa7a6110, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4, _A_a3=@0xbfa52af4) at /usr/include/sigc++-2.0/sigc++/functors/ptr_fun.h:185 #9 0x08662e17 in sigc::adaptor_functor<sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void> >::operator()<Inkscape::Selection* const&, unsigned int const&, Inkscape::UI::Widget::SelectedStyle*&> (this=0xa7a610c, _A_arg1=@0xbfa52be4, _A_arg2=@0xbfa52bf4, _A_arg3=@0xa7a6114) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:123 #10 0x08662e4e in sigc::bind_functor<-1, sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>::operator()<Inkscape::Selection* const&, unsigned int const&> (this=0xa7a6108, _A_arg1=@0xbfa52be4, _A_arg2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/adaptors/bind.h:1144 #11 0x08662e78 in sigc::internal::slot_call2<sigc::bind_functor<-1, sigc::pointer_functor3<Inkscape::Selection*, unsigned int, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void, Inkscape::Selection*, unsigned int>::call_it (rep=0xa7a60f0, a_1=@0xbfa52be4, a_2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:173 #12 0x082e7d19 in sigc::internal::signal_emit2<void, Inkscape::Selection*, unsigned int, sigc::nil>::emit (impl=0xa7a3ca8, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/signal.h:832 #13 0x082e7de2 in sigc::signal2<void, Inkscape::Selection*, unsigned int, sigc::nil>::emit (this=0xa6afff0, _A_a1=@0xbfa52be4, _A_a2=@0xbfa52bf4) at /usr/include/sigc++-2.0/sigc++/signal.h:1924 #14 0x082e661a in Inkscape::Selection::_emitModified (this=0xa6affc0, flags=11) at selection.cpp:93 #15 0x082e6651 in Inkscape::Selection::_emit_modified (selection=0xa6affc0) at selection.cpp:85 ---Type <return> to continue, or q <return> to quit--- #16 0x00d8b6e1 in g_list_remove_link () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #17 0x00d8d09d in g_main_context_dispatch () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #18 0x00d9032f in g_main_context_check () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #19 0x00d906d9 in g_main_loop_run () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #20 0x03b39a6b in gtk_dialog_run () at /usr/lib/gcc/i386-redhat-linux/4.1.0/../../../../include/c++/4.1.0/exception:56 #21 0x082d25ef in inkscape_segv_handler (signum=11) at inkscape.cpp:525 #22 <signal handler called> #23 0x08648c53 in Inkscape::UI::Widget::SelectedStyle::update (this=0xa74e800) at ui/widget/selected-style.cpp:893 #24 0x086495e1 in ss_selection_changed (data=0xa74e800) at ui/widget/selected-style.cpp:46 #25 0x086495fd in ss_subselection_changed (dragger=0xa659a00, data=0xa74e800) at ui/widget/selected-style.cpp:58 #26 0x084f9f96 in sigc::pointer_functor2<void*, void*, void>::operator() ( this=0xa7a61a8, _A_a1=@0xbfa538c4, _A_a2=@0xbfa53804) at /usr/include/sigc++-2.0/sigc++/functors/ptr_fun.h:147 #27 0x08662ea4 in sigc::adaptor_functor<sigc::pointer_functor2<void*, void*, void> >::operator()<void* const&, Inkscape::UI::Widget::SelectedStyle*&> ( this=0xa7a61a4, _A_arg1=@0xbfa538c4, _A_arg2=@0xa7a61ac) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:103 #28 0x08662ed3 in sigc::bind_functor<-1, sigc::pointer_functor2<void*, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>::operator()<void* const&> (this=0xa7a61a0, _A_arg1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/adaptors/bind.h:1122 #29 0x08662ef7 in sigc::internal::slot_call1<sigc::bind_functor<-1, sigc::pointer_functor2<void*, void*, void>, Inkscape::UI::Widget::SelectedStyle*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>, void, void*>::call_it (rep=0xa7a6188, a_1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:137 #30 0x0837e5ae in sigc::internal::signal_emit1<void, void*, sigc::nil>::emit ( impl=0xa7a6158, _A_a1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/signal.h:686 #31 0x0837e66f in sigc::signal1<void, void*, sigc::nil>::emit (this=0xa6aef94, _A_a1=@0xbfa538c4) at /usr/include/sigc++-2.0/sigc++/signal.h:1812 #32 0x08377605 in SPDesktop::emitToolSubselectionChanged (this=0xa6aee00, data=0xa659a00) at desktop.cpp:1017 ......

3 2

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 07 Apr '06

07 Apr '06

Bunch of new warnings today in knot.cpp. Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Thu, 06 Apr 2006 17:21:33 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Thu Apr 6 17:10:56 2006 (Run 1936) Snapshot: inkscape-20060406-1600.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 27 0 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == none == Warnings == knot.cpp:109: warning: invalid access to non-static data member `SPKnotClass::event' of NULL object knot.cpp:109: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:118: warning: invalid access to non-static data member `SPKnotClass::clicked' of NULL object knot.cpp:118: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:127: warning: invalid access to non-static data member `SPKnotClass::doubleclicked' of NULL object knot.cpp:127: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:136: warning: invalid access to non-static data member `SPKnotClass::grabbed' of NULL object knot.cpp:136: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:145: warning: invalid access to non-static data member `SPKnotClass::ungrabbed' of NULL object knot.cpp:145: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:154: warning: invalid access to non-static data member `SPKnotClass::moved' of NULL object knot.cpp:154: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:163: warning: invalid access to non-static data member `SPKnotClass::request' of NULL object knot.cpp:163: warning: (perhaps the `offsetof' macro was used incorrectly) knot.cpp:172: warning: invalid access to non-static data member `SPKnotClass::distance' of NULL object knot.cpp:172: warning: (perhaps the `offsetof' macro was used incorrectly) sp-flowtext.cpp:339: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-item.cpp:744: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:733) sp-shape.cpp:609: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:644: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:723: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) trace/trace.cpp:196: warning: unused variable `Inkscape::XML::Node*imgRepr' == Environment Summary == ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

Clipping and masking bugs
by Tavmjong Bah 06 Apr '06

06 Apr '06

Hi, I've begun to update my book for 0.44. Should be a great release! But, I have run into a few bugs with a version of Inkscape from SVN a day or two ago. The following file can be used to illustrate the problems: http://tavmjong.free.fr/INKSCAPE/DRAWINGS/ClipMask2.svg The raw objects for clipping and masking are on the left, the clipped and masked objects (blue rectangles) are on the right. In the case of the first two items, the file is displayed correctly in Firefox trunk. 1. Clipping using stroked text without fill doesn't seem to work. 2. The masked object is invisible when the file is saved and reopened. The masked object can be restored by selecting the object, unmasking and remasking. 3. Sometimes the display of the gradient is not updated when the gradient tool is used to adjust it. Try editing the gradient in the above document by dragging a gradient node. 4. Not really a bug... but very confusing. The gradient editor does not switch to the gradient selected with the the gradient tool. This behavior is different from all other dialogs. If needed, I'll file bug reports but I thought I would bring them up here first. Tav

2 3

IO::Resource vs. Binreloc
by Aaron Spike 06 Apr '06

06 Apr '06

I was going to build an autopackage this morning for those who would like to play with the new keymaps but the build errored out with the following message. I'm assuming that it is caused by Binreloc because that is something that is different in the autopackage build. I understand some of the words but it is still a little beyond me. mental? Aaron Spike io/resource.cpp: In function ‘Inkscape::Util::ptr_shared<char> Inkscape::IO::Resource::get_path(Inkscape::IO::Resource::Domain, Inkscape::IO::Resource::Type, const char*)’: io/resource.cpp:38: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:39: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:40: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:41: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:42: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:43: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:44: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:45: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:46: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:47: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:48: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:49: error: invalid conversion from ‘const char*’ to ‘gchar*’ io/resource.cpp:50: error: invalid conversion from ‘const char*’ to ‘gchar*’

2 2

[new] configurable keymaps
by MenTaLguY 06 Apr '06

06 Apr '06

I've just committed basic support for configurable keymaps. You'll probably need to do a fresh ./configure to get share/keys -- and a 'make install' to install share/keys/default.xml and get your keyboard shortcuts back! share/keys/default.xml contains the default key configuration for Inkscape; until I document the format further, you can use it for reference when developing your own keymaps. The key names in it are GDK keysym names. share/keys/default.xml gets loaded first, followed by ~/.inkscape/keys/default.xml if it exists. At present, a user keymap is overlaid on the system keymap rather than clearing it completely. -mental

1 0

Icons, and cursors, and multiples... oh my
by Jon A. Cruz 05 Apr '06

05 Apr '06

I was skimming through my log, and noticed a few things that could be brought up here... First is reusing the icon code for cursors. This is probably a good idea, and for even more reason than thought. One of the additional benefits would be nice fallback to CREATE assets, etc. I'm fairly up on the various bits of code involved, and also cursor stuff, so definitely hit me up about it. Oh... and a minor point... the XPM spec (what we use for our cursors currently) allows for the hot X and Y to be in the XPM file itself. I was looking at this a bit, as it would take the position hardcoding out of our source code that loads icons. The default routines don't give you X and Y, but I can add it easily. We probably could fold this in to the other cursor work with minimal effort. Then there's the whole thing about multiple export. It's actually not to hard to do... and something I'm doing in the Icon Preview dialog. With just a little bit of tuning, that can be refactored to also support multiple-res export. This would be good for icons and cursors, and is very low-hanging fruit in that I can probably get it going in a day or so. Plus there've been enough user requests to make something like that worthwhile. So... start thinking about how this could be done for the most effect with the least effort. Hitting cursors and icon needs would be the minimum. Roughing this out could help both the export and the preview. Oh, and one of the other features I was looking at was adding librsvg rendering to the icon preview window. Again, I've done all the research on it and it will take only a small bit of coding (perhaps less than hooking in LittleCms took). I'm wondering if this might be useful as an option for the multi-export, in addition to the preview window. Anyway, start thinking about all this. There's a lot we can do to combine a few simple things and end up with some powerful workflow tools. UI, command-line invocation and use cases of different types of users could all be helpful.

1 0

printing
by Mickael Drean 05 Apr '06

05 Apr '06

Hi there, Recently i started to develop with Gtkmm and I need to print and export custom Widget to picture file. As Inkscape is capable of doing it, i 'd like to know how you dit it. Do you use an external librairy? or have you developped the functionnality? Please, could you help me to achieve my goals? Thanks, Mick PS: my english may be unclear, do not hesitate to say it...

2 1

[root@...1070...: [Inkscape-tester] inkscape build report]
by Bryce Harrington 05 Apr '06

05 Apr '06

Build system is picking up an error in svg-color-test.h... Bryce ----- Forwarded message from root <root@...1070...> ----- Date: Tue, 04 Apr 2006 17:21:16 -0700 From: root <root@...1070...> To: inkscape-tester(a)lists.sourceforge.net Subject: [Inkscape-tester] inkscape build report = Analysis Report for inkscape = Report Time: Tue Apr 4 16:54:55 2006 (Run 1886) Snapshot: inkscape-20060404-1400.tar.bz2 Status: finished Platform Unpack Config Build Install WRNS ERRS ------------------------------------------------------------------------ debian x86 0 0 0 0 12 2 Test Status Score Info ------------------------------------------------------------------------ sut-1 ?? == Errors == svg/svg-color-test.h:26: error: `assert' undeclared (first use this function) svg/svg-color-test.h:26: error: (Each undeclared identifier is reported only once for each function it appears in.) == Warnings == sp-flowtext.cpp:324: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-image.cpp:516:8: warning: extra tokens at end of #endif directive sp-item.cpp:730: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.cpp:719) sp-shape.cpp:611: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) sp-text.cpp:472: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:644: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) dialogs/export.cpp:723: warning: `sp_item_bbox_desktop' is deprecated (declared at sp-item.h:215) display/canvas-arena.cpp:85: warning: invalid access to non-static data member `SPCanvasArenaClass::arena_event' of NULL object display/canvas-arena.cpp:85: warning: (perhaps the `offsetof' macro was used incorrectly) display/sp-canvas.cpp:132: warning: invalid access to non-static data member `SPCanvasItemClass::event' of NULL object display/sp-canvas.cpp:132: warning: (perhaps the `offsetof' macro was used incorrectly) trace/trace.cpp:196: warning: unused variable `Inkscape::XML::Node*imgRepr' == Environment Summary == ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Inkscape-tester mailing list Inkscape-tester(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-tester ----- End forwarded message -----

1 0

[Portland] File dialog as trusted desktop service
by Bryce Harrington 05 Apr '06

05 Apr '06

----- Forwarded message from "Bastian, Waldo" <waldo.bastian@...1100...> ----- Date: Mon, 20 Mar 2006 08:26:45 -0800 From: "Bastian, Waldo" <waldo.bastian@...1100...> To: portland@...626... Subject: [Portland] File dialog as trusted desktop service FYI Waldo Bastian Linux Client Architect - Channel Platform Solutions Group Intel Corporation - http://www.intel.com/go/linux OSDL DTL Tech Board Chairman -----Original Message----- From: gtk-devel-list-bounces@...45... [mailto:gtk-devel-list-bounces@...45...] On Behalf Of Mark Seaborn Sent: Saturday, March 18, 2006 9:22 AM To: gtk-devel-list@...45...; gtk-list@...45... Subject: ANNOUNCE: Plash 1.16, with Powerbox for Gtk Hi folks, I have released a new version of Plash, which is available from: http://plash.beasts.org Plash is a system for sandboxing GNU/Linux programs so that they can be run with minimum authority/privileges. Plash can be used with GUI applications: you can dynamically grant a GUI application access rights to individual files that you want to open and edit. This happens transparently through the Open/Save file chooser dialog box. Plash replaces Gtk's GtkFileChooserDialog so that the file chooser is implemented outside the application in a separate process, as a trusted component. This file chooser is known as a powerbox, because it delegates additional power to the application. For example, Inkscape can be launched in a sandbox using the following command. Initially it won't have access to anything in your home directory. Choosing a file using File->Open grants Inkscape access to the file, attaching the file into Inkscape's file namespace. pola-run --prog /usr/bin/inkscape \ -B -fl /etc --x11 \ --env LD_PRELOAD=/usr/lib/plash/lib/powerbox-for-gtk.so \ --powerbox --pet-name "Inkscape" The main change in this release is a reimplementation of the powerbox/Gtk integration. In the previous version, the replacement GtkFileChooserDialog class inherited only from GtkObject, which caused various problems. The new version inherits from GtkDialog (and hence from GtkWindow, GtkWidget, etc.), just as the ordinary GtkFileChooserDialog does. This works with a lot more Gtk applications. The new GtkFileChooserDialog replacement prevents its parent GtkWindow from opening a window by overriding the GtkWidget "map" method with code that does not pass the call on to GtkWindow. Instead, the "map" method invokes the powerbox API, which causes the powerbox manager to open a file chooser instead. You can see the code for this at: new: http://svn.gna.org/viewcvs/plash/trunk/src/gtk-powerbox.c old: http://svn.gna.org/viewcvs/plash/trunk/src/gtk-powerbox-noninherit.c This still works as an LD_PRELOADed library, which replaces gtk_file_chooser_* functions. Would there be any interest in merging this functionality into mainline Gtk, so that the powerbox code can optionally be compiled in, and optionally be enabled at run time? Mark _______________________________________________ gtk-devel-list mailing list gtk-devel-list@...45... http://mail.gnome.org/mailman/listinfo/gtk-devel-list _______________________________________________ Portland mailing list Portland@...626... http://lists.freedesktop.org/mailman/listinfo/portland ----- End forwarded message -----

1 0

next about screen
by Jon Phillips 04 Apr '06

04 Apr '06

Who is doing the next about screen? It seems like it should be added in here soon...is there a time-table for this? Jon -- Jon Phillips San Francisco, CA USA PH 510.499.0894 jon@...235... http://www.rejon.org MSN, AIM, Yahoo Chat: kidproto Jabber Chat: rejon@...896... IRC: rejon@...897... Inkscape (http://inkscape.org) Open Clip Art Library (www.openclipart.org) Creative Commons (www.creativecommons.org) San Francisco Art Institute (www.sfai.edu)

5 7