https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c2 --- Comment #2 from David Rankin 2014-07-18 00:24:03 UTC --- I have tried to summarize boot entries related to video card initialization and backlight control from both the 11.4 dmesg output and 13.1 journalctl. The full output is contained in the attachment posted earlier. Both appear to register the backlight control, but 11.4 assigns acpi device:27 and the result is backlight control works. 13.1 appears to do the same thing, but has additional entries not present in 11.4. Whatever 13.1 is doing, the backlight control does not work in 13.1. Here is a summary of related entries from the 11.4 dmesg file: [ 2.936191] radeon 0000:01:05.0: power state changed by ACPI to D0 [ 2.936200] radeon 0000:01:05.0: power state changed by ACPI to D0 [ 2.936210] radeon 0000:01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 Later initializing Radeon Display Connection, 11.4 does the following: [ 2.956647] [drm] Radeon Display Connectors [ 2.956650] [drm] Connector 0: [ 2.956652] [drm] VGA [ 2.956654] [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c [ 2.956657] [drm] Encoders: [ 2.956658] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 2.956660] [drm] Connector 1: [ 2.956662] [drm] LVDS [ 2.956664] [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c [ 2.956666] [drm] Encoders: [ 2.956668] [drm] LCD1: INTERNAL_LVTM1 [ 2.956670] [drm] Connector 2: [ 2.956671] [drm] S-video [ 2.956673] [drm] Encoders: [ 2.956674] [drm] TV1: INTERNAL_KLDSCP_DAC1 [ 3.510984] [drm] fb mappable at 0xF0040000 [ 3.510988] [drm] vram apper at 0xF0000000 [ 3.510990] [drm] size 5300224 [ 3.510992] [drm] fb depth is 24 [ 3.510994] [drm] pitch is 5888 Then the backlight is initially set in 11.4: [ 11.641707] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness [ 11.645898] acpi device:27: registered as cooling_device2 [ 11.646134] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/LNXVIDEO:01/input/input6 [ 11.646216] ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) There are no further entries in 11.4 that I could find. In the 13.1 output, after entries similar to 11.4, 13.1 appears to initialize 'radeon atom DIG backlight initialized' (which may be what 11.4 does), but it is not working: Jul 16 15:52:27 alchemy kernel: ohci-pci 0000:00:13.0: irq 16, io mem 0xf8704000 Jul 16 15:52:27 alchemy kernel: [drm] radeon atom DIG backlight initialized Jul 16 15:52:27 alchemy kernel: [drm] Radeon Display Connectors Jul 16 15:52:27 alchemy kernel: [drm] Connector 0: Jul 16 15:52:27 alchemy kernel: [drm] VGA-1 Jul 16 15:52:27 alchemy kernel: [drm] DDC: 0x7e50 0x7e40 0x7e54 0x7e44 0x7e58 0x7e48 0x7e5c 0x7e4c Jul 16 15:52:27 alchemy kernel: [drm] Encoders: Jul 16 15:52:27 alchemy kernel: [drm] CRT1: INTERNAL_KLDSCP_DAC1 Jul 16 15:52:27 alchemy kernel: [drm] Connector 1: Jul 16 15:52:27 alchemy kernel: [drm] LVDS-1 Jul 16 15:52:27 alchemy kernel: [drm] DDC: 0x7e40 0x7e50 0x7e44 0x7e54 0x7e48 0x7e58 0x7e4c 0x7e5c Jul 16 15:52:27 alchemy kernel: [drm] Encoders: Jul 16 15:52:27 alchemy kernel: [drm] LCD1: INTERNAL_LVTM1 Jul 16 15:52:27 alchemy kernel: [drm] Connector 2: Jul 16 15:52:27 alchemy kernel: [drm] SVIDEO-1 Jul 16 15:52:27 alchemy kernel: [drm] Encoders: Jul 16 15:52:27 alchemy kernel: [drm] TV1: INTERNAL_KLDSCP_DAC1 The 13.1 entries to initialize backlight control are almost identical to 11.4, but entries are in a different order: Jul 16 15:52:28 alchemy kernel: [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness Jul 16 15:52:28 alchemy kernel: acpi device:27: registered as cooling_device2 Jul 16 15:52:28 alchemy kernel: ACPI: Video Device [VGA1] (multi-head: yes rom: no post: no) Jul 16 15:52:28 alchemy kernel: input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/LNXVIDEO:01/input/input6 Jul 16 15:52:28 alchemy kernel: ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared Hopefully this will help. Let me know if you need additional information. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c4 --- Comment #4 from David Rankin 2014-07-22 07:47:50 UTC --- (In reply to comment #3)

