[i815] Wrong resolution on Vaio PCG-SRX51, PCG-SRX41 and PCG-FX370 due to incorrect h/v rates

Bug #288807 reported by Alexander Muon
58
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Wishlist
Unassigned
xserver-xorg-video-intel (Ubuntu)
Invalid
Wishlist
Unassigned

Bug Description

[Problem]
Resolutions are incorrect on several Sony Vaio laptops because their display panels do not support DDC, and thus is not properly communicating its horizontal and vertical sync rate capabilities to the driver.

[Discussion]
Prior to Hardy, xorg.conf's required having the HorizSync and VertRefresh settings explicitly specified in the xorg.conf; Hardy's xserver gained the capability to detect these settings from the monitor itself using DDC reads, and thus the installation scripts were modified to not list these two pieces of data. However, the Vaio PCG-SRX51 does not correctly communicate these values, so users started seeing problems in Hardy. This can be seen in Xorg.0.log files from the following error:

    (II) intel(0): VESA VBE DDC read failed

The HorizSync and VertRefresh values are employed in the calculation of valid modelines (i.e. resolutions), so a consequence of this problem is that users were not able to load all the resolutions that the hardware is capable of doing. (Bad sync rates can cause other glitches, but the resolution issue is the most noticeable problem). The Xorg.0.log shows a stream of "Not using default mode ..." and falling all the way down to an 800x600 resolution.

An example set of files from experiencing this behavior are seen here:
http://launchpadlibrarian.net/19497368/i8xx-resolution-bug-report

Running get-edid | parse-edid indicates that the hardware doesn't support DDC at all:

 Monitor and video card combination does not support DDC1 transfers
 Monitor and video card combination does not support DDC2 transfers

[Proposed Solution]
Unfortunately since neither DDC nor EDID works, that poses a considerable constraint for automatic detection. However, perhaps it could be quirked based on both the hostbridge and video chip:

00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 02)
 Subsystem: Compaq Computer Corporation Device [0e11:001a]

Unfortunately neither -intel nor the xserver has infrastructure in place for synthetically setting DDC info this way. It may be worthwhile establishing an infrastructure if there is additional hardware that needs to be similarly quirked.

One approach could be to introduce a check in i810_driver.c in I810DoDDC() of the return from vbeDoEDID; if it is NULL, then if the PCI's match the above, generate a synthetic MonInfo structure with appropriate h/v sync values and so on. This approach would also let us hardcode the vendor and twiddle other monitor details.

Alternatively, a possibly simpler approach could be to modify the handling of undefined h/v sync rates inside xf86ValidateModes() in the xserver. Instead of just defaulting to 31.5-37.9 / 50-70, it could do a check of the chip and hostbridge, and if it matches a quirked one, use that for the h/v sync rates. This approach would have the advantage of being usable across all drivers.

[Workaround]
Make your xorg.conf look like this:

Section "Device"
        Identifier "Configured Video Device"
        Driver "intel"
EndSection

Section "Monitor"
        Identifier "Configured Monitor"
        HorizSync 31.5-48.5
        VertRefresh 40-70
        Option "dpms"
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Configured Monitor"
        Device "Configured Video Device"
        DefaultDepth 16
        Option "Accel"
        SubSection "Display"
                Depth 16
                Modes "1024x768"
        EndSubSection
        SubSection "Display"
                Depth 24
                Modes "1024x768"
        EndSubSection
EndSection

this is thanks denvergeek on the Ubuntu forums:
http://ubuntuforums.org/showthread.php?t=972062&highlight=8.10+ibex+screen+resolution&page=2

