Bug 493441 - rage128 uses 800x600 resolution for LCD panel with 1024x768 native resolution
Summary: rage128 uses 800x600 resolution for LCD panel with 1024x768 native resolution
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-r128
Version: 18
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 532842 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-01 18:58 UTC by John Reiser
Modified: 2018-04-11 19:16 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:38:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.0.log (33.10 KB, text/plain)
2009-04-01 18:58 UTC, John Reiser
no flags Details
/var/log/Xorg.0.log (28.52 KB, text/plain)
2009-09-09 15:23 UTC, John Reiser
no flags Details
/var/log/Xorg.0.log (28.45 KB, text/plain)
2009-09-15 20:41 UTC, John Reiser
no flags Details
Xorg.0.log of vesa only (no r128) (48.76 KB, text/plain)
2009-09-16 17:19 UTC, John Reiser
no flags Details
Xorg.0.log (28.03 KB, text/plain)
2009-09-20 14:17 UTC, John Reiser
no flags Details
Xorg.0.log using explicit /etc/X11/xorg.conf (25.26 KB, text/plain)
2009-11-18 04:00 UTC, John Reiser
no flags Details
Xorg.0.log with no xorg.conf (28.02 KB, text/plain)
2009-11-18 04:07 UTC, John Reiser
no flags Details
Xorg.0.log from Fedora 17 (79.72 KB, text/plain)
2012-09-05 00:19 UTC, John Reiser
no flags Details
X.log during install of Fedora 18-Alpha-TC5 (32.81 KB, text/plain)
2012-09-05 00:23 UTC, John Reiser
no flags Details

Description John Reiser 2009-04-01 18:58:56 UTC
Created attachment 337615 [details]
Xorg.0.log

Description of problem: Radeon driver chooses 800x600 as the resolution for an LCD panel whose native resolution is 1024x768.


Version-Release number of selected component (if applicable):
fedora-livecd-testday-20090331-i386
xorg-x11-server 1.6.0-16.fc11

How reproducible: always


Steps to Reproduce:
1. boot livecd for Radeon test day: fedora-livecd-testday-20090331-i386
2.
3.
  
Actual results: X11 display resolution is 800x600, which is less than the native panel resolution.


Expected results: X11 display resolution is 1024x768, which is the native panel resolution.


Additional info: xrandr reports:
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600        60.0*    56.0
   640x480        60.0  

Particularly relevant lines of Xorg.0.log are:
(--) R128(0): Chipset: "ATI Rage 128 Mobility M3 LF (AGP)" (ChipID = 0x4c46)
(--) R128(0): Linear framebuffer at 0xf8000000
(--) R128(0): MMIO registers at 0xfdffc000
(--) R128(0): VideoRAM: 8192 kByte (128-bit SDR SGRAM 1:1)
(**) R128(0): Using flat panel for display
(II) R128(0): Primary Display == Type 2
(II) R128(0): Panel size: 1024x768          <<<<<<<<<< HERE <<<<<<<<<<
(II) R128(0): Panel ID: IBM ITXG76E2
(II) R128(0): Panel Type: Color, Single, TFT
(II) R128(0): Panel Interface: LVDS
(II) R128(0): PLL parameters: rf=2700 rd=12 min=12000 max=27000; xclk=10500

lspci says:
01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02)
01:00.0 0300: 1002:4c46 (rev 02)

There is a VGA port for an external display (which I have used at 1024x768; it always is a clone of the main display) but there was nothing connected to the external port in this test.  Microsoft Windows ME runs the panel at its native 1024x768.  Fedora 10 also chooses only 800x600.  Fedora 9 ran at 1024x768 because there was a configuration file where I could increase the HorizFreq (to 57.0 KHz, if I recall.)

Comment 1 Bug Zapper 2009-06-09 13:00:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 John Reiser 2009-09-09 15:20:57 UTC
The problem still occurs using
  xorg-x11-drv-ati-6.13.0-0.3.20090908git651fe5a47.fc12.i686
  xorg-x11-server-Xorg-1.6.99.900-1.fc12.i686
  kernel-2.6.31-0.212.rc9.git1.fc12.i686
