October 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] systemd service unit with instance not working ? (leap 42.3)
by Per Jessen 23 Oct '19

23 Oct '19

I'm sure this is a case of needing another pair of eyes. Mine are getting tired. I have the following service unit: ------------------------ systemctl cat firewall@ipv4 # /etc/systemd/system/firewall@.service [Unit] Description=firewall %i After=network.target [Service] Type=oneshot ExecStart=/usr/local/bin/firewall-%i ExecStop=/usr/local/bin/firewall-%i stop RemainAfterExit=yes [Install] WantedBy=multi-user.target ---------------------------- When I try to start it, it fails: systemd[1]: Starting firewall ipv4... systemd[1094]: firewall(a)ipv4.service: Failed at step EXEC spawning /usr/local/bin/firewall-%i: No such file or directory systemd[1]: firewall(a)ipv4.service: Main process exited, code=exited, status=203/EXEC systemd[1]: Failed to start firewall ipv4. Despite the '/usr/local/bin/firewall-%i: No such file or directory', that script _does_ exist: # ls -lF /usr/local/bin/firewal* -rwxr-xr-x 1 root root 5651 Oct 22 15:08 /usr/local/bin/firewall-ipv4* -rwxr-xr-x 1 root root 2522 May 20 17:41 /usr/local/bin/firewall-ipv6* Remarkably, the exact same works just fine on Leap 15.0. Can anyone help me spot my mistake? Thanks. -- Per Jessen, Zürich (11.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] changes between openssh 6.6p1 (leap42.1) and openssh 7.2p2 (Leap 42.3) ?
by Per Jessen 23 Oct '19

23 Oct '19

I'm moving a customer to Leap42.3 (they require php5 which we don't seem to build for leap151) - they are now unable to login, public key ssh. Failed publickey for 'brian' from 1.2.3.4 port 33188 ssh2: RSA SHA256:snip Is anyone aware of any significant/incompatible changes between 6.6p1 and 7.2p2 ? With 6.6, the message looked quite different: Accepted publickey for brian from 1.2.3.4 port 56047 ssh2: RSA 57:ba:49:2c:3e:42:cf:78:38:a0:74:83:2c:6a:40:9c [MD5] The client is: Client protocol version 2.0; client software version OpenSSH_6.7p1 Ubuntu-5ubuntu1.4 -- Per Jessen, Zürich (11.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Youtube viewing on Chrome based browsers
by Ianseeks 23 Oct '19

23 Oct '19

Hi Is it just me or does Firefox produce better and smoother youtube viewing experience than the Chrome based browsers? I seem to get a lot of image splitting, blanking and shuddering watching youtube videos in Chrome based browsers. Ian -- opensuse:tumbleweed:20191018 Qt: 5.13.1 KDE Frameworks: 5.63.0 - KDE Plasma: 5.17.0 - kwin 5.17.0 kmail2 5.12.2 - akonadiserver 5.12.2 - Kernel: 5.3.6-1-default - xf86-video-nouveau: 1.0.15 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] KDE3 and KDE4/plasma5 in Leap 15.1
by Istvan Gabor 23 Oct '19

23 Oct '19

Hello: I have installed openSUSE Leap 15.1 with KDE3 and it works nicely. Unfortunately there are a few programs (eg digikam) a little bit obsolete for my purposes and I'd prefer to use newer versions, either KDE4 or plasma 5 versions. In openSUSE Leap 42.3 it was possible to install KDE4 programs from a wolfi323 repo. I wonder if it is possible to install KDE4 in Leap 15.1 as well. I am really confused by the terms plasma and KDE frameworks, therefore I don't know what to search for. Plasma 5 would be OK as well but in Leap 15.0 KDE3 and plasma 5 can not coexist. If I remember correctly both KDE3 and plasma 5 use the same .kde dir for their settings. Is there any change regarding this in 15.1? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] looking for portable ssd
by Doug McGarrett 23 Oct '19

23 Oct '19

Saw a Samsung portable 500G ssd, but it spoke about s/w for Windows and Mac. I'd like to have a removable ssd to backup my TW system. Is there some kind of software I need to do this, and if so, where do I find it? What is the simplest software to do the job? I'm running on just one partition (not my choice, but openSuse's). The internal drive is multi-boot with Win 10. (I don't care if Windows is backed up.) All information welcome. Thanx--doug -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 44

[opensuse] smartctl usage & GSmartControl
by Dave Howorth 22 Oct '19

22 Oct '19

