March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1080177] New: Kernel 4.15.* doesn't bot any more on a Lenovo L450 i5-5200U
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1080177 Bug ID: 1080177 Summary: Kernel 4.15.* doesn't bot any more on a Lenovo L450 i5-5200U Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: joop.boonen(a)boonen.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Lenovo L450 doesn't boot any more with kernel 4.15.* . The system switches the monitor off and doesn't ask the encryption password. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1078290] Unexpected yast behavior when opening conflicting modules in parallel
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1078290 http://bugzilla.suse.com/show_bug.cgi?id=1078290#c3 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(lslezak(a)suse.com) | --- Comment #3 from Ladislav Slezák <lslezak(a)suse.com> --- I have tested this scenario in Leap 15.0 Beta and there is no error popup displayed. Works fine for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1081022] New: VFAT mount option "iocharset=utf8" breaks filename case sensitivity
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1081022 Bug ID: 1081022 Summary: VFAT mount option "iocharset=utf8" breaks filename case sensitivity Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: shundhammer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 760171 --> http://bugzilla.opensuse.org/attachment.cgi?id=760171&action=edit Sample shell session (layout not broken by Bugzilla) I found this while investigating what mount options to use for bug #1080731: When a VFAT filesystem is mounted with option "iocharset=utf8", case sensitivity in file/directory names changes its behaviour in weird ways: "mkdir -p" can fail with EEXIST ("mkdir: cannot create directory ‘/mnt/efi’: File exists") which according to the mkdir man page should never happen. Using mount option "utf8" instead which should be the same according to the "mount" man page changes the behaviour to normal. For one thing, "mkdir -p" should never fail with EEXIST. But that's a matter of that tool which might do the check if a directory already exists the wrong way. That's not what this bug is all about. The weird behaviour is that this check behaves inconsistently depending on the mount options used: "iocharset=utf8" should not change the way at all that a purely ASCII file/directory name is treated. There are no non-ASCII characters involved at all. And there appears to be a difference if a VFAT "long name" exists or not: If there is only a "short name" (the old MS-DOS 8+3 filename), the bug appears. If there is also a "long name", everything works fine. In addition to that, the promise that mount option "utf8" is equivalent to "iocharset=utf8" is broken: Obviously, they behave differently. Sample shell session (also attached): [root @ morgul] ~ # uname -a Linux morgul 4.14.9-1-default #1 SMP PREEMPT Mon Dec 25 15:42:48 UTC 2017 (9423ca2) x86_64 x86_64 x86_64 GNU/Linux # # Using iocharset=utf8 # # FAIL # [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o iocharset=utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o iocharset=utf8 /dev/sdb1 /mnt [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # umount /dev/sdb1 # # Using default mount options (i.e. implicitly iocharset=iso8859-1) # # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # # Using iocharset=iso8859-15 # # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o iocharset=iso8859-15 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-15,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o iocharset=iso8859-15 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-15,shortname=mixed,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # # Using utf8 (which should be equivalent to iocharset=utf8) # # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # Using utf8 and iocharset=utf8 combined # # FAIL # [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o utf8,iocharset=utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # umount /dev/sdb1 # OK [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o utf8,iocharset=utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 # FAIL [root @ morgul] ~ # mkfs.vfat /dev/sdb1 mkfs.fat 4.1 (2017-01-24) [root @ morgul] ~ # mount -t vfat -o iocharset=utf8,utf8 /dev/sdb1 /mnt [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/EFI/boot [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # mkdir -p /mnt/efi/boot mkdir: cannot create directory ‘/mnt/efi’: File exists [root @ morgul] ~ # grep sdb /proc/mounts /dev/sdb1 /mnt vfat rw,relatime,fmask=0002,dmask=0002,allow_utime=0020,codepage=437,iocharset=utf8,shortname=mixed,utf8,errors=remount-ro 0 0 [root @ morgul] ~ # umount /dev/sdb1 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1082704] compiling nvidia kernel modules uses wrong kernel tree?
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1082704 http://bugzilla.suse.com/show_bug.cgi?id=1082704#c20 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #20 from Stefan Dirsch <sndirsch(a)suse.com> --- Eventually I was able to test the changes. Looks good so far. Changes will be for the next driver update. Closing as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1065058] Incorrect console keyboard layout loaded at boot
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1065058 http://bugzilla.suse.com/show_bug.cgi?id=1065058#c3 --- Comment #3 from Daniel Molkentin <daniel.molkentin(a)suse.com> --- Patch accepted and part of the devel repo at https://build.opensuse.org/package/show/home:dmolkentin:dracut:devel:git/dr…. Merge to staging, Factory and backports will happen next week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1082033] X11:XOrg/xdm firewall configuration changes
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1082033 http://bugzilla.opensuse.org/show_bug.cgi?id=1082033#c7 --- Comment #7 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Stefan Dirsch from comment #6) > Currently the content is: > > <?xml version="1.0" encoding="utf-8"?> > <service> > <short>Legacy Xserver Remote Access</short> > <description>TCP/UDP ports needed for legacy remote access to Xserver. > Needs more configuration settings in display manager, e.g. > DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN in /etc/sysconfig/displaymanager > for xdm. </description> > <port protocol="tcp" port="6000-6063"/> > <port protocol="udp" port="6000-6063"/> > </service> > > Is this still considered wrong? Do I really need one line for each port? That looks good - I only checked what is in current Tumbleweed; I just see there was one more submission for xdm: https://build.opensuse.org/request/show/580332 Which is in the currently building/testing snapshot. so that should be fine; Sorry for not realizing there was one more thing on the way out already -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1054473] system fails to recover from dracut emergency shell with "Transaction is destructive"
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1054473 http://bugzilla.suse.com/show_bug.cgi?id=1054473#c26 --- Comment #26 from Daniel Molkentin <daniel.molkentin(a)suse.com> --- Thanks Martin. I cherry-picked this into the dracut devel repo: https://build.opensuse.org/package/show/home:dmolkentin:dracut:devel:git/dr…. Will transition into staging repo early next week. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1082033] X11:XOrg/xdm firewall configuration changes
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1082033 http://bugzilla.opensuse.org/show_bug.cgi?id=1082033#c6 --- Comment #6 from Stefan Dirsch <sndirsch(a)suse.com> --- Currently the content is: <?xml version="1.0" encoding="utf-8"?> <service> <short>Legacy Xserver Remote Access</short> <description>TCP/UDP ports needed for legacy remote access to Xserver. Needs more configuration settings in display manager, e.g. DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN in /etc/sysconfig/displaymanager for xdm. </description> <port protocol="tcp" port="6000-6063"/> <port protocol="udp" port="6000-6063"/> </service> Is this still considered wrong? Do I really need one line for each port? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1080305] Xorg crashes when Yast tries to configure VNC
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1080305 http://bugzilla.suse.com/show_bug.cgi?id=1080305#c9 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |KDE Workspace (Plasma) Assignee|yast-internal(a)suse.de |opensuse-kde-bugs@opensuse. | |org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #9 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Raphael Groner from comment #6) > > Which display manager / desktop environment do you use? > sddm So reassigning to KDE. As mentioned, in comment#5 the problem seems to be that reloading 'display-manager' service is way too aggressive. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1083037] Freshly installed system doesn't boot at all (no boot device found)
by bugzilla_noreply＠novell.com 02 Mar '18

02 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1083037 http://bugzilla.opensuse.org/show_bug.cgi?id=1083037#c8 Michal Svec <msvec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msvec(a)suse.com) | --- Comment #8 from Michal Svec <msvec(a)suse.com> --- (In reply to Jiri Srain from comment #6) > Well, the generic code is written to MBR: That seems to be correct: f120205471a79e72e8c3f099a8e368f1 /usr/share/syslinux/gptmbr.bin f120205471a79e72e8c3f099a8e368f1 /tmp/mbr1 > And, please, check whether your BIOS tries to load system from the right > disk and whether it supports GPT partition tables. It worked before with preinstalled Windows so I suppose it should work fine. (In reply to Josef Reidinger from comment #7) > parted -s /dev/sda disk_set pmbr_boot on That didn't help either. -- You are receiving this mail because: You are on the CC list for the bug.

1 0