October 2023 - openSUSE Users - openSUSE Mailing Lists

Securely formatting BTRFS
by Simon Heimbach 25 Oct '23

25 Oct '23

Hi everybody, does anyone know how to securely format a btrfs-partition[1]? I have an unused SSD with a former root partition that I have to return and I want to make sure that all data is erased before giving it back. Thank you in advance! Simon [1] Without physically destroying the SSD obviously

3 2

Misconfigured dns for mx1.infra.opensuse.org
by Togan Muftuoglu 23 Oct '23

23 Oct '23

Hi, I have tried to mail to the list owner, but it seems that is not read by anyone in a timely manner. Currently the mailing list mailserver has a misconfiguration with the dns settings and as a result my mailserver is rejecting the mails from the list The issue is there is no host mx1.infra.opensuse.org 2023-10-23T15:03:10.411301+02:00 forest postfix/smtpd[29482]: NOQUEUE: reject: RCPT from mx1.opensuse.org[195.135.221.175]: 450 4.7.1 <mx1.infra.opensuse.org>: Helo command rejected: Host not found; from=<SRS0=HSS3=GD=lists.opensuse.org=users-bounces(a)opensuse.org> to=<toganm(a)dinamizm.com> proto=ESMTP helo=<mx1.infra.opensuse.org> So someone with admin capabilities on the opensuse.org should better fix this Thanks Togan

2 1

OS disk cloning
by Roger Oberholtzer 23 Oct '23

23 Oct '23

If, as part of a disaster recovery system, you wanted to make a copy of your openSUSE OS disk, what are the best programs to use? I guess as part of this there is the discussion of what might need to be changed if the image is on another disk (/etc/fstab) for example). How about rescuezilla? -- Roger Oberholtzer

10 39

Backup files deleted by: "Repository 'repo-oss (15.5)' is managed by service"
by Per Inge Oestmoen 22 Oct '23

22 Oct '23

Hello! Yesterday I installed and configured a new machine. This time I chose openSUSE 15.5, which may have been a not so wise choice. - Let us see. - Normally, the first thing I do before applying any update from the repositories is to configure the system so that the downloaded packages are kept, in /var/cache/zypp/packages. From there, I can copy and download them for future installations with no need for a connectivity. This is my normal procedure. However, after having configured the repositories the way I have always done, I got the message for each and everyone of them: "Repository X is managed by service 'Y' Your manual changes might be reset by the next service refresh!" Upon looking into /var/cache/zypp/packages it turned out that there was nothing there - the system had not kept my downloads. I have never asked a "service" to manage the repositories and reset my chosen changes! Why does this suddenly happen? What do I have to do in order to delete these infamous "services" once and for all so that they do not reset my changes - something I absolutely do not want. See the messages below. Thank you for your help! ---- Repository 'repo-oss (15.5)' is managed by service 'openSUSE'. Your manual changes might be reset by the next service refresh! Repository 'repo-non-free (15.5)' is managed by service 'NVIDIA'. Your manual changes might be reset by the next service refresh! Repository 'update-non-oss (15.5)' is managed by service 'openSUSE'. Your manual changes might be reset by the next service refresh! Repository 'repo-oss-source (15.5)' is managed by service 'openSUSE'. Your manual changes might be reset by the next service refresh! Repository 'update-backports (15.5)' is managed by service 'openSUSE'. Your manual changes might be reset by the next service refresh! ---- Per Inge Oestmoen, Norway

7 20

Sound under Tumbletweed
by Wolfgang Mueller 21 Oct '23

21 Oct '23

On Monday last week, I have installed Tumbletweed with KDE Plasma. In the first two days, the sound worked fine, but then it stopped working and a red diagonal stroke appeared across the speaker icon on the panel. When I click on it, a window pops up, entitled "Audio volume" and saying: "No output or input devices found", but not giving me any chance of specifying such a device. Since under Tumbletweed, Yast does not contain any possibility of sound configuration, I don't know what to do for making the two sound cards, or at least one of them, work. Any help is welcome. Thank you in advance and best regards, Wolfgang.

4 11

Xorg failure, I need help
by Marc Chamberlin 18 Oct '23

18 Oct '23

Hi, this is a little above my pay grade to try and solve, so need a kind guru! I am running OpenSuSE Leap 15.4 x64 along with the x11vnc server version 0.9.16 and TigerVNC/vncviewer version 1.10.1 Until relatively recently I have been able to make VNC connections between my systems, but recently one system got sick and no longer allows a vnc session to be created. The Xorg.1.log file is showing a bunch of surprising errors, so my questions are, 1. What happened? and 2. How do I fix this? I am happy to provide any additional info and thanks in advance for your help... Marc... bigbang:/var/log # grep "(EE)" Xorg.1.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [2293287.320] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [2293287.344] (EE) Failed to load module "intel" (module does not exist, 0) [2293287.368] (EE) Screen 0 deleted because of no matching config section. [2293287.556] (EE) modeset(0): drmSetMaster failed: Device or resource busy [2293287.556] (EE) [2293287.556] (EE) AddScreen/ScreenInit failed for driver 0 [2293287.556] (EE) [2293287.556] (EE) [2293287.556] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [2293287.556] (EE) [2293287.556] (EE) Server terminated with error (1). Closing log file. bigbang:/var/log # ll /dev/dri/card0 crw-rw----+ 1 root video 226, 0 Oct 15 22:15 /dev/dri/card0 Information about my system is shown below - lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a] Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005] Kernel driver in use: ahci Kernel modules: ahci 00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1) Kernel driver in use: pcieport 00:1b.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 [8086:a169] (rev f1) Kernel driver in use: pcieport 00:1b.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #20 [8086:a16a] (rev f1) Kernel driver in use: pcieport 00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1) Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 [8086:a112] (rev f1) Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 [8086:a113] (rev f1) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1) Kernel driver in use: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1) Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Z170 Chipset LPC/eSPI Controller [8086:a145] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] 00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:a182] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04) 03:00.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05) Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter [8086:1376] Kernel driver in use: e1000 Kernel modules: e1000 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000] Kernel driver in use: r8169 Kernel modules: r8169 --

