December 2023 - openSUSE Bugs - openSUSE Mailing Lists

[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 1215349] New: VUL-0: CVE-2023-4863: dssim: Heap buffer overflow in WebP
by bugzilla_noreply＠suse.com 27 Nov '24

27 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215349 Bug ID: 1215349 Summary: VUL-0: CVE-2023-4863: dssim: Heap buffer overflow in WebP Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/377966/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: Andreas.Stieger(a)gmx.de, gianluca.gabrielli(a)suse.com, gmbr3(a)opensuse.org, gnome-bugs(a)suse.de, jengelh(a)inai.de, m.szczepaniak.000(a)gmail.com, martin.sirringhaus(a)suse.com, meissner(a)suse.com, security-team(a)suse.de, wolfgang(a)rosenauer.org, xiaoguang.wang(a)suse.com Depends on: 1215231 Blocks: 1215347 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1215231 +++ CVE-2023-4863 The Stable and Extended stable channels has been updated to 116.0.5845.187 for Mac and Linux and 116.0.5845.187/.188 for Windows, which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. CVE-2023-4863: Heap buffer overflow in WebP. Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at The University of Torontoʼs Munk School on 2023-09-06 Google is aware that an exploit for CVE-2023-4863 exists in the wild. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=1479274 References: https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-des… http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 https://bugzilla.redhat.com/show_bug.cgi?id=2238431 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1215347] New: VUL-0: CVE-2023-4863: zola: Heap buffer overflow in WebP
by bugzilla_noreply＠suse.com 27 Nov '24

27 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215347 Bug ID: 1215347 Summary: VUL-0: CVE-2023-4863: zola: Heap buffer overflow in WebP Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://smash.suse.de/issue/377966/ OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Security Assignee: socvirnyl.estela(a)gmail.com Reporter: carlos.lopez(a)suse.com QA Contact: security-team(a)suse.de CC: Andreas.Stieger(a)gmx.de, gianluca.gabrielli(a)suse.com, gmbr3(a)opensuse.org, gnome-bugs(a)suse.de, jengelh(a)inai.de, m.szczepaniak.000(a)gmail.com, martin.sirringhaus(a)suse.com, meissner(a)suse.com, security-team(a)suse.de, wolfgang(a)rosenauer.org, xiaoguang.wang(a)suse.com Depends on: 1215231 Target Milestone: --- Found By: Security Response Team Blocker: --- +++ This bug was initially created as a clone of Bug #1215231 +++ CVE-2023-4863 The Stable and Extended stable channels has been updated to 116.0.5845.187 for Mac and Linux and 116.0.5845.187/.188 for Windows, which will roll out over the coming days/weeks. A full list of changes in this build is available in the log. This update includes 1 security fix. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information. CVE-2023-4863: Heap buffer overflow in WebP. Reported by Apple Security Engineering and Architecture (SEAR) and The Citizen Lab at The University of Torontoʼs Munk School on 2023-09-06 Google is aware that an exploit for CVE-2023-4863 exists in the wild. Upstream bug(s): https://code.google.com/p/chromium/issues/detail?id=1479274 References: https://chromereleases.googleblog.com/2023/09/stable-channel-update-for-des… http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-4863 https://bugzilla.redhat.com/show_bug.cgi?id=2238431 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213370] New: tesseract-ocr should not be built with experimantal opencl support
by bugzilla_noreply＠suse.com 25 Nov '24

