Bug 1314138 - rsvg-convert scaling is broken
Summary: rsvg-convert scaling is broken
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: librsvg2
Version: 22
Hardware: Unspecified
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 01:58 UTC by lostbard
Modified: 2016-07-19 18:45 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:45:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lostbard 2016-03-03 01:58:03 UTC
Description of problem:

When using rsvg-convert, specifying a width or height would scale the svg file. 


Version-Release number of selected component (if applicable): 2.40.13-1


How reproducible: always


Steps to Reproduce:
1. use -w option that is smaller than the svg image. ie: rsvg-convert -w 64 someimagebiggerthan64pixels > test.png
2. look at created test.png

Actual results:

image will show part of the rvg image, 


Expected results:

should have scaled image.


Additional info:

This has been filed as a regression for rsvg2-convert - see https://bugzilla.gnome.org/show_bug.cgi?id=762115

however other linux distros have gotten around the issue by reverting the changeset that caused the issue - see https://bugzilla.gnome.org/show_bug.cgi?id=520654

Comment 1 Fedora End Of Life 2016-07-19 18:45:27 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.