2256993 – Bluetooth speaker disconnecting as soon as music stop playing

Bug 2256993 - Bluetooth speaker disconnecting as soon as music stop playing

Summary: Bluetooth speaker disconnecting as soon as music stop playing

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	bluez
Sub Component:
Version:	39
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	---
Assignee:	Gopal krishna tiwari
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Duplicates (3):	2255534 2256964 2257093 (view as bug list)
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2024-01-05 21:58 UTC by Jakub Jankiewicz
Modified:	2024-01-29 07:52 UTC (History)
CC List:	7 users (show)
Fixed In Version:	bluez-5.71-3.fc39 bluez-5.72-1.fc38
Clone Of:
Environment:
Last Closed:	2024-01-10 01:09:00 UTC
Type:	---
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Description Jakub Jankiewicz 2024-01-05 21:58:29 UTC

There was no issues with Bluetooth but now when I play music on YouTube and TY pauses to confirm that you still listening or there is a short connection problem and the music is not playing, the Bluetooth speaker immediately disconnects.

Reproducible: Always

Steps to Reproduce:
1. Connect Bluetooth speaker
2. Palay music
3. Stop it
Actual Results:  
Bluetooth disconnects

Expected Results:  
Bluetooth is still connected

This is the output of dmesg:

[1907316.519605] bluetoothd[3566258]: segfault at 55c6300e1d05 ip 000055c36b059e96 sp 00007ffd7fe0a970 error 4 in bluetoothd[55c36b038000+e0000] likely on CPU 3 (core 3, socket 0)
[1907316.519648] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1907685.088241] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input45
[1907725.463015] bluetoothd[3575581]: segfault at 55db5c1c8acc ip 000055de018a2e96 sp 00007ffdc9f2b710 error 4 in bluetoothd[55de01881000+e0000] likely on CPU 4 (core 0, socket 0)
[1907725.463029] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1907726.611277] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input46
[1907828.470224] bluetoothd[3577125]: segfault at 55de301c5e6e ip 000055db6d6dde96 sp 00007ffd41c87120 error 4 in bluetoothd[55db6d6bc000+e0000] likely on CPU 2 (core 2, socket 0)
[1907828.470241] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1907910.494740] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input47
[1910330.204181] bluetoothd[3577762]: segfault at 5654fb2ce2dd ip 000056519dc50e96 sp 00007ffea8364170 error 4 in bluetoothd[56519dc2f000+e0000] likely on CPU 6 (core 2, socket 0)
[1910330.204206] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1910331.270310] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input48
[1913538.316578] bluetoothd[3585355]: segfault at 55fb168beba6 ip 000055fe477f9e96 sp 00007ffcf2e9fc80 error 4 in bluetoothd[55fe477d8000+e0000] likely on CPU 3 (core 3, socket 0)
[1913538.316602] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1913539.400512] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input49
[1915966.074993] bluetoothd[3595033]: segfault at 55b399f97e81 ip 000055b6c1a46e96 sp 00007ffd4503ba20 error 4 in bluetoothd[55b6c1a25000+e0000] likely on CPU 7 (core 3, socket 0)
[1915966.075007] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1915986.057379] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input50
[1916619.495526] bluetoothd[3602300]: segfault at 55fa6ee0370b ip 000055ff2f52ce96 sp 00007ffc57445870 error 4 in bluetoothd[55ff2f50b000+e0000] likely on CPU 4 (core 0, socket 0)
[1916619.495538] Code: 4c 89 f7 e8 cc ac 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
[1916640.044473] input: JBL Flip 4 (AVRCP) as /devices/virtual/input/input51

Comment 1 Jakub Jankiewicz 2024-01-06 12:17:00 UTC

Additional information:

I use a Dell Inspiron 15 5570 i7-8550U laptop and JBL Flip 4 Speaker

Got this error from btmon when Bluetooth speaker disconnects.

@ MGMT Event: Device Disconnected (0x000c) plen 8                                                                             {0x0001} [hci0] 540.821335
        BR/EDR Address: 04:FE:A1:57:6D:F3 (Fihonest communication co.,Ltd)
        Reason: Connection terminated by local host (0x02)

Comment 2 Peter Robinson 2024-01-07 15:51:38 UTC

Please report at least the versions of bluez and the kernel, and probably better to use abrt to report the bug as it will give a full backtrace with symbols so we can vaguely see what's actually going on.

Comment 3 Peter Robinson 2024-01-07 15:53:11 UTC

*** Bug 2257093 has been marked as a duplicate of this bug. ***

Comment 4 Peter Robinson 2024-01-07 15:53:33 UTC

*** Bug 2256964 has been marked as a duplicate of this bug. ***

Comment 5 Jakub Jankiewicz 2024-01-07 16:04:49 UTC

Bluez 5.71-2.fc39
Kernel: 6.6.9-200.fc39.x86_64

The app crashed but I don't get a popup with a way to report an error. I'm not sure how to run abrt when it didn't provide a way to report a bug.

Comment 6 Steevithak 2024-01-07 19:09:00 UTC