25 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213370 Bug ID: 1213370 Summary: tesseract-ocr should not be built with experimantal opencl support Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- opencl in tesseract-ocr is considered experimental, according to this thread (https://groups.google.com/g/tesseract-ocr/c/eIQbsurfSEM/m/mVb_4GF1BgAJ) it is considered just an entry point for possible developers. Their own doucmentantion (https://tesseract-ocr.github.io/tessdoc/TesseractOpenCL.html) states: "Important note: OpenCL support in Tesseract is still considered experimental. There are some major bugs associated with it (see issue 837). Building Tesseract with OpenCL support is not recommended (for any version of Tesseract), unless you are a developer and want to improve the OpenCL code" Please remove the flag "--enable-opencl" from https://build.opensuse.org/package/view_file/openSUSE:Factory/tesseract-ocr… This would also resolve https://bugzilla.opensuse.org/show_bug.cgi?id=1207570 PS: I indeed encounter problems with the opencl code path -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215403] New: SDDM default display-manager cannot login to X11 desktop
by bugzilla_noreply＠suse.com 16 Nov '24

16 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215403 Bug ID: 1215403 Summary: SDDM default display-manager cannot login to X11 desktop 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: ajbudge(a)errichel.co.uk QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With TW as OS and KDE desktop, when running SDDM as default-displaymanager after boot login will only work with Plasma (Wayland) desktop. Selecting X11 and logging in goes dark and then after a few seconds returns to login screen. journal gives me:- Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: Starting X11 session: "" "/usr/etc/X11/xdm/Xsession \"/usr/bin/startplasma-x11\"" Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Session started false Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Closing session Sep 16 09:22:04 HP-Z640-1 sddm-helper[2134]: [PAM] Ended. Sep 16 09:22:04 HP-Z640-1 sddm[1851]: Auth: sddm-helper exited with 2 and there is nothing in /etc/sddm.conf.d> or /.local/share/sddm> cat xorg-session.log (nothing here) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1213139] New: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1213139 Bug ID: 1213139 Summary: [Build 20230706] openQA test fails in consoletest_setup: vmalloc error in kernel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3412937/modules/cons oletest_setup/steps/52 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Randomly (currently every ~4th run), the test fails because systemd-vconsole-setup fails to complete. The kernel spits out an allocation failure: [ 519.853569] systemd-vconsol: vmalloc error: size 0, page order 9, failed to allocate pages, mode:0xcc2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null),cpuset=/,mems_allowed=0 [ 519.854619] CPU: 0 PID: 11361 Comm: systemd-vconsol Not tainted 6.3.9-1-default #1 openSUSE Tumbleweed 4b767630dbc263131e96e89ef291fd4fd2951892 [ 519.855385] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 [ 519.855860] Call Trace: [ 519.856047] <TASK> [ 519.856208] dump_stack_lvl+0x47/0x60 [ 519.856455] warn_alloc+0x13a/0x1b0 [ 519.856693] ? __alloc_pages+0x32d/0x350 [ 519.857009] __vmalloc_node_range+0x631/0x8b0 [ 519.857343] ? con_font_op+0x193/0x430 [ 519.857593] kvmalloc_node+0xa6/0xd0 [ 519.857857] ? con_font_op+0x193/0x430 [ 519.858105] con_font_op+0x193/0x430 [ 519.858346] ? __pfx_bpf_lsm_capable+0x10/0x10 [ 519.858631] ? security_capable+0x44/0x70 [ 519.858891] vt_ioctl+0x834/0x1380 [ 519.859126] tty_ioctl+0x4b1/0x870 [ 519.859355] __x64_sys_ioctl+0x94/0xd0 [ 519.859601] do_syscall_64+0x60/0x90 [ 519.859871] ? exc_page_fault+0x6e/0x150 [ 519.860129] entry_SYSCALL_64_after_hwframe+0x72/0xdc [ 519.860447] RIP: 0033:0x7f1144d0c2cf [ 519.860710] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 [ 519.861757] RSP: 002b:00007ffe520b5af0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 519.862201] RAX: ffffffffffffffda RBX: 00007ffe520b5c10 RCX: 00007f1144d0c2cf [ 519.862843] RDX: 00007ffe520b5bf0 RSI: 0000000000004b72 RDI: 0000000000000003 [ 519.863463] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001 [ 519.864093] R10: 0000000000000004 R11: 0000000000000246 R12: 0000000000000008 [ 519.864705] R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000 [ 519.865317] </TASK> [ 519.865681] Mem-Info: [ 519.866038] active_anon:34752 inactive_anon:94983 isolated_anon:0 active_file:120769 inactive_file:114642 isolated_file:0 unevictable:3088 dirty:1160 writeback:0 slab_reclaimable:23978 slab_unreclaimable:21653 mapped:30383 shmem:4200 pagetables:3497 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:66953 free_pcp:198 free_cma:0 [ 519.881932] Node 0 active_anon:139008kB inactive_anon:379932kB active_file:483076kB inactive_file:458568kB unevictable:12352kB isolated(anon):0kB isolated(file):0kB mapped:121532kB dirty:4640kB writeback:0kB shmem:16800kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 61440kB writeback_tmp:0kB kernel_stack:8040kB pagetables:13988kB sec_pagetables:0kB all_unreclaimable? no [ 519.893364] Node 0 DMA free:8220kB boost:0kB min:328kB low:408kB high:488kB reserved_highatomic:0KB active_anon:32kB inactive_anon:1908kB active_file:1564kB inactive_file:2136kB unevictable:0kB writepending:0kB present:15000kB managed:14364kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB [ 519.903019] lowmem_reserve[]: 0 1889 1889 1889 1889 [ 519.905153] Node 0 DMA32 free:259592kB boost:0kB min:44724kB low:55904kB high:67084kB reserved_highatomic:16384KB active_anon:138976kB inactive_anon:378024kB active_file:481512kB inactive_file:456432kB unevictable:12352kB writepending:4640kB present:2076960kB managed:1966804kB mlocked:16kB bounce:0kB free_pcp:792kB local_pcp:792kB free_cma:0kB [ 519.915738] lowmem_reserve[]: 0 0 0 0 0 [ 519.917815] Node 0 DMA: 31*4kB (UME) 13*8kB (UME) 10*16kB (UM) 21*32kB (UME) 20*64kB (UM) 10*128kB (UME) 2*256kB (UE) 2*512kB (UE) 1*1024kB (E) 1*2048kB (E) 0*4096kB = 8228kB [ 519.920264] Node 0 DMA32: 20402*4kB (UMEH) 7366*8kB (UMEH) 2957*16kB (UMEH) 1109*32kB (UMEH) 359*64kB (UMEH) 66*128kB (UMEH) 11*256kB (MH) 4*512kB (MH) 0*1024kB 0*2048kB 0*4096kB = 259624kB [ 519.922145] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB [ 519.923229] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [ 519.924415] 262294 total pagecache pages [ 519.925139] 22685 pages in swap cache [ 519.925777] Free swap = 1663652kB [ 519.926439] Total swap = 2097148kB [ 519.927082] 522990 pages RAM [ 519.927676] 0 pages HighMem/MovableOnly [ 519.928332] 27698 pages reserved [ 519.929181] 0 pages cma reserved [ 519.929828] 0 pages hwpoisoned If the system was actually out of RAM, I'd expect it to fail earlier in random places already. ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-upgrade_Leap_15.2_cryptlvm@uefi fails in [consoletest_setup](https://openqa.opensuse.org/tests/3412937/modules/consol… ## Test suite description Upgrade scenario with cryptlvm for Leap 15.2 Set QEMUVGA=virtio due to bsc#1210555 ## Reproducible Fails since (at least) Build [20230401](https://openqa.opensuse.org/tests/3205451) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1212937] New: Kernel panic when booting up tumbleweed 20230629
by bugzilla_noreply＠suse.com 15 Nov '24

