June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 899104] New: KDE complains about X-KDE-Library from yast desktop files
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.suse.com/show_bug.cgi?id=899104 Bug ID: 899104 Summary: KDE complains about X-KDE-Library from yast desktop files Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- See https://openqa.opensuse.org/tests/25123/file/XSE KDE complains about the X-KDE-Library entries in yast's desktop files. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1082027] New: gcc7 can not build clisp even with --enable-portability (no memory/stack changes)
by bugzilla_noreply＠novell.com 07 Jan '21

07 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1082027 Bug ID: 1082027 Summary: gcc7 can not build clisp even with --enable-portability (no memory/stack changes) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since gcc7 it is not possible anymore to build clisp even with disabling assembler as well stack and memory layout with the configure option --enable-portability ... note that this is the only architecture which does not build. Hence upstream has the opinion that our gcc7 is somehow broken as on Debian s390x with an older gcc the clisp-2.49.92 does build. Is there any older gcc available for Factory/Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1034350] New: wxWidgets-3_0: spurious assert in wxGTK wxDataViewCtrl::EditItem()
by bugzilla_noreply＠novell.com 03 Jan '21

03 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1034350 Bug ID: 1034350 Summary: wxWidgets-3_0: spurious assert in wxGTK wxDataViewCtrl::EditItem() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: jengelh(a)inai.de Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From PoEdit news https://github.com/vslavik/poedit/blob/master/NEWS#L14-L17 > IMPORTANT NOTE TO DISTRIBUTION MAINTAINERS: > Poedit is affected by a bug in wxGTK 3.0.2 that cannot be worked around in user > code, requiring this patch to wxGTK to be applied: > https://github.com/wxWidgets/wxWidgets/commit > /ed88188be7e97a0503f3471f7b0452740b732902 Could the diff below please be applied at the next convenience? https://github.com/wxWidgets/wxWidgets/commit/ed88188be7e97a0503f3471f7b045… -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1098587] New: electronics/kicad-unstable: Bug
by bugzilla_noreply＠novell.com 30 Dec '20

30 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1098587 Bug ID: 1098587 Summary: electronics/kicad-unstable: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dmitry(a)roshchin.org Reporter: suse(a)tejaphilipp.de QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- Current kicad-unstable failing to start after recent tumbleweed update: t@buhu:~/> kicad Fatal Error: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1012,STL containers,compatible with 2.8), and your program used 3.0 (wchar_t,compiler with C++ ABI 1002,STL containers,compatible with 2.8). Aborted (core dumped) t@buhu:~/> Thanks for your efforts in advance!! -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1091353] New: [Build 20180417] openQA test fails to install inkscape over pkcon sporadically
by bugzilla_noreply＠novell.com 29 Dec '20

29 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1091353 Bug ID: 1091353 Summary: [Build 20180417] openQA test fails to install inkscape over pkcon sporadically Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/658802/modules/inksc ape/steps/12 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org Found By: --- Blocker: --- Created attachment 768621 --> http://bugzilla.opensuse.org/attachment.cgi?id=768621&action=edit pk_backend_zypp files from both the "failed" as well as "good" case for comparison. ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-zdup-Leap-42.2-gnome@64bit fails in [inkscape](https://openqa.opensuse.org/tests/658802/modules/inkscape/steps/1… ## Reproducible Sporadically reproduced, see openQA test scenario, especially in upgrade cases. ## Expected result See [20180416](https://openqa.opensuse.org/tests/657426) how it should look like. https://openqa.opensuse.org/tests/660733#step/inkscape/13 shows the expected screen ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?test=zdup-Leap-42.2-gnome&… I looked up the corresponding pk_backend_zypp logfiles for the "failed" and "good" case, see pk_backend_zypp_failed_good.tar.xz for that. Complete logfiles for "failed" are available in https://openqa.opensuse.org/tests/658802#downloads and correspondingly in https://openqa.opensuse.org/tests/660733#downloads for "good". -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1027702] New: Feature Requested - Make smoother transition from startup screen to X and back.
by bugzilla_noreply＠novell.com 29 Dec '20

