April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1222946] New: raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 Bug ID: 1222946 Summary: raise default inotify instance limit Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- especially when running Unison, I quite often experienced the following error: `Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")` Running "strace unison-fsmonitor" yielded: ``` fcntl(0, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(0, F_SETFL, O_RDWR|O_NONBLOCK) = 0 fcntl(1, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK) fcntl(1, F_SETFL, O_RDWR|O_NONBLOCK) = 0 inotify_init() = -1 EMFILE (Too many open files) fcntl(-1, F_GETFL) = -1 EBADF (Bad file descriptor) write(2, "Fatal error: exception Unix.Unix"..., 71Fatal error: exception Unix.Unix_error(Unix.EBADF, "set_nonblock", "")) = 71 exit_group(2) = ? +++ exited with 2 +++ ``` Sometimes closing open IDEs or Firefox has helped, but the culprit seems to be the standard value of fs.inotify.max_user_instances = 128 After doubling the number, I was able to use Unison, again. Others have observed this issue, too: https://intellij-support.jetbrains.com/hc/en-us/articles/15268110231826-Ino… ---quote For an intelligent IDE, it is essential to be in the know about any external changes in files it working with - e.g. changes made by VCS, or build tools, or code generators, etc. For that reason, the IntelliJ platform spins a background process to monitor such changes. The method it uses is platform-specific, and on Linux, it is the Inotify facility. Before operating, inotify requires an "instance" to be initialized. While the default per-user limit of instances used to be high enough, a growing number of programs that also use inotify may lead to instance shortage - in which case file watcher will be unable to start. If this is the case, the limit may be temporarily increased by the following command: sudo sh -c "echo 256 > /proc/sys/fs/inotify/max_user_instances" Don't forget to restart the IDE afterward. ---quote My workaround at present is: `sysctl -w fs.inotify.max_user_instances=256 >> /etc/sysctl.d/unison.conf` This is also documented at https://github.com/bcpierce00/unison/issues/1019 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1220892] YaST with systemd-boot: most kernel options are missing
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220892 https://bugzilla.suse.com/show_bug.cgi?id=1220892#c1 --- Comment #1 from Stefan Schubert <schubi(a)suse.com> --- PRs are on the way: https://github.com/yast/yast-bootloader/pull/700 https://github.com/yast/yast-installation/pull/1116 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222187] New: Cooling fans don't spins up on rx580
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222187 Bug ID: 1222187 Summary: Cooling fans don't spins up on rx580 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs(a)suse.de Reporter: artem.ivanov(a)syntlabs.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After upgrading, my fans eventually stops working anymore on my rx580 from china. After I saw it, i tested on a new arch linux and old build of tumbleweed. Its works normally only on old build. Manual mode don't change anything at all. Setting up kernel option on starting acpi=off too. Any software, what may mess with fans, removed, and nothing changed. Reproducible: Always Steps to Reproduce: 1.Start PC 2.Wait until 85+ C 3.Check temp Actual Results: Cooling fans don't activate. Expected Results: Cooling fans should keep the CPU temperature at around 20-40C -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1223090] [Build 20240417] openQA test fails in await_install: Installation of package filesystem failed
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223090 https://bugzilla.suse.com/show_bug.cgi?id=1223090#c18 --- Comment #18 from Dominique Leuenberger <dimstar(a)opensuse.org> --- For reference: the test passed openQA: https://openqa.opensuse.org/tests/4109573 IMHO the package should still be changed to install its files to /usr/lib directly instead of relying other packages timely putting the lib -> usr/lib symlink in place -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222946] raise default inotify instance limit
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222946 https://bugzilla.suse.com/show_bug.cgi?id=1222946#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- The default value is hardcoded to 128 even in the latest upstream code, and I see no big gain to have an extra kernel config for defining it when an easy tuning knob with sysctl is already present. I bet the suggestion to the upstream would be declined by that reason, too. You can statically set the value in /etc/sysctl.d/* instead. e.g. unison package may contain such a sysctl snippet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223419] Issue installing MediaTomb-0.12.1
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223419 https://bugzilla.suse.com/show_bug.cgi?id=1223419#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |Andreas.Stieger(a)gmx.de Status|NEW |RESOLVED --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Packman package. Contact packman. http://packman.links2linux.org/package/mediatomb http://packman.links2linux.org/help https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org/threa… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223361] Enabling nextcloud-desktop virtual file system requires manual hackery
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223361 https://bugzilla.suse.com/show_bug.cgi?id=1223361#c10 --- Comment #10 from Johannes Studt <johannes(a)studt.de> --- (In reply to Atri Bhattacharya from comment #8) > Maybe it is your sync server that may be working slower than usual or > something network related. Please let me know if the problem persists. Could > just be an issue with 3.13.0 itself. I updated NC to the just now released 28.0.5, restarted php-fpm and apache2 und tried again, and it just works now. Please excuse the confusion. Now I only have one “micro-issue”, but I may open a new report for that: NC Client recreates the old config directory ~/.local/share/Nextcloud at every startup and creates the file Cloud_sync.log in it. When restarting, NC Client tries to migrate the incorrectly recognized old installation to ~/.config/Nextcloud, but of course this fails. > hannes@cadpc:~> nextcloud > nextcloud.gui.application: Migrating old config from "/home/hannes/.local/share/Nextcloud” to “/home/hannes/.config/Nextcloud” > nextcloud.gui.application: Failed to move the old config directory to its new location ( “/home/hannes/.local/share/Nextcloud” to “/home/hannes/.config/Nextcloud” ) > nextcloud.gui.application: Will move the individual files () Apart from that cosmetic failure, everything works fine. :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1205042] [TRACKERBUG] Set OpenSSL 3.0 as the default openssl in TW
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1205042 https://bugzilla.suse.com/show_bug.cgi?id=1205042#c75 --- Comment #75 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-FU-2024:1448-1: An update that solves one vulnerability, contains one feature and has two fixes can now be installed. Category: feature (low) Bug References: 1205042, 1212757, 1217782 CVE References: CVE-2020-25657 Jira References: PED-68 Maintenance Incident: [SUSE:Maintenance:33320](https://smelt.suse.de/incident/33320/) Sources used: openSUSE Leap 15.4 (src): python-M2Crypto-0.40.0-150400.3.9.1 openSUSE Leap 15.5 (src): python-M2Crypto-0.40.0-150400.3.9.1 Python 3 Module 15-SP5 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1212757] python-M2Crypto MiscSSLClientTestCase.test_server_simple_timeouts test fails with HZ=300
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1212757 https://bugzilla.suse.com/show_bug.cgi?id=1212757#c11 --- Comment #11 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-FU-2024:1448-1: An update that solves one vulnerability, contains one feature and has two fixes can now be installed. Category: feature (low) Bug References: 1205042, 1212757, 1217782 CVE References: CVE-2020-25657 Jira References: PED-68 Maintenance Incident: [SUSE:Maintenance:33320](https://smelt.suse.de/incident/33320/) Sources used: openSUSE Leap 15.4 (src): python-M2Crypto-0.40.0-150400.3.9.1 openSUSE Leap 15.5 (src): python-M2Crypto-0.40.0-150400.3.9.1 Python 3 Module 15-SP5 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): python-M2Crypto-0.40.0-150400.3.9.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223361] Enabling nextcloud-desktop virtual file system requires manual hackery
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1223361 https://bugzilla.suse.com/show_bug.cgi?id=1223361#c9 --- Comment #9 from Atri Bhattacharya <badshah400(a)gmail.com> --- Realised that(In reply to Atri Bhattacharya from comment #8) > (In reply to Johannes Studt from comment #7) > > (In reply to Atri Bhattacharya from comment #6) > > > With this, I consider this feature as completed. > > > > Yes. > > > > Just a short question: You uploaded new packages to your test repository > > yesterday (version 3.13.0-5.1). > > Did you change anything compared to version *-4.1? Since installing this > > version, the sync or the preparation for the first sync after starting the > > client is extremely slow. The log is full of messages > > > Ignoring spurious notification for file XYZ > > Nothing that should cause this. Here is the change from revision 5: > <https://build.opensuse.org/package/rdiff/home:badshah400:nextcloud-desktop- > vfs/nextcloud-desktop?linkrev=base&rev=5> > I realise that you would need to login to see this; anyway the change between revision 4 and 5 is as follows: Index: nextcloud-desktop.changes =================================================================== --- nextcloud-desktop.changes (revision 4) +++ nextcloud-desktop.changes (revision 5) @@ -2,7 +2,7 @@ Wed Apr 24 14:36:05 UTC 2024 - Atri Bhattacharya <badshah400(a)gmail.com> - Split out a nextcloud-desktop-vfs-plugin package. -- Add README.vf.md file outlining steps needed to enable +- Add README.vfs.md file outlining steps needed to enable virtual-file system plugin. ------------------------------------------------------------------- -- You are receiving this mail because: You are on the CC list for the bug.

1 0