January 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 443819] New: [BETA 5] ksnapshot crashed compiz-decorator when launched
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=443819 Summary: [BETA 5] ksnapshot crashed compiz-decorator when launched Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Compiz AssignedTo: bnc-team-compiz(a)forge.provo.novell.com ReportedBy: ben.kevan(a)gmail.com QAContact: bperry(a)novell.com Found By: --- Today I removed emerald, updating to the compiz in factory (as opposed to the one in XGL) .. and went to take a snapshot w/ ksnapshot and it crashed my compiz-decorator. rpm -qa | grep compiz compiz-plugins-dmx-0.1.0-3.16 compiz-kde-0.7.8-4.7 compizconfig-settings-manager-0.7.8-1.25 compiz-0.7.8-4.7 libcompizconfig-0.7.8-1.28 python-compizconfig-0.7.8-1.28 compiz-fusion-plugins-main-0.7.8-3.17 Also, I am unable to set the Backend as KDE (which I believe compiz-kde should give). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 13

[Bug 343874] New: If the system hybernates with an usb external drive mounted, weird things happen
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=343874 Summary: If the system hybernates with an usb external drive mounted, weird things happen Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robin.listas(a)telefonica.net QAContact: qa(a)suse.de Found By: --- I hibernated forgotting to umount a manually mounted external HD on USB. The disk was on sda1, and mounted using this fstab line: LABEL=usb_sg60 /mnt/usb/usb_sg60 reiserfs noatime,user,noauto,acl,user_xattr 0 0 After hibernating, the disk moves to sdb1: nimrodel:~ # l /dev/disk/by-label/ | grep usb_sg60 lrwxrwxrwx 1 root root 10 Nov 24 14:10 usb_sg60 -> ../../sdb1 but the kernel thinks it is still mounted on sda1: nimrodel:~ # mount -l | grep usb_sg60 /dev/sda1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) and it is possible to remount it correctly: nimrodel:~ # umount /mnt/usb/usb_sg60 nimrodel:~ # mount /mnt/usb/usb_sg60 nimrodel:~ # mount -l | grep usb_sg60 /dev/sdb1 on /mnt/usb/usb_sg60 type reiserfs (rw,noexec,nosuid,nodev,noatime,acl,user_xattr) [usb_sg60] but sda has dissapeared: nimrodel:~ # l /dev/sd?* brw-r----- 1 root disk 8, 16 Nov 24 14:10 /dev/sdb brw-r----- 1 root disk 8, 17 Nov 24 14:10 /dev/sdb1 Here goes the kernel log: Nov 24 14:09:32 nimrodel kernel: swsusp: critical section: Nov 24 14:09:32 nimrodel kernel: swsusp: Need to copy 113403 pages Nov 24 14:09:32 nimrodel kernel: Intel machine check architecture supported. Nov 24 14:09:32 nimrodel kernel: Intel machine check reporting enabled on CPU#0. Nov 24 14:09:32 nimrodel kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) available Nov 24 14:09:32 nimrodel kernel: CPU0: Thermal monitoring enabled Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1e.0 to 64 Nov 24 14:09:32 nimrodel kernel: PM: Writing back config space on device 0000:00:1f.5 at offset 1 (was 2800005, writing 2800001) Nov 24 14:09:32 nimrodel kernel: ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 19 Nov 24 14:09:32 nimrodel kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64 Nov 24 14:09:32 nimrodel kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 17 Nov 24 14:09:38 nimrodel kernel: usb usb2: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.1[B] -> GSI 19 (level, low) -> IRQ 18 Nov 24 14:09:38 nimrodel kernel: usb usb3: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: ACPI: PCI Interrupt 0000:02:02.2[C] -> GSI 16 (level, low) -> IRQ 16 Nov 24 14:09:38 nimrodel kernel: usb usb1: root hub lost power or was reset Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:08 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:09 activated. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0b. Nov 24 14:09:38 nimrodel kernel: pnp: Failed to activate device 00:0c. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0d activated. Nov 24 14:09:38 nimrodel kernel: pnp: Device 00:0e activated. Nov 24 14:09:38 nimrodel kernel: hda: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdb: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: hdc: selected mode 0x42 Nov 24 14:09:38 nimrodel kernel: hdd: selected mode 0x45 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep00: PM: resume from 0, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb-storage 1-1:1.0: PM: resume from 1, parent 1-1 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep02: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: usb_endpoint usbdev1.3_ep86: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: host0: PM: resume from 0, parent 1-1:1.0 still 1 Nov 24 14:09:38 nimrodel kernel: Restarting tasks ... <6>usb 1-1: USB disconnect, address 3 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7514 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: Buffer I/O error on device sda1, logical block 7515 Nov 24 14:09:38 nimrodel kernel: lost page write due to I/O error on sda1 Nov 24 14:09:38 nimrodel kernel: REISERFS abort (device sda1): Journal write error in flush_commit_list Nov 24 14:09:38 nimrodel kernel: done. Nov 24 14:09:38 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 24 14:09:38 nimrodel kernel: usb 1-1: new high speed USB device using ehci_hcd and address 4 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device found, idVendor=04b4, idProduct=6830 Nov 24 14:09:38 nimrodel kernel: usb 1-1: new device strings: Mfr=56, Product=78, SerialNumber=100 Nov 24 14:09:38 nimrodel kernel: usb 1-1: Product: USB2.0 Storage Device Nov 24 14:09:38 nimrodel kernel: usb 1-1: Manufacturer: Cypress Semiconductor Nov 24 14:09:38 nimrodel kernel: usb 1-1: SerialNumber: DEF10000CE2DB1A Nov 24 14:09:38 nimrodel kernel: usb 1-1: configuration #1 chosen from 1 choice Nov 24 14:09:38 nimrodel kernel: scsi1 : SCSI emulation for USB Mass Storage devices Nov 24 14:09:38 nimrodel kernel: usb-storage: device found at 4 Nov 24 14:09:38 nimrodel kernel: usb-storage: waiting for device to settle before scanning Nov 24 14:09:38 nimrodel kernel: scsi 1:0:0:0: Direct-Access ST360020 A 0000 PQ: 0 ANSI: 0 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] 117231408 512-byte hardware sectors (60022 MB) Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Write Protect is off Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Mode Sense: 27 00 00 00 Nov 24 14:09:38 nimrodel kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through Nov 24 14:09:38 nimrodel kernel: sdb:<6>input: Power Button (FF) as /class/input/input18 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 24 14:09:38 nimrodel kernel: input: Power Button (CM) as /class/input/input19 Nov 24 14:09:38 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 24 14:09:38 nimrodel kernel: input: Sleep Button (CM) as /class/input/input20 Nov 24 14:09:38 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB] Nov 24 14:10:03 nimrodel kernel: usb 1-1: reset high speed USB device using ehci_hcd and address 4 Nov 24 14:10:04 nimrodel kernel: sdb1 Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 24 14:10:04 nimrodel kernel: sd 1:0:0:0: Attached scsi generic sg0 type 0 Nov 24 14:10:04 nimrodel kernel: usb-storage: device scan complete Nov 24 14:43:26 nimrodel kernel: scsi 0:0:0:0: rejecting I/O to dead device I suppose I could add my own hook to umount the device if I forget, but I propose that you could add a generic hook to umount usb devices on hybernate, or ensure that they resurrect on the correct device. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 49

