May 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 988273] New: Steam segmentation fault
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=988273 Bug ID: 988273 Summary: Steam segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: quarckster(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: Steam crashes immediately after starting due this bug https://github.com/ValveSoftware/steam-for-linux/issues/4504 Reproducible: Always Steps to Reproduce: 1. Install steam 1.0.0.52 2. Run it Actual Results: Steam crashes with segmentation fault. Expected Results: Steam works fine. There is fix/workaround for this http://www.gearsongallium.com/?p=3276#utm_source=feedly&utm_medium=rss&utm_… mesa must be compiled with libnettle: --with-sha1=libnettle -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1036356] Missing docker dependencies
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036356 http://bugzilla.suse.com/show_bug.cgi?id=1036356#c5 --- Comment #5 from Jordi Massaguer <jmassaguerpla(a)suse.com> --- About runc, coreos had a similar issue and the problem was fixed by specifying the commit when building https://github.com/coreos/coreos-overlay/pull/2428/commits/a0294fbf2caf5f1a… There is a similar issue in RedHat bugzilla. The warning is harmless but the thing is that docker checks whether you are using their docker runc binary built with a very specific commit. If this is not causing you an issue, we can fix that in the next docker update. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036356] Missing docker dependencies
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036356 http://bugzilla.suse.com/show_bug.cgi?id=1036356#c4 --- Comment #4 from Jordi Massaguer <jmassaguerpla(a)suse.com> --- the runc issue is more concerning. Can you give us the output of: rpm -qa | grep docker rpm -qa | grep runc ls -l /usr/bin/docker-runc ls -l /usr/sbin/runc runc --version I see it is also a warning. Is this causing you some real issue? I mean, are you able to run your docker images even the warning? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036356] Missing docker dependencies
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036356 http://bugzilla.suse.com/show_bug.cgi?id=1036356#c3 --- Comment #3 from Jordi Massaguer <jmassaguerpla(a)suse.com> --- Hi, the docker-init seems more like a warning. This is optional. The docker-init is a binary that you can use in your images to handle the signals properly, as the init binary for your images. Right now we are not releasing an init binary but if you are interested, you could try with tini: https://build.opensuse.org/package/show/Virtualization:containers/tini -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036331] New: slrn licensing issue
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1036331 Bug ID: 1036331 Summary: slrn licensing issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: nadvornik(a)suse.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gber(a)opensuse.org Found By: --- Blocker: --- https://build.opensuse.org/request/show/487324 @babelworx declined the legal report with the following comment: See license of slrn-1.0.3/src/vms.c (non-commercial > * Copyright : (c) Copyright 1991-95 by Iain Lea & Andrew Greer > * You may freely copy or redistribute this software, > * so long as there is no profit made from its use, sale > * trade or reproduction. You may not change this copy- > * right notice, and it must be included in any copy made #if ! SLRN_USE_SLTCP Please note that this version of slrn also contains code published under a different license: " This software is Copyright 1991 by Stan Barber.", "", " Permission is hereby granted to copy, reproduce, redistribute or otherwise", " use this software as long as: there is no monetary profit gained", " specifically from the use or reproduction or this software, it is not", " sold, rented, traded or otherwise marketed, and this copyright notice is", " included prominently in any copy made.", "", " The author make no claims as to the fitness or correctness of this software", " for any use whatsoever, and it is provided as is. Any use of this software", " is at the user's own risk.", -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1037139] New: Installation of spice-gtk-0.33-6.1.x86_64: cannot verify root:root 0755 - not listed in /etc/permissions
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1037139 Bug ID: 1037139 Summary: Installation of spice-gtk-0.33-6.1.x86_64: cannot verify root:root 0755 - not listed in /etc/permissions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pgeorgiadis(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The installation of `spice-gtk-lang-0.33-6.1.noarch` triggered (as a dependency) the installation of `spice-gtk-0.33-6.1.x86_64`. Here's is the message that gets displayed: > Installing: spice-gtk-0.33-6.1.x86_64 [.......done] > Additional rpm output: > /usr/bin/spice-client-glib-usb-acl-helper: cannot verify root:root 0755 - not listed in /etc/permissions Notice that the installation took place in a clean system, which means that the 'spice-gtk-0.33-6.1' cannot verify the default's machine's security policy. If this is just a false warning that can be ignored, please provide a message saying so. If this is not possible, then feel free to close this bug-report. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1037126] New: binutils: enable as-needed by default
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1037126 Bug ID: 1037126 Summary: binutils: enable as-needed by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Development Assignee: matz(a)suse.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: rguenther(a)suse.com Found By: --- Blocker: --- Inside the build service environment created by /usr/bin/build, $SUSE_ASNEEDED is set and ld behaves as if it were passed -Wl,--as-needed. Outside that box, in a "normal" system, SUSE_ASNEEDED=0. This behavior is puzzling to some people every now and then. https://lists.opensuse.org/opensuse-packaging/2017-05/msg00000.html I think we should always enable --as-needed for the openSUSE "normal" system. Debian systems also behave such that an incorrect -l order leads to builds stopping. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1030548] [Build 9.7] openQA test fails in yast2_bootloader "error: install device isn't specified"
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1030548 http://bugzilla.suse.com/show_bug.cgi?id=1030548#c10 --- Comment #10 from Michael Chang <mchang(a)suse.com> --- (In reply to Michael Chang from comment #9) > Did you check '/sys/firmware/efi' was there .. (as previous comment)? Sorry. Check /sys/firmware/efi is a directory and not empty ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1030548] [Build 9.7] openQA test fails in yast2_bootloader "error: install device isn't specified"
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1030548 http://bugzilla.suse.com/show_bug.cgi?id=1030548#c9 --- Comment #9 from Michael Chang <mchang(a)suse.com> --- (In reply to Josef Reidinger from comment #7) > mchang - but see my output from real hardware which is booted via EFI. It > also failed when I run shim-install manually. Did you check '/sys/firmware/efi' was there .. (as previous comment)? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1030548] [Build 9.7] openQA test fails in yast2_bootloader "error: install device isn't specified"
by bugzilla_noreply＠novell.com 03 May '17

03 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1030548 http://bugzilla.suse.com/show_bug.cgi?id=1030548#c8 --- Comment #8 from Michael Chang <mchang(a)suse.com> --- (In reply to Josef Reidinger from comment #5) > mchang - same happen on my system when doing zypper dup in Tumbleweed. > so shim-install do not pass target and grub2-install for unknown reason try > to use i386-pc. The grub2-install checks '/sys/firmware/efi' directory for UEFI system, Could you please make sure it's there ? > > shim-install do not recognize --target option, so I cannot help there with > passing it explicitly. We can patch shim-install to force the target option, however if it was actually caused by missing '/sys/firmware/efi' on (supposed to be) UEFI system we might also have other problem (as other utility like efibootmgr may also need it to work). -- You are receiving this mail because: You are on the CC list for the bug.

1 0