3 2

[oS-en] Conflict on update with xfce4-panel-branding (Leap)
by Carlos E. R. 17 Oct '23

17 Oct '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Siince a few days I get this conflich updating Leap 15.5: #### YaST2 conflicts list - generated 2023-10-17 17:35:42 #### the to be installed xfce4-panel-4.18.5-bp155.2.6.1.x86_64 requires 'xfce4-panel-branding = 4.18.5', but this requirement cannot be provided not installable providers: xfce4-panel-branding-upstream-4.18.5-bp155.2.6.1.noarch[repo-backports-update] [ ] Following actions will be done: deinstallation of xfce4-panel-4.18.4-bp155.2.3.1.x86_64 deinstallation of xfce4-panel-lang-4.18.4-bp155.2.3.1.noarch deinstallation of xfce4-panel-profiles-1.0.14-bp155.4.3.1.noarch deinstallation of xfce4-power-manager-plugin-4.18.2-bp155.2.3.1.x86_64 deinstallation of xfce4-pulseaudio-plugin-0.4.8-bp155.2.6.1.x86_64 deinstallation of xfce4-screenshooter-plugin-1.10.4-bp155.2.3.1.x86_64 deinstallation of xfce4-xkb-plugin-0.8.3-bp155.1.9.x86_64 deinstallation of patterns-xfce-xfce_basis-20230212-lp155.1.4.x86_64 deinstallation of xfce4-clipman-plugin-1.6.4-bp155.2.3.1.x86_64 deinstallation of xfce4-xkb-plugin-lang-0.8.3-bp155.1.9.noarch deinstallation of patterns-xfce-xfce_office-20230212-lp155.1.4.x86_64 deinstallation of patterns-xfce-xfce-20230212-lp155.1.4.x86_64 [ ] deinstallation of xfce4-panel-branding-openSUSE-4.18.0+git0.9a2f754-lp155.2.2.1.noarch [ ] do not install patch:openSUSE-2023-299-1.noarch [ ] break xfce4-panel-4.18.5-bp155.2.6.1.x86_64 by ignoring some of its dependencies #### YaST2 conflicts list END ### I am, for now, not installing the patch. I seem to recall a similar conflict this summer, but grepping the mail archive doesn't find it for me. Ideas? - -- Cheers Carlos E. R. (from openSUSE Leap 15.5 at Laicolasse) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZS6q/hwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVmgsAn0G+rRm3mCSOMvrGFt9X 6lWfZKLMAJ9voTw/firCOGA6V3WSUQZHcMftCw== =a1Wv -----END PGP SIGNATURE-----

2 2

error spamming journal files
by Frank McCormick 15 Oct '23

15 Oct '23

Looking through my journal log files today and I noticed this: Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified Oct 14 09:55:52 desktop-tumbleweed bamfdaemon[6594]: Authorization required, but no authorization protocol specified This error goes on for literally hundreds of lines. I checked older boots and found the same thing so I am not sure how long this has been going on. Can someone suggest where I could start looking to resolve this ? Thanks

3 11

glibc version in Leap 15.1
by Roger Oberholtzer 15 Oct '23

15 Oct '23

Leap 15.5 uses glibc 2.31. I have a binary SDK from a LiDAR sensor supplier that seems to have been linked with glibc 2.34. So when I try to link with it on a Leap 15.5 system, I get: ./libscanifc-mt.so: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./libscanifc-mt.so) ./libscanifc-mt.so: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./libscanifc-mt.so) I am trying to see if the supplier has a version of their SDK linked with an older glibc. I hope one that is not older (in their SDK versions) than the one I have for 2.34 (which they claim is built with gcc 11). That one works fine on Tumbleweed. So I caught this when trying to do a build of our software for a different target platform (Leap 15.5). While I wait for that info, I am exploring my options. I know that glibc is a fragile and key component, so mucking about with it is generally to be avoided. Having said that, is it possible to update glibc on Leap 15.5? If so, how obtrusive is that update? As it should provide the earlier glibc interfaces as well, maybe it is rather self-contained? Just the glibc needs to be updated? These glibc things are installed in the Leap 15.5 system: glibc-locale-base-2.31-150300.58.1.x86_64 glibc-locale-2.31-150300.58.1.x86_64 linux-glibc-devel-5.14-150500.12.3.2.x86_64 glibc-2.31-150300.58.1.x86_64 glibc-devel-2.31-150300.58.1.x86_64 -- Roger Oberholtzer

2 2

Leap 15.5 network not fully functional
by Damon Register 14 Oct '23

14 Oct '23

I just installed Leap 15.5 on my home server computer. The install seemed to go ok and the system is up and running, sort of. online updates hang and then finally timeout. Yast package manager won't load. Firefox cannot navigate to opensuse.org but I am able to surf elsewhere and even play a Youtube video. On my Windows PC I am able to navigate to opensuse.org which is how I downloaded the installation media but for reason I don't understand the Leap 15.5 PC just doesn't like opensuse. Any idea why only opensuse is a problem with this PC? I have a bad feeling like that guy from from the movie "Airplane" that my timing is bad. I remember talk about possible demise of Leap but I don't know if that has anything to do with my problem. Damon Register

2 1