June 2023 - openSUSE Users - openSUSE Mailing Lists

something wrong with these TW repos?
by bent fender 28 Jun '23

28 Jun '23

# zypper dup Retrieving repository 'Packman Essentials Repository' metadata ........[done] Building repository 'Packman Essentials Repository' cache .............[done] Retrieving repository 'Packman Repository' metadata ...................[done] Building repository 'Packman Repository' cache ........................[done] Retrieving repository 'openSUSE-Tumbleweed-Non-Oss' metadata ..........[done] Building repository 'openSUSE-Tumbleweed-Non-Oss' cache ...............[done] Retrieving repository 'openSUSE-Tumbleweed-Oss' metadata ..............[done] Building repository 'openSUSE-Tumbleweed-Oss' cache ...................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Illegal instruction (core dumped)

4 12

Mono and dotnet (which has perhaps gone missing?)
by Roger Oberholtzer 28 Jun '23

28 Jun '23

I have a package (hardware vendor supplied) that requires Mono/dotnet. I have used this in the past with openSUSE. But when installing this package on a different system, I am experiencing difficulties. Most likely because I don't know how the Mono/dotnet stuff is organized in openSUSE packages. When installing the package, it complains: error: Failed dependencies: mono(System.Collections) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.ComponentModel.Primitives) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Console) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Diagnostics.Process) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.IO.FileSystem) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Linq) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Runtime) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Runtime.Extensions) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Text.RegularExpressions) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Threading) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Threading.Thread) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Xml.ReaderWriter) = 4.2.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 mono(System.Xml.XmlSerializer) = 4.1.1.0 is needed by navsolve-cmd-1.2.0-2.x86_64 Ok. Fair enough. So I installed mono-core, which installs lots of stuff. It did not help. Maybe the explicit version number checks are wrong. I converted a DEB to an RPM, which has been working great. But maybe the version stuff that is there is too strict. That's a different topic... I then installed the package with --nodeps. Just to see what's going on. When I try to run the application, I get this: /usr/local/bin/navsolve-cmd: line 3: dotnet: command not found Ok. I seem to recall having to install dotnet. But it does not seem to be available anymore via Yast. If I go the the openSUSE software download page and look for dotnet for any number of openSUSE/SUSE distros, it claims that there are no packages found. It does find them for Centos. And perhaps others- Anyone know where dotnet for openSUSE has scurried off to? -- Roger Oberholtzer

2 2

how/what formatting disks for sale
by Daniel Bauer 27 Jun '23

27 Jun '23

Hi, There are some external 1 and 2TB disks laying around here who got too small for me and I want sell them cheap. Each has an encrypted partition with reiserfs inside. So, I guess, first I'll have to remove the encrypted partition and make a new one with fdisk. Then add a file-system with mkfs. Two questions: - should I use NTFS? - after installing the file system usually the device belongs to root and I first have to change it to "me-user" before I can write on it as a user. I don't know about rights on Win or Mac. Is there anything I should/must do so that a Win or Mac-User can use the disks just switching them in? Thanks Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

8 9

how to auto install downloaded packages using zypper?
by vani jindam 27 Jun '23

27 Jun '23

*To check file conflict: # zypper --dry-run --download-only git * zypper has downloaded package but **not installed** it * which zypper command recognises packages which are downloaded but not installed aka how do i install downloaded packages [ in cache? ] using zypper command? Regards, Jindam

4 5

hardware(?)-problem with new mini pc
by Daniel Bauer 26 Jun '23

26 Jun '23

Hi, I just bought a new intel-I7-mini pc (brand of a Spanish shop pccomoponentes, which doesn't exist in internet, so I don't know about the psysical details). I installed OpenSuse 15.5 which went flawless, but later, during the first update, it suddenly shut down and rebooted. This repeated several times, but the sudden shutdown/reboot occurs after different times in different situations. Because my first thought was that it's a memory problem I booted with memtest86 and let it run for approx. 5 hours (1 full pass plus some more) with no error reported. In one occasion while running OS I got the following system messages: Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.281458] mce: [Hardware Error]: TSC 0 ADDR 7fad98dd9bb7 MISC 7fad98dd9bb7 Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.281462] mce: [Hardware Error]: PROCESSOR 0:806ec TIME 1686379255 SOCKET 0 APIC 0 microcode ec Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.284382] mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 3: be00000000800400 Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.284389] mce: [Hardware Error]: TSC 0 ADDR 7fad98dd9bb7 MISC 7fad98dd9bb7 Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.284393] mce: [Hardware Error]: PROCESSOR 0:806ec TIME 1686379255 SOCKET 0 APIC 2 microcode ec Message from syslogd@localhost at Jun 10 08:41:52 ... kernel:[ 0.281453] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: be00000000800400 that explain to: Hardware event. This is not a software error. CPU 0 BANK 0 TIME 1686379255 Sat Jun 10 08:40:55 2023 MCG status: MCi status: Machine check not valid Corrected error MCA: No Error STATUS 0 MCGSTATUS 0 CPUID Vendor Intel Family 6 Model 142 Step 12 SOCKET 0 APIC 0 microcode ec Hardware event. This is not a software error. CPU 1 BANK 3 MISC 7fad98dd9bb7 ADDR 7fad98dd9bb7 TIME 1686379255 Sat Jun 10 08:40:55 2023 MCG status: MCi status: Uncorrected error Error enabled MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: Internal Timer error STATUS be00000000800400 MCGSTATUS 0 CPUID Vendor Intel Family 6 Model 142 Step 12 SOCKET 0 APIC 2 microcode ec Hardware event. This is not a software error. CPU 0 BANK 4 MISC 0 ADDR 0 MCG status: MCi status: Uncorrected error Error enabled MCi_MISC register valid MCi_ADDR register valid Processor context corrupt MCA: Internal Timer error STATUS be00000000800400 MCGSTATUS 0 The beep is here: https://www.daniel-bauer.com/div/bib.mp4 (begins a 8 seconds, low sound from phone recording, but clear; pushig the power button 8 seconds nothing happens, then come(s) the beep(s), after a second another short beep and then it boots). My questions: - Can anyone decrypt those mce messages? - Is is clear that it is a hardware error or could it be a software thing? Thanks for your hints! Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com

7 36

VirtualBox crashes gnome-shell on TW
by Wolfgang Rosenauer 25 Jun '23

25 Jun '23

Hi, I have two machines running TW. One is running with Xfce and I don't see a single issue with VirtualBox. But the other machine is a pretty new one (Lenovo X1) running Gnome and VirtualBox is pretty much unusable there. When I try to run a Windows VM it crashes. When I try to install the vbox-extensions it crashes. And when I say "it" according to logs it mainly is gnome-shell which is crashing. Jun 24 20:21:49 ox.rosenauer.org gnome-shell[9547]: Clutter:ERROR:../clutter/clutter/clutter-actor.c:5552:clutter_actor_finalize: assertion failed: (priv->grabs == NULL) Jun 24 20:21:49 ox.rosenauer.org gnome-shell[9547]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-actor.c:5552:clutter_actor_finalize: assertion failed: (priv->grabs == NULL) Jun 24 20:21:49 ox.rosenauer.org gnome-shell[9547]: == Stack trace for context 0x56540a7660f0 == VirtualBox is just a black window from then on as well. Anyone else who has seen something like this? Thanks, Wolfgang

2 2

[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