[Bug 1235097] New: zypper output cluttered by failed assertions
https://bugzilla.suse.com/show_bug.cgi?id=1235097 Bug ID: 1235097 Summary: zypper output cluttered by failed assertions Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: jdelvare@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I installed a fresh Leap 15.6 on bare metal last week, and I'm getting loads of failed assertions on most zypper commands: (process:6854): GLib-CRITICAL **: 10:48:10.576: g_uri_get_scheme: assertion 'uri != NULL' failed (process:6854): GLib-CRITICAL **: 10:48:10.576: g_str_has_prefix: assertion 'str != NULL' failed I've read bug #1228999 and bug #1220128 which seem related, however the first bug is supposedly fixed by a libproxy update (0.5.3-150600.4.3.2) which I have already installed, and the second bug was closed without details, being supposedly already fixed but on a different product (Tumbleweed). For the record, I am not using any proxy. This is a pretty basic install with default repositories, except for Packman and Libdvdcss repositories being added, and a static IPv4 address, DNS server and route instead of the default DHCP config. While I did not observe any functional issue due to these errors, it makes zypper unpleasant to use, as this could hide more useful messages, and fills out the shell windows' log, making it harder to scroll back when needed. So I would appreciate if this can be fixed. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alynx.zhou@suse.com, | |xiaoguang.wang@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c1 --- Comment #1 from Jean Delvare <jdelvare@suse.com> --- Created attachment 879407 --> https://bugzilla.suse.com/attachment.cgi?id=879407&action=edit stdout of "zypper ref" with PX_DEBUG=1 As you asked for it in the other bug, here's the output of "zypper ref" with PX_DEBUG=1. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c2 --- Comment #2 from Jean Delvare <jdelvare@suse.com> --- Created attachment 879408 --> https://bugzilla.suse.com/attachment.cgi?id=879408&action=edit stderr of "zypper ref" with PX_DEBUG=1 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c5 --- Comment #5 from Jean Delvare <jdelvare@suse.com> --- # grep '^[A-Z].*=' /etc/sysconfig/proxy PROXY_ENABLED="no" HTTP_PROXY="" HTTPS_PROXY="" FTP_PROXY="" GOPHER_PROXY="" SOCKS_PROXY="" SOCKS5_SERVER="" NO_PROXY="localhost, 127.0.0.1" # env | grep PROXY # That being said, you may be up to something with the desktop environment, as I only see the issue when running zypper under Gnome. If I switch to a text console (Ctrl+Alt+F3), zypper works without failed assertions. Still, I checked the network settings in the Gnome settings tool, and the proxy server is disabled there too. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c6 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jdelvare@suse.com | |) CC| |jdelvare@suse.com --- Comment #6 from Jean Delvare <jdelvare@suse.com> --- I must amend my previous comment. The failed assertions are no longer reported if I log into a text console *directly as root* and run zypper there. However if I log into a text console with my regular user account, the failed assertions are still reported. If I switch to root using "su" then the failed assertions stay, while they go away if I use "su -" instead. So it most certainly depends on something in the environment. I need to figure out what it is. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c8 --- Comment #8 from Jean Delvare <jdelvare@suse.com> --- Dang, you're right. I stand corrected, I never expected lower-case environment variables. $ env | grep proxy https_proxy= http_proxy= socks_proxy= ftp_proxy= Now if I do: $ unset http_proxy And then run zypper, no failed assertions are being reported anymore. So the failed assertions are indeed caused by defined but empty proxy environment variables, as you suspected from the beginning. While I think these should NOT be defined by default in the first place if empty, I still think that libproxy should be made robust against such empty proxy settings, as any user could tweak their environment in a way which could lead to partially empty proxy settings. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c9 --- Comment #9 from Jean Delvare <jdelvare@suse.com> --- As to how these empty proxy settings made it into my environment, despite /etc/sysconfig/proxy having PROXY_ENABLED="no"... Well look at what I just found in my ~/.bashrc file: ulimit -c unlimited export http_proxy='' export https_proxy='' export ftp_proxy='' export socks_proxy='' Mystery solved. I can't remember why these settings are there, I have not been using any proxy on that system for over a decade. I can only imagine I was trying to work around another issue. Time for some cleanup I suppose. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c10 --- Comment #10 from Jean Delvare <jdelvare@suse.com> --- Note that setting some proxy variables to empty strings is actually needed in certain scenarios, according to bug #756012. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c14 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #14 from Jean Delvare <jdelvare@suse.com> --- Thank you! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1235097 https://bugzilla.suse.com/show_bug.cgi?id=1235097#c18 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #18 from Jean Delvare <jdelvare@suse.com> --- Update released (0.5.3-150600.4.6.2) and fix verified, thanks. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com