July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1210750] KDE:Extra/Digikam 8.x - no sound support
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1210750 https://bugzilla.suse.com/show_bug.cgi?id=1210750#c2 Roland Kummler <rke(a)arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|KDE:Extra/Digikam 8.0.0 - |KDE:Extra/Digikam 8.x - no |no sound support |sound support --- Comment #2 from Roland Kummler <rke(a)arcor.de> --- no improvement with digikam 8.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213721] [SELinux] add SELinux rule for new versions of kdump
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213721 https://bugzilla.suse.com/show_bug.cgi?id=1213721#c2 Jiri Bohac <jbohac(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jbohac(a)suse.com) | --- Comment #2 from Jiri Bohac <jbohac(a)suse.com> --- yes, just read it. See: https://github.com/openSUSE/kdump/blob/master/init/load.sh First, on lines 373 and 374 it is tested that the two files (initrd and kernel) in /var/lib/kdump exist. On line 202 they are passed to kexec. In between that, mkdumprd is called that compares timestamps and possibly regenerates /var/lib/kdump/initrd but that does not seem to be blocked by SELinux. As noted in Comment #0, audit2allow suggested "allow kdump_t kdump_var_lib_t:lnk_file read;" and that works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213714] copy/paste failure between weston and X11
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213714 https://bugzilla.suse.com/show_bug.cgi?id=1213714#c1 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |epistemepromeneur(a)free.fr, | |fvogt(a)suse.com Flags| |needinfo?(epistemepromeneur | |(a)free.fr) --- Comment #1 from Fabian Vogt <fvogt(a)suse.com> --- Works here. Anything useful in the journal? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213627] New: Firewalld and container compatibility leading to not include a firewall by default in Aeon?
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213627 Bug ID: 1213627 Summary: Firewalld and container compatibility leading to not include a firewall by default in Aeon? Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: kjong+lists(a)neobits.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi, I'm intrigued by the Aeon project, but the choice of not installing a firewall by default worries me. I know I can enable the firewall pattern in the installer, or install it later on with `transactional-update package install firewalld`. And that works fine. But not having it there in a default installation opens up certain attack vectors in my opinion. I've read some reasoning about this on online platforms, such as that a firewall is not needed or would mess up container setups. I'm not so sure if I agree to the point of not including a firewall by default. If it's in the way for a user that wants to do something "special", then that user can disable/modify the firewall. But by default it would make sense to have the protection of a firewall. I didn't open this issue to debate it, but to understand the reasoning better. Maybe I'm wrong, that's also possible. Then this would be a nice reference point for future questions. On the firewalld page it mentions compatibility with Podman and Docker (iptables only): > Applications and libraries which support firewalld as a firewall management tool include: > > NetworkManager > libvirt > podman > docker (iptables backend only) > fail2ban I also host a Discourse forum on Debian for a couple of years, which runs in a Docker container, with firewalld enabled. I have not encountered issues so far. It of course depends on the use case of when issues may arise with firewalld. But this is an example of when the firewall would not be an issue and is good to have it around as a layer of protection. One of many layers, as security should be applied. If one layer fails, there is another one to protect the data. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213721] [SELinux] add SELinux rule for new versions of kdump
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213721 https://bugzilla.suse.com/show_bug.cgi?id=1213721#c1 Filippo Bonazzi <filippo.bonazzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jbohac(a)suse.com) Status|NEW |IN_PROGRESS CC| |jbohac(a)suse.com --- Comment #1 from Filippo Bonazzi <filippo.bonazzi(a)suse.com> --- Hi, thanks for opening the bug. I'm currently looking into what the best solution could be. What does kdump need to do with the kernel that is pointed to by the symlink? Will it need to just read it or more than that? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213721] [SELinux] add SELinux rule for new versions of kdump
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213721 Filippo Bonazzi <filippo.bonazzi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |filippo.bonazzi(a)suse.com CC| |filippo.bonazzi(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213620] kernel oops: Unable to handle kernel paging request at virtual address 0000000000001ea0
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213620 https://bugzilla.suse.com/show_bug.cgi?id=1213620#c2 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|kernel-bugs(a)opensuse.org |ivan.ivanov(a)suse.com --- Comment #2 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- It looks like this [1] commit is addressing this crash. 15.4 will need same fix from what I see. [1] efedd01de475e ("KVM: arm64: Warn if accessing timer pending state outside of vcpu context") -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213492] python3-podman-compose.rpm bring 247 packages uneeded
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213492 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kastl(a)b1-systems.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213495] Mariadb: InnoDB: Unable to find charset-collation for X
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213495 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |danilo.spinella(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213615] SuperCollider does not see supercollider-sc3-plugins when installed
by bugzilla_noreply＠suse.com 28 Jul '23

28 Jul '23

https://bugzilla.suse.com/show_bug.cgi?id=1213615 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kv(a)kott.no-ip.biz -- You are receiving this mail because: You are on the CC list for the bug.

1 0