June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1096096] Leap 15.0 - Lenovo Laptop 320: Hardware problem during startup and shutdown.
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1096096 http://bugzilla.suse.com/show_bug.cgi?id=1096096#c4 --- Comment #4 from Takashi Iwai <tiwai(a)suse.com> --- They were in 4.11 and older, so already included... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1094924] New: partition imported during installation would all be formatted by default
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1094924 Bug ID: 1094924 Summary: partition imported during installation would all be formatted by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have a efi PC with the following partitions: / /boot/efi /home swap Now I decide to install tumbleweed an keep the same partition structure. During the installation process in the Suggested Partition screen I select: Expert Partitioner -> Start with Existing partitions Import Mount Points Import Now I have a layout with the previous partitions. - Partition / would be formatted, that's ok. - Partition swap would be formatted, that's normally ok, but the day that the swap partition format changes that would probably break a dual boot linux installation (the other installation will probably not understand the new format). Better, by default, not to format the swap partition as in 42.3. - Partition /home would be formatted. That's crazy. If I don't pay attention all my data get lost. Absolutely better, by default, not to format any data partition as in 42.3. - Partition /boot/efi would be formatted. If I have e multi boot efi PC, I would not be able to boot any other OS. It is mandatory, by default, not to format the /boot/efi partition as in 42.3. Up to 42.3, in the "Import Mount Points from existing Window" screen there was the option (on by default) Format System Volumes (that means / and /boot). Please put it back and do not set by default to format all the imported partitions. This bug apply to Leap 15.0 as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1095687] Installation Media won't boot with Secure Boot enabled on Asus H87-Pro
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095687 http://bugzilla.suse.com/show_bug.cgi?id=1095687#c6 --- Comment #6 from Gary Ching-Pang Lin <glin(a)suse.com> --- So you actually saw "Welcome to Grub!"? It means that shim already loaded grub2.efi, but grub got stuck for some reason. It's weird that switching Secure Boot could change the behavior. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092000] New: Tumbleweed can't boot after 20180427 update
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1092000 Bug ID: 1092000 Summary: Tumbleweed can't boot after 20180427 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: syafaatkukuh(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 769101 --> http://bugzilla.opensuse.org/attachment.cgi?id=769101&action=edit This message only appears about 1-2 seconds * Hardware: Lenovo ThinkPad X1 Carbon 2015 i7-5600U * OS: openSUSE Tumbleweed * Partition: * EFI (sda1) * swap (sda2, encrypted) * root (sda3, encrypted) * Secure boot off * Story: After running 20180427 update and restart the computer, it showing the message like on the attachment below for 1-2 seconds then computer restart, again and again, just like bootloop. At first, i thought it was EFI problem. After i checked http://mirrors.ustc.edu.cn/opensuse/tumbleweed/iso/Changes.20180427.txt that it was update on shim, probably this was the caused. Through chroot, i tried to reinstall shim and based on https://en.opensuse.org/openSUSE:UEFI, tried to follow "Booting the Machine that supports only one signature with vendor provided Keys" part. But the result was same. I have no idea about this error. Just backup my data and installing 42.3 for a while. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1079320] [Build 20180203] openQA test fails in NM_wpa2_enterprise
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1079320 http://bugzilla.suse.com/show_bug.cgi?id=1079320#c27 Jonathan Kang <sckang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #27 from Jonathan Kang <sckang(a)suse.com> --- RESOLVED FIXED. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1095598] Intel built-in i211 Ethernet Card and Wicked - Non-functional networking
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1095598 Jeffrey Cheung <jcheung(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jcheung(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1096355] New: On upgrade , Inappropriate ioctl for device
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1096355 Bug ID: 1096355 Summary: On upgrade , Inappropriate ioctl for device Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: hdf3(a)comcast.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This is an upgrade from 42.3, not a true install. The major bug is reported at the end: ERROR: failed to lookup root id: Inappropriate ioctl for device I had many problems, so had to employ chroot get the /grub2/device.map etc. set so that grub2-mkconfig would run. This system was running 42.3 so many conditions previously ignored became critical errors in 15.0. I would hope that non critical issues could be posted as notes and ignored so one is not left with a system that will not boot. The output from my grub2-mkconfig command follows. grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found theme: /boot/grub2/themes/openSUSE/theme.txt Found linux image: /boot/vmlinuz-4.12.14-lp150.12.4-default Found initrd image: /boot/initrd-4.12.14-lp150.12.4-default Found linux image: /boot/vmlinuz-4.4.126-48-default Found initrd image: /boot/initrd-4.4.126-48-default Found linux image: /boot/vmlinuz-4.4.79-19-default Found initrd image: /boot/initrd-4.4.79-19-default Found linux image: /boot/vmlinuz-3.16.7-7-desktop Found initrd image: /boot/initrd-3.16.7-7-desktop WARNING: Not using lvmetad after response error. Found Windows 7 on /dev/sda1 Found openSUSE Leap 15.0 on /dev/sdb2 Found openSUSE Leap 42.3 on /dev/sdd2 ERROR: failed to lookup root id: Inappropriate ioctl for device output of hwinfo for the disk is (abbreviated): IDE 500.0: 10600 Disk [Created at block.245] Unique ID: _kuT.BVF64zRbVj6 Parent ID: w7Y8.MOsD+3QQ1xE SysFS ID: /class/block/sdc SysFS BusID: 5:0:0:0 SysFS Device Link: /devices/pci0000:00/0000:00:1f.2/ata6/host5/target5:0:0/5:0:0:0 Hardware Class: disk Model: "Samsung SSD 840" Vendor: "Samsung" Device: "SSD 840" Revision: "2B6Q" Driver: "ahci", "sd" Driver Modules: "ahci", "sd_mod" Device File: /dev/sdc Device Files: /dev/sdc, /dev/disk/by-id/ata-Samsung_SSD_840_EVO_1TB_mSATA_S1KRNEAFC02617H, /dev/disk/by-id/scsi-0ATA_Samsung_SSD_840_S1KRNEAFC02617H, /dev/disk/by-id/scsi-1ATA_Samsung_SSD_840_EVO_1TB_mSATA_S1KRNEAFC02617H, /dev/disk/by-id/scsi-35002538844584d30, /dev/disk/by-id/scsi-SATA_Samsung_SSD_840S1KRNEAFC02617H, /dev/disk/by-id/scsi-SATA_Samsung_SSD_840_S1KRNEAFC02617H, /dev/disk/by-id/wwn-0x5002538844584d30, /dev/disk/by-path/pci-0000:00:1f.2-ata-6, /dev/disk/by-path/pci-0000:00:1f.2-scsi-5:0:0:0 Device Number: block 8:32-8:47 BIOS id: 0x82 Drive status: no medium Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (SATA controller) I do not know what the missing ioctl is or where it would look for it. I hope this is enough data, and not too much:-) Thanks for your help. Don -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084044] Yast2 --Install from Tumbleweed locks up
by bugzilla_noreply＠novell.com 06 Jun '18

06 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1084044 http://bugzilla.suse.com/show_bug.cgi?id=1084044#c9 --- Comment #9 from Ryan Bach <romulasry(a)gmail.com> --- Sure. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 354164] provide/require -32bit modules
by bugzilla_noreply＠novell.com 06 Jun '18

06 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=354164 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:8244:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1072697] VUL-0: CVE-2017-13098: bouncycastle: TLS server vulnerable to Adaptive Chosen Ciphertext attack when using JCE allowing plaintext recovery or MITM attack
by bugzilla_noreply＠novell.com 06 Jun '18

06 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1072697 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:8242:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0