September 2022 - openSUSE Support - openSUSE Mailing Lists

checksum fails for downloaded ISO
by Axel Braun 16 Sep '22

16 Sep '22

Hi, I was notified about an issue when trying to verify the downloaded ISO image: In the checksum file there is a different filename (although the checksum itself is correct): openSUSE-Leap-15.4-DVD-x86_64-Media.iso The downloaded file is: https://ftp.gwdg.de/pub/opensuse/distribution/leap/15.4/iso/openSUSE-Leap-1… This is unconvenient up to confusing for a user. Does anyone know what the reason is and how we can prevent this for the future? Cheers Axel

11 32

Installing new GTK Theme changes DE aspect just partially
by Marco Calistri 16 Sep '22

16 Sep '22

Hello, I have a doubt to clarify regarding the window aspect after installing a new GTK DE theme, in fact the theme seems applied only partially to the desktop windows. The main window and settings get changed by new theme's style, while some apps as for example Thunderbird, Firefox, Xfce4-terminal, and several others, are not. What this behavior depends by? Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20220912 Kernel: 5.19.8-1-default - XFCE: (4.16.0)

1 1

$releasever usage; https://en.opensuse.org/SDB:System_upgrade
by Felix Miata 14 Sep '22

14 Sep '22

I wish to change the wiki page referenced by $SUBJECT, as follows: ... ''Solution'' - follow repo URL but one level up from "openSUSE_Leap_15.3" and check available targets. If "15.4" is there just manually correct URL.}}[/existing] [proposed] {{Info|Use of $releasever in repo files is not mandatory. The literal version number is exclusively employed in all 60+ of my Leap 15.3 & newer installations, just as in previous Leap releases. This obviates need for --releasever in zypper operations, and shrinks repo and log file sizes. Indeed it is inconstent with use of --releasever, meaning that if such use is wished, repo files must contain $releasever rather than literal version. F.M.}} [/proposed] [existing] ====3. Refresh with the new repos==== ... I'm having no luck locating documentation about use of $releasever in /etc/zypp/repos.d/*.repo. # man *.repo No manual entry for *.repo # man .repo No manual entry for .repo # man repo No manual entry for repo # man zypper <no reference> # man repos.d No manual entry for repos.d # man repos.d/ man: repos.d/: No such file or directory No manual entry for repos.d/ # man repos.d/* man: can't chdir to repos.d: No such file or directory # man /etc/zypp/repos.d/* man: can't chdir to /etc/zypp/repos.d/BaseSystem.repoD-/etc/zypp/repos.d: No such file or directory ... man: can't chdir to /etc/zypp/repos.d/X11Utilities.repoD-/etc/zypp/repos.d: No such file or directory Where's the official documentation for the structure of repo files? I can't knowingly put error on a wiki page. :p -- 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

2 2

Security Notice (from mail.com): Deactivation of TLS 1.0, TLS 1.1 and unencrypted access
by J Leslie Turriff 14 Sep '22

14 Sep '22

