July 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1213043] New: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213043 Bug ID: 1213043 Summary: windows:mingw:win{32|64}/mingw{32|64}-cross-cmake: no version support for generated mingw32(cmake:xxx) provides Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- Qt6 packages often uses dependencies to cmake package including a version as shown below: %package devel Summary: Qt 6 base development meta package Requires: qt6-base-common-devel Requires: cmake(Qt6Concurrent) = %{real_version} Requires: cmake(Qt6Core) = %{real_version} Requires: cmake(Qt6DBus) = %{real_version} Requires: cmake(Qt6Gui) = %{real_version} Requires: cmake(Qt6Network) = %{real_version} Requires: cmake(Qt6OpenGL) = %{real_version} Requires: cmake(Qt6OpenGLWidgets) = %{real_version} Requires: cmake(Qt6PrintSupport) = %{real_version} Requires: cmake(Qt6Sql) = %{real_version} Requires: cmake(Qt6Test) = %{real_version} Requires: cmake(Qt6Widgets) = %{real_version} Requires: cmake(Qt6Xml) = %{real_version} BuildArch: noarch https://build.opensuse.org/package/view_file/KDE:Qt6/qt6-base/qt6-base.spec… Cmake-related provides generated by the named package do not currently support versions. This means that when porting Qt6 packages to MinGW, the versions would have to be removed manually or via script. It would therefore be helpful if a version were available for these generated "Provides". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213028] New: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support
by bugzilla_noreply＠suse.com 07 Mar '24

07 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213028 Bug ID: 1213028 Summary: windows:mingw:win{32|64}/mingw{32|64}-libmng: no pkgconfig support Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- On building mingw32-qt6-imageformat for MinGW it turned out that the mentioned package does not have pkgconfig support ~/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats> osc build openSUSE_Leap_15.5 -j12 Building mingw32-qt6-imageformats.spec for openSUSE_Leap_15.5/x86_64 Getting buildconfig from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildconfig-openSUSE_Leap_15.5-x86_64 Getting buildinfo from server and store to /home/osc/home:rhabacker:branches:windows:mingw:win32:Qt65/mingw32-qt6-imageformats/.osc/_buildinfo-openSUSE_Leap_15.5-x86_64.xml buildinfo is broken... it says: unresolvable: nothing provides mingw32(pkg:libmng) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1213384] New: Jul-2023 update of windows 10/11 breaks trust relationship
by bugzilla_noreply＠suse.com 27 Feb '24

27 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213384 Bug ID: 1213384 Summary: Jul-2023 update of windows 10/11 breaks trust relationship Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: nopower(a)suse.com QA Contact: samba-maintainers(a)SuSE.de Target Milestone: --- Found By: --- Blocker: --- Reports of users getting errors like "The trust relationship between this workstation and the primary domain failed." have been reported upstream since applying updates KB5028166 / KB5028185. this at least affects samba domain controllers (AD & PDC I believe) it also apparently can affect rdp access. upstream bug https://bugzilla.samba.org/show_bug.cgi?id=15418 -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1213353] New: bash crash during autocompletion: systemctmalloc_consolidate(): unaligned fastbin chunk detected
by bugzilla_noreply＠suse.com 23 Feb '24

