openSUSE Bugs November 2022

bugs@lists.opensuse.org

1 participants
1900 discussions

[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

[Bug 1140614] New: Error loading Applications menu extension in SLE-Classic
by bugzilla_noreply＠novell.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1140614 Bug ID: 1140614 Summary: Error loading Applications menu extension in SLE-Classic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: qkzhu(a)suse.com Reporter: qkzhu(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gwang(a)suse.com, xiaoguang.wang(a)suse.com, yfjiang(a)suse.com, zcjia(a)suse.com Found By: --- Blocker: --- apps-menu disappeared in TW-20190704, and journalctl shows: > gnome-shell[2369]: Extension "apps-menu(a)gnome-shell-extensions.gcampax.github.com" had error: Error: Requiring GMenu, version none: Typelib file for namespace 'GMenu' (any version) not found -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1205261] New: dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk
by bugzilla_noreply＠suse.com 20 Mar '23

20 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1205261 Bug ID: 1205261 Summary: dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 862770 --> http://bugzilla.opensuse.org/attachment.cgi?id=862770&action=edit rdsosreport.txt from TW boot attempt Original Summary: dracut/hooks/emergency...ESP's FAT serial number in initrd halts boot in dracut emergency shell after rsync migration to new GPT system disk Initial state: 1-configured booting & mounting are via LABELs (making UUIDs administratively unimportant, and grub.cfg's own auto-generated stanzas uncommonly necessary or desired), with /etc/grub.d/06_custom causing /boot/grub2/custom.cfg's vmlinuz & initrd symlink stanzas to precede auto-generated entries at boot time. Example: <https://forums.opensuse.org/showthread.php/533087-How-to-have-a-custom-UEFI…> 2-in /etc/default/grub: GRUB_DISTRIBUTOR="opensusetw" # TW20221008 last zypper dup 3-multiboot of TW with Leap 15.1, 15.2, 15.3, 15.4, Debian 11 & 12, Ubuntu 20.04 & 22.04 on single NVME 4-only TW installation is configured to touch NVRAM or ESP for writing (e.g., other OSes' fstabs don't mount ESP, and/or they have no bootloader installed) To reproduce: 1-GPT partition new NVME with ESP, swap, and / targets for TW, and / for at least one additional distro 2-format new NVME's matching targets ESP FAT32, swap swap, and / EXT4 for TW 3-"rsync -rlptgoDHAX --exclude 'lost+found'" from old NVME's ESP and / to new ESP and / filesystems for TW 4-appropriately edit volume LABELs on new NVME /boot/grub2/grub.cfg, /boot/grub2/custom.cfg, /etc/fstab 5-repeat create/format/rsync/edit for additional distro(s) 6-remove original NVME 7-try to boot from new NVME Actual behavior: 1-all other distro(s) boot normally (via TW's custom.cfg entries) as if nothing had been changed 2-TW boot halts in dracut emergency shell because the original ESP's FAT serial number cannot be found (see attached rdsosreport.txt) Expected behavior: 1-all distros boot normally (via custom.cfg entries) as if nothing had been changed Notes: 1-Boot is normal since rebuilding of initrds post-migration. 2-I looked for ESP FAT serial references in several non-TW initrds and found none. 3-from lsinitrd of original initrd-5.19.13-default: -rw-r--r-- 1 root root 92 Oct 9 23:10 usr/lib/dracut/hooks/emergency/80-\x2fdev\x2fdisk\x2fby-uuid\x2f20A0-1003.sh 4-# lsblk -f | grep vfat # (current state, not initial state) ��nvme1n1p1 vfat FAT16 PI3P01ESP 20A0-1003 (*original* ESP on 120G NVME) ��nvme0n1p1 vfat FAT32 PNY5P01ESP 4C58-8D7E 294.1M 8% /boot/efi (*new* ESP on 500G NVME) 5-This issue complicates restoring from backups. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1146018] New: Unreliable copy and cut
by bugzilla_noreply＠novell.com 19 Mar '23

19 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1146018 Bug ID: 1146018 Summary: Unreliable copy and cut Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: audi_s4(a)luukku.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After fresh installation of Tumbleweed to a new hardware (Ryzen Threadripper + AMD gfx) copy and cut with ctrl+c/x started working unreliably (never experienced this with the previous hardware setups). After KDE is started these work OK but after few hours already copy and cut start to miss these presses. 2nd press usually works but not always. After several days without restarting KDE this problem gets more severe - misses more often. Also, strange behaviour happens with Dolphin for example. When ctrl+x is pressed the file/folder icon flicks quickly to greyed out (cut selection) and back to normal. It becomes difficult to press ctrl+x so that cut selection remains. Holding ctrl+x pressed for repeat the icon start to flicker between normal and selected. Tried changing clipboard configuration options but none have made any difference to the problem. I have not seen issues with paste i.e. if there's something on a clipboard it can be pasted. This is not only ctrl+c/x button combination issue but same applied to selecting copy&cut from application menus. All applications (KDE basic apps, LibreOffice, Thunderbird, Firefox..) I use suffer from this problem thus it seems to be KDE related issue. This has been an issue for several months (since installation early 2019). In the beginning it was even worse i.e. some updates have reduced the issue a bit but not much. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1185952] New: [Build 20210510] PostgreSQL is not startable on s390x
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1185952 Bug ID: 1185952 Summary: [Build 20210510] PostgreSQL is not startable on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 URL: https://openqa.opensuse.org/tests/1734657/modules/post gresql_server/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-s390x-textmode@s390x-zVM-vswitch-l2 fails in [postgresql_server](https://openqa.opensuse.org/tests/1734657/modules/postgr… All packages can be installed. The problem is that the PostgreSQL server can not be started. The journal log is saying: -- Logs begin at Mon 2021-05-10 22:41:06 EDT, end at Mon 2021-05-10 23:23:02 EDT. -- May 10 23:15:15 susetest systemd[1]: Starting PostgreSQL database server... May 10 23:15:15 susetest systemd[1]: postgresql.service: Control process exited, code=exited, status=1/FAILURE May 10 23:15:15 susetest systemd[1]: postgresql.service: Failed with result 'exit-code'. May 10 23:15:15 susetest systemd[1]: Failed to start PostgreSQL database server. May 10 23:15:15 susetest postgresql-script[12832]: Cannot find an active PostgreSQL server binary. Please install one of the PostgreSQL May 10 23:15:15 susetest postgresql-script[12832]: server packages or activate an already installed version using update-alternatives. ## Test suite description Maintainer: QE Yast Installation in textmode and selecting the textmode "desktop" during installation. ## Reproducible Fails since (at least) Build [20210510](https://openqa.opensuse.org/tests/1734657) (current job) ## Expected result Last good: [20210507](https://openqa.opensuse.org/tests/1731697) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=s390x&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1203019] New: yast2: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1203019 Bug ID: 1203019 Summary: yast2: replace mkinitrd wrapper with native dracut Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: antonio.feijoo(a)suse.com QA Contact: jsrain(a)suse.com Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…). ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. References: - yast2 /usr/share/YaST2/modules/Initrd.rb:72: # parametr for mkinitrd because of splash screen /usr/share/YaST2/modules/Initrd.rb:75: # Additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:391: "/lib/mkinitrd/scripts/setup-splash.sh" /usr/share/YaST2/modules/Initrd.rb:400: "/sbin/mkinitrd %1 %2 >> %3 2>&1", /usr/share/YaST2/modules/Initrd.rb:405: File.join(Directory.logdir, "y2logmkinitrd").shellescape /usr/share/YaST2/modules/Initrd.rb:411: Ops.add(Directory.logdir, "/y2logmkinitrd") /usr/share/YaST2/modules/Initrd.rb:434: # Set the -s parameter of mkinitrd /usr/share/YaST2/modules/Initrd.rb:463: # Get additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:464: # @return [String] additional mkinitrd parameters /usr/share/YaST2/modules/Initrd.rb:469: # Set additional parameters for mkinitrd /usr/share/YaST2/modules/Initrd.rb:470: # @param [String] params string additional mkinitrd parameters # rpm -qf /usr/share/YaST2/modules/Initrd.rb yast2-4.5.10-1.1.x86_64 - yast2-country /usr/share/YaST2/modules/Timezone.rb:85: # if mkinitrd should be called at the end /usr/share/YaST2/modules/Timezone.rb:86: @call_mkinitrd = false /usr/share/YaST2/modules/Timezone.rb:467: Builtins.y2milestone("calling mkinitrd...") /usr/share/YaST2/modules/Timezone.rb:470: "/sbin/mkinitrd >> /var/log/YaST2/y2logmkinitrd 2>> /var/log/YaST2/y2logmkinitrd" /usr/share/YaST2/modules/Timezone.rb:860: CallMkinitrd() if @call_mkinitrd && !Stage.initial /usr/share/YaST2/modules/Timezone.rb:1081: publish :variable => :call_mkinitrd, :type => "boolean" # rpm -qf /usr/share/YaST2/modules/Timezone.rb yast2-country-4.5.1-1.1.x86_64 - yast2-kdump /usr/share/YaST2/modules/Kdump.rb:419: update_command = (using_fadump? ? "/usr/sbin/mkdumprd -f" : "/sbin/mkinitrd") /usr/share/YaST2/modules/Kdump.rb:426: update_logfile = File.join(Directory.logdir, "y2logmkinitrd") # rpm -qf /usr/share/YaST2/modules/Kdump.rb yast2-kdump-4.5.3-1.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1100677] New: trackerbug: packages do not build reproducibly from compile-time CPU-detection
by bugzilla_noreply＠novell.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1100677 Bug ID: 1100677 Summary: trackerbug: packages do not build reproducibly from compile-time CPU-detection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Depends on: 1100520 Blocks: 1081754 Found By: Development Blocker: --- e.g. bug 1100520 compiler options -march=native and -mtune=native make the resulting machine code depend on the build system's CPU which breaks reproducible builds. affects at least: glucat form python-annoy legion trigger-rally This is already fixed in: clpeak higan kyotocabinet one common approach seems to do sed -i "s|-march=native||g" $FILE -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1159231] New: tesseract-ocr builds with march=native
by bugzilla_noreply＠novell.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1159231 Bug ID: 1159231 Summary: tesseract-ocr builds with march=native Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: idonmez(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hiwatari.seiji(a)gmail.com Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that the tesseract-ocr package binary varies depending on build machine CPU. This is a bug that can cause crashes on machines older that the random build machine. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs November 2022