On Tuesday 25 November 2008 11:21:28 pm you wrote:

One thing I am unclear of from your post is whether you are saying compiz will not start at all, or just will not start a login? Generally with kde, if compiz is running when you end your session, it will start again on the next login. I prefer loading kwin to begin with and then starting compiz manually, but obviously you would like it to do it automatically.

Hi David, Yes I mean it's just not starting automatically after login, but if I go to start -> utilities -> desktop -> sccsm and put the tick "enable desktop effects" once I logged in, compiz starts and everything is fine. I just don't want to do that every time I restart my computer. (I can get it working also by doing "reload window manager" from compiz fusion icon)

.config/compiz/compizconfig/config

my config file looks pretty minimalist. --------------------- [kde_session] backend = ini profile = Default ---------------------

that would accomplish what your want. Also, you can set compiz as the default windows manager in kde control-center -> kde components -> Session Manager -> Window Manager.

I checked that earlier and yes it is set to compiz there (there was another option of compiz-custom which I also tried and it didn't work), but it still doesn't start automatically after restart. There was a suggestion in one of the forums to create a file script in ~/.kde/Autostart, but I'm not sure I need to do that, since I already have something there lrwxrwxrwx 1 floyd users 23 2008-05-02 23:16 compiz-manager -> /usr/bin/compiz-manager -rw-r--r-- 1 floyd users 1950 2008-06-21 00:24 .directory It used to work smoothly before, I didn't even have fusion icon installed. Now it's so annoying to start it each time manually :-( Thanks a lot for your help. Sergey -- Sergey Mkrtchyan, Graduate Student @ Department of Physics & Astronomy, Faculty of Science, University of Waterloo -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sergey Mkrtchyan wrote:

On Tuesday 25 November 2008 11:21:28 pm you wrote:

...

One thing I am unclear of from your post is whether you are saying compiz will not start at all, or just will not start a login? Generally with kde, if compiz is running when you end your session, it will start again on the next login. I prefer loading kwin to begin with and then starting compiz manually, but obviously you would like it to do it automatically.

Hi David,

Yes I mean it's just not starting automatically after login, but if I go to start -> utilities -> desktop -> sccsm and put the tick "enable desktop effects" once I logged in, compiz starts and everything is fine. I just don't want to do that every time I restart my computer. (I can get it working also by doing "reload window manager" from compiz fusion icon)

...

.config/compiz/compizconfig/config

my config file looks pretty minimalist. --------------------- [kde_session] backend = ini profile = Default ---------------------

...

that would accomplish what your want. Also, you can set compiz as the default windows manager in kde control-center -> kde components -> Session Manager -> Window Manager.

I checked that earlier and yes it is set to compiz there (there was another option of compiz-custom which I also tried and it didn't work), but it still doesn't start automatically after restart.

There was a suggestion in one of the forums to create a file script in ~/.kde/Autostart, but I'm not sure I need to do that, since I already have something there

lrwxrwxrwx 1 floyd users 23 2008-05-02 23:16 compiz-manager -> /usr/bin/compiz-manager -rw-r--r-- 1 floyd users 1950 2008-06-21 00:24 .directory

It used to work smoothly before, I didn't even have fusion icon installed. Now it's so annoying to start it each time manually :-(

Thanks a lot for your help.

Sergey

Sergey, I also found this which looks promising. I haven't tried it, but this looks like where it needs to be changed: In KDE 3.5 you need to edit the text file $HOME/.kde/share/config/ksmserverrc and change the line defaultWM= [General] confirmLogout=true defaultWM=compiz-manager ^^^^^^^^^^^^^^^^^^^^^^^ excludeApps= loginMode=restorePreviousLogout offerShutdown=true screenCount=1 shutdownType=0 Give it a shot and report back. (move or remove the Autostart/start-compiz script if you installed it) -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sergey Mkrtchyan wrote:

On Wednesday 26 November 2008 09:51:31 pm David C. Rankin wrote:

...

In KDE 3.5 you need to edit the text file $HOME/.kde/share/config/ksmserverrc and change the line defaultWM=

[General] confirmLogout=true defaultWM=compiz-manager ^^^^^^^^^^^^^^^^^^^^^^^ excludeApps= loginMode=restorePreviousLogout offerShutdown=true screenCount=1 shutdownType=0

Give it a shot and report back. (move or remove the Autostart/start-compiz script if you installed it)

Hi David,

Yeah things get really mysterious here.

1. I did the script and put it in the autostart folder as you suggested, then when I restarted I got two compiz fusion icons in the taskbar next to each other and yet compiz was not started. Again, if I click on one of them and do reload window manager everything comes back to normal.

Weird thing: In settings for compiz (CCSM), I enabled the splash screen for compiz, and now when I login, the splash screen is actually coming up (fancy written compiz fusion with some waves around it), but still no compiz, no cube, no emerald.

2 fusion-icons? I've seen that before, but only when I accidentally started it twice. I think we can fix this thing, and I think compiz-manager has got to be the problem. As far as any other configurations go, I don't think there is anything else. I've included my various ~/.config/compiz setup at the end of this email, just in case. Yes, I know the splash screen well, I enable it on every install. As far as neat splashes go, that is one of the best. If the splash is showing, then compiz *is* being *called*, but for some reason it is failing to actually start the application. If you have 2 fusion-icons, then we started compiz twice. If you don't have compiz enabled after that, then the way we called it didn't work. I bet this is where the 2 fusion-icons came from: 1-from the Autostart script and 1-from ksmserverrc. (both with compiz-manager). I do NOT have compiz-manager installed. I either start compiz manually or with fusion-icon. compiz-manager, just being a shell script that tries to start compiz based on its guesses about your system. It may be trying to start it wrong and the start script gets run, but fails to leave you with a working compiz. However, when you start compiz with fusion-icon, it works because you are not relying on compiz-manager, you are just starting compiz with the options set in /usr/lib64/python2.5/site-packages/FusionIcon/data.py: compiz_args = ['--replace', '--sm-disable', '--ignore-desktop-hints', 'ccp']

2. I also checked in the ksmserverrc... file you said, __________________________________ [General] confirmLogout=true defaultWM=compiz-manager <<- added this line, still no luck excludeApps= loginMode=restorePreviousLogout offerShutdown=true screenCount=1 shutdownType=0 windowManager=compiz <<- used to have this line before __________________________________

It's strange that this has never happened before, I didn't even had fusion icon before and I don't remember doing anything after my first install, it just worked.

Thanks a lot anyways, I really appreciate your help.

Sergey

If I have guessed right, then we can fix it in one of the following way: (1) Test 1 - Remove Autostart, change defaultWM=fusion-icon: Remove/move the ~/.kde/Autostart script to get rid of it for now. In ~/.kde/share/config/ksmserverrc, change 'defaultWM=fusion-icon' and then logout and back in. If it works, compiz-manager was failing to start compiz. We have replaced the calls to compiz-manager with calls to fusion-icon so you can safely remove compiz-manager. If test 1 fails, try passing defaultWM the options you see as the result of running 'ps ax | grep compiz' which should be something like: defaultWM='compiz --replace --sm-disable --ignore-desktop-hints ccp' which should be the same thing as passing it fusion-icon, but I don't know what parameter type defaultWM is expecting. Logout/login and see if this fixed it. If it is, then for the same reasons, you can safely remove compiz-manager. (2) Test 2 - Delete defaultWM= line in ksmserverrc, try a modified Autostart script: Completely delete the defaultWM= line in ~/.kde/share/config/ksmserverrc, it normally isn't there, then: modify the Autostart/start-compiz script to call fusion-icon like this: #!/bin/bash --norc /usr/bin/fusion-icon & sleep 2 emerald --replace & exit 0 If you deleted the script the first time, make sure it is still executable: chmod 0750 start-compiz Now logout/login. Regardless, we should only have 1 fusion-icon showing in the tray. If we have more than 1, something else is awry. If compiz works on login, the problem i remove compiz-manager (3) Test 3 - The Nuclear Option: I think we have pretty much exhausted the what ifs by this point, it is time for the big hammer. If it is still hosed, then I would set kde back to kwin, nuke compiz and then go through a fresh install with clean config files and stab this thing in the heart -- wooden steak not optional: kwin --replace & remove any Autostart script that is still there rpm -e $(rpm -qa | grep compiz) $(rpm -qa | grep ccsm) fusion-icon mv ~/.xcompmgrrc ~/.xcompmgrrc-save mkdir ~/tmp && mv ~/.config/compiz ~/tmp/compiz-save Compiz is now gone -- LOGOUT AND LOG BACK IN -- to make sure you login to kwin *** Then make SURE the only buildservice X11:/ repository you have enabled is: http://download.opensuse.org/repositories/X11:/XGL/openSUSE_11.0/ Find the alias for the reposory so we can specify the -r command with 'zypper in' to make sure you only pull the compiz packages from there. Then simply do a quick fresh install of compiz (minus compiz-manager) and (as root or sudo): zypper in -r x11 \ compizconfig-settings-manager \ compiz-emerald-themes \ compiz-fusion-plugins-extra \ compiz-emerald \ compiz \ python-compizconfig \ compiz-fusion-plugins-main \ compiz-kde \ libcompizconfig \ fusion-icon *** Note: my alias for the repo above is 'x11'. Just replace it with your alias for the repo. (I have tested the install and it works fine) or, if you prefer one line: zypper in -r x11 compizconfig-settings-manager compiz-emerald-themes compiz-fusion-plugins-extra compiz-emerald compiz python-compizconfig compiz-fusion-plugins-main compiz-kde libcompizconfig fusion-icon Then start and reconfigure compiz. With compiz running now on a fresh install, try a couple of logout/logins to see what it is doing. I know when I start with fusion icon, I will see the fusion-icon in the systray. On subsequent logins however, compiz will start automatically, but there will be no fusion icon in the systray. See what yours does. If you are starting fine on login, then I wouldn't do anything else to try and "make it any more permanent than it is, knowing that from time and again, for some reason it may not start that one time and youll have to manually start it. I know I probably get 5-8 login/logouts where compiz just starts as you want it to. Then the wind blows the wrong way one day and I'm dumped into kwin. I start it again and I know I'm good for the next week or so. I live with it like that. But to go farther and command that it shall from heretofore always start with compiz leads us to test 4. (4) Test 4 - A new Hope for the Desktop To add certainty to compiz always starting on login, I think your best bet is to try again to make it permanent with defaultWM=fusion-icon or as based on the results we got from tests 1 & 2 above. Not knowing how defaultWM= gets set, but knowing it does get set, leads me to say the Autostart method, may be a bandaid, but it isn't the longterm solution due to defaultWM= having the possibility of being set that would then bring back your 2 favorite fusion-icons. My bet says Test 1 fixed it, unless there was an underlying problem with your package configs. I would be surprised if we had to execute the nuclear option, but that is always a good guarantee that you have a clean slate to work from. Not to mention when nuking and reinstalling everything has been captured in 2 command lines, it doesn't take that much time to get that gaurantee. We have a command line, why not use it? Generating the install command for compiz fusion with zypper was nothing more than couple of helper apps strung together which is pretty hand and can be made applicable to just about any set of packages you deal with on a daily basis. Here is how I did it: echo "zypper in -r x11 \\"; for i in $(rpm -qa | grep compiz) $(rpm -q fusion-icon); do echo "$(echo $i | sed -e 's/-0.*$//') \\"; done Then just cut and paste ... and be careful not to grab the last \ after fusion-icon. My config files are below that you can check against, just in case there is something there that is also giving you grief. Good Luck and Happy Thanksgiving ;-) _______________ Local Config Here is what I have in ~/.config/compiz: fusion-icon: [compiz options] indirect rendering = true loose binding = false [window manager] active wm = compiz In ~/.config/compiz/compizconfig, I have: config: [kde_session] backend = ini profile = Default.ini: [decoration] as_command = emerald --replace [core] as_active_plugins = core;resize;decoration;water;zoom;splash;png;minimize;workarounds;shift;wobbly;regex;place;firepaint;mousepoll;obs;fade;move;cube;showmouse;rotate;switcher;cubeaddon;scale; as_command_screenshot = /opt/kde3/bin/ksnapshot as_command_window_screenshot = /opt/kde3/bin/ksnapshot --current [cube] s0_skydome_image = /usr/share/wallpapers/darksunset.png s0_skydome = true as_next_slide_key = Disabled [rotate] s0_zoom = 0.503300 [cubeaddon] s0_intensity = 0.652600 s0_ground_color1 = #282baecc s0_bottom_images = /usr/share/compiz/opensuse_alien.png;/usr/share/compiz/opensuse.png;compizcap.png; s0_bottom_scale = false s0_top_images = /usr/share/compiz/opensuse_alien.png;opensuse.png; s0_top_color = #000000ff s0_bottom_color = #000000ff s0_sphere_aspect = 0.797800 [wobbly] s0_friction = 2.698200 s0_spring_k = 6.707500 [ring] s0_ring_height = 55 s0_thumb_width = 375 s0_thumb_height = 425 as_prev_all_key = Disabled as_next_all_key = Disabled [move] as_constrain_y = false [obs] s0_opacity_step = 7 [showmouse] s0_color = #fcef35ff s0_size = 10.140000 s0_num_particles = 705 s0_slowdown = 0.928700 s0_darken = 0.906500 s0_radius = 75 [water] as_rain_delay = 1 [shift] s0_intensity = 0.602300 s0_ground_color1 = #120c4ccc s0_ground_color2 = #090d3308 s0_ground_size = 0.350000 I don't think these would make a difference, but you never know. It may be worth checking ~/.xcompmngrrc: [xcompmgr] Compmode=CompClientShadows DisableARGB=false FadeInStep=0.061 FadeOutStep=0.07 FadeTrans=false FadeWindows=true ShadowColor=0x00003B ShadowOffsetX=-40 ShadowOffsetY=-80 ShadowRadius=10 -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Sergey Mkrtchyan napsal(a):

On Wednesday 26 November 2008 09:51:31 pm David C. Rankin wrote:

...

In KDE 3.5 you need to edit the text file $HOME/.kde/share/config/ksmserverrc and change the line defaultWM=

[General] confirmLogout=true defaultWM=compiz-manager ^^^^^^^^^^^^^^^^^^^^^^^ excludeApps= loginMode=restorePreviousLogout offerShutdown=true screenCount=1 shutdownType=0

Give it a shot and report back. (move or remove the Autostart/start-compiz script if you installed it)

Hi David,

Yeah things get really mysterious here.

1. I did the script and put it in the autostart folder as you suggested, then when I restarted I got two compiz fusion icons in the taskbar next to each other and yet compiz was not started. Again, if I click on one of them and do reload window manager everything comes back to normal.

Weird thing: In settings for compiz (CCSM), I enabled the splash screen for compiz, and now when I login, the splash screen is actually coming up (fancy written compiz fusion with some waves around it), but still no compiz, no cube, no emerald.

2. I also checked in the ksmserverrc... file you said, __________________________________ [General] confirmLogout=true defaultWM=compiz-manager <<- added this line, still no luck excludeApps= loginMode=restorePreviousLogout offerShutdown=true screenCount=1 shutdownType=0 windowManager=compiz <<- used to have this line before __________________________________

It's strange that this has never happened before, I didn't even had fusion icon before and I don't remember doing anything after my first install, it just worked.

Thanks a lot anyways, I really appreciate your help.

Sergey

You have 2 fusion icons because you run it twice in your ~/kde/Autostart/ folder... (1 symlink: compiz-manager -> /usr/bin/compiz-manager and 2nd the new script...) Just remove one of them... (i suggest the script... compiz manager is not the problem) I cannot help you with the autostart problem though... :-( Gryffus