November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203632] LibreOffice fails to print Cantarell
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203632 https://bugzilla.suse.com/show_bug.cgi?id=1203632#c4 Thomas Schraitle <thomas.schraitle(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Thomas Schraitle <thomas.schraitle(a)suse.com> --- Archive still unavailable. Once this is fixed in upstream project we can reopen it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204315] [RPi] Kernel 6.0 - [drm] *ERROR* could not acquire memory range
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1204315 https://bugzilla.suse.com/show_bug.cgi?id=1204315#c32 --- Comment #32 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Yep. Arm servers with EFI don't have DTs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 818373] chattr cannot add compression flags (+c) to some files on btrfs
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=818373 Anya Anya <47f40qm5p(a)relay.firefox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |47f40qm5p(a)relay.firefox.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1161823] New: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported"
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1161823 Bug ID: 1161823 Summary: Adding compress=zstd in fstab option in YaST2 on / partition result in "compression type 0x3 not supported" 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: andythe_great(a)pm.me QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 828281 --> http://bugzilla.opensuse.org/attachment.cgi?id=828281&action=edit Step 1 of installation When installing OpenSUSE TW, by adding compress=zstd in fstab arbitrary option value will result in broken grub "compression type 0x3 not supported" even it grub already support zstd compression on btrfs. Or maybe I did something wrong. Installation process photos were attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 1174939] snapper list on transactional server doesn't show consumed space by snapshots
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1174939 Anya Anya <47f40qm5p(a)relay.firefox.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |47f40qm5p(a)relay.firefox.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202059] AUDIT-0: ruby3.1-rubygem-d-installer: review of D-Bus services org.opensuse.DInstaller (and friends)
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202059 https://bugzilla.suse.com/show_bug.cgi?id=1202059#c18 --- Comment #18 from Martin Vidner <mvidner(a)suse.com> --- With PR https://github.com/yast/d-installer/pull/295 we have fixed the activation and want to bring the service files back. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205246] New: AUDIT-0: rubygem-d-installer: review of D-Bus services org.opensuse.DInstaller*.service
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205246 Bug ID: 1205246 Summary: AUDIT-0: rubygem-d-installer: review of D-Bus services org.opensuse.DInstaller*.service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mvidner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://github.com/yast/d-installer/ , packaged at https://build.opensuse.org/project/show/YaST:Head:D-Installer is built on a D-Bus interface With PR https://github.com/yast/d-installer/pull/295 we have fixed the activation of its handful of services, running them as root, so an audit is needed. The D-Bus policy file is https://github.com/yast/d-installer/blob/master/service/share/dbus.conf and AFAICT it only allows calls from root. OTOH it looks trivially redundant, and RPMlint warns: ruby3.1-rubygem-d-installer.x86_64: W: dbus-policy-allow-receive <allow receive_sender="org.opensuse.DInstaller"/> /usr/share/dbus-1/system.d/org.opensuse.DInstaller.conf ... allow receive_* is normally not needed as that is the default. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1202059] AUDIT-0: ruby3.1-rubygem-d-installer: review of D-Bus services org.opensuse.DInstaller (and friends)
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1202059 https://bugzilla.suse.com/show_bug.cgi?id=1202059#c17 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner(a)suse.com --- Comment #17 from Martin Vidner <mvidner(a)suse.com> --- *** Bug 1205246 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205261] dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205261 https://bugzilla.suse.com/show_bug.cgi?id=1205261#c2 Antonio Feijoo <antonio.feijoo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |dracut-maintainers(a)suse.de --- Comment #2 from Antonio Feijoo <antonio.feijoo(a)suse.com> --- (In reply to Felix Miata from comment #0) > Created attachment 862770 [details] > rdsosreport.txt from TW boot attempt > > Original Summary: > dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in > dracut emergency shell after rsync migration to new GPT system disk > > Initial state: > 1-configured booting & mounting are via LABELs (making UUIDs > administratively unimportant... Have you overridden dracut's default persistent policy "by-uuid" (/etc/dracut.conf.d/10-persistent_policy.conf) to "by-label"? I recommend you to create a new conf snippet with a higher number, because this will be overwritten after a dracut update. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205115] New: After 2022-11-05 opensuse patch/up chrome loses 'follow system theme' after playing video
by bugzilla_noreply＠suse.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205115 Bug ID: 1205115 Summary: After 2022-11-05 opensuse patch/up chrome loses 'follow system theme' after playing video Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: landis.reed(a)yandex.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862682 --> http://bugzilla.opensuse.org/attachment.cgi?id=862682&action=edit how chrome looks with 'theme follow system' at startup, (white) after stop play and after refreshed after zypper patch, zypper up Chrome updated and when i use to view PlexMediaServer, stop playing, the system (KED) theme is gone and colors are transposed. requires page refresh to get 'theme colors' bach. Seems to have to do with the video in chrome. This is brand new (to me) and happened immediately after patch/up 2022-11-05 -- You are receiving this mail because: You are on the CC list for the bug.

1 2