23 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213353 Bug ID: 1213353 Summary: bash crash during autocompletion: systemctmalloc_consolidate(): unaligned fastbin chunk detected Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: werner(a)suse.com Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868226 --> https://bugzilla.suse.com/attachment.cgi?id=868226&action=edit bash screendump and coredumpctl output with intact linebreaks I just had the following bash crash during autocompletion: Unfortunately I don't remember exactly what I did when bash crashed. The only hint that I can offer is that my prompt starts with $? if it's non-zero. The last propmt line indicates that $? was [INT] ====================================================================== cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl enable -- --after --defaults --firmware-setup --help --legend=no --no-ask-password --now --plain --recursive --show-types --timestamp --version --all --dry-run --force --host --lines --no-block --no-wall --preset-mode --reverse --signal --type --wait --before --fail --full --job-mode --machine --no-pager --no-warn --property --root --state --user --check-inhibitors --failed --global --kill-whom --message --no-reload --output --quiet --runtime --system --value cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl enable --no --no-ask-password --no-block --no-pager --no-reload --now --no-wall --no-warn cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctl e [INT] cb@tux:~/isotopp.github.io/content/posts cboltz-typo52 L …4> systemctmalloc_consolidate(): unaligned fastbin chunk detected Achtung: Das Programm „/bin/bash“ ist abgestürzt. ====================================================================== ====================================================================== # coredumpctl dump bash PID: 13069 (bash) UID: 1000 (cb) GID: 100 (users) Signal: 6 (ABRT) Timestamp: Fri 2023-07-14 19:58:42 CEST (8min ago) Command Line: /bin/bash Executable: /usr/bin/bash Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-kde_autostart@autostart.service Unit: user(a)1000.service User Unit: app-kde_autostart(a)autostart.service Slice: user-1000.slice Owner UID: 1000 (cb) Boot ID: c4b7162d927340e9995cb85273857589 Machine ID: abf06ac46e2e487ea0edd474065e8b87 Hostname: tux.boltz Storage: /var/lib/systemd/coredump/core.bash.1000.c4b7162d927340e9995cb85273857589.13069.1689357522000000.zst (present) Size on Disk: 722.5K Message: Process 13069 (bash) of user 1000 dumped core. Stack trace of thread 13069: #0 0x00007fe721781a7c __pthread_kill_implementation (libc.so.6 + 0x8fa7c) #1 0x00007fe721730226 raise (libc.so.6 + 0x3e226) #2 0x00007fe721718921 abort (libc.so.6 + 0x26921) #3 0x00007fe721719611 __libc_message.cold (libc.so.6 + 0x27611) #4 0x00007fe72178c417 malloc_printerr (libc.so.6 + 0x9a417) #5 0x00007fe72178d03c malloc_consolidate (libc.so.6 + 0x9b03c) #6 0x00007fe72178f6b8 _int_malloc (libc.so.6 + 0x9d6b8) #7 0x00007fe721790aba __libc_malloc (libc.so.6 + 0x9eaba) #8 0x000055ff5a6938ee xmalloc (bash + 0x758ee) #9 0x000055ff5a69fd61 n/a (bash + 0x81d61) #10 0x000055ff5a6b98cf map_over_funcs (bash + 0x9b8cf) #11 0x000055ff5a6818f6 all_visible_functions (bash + 0x638f6) #12 0x000055ff5a68dc6a command_word_completion_function (bash + 0x6fc6a) #13 0x00007fe72190cddb rl_completion_matches (libreadline.so.8 + 0x1dddb) #14 0x000055ff5a68c7a0 bash_default_completion (bash + 0x6e7a0) #15 0x00007fe72190cef3 n/a (libreadline.so.8 + 0x1def3) #16 0x00007fe72191579c rl_complete_internal (libreadline.so.8 + 0x2679c) #17 0x00007fe72190d178 _rl_dispatch_subseq (libreadline.so.8 + 0x1e178) #18 0x00007fe72190dfa6 readline_internal_char (libreadline.so.8 + 0x1efa6) #19 0x00007fe721916f65 readline (libreadline.so.8 + 0x27f65) #20 0x000055ff5a65ce67 n/a (bash + 0x3ee67) #21 0x000055ff5a69904e n/a (bash + 0x7b04e) #22 0x000055ff5a697394 n/a (bash + 0x79394) #23 0x000055ff5a696be7 yyparse (bash + 0x78be7) #24 0x000055ff5a696821 parse_command (bash + 0x78821) #25 0x000055ff5a6a2c8e read_command (bash + 0x84c8e) #26 0x000055ff5a6a2919 reader_loop (bash + 0x84919) #27 0x000055ff5a6b5f04 main (bash + 0x97f04) #28 0x00007fe721719bb0 __libc_start_call_main (libc.so.6 + 0x27bb0) #29 0x00007fe721719c79 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c79) #30 0x000055ff5a6b4fe5 _start (bash + 0x96fe5) ELF object binary architecture: AMD x86-64 Refusing to dump core to tty (use shell redirection or specify --output). ====================================================================== I can provide the full coredump on request. Unfortunately it contains private data (for example filenames from the bash history), therefore I don't want to attach it to a public bugreport. However, I can send it by mail if needed. [Note to myself: the coredump is in ~/susebeta/2023-07-14-*.zst] The attached file contains the above bash screendump and coredumpctl output, just in case bugzilla inserts funny linebreaks. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1213757] New: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi
by bugzilla_noreply＠suse.com 20 Feb '24

20 Feb '24