Prompted by recent discussions about SSD vs HDD I decided to check out my devices with smartctl. But I'm overwhelmed by the smartctl man page! My main disk - sda - is reported to be fine :) My backup disk - sdb - is not found # smartctl -P show /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x4971:0xce23 (0x000)] Please specify device type with the -d option. Use smartctl -h to get a usage summary So I tried telling it that the disk is SATA and with that it can find it: # smartctl -P show -d sat /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.12.14-lp150.12.7-default] (SUSE RPM) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Drive found in smartmontools Database. Drive identity strings: MODEL: Hitachi HDS721010CLA332 FIRMWARE: JP4OA3EA match smartmontools Drive Database entry: MODEL REGEXP: (Hitachi )?HDS7210((16|25)CLA[36]82|(32|50)CLA[36]62|(64|75|10)CLA[36]3[02]) FIRMWARE REGEXP: .* MODEL FAMILY: Hitachi Deskstar 7K1000.C ATTRIBUTE OPTIONS: None preset; no -v options are required. but how do I get it to actually scan it regularly like my main disk? I installed GSmartControl in the hope it would be simpler to use. But the Help/Help button does nothing, and for my backup disk it says: Drive information: /dev/sdb (scsi), 1.00 TB, HDS721010CLA332 Basic health check: Unknown Model family: Unknown and the checkboxes to Enable SMART and to Enable Offline Data Collection are both greyed out. So how come it doesn't seem to be able to access the same data as smartctl? Does anybody use it, or is it really as useless as it seems? YaST Partitioner can see it without me having to do anything special, why can't smart? Similar questions also apply to an SD card I happen to have plugged in at the moment! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Tumbleweed boot difficulty
by Roger Oberholtzer 22 Oct '19

22 Oct '19

I have done a new Tumbleweed install. All went fine. But booting is a problem. I need to run the original installer + update to get it to boot. Then, after doing the update (basically installing any new packages), it boots in to the OS fine. But on it's own, I get the graphic boot menu. Then a black window that lists the name of the kernel, and the name if the initrd file. Then ... nothing. No complaint. It just waits. No keys can do anything (e.g., an alternative console) When it boots, it is working fine, I can do most everything I have tried. I see that /proc/cmdline says: BOOT_IMAGE=/boot/vmlinuz-5.3.2-1-default root=UUID=02e67b6d-c8b5-4de1-8ac5-96a13174a855 splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet splash=silent resume=/dev/disk/by-id/ata-WDC_WD10EARS-003BB1_WD-WCAV5J249635-part3 quiet mitigations=off The devices and UUID look correct. I'm just curious why the resume= and quite are listed twice. Could that be the problem? I know that the kernel was updated in all of this. The dracut is whatever the kernel packages does. I have not changed anything. I have tried various boot alternatives (rescue, a snapshot, etc). All do the same. This is a new one on me. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Help Reading Serial Device /dev/bus/usb/001/010
by David C. Rankin 22 Oct '19

22 Oct '19

All, I have a small ARM board that I am working with: http://processors.wiki.ti.com/index.php/LAUNCHXL2-RM46 I can build for the board using gcc-arm-none-eabi and flash the firmware with the TI UniFlash software. However I cannot figure out how to connect a serial device to it. The manual says I should be able to: Configure Baud Rate: 19200, Data Bits: 8, Stop Bits: 2 and Parity: None http://processors.wiki.ti.com/index.php/LAUNCHXL2_RM46:_Project_1 When connected there are two /dev/tty devices created: crw-rw-rw- 1 root dialout 166, 0 Oct 12 21:55 /dev/ttyACM0 crw-rw-rw- 1 root dialout 166, 1 Oct 12 21:55 /dev/ttyACM1 These are in some manner related to: /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 and the character device /dev/char/189:9 I have tried minicom through /dev/ttyACM0, without success. I can find the device and query it through: # udevadm test /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 calling: test version 228 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 228 file size: 7007575 bytes header size 80 bytes strings 1743863 bytes nodes 5263632 bytes Load module index <snip> starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10'(out) '0' Process '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' succeeded. MODE 0666 /etc/udev/rules.d/71-ti-permissions.rules:10 handling device node '/dev/bus/usb/001/010', devnum=c189:9, mode=0666, uid=0, gid=0 preserve permissions /dev/bus/usb/001/010, 020666, uid=0, gid=0 preserve already existing symlink '/dev/char/189:9' to '../bus/usb/001/010' created db file '/run/udev/data/c189:9' for '/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1' ACTION=add BUSNUM=001 DEVNAME=/dev/bus/usb/001/010 DEVNUM=010 DEVPATH=/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=XDS110__03.00.00.02__Embed_with_CMSIS-DAP ID_MODEL_ENC=XDS110\x20\x2803.00.00.02\x29\x20Embed\x20with\x20CMSIS-DAP ID_MODEL_ID=bef3 ID_REVISION=0100 ID_SERIAL=Texas_Instruments_XDS110__03.00.00.02__Embed_with_CMSIS-DAP_HLR46000 ID_SERIAL_SHORT=HLR46000 ID_USB_INTERFACES=:020201:0a0000:ff0000:030000: ID_VENDOR=Texas_Instruments ID_VENDOR_ENC=Texas\x20Instruments ID_VENDOR_FROM_DATABASE=Texas Instruments, Inc. ID_VENDOR_ID=0451 MAJOR=189 MINOR=9 PRODUCT=451/bef3/100 SUBSYSTEM=usb TYPE=239/2/1 USEC_INITIALIZED=120561513447 run: '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 9 ef' Unload module index Unloaded link configuration context. This is the correct udev rule for the device, but that is where I am stuck. What I need to do is get a serial console open to it so that when I load an executable that reads/writes to stdin/stdout I can see the output and provide the input. (blinking diodes are the board are nice, but worthless for providing user authentication through) Connecting a serial console seems like a simple process, but I must be missing something stupid simple about it. Minicom can be configured for either /dev/ttyACM0 or /dev/ttyACM1 (and N82 19200) but there is nothing ever output on either (even after loading a program that generates output to stdout) Yes, the flash goes fine and I can load different executables to make the diodes respond in varying ways -- so the fact that the code is loaded and running correctly if verified, but how do I interface with the serial terminal on this thing? Anybody been down this road before? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 9

