January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1214420] [LXQt]compton-conf / picom
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1214420 https://bugzilla.suse.com/show_bug.cgi?id=1214420#c8 Shawn Dunn <sfalken(a)cloverleaf-linux.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #8 from Shawn Dunn <sfalken(a)cloverleaf-linux.org> --- picom-conf is now packaged, and accepted into :Factory, should be in the next TW snapshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217496] Roundcube smtp error() due to obsolete configuration option.
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217496 https://bugzilla.suse.com/show_bug.cgi?id=1217496#c8 --- Comment #8 from Joseph Acquisto <joea(a)j4computers.com> --- I'm certain it was a fresh install via YAST. Please allow me a few days to install a fresh 15.5 on a new VM and install those packages and look it over. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217496] Roundcube smtp error() due to obsolete configuration option.
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217496 https://bugzilla.suse.com/show_bug.cgi?id=1217496#c7 --- Comment #7 from Lars Vogdt <lars.vogdt(a)suse.com> --- Thanks for the feedback. I checked the package (available in openSUSE:Backports:SLE-15-SP5:Update/roundcubemail aka https://build.opensuse.org/package/show/openSUSE:Maintenance:18166/roundcub… ) and also the released binary RPM (available in http://download.opensuse.org/update/leap/15.5/backports/noarch/roundcubemai… ). What wonders me: we ship the official config.php(.sample), that is also provided by Roundcube upstream. There is no 'smtp_port' config option in the whole config sub-directory. My suspicion would be an upgraded Roundcubemail package. But you are talking about a new installation via Yast, so I have currently not a single idea how this can happen. Can you please verify that this is really a fresh installation and not an update/upgrade? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181762] grub2-xen ignores standard /boot/grub/grub.conf location
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1181762 don matheson <don.matheson(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |don.matheson(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217496] Roundcube smtp error() due to obsolete configuration option.
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1217496 https://bugzilla.suse.com/show_bug.cgi?id=1217496#c6 --- Comment #6 from Joseph Acquisto <joea(a)j4computers.com> --- Sorry for the confusion. ~# rpm -q roundcubemail roundcubemail-1.6.4-bp155.2.6.1.noarch ~# rpm -qi roundcubemail | grep Distribution Distribution: SUSE Linux Enterprise 15 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1216061] New: Syntax error in update_postmaps script
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216061 Bug ID: 1216061 Summary: Syntax error in update_postmaps script 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: noreply.section+dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- If POSTFIX_UPDATE_MAPS="no" in /etc/sysconfig/postfix, starting postfix generates the error: /usr/lib/postfix/systemd/update_postmaps: line 14: return: can only `return' from a function or sourced script -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218771] New: microphone not working in video conferencing after updating libaom3 a/o libfstrm0
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218771 Bug ID: 1218771 Summary: microphone not working in video conferencing after updating libaom3 a/o libfstrm0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: heiko.rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: Other Blocker: --- After having applied these two packages updates from the internal test channel libaom3-3.2.0-150400.3.3.1 libfstrm0-0.6.1-150300.9.5.1 video conferencing doesn't seem to transport my microphone input (tested both Google Meet and Microsoft Teams). When using pavucontrol on my XFCE desktop, I however can see that the microphone is turned on and operational and recording levels are proper. It is only that the input is not streamed back to other participants in the video conference. When reverting to the previous versions libaom3-3.2.0-150400.1.8 libfstrm0-0.6.1-150300.9.3.1 the issue disappears. I have not yet bisected which of these two is the culprit. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219107] New: Migrate away from update-alternatives (phase 1)
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219107 Bug ID: 1219107 Summary: Migrate away from update-alternatives (phase 1) 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: martin.schreiner(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Following the mailing list thread: https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/… And the summarised view of the discussion, as presented on the Wiki: https://en.opensuse.org/openSUSE:Update-alternatives_migration We'd like to keep pushing for libalternatives to be adopted, replacing update-alternatives where feasible, leaving the door open for certain packages to use Conflicts and/or systemd units where applicable. This will have to be considered on a case-by-case basis, but for the majority of packages, libalternatives should work just fine, as it supports setting default binaries and manpages tied to a particular alternative choice. I therefore propose the following: Phase 1) We identify common packaging patterns regarding the update-alternatives -> libalternatives migration. For instance, some packages are fairly straightforward, and do not require regular files to be changed based on an alternative setting. They may not even provide different manpages. Some packages do provide different manpages based on a given alternative. And some packages provide different arbitrary files based on alternative. We'll document and provide examples on OBS/IBS as to how these should be handled. Phase 2) We communicate. Word needs to get out. Everyone doing packaging should be aware that update-alternatives is being slowly phased out. Labs Conference may be a good place to spread the word. We also need to let our users know what's going on. The Tumbleweed announcement blog, the mailing list, even Reddit, all of these could play a role. We'll explain our rationale and try to prevent any backlash from the community. If anyone provides valuable feedback, we'll approach carefully, openly, always keeping the project's best interest at heart. Phase 3) We make ourselves available. Should anyone need help, or any particularly tricky migration require our help, we can be counted on. When I say "we", I mean any developer who's interested in this migration and is willing to help our efforts. Of course the Pack team plays a special role, but anyone interested is more than welcome to be a part of this. This is a sizable change. We need to stick together. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1216604] [Build 20231025] graphicsMagick: config file references ghostscript fonts - but does not trigger installation
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1216604 https://bugzilla.suse.com/show_bug.cgi?id=1216604#c4 --- Comment #4 from Petr Gajdos <pgajdos(a)suse.com> --- Perhaps we could introduce type-dejavu.mgk for example? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215538] systemd-sysusers fails when upgrading packages on WSL with Failed to take /etc/passwd lock
by bugzilla_noreply＠suse.com 26 Jan '24

26 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1215538 https://bugzilla.suse.com/show_bug.cgi?id=1215538#c11 --- Comment #11 from Thorsten Kukuk <kukuk(a)suse.com> --- For the user creation part I think we should better enhance the sysuser-tools script to use the fallbacks in the case systemd fails, too. Will try to look at it after my sick leave. -- You are receiving this mail because: You are on the CC list for the bug.

1 0