April 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1086036] New: translation-update-upstream commented out for Leap
by bugzilla_noreply＠novell.com 19 Jul '21

19 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 Bug ID: 1086036 Summary: translation-update-upstream commented out for Leap Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Translations Assignee: dimstar(a)opensuse.org Reporter: sbrabec(a)suse.com QA Contact: ke(a)suse.com CC: tchvatal(a)suse.com Found By: --- Blocker: --- Looking at the packages, many of them now use: %if !0%{?is_opensuse} translation-update-upstream %endif This is an ugly divergence between SLE15 and Leap, as it forces splitting of translation-update and translation-update-upstream packages for SLE15 and Leap15, and doubles amount of work on translation updates. Disabling translation-update-upstream makes impossible to do a build-time translation update and forces post-installation updates). It makes translation-update for SLE unusable for Leap, and it also increases size of installation image with translations. I am aware of a small increase of build time, but it makes possible to easily update translations directly in the lang package without touching the sources. Technical details: translation-update-upstream: Package that contains new upstream translations that can be used during the build time. It contains supplementary scripts to get the update. translation-update: Package that contains post-installation updates. The tarball in this package is generated from translation-update-upstream using the %prep log (if translation-update-upsteam succeeds, build-time translation update is used, if it fails, post-installation translation update is used). translation-update depends on a dedicated glibc patch. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1082345] New: [NEEDS-REBASE] gnome-shell-extensions 3.27.91 patches need rebase
by bugzilla_noreply＠novell.com 19 Jul '21

19 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1082345 Bug ID: 1082345 Summary: [NEEDS-REBASE] gnome-shell-extensions 3.27.91 patches need rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - Disable SLE-classic patches that need rebase: gse-sle-classic-ext.patch, gnome-shell-add-app-to-desktop.patch, gnome-shell-favorites-menu-at-end.patch and gnome-shell-extensions-window-list-app-icon-not-shown.patch. Those patches do not apply on GNOME Shell exteions 3.27.91 (in GNOME:Next) -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061742] New: GNOME: sle-classic applications menu handles right click like left click
by bugzilla_noreply＠novell.com 19 Jul '21

19 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1061742 Bug ID: 1061742 Summary: GNOME: sle-classic applications menu handles right click like left click Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: Other Status: NEW Keywords: Usability Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: sebastian.parschauer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: L3 Blocker: --- On Leap 42.3 sle-classic session the right click on an application in the applications menu results in just opening the application instead of showing a small popup like this: Open --- Add to Favorites Add to Desktop My expectation is that this works the same way like on SLES12-SP2. Please fix this. TIA -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1039756] New: GNOME needs to support default.desktop in session directories
by bugzilla_noreply＠novell.com 19 Jul '21

19 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1039756 Bug ID: 1039756 Summary: GNOME needs to support default.desktop in session directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/376325/modules/first_ boot/steps/21 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org, fvogt(a)suse.com, jreidinger(a)suse.com, lnussel(a)suse.com, lslezak(a)suse.com, mlin(a)suse.com, okurz(a)suse.com, simonf.lees(a)suse.com Depends on: 1030873 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1030873 +++ If no default autologin session is defined, default.desktop (usually in /usr/share/xsessions, but can eventually be in wayland-sessions as well) is used by displaymanagers such as lightdm and sddm. This link is now created by update-alternatives for IceWM, Xfce, LXQt (sr not accepted yet), Plasma5 and enlightenment. This means that if GDM is used if one of those is installed, it will list default.desktop twice, as it is a symlink to a .desktop file in the same directory. lightdm and sddm are patched to recognize this properly. GDM should respect the default.desktop selection if nothing else is defined in /etc/sysconfig/displaymanager. GNOME should also register itself with update-alternatives, with the same priority as KDE (25), for reference: https://build.opensuse.org/package/rdiff/KDE:Frameworks5/plasma5-session?li… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1090376] New: plasma panel bar does not scale up
by bugzilla_noreply＠novell.com 19 Jul '21

19 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1090376 Bug ID: 1090376 Summary: plasma panel bar does not scale up Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- on a 3840x2160 screen with 157x161 dots per inch KDE looks quite ok by default, only the panel did not scale up -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1087369] New: Change default TLS configuration of lighttpd for better security out-of-the-box
by bugzilla_noreply＠novell.com 18 Jul '21

