September 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218424] New: go1.22 release tracking
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1218424 Bug ID: 1218424 Summary: go1.22 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- go1.22 (expected February 2024) is a major release of Go. Minor releases of go1.22.x will be provided through February 2025. This issue tracks go1.22.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1228165] New: Position of SUSE Python interpreters on Externally managed environments
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1228165 Bug ID: 1228165 Summary: Position of SUSE Python interpreters on Externally managed environments Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dmueller(a)suse.com Target Milestone: --- Found By: --- Blocker: --- https://packaging.python.org/en/latest/specifications/externally-managed-en… This linked specification presents the use case rather well. Unlimited installation of Python packages can cause a serious damage, when the system component imports incompatible version of Python package instead of the intended one. (A parallel thought: are there any initiatives to port low-level components like firewalld to compiled languages? I know about firewalld-recode [1], but it seems to be quite dead). This specification tries to alleviate the problem by making it more difficult and painfully obvious that installing packages outside of the using system package manager is a wrong idea. That might be a good idea for normal users, but it seems like quite a bother for people who create containers, where the designers of such systems usually know what they are doing and who can check and test that nothing has been broken. The purpose of this bug is to discuss, whether we could produce some better solution to the problem, which wouldn’t be that obnoxious to our customers. One possible improvement would be to change our default hashbang to include `-s` parameter to calling our Python interpreters, so that modules in `$HOME` are not considered. Any possible improvements? [1] https://web.archive.org/web/20160318144103/https://fedorahosted.org/firewal… -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1225574] New: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1225574 Bug ID: 1225574 Summary: AUDIT-FIND: apache2-mod_mono: configuration defaults to predictable socket path in /tmp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: wolfgang.frisch(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- apache2-mod_mono, by default, creates a socket `/tmp/mod_mono_server_global`, allowing unprivileged users to break the module by creating an identically named file in that location. However a) this behavior is documented b) it is mitigated by a systemd hardening in the apache2 package: > [Unit] > Description=The Apache Webserver > After=network.target nss-lookup.target time-sync.target remote-fs.target > Before=getty(a)tty1.service plymouth-quit.service xdm.service > PartOf=apache2.target > [Service] > Type=notify > PrivateTmp=true -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1227378] New: /usr/bin/idle* don't have executable bits
by bugzilla_noreply＠suse.com 04 Dec '24

04 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227378 Bug ID: 1227378 Summary: /usr/bin/idle* don't have executable bits Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Python Assignee: python-maintainers(a)suse.com Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- tumbleweed-pkg~$ l /usr/bin/*idle* -rw-r--r--. 1 root root 94 čen 25 23:57 /usr/bin/idle3.11 -rw-r--r--. 1 root root 94 čen 30 21:20 /usr/bin/idle3.13 tumbleweed-pkg~$ -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1219943] New: Certificate error while fetching from https://debuginfod.opensuse.org
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1219943 Bug ID: 1219943 Summary: Certificate error while fetching from https://debuginfod.opensuse.org Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jimis(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Certificate error while fetching from https://debuginfod.opensuse.org Sorry about setting the component to "other" but I couldn't find a suitable one, I was searching for something like "infrastructure" or "administration". -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1227344] New: MicroOS Cockpit Applications missing from menu
by bugzilla_noreply＠suse.com 03 Dec '24

03 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1227344 Bug ID: 1227344 Summary: MicroOS Cockpit Applications missing from menu Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Cockpit Assignee: Cockpit-bugs(a)suse.de Reporter: robert.koktan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875848 --> https://bugzilla.suse.com/attachment.cgi?id=875848&action=edit Overview I do not recall when the SELinux and Storage Applications vanished form the Cockpit menu, but it's been several updates since. If one clicks on Applications, Cockpit lists the installed Applications, and SELinux and Storage are present, but on drilling down in to either of them, a Not Found error screen is returned. NAME="openSUSE MicroOS" # VERSION="20240629" ID="opensuse-microos" ID_LIKE="suse opensuse opensuse-tumbleweed microos sl-micro" VERSION_ID="20240629" PRETTY_NAME="openSUSE MicroOS" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:microos:20240629" BUG_REPORT_URL="https://bugzilla.opensuse.org" SUPPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:MicroOS" LOGO="distributor-logo-MicroOS" -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1223434] New: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse
by bugzilla_noreply＠suse.com 02 Dec '24

02 Dec '24