[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 Chipset Graphics Controller (CGC) [8086:1132] (rev 11)
 Subsystem: Sony Corporation Device [104d:80df]

[Original Report]
ubuntu intrepid,
limited to 800x600, 640x480,
should have detected 1024x768

Update: X can't read DDC info from the monitor:
(II) intel(0): VESA VBE DDC read failed

Revision history for this message
Alexander Muon (webthrower000) wrote :
Geir Ove Myhr (gomyhr)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote : Re: [i815] screen resolution not detected

Thank you for including your Xorg.0.log. Please also attach the following:
* Output from `lspci -vvnn`
* Output from `xrandr --verbose`
* Output from `get-edid | parse-edid` (you'll need the read-edid package for this)

Changed in xserver-xorg-video-intel:
status: New → Incomplete
Revision history for this message
no2nonFree (agnesarts) wrote :

OK ... I have similar / probably same issue ... the old laptop in question is a Sony Vaio PCG-FX103

my card I guess from giving 'lshw -C display' ...

root@vaio:/home/no2nonFree# lshw -C display
  *-display UNCLAIMED
       description: VGA compatible controller
       product: 82815 Chipset Graphics Controller (CGC)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 11
       width: 32 bits
       clock: 66MHz
       capabilities: pm bus_master cap_list
       configuration: latency=0

... is i815 (or atleast i8xx)

I attach (all in one file delimited by dashes ie: '---' )
1) Xorg.0.log
2) Output from `lspci -vvnn`
3) Output from `xrandr --verbose`
4) Output from `get-edid | parse-edid`

The file is called "i8xx-resolution-bug-report" (39.819 K)

I have attempted to change few configurations and tools like 'xrandr' to fix the problem in its initial stages ... but don't think any settings are affected due to my earlier attempts. All the best.

Revision history for this message
Alexander Muon (webthrower000) wrote :

requested information:

Revision history for this message
Alexander Muon (webthrower000) wrote :
Revision history for this message
Alexander Muon (webthrower000) wrote :
Revision history for this message
jaypmcwilliams (jaypmcwilliams) wrote :

OK, I found a way around the video not detecting the 1024x768 resolution. currently only went up to 800x600. Now goes to 1024x768. It's a pain, but here's how; Install Ubuntu 7.10/Gutsy. Then change the monitor in DisplayConfig to "Generic" "LCD 1024x768". Restart Computer. Then go to /etc/X11 & copy the RGB & xorg.conf files to a USB drive. Install Ubuntu 8.10/Intrepid. Then install Guidance Backend then install displayconfig. use the ROOT nautilus & copy the RGB & xorg.conf files from the USB to the /etc/X11. Restart the computer & it should automatically recognize & stretch the display to the 1024x768. I really don't think you even need those packages installed. I currently have a SONY VAIO R505 with Intel video PIII. If you need more details, pls let me know. JayPMcWilliams

Revision history for this message
jaypmcwilliams (jaypmcwilliams) wrote :

OK, I found a way around the video not detecting the 1024x768 resolution. currently only went up to 800x600. Now goes to 1024x768. It's a pain, but here's how; Install Ubuntu 7.10/Gutsy. Then change the monitor in DisplayConfig to "Generic" "LCD 1024x768". Restart Computer. Then go to /etc/X11 & copy the RGB & xorg.conf files to a USB drive. Install Ubuntu 8.10/Intrepid. Then install Guidance Backend then install displayconfig. use the ROOT nautilus & copy the RGB & xorg.conf files from the USB to the /etc/X11. Restart the computer & it should automatically recognize & stretch the display to the 1024x768. I really don't think you even need those packages installed. I currently have a SONY VAIO R505 with Intel video PIII. If you need more details, pls let me know. JayPMcWilliams

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
status: Incomplete → Confirmed
Revision history for this message
Alexander Muon (webthrower000) wrote :

I've been using my old xorg.conf ever since Gutsy to address this issue. I'm concerned about how this will effect a new users perception of linux, since most will experience it through the live cd initially.

Bryce Harrington (bryce)
description: updated
Changed in xserver-xorg-video-intel:
importance: Undecided → High
status: Confirmed → Triaged
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

I've updated the description with my analysis of the problem. Basically, some of the old Sony Vaio laptops have braindead display panels, so X is picking default h/v sync rates which unfortunately are too limited, so the laptop ends up with reduced available resolutions.

