October 2023 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1216042] New: Kernels fail to build in Kernel:stable:Backport
by bugzilla_noreply＠suse.com 06 Apr '24

06 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1216042 Bug ID: 1216042 Summary: Kernels fail to build in Kernel:stable:Backport Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recently updated binutils in openSUSE_Leap_15.4 generate new DT_ tags which dwarves does not know about: [ 1122s] Unsupported DW_TAG_unspecified_type(0x3b) [ 1122s] Encountered error while encoding BTF. osc branch --nodevelproject openSUSE:Factory dwarves Kernel:stable:Backport would probably solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214160] New: libvirt-routed firewalld zone not functional
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1214160 Bug ID: 1214160 Summary: libvirt-routed firewalld zone not functional 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: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- After a recent update of my virtual machines host (sorry for being fuzzy) I started seeing connections being dropped between the VMs and the host, specifically NFS. The interfaces are assigned to the libvirt-routed interface contributed by libvirt-daemon-driver-network. # firewall-cmd --get-active-zones (...) libvirt-routed interfaces: kubic-net-br virbr1 # rpm -qf /usr/lib/firewalld/zones/libvirt-routed.xml libvirt-daemon-driver-network-9.0.0-150500.6.11.1.x86_64 Once enabling firewalld dropped packages logging I see log entries such as Aug 10 13:08:02 vmhost002 kernel: "filter_IN_policy_libvirt-to-host_REJECT: "IN=virbr1 OUT= MAC=52:54:00:33:68:12:52:54:00:ce:5c:25:08:00 SRC=10.25.1.6 DST=10.25.0.1 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=54291 DF PROTO=TCP SPT=943 DPT=2049 WINDOW=64240 RES=0x00 SYN URGP=0 The nfs service should be allowed # firewall-cmd --info-zone=libvirt-routed | grep services services: http mountd mysql nfs rpc-bind # firewall-cmd --info-service=nfs nfs ports: 2049/tcp protocols: source-ports: modules: destination: includes: helpers: What is worrying me and pointing to a bug are the following messages from the system journal which point to the firewalld zone not being functional Aug 09 13:12:36 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'RUNNING', False, 'public', {'nf_nat_tftp': 4}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:12:36 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'RUNNING', False, 'public', {'nf_nat_tftp': 4}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:13:33 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', False, 'public', {}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Aug 09 13:13:33 vmhost002 firewalld[17692]: ERROR: Calling pre func <bound method Firewall.full_check_config of <class 'firewall.core.fw.Firewall'>(True, True, True, 'INIT', False, 'public', {'nf_nat_tftp': 1}, [], True, True, True, False, 'all')>(()) failed: INVALID_ZONE: 'libvirt-routed' not among existing zones Happy to provide more information if needed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1215981] New: Black Screen during boot on both internal and external screen in kernel 6.5.4-1 on Thinkpad P16 (Discrete Graphics mode)
by bugzilla_noreply＠suse.com 04 Apr '24

