October 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1231832] New: [Build 20241020] openQA test fails in podman_netavark
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231832 Bug ID: 1231832 Summary: [Build 20241020] openQA test fails in podman_netavark Classification: openSUSE Product: openSUSE Tumbleweed Version: Slowroll Hardware: Other URL: https://openqa.opensuse.org/tests/4580879/modules/podm an_netavark/steps/183 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation Error: netavark: unable to append rule '-j MARK --set-xmark 0x2000/0x2000' to table 'nat': code: 2, msg: Warning: Extension MARK revision 0 not supported, missing kernel module? ip6tables v1.8.10 (legacy): unknown option "--set-xmark" Try `ip6tables -h' or 'ip6tables --help' for more information The 'missing kernel module', and the fact that we updated the kernel to 6.11.4 in this snapshot (and I did not see anything podman/netavark related) triggered me to file this bug against Kernel component openQA test in scenario microos-Tumbleweed-DVD-x86_64-container-host@64bit fails in [podman_netavark](https://openqa.opensuse.org/tests/4580879/modules/podman_n… ## Test suite description ## Reproducible Fails since (at least) Build [20241020](https://openqa.opensuse.org/tests/4580329) ## Expected result Last good: [20241018](https://openqa.opensuse.org/tests/4577907) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1231825] New: Kernel 6.11.4 bluetooth scan stops working
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231825 Bug ID: 1231825 Summary: Kernel 6.11.4 bluetooth scan stops working Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: novell(a)tower-net.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- With Kernel 6.11.4 from https://build.opensuse.org/project/show/Kernel:stable:Backport the bluetooth scan doesn't find my mouse any longer. Rebooting 6.11.3 I can pair mouse and booting 6.11.4 I can use a pre-connected but no reconnect possible. dmesg | grep -i blue: [ 1.826585] usb 3-3: Product: Bluetooth Radio [ 2.947702] Bluetooth: Core ver 2.22 [ 2.947728] NET: Registered PF_BLUETOOTH protocol family [ 2.947730] Bluetooth: HCI device and connection manager initialized [ 2.947739] Bluetooth: HCI socket layer initialized [ 2.947743] Bluetooth: L2CAP socket layer initialized [ 2.947748] Bluetooth: SCO socket layer initialized [ 3.118618] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 3.120636] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 3.120645] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 3.126553] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_config.bin [ 3.128658] Bluetooth: hci0: RTL: cfg_sz 6, total sz 65603 [ 3.192619] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 3.192622] Bluetooth: BNEP filters: protocol multicast [ 3.192628] Bluetooth: BNEP socket layer initialized [ 3.711634] Bluetooth: hci0: RTL: fw version 0x04479301 [ 3.840057] Bluetooth: hci0: AOSP extensions version v1.00 [ 3.840061] Bluetooth: hci0: AOSP quality report is supported [ 4.081505] Bluetooth: MGMT ver 1.23 [ 15.909955] Bluetooth: hci0: AOSP extensions version v1.00 [ 15.909971] Bluetooth: hci0: AOSP quality report is supported [ 17.644507] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input19 [ 17.644841] input: Lenovo Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input20 [ 17.645123] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0002/input/input21 [ 17.645391] hid-generic 0005:17EF:60EF.0002: input,hidraw1: BLUETOOTH HID v0.15 Mouse [Lenovo Bluetooth Mouse] on f4:6a:dd:7d:17:10 [ 131.404331] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input22 [ 131.405030] input: Lenovo Bluetooth Mouse Keyboard as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input23 [ 131.405255] input: Lenovo Bluetooth Mouse as /devices/virtual/misc/uhid/0005:17EF:60EF.0003/input/input24 [ 131.405436] hid-generic 0005:17EF:60EF.0003: input,hidraw1: BLUETOOTH HID v0.15 Mouse [Lenovo Bluetooth Mouse] on f4:6a:dd:7d:17:10 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1228540] New: [SELinux] avc during boot for int-xenstore-d and qemu-system-i386
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1228540 Bug ID: 1228540 Summary: [SELinux] avc during boot for int-xenstore-d and qemu-system-i386 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: conde.philippe(a)skynet.be QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876364 --> https://bugzilla.suse.com/attachment.cgi?id=876364&action=edit output of commande ausearch I have a server with latest openSUSE tumbleweed and with KDE. I have a VM (with opensuse tumbleweed also) that I start with virtmgr when needed. I have activated selinux in permissive mode on the host following your advice: https://en.opensuse.org/Portal:SELinux/Setup#Tumbleweed hpprol2:~ # sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: permissive Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 33 hpprol2:~ # hpprol2:~ # zypper info selinux-policy Loading repository data... Reading installed packages... Information for package selinux-policy: --------------------------------------- Repository : security:SELinux Name : selinux-policy Version : 20240729-249.1 Arch : noarch Vendor : obs://build.opensuse.org/security:SELinux Installed Size : 28.3 KiB Installed : Yes Status : up-to-date Source package : selinux-policy-20240729-249.1.src Upstream URL : https://github.com/fedora-selinux/selinux-policy.git Summary : SELinux policy configuration I boot the xen kernel and receive the errors during boot. as far as I see the problem is with directory /var/lib/xen which is labeled as hpprol2:~ # ls -dZ /var/lib/xen system_u:object_r:xend_var_lib_t:s0 /var/lib/xen hpprol2:~ # ls -lZ /var/lib/xen/* -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 209 Jul 30 10:24 /var/lib/xen/userdata-d.0.00000000-0000-0000-0000-000000000000.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 209 Jul 30 10:24 /var/lib/xen/userdata-d.1.00000000-0000-0000-0000-000000000000.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Jul 5 22:43 /var/lib/xen/userdata-d.2.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Jul 5 22:43 /var/lib/xen/userdata-d.2.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Jul 5 12:01 /var/lib/xen/userdata-d.3.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2181 Jul 5 12:01 /var/lib/xen/userdata-d.3.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Mar 17 11:47 /var/lib/xen/userdata-d.4.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Mar 17 11:47 /var/lib/xen/userdata-d.4.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2257 Oct 20 2023 /var/lib/xen/userdata-d.8.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libvirt-xml -rw-------. 1 root root system_u:object_r:xend_var_lib_t:s0 2121 Oct 20 2023 /var/lib/xen/userdata-d.8.c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad.libxl-json I attach the ausearch -ts today -m avc output related to this problem version of xen-tools Information for package xen-tools: ---------------------------------- Repository : Main Repository (OSS) Name : xen-tools Version : 4.18.2_06-2.1 Arch : x86_64 Vendor : openSUSE Installed Size : 2.8 MiB Installed : Yes (automatically) Status : up-to-date Source package : xen-4.18.2_06-2.1.src Upstream URL : http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Summary : Xen Virtualization: Control tools for domain 0 My vm défintion /etc/libvirt/libxl/opensusetumbleweed.xml  <domain type="xen"> <name>opensusetumbleweed</name> <uuid>c33dd6e1-0a2d-4a5a-9f8b-9f3d804840ad</uuid> <metadata> <libosinfo:libosinfo> <libosinfo:os id="http://opensuse.org/opensuse/tumbleweed"/> </libosinfo:libosinfo> </metadata> <memory unit="KiB">2097152</memory> <currentMemory unit="KiB">2097152</currentMemory> <vcpu placement="static">2</vcpu> <os> <type arch="x86_64" machine="xenfv">hvm</type> <loader type="rom">/usr/lib/xen/boot/hvmloader</loader> <boot dev="hd"/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset="utc"/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/lib/xen/bin/qemu-system-i386</emulator> <disk type="block" device="disk"> <driver name="phy" type="raw"/> <source dev="/dev/disk/by-id/scsi-3600508b1001c21d488c454a46bc39f22-part1"/> <target dev="hda" bus="ide"/> <address type="drive" controller="0" bus="0" target="0" unit="0"/> </disk> <disk type="block" device="cdrom"> <driver name="qemu" type="raw"/> <source dev="/dev/sr0"/> <target dev="hdb" bus="ide"/> <readonly/> <address type="drive" controller="0" bus="0" target="0" unit="1"/> </disk> <controller type="xenbus" index="0"/> <controller type="ide" index="0"/> <interface type="bridge"> <mac address="00:16:3e:9c:13:3e"/> <source bridge="br0"/> </interface> <serial type="pty"> <target port="0"/> </serial> <console type="pty"> <target type="serial" port="0"/> </console> <input type="mouse" bus="ps2"/> <input type="keyboard" bus="ps2"/> <graphics type="vnc" port="-1" autoport="yes"> <listen type="address"/> </graphics> <video> <model type="vga" vram="16384" heads="1" primary="yes"/> </video> <memballoon model="xen"/> </devices> </domain> -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1215865] New: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215865 Bug ID: 1215865 Summary: VUL-0: CVE-2023-0809: mosquitto: excessive memory being allocated based on malicious initial packets that are not CONNECT packets Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-0809 Fix excessive memory being allocated based on malicious initial packets that are not CONNECT packets. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1215864] New: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1215864 Bug ID: 1215864 Summary: VUL-0: CVE-2023-3592: mosquitto: memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: mardnh(a)gmx.de Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- https://security-tracker.debian.org/tracker/DSA-5511-1 CVE-2023-3592 Fix memory leak when clients send v5 CONNECT packets with a will message that contains invalid property types. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1232650] New: Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode
by bugzilla_noreply＠suse.com 04 Nov '24

