June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1045886] New: ecryptfs problems with recent Tumbleweed
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1045886 Bug ID: 1045886 Summary: ecryptfs problems with recent Tumbleweed 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: roger.whittaker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ecryptfs and the ecryptfs tools have stopped working correctly on recent versions of Tumbleweed. I noticed this because an existing ecryptfs Private directory could only be seen after a local login. ecryptfs-mount-private over ssh stopped working. On investigation, it is no longer possible to do ecryptfs-setup-private for a new user. $ ecryptfs-setup-private Enter your login passphrase [roger]: Enter your mount passphrase [leave blank to generate one]: ************************************************************************ YOU SHOULD RECORD YOUR MOUNT PASSPHRASE AND STORE IT IN A SAFE LOCATION. ecryptfs-unwrap-passphrase ~/.ecryptfs/wrapped-passphrase THIS WILL BE REQUIRED IF YOU NEED TO RECOVER YOUR DATA AT A LATER TIME. ************************************************************************ Done configuring. Testing mount/write/umount/read... Inserted auth tok with sig [83ecc1d632221288] into the user session keyring Inserted auth tok with sig [90e42628446d371b] into the user session keyring mount: No such file or directory ERROR: Could not mount private ecryptfs directory In the system logs we see: 2017-06-25T07:04:39.396038+01:00 [localhost] kernel: [140502.266628] Could not find key with description: [90e42628446d371b] 2017-06-25T07:04:39.396052+01:00 [localhost] kernel: [140502.266630] process_request_key_err: No key 2017-06-25T07:04:39.396054+01:00 [localhost] kernel: [140502.266631] Could not find valid key in user session keyring for sig specified in mount option: [90e42628446d371b] 2017-06-25T07:04:39.396056+01:00 [localhost] kernel: [140502.266631] One or more global auth toks could not properly register; rc = [-2] 2017-06-25T07:04:39.396072+01:00 [localhost] kernel: [140502.266632] Error parsing options; rc = [-2] $ uname -r 4.11.6-1-default $ grep VERSION_ID /etc/os-release VERSION_ID="20170620" -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 941931] New: GRUB2 graphical menu is extremely slow
by bugzilla_noreply＠novell.com 19 Apr '22