There isn't a simple way to fix this, since it's really hardware brokenness here. I can see a couple not-so-simple ways to fix it. Unfortunately, in a cursory scan through launchpad, I'm not spotting much hardware beyond the Sony Vaio that have this particular problem, so am not sure it's going to be worth the effort. But I'll keep an eye out, who knows. Meanwhile, Sony Vaio owners with this bug will need to edit their xorg.conf and put in the workaround listed in the description.

Revision history for this message
demikid (kenmaina) wrote :

I cant get correct screen resolution(1280x1024) in Ubuntu 8.10.
This monitor and video card setup works perfectly in Ubuntu 8.04.
My monitor id Dell E177fp

H: 31-80

V: 56-75

$lspci -vvnn

Intel Corporation 82945G/GZ Integrated Graphics Controller

$cat /etc/lsb-release

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=8.10

DISTRIB_CODENAME=intrepid

DISTRIB_DESCRIPTION="Ubuntu 8.10"

$uname -a

Linux demichild 2.6.28-4-generic #11-Ubuntu SMP Fri Jan 16 21:57:57 UTC 2009 i686 GNU/Linux

$ddcprobe

vbe: VESA 3.0 detected.

oem: Intel(r) 82945G Chipset Family Graphics Chip Accelerated VGA BIOS

vendor: Intel Corporation

product: Intel(r) 82945G Chipset Family Graphics Controller Hardware Version 0.0

memory: 7872kb

mode: 1280x1024x256

mode: 1280x1024x64k

mode: 1280x1024x16m

mode: 1024x768x256

mode: 1024x768x64k

mode: 1024x768x16m

mode: 640x480x16m

mode: 800x600x64k

mode: 800x600x16m

mode: 640x480x256

mode: 800x600x256

mode: 640x480x64k

edid:

edidfail

$ xrandr

Screen 0: minimum 320 x 200, current 1152 x 864, maximum 1360 x 1360

VGA connected 1152x864+0+0 (normal left inverted right x axis y axis) 0mm x 0mm

   1360x768 59.8

   1152x864 60.0*

   1024x768 60.0

   800x600 60.3

   640x480 59.9

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
importance: High → Wishlist
Revision history for this message
TJ (tj) wrote :

Today I found that an update to the Jaunty packages changed something subtle and the previously working xorg.conf settings were no longer effective. The symptom was the intel driver deciding it is possible to do 1360x768 on the 1024x768 monitor.

The intel driver also ignores monitor options "PreferredMode" "MaxClock" which meant the pixel clock rate of the monitor can't be specified, to prevent the incorrect mode.

