This morning when I started up my computer I noticed that my workspace switcher had defaulted to only one window. I reset the panel applet back to 4 what I normally use, but no matter how many I add I continue to get results as if there is only 1 workspace. I’ve made sure all updates have been done and even tried a few reboots. I then went to shortcut keys in control panel and all the options for switching workspace key shortcuts are gone. It’s like the entire switcher program has been scrubbed from the system.
Also, when I try to open CCSM, the control screen comes up but for only 3 or 4 seconds then disappears automatically. In the short time that it is up it will not allow me to make any changes and the same goes for Desktop Effects which won’t even open now.
AFAIK this is because compiz is managing the virtual desktops. You tried to fool it, and now the control screen runs on a virtual desktop you can no longer see. IIRC one is able to set the management of virtual desktops in CCSM.
Hmm, I think I’m following you. I’ve corrected some things by completely removing Compiz and all of its add-ons. Now I have my multiple workspaces back, however nothing to use in Compiz. Any recommendations to go from here? What I’m truly trying to accomplish is getting back to using expo as I used to use in Ubuntu. See my article here Expo Viewer
I now have Compiz re-installed with minimal additions and the UI stays up as normal. I still have no option for Expo mode, but have 3D cube and cube rotation ticked. I’m surfing forums online for more information and will check in and report as I progress.
I just finished installing the extras a few minutes ago which gave me the option for Expo. Now I just need to figure out how to initialize it. Holding <power>+e isn’t making it come up. I checked my installed drivers for a Nvidia 9800GT and I have the correct X11 drivers installed. The only thing I can think of is that it has to do with my using a Wacom Bamboo tablet instead of a mouse. I plugged in a usb mouse and it was detected, but I still can’t get Expo to come on. I went into Expo and checked all the configurations, they all look good. The autodetect on the Wacom is all working great in every other fashion from the time of installation. However, I’m running out of ideas since I’m a newbie to openSUSE.
I went through the Nvidia Xserver settings to make sure I had all graphics set to maximum render and that all seems fine. I went back in and installed the Simple CCSM package and that went in, but it still will not launch anything. It thinks about it then does nothing. I read this article and was following the instructions thinking maybe that would lead me to a solution, but so far no luck.
As a test user I still get no results from Desktop Effects and CCSM shows up for only 4 seconds then disappears. When I log back in as Admin (normal) CCSM is working but nothing will activate Expo. Also Desktop Effects still aren’t working and if I try to turn on Animations it makes CCSM close.
Sorry about the confusion. No, I don’t run as root. I just refer to myself as admin since my password controls the system. I.e. only I am allowed to create and delete users and programs etc.
When I run this in terminal it makes the window controls go away and the desktop workspace switcher applet lock up. My response to the command in terminal was [1] 26471. That was it.
I’ve installed the KDE4 desktop environment to see if the problem persists there as well. So far so good. Now I just have to learn to navigate my way around KDE, which I have not used before. Thus far I have to say that it is AMAZING with all the visual graphics very similar to OSx. If someone can help me navigate to where the Compiz is and how I should proceed on initializing Expo I would appreciate it. So far I still haven’t had much luck on the GNOME desktop.
Well, switching to the KDE4 desktop seemed to fix whatever it was preventing Expo. I have a delightfully graphic rich environment now, and I have to say that the bouncing ball icons during program launches are really cool. So the only conclusion I can come to is that the problem was something between GNOME and my hardware drivers. In case anyone wants to research this further, here is my rig: