Public bug reported:
[Summary]
Since the package "gir1.2-rsvg-2.0:amd64" been upgraded from 2.46.4-1ubuntu1 to
2.48.0-1 in Focal's daily build, ubiquity will crash as attached crash log.
[Steps to reproduce]
1. Boot with OEM mode,
2. Finish the 1st stage
3. Reboot
4. Boot into OOBE(oem-config)
[Expected result]
Should start oobe without any error.
[Actual result]
The error message 『The installer encountered an unrecoverable error. A desktop
session will now be run so that you may investigate the problem or try
installing again.』shown on the screen.
[Failure rate]
100%
[Additional information]
No idea why, but some "nm-signal-*-secure" images will fail in
Gtk.IconTheme().lookup_icon(n, 22, 0).load_icon(), and below error message will
show:
"
Gtk-WARNING **: 18:23:31.380: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
"
** Affects: librsvg (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "_usr_lib_ubiquity_bin_ubiquity.0.crash"
https://bugs.launchpad.net/bugs/1867766/+attachment/5337963/+files/_usr_lib_ubiquity_bin_ubiquity.0.crash
** Summary changed:
- gi.repository.GLib.GError: rsvg-error-quark: XML parse error: error code=201
(3) in (null):40:466: Namespace prefix sodipodi on namedview is not defined
+ Namespace prefix sodipodi on namedview is not defined
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867766
Title:
Namespace prefix sodipodi on namedview is not defined
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1867766/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