04 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1215981 Bug ID: 1215981 Summary: Black Screen during boot on both internal and external screen in kernel 6.5.4-1 on Thinkpad P16 (Discrete Graphics mode) 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have similar problem to #1213693, but on newer kernel 6.5.4-1, which should contain the fix. #1213693 was broken by commit ca62297b2085 ("drm/edid: Fix csync detailed mode parsing") in v6.4-rc1, which was fixed by revert it in 50b6f2c82977 ("Revert "drm/edid: Fix csync detailed mode parsing"") in v6.5-rc7. In my case I'm not able to see anything after kernel being loaded. I have Tumbleweed kernel 6.5.4-1 and 6.5.2-1. Problem is on Thinkpad P16 with 2 GPU: 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-HX GT1 [UHD Graphics 770] (rev 0c) 01:00.0 VGA compatible controller: NVIDIA Corporation GA107GLM [RTX A1000 Laptop GPU] (rev a1) The problem is on "Discrete Graphics" (Nvidia only) mode. "Hybrid Graphics" (Intel + Nvidia) works, but I need for external screen to use "Discrete Graphics" as it's the only way to get external screens working (because external output is wired only to nvidia): i.e. on Discrete Graphics there is only Intel card being used $ drm_info |grep -i node: -A1 Node: /dev/dri/card0 Driver: i915 (Intel Graphics) version 1.6.0 (20201103) I tested with internal screen only and with internal screen + 2 external GPU. I tested to disable plymouth with rd.plymouth=0 plymouth.enable=0 plymouth=0 cmdline args, also tried fbcon=map:1 also boot to runlevel 1 and 3 instead the default. None helped. $ rpm -qa |grep -i -e nouveau -e intel -e ^kernel kernel-firmware-nvidia-gsp-G06-525.116.04-2.1.x86_64 kernel-firmware-nvidia-gspx-G06-535.113.01-1.1.x86_64 kernel-firmware-serial-20230829-1.1.noarch libdrm_nouveau2-2.4.116-2.1.x86_64 intel-vaapi-driver-2.4.1-5.11.x86_64 kernel-firmware-mwifiex-20230829-1.1.noarch xf86-video-intel-2.99.917.916_g31486f40-3.6.x86_64 kernel-firmware-platform-20230829-1.1.noarch kernel-firmware-intel-20230829-1.1.noarch kernel-firmware-iwlwifi-20230829-1.1.noarch kernel-firmware-all-20230829-1.1.noarch intel-media-driver-23.3.3-1.1.x86_64 ucode-intel-20230808-1.1.x86_64 kernel-firmware-nvidia-gsp-G06-535.54.03-1.1.x86_64 kernel-firmware-amdgpu-20230829-1.1.noarch kernel-firmware-usb-network-20230829-1.1.noarch kernel-firmware-i915-20230829-1.1.noarch kernel-macros-6.5.4-1.1.noarch kernel-firmware-qcom-20230829-1.1.noarch libvulkan_intel-23.2.0-1699.360.pm.1.x86_64 intel-gpu-tools-1.27.1-2.3.x86_64 kernel-firmware-sound-20230829-1.1.noarch kernel-firmware-ath10k-20230829-1.1.noarch libvdpau_nouveau-23.2.0-1699.360.pm.1.x86_64 kernel-firmware-bnx2-20230829-1.1.noarch Mesa-dri-nouveau-23.2.0-1699.360.pm.1.x86_64 kernel-firmware-dpaa2-20230829-1.1.noarch kernel-firmware-atheros-20230829-1.1.noarch kernel-firmware-radeon-20230829-1.1.noarch kernel-firmware-ueagle-20230829-1.1.noarch kernel-firmware-brcm-20230829-1.1.noarch kernel-firmware-chelsio-20230829-1.1.noarch kernel-firmware-nvidia-20230829-1.1.noarch kernel-firmware-ti-20230829-1.1.noarch kernel-firmware-media-20230829-1.1.noarch kernel-firmware-realtek-20230829-1.1.noarch kernel-firmware-mellanox-20230829-1.1.noarch libdrm_intel1-2.4.116-2.1.x86_64 kernel-firmware-network-20230829-1.1.noarch kernel-firmware-ath11k-20230829-1.1.noarch kernel-firmware-mediatek-20230829-1.1.noarch kernel-firmware-bluetooth-20230829-1.1.noarch kernel-firmware-prestera-20230829-1.1.noarch kernel-firmware-liquidio-20230829-1.1.noarch kernel-firmware-marvell-20230829-1.1.noarch kernel-default-6.5.2-1.1.x86_64 kernel-firmware-nfp-20230829-1.1.noarch kernel-default-devel-6.5.2-1.1.x86_64 kernel-devel-6.5.4-1.1.noarch kernel-firmware-qlogic-20230829-1.1.noarch kernel-default-devel-6.5.4-1.1.x86_64 kernel-default-6.5.4-1.1.x86_64 kernel-devel-6.5.2-1.1.noarch $ lsmod |grep -i -e i915 -e nvidia -e nouveau nvidia_drm 94208 0 nvidia_modeset 1794048 1 nvidia_drm nvidia_uvm 3608576 0 i915 4087808 5 drm_buddy 20480 1 i915 i2c_algo_bit 20480 1 i915 drm_display_helper 237568 1 i915 ttm 102400 1 i915 cec 90112 2 drm_display_helper,i915 nvidia 8843264 2 nvidia_uvm,nvidia_modeset video 77824 3 thinkpad_acpi,i915,nvidia_modeset $ modinfo nvidia |grep -i version version: 535.113.01 srcversion: 81566B70A70B0B19F40FD1A vermagic: 6.5.4-1-default SMP preempt mod_unload modversions $ cat /proc/cmdline # but I tested with others, see above BOOT_IMAGE=/boot/vmlinuz-6.5.4-1-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap mitigations=auto quiet security=apparmor modprobe.blacklist=i915 nosimplefb=1 I use these non-factory repos: https://download.opensuse.org/repositories/X11:/Drivers:/Video:/Redesign/op… https://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Tumbleweed/ https://download.nvidia.com/opensuse/tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 45

[Bug 1215987] New: Slowroll - XDM doesn't launch default Plasma X11 session
by bugzilla_noreply＠suse.com 31 Mar '24