[Bug 357354] New: lenovo X60s jw collector bug
by bugzilla_noreply＠novell.com 27 Mar '09

27 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=357354 Summary: lenovo X60s jw collector bug Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: jw(a)novell.com ReportedBy: jw(a)novell.com QAContact: qa(a)suse.de Depends on: 355128 Found By: --- This defect depends on all issues found with my X60s -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 99

[Bug 469803] New: Asus Eee 901: s2ram works but pm-utils doesn't
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=469803 Summary: Asus Eee 901: s2ram works but pm-utils doesn't Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: psychonaut(a)nothingisreal.com QAContact: qa(a)suse.de Found By: --- Created an attachment (id=267949) --> (https://bugzilla.novell.com/attachment.cgi?id=267949) /var/log/pm-suspend.log from a machine that refuses to wake up User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.19) Gecko/20081213 SUSE/1.1.14-3.1 SeaMonkey/1.1.14 I just installed openSUSE 11.1 on my Asus EEE 901. Out of the box, the Suspend to RAM option from the KDE menu seems to correctly suspend the machine, but thereafter it's not possible to wake it. If I press a key while the machine is suspended, all the LEDs light up, but the screen remains blank. The machine is then completely locked up. No key combination (including Ctrl+Alt+F1, Ctrl+Alt+F7, Ctrl+Alt+Backspace, Ctrl+Alt+Delete) can revive it. Pressing or holding down the power button has no effect. The only solution is to remove the AC power and battery. This same problem also occurs if s2ram -f is run as root. However, if I run s2ram -f -a 2 as root, then the machine can suspend and wake just fine. So I created a file /etc/pm/config.d/config with the following contents: S2RAM_OPTS="-f -a 2" This should make pm-utils work, right? Well, I tried using the Suspend to RAM option from the K Menu again, and it failed the same as before: successful suspend, but not possible to wake. According to /var/log/pm-suspend.log (attached), pm-utils did find the S2RAM_OPTS option, so it presumably invoked s2ram with the correct options. But for some reason, it's still causing the machine to lock up. Reproducible: Always Steps to Reproduce: 1. Createda file /etc/pm/config.d/config with the following contents: S2RAM_OPTS="-f -a 2" 2. K Menu->Leave->Suspend to RAM Actual Results: 3. Machine suspends, but won't wake up again. Expected Results: 3. Machine should suspend and wake up again when a key is pressed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 14

