Today I updated fvwm3 from 1.1.1-r1 to 1.1.2. Afterwards no svg icons get loaded anymore. ~> equery u fvwm3 [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for x11-wm/fvwm3-1.1.2: U I - - bidi : Enable bidirectional language support + + go : Enable building dev-lang/go code (FvwmPrompt) + + nls : Add Native Language Support (using gettext - GNU locale utilities) - - python_single_target_python3_11 : Build for Python 3.11 only + + python_single_target_python3_12 : Build for Python 3.12 only - - python_single_target_python3_13 : Build for Python 3.13 only + + readline : Enable support for libreadline, a GNU line-editing library that almost everyone wants + + svg : Add support for SVG (Scalable Vector Graphics) Reproducible: Always Steps to Reproduce: 1. Use svg in config Actual Results: The svg gets silently not loaded Expected Results: The svg gets shown
Does it work when downgrading to 1.1.1-r1 again?
Ah..
This appears to be intentional on the part of upstream: SVGs without a 'viewBox' attribute will not display because there are no associated dimensions. It seems that attempting to infer this information has caused issues in the past. As per the linked issues / PR, the best way to fix this is probably going to be updating the SVGs to include a 'viewBox' and getting that in upstream. Suggest logging bugs against the appropriate packages (if any exist) and referencing this bug and the upstream responses.