04 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232650 Bug ID: 1232650 Summary: Lenovo Yoga Pro 7 14ASP9 fails to wake up from suspend mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: 2835365572zty(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Description: I recently received a new Lenovo Yoga Pro 7 14ASP9 and installed Linux on it (kernel version 6.11.5). Most hardware functions as expected out of the box, including Wi-Fi, Bluetooth, touchpad, keyboard backlight, audio, touchscreen, and graphics card. However, the system fails to wake up after entering sleep/suspend mode. When the system goes into suspend, the power button indicator light continues flashing, but attempting to wake it by pressing the keyboard or the power button has no effect. The system remains unresponsive. I also tried running sudo rtcwake -m mem -s 20 to test suspend mode, but the system did not wake up after the specified 20 seconds. Hardware Information: Device Model: Lenovo Yoga Pro 7 14ASP9 Linux Kernel Version: 6.11.5 dmesg log: https://linux-hardware.org/?probe=414716466d&log=dmesg.1 Full Hardware Probe: https://linux-hardware.org/?probe=414716466d https://pastebin.com/eMTCCPp3 Here is loglevel7 version. Steps to Reproduce: 1.Put the device into suspend/sleep mode via the power menu or by using sudo rtcwake -m mem -s 20. 2.Wait for the device to enter suspend, as indicated by the flashing power button light. 3.Attempt to wake the device by pressing any key or the power button. Expected Behavior: The device should resume from suspend mode, with the display and other system functions restored to a usable state. Actual Behavior: The device remains unresponsive, with only the power button indicator flashing. The system does not respond to key presses or the power button, requiring a forced reboot to recover. Additional Notes: 1.This issue has been observed consistently with kernel version 6.11.5. 2.No errors or warnings related to this behavior appear in the logs leading up to suspend. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1218784] New: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc
by bugzilla_noreply＠suse.com 03 Nov '24

03 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1218784 Bug ID: 1218784 Summary: ark cannot open tar archives which contain files with non-ascii chars in filename like umlauts äöÜ etc 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: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: otto47(a)bk13.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- create two files bla.txt and test-ö.txt, then put them into a new tar achive. Opening this archive by ark throws a message "The archive you're trying to open is corrupt. Some files may be missing or damaged." It offers two buttons "Open as Read-Only" plus " Don't Open". Opening as Read-Only displays only one file bla.txt in the archive -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1232644] New: Upgrade 15.5 > 15.6 makes Apache served website unusable
by bugzilla_noreply＠suse.com 03 Nov '24

