April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220715] New: postfix 3.8.5-2.1: myhostname variable broken
by bugzilla_noreply＠suse.com 19 Jul '24

19 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220715 Bug ID: 1220715 Summary: postfix 3.8.5-2.1: myhostname variable broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: draeath(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873135 --> https://bugzilla.suse.com/attachment.cgi?id=873135&action=edit archive of /etc/postfix in case the contents post package installation After updating my tumbleweed system today to postfix-3.8.5-2.1.x86_64, postfix no longer starts. To ensure it wasn't something I had done, I moved the whole of /etc/postfix aside, and reinstalled the package. The daemon failed in the same way with fresh default configurations: Feb 29 12:38:18 my.redacted.fqdn systemd[1]: Starting Postfix Mail Transport Agent... Feb 29 12:38:18 my.redacted.fqdn echo[28183]: Starting mail service (Postfix) Feb 29 12:38:18 my.redacted.fqdn (storecon)[28311]: postfix.service: Executable /sbin/restorecon missing, skipping: No such file or directory Feb 29 12:38:18 my.redacted.fqdn update_postmaps[28498]: postmap: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:18 my.redacted.fqdn postfix/postmap[28498]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:19 my.redacted.fqdn update_postmaps[29383]: postmap: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:19 my.redacted.fqdn postfix/postmap[29383]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:20 my.redacted.fqdn update_postmaps[29475]: postmap: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:20 my.redacted.fqdn postfix/postmap[29475]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:21 my.redacted.fqdn update_postmaps[29477]: postmap: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:21 my.redacted.fqdn postfix/postmap[29477]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:22 my.redacted.fqdn update_postmaps[29480]: postmap: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:22 my.redacted.fqdn postfix/postmap[29480]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:23 my.redacted.fqdn update_postmaps[29487]: postalias: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:23 my.redacted.fqdn postfix/postalias[29487]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:24 my.redacted.fqdn postfix[29489]: postfix: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:24 my.redacted.fqdn postfix[29489]: fatal: bad string length 0 < 1: myhostname = Feb 29 12:38:25 my.redacted.fqdn systemd[1]: postfix.service: Control process exited, code=exited, status=1/FAILURE Feb 29 12:38:25 my.redacted.fqdn systemd[1]: postfix.service: Failed with result 'exit-code'. Feb 29 12:38:25 my.redacted.fqdn systemd[1]: Failed to start Postfix Mail Transport Agent. ginnungagap:~ # postfix check postfix: fatal: bad string length 0 < 1: myhostname = hostnamectl reports a static hostname of my FQDN, with a pretty hostname of just the hostname component. I have had this configuration for years. I have attached /etc/postfix in case that should be useful (ie in case some postinst scripts are mangling it). The directory was absent prior to reinstalling the package, and I made no changes. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1222395] New: mariadbd crashes with Illegal Instruction
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222395 Bug ID: 1222395 Summary: mariadbd crashes with Illegal Instruction Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: RISC-V OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- # /usr/sbin/mariadbd --lc-messages=en_US --bootstrap --silent-startup --basedir=/usr --datadir=/var/lib/mysql --log-warnings=0 --enforce-storage-engine= --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mysql/mysqld.log --max_allowed_packet=8M --net_buffer_length=16K Illegal instruction (core dumped) # cat /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20240404" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20240404" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" # CPE 2.3 format, boo#1217921 CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240404:*:*:*:*:*:*:*" #CPE 2.2 format #CPE_NAME="cpe:/o:opensuse:tumbleweed:20240404" 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:Tumbleweed" LOGO="distributor-logo-Tumbleweed" # uname -r 6.9.0-rc2-89-default (gdb) bt #0 0x0000002ad529bed4 in my_timer_init () #1 0x0000002ad4bfa35e in mysqld_main(int, char**) () #2 0x0000003fa682a668 in __libc_start_call_main () from /lib64/lp64d/libc.so.6 #3 0x0000003fa682a710 in __libc_start_main_impl () from /lib64/lp64d/libc.so.6 #4 0x0000002ad4bc1538 in _start () (gdb) disas Dump of assembler code for function my_timer_init: 0x0000002ad529bea0 <+0>: add sp,sp,-176 0x0000002ad529bea2 <+2>: sd s0,160(sp) 0x0000002ad529bea4 <+4>: sd s1,152(sp) 0x0000002ad529bea6 <+6>: sd ra,168(sp) 0x0000002ad529bea8 <+8>: sd s2,144(sp) 0x0000002ad529beaa <+10>: sd s3,136(sp) 0x0000002ad529beac <+12>: sd s4,128(sp) 0x0000002ad529beae <+14>: sd s5,120(sp) 0x0000002ad529beb0 <+16>: sd s6,112(sp) 0x0000002ad529beb2 <+18>: sd s7,104(sp) 0x0000002ad529beb4 <+20>: sd s8,96(sp) 0x0000002ad529beb6 <+22>: add s0,sp,176 0x0000002ad529beb8 <+24>: lui a5,0x3b9ad 0x0000002ad529bebc <+28>: add a5,a5,-1536 # 0x3b9aca00 0x0000002ad529bec0 <+32>: auipc a3,0x97b 0x0000002ad529bec4 <+36>: ld a3,960(a3) # 0x2ad5c17280 0x0000002ad529bec8 <+40>: mv s1,a0 0x0000002ad529beca <+42>: ld a4,0(a3) 0x0000002ad529becc <+44>: sd a4,-120(s0) 0x0000002ad529bed0 <+48>: li a4,0 0x0000002ad529bed2 <+50>: sd a5,16(a0) => 0x0000002ad529bed4 <+52>: rdcycle a5 0x0000002ad529bed8 <+56>: beqz a5,0x2ad529c182 <my_timer_init+738> objdump -d: d23ed4: c00027f3 rdcycle a5 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1217306] New: distrobox stuck at starting container
by bugzilla_noreply＠suse.com 18 Jul '24

18 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1217306 Bug ID: 1217306 Summary: distrobox stuck at starting container Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 870843 --> https://bugzilla.suse.com/attachment.cgi?id=870843&action=edit few seconds of strace -p 5212 2>&1 | tee /tmp/strace-out.log Following happened on Leap 15.6 lkocman@localhost:~/Workspace> distrobox enter mirror Error: no such container mirror Cannot find container mirror Creating the container with command: /usr/bin/distrobox-create -i registry.opensuse.org/opensuse/distrobox:latest -n mirror Trying to pull registry.opensuse.org/opensuse/distrobox:latest... Getting image source signatures Copying blob 942e611a39d7 done Copying blob 1517c1ea8bb6 done Copying config 8372decf75 done Writing manifest to image destination 8372decf752e74665fcb94d31b9b378dd1790233ab36b03d37f63dac462e0fbc Creating 'mirror' using image registry.opensuse.org/opensuse/distrobox:latest [ OK ] Distrobox 'mirror' successfully created. To enter, run: distrobox enter mirror Container mirror is not running. Starting container mirror run this command to follow along: podman logs -f mirror Starting container... # Stuck here for 30 minutes or so lkocman@localhost:~/Workspace> ps aux | grep distro lkocman 5210 0.0 0.0 11096 3328 pts/0 S+ 08:13 0:00 /bin/sh /usr/bin/distrobox enter mirror lkocman 5212 2.1 0.0 11224 3840 pts/0 S+ 08:13 0:53 /bin/sh /usr/bin/distrobox-enter mirror lkocman 27424 0.0 0.0 8212 2304 pts/1 S+ 08:56 0:00 grep --color=auto distro Strace seems that the program itself is busy Not sure if this isn't an issue rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=27782, si_uid=1000, si_status=0, si_utime=2, si_stime=0} --- wait4(-1, 0x7ffc3cd5bbd0, WNOHANG, NULL) = -1 ECHILD (No child processes) rt_sigreturn({mask=[]}) = 0 openat(AT_FDCWD, "/home/lkocman/.cache/.mirror.fifo", O_RDONLY) = 3 fcntl(0, F_GETFD) = 0 fcntl(0, F_DUPFD, 10) = 10 fcntl(0, F_GETFD) = 0 fcntl(10, F_SETFD, FD_CLOEXEC) = 0 dup2(3, 0) = 0 close(3) = 0 ioctl(0, TCGETS, 0x7ffc3cd5c4f0) = -1 ENOTTY (Inappropriate ioctl for device) -- You are receiving this mail because: You are on the CC list for the bug.

1 22

[Bug 1222533] New: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222533 Bug ID: 1222533 Summary: Libreoffice needs 100% CPU for 3 minutes to open Lenovo compatibility matrix Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874156 --> https://bugzilla.suse.com/attachment.cgi?id=874156&action=edit perf record data for loading the file with native TW package Upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=160595 Environment: OpenSUSE Tumbleweed 20240329, GNOME/X11, libreoffice-calc-24.2.2.2-1.2.x86_64 Offending file: Lenovo Accessories and Options Compatibility Matrix (OCM) https://download.lenovo.com/pccbbs/options_iso/ocm_apr_2024.xlsx (access via http://www.lenovo.com/accessoriesguide) Steps to reproduce: Download and open the file with calc. Results: Calc hangs with 100% CPU with "load document" progress bar at ~80%. It finishes after ~3 minutes. With the flatpak version of Libreoffice, opening the file takes only ~15s. "perf report" shows for the openSUSE native package: Samples: 520K of event 'cycles:P', Event count (approx.): 366840243651 Overhead Command Shared Object Symbol 49.69% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7a8 27.60% soffice.bin libglib-2.0.so.0.8000.0 [.] g_node_insert_before 2.49% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7ac 1.32% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7af 0.85% soffice.bin libgtk-3.so.0.2409.32 [.] 0x000000000030d7b7 0.43% soffice.bin libc.so.6 [.] malloc 0.27% soffice.bin libuno_cppu.so.3 [.] typelib_typedescriptionreference_equals 0.23% soffice.bin libc.so.6 [.] _int_free -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1218122] New: Aeon: Unable to load any usable ISO8859 font
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1218122 Bug ID: 1218122 Summary: Aeon: Unable to load any usable ISO8859 font Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Base Assignee: rbrown(a)suse.com Reporter: alexlevinb(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: I am getting Unable to load any usable ISO8859 font error when installing Veracrypt with ./veracrypt-1.26.7-setup-gtk3-gui-x64 Same error when running xmessage test: alex@dell-desktop:~> xmessage test Warning: Unable to load any usable ISO8859 font Error: Aborting: no font found I am getting the sam Reproducible: Always Steps to Reproduce: Run xmessage test -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1219979] New: Bash exported function are renamed internally then are ignored by Systemd - Kde desktop
by bugzilla_noreply＠suse.com 17 Jul '24

17 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1219979 Bug ID: 1219979 Summary: Bash exported function are renamed internally then are ignored by Systemd - Kde desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: jcdole(a)free.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have bash definition functions and variables that are sourced from /etc/profile.d (case 1) or from ~/.profile (case 2) In case 1, journald show : Feb 15 17:13:55 15-4---G731GV-VM-04 startplasma-x11[1725]: Skipping syncing of environment variable "BASH_FUNC__MY_ECHO_%%" as name contains unsupported characters None of my function are exported to user environment. None of my functions use the double characters '%%' I have environment variables that defined colors : MY_LIGHT_RED=$'\e[1;31m' Journald show : Feb 15 17:13:55 15-4---G731GV-VM-04 startplasma-x11[1725]: Skipping syncing of environment variable "MY_LIGHT_RED" as value contains unsupported characters These colors definition are not exported to user environment. In case 2, journald show the same errors but in this case functions and env var are exported to the user environment. Any help is very welcome. -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1220440] New: error: source_date_epoch_from_changelog set but %changelog is missing
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220440 Bug ID: 1220440 Summary: error: source_date_epoch_from_changelog set but %changelog is missing 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: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- private pkgs fail to build: error: source_date_epoch_from_changelog set but %changelog is missing private pkgs have no requirement for a %changelog tag nor a *.changes file in the pkg container. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213595] New: Live ISO does not creates Persistent storage
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1213595 Bug ID: 1213595 Summary: Live ISO does not creates Persistent storage Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: sehsuvarselmanoglu(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868398 --> https://bugzilla.suse.com/attachment.cgi?id=868398&action=edit 7z File for some logs Hi, I downloaded OpenSUSE Leap ISO (openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.40-Media.iso) at 08/06/2023 (as soon as released) then I “dd” to USB stick and plugged to computer and it worked fine. At first boot, it did create the persistent storage cow (boot.log : [ 22.002982] dracut-initqueue[877]: mke2fs 1.46.4 (18-Aug-2021) ) Few days later I download again this time build number was different (openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.57-Media.iso). At first boot, it did not create persistent storage. dracut says (boot.log : [ 21.489260] dracut-initqueue[769]: Warning: Falling back to temporary overlay) same as the new release (openSUSE-Leap-15.5-KDE-Live-x86_64-Build10.73-Media.iso) Any release after 10.40 does not creates persistent storage (neither 10.53 nor 10.73) I tried with different CPU (AMD, Core Duo, I5) and different USB stick (4GB 8GB 16GB and 32GB) even with different port (USB2 USB3) with different USB s and so on. No matter what I tried don't work. Releases after 10.40 (10.57 or 10.73) do not creates the persistent storage. So I open discussion on the forums.opensuse.org and someone suggested that I need to open bug report. and he/she wrote "It is not something you can fix without recreating initrd. The script that is used here comes from kiwi dracut module.". I also add the 7zip file for each ISO "....10.40", "...10.57", "...10.73" that contains some log files. "boot.log" : "sudo cp /var/log/boot.log" "boot.msg" : "cp /var/log/boot.msg" "dmesg.txt" : Output of "dmesg" right after the first boot "fdisk.txt" : 0utput of "fdisk -l" right after first boot "journal.txt" : Output of "sudo journalctl --no-pager --full -b" Thank you very much. -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1214353] New: mhi: Enabling broadband connecting not working
by bugzilla_noreply＠suse.com 16 Jul '24

16 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1214353 Bug ID: 1214353 Summary: mhi: Enabling broadband connecting not working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868851 --> https://bugzilla.suse.com/attachment.cgi?id=868851&action=edit hwinfo.txt When trying to use broadband connecting with network manager, I can not get beyond entering SIM code - starting connection does not work System Slot: #36 Designation: "M.2 WWAN Connector (J3702)" Type: 0xa6 (Other) Bus Width: 0x08 (Other) Status: 0x03 (Available) Length: 0x04 (Long) Slot ID: 4 Characteristics: 0x0704 (3.3 V, PME#, Hot-Plug) -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1222695] New: lensfun‑update‑data command does not work
by bugzilla_noreply＠suse.com 15 Jul '24

15 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222695 Bug ID: 1222695 Summary: lensfun‑update‑data command does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The lensfun‑update‑data command does not work. To update the lensfun database, you need to specify the full path to the program /usr/bin/lensfun-update-data -- You are receiving this mail because: You are on the CC list for the bug.

1 1