https://bugzilla.suse.com/show_bug.cgi?id=1213757 Bug ID: 1213757 Summary: All processes that try to communicate with NETLINK socket hang up if running hostapd on Raspberry Pi Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868483 --> https://bugzilla.suse.com/attachment.cgi?id=868483&action=edit strace of hanging "ip a" The issue appears a few (~5) minutes after hostapd is started. Jul 28 12:47:40 openqa-piworker systemd[1]: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator. Jul 28 12:47:40 openqa-piworker hostapd[15307]: Configuration file: /etc/hostapd.conf Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:40 openqa-piworker kernel: br0: port 1(wlan0) entered disabled state Jul 28 12:47:40 openqa-piworker kernel: device wlan0 entered promiscuous mode Jul 28 12:47:40 openqa-piworker hostapd[15307]: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service' requested by ':1.31' (uid=0 pid=730 comm="/usr/sbin/wickedd --systemd --foreground ") Jul 28 12:47:41 openqa-piworker systemd[1]: Starting WPA Supplicant daemon... Jul 28 12:47:41 openqa-piworker dbus-daemon[629]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Jul 28 12:47:41 openqa-piworker systemd[1]: Started WPA Supplicant daemon. Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: Could not connect to kernel driver Jul 28 12:47:45 openqa-piworker hostapd[15307]: Using interface wlan0 with hwaddr e4:5f:01:bb:63:41 and ssid "openQA-worker" Jul 28 12:47:45 openqa-piworker kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered blocking state Jul 28 12:47:45 openqa-piworker kernel: br0: port 1(wlan0) entered forwarding state Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: interface state COUNTRY_UPDATE->ENABLED Jul 28 12:47:45 openqa-piworker hostapd[15307]: wlan0: AP-ENABLED openqa-piworker:~ # cat /etc/sysconfig/network/ifcfg-br0 IPADDR='192.168.7.1/24' BOOTPROTO='static' STARTMODE='auto' BRIDGE='yes' BRIDGE_PORTS='' BRIDGE_STP='off' BRIDGE_FORWARDDELAY='15' ZONE=dmz openqa-piworker:~ # cat /etc/hostapd.conf interface=wlan0 bridge=br0 ssid=openQA-worker wpa_passphrase=0foobar12345 driver=nl80211 country_code=DE hw_mode=g channel=7 # Bit field: bit0 = WPA, bit1 = WPA2, 3=both wpa=2 # Bit field: 1=wpa, 2=wep, 3=both auth_algs=1 wpa_pairwise=CCMP wpa_key_mgmt=WPA-PSK logger_stdout=-1 logger_stdout_level=2 openqa-piworker:~ # systemctl cat hostapd.service # /usr/lib/systemd/system/hostapd.service [Unit] Description=Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator After=network.target [Service] ExecStart=/usr/sbin/hostapd /etc/hostapd.conf ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target # /etc/systemd/system/hostapd.service.d/override.conf # Ensure that wlan0 is up before starting hostapd (otherwise hostapd will not add wlan0 to the bridge) [Unit] BindsTo=sys-subsystem-net-devices-wlan0.device After=sys-subsystem-net-devices-wlan0.device -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1213477] New: Update to gutenprint 5.3 broke cups config
by bugzilla_noreply＠suse.com 05 Jan '24

05 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1213477 Bug ID: 1213477 Summary: Update to gutenprint 5.3 broke cups config Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: dheidler(a)suse.com QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- From cups log: E [19/Jul/2023:14:07:42 +0200] Samsung_Samsung_ML-2525W: Datei \"/usr/lib/cups/filter/rastertogutenprint.5.2\" nicht verfügbar: No such file or directory E [19/Jul/2023:14:07:42 +0200] [Job 49] Unable to start filter "rastertogutenprint.5.2" - No such file or directory. E [19/Jul/2023:14:07:42 +0200] [Job 49] Stopping job because the scheduler could not execute a filter. From cups config: <Printer Samsung_Samsung_ML-2525W> PrinterId 45 UUID urn:uuid:70334a01-d800-39ed-5a4e-5e4f45e9c01f Info Samsung Samsung ML-2525W Location MakeModel Samsung ML-2550 - CUPS+Gutenprint v5.2.15 DeviceURI socket://10.131.0.20 State Idle StateTime 1689768462 ConfigTime 1689767864 Type 8392724 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#000000 Attribute marker-levels 50 Attribute marker-names Toner S/N:CRUM-11000311613 Attribute marker-types toner Attribute marker-change-time 1683056782 </Printer> It seems that the config was not updated breaking the printing driver as the config was still pointing to gutenprint 5.2. This should be somehow prevented - eg by not including the version number in the config or updating the config automatically. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1213152] New: noto sans display gets mismatched for regular noto sans and noto serif has not properly matched styles
by bugzilla_noreply＠suse.com 21 Dec '23

