Terminal will not open on monitor (but will on TV!)

NoodleDoodleMan · 03-11-2008, 07:30 PM

Hi there!

I've just messed up my new linux machine by playing around with Xinerama. The setup of my computer is to display my main monitor on a crt then have another display which is my TV. I first did this without Xinerama, and it worked ok, but I wanted to be able to drag windows to the TV screen. So I set it up with Xinerama, it no longer opens a terminal window! All that happens is it says Starting Terminal... then it disappears with no terminal in its place.

So I used my backup to revert back to what I had which was a clone screen setup and now it only opens the terminal on the TV screen... bizarre and quite useless for me!

Below is my xorg.conf file:

Code:

# Xorg configuration created by livna-config-display

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen 0  "Screen[0]" 
        Screen 1  "Screen[1]" LeftOf "Screen[0]" 
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
	ModulePath   "/usr/lib/xorg/modules"
EndSection

Section "ServerFlags"
	Option	    "AIGLX" "on"

### PLEASE NOTE: This is the only line I added to the xorg.conf ###
### before everything started going wrong, then I removed it to ###
### try and fix it and the problem persisted.                   ###
#       Option      "Xinerama" "1"   
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "gb"
EndSection

Section "Device"
	Identifier  "Device[0]"
	Driver      "nvidia"
	Option	    "AddARGBGLXVisuals" "True"
        Screen 0
EndSection

Section "Device" 
   	Driver          "nvidia" 
   	Identifier      "Device[1]" 
   	Screen 1 
   	Option          "TVOutFormat" "Composite" 
   	Option          "TVStandard" "PAL-G" #or NTSC etc 
   	Option          "ConnectedMonitor" "Monitor[1]" 
   	BusID           "PCI:1:0:0" #adjust using 'lspci' or cat /proc/pci 
EndSection

Section "Screen"
	Identifier "Screen[0]"
	Device     "Device[0]"
        Monitor    "Monitor[0]"
	SubSection "Display"
		Depth		1
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		4
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		8
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		15
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		16
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		24
		Modes		"1280x1024" "1024x768" "832x624" "800x600" "720x400" "640x480"
	EndSubSection
EndSection

Section "Screen" 
   	Device "Device[1]" 
   	Identifier "Screen[1]" 
   	Monitor "Monitor[1]" 
   	DefaultDepth 24 
       	SubSection "Display" 
               Depth 24 
               Modes "1024x768_60" 
       	EndSubSection    
EndSection

Section "Monitor"
	Identifier "Monitor[0]" #CRT
	Option		"DPMS"
	HorizSync 31.5-80 
        	VertRefresh 56.3-75 
EndSection

Section "Monitor" 
    Identifier "Monitor[1]" #TV 
    HorizSync 30-50
    VertRefresh 60 
EndSection

Section "Extensions"
	Option	    "Composite" "Enable"
EndSection

I did read somewhere that it could be a permissions thing, but I'm not sure how or why in this case... so I did log in as root and tried it, which worked fine, like the good old days... So maybe it does have something to do with it...

I'm using Fedora 8 and Nvidia Geforce 4200Ti graphics card with the kmod-nvidia-96xx driver.

Can someone help?

Many thanks!

NoodleDoodleMan · 03-11-2008, 07:42 PM

Wierd...

I decided to create a shortcut on my desktop to see if that would work and it did... So I was going to compare the properties of the new shortcut and the menu shortcut (which I always used before). And I launched the menu shortcut by accident instead of looking at its properties and now its working... Could it be to do with creating the new desktop shortcut? I don't know... but it works now.

Thanks!