from the testday-20090908-i686 live CD during Fedora 12 Alpha.

It's especially irritating that System > Preferences > Display won't let me change the resolution to 1024x768 @ 60Hz which I am absolutely certain that this LCD panel can handle.

Comment 3 John Reiser 2009-09-09 15:23:02 UTC
Created attachment 360253 [details]
/var/log/Xorg.0.log

Current Xorg.0.log

Comment 4 Adam Jackson 2009-09-15 19:39:55 UTC
Could you try running vesa on this hardware?  I'd like to see whether it can a) do DDC reliably, b) gets a PanelID response.

Comment 5 John Reiser 2009-09-15 20:41:52 UTC
Created attachment 361136 [details]
/var/log/Xorg.0.log

Booting F12-Snap2-i686-Live on this machine, but with "xdriver=vesa" replacing "quiet rhgb" on the kernel boot command line, still gives 800x600, with 640x480 as the only other choice.  Attached is the complete Xorg.0.log.

I see:
   (II) R128(0): Panel size: 1024x768
and also:
   (II) Loading sub module "ddc"
   (II) LoadModule: "ddc"
   (II) Module "ddc" already built-in
   (II) R128(0): VESA VBE DDC supported
   (II) R128(0): VESA VBE DDC Level none
   (II) R128(0): VESA VBE DDC transfer in appr. 2 sec.
   (II) R128(0): VESA VBE DDC read failed
so DDC does not work there, but the panel still is 1024x768.

Comment 6 Adam Jackson 2009-09-16 14:44:32 UTC
xdriver=vesa is an anaconda option, not an X option.  You'll need to actually write an X config file (or, move the r128 driver file out of the way so we don't load it).

Comment 7 John Reiser 2009-09-16 17:19:03 UTC
Created attachment 361329 [details]
Xorg.0.log of vesa only (no r128)

I booted F12-Snap2-i686-Live with additional parameter " 3" to get multi-user but no X11.  Then I logged in as root, and moved these drivers out of the way:
   /lib/modules/2.6.31-2.fc12.i686/kernel/drivers/gpu/drm/r128/r128.ko.SAVE
   /usr/lib/xorg/modules/drivers/r128_drv.so.SAVE

Then I invoked "startx".  "xrandr" shows:
-----
Screen 0: minimum 800 x 600, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768        0.0* 
   800x600        61.0  
-----
So that part worked!  Perhaps a little too well, because 640x480 is not an option.

In the Xorg.0.log I see that loading module r128 failed (as expected because I moved it away), loading module vesa succeeded, DDC read failed, and VBE PanelID read successfully:
-----
(II) LoadModule: "r128"
(WW) Warning, couldn't open module r128
(II) UnloadModule: "r128"
(EE) Failed to load module "r128" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
        compiled for 1.6.99.1, module version = 2.2.1
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
   <<snip>>
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 2.0
(II) VESA(0): VESA VBE Total Mem: 8192 kB
(II) VESA(0): VESA VBE OEM: ATI MOBILE M3
(II) VESA(0): VESA VBE OEM Software Rev: 1.0
(II) VESA(0): VESA VBE OEM Vendor: ATI Technologies Inc.
(II) VESA(0): VESA VBE OEM Product: M3 
(II) VESA(0): VESA VBE OEM Product Rev: 01.00
(II) VESA(0): Creating default Display subsection in Screen section
        "Builtin Default vesa Screen 0" for depth/fbbpp 24/32
(==) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level none
(II) VESA(0): VESA VBE DDC transfer in appr. 2 sec.
(II) VESA(0): VESA VBE DDC read failed
(II) VESA(0): VESA VBE PanelID read successfully
(II) VESA(0): PanelID returned panel resolution 1024x768
-----

Comment 8 Adam Jackson 2009-09-18 20:58:53 UTC
Try xorg-x11-drv-r128-6.8.1-2.fc12 in tomorrow's rawhide, it has a patch to adjust sync ranges based on the panel info.