I used the Windows tool, PowerStrip, (referenced from the Xorg FAQ at http://www.x.org/wiki/FAQVideoModes#head-82230a582646cbf28ac41dec2139732ee868e0d2). to get the ModeLine that works for Windows.

That didn't help either because the intel driver either ignores it or merges it with its own calculations.

The final solution was to add the "Virtual" size setting to "Display" SubSections of the "Screen" section.

Here's the resulting xorg.conf:

Section "Device"
        Identifier "Configured Video Device"
EndSection

Section "Monitor"
        Identifier "Sony Notebook Panel"
        # no EDID
        DisplaySize 210 158
        HorizSync 28-48.5
        VertRefresh 43-75
        Option "DPMS"
        # clock is in kHz
        Option "MinClock" "10000"
        Option "MaxClock" "65000"
        Option "PreferredMode" "1024x768"
        ModeLine "1024x768" 65.000 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
EndSection

Section "Screen"
        Identifier "Default Screen"
        Monitor "Sony Notebook Panel"
        Device "Configured Video Device"
        DefaultDepth 24
        SubSection "Display"
                Depth 24
                Virtual 1024 768
        EndSubSection
        SubSection "Display"
                Depth 16
                Virtual 1024 768
        EndSubSection
EndSection

Revision history for this message
Joel Goguen (jgoguen) wrote :

Looking at the attachments in this bug report, I noticed that two were flagged as a patch incorrectly. A patch contains changes to an Ubuntu package that will resolve a bug. Since this was not one I've unchecked the patch flag for it. In the future keep in mind the definition of a patch. You can learn more about what qualifies as a patch at https://wiki.ubuntu.com/Bugs/Patches. Thanks!

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Alexander,
     As you may be aware, the modesetting bits are now being handled in the kernel. AS such, I'd appreciate if you could test this against the latest build of Lucid and, if the behavior is still present, against the latest vanilla mainline build.

I'll be adding a kernel task to this bug and marking the xorg item invalid.

Thanks!

-JFo

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in xserver-xorg-video-intel (Ubuntu):
status: Triaged → Invalid
Changed in linux (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
TJ (tj) wrote :

Things are now much worse - I've attached a photo of the screen from a Lucid Xubuntu LiveCD.

1. Xorg thinks its running 800x600 but rendered area is only 640 wide so right-side of desktop is cut-off
2. Repeated artifacts between the bottom of the desktop and bottom of the LCD
3. Desktop not centred vertically on the LCD (unless you allow for the artifacts) as it was previously when in a lower-than-physical resolution

Revision history for this message
Surbhi Palande (csurbhi) wrote :

@TJ, can you attach the output of:
1) lspci -vvvnn

Revision history for this message
TJ (tj) wrote : Re: [Bug 288807] Re: [i815] Wrong resolution on Vaio PCG-SRX51, PCG-SRX41 and PCG-FX370 due to incorrect h/v rates

On Mon, 2010-03-01 at 15:31 +0000, Surbhi Palande wrote:
> @TJ, can you attach the output of:
> 1) lspci -vvvnn

This information is already attached to the bug report by Alexander.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

TJ,
      I think Surbhi wants to do a comparative analysis of the results from both of you, so your data would be most helpful.

Thanks!

~JFo

Revision history for this message
TJ (tj) wrote :