21 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213152 Bug ID: 1213152 Summary: noto sans display gets mismatched for regular noto sans and noto serif has not properly matched styles Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: screening-team-bugs(a)suse.de Reporter: piotrus3g(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868101 --> https://bugzilla.suse.com/attachment.cgi?id=868101&action=edit I think the family property should only be Noto Sans Display and Noto Serif Display for the display versions of the fonts Hello, I noticed that in mpv after changing my default preferences for system sans-serif font I get Noto Sans Display, even though I've set it to normal Noto Sans. When I go to the kde font viewer there is only the Noto Sans font family, but there is no Noto Sans Display. With Noto Serif there is Noto Serif Display, but there are only italic versions of the font. My guess is that the display versions of the fonts shouldn't be in the normal Noto Sans/Noto Serif families. They should be a different family named Noto Sans Display/Noto Serif Display. The Noto Serif Display is a different family in the kde font viewer, but comparing the output of fc-match -a "Noto Serif" and fc-match -a "Noto Sans" gives something interesting: the display versions of the fonts belong to the normal noto font families, so when I want it to match "Noto Sans" I get the one that is alphabetically the first one (will give output in attachment). The serif one gets matched with the regular one first as the names of the noto serif display and noto sans display fonts are without and with a hyphen between the display in the font file name (alphabetically first is "-", "D" is after). The terminal output shows what is going on with the families. Thanks for any help -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1213830] New: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213830 Bug ID: 1213830 Summary: rather current notebook hw (from 2021) has no deep sleep /sys/power/mem_sleep - desktop hw and really old hw does have it Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: abittner(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello Opensuse Kernel team, how come that my rather new notebook hardware (hp probook with amd apu, from 2021) does not sleep properly and eats up the battery all the time. barely any difference between when leaving an idle desktop (KDE) sitting around and blanking the screen and when only s2idle sleeping it (lid close, or kde function: sleep) i have tried to make sense of all of this, also reading about the linux folks over at framework-laptop e.g. <https://community.frame.work/t/responded-linux-deep-sleep/2491> all i can find is the value: cat /sys/power/mem_sleep [s2idle] cat /sys/power/state freeze mem disk also added the kernel boot parameter mem_sleep_default=deep command line via yast2 to grub2 or something: ---------- sudo dmesg -e | grep mem_sleep [ +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto [ +0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.7-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap preempt=full quiet security=apparmor mem_sleep_default=deep mitigations=auto --------------- to sum it up, the system eats away the battery/power at high rates even when sleeping, lid closed etc. how to make this work on leap 15.5 with proper (deep?) memory sleep states and all? is this maybe incompatible with FDE, secureboot? this kernel lockdown stuff? i am not understanding much of this i guess. i am wondering why a really old system and other also older desktop systems just instantly show deep mem_sleep feature activated and working? this system: UEFI ans secureboot system [ +0.109168] smpboot: CPU0: AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0) full disk encryption on single nvme drive thanks for helping. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1213217] New: ceph: fails to build against fmt 10.0
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213217 Bug ID: 1213217 Summary: ceph: fails to build against fmt 10.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: ceph-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868147 --> https://bugzilla.suse.com/attachment.cgi?id=868147&action=edit ceph ftbs with fmt 10 fmt 10.0 has been submitted for inclusion into Factory. During the staging process we have observed ceph failing to build, I'm attaching the full log. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1213177] New: Libreoffice FTBFS with GCC13 update (13.1.1+git7489)
by bugzilla_noreply＠suse.com 15 Dec '23

15 Dec '23

https://bugzilla.suse.com/show_bug.cgi?id=1213177 Bug ID: 1213177 Summary: Libreoffice FTBFS with GCC13 update (13.1.1+git7489) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: screening-team-bugs(a)suse.de Reporter: ana.guerrero(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868120 --> https://bugzilla.suse.com/attachment.cgi?id=868120&action=edit Libreoffice x86_64 build log Libreoffice fails to build with an update of GCC13 to 13.1.1+git7489. Please see the attached log. -- You are receiving this mail because: You are on the CC list for the bug.

1 2