[opensuse] restoring efi boot / home after failed SSD
by gumb 20 Oct '19

20 Oct '19

I recently suffered a cataclysmic SSD failure. This machine has two SSD drives, the M.2 drive (sdb) holds the root partition (sdb1) and swap, which is all still intact, whilst the SATA drive which failed (sda) held the boot/efi partition in addition to the /home partition, and hence all my personal data. I've installed a new replacement SATA SSD, booted the openSUSE rescue system from a USB stick, changed root to the original oS installation on sdb1 and then, from within yast2, created a new /boot/efi partition (sda1) and /home (sda2) on the new disk. What is the next step to get this to boot? Currently I'm at the error: no such device: /efi/boot/fallback.efi -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] SSH Public Key Authentication Broken By Upgrade [zypper dup]
by Adam Tauno Williams 19 Oct '19

19 Oct '19

After doing a zypper dup to 15.1 all appears to be working great - as expected - except however for SSH public key authentication. GNOME does not prompt for the passphrase and authentication falls back to password mode [assuming the server allows it]. Tips / pointers? __agent is running, correctly linked in environment__ awilliam@beast01:~> ps ax | grep key ... 7245 ? S 0:00 /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh awilliam@beast01:~> ls -l /run/user/1000/keyring/.ssh srw------- 1 awilliam users 0 Oct 17 08:39 /run/user/1000/keyring/.ssh awilliam@beast01:~> env | grep SSH SSH_AUTH_SOCK=/run/user/1000/keyring/ssh SSH_ASKPASS=/usr/lib/ssh/ssh-askpass SSH_AGENT_PID=3113 __OS Relase__ awilliam@beast01:/etc> cat os-release NAME="openSUSE Leap" VERSION="15.1 " ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.1" PRETTY_NAME="openSUSE Leap 15.1" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" __agent knows the keys__ awilliam@beast01:/etc> ssh-add -l 1024 SHA256:Mom8WjkrR5gYjlRXsH4ROtA7HcsvC0UI/2c+BFsEp0U ogo(a)workflow.mormail.com (DSA) 1024 SHA256:xVXJ4TscK0z/lZRf6t6n/9yt3G9sIxy46bmGd2RDCr4 awilliam(a)linux-yu4c.site (DSA) 1024 SHA256:ZNRZeqkdHCI266I72nNCOiwagJ85XLScOkmEtwYIilk awilliam(a)linux-86wr.site (DSA) __entering the passphrase 'works' but is not effective__ awilliam@beast01:/etc> ssh-add Enter passphrase for /home/awilliam/.ssh/id_dsa: Identity added: /home/awilliam/.ssh/id_dsa (/home/awilliam/.ssh/id_dsa) __gcr-ssh-askpass is installed__ awilliam@beast01:~> ls -l /usr/lib/gcr-ssh-askpass -rwxr-xr-x 1 root root 43920 Feb 24 2019 /usr/lib/gcr-ssh-askpass awilliam@beast01:~> rpm -qf /usr/lib/gcr-ssh-askpass gcr-ssh-askpass-3.28.1-lp151.1.1.x86_64 -- Adam Tauno Williams <mailto:awilliam@whitemice.org> GPG D95ED383 OpenGroupware Developer <http://www.opengroupware.us/> -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10