#891561 librsvg2-2: With librsvg2-2 version 2.40.20 no svg-images are shown

Package:
librsvg2-2
Source:
librsvg
Description:
SAX-based renderer library for SVG files (runtime)
Submitter:
MB
Date:
2020-12-03 22:03:06 UTC
Severity:
normal
Tags:
#891561#5
Date:
2018-02-26 17:30:29 UTC
From:
To:
Dear Maintainer,

I'm using the svg icon-theme ACYL.
It was working for me until librsvg2-2 version 2.40.18. After the update to version 2.40.20 no svg-images are shown in my theme anymore.
I did not change anything to the icons or the theme itself.
After a downgrade back to version 2.40.18 everything works fine again.
For your help thanks in advance.

Kind regards
MB
#891561#10
Date:
2018-02-26 18:30:08 UTC
From:
To:
Please make sure that librsvg2-common is installed.

Thanks,
Jeremy Bicha
#891561#15
Date:
2018-02-28 20:02:31 UTC
From:
To:
#891561#20
Date:
2018-03-12 15:28:38 UTC
From:
To:
#891561#25
Date:
2020-12-03 20:55:21 UTC
From:
To:
On this host (Geode LX800 i.e. an i686 minus PAE), the SVG library flat out crashes:

[  204.840919] traps: gnome-session-f[939] trap invalid opcode ip:b4e7f86a sp:bfcc1460 error:0 in librsvg-2.so.2.47.0[b4e6d000+5b7000]

As a test, I downgraded all 3 packages (librsvg2-common, librsvg2-2, gir1.2-rsvg-2.0) to 2.44.10-2.1 from Buster/stable. Still no good.

I then downgraded to 2.40.16-1+b1 from oldstable, which shows the SVG expected content.

- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (1000, 'testing-debug'), (1000, 'testing'), (500, 'stable')
Architecture: i386 (i586)

Kernel: Linux 5.9.0-4-686 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages librsvg2-2 depends on:
ii  libc6                2.31-4
ii  libcairo-gobject2    1.16.0-4
ii  libcairo2            1.16.0-4
ii  libgcc-s1            10.2.0-19
ii  libgdk-pixbuf-2.0-0  2.40.0+dfsg-7
ii  libgdk-pixbuf2.0-0   2.40.0+dfsg-7
ii  libglib2.0-0         2.66.3-1
ii  libpango-1.0-0       1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libxml2              2.9.10+dfsg-6.3

Versions of packages librsvg2-2 recommends:
ii  librsvg2-common  2.50.2+dfsg-1

Versions of packages librsvg2-2 suggests:
pn  librsvg2-bin  <none>

- -- no debconf information
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl/JULEACgkQrh+Cd8S0
17bk5w//VOynIb9LuT2IMCfNF+v59pNSLD94C/7fnkkUAYsB7kWAQUCKLmUugUfv
6EODK/BrBmDMUf+hcZ6KlAnMHZRGN5/CNFBHIiMDpq1FRl0JWe7Co0ThXlKz4Bed
9zfewZBupwr4dzs9Y9p6tyTeh8sTLbTroV4og7XwUANakRwDGGiXr4UNyBnuwpnL
OVmOlbESDDJQCfb7dSTKdbyxSin0hpJ74UlX/UtG3wGMS/glmkikoHFNidwuNrYO
kcnSRQo28mN43CdKc+Va9DLf0yWsxibs97TwbCr1BF+d33sXv5fpI5uyVXDb54iG
OID7DGMHuC0ioHUZTPvpcBaJmC/mlLtDDHRQfhEuWDcgH3oPT26cRwB1AM5SLTsx
EsLfd+9cUJuCngeuRaIdBi3W6pQ6eDaSqnOb1JMB6do60uKO9zicSzlZ2WmVIYMN
sh0jbIX03uBZc5sb8J4zw7a8iNEtgxHUdM61aILtacLq8p3Unz36mmE0B7rrDjBv
xeLmUIreJBAytHMc6+P/BKhonAZ59QAFraCH/ejF6FMe41dgS6kES/WEv1hC91lS
kJ1/ivTJkQKKz2EcHH2NS4GH5/1K00UmQrGxc210+RBlOPG9jnMcNIzK4Ws9/cr6
eU0KWdnOdFhhuBKA7yWmbsJj3dXOyzA+7+JGQ5A1iYNZ27ujyuk=
=EF24
-----END PGP SIGNATURE-----
#891561#30
Date:
2020-12-03 21:58:30 UTC
From:
To:
It seems unlikely that this is the same bug that the original submitter
of #891561 had in 2018, since they were using an amd64 system and the
symptoms they describe (although relatively vague) do not include a crash.
Please report this separately.

If 2.40.x works and 2.44.x doesn't, that's consistent with the theory
that the rust compiler is emitting opcodes not supported by your CPU, since
librsvg 2.40.x was C code and 2.44.x was at least partially Rust.

    smcv