29 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1027702 Bug ID: 1027702 Summary: Feature Requested - Make smoother transition from startup screen to X and back. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Usability Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jzimm0007(a)aol.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have an MSI MS-7640 with An AMD FX Processor If you could make Suse's bootup smoother in such a way that it doesn't go to black screens and stuff between starting x and going back to the login screen and the like; that would be cool (Feature). I think X gave a black screen at one point if I recall right. That was apparently due to the type of processor in the machine. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1012628] New: Continuous stable update tracker for Tumbleweed
by bugzilla_noreply＠novell.com 18 Dec '20

18 Dec '20

http://bugzilla.suse.com/show_bug.cgi?id=1012628 Bug ID: 1012628 Summary: Continuous stable update tracker for Tumbleweed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Here we can track regressions and bugs against stable kernel 4.4 which is merged into our branches. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 911623] New: Bluetooth will not pair a headset
by bugzilla_noreply＠novell.com 17 Dec '20

17 Dec '20

http://bugzilla.opensuse.org/show_bug.cgi?id=911623 Bug ID: 911623 Summary: Bluetooth will not pair a headset Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: bbagger(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to pair a Bluetooh headset (BPM X1 Headphones) the operations times out, and the following appears in /var/log/messages: ==== 112416+01:00 yosie kernel: [ 4397.298229] ------------[ cut here ]------------ 2015-01-04T19:25:28.112450+01:00 yosie kernel: [ 4397.298288] WARNING: CPU: 1 PID: 28817 at ../net/bluetooth/hci_conn.c:296 hci_conn_timeout+0x4a/0x280 [bluetooth]() 2015-01-04T19:25:28.112454+01:00 yosie kernel: [ 4397.298293] Modules linked in: fuse nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache rfcomm iscsi_ibft iscsi_boot_sysfs af_packet bnep ecb btusb bluetooth 6lowpan_iphc raid1 uvcvideo md_mod videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_core snd_usbmidi_lib v4l2_common videodev eeepc_wmi asus_wmi sparse_keymap rfkill video kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_codec_hdmi pcspkr k10temp snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep r8169 mii snd_ens1371 snd_rawmidi snd_ac97_codec snd_pcm shpchp ac97_bus gameport i2c_piix4 wmi tpm_infineon tpm_tis tpm acpi_cpufreq button processor snd_seq snd_seq_device snd_timer snd soundcore ata_generic pata_atiixp ohci_pci radeon sr_mod cdrom i2c_algo_bit drm_kms_helper ttm drm xhci_hcd dm_mirror dm_region_hash dm_log dm_mod sg 2015-01-04T19:25:28.112458+01:00 yosie kernel: [ 4397.298411] CPU: 1 PID: 28817 Comm: kworker/u9:0 Tainted: G W 3.16.7-7-desktop #1 2015-01-04T19:25:28.112461+01:00 yosie kernel: [ 4397.298416] Hardware name: System manufacturer System Product Name/F1A75-M-PRO R2.0, BIOS 5010 08/09/2012 2015-01-04T19:25:28.112464+01:00 yosie kernel: [ 4397.298446] Workqueue: hci0 hci_conn_timeout [bluetooth] 2015-01-04T19:25:28.112467+01:00 yosie kernel: [ 4397.298451] 0000000000000009 ffffffff8161bd03 0000000000000000 ffffffff8105cad7 2015-01-04T19:25:28.112469+01:00 yosie kernel: [ 4397.298458] ffff8800b8cfa8b8 00000000ffffffff ffff8800b8cfa800 ffff88021158a900 2015-01-04T19:25:28.112472+01:00 yosie kernel: [ 4397.298465] 0000000000000000 ffffffffa05c3d3a ffffffff8161e59d ffff8800b8cfa8b8 2015-01-04T19:25:28.112474+01:00 yosie kernel: [ 4397.298471] Call Trace: 2015-01-04T19:25:28.112477+01:00 yosie kernel: [ 4397.298499] [<ffffffff810051ee>] dump_trace+0x8e/0x350 2015-01-04T19:25:28.112479+01:00 yosie kernel: [ 4397.298511] [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 2015-01-04T19:25:28.112482+01:00 yosie kernel: [ 4397.298521] [<ffffffff81006c51>] show_stack+0x21/0x50 2015-01-04T19:25:28.112484+01:00 yosie kernel: [ 4397.298532] [<ffffffff8161bd03>] dump_stack+0x49/0x6a 2015-01-04T19:25:28.112487+01:00 yosie kernel: [ 4397.298543] [<ffffffff8105cad7>] warn_slowpath_common+0x77/0x90 2015-01-04T19:25:28.112489+01:00 yosie kernel: [ 4397.298576] [<ffffffffa05c3d3a>] hci_conn_timeout+0x4a/0x280 [bluetooth] 2015-01-04T19:25:28.112584+01:00 yosie kernel: [ 4397.298640] [<ffffffff810770fd>] process_one_work+0x16d/0x460 2015-01-04T19:25:28.112596+01:00 yosie kernel: [ 4397.298651] [<ffffffff810779e5>] worker_thread+0x115/0x5102015-01-04T19:25:28.112416+01:00 yosie kernel: [ 4397.298229] ------------[ cut here ]------------ 2015-01-04T19:25:28.112450+01:00 yosie kernel: [ 4397.298288] WARNING: CPU: 1 PID: 28817 at ../net/bluetooth/hci_conn.c:296 hci_conn_timeout+0x4a/0x280 [bluetooth]() 2015-01-04T19:25:28.112454+01:00 yosie kernel: [ 4397.298293] Modules linked in: fuse nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss oid_registry nfsv4 dns_resolver nfs lockd sunrpc fscache rfcomm iscsi_ibft iscsi_boot_sysfs af_packet bnep ecb btusb bluetooth 6lowpan_iphc raid1 uvcvideo md_mod videobuf2_vmalloc snd_usb_audio videobuf2_memops videobuf2_core snd_usbmidi_lib v4l2_common videodev eeepc_wmi asus_wmi sparse_keymap rfkill video kvm_amd kvm snd_hda_codec_realtek snd_hda_codec_generic serio_raw snd_hda_codec_hdmi pcspkr k10temp snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep r8169 mii snd_ens1371 snd_rawmidi snd_ac97_codec snd_pcm shpchp ac97_bus gameport i2c_piix4 wmi tpm_infineon tpm_tis tpm acpi_cpufreq button processor snd_seq snd_seq_device snd_timer snd soundcore ata_generic pata_atiixp ohci_pci radeon sr_mod cdrom i2c_algo_bit drm_kms_helper ttm drm xhci_hcd dm_mirror dm_region_hash dm_log dm_mod sg 2015-01-04T19:25:28.112458+01:00 yosie kernel: [ 4397.298411] CPU: 1 PID: 28817 Comm: kworker/u9:0 Tainted: G W 3.16.7-7-desktop #1 2015-01-04T19:25:28.112461+01:00 yosie kernel: [ 4397.298416] Hardware name: System manufacturer System Product Name/F1A75-M-PRO R2.0, BIOS 5010 08/09/2012 2015-01-04T19:25:28.112464+01:00 yosie kernel: [ 4397.298446] Workqueue: hci0 hci_conn_timeout [bluetooth] 2015-01-04T19:25:28.112467+01:00 yosie kernel: [ 4397.298451] 0000000000000009 ffffffff8161bd03 0000000000000000 ffffffff8105cad7 2015-01-04T19:25:28.112469+01:00 yosie kernel: [ 4397.298458] ffff8800b8cfa8b8 00000000ffffffff ffff8800b8cfa800 ffff88021158a900 2015-01-04T19:25:28.112472+01:00 yosie kernel: [ 4397.298465] 0000000000000000 ffffffffa05c3d3a ffffffff8161e59d ffff8800b8cfa8b8 2015-01-04T19:25:28.112474+01:00 yosie kernel: [ 4397.298471] Call Trace: 2015-01-04T19:25:28.112477+01:00 yosie kernel: [ 4397.298499] [<ffffffff810051ee>] dump_trace+0x8e/0x350 2015-01-04T19:25:28.112479+01:00 yosie kernel: [ 4397.298511] [<ffffffff81005556>] show_stack_log_lvl+0xa6/0x190 2015-01-04T19:25:28.112482+01:00 yosie kernel: [ 4397.298521] [<ffffffff81006c51>] show_stack+0x21/0x50 2015-01-04T19:25:28.112484+01:00 yosie kernel: [ 4397.298532] [<ffffffff8161bd03>] dump_stack+0x49/0x6a 2015-01-04T19:25:28.112487+01:00 yosie kernel: [ 4397.298543] [<ffffffff8105cad7>] warn_slowpath_common+0x77/0x90 2015-01-04T19:25:28.112489+01:00 yosie kernel: [ 4397.298576] [<ffffffffa05c3d3a>] hci_conn_timeout+0x4a/0x280 [bluetooth] 2015-01-04T19:25:28.112584+01:00 yosie kernel: [ 4397.298640] [<ffffffff810770fd>] process_one_work+0x16d/0x460 2015-01-04T19:25:28.112596+01:00 yosie kernel: [ 4397.298651] [<ffffffff810779e5>] worker_thread+0x115/0x510 2015-01-04T19:25:28.112598+01:00 yosie kernel: [ 4397.298662] [<ffffffff8107dd5d>] kthread+0xbd/0xe0 2015-01-04T19:25:28.112601+01:00 yosie kernel: [ 4397.298672] [<ffffffff8162297c>] ret_from_fork+0x7c/0xb0 2015-01-04T19:25:28.112604+01:00 yosie kernel: [ 4397.298681] ---[ end trace 4772ff5681be4670 ]--- 2015-01-04T19:25:28.194795+01:00 yosie bluetoothd[1061]: connect error: Software caused connection abort (103) 2015-01-04T19:25:28.112598+01:00 yosie kernel: [ 4397.298662] [<ffffffff8107dd5d>] kthread+0xbd/0xe0 2015-01-04T19:25:28.112601+01:00 yosie kernel: [ 4397.298672] [<ffffffff8162297c>] ret_from_fork+0x7c/0xb0 2015-01-04T19:25:28.112604+01:00 yosie kernel: [ 4397.298681] ---[ end trace 4772ff5681be4670 ]--- 2015-01-04T19:25:28.194795+01:00 yosie bluetoothd[1061]: connect error: Software caused connection abort (103) ===== I have tried to pair the same headset on a live Rosa setup, and there it works as expected. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1052770] New: Failed to save IO scheduler settings
by bugzilla_noreply＠novell.com 11 Dec '20