31 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215987 Bug ID: 1215987 Summary: Slowroll - XDM doesn't launch default Plasma X11 session Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: bwiedemann(a)suse.com, msrb(a)suse.com, werner(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Initial Summary: Slowroll - XDM doesn't launch default Plasma X11 session To reproduce: 1-install minimal X role 2-install patterns-kde-kde_plasma constrained by solver.onlyRequires = true 3-ensure no DM is installed except XDM 4-ensure plasma5.desktop is the default xsession : # inxi -S System: Host: ara88 Kernel: 6.4.12-1-default arch: x86_64 bits: 64 Console: pty pts/0 Distro: openSUSE Tumbleweed-Slowroll 20231001 # update-alternatives --display default-displaymanager default-displaymanager - manual mode link best version is /usr/lib/X11/displaymanagers/xdm link currently points to /usr/lib/X11/displaymanagers/xdm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/xdm - priority 10 # update-alternatives --display default-xsession.desktop default-xsession.desktop - manual mode link best version is /usr/share/xsessions/plasma5.desktop link currently points to /usr/share/xsessions/plasma5.desktop link default-xsession.desktop is /usr/share/xsessions/default.desktop /usr/share/xsessions/icewm-session.desktop - priority 15 /usr/share/xsessions/plasma5.desktop - priority 25 # Actual behavior: 1-yellow-gray display screens with a decoration-free Xterm launch 2-WINDOWMANAGER=startplasma-x11 startx in the Xterm launches an apparently normal Plasma session Expected behavior: 1-Plasma session launches directly Additional information: 1-This is not unique to Slowroll, or this particular PC. I have it happening in Leap installations as well. This particular Slowroll was was born as a zypper dup from a cloned 15.5, which has the same problem. 2-This is not a recent development. ISTR 15.4 did it too, at least 6 months ago, but rather than reporting I installed KDM3 or TDM on them instead of keeping XDM only. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1213659] New: VUL-0: CVE-2023-38496: apptainer: Ineffective privileges drop when requesting container network
by bugzilla_noreply＠suse.com 28 Mar '24

28 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1213659 Bug ID: 1213659 Summary: VUL-0: CVE-2023-38496: apptainer: Ineffective privileges drop when requesting container network Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other URL: https://smash.suse.de/issue/373431/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: cgoll(a)suse.com Reporter: gianluca.gabrielli(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Apptainer is an open source container platform. Version 1.2.0-rc.2 introduced an ineffective privilege drop when requesting container network setup, therefore subsequent functions are called with root privileges, the attack surface is rather limited for users but an attacker could possibly craft a starter config to delete any directory on the host filesystems. A security fix has been included in Apptainer 1.2.1. There is no known workaround outside of upgrading to Apptainer 1.2.1. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-38496 https://bugzilla.redhat.com/show_bug.cgi?id=2226582 https://www.cve.org/CVERecord?id=CVE-2023-38496 http://www.cvedetails.com/cve/CVE-2023-38496/ https://github.com/apptainer/apptainer/pull/1523 https://github.com/apptainer/apptainer/pull/1578 https://github.com/apptainer/apptainer/security/advisories/GHSA-mmx5-32m4-w… -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214850] New: open-vm-tools 12.3.0 has been released - please rebase
by bugzilla_noreply＠suse.com 27 Mar '24

27 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214850 Bug ID: 1214850 Summary: open-vm-tools 12.3.0 has been released - please rebase Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jwolfe(a)vmware.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- open-vm-tools 12.3.0 was released on Aug. 31, 2023. Also affects project (?) Also affects distribution/package Edit Bug Description There are no new features in the open-vm-tools 12.3.0 release. This is primarily a maintenance release that addresses a few critical problems, including: This release resolves CVE-2023-20900. For more information on this vulnerability and its impact on VMware products, see https://www.vmware.com/security/advisories/VMSA-2023-0019.html. A tools.conf configuration setting is available to temporaily direct Linux quiesced snaphots to restore pre open-vm-tools 12.2.0 behavior of ignoring file systems already frozen. Building of the VMware Guest Authentication Service (VGAuth) using "xml-security-c" and "xerces-c" is being deprecated. A number of Coverity reported issues have been addressed. A number of GitHub issues and pull requests have been handled. Please see the Resolves Issues section of the Release Notes. For issues resolved in this release, see the Resolved Issues section of the Release Notes. For complete details, see: https://github.com/vmware/open-vm-tools/releases/tag/stable-12.3.0 Release Notes are available at https://github.com/vmware/open-vm-tools/blob/stable-12.3.0/ReleaseNotes.md The granular changes that have gone into the 12.3.0 release are in the ChangeLog at https://github.com/vmware/open-vm-tools/blob/stable-12.3.0/open-vm-tools/Ch… Note: With the changes upstreamed and the fix for CVE-2023-20867 in the source, you may not need the following patches in your open-vm-toold pacjage build: 0001-build-put-l-specifiers-into-LIBADD-not-LDFLAGS.patch 0002-build-use-grpc-pkgconfig-to-retrieve-flags-libraries.patch 2023-20867-Remove-some-dead-code.patch detect-suse-location.patch Please rebase open-vm-tools version 12.3.0 in supported releases of SLES 12 and SLES 15 for x86_64/amd64 and aarch64/ARM64 architectures as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1215962] New: sddm fails when starting as a wayland client
by bugzilla_noreply＠suse.com 17 Mar '24