I received this notice from my email provider, and the maintainer of my email client (Trinity Desktop) tells me that the version of TLS that it uses depends on the version of SSL that is installed in my OS. I checked with zypper, and what is currently installed is | libopenssl1_1-1.1.1l-150400.7.7.1.x86_64 | openssl-1_1-1.1.1l-150400.7.7.1.x86_64 What he said might not be completely accurate; I see that I see also that | libgnutls30 which contains | libgnutls.so.30.31.0 is also installed, which makes me wonder why my mail client is still using TLS 1? Do I need to install | libopenssl3-3.0.1-150400.4.7.1.x86_64 | openssl-3-3.0.1-150400.4.7.1.x86_64 to make the client use TLS 3? Leslie ---------- Forwarded Message ---------- Subject: Security Notice: Deactivation of TLS 1.0, TLS 1.1 and unencrypted access Date: 2022-09-12, 10:44:38 From: "mail.com service" <service(a)corp.mail.com> To: Leslie Turriff <jlturriff(a)mail.com> Deactivation of TLS 1.0, TLS 1.1 and unencrypted access ------------------------------------------------------------------- Dear Mr. Turriff, We are contacting you because one or more of your devices or programs uses the TLS 1.0 and/or TLS 1.1 encryption protocols to connect to our mail.com email servers, or is using an unencrypted connection. This involves either access via SMTP (sending emails) or retrieval via POP3/IMAP (receiving emails). Unfortunately, the TLS 1.0 and TLS 1.1 encryption protocols are outdated and no longer meet current security standards. To protect your email communications, soon we will no longer allow access to our mail.com servers with these outdated protocols. Unencrypted access will also no longer be possible. What does this mean for you? After the protocols have been deactivated, the transfer of emails between your affected device or program and our mail.com servers will no longer work; i.e. no emails will be transmitted to or from your mail.com email account using TLS 1.0 and TLS 1.1. Furthermore, unencrypted SMTP/IMAP/POP3 connections will no longer function. In other words, as of Oct 5, 2022, it will only be possible to connect if TLS 1.2 or TLS 1.3 encryption is in place. The following devices or programs may be affected: - Third-party email programs such as Outlook, Thunderbird or pre-installed apps in which you have set up your mail.com email account. - Email accounts of other providers which you have linked to your mail.com email account. - Webcams, printers and/or routers that send emails from your mail.com email account. If the above apply to you, please take a moment to check your POP3 and/or IMAP server settings and make sure that you have enabled an encrypted connection. Need help enabling encryption? Please see our Help pages: For more information on POP3, please visit: https://support.mail.com/pop-imap/pop3/index.html For more information on IMAP, please visit: https://support.mail.com/pop-imap/imap/index.html Please rest assured that you can continue to access your emails at all times by logging in to your account at https://www.mail.com or using the mail.com Mail App, which are protected by the highest security standards. ------------------------------------------------------------------ We recommend that you only use newer devices and programs that support the latest TLS 1.2 or 1.3 encryption protocols and transfer your emails securely. In addition, please remember that it is important to install security updates regularly. ------------------------------------------------------------------ Thank you for your understanding! Best regards, Your mail.com Customer Management Team ------------------------------------------------------- -- 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

3 2

Fwd: Fwd: checksum fails for downloaded ISO
by Luna Jernberg 12 Sep '22

12 Sep '22

---------- Forwarded message ---------- From: Michal Suchánek <msuchanek(a)suse.de> Date: Mon, 12 Sep 2022 17:06:07 +0200 Subject: Re: Fwd: checksum fails for downloaded ISO To: Luna Jernberg <droidbittin(a)gmail.com> Cc: factory <factory(a)lists.opensuse.org> Hello, On Mon, Sep 12, 2022 at 04:56:11PM +0200, Luna Jernberg wrote: > ---------- Forwarded message ---------- > From: Axel Braun <docb(a)opensuse.org> > Date: Mon, 12 Sep 2022 16:52:33 +0200 > Subject: checksum fails for downloaded ISO > To: support(a)lists.opensuse.org > > Hi, > > I was notified about an issue when trying to verify the downloaded ISO image: > > In the checksum file there is a different filename (although the checksum > itself is correct): openSUSE-Leap-15.4-DVD-x86_64-Media.iso > > The downloaded file is: > https://ftp.gwdg.de/pub/opensuse/distribution/leap/15.4/iso/openSUSE-Leap-1… > > This is unconvenient up to confusing for a user. > > Does anyone know what the reason is and how we can prevent this for the > future? AFAIK this is a long-standing problem. The files can be downloaded under two names - one with build number, one without. The checksum file only supports one filename for the checksum so it works only for one filename. When the download link points to the filename specified in the checksum file the checksum can be verified easily. Thanks Michal

1 0

[oS-support] Stale systemd service
by Carlos E. R. 11 Sep '22

