June 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Which kernel use?
by sysek 24 Jun '19

24 Jun '19

Hi, A few days ago I found article about 'Which kernel use in Linux distribution' but I can't find that again, so I just started to thinking, which kernel can I use to not break the system. On kernel.org there's a LTS kernel which version is 4.19.55 or 4.14.129 but in openSUSE Leap 15.1 is 4.12.14 and as I assume the newest modules(?), drivers(?) are included as a backport right? If I'm wrong do not hesitate to correct me. -- Cheers, MM -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] cannot change root while attempting to reinstall grub
by George from the tribe 24 Jun '19

24 Jun '19

I am trying to copy my root partition into another partition in order to boot from that partition. My system has 2 hard drives - an sdd which is /dev/sda, and an hdd, which is /dev/sdb. Here is how they are partitioned: > fdisk -l Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5105ED88-0EA8-4BF5-B7B8-31C56BA1351E Device Start End Sectors Size Type /dev/sda1 2048 52430847 52428800 25G Linux filesystem /dev/sda2 52430848 104859647 52428800 25G Microsoft basic data /dev/sda3 104859648 488396799 383537152 182.9G Microsoft basic data Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: A4BA7F24-83E8-4139-BBE3-76AB94D3CDDC Device Start End Sectors Size Type /dev/sdb1 2048 1026047 1024000 500M EFI System /dev/sdb2 1026048 1288191 262144 128M Microsoft reserved /dev/sdb3 1288192 433004543 431716352 205.9G Microsoft basic data /dev/sdb4 1928595456 1929517055 921600 450M Windows recovery environment /dev/sdb5 1929517056 1951195135 21678080 10.3G Windows recovery environment /dev/sdb6 1951197184 1953523711 2326528 1.1G Windows recovery environment /dev/sdb7 433004544 466558975 33554432 16G Linux swap /dev/sdb8 466558976 518987775 52428800 25G Linux filesystem /dev/sdb9 518987776 1928595455 1409607680 672.2G Linux filesystem Partition table entries are not in disk order. What I want to do is copy the contents of /dev/sda1 to /dev/sdb8, then setup grub to see the operating system at /dev/sdb8, and be able to boot from there. I have already copied /dev/sda1 to /dev/sdb1 using rsync, so now it is just a matter of setting up grub. I have successfully used the following procedure many times in the past, but this time it isn't working. root@tribetrekDellbig:/home/george> mount /dev/sdb8 /mnt root@tribetrekDellbig:/home/george> mount -o bind /proc /mnt/proc/ root@tribetrekDellbig:/home/george> mount -o bind /sys /mnt/sys/ root@tribetrekDellbig:/home/george> mount -o bind /dev /mnt/dev/ root@tribetrekDellbig:/home/george> cd /mnt root@tribetrekDellbig:/mnt> chroot /mnt /bin/bash: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory The plan was after changing root, I was going to re-install grub. I can reinstall grub regardless, but if I change the root first, then it will make the new partition the first partition in the grub list. I also tried to do this using a rescue system, but I get the same error. My rescue system stick is a leap 42.3 stick, so I expect that library was not part of 42.3 and that is the problem there. But trying to change root inside a shell on a fully booted system, where the root partition files are simply copied from one partition to another should not cause this problem. I am running leap 15.0 in this partition that I copied over to /dev/sdb8. I was running tumbleweed on this partition before, but I used a zypper dup to change it to leap 15.0. Any suggestions? -- George Box: TW | Plasma 5 | AMD Phenom IIX4 | 64 | 32GB Laptop #1: 15.0 | Plasma 5 | AMD FX 7TH GEN | 64 | 32GB Laptop #2: 15.0 | Plasma 5 | Core i5 | 64 | 8GB -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Is your clamav 0.101.2 working properly?
by Masaru Nomiya 23 Jun '19

23 Jun '19

Hello, If you have installed clamav 0.101.2 from opensuse's repository, is it working properly? I can't think so. To check this, try; $ ldd /usr/bin/clam* | grep libclamms You will get; libclammspack.so.0 => not found libclammspack.so.0 => not found libclammspack.so.0 => not found libclammspack.so.0 => not found In my case; libclammspack.so.0 => /usr/lib64/libclammspack.so.0 (0x00007fa6ac38f000) libclammspack.so.0 => /usr/lib64/libclammspack.so.0 (0x00007ff5cdbdf000) libclammspack.so.0 => /usr/lib64/libclammspack.so.0 (0x00007f1e55793000) libclammspack.so.0 => /usr/lib64/libclammspack.so.0 (0x00007eff03dad000) Because, I made clamav-0.101.2-1.1.src.rpm by my self with the release of clamav-0.101.2.tar.gz, then compile & installed. Regards, --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computers. Not with Me!" "No..., with money." -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 10

[opensuse] Is my new WD external disk defect?
by Daniel Bauer 22 Jun '19

22 Jun '19

