December 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1117079] Changing existing entries in YaST Software-Repositories does not work
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=1117079 http://bugzilla.suse.com/show_bug.cgi?id=1117079#c6 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak(a)suse.com) | --- Comment #6 from Ladislav Slezák <lslezak(a)suse.com> --- (In reply to Frank Kruger from comment #3) > FYI: Works with yast2-4.1.35-lp150.1.1.x86_64 from > https://download.opensuse.org/repositories/YaST:/Head/openSUSE_Leap_15.0/ OK, let's consider it as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1117079] Changing existing entries in YaST Software-Repositories does not work
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=1117079 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1118212] Misbehaving SATA device leaks kernel memory pages to unprivileged user
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

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

1 0

[Bug 1099391] cannot boot system installed on lvm ontop raid1 after update (Cannot activate LVs in VG vghome while PVs appear on duplicate devices)
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=1099391 http://bugzilla.suse.com/show_bug.cgi?id=1099391#c28 --- Comment #28 from Gang He <ghe(a)suse.com> --- Hello Michael, Sorry for interruption again. The upstream developer submitted more patches, to fix this bug. I have created a new lvm2 rpms, which includes these patches, see comment #27. Could you help to verify if the new rpms works on your case? Thanks Gang -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1099391] cannot boot system installed on lvm ontop raid1 after update (Cannot activate LVs in VG vghome while PVs appear on duplicate devices)
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=1099391 http://bugzilla.suse.com/show_bug.cgi?id=1099391#c27 --- Comment #27 from Gang He <ghe(a)suse.com> --- Created attachment 792013 --> http://bugzilla.suse.com/attachment.cgi?id=792013&action=edit lvm2_2.02.182 rpm,which also includes some patches to fix this bug -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1118363] New: shim-install is broken
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1118363 Bug ID: 1118363 Summary: shim-install is broken 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: nwr10cst-oslnx(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: I recently installed Tumbleweed on an external USB drive). I installed using "grub2" and booting from the MBR. But I wanted to also be able to boot this external drive from a UEFI system. Here's what I attempted: # shim-install --no-nvram --removable copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/boot/grub.efi Installing for i386-pc platform. /usr/sbin/grub2-install: error: install device isn't specified. Evidently, "shim-install" is internally calling "grub2-install". But it is calling it the wrong way. It should be calling with "--target=x86_64-efi" To work around the problem, I manually did what shim-install should have done: # grub2-install --target=x86_64-efi --no-nvram --removable Installing for x86_64-efi platform. Installation finished. No error reported. I then repeated the same "shim-install" command as used earlier, with the same error message. But the combination seems to have done what I wanted. I have successfully booted from that external drive on both a legacy BIOS system and on a UEFI system. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1118163] New: LTO introduces indeterminism into .o files
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1118163 Bug ID: 1118163 Summary: LTO introduces indeterminism into .o files Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: matz(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: rguenther(a)suse.com Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that the valgrind package varied for every build because its .a files contain .o files created by gcc -flto -c Here is the minimal reproducer: echo 'void f() {}' > test.c for i in $(seq 10) ; do gcc -flto -c test.c ; md5sum test.o ; done | sort | uniq -c > rpm -q gcc8 gcc8-8.2.1+r265901-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1118529] VUL-0: chromium: multiple vulnerabilities fixed in 71.0.3578.80
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

1 0

[Bug 1110421] New: Brightness change without effect after suspend (and removing external screen)
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1110421 Bug ID: 1110421 Summary: Brightness change without effect after suspend (and removing external screen) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cyberbeat(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To reproduce (hwinfo see underneath): 1. Start laptop with current kde plasma 2. configure kde (kscreen) to only use external screen (DVI as main output), internal screen LVDS1 off 3. suspend laptop 4. remove external screen by removing laptop from docking station 5. awake laptop from suspend ==> 6. now the internal screen is active, but dimmed to the lowest brightness. The kde brightness controls have no effect anymore. The only thing that helps: reboot. After that the brightness is set right to highest value, and the controls work again. hwinfo --gfx --monitor 14: PCI 02.1: 0380 Display controller [Created at pci.378] Unique ID: ruGf.Gsn0zTMyIl3 SysFS ID: /devices/pci0000:00/0000:00:02.1 SysFS BusID: 0000:00:02.1 Hardware Class: graphics card Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1179 "Toshiba America Info Systems" SubDevice: pci 0x000d Revision: 0x07 Memory Range: 0xc0000000-0xc00fffff (rw,non-prefetchable,disabled) Module Alias: "pci:v00008086d00002A43sv00001179sd0000000Dbc03sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown 26: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.378] Unique ID: _Znp.lPQO3e3I18E SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x2a42 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x1179 "Toshiba America Info Systems" SubDevice: pci 0x000d Revision: 0x07 Driver: "i915" Driver Modules: "i915" Memory Range: 0xff400000-0xff7fffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable) I/O Ports: 0xcff8-0xcfff (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 16 (786899 events) I/O Ports: 0x3c0-0x3df (rw) Module Alias: "pci:v00008086d00002A42sv00001179sd0000000Dbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=no, avail=yes, need=no, active=unknown 28: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.HWxGBMIb4T1 Parent ID: _Znp.lPQO3e3I18E Hardware Class: monitor Model: "LG ELECTRONICS L1953TR " Vendor: GSM "LG ELECTRONICS" Device: eisa 0x4b44 "L1953TR " Resolution: 720x400@70Hz Resolution: 640x480@60Hz Resolution: 640x480@75Hz Resolution: 800x600@60Hz Resolution: 800x600@75Hz Resolution: 832x624@75Hz Resolution: 1024x768@60Hz Resolution: 1024x768@75Hz Resolution: 640x480@75Hz Resolution: 800x600@75Hz Resolution: 1024x768@75Hz Resolution: 1280x1024@60Hz Size: 338x270 mm Year of Manufacture: 2008 Week of Manufacture: 5 Detailed Timings #0: Resolution: 1280x1024 Horizontal: 1280 1328 1440 1688 (+48 +160 +408) +hsync Vertical: 1024 1025 1028 1066 (+1 +4 +42) +vsync Frequencies: 108.00 MHz, 63.98 kHz, 60.02 Hz Driver Info #0: Max. Resolution: 1280x1024 Vert. Sync Range: 56-75 Hz Hor. Sync Range: 30-71 kHz Bandwidth: 108 MHz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #26 (VGA compatible controller) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1112824] Severe Performance Degradation with update to latest tumbleweed (20181018)
by bugzilla_noreply＠novell.com 06 Dec '18

06 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=1112824 http://bugzilla.suse.com/show_bug.cgi?id=1112824#c75 --- Comment #75 from Dead Mozay <windowskaput(a)gmail.com> --- Created attachment 792011 --> http://bugzilla.suse.com/attachment.cgi?id=792011&action=edit Logs (In reply to Borislav Petkov from comment #71) > (In reply to Dead Mozay from comment #69) > > I'm talking about it, openSUSE boot with pti=off spectre_v2=off l1tf=off > > nospec_store_bypass_disable no_stf_barrier, Fedora with default settings. In > > Fedora no problem even with enabled hyper-threading. > > Can you upload full dmesg from the Fedora kernel and also do > > $ grep . /sys/devices/system/cpu/vulnerabilities/* > vuln.log > > on it and upload that vuln.log file too? > > Thx. Sure -- You are receiving this mail because: You are on the CC list for the bug.

1 0