displayconfig-gtk crashed (core dumped) while trying dual head intel 945

here is the xorg.conf that leads to the bug

note : i'm still using ubuntu 7.10 Gutsy (tribe x) and my gutsy was updated today (Tuesday, August 28th) just before the test

strange. it should not be allowed to press the test (validate) button on a system with intel cards, since they do not support it.

the new intel driver was missing. I disabled the test function for those now. it should be fixed with the next guidance release.

validate != test

It is "valider" in french (my native language) but probably "apply" or something like that in English that causes the bug.

My video driver is the "intel" (!="i810") one (i don't know what you mean with "the new intel driver was missing")

In my case, it is still possible to press the "test" button.

I have the same problem (I think) on Gutsy Tribe-5. I have an Intel G965 chipset (on Asus P5B-V mobo) with a 19" Iiyama VisionMaster Pro 451 CRT.
When I start displayconfig-gtk, I get a list of resolutions of which 1280x1024@75Hz is selected. When I switch to 1600x1200x75Hz I get this:
Gdk-ERROR **: The program 'displayconfig-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 13 error_code 2 request_code 155 minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
Aborted (core dumped)

The Test button is and stays disabled when I change the resolution. Running with the --sync option seems to make no difference.

Why status of this bug is "fix commited' ? I'm runing displayconfig-gtk version 0.2+20070905 and guidance-backends version 0.8.0svn20070727-0feisty6 and still get an error when trying to change screen resolution (tested with nv drivers):

ubuntu@baltix:~$ sudo displayconfig-gtk
The program 'displayconfig-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 13 error_code 2 request_code 153 minor_code 2)

Fix committed means that the change was added to a branch, fix released is when the update is actually available to the users. Mr. Sebastian, ignoring this information, is there any way to give proof that the fix was committed or can you give a description of the change you made? I have the same question for my bug # 139029. I know I shouldn't have marked this as incomplete, but maybe this was the only way of getting your attention?

I guess you're uploading the package for this one too...

Dual screen is still not working with gutsy Beta and all updates...

And it's not able to correctly identify the resolution of the screen.

using Dell D420 and Intel GMA945

Fix Committed means Sebastien had checked the fix into Bazaar, but hadn't made a release of the code for users yet. However, recently version 0.3.1 has been uploaded, which I imagine may have this fix included.

Nanley, a better way to get a developer's attention is to contact them via email or irc; changing bug states is unlikely to gain their attention. ;-)

Xvani, note that dual screen with Intel is not currently supported by displayconfig-gtk because -intel uses xrandr 1.2 for this, which displayconfig-gtk does not yet support. This deficiency is already covered in bug 144641, so this bug focused specifically on addressing the crash when attempting to do dual mode with -intel.

Hy Bryce.

Now I am testing my new MacBook 2nd generation and trying to configure touchpad synaptics without xorg. Is that possible ?
Using displayconfig-gtk "screens and graphics" to detect better display configuration I have reached bug #147721.
I set up all devices and they are working very well but every kernel update have to reconfigure all again.

mabovo@macbook:~$ sudo lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
 Subsystem: Intel Corporation Unknown device [8086:7270]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
 Latency: 0
 Capabilities: [e0] Vendor Specific Information

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Unknown device [8086:7270]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at 50380000 (32-bit, non-prefetchable) [size=512K]
 Region 1: I/O ports at 20e0 [size=8]
 Region 2: Memory at 40000000 (32-bit, prefetchable) [size=256M]
 Region 3: Memory at 50400000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
  Address: 00000000 Data: 0000
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
 Subsystem: Intel Corporation Unknown device [8086:7270]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0
 Region 0: Memory at 50300000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=0 PME-

About dual screen, see Bug #149030 and Bug #182883.

Thank you for reporting this bug and for your efforts to make Ubuntu better. As Xorg has improved this past year, an unfortunate side effect of these improvements is that it has rendered several design assumptions in displayconfig-gtk obsolete. So, starting with Hardy we are no longer putting displayconfig-gtk forth as a primary configuration tool, and are putting our development focus into the Screen Resolution applet. As a result, we do not plan to fix this bug and thus are closing it.

For more background on this change, please see this page: [WWW] https://wiki.ubuntu.com/X/DisplayConfigGtk

Kubuntu is also moving to a new display tool in Intrepid. Also with current xorg, dual head with displayconfig is pretty well unsupported due to displayconfig using Xinerama and not Xrandr. It would take a major redesign to change that.