October 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1115112] New: Qt-Creator Documentation is not found out-of-the-box
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1115112 Bug ID: 1115112 Summary: Qt-Creator Documentation is not found out-of-the-box Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: novell(a)howorth.org.uk QA Contact: qa-bugs(a)suse.de CC: gorgoglione(a)gmail.com Depends on: 976384 Found By: --- Blocker: --- In Qt-Creator 4.6.1 from the standard repositories, selecting the first tutorial in the Tutorials page (Build and Run Examples) takes me to a web page <https://doc.qt.io/qtcreator/creator-build-example-application.html> which is for version 4.7.2. That occurs on the first time of clicking on that link. Clicking on it again a day or so later takes me to the installed help pages for 4.6.1, so something is misconfigured in the installed package, and perhaps some of the other button clicking I did in the meantime made the problem go away. Very annoying, and a total waste of my time. PS Why is openSUSE Leap 15.0 not listed in the options for OS when reporting a bug? -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 976384] New: Qt-Creator Documentation is not found out-of-the-box
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=976384 Bug ID: 976384 Summary: Qt-Creator Documentation is not found out-of-the-box Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gorgoglione(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In Qt-Creator 3.6.0, selecting Help -> Contents from menu, the following error message is displayed: The page could not be found Error loading: qthelp://org.qt-project.qtcreator.360/doc/index.html Check that you have the corresponding documentation set installed. Probably the documentation it's not installed into the default folder and Qt-Creator configuration was not updated to point to the right location. The fix which worked for me was to select Tools -> Options... -> Help -> Documentation -> Add, and select the following file: /usr/share/doc/packages/libqt5/qtcreator.qch -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1065388] New: apparmor is breaking tool file in lessopen.sh
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1065388 Bug ID: 1065388 Summary: apparmor is breaking tool file in lessopen.sh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tracing lessopen.sh with export LESS_ADVANCED_PREPROCESSOR=yes shows [...] ++ file -L ./less.1 + type='./less.1: writable, regular file, no read permission' but it should be noether less/less-487> file -L ./less.1 ./less.1: troff or preprocessor input, ASCII text in /etc/apparmor.d/usr.bin.lessopen.sh I found /usr/bin/file rix, but no rule for /usr/bin/file its self! All tools listed in /etc/apparmor.d/usr.bin.lessopen.sh should be able to read files as otherwise nothings goes. -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1187137] New: Syntax error in qtconcurrent header
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1187137 Bug ID: 1187137 Summary: Syntax error in qtconcurrent header Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: uhhadd(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: andresbs2000(a)protonmail.com Found By: --- Blocker: --- This causes anything including QtConcurrent to fail to build with the following message or similar: [ 67s] ERROR: In file included from /usr/include/qt5/QtConcurrent/qtconcurrentiteratekernel.h:49, [ 67s] from /usr/include/qt5/QtConcurrent/qtconcurrentfilterkernel.h:47, [ 67s] from /usr/include/qt5/QtConcurrent/qtconcurrentfilter.h:47, [ 67s] from /usr/include/qt5/QtConcurrent/QtConcurrent:8, [ 67s] from /home/abuild/rpmbuild/BUILD/tok-0.0.1+git.20210605.035ab76/src/client_p.cpp:5: [ 67s] /usr/include/qt5/QtConcurrent/qtconcurrentthreadengine.h:250:50: error: invalid declarator before '*' token [ 67s] 250 | ThreadEngineStarter<void>(ThreadEngine<void> *_threadEngine) [ 67s] | ^ [ 67s] /usr/include/qt5/QtConcurrent/qtconcurrentthreadengine.h:250:49: error: expected ')' before '*' token [ 67s] 250 | ThreadEngineStarter<void>(ThreadEngine<void> *_threadEngine) [ 67s] | ~ ^~ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1179613] New: Remove KDE4 and related qt4 libraries
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1179613 Bug ID: 1179613 Summary: Remove KDE4 and related qt4 libraries Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker for removal of KDE4 and related qt4 libraries that are no longer needed. Both were already unsupported in 15.2, and we'd like to remove them as we're now facing a lot of build issues in openSUSE Backports 15.3 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 972678] New: KDE:Qt/python-pyside: Bug - Installation of this breaks software "opensesame"
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=972678 Bug ID: 972678 Summary: KDE:Qt/python-pyside: Bug - Installation of this breaks software "opensesame" Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: dmueller(a)suse.com Reporter: patrickmurphy221(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- - Overview Tumbleweed zypper dup requests installation of python-pyside, but installing it breaks the program "opensesame". - More detail Installed OpenSUSE Tumbleweed (snapshot 2016-03-18). Installed package "opensesame" (psychology experiment builder, homepage: http://osdoc.cogsci.nl/) from OpenSUSE Science repository (https://build.opensuse.org/project/show/science) It works fine. When I do a "zypper dup" (March 23rd or 24th), the package "python-pyside" is installed (requested by the distribution; not a dependency of opensesame) and it breaks opensesame. Trying to run opensesame gives this error instead of launching the program: python: siplib.c:8551: sip_api_can_convert_to_type: Assertion `td == ((void *)0) || (((td)->td_flags & 0x0007) == 0x0000) || (((td)->td_flags & 0x0007) == 0x0002)' failed. Aborted (core dumped) Uninstalling python-pyside makes opensesame work again (but "zypper dup" continues to request that I install python-pyside). This does not seem to be specific to the OpenSUSE Science repository, since downloading the opensesame python source from its official website and running that gives the exact same result. - To reproduce 1. Install opensesame, from OpenSUSE Science repo or from source. 2. Install python-pyside (as requested by zypper dup). Reversing the order has same effect. Happens on Tumbleweed. In the past I've run opensesame on Leap without problems, but I don't think it ever requested installation of python-pyside, so breakage would not be expected. (First time submitting a bug; apologies if I didn't include the right detail or use the right format.) -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1040812] New: KDE:Qt5/libqt5-qtbase: Bug: KDE:Qt5 has been upgraded to QT 5.9, publishing is OFF
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1040812 Bug ID: 1040812 Summary: KDE:Qt5/libqt5-qtbase: Bug: KDE:Qt5 has been upgraded to QT 5.9, publishing is OFF Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: hrvoje.senjan(a)gmail.com Reporter: Mathias.Homann(a)opensuse.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Again KDE:Qt5 has been up- or downgraded, this time to Qt 5.9, but publishing is OFF, so AGAIN all repositories that build using Qt5 are broken. FIX ASAP. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1189283] New: kernel-obs-build needs af_alg
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1189283 Bug ID: 1189283 Summary: kernel-obs-build needs af_alg Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libkcapi got updated to 1.3.1 (https://build.opensuse.org/request/show/910806) and apparently gnutls picks that up now and enables support for it. It seems like that depends on AF_ALG sockets though, which are currently not enabled in kernel-obs-build (missing af_alg module), so various builds (libzip, libvirt) fail with libkcapi - Error: AF_ALG: socket syscall failed (errno: -97) I'm not sure whether just af_alg is enough, it might need some other modules as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1173619] New: VUL-0: unbound: LPE from unbound to root
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1173619 Bug ID: 1173619 Summary: VUL-0: unbound: LPE from unbound to root Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: darin(a)darins.net Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- via security(a)suse.de: I believe to have found a configuration issue in the Unbound package. Or, depending on how you look at it, in the Unbound server itself. 1. Before starting the Unbound server, systemd routinely runs unbound-anchor. From 'systemctl cat unbound': ExecStartPre=/usr/bin/sudo -u unbound /usr/sbin/unbound-anchor -a /var/lib/unbound/root.key -c /etc/unbound/icannbundle.pem As you can see this process is run as user unbound. 2. The Unbound server writes a pid file before dropping privileges, i.e. as root. It then chown's the file in a second step. 'grep username /etc/unbound/unbound.conf': username: "unbound" And from the Unbound source: https://github.com/NLnetLabs/unbound/blob/2a90e8fa1e22aa75d1cf67a1f71ebbf3f… As you can see in the source, Unbound doesn't check if there is already a symbolic link in place of the pid file. 3. openSUSE configures Unbound to create the pid file in a directory owned by the unbound user. 'grep pidfile /etc/unbound/unbound.conf': pidfile: "/var/run/unbound/unbound.pid" 'cat /usr/lib/tmpfiles.d/unbound.conf': D /run/unbound 0755 unbound unbound - 4. unbound-anchor is a nice little "do-one-thing-and-do-it-right" tool. But if it is compromised, and as it has write permission in the pid file directory and reliably runs before the server, an attacker could easily gain full root privileges by just creating a symbolic link /run/unbound/unbound.pid. 5. IMHO this would be best fixed in openSUSE by creating a root owned /run/unbound directory, or changing the pid file path to /run/unbound.pid or something like that. I think this would have the added advantage that openSUSE could ship and maybe enforce the Unbound AppArmor profile used in Debian and Ubuntu: https://gitlab.com/apparmor/apparmor-profiles/-/blob/master/ubuntu/20.04/us… With the current openSUSE setup there is the problem that if AppArmor filters CAP_DAC_OVERRIDE, Unbound has no permission to create a pid file in /run/unbound anymore. If you have questions please don't hesitate to contact me. Thanks for taking a look. Kind regards, Detlef -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1181471] New: libcurl hangs in a __poll below curl_easy_cleanup
by bugzilla_noreply＠suse.com 27 Feb '23

27 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1181471 Bug ID: 1181471 Summary: libcurl hangs in a __poll below curl_easy_cleanup Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi Predro, a puzzle for the curl maintainers. I'm lost how to further investigate it. Maybe you've got an idea: [https://github.com/openSUSE/zypper/issues/364] - 'Proot' is used to chroot into an openSUSE TW system. This might be the reason, at least ZYPP never received a similar issue report, neither on aarch64 nor on any other architecture. From within the system, libzypp (via libcurl) is able to connect to e.g. download. opensuse.org (the log shows a successful head request). But when closing the connection libcurl reproducible hangs below a call to curl_easy_cleanup (for 20+ minutes before killing zypper). A stacktrace created by libzypp shows curl_easy_cleanup staying in a call to poll: > [bt]: (0) /lib64/libc.so.6 : __poll+0xec [0x7f8a71618c] > [bt]: (1) /usr/lib64/libcurl.so.4 : +0x5e088 [0x7f8a54f088] > [bt]: (2) /usr/lib64/libcurl.so.4 : +0x6024c [0x7f8a55124c] > [bt]: (3) /usr/lib64/libcurl.so.4 : +0x47240 [0x7f8a538240] > [bt]: (4) /usr/lib64/libcurl.so.4 : +0x4740c [0x7f8a53840c] > [bt]: (5) /usr/lib64/libcurl.so.4 : +0x1a3c4 [0x7f8a50b3c4] > [bt]: (6) /usr/lib64/libcurl.so.4 : +0x6e7d0 [0x7f8a55f7d0] > [bt]: (7) /usr/lib64/libcurl.so.4 : curl_easy_cleanup+0x40 [0x7f8a506db0] > [bt]: (8) /usr/lib64/libzypp.so.1722 : zypp::media::MediaCurl::disconnectFrom()+0x2c [0x7f8ada0bdc] > [bt]: (9) /usr/lib64/libzypp.so.1722 : zypp::media::MediaHandler::disconnect()+0x34 [0x7f8ad8bab4] The same is seen in the strace log: > https://github.com/openSUSE/zypper/files/5856500/zypper.strace.log.zip > (search for 'Releasing media http<http://download.opensuse.org' After writing the log line libzypp calls curl_easy_cleanup. Then you see just an endless loop of ppoll calls. Any idea/hint how to circumvent this is welcome. -- You are receiving this mail because: You are on the CC list for the bug.

1 4