February 2024 - openSUSE Support - openSUSE Mailing Lists

15.5, wireguard, resolve-dns.sh script not available? not needed anymore?
by cagsm 12 Apr '24

12 Apr '24

Support, a very simple 15.5 with wireguard, dynamic chaning public ipv4 addresses as endpoint hostname:port i am rather new to this, yet I am not aware if this script for tackling this situation > <https://github.com/WireGuard/wireguard-tools/blob/master/contrib/reresolve-…> is still part of the whole deal, as the wireguard-tools package rpm, does not list this file as its content on leap 15.5 is this deprecated? as maybe > <https://github.com/WireGuard/wireguard-monolithic-historical/blob/master/co…> hints? or whatever that state there means? I have just set up my wireguard with two peers total, so I will see within the next hours or days or so if this tunnel survives dns (ip) changes of the public ipv4 address (endpoint) and how this works. any experience with this on opensuse current versions? ----------- rpm -qi wireguard-tools --filesbypkg .... wireguard-tools /etc/wireguard wireguard-tools /usr/bin/wg wireguard-tools /usr/bin/wg-quick wireguard-tools /usr/lib/systemd/system/wg-quick.target wireguard-tools /usr/lib/systemd/system/wg-quick@.service wireguard-tools /usr/share/bash-completion/completions/wg wireguard-tools /usr/share/bash-completion/completions/wg-quick wireguard-tools /usr/share/doc/packages/wireguard-tools wireguard-tools /usr/share/doc/packages/wireguard-tools/README.md wireguard-tools /usr/share/licenses/wireguard-tools wireguard-tools /usr/share/licenses/wireguard-tools/COPYING wireguard-tools /usr/share/man/man8/wg-quick.8.gz wireguard-tools /usr/share/man/man8/wg.8.gz ------------- ty

3 15

bluetooth headphone not in audio devices
by Jogchum Reitsma 03 Mar '24

03 Mar '24

Hi, Not for the first time, I have trouble connecting a headphone as an audio device. In my case, it is a SennheiserLE-PXC 550-II. Up till now, in these cases I ignored the problem, until some new snapshot made it automagically go away. I can make a bluetooth connection to this device, and it is referred to as an audio device, but it doesn't show up in the list of audio devices. Pipewire doesn't see it, either. How can I convince the system to treat it as an audio device? I'm on TW, yesterday's snapshot. Any help would be greatly appreciated! regards, Jogchum

3 4

zypper fails to connect to 127.0.0.1:1080
by J. Leslie Turriff 28 Feb '24

28 Feb '24

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.x…': | 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/…': | 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/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 '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/repom…': | 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

6 17

dead links on opensuse
by Ianseeks 23 Feb '24

23 Feb '24

Hi Who do i report a dead link to? https://software.opensuse.org/package/akonadi-backend-postgresql?locale=en Been trying to find instructions on how to convert akonadi to use postgresql for someone on the kdepim-users mailing list and having zero success regards Ian :o:opensuse:tumbleweed:20240 :opensuse:tumbleweed:2024021 Qt: 5.15.12 KDE Frameworks: 5.115.0 - KDE Plasma: 5.27.10 - kwin 5.27.10 kmail2 5.24.4 (23.08.4) - akonadiserver 5.24.4 (23.08.4) - Kernel: 6.7.5-1- default - kernel-firmware-radeon 20240201

3 6

VPN-Fun (this time with Wireguard)
by Axel Braun 22 Feb '24

22 Feb '24

Hi, after my recent experience with vpnc, which obviously does not support IPv6. I made another attempt with Wireguard, to connect to a IPv6 only host (DS-LITE connection). I could not get Strongswan for IPSec running. I followed the instructions of the FritzBox (6600 cable) and created a working Wireguard connection. At least it claims to work. Here is the startup protocoll: https://paste.opensuse.org/pastes/41e4656db770 So, if I'm on a IPv6 Telekom Connection and connect, it still shows Teleckm as provider (although VPN host is in via Vodafone) That means in fact it is not working! If I use an IPv4 connection it claims to work again, but same result - in fact it does not. Above log is from a IPv4 I tried to work this out with AVM support (Manufacturer of FritzBox), no success. Any ideas? Has anyone Wiresguard running (on TW)? Thanks Axel

3 19

Sent a message with video (3.3M) in size:
by -pj 19 Feb '24

19 Feb '24

Hi, I sent a message to users(a)lists.opensuse.org with a video of an error that displays very very quickly see [:11]. Will this message be to large or what will happen? -Thanks

5 7

Intermittent machine lockup when attempting shutdown or suspend:
by -pj 17 Feb '24

17 Feb '24

Hi, When shutdown or powercycling attempts are envoked, the a machine here is locking up with frozen message output displayed in TTY (I think this is the correct wording to use for this). What is the best way to show these messages since the photo taken of the trace output is larger than susepaste will allow? Would this possibly have something to do with providing Y2logs? Or maybe reviewing a journal file perhaps? -Regards