With Lucid Alpha 3 things have got worse. Xorg crashes each time the LiveCD "ubuntu" user tries to log-in, resulting in the user returning to the standard GDM log-in screen. Manual attempts to log-in result in the same Xorg crash and restart of GDM. There appear to be a lot of similar reports for installed alpha-3 too (#532183, #532173, #532047 ...).

Additionally, the tty consoles become invisible when doing a Ctrl+Alt+F1-F6 switch. The user can type blindly but sees nothing.

Using this 'facility' I was able to do "sudo apt-get update && sudo apt-get install openssh-server" and subsequently connect to the SRX51 from another PC using SSH (after a blind "sudo passwd ubuntu"). I pulled the contents of /var/log/ as a tgz archive and the ubuntu ".xsession-errors" log. The Xorg logs show input device errors but nothing definite on the reason for the crash, e.g:

(EE) PreInit returned NULL for ""Macintosh mouse button emulation""

From an apport.log entry it looks to be gnome-panel failing:

apport (pid 3302) Fri Mar 5 08:02:22 2010: wrote report /var/crash/_usr_bin_gnome-panel.999.crash

Until these issues are resolved it isn't possible to diagnose this screen resolution problem.

Revision history for this message
TJ (tj) wrote :

Relatively good news: testing with the 2010-03-04 LiveCD i386 Ubuntu image, after hitting bug #532530 "Segmentation fault at address (nil)" at the first log-in, and after stopping/restarting GDM, a Gnome session is started at 800x600. This doesn't scale to fill the 1024x768 screen but is centred on the LCD panel.

I then tried to test the xorg.conf used in the installed 9.10 configuration from the hard-drive, and given here in comment #12. That failed with an error reporting that DRI is not possible using colour-depth of 24 bits; only 16 bits is supported. Attempts to restart the xserver with 16-bit dept failed because the int10 code kept issuing a seg-fault!

With a fresh boot the Ubuntu LiveCD logged in automatically the first time but the screen is again offset, and I notice this time is missing the gnome-panel across the top. I'm attaching a photo of this.

Revision history for this message
TJ (tj) wrote :

I've just noticed, after switching to another VT and back, that the GUI is now centred on the LCD (not shifted to the top). Other than the positional change though, nothing else seems to have changed.

I'm attaching a tar.gz containing the kern.log, Xorg.0.log and .xsession-errors files for this session.

Revision history for this message
TJ (tj) wrote :

Things get curiouser!

I've just booted the Xubuntu LiveCD i386 (2010-03-04) image (via PXE/NFS as always). The initial desktop display has the same problem described and shown in comment #15. HOWEVER, after switching VT's to tty1 and back to tty7 the desktop display is complete, albeit still only 800x600 centred in the LCD.

Still not able to test the custom xorg.conf since restarting the xserver always causes bug #532579 "Segfault in libint10 when restarting xserver". Next step is to break out the squashfs of the liveCD image and add the custom xorg.conf there, to be able to move on with this particular issue regardless of the other bugs.

Revision history for this message
Russel Winder (russel) wrote :

I have just tried the Ubuntu Lucid nightly build of 2010-03-05 on my PCG-SRX51 in "Live CD Try Me" mode and although it came up 800x600 instead of 1280x768, it seemed to work fine. I am therefore taking the risk of doing a full clean install. More news soon . . .

Revision history for this message
TJ (tj) wrote :

On one of the SRX51's I took the plunge and did a "do-release-upgrade -d" to Lucid from a fully working Karmic Xubuntu.

Starting without that xorg.conf in place, Xorg starts with 800x600 shifted to the top of the LCD but a VT switch away and back brings it to the centre of the LCD.

The custom xorg.conf that worked with Karmic (detailed in comment #12) causes Xorg to fail on Lucid with the same reports as bug #532579 "Segfault in libint10 when restarting xserver".

Revision history for this message
Russel Winder (russel) wrote :

Install appears to have gone OK for me.

On boot the login (is it still GDM?) frame is at the top of the screen and snaller than 800x600. Try logging in and it fails, but the refreshed X puts a 800x600 login screen up. Loggin in again gives success, but at 800x600.

Apart from the screen problem, there appears to be a problem with the wifi. It appears to have detected a signal but cannot connect :-( Still that is for a different bug report.

All the virtual terminals seems to work for me. Actually apart from the screen size the weird initial behaviour after boot and the wifi, it all seems to be working.

Revision history for this message
TJ (tj) wrote :

I've solved bug #532579 "Segfault in libint10 when restarting xserver or using xorg.conf" - the vesa module is needed to check the VBE VESA settings.

This enhanced xorg.conf provides the workaround for full 1024x768 on Lucid:

----- /etc/X11/xorg.conf -----
Section "Module"
 Load "vesa"
EndSection

Section "Device"
 Identifier "Intel Corporation 82815 CGC"
 Driver "intel"
EndSection

Section "Monitor"
 Identifier "LCD Panel 1024x768"
 Option "DPMS"
 HorizSync 28-64
 VertRefresh 43-60
EndSection

Section "Screen"
 Identifier "Default Screen"
 Device "Intel Corporation 82815 CGC"
 Monitor "LCD Panel 1024x768"
 DefaultDepth 16
 SubSection "Display"
  Modes "1024x768"
 EndSubSection
EndSection

Section "ServerLayout"
 Identifier "Default Layout"
 Screen "Default Screen"
EndSection

Revision history for this message
Russel Winder (russel) wrote :

Rock on :-)

I didn't have an xorg.conf file so it was just doing all the default activity. Adding this xorg,conf means that once logged in I have 1024x768.

Interesting (!) after boot I still get an incorrect login frame and teh first login is rejected but then everything settles out. It is as though X is not working at all correctly and then on restart gets it right.

Revision history for this message
TJ (tj) wrote :

On Fri, 2010-03-05 at 20:00 +0000, Russel Winder wrote:
> Rock on :-)
>
> I didn't have an xorg.conf file so it was just doing all the default
> activity. Adding this xorg,conf means that once logged in I have
> 1024x768.
>
> Interesting (!) after boot I still get an incorrect login frame and teh
> first login is rejected but then everything settles out. It is as
> though X is not working at all correctly and then on restart gets it
> right.

Yes, I'm chasing that down via bug #532047 "Xorg crashed at first login
attempt".

Revision history for this message
TJ (tj) wrote :

On Fri, 2010-03-05 at 20:00 +0000, Russel Winder wrote:

> Interesting (!) after boot I still get an incorrect login frame and teh
> first login is rejected

This is caused by plymouth (the graphical splash). A workaround is
available in bug #532047.

The incorrect layout is, I think, also caused by plymouth because it
falls back to a text splash if KMS isn't available, and some of the
linux terminal control-codes it is writing to tty7 are failing/causing
unexpected results.

Revision history for this message
rajn (rjngrj2010) wrote :

Hi,
I have a Sony Vaio-PCG-FX220 and I am having screen resolution issues as described in this report (i.e., max 860x480). I tried with Xubuntu and Ubuntu (at different installs) all the above suggestions but none seem to work.

First I do not find xorg.conf. But I make a new file and place it in /etc/X11. The generated xorg.conf document has the same information as provided in the bug report [Workaround]. When I insert the document using sudo nano and save it and then quit the computer to restart it again, I am not logged in into Windows but instead into a tty1-6 terminals. I cannot renter tty7 term. I have to erase the xorg.conf file to re-enter the window. Am I doing something wrong in the xorg.conf parameters? I am a newbie (learnt about Ubuntu or other Linux distros last week) and have not yet figured out how to generate outputs to post it here. Moreover, I haven't yet tried to connect to the internet thinking to solve each issue in that order and then move to the next. I am writing this from a different computer.

I tried several other ways like xrandr --newmode and then adding by --addmode after getting information on h/v rates using gtf or ctv. But nothing works, at times the screen goes white and then says unrecognized crtc?. I also tried random h/v rates and for few I saw full screen lighting up but the screen was garbled with strips running across the whole screen. And when this happens, every time I have to reinstall Ubuntu. Therefore, it definitely looks like h/v rates are not being recognized properly.

Finally out of frustation, I decided to move to Mandriv. From several nights of googling (actually just a week), I figured out that this version had no issues with my type of computer. And yes indeed, after running it from a CD (without installing on the hard drive) I see the whole screen lighting up with Mandriv blue screen logo. Then I decide to find the xorg. conf to copy it and transfer it for Ubuntu installation. However, I cannot open the xorg.conf file. It comes out as blank. Is that because I am running from a CD mode and I am not allowed to read the files? Also in Mandriv I have to login as a guest.

What I do not get is this - how come Mandriv recognizes the Sony hardware I815 while Ubuntu cannot? I see all the blame game pointing to Sony Vaio, but if that is so why should it work with some other distros - like mentioned in one of the posts here - jaunty? I am inquiring from curiosity and not pointing fingers at anyone. Maybe the answer will help me to solve this issue.

Anyway, from the posts here looks like just rewriting or generating new xorg.conf files seem to have solved most of the problems. Am I doing something wrong here?
Please suggest,
Thanks

Revision history for this message
Geir Ove Myhr (gomyhr) wrote : Re: [Bug 288807] Re: [i815] Wrong resolution on Vaio PCG-SRX51, PCG-SRX41 and PCG-FX370 due to incorrect h/v rates

rajn, you will probably get much better response if you try the forums
at http://ubuntuforums.org/ . They are meant for helping Ubuntu users,
while a bug report is more technical and aimed at improving something
that is not quite right (and downright wrong) with Ubuntu.

Good luck, and I hope you find a solution. I suspect it is about
getting xorg.conf right, but that can be difficult sometimes.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.