17 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1215962 Bug ID: 1215962 Summary: sddm fails when starting as a wayland client Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: sfalken(a)cloverleaf-linux.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 869927 --> https://bugzilla.suse.com/attachment.cgi?id=869927&action=edit Output of Journal, for failure condition Setting an override in /etc/sddm.conf.d/10-wayland.conf for: [General] DisplayManager=wayland I would expect to get sddm running as a wayland client, but it crashes with an SDDM::Auth::Helper_AUTH_ERROR Please see attached log from the journal. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1214274] New: Google Chrome and Chromium: Skia shader compilation error
by bugzilla_noreply＠suse.com 17 Mar '24

17 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214274 Bug ID: 1214274 Summary: Google Chrome and Chromium: Skia shader compilation error 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: miso(a)hlavki.eu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868797 --> https://bugzilla.suse.com/attachment.cgi?id=868797&action=edit error log After upgrade to snapshots 20230812, 20230813 Google Chrome and Chromium stops render properly web pages. Started to blink and console log shows errors. Attachned error.txt It looks similar to: https://bugs.chromium.org/p/chromium/issues/detail?id=1442633 Can confirm that workaround is: google-chrome --disable-gpu-driver-bug-workarounds -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1216681] New: AltGr key gets stuck in virtual console after switching to Swedish keyboard layout's "mac" variant using `localectl`
by bugzilla_noreply＠suse.com 15 Mar '24

15 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1216681 Bug ID: 1216681 Summary: AltGr key gets stuck in virtual console after switching to Swedish keyboard layout's "mac" variant using `localectl` Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: no(a)no.noooo.ooo QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 Build Identifier: Using a standard European keyboard (I use Swedish) with an AltGr key, after using `localectl` to switch to Swedish keyboard's MAC variant, virtual console would make AltGr stuck after typing `AltGr+Shift+<anything>`. Reproducible: Always Steps to Reproduce: 0. Get a European keyboard (I use Swedish) with an 'AltGr' key. 1. Log into any X11 GUI terminals and do sudo localectl set-x11-keymap se pc104 mac ctrl:nocaps In fact any keyboard models (pc104 etc.) I've tried will reproduce the bug. 2. Press Ctrl+Alt+F1 to go from X11 to virtual console. 3. Try typing the '{' character by pressing AltGr+Right_Shift+8. Actual Results: Now just press the '2' on your keyboard; but instead of '2', the character '@' is inserted because it seems to think that AltGr is still active, and in this Swedish layout '@' is AltGr+2. Similarly typing 'hckiang' produces 'ħ¢ĸ→æ”ŋ' as if the AltGr key is down. Now there're no easy ways to even shutdown the computer because you can't type any normal command/shortcuts any more. Not even Ctrl+Alt+F2 to switch back to X11. The only choice is to hit my laptop's power button to restart. Expected Results: After pressing AltGr+Right_Shift+8 to input a '{', you can still type normally, such that keyboard sequence 'hckiang' should input 'hckiang' rather than 'ħ¢ĸ→æ”ŋ'. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1214800] New: KDE Wayland Screen Energy Saving Problem
by bugzilla_noreply＠suse.com 14 Mar '24

14 Mar '24

https://bugzilla.suse.com/show_bug.cgi?id=1214800 Bug ID: 1214800 Summary: KDE Wayland Screen Energy Saving Problem Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pfaca(a)tutamail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- When using Wayland, Screen Energy Saving doesn't work. Either waiting for the switch off timer, or using Ctrl + Alt + D the outcome is the same: 1. display turns off 2. display says that there is no signal/input 3. display turns off again 4. display wakes up immediately Journal gives the following: plasmashell[2276] qt.qpa.wayland: Wayland does not support QWindow::requestActivate() At bugs.kde.org there is the bug number 462695 (https://bugs.kde.org/show_bug.cgi?id=462695) where it claims the bug was resolved at KDE side and the fix has to be provided by openSUSE. My specs: openSUSE Tumbleweed Kernel 6.4.11-1-default DE Plasma 5.27.7 CPU Intel i5-4670K GPU AMD ATI Radeon RX 6750 XT Note: Everything works has expected using X11. -- You are receiving this mail because: You are on the CC list for the bug.

1 5