openSUSE Bugs June 2020

bugs@lists.opensuse.org

1 participants
3968 discussions

[Bug 1167780] New: MicroOS images don't update grub if booted without EFI
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1167780 Bug ID: 1167780 Summary: MicroOS images don't update grub if booted without EFI Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kubic-bugs(a)opensuse.org Found By: --- Blocker: --- The .qcow2 images are meant to work fine on systems with EFI (optionally secure boot) and without, so they have both i386-pc and x86_64-efi targets of grub2 installed by kiwi during image building. Kiwi sets LOADER_TYPE="grub2-efi" for this. When booting the image without EFI though, this is not changed by anything and so update-bootloader only manages the x86_64-efi target of grub2. As the grub.cfg file is in the same location, there aren't any immediate issues, but it means that grub is never updated in those deployments. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[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 1172519] New: create_dirs_from_rpmdb needs rpm cookie
by bugzilla_noreply＠suse.com 25 Dec '22

25 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172519 Bug ID: 1172519 Summary: create_dirs_from_rpmdb needs rpm cookie Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- create_dirs_from_rpmdb relies on rpmdbCookie() which is not available on 15. We need some alternate method (or a backport in rpm) on 15 to avoid walking the whole rpmdb on each boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1106751] New: iptables does not work with kernel-default-base
by bugzilla_noreply＠novell.com 23 Dec '22

23 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1106751 Bug ID: 1106751 Summary: iptables does not work with kernel-default-base Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initially reported as https://github.com/kubic-project/automation/pull/474#issuecomment-417329301 Docker (and cri-o) do not work in Kubic VM images as iptables does not work: g47:~ # iptables -L iptables: No chain/target/match by that name. -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 1114673] New: New UI for firewalld: interface not assigned to the right zone when changed to public in first run
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1114673 Bug ID: 1114673 Summary: New UI for firewalld: interface not assigned to the right zone when changed to public in first run Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jeriveramoya(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Interface is not assigned to the right zone after following steps: - Open new UI for firewalld: yast2 firewall - Assign interface to different zone (for example public) - In Zones, set different zone (for example trusted) as default. - Accept - Check with firewall-cmd interface assignation: firewall-cmd --list-interfaces --zone=public | grep ens4 (is not there) but firewall-cmd --list-interfaces --zone=trusted | grep ens4 (it succeeds and it is pointing to the default zone not the one that was assigned) (same result also after trying a firewall-cmd --reload) Assignation works in general, but in this combination and just when the user enters first to this screen and set previous steps, does not work (perhaps some wrong initialization). Expected result: Point to the interface that is assigned in the UI (in the example, to public) -- You are receiving this mail because: You are on the CC list for the bug.

2 32

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1165294] New: haveged is marked as deleted after reboot
by bugzilla_noreply＠novell.com 21 Dec '22

21 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1165294 Bug ID: 1165294 Summary: haveged is marked as deleted after reboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hpj(a)urpla.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, *After reboot*, a couple of my TW systems show: $ zyp ps Verbosity: 2 Checking for running processes using deleted libraries... The following running processes use deleted files: PID | PPID | UID | User | Command | Service | Files ----+------+-----+------+-------------------+--------- +------------------------------ 531 | 1 | 0 | root | haveged (deleted) | haveged | /lib64/ld-2.31.so | | | | | | /lib64/libc-2.31.so | | | | | | /usr/sbin/haveged (deleted) | | | | | | /usr/lib64/libhavege.so.1.1.0 You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. No core libraries or services have been updated. Reboot is probably not necessary. Marcus Meissner noted on the factory ML, that: > It is ran in the initrd and probably still running after transition to the > regular system. > > (Likely pulled in via dracut-fips module) Shouldn't a transition from initrd to regular operation include a restart of this service then? -- You are receiving this mail because: You are on the CC list for the bug.

2 7

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs June 2020