[Bug 1220128] New: zypper lu assertions in glib uri != null
https://bugzilla.suse.com/show_bug.cgi?id=1220128 Bug ID: 1220128 Summary: zypper lu assertions in glib uri != null Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: dirk.datzert@gmx.de QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- 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 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220128 https://bugzilla.suse.com/show_bug.cgi?id=1220128#c1 --- Comment #1 from Dirk Datzert <dirk.datzert@gmx.de> --- 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 -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220128 https://bugzilla.suse.com/show_bug.cgi?id=1220128#c2 --- Comment #2 from Dirk Datzert <dirk.datzert@gmx.de> --- 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. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220128 https://bugzilla.suse.com/show_bug.cgi?id=1220128#c3 --- Comment #3 from Dirk Datzert <dirk.datzert@gmx.de> --- The messages comes on zypper ref, after that zypper lu has no messages. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220128 https://bugzilla.suse.com/show_bug.cgi?id=1220128#c4 --- Comment #4 from Dirk Datzert <dirk.datzert@gmx.de> --- 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. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1220128 https://bugzilla.suse.com/show_bug.cgi?id=1220128#c5 --- Comment #5 from Dirk Datzert <dirk.datzert@gmx.de> --- 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 ? -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com