19 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=941931 Bug ID: 941931 Summary: GRUB2 graphical menu is extremely slow Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jmatejek(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 643998 --> http://bugzilla.suse.com/attachment.cgi?id=643998&action=edit screen showing output of vbeinfo i'm using an AMD GPU and a 2560x1440 native display. on this configuration, the GRUB2 UI is slow to the point of unusability; it takes a full second to flip from one menu item to another, 3-5s just to display the boot menu, before booting starts. drawing the chameleon logo is visible line-by-line, too lowering the resolution helps, at 1280x960x32 the speed is almost usable, 1280x960x16 is sluggish but OK (so i'm sticking with this resolution for now) my GPU is reported as follows: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] detected graphics modes are attached -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1098354] New: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive
by bugzilla_noreply＠novell.com 18 Apr '22

18 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098354 Bug ID: 1098354 Summary: VUL-0: CVE-2018-1002209: quazip: arbitrary file write vulnerability achieved by using a specially crafted zip archive Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://smash.suse.de/issue/208490/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: crrodriguez(a)opensuse.org Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#1593011 A vulnerability has been found in the way developers have implemented the archive extraction of files. An arbitrary file write vulnerability, that can be achieved using a specially crafted zip archive (affects other archives as well, bzip2, tar,xz, war, cpio, 7z), that holds path traversal filenames. So when the filename gets concatenated to the target extraction directory, the final path ends up outside of the target folder. Of course if an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily. This affects multiple libraries that lacks of a high level APIs that provide the archive extraction functionality. References: https://snyk.io/research/zip-slip-vulnerability References: https://bugzilla.redhat.com/show_bug.cgi?id=1593011 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1002209 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1071230] New: java installs symlinks that are not owned by a package
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=1071230 Bug ID: 1071230 Summary: java installs symlinks that are not owned by a package Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- java packages install e.g /usr/bin/keytool managed by update-alternatives but those files are not owned by any package. Since the symlink in /usr does not actually change it should be owned by a package. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 994084] New: Tracker bug: make packages own their symlinks in /etc/alternatives/*
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=994084 Bug ID: 994084 Summary: Tracker bug: make packages own their symlinks in /etc/alternatives/* 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: vcuadradojuan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for making all packages using update-alternatives own their symlinks at `/etc/alternatives/*`. Problem: Currently there is a mix of owned and not owned files by packages in `/etc/alternatives/*` (just look at `rpm -qf /etc/alternatives/*`). Currently there seems to be a sizeable chunk of packages not declaring `%ghost %_sysconfdir/alternatives/<binary>`, as specified at [1]. Also, see discussion on opensuse-factory m-l [2]. Once the mass bug filling for the issue is done, I will wait until 1 October for maintainers to action on the bugs, and afterwards I will start fixing each package by hand. Cheers, [1] https://en.opensuse.org/openSUSE:Packaging_Multiple_Version_guidelines [2] https://lists.opensuse.org/opensuse-factory/2016-08/msg00218.html -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 931978] New: VUL-0: CVE-2014-9721: zeromq: protocol downgrade attack on sockets using the ZMTP v3 protocol
by bugzilla_noreply＠novell.com 07 Apr '22

07 Apr '22

http://bugzilla.suse.com/show_bug.cgi?id=931978 Bug ID: 931978 Summary: VUL-0: CVE-2014-9721: zeromq: protocol downgrade attack on sockets using the ZMTP v3 protocol Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: tchvatal(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- rh#1221666 ------------------------------------- It was discovered that zeromq, a lightweight messaging kernel, is susceptible to a protocol downgrade attack on sockets using the ZMTP v3 protocol. This could allow remote attackers to bypass ZMTP v3 security mechanisms by sending ZMTP v2 or earlier headers. CVE request: http://openwall.com/lists/oss-security/2015/05/07/8 Upstream bug report: https://github.com/zeromq/libzmq/issues/1273 Upstream fix: https://github.com/zeromq/zeromq4-x/commit/b6e3e0f601e2c1ec1f3aac880ed6a3fe… ------------------------------------- References: https://bugzilla.redhat.com/show_bug.cgi?id=1221666 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-9721 http://seclists.org/oss-sec/2015/q2/515 http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-9721.html -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 953735] New: Change libqt5-creator name to qt5-creator
by bugzilla_noreply＠novell.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=953735 Bug ID: 953735 Summary: Change libqt5-creator name to qt5-creator Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! In Tumbleweed, I have been using the package qt-creator to develop Qt applications for a long time. I have always complained about the old version, since qt-creator is 3.2.2 and the newest version available is 3.5.1. However, it turns out that the newest version is already available in Tumbleweed (and in Leap) under the name libqt5-creator. Is there any good reason to name the package as libqt5-creator? I think this is very confusing. Since it has a lib* in the name, I did not even look at the description, so I was using a very old version all the time. Thus, I am wondering if it is possible to change the name of libqt5-creator to qt5-creator or something else. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1014929] New: GNOME:Apps/gnucash-docs: Bug
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1014929 Bug ID: 1014929 Summary: GNOME:Apps/gnucash-docs: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: adrian.klaver(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Need to add a dependency for yelp to package. Covers the case where the package is being installed on system that is not using GNOME as its desktop, eg using KDE. Without yelp you get the following message when trying to open the GnuCash Help: "GnuCash could not find the files for the help documentation. " even though gnucash-docs is installed. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1091802] New: openldap2: incomplete macro expansion(?) in script
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091802 Bug ID: 1091802 Summary: openldap2: incomplete macro expansion(?) in script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: GuoHouzuo(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com, varkoly(a)suse.com Found By: --- Blocker: --- The following product is going to be upgraded: openSUSE Tumbleweed 20180427-0 -> 20180501-0 x86_64 base openSUSE (38/73) Installing: openldap2-2.4.46-33.1.x86_64 ...................................................[done] Additional rpm output: /usr/sbin/openldap_update_modules_path.sh: line 1: s: command not found Updating /etc/sysconfig/openldap ... -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1040589] New: bash/gcc/gzip/python differ between builds because of profiling
by bugzilla_noreply＠novell.com 31 Mar '22

31 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 Bug ID: 1040589 Summary: bash/gcc/gzip/python differ between builds because of profiling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matz(a)suse.com Found By: Development Blocker: --- In https://build.opensuse.org/project/prjconf/openSUSE:Factory we have %do_profiling 1 and because of that in our bash.spec we enable gcc's 'profile feedback directed optimizations' but that causes the jobs.o and resulting bash binary to differ between builds, even when running on the same build host. And because of that, build-compare always thinks there is a change and triggers a re-publish and rebuild of depending packages We also have such binary diffs in gcc6 and gcc6.spec calls a make profiledbootstrap The do_profiling macro is used in bash gzip hello python3-base python-base sed xz and in http://rb.zq1.de/compare.factory-20170523/bash-compare.out http://rb.zq1.de/compare.factory-20170523/gcc6-compare.out http://rb.zq1.de/compare.factory-20170523/gzip-compare.out http://rb.zq1.de/compare.factory-20170523/python-base-compare.out http://rb.zq1.de/compare.factory-20170523/python3-base-compare.out we have strange diffs in assembler that I could not trace down to other sources of non-determinism until today. Diffs did go away when building without profiling (it was harder to disable for gcc6 and bash though) Do the profiles just count invocations of functions or do they depend on the type and speed of the system? In the first case, it should be possible to fix the profiling runs to be deterministic, but for that it would be useful to be able to see the differences between runs. How could I diff gcc's .gcda files? -- You are receiving this mail because: You are on the CC list for the bug.

2 15