September 2021 - openSUSE Users - openSUSE Mailing Lists

replacing RAID drive
by George from the tribe 23 Sep '21

23 Sep '21

So I have had these 2 drives in RAID 1 configuration for 5 separate partitions on each drive. It was a holdover to previous linux versions - one of the partitions was an installation of opensuse 13.2! Well, one of the hard drives failed, putting all 5 RAIDed partitions into degraded status. So I thought, what the heck, these drives are 5 years old, I am just going to replace both hard drives instead of only the one that failed, and at the same time upgrade them from 1TB size to 2TB size since they are so cheap now. The challenge was, one of the RAID partitions was also my root partition. So I bought the 2 new drives, and took out the old failed drive, and started the process. My plan was to put in the new 2TB drive, partition it with 4 of the 5 partitions (I certainly don't need 13.2 anymore), hook them to the RAID arrays, wait until they sync, then reboot to check that it works. Reinstall grub on the new drive, then remove the 2nd old drive (the one that works), and reboot to check that I can boot up on the new drive, now with all 4 partitions running in degraded RAID configuration. Then, once that is verified to work, put in the 2nd new drive, partition it, add the new partitions to the RAID arrays, and then be back up and running. I ran into a bit of a problem on the way, though everything is finally resolved, but it raised a question I hope someone can answer. After I had connected the 1st new drive to the RAID arrays, I did this: - I went to a terminal and installed grub on the 1st new drive, - modified fstab to make sure all the appropriate partitions would be loaded and removed the calls to the older drive, - modified the mdadm.conf file to have it reflect only 4 RAID partitions instead of 5 which I had previously, - ran mkinitrd to get the raid configuration into the intial ramdisk So then I powered off, disconnected the 2nd older drive, and tried to boot up again. Once it got past grub, it ran into a problem and would only boot to emergency mode. In emergency mode, it only had a very small very basic system installed, so I couldn't do much of anything. In order to get my system up and running again, I had to use an installation USB, go to the rescue system, and run through the procedure to reinstall grub, which includes running mkinitrd and the grub configuration. After I did that, my system booted up fine and I was able to get the new RAID partitions fully working on both of my new drives. But I don't understand why I had to use the rescue system? Why wouldn't running mkinitrd from the operating system when the RAID configuration was half on the old drive and half on the new drive be good enough? I think I don't fully understand what I did here. -- George Box: 15.2 | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.2 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: TW | Plasma 5 | Core i7 | 64 | 16GB

1 0

Q: Raspi / TW Fixed Headless Resolution
by Andrei Verovski 22 Sep '21

22 Sep '21

Hi, I installed Tumbleweed on Raspberry Pi 3 and so far was unable to setup fixed headless resolution. Using x0vncserver (time to time I also connect real monitor). With Debian Buster this worked fine (/boot/config.txt) hdmi_edid_file=1 hdmi_edid_filename:0=edid-1920x1080.bin "edid-1920x1080.bin" located on /boot partition. On Tumbleweed I had to add this in order to get signal on monitor: hdmi_force_hotplug=1 config_hdmi_boost=4 Instead of "/boot/config.txt" Tumbleweed uses “/boot/efi/extraconfig.txt” Copied "edid-1920x1080.bin” into both “/boot” and “/boot/efi”. Unfortunately, it doesn’t work. Also tried: hdmi_force_hotplug=1 hdmi_group=2 hdmi_mode=82 No success either. Anyone know how to to fix this? Thanks in advance. Andrei

1 1

How does one contact an OBS package maintainer?
by J Leslie Turriff 20 Sep '21

20 Sep '21

I found a package for a program I want to use in | obs://build.opensuse.org/editors but I want to contact the maintainer to improve its usability. Using RPM -qi, I get the following: | ● rpm -q -i THE-3.3~RC7 | Name : THE | Version : 3.3~RC7 | Release : lp153.22.57 | Architecture: x86_64 | Install Date: Sat Sep 18 16:53:31 2021 | Group : Unspecified | Size : 1273234 | License : GFDL-1.1-only AND GPL-2.0-or-later AND SUSE-Freeware | Signature : DSA/SHA1, Thu Sep 9 08:44:07 2021, Key ID fd45d89e24f1ba50 | Source RPM : THE-3.3~RC7-lp153.22.57.src.rpm | Build Date : Thu Sep 9 08:43:37 2021 | Build Host : lamb53 | Relocations : (not relocatable) | Vendor : obs://build.opensuse.org/editors | URL : http://hessling-editor.sourceforge.net/ | Summary : The Hessling Editor (z/VM-CMS xedit clone) | Description : | THE is a text editor that uses both command line commands and key bindings | to operate. It is intended to be similar to the z/VM-CMS system editor, | XEDIT, and to Mansfield Software's, KEDIT | Distribution: editors / openSUSE_Leap_15.3 | @16:54:51,root@pinto rc=0 There seems not to be any contact information here (unless it is Build Host?). How can I get in contact with a real person? Leslie -- Distribution: openSUSE Leap 15.3 x86_64

3 4

TW - i2c permissions for normal users?
by Michael Hamilton 20 Sep '21

20 Sep '21

My i2c devices /dev/i2c-* are all set to 0660, yet non-root users logged into the desktop appear to have access. How is this achieved? Background: During a covid-19 lockdown I wrote vdu_controls, a GUI front end to ddcutil that I use to adjust the backlights on my external monitors: Ddcutil uses VESA DDC/MCCS over i2c to interact with external monitors. Details here: https://forums.opensuse.org/showthread.php/559401-Desktop-control-of-extern… https://www.ddcutil.com/ I recently had an enquiry from someone attempting to use vdu_controls on a non-SUSE distro. Clearly their problem is lack of permissions to /dev/i2c-* On other distributions the permissions seem to be granted by an entry in /etc/udev/rules.d such as KERNEL=="i2c-[0-9]*", MODE="0666" ( https://www.ddcutil.com/i2c_permissions/ ). I can't find where anything similar is set in Tumbleweed. But ddcutil is working fine, so how it a normal user getting access to /dev/i2c-*? I suspect it's due to an apparmor rule, but I can't find it. Puzzled.

7 10

EROFS within CFEngine
by Ansgar Esztermann-Kirchner 16 Sep '21

16 Sep '21

Hello List, with one of the recent updates, CFEngine starts getting EROFS whenever it tries to write a file. Since writing works just fine from a shell, I assume this is the result of some security measure that isn't properly configured. Does anyone have an idea where to look? Thanks, A. -- Ansgar Esztermann Sysadmin Dep. Theoretical and Computational Biophysics http://www.mpibpc.mpg.de/grubmueller/esztermann

2 3

Re: no ip address
by Carlos E. R. 16 Sep '21

16 Sep '21

On 12/09/2021 00.40, Douglas McGarrett wrote: > On 9/12/2021 12:08 AM, Carlos E. R. wrote: >> On 11/09/2021 22.14, Douglas McGarrett wrote: >> To find a networked hp printer, you probably want to do: >> >> nmap -p 9100 -n 192.168.1.* > > ran that in Windows, but got no answers: > > C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.1.* > Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 20:57 GMT Summer Time > Nmap done: 256 IP addresses (0 hosts up) scanned in 208.53 seconds > > Then tried with the third entry set to 0 and got this: > > C:\Users\Douglas McGarrett>nmap -p 9100 -n 192.168.0.* > Starting Nmap 7.92 ( https://nmap.org ) at 2021-09-11 23:34 GMT Summer Time > Nmap scan report for 192.168.0.1 > Host is up (0.0029s latency). > > PORT STATE SERVICE > 9100/tcp closed jetdirect > MAC Address: 1C:AF:F7:DD:AE:FF (D-Link International) That's the router. > Nmap scan report for 192.168.0.102 > Host is up (0.0020s latency). > > PORT STATE SERVICE > 9100/tcp filtered jetdirect > MAC Address: F0:4D:A2:0F:81:CF (Dell) > > Nmap scan report for 192.168.0.103 > Host is up (0.0029s latency). > > PORT STATE SERVICE > 9100/tcp open jetdirect > MAC Address: 48:0F:CF:C3:33:B7 (Hewlett Packard) The HP printer, probably. > Nmap scan report for 192.168.0.104 > Host is up (0.0023s latency). > > PORT STATE SERVICE > 9100/tcp closed jetdirect > MAC Address: 00:26:B9:D4:42:2D (Dell) > > Nmap scan report for 192.168.0.100 > Host is up (0.00s latency). > > I am not familiar with the value of the third number in the ips. I seem > to remember that 5 or 6 years ago, all my ips had a 1 in the third > position; now they all seem to want a 0. Well, your router changed, didn't it? Then the numbers can change, 0 and 1 are typical, but it could be 132, or 83, or 200, for instance. > > Anyway, not discovering the Epson printer ip, if any. Well, I told you the trick for HPs, not Epson. I don't know what port the Epson uses. Google "what port uses an epson printer" <https://epson.com/faq/SPT_C11CD16201~faq-0000525-shared?faq_cat=faq-8796127…> ok, try: nmap -p 3289,515,9100,631 -n 192.168.0.* -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))

8 34

Problem with software raid and Tumbleweed
by Markus Egg 15 Sep '21

15 Sep '21

Hello, I got Tumbleweed Snapshot20210115 and wanted to install it on a rather old machine with a software raid1 (UEFI raid). On this raid some Windows 10 is already existing. The installer of Tumbleweed Snapshot20210115 does not recognize this software raid1. It only shows single harddiscs and no raid volume. An older snapshot 20190704 is able to see that software raid1 but I cannot do any zypper dup with that one (this version was running previously before some hardware crash). Any help for that - either a snapshot which can handle software raid1 or some way to set zypper dup running again with the older snapshot? BR and thanks in advance Markus

14 46

faulty patch? leap 15.3, The following package update will NOT be installed: yast2-theme
by cagsm 15 Sep '21

15 Sep '21

hello, sudo zypper up Loading repository data... Reading installed packages... The following package update will NOT be installed: yast2-theme Nothing to do. sudo zypper lp Loading repository data... Reading installed packages... Repository | Name | Category | Severity | Interactive | Status | Since | Summary -------------------------------------------------------------+-----------------------------+-------------+----------+-------------+--------+-------+---------------------------------- - Update repository with updates from SUSE Linux Enterprise 15 | openSUSE-SLE-15.3-2021-3033 | recommended | low | --- | needed | - | Recommended update for yast2-them e Found 1 applicable patch: 1 patch needed (0 security patches) sudo zypper patch [sudo] password for root: Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the installed yast2-theme-oxygen-4.3.8-lp153.1.1.noarch requires 'yast2-branding = 4.3.8', but this requirement cannot be provided Solution 1: Following actions will be done: deinstallation of yast2-theme-oxygen-4.3.8-lp153.1.1.noarch deinstallation of yast2-theme-breeze-4.3.8-lp153.1.1.noarch deinstallation of patterns-kde-kde_yast-20181130-lp153.2.8.noarch Solution 2: do not install patch:openSUSE-SLE-15.3-2021-3033-1.noarch Solution 3: break yast2-theme-oxygen-4.3.8-lp153.1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): ty.

3 2

Sluggish Seamonkey
by James Knott 13 Sep '21

13 Sep '21

I use Seamonkey for email and I've noticed it's sometimes very sluggish when I press a key or move the mouse. It someties takes several seconds to respond. If I kill & restart it, it works OK for a while. Other apps don't seem to have the problem. Anyone else seen this? Running on Leap 15.3 & KDE tnx jk

6 18

Q: How to Increase Font Size in YaST
by Andrei Verovski 13 Sep '21

13 Sep '21

Hi, I have 4k 32" display and would like to increase font size in YaST, because all letters are too small. I changed font size for root with: kdesu kcmshell5 kcm_fonts Unfortunately, nothing changed in YaST. How to fix this? Thanks in advance. Andrei

7 12