February 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1048660] New: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported.
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048660 Bug ID: 1048660 Summary: LibreOffice 5.3.3 update: Type 1 (Postscript) fonts are no longer supported. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 13th July 2017: With the Leap 42.2 upgrade of LibreOffice from version 5.2.5 to version 5.3.3 the fact that, with version 5.3 LibreOffice has dropped support for Type 1 (Postscript) fonts was a not so pleasant surprise. Please consider placing a note indicating that, LibreOffice as of version 5.3 no longer supports Type 1 (Postscript) fonts in the Release Notes. Is also, possibly an issue for the Leap 42.3 Release Notes. --------------------------------------------------------- I haven't found anything in the LibreOffice Release Notes indicating this issue: <https://www.libreoffice.org/download/release-notes/> There's only this article in "Linux Magazine": <http://www.linux-magazine.com/Online/Blogs/Off-the-Beat-Bruce-Byfield-s-Blo…> There's information in this Document Foundation Bug Report: Bug 104701 <https://bugs.documentfoundation.org/show_bug.cgi?id=104701> --------------------------------------------------------- There's possibly help for the folks (like me) with a suite of Type 1 fonts here: <https://slackbuilds.org/repository/14.2/system/afdko/> Haven't tried to build the "Adobe Font Development Kit for OpenType" yet -- will happen later today. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1048392] New: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version
by bugzilla_noreply＠novell.com 11 May '22

11 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1048392 Bug ID: 1048392 Summary: [doc] Extended Permission bits: Konqueror is also the Plasma 5 version Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: sknorr(a)suse.com Reporter: bugrprt21882(a)online.de QA Contact: lnussel(a)suse.com Found By: --- Blocker: --- 3.2 Dolphin Does Not Set Extended Permission Bits https://doc.opensuse.org/release-notes/x86_64/openSUSE/Leap/42.3/#sec.gener… Unfortunately, with Leap 42.3, Konqueror is also the Plasma 5 version and, it also can not set the Extended Permissions bits . . . Therefore, the Leap 42.3, CLI only to toggle the Extended Permission bits . . . -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1021059] New: [s390x-port][Build0001] dependency issues when installing default with kde
by bugzilla_noreply＠novell.com 08 May '22

08 May '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1021059 Bug ID: 1021059 Summary: [s390x-port][Build0001] dependency issues when installing default with kde Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mgriessmeier(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 710981 --> http://bugzilla.opensuse.org/attachment.cgi?id=710981&action=edit y2logs I'm trying to install Tumbleweed on s390x for the first time. Default pattern and KDE as default desktop, resulting in following dependency problems: #### YaST2 conflicts list - generated 2017-01-20 10:15:31 #### nothing provides libpfm.so.4()(64bit) needed by s390-tools-1.34.0-1.1.s390x [ ] do not install grub2-2.02~beta3-16.1.s390x [ ] break s390-tools-1.34.0-1.1.s390x by ignoring some of its dependencies nothing provides plasma5-desktop needed by patterns-openSUSE-kde_plasma-20151112-29.1.s390x [ ] do not install pattern:kde-20151112-29.1.s390x [ ] break patterns-openSUSE-kde_plasma-20151112-29.1.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install ntp-4.2.8p9-1.2.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install xinetd-2.3.15-11.4.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install kernel-default-4.9.0-2.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:base-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies nothing provides libicu57_1-bedata = 57.1 needed by libicu57_1-57.1-1.11.s390x [ ] do not install pattern:x11-20151112-29.1.s390x [ ] break libicu57_1-57.1-1.11.s390x by ignoring some of its dependencies #### YaST2 conflicts list END ### see attached y2logs -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1081947] New: PAM module pam_keyinit is still not included in the PAM stack
by bugzilla_noreply＠novell.com 20 Apr '22

20 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1081947 Bug ID: 1081947 Summary: PAM module pam_keyinit is still not included in the PAM stack 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Bug #1045886 revealed the lack of the integration of the PAM module "pam_keyinit". The pam_keyinit PAM module ensures that the invoking process has a session keyring other than the user default session keyring. The created session keyring will be linked to the user keyring. Even if it currently works without the integration of "pam_keyinit", in this case the user session keyring is used as fallback, it's strongly recommended to use a session-keyring instead especially for root user, see man user-session-keyring(7). That would also has the benefit to re-enable the keyring support in systemd where each system service gets its own session keyring automatically not linked with the user-keyring (the root one). pam-config gained support for the configuration of pam_keyinit recently [1] but it's still not used and therefore pam_keyinit is still not integrated in the PAM stack. [1] https://build.opensuse.org/request/show/565816 -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[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 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