11 Dec '20

http://bugzilla.suse.com/show_bug.cgi?id=1052770 Bug ID: 1052770 Summary: Failed to save IO scheduler settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 735702 --> http://bugzilla.suse.com/attachment.cgi?id=735702&action=edit y2log The system is a freshly installed KVM running the latest snapshot of tumbleweed. When attempting to change system-wide IO scheduler to noop, this error occurs: Details: Invalid argument @ fptr_finalize_flush - /sys/block/vda/queue/scheduler Caller: /usr/share/YaST2/modules/SystemSettings.rb:252:in `write' lsblk -O output is the following: NAME KNAME MAJ:MIN FSTYPE MOUNTPOINT LABEL UUID PARTTYPE PARTLABEL PARTUUID PARTFLAGS RA RO RM HOTPLUG MODEL SERIAL SIZE STATE OWNER GROUP MODE ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE TYPE DISC-ALN DISC-GRAN DISC-MAX DISC-ZERO WSAME WWN RAND PKNAME HCTL TRAN SUBSYSTEMS REV VENDOR ZONED sr0 sr0 11:0 512 0 1 1 QEMU 1024M runni root cdrom brw-rw---- 0 512 0 512 512 1 noop 128 rom 0 0B 0B 0 0B 1 0:0:0:0 sata block:scsi:pci 2.5+ QEMU none vda vda 254:0 512 0 0 0 64G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 disk 0 0B 0B 0 0B 0 block:virtio:pci │ 0x1af4 none ├─vda1 │ vda1 254:1 swap [SWAP] aeec6ca8-628d-49e3-ae58-1daf1c3accc2 0x82 328c4097-01 512 0 0 0 2G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline │ 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci │ none └─vda2 vda2 254:2 ext4 / f871d33d-0b38-4b2d-b9e0-ba204b2bb05e 0x83 328c4097-02 0x80 512 0 0 0 62G root disk brw-rw---- 0 512 0 512 512 1 mq-deadline 256 part 0 0B 0B 0 0B 0 vda block:virtio:pci none -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1094222] New: gcc-8 on opensuse tumbleweed points to wrong location when displaying error
by bugzilla_noreply＠novell.com 09 Dec '20

