April 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1198155] New: pencil: can not start firefox too new
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1198155 Bug ID: 1198155 Summary: pencil: can not start firefox too new Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: rpm(a)fthiessen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After installing pencil[1] I noticed it can not start because it requires firefox < 52.0. ``` % pencil Error: Platform version '98.0.2' is not compatible with minVersion >= 4.0 maxVersion <= 52.0 ``` So the package is broken on Factory, as there is no old enough firefox available. There is a new version using electron instead of XULrunner, but not sure if it can be packaged: https://github.com/evolus/pencil [1] https://build.opensuse.org/package/show/openSUSE:Factory/pencil -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1195873] Xpra (4.2.3-15.5) "failed to connect" with "received uninterpretable nonsense" when testing on SAME MACHINE
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1195873 http://bugzilla.opensuse.org/show_bug.cgi?id=1195873#c38 --- Comment #38 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1195873) was mentioned in https://build.opensuse.org/request/show/967357 Factory / xpra-html5 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1186158] SElinux is blocking podman socket access to /var/run/podman/podman.sock
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1186158 https://bugzilla.suse.com/show_bug.cgi?id=1186158#c12 --- Comment #12 from Gayane Osipyan <gayane.osipyan(a)suse.com> --- Hi, Thanks for details after doing some research and also replicating this issue on non microos setup with SElinux enabled my understanding is following 1. File provider should be used for rootless podman container+traefik .(For my testing purposes it worked) providers: file: filename: /path/to/config/dynamic_conf.yml 2. SElinux policy can be adjusted locally but seems its strongly not recommended(you can use udica which will generate policy for specific container) 3. run Traefik from a rootfull container. One suggestion I found is to run traefik non-rootfull and use the tcp exposed docker-socket .The dockerproxy has to run rootfull .(Haven't tested this ) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198051] Uninstalling package "gtk4-devel" leaves behind .desktop files for "Icon Browser" and "Print Editor"
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1198051 https://bugzilla.suse.com/show_bug.cgi?id=1198051#c1 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |dimstar(a)opensuse.org Resolution|--- |INVALID --- Comment #1 from Dominique Leuenberger <dimstar(a)opensuse.org> --- Icon browser and print editor live in the package 'gtk4-devel-tools' Uninstalling any other package won't affect their presence -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1195608] YAST status halts from beginning.
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1195608 https://bugzilla.suse.com/show_bug.cgi?id=1195608#c22 --- Comment #22 from Stefan Hundhammer <shundhammer(a)suse.com> --- Pull requests for SLE-15-SP4: https://github.com/yast/yast-packager/pull/609 (yast2-packager-4.4.28) https://github.com/yast/yast-yast2/pull/1250 (yast2-4.4.48) Since this problem affects the installed system, not the installation, an installer self-update for this is purely optional. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171883] VUL-0: CVE-2020-8025: pcp: outdated entries in permissions profiles for /var/lib/pcp/tmp/* may cause security issues
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1171883 Gabriele Sonnu <gabriele.sonnu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coldpool(a)suse.de Flags| |needinfo?(coldpool(a)suse.de) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171883] VUL-0: CVE-2020-8025: pcp: outdated entries in permissions profiles for /var/lib/pcp/tmp/* may cause security issues
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1171883 Gabriele Sonnu <gabriele.sonnu(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gabriele.sonnu(a)suse.com Assignee|ddiss(a)suse.com |coldpool(a)suse.de -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189791] New: btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1189791 Bug ID: 1189791 Summary: btrfs filesystem corruptions with HyperPAV Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: azouhr(a)opensuse.org QA Contact: qa-bugs(a)suse.de CC: ada.lovelace(a)gmx.de Found By: --- Blocker: --- For a proof of concept, I created a machine with 22 3390-54 Disks attached to a single btrfs, cylinder 0 excluded as minidisks. This happened in certain junks of disks (at least 4 at a time). After adding devices, I always did a rebalance of the btrfs. When I added disk 15-18, I also enabled hyperpav (without cylinder 0 on the base devices) as available as feature for z/VM 7.2 (feature also has been added to z/VM). The definition looks like this in the directory: COMMAND DEFINE HYPERPAVALIAS 01C0 FOR BASE 0100 I also added alias devices at addresses 01C1-01C7. However, later on when copying data from that disk, I found quite a number of corruptions within btrfs. After a while the server even crashed, and is now running without hyperpav. Corruptions that already happened are obviously still there, but besides that, the system works without the hangs I experienced before. By chance (don't think that would be the issue), the first disk with corruptions is the 16th disk in the system (including the system disk). And while thinking about this, the disk with number 100 has not been enabled on the system, although all disks are defined to the same control unit. HyperPAV has been used during rebalance of the last 8 disks because dasdstat displayed workload on the PAV device. # btrfs device stats /srv | grep corruption_errs [/dev/dasdb1].corruption_errs 0 [/dev/dasdc1].corruption_errs 0 [/dev/dasdd1].corruption_errs 0 [/dev/dasde1].corruption_errs 0 [/dev/dasdk1].corruption_errs 0 [/dev/dasdj1].corruption_errs 0 [/dev/dasdh1].corruption_errs 0 [/dev/dasdm1].corruption_errs 0 [/dev/dasdf1].corruption_errs 0 [/dev/dasdg1].corruption_errs 0 [/dev/dasdl1].corruption_errs 0 [/dev/dasdi1].corruption_errs 0 [/dev/dasdn1].corruption_errs 0 [/dev/dasdo1].corruption_errs 0 [/dev/dasdp1].corruption_errs 331 [/dev/dasdq1].corruption_errs 303 [/dev/dasds1].corruption_errs 302 [/dev/dasdv1].corruption_errs 399 [/dev/dasdr1].corruption_errs 356 [/dev/dasdt1].corruption_errs 206 [/dev/dasdw1].corruption_errs 279 [/dev/dasdu1].corruption_errs 218 # dmesg | tail [ 6616.004750] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.004755] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 401, gen 0 [ 6616.005008] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 3637248 csum 0x8941f998 expected csum 0xe55a18c7 mirror 1 [ 6616.005013] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 402, gen 0 [ 6616.005238] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.005244] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 403, gen 0 [ 6616.005513] BTRFS warning (device dasdb1): csum failed root 5 ino 40234 off 1818624 csum 0x8941f998 expected csum 0x99cae683 mirror 1 [ 6616.005565] BTRFS error (device dasdb1): bdev /dev/dasdv1 errs: wr 0, rd 0, flush 0, corrupt 404, gen 0 [ 6616.882699] BTRFS warning (device dasdb1): csum failed root 5 ino 40224 off 10055680 csum 0x8941f998 expected csum 0x26222530 mirror 1 [ 6616.882715] BTRFS error (device dasdb1): bdev /dev/dasdu1 errs: wr 0, rd 0, flush 0, corrupt 249, gen 0 # uname -a Linux zlxusr1020 5.12.12-1-default #1 SMP Fri Jun 18 11:07:46 UTC 2021 (0e46a2c) s390x s390x s390x GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1188964] New: inconsistencies between kernel and fuse exfat driver
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

https://bugzilla.suse.com/show_bug.cgi?id=1188964 Bug ID: 1188964 Summary: inconsistencies between kernel and fuse exfat driver 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: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Generating a file with trailing dots works fine using the fuse exfat driver. But after switching to the kernel driver ls reports an error and cannot properly show the file information anymore. Note: Using the kernel driver creating a file with trailing dots generates are file without trailing dots. # mount /dev/sdb1 /mnt/ FUSE exfat 1.3.0 # cd /mnt/ # touch test1 test2... # ll total 0 -rwxrwxrwx 1 root root 0 Aug 2 07:57 test1 -rwxrwxrwx 1 root root 0 Aug 2 07:57 test2... [...] # rpm -e fuse-exfat # mount /dev/sdb1 /mnt/ [...] # ll ls: cannot access 'test2...': No such file or directory total 0 -rwxr-xr-x 1 root root 0 Aug 2 2021 test1 -????????? ? ? ? ? ? test2... -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1196256] New: [Build 20220219] openQA test fails in podman_firewall
by bugzilla_noreply＠suse.com 06 Apr '22

06 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1196256 Bug ID: 1196256 Summary: [Build 20220219] openQA test fails in podman_firewall Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2199485/modules/podm an_firewall/steps/113 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: guillaume.gardet(a)arm.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-JeOS-for-AArch64-aarch64-jeos-containers@aarch64-HD24G fails in [podman_firewall](https://openqa.opensuse.org/tests/2199485/modules/podman_f… The ping test fails. ## Test suite description JeOS as container host. Test container runtimes (podman and docker) and related tools. @jlausuch (2021-11-25): I have removed `BOOT_HDD_IMAGE=1`, since it's irrelevant for JeOS and schedules unwanted modules in main_containers.pm ## Reproducible Fails since (at least) Build [20220210](https://openqa.opensuse.org/tests/2185142) ## Expected result Last good: [20220209](https://openqa.opensuse.org/tests/2182191) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 2