03 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1232644 Bug ID: 1232644 Summary: Upgrade 15.5 > 15.6 makes Apache served website unusable Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Apache Assignee: apache-bugs(a)suse.de Reporter: henk.vanvelden(a)xs4all.nl QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Upgraded Leap 15.5 > 15.6 using the on-line metod (with --releasver). Website can not be reached, but Alias roots and deep links function. Found out that /srv/www/htdocs/index.html and /srv/www/htdocs/favicon.ico were . renamed to the same name with suffix .rpmnew; . owner changed to root:root; . r-bit for group removed. After reporting on the openSUSE forums, some member hinted at looking in the zypper log: # 2024-10-28 14:41:11 apache2-2.4.58-150600.5.26.1.x86_64.rpm installed ok # Additional rpm output: # Please check /etc/permissions.local for settings of /usr/sbin/suexec . # Updating /etc/sysconfig/apache2 ... # warning: /srv/www/htdocs/index.html saved as /srv/www/htdocs/index.html.rpmsave # warning: /srv/www/htdocs/favicon.ico saved as /srv/www/htdocs/favicon.ico.rpmsave # Requesting apache restart (all instances) # So it saves these, but there is no replacement (as is normaly the csae when .rpmnew is created. I do not know what the idea behind this could be. But I hope that breaking the main page of the website is not as intended. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1231061] New: [Leap 15.6; TW] KDE Plasma Wayland locks up when Distrobox (with Docker) container is ran
by bugzilla_noreply＠suse.com 03 Nov '24