09 Dec '20

http://bugzilla.suse.com/show_bug.cgi?id=1094222 Bug ID: 1094222 Summary: gcc-8 on opensuse tumbleweed points to wrong location when displaying error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jmcdonough(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 770999 --> http://bugzilla.suse.com/attachment.cgi?id=770999&action=edit .i file from building lib/util/debug.c Compiling the latest upstream samba with -O3, -Werror, among other flags, fails but doesn't point to the correct error location. The line it's giving us doesn't make any sense for the error printed. Below is the failing command and error messages. I'll attach the .i as well. gcc-8 -O3 -DDEVELOPER -DDEBUG_PASSWORD -fPIC -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -fstack-protector -g -Wall -Wshadow -Wmissing-prototypes -Wcast-align -Wcast-qual -fno-common -Werror=address -Werror=strict-prototypes -Wstrict-prototypes -Werror=write-strings -Wwrite-strings -Werror-implicit-function-declaration -Werror=pointer-arith -Wpointer-arith -Werror=declaration-after-statement -Wdeclaration-after-statement -Werror=return-type -Wreturn-type -Werror=uninitialized -Wuninitialized -Wimplicit-fallthrough -Werror=strict-overflow -Wstrict-overflow=2 -Wformat=2 -Wno-format-y2k -Wno-format-zero-length -Werror=format-security -Wformat-security -Werror=format -Werror -Wno-error=deprecated-declarations -Wno-error=tautological-compare -DSTATIC_samba_debug_MODULES=NULL -DSTATIC_samba_debug_MODULES_PROTO="extern void __samba_debug_dummy_module_proto(void)" -MD -Idefault/include/public -I../include/public -Idefault/source4 -I../source4 -Idefault/lib -I../lib -Idefault/source4/lib -I../source4/lib -Idefault/source4/include -I../source4/include -Idefault/include -I../include -Idefault/lib/replace -I../lib/replace -Idefault -I.. -Idefault/lib/talloc -I../lib/talloc -I/usr/local/include -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H=1 -D_GNU_SOURCE=1 -D_XOPEN_SOURCE_EXTENDED=1 ../lib/util/debug.c -c -save-temps -o default/lib/util/debug_11.o ../lib/util/debug.c: In function 'debug_parse_levels': ../lib/util/debug.c:796:5: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] bool debug_parse_levels(const char *params_str) ^~~~~~~~~~~~~~~~~~ cc1: all warnings being treated as errors -- You are receiving this mail because: You are on the CC list for the bug.

2 18