November 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1191473] New: rpath related failures on x86_64
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191473 Bug ID: 1191473 Summary: rpath related failures on x86_64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages started failing after september, 19 with rpath errors: https://build.opensuse.org/packages/AppCSXCAD/job_history/openSUSE:Factory/… https://build.opensuse.org/packages/libqt5-creator/job_history/KDE:Qt5/open… In both cases, only x86_64 fails, i586 is fine. for libqt5-creator, it's even stranger, the package only fails in the devel project. For AppCSXCAD : [ 67s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/AppCSXCAD-0.2.2-2.9.x86_64/usr/bin/AppCSXCAD [ 67s] CMake Error at cmake_install.cmake:55 (file): [ 67s] file RPATH_CHANGE could not write new RPATH: [ 67s] [ 67s] /usr/lib64 [ 67s] [ 67s] to the file: [ 67s] [ 67s] /home/abuild/rpmbuild/BUILDROOT/AppCSXCAD-0.2.2-2.9.x86_64/usr/bin/AppCSXCAD [ 67s] [ 67s] No valid ELF RPATH or RUNPATH entry exists in the file; for qtcreator: [ 4291s] -- Installing: /home/abuild/rpmbuild/BUILDROOT/libqt5-creator-5.0.1-1.8.x86_64/usr/libexec/qtcreator/qtpromaker [ 4291s] CMake Error at src/tools/qtpromaker/cmake_install.cmake:55 (file): [ 4291s] file RPATH_CHANGE could not write new RPATH: [ 4291s] [ 4291s] $ORIGIN/../../lib64/qtcreator:$ORIGIN/../../lib64/Qt/lib:$ORIGIN/../../lib64/qtcreator/plugins [ 4291s] [ 4291s] to the file: [ 4291s] [ 4291s] /home/abuild/rpmbuild/BUILDROOT/libqt5-creator-5.0.1-1.8.x86_64/usr/libexec/qtcreator/qtpromaker [ 4291s] [ 4291s] The current RUNPATH is: [ 4291s] [ 4291s] $ORIGIN/../../lib64/qtcreator: [ 4291s] [ 4291s] which does not contain: [ 4291s] [ 4291s] $ORIGIN/../../lib64/qtcreator::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: [ 4291s] [ 4291s] as was expected. --- Trying to rollback the cmake and binutils packages to older revisions didn't improve the situation. But, unsetting SUSE_IGNORED_RPATHS which is used in https://build.opensuse.org/package/view_file/devel:gcc/binutils/binutils-sk… fixes both builds (visible here: https://build.opensuse.org/package/show/home:cgiboudeaux:bisect/AppCSXCAD and here: https://build.opensuse.org/package/show/home:cgiboudeaux:branches:home:cgib…) -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1188941] ppc64 optflags don't enable LTO
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

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