03 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231061 Bug ID: 1231061 Summary: [Leap 15.6; TW] KDE Plasma Wayland locks up when Distrobox (with Docker) container is ran Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ciao.tuto2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0 Build Identifier: When running a Distrobox container with systemd (when creating container add "--init" flag) with Docker on Plasma in Wayland, the DE locks up. This issue happens on Tumbleweed as well, but it doesn't happen in any other distro. It also doesn't happen if Plasma is ran in X11. It doesn't happen if the container manager is podman, but then there is no way to run snaps in a rootless container, which for my workflow is needed. There are no stderr messages in "$HOME/.local/share/sddm/wayland-session.log" Reproducible: Always Steps to Reproduce: 1. Install distrobox and docker. sudo zypper in distrobox docker 2. Add the user to the group, enable docker and reboot. sudo usermod -a -G docker user && sudo systemctl enable docker.service && sudo reboot 3. Create the distrobox container on Plasma using Wayland. It doesn't matter which distro is ran nor the name, but it's important that systemd is present. distrobox create --image quay.io/toolbx/ubuntu-toolbox:24.04 --init --name 'ubuntu' 4. Enter the distrobox and after "Firing up init system." it will freeze. distrobox enter ubuntu Actual Results: Plasma freezes. Expected Results: It shouldn't have freezed. Video to reproduce steps and to show what happens: https://0x0.st/XgZ0.mp4 (I have encrypted the VM drive because that's what I had on the hardware I have the issue on) Log of "journalctl > log.txt": https://0x0.st/XgZD.txt Log of "journalctl -xu docker.service > logdockerd.txt": https://0x0.st/XgZk.txt (I have no idea why some things are in italian even though I set english in KDE Plasma Settings) Log of "docker logs ubuntu > logcontainer.txt": https://0x0.st/XgZd.txt -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1231594] New: Unable to drag'n'drop since plasma 6.2 update
by bugzilla_noreply＠suse.com 02 Nov '24

02 Nov '24

https://bugzilla.suse.com/show_bug.cgi?id=1231594 Bug ID: 1231594 Summary: Unable to drag'n'drop since plasma 6.2 update 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: pallaswept(a)proton.me QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I am unable to use drag'n'drop in various KDE applications, since updating to plasma 6.2 (or more specifically, since the 20241006 snapshot) I've noticed this in kate, dolphin, and the plasma desktop panels, such as task manager and launcher. Drag'n'drop works for example inside the browser (firefox). I filed bugs with KDE, they are unable to replicate, and have requested that I report this bug here. Upstream bugs: https://bugs.kde.org/show_bug.cgi?id=494581 https://bugs.kde.org/show_bug.cgi?id=494582 https://bugs.kde.org/show_bug.cgi?id=494520 https://bugs.kde.org/show_bug.cgi?id=494622 Video: (more available from links above, including with a new user account) https://bugsfiles.kde.org/attachment.cgi?id=174721 Thanks for any help you could give with this. -- You are receiving this mail because: You are on the CC list for the bug.

1 1