18 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087369 Bug ID: 1087369 Summary: Change default TLS configuration of lighttpd for better security out-of-the-box Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Depends on: 1086764 Found By: --- Blocker: --- To comply with upcoming standards (PCI DSS) a default installation of nginx should only support TLS 1.1 and above (1.2 recommended / strongly encouraged): [0] https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-… > 30 June 2018 is the deadline for disabling SSL/early TLS and implementing a > more secure encryption protocol – TLS 1.1 or higher (TLS v1.2 is strongly > encouraged) in order to meet the PCI Data Security Standard (PCI DSS) for > safeguarding payment data. For some more details refer to [1] https://bugzilla.suse.com/show_bug.cgi?id=1086764 Therefore the default should be changed in /etc/lighttpd/lighttpd.conf [2] https://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_SSL Configuration ====================== ssl.openssl.ssl-conf-cmd specify openssl config commands (e.g. ("Protocol" => "-ALL, TLSv1.2") restricts protocol to only TLS 1.2) (since 1.4.48) (commit https://redmine.lighttpd.net/projects/lighttpd/repository/revisions/c09acbe…) ====================== lighttpd version 1.4.48 is in openSUSE Tumbleweed and openSUSE Leap 15 only: https://software.opensuse.org/package/lighttpd Something to be like this in 'SSL Support' section of /etc/lighttpd/lighttpd.conf file: ============================ # Allow TLS version 1.2 only, which is a recommended default these days # by international information security standards. #ssl.openssl.ssl-conf-cmd = ("Protocol" => "-ALL, TLSv1.2") ============================ See also: ============= [3] https://bugzilla.suse.com/show_bug.cgi?id=1086854 (Change default TLS configuration of apache2 for better security out-of-the-box) [4] https://bugzilla.suse.com/show_bug.cgi?id=1086855 (Change default TLS configuration of nginx for better security out-of-the-box) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1109665] New: Disabling f2fs
by bugzilla_noreply＠novell.com 16 Jul '21

16 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1109665 Bug ID: 1109665 Summary: Disabling f2fs Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: nborisov(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This issue is to be used as a collection of all discussions regarding disabling the compilation of f2fs in various opensuse distributions. Currently this filesystem received only sporadic CVE-related backports. In the process of doing said backports I have also identified several drawbacks which make it rather hard to support and provide sensible experience: 1. There are a bunch of validation checks which are not being backported since they are not linked to a particular CVE as such the stability of the filesystem is questionable even with CVE backports. 2. Currently the filesystem doesn't have a way to disable mounting of filesystems created with newer kernels, containing on-disk incompatible changes. I have talked with one of the maintainers and they recognize this fact but so far no one is working on this. This is a pretty major since newer images could potentially crash older kernels not being able to properly parse them. 3. All in all this leads me to believe that f2fs requires a rather controller environment in terms of kernel/tools versions so is not a good candidate to be included in a community-based distribution kernel. I've already spoken to release manager for leap/tumbleweed and they are fine with disabling it. -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1127886] New: drop openSUSE specific nf_conntrack_slp module
by bugzilla_noreply＠novell.com 14 Jul '21

14 Jul '21

http://bugzilla.suse.com/show_bug.cgi?id=1127886 Bug ID: 1127886 Summary: drop openSUSE specific nf_conntrack_slp module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For years, we have been keeping non-upstream patch patches.suse/netfilter-ip_conntrack_slp.patch in our kernels. The patch adds conntrack helper for SLP protocol. However, the patch has been rejected by upstream https://www.spinics.net/lists/netfilter-devel/msg26254.html because since kernel 3.6, there is a netfilter infrastructure for userspace conntrack helpers and in kernel helpers are deprecated. The SLP helper is trivial so that it won't be difficult to write a userspace helper for conntrack-tools package (or even use e.g. existing one for mdns) and use it. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1115435] New: atop: migrate from cron to systemd timers
by bugzilla_noreply＠novell.com 12 Jul '21

12 Jul '21

http://bugzilla.suse.com/show_bug.cgi?id=1115435 Bug ID: 1115435 Summary: atop: migrate from cron to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: plinnell(a)opensuse.org Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com Found By: --- Blocker: --- This bug is part of TRACKERBUG bug#1115430. Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers. It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason. Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service". -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1096677] New: gcc-go is missing gccgo command
by bugzilla_noreply＠novell.com 11 Jul '21

11 Jul '21

http://bugzilla.suse.com/show_bug.cgi?id=1096677 Bug ID: 1096677 Summary: gcc-go is missing gccgo command 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: tdevries(a)suse.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In leap 15.0 I have: ... $ zypper search gcc | grep go i+ | gcc-go | The system GNU Go Compiler | package i+ | gcc-go-32bit | The system GNU Go Compiler | package i | gcc7-go | GNU Go Compiler | package i | gcc7-go-32bit | GNU Go Compiler | package $ gccgo If 'gccgo' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf gccgo $ cnf gccgo gccgo: command not found ... Compare this to ubuntu 16.04: ... $ gccgo The program 'gccgo' is currently not installed. You can install it by typing: sudo apt install gccgo $ sudo apt install gccgo The following NEW packages will be installed: gccgo gccgo-6 libgo9 $ gccgo gccgo: fatal error: no input files compilation terminated. ... When building gdb, it checks for the presence of gccgo. -- You are receiving this mail because: You are on the CC list for the bug.

2 7