openSUSE Bugs February 2021

bugs@lists.opensuse.org

1 participants
3510 discussions

[Bug 1181974] New: Lenovo X1 Extreme Gen.3: suspend/hibernate to ram doesn't work properly
by bugzilla_noreply＠suse.com 08 Jan '23

08 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1181974 Bug ID: 1181974 Summary: Lenovo X1 Extreme Gen.3: suspend/hibernate to ram doesn't work properly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: p.heinlein(a)heinlein-support.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845928 --> http://bugzilla.opensuse.org/attachment.cgi?id=845928&action=edit output hwinfo On Lenovo X1 Extreme Gen.3 suspend/hibernate to RAM doesn't work properly. 5.3.18-lp152.63-default openSUSE Leap 15.2 If I close the cover it suspends/hibernates and starts sleeping, but when I re-open the cover it does not survive beeing awaked. Instead, it works $something for half a second and then it powers of completely. After pressing the power button, it does a complete cold boot. In rare cases it did survive a suspend and it did awake properly. But only in very rare cases. dmesg logs: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Lockdown: hwinfo: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7 Lockdown: modprobe: unsafe module parameters is restricted; see man kernel_lockdown.7 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1052765] New: net-snmp still use SysVinit boot scripts
by bugzilla_noreply＠novell.com 06 Jan '23

06 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1052765 Bug ID: 1052765 Summary: net-snmp still use SysVinit boot scripts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please port the boot script AFAP to systemd units: rpm -ql net-snmp | grep init\\.d /etc/init.d/snmpd /etc/init.d/snmptrapd this because as net-snmp will also reach SLES15 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1160249] New: VNC issues (meta bug)
by bugzilla_noreply＠novell.com 04 Jan '23