15 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1212937 Bug ID: 1212937 Summary: Kernel panic when booting up tumbleweed 20230629 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other 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 867932 --> https://bugzilla.suse.com/attachment.cgi?id=867932&action=edit screenshot When I booted my tw system today, I ran into a kernel panic. Kernel: Linux 6.3.9-1-default Architecture: x86-64 Hardware Vendor: Lenovo Hardware Model: ThinkPad T14s Gen 2a The issue happened once and after a reboot I was able to boot up fine. The standby issue with the laptop hanging up on resume and eventually rebooting automatically is back again and sadly reproducible always. Not sure if that could be related. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1214060] New: html2ps conversion fails with perl >= 5.26
by bugzilla_noreply＠suse.com 14 Nov '24

14 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1214060 Bug ID: 1214060 Summary: html2ps conversion fails with perl >= 5.26 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Affected: Tumbleweed, Leap, SLE 15 html2ps -f <file> fails with this error: Unimplemented: POSIX::tmpnam(): use File::Temp instead at /usr/bin/html2ps line 498. We're apparently having an old version in openSUSE (some distro have 1.0b7) and it needs patching. Debian has a collection of improvements and fixes: https://salsa.debian.org/debian/html2ps/-/tree/master/debian/patches The important one for this report is perl-deprecation.patch -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1218342] New: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed
by bugzilla_noreply＠suse.com 11 Nov '24

11 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218342 Bug ID: 1218342 Summary: [TRACKERBUG] OpenSSL 3.2.0 upgrade tracker bug for Tumbleweed 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: otto.hollmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This bug collects the challenges and packages that need to be adapted for OpenSSL 3.2.0 upgrade in Tumbleweed. OpenSSL 3.2 migration guide: https://www.openssl.org/docs/man3.2/man7/migration_guide.html -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1215090] New: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver/html/
by bugzilla_noreply＠suse.com 07 Nov '24

07 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215090 Bug ID: 1215090 Summary: go1.20,go1.21: Go toolchain packages missing src/cmd/vendor/github.com/google/pprof/internal/driver /html/ 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: --- Include the missing directory src/cmd/vendor/github.com/google/pprof/internal/driver/html/ in our go1.1x toolchain packages. This will fix failing builds with applications that directly import runtime/pprof e.g. kubeconform which failed to build with the following error: /usr/lib64/go/1.21/src/cmd/vendor/github.com/google/pprof/internal/driv er/webhtml.go:26:12: pattern html: no matching files found Upstream Go sources vendor certain tools including the pprof profiler [1]. pprof has an asset directory pprof/internal/driver/html containing only html templates used by the pprof viewer and no Go source code. Our go packaging tries to be conservative in what we include in the RPM, and with our find/glob patterns this directory has never been included in the packaging. The issue was first reported with go1.21. However, the last vendoring update was for go1.20, so we will include the fix in go1.20 packaging as well: bb917bd 2022-11-22 09:39 cmd/vendor: update vendored github.com/google/pprof for Go 1.20 release [1] https://github.com/google/pprof -- You are receiving this mail because: You are on the CC list for the bug.

1 6