January 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1095670] New: Problem with suid pgms on Leap-15.0
by bugzilla_noreply＠novell.com 24 Nov '21

24 Nov '21

http://bugzilla.suse.com/show_bug.cgi?id=1095670 Bug ID: 1095670 Summary: Problem with suid pgms on Leap-15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarkh(a)cfl.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am upgrading an older SuSE-13.2 box to Leap. I have done a fresh Leap-15.0 install and ported over the source code that we ran on the 13.2 box. It builds fine but I am having an issue. The program is/has to be an suid pgm. It also uses fork/execvpe/wait to execute some external scripts. And that is where my problem lies. The user is a member of several groups but these group memberships seem to disappear when these external scripts are executed. For instance the user is a member of the cdrom group so he can eject and work with a DVD. I have created a simple example script and source for a pgm that execvpe's that script which shows my problem. test.sh script: #!/bin/sh whoami id test.c pgm source: #define _GNU_SOURCE #include <unistd.h> #include <stdio.h> #include <stdlib.h> #include <string.h> int main() { char *path = getenv("PATH"); char pathenv[strlen(path) + sizeof("PATH=")]; sprintf(pathenv, "PATH=%s", path); char *envp[] = {pathenv, NULL}; char *tests[] = {"./test.sh", NULL}; execvpe(tests[0], tests, envp); } #cc test.c #/a.out markh uid=5076(markh) gid=100(users) groups=100(users),19(floppy),200(lcrs),484(tape),485(lp),488(disk),489(dialout),490(cdrom) Then as root: #chown root ./a.out #chgrp root ./a.out #chmod +s ./a.out Then as user #./a.out markh uid=5076(markh) gid=100(users) groups=100(users) Once the pgm is owned by root and suid, I lose all my group memberships for some unknown reason. It is not proper to me. This all works fine on 13.2 but does not on Leap 15 or Leap 42.3. Is there some security setting somewhere that broke this? -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 929755] New: shutter is missing perl(Gnome2) in Tumbleweed
by bugzilla_noreply＠novell.com 21 Nov '21

21 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=929755 Bug ID: 929755 Summary: shutter is missing perl(Gnome2) in Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f_koch(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 Build Identifier: flo@linux-mvsa:~> sudo zypper in shutter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl(Gnome2) needed by shutter-0.93.1-1.1.noarch Solution 1: do not install shutter-0.93.1-1.1.noarch Solution 2: break shutter-0.93.1-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1120098] New: Clang 7 packaging is inconsistent
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1120098 Bug ID: 1120098 Summary: Clang 7 packaging is inconsistent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: aaronpuchert(a)alice-dsl.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In llvm7.spec, the Clang binaries are renamed: # Fix the clang -> clang-X.Y symlink to work with update-alternatives mv %{buildroot}%{_bindir}/clang-%{_sonum} %{buildroot}%{_bindir}/clang ln -s %{_bindir}/clang-%{_relver} %{buildroot}%{_bindir}/clang-%{_minor} but the installed CMake files (in /usr/lib64/cmake/clang/) aren't changed accordingly. This makes it hard to build software that uses libclang. (I came across this when trying to update include-what-you-use.) The issue is easy to reproduce. Just create a folder with a CMakeLists.txt having just this line: find_package(Clang CONFIG REQUIRED) Then run "cmake ." and there will be an error message like CMake Error at /usr/lib64/cmake/clang/ClangTargets.cmake:296 (message): The imported target "clang" references the file "/usr/bin/clang-7" but this file does not exist. Possible reasons include: [...] Indeed, we have * /usr/bin/clang -> /etc/alternatives/clang -> /usr/bin/clang-7.0.0 * /usr/bin/clang-7.0 -> /usr/bin/clang-7.0.0 but no /usr/bin/clang-7. That is a bit unusual. On the other hand for gcc, we have * /usr/bin/gcc -> /usr/bin/gcc-8 -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1119092] New: llvm7: libLLVM is ABI incompatible between GCC and CLANG
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1119092 Bug ID: 1119092 Summary: llvm7: libLLVM is ABI incompatible between GCC and CLANG Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a clang-specific optimization in llvm::Optional, which makes code compiled with gcc and clang incompatible with each other. We build libLLVM, libclang, etc using clang, but the rest of the distribution is build using gcc. So anything that links against libLLVM, libclang, etc may be broken. Bug that introduced the clang-only optimization: https://bugs.llvm.org/show_bug.cgi?id=35978 Fix (removing the optimization from everywhere): https://reviews.llvm.org/D50710 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1112730] New: llvm opt-viewer can not find style.css
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1112730 Bug ID: 1112730 Summary: llvm opt-viewer can not find style.css Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using opt-viewer fails with: FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/style.css' The opt-viewer script is installed in /usr/bin and looks for "style.css" in its own directory, but "style.css" is installed in /usr/share/opt-viewer. LLVM by default installs all opt* tools in /usr/share/opt-viewer, but we move them to /usr/bin to follow our packaging rules. The opt-viewer needs to be patched to find the file. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1106000] New: llvm-config contains gcc-incompatible flags
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1106000 Bug ID: 1106000 Summary: llvm-config contains gcc-incompatible flags Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: msrb(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- llvm-config --cflags contains "-Werror=unguarded-availability-new" which makes builds with gcc fail: cc1plus: error: -Werror=unguarded-availability-new: no option -Wunguarded-availability-new -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1092697] New: LLVM build fails on armv7l
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1092697 Bug ID: 1092697 Summary: LLVM build fails on armv7l Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: msrb(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The llvm4/5/6 build fails on armv7l because it is running out of memory. It is happening during linking of stage1, most likely because of the size of debuginfo. Stage1 should not be built with debuginfo (it is only used to compile the next stage), but it got the "-g" parameter accidentally from %optflags. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1087136] New: GCC 8: llvm5 build fails
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087136 Bug ID: 1087136 Summary: GCC 8: llvm5 build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Build the package with GCC 8, there's error: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… Please build the project as follows to reproduce the issue: osc build --alternative-project=openSUSE:Factory:Staging:Gcc7 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1086445] New: libLLVMTableGen not packaged
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086445 Bug ID: 1086445 Summary: libLLVMTableGen not packaged Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guillaume.gardet(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently, in Tumbleweed, LLVM only packages libLLVM.so* and we are missing additional libraries, such as libLLVMTableGen.so* Some packages fails to build (e.g. ldc package) because of the missing additional libraries. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1073210] New: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1073210 Bug ID: 1073210 Summary: Link Time Optimization doesn't work out of the box on 64 bit systems because of bfd-plugins path mixup Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: l.lunak(a)centrum.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using LTO, linker is supposed to find a plugin for handling LTO in /usr/lib/bfd-plugins . And this path is hardcoded in sources, and it's "lib" even for 64 bit systems. However, neither GCC nor Clang/LLVM install their plugin there. GCC doesn't do anything with its plugin except for shipping it in its own directory, and LLVMGold is installed to /usr/lib64/bfd-plugins. So instead of LTO simply working when using -flto, one has to use gcc-ar/llvm-ar etc. to override the ar etc. which should work but don't because of this. I can easily submit fixed binutils and gcc packages to make them use /usr/lib64/bfd-plugins too, but I've first created this bugreport so that there's just one place for referring to this issue. Also I would first like to verify that this would indeed be the proper fix - is there any special reason why binutils hardcodes the "lib" there? -- You are receiving this mail because: You are on the CC list for the bug.

2 3