June 2022 - openSUSE Support - openSUSE Mailing Lists

After updating Leap 15.3 all repositories become invalid?
by J Leslie Turriff 09 Jul '22

09 Jul '22

Last night I performed | zypper --non-interactive update --no-recommends then rebooted. Now when I perform | zypper refresh I get this: | ~ | ● zypper refresh | Retrieving repository 'Codec' metadata ............................................................................................................................................................................................................................. [error] | Repository 'Codec' is invalid. | [Codec|http://opensuse-guide.org/repo/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [Codec|http://opensuse-guide.org/repo/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Codec' because of the above error. | Repository 'Local' is up to date. | Problem retrieving files from 'Mozilla'. | Download (curl) error for 'https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/repod…': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'Mozilla' because of the above error. | Retrieving repository 'Packman Repository' metadata ................................................................................................................................................................................................................ [error] | Repository 'Packman Repository' is invalid. | [ftp.gwdg.de-openSUSE_Leap_$releasever| http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [ftp.gwdg.de-openSUSE_Leap_$releasever| http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Packman Repository' because of the above error. | Problem retrieving files from 'google-chrome'. | Download (curl) error for 'https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'google-chrome' because of the above error. | Problem retrieving files from 'hplip'. | Download (curl) error for 'https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15…': | Error code: HTTP response: 0 | Error message: The requested URL returned error: 404 | | Please see the above error message for a hint. | Skipping repository 'hplip' because of the above error. | Retrieving repository 'Fonts' metadata ............................................................................................................................................................................................................................. [error] | Repository 'Fonts' is invalid. | [openSUSE_Leap_15.3| http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/] Valid metadata not found at specified URL | History: | - [openSUSE_Leap_15.3| http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Fonts' because of the above error. | Retrieving repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' metadata ...................................................................................................................................................... [error] | Repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' is invalid. | [repo-backports-debug-update| http://download.opensuse.org/update/leap/15.3/backports_debug/] Valid metadata not found at specified URL | History: | - [repo-backports-debug-update| http://download.opensuse.org/update/leap/15.3/backports_debug/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with Backports debuginfo package updates for openSUSE Leap' because of the above error. | Retrieving repository 'Update repository of openSUSE Backports' metadata ........................................................................................................................................................................................... [error] | Repository 'Update repository of openSUSE Backports' is invalid. | [repo-backports-update|http://download.opensuse.org/update/leap/15.3/backpor…] Valid metadata not found at specified URL | History: | - [repo-backports-update|http://download.opensuse.org/update/leap/15.3/backpor…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository of openSUSE Backports' because of the above error. | Retrieving repository 'Debug Repository' metadata .................................................................................................................................................................................................................. [error] | Repository 'Debug Repository' is invalid. | [repo-debug|http://download.opensuse.org/debug/distribution/leap/15.3/repo/o…] Valid metadata not found at specified URL | History: | - [repo-debug|http://download.opensuse.org/debug/distribution/leap/15.3/repo/o…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Debug Repository' because of the above error. | Retrieving repository 'Debug Repository (Non-OSS)' metadata ........................................................................................................................................................................................................ [error] | Repository 'Debug Repository (Non-OSS)' is invalid. | [repo-debug-non-oss| http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/] Valid metadata not found at specified URL | History: | - [repo-debug-non-oss| http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Debug Repository (Non-OSS)' because of the above error. | Retrieving repository 'Update Repository (Debug)' metadata ......................................................................................................................................................................................................... [error] | Repository 'Update Repository (Debug)' is invalid. | [repo-debug-update|http://download.opensuse.org/debug/update/leap/15.3/oss] Valid metadata not found at specified URL | History: | - [repo-debug-update|http://download.opensuse.org/debug/update/leap/15.3/oss] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Debug)' because of the above error. | Retrieving repository 'Update Repository (Debug, Non-OSS)' metadata ................................................................................................................................................................................................ [error] | Repository 'Update Repository (Debug, Non-OSS)' is invalid. | [repo-debug-update-non-oss|http://download.opensuse.org/debug/update/leap/15…] Valid metadata not found at specified URL | History: | - [repo-debug-update-non-oss| http://download.opensuse.org/debug/update/leap/15.3/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Debug, Non-OSS)' because of the above error. | Retrieving repository 'Non-OSS Repository' metadata ................................................................................................................................................................................................................ [error] | Repository 'Non-OSS Repository' is invalid. | [repo-non-oss|http://download.opensuse.org/distribution/leap/15.3/repo/non-o…] Valid metadata not found at specified URL | History: | - [repo-non-oss|http://download.opensuse.org/distribution/leap/15.3/repo/non-o…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Non-OSS Repository' because of the above error. | Retrieving repository 'Main Repository' metadata ................................................................................................................................................................................................................... [error] | Repository 'Main Repository' is invalid. | [repo-oss|http://download.opensuse.org/distribution/leap/15.3/repo/oss/] Valid metadata not found at specified URL | History: | - [repo-oss|http://download.opensuse.org/distribution/leap/15.3/repo/oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Main Repository' because of the above error. | Retrieving repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' metadata ........................................................................................................................................................ [error] | Repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' is invalid. | [repo-sle-debug-update|http://download.opensuse.org/debug/update/leap/15.3/s…] Valid metadata not found at specified URL | History: | - [repo-sle-debug-update|http://download.opensuse.org/debug/update/leap/15.3/s…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with debuginfo for updates from SUSE Linux Enterprise 15' because of the above error. | Retrieving repository 'Update repository with updates from SUSE Linux Enterprise 15' metadata ...................................................................................................................................................................... [error] | Repository 'Update repository with updates from SUSE Linux Enterprise 15' is invalid. | [repo-sle-update|http://download.opensuse.org/update/leap/15.3/sle/] Valid metadata not found at specified URL | History: | - [repo-sle-update|http://download.opensuse.org/update/leap/15.3/sle/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update repository with updates from SUSE Linux Enterprise 15' because of the above error. | Retrieving repository 'Source Repository' metadata ................................................................................................................................................................................................................. [error] | Repository 'Source Repository' is invalid. | [repo-source|http://download.opensuse.org/source/distribution/leap/15.3/repo…] Valid metadata not found at specified URL | History: | - [repo-source|http://download.opensuse.org/source/distribution/leap/15.3/repo…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Source Repository' because of the above error. | Retrieving repository 'Main Update Repository' metadata ............................................................................................................................................................................................................ [error] | Repository 'Main Update Repository' is invalid. | [repo-update|http://download.opensuse.org/update/leap/15.3/oss] Valid metadata not found at specified URL | History: | - [repo-update|http://download.opensuse.org/update/leap/15.3/oss] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Main Update Repository' because of the above error. | Retrieving repository 'Update Repository (Non-Oss)' metadata ....................................................................................................................................................................................................... [error] | Repository 'Update Repository (Non-Oss)' is invalid. | [repo-update-non-oss|http://download.opensuse.org/update/leap/15.3/non-oss/] Valid metadata not found at specified URL | History: | - [repo-update-non-oss|http://download.opensuse.org/update/leap/15.3/non-oss/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Update Repository (Non-Oss)' because of the above error. | Retrieving repository 'Untested Updates' metadata .................................................................................................................................................................................................................. [error] | Repository 'Untested Updates' is invalid. | [repo-update-test|http://download.opensuse.org/update/leap/15.3-test/] Valid metadata not found at specified URL | History: | - [repo-update-test|http://download.opensuse.org/update/leap/15.3-test/] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'Untested Updates' because of the above error. | Retrieving repository 'trinity-bin' metadata ....................................................................................................................................................................................................................... [error] | Repository 'trinity-bin' is invalid. | [trinity-bin| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Valid metadata not found at specified URL | History: | - [trinity-bin| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'trinity-bin' because of the above error. | Retrieving repository 'trinity-noarch' metadata .................................................................................................................................................................................................................... [error] | Repository 'trinity-noarch' is invalid. | [trinity-noarch| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Valid metadata not found at specified URL | History: | - [trinity-noarch| http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R…] Repository type can't be determined. | | Please check if the URIs defined for this repository are pointing to a valid repository. | Skipping repository 'trinity-noarch' because of the above error. | Some of the repositories have not been refreshed because of an error. | @20:30:33,root@pinto rc=4 I had not made any changes before or after doing the update. Here are my repositories: | ~ | ● zypper lr -u | Repository priorities in effect: (See 'zypper lr -P' for details) | 97 (raised priority) : 1 repository | 98 (raised priority) : 3 repositories | 99 (default priority) : 19 repositories | | # | Alias | Name | Enabled | GPG Check | Refresh | URI | ---+---------------------------------------+------------------------------------------------------------------------------+---------+-----------+---------+-------------------------------------------------------------------------------------- | 1 | Codec | Codec | Yes | (r ) Yes | Yes | http://opensuse-guide.org/repo/openSUSE_Leap_15.3/ | 2 | Local | Local | Yes | ( ) No | Yes | dir:/usr/local/RPMrepository | 3 | Mozilla | Mozilla | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/mozilla/openSUSE_Leap_15.3/ | 4 | ftp.gwdg.de-openSUSE_Leap_$releasever | Packman Repository | Yes | (r ) Yes | Yes | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.3/ | 5 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | https://dl.google.com/linux/chrome/rpm/stable/x86_64 | 6 | hplip | hplip | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15… | 7 | openSUSE_Leap_15.3 | Fonts | Yes | (r ) Yes | Yes | http://download.opensuse.org/repositories/M17N:/fonts/openSUSE_Leap_15.3/ | 8 | repo-backports-debug-update | Update repository with Backports debuginfo package updates for openSUSE Leap | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/backports_debug/ | 9 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/backports/ | 10 | repo-debug | Debug Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.3/repo/oss/ | 11 | repo-debug-non-oss | Debug Repository (Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/distribution/leap/15.3/repo/non-oss/ | 12 | repo-debug-update | Update Repository (Debug) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/oss | 13 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/non-oss/ | 14 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/non-oss/ | 15 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.3/repo/oss/ | 16 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/update/leap/15.3/sle/ | 17 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/sle/ | 18 | repo-source | Source Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/distribution/leap/15.3/repo/oss/ | 19 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/oss | 20 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3/non-oss/ | 21 | repo-update-test | Untested Updates | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/leap/15.3-test/ | 22 | trinity-bin | trinity-bin | Yes | (r ) Yes | Yes | http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… | 23 | trinity-noarch | trinity-noarch | Yes | (r ) Yes | Yes | http://mirror.ppa.trinitydesktop.org/trinity/rpm/opensuse15.3/trinity-r14/R… | @20:30:15,root@pinto rc=0 Leslie -- Platform: Linux Distribution: openSUSE Leap 15.3 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.11 tde-config: 1.0

7 14

Re: Strange behaviour of bash script in crontab
by Freek de Kruijf 28 Jun '22

28 Jun '22

Op maandag 27 juni 2022 19:03:23 CEST schreef Freek de Kruijf: I did twice a "strace dig smtp.gmail.com", one with the issue and the other one without the SIGTERM issue. I provide the last few lines of the output of these commands: --- with SIGTERM issue --- ;; Query time: 0 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Mon Jun 27 18:46:47 CEST 2022 ;; MSG SIZE rcvd: 59 <unfinished ...>) = ? +++ killed by SIGTERM +++ Terminated --- without SIGTERM issue --- ;; Query time: 0 msec ;; SERVER: 192.168.178.1#53(192.168.178.1) ;; WHEN: Mon Jun 27 18:59:12 CEST 2022 ;; MSG SIZE rcvd: 59 {si_signo=SIGTERM, si_code=SI_USER, si_pid=16663, si_uid=1001}, NULL, 8) = 15 (SIGTERM) write(8, "\1\0\0\0\0\0\0\0", 8) = 8 futex(0xffffba4f2020, FUTEX_WAKE_PRIVATE, 1) = 1 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 write(8, "\1\0\0\0\0\0\0\0", 8) = 8 close(6) = 0 close(7) = 0 close(8) = 0 close(3) = 0 munmap(0xffffba3a4000, 1314816) = 0 write(10, "\0\0\0\0\377\377\377\377", 8) = 8 epoll_ctl(11, EPOLL_CTL_DEL, 9, 0xffffc8568268) = 0 close(11) = 0 munmap(0xffffb9378000, 172032) = 0 futex(0xffffba4f30a0, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0xffffba4f3020, FUTEX_WAKE_PRIVATE, 1) = 1 futex(0xffffb9ba20b0, FUTEX_WAIT, 16665, NULL) = -1 EAGAIN (Resource temporarily unavailable) munmap(0xffffba4e5000, 266240) = 0 futex(0xffffbb37408c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0xffffbb37404c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 futex(0xffffbb373f1c, FUTEX_WAKE_PRIVATE, 2147483647) = 0 exit_group(0) = ? +++ exited with 0 +++ -- fr.gr. member openSUSE Freek de Kruijf

