June 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1114273] New: Broadband connection established but all packages dropped
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1114273 Bug ID: 1114273 Summary: Broadband connection established but all packages dropped Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tested https://bugzilla.opensuse.org/show_bug.cgi?id=1104571 on 2018.10.31 Tumbleweeed. The same result as on Leap15. All RX and all TX packages are dropped Connection is established, signal strength is good, IP is obtained, Routing is set to default gw received from 4g modem, DNS servers are also received. Cannot even ping gateway. The same setup works as soon as I boot Ubuntu with no different settings in NetworkManager. wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.111.71.20 netmask 255.255.255.248 broadcast 10.111.71.23 inet6 fe80::73fb:926a:b538:f135 prefixlen 64 scopeid 0x20<link> ether 7a:c6:53:8c:bf:03 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 1280 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 42 dropped 0 overruns 0 carrier 0 collisions 0 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1123557] New: network:vpn/openvpn: Bug --suppress-timestamps unneeded in systemd unit file?
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1123557 Bug ID: 1123557 Summary: network:vpn/openvpn: Bug --suppress-timestamps unneeded in systemd unit file? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: max(a)suse.com Reporter: jon.brightwell(a)zpg.co.uk QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: nirmoy.das(a)suse.com Found By: --- Blocker: --- It makes logging hard (no timestamps!) and doesn't seem to affect journalctl. I changed mine to ExecStart=/usr/sbin/openvpn --daemon --writepid /run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf Does it also need a wait so it doesn't spit of these openvpn(a)lab.service: PID file /run/openvpn/lab.pid not readable (yet?) after start: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[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 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 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 1168405] New: adjust issue handling to new agetty
by bugzilla_noreply＠novell.com 20 Dec '22

20 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1168405 Bug ID: 1168405 Summary: adjust issue handling to new agetty 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: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- agetty from util-linux 2.35 (not yet packaged) supports reading issue files from /run and /usr in the following way: if /etc/issue exists: read /etc/issue and /etc/issue.d else if /run/issue exists or /run/issue.d has any files read those else read /usr/lib/issue read /usr/lib/issue.d Moreover, the \4 and \6 escape codes use the first configured interface to print the IP address. That means for the most useful default case we don't need to run the extra code of issue generator to enumerate network interfaces and merge issue files anymore. We can rely on agetty built-in features only. Those who need the extra features to print ssh keys or custom computed stuff could still install issue-generator. So I propose the following change: - don't hard require issue-generator in openSUSE-release - don't ship /etc/issue - ship /usr/lib/issue.d/10-openSUSE.issue with the following content: Welcome to \S{PRETTY_NAME} \S{VERSION_ID} - Kernel \r (\l). \4 \6 -- You are receiving this mail because: You are on the CC list for the bug.

2 5