Hi all,
I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present.
Steps to reproduce :
Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang.
I can reproduce this bug in Windows 7 too with the revision 10350.
On Sun, Jun 26, 2011 at 8:26 AM, SorinN <nemes.sorin@...400...> wrote:
Hi all,
I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present.
Steps to reproduce :
Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang.
I can reproduce this bug in Windows 7 too with the revision 10350.
Please elaborate on "Bang". I think I saw an issue myself, but I can't confirm until you actually say what is happening.
Cheers, Josh
No problem ;)
Bang === Crash
so to be very explicit, next second after "Bang" is the moment of the window which tell you that the emergency save was done right.
Btw - "Bang" was the last word in that sentence that mean the final step [I mean the place where the things were broken OR where the crash occur] - is not a rocket science to understand what I mean it's not Morse code.
Should I write "Bang" ? ..sorry but if we stop on small things like this ..there's no too much hope in dialog.
2011/6/26 Josh Andler <scislac@...400...>:
On Sun, Jun 26, 2011 at 8:26 AM, SorinN <nemes.sorin@...400...> wrote:
Hi all,
I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present.
Steps to reproduce :
Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang.
I can reproduce this bug in Windows 7 too with the revision 10350.
Please elaborate on "Bang". I think I saw an issue myself, but I can't confirm until you actually say what is happening.
Cheers, Josh
On 26/6/11 17:26, SorinN wrote:
Hi all,
I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present.
Steps to reproduce :
Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang.
I can reproduce this bug in Windows 7 too with the revision 10350.
tested on Mac OS X 10.5.8 (i386):
the bug is already present in the cairo-rendering branch, and in current trunk after the merge in 10326.
Steps to reproduce: 1) open new document, draw a rectangle 2) assign a gradient with the gradient tool 3) click on 'Edit..' on the gradient tool controls bar to open the gradient editor 4) switch to a different color mode tab
-> crash (backtrace attached).
Crash does not happen when editing the stop color on-canvas with the gradient tool and the color-preview in the fill&stroke dialog.
~suv
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0xc8628443 0x0149033e in Gtk::Widget::get_is_drawable () (gdb) bt #0 0x0149033e in Gtk::Widget::get_is_drawable () #1 0x01490371 in Gtk::Widget::is_drawable () #2 0x00627648 in Inkscape::UI::Widget::ColorPreview::setRgba32 (this=0x6e9ddd8, rgba=4278190335) at ui/widget/color-preview.cpp:59 #3 0x0041f856 in ~basic_ostringstream [inlined] () at widgets/gradient-vector.cpp:1193 #4 ~CSSOStringStream [inlined] () at sstream:15 #5 sp_gradient_vector_color_changed (csel=<value temporarily unavailable, due to optimizations>, object=0x6825dc0) at css-ostringstream.h:1193 #6 0x033e4f59 in g_closure_invoke () #7 0x033f70d3 in signal_emit_unlocked_R () #8 0x033f8761 in g_signal_emit_valist () #9 0x033f8a69 in g_signal_emit () #10 0x004492ef in ColorSelector::_released (this=0x7bab6e0) at widgets/sp-color-selector.cpp:267 #11 0x004432dd in Inkscape::Preferences::get () at preferences.h:112 #12 sp_color_notebook_switch_page (notebook=0x61346e0, page=0x6825d68, page_num=1, colorbook=0x7bab6e0) at widgets/sp-color-notebook.cpp:115 #13 0x033e4f59 in g_closure_invoke () #14 0x033f70d3 in signal_emit_unlocked_R () #15 0x033f8761 in g_signal_emit_valist () #16 0x033f8a69 in g_signal_emit () #17 0x019b2f61 in gtk_notebook_switch_page () #18 0x019b3e8b in gtk_notebook_button_press () #19 0x0198e85b in _gtk_marshal_BOOLEAN__BOXED () #20 0x033e4f59 in g_closure_invoke () #21 0x033f7258 in signal_emit_unlocked_R () #22 0x033f84a7 in g_signal_emit_valist () #23 0x033f8a69 in g_signal_emit () #24 0x01abd546 in gtk_widget_event_internal () #25 0x0198ca58 in gtk_propagate_event () #26 0x0198d06a in gtk_main_do_event () #27 0x027ac845 in gdk_event_dispatch () #28 0x034a051d in g_main_context_dispatch () #29 0x034a43ab in g_main_context_iterate () #30 0x034a4687 in g_main_loop_run () #31 0x0198bfa1 in gtk_main () #32 0x0141159b in Gtk::Main::run () #33 0x00005d9c in ~vector [inlined] () at stl_vector.h:978 #34 sp_main_gui (argc=1, argv=0xbffff0fc) at main.cpp:985 #35 0x00004996 in start () (gdb)
On Jun 26, 2011, at 9:36 AM, ~suv wrote:
tested on Mac OS X 10.5.8 (i386):
the bug is already present in the cairo-rendering branch, and in current trunk after the merge in 10326.
Steps to reproduce:
- open new document, draw a rectangle
- assign a gradient with the gradient tool
- click on 'Edit..' on the gradient tool controls bar
to open the gradient editor 4) switch to a different color mode tab
-> crash (backtrace attached).
Crash does not happen when editing the stop color on-canvas with the gradient tool and the color-preview in the fill&stroke dialog.
Please retest with trunk revision 10404 or later. I believe this is bug 804243 and is now fixed.
Excellent ! Fixed here on Kubuntu 10.04 !
ivan
________________________________ De : Jon Cruz <jon@...18...> À : inkscape-devel List Inkscape-devel@lists.sourceforge.net; Nemes Ioan Sorin <nemes.sorin@...400...>; Ivan Louette <ivan_louette@...48...> Envoyé le : Samedi 2 Juillet 2011 18h01 Objet : Re: [Inkscape-devel] bug in changing gradient color
On Jun 26, 2011, at 9:36 AM, ~suv wrote:
tested on Mac OS X 10.5.8 (i386):
the bug is already present in the cairo-rendering branch, and in current trunk after the merge in 10326.
Steps to reproduce:
- open new document, draw a rectangle
- assign a gradient with the gradient tool
- click on 'Edit..' on the gradient tool controls bar
to open the gradient editor 4) switch to a different color mode tab
-> crash (backtrace attached).
Crash does not happen when editing the stop color on-canvas with the gradient tool and the color-preview in the fill&stroke dialog.
Please retest with trunk revision 10404 or later. I believe this is bug 804243 and is now fixed.
someone have a .deb for 10404+ revision ?
I can't compile on my machine at this moment ( and at least for a week or two ) here https://code.launchpad.net/~inkscape.dev/+recipe/inkscape-trunk-daily the last version was published 22 hours ago the the rev. number is 10393
2011/7/3 Ivan Louette <ivan_louette@...48...>:
Excellent ! Fixed here on Kubuntu 10.04 ! ivan ________________________________ De : Jon Cruz <jon@...18...> À : inkscape-devel List Inkscape-devel@lists.sourceforge.net; Nemes Ioan Sorin <nemes.sorin@...400...>; Ivan Louette <ivan_louette@...48...> Envoyé le : Samedi 2 Juillet 2011 18h01 Objet : Re: [Inkscape-devel] bug in changing gradient color
On Jun 26, 2011, at 9:36 AM, ~suv wrote:
tested on Mac OS X 10.5.8 (i386):
the bug is already present in the cairo-rendering branch, and in current trunk after the merge in 10326.
Steps to reproduce:
- open new document, draw a rectangle
- assign a gradient with the gradient tool
- click on 'Edit..' on the gradient tool controls bar
to open the gradient editor 4) switch to a different color mode tab
-> crash (backtrace attached).
Crash does not happen when editing the stop color on-canvas with the gradient tool and the color-preview in the fill&stroke dialog.
Please retest with trunk revision 10404 or later. I believe this is bug 804243 and is now fixed.
The nightly builds will automatically be updated. Hopefully, they should be up to 10404+ by tomorrow.
AV
On 2 July 2011 18:33, SorinN <nemes.sorin@...400...> wrote:
someone have a .deb for 10404+ revision ?
I can't compile on my machine at this moment ( and at least for a week or two ) here https://code.launchpad.net/~inkscape.dev/+recipe/inkscape-trunk-daily the last version was published 22 hours ago the the rev. number is 10393
2011/7/3 Ivan Louette <ivan_louette@...48...>:
Excellent ! Fixed here on Kubuntu 10.04 ! ivan ________________________________ De : Jon Cruz <jon@...18...> À : inkscape-devel List Inkscape-devel@lists.sourceforge.net; Nemes Ioan Sorin <nemes.sorin@...400...>; Ivan Louette <ivan_louette@...48...> Envoyé le : Samedi 2 Juillet 2011 18h01 Objet : Re: [Inkscape-devel] bug in changing gradient color
On Jun 26, 2011, at 9:36 AM, ~suv wrote:
tested on Mac OS X 10.5.8 (i386):
the bug is already present in the cairo-rendering branch, and in current trunk after the merge in 10326.
Steps to reproduce:
- open new document, draw a rectangle
- assign a gradient with the gradient tool
- click on 'Edit..' on the gradient tool controls bar
to open the gradient editor 4) switch to a different color mode tab
-> crash (backtrace attached).
Crash does not happen when editing the stop color on-canvas with the gradient tool and the color-preview in the fill&stroke dialog.
Please retest with trunk revision 10404 or later. I believe this is bug 804243 and is now fixed.
-- Nemes Ioan Sorin
All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Reproduced with rev 10355 on Kubuntu 10.04
________________________________ De : SorinN <nemes.sorin@...400...> À : Inkscape-devel@lists.sourceforge.net Envoyé le : Dimanche 26 Juin 2011 17h26 Objet : [Inkscape-devel] bug in changing gradient color
Hi all,
I just "tested" this bug with few inkscape-trunk revisions (Win32 and Natty). It is present for any inkscape-trunk versions bigger that 10349 (I didn't check earlier versions). now I use 10359 and the bug is still present.
Steps to reproduce :
Open a blank file - Draw a rectangle - Assign a color - Make a gradient using the gradient tool OR using Fill tab option - Edit the gradient, chose the color node then try to change colorspace to another one (CMYK, RGB, etc). - Bang.
I can reproduce this bug in Windows 7 too with the revision 10350.
participants (6)
-
Alex Valavanis -
Ivan Louette -
Jon Cruz -
Josh Andler -
SorinN -
~suv