December 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1135030] New: LTO: ceph build fails
by bugzilla_noreply＠novell.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1135030 Bug ID: 1135030 Summary: LTO: ceph build fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… due to: [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_aio_create_completion' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_create_with_context' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_version' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_create2' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_nobjects_list_next' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_conf_parse_env' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_conf_set' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_create' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_ioctx_create2' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_conf_parse_argv' [ 8864s] /usr/lib64/gcc/x86_64-suse-linux/9/../../../../x86_64-suse-linux/bin/ld: ../../../lib/librados.so.2.0.0: undefined reference to `rados_conf_read_file' -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1165294] New: haveged is marked as deleted after reboot
by bugzilla_noreply＠novell.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1165294 Bug ID: 1165294 Summary: haveged is marked as deleted after reboot 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: hpj(a)urpla.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, *After reboot*, a couple of my TW systems show: $ zyp ps Verbosity: 2 Checking for running processes using deleted libraries... The following running processes use deleted files: PID | PPID | UID | User | Command | Service | Files ----+------+-----+------+-------------------+--------- +------------------------------ 531 | 1 | 0 | root | haveged (deleted) | haveged | /lib64/ld-2.31.so | | | | | | /lib64/libc-2.31.so | | | | | | /usr/sbin/haveged (deleted) | | | | | | /usr/lib64/libhavege.so.1.1.0 You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. No core libraries or services have been updated. Reboot is probably not necessary. Marcus Meissner noted on the factory ML, that: > It is ran in the initrd and probably still running after transition to the > regular system. > > (Likely pulled in via dracut-fips module) Shouldn't a transition from initrd to regular operation include a restart of this service then? -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1183965] New: makedumpfile, crash: are not able to read kenrel log from the lockless ringbuffer added in kernel-5.10
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1183965 Bug ID: 1183965 Summary: makedumpfile, crash: are not able to read kenrel log from the lockless ringbuffer added in kernel-5.10 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: pmladek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kernel-5.10 started storing kernel (printk) messages in a new lockless ringbuffer. As a result makedumpfile and crash tools are not able to read the kernel log from vmcore 5.10+ kernels. crasdump is important tool for kernel debugging. The log is usually the first thing that people look at. These never kernels are already used in openSUSE Tumbleweek. The needed changes are already upstream. It is just a matter to backport them. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1194193] New: Difficult login to bugzilla.opensuse.org
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1194193 Bug ID: 1194193 Summary: Difficult login to bugzilla.opensuse.org Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- How to reproduce: * Go to https://bugzilla.opensuse.org * Click login * Fill username and password * Nothing happens How to workaround: * Go to https://bugzilla.suse.com/ * Login there * Go to https://bugzilla.opensuse.org * Login works -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1190261] New: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1190261 Bug ID: 1190261 Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Spin-off from bug 1189841. From https://github.com/openSUSE/suse-module-tools/pull/33: @mwilck: so why not test this? e.g. like this: if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then ... fi @hramrach: ??? The part that github displays as context for this comment does not look relevant @hramrach hramrach 21 hours ago Member Right, if you refer to XXX: Only call mokutil if UEFI and shim are used then I have no opinion on that. Should be probably handled in a separate bug and the implications of any possible check discussed to death. @hramrach hramrach 21 hours ago Member Actually, there is the problem that on arm64 you suddenly get from no shim to shim on SP update without any warning so this is really hairy to get right. Really deserves a separate bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1193250] New: Fully switch TW to DRM graphics drivers and disable fbdev drivers
by bugzilla_noreply＠suse.com 22 Mar '23

22 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193250 Bug ID: 1193250 Summary: Fully switch TW to DRM graphics drivers and disable fbdev drivers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: tzimmermann(a)suse.com QA Contact: gfx-bugs(a)suse.de Found By: --- Blocker: --- In TW, we mostly use fbdev vesafb and efifb drivers for early-boot display output and as fallback. This has a number of problems, such as * Most modern Wayland compositors don't support fbdev any longer. Even X' support is bolted-on. Generally, userspace support for fbdev is slowly fading. See bug 1187154. * Handover from fbdev to native DRM drivers is unreliable and can result in stuck systems during boot. See bug 1181913. Therefore, replace TW's fbdev drivers with simpledrm and maybe other DRM drivers. -- You are receiving this mail because: You are on the CC list for the bug.

1 80

[Bug 1180882] New: perf does not build reproducibly
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1180882 Bug ID: 1180882 Summary: perf does not build reproducibly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1041090 Found By: Development Blocker: --- While working on reproducible builds for SLE and openSUSE, I found that our perf package differs across builds. /usr/bin/perf differs in ELF section .dynsym /usr/bin/perf differs in ELF section .rela.dyn because nftw in https://github.com/torvalds/linux/blob/v5.3/tools/perf/pmu-events/jevents.c… reads pmu-events/arch/x86/*/*.json in random filesystem readdir order -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 952198] New: django-admin does not work, django-admin.py does
by bugzilla_noreply＠novell.com 20 Mar '23

20 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=952198 Bug ID: 952198 Summary: django-admin does not work, django-admin.py does Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: o.kurz(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- observation: The django tutorial https://docs.djangoproject.com/en/1.8/intro/tutorial01/ suggests to use the tool "django-admin" with django >= v1.7 which is also available in Leap but does not work. "django-admin.py" also exists and works ok. steps to reproduce: - "zypper in python-Django python-sqlite" # confirm uninstallation of blocker package - "django-admin startproject mysite" - observe error with python traceback problem: unknown so far. Is ist maybe related that python-Django (still) uses python2? workaround: - Use django-admin.py which works flawlessly, e.g. example project can be configured and run: "django-admin.py startproject mysite && python manage.py migrate && python manage.py runserver", connect with webbrowser to http://localhost:8000. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1129471] New: kernel 5.0.1-1-default: Problem loading X.509 certificate -65
by bugzilla_noreply＠novell.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1129471 Bug ID: 1129471 Summary: kernel 5.0.1-1-default: Problem loading X.509 certificate -65 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: hendrikw(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Sins Tumbleweed 20190314, with kernel 5.0.1-1-default (x86_64) I get the following message during boot: integrity: Problem loading X.509 certificate -65 Log snippet: [ 2.985576] sched_clock: Marking stable (2989021511, -3468039)->(2994215803, -8662331) [ 2.986009] registered taskstats version 1 [ 2.986012] Loading compiled-in X.509 certificates [ 2.986062] Loaded X.509 cert 'openSUSE Secure Boot Signkey: 0332fa9cbf0d88bf21924b0de82a09a54d5defc8' [ 2.986093] zswap: loaded using pool lzo/zbud [ 2.998908] Key type big_key registered [ 3.005600] Key type encrypted registered [ 3.005606] AppArmor: AppArmor sha1 policy hashing enabled [ 3.008353] integrity: Loading X.509 certificate: UEFI:db [ 3.008414] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53' [ 3.008415] integrity: Loading X.509 certificate: UEFI:db [ 3.008452] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4' [ 3.008453] integrity: Loading X.509 certificate: UEFI:db [ 3.008476] integrity: Loaded X.509 cert 'Acer Database: 84f00f5841571abd2cc11a8c26d5c9c8d2b6b0b5' [ 3.008477] integrity: Loading X.509 certificate: UEFI:db [ 3.008482] integrity: Problem loading X.509 certificate -65 [ 3.008494] fbcon: Taking over console [ 3.008496] Error adding keys to platform keyring UEFI:db [ 3.008497] integrity: Loading X.509 certificate: UEFI:db [ 3.008501] integrity: Problem loading X.509 certificate -65 [ 3.008505] Error adding keys to platform keyring UEFI:db [ 3.008596] Console: switching to colour frame buffer device 240x67 [ 3.009680] integrity: Loading X.509 certificate: UEFI:MokListRT [ 3.009739] integrity: Loaded X.509 cert 'openSUSE Secure Boot Signkey: 0332fa9cbf0d88bf21924b0de82a09a54d5defc8' [ 3.009740] integrity: Loading X.509 certificate: UEFI:MokListRT [ 3.012608] integrity: Loaded X.509 cert 'openSUSE Secure Boot CA: 6842600de22c4c477e95be23dfea9513e5971762' [ 3.014923] ima: Allocated hash algorithm: sha256 [ 3.052885] evm: Initialising EVM extended attributes: hardware: Laptop Acer Aspire A517-51-5832, one year old -- You are receiving this mail because: You are on the CC list for the bug.

2 20

[Bug 1153837] New: gobject-introspection has to require a specific Python ABI version
by bugzilla_noreply＠novell.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1153837 Bug ID: 1153837 Summary: gobject-introspection has to require a specific Python ABI version Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The _giscanner module depends on the ABI version used during the build: https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:… [ 108s] /usr/lib64/gobject-introspection/giscanner/__init__.py 0 (none) 100644 root root 0 4294967295 [ 108s] -/usr/lib64/gobject-introspection/giscanner/_giscanner.cpython-38-x86_64-linux-gnu.so 0 (none) 100755 root root 0 4294967295 [ 108s] +/usr/lib64/gobject-introspection/giscanner/_giscanner.cpython-37m-x86_64-linux-gnu.so 0 (none) 100755 root root 0 4294967295 [ 108s] /usr/lib64/gobject-introspection/giscanner/_version.py 0 (none) 100644 root root 0 4294967295 Trying to use g-ir-scanner then leads to non-obvious errors, e.g.: https://build.opensuse.org/build/openSUSE:Factory:Staging:C/standard/x86_64… [ 50s] [ 28%] Built target fcitx-addon-fcitx-classic-ui--headers-1 [ 50s] Scanning dependencies of target fcitx-addon-fcitx-x11--addon--conf-1 [ 50s] Traceback (most recent call last): [ 50s] File "/usr/bin/g-ir-scanner", line 98, in <module> [ 50s] from giscanner.scannermain import scanner_main [ 50s] File "/usr/lib64/gobject-introspection/giscanner/scannermain.py", line 35, in <module> [ 50s] from giscanner.ast import Include, Namespace [ 50s] File "/usr/lib64/gobject-introspection/giscanner/ast.py", line 29, in <module> [ 50s] from .sourcescanner import CTYPE_TYPEDEF, CSYMBOL_TYPE_TYPEDEF [ 50s] File "/usr/lib64/gobject-introspection/giscanner/sourcescanner.py", line 33, in <module> [ 50s] from giscanner._giscanner import SourceScanner as CSourceScanner [ 50s] ModuleNotFoundError: No module named 'giscanner._giscanner' -- You are receiving this mail because: You are on the CC list for the bug.

2 3