Hi, I just bought a new external disk, but it doesn't show up when plugging it. It also doesn't show up in Yast partitioner. So I unplugged it, plugged it again and typed dmesg This is the output: [ 757.034290] usb 8-2: new SuperSpeed USB device number 6 using xhci_hcd [ 757.056488] usb 8-2: New USB device found, idVendor=1058, idProduct=1230 [ 757.056492] usb 8-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 757.056494] usb 8-2: Product: My Book 1230 [ 757.056497] usb 8-2: Manufacturer: Western Digital [ 757.056499] usb 8-2: SerialNumber: 574343344531373430333935 [ 757.057552] usb-storage 8-2:1.0: USB Mass Storage device detected [ 757.057816] scsi host20: usb-storage 8-2:1.0 [ 758.055354] scsi 20:0:0:0: Direct-Access WD My Book 1230 1065 PQ: 0 ANSI: 6 [ 758.055724] sd 20:0:0:0: Attached scsi generic sg4 type 0 [ 758.057137] scsi 20:0:0:1: Enclosure WD SES Device 1065 PQ: 0 ANSI: 6 [ 758.057704] sd 20:0:0:0: [sdc] Unit Not Ready [ 758.057709] sd 20:0:0:0: [sdc] Sense Key : Hardware Error [current] [ 758.057714] sd 20:0:0:0: [sdc] ASC=0x30 <<vendor>>ASCQ=0x89 [ 758.060536] ses 20:0:0:1: Attached Enclosure device [ 758.060736] ses 20:0:0:1: Attached scsi generic sg5 type 13 [ 758.061684] ses 20:0:0:1: Failed to get diagnostic page 0x1 [ 758.061687] ses 20:0:0:1: Failed to bind enclosure -19 I saw the "Sense Key : Hardware Error [current]" and thought, well, maybe formatting will help. So I typed fdisk -l | grep '^Disk' But all I see are the disks I already know. The new external doesn't appear. Is it defect? Thanks for hints! Daniel -- Daniel Bauer photographer Basel Málaga https://www.patreon.com/danielbauer https://www.daniel-bauer.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] system freeze during boot of new kernel v. 4.4.180-102.1.x86_64
by ken 22 Jun '19

22 Jun '19

The day before yesterday I did a system update, including downloading and installing a new kernel (v. 4.4.180-102.1.x86_64). I didn't reboot however; rather I continued to run the previous kernel (4.4.179-99-default). This may be worth mentioning only because towards the end of the day yesterday my system froze up. That is, I could move the mouse pointer around, but clicking on any window did nothing. This meant that I couldn't switch to any other window, so no way to try to diagnose anything. From gkrellm, however, I did see that both RAM and swap usage were normal, not maxed out, so no runaway processses. But the only way to get out of that frozen system was to power down via the power switch. Turning the laptop back on, I booted into the new kernel. However, it wouldn't boot. It hung even before I was able to log in, when the text messages about the boot processes were still rolling up the screen. Here's what I saw: ... [ OK ] Reached target System Iniitialization. Starting Show Plymouth Boot Screen... Starting dracut Initqueue hook... [ 1.761617] wmi: Mapper loaded [ 8.862476] nouveau 0000:01:00.0: DRM: evicting buffers... [ 8.862400] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle... [ 8.862497] nouveau 0000:01:00.0: DRM: suspending client object trees... [ 8.865333] nouveau 0000:01:00.0: DRM: suspending kernel object trees.. And that's where it hung... for at least fifteen minutes (that's about how long it took me to note by hand all of what I saw onscreen). I had to hard-reboot (again), where I selected the previous (bootable) kernel (4.4.179-99-default). There was no problem booting it and haven't had any problems running it for more than a day-and-a-half. Any explanations and/or recommendations? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] TW : Mouse
by ellanios82 21 Jun '19

21 Jun '19

TW : am using a wireless Microsoft Mouse, with new battery , on xfce: recently, mouse-action jerky & unpredictable. - anyone else seen similar ? .... regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] How many packages?
by James Knott 21 Jun '19

21 Jun '19

I've noticed that when the software updates installs packages, there may be more than one line about successful updates. For example there was just an update and the pop up box had 2 lines, one for 7 packages and one for 6. Why not just say 13 packages successfully updated? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 11

[opensuse] CVE-2019-11477 (/proc/sys/net/ipv4/tcp_sack = 1) ?
by David C. Rankin 21 Jun '19

21 Jun '19

All, Anyone know whether there is a planned fix for: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11477 related: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11478 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11479 Suggested work-around: echo 0 > /proc/sys/net/ipv4/tcp_sack (default is 1) From El Reg: With CVE-2019-11477, a string of TCP SACK responses will cause the Linux kernel to unexpectedly hit an internal data structure limit, triggering a fatal panic. The others affecting Linux will force the system to consume resources, thus slowing it down, as Red Hat explained in its technical summary (https://access.redhat.com/security/vulnerabilities/tcpsack) today. (had to resend from a day or so ago) -- 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 3

[opensuse] Test
by David C. Rankin 21 Jun '19

21 Jun '19

disregard... ISP hosed reverse lookup, messages to list have bounced last 3 days... -- 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

1 0

[opensuse] leap15.1 - difference between libjpeg.8 and libjpeg.62 ?
by Per Jessen 20 Jun '19

20 Jun '19

I'm building some fairly old code which uses libgd, which in turn uses libjpeg. ldd /usr/lib64/libgd.so [snip] libjpeg.so.8 => /usr/lib64/libjpeg.so.8 (0x00007ff6f1c45000) When I link, I get this warning: warning: libjpeg.so.8, needed by /usr/lib64/gcc/x86_64-suse-linux/7/../../../../lib64/libgd.so, may conflict with libjpeg.so.62 This is in fact caused by the Makefile including "-ljpeg', which issuperfluous, but it made me curious - what's the difference between the 8 and the 62 version? Their package descriptions are virtually identical. -- Per Jessen, Zürich (19.5°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 2