January 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1206756] AUDIT-WHITELIST: NetworkManager-iodine: move dbus system.d file to /usr
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

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

1 0

[Bug 1206367] systemd-status-mail does not send mail....
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206367 https://bugzilla.suse.com/show_bug.cgi?id=1206367#c11 --- Comment #11 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Thorsten Kukuk from comment #10) > (In reply to Axel Braun from comment #9) > > > This is a MicroOS Desktop system. > > Create a new bug? > > You did configure mailx but you are using sendmail... > Fix your mail setup on your machine. in /etc/default/systemd-status-mail I have set MAILER=mailx plus MAILX_options. /usr/etc/default/systemd-status-mail is untouched. So why is sendmail used? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206367] systemd-status-mail does not send mail....
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206367 https://bugzilla.suse.com/show_bug.cgi?id=1206367#c10 --- Comment #10 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Axel Braun from comment #9) > This is a MicroOS Desktop system. > Create a new bug? You did configure mailx but you are using sendmail... Fix your mail setup on your machine. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206367] systemd-status-mail does not send mail....
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206367 https://bugzilla.suse.com/show_bug.cgi?id=1206367#c9 --- Comment #9 from Axel Braun <axel.braun(a)gmx.de> --- (In reply to Thorsten Kukuk from comment #8) > - try MAILX_OPTIONS > (https://manpages.opensuse.org/Tumbleweed/systemd-status-mail/systemd-status- > mail.8.en.html) Ah, a new option :-) I have now a working mailx configuration, can send from command line. With mailx-options...... > Your mail setup is not a problem of systemd-status-mail, this tool expects a > working mail setup (like e.g. cron does, too) and is no replacement for it. ....I run into the next error: an 10 11:45:48 localhost.localdomain systemd[1]: Starting Send status mail for test.service... Jan 10 11:45:48 localhost.localdomain systemd-status-mail[14744]: postdrop: fatal: mail_queue_enter: create file maildrop/302666.14744: no permission Jan 10 11:45:48 localhost.localdomain postfix/postdrop[14744]: fatal: mail_queue_enter: create file maildrop/302666.14744: no permission Jan 10 11:45:49 localhost.localdomain systemd-status-mail[14740]: sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 1 Jan 10 11:45:49 localhost.localdomain systemd-status-mail[14740]: sendmail: fatal: root(a)localhost.localdomain(65534): unable to execute /usr/sbin/postdrop -r: Application error Jan 10 11:45:49 localhost.localdomain postfix/sendmail[14740]: warning: command "/usr/sbin/postdrop -r" exited with status 1 Jan 10 11:45:49 localhost.localdomain postfix/sendmail[14740]: fatal: root(a)localhost.localdomain(65534): unable to execute /usr/sbin/postdrop -r: Application error Jan 10 11:45:49 localhost.localdomain systemd[1]: systemd-status-mail(a)test.service.service: Main process exited, code=exited, status=1/FAILURE Jan 10 11:45:49 localhost.localdomain systemd[1]: systemd-status-mail(a)test.service.service: Failed with result 'exit-code'. Jan 10 11:45:49 localhost.localdomain systemd[1]: Failed to start Send status mail for test.service. This is a MicroOS Desktop system. Create a new bug? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206322] [Build 20221211] graphicsMagick fails test suite on i586
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206322 https://bugzilla.suse.com/show_bug.cgi?id=1206322#c28 --- Comment #28 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Petr Gajdos from comment #27) > > ## Expected result > > > > Last good: (unknown) (or more recent) > > So this is a regression or not? Does it mean that it started to fail after > <revert> and (before <revert> and before before <revert>) not? This sounds > fishy a bit. Not really. The i586 version was just never tested and after splitting out i586 from openSUSE:Factory to :LegacyX86 (and having it roll independently) the test suite was slightly increased, where this popped up (hence: last good: unknown) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206980] akonadipop3 times out when retriving mail
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206980 https://bugzilla.suse.com/show_bug.cgi?id=1206980#c6 --- Comment #6 from Fabian Vogt <fvogt(a)suse.com> --- Can you try with IMAP instead of (outdated) pop3? (In reply to Stakanov Schufter from comment #2) > The malfunctions seems to appear random, the program just does not load mail > in automatic any more (or better, the messages you expect are on the imap > client of your smartphone but do not appear in the PC) and then if you push > control manually the program complains. In that scenario pop3 wouldn't work well anyway I'd say. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206937] Enable CONFIG_LRU_GEN_ENABLED by default on x86_64
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206937 https://bugzilla.suse.com/show_bug.cgi?id=1206937#c7 --- Comment #7 from Mel Gorman <mgorman(a)suse.com> --- (In reply to John Doe from comment #5) > (In reply to Michal Hocko from comment #2) > > (In reply to John Doe from comment #0) > > > Enabling MGLRU could give some performance benefits. Right now it is > > > compiled into the kernel but not enabled by default > > > > Do you have any specific usecase in mind or is this more of a "I want to > > play with this new reclaim implementation"? > > No specific use case but others might find this useful due to the > performance benefits. Arch enabled it already and I presume Fedora will have > it enabled when 6.1 reaches Fedora 37 As far as I'm aware, the main benefits have been demonstrated on relatively small machines with desktop-class workloads -- primarily workloads interesting to a chromebook where interactive tasks perform better when the total working set for foreground and background tasks exceeds total memory. That's a less common scenario then what is seen on server class workloads. For example, one of our biggest customers by revenue has applications that carefully size their workload to avoid swapping and reclaim decisions as much as possible and MGLRU would have limited to no benefit. Hence the caution about enabling it by default because it could take years to rattle out the issues. However, the option to enable it and experiment it is available so if a few requests were made based on "Workload X benefits from MGLRU and we should not have to tune it every time" then there would be greater confidence in enabling it by default. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206980] akonadipop3 times out when retriving mail
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206980 https://bugzilla.suse.com/show_bug.cgi?id=1206980#c5 --- Comment #5 from Stakanov Schufter <stakanov(a)disroot.org> --- OK, setting up a brand new account of mailbox org gets the very same timeout with "host not found" but the server does show green (that is username and password were accepted as correct when setting up the server). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206957] lua-lmod Permission denied in init/bash
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206957 https://bugzilla.suse.com/show_bug.cgi?id=1206957#c15 --- Comment #15 from Ludwig Nussel <lnussel(a)suse.com> --- (In reply to Egbert Eich from comment #10) > (In reply to Ludwig Nussel from comment #5) > > No it's not a duplicate. lmod is doing nasty things here and pollutes the > > shell environment via /etc/profile.d/lmod.sh. My strong advice would be not > > do that. Instead there could be eg. only something like an "lmod-activate" > > or "lmod-enter" alias that sources /usr/share/lmod/8.7.15/init/bash *on > > demand* rather than for each and every shell of each and every user. > > This would break every existing job scripts for users. We cannot do this. > 'module load' needs to work in a batch environment from inside shell > scripts. This is why BASH_ENV is set. > Also, it is expected that every (physical) user logging into a system with > Lmod installed will actually need it. On non-HPC systems, the lua-lmod > package should not be installed. There is nothing that prevents lua-lmod from being installed in a normal system. In fact the description sounds very generic and has no reference to specific HPC setups. Introducing a generic command called "module" and even a two letter one, ie "ml" looks rather dangerous to me. How can we as distribution make sure that no other package introduces those commands too? How to make sure noone else uses BASH_ENV for some other magic? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1206980] akonadipop3 times out when retriving mail
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1206980 https://bugzilla.suse.com/show_bug.cgi?id=1206980#c4 --- Comment #4 from Stakanov Schufter <stakanov(a)disroot.org> --- The issue appears only with one provider as the pop3 e.g. with disroot works. But with mailbox.org times out. I will now try to simply erase the account and set it up from the scratch to see if this changes something. I will update you on this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0