zypper fails to connect to 127.0.0.1:1080
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and on a spare drive on my system. All seemed to be working well, then when I was getting ready to install some pipewire bits, this happened : | @19:31:45 root@pinto | wd=~ | ● zypper ref | Problem retrieving files from 'KDE3'. | Download (curl) error for 'https://download.opensuse.org/repositories/KDE:/KDE3/15.5/repodata/repomd.xm...': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'KDE3' because of the above error. | Repository 'Local' is up to date. | Problem retrieving files from 'Packman Repository'. | Download (curl) error for 'http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.5/repodata/r...': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Packman Repository' because of the above error. | Problem retrieving files from 'repo-non-oss (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/distribution/leap/15.5/repo/non-oss/repodata/repomd....': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'repo-non-oss (15.5)' because of the above error. | Problem retrieving files from 'repo-openh264 (15.5)'. | Download (curl) error for 'http://codecs.opensuse.org/openh264/openSUSE_Leap/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'repo-openh264 (15.5)' because of the above error. | Problem retrieving files from 'repo-oss (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/distribution/leap/15.5/repo/oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'repo-oss (15.5)' because of the above error. | Problem retrieving files from 'update-backports (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'update-backports (15.5)' because of the above error. | Problem retrieving files from 'update-non-oss (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/update/leap/15.5/non-oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'update-non-oss (15.5)' because of the above error. | Problem retrieving files from 'update-oss (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/update/leap/15.5/oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'update-oss (15.5)' because of the above error. | Problem retrieving files from 'update-sle (15.5)'. | Download (curl) error for 'http://cdn.opensuse.org/update/leap/15.5/sle/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'update-sle (15.5)' because of the above error. | Problem retrieving files from 'packman'. | Download (curl) error for 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.5/repodata/...': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'packman' because of the above error. | Problem retrieving files from 'Update repository of openSUSE Backports'. | Download (curl) error for 'http://download.opensuse.org/update/leap/15.5/backports/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Update repository of openSUSE Backports' because of the above error. | Problem retrieving files from 'Non-OSS Repository'. | Download (curl) error for 'http://download.opensuse.org/distribution/leap/15.5/repo/non-oss/repodata/re...': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Non-OSS Repository' because of the above error. | Problem retrieving files from 'Open H.264 Codec (openSUSE Leap)'. | Download (curl) error for 'http://codecs.opensuse.org/openh264/openSUSE_Leap/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Open H.264 Codec (openSUSE Leap)' because of the above error. | Problem retrieving files from 'Main Repository'. | Download (curl) error for 'http://download.opensuse.org/distribution/leap/15.5/repo/oss/repodata/repomd...': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Main Repository' because of the above error. | Problem retrieving files from 'Update repository with updates from SUSE Linux Enterprise 15'. | Download (curl) error for 'http://download.opensuse.org/update/leap/15.5/sle/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Update repository with updates from SUSE Linux Enterprise 15' because of the above error. | Problem retrieving files from 'Main Update Repository'. | Download (curl) error for 'http://download.opensuse.org/update/leap/15.5/oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Main Update Repository' because of the above error. | Problem retrieving files from 'Update Repository (Non-Oss)'. | Download (curl) error for 'http://download.opensuse.org/update/leap/15.5/non-oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: Couldn't connect to server | | Please see the above error message for a hint. | Skipping repository 'Update Repository (Non-Oss)' because of the above error. | Some of the repositories have not been refreshed because of an error. | rc=4 I tried using YaST sw_single, but it did the same thing. (See attached.) For some reason, YaST is now working again on one machine, but the problem persists with zypper on both. Other network applications (web browser, email) work just fine. The reference to 127.0.0.1 leads me to conclude that the issue is internal to my machines, but networking is pretty much a black box to me and various tools keep being replaced with new ones, I have no idea how to collect additional information that might explain what is happening. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and on a spare drive on my system. All seemed to be working well, then when I was getting
ready to install some pipewire bits, this happened : | @19:31:45 root@pinto | wd=~ | ● zypper ref | Problem retrieving files from 'KDE3'. | Download (curl) error
for 'https://aus01.safelinks.protection.outlook.com/? url=https%3A%2F%2Fdownload.opensuse.org%2Frepositories%2FKDE%3A%2FKDE3%2F15.5 %2Frepodata%2Frepomd.xml&data=05%7C02%7C%7Caaeb891e26474c47f32108dc35b31300 %7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638444290471308668%7CUnknown %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0 %3D%7C0%7C%7C%7C&sdata=b2gA3u65Td%2BRxh17HygaYxu55FjVTzcSdYRI4ItDOfc%3D&r eserved=0': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: | Couldn't connect to server [...]
I tried using YaST sw_single, but it did the same thing. (See attached.) For some reason, YaST is now working again on one machine, but the problem persists with zypper on both. Other network applications (web browser, email) work just fine.
The reference to 127.0.0.1 leads me to conclude that the issue is internal to my machines, but networking is pretty much a black box to me and various tools keep being replaced with new ones, I have no idea how to collect additional information that might explain what is happening.
Leslie
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses. Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost. Do you have entries in your /etc/hosts file? What about /etc/resolv.conf? Are you running a filtered proxy server or some other process that was working and now is not? What are the URLs for the repos under /etc/zypp/repos.d? Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)? Or perhaps an environment variable doing the same? Regards, Rodney. -- ============================================================================== ============================ Rodney Baker rodney.baker@outlook.com.au ============================================================================== ============================
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search. regards Hartmut Delmenhorst ----------- Am 25.02.24 um 05:01 schrieb Rodney Baker:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and on a spare
drive on my system. All seemed to be working well, then when I was getting
ready to install some pipewire bits, this happened :
| @19:31:45 root@pinto
| wd=~
| ● zypper ref
| Problem retrieving files from 'KDE3'.
| Download (curl) error
| Error code: Connection failed
| Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms:
| Couldn't
connect to server
[...]
I tried using YaST sw_single, but it did the same thing. (See attached.)
For some reason, YaST is now working again on one machine, but the problem
persists with zypper on both. Other network applications (web browser,
email) work just fine.
The reference to 127.0.0.1 leads me to conclude that the issue is internal
to my machines, but networking is pretty much a black box to me and various
tools keep being replaced with new ones, I have no idea how to collect
additional information that might explain what is happening.
Leslie
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost.
Do you have entries in your /etc/hosts file?
What about /etc/resolv.conf?
Are you running a filtered proxy server or some other process that was working and now is not?
What are the URLs for the repos under /etc/zypp/repos.d?
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)? Or perhaps an environment variable doing the same?
Regards,
Rodney.
--
==========================================================================================================
Rodney Baker
rodney.baker@outlook.com.au
==========================================================================================================
Hi, sorry for the Leap attachment in my previous email, I was to quick regards Hartmut Delmenhorst ----------- Am 25.02.24 um 13:13 schrieb Hartmut Rosch:
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search.
regards
Hartmut
Delmenhorst -----------
On 2024-02-25 13:18, Hartmut Rosch wrote:
Hi, sorry for the Leap attachment in my previous email, I was to quick
When you post here a new email, you have to really use "New message" and enter the list address (or create a template). You can not use "reply", because that way your post is linked or threaded back to the post you replied to (even if you delete the old mail material). That action is called "thread hijacking".
Am 25.02.24 um 13:13 schrieb Hartmut Rosch:
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search.
Sorry, I do not know. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hi Hartmut, On Sun, 25 Feb 2024, 13:13:39 +0100, Hartmut Rosch wrote:
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search.
which package contains the command "codeblocks"? I just searched the standard TW repos and only found "texlive-tikzcodeblocks". Can you please run the following commands: rpm -qf --qf "%{name}\n" $(type -p codeblocks) zypper se -s -x -i $(rpm -qf --qf "%{name}\n" $(type -p codeblocks)) The first one should show the name of the package containing that program. The second command should show the details about the particular package installed on your system. Perhaps the package just need to be manually rebuilt in OBS because some library has been changed.
regards
Hartmut
HTH, cheers. l8er manfred
On Sun, 25 Feb 2024, 14:51:32 +0100, Manfred Hollstein wrote:
Hi Hartmut,
On Sun, 25 Feb 2024, 13:13:39 +0100, Hartmut Rosch wrote:
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search.
which package contains the command "codeblocks"? I just searched the standard TW repos and only found "texlive-tikzcodeblocks". Can you please run the following commands:
rpm -qf --qf "%{name}\n" $(type -p codeblocks) zypper se -s -x -i $(rpm -qf --qf "%{name}\n" $(type -p codeblocks))
The first one should show the name of the package containing that program. The second command should show the details about the particular package installed on your system. Perhaps the package just need to be manually rebuilt in OBS because some library has been changed.
looking at the Subject: would have shown me, it's home:plater/codeblocks. That package has been rebuilt just yesterday, so you might want to contact Dave Plater directly.
regards
Hartmut
HTH, cheers. l8er manfred
Thank you for your information. I did a "sudo zypper dup --no-allow-vendor-change --no-recommends" yesterday evening, Calling codeblocks this morning and the result is "codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display" This shows a missing symbol in the libwx_gtk3u-2.2.so.0 library. Assuming this symbol is somewhre in the GTK or GDK libraries called from the libwx_gtk3u-3.2 lib. But where? regards Hartmut Delmenhorst ----------- Am 25.02.24 um 14:55 schrieb Manfred Hollstein:
On Sun, 25 Feb 2024, 14:51:32 +0100, Manfred Hollstein wrote:
Hi Hartmut,
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search. which package contains the command "codeblocks"? I just searched the standard TW repos and only found "texlive-tikzcodeblocks". Can you
On Sun, 25 Feb 2024, 13:13:39 +0100, Hartmut Rosch wrote: please run the following commands:
rpm -qf --qf "%{name}\n" $(type -p codeblocks) zypper se -s -x -i $(rpm -qf --qf "%{name}\n" $(type -p codeblocks))
The first one should show the name of the package containing that program. The second command should show the details about the particular package installed on your system. Perhaps the package just need to be manually rebuilt in OBS because some library has been changed. looking at the Subject: would have shown me, it's home:plater/codeblocks. That package has been rebuilt just yesterday, so you might want to contact Dave Plater directly.
regards
Hartmut HTH, cheers.
l8er manfred
On Mon, 26 Feb 2024, 10:50:02 +0100, Hartmut Rosch wrote:
Thank you for your information. I did a "sudo zypper dup --no-allow-vendor-change --no-recommends" yesterday evening, Calling codeblocks this morning and the result is "codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display" This shows a missing symbol in the libwx_gtk3u-2.2.so.0 library. Assuming this symbol is somewhre in the GTK or GDK libraries called from the libwx_gtk3u-3.2 lib. But where?
OK, then please do the same, but for file /lib64/libwx_gtk3u-3.2.so.0: rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u-3.2.so.0 zypper se -s -x -i $(rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u-3.2.so.0)
regards
Hartmut
Cheers. l8er manfred
Delmenhorst -----------
Am 25.02.24 um 14:55 schrieb Manfred Hollstein:
On Sun, 25 Feb 2024, 14:51:32 +0100, Manfred Hollstein wrote:
Hi Hartmut,
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search. which package contains the command "codeblocks"? I just searched the standard TW repos and only found "texlive-tikzcodeblocks". Can you
On Sun, 25 Feb 2024, 13:13:39 +0100, Hartmut Rosch wrote: please run the following commands:
rpm -qf --qf "%{name}\n" $(type -p codeblocks) zypper se -s -x -i $(rpm -qf --qf "%{name}\n" $(type -p codeblocks))
The first one should show the name of the package containing that program. The second command should show the details about the particular package installed on your system. Perhaps the package just need to be manually rebuilt in OBS because some library has been changed. looking at the Subject: would have shown me, it's home:plater/codeblocks. That package has been rebuilt just yesterday, so you might want to contact Dave Plater directly.
regards
Hartmut HTH, cheers.
l8er manfred
Thank you again. Well, I did a "ln -s libwx_gtk3u_core-suse.so.10.0.0 libwx_gtk3u-3.2.so.0" but forgot. After removing that symlink I got "codeblocks: error while loading shared libraries: libwx_gtk3u-3.2.so.0: cannot open shared object file: No such file or directory" It is true. There is no libwx_gtk3u-3.2.so.0 but always alibwx_gtk3u_core-suse.so.10.0.0 or similar. And then, you guess it. The question is, how to cirvumvent this? cheers Hartmut Delmenhorst ----------- Am 26.02.24 um 11:01 schrieb Manfred Hollstein:
On Mon, 26 Feb 2024, 10:50:02 +0100, Hartmut Rosch wrote:
Thank you for your information. I did a "sudo zypper dup --no-allow-vendor-change --no-recommends" yesterday evening, Calling codeblocks this morning and the result is "codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display" This shows a missing symbol in the libwx_gtk3u-2.2.so.0 library. Assuming this symbol is somewhre in the GTK or GDK libraries called from the libwx_gtk3u-3.2 lib. But where? OK, then please do the same, but for file /lib64/libwx_gtk3u-3.2.so.0:
rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u-3.2.so.0 zypper se -s -x -i $(rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u-3.2.so.0)
regards
Hartmut Cheers.
l8er manfred
Delmenhorst -----------
Am 25.02.24 um 14:55 schrieb Manfred Hollstein:
On Sun, 25 Feb 2024, 14:51:32 +0100, Manfred Hollstein wrote:
Hi Hartmut,
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search. which package contains the command "codeblocks"? I just searched the standard TW repos and only found "texlive-tikzcodeblocks". Can you
On Sun, 25 Feb 2024, 13:13:39 +0100, Hartmut Rosch wrote: please run the following commands:
rpm -qf --qf "%{name}\n" $(type -p codeblocks) zypper se -s -x -i $(rpm -qf --qf "%{name}\n" $(type -p codeblocks))
The first one should show the name of the package containing that program. The second command should show the details about the particular package installed on your system. Perhaps the package just need to be manually rebuilt in OBS because some library has been changed. looking at the Subject: would have shown me, it's home:plater/codeblocks. That package has been rebuilt just yesterday, so you might want to contact Dave Plater directly.
regards
Hartmut HTH, cheers.
l8er manfred
Hi Hartmut, On Mon, 26 Feb 2024, 11:39:54 +0100, Hartmut Rosch wrote:
Thank you again. Well, I did a "ln -s libwx_gtk3u_core-suse.so.10.0.0 libwx_gtk3u-3.2.so.0" but forgot.
you should never need to do that manually. This leads to the question where you got this library from. Again, please show the output of running the following commands: rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u_core-suse.so.10.0.0 zypper se -s -x -i $(rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u_core-suse.so.10.0.0) ldd /lib64/libwx_gtk3u_core-suse.so.10.0.0
After removing that symlink I got "codeblocks: error while loading shared libraries: libwx_gtk3u-3.2.so.0: cannot open shared object file: No such file or directory" It is true. There is no libwx_gtk3u-3.2.so.0 but always alibwx_gtk3u_core-suse.so.10.0.0 or similar. And then, you guess it. The question is, how to cirvumvent this?
It shouldn't be necessary to circumvent anything, it should just work.
cheers
Hartmut
Cheers. l8er manfred
Hi Hartmut, On Mon, 26 Feb 2024, 11:54:14 +0100, Manfred Hollstein wrote:
On Mon, 26 Feb 2024, 11:39:54 +0100, Hartmut Rosch wrote:
Thank you again. Well, I did a "ln -s libwx_gtk3u_core-suse.so.10.0.0 libwx_gtk3u-3.2.so.0" but forgot.
you should never need to do that manually. This leads to the question where you got this library from. Again, please show the output of running the following commands:
rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u_core-suse.so.10.0.0 zypper se -s -x -i $(rpm -qf --qf "%{name}\n" /lib64/libwx_gtk3u_core-suse.so.10.0.0) ldd /lib64/libwx_gtk3u_core-suse.so.10.0.0
After removing that symlink I got "codeblocks: error while loading shared libraries: libwx_gtk3u-3.2.so.0: cannot open shared object file: No such file or directory" It is true. There is no libwx_gtk3u-3.2.so.0 but always alibwx_gtk3u_core-suse.so.10.0.0 or similar. And then, you guess it. The question is, how to cirvumvent this?
It shouldn't be necessary to circumvent anything, it should just work.
I just bit the bullet and installed "codeworks" from devel:tools:ide/codeworks for openSUSE_Factory on my TW 20240223 installation. It pulled in the following packages: codeblocks-20.03-1.772.x86_64 libcodeblocks0-20.03-1.772.x86_64 libwx_baseu-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_baseu_net-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_baseu_xml-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_adv-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_aui-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_core-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_html-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_propgrid-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_qa-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 libwx_gtk2u_xrc-suse-nostl3_0_5-3.0.5.1-4.6.x86_64 wxWidgets-lang-3.0.5.1-4.6.noarch Note the "nostl" piece! Looking at your messages, it appears that you don't have the libwx_gtk2u_core-suse-nostl3_0_5 package installed, but libwx_gtk2u_core-suse3_0_5. In any case, the program works for me, so I'd recommend you check your "*wx*" packages on your system.
cheers
Hartmut
HTH, cheers. l8er manfred
You hijacked my thread! :-) Leslie On 2024-02-25 07:13:39 Hartmut Rosch wrote:
Hi, I want to use codeblocks on my tumbleweed machine. An update from that repo is still failing. When I run /home/rosch> codeblocks it comes back with codeblocks: symbol lookup error: /lib64/libwx_gtk3u-3.2.so.0: undefined symbol: gdk_wayland_display_get_wl_display Well I am running full KDE with full Qt5-devel and of course libwx... I am unable to find the missing symbol. looked at several Libaries but no avail. Can someone tell me please where I have to search.
regards
Hartmut
Delmenhorst -----------
Am 25.02.24 um 05:01 schrieb Rodney Baker:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and
on a spare
drive on my system. All seemed to be working well, then when I was
getting
ready to install some pipewire bits, this happened : | @19:31:45 root@pinto | | wd=~ | | ● zypper ref | | Problem retrieving files from 'KDE3'. | | Download (curl) error
for
| Error code: Connection failed | | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: | | Couldn't
connect to server
[...]
I tried using YaST sw_single, but it did the same thing. (See
attached.)
For some reason, YaST is now working again on one machine, but the
problem
persists with zypper on both. Other network applications (web browser,
email) work just fine.
The reference to 127.0.0.1 leads me to conclude that the issue
is internal
to my machines, but networking is pretty much a black box to me and
various
tools keep being replaced with new ones, I have no idea how to collect
additional information that might explain what is happening.
Leslie
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost.
Do you have entries in your /etc/hosts file?
What about /etc/resolv.conf?
Are you running a filtered proxy server or some other process that was working and now is not?
What are the URLs for the repos under /etc/zypp/repos.d?
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)? Or perhaps an environment variable doing the same?
Regards,
Rodney.
--
========================================================================= =================================
Rodney Baker
rodney.baker@outlook.com.au
========================================================================= =================================
On 2024-02-25 05:01, Rodney Baker wrote:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
...
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost.
Do you have entries in your /etc/hosts file?
What about /etc/resolv.conf?
Are you running a filtered proxy server or some other process that was working and now is not?
What are the URLs for the repos under /etc/zypp/repos.d?
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)? Or perhaps an environment variable doing the same?
a vpn, perrhaps? -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-02-25 07:30:07 Carlos E. R. wrote:
On 2024-02-25 05:01, Rodney Baker wrote:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
...
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost.
Do you have entries in your /etc/hosts file?
What about /etc/resolv.conf?
Are you running a filtered proxy server or some other process that was working and now is not?
What are the URLs for the repos under /etc/zypp/repos.d?
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)? Or perhaps an environment variable doing the same?
a vpn, perrhaps?
Nope; no vpn is installed. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 2024-02-24 23:01:51 Rodney Baker wrote:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
A few days ago I installed Leap 15.5 on a Lenovo ThinkPad, and on a spare drive on my system. All seemed to be working well, then when I was getting
ready to install some pipewire bits, this happened : | @19:31:45 root@pinto | wd=~ | ● zypper ref | Problem retrieving files from 'KDE3'. | Download (curl) error
url=https%3A%2F%2Fdownload.opensuse.org%2Frepositories%2FKDE%3A%2FKDE3%2F15 .5 %2Frepodata%2Frepomd.xml&data=05%7C02%7C%7Caaeb891e26474c47f32108dc35b31300 %7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638444290471308668%7CUnknown %7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6 Mn0 %3D%7C0%7C%7C%7C&sdata=b2gA3u65Td%2BRxh17HygaYxu55FjVTzcSdYRI4ItDOfc%3D&r
eserved=0':
| Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 1080 after 0 ms: | Couldn't
connect to server
[...]
I tried using YaST sw_single, but it did the same thing. (See attached.) For some reason, YaST is now working again on one machine, but the problem persists with zypper on both. Other network applications (web browser, email) work just fine.
The reference to 127.0.0.1 leads me to conclude that the issue is internal to my machines, but networking is pretty much a black box to me and various tools keep being replaced with new ones, I have no idea how to collect additional information that might explain what is happening.
Leslie
127.0.0.1 is always "localhost" i.e. the local machine. It looks like curl is configured to use a (possibly filtered) proxy on the local machine, or the repo addresses are somehow being resolved to localhost rather than their actual IP addresses.
Localhost addresses will never be routed externally to the local machine, so you 'll need to figure out why those addresses appear to be being resolved as localhost. Yes, as I said above; but I don't know how to diagnose that.
Do you have entries in your /etc/hosts file? Yes: | # | # hosts This file describes a number of hostname-to-address | # mappings for the TCP/IP subsystem. It is mostly | # used at boot time, when no name servers are running. | # On small systems, this file can be used instead of a | # "named" name server. | # Syntax: | # | # IPv4 Address Fully Qualified Hostname Short Hostnames | #------------- ------------------------ ------------------- | 127.0.0.1 localhost | # | 192.168.1.1 grey.sixys.site grey router | 192.168.1.2 pinto.sixys.site pinto desktop1 | 192.168.1.3 philips.sixys.site philips TV | 192.168.1.4 chestnut.sixys.site chestnut desktop2 | 192.168.1.5 black.sixys.site black windows | 192.168.1.6 charcoal.sixys.site charcoal dell | #92.168.1.7 unused | #92.168.1.8 unused | 192.168.1.9 palomino.sixys.site palomino server | 192.168.1.10 buckskin.sixys.site buckskin printer | #92.168.1.11 unused | 192.168.1.12 chrome.sixys.site chrome laptop1 | 192.168.1.13 pinto-foal.sixys.site pinto-foal UPS | 192.168.1.14 toreador.sixys.site toreador laptop2 | # | 192.168.100.1 blueroan.sixys.site blueroan downlink | # | #============================================================ | # IPv6 Address Hostnames | #------------- --------------------------------------------- | ::1 localhost ipv6-localhost ipv6-loopback | | fe00::0 ipv6-localnet | | ff00::0 ipv6-mcastprefix | ff02::1 ipv6-allnodes | ff02::2 ipv6-allrouters | ff02::3 ipv6-allhosts | # | #============================================================ | # DNS Servers: | # 192.168.1.1 | 99.197.99.99 | 99.196.99.99 | #============================================================
What about /etc/resolv.conf?
Just the DNS list: | 23:10:07 root@pinto | wd=~ | ● ll /etc/resolv.conf | lrwxrwxrwx 1 root root 26 2024-02-20 22:25:28 /etc/resolv.conf -> /run/netconfig/resolv.conf | rc=0 | @00:04:14 root@pinto | wd=~ | ● l /run/netconfig/resolv.conf | ### /etc/resolv.conf is a symlink to /run/netconfig/resolv.conf | ### autogenerated by netconfig! | # | # Before you change this file manually, consider to define the | # static DNS configuration using the following variables in the | # /etc/sysconfig/network/config file: | # NETCONFIG_DNS_STATIC_SEARCHLIST | # NETCONFIG_DNS_STATIC_SERVERS | # NETCONFIG_DNS_FORWARDER | # or disable DNS configuration updates via netconfig by setting: | # NETCONFIG_DNS_POLICY='' | # | # See also the netconfig(8) manual page and other documentation. | # | ### Call "netconfig update -f" to force adjusting of /etc/resolv.conf. | nameserver 192.168.1.1 | nameserver 99.197.99.99 | nameserver 99.196.99.99 |rc=0
Are you running a filtered proxy server or some other process that was working and now is not?
I run Privoxy, installed from the openSUSE repository and activated by YaST Service Manager. It uses 127.0.0.1:8118.
What are the URLs for the repos under /etc/zypp/repos.d?
| @00:28:33 root@pinto | wd=~ | ● l /etc/zypp/repos.d | total 152K | -rw-r--r-- 1 root root 154 Feb 21 18:05 KDE3.repo | -rw-r--r-- 1 root root 128 Feb 21 18:05 Local.repo | -rw-r--r-- 1 root root 188 Feb 21 18:05 NVIDIA:repo-non-free.repo | -rw-r--r-- 1 root root 204 Feb 21 18:05 ftp.gwdg.de-openSUSE_Leap_$releasever.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 openSUSE-Leap-15.5-1.repo | -rw-r--r-- 1 root root 209 Feb 21 18:05 openSUSE:repo-non-oss-debug.repo | -rw-r--r-- 1 root root 203 Feb 21 18:05 openSUSE:repo-non-oss.repo | -rw-r--r-- 1 root root 186 Feb 21 18:05 openSUSE:repo-openh264.repo | -rw-r--r-- 1 root root 197 Feb 21 18:05 openSUSE:repo-oss-debug.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 openSUSE:repo-oss-source.repo | -rw-r--r-- 1 root root 191 Feb 21 18:05 openSUSE:repo-oss.repo | -rw-r--r-- 1 root root 208 Feb 21 18:05 openSUSE:update-backports-debug.repo | -rw-r--r-- 1 root root 202 Feb 21 18:05 openSUSE:update-backports.repo | -rw-r--r-- 1 root root 202 Feb 21 18:05 openSUSE:update-non-oss-debug.repo | -rw-r--r-- 1 root root 196 Feb 21 18:05 openSUSE:update-non-oss.repo | -rw-r--r-- 1 root root 190 Feb 21 18:05 openSUSE:update-oss-debug.repo | -rw-r--r-- 1 root root 184 Feb 21 18:05 openSUSE:update-oss.repo | -rw-r--r-- 1 root root 190 Feb 21 18:05 openSUSE:update-sle-debug.repo | -rw-r--r-- 1 root root 184 Feb 21 18:05 openSUSE:update-sle.repo | -rw-r--r-- 1 root root 149 Feb 21 18:05 packman.repo | -rw-r--r-- 1 root root 200 Feb 21 18:05 repo-backports-debug-update.repo | -rw-r--r-- 1 root root 254 May 23 2023 repo-backports-debug-update.repo.rpmsave | -rw-r--r-- 1 root root 199 Feb 21 18:05 repo-backports-update.repo | -rw-r--r-- 1 root root 199 May 23 2023 repo-backports-update.repo.rpmsave | -rw-r--r-- 1 root root 179 Feb 21 18:05 repo-debug-non-oss.repo | -rw-r--r-- 1 root root 183 Feb 21 18:05 repo-debug-update-non-oss.repo | -rw-r--r-- 1 root root 162 Feb 21 18:05 repo-debug-update.repo | -rw-r--r-- 1 root root 157 Feb 21 18:05 repo-debug.repo | -rw-r--r-- 1 root root 178 Feb 21 18:05 repo-non-oss.repo | -rw-r--r-- 1 root root 164 Feb 21 18:05 repo-openh264.repo | -rw-r--r-- 1 root root 167 Feb 21 18:05 repo-oss.repo | -rw-r--r-- 1 root root 209 Feb 21 18:05 repo-sle-debug-update.repo | -rw-r--r-- 1 root root 234 May 23 2023 repo-sle-debug-update.repo.rpmsave | -rw-r--r-- 1 root root 208 Feb 21 18:05 repo-sle-update.repo | -rw-r--r-- 1 root root 208 May 23 2023 repo-sle-update.repo.rpmsave | -rw-r--r-- 1 root root 160 Feb 21 18:05 repo-source.repo | -rw-r--r-- 1 root root 183 Feb 21 18:05 repo-update-non-oss.repo | -rw-r--r-- 1 root root 165 Feb 21 18:05 repo-update.repo | rc=0
Is there anything in /etc/curlrc or /root/.curlrc that is configuring a proxy at localhost:1080 (or 127.0.0.1:1080)?
| @00:31:16 root@pinto | wd=~ | ● ll /etc/curlrc | /bin/ls: cannot access '/etc/curlrc': No such file or directory | rc=2 | @00:31:50 root@pinto | wd=~ | ● ll .curlrc | /bin/ls: cannot access '.curlrc': No such file or directory | rc=2
Or perhaps an environment variable doing the same? | @00:31:55 root@pinto | wd=~ | ● env|grep 1080 | rc=1 | @00:33:10 root@pinto | wd=~ | ● env|grep 8118 | https_proxy=127.0.0.1/8118 | http_proxy=127.0.0.1/8118 | rc=0
Regards, Rodney.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64
On 2024-02-27 06:34, J. Leslie Turriff wrote:
On 2024-02-24 23:01:51 Rodney Baker wrote:
On Sunday, 25 February 2024 14:06:28 ACDT J. Leslie Turriff wrote:
...
What are the URLs for the repos under /etc/zypp/repos.d? | @00:28:33 root@pinto | wd=~ | ● l /etc/zypp/repos.d | total 152K | -rw-r--r-- 1 root root 154 Feb 21 18:05 KDE3.repo | -rw-r--r-- 1 root root 128 Feb 21 18:05 Local.repo
No. grep "baseurl" /etc/zypp/repos.d/* Or better zypper lr --details > somefile.txt Then attach "somefile.txt". Don't paste unless you can disable line wrap. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hi Leslie, On Tue, Feb 27, 2024 at 12:43:26PM +0100, Carlos E. R. wrote:
What are the URLs for the repos under /etc/zypp/repos.d? | @00:28:33 root@pinto | wd=~ | ● l /etc/zypp/repos.d | total 152K | -rw-r--r-- 1 root root 154 Feb 21 18:05 KDE3.repo | -rw-r--r-- 1 root root 128 Feb 21 18:05 Local.repo
No.
grep "baseurl" /etc/zypp/repos.d/*
Or better
zypper lr --details > somefile.txt
Then attach "somefile.txt". Don't paste unless you can disable line wrap.
'man curl' shows port 1080 just happens to be the "assumed" SOCKS proxy port for curl. Does the Leap 15.5 installer have an option to use a proxy? Has it squirreled a setting away for future use, and now that proxy isn't available, is on a different port, or the port is unspecified? Perhaps that's what Carlos thinks may be tucked away in the repo descriptions. Does /etc/sysconfig/proxy look sensible? Does it say PROXY_ENABLED="yes" and SOCKS_PROXY="" perhaps? Just wondering about the logic if zypper is told to refer to a proxy will libcurl default to SOCKS and inherit an empty/bad value? Also worth checking the journal and doing a quick search for moans about 1080. I don't use proxies, but still curious - and extra sympathetic when someone mentions a networking problem and then "disappears" for a few days ;-) Daniel
participants (6)
-
Carlos E. R. -
Daniel Morris -
Hartmut Rosch -
J. Leslie Turriff -
Manfred Hollstein -
Rodney Baker