https://bugzilla.suse.com/show_bug.cgi?id=1223434 Bug ID: 1223434 Summary: /etc/fonts/conf.d/21-emoji-rendering.conf makes emoji rendering in Firefox worse Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: gerald_chen(a)foxmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874523 --> https://bugzilla.suse.com/attachment.cgi?id=874523&action=edit With 21.conf vs without 21.conf I've noticed that emoji look weird in Firefox, as shown in the upper side of the attachment (look at those spooky triangle eyes!). After deleting /etc/fonts/conf.d/21-emoji-rendering.conf, emoji got rendered properly, as shown in the lower side of the attachment. Other applications, such as Konsole and Chromium, don't have this problem. /etc/fonts/conf.d/21-emoji-rendering.conf says that emoji fonts don't need hinting. It seems not to be the case. My fontconfig file in home directory hasn't specified hinting or hintstyle. System info: Operating System: openSUSE Tumbleweed 20240423 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: Wayland Other files in /etc/fonts/conf.d: 09-autohint-if-no-hinting.conf 10-hinting-slight.conf 10-rendering-options.conf 10-scale-bitmap-fonts.conf 10-sub-pixel-none.conf 10-yes-antialias.conf 11-base-rendering.conf 11-lcdfilter-default.conf 12-tt-monospace-rendering.conf 13-selective-rendering.conf 13-selective-rendering-ipa.conf 20-unhint-small-vera.conf 22-noto-cjk-rendering.conf 30-metric-aliases.conf 31-metric-aliases-bw.conf 32-emoji-reject.conf 32-symbol-substitution.conf 40-nonlatin.conf 45-generic.conf 45-latin.conf 48-spacing.conf 49-family-default.conf 49-family-default-emoji.conf 49-sansserif.conf 55-local.conf 56-user.conf 58-family-prefer-local.conf 59-family-prefer-lang-specific-cjk.conf 59-family-prefer-lang-specific.conf 59-family-prefer-lang-specific-noto.conf 60-family-prefer.conf 60-generic.conf 61-latin.conf 61-stix.conf 61-wine-aliases.conf 65-fonts-persian.conf 65-nonlatin.conf 69-unifont.conf 70-reject.conf 80-delicious.conf 90-synthetic.conf README -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1230281] New: crash: dminfo.so reproducible builds issue
by bugzilla_noreply＠suse.com 30 Nov '24

30 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1230281 Bug ID: 1230281 Summary: crash: dminfo.so reproducible builds issue 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: 1102408 Target Milestone: --- Found By: Development Blocker: --- Created attachment 877173 --> https://bugzilla.suse.com/attachment.cgi?id=877173&action=edit diff of strings output While working on reproducible builds for openSUSE, I found that our crash package's dminfo.so varied between -j1 and -j4 (kvm) osc builds The -j1 version contains the string _ITM_deregisterTMCloneTable while the -j4 version does not. This indicates that there is some build-time race condition that causes this and it should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213879] New: Could not allocate memory for RTAS
by bugzilla_noreply＠suse.com 28 Nov '24

28 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213879 Bug ID: 1213879 Summary: Could not allocate memory for RTAS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: PowerPC OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: screening-team-bugs(a)suse.de Reporter: dmitriy.markov(a)mezame.ru QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: Good afternoon. While booting from iso for further installation of the system, I encountered the error "Could not allocate memory for RTAS". The problem is only present in the openSUSE Leap 15.5 ppc64le distribution. OpenSUSE Leap 15.4 ppc64le does not have this problem. Of course, on the Internet there was a solution from the equipment manufacturer. (https://www.ibm.com/support/pages/could-not-allocate-memory-rtas-grub-or-ya…) But it does not help and the error remains. My opinion is that this is a bug in the distribution, if it is not, please let me know about it. Reproducible: Always Steps to Reproduce: 1.Booting LPAR from CD/DVD openSUSE-Leap-15.5-DVD-ppc64le-Media.iso 2.In the bootloader, select "install operating system" 3.We get an error Actual Results: We get an error Welcome to GRUB! search prep from disk `ieee1275//vdevice/v-s csi@3000000b/disk@8100000000000000' error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. earlycfg: root=memdisk prefix=(memdisk)/ bdev=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000 bpart=,1 bpath=/boot/ppc64le/grub2-ieee1275 Reading vars from (ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000) error: ../../grub-core/commands/prep_loadenv.c:179:no prep partition. ENV_HINT= ENV_GRUB_DIR= ENV_FS_UUID= searching for /boot/ppc64le/grub2-ieee1275/grub.cfg /boot/ppc64le/grub2-ieee1275/grub.cfg is on ieee1275//vdevice/v-scsi@3000000b/disk@81000 00000000000,1 prefix=(ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1)/boot/ppc64le /grub2-ieee1275 root=ieee1275//vdevice/v-scsi@3000000b/disk@8100000000000000,1 Loading kernel ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 5.14.21-150500.53-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binut ils; SUSE Linux Enterprise 15) 2.39.0.20220810-150100.7.40) #1 SMP Wed May 10 07:56:26 UTC 2023 (b630043) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/boot/ppc64le/linux Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : 0000000000000000 (16 MB aligned) alloc_bottom : 000000001fef0000 alloc_top : 0000000020000000 alloc_top_hi : 0000000020000000 rmo_top : 0000000020000000 ram_top : 0000000020000000 Could not allocate memory for RTAS EXIT called ok 0 > Expected Results: The system installer is loading iso SHA-256 checksum - pass My HW - IBM Power E880 SLES 12SP5 - also not affected by this error. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1228274] New: lxc-net does not work without iptables and dnsmasq, and lxc does not work without apparmor
by bugzilla_noreply＠suse.com 27 Nov '24

27 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228274 Bug ID: 1228274 Summary: lxc-net does not work without iptables and dnsmasq, and lxc does not work without apparmor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: fijik19(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- It seems, that lxc-net service does not work without iptables and dnsmasq, which is not required by lxc package, also, lxc-start fails without apparmor-profiles package installed -- You are receiving this mail because: You are on the CC list for the bug.

1 1