1 0

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 https://bugzilla.suse.com/show_bug.cgi?id=1192278#c4 Adrian Schr�ter <adrian.schroeter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(adrian.schroeter@ | |suse.com) | --- Comment #4 from Adrian Schr�ter <adrian.schroeter(a)suse.com> --- no, we published an older -1 one for some reason (seems there was an internal release which never went to the outside). However, stage has now the right -2 ftp tree. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188143] Firewall Zone-Interface association not applied with "Reload"
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188143 https://bugzilla.suse.com/show_bug.cgi?id=1188143#c6 --- Comment #6 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Jos� Iv�n L�pez Gonz�lez from comment #5) > Any feedback here? Josef, if no feedback, do you think YaST should use > `firewall-cmd --reload`? well, it would be inconsistent with other similar modules..but it is possible. Still I expect it should behave same for both calls. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 https://bugzilla.suse.com/show_bug.cgi?id=1192278#c3 Lubos Kocman <lubos.kocman(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.schroeter(a)suse.com Flags| |needinfo?(adrian.schroeter@ | |suse.com) --- Comment #3 from Lubos Kocman <lubos.kocman(a)suse.com> --- So it seems that this is above what I can do as ftp-stage has obsoleted version as well lkocman@pontifex2:/srv/ftp/pub/opensuse/distribution/leap/15.3/repo/oss/x86_64> rpm -q --provides -p /srv/{ftp,ftp-stage}/pub/opensuse/distribution/leap/15.3/repo/oss/x86_64/openSUSE-release-15.3*.rpm | grep "product(Leap)" product(Leap) = 15.3-1 product(Leap) = 15.3-1 I recall Adrian mentioned that there were two ftp-trees published on the OBS side. Perhaps we're publish the wrong one into ftp-stage. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 https://bugzilla.suse.com/show_bug.cgi?id=1192278#c2 --- Comment #2 from Lubos Kocman <lubos.kocman(a)suse.com> --- I'm looking into it. The publish was executed for both images and ftp-tree. I'll try to re-run it otherwise it will have to be investigated by autobuild team. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192148] New: yast wrong geometry with one display in portrait mode
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192148 Bug ID: 1192148 Summary: yast wrong geometry with one display in portrait mode Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: robert.simai(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- My setup consists of 3 regular HD monitors. First in portrait mode, second (main display, in the middle) and third in landscape mode. I'm running regular KDE. From xrandr: HDMI-1 connected 1080x1920+0+0 left (normal left inverted right x axis y axis) 509mm x 286mm DP-1 connected 1920x1080+1080+494 (normal left inverted right x axis y axis) 527mm x 296mm DP-2 connected 1920x1080+3000+494 (normal left inverted right x axis y axis) 527mm x 296mm I typically start applications from the middle display and I noticed that yast modules behave weird with their geometry, they seem to adapt to the portrait mode of the first display, regardless where they are started and displayed . Yast Control Center is correct but any module started from there is wrong. xwininfo tells me Corners: +1080+523 -3040+523 -3040-53 +1080-53 -geometry 800x1344+1080-53 You see 1344 is more than the available 1080. This requires to always correct the geometry to reach the buttons at the bottom, they are initially out of reach. Expected: the geometry should be taken from the active display, or at least must not exceed its resolution. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1192294] New: at and batch fail with "Execution directory inaccessible" and "Not a directory"
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192294 Bug ID: 1192294 Summary: at and batch fail with "Execution directory inaccessible" and "Not a directory" 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: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just upgraded from openSUSE Tumbleweed 20211008 to 20211031, which included an upgrade from at 3.2.2-1.2 to 3.2.2-2.1. Now it's no longer possible for me to run any commands at all via at or batch. Trying to do so always results in an e-mailed error message with the following text: sh: line 87: cd: /home/psy: Not a directory Execution directory inaccessible (Here the line number may vary, and the directory following "cd" is whatever directory the at/batch command was run from, or my home directory in the case that the command was run via a cron job.) I can easily reproduce the problem by running some dummy command via batch. For example: echo sleep 1|batch -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c6 --- Comment #6 from Takashi Iwai <tiwai(a)suse.com> --- Well, if it's with Nvidia binary-only driver, the things get more complicated, unfortunately. Can we reproduce the problem without Nvidia driver? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c3 --- Comment #3 from Olav Reinert <seroton10(a)gmail.com> --- The instructions on that web page seem to be outdated: blackbox:~ # zypper in --from Kernel:SLE15-SP3 kernel-default Retrieving repository 'Kernel:SLE15-SP3' metadata ................................................[error] Repository 'Kernel:SLE15-SP3' is invalid. [Kernel:SLE15-SP3|https://download.opensuse.org/repositories/Kernel:/SLE15-S…] Valid metadata not found at specified URL History: - [Kernel:SLE15-SP3|https://download.opensuse.org/repositories/Kernel:/SLE15-S…] Repository type can't be determined. -- You are receiving this mail because: You are on the CC list for the bug.

1 0