Comment 9 John Reiser 2009-09-20 14:17:39 UTC
Created attachment 361823 [details]
Xorg.0.log

I still get 800x600 instead of 1024x768.
  xorg-x11-drv-r128-6.8.1-2.fc12.i686
  kernel-PAE-2.6.31-33.fc12.i686

$ xrandr
Screen 0: minimum 640 x 480, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
   800x600        60.0*    56.0  
   640x480        60.0  
$ ls -l /usr/lib/xorg/modules/drivers/r128_drv.so
-rwxr-xr-x. 1 root root 107428 2009-09-18 14:04 /usr/lib/xorg/modules/drivers/r128_drv.so
$ sum /usr/lib/xorg/modules/drivers/r128_drv.so
44155   105
$

Comment 10 Adam Williamson 2009-11-04 16:19:12 UTC
*** Bug 532842 has been marked as a duplicate of this bug. ***

Comment 11 Matěj Cepl 2009-11-05 17:12:44 UTC
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).

Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.

If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]

Comment 12 John Reiser 2009-11-05 19:14:22 UTC
The problem persists with today's rawhide for Fedora 12 (same day as Release Candidate is scheduled to be composed):
  kernel-PAE-2.6.31.5-117.fc12.i686
  xorg-x11-drv-r128-6.8.1-2.fc12.i686
  xorg-x11-server-Xorg-1.7.1-6.fc12.i686
  xorg-x11-server-common-1.7.1-6.fc12.i686
My 1024x768 LCD notebook panel gets 800x600.

Excerpts from /var/log/Xorg.0.log:
=====
Build Date: 04 November 2009  04:35:42PM
Build ID: xorg-x11-server 1.7.1-6.fc12