3 2

Boot problem
by Vojtěch Zeisek 15 Feb '24

15 Feb '24

Hi, I have AMD desktop with 4 drives, and installation of TW works, but system doesn't boot. I have to press F12 and manually select UEFI opensuse-secureboot or opensuse item. The machine has - 2x 2TB NVMe - used as SW RAID0 for encrypted /home - 1x 1TB SSD for /boot/efi and encrypted LVM with / and swap - 1x 5TB HDD for internal backups (rsync with cron) Interestingly, when I boot install USB drive, I randomly see SSD as sda or sdb, and HDD as sdb or sda. Anyway, regardless I place /boot/efi on beginning of SSD or 1st NVMe, BIOS has troubles to find boot openSUSE. Also, when I press F12 to manually select boot device, I sometimes get info that the firmware was reset (Problem with CMOS battery or so?), but otherwise everything seems correct there. When I install Leap with above setup, it works. I have similar setup (2x NVMe, 1st with /boot/efi and encrypted LVM with /and swap, and 2nd with encrypted / home) on another machine, and I use to use setup with /boot/efi and rest in encrypted LVM for years, so I'm sure this setup works reliably. So I wonder if I do something wrong or I face some issue with motherboard of my desktop...? Yours, V. -- Vojtěch Zeisek https://trapa.cz/ Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/

3 3

Repositories and priority
by Marco Calistri 13 Feb '24

13 Feb '24

Hello! File /usr/lib64/gstreamer-1.0/libgstresindvd.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) File /usr/lib64/gstreamer-1.0/libgstsiren.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) How should I avoid to receive this kind of warnings during the update process? sudo zypper lr -E -P # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+----------------------------------+-------------------------------------------+---------+-----------+---------+--------- 3 | Packman | Packman | Sì | (r ) Sì | Sì | 80 6 | download.opensuse.org-tumbleweed | Repository principale degli aggiornamenti | Sì | (r ) Sì | Sì | 90 1 | Google_Chrome_repository | Google_Chrome_repository | Sì | (r ) Sì | Sì | 99 2 | Hamradio | Hamradio | Sì | (r ) Sì | Sì | 99 4 | download.opensuse.org-non-oss | Repository principale (NON-OSS) | Sì | (r ) Sì | Sì | 99 5 | download.opensuse.org-oss | Repository principale (OSS) | Sì | (r ) Sì | Sì | 99 15 | nordvpn | nordvpn | Sì | (r ) Sì | Sì | 99 20 | skype-stable | skype (stable) | Sì | (r ) Sì | Sì | 99 I wish to keep Packman at higher priority, now I don't know what OSS Vs. @System means in the warning. Could you please be so kind to explain? Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20240209 Kernel: 6.7.2-1-default - XFCE: (4.18.3) Uptime: 10:00:01 up 5 days 19:50, 1 user, carico medio: 1,90, 2,46, 1,91

10 16

Repositories and priority
by Marco Calistri 13 Feb '24

13 Feb '24

Hello! File /usr/lib64/gstreamer-1.0/libgstresindvd.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) File /usr/lib64/gstreamer-1.0/libgstsiren.so from install of gstreamer-plugins-bad-1.22.9-3.1.x86_64 (Repository principale (OSS)) conflicts with file from package gstreamer-plugins-bad-orig-addon-1.22.6-33.2.x86_64 (@System) How should I avoid to receive this kind of warnings during the update process? sudo zypper lr -E -P # | Alias | Name | Enabled | GPG Check | Refresh | Priority ---+----------------------------------+-------------------------------------------+---------+-----------+---------+--------- 3 | Packman | Packman | Sì | (r ) Sì | Sì | 80 6 | download.opensuse.org-tumbleweed | Repository principale degli aggiornamenti | Sì | (r ) Sì | Sì | 90 1 | Google_Chrome_repository | Google_Chrome_repository | Sì | (r ) Sì | Sì | 99 2 | Hamradio | Hamradio | Sì | (r ) Sì | Sì | 99 4 | download.opensuse.org-non-oss | Repository principale (NON-OSS) | Sì | (r ) Sì | Sì | 99 5 | download.opensuse.org-oss | Repository principale (OSS) | Sì | (r ) Sì | Sì | 99 15 | nordvpn | nordvpn | Sì | (r ) Sì | Sì | 99 20 | skype-stable | skype (stable) | Sì | (r ) Sì | Sì | 99 I wish to keep Packman at higher priority, now I don't know what OSS Vs. @System means in the warning. Could you please be so kind to explain? Thanks! -- Marco Calistri Build: openSUSE Tumbleweed 20240209 Kernel: 6.7.2-1-default - XFCE: (4.18.3) Uptime: 10:00:01 up 5 days 19:50, 1 user, carico medio: 1,90, 2,46, 1,91

5 9