May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 948280] windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options?
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=948280 https://bugzilla.suse.com/show_bug.cgi?id=948280#c4 --- Comment #4 from Ralf Habacker <ralf.habacker(a)freenet.de> --- (In reply to Ralf Habacker from comment #2) > address space layout randomization (ASLR) > --nxcompat Image is compatible with data execution > prevention According to https://github.com/bminor/binutils-gdb/commit/514b4e191d5f46de8e142fe216e67… this is set by default since binutils 2.36. The uses settings can be inspected with: $ objdump -x <file.dll> | grep -A3 DllCh DllCharacteristics 00000140 DYNAMIC_BASE NX_COMPAT SizeOfStackReserve 00200000 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 948280] windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add hardening options?
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=948280 https://bugzilla.suse.com/show_bug.cgi?id=948280#c3 --- Comment #3 from Ralf Habacker <ralf.habacker(a)freenet.de> --- (In reply to Ralf Habacker from comment #2) > --dynamicbase Image base address may be relocated using > address space layout randomization (ASLR) According to https://github.com/gcc-mirror/gcc/commit/2bdf17de1d0ad7a75d3474e672a3a21109… this seems to be set by default since binutils 2.36. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225754] New: samba: new non-determinism in 4.20.1
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225754 Bug ID: 1225754 Summary: samba: new non-determinism in 4.20.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: bwiedemann(a)suse.com QA Contact: samba-maintainers(a)SuSE.de CC: scabrero(a)suse.com Target Milestone: --- Found By: Development Blocker: --- My tools for testing reproducible builds show me that there is new non-determinism from ASLR and parallelism that comes in via --- /home/abuild/rpmbuild/BUILD/samba-4.20.1+git.335.0a46cdafe2/bin/default/source3/librpc/gen_ndr/py_smbXsrv.c +++ /home/abuild/rpmbuild/BUILD/samba-4.20.1+git.335.0a46cdafe2/bin/default/source3/librpc/gen_ndr/py_smbXsrv.c @@ -1695,7 +1695,7 @@ object->raw_ev_ctx = NULL; } else { object->raw_ev_ctx = NULL; - PyErr_SetString(PyExc_TypeError, "Can not convert C Type struct HASH(0x555555e02eb0) from Python"); + PyErr_SetString(PyExc_TypeError, "Can not convert C Type struct HASH(0x555555e02e20) from Python"); This was not an issue with previous version 4.19.5+git.342.57620c4f7e-304 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223910] Package aalib does not build with gcc 14
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223910 https://bugzilla.suse.com/show_bug.cgi?id=1223910#c3 Martin Jambor <mjambor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de --- Comment #3 from Martin Jambor <mjambor(a)suse.com> --- (In reply to OBSbugzilla Bot from comment #2) > This is an autogenerated message for OBS integration: > This bug (1223910) was mentioned in > https://build.opensuse.org/request/show/1172933 Factory / aalib This is not enough, old configure script does not create "proper" main functions and so the package still fails. Somehow setting CFLAGS is not enough to prevent this, setting optflags like in the submission from comment #1 is. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225666] New: first time experience with zypper gpg import is suboptimal
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1225666 Bug ID: 1225666 Summary: first time experience with zypper gpg import is suboptimal Classification: openSUSE Product: openSUSE Leap Micro Version: 6.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Transactional Update Assignee: lubos.kocman(a)suse.com Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On a fresh installed Leap Micro with openSUSE-repos login do something like a zypper search and you'll be instantly prompted to accept new gpg key followed by error as the tranasaction lock /usr/lib/sysimage/rpm/rpm.lock can't be created For a zypper ref/search that's a bit too much. I'm perfectly fine with anything installation related being done in transactional-update shell etc ... We should do something about the current behavior. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c17 --- Comment #17 from Imo Hester <vortex(a)z-ray.de> --- Created attachment 875249 --> https://bugzilla.suse.com/attachment.cgi?id=875249&action=edit Output of lsinitrd | grep nvidia -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c16 --- Comment #16 from Imo Hester <vortex(a)z-ray.de> --- A never mind. I rolled back to snapshot #2 before installing the driver. Then ran transactional-update pkg in nvidia-drivers-G06 Rebooted And ran the command. It seems the driver package on it's own seems not to generate an initramfs on it's own. After manually running transactional-update initrd reboot I now get the following output (see attached log file) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1224773] Cannot install NVIDIA drivers in latest Aeon RC2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1224773 https://bugzilla.suse.com/show_bug.cgi?id=1224773#c15 --- Comment #15 from Imo Hester <vortex(a)z-ray.de> --- Hm, I get the following output: >sudo lsinitrd | grep nvidia >No <initramfs file> specified and the default image '/boot/efi/7b5e214ac1c6413b9145cd262341e2fe/6.9.1-1-default/initrd' cannot be accessed! Am I using the command wrong? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213915] New: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213915 Bug ID: 1213915 Summary: Kernel panic - illegal instruction (4) at 7fffb6a4f874 nip 7fffb6a4f874 lr 7fffb6a4380c code 1 in ld64.so.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jrivrain(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868604 --> https://bugzilla.suse.com/attachment.cgi?id=868604&action=edit serial output All ppc64 Tumbleweed tests in Openqa are failing right now with a kernel panic. All the workers are on power8 cpus, this does not happen on a qemu emulated power9 cpu. Example of failing test: https://openqa.opensuse.org/tests/3476697 See attached serial output. -- You are receiving this mail because: You are on the CC list for the bug.

1 30

[Bug 1220818] ImageMagick uses update-alternatives (was: ImageMagick and ImageMagick-config-7-SUSE file conflict)
by bugzilla_noreply＠suse.com 31 May '24

31 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220818 https://bugzilla.suse.com/show_bug.cgi?id=1220818#c40 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ImageMagick and |ImageMagick uses |ImageMagick-config-7-SUSE |update-alternatives (was: |file conflict |ImageMagick and | |ImageMagick-config-7-SUSE | |file conflict) --- Comment #40 from Petr Gajdos <pgajdos(a)suse.com> --- For the information, the revert of update-alternatives removal is now in Factory trough https://build.opensuse.org/request/show/1176179 (unfortunately, I have realized that post-mortem as I missed the obs notification mail) In https://build.opensuse.org/project/show/home:pgajdos:magick-no-ua there is a variant without update alternatives. To summarize, it: 1. uses a new /etc/IMagick-7 dir (question is, whether this is reasonable, given that the revert is in factory yet) 2. ships policies under %{_datadir}/libMagickCore%{libspec}%{clibver}/policies together with imagick-set-policy helper script which is supposed make a link /etc/IMagick-7/policy.xml to one of that policy 3. policies can be installed in parallel, imagick-set-policy will choose the 'most secure one' even if they can not be exactly linearly ordered to provide /etc/IMagick-7/policy.xml; other policies installed on the same system can be used together with MAGICK_CONFIGURE_PATH 4. imagick-set-policy is run from %post/%postun of individual configuration variant packages and the main package; it can be used even directly, for testing purposes We can choose (again, given that the revert is in factory already) the less intrusive change and replace the update-alternaives with the script analogous to imagick-set-policy to provide the /etc/ImageMagick-7 link to variants instead of update-alternatives. -- You are receiving this mail because: You are on the CC list for the bug.

1 0