Segfault when searching OCAL resources using "Import clipart..." dialog

Bug #1005966 reported by dopelover
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
High
Unassigned

Bug Description

Inkscape receives SIGSEGV when I try to search Open Clip Art Library resources. 3-letters or shorter queries produces SIGSEGV. Longer queries doesn't crash Inkscape but also doesn't show any results.

This issue affects Inkscape rev 11435 on Windows XP.

Revision history for this message
su_v (suv-lp) wrote :

> This issue affects Inkscape rev 11435 on Windows XP.

Either a duplicate of
Bug #943275 "New 'Import Clip Art…' dialog crashes on Windows "
(issues on Windows with the new ocal dialog in current trunk)

or of
Bug #989257 Inkscape crashes when I search the Open Clip Art Library
(crashes due to changes in ocal's feed - affect stable Inkscape 0.48,
unfortunately it is unknown whether this also affects the refactored dialog in trunk)

tags: added: openclipart win32
su_v (suv-lp)
tags: added: crash
Revision history for this message
su_v (suv-lp) wrote :

> This issue affects Inkscape rev 11435 on Windows XP.

@dopelover - could you take a look at the list of known (and fixed) issues with ocal import on Windows in bug #943275, and report back about the status on your system with current trunk?

Changed in inkscape:
status: New → Incomplete
Revision history for this message
dopelover (dopelover) wrote :

@~suv (suv-lp)
I have tried to reproduce those issues reported in bug #943275 and everything seems to be OK. I tested them against Inkscape r11595 on Windows XP. No crashes, no warnings.

Revision history for this message
su_v (suv-lp) wrote :

> those issues reported in bug #943275 and everything seems to be OK

Does the issue as originally reported here (bug #1005966) still persist with r11595 ( 3-letters or shorter queries produces SIGSEGV)?

Revision history for this message
Kris (kris-degussem) wrote :

Seems to work with r11810 on vista.
What to do with this bug? Could we close this as fix committed because of the changes in the code mentioned earlier?

Revision history for this message
jazzynico (jazzynico) wrote :

Kris> Could we close this as fix committed because of the changes in the code mentioned earlier?

Yes!

Changed in inkscape:
importance: Undecided → High
milestone: none → 0.49
status: Incomplete → Fix Committed
Bryce Harrington (bryce)
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.