So, actually there are two problems. The main issue is that acpi video driver got broken for this laptop, and another issue is that radeon native backlight control doesn't work well either.

Could you try the upstream kernel from OBS Kernel:stable repo to see whether both issues are addressed? There have been known fixes for acpi video backlight (and rather disabling it) in the upstream.

The backport to openSUSE 13.1 kernel might be not so easy, as it may affect too many devices, unfortunately... Let's see.

Takashi, I'll be happy to give it a try. I should be able to get to it tomorrow evening when I get back in town. In the mean time, do you have any ideas why the acpi video driver isn't seeing the function key? As detailed above, using acpi_listen, I confirm that the key codes are generated, but for some reason the mapping of the key codes does not get mapped into /sys/class/backlight/acpi_video0/brightness? It appears if the connection/mapping/whatever would just send the fn key, the backlight would work as normal with the current kernel. My manual echo [0-7] > /sys/class/backlight/acpi_video0/brightness works fine? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c6 --- Comment #6 from Takashi Iwai 2014-07-24 09:58:08 UTC --- For the brightness key, ACPI video driver just notifies the input to the input device. How to interpret the key event depends on the rest user-space. Usually a desktop takes the key event and increases/decreases the backlight via xrandr function. Check whether you can get/set the backlight level via xbacklight program. If xbacklight program works as expected, the problem is the missing handling of brightness key input events. If xbacklight program doesn't work, the problem is broken native driver or wrong video driver choice. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c8 --- Comment #8 from David Rankin 2014-07-24 22:02:08 UTC --- Created an attachment (id=599839) --> (http://bugzilla.novell.com/attachment.cgi?id=599839) module list for both 11.4 & 13.1 (lsmod from each) I don't know if this will help, but maybe it will. Here is a list of modules loaded from 11.4 and from 13.1. Created with lsmod > modlist_###.txt. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c10 --- Comment #10 from David Rankin 2014-07-25 06:47:55 UTC --- Takashi, Yes, both /sys/class/backlight/acpi_video0 and /sys/class/backlight/radeon_bl0 are both still present just exactly as they have been. I'll attach the Xorg log. $ xrandr --verbose Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x51 Timestamp: 31626 Subpixel: no subpixels Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: load detection: 1 range: (0, 1) LVDS connected 1440x900+0+0 (0x55) normal (normal left inverted right x axis y axis) 367mm x 230mm Identifier: 0x52 Timestamp: 31626 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff004ca3473800000000 00100103802517780a87f594574f8c27 27505400000001010101010101010101 0101010101019f25a04051840c304020 33006fe6100000190000000f00000000 000000000078e6022300000000fe0053 414d53554e470a2020202020000000fe 004c544e31373058322d4c30320a00f1 scaling mode: Full supported: None, Full, Center, Full aspect 1440x900 (0x55) 96.3MHz -HSync -VSync *current +preferred h: width 1440 start 1504 end 1536 total 1760 skew 0 clock 54.7KHz v: height 900 start 903 end 906 total 912 clock 60.0Hz 1280x854 (0x56) 89.2MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 53.1KHz v: height 854 start 857 end 867 total 887 clock 59.9Hz 1280x800 (0x57) 83.5MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.7KHz v: height 800 start 803 end 809 total 831 clock 59.8Hz 1280x720 (0x58) 74.5MHz -HSync +VSync h: width 1280 start 1344 end 1472 total 1664 skew 0 clock 44.8KHz v: height 720 start 723 end 728 total 748 clock 59.9Hz 1152x768 (0x59) 71.8MHz -HSync +VSync h: width 1152 start 1216 end 1328 total 1504 skew 0 clock 47.7KHz v: height 768 start 771 end 781 total 798 clock 59.8Hz 1024x768 (0x5a) 63.5MHz -HSync +VSync h: width 1024 start 1072 end 1176 total 1328 skew 0 clock 47.8KHz v: height 768 start 771 end 775 total 798 clock 59.9Hz 800x600 (0x5b) 38.2MHz -HSync +VSync h: width 800 start 832 end 912 total 1024 skew 0 clock 37.4KHz v: height 600 start 603 end 607 total 624 clock 59.9Hz 848x480 (0x5c) 31.5MHz -HSync +VSync h: width 848 start 872 end 952 total 1056 skew 0 clock 29.8KHz v: height 480 start 483 end 493 total 500 clock 59.7Hz 720x480 (0x5d) 26.8MHz -HSync +VSync h: width 720 start 744 end 808 total 896 skew 0 clock 29.9KHz v: height 480 start 483 end 493 total 500 clock 59.7Hz 640x480 (0x5e) 23.8MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew 0 clock 29.7KHz v: height 480 start 483 end 487 total 500 clock 59.4Hz S-video disconnected (normal left inverted right x axis y axis) Identifier: 0x53 Timestamp: 31626 Subpixel: no subpixels Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: tv standard: ntsc supported: ntsc, pal, pal-m, pal-60, ntsc-j, scart-pal, pal-cn, secam load detection: 1 range: (0, 1) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c12 --- Comment #12 from David Rankin 2014-07-25 07:02:25 UTC --- Created an attachment (id=599877) --> (http://bugzilla.novell.com/attachment.cgi?id=599877) Xorg.0.log - 11.4 working backlight Takashi, I have also attached the Xorg.0.log from 11.4 where the backlight is working fine. Let me know if you need anything else. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c14 --- Comment #14 from David Rankin 2014-07-25 16:30:35 UTC --- The behavior is the same in 13.1 OSS. This is frustrating. the backlight keys have always worked on this laptop and I've had at least 5 different operating systems on it. Never a problem until now. The tests booting to the 3.11 OSS kernel are the same: $ uname -a Linux alchemy 3.11.10-17-desktop #1 SMP PREEMPT Mon Jun 16 15:28:13 UTC 2014 (fba7c1f) x86_64 x86_64 x86_64 GNU/Linux $ xbacklight No outputs have backlight property $ xrandr --verbose Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x51 Timestamp: 39292 Subpixel: no subpixels Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: load detection: 1 range: (0, 1) LVDS connected 1440x900+0+0 (0x55) normal (normal left inverted right x axis y axis) 367mm x 230mm Identifier: 0x52 Timestamp: 39292 Subpixel: horizontal rgb Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 0 CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: EDID: 00ffffffffffff004ca3473800000000 00100103802517780a87f594574f8c27 27505400000001010101010101010101 0101010101019f25a04051840c304020 33006fe6100000190000000f00000000 000000000078e6022300000000fe0053 414d53554e470a2020202020000000fe 004c544e31373058322d4c30320a00f1 scaling mode: Full supported: None, Full, Center, Full aspect 1440x900 (0x55) 96.3MHz -HSync -VSync *current +preferred h: width 1440 start 1504 end 1536 total 1760 skew 0 clock 54.7KHz v: height 900 start 903 end 906 total 912 clock 60.0Hz 1280x854 (0x56) 89.2MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 53.1KHz v: height 854 start 857 end 867 total 887 clock 59.9Hz 1280x800 (0x57) 83.5MHz -HSync +VSync h: width 1280 start 1352 end 1480 total 1680 skew 0 clock 49.7KHz v: height 800 start 803 end 809 total 831 clock 59.8Hz 1280x720 (0x58) 74.5MHz -HSync +VSync h: width 1280 start 1344 end 1472 total 1664 skew 0 clock 44.8KHz v: height 720 start 723 end 728 total 748 clock 59.9Hz 1152x768 (0x59) 71.8MHz -HSync +VSync h: width 1152 start 1216 end 1328 total 1504 skew 0 clock 47.7KHz v: height 768 start 771 end 781 total 798 clock 59.8Hz 1024x768 (0x5a) 63.5MHz -HSync +VSync h: width 1024 start 1072 end 1176 total 1328 skew 0 clock 47.8KHz v: height 768 start 771 end 775 total 798 clock 59.9Hz 800x600 (0x5b) 38.2MHz -HSync +VSync h: width 800 start 832 end 912 total 1024 skew 0 clock 37.4KHz v: height 600 start 603 end 607 total 624 clock 59.9Hz 848x480 (0x5c) 31.5MHz -HSync +VSync h: width 848 start 872 end 952 total 1056 skew 0 clock 29.8KHz v: height 480 start 483 end 493 total 500 clock 59.7Hz 720x480 (0x5d) 26.8MHz -HSync +VSync h: width 720 start 744 end 808 total 896 skew 0 clock 29.9KHz v: height 480 start 483 end 493 total 500 clock 59.7Hz 640x480 (0x5e) 23.8MHz -HSync +VSync h: width 640 start 664 end 720 total 800 skew 0 clock 29.7KHz v: height 480 start 483 end 487 total 500 clock 59.4Hz S-video disconnected (normal left inverted right x axis y axis) Identifier: 0x53 Timestamp: 39292 Subpixel: no subpixels Clones: CRTCs: 0 1 Transform: 1.000000 0.000000 0.000000 0.000000 1.000000 0.000000 0.000000 0.000000 1.000000 filter: tv standard: ntsc supported: ntsc, pal, pal-m, pal-60, ntsc-j, scart-pal, pal-cn, secam load detection: 1 range: (0, 1) And the same /sys/class/backlight entries are present: $ l1 /sys/class/backlight/ acpi_video0 radeon_bl0 What do we need to test in X to find out where it is broken? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c16 --- Comment #16 from David Rankin 2014-07-28 19:14:52 UTC --- Oh No! Why in the world would radeon drop backlight support? Does radeonHD exists any longer and is there a build for 13.1 that could be tested? I hate when stuff like this just disappears... Do you know if there is a radeon build flag that can be enabled to provide the traditional backlight? Desktop: I use kde3 (repositories/KDE:/KDE3/openSUSE_13.1/) It has the old Xrandr support. If we can determine exactly what is needed, we can push a patch to kde3 going forward (to both openSuSE kde3 and TDE [the Trinity project]) Oh yes, the move was known to be painful -- that is why it was put off until absolutely necessary (dying HD was the 'absolutely necessary' trigger). I'm very familiar with HAL going away. I have built TDE for Archlinux for the past several years and have been in the middle of updating the desktop to build with the '--no-hal' option :) Just wait until console-kit goes away.... OK, so we know the issue here is radeon dropping backlight support is the cause of my backlight problem. The question becomes "What is the best way to fix this in 13.1 so that backlight control works?" From what I understand, the options are: (1) (if possible) enable backlight control in the radeon X11 driver build; (2) (if exists) install/test radeonHD X11 driver; or (3) patch the desktop software so that backlight control now resides in the desktop and not the X11 driver. Of those options, option (3) makes the least sense. Backlight control would still be broken in runlevel 3 and it would be broken for *every* desktop that isn't specifically patched to take over backlight control. Bad solution. So when I launch fluxbox or WindowMaker I would be back to square 1. What can be done to get backlight control working again in the radeon X11 driver? Surely they didn't drop the backlight control code from the driver. Can it be enabled again? If not, why not? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c18 --- Comment #18 from David Rankin 2014-07-28 21:53:10 UTC --- Created an attachment (id=600129) --> (http://bugzilla.novell.com/attachment.cgi?id=600129) Screen Brightness Script Used to Control Backlight Takashi, As a workaround, I wrote a script to incrementally increase/decrease the backlight. In KDE3, I simply created 2 menu entries 'Backlight Control Increase' and assigned the shortcut 'screenbrightness.sh -i' to the XF86MonBrightnessUp key and a similar entry 'Backlight Control Decrease' and assigned the shortcut 'screenbrightness.sh -i' to the XF86MonBrightnessDown key. (uncheck Enable Launch Feedback on each entry) This is functional as a work around, but is not a fix. We need to get the kernel/X11 driver fixed so it is not a desktop-by-desktop kludge... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c20 --- Comment #20 from Takashi Iwai 2014-07-29 09:12:20 UTC --- IIRC, radeon X11 driver never supported Xrandr backlight, so far. So, the lack of xrandr backlight support in radeon driver itself is no regression. And, the kernel doesn't drop the support, either. It keeps the same functionality. This is also no regression. That said, the regression is rather the whole framework change between years ago and now. There is no easy solution for this. The real fix would be either: - Enhance KDE to control over /sys/class/backlight/*, or - Enhance radeon X11 driver to add Xrandr backlight control. And, in addition, we need to fix radeon KMS to handle the backlight of your laptop properly. (BTW the reference in comment 17 is irrelevant from your problem.) If it had been reported a few years ago at the time HAL was dropped, we could handle a bit more easily. But I don't think this will be ever fixed, especially because it's specific to a certain old machine. Despite the difficult "solution", we can think of a "workaround". The workaround you put in comment 18 is similar as what I wanted to suggest. (I thought of a helper daemon invoked by a systemd unit file at boot, instead.) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=887629 https://bugzilla.novell.com/show_bug.cgi?id=887629#c22 --- Comment #22 from Takashi Iwai 2014-07-30 05:46:17 UTC --- I don't want to give a long history course on Bugzilla, but let me write down briefly what have happened between openSUSE 11.4 and nowadays: - Years ago (it's literally *old* in the world of PC), the desktop could use two ways to control the backlight: one is over Xrandr and another is over HAL. Most of desktops takes the latter as fallback. - More years ago, the ACPI video driver changed directly the brightness via ACPI key event. This was dropped because it interferes the action done by desktop; the backlight control is a role of desktop environment, and desktop needs to take the full control. - *X11* radeon driver (not kernel) hasn't (and still doesn't) supported backlight control, although the *kernel* radeon driver supports and provides the interface for native backlight control via sysfs. Thus, there has been no Xrandr backlight control on your machine ever. - Because of the above, old desktops deployed HAL for controlling the backlight. And HAL managed both ACPI and native backlight controls, eventually this worked. - HAL was dropped after some time because no one could / want maintain it. Since then, some desktops (e.g. GNOME) took another approach for backlight control, namely by accessing directly backlight sysfs. Meanwhile some desktops remain and rely on only Xrandr backlight control. We're at this point. You're using desktops of the latter type, so the backlight control doesn't work on it. Did you try GNOME? This would work on your machine even now. If this doesn't work, the problem is in the kernel. We can report to the upstream for fixing the native backlight control of kernel radeon driver. But, the fact it doesn't work on KDE is due to the missing feature, as explained in the above. For really fixing the problem, either X11 radeon needs to be enhanced to provide Xrandr backlight, or KDE needs to be enhanced to control over sysfs like GNOME. -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=887629 http://bugzilla.novell.com/show_bug.cgi?id=887629#c24 Jiri Slaby changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby@suse.com Resolution|--- |UPSTREAM --- Comment #24 from Jiri Slaby --- bfo would be the best place: https://bugs.freedesktop.org/enter_bug.cgi?product=xorg Use driver/radeon in there. -- You are receiving this mail because: You are on the CC list for the bug.