Bugzilla – Bug 1220128
zypper lu assertions in glib uri != null
Last modified: 2024-03-11 14:33:15 UTC
After the Change of glib 2.78 I got at the sametime multiple assertions on GLIB by zypper lu on the console: (process:27691): GLib-CRITICAL **: 06:30:06.392: g_uri_get_scheme: assertion 'uri != NULL' failed 8 time on 4 repositories
Sorry, there are different messages: zypper lu (process:783): GLib-CRITICAL **: 08:14:04.580: g_uri_get_scheme: assertion 'uri != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_uri_get_scheme: assertion 'uri != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_str_has_prefix: assertion 'str != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_uri_get_scheme: assertion 'uri != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_str_has_prefix: assertion 'str != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_uri_get_scheme: assertion 'uri != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_str_has_prefix: assertion 'str != NULL' failed (process:783): GLib-CRITICAL **: 08:14:04.580: g_uri_to_string: assertion 'uri != NULL' failed
glib2-tools-2.78.3-1.2.x86_64 MicroOS-release-20240218-2754.1.x86_64 zypper-1.14.68-1.3.x86_64 I have 9 nodes with the same behaviour.
The messages comes on zypper ref, after that zypper lu has no messages.
As an examples one repo definition file: /etc/zypp/repos.d # cat repo-update.repo [repo-update] name=openSUSE-Tumbleweed-Update enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/update/tumbleweed/ path=/ keeppackages=0 Seems to me as usual.
I deactivated one of our own repositories an the messages are gone: [k3s-airgap-repo] enabled=1 autorefresh=1 baseurl=ftp://yum01/k3s type=rpm-md gpgcheck=0 Whats wrong here ? Or is it inside the repo on that server ?
The error can be fixed by adding our companys domain to the baseurl.