04 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1160249 Bug ID: 1160249 Summary: VNC issues (meta bug) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: sndirsch(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- VNC issues (meta bug) -- You are receiving this mail because: You are on the CC list for the bug.

2 61

[Bug 1133423] New: AutoYaST: repository priority not working in add-on section
by bugzilla_noreply＠novell.com 04 Jan '23

04 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1133423 Bug ID: 1133423 Summary: AutoYaST: repository priority not working in add-on section Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: apoulat(a)vitechnology.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 803606 --> http://bugzilla.suse.com/attachment.cgi?id=803606&action=edit add-on.xml Hi, I've just seen that, for example with attached add-on.xml given to AutoYaST, with, as you can see one repository with priority 20 and another with priority 10, they both, after install, have a (default) 99 priority (checked with "zypper -lr -p" command). See documentation about that here: https://doc.opensuse.org/projects/autoyast/#idm139966593990112 Note: I'm not sure on how <product> and <product_dir> tags are relevant then I tried without them and there is still the same issue. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1029961] New: [META] Finalize /bin -> /usr/bin merge
by bugzilla_noreply＠novell.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1029961 Bug ID: 1029961 Summary: [META] Finalize /bin -> /usr/bin merge 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages still install files to /bin that are not symlinks. A "find /bin -type f -exec rpm -qf {} \; | sort -u" on a recent TW yields: bash-4.4-95.1.x86_64 dbus-1-1.10.16-1.1.x86_64 keyutils-1.5.9-5.33.x86_64 ksh-93v-6.15.x86_64 net-tools-deprecated-1.60-770.1.x86_64 procps-3.3.12-3.1.x86_64 psmisc-22.21-6.9.x86_64 rpm-4.13.0.1-1.1.x86_64 sash-3.8-2.8.x86_64 sysvinit-tools-2.88+-103.1.x86_64 tar-1.29-3.1.x86_64 tcsh-6.20.00-3.1.x86_64 util-linux-2.29.1-1.1.x86_64 vim-8.0.324-2.1.x86_64 These packages should all install their binaries to %_bindir, i.e. /usr/bin, and have a symlink in /bin. This would finalize the /bin deprecation. I am opening bugs for each of the packages. Once they are all closed, I'll close this one. -- You are receiving this mail because: You are on the CC list for the bug.

2 67

[Bug 1173619] New: VUL-0: unbound: LPE from unbound to root
by bugzilla_noreply＠suse.com 29 Dec '22

29 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173619 Bug ID: 1173619 Summary: VUL-0: unbound: LPE from unbound to root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: darin(a)darins.net Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- via security(a)suse.de: I believe to have found a configuration issue in the Unbound package. Or, depending on how you look at it, in the Unbound server itself. 1. Before starting the Unbound server, systemd routinely runs unbound-anchor. From 'systemctl cat unbound': ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem As you can see this process is run as user unbound. 2. The Unbound server writes a pid file before dropping privileges, i.e. as root. It then chown's the file in a second step. 'grep username /etc/unbound/unbound.conf': username: "unbound" And from the Unbound source: https://github.com/NLnetLabs/unbound/blob/2a90e8fa1e22aa75d1cf67a1f71ebbf3f… As you can see in the source, Unbound doesn't check if there is already a symbolic link in place of the pid file. 3. openSUSE configures Unbound to create the pid file in a directory owned by the unbound user. 'grep pidfile /etc/unbound/unbound.conf': pidfile: "/var/run/unbound/unbound.pid" 'cat /usr/lib/tmpfiles.d/unbound.conf': D /run/unbound 0755 unbound unbound - 4. unbound-anchor is a nice little "do-one-thing-and-do-it-right" tool. But if it is compromised, and as it has write permission in the pid file directory and reliably runs before the server, an attacker could easily gain full root privileges by just creating a symbolic link /run/unbound/unbound.pid. 5. IMHO this would be best fixed in openSUSE by creating a root owned /run/unbound directory, or changing the pid file path to /run/unbound.pid or something like that. I think this would have the added advantage that openSUSE could ship and maybe enforce the Unbound AppArmor profile used in Debian and Ubuntu: https://gitlab.com/apparmor/apparmor-profiles/-/blob/master/ubuntu/20.04/us… With the current openSUSE setup there is the problem that if AppArmor filters CAP_DAC_OVERRIDE, Unbound has no permission to create a pid file in /run/unbound anymore. If you have questions please don't hesitate to contact me. Thanks for taking a look. Kind regards, Detlef -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1174075] New: Changing %{_libexecdir} breaks some packages which are misusing the macro
by bugzilla_noreply＠suse.com 28 Dec '22

28 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174075 Bug ID: 1174075 Summary: Changing %{_libexecdir} breaks some packages which are misusing the macro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: callumjfarmer13(a)gmail.com Reporter: callumjfarmer13(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a bug to log changes regarding the current major change to the rpm macro %{_libexecdir} which has resulted in many packages breaking where they explicitly call /usr/lib , in these cases the packages are being changed to use %{_prefix}/lib. Most changes to individual packages are being completed by myself. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 1174609] New: Ctrl+Alt+Shift+Del - Keyboard shortcut - logout without confirmation cause crash KDE interface
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174609 Bug ID: 1174609 Summary: Ctrl+Alt+Shift+Del - Keyboard shortcut - logout without confirmation cause crash KDE interface Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ctrl+Alt+Shift+Del - Keyboard shortcut - logout without confirmation cause crash KDE interface Hi OpenSUSE Team, I noticed this bug, which is very annoying. With this KBShortcut, system is unstable. With resume, graphic windows no longer appear. With full restart OS, working correctly KDE. Application: plasmashell (5.19.3) Qt Version: 5.15.0 Frameworks Version: 5.72.0 Operating System: Linux 5.7.9-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20200726" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200726" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20200726" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[opensuse-bugs] [Bug 1178989] New: Multiboot and multiboot2 is supported with Grub2?
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1178989 Bug ID: 1178989 Summary: Multiboot and multiboot2 is supported with Grub2? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi OpenSUSE team, One question: Multiboot and multiboot2 is supported with Grub2? Example: menuentry 'Boot OS from multiboot2' { insmod part_gpt insmod ext2 echo 'Loading OS ...' multiboot2 /boot/os.bin module2 /boot/kernel4os-part1 xxxxxx $(os1 bootargs) module2 /boot/kernel4os-part2 yyyyyy $(os2 bootargs) } Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1175310] New: [Build 20200814] sshd segfault detected
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1175310 Bug ID: 1175310 Summary: [Build 20200814] sshd segfault detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: ionut_n2001(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I observed issue with sshd process. [ 8843.662719] show_signal_msg: 17 callbacks suppressed [ 8843.662721] sshd[4304]: segfault at 2f8 ip 0000559d32402543 sp 00007ffcdba998d0 error 4 in sshd[559d323c0000+74000] [ 8843.662726] Code: 1f 84 00 00 00 00 00 48 85 ff 0f 84 d7 00 00 00 41 54 55 48 89 fd 48 83 ec 08 48 8b 87 20 01 00 00 48 85 c0 0f 84 95 00 00 00 <8b> 40 18 a8 02 75 46 a8 04 0f 85 8e 00 00 00 48 8b 7d 08 e8 15 f0 ... [62657.009387] perf: interrupt took too long (4995 > 4990), lowering kernel.perf_event_max_sample_rate to 40000 [82262.104123] sshd[19593]: segfault at 418 ip 000055bb76f51543 sp 00007ffc0097d0e0 error 4 in sshd[55bb76f0f000+74000] [82262.104157] Code: 1f 84 00 00 00 00 00 48 85 ff 0f 84 d7 00 00 00 41 54 55 48 89 fd 48 83 ec 08 48 8b 87 20 01 00 00 48 85 c0 0f 84 95 00 00 00 <8b> 40 18 a8 02 75 46 a8 04 0f 85 8e 00 00 00 48 8b 7d 08 e8 15 f0 # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20200814" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20200814" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20200814" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" # uname -a Linux os1 5.7.12-1.g9c98feb-default #1 SMP Sat Aug 1 06:18:58 UTC 2020 (9c98feb) x86_64 x86_64 x86_64 GNU/Linux # zypper ls # | Alias | Name | Enabled | GPG Check | Refresh | Type ---+--------------------------------------+--------------------------------------------+---------+-----------+---------+------- 1 | Emulators | Emulators (openSUSE_Tumbleweed) | Yes | (r ) Yes | No | rpm-md 2 | Emulators_Wine | Wine (openSUSE_Tumbleweed) | Yes | (r ) Yes | Yes | rpm-md 3 | Google-Chrome | Google-Chrome | Yes | (r ) Yes | No | NONE 4 | dvd | dvd | Yes | (r ) Yes | Yes | NONE 5 | games | games | Yes | (r ) Yes | No | NONE 6 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | rpm-md 7 | home_tiwai_kernel_5.7 | Kernel builds for branch stable (standard) | Yes | (r ) Yes | No | rpm-md 8 | https-download.opensuse.org-412f9ba1 | openSUSE:Factory | Yes | (r ) Yes | Yes | rpm-md 9 | https-download.opensuse.org-49569944 | utilities | Yes | (r ) Yes | Yes | rpm-md 10 | https-download.opensuse.org-589e1d6c | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes | rpm-md 11 | https-download.opensuse.org-7bdb3480 | https-download.opensuse.org-7bdb3480 | Yes | (r ) Yes | Yes | rpm-md 12 | https-download.opensuse.org-ff31ee0b | home:Dead_Mozay | Yes | (r ) Yes | Yes | rpm-md 13 | https-download.opensuse.org-ff3ec87b | devel:languages:go | Yes | (r ) Yes | Yes | rpm-md 14 | mozilla | mozilla | Yes | (r ) Yes | Yes | NONE 15 | openSUSE-20200810-0 | openSUSE-20200810-0 | No | ---- | ---- | rpm-md 16 | packman | packman | Yes | (r ) Yes | Yes | NONE 17 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | NONE 18 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | NONE 19 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | NONE 20 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | NONE 21 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | NONE 22 | snappy | snappy | Yes | (r ) Yes | Yes | NONE 23 | sublime-text | Sublime Text - x86_64 - Stable | Yes | (r ) Yes | Yes | NONE 24 | vscode | vscode | Yes | (r ) Yes | No | NONE # rpm -qa | grep ssh libssh-config-0.9.4-1.3.x86_64 libssh4-0.9.4-1.3.x86_64 libssh2-1-1.9.0-2.4.x86_64 sshfs-3.7.0-1.2.x86_64 ksshaskpass5-5.19.4-1.1.x86_64 ksshaskpass5-lang-5.19.4-1.1.noarch openssh-8.3p1-1.2.x86_64 openssh-helpers-8.3p1-1.2.x86_64 openssh-askpass-gnome-8.3p1-1.1.x86_64 libssh4-32bit-0.9.4-1.3.x86_64 sshpass-1.06-1.11.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

← Newer
1
2
3
4
5
6
7
...
351
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs February 2021