1 0

Strange behaviour of bash script in crontab
by Freek de Kruijf 27 Jun '22

27 Jun '22

I have a crontab entry which runs ones per hour calling a bash script. The content of the script is: #! /bin/bash # # dig smtp.gmail.com >> digoutput.txt 2>&1 rc=$? [ $rc -ne 0 ] && echo "exitcode dig = $rc" The output of the cronjob is: /home/xxxxx/bin/script.sh: line 4: 32349 Terminated dig smtp.gmail.com >> digoutput.txt 2>&1 exitcode dig =143 143 means the dig command is terminated by SIGTERM Any idea? -- fr.gr. member openSUSE Freek de Kruijf

5 7

[support][TW] logrotate zypper.log
by Felix Miata 26 Jun '22

26 Jun '22

On a PC that sees only occasional use, I'm using what appears to be default files in /etc/logrotate.d/, timestamped Oct 2018. zypper.lr there specifies size 10M. After a reboot with its size exceeding 10M, e.g. 25,000K, it remains the same size until some later unknown time or number of boots when it finally gets rotated and shrunk. Why? How can rotating and compressing it be made to happen when on boot it is found to exceed the configured limit. Is it simply that logrotate needs to be forced to run other than via a daily cron job? If yes, what is a good method? If not, how? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

