After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351035 - big, unwanted text fragments in rendered image
big, unwanted text fragments in rendered image
Status: RESOLVED DUPLICATE of bug 337979
Product: librsvg
Classification: Core
Component: general
Other Windows
: Normal minor
: ---
Assigned To: librsvg maintainers
librsvg maintainers
Depends on:
Reported: 2006-08-12 12:10 UTC by duese
Modified: 2006-08-23 13:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

This is the buggy SVG-file (83.61 KB, image/svg+xml)
2006-08-12 12:12 UTC, duese
This is the SVG file rendered with GIMP. (33.46 KB, image/png)
2006-08-12 12:13 UTC, duese

Description duese 2006-08-12 12:10:38 UTC
Please describe the problem:
I created an chemical structure with BKchem. Next I imported the BKchem-SVG-file into Inkscape and made further manipulations. The Inkscape-SVG-file is next rendered with Gimp. In the rendered image there are big, disturbing, unwanted textfragments. Like parts of a "Z" or a "2". 

This also happens in the Wikimedia-Commons.

Steps to reproduce:
1a. Render the appended SVG-file with Gimp.
1b. Upload the SVG-file to the wikimedia-commons

Actual results:
See above

Expected results:
I do not want to see these text fragments.

Does this happen every time?

Other information:
There is a workaround for this bug: In Inkscape select the BKchem structure an ungroup it. Next transform the text into paths.
Comment 1 duese 2006-08-12 12:12:27 UTC
Created attachment 70770 [details]
This is the buggy SVG-file

If this file is rendered with Gimp or by the wikimedia-commons you see the disturbing fragments.
Comment 2 duese 2006-08-12 12:13:47 UTC
Created attachment 70771 [details]
This is the SVG file rendered with GIMP.
Comment 3 duese 2006-08-12 12:16:28 UTC
This Bug seems to be similar to the Bug 337979 (
Comment 4 Dominic Lachowicz 2006-08-23 13:08:01 UTC
Indeed, this is a duplicate of bug 337979. The file occasionally uses:


Thanks for the bug report.

*** This bug has been marked as a duplicate of 337979 ***