January 2018 - openSUSE Users - openSUSE Mailing Lists

[opensuse] A nice explanation of how the spectre or meltdown issues work.
by Carlos E. R. 07 Jan '18

07 Jan '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 <https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectr…> This link explains in simple terms how the atack works. Of course, the intention is to say that their machines are not affected and why, but in the road the explanation of the issue is very good. (Please follow up in the opensuse-offtopic(a)opensuse.org mail list) - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlpSHYkACgkQtTMYHG2NR9XgVQCfRCQT66sI7JKdZXyEZDiwebMz cPcAnRLcS1SHHrPYRjlDJLTkiMUuqeXi =BlwK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 8

[opensuse] Leap 42.3 & MATE - Almost unusable due to missing mouse clicks
by Andrei V 07 Jan '18

07 Jan '18

Hi, I have MATE desktop on 42.3 installed from this repository http://download.opensuse.org/repositories/X11:/MATE:/Current/openSUSE_Leap_… Tried on 3 PCs (2 bare metal and 1 virtual appliance under KVM), and on all of them there is a common symptom - missing mouse click on bottom toolbar / start menu. Its impossible to launch anything, ar add launch icon to the desktop (apart from terminal command line of course). Googling didn't help. Anyone have any idea how to fix this ? Thanks in advance. Andrei -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] alien ssh access
by gumb 05 Jan '18

05 Jan '18

ssh newbie question: I only know the very basics of ssh (and next to nothing useful of Linux security). When I access a remote openSUSE machine using a private key previously exchanged, as opposed to a basic password (note: the remote PC has a very 'standard' configuration and its firewall is activated), I usually check the system log in YaST and apply a filter 'ssh' starting from my previous date of access. On this occasion I see something alien in the log. It appears to be just a failed attempt at unauthorized access. There are two entries from two separate dates. Example: kernel │SFW2-INext-ACC-TCP IN=eth0 OUT= MAC={big-long-mac-address} SRC=5.8.18.70 DST=192.168.1.64 LEN=52 TOS=0x02 sshd[4243] |Bad protocol version identification '\003' from 5.8.18.70 port 526 I did a search for this IP address and see this page: https://www.abuseipdb.com/check/5.8.18.70 which has several recent abuse reports. Without getting into complex nerdy affairs, what should my next simple step be? I assume I should only be concerned if I see a line suggesting a new ssh session was opened by somebody other than me? Or is there anything else I should keep a lookout for in future? gumb -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 15

[opensuse] MTU problems
by suse＠a-domani.nl 05 Jan '18

05 Jan '18

Hi all, I noticed that my ISP requires me to reduce my MTU to 1472. As my ethernet devices are used via bridge devices, I wonder if: A) it is enough to lower the MTU on the physical ethernet device on my linux box.. B) also lower the MTU of the related bridge device C) also required to lower the MTU of the other (virtual) devices connected to this bridge? Kind regards, Hans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 16

[opensuse] Moving to MariaDB Galera Cluster
by Carlos Xavier 05 Jan '18

05 Jan '18

Hi. We are running a database on two servers configured as Master-Master bidirectional replication on OpenSUSE Leap 42.3. Now its time to add more hosts to the setup. I don't want to go to a circular redundancy configuration, since one of the hosts will be on another location. The main question is, witch packages do I have to remove/install to be able to configure the servers? I already went to https://software.opensuse.org/search?utf8=%E2%9C%93&q=galera&search_devel=f… But I got confused and didn't realize what do I have to do. Do I need to remove MariaDB and install a brand new package? Please, can someone show me the right packages I have to install? Is there any documentation on how can I achieve this working? Regards, Carlos -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] systemd-modules-load[134]: Failed to find module 'no'
by Felix Miata 05 Jan '18

05 Jan '18

I'm noticing these failures during boot on many TW installations, maybe more than half. Below are from the journals of two installations. In recent days, I've seen these messages on at least 4 of 7 installations. # TW20171230 4.14.8 p5bse systemd-modules-load[134]: Failed to find module 'no' p5bse systemd-modules-load[134]: Inserted module 'scsi_dh_alua' p5bse systemd-modules-load[134]: Inserted module 'scsi_dh_emc' p5bse systemd-modules-load[134]: Inserted module 'scsi_dh_rdac' p5bse systemd-modules-load[134]: Inserted module 'dm_multipath' p5bse systemd-modules-load[134]: Inserted module 'sg' p5bse systemd-modules-load[426]: Failed to find module 'no' p5bse systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE p5bse systemd[1]: systemd-modules-load.service: Unit entered failed state. p5bse systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. p5bse systemd-modules-load[608]: Failed to find module 'no' p5bse systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE p5bse systemd[1]: systemd-modules-load.service: Unit entered failed state. p5bse systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. # TW20171231 4.13.12 & 4.14.9 fi965 systemd-modules-load[144]: Failed to find module 'no' fi965 systemd-modules-load[144]: Inserted module 'scsi_dh_alua' fi965 systemd-modules-load[144]: Inserted module 'scsi_dh_emc' fi965 systemd-modules-load[144]: Inserted module 'scsi_dh_rdac' fi965 systemd-modules-load[144]: Inserted module 'dm_multipath' fi965 systemd-modules-load[144]: Inserted module 'sg' fi965 systemd-modules-load[443]: Failed to find module 'no' fi965 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE fi965 systemd[1]: systemd-modules-load.service: Unit entered failed state. fi965 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. fi965 systemd-modules-load[658]: Failed to find module 'no' fi965 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE fi965 systemd[1]: systemd-modules-load.service: Unit entered failed state. fi965 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. How do I find what causes these? Do other see them too? Is this a problem that needs fixing? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3