[Bug 463172] New: In frontend - rake db:migrate fails with " Multiple migrations have the name AddArchs"
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=463172 Summary: In frontend - rake db:migrate fails with "Multiple migrations have the name AddArchs" Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: srinidhi(a)novell.com QAContact: adrian(a)novell.com Found By: --- Fresh checkout from SVN trunk on a freshly installed on 64 bit openSUSE 11.1. Installed mysql, ruby-mysql and ran the following commands: $ rake db:create (in /home/srinidhi/repos/obs/buildservice/src/frontend) Using global environment /home/srinidhi/repos/obs/buildservice/src/frontend/config/environments/development_base.rb $ rake db:migrate (in /home/srinidhi/repos/obs/buildservice/src/frontend) Using global environment /home/srinidhi/repos/obs/buildservice/src/frontend/config/environments/development_base.rb rake aborted! Multiple migrations have the name AddArchs (See full trace by running task with --trace) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 455774] New: tcpdump doesn't work on usb0 network device
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=455774 Summary: tcpdump doesn't work on usb0 network device Product: openSUSE 11.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joop_boonen(a)web.de QAContact: qa(a)suse.de Found By: --- tcpdump doesn't work on usb0 network device centrino:~ # tcpdump -lni usb0 tcpdump: Can't open USB bus file /sys/kernel/debug/usbmon/0t: No such file or di rectory centrino:~ # ifconfig -a br0 Link encap:Ethernet HWaddr 00:14:C2:D8:38:59 inet addr:192.168.0.131 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::214:c2ff:fed8:3859/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:635 errors:0 dropped:0 overruns:0 frame:0 TX packets:502 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:837466 (817.8 Kb) TX bytes:44366 (43.3 Kb) eth0 Link encap:Ethernet HWaddr 00:12:F0:82:8E:D0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:21 Base address:0x6000 Memory:d0000000-d0000fff eth1 Link encap:Ethernet HWaddr 00:14:C2:D8:38:59 inet6 addr: fe80::214:c2ff:fed8:3859/64 Scope:Link UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 RX packets:635 errors:0 dropped:0 overruns:0 frame:0 TX packets:504 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:848896 (829.0 Kb) TX bytes:46516 (45.4 Kb) Interrupt:16 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:62 errors:0 dropped:0 overruns:0 frame:0 TX packets:62 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4028 (3.9 Kb) TX bytes:4028 (3.9 Kb) usb0 Link encap:Ethernet HWaddr 8A:9E:E1:F7:30:EC inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::889e:e1ff:fef7:30ec/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:4 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11911 (11.6 Kb) TX bytes:5482 (5.3 Kb) centrino:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 29

[Bug 458324] New: use of really abort pop up in network settings module even if no changes are made
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458324 Summary: use of really abort pop up in network settings module even if no changes are made Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mschmidkunz(a)novell.com QAContact: jsrain(a)novell.com Found By: --- If the user made no changes in the network settings module and closes it, a really abort pop up appears. According to the style guide the really abort pop up should only be used, when changes are made (http://en.opensuse.org/YaST/Style_Guide#Generic_YaST_Dialog). Please fix this as this enhances the consistency with the other YaST modules. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 384579] New: zypper should be able to download only
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=384579 Summary: zypper should be able to download only Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: cgoncalves(a)opensuse.org QAContact: dmacvicar(a)novell.com Found By: --- Sometimes users don't want to download and install packages at the same time because they just want to download and them install later. There are several reasons: - running on battery; - not the appropriate time to get their system under heavy resource usage; - or simply because they want to download everything first and install afterwards. So my request is if it would be possible to add a --download-only feature into update, upgrade, and install zypper commands. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 9

[Bug 390526] New: yast2-gtk: During automatic installation, some dialog boxes have abort, others don't
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=390526 Summary: yast2-gtk: During automatic installation, some dialog boxes have abort, others don't Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: captain.magnus(a)opensuse.org QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=215337) --> (https://bugzilla.novell.com/attachment.cgi?id=215337) Now Featuring... An abort button First, why do we have these really small and ugly dialog boxes information the user about "Detecting this" and "Detecting that"? Wouldn't it be better to have an icon row below the two status bars in the main window which are grayed out to start with, and as it progresses with hardware detection, light them up (Same as in the beginning of the installation). Anyway... During hardware detection, one dialog box stands out as it contains an abort button, whilst none of the others have it. It'd be nice to get some consistency. See attached screenshots. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 281270] New: RPM package installation fails if the location(i.e, folder names) contains spaces in between with "Install Software"
by bugzilla_noreply＠novell.com 26 Mar '09

26 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=281270 Summary: RPM package installation fails if the location(i.e, folder names) contains spaces in between with "Install Software" Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: openSUSE 10.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mailtoravi_79(a)yahoo.co.in QAContact: jsrain(a)novell.com Pre-Condition: Make sure that you have any RPM package in a folder which has spaces in between. Used "VMware-workstation-5.5.3-34685.i386.rpm" for testing. Steps: 1. Select the RPM package "VMware-workstation-5.5.3-34685.i386.rpm" 2. Right click and choose 'Open with "Install Software". Actual Result: Error message "Transaction failed: Invalid path name component '/ravikumar/Desktop/VMWare/VMWare Linux Builds/VMware-workstation-5.5.3-34685.i386.rpm" is displayed. Expected Result: Installation should be successful. Note: Observed the same behavior on both "GNOME" and "KDE" desktop sessions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 6