April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220817] os-update script reboots too much
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220817 https://bugzilla.suse.com/show_bug.cgi?id=1220817#c4 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE Flags|needinfo?(jshand2013@gmail. | |com) | --- Comment #4 from Thorsten Kukuk <kukuk(a)suse.com> --- No answer nor any helpful information, closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220724] New: emacs-x11 and emacs-nox packages break clang
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220724 Bug ID: 1220724 Summary: emacs-x11 and emacs-nox packages break clang 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: dmk(a)dmk.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When emacs is installed, clang++ cannot find the C++ library. To reproduce this: 1. Install emacs. It does not matter whether you install the X or non-X version. 2. Install clang. 3. Try to compile and link a C++ program. ``` $ clang++ hello.cpp /usr/bin/ld: cannot find -lstdc++: No such file or directory clang++: error: linker command failed with exit code 1 (use -v to see invocation) $ ``` The problem: The latest stable, released version of gcc is gcc13. I have this installed. When clang++ is run, it looks for the latest gcc it can find, to use its C++ library. However, both the emacs-x11 and emacs-nox packages depend on gcc14, which is unstable and unreleased. ``` $ zypper info --requires emacs-x11 | grep 14 libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit) $ zypper info --requires emacs-nox | grep 14 libgccjit.so.0(LIBGCCJIT_ABI_14)(64bit) $ ``` Consequently, installing emacs causes gcc14 to be installed. Clang++ then finds this and tries to use it. ``` $ clang++ -v clang version 17.0.6 Target: x86_64-suse-linux Thread model: posix InstalledDir: /usr/bin Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/13 Found candidate GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14 Selected GCC installation: /usr/bin/../lib64/gcc/x86_64-suse-linux/14 Candidate multilib: .;@m64 Selected multilib: .;@m64 $ ``` Since emacs does not require the C++ library, that is not installed. Clang++ tries to use gcc14 and finds libc++ missing. How to fix this: There is an unacceptable workaround. It is possible to work around the problem by installing libstdc++6-devel-gcc14 . The reason this is unacceptable is that then, a stable, released clang depends on an unstable, unreleased gcc installation. It would not be possible to trust the binaries compiled and linked by this configuration. I see a few possible ways to fix it in acceptable ways. Any one of them would work. 1. Do not make emacs-x11 and emacs-nox depend on a gcc14 library. 2. Install unstable, unreleased versions of gcc in a different location so clang++ cannot find them. 3. Modify the clang package not to find unstable, unreleased versions of gcc. -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1222281] wall / write don't work in plasma6
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222281 https://bugzilla.suse.com/show_bug.cgi?id=1222281#c4 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(kukuk(a)suse.com) | --- Comment #4 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Fabian Vogt from comment #1) > It's unrelated to plasma, it's caused by the move away from utmp to using > info from logind. kwrited opens a pty and registers this in utmp, but this > is no longer read by mesg. > > Is there some alternative way already possible? > > Not sure how useful this currently is beyond some rare uses of wall/write. There is no alternative currently, as nearly nobody is interested in it. GNOME e.g. doesn't support wall/write since a very long time, similar for other display manager/desktop systems (if they did create utmp entries at all, they were often broken and don't work for write/wall). Standard answer I got was: Desktop systems are normally booted by the user and don't need the message, remote users get them. I see two possible solutions: 1. sddm forwards the message to the desktop 2. kwrited registers a fake session with systemd-logind Upstream systemd does not like 2. and has some protections against it, and they plan to increase them even. But it should be possible by creating a new process group or so. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1220724] Packages pulling gcc14 (like emacs-x11 and emacs-nox) break clang
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220724 https://bugzilla.suse.com/show_bug.cgi?id=1220724#c33 --- Comment #33 from Richard Biener <rguenther(a)suse.com> --- (In reply to Aaron Puchert from comment #32) > Submit request https://build.opensuse.org/request/show/1164981 adds the > configuration file directories to llvm18. I notice that the directory does not contain the llvm version and the llvm docs do not indicate the config files searched have version specific names. That means the config is shared between installed llvm versions which makes it unsuitable to eventually hardwire a llvm-N -> GCC-M dependence (but that might not have been the intention). It opens up the possibility to have GCCs libstdc++-devel package to populate /etc/clang/clang++.cfg but then this would stick to GCC 7 headers on Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218523] libreoffice: drop libqxp dependency
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218523 https://bugzilla.suse.com/show_bug.cgi?id=1218523#c7 --- Comment #7 from Fridrich Strba <fstrba(a)suse.com> --- https://www.documentliberation.org/ -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218523] libreoffice: drop libqxp dependency
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218523 https://bugzilla.suse.com/show_bug.cgi?id=1218523#c6 --- Comment #6 from Fridrich Strba <fstrba(a)suse.com> --- As a matter of fact: when we created the Document Liberation Project, this was exactly the point of it. We even went in the length to reverse engineer the CorelDraw 1 and 2 formats, not because people were having tons of documents, but for the 1-2 guys that would be stuck with some of them. And we can claim that we are able to open in LibreOffice draw documents from CorelDraw versions that even modern CorelDraw does not open. I can imagine, that the xz fiasco triggers people that will now frenetically look for trimming dependencies. But overreaction will not solve the issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218523] libreoffice: drop libqxp dependency
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218523 https://bugzilla.suse.com/show_bug.cgi?id=1218523#c5 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX CC| |fstrba(a)suse.com --- Comment #5 from Fridrich Strba <fstrba(a)suse.com> --- This is actually the point of the whole Document Liberation Project within The Document Foundation: to be able to open some documents from 20-30 years ago and open them in LibreOffice. That libqxp depends only on the librevenge framework (like libvisio, libcdr, libwpg, libwpd, ....) and on icu, so I see really no reason to carve it out. I am closing this as WONTFIX, since it makes little sense to carve out features only because of the "doubt anyone today has any use of it". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222186] VirtualBox not allowed to access USB devices although user is in vboxusers group
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222186 https://bugzilla.suse.com/show_bug.cgi?id=1222186#c30 T Adams <timothyadams(a)ymail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #30 from T Adams <timothyadams(a)ymail.com> --- Fixed! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217262] strawberry fails to build qfile.h:13:10: fatal error: filesystem: No such file or directory
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1217262 https://bugzilla.suse.com/show_bug.cgi?id=1217262#c2 Jonas Kvinge <jonaski(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Jonas Kvinge <jonaski(a)opensuse.org> --- Already fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222194] kubo ipfs tries to start before the network appears and fails with an error
by bugzilla_noreply＠suse.com 05 Apr '24

05 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1222194 https://bugzilla.suse.com/show_bug.cgi?id=1222194#c2 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- It should be fixed with the 0.27.0 version in the next Tumbleweed snapshot. If it still does not work, please re-open this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0