4 8

TW: systemd logging services
by Axel Braun 25 Jun '22

25 Jun '22

Hi, since some TW snapshots I see a systemd logging services job hanging on shutdowen, until it is killed after 1:30 min Anyone else noticed this? Cheers Axel

3 2

Systemsettings KDE
by JJM de Faber 25 Jun '22

25 Jun '22

OpenSuse version 15.4 ,up to date, desktop KDE When I try to install a new global theme or other additional features I get the following errer message: "Download of "Leaf Light Color Aurorae Window Decoration" failed, error: SETTINGS invalid number of concurrent streams" What is the problem ???

1 0

Fwd: opensuse server issues going on now ?
by Luna Jernberg 24 Jun '22

24 Jun '22

---------- Forwarded message --------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Fri, Jun 24, 2022 at 9:57 AM Subject: Fwd: opensuse server issues going on now ? To: <support(a)opensuse.org> ---------- Forwarded message --------- From: Luna Jernberg <droidbittin(a)gmail.com> Date: Fri, Jun 24, 2022 at 7:14 AM Subject: Fwd: opensuse server issues going on now ? To: opensuse-project <opensuse-project(a)opensuse.org> Cc: admin <admin(a)opensuse.org> ---------- Forwarded message ---------- From: Joe Salmeri <jmscdba(a)gmail.com> Date: Thu, 23 Jun 2022 18:23:02 -0000 Subject: opensuse server issues going on now ? To: factory(a)lists.opensuse.org I was attempting to update to the new 20220622 build that was just published. I use tumbleweed-cli to control which build I switch to. In does not show a new build as available until after the build has been copied to a build folder ( example: https://download/opensuse.org/history20220622 ) I switched tumbleweed-cli to build 20220622, here are my repoositories: Repository priorities in effect: (See 'zypper lr -P' for details) 90 (raised priority) : 1 repository 99 (default priority) : 7 repositories # | Alias | Name | Enabled | GPG Check | Refresh | URI --+----------------------------------+--------------------------------------+---------+-----------+---------+------------------------------------------------------------------------------------- 1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) (20220622) | Yes | (r ) Yes | Yes | http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/ 2 | download.opensuse.org-oss | Main Repository (DEBUG) | Yes | (r ) Yes | Yes | http://download.opensuse.org/debug/tumbleweed/repo/oss/ 3 | download.opensuse.org-oss_1 | Main Repository (Sources) | Yes | (r ) Yes | Yes | http://download.opensuse.org/source/tumbleweed/repo/oss/ 4 | download.opensuse.org-oss_2 | Main Repository (OSS) (20220622) | Yes | (r ) Yes | Yes | http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/ 5 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/tumbleweed/ 6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | https://dl.google.com/linux/chrome/rpm/stable/x86_64 7 | openSUSE-20210215-0 | openSUSE-20210215-0 | No | ---- | ---- | cd:/?devices=/dev/disk/by-id/ata-VMware_Virtual_IDE_CDROM_Drive_10000000000000000001 8 | skype-stable | skype (stable) | Yes | (r ) Yes | Yes | https://repo.skype.com/rpm/stable/ 9 | vlc | VLC | Yes | (r ) Yes | Yes | http://download.videolan.org/pub/vlc/SuSE/Tumbleweed/ zypper dup or zypper refresh fails with: Retrieving repository 'Main Repository (NON-OSS) (20220622)' metadata ...........................................................................................[error] Repository 'Main Repository (NON-OSS) (20220622)' is invalid. [download.opensuse.org-non-oss| http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/] Valid metadata not found at specified URL History: - Download (curl) error for ' http://download.opensuse.org/history/20220622/tumbleweed/repo/non-oss/repod… ': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 98 ms: Connection refused - Can't provide ./repodata/dc7b3afc60d401de7ee4b3ef2816045a98feb2e30153cffcb43f32300f5dc389-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (NON-OSS) (20220622)' because of the above error. Retrieving repository 'Main Repository (DEBUG)' metadata ........................................................................................................[error] Repository 'Main Repository (DEBUG)' is invalid. [download.opensuse.org-oss| http://download.opensuse.org/debug/tumbleweed/repo/oss/] Valid metadata not found at specified URL History: - Download (curl) error for ' http://download.opensuse.org/debug/tumbleweed/repo/oss/repodata/f889c274abb… ': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/f889c274abb0761e4b3869ff0c8bacb1bd2f253449c86e2a193bbdb5fb1a55bb-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (DEBUG)' because of the above error. Retrieving repository 'Main Repository (Sources)' metadata ......................................................................................................[error] Repository 'Main Repository (Sources)' is invalid. [download.opensuse.org-oss_1| http://download.opensuse.org/source/tumbleweed/repo/oss/] Valid metadata not found at specified URL History: - Download (curl) error for ' http://download.opensuse.org/source/tumbleweed/repo/oss/repodata/a743c61b4c… ': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/a743c61b4c1af8cc7cc4c46638a9892e5a46781cf86c2a3b49b09578a4b72337-primary.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (Sources)' because of the above error. Retrieving repository 'Main Repository (OSS) (20220622)' metadata ...............................................................................................[error] Repository 'Main Repository (OSS) (20220622)' is invalid. [download.opensuse.org-oss_2| http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/] Valid metadata not found at specified URL History: - Download (curl) error for ' http://download.opensuse.org/history/20220622/tumbleweed/repo/oss/repodata/… ': Error code: Connection failed Error message: Failed to connect to mirrorcache-us.opensuse.org port 80 after 84 ms: Connection refused - Can't provide ./repodata/90d89069e262e73545f7149e8ce79f699ef7f2fe8198b599dfe601fe6836274f-appdata.xml.gz Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Main Repository (OSS) (20220622)' because of the above error. Repository 'Main Update Repository' is up to date. Repository 'google-chrome' is up to date. Repository 'skype (stable)' is up to date. Repository 'VLC' is up to date. Some of the repositories have not been refreshed because of an error. If I go to the one of the 20220622 download locations in Chrome https://download.opensuse.org/history/20220622/tumbleweed/repo/oss/x86_64/ And then try to manually download a single item like: konsole-22.04.2-1.1.x86_64.rpm It returns: This site can’t be reached mirrorcache-us.opensuse.org refused to connect. I have a direct internet connection ( No proxy ) so it appears that there is a problem with the cache servers. Going to an older build like 20220606 which is what I am currently running has the same issues so that eliminates that 20220622 had not finished copying yet. Anybody else seeing this?

1 0

[TW] What is akonadi? Can I get rid of it?
by Bob Williams 22 Jun '22

22 Jun '22

I have just installed Tumbleweed on a new partition. I previously used (and still have available) Leap 15.4. I am new to TW, and want to try it out. In Tumbleweed, akonadi_davgroupware_resource_6 keeps asking for a kwallet password. I have never used kwallet, so I don't have a password to enter. I seem to remember tabooing akonadi a long, long time ago, but I can't remember which files to taboo. I do not use kontact, kmail, kaddressbook, knotes etc. Kleopatra is useful, but I can live without it. Regards Bob -- Bob Williams

2 2

Problem with keyboard layout US int. with dead keys in latest Tumbleweed
by Freek de Kruijf 21 Jun '22

21 Jun '22

Hi, since one of the latest upgrades of Tumbleweed, the system, using KDE, does not give me the special characters that are made using dead keys. I tried the two versions of keyboard US international, but both do not give me these special characters, at least not when typing this message in KMail, in the konsole and in lokalize. I can get these characters in Firefox. My workaround is using the application Special Characters, but this is only a workaround. Anybody having the same problem? Solution? -- fr.gr. member openSUSE Freek de Kruijf

5 8

Bash not working in chroot environment during update
by Fodrek Peter ml. 16 Jun '22

16 Jun '22

Dear openSUSE experts, I am to try to recover system via update Now package update crashes on /bin/sh not found even if it exist It seems that bash dose not work in chroot environment as of /mnt/bin/bash works chroot /mnt /bin/bash crashes on file not found ldconfig -vr /mnt as well as running ldconfig in busybox as of chroot /mnt /bin/busybox ldconfig -v does not help ldd dose not run in busybox as vell I was mentioned to copy some *so* library files for install usb into system to be updated but I am not sure about minimal set of libraries to be copied as I am to influence updated system at miniml possible level Is there anybody do help me with this problem I look forward hearing from you Yours faithfully Peter Fodrek,j.r.

2 2

nvidia G04 display broken by kernel 5.18.1
by Patrick Shanahan 15 Jun '22

15 Jun '22

Tumbleweed 20220606 kernel 5.18.1 nvidia 390.151 GeForce GTS 450 nvidia-computeG04-390.151-60.2.x86_64 nvidia-gfxG04-kmp-default-390.151_k5.17.9_9-60.4.x86_64 nvidia-glG04-390.151-60.2.x86_64 x11-video-nvidiaG04-390.151-60.2.x86_64 I do not get full graphical screen with kernel 5.18.1 meanwhile running 5.17.9 w/o a problem. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

3 10

Can't install keepassxc in Leap 15.4
by J Leslie Turriff 15 Jun '22

15 Jun '22

After upgrading to Leap 15.4 I'm stuck without my password wallet. keepassxc requires glibc-2.34, but it's not in any of the repositories. I found several RPMs on other sites, but they won't install either because of more dependencies. Should I bother the keepassxc maintainers or the openSUSE maintainers about this? Leslie -- Operating System: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0

5 9

flatpak and flathub, proven and good way to get software? - e.g. elements chat (matrix network and platform)
by cagsm 15 Jun '22

15 Jun '22

Dear support, more questions by a noob with linux and desktop. The elements chat (formerly riot chat) for the matrix ecosystem and network, seems to be available via flatpak flathub according to <https://element.io/get-started#linux-details> And digging via zypper or looking for native (?) packages for opensuse didnt bring up much current or maintained stuff? Then I also discovered the GUI interface in KDE called KDE Discover <https://apps.kde.org/de/discover/> which also has an interface to flatpak or such. Now I wonder how I would use a permanent and most up-to-date element chat instance in the best way on a current opensuse leap. Thanks for sharing your experiences and knowledge about whats proven and what not and best pracices and all. ty.

6 11

Leap 15.4: Where can I find Qt 6.2 LTS?
by Martin Winter 14 Jun '22

14 Jun '22

I'm currently porting a Qt project to Qt 6, specifically the Qt 6.2 LTS. I'm on Leap 15.3 and am using the builds from https://build.opensuse.org/project/show/KDE:Qt:6.2. But I can see that even for 15.3 they are mostly completely disabled and for 15.4 they are not present at all, so this is probably not the right location. Can somebody give me a pointer where Qt 6.2 LTS is built, especially for 15.4?

2 2

setting screen brightness with special keys via keyboard, scan codes and what not
by cagsm 13 Jun '22

13 Jun '22

Support list, doing some first steps on rather mobile systems a.k.a. notebook laptop with leap 15.4 for example. Install went fine. Now digging into the first real world situation and problems here. machine vendor has some special keys on keyboard, so called and named "FN" key, even fn-lock with small LED lighting up when setting the lock FN function. Apparently there are no standards(?) for certain advanced features such as turn up and down volume (speaker) or turning up and down screen brightness and other fancy stuff :/ Coming a long way I remember keyboard scan codes ;) so then trying to look that stuff up and how to use 15.4 kde desktop installation to adjust the screen brightness. In the power settings of the kde desktop there is a place where I can adjust the screen brightness just fine via mouse and gui elements of KDE. so far so good so the basic hardware driver of some kind to adjust LED energy output and thus adjusting brightness of background illumination and stuff works fine. Then i tried to find to adjust the shortcuts/keyboard shortcuts for this feature. There is some KDE konfiguration dialog where it asks me to press my desired key combination for examle for brightness and volume of the speaker. Only it notices or gets told the wrong keyboard sequences, it always only reports Fx function key values and reminds me that many are already taken for other features and functions and if I want to redefine those. So wht now? Digging around on the net there are people that claim that FN key at its own doesnt create a scan code but only will deliver differing scan codes for those specialty keys though. But apparently KDE doesnt get told or doesnt notices the differing scan codes or something else is amiss? where and how to use the special keys of todays hardware and what is the reasoning behind? Apparently its not just that easy as a mere scan code that gets created and sent to the software? what I for example also noticed is that in the power settings, this machine reacts just fine when closing the machines lid, but defining the power button behavior just doesnt do anything. maybe thats a special key in some ways as well, not wired via ATX or what other ways such as in desktop ways and more :( any isights? ty.

5 8

Re: Your confirmation is needed to leave the support@lists.opensuse.org mailing list.
by Robert Williams 11 Jun '22

11 Jun '22

On Sat, 11 Jun 2022 11:20:22 +0000 support-confirm+f6d99a723c7ef260f627ff138ae58666730ab947(a)lists.opensuse.org wrote: > Email Address Unsubscription Confirmation > > Hello, this is the GNU Mailman server at lists.opensuse.org. > > We have received an unsubscription request for the email address > > bob.williams(a)karmasailing.uk > > Before GNU Mailman can unsubscribe you, you must first confirm your > request. You can do this by simply replying to this message. > > Or you should include the following line -- and only the following > line -- in a message to support-request(a)lists.opensuse.org: > > confirm f6d99a723c7ef260f627ff138ae58666730ab947 > > Note that simply sending a `reply' to this message should work from > most mail readers. > > If you do not wish to unsubscribe this email address, simply > disregard this message. If you think you are being maliciously > unsubscribed from the list, or have any other questions, you may > contact > > support-owner(a)lists.opensuse.org -- Robert Williams bob.williams(a)karmasailing.uk +44 (0)1903 866960

3 3

After installing Leap 15.4, zypper and YaST can't see repositories.
by J Leslie Turriff 11 Jun '22

11 Jun '22

Hello, I have been having trouble getting zypper and YaST to see the openSUSE repositories from Leap 15.3, and now after installing Leap 15.4 into newly formatted partitions as well. I'm getting a message that tells me that they are trying to communicate with privoxy, which uses port 8118: | ~ | ● zypper ref | Retrieving repository 'Update Repository (Non-Oss)' metadata ....................................................................................................[done] | Building repository ''Update Repository (Non-Oss) cache .........................................................................................................[done] | Problem retrieving files from 'Update Repository (Non-Oss)'. | Download (curl) error for 'http://download.opensuse.org/update/leap/15.4/non-oss/repodata/repomd.xml': | Error code: Connection failed | Error message: Failed to connect to 127.0.0.1 port 8118 after 0 ms: Connection refused | 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. | @19:18:51,root@pinto rc=4 Just to be sure, I checked to see if it's even installed: | ~ | $ zypper se -i privoxy | Loading repository data... | Reading installed packages... | No matching items found. | @19:20:08,leslie@pinto rc=104 Nope. Then I looked at sysconfig: | YaST2 - sysconfig @ pinto | | ┌Configuration Options───────────────────┐ /etc/sysconfig Editor | │─+─Applications │ Current Selection: Network/Proxy | │─+─Desktop │ | │─+─Hardware │ Setting of: PROXY_ENABLED [Default] | │─┬─Network │ no▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓ but it says it's not enabled. Just to be safe, I added software.opensuse.org the the NO_PROXY list | YaST2 - sysconfig @ pinto | | ┌Configuration Options───────────────────┐ /etc/sysconfig Editor | │─+─Applications │ Current Selection: Network/Proxy | │─+─Desktop │ | │─+─Hardware │ Setting of: NO_PROXY [Default] | │─┬─Network │ localhost, 127.0.0.1, software.opensuse.org▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒↓ but that didn't make any difference. I grepped the zypper .conf files for proxy and 8118, but found no matches. Can anyone out there explain where zypper is getting the idea that it needs to use privoxy? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.0.12 tde-config: 1.0

2 2

Re: Help on wrong HDD partitioning after using Clonezilla
by Marco Calistri 03 Jun '22

03 Jun '22

Il 01/06/22 01:46, Robert Webb ha scritto: > Marco, re-reading your message, I see that only a few of your partitions are > Linux. LVM would not be usable for the rest, so ignore all that. Hello Robert! Thanks for your double response! Sorry for my delayed reply, but I spent almost two days to get rid of the issue and finally I've sorted it out. I'm not using LVM here, but EXT-4 with an extended partition. I had to re-partitioning my HDD in order to have the number of sectors divisible by 8 as requested by my 1 Terabyte HDD Western Digital, which has the advanced format using 4096 bytes/Sector. Now I don't get anymore the "Boundary" warning message, by the way my partitions are not "disk ordered", due the fact that I had to rearrange everything on the fly using Gparted. I've read that this unordered partitions doesn't represent a problem in any form, so for the moment I will stay with it. (I'm including in this email the list "opensuse-support" as well, in order to update the topic in general and provide an update to Carlos in particular, since him has provided me some feedback's) #Current HDD onfiguration marco@linux-turion64:~> sudo fdisk -x [sudo] password di root: Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 514047 512000 7 HPFS 0/32/33 31/254/31 80 /dev/sda2 1919971328 1953523711 33552384 82 Linu 1023/254/63 1023/254/63 /dev/sda3 976773120 1919971327 943198208 83 Linu 1023/254/63 1023/254/63 /dev/sda4 514048 976773119 976259072 f W95 31/254/32 1023/254/63 /dev/sda5 820649984 976773119 156123136 83 Linu 1023/254/63 1023/254/63 /dev/sda6 224763904 820647935 595884032 7 HPFS 1023/254/63 1023/254/63 /dev/sda7 516096 1437695 921600 7 HPFS 32/32/1 89/125/36 /dev/sda8 1439744 224761855 223322112 7 HPFS 89/158/6 1023/254/63 *Partition table entries are not in disk order.* And this was *before*: #Previous HDD configuration marco@linux-turion64:~> sudo fdisk -x Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 1026036 1023989 7 HPFS 0/32/33 63/221/19 80 /dev/sda2 1026037 447673612 446647576 7 HPFS 63/221/20 218/100/23 /dev/sda3 447673613 449516792 1843180 27 Hidd 218/100/24 333/32/12 /dev/sda4 449516793 1953523118 1504006326 f W95 333/32/13 769/48/30 /dev/sda5 449516795 617287136 167770342 83 Linu 333/32/15 536/88/33 /dev/sda6 617287138 1918772938 1301485801 83 Linu 536/88/35 654/23/20 /dev/sda7 1918772940 1953521663 34748724 82 Linu 654/23/22 1023/254/63 Partition 2 does not start on physical sector boundary. Partition 3 does not start on physical sector boundary. Partition 4 does not start on physical sector boundary. Partition 5 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary. Partition 7 does not start on physical sector boundary. Cheers, -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7

1 0

Help on wrong HDD partitioning after using Clonezilla
by Marco Calistri 01 Jun '22

01 Jun '22

Hello, This is not an openSUSE specific support request but it's related to a series of error messages I noticed after having cloned my older HDD 512/512 bytes/sector to a newer Western Digital HDD, which uses the advanced format 512/4096 bytes per sector. I would like to avoid that this sort of partitioning may affect the read/write IO rates. The errors I see are these: marco@linux-turion64:~> sudo fdisk -x Disk /dev/sda: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10SPZX-22Z Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x5bc53d8b Dispositivo Avvio Start Fine Settori Id Tipo Start-C/H/S End-C/H/S Attrs /dev/sda1 * 2048 1026036 1023989 7 HPFS 0/32/33 63/221/19 80 /dev/sda2 1026037 447673612 446647576 7 HPFS 63/221/20 218/100/23 /dev/sda3 447673613 449516792 1843180 27 Hidd 218/100/24 333/32/12 /dev/sda4 449516793 1953523118 1504006326 f W95 333/32/13 769/48/30 /dev/sda5 449516795 617287136 167770342 83 Linu 333/32/15 536/88/33 /dev/sda6 617287138 1918772938 1301485801 83 Linu 536/88/35 654/23/20 /dev/sda7 1918772940 1953521663 34748724 82 Linu 654/23/22 1023/254/63 Partition 2 does not start on physical sector boundary. Partition 3 does not start on physical sector boundary. Partition 4 does not start on physical sector boundary. Partition 5 does not start on physical sector boundary. Partition 6 does not start on physical sector boundary. Partition 7 does not start on physical sector boundary. I have the original data on the older HDD and I would like to get the best suggestion in order to correct this issue. When I say "better", I mean less effort-cost and safe enough to avoid to lost data on the new HDD if possible despite I have the backup on previous disk. If you prefer you can send me the suggestions by private message. Thanks in advance! Best Regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220523 Kernel: 5.17.9-1-default - Cinnamon 5.2.7

2 3

x2go immediately disconnects after connection
by Tristan Miller 01 Jun '22

01 Jun '22

Dear all, I've been using X2Go on a pair of openSUSE Tumbleweed systems. On 2022-05-23 I did a dist-upgrade on both and now I'm no longer able to run a remote application or desktop via X2Go -- the client successfully connects to the server but then immediately disconnects. There's nothing obvious in the client and server logs (even at debug-level verbosity) that explains the immediate disconnects -- I see the client successfully connecting to the server and then immediately disconnecting. (Still, I can provide the logs on request.) Some additional relevant pieces of information: * The problem occurs regardless which remote application or desktop I'm trying to run. I've tried xfce4-terminal, xterm, icewm, and others. * The client has no problem connecting to the Tumbleweed server directly via ssh -X and running remote applications. * The client has no problem connecting to an X2Go server running on a different machine running Leap 15.3. * X2Go itself was not updated in the dist-upgrade. * I've tried upgrading to the latest development versions of x2goserver and x2goclient but this hasn't helped. ( I am thinking that some security-hardening update may be at fault here. I tried temporarily disabling AppArmor on the server but that didn't work around the problem. And it doesn't look like the server's sshd_config file was touched in the dist-upgrade. Can anyone suggest any further troubleshooting steps? If anyone cares to do any testing themselves, my packages for the latest x2goserver, x2goclient, nx-libs, and pinentry-x2go are available at <https://download.opensuse.org/repositories/home:/psych0naut:/x2go/openSUSE_…>. Regards, Tristan -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tristan Miller Free Software developer, ferret herder, logologist https://logological.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

2 3