(II) LoadModule: "ati"
(II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
(II) Module ati: vendor="X.Org Foundation"
        compiled for 1.7.0, module version = 6.12.99
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "r128"
(II) Loading /usr/lib/xorg/modules/drivers/r128_drv.so
(II) Module r128: vendor="X.Org Foundation"
        compiled for 1.6.99.901, module version = 6.8.1
        Module class: X.Org Video Driver
        ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
        compiled for 1.6.99.1, module version = 2.2.1
        Module class: X.Org Video Driver
        lass: X.Org Video Driver, version 6.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
(II) Module fbdev: vendor="X.Org Foundation"
        compiled for 1.6.99.1, module version = 0.4.1
        ABI class: X.Org Video Driver, version 6.0

(II) VESA: driver for VESA chipsets: vesa
(II) FBDEV: driver for framebuffer: fbdev
(II) Primary Device is: PCI 01@00:00:0
(WW) Falling back to old probe method for vesa
(WW) Falling back to old probe method for fbdev
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
        compiled for 1.7.1, module version = 0.0.2
        ABI class: X.Org Video Driver, version 6.0

(II) R128(0): initializing int10
(II) R128(0): Primary V_BIOS segment is: 0xc000
(--) R128(0): Chipset: "ATI Rage 128 Mobility M3 LF (AGP)" (ChipID = 0x4c46)
(--) R128(0): Linear framebuffer at 0xf8000000
(--) R128(0): MMIO registers at 0xfdffc000
(--) R128(0): VideoRAM: 8192 kByte (128-bit SDR SGRAM 1:1)
(**) R128(0): Using flat panel for display
(II) R128(0): Primary Display == Type 2
(II) R128(0): Panel size: 1024x768            ***** the real resolution *****
(II) R128(0): Panel ID: IBM ITXG76E2
(II) R128(0): Panel Type: Color, Single, TFT
(II) R128(0): Panel Interface: LVDS
(II) R128(0): PLL parameters: rf=2700 rd=12 min=12000 max=27000; xclk=10500
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"

(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) R128(0): VESA VBE DDC supported
(II) R128(0): VESA VBE DDC Level none
(II) R128(0): VESA VBE DDC transfer in appr. 2 sec.
(II) R128(0): VESA VBE DDC read failed
(==) R128(0): Using gamma correction (1.0, 1.0, 1.0)
(II) R128(0): <default monitor>: Using hsync range of 31.50-47.30 kHz
(II) R128(0): <default monitor>: Using vrefresh range of 56.00-59.87 Hz


In my opinion the vrefresh should include 60.0Hz (not just 59.87) and the hsync should include 59KHz (not just 47.3); then I would get 1024x768.

Comment 13 Robert G. 'Doc' Savage 2009-11-05 19:50:36 UTC
I agree with John Reiser. Two days ago I posted bug 532842, which Adam Williamson just marked as a dupe to this bug. In my bug a ThinkPad A22p's 1600x1200 LCD screen can only be set to a maximum resolution of 1280x1024 using the r128 driver, and then only after the initial installation. If I use the native r128 driver during installation, the right side of the 800x600 window in the center of the display is torn and folded (bad mode lines?). After initial installation the 1280x1024 video suffers from similar tearing on the right side.

Comment 14 Robert G. 'Doc' Savage 2009-11-05 19:52:26 UTC
I agree with John Reiser. Two days ago I posted bug 532842, which Adam Williamson just marked as a dupe to this bug. In my bug a ThinkPad A22p's 1600x1200 LCD screen can only be set to a maximum resolution of 1280x1024 using the r128 driver, and then only after the initial installation. If I use the native r128 driver during installation, the right side of the 800x600 window in the center of the display is torn and folded (bad mode lines?). After initial installation the 1280x1024 video suffers from similar tearing on the right side.

Comment 15 Bug Zapper 2009-11-16 09:53:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 John Reiser 2009-11-18 04:00:31 UTC
Created attachment 370003 [details]
Xorg.0.log using explicit /etc/X11/xorg.conf

An explicit xorg.conf does not override the internal 800x600; my "HorizSync 24.0 - 65.0" is squashed to "31.50-47.30 kHz".  Thus I cannot get 1024x768 *at ll*.  Time to revert to Fedora 11, where at least 1024x768 was obtainable via xorg.conf.

Failing Fedora 12 modules:
xorg-x11-drv-r128-6.8.1-2.fc12.i686
xorg-x11-server-Xorg-1.7.1-7.fc12.i686
kernel-PAE-2.6.31.5-127.fc12.i686

The /etc/X11/xorg.conf is:
-----Section "Monitor"
	Identifier "lvdsPanel"
	HorizSync  24.0 - 65.0
	VertRefresh 49.0 - 73.0
EndSection

Section "Screen"
	Identifier "Screen0"
	Monitor "lvdsPanel"
	DefaultDepth 24
	SubSection "Display"
		Viewport 0 0
		Depth 24
		Modes "1024x768"
	EndSubSection
EndSection
-----

Comment 17 John Reiser 2009-11-18 04:07:31 UTC
Created attachment 370006 [details]
Xorg.0.log with no xorg.conf

This is the Xorg.0.log from Fedora 12 with no /etc/X11/xorg.conf (no attempt to override the internal builtin configuration rules.)  Still gives only 800x600 on a 1024x768 panel.

Comment 18 Dan Campbell 2009-12-12 02:30:34 UTC
I think the issue may have to do with the calculation for horizontal sync.  Not an expert or understand in depth the xorg code, but typically you need to provide an overscan amount.  7.5% per side is a gratuitous figure, but typical.

The following patch works fine on the Dell Latitude C600 I have (with or without and xorg.conf file).  Hope it helps.

[danc@localhost rpmbuild]$ diff -Naur SOURCES/r128-6.8.1-panel-hack.patch.orig SOURCES/r128-6.8.1-panel-hack.patch
--- SOURCES/r128-6.8.1-panel-hack.patch.orig	2009-12-10 19:31:05.708433955 -0700
+++ SOURCES/r128-6.8.1-panel-hack.patch	2009-12-11 18:04:08.522680718 -0700
@@ -13,7 +13,7 @@
 +	    pScrn->monitor->nHsync = 1;
 +	    pScrn->monitor->hsync[0].lo = 31.5;
 +	    pScrn->monitor->hsync[0].hi =
-+		(float)mode->Clock / (float)mode->HTotal;
++		(float)mode->Clock / (float)mode->HTotal * 1.15;
 +	    pScrn->monitor->nVrefresh = 1;
 +	    pScrn->monitor->vrefresh[0].lo = 56.0;
 +	    pScrn->monitor->vrefresh[0].hi =
[danc@localhost rpmbuild]$

Comment 19 Adam Jackson 2010-11-01 15:42:24 UTC
The mode filtering code already has slop for this.  The bug was using the CVT-R formula instead of plain CVT.  Should be fixed in rawhide.

Comment 20 Dan Campbell 2011-01-20 03:01:45 UTC
(In reply to comment #19)
> The mode filtering code already has slop for this.  The bug was using the CVT-R
> formula instead of plain CVT.  Should be fixed in rawhide.

Sorry, but still does not correct issue.  Using xorg-x11-drv-r128-6.8.1-7.fc15.src.rpm from rawhide still will only provide 800x600 resolution on a Dell C600.

Comment 21 John Reiser 2012-09-05 00:16:17 UTC
This problem re-appears in the anaconda installer 18.6.4 for Fedora 18-Alpha-TC5, using only 800x600 for a panel with native 1024x768 [the same physical panel as this original bug.]  It's a regression from Fedora 17, which did use 1024x768.

  good: xorg-x11-server-Xorg-1.12.3-1.fc17.x86_64
        xorg-x11-drv-ati-6.14.4-6.20120602git930760942.fc17.x86_64

   bad: X.Org X Server 1.12.99.904 (1.13.0 RC 4)
        ati_drv.so   compiled for 1.12.99.902, module version = 6.99.99

I will attach the X log from both cases.

Comment 22 John Reiser 2012-09-05 00:19:54 UTC
Created attachment 609816 [details]
Xorg.0.log from Fedora 17

Running Fedora 17, correctly detects 1024x768 panel:

[    31.367] (II) Loading sub module "ddc"
[    31.367] (II) LoadModule: "ddc"
[    31.367] (II) Module "ddc" already built-in
[    31.397] (II) VESA(0): VESA VBE DDC supported
[    31.397] (II) VESA(0): VESA VBE DDC Level none
[    31.397] (II) VESA(0): VESA VBE DDC transfer in appr. 2 sec.
[    31.488] (II) VESA(0): VESA VBE DDC read failed
[    31.489] (II) VESA(0): VESA VBE PanelID read successfully
[    31.489] (II) VESA(0): PanelID returned panel resolution 1024x768

Comment 23 John Reiser 2012-09-05 00:23:35 UTC
Created attachment 609817 [details]
X.log during install of Fedora 18-Alpha-TC5

Running anaconda-18.6.4, Fedora 18-Alpha-TC5:

[   209.679] (II) Loading sub module "ddc"
[   209.679] (II) LoadModule: "ddc"
[   209.679] (II) Module "ddc" already built-in
[   209.683] (II) R128(0): VESA VBE DDC supported
[   209.683] (II) R128(0): VESA VBE DDC Level none
[   209.688] (II) R128(0): VESA VBE DDC transfer in appr. 2 sec.
[   209.704] (II) R128(0): VESA VBE DDC read failed
[   209.704] (==) R128(0): Using gamma correction (1.0, 1.0, 1.0)
[   209.704] (II) R128(0): <default monitor>: Using hsync range of 31.50-47.82 kHz
[   209.704] (II) R128(0): <default monitor>: Using vrefresh range of 56.00-59.92 Hz
[   209.705] (WW) R128(0): Unable to estimate virtual size
[   209.705] (II) R128(0): Clock range:  12.00 to 270.00 MHz
   [snip]
[   209.707] (II) R128(0): Not using default mode "1024x768" (hsync out of range)
   [snip]
[   209.713] (--) R128(0): Virtual size is 800x600 (pitch 800)
[   209.713] (**) R128(0): *Default mode "800x600": 65.0 MHz (scaled from 40.0 MHz), 37.9 kHz, 60.3 Hz

Comment 24 Fedora End Of Life 2013-12-21 14:51:31 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 25 Fedora End Of Life 2014-02-05 22:38:41 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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