My Bug 2256964 was marked as a duplicate of this one, so I'll add my info here too.

In my case bluetoothd is crashing with a segfault several times per day during normal use. I have two bluetooth devices which have worked perfectly up until the recent bluez update. They are:
1. A Kensington Smart Mouse
2. Edifier R1700BT speakers

I'm running Fedora 38 on an Intel NUC13L3Kv7 (with Intel Core i7-1370P cpu).
Versions of relevant packages:
- bluez-5.71-2.fc38.x86_64  (problem started with 5.71-1 update I believe)
- kernel-6.6.9-100.fc38.x86_64 

and here's a copy of journalctl output during the crash:

Jan 05 11:33:02 fedora audit[12591]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:bluetooth_t:s0 pid=12591 comm="bluetoothd" exe="/usr/libexec/bluetooth/bluetoothd" sig=11 res=1
Jan 05 11:33:02 fedora kernel: bluetoothd[12591]: segfault at 55f1bbdb0b7c ip 000055f4e3174e36 sp 00007ffc96788450 error 4 in bluetoothd[55f4e3153000+e0000] likely on CPU 7 (core 12, socket 0)
Jan 05 11:33:02 fedora kernel: Code: 4c 89 f7 e8 ac ad 0b 00 31 c0 e9 51 ff ff ff 0f 1f 44 00 00 f3 0f 1e fa 55 48 8b 7a 08 48 89 e5 41 56 41 55 41 54 4c 8b 22 53 <49> 8b 44 24 20 4d 8b b4 24 88 00 00 00 4c 8b 28 48 85 ff 74 19 c7
Jan 05 11:33:02 fedora audit: BPF prog-id=114 op=LOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=115 op=LOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=116 op=LOAD
Jan 05 11:33:02 fedora systemd[1]: Started systemd-coredump - Process Core Dump (PID 14112/UID 0).
Jan 05 11:33:02 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@2-14112-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 05 11:33:02 fedora systemd-coredump[14113]: [🡕] Process 12591 (bluetoothd) of user 0 dumped core.
                                                
                                                Module libudev.so.1 from rpm systemd-253.14-1.fc38.x86_64
                                                Module sixaxis.so from rpm bluez-5.71-2.fc38.x86_64
                                                Module liblz4.so.1 from rpm lz4-1.9.4-2.fc38.x86_64
                                                Module libzstd.so.1 from rpm zstd-1.5.5-1.fc38.x86_64
                                                Module liblzma.so.5 from rpm xz-5.4.1-1.fc38.x86_64
                                                Module libcap.so.2 from rpm libcap-2.48-8.fc38.x86_64
                                                Module libsystemd.so.0 from rpm systemd-253.14-1.fc38.x86_64
                                                Module libpcre2-8.so.0 from rpm pcre2-10.42-1.fc38.1.x86_64
                                                Module libdbus-1.so.3 from rpm dbus-1.14.10-1.fc38.x86_64
                                                Module libglib-2.0.so.0 from rpm glib2-2.76.6-1.fc38.x86_64
                                                Module bluetoothd from rpm bluez-5.71-2.fc38.x86_64
                                                Stack trace of thread 12591:
                                                #0  0x000055f4e3174e36 a2dp_suspend_complete (bluetoothd + 0x43e36)
                                                #1  0x000055f4e315b04f finalize_suspend.lto_priv.0 (bluetoothd + 0x2a04f)
                                                #2  0x000055f4e315d270 suspend_cfm.lto_priv.0 (bluetoothd + 0x2c270)
                                                #3  0x000055f4e316b469 session_cb (bluetoothd + 0x3a469)
                                                #4  0x00007f79334ce4fc g_main_context_dispatch (libglib-2.0.so.0 + 0x5c4fc)
                                                #5  0x00007f793352c6b8 g_main_context_iterate.isra.0 (libglib-2.0.so.0 + 0xba6b8)
                                                #6  0x00007f79334cdaff g_main_loop_run (libglib-2.0.so.0 + 0x5baff)
                                                #7  0x000055f4e3157bed main (bluetoothd + 0x26bed)
                                                #8  0x00007f7933266b8a __libc_start_call_main (libc.so.6 + 0x27b8a)
                                                #9  0x00007f7933266c4b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c4b)
                                                #10 0x000055f4e3158d35 _start (bluetoothd + 0x27d35)
                                                ELF object binary architecture: AMD x86-64
