September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1144543] [Build 20190805] Migration from SFW2 to firewalld: disabled
by bugzilla_noreply＠suse.com 10 Sep '21

10 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1144543 https://bugzilla.suse.com/show_bug.cgi?id=1144543#c41 --- Comment #41 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: upgrade_Leap_42.2_kde https://openqa.opensuse.org/tests/1909888 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190144] New: rpc.gssd segfault on mounting nfs4-share
by bugzilla_noreply＠suse.com 10 Sep '21

10 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190144 Bug ID: 1190144 Summary: rpc.gssd segfault on mounting nfs4-share Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: simo.hakanen(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 Build Identifier: Mount in /etc/fstab or manual mount causes rpc-gssd service to die due to segfault. I have a kerberized nfs-server and mounts used to work correctly in the beginning of August, so I suspect that the problem started after update to nfs-client-2.5.4-25.1.x86_64. I'm running MicroOs but rolling back the snapshots doesn't help, the problem persists. This prevents the use of any podman container that uses nfs-mount volumes. Reproducible: Always Steps to Reproduce: 1. Have working kerberized nfs4-server with shares 2. Check that rpc-gssd.service is running on client 3. Mount a share from the server, e.g. mount.nfs4 server.domain:/ /mnt -o sec=krb5 Actual Results: Remote share is mounted and accessible Expected Results: Rpc-gssd.service dies due to segfault and share is not mounted laura:~ # uname -a Linux laura 5.13.13-1-default #1 SMP Fri Aug 27 08:52:15 UTC 2021 (6339fac) x86_64 x86_64 x86_64 GNU/Linux laura:~ # rpm -qa | grep -e nfs-client -e libtirpc -e rpcbind nfs-client-2.5.4-25.1.x86_64 rpcbind-1.2.6-2.1.x86_64 libtirpc3-1.3.2-1.3.x86_64 libtirpc-netconfig-1.3.2-1.3.x86_64 rpc-gssd.service status after laura:~ # systemctl status rpc-gssd.service �� rpc-gssd.service - RPC security service for NFS client and server Loaded: loaded (/usr/lib/systemd/system/rpc-gssd.service; static) Drop-In: /usr/lib/systemd/system/rpc-gssd.service.d ��options.conf Active: inactive (dead) since Fri 2021-09-03 08:53:44 EEST; 10s ago Process: 690 ExecStart=/usr/sbin/rpc.gssd $GSSD_OPTIONS (code=exited, status=0/SUCCESS) Main PID: 691 (code=killed, signal=SEGV) CPU: 8ms GSSD_OPTIONS='-v -v -v -v -r -r -r -r -M' Line in dmesg traps: rpc.gssd[1475] general protection fault ip:7ff8d98210b7 sp:7ff8d8a7f468 error:0 in libc-2.33.so[7ff8d96e4000+14d000] -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠suse.com 10 Sep '21

10 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1063638 https://bugzilla.suse.com/show_bug.cgi?id=1063638#c268 --- Comment #268 from openQA Review <openqa-review(a)suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: system_performance@ppc64le-2g https://openqa.suse.de/tests/7029755 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190314] New: nextcloud does not support major version jumps
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190314 Bug ID: 1190314 Summary: nextcloud does not support major version jumps 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: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, nextcloud is a fast-moving project. However, it does not allow a user to upgrade from version N to N+2. You need to install intermediate releases and follow the upgrade procedure. The issue is that nextcloud in OpenSUSE (Tumbleweed) only keeps the latest package. It would be interesting to keep a copy of that package before applying a major upgrade to the package (i.e.: nextcloud20, nextcloud21...). Eventually a broken dependency will break these older packages but, until then, it will provide an upgrade path for users. I created that myself sniffing trhough the nextcloud package revision (https://build.opensuse.org/project/show/home:luizluca:branches:openSUSE:Fac…) but I think that is something to be provided by default for any nextcloud admin. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1190273] New: Unzip thinks some files are symlinks
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190273 Bug ID: 1190273 Summary: Unzip thinks some files are symlinks Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: echotangocharlie(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a bug in unzip that sometimes causes files to be converted to symlinks. This can be reproduced with the following archive: https://github.com/shopware/platform/archive/5c5f5d9b0d502dc104eee89456d1b0… I was able to reproduce it on Leap 15.3 and someone else on the mailing list reproduced it with Tumbleweed. With the above archive, the following symlinks are created: ./bin/console ./src/Storefront/Resources/app/storefront/dist/assets/icon/default/editor-redo.svg ./easy-coding-standard.php This may be related to a bug first reported in Debian in 2013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717029 The package was uploaded for testing here: https://build.opensuse.org/package/show/home:glaubitz:branches:Archiving/un… Kira M. Backes originally posted about this bug to the mailing list and provided a link to the archive which can reproduce the bug. John Paul Adrian Glaubitz reproduced it on Tumbeweed, tracked down the Debian bug report, and uploaded the package for testing. The mailing list discussion is here: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… I hope mentioning their names was not a breach of etiquette, but since the mailing list is public, I��ve erred on the side of giving them credit. I noticed that in all cases the symlinks point to a file in the same folder with a filename consisting of the text content of the original file. For example, the original easy-coding-standard.php file only contained the text ��ecs.php�� and the symlink points to a file with the name ecs.php in the same folder. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1190353] New: X11 Forwarding is not working
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190353 Bug ID: 1190353 Summary: X11 Forwarding is not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: ondrej.hrstka(a)iba-group.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fresh installed openSUSE 15.3 with updates. In /etc/ssh/sshd_config, have: X11Forwarding yes No firewall enabled. Installed gvim. > ssh -X -Y <suse15.host> > gvim E233: cannot open display Press ENTER or type command to continue E852: The child process failed to start the GUI Press ENTER or type command to continue > echo $DISPLAY > export DISPLAY=localhost:10.0 > gvim E233: cannot open display Press ENTER or type command to continue E852: The child process failed to start the GUI Press ENTER or type command to continue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172262] spampd does not start on boot
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1172262 https://bugzilla.suse.com/show_bug.cgi?id=1172262#c6 Peter Varkoly <varkoly(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Peter Varkoly <varkoly(a)suse.com> --- Allready fixed in v3.4.6 in factory and v3.4.5 in leap 15.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190267] zypper package lock not work on autoupdate from gui?
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190267 https://bugzilla.suse.com/show_bug.cgi?id=1190267#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vinrarus(a)meta.ua Flags| |needinfo?(vinrarus(a)meta.ua) --- Comment #1 from Michael Andres <ma(a)suse.com> --- Please attach: /var/log/zypp/history /var/log/pk_backend_zypp The history file should reveal who installed the package (and when). The updater applet usually uses packagekit (not zypper) to update the system. The pk_backend log may contain some hint. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183521] [Build 20210312] openQA test fails in transactional_update
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183521 http://bugzilla.opensuse.org/show_bug.cgi?id=1183521#c5 --- Comment #5 from Ignaz Forster <iforster(a)suse.com> --- This bug had been fixed (a long time ago) in transactional-update 3.3.0: The link to the RPM database is created as a relative link now. The workdir issue is a bit more tricky, as we can't fix the old transactional-update version. The bug was triggered when using an old transactional-update version < 3.0, explicitly stating --no-selfupdate, on a snapshot created with a transactional-update version >= 3.0; the *old* transactional-update would fail to recognize the /etc overlay due to a changed path of the workdir and not create a new overlay for this snapshot. The *new* transactional-update will then fail to use that snapshot due to the missing overlay for the snapshot. Support for snapshots without corresponding overlay has been added meanwhile, so the problem should at least fix itself. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190348] New: Bluetooth adapter don't work after zypper dup (few time ago)
by bugzilla_noreply＠suse.com 09 Sep '21

09 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190348 Bug ID: 1190348 Summary: Bluetooth adapter don't work after zypper dup (few time ago) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: matimaone(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- before i upgrade the opensuse tumbleweed the Bluetooth adapter work fine, but after the upgrade i can work with it: the problem now is the lsusb didn't show it i try different port but without success, and if i turn the system to windows as example the adapter work normally information about the Bluetooth adapter: T7-5 Bluetooth-compatible 5.0 Adapter USB Wireless Transmitter Receiver Music Audio for PC TV Car Hands-free 3.5mm AUX Adaptador -- You are receiving this mail because: You are on the CC list for the bug.

1 0