11 Sep '22

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On a terminal, as root: Telcontar:~ # systemctl status syslog[TAB][TAB] syslog-ng.service syslog.service syslog.socket syslogd.service Telcontar:~ # systemctl status syslog-ng.service Unit syslog-ng.service could not be found. Telcontar:~ # The autocompletion suggests there is a syslog-ng.service, but it does not exist. Telcontar:~ # time updatedb && locate syslog-ng.service real 1m23.533s user 0m0.631s sys 0m2.029s Telcontar:~ # I only found some old configuration directory, "/etc/syslog-ng/", which I have deleted. Similarly: Telcontar:~ # systemctl status syslogd.service Unit syslogd.service could not be found. Telcontar:~ # Telcontar:~ # locate syslogd.service Telcontar:~ # How can I remove those two ghost entries? - -- Cheers Carlos E. R. (from 15.3 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYx5G2Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVeEgAoIR2806rHQGmWtwiAe5Z UocGlg2NAKCQ0m7Pt9BtW45KxGlXI8ZytTxPeQ== =oro6 -----END PGP SIGNATURE-----

1 0

Tumbleweed: how to recover from a botched zypper dup
by Achim Gratz 11 Sep '22

11 Sep '22

I have an old AthlonXP system that I decomissioned three years ago. It turned out later that just an SATA cable needed replacement. Today I tried to update to the latest Tumbleweed using zypper dup, which initially went well (if slowly), but then it hit the installation of filesystem, complained about missing lua triggers and admonished me that I would need a rescue system. Nothing in /usr/bin works anymore, although the (old) kernel boots until the first time it needs a shell for something. I do have a rescue system on USB from that time (actually a net install for Tumbleweed that I used to install the replacement system with), but it runs into trouble: the available shell prompt does not seem to offer a chroot command nor zypper and clicking past the language prompt will blink caps and scroll lock on the keyboard for about a minute and then reboots (perhaps it tried to mount the botched filesystem?). I'm not even sure a chroot would work since the filesystem isn't set up… Preferrably I could somehow use zypper (or rpm) to use the already downloaded package and target the failed installation (with --root /mnt or something like that). Is there a way to do that? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

6 17

Thunderbird and Firefox refuse to open existing profile after upgrade 15.2->15.3
by Jogchum Reitsma 10 Sep '22

10 Sep '22

Hi, Yesterday I upgraded my sister's system from 15.2 to 15.3 After that, both Thunderbird and Firefox refuse to open te existing profiles. Gives the message "You are starting with an old version of <Thunderbird | Frirefox>". Which is an odd messages, because one would expect TB and FF to be newer, not older, after the upgrade... Anyone an idea how to solve this? regards, Jogchum Reitsma

8 10

Re: Leap 15.4 error gtk3-immodule-amharic-3.24.34-150400.3.3.1.x86_64 requires 'gtk3 = 3.24.34', but this requirement cannot be provided
by Larry Len Rainey 09 Sep '22

09 Sep '22

1 0

Update error--redux
by Mark Neidorff 08 Sep '22

08 Sep '22

Running Leap 15.4--fresh install (not from an upgrade) with KDE desktop. Day before yesterday, I got a "software update notice" for 13 updates". Looked them over, and said OK. Upon starting the update I got an error: "the installed gtk3-branding-openSUSE-15.0-lp154.1.9.noarch requires 'libgtk-3-0 = 3.24.31', but this requirement cannot be provided ". It was late, so I put it off. Then, I read the thread about problems with these updates...and that they problems were being worked on....so I didn't worry. Today, I got a "software update notice" again but this time for 21 updates. I thought to myself that I'm glad that they fixed the problems, but the update errored out again with the same message: the installed gtk3-branding-openSUSE-15.0-lp154.1.9.noarch requires 'libgtk-3-0 = 3.24.31', but this requirement cannot be provided. If I deselect the offending package, and restart the update, it does not happen. Is tere a way to work around this...or do I wait? Thank you, Mark -- I used to be indecisive. Now, I'm not sure.

2 2