Well, i'm only about a week into Ubuntu, and although i'm feeling my way around little by little, i'm still very much a beginner at it. The good news: this is the first problem to completely stump me so far...
Separate X Screens is causing a whole mess of problems for me.
I am running Ubuntu 10.04 with a nVidia Corporation GT215 [GeForce GT 240] with a samsung LCD monitor in the VGA slot and a toshiba TV in the HDMI slot. When i run only one display (the samsung) everything works perfectly. Same with TwinView. But with Separate X screens (my preferred setup), there is a whole list of problems.
First off, in SXscreens my desktop icons aren't shown and i can't right click into a context menu on the desktop. Through diligent googling i've learned that Nautilus draws my desktop. So upon checking for a running nautilus process in SXscreens mode i couldn't find one. In standard, single display mode, a nautilus process IS running and i can right-click all day long. Also, in SXscreens mode i can't open nautilus from a terminal. The command:
yields this result:"jon@ubuntu:~$ nautilus"
And the command:"(nautilus:5685): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
(nautilus:5685): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
yields this result:"jon@ubuntu:~$ sudo nautilus"
...but i can open it by clicking any option on my "Places" menu. Additionally, both of the above commands work in single display mode and in TwinView. And in gconf-editor, under apps/nautilus/preferences "show desktop" is checked (enabled)."The program 'nautilus' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 608 error_code 3 request_code 18 minor_code 0)
(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.)"
I have "desktop cube" enabled with a 40% "opacity during rotation", as well as "rotate cube" and "cube reflection and deformation" with a cylinder deformation in Compiz. It all works perfectly in single display mode and TwinView, but in SXscreens the following issues arise:
Main screen (samsung): no transparency during rotation except top and bottom images, no cylinder deformation (it remains a cube), as well as a lack of ability to right-click into context menu and no desktop icons.
Second screen (toshiba): can't cycle through desktops, can't rotate cube with mouse (<ctrl><alt>Button1 just makes cursor disappear), no taskbar on top of screen (with applications, places, etc.) as well as a lack of ability to right-click into context menu and no desktop icons.
Additionally these problems *occasionally* arise: No top bar on windows (i think it's called the title bar? with the close, minimize, and maximize buttons) and login screen wallpaper stays on second display (the toshiba, this only happened once)
Has anyone encountered these problems or problems like them? The desktop problem seems to be nautilus-based, but how? And what's with the lack of Compiz functionality? I am stumped.
Bookmarks