there is no kicker in 4.0.1 and this is obviously an installation and/or packaging issue since plasma works just fine with xinerama including on upgraded-from-3.5.x systems.

can you include the output of running plasma directly from a konsole/xterm? you can run it by pressing alt-f2 to get the run command dialog.

Ok, here is what I did:

from kde3, 
1. ctr+alt+f2.
2. sudo /usr/lib/kde4/plasma

Error Message:
<unknown program name> (6298) /: Cannot connect to the X server
Plasma (6299) : KUniqueApplication : Cannot find the D-Bus session server
Plasma (6298) : KUniqueApplication : Pipe closed unexpectedly 

If this was not what you wanted me to do, can you provide me with a step by step procedure to follow?

that isn't what i meant, no.

open a konsole.
from that konsole window start plasma (no sudo...)

Created attachment 23627 [details]
plasma startup error

This is the error outputted by plasma upon running it from a console.

Ok, I opened konsole in kde 3.5.9 and executed plasma as
/usr/lib/kde4/bin/plasma

and the output is in the attachment (id=23627)

I tried another thing:
Changed from
Section "ServerFlags"
    Option         "Xinerama" "1"
EndSection 

to 

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection 

Now everything works fine, EXCEPT the DUAL SCREEN.
And hence agreeing that it is a problem with xinerama.

I cannot get kde4 to use dual screen either, although I don't use xinerama. I do have have dual screen working on kde 3.5.8. The xorg that I use for my dual display is.

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 1.0  (buildmeister@builder3)  Thu Oct  4 10:34:46 PDT 2007

# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
#   sudo dpkg-reconfigure -phigh xserver-xorg

Section "ServerLayout"

	# Uncomment if you have a wacom tablet
	#	InputDevice     "stylus"	"SendCoreEvents"
	#	InputDevice     "cursor"	"SendCoreEvents"
	#	InputDevice     "eraser"	"SendCoreEvents"
    Identifier     "Default Layout"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Generic Keyboard"
    InputDevice    "Configured Mouse"
EndSection

Section "Files"
EndSection

Section "Module"
    Load           "glx"
EndSection

Section "ServerFlags"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    Identifier     "Generic Keyboard"
    Driver         "kbd"
    Option         "CoreKeyboard"
    Option         "XkbRules" "xorg"
    Option         "XkbModel" "pc105"
    Option         "XkbLayout" "us"
EndSection

Section "InputDevice"
    Identifier     "Configured Mouse"
    Driver         "mouse"
    Option         "CorePointer"
    Option         "Device" "/dev/input/mice"
    Option         "Protocol" "ImPS/2"
    Option         "ZAxisMapping" "4 5"
    Option         "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
    Identifier     "stylus"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "stylus"
    Option         "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
    Identifier     "eraser"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "eraser"
    Option         "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "InputDevice"
    Identifier     "cursor"
    Driver         "wacom"
    Option         "Device" "/dev/input/wacom"
    Option         "Type" "cursor"
    Option         "ForceDevice" "ISDV4"# Tablet PC ONLY
EndSection

Section "Monitor"
    Identifier     "Generic Monitor"
    HorizSync       30.0 - 70.0
    VertRefresh     50.0 - 160.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG L194WT"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 75.0
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "TV-0"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
EndSection

Section "Device"
    Identifier     "nVidia Corporation NV44A [GeForce 6200]"
    Driver         "nvidia"
    Option         "AddARGBVisuals" "True"
    Option         "AddARGBGLXVisuals" "True"
    Option         "NoLogo" "True"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Videocard0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 6200"
    BusID          "PCI:1:0:0"
    Screen          0
EndSection

Section "Device"
    Identifier     "Videocard1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 6200"
    BusID          "PCI:1:0:0"
    Screen          1
EndSection

Section "Screen"
    Identifier     "Default Screen"
    Device         "nVidia Corporation NV44A [GeForce 6200]"
    Monitor        "Generic Monitor"
    DefaultDepth    24
    Option         "AddARGBGLXVisuals" "True"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Videocard0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "CRT: nvidia-auto-select +0+0"
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Videocard1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "TV: nvidia-auto-select +0+0"
EndSection

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

@sayth: dual head is a completely different issue. see BR#156475

@prasadae: i still can't reproduce your problems here with xinerama. others are also running it fine with xinerama. i'm really at a loss at what to do for you. the debug output shows everything is being detected and set up properly as well. *shrug*

I am new at these things. Can you clarify if what I understand is right?
Xinrama working is unrelated to Dual head working? That is currently xinerama DOES working, but dual head does not not? Cos I can get KDE4 to work when I comment out all references to the other screen. 

If so, I can close this issue and comment on BR#156475? Which is more related to dual head. I have the same set up on my laptop and KDE4 is coming up to be really great! Thanks..

Dual head does not work, yes, while Xinerama does (with some provisos for things like struts which are messes in x.org itself).

The difference between "dual head" and "xinerama" is that in dual head there is actually a different X session running on each screen, while in xinerama there is one X session and all the screens belong within it.

You were right Aaron. This was a packaging issue.
I recently upgraded to Kubuntu 8.04 Beta (Hardy) and everything is fine, except a minor issue which is not related so I will not comment about it here.

Probably a packaging issue or Xorg 7.3 (One of the things new in 8.04) works better with plasma or whatever, It works now. And it was never kde4 as I still had the same kde 4.0.3 before upgrade!

Thanks anyway. And plasma rules. I cannot wait to show this off with other people in my lab! :-)