Jan 05 11:33:02 fedora systemd[1]: systemd-coredump: Deactivated successfully.
Jan 05 11:33:02 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@2-14112-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 05 11:33:02 fedora audit: BPF prog-id=116 op=UNLOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=115 op=UNLOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=114 op=UNLOAD
Jan 05 11:33:02 fedora systemd[1]: bluetooth.service: Main process exited, code=dumped, status=11/SEGV
Jan 05 11:33:02 fedora systemd[1]: bluetooth.service: Failed with result 'core-dump'.
Jan 05 11:33:02 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jan 05 11:33:02 fedora systemd[1]: bluetooth.service: Consumed 2.460s CPU time.
Jan 05 11:33:02 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
Jan 05 11:33:02 fedora bluetoothd[14149]: Bluetooth daemon 5.71
Jan 05 11:33:02 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
Jan 05 11:33:02 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 05 11:33:02 fedora bluetoothd[14149]: Starting SDP server
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support csip plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support micp plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support vcp plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support mcp plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support bass plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: src/plugin.c:plugin_init() System does not support bap plugin
Jan 05 11:33:02 fedora bluetoothd[14149]: Bluetooth management interface 1.22 initialized
Jan 05 11:33:02 fedora bluetoothd[14149]: Battery Provider Manager created
Jan 05 11:33:02 fedora bluetoothd[14149]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Jan 05 11:33:02 fedora bluetoothd[14149]: Failed to set privacy: Rejected (0x0b)
Jan 05 11:33:02 fedora gsd-media-keys[2577]: Unable to get default sink
Jan 05 11:33:02 fedora audit: BPF prog-id=117 op=LOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=118 op=LOAD
Jan 05 11:33:02 fedora audit: BPF prog-id=119 op=LOAD
Jan 05 11:33:02 fedora gsd-media-keys[2577]: Unable to get default source
Jan 05 11:33:02 fedora systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/ldac
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/aac
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/aac
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/sbc_xq
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/sbc_xq
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/faststream
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/opus_05
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/opus_05
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 05 11:33:02 fedora bluetoothd[14149]: Endpoint registered: sender=:1.86 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 05 11:33:02 fedora bluetoothd[14149]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 05 11:33:02 fedora kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Jan 05 11:33:02 fedora systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Jan 05 11:33:02 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 05 11:33:02 fedora abrt-server[14164]: Deleting problem directory ccpp-2024-01-05-11:33:02.622954-12591 (dup of ccpp-2023-12-30-17:16:35.769038-4599)
Jan 05 11:33:03 fedora abrt-notification[14223]: [🡕] Process 4599 (bluetoothd) crashed in a2dp_suspend_complete()

Comment 7 Peter Robinson 2024-01-07 20:55:57 UTC

Looks like this report upstream:
https://github.com/bluez/bluez/issues/701

Looks like we have a fix, I'll do a scratch build for confirmation it fixes.

Comment 8 Peter Robinson 2024-01-07 21:01:01 UTC

Hmm, of course it's in a file that's had a lot of churn since the last release, might take a bit :-/

Comment 9 Peter Robinson 2024-01-07 21:34:29 UTC

scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=111447852

Let me know of success/failure.

Comment 10 Peter Robinson 2024-01-08 15:38:10 UTC

*** Bug 2255534 has been marked as a duplicate of this bug. ***

Comment 11 SP 2024-01-08 15:58:55 UTC

Thanks, Peter.  But one needs to run Rawhide fc40 to test.  Any patch available for fc39 stable?

Comment 12 Peter Robinson 2024-01-08 16:02:53 UTC

(In reply to SP from comment #11)
> Thanks, Peter.  But one needs to run Rawhide fc40 to test.  Any patch
> available for fc39 stable?

f39 scratch build running here: https://koji.fedoraproject.org/koji/taskinfo?taskID=111482750

Comment 13 SP 2024-01-08 17:20:06 UTC

Peter - thank you.  That fixes it.  Bluetoothd no longer crashes when the output to the device is paused or stopped.   Downloaded bluez-5.71-2.1.fc39.x86_64.rpm        bluez-deprecated-5.71-2.1.fc39.x86_64.rpm   bluez-libs-5.71-2.1.fc39.x86_64.rpm        'bluez-obexd-5.71-2.1.fc39.x86_64(1).rpm'
 bluez-cups-5.71-2.1.fc39.x86_64.rpm   bluez-hid2hci-5.71-2.1.fc39.x86_64.rpm      bluez-libs-devel-5.71-2.1.fc39.x86_64.rpm
and installed with sudo rpm -Uvh bluez-*

Comment 14 SP 2024-01-08 17:39:18 UTC

confirmed as working on two machines.

Comment 15 Fedora Update System 2024-01-08 19:44:00 UTC

FEDORA-2024-93d2d0bf55 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-93d2d0bf55

Comment 16 Fedora Update System 2024-01-08 19:44:01 UTC

FEDORA-2024-c501bb0b43 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c501bb0b43

Comment 17 Fedora Update System 2024-01-09 01:20:42 UTC

FEDORA-2024-c501bb0b43 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c501bb0b43`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c501bb0b43

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 18 Fedora Update System 2024-01-09 01:39:23 UTC

FEDORA-2024-93d2d0bf55 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-93d2d0bf55`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-93d2d0bf55

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 19 Fedora Update System 2024-01-10 01:09:00 UTC

FEDORA-2024-c501bb0b43 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 20 Fedora Update System 2024-01-15 02:05:38 UTC

FEDORA-2024-c8bc092b2b has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c8bc092b2b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c8bc092b2b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 21 Fedora Update System 2024-01-29 07:52:39 UTC

FEDORA-2024-c8bc092b2b has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.