openSUSE Bugs July 2020

bugs@lists.opensuse.org

1 participants
3563 discussions

[Bug 1174564] New: vim-small has no /usr/bin/vi link
by bugzilla_noreply＠suse.com 27 Dec '22

27 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1174564 Bug ID: 1174564 Summary: vim-small has no /usr/bin/vi link Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The vim-small package does not provide /usr/bin/vi -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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 1173574] New: fwupd Initialize default tcti. ErrorCode (0x000a000a)
by bugzilla_noreply＠suse.com 22 Dec '22

22 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1173574 Bug ID: 1173574 Summary: fwupd Initialize default tcti. ErrorCode (0x000a000a) 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: emiliano.langella(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I noticed the following fwupd errors: # journalctl -u fwupd.service -b -- Logs begin at Thu 2020-04-23 11:28:04 CEST, end at Wed 2020-07-01 09:54:57 CEST. -- Jul 01 09:52:40 kitt systemd[1]: Starting Firmware update daemon... Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:42 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: ERROR:esys:src/tss2-esys/esys_context.c:69:Esys_Initialize() Initialize default tcti. ErrorCode (0x000a000a) Jul 01 09:52:43 kitt fwupd[2846]: 07:52:43:0646 FuEngine failed to add udev device /sys/devices/platform/MSFT0101:00/tpm/tpm0: failed to initialize> Jul 01 09:52:43 kitt systemd[1]: Started Firmware update daemon. # fwupdate -i failed: Error opening file /sys/firmware/efi/efivars/fwupd-34578c72-11dc-4378-bc7f-b643866f598c-0-0abba7dc-e516-4167-bbf5-4d9d1c739416: No such file or directory Laptop: Dell Precision 5520 Tumbleweed: 20200628 # fwupdmgr --version client version: 1.4.2 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.4.2 Let me know if you need any additional info. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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

[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

[Bug 1093592] New: redshift doesn't work after geoclue2 update
by bugzilla_noreply＠novell.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Bug ID: 1093592 Summary: redshift doesn't work after geoclue2 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarcoux(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 770512 --> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit redshift error Hello, I updated to the latest snapshot (2018 05 15) and since then, redshift with geoclue2 doesn't work. After launching, it displays an error (see attachment). This wasn't happening with the previous snapshot I had, but I'm not sure which one. The issue seems to arise due to changes within the recent revisions of the geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I suspect it is in one of those: - 2018 03 04 - 2018 04 24 - 2018 05 11 - 2018 05 13 The workaround is to provide the latitude and longitude manually with the option -l. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1173319] New: Move /etc/logrotate.d/* to /usr/etc/logrotate.d
by bugzilla_noreply＠suse.com 15 Dec '22

15 Dec '22

https://bugzilla.suse.com/show_bug.cgi?id=1173319 Bug ID: 1173319 Summary: Move /etc/logrotate.d/* to /usr/etc/logrotate.d 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: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm currently working on the config file switch /etc --> /usr/etc (find Details on https://en.opensuse.org/openSUSE:Packaging_UsrEtc) and now I'm wondering what should be done with /etc/logrotate.d/* files. Thorsten Kukuk: Somebody need to rewrite logrotate first. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

1 16

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

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs July 2020