June 2023 - openSUSE Users - openSUSE Mailing Lists

[solved] Bug 1200983 - mouse & keyboard not available after a reboot (needs replug the devices)
by mh＠mike.franken.de 25 Jun '23

25 Jun '23

Hi @all, perhaps this can help others too: For a few months now I had Bug 1200983 "mouse & keyboard not available after a reboot (needs replug the devices)" (https://bugzilla.suse.com/show_bug.cgi? id=1200983) on my Tumblewed installation: I first thought, it only would affect mouse & keyboard in KDE, but after a while I saw, that it also happened in the Linux console. The behaviour was like this: 1. During boot the keyboard was usable as expected - one could chose the kernel to boot, enter the LUKS passphrase and so on. 2. As soon as the system was up, the keyboard lights went off. 3. The next, and only the next keypress in the console was ignored then. 4. After the second keypress the keyboard lights went on and one could use the keyboard again. 5. After a few seconds without keyboard usage the lights were switched off again and everything restarted at no 3. 6. When switching to the sddm login screen, the mouse also was "paralyzed". 7. Unplugging the keyboard and plugging it in again solved this problem. From then on keyboard and mouse worked as expected. In the last few days I found enough time to analyze the problem thoroughly. I installed a second Tumbleweed system. This one didn't show the problem. So I compared /etc, running services and so on. After disabling powertop, mouse and keyboard worked as expected after a reboot. So: The culprit was powertop! I don't understand fully, what was going on there. The pitfall is, that now my fans are running more often, so I suspect the system is using more power, which in turn will cause a lower battery runtime. Bye. Michael.

1 1

Problems with sddm
by Niels Kobschätzki 24 Jun '23

24 Jun '23

Hi, I just migrated from Fedora 38 to OpenSUSE Tumbleweed and rsynced my home except .caches to the OpenSUSE-installation. I had once Plasma installed on Fedora but wasn’t happy with. I installed Tumbleweed with Gnome. Now I wanted to try out Plasma again, installed it via zypper, switched to sddm from gdm and ran into a problem. When I try to log in (Plasma Wayland) as my user sddm hangs after I entered my password. After quite a while I can switch to a tty while sddm seems to be frozen except that the mouse cursor turned up. There is nothing in the journal. I deleted everything in .local/share and .config which might be KD/Plasma-related I can log in through sddm as root and when I switch back to gdm I can log into Plasma (Wayland) as my user, too. Any idea how to debug further or what the problem could be? Best, Niels

6 22

Sendmail broke in OpenSuSE 15.4
by Marc Chamberlin 22 Jun '23

22 Jun '23

Hello OpenSuSE Lister's - I think I have encountered a change on BSD Sendmail's behavior (version 8.15.2-150000.8.9.1) that coincides with upgrading OpenSuSE 15.4. I want to run sendmail on some systems that are running another MTA also (such as Apache James, Axigen) For many many moons of OpenSuSE releases, I accomplish this feat by turning off the running of sendmail in daemon mode. That is accomplished by NOT including the -bd parameter for sendmail when starting the systemd sendmail service. This effectively turns off the ability for sendmail to listen for incoming connection request on port 25. But this configuration did not stop sendmail from sending emails for clients such as clamd, cron, etc., which use sendmail internally to send emails as needed. And it did not cause a conflict of the usage of port 25 between sendmail and another MTA. As of OpenSuSE15.4 the ability of sendmail to send emails, and not receive them is broken. Trying to send an email (via localhost) - such as the following test - echo "Subject: sendmail test from Quasar" | sendmail -v marc(a)marcchamberlin.com results in the following useless and misleading error message - marc(a)marcchamberlin.com... Connecting to [127.0.0.1] port 25 via relay... marc(a)marcchamberlin.com... Deferred: Connection refused by [127.0.0.1] I tried exploring firewalld, routes, dhcpd and other network tools all to no joy. The one thing I have found, that will work and get sendmail to send email messages, is to restore the -bd parameter, which up to 15.4 has never affected sendmail's ability to send emails. But as I already said, I cannot use -bd for systems on which I am running another smtp mail server also. If others are willing to concur that this is a new bug, I will happily submit a bug report. I also need to know where to submit it, I tried using Google and got lots of hits on places where sendmail bug reports had been made. Should I submit a bug report on OpenSuSE's bugzilla and let the maintainers figure out where to forward the bug report? Alternatively, perhaps some kind guru knows of an alternative way to configure BSD Sendmail to send but not receive emails? As always, thoughts and comments are much appreciated! Marc.... -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before!

5 13

[oS-en] Firefox suddenly requests to restart to apply an update.
by Carlos E. R. 19 Jun '23

19 Jun '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Leap 15.5, using 102.11.0esr, on opening any new page, I get a page (see photo on link) saying to restart firefox to apply update. This whould be impossible, updates happened through YaST only. Bug? Have I been hacked? https://paste.opensuse.org/pastes/38980520de1c - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZI9HWxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV1FoAnjwhCy7lxtA1aw4ggeeG HJpfAnSwAJ4p2lpZMUMjZf+LXU8c9wiwZWaVhg== =YvsT -----END PGP SIGNATURE-----

6 11

[oS-EN] 15.5 Upgrade thoughts.
by Carlos E. R. 18 Jun '23

18 Jun '23

Hi, I have upgraded two machines to 15.5, using the DVD image on usb stick, choosing upgrade. On a modern laptop, I noticed that it erased "GRUB_DISTRIBUTOR=" in "/etc/default/grub". This can cause crashes (collisions) on machines with multiboots. On an old desktop (classic BIOS) I noticed two things. It did not recognize the partition to upgrade, maybe because this machine uses a separate /usr partition. I managed to reboot and restart the procedure, and it seems to be working. I'm typing on it. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.5)

8 23

Unable to log in to bugzilla
by Marc Chamberlin 18 Jun '23

18 Jun '23

Hello OpenSuSE list - In trying to solve one problem I encountered yet another problem! (Sigh story of my life!) I have a profile/account on https://bugzilla.opensuse.org/ and when I try to log in I am getting a bizarre error response - > "There is already an account with the login name > marc(a)marcchamberlin.com." Of course there is already an account for me, and I am trying to log in with it! WTF! I cannot find any link that would allow me to report this issue to the maintainers of the bugzilla web site (no feedback link). So I turn to this list hoping some kind guru can help me solve this Catch 22. One other anomaly I observed, when making a change to my profile I got told - "Login to profile is not available for employees yet." Since I am not an employee I simply ignore it, but this message does keep popping up. Thanks as always, in advance, for any help or ideas offered. Marc.. -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before!

5 11

Problem with dhclient
by Marc Chamberlin 18 Jun '23

18 Jun '23

Hi OpenSuSE List, I have encounter an anomaly that from Google searches seems to be specific to OpenSuSE. There has been a couple of discussions dating back to 2014-2016 about this or perhaps something related, just Google for the error message like I did to find them. I dunno if those reports were fixed or not. I am running OpenSuSE15.4 x64 and having some issues with routes (perhaps) on my dhcpd server. When I make changes in the configuration of my dhcpd server, and then try to release and renew a dhcp lease on a client system, using the following commands - dhclient -r -v; dhclient -v, nothing happens/changes. (particularly with routes that I am working on, which are deployed by the dhcpd service.) So what are these error messages from the dhclient-script about and are they serious and the culprit behind what appears to be an apparent failure? Is this the same error as was reported back in 2014-2016? and if so why hasn't it been fixed yet? It appears that there might have been a patch provided but I neither know how or whether it can even be applied to the dhclient-script in OpenSuSE 15.4. Log files were unhelpful and didn't report anything new. Inquiring minds need to know, lol, and as always many thanks for any and all suggestions/help offered, in advance. Marc... Here is the command and the output I got - # dhclient -r -v; dhclient -v Internet Systems Consortium DHCP Client 4.3.6-P1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/00:13:3b:4a:59:8a Sending on LPF/eth0/00:13:3b:4a:59:8a Listening on LPF/eth1/00:13:3b:4a:59:89 Sending on LPF/eth1/00:13:3b:4a:59:89 Listening on LPF/eth2/00:1b:21:a1:21:1c Sending on LPF/eth2/00:1b:21:a1:21:1c Listening on LPF/eth3/40:8d:5c:e3:98:0b Sending on LPF/eth3/40:8d:5c:e3:98:0b Sending on Socket/fallback Internet Systems Consortium DHCP Client 4.3.6-P1 Copyright 2004-2018 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /sbin/dhclient-script: unable to pre-init requested interface eth0 /sbin/dhclient-script: unable to pre-init requested interface eth1 /sbin/dhclient-script: unable to pre-init requested interface eth2 /sbin/dhclient-script: unable to pre-init requested interface eth3 /sbin/dhclient-script: unable to pre-init requested interfaces -- see log messages If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting. -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before!

4 12

Microsoft Secure Boot Bug
by J Leslie Turriff 17 Jun '23

17 Jun '23

How (if at all) will this affect installation of non-Microsoft OSs? From Bruce Schneier's Cryptogram newsletter: Microsoft Secure Boot Bug [2023.05.17] Microsoft is currently patching a zero-day Secure-Boot bug. The BlackLotus bootkit is the first-known real-world malware that can bypass Secure Boot protections, allowing for the execution of malicious code before your PC begins loading Windows and its many security protections. Secure Boot has been enabled by default for over a decade on most Windows PCs sold by companies like Dell, Lenovo, HP, Acer, and others. PCs running Windows 11 must have it enabled to meet the software’s system requirements. Microsoft says that the vulnerability can be exploited by an attacker with either physical access to a system or administrator rights on a system. It can affect physical PCs and virtual machines with Secure Boot enabled. That’s important. This is a nasty vulnerability, but it takes some work to exploit it. The problem with the patch is that it breaks backwards compatibility: “...once the fixes have been enabled, your PC will no longer be able to boot from older bootable media that doesn’t include the fixes.” And: Not wanting to suddenly render any users’ systems unbootable, Microsoft will be rolling the update out in phases over the next few months. The initial version of the patch requires substantial user intervention to enable -- you first need to install May’s security updates, then use a five-step process to manually apply and verify a pair of “revocation files” that update your system’s hidden EFI boot partition and your registry. These will make it so that older, vulnerable versions of the bootloader will no longer be trusted by PCs. A second update will follow in July that won’t enable the patch by default but will make it easier to enable. A third update in “first quarter 2024” will enable the fix by default and render older boot media unbootable on all patched Windows PCs. Microsoft says it is “looking for opportunities to accelerate this schedule,” though it’s unclear what that would entail. So it’ll be almost a year before this is completely fixed. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64)

3 8

Another take on Flatpack and Snap packages
by J Leslie Turriff 16 Jun '23

16 Jun '23

https://www.theregister.com/2023/06/09/will_flatpak_and_snap_replace/ Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64)

3 4

15.5 Vagrant box
by Ansgar Esztermann-Kirchner 14 Jun '23

14 Jun '23

Hello List, there is a bunch of boxes available at https://app.vagrantup.com/opensuse, but 15.5 is not among them. Does anyone know if/when it will be added? Thanks, A. -- Ansgar Esztermann Sysadmin Dep. Theoretical and Computational Biophysics https://www.mpinat.mpg.de/person/11315/3883774

1 0