April 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1084812] [aarch64] IPv4 DNS leading to segfaults
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.novell.com/show_bug.cgi?id=1084812 http://bugzilla.novell.com/show_bug.cgi?id=1084812#c41 Michael Matz <matz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz(a)suse.com --- Comment #41 from Michael Matz <matz(a)suse.com> --- Well, in 2015, when the thread was written obviously the hope still was that ARM would be fixing this bug in later revisions of the mask, hence the optimistic "early revisions". Equally obviously ARM thought it not worth the trouble; I'm guessing it has something to do with bang-for-buck and margins :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084812] [aarch64] IPv4 DNS leading to segfaults
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084812 http://bugzilla.suse.com/show_bug.cgi?id=1084812#c40 --- Comment #40 from Matthias Brugger <mbrugger(a)suse.com> --- Pine64's A64 is also r0p4... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084812] [aarch64] IPv4 DNS leading to segfaults
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084812 http://bugzilla.suse.com/show_bug.cgi?id=1084812#c39 --- Comment #39 from Alexander Graf <agraf(a)suse.com> --- Xilinx ZynqMP is also r0p4, thus is affected. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084812] [aarch64] IPv4 DNS leading to segfaults
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1084812 http://bugzilla.suse.com/show_bug.cgi?id=1084812#c38 --- Comment #38 from Petr Tesařík <ptesarik(a)suse.com> --- I think the upstream thread is confused. ARM says r0p0, r0p1, r0p2, r0p3, r0p4. In rxpy, the x corresponds to major revision (aka Variant field in MIDR_EL1 aka "CPU variant" in /proc/cpuinfo), and y corresponds to minor revision or product revision (aka Revision field in MIDR_EL1 aka "CPU revision" in /proc/cpuinfo). Commented content of /proc/cpuinfo on a RPi3 system (rpi33.arch) says: CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 // major revision number 0 CPU part : 0xd03 // Cortex-A53 processor CPU revision : 4 // product revision number 4 In short, this CPU is r0p4, thus affected by the erratum 843419 according to ARM official documentation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087903] New: Google Chrome and Chromium show empty (transparent) window with NVidia drivers
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087903 Bug ID: 1087903 Summary: Google Chrome and Chromium show empty (transparent) window with NVidia drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: shundhammer(a)suse.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 765784 --> http://bugzilla.opensuse.org/attachment.cgi?id=765784&action=edit Output of rpm -qa | sort With the recent TW update, both Google Chrome and Chromium don't render anything on my machine; I only get a transparent window, not even window manager borders. The window appears to get the keyboard focus, it shows up in the (Xfce) task list, and I can use Alt-Tab to cycle between it and the other windows on my desktop as usual. In some regions of this transparent window I even can create a rectangular selection with the mouse; I can see the selection rectangle, but nothing else. When I try to make a screenshot, the screenshot also doesn't contain any content (other than the windows below it and the desktop background). All this worked well all the time for over two years, but something in the recent TW update broke it. I am not sure if it's on the NVidia driver side or on the Chrome/Chromium/WebKit side; I suspect NVidia. Versions: Tumbleweed from 2018-04-01 [shundhammer @ morgul] ~ % rpm -qa | grep nvidia nvidia-glG04-390.42-11.1.x86_64 nvidia-computeG04-390.42-11.1.x86_64 x11-video-nvidiaG04-390.42-11.1.x86_64 nvidia-gfxG04-kmp-default-390.42_k4.15.13_1-11.4.x86_64 [shundhammer @ morgul] ~ % rpm -qa | grep chrom google-chrome-stable-65.0.3325.181-1.x86_64 chromium-65.0.3325.181-1.2.x86_64 chrome-gnome-shell-10.1-1.1.x86_64 [shundhammer @ morgul] ~ % uname -a Linux morgul 4.15.13-1-default #1 SMP PREEMPT Sun Mar 25 08:34:58 UTC 2018 (950fc49) x86_64 x86_64 x86_64 GNU/Linux [shundhammer @ morgul] ~ % cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20180401" ID=opensuse ID_LIKE="suse" VERSION_ID="20180401" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20180401" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1085676] usbip stopped working as of 42.3
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1085676 http://bugzilla.suse.com/show_bug.cgi?id=1085676#c6 --- Comment #6 from Eleftherios Koutsofios <ek(a)research.att.com> --- I guess my tumbleweed version is: VERSION_ID="20180331" PRETTY_NAME="openSUSE Tumbleweed" kernel is 4.15.13-1-default (although I tested it a couple weeks ago so it was probably a slightly older version). usbip also works on 15.0 beta, kernel 4.12.14-lp150.6-default thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087791] Image ARM-JeOS-raspberrypi2.armv7l-2018.03.31-Build3.3 does not boot
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087791 http://bugzilla.suse.com/show_bug.cgi?id=1087791#c3 Andreas Färber <afaerber(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Bootloader Assignee|afaerber(a)suse.com |agraf(a)suse.com OS|Other |openSUSE Factory --- Comment #3 from Andreas Färber <afaerber(a)suse.com> --- I'm guessing this is a duplicate of bug #1083334, related to u-boot package update and missing raspberrypi-firmware-dt package in the JeOS Kiwi description. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087547] contrasts bad in context menus, tabs & details
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087547 http://bugzilla.suse.com/show_bug.cgi?id=1087547#c4 --- Comment #4 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1087547) was mentioned in https://build.opensuse.org/request/show/593237 15.0 / branding-openSUSE -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1087547] New: contrasts bad in context menus, tabs & details
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1087547 Bug ID: 1087547 Summary: contrasts bad in context menus, tabs & details Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- 15.0 build 182.1 installer on real hardware Actual behavior: 1:[frustrating] contrast appears to be less than maximized (text looks gray, not black) except where obviously emboldened (e.g. package names in installation summary and search results panes) 2:[annoying] unselected tabs' text on View/Search/Patterns/Installation Summary row and Description/Technical Data/Dependencies/Versions row appear grayed out as if intended to be unavailable for selection, unless and until they are hovered 3:[serious] hovered context menu item for selectable packages and hovered view menu item is grayed out as if intended to be unavailable for selection, virtually invisible; 4:functional equivalent of #3 for partitioner select lists 5:functional equivalent of #2 for bootloader tabs Expected behavior: 1-crisp black high contrast normal (non-bold) text 2-tab text legible without need to hover 3-selected context menu item and selected View menu item equal to or greater than contrast of adjacent items 4:=#3 5:=#2 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1087829] Installer continues despite digest verification failure
by bugzilla_noreply＠novell.com 03 Apr '18

03 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=1087829 http://bugzilla.suse.com/show_bug.cgi?id=1087829#c5 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |CONFIRMED URL| |https://trello.com/c/cwzB97 | |7M Assignee|yast2-maintainers(a)suse.de |yast-internal(a)suse.de --- Comment #5 from Steffen Winterfeldt <snwint(a)suse.com> --- yast2-trans-en_US are the en_US translations (used mainly for spelling corrections). While this is all true you normally do not run into this situation. And security is not compromised as files failing signature checks are not used. I can still schedule this but there's unlikely to happen anything anytime soon. Tracking in YaST scrum board. -- You are receiving this mail because: You are on the CC list for the bug.

1 0