[opensuse] why is my LVM-disk busy when shutting down?
by Daniel Bauer 04 Jan '18

04 Jan '18

Hi, hope all of you have started a great year! When I shut down my computer (using the kde button or entering "shutdown -h now", doesn't matter) at the end of all the shutdown messages appears the following: Command failed device-mapper: remove ioctl on diska-disk1sys failed: Device or resource busy Command failed device-mapper: remove ioctl on ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part3 failed: Device or resource busy These messages repeat numerous times and run quickly over the screen (I took a photo to read it...), finally after a quite short while the computer shuts down normally. This is my disk-layout: > daniel@venus:~> lsblk > NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT > sda 8:0 0 1.8T 0 disk > ├─sda1 8:1 0 297M 0 part /boot/efi > ├─sda2 8:2 0 1G 0 part /boot > └─sda3 8:3 0 1.8T 0 part > └─cr_ata-WDC_WD20EARS-00MVWB0_WD-WMAZA2401793-part3 254:0 0 1.8T 0 crypt > ├─diska-disk1sys 254:1 0 200G 0 lvm / > ├─diska-system 254:2 0 4G 0 lvm [SWAP] > └─diska-disk1hme 254:5 0 1.6T 0 lvm /home > sdb 8:16 0 1.8T 0 disk > └─sdb1 8:17 0 1.8T 0 part > └─cr_ata-WDC_WD2002FAEX-007BA0_WD-WCAY01001843-part1 254:3 0 1.8T 0 crypt > └─diskb-disk2 254:4 0 1.8T 0 lvm /home/daniel/disk2 > sr0 11:0 1 1024M 0 rom the cr_ata_... are both encrypted LVM's all logical volumes except swap are formatted with ext4 So something in the root files is "busy", but why? And how can I find out what is busy? (I only shut down my computer after a new kernel update, so it's not often that I see this, but now I thought it's the moment to ask :-) ) Thanks for hints! Daniel -- Daniel Bauer photographer Basel Barcelona https://www.patreon.com/danielbauer http://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

Re: [opensuse] time to pressure Intel for a chip replacement (was Re: Time to look for a kernel update...)
by John Andersen 04 Jan '18

04 Jan '18

On January 3, 2018 2:35:35 PM PST, Jones de Andrade <johannesrs(a)gmail.com> wrote: >On Wed, Jan 3, 2018 at 6:49 PM, John Andersen <jsamyth(a)gmail.com> >wrote: > >> On 01/03/2018 11:31 AM, Christopher Myers wrote: >> > From AMD's perspective, it would definitely be exasperating to have >> > your hardware penalized when you didn't screw stuff up... Surely >> > there's got to be some way to selectively enable the "protections" >> > based off of CPU model, like there is with other features? >> >> It was in a patch that exempted AMD processors submitted by an >> AMD employee that the hint as to the root cause was found. >> >> So the patch, already accepted, will do as you suggest. >> > >Important: at least accordingly to Intel, AMD is also affected: > >https://www.streetinsider.com/Corporate+News/Intel+%28INTC%29+Responds+to+S… Neither Intel, nor your linked article says AMD is affected. Some ARM processors are. But AMD has specificly denied it. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] systemd unit file ignores minidlna default configuration
by Bob Williams 03 Jan '18

03 Jan '18

For some time I have been successfully running a minidlna server which streams music to a Bose Soundtouch device over WiFi. However, it stopped working a few weeks ago, and the SoundTouch device could only find an empty folder. After several re-writes of /etc/minidlna.conf without success, searching for other versions of minidlna.conf in non-default locations, I finally tracked the culprit down to /usr/lib/systemd/system/minidlna.service: [Unit] Description=MiniDLNA UPnP-A/V and DLNA media server After=var-run.mount nss-lookup.target network.target remote-fs.target [Service] Type=forking PIDFile=/var/run/minidlnad.pid ExecStartPre=/usr/sbin/minidlnaconfig EnvironmentFile=-/var/lib/minidlna/rescan.conf ExecStart=/usr/sbin/minidlnad $RESCAN -P /var/run/minidlnad.pid -f /var/lib/minidlna/minidlna.conf [0] [Install] WantedBy=multi-user.target So the unit file was forcing minidlna to use the configuration file in /var/lib/minidlna/minidlna.conf rather than the default /etc/minidlna.conf! /var/lib/minidlna/minidlna.conf pointed to media_dir=/mnt and was recreated at start-up, so even editing the media_dir= line didn't work. Changing line [0] to include "-f /etc/minidlna.conf" got things working again - and just in time for Christmas. ;-) I have no idea how this got changed, but I wonder if anyone else has come across anything similar? Bob -- Bob Williams System: Linux 4.4.103-36-default Distro: openSUSE 42.3 (x86_64) Desktop: KDE Frameworks: 5.32.0, Qt: 5.6.2 and Plasma: 5.8.7 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 8

[opensuse] Why is Leap 42.2 missing /usr/include/sys/random.h?? (and no getrandom in linux/random.h)
by David C. Rankin 03 Jan '18

03 Jan '18

All, getrandom() was added with the 3.17 kernel, yet Leap 42.2 does not contain a prototype in /usr/include/linux/random.h and does not include /usr/include/sys/random.h at all. Anybody know why?? -- 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

5 10