Compiz problem
Compiz problem
I was running MX Linux 17 off a USB stick.
I mention in this posting viewtopic.php?f=97&t=43514 that I had a problem with the monitor turning off, once after I installed Compiz.
I redid the USB stick with a fresh install of MX Linux. I installed Compiz a couple of days ago and started it with the fusion icon. My aim was to see if it introduced shadows on the Conky. The answer was yes.
I checked to see if Compiz was set to autostart after reboot, but this had not been done during its install. I left things as they were and rebooted.
After reboot the desktop appeared in black and white as per usual, the places bar appeared, and that was it. The desktop remained monochrome, and my mouse pointer became an "X" when hovered over it. I clicked the whisker menu and it worked, so I selected to start the fusion icon.
The desktop finally got its color back, but places bar disappeared.
I could get a menu whilst hovering over my all present desktop, so I rebooted.
Same problem when I booted up, so this time I decided to simply start Compiz. Same thing, nice colorful desktop, but nothing else. I shut the computer down with a growl.
I decided to have a final bash with this live version of MX linux from the USB, but this time I simply got "no signal" when it booted.
I found on MX 16 that after using Compiz I couldn't simply turn it off and return to using a different compositor, bits were missing after a reboot and Compiz had to be restarted to correct the problems. Does Compiz set specific parameters when it is used, and if so can they be reset if it doesn't autostart? It strikes me this would solve potential problems.
I mention in this posting viewtopic.php?f=97&t=43514 that I had a problem with the monitor turning off, once after I installed Compiz.
I redid the USB stick with a fresh install of MX Linux. I installed Compiz a couple of days ago and started it with the fusion icon. My aim was to see if it introduced shadows on the Conky. The answer was yes.
I checked to see if Compiz was set to autostart after reboot, but this had not been done during its install. I left things as they were and rebooted.
After reboot the desktop appeared in black and white as per usual, the places bar appeared, and that was it. The desktop remained monochrome, and my mouse pointer became an "X" when hovered over it. I clicked the whisker menu and it worked, so I selected to start the fusion icon.
The desktop finally got its color back, but places bar disappeared.
I could get a menu whilst hovering over my all present desktop, so I rebooted.
Same problem when I booted up, so this time I decided to simply start Compiz. Same thing, nice colorful desktop, but nothing else. I shut the computer down with a growl.
I decided to have a final bash with this live version of MX linux from the USB, but this time I simply got "no signal" when it booted.
I found on MX 16 that after using Compiz I couldn't simply turn it off and return to using a different compositor, bits were missing after a reboot and Compiz had to be restarted to correct the problems. Does Compiz set specific parameters when it is used, and if so can they be reset if it doesn't autostart? It strikes me this would solve potential problems.
Re: Compiz problem
Not sure what the cause of your problem is. Buy here are the two compiz config files I have. Some of the parameters are specific to my settings.
/.config/compiz/compizconfig/config
/.config/compiz/compizconfig/defaukt.ini
/.config/compiz/compizconfig/config
Code: Select all
[general]
profile =
integration = true
[kde_session]
backend = ini
profile =
integration = true
plugin_list_autosort = true
Code: Select all
[decoration]
as_command = emerald --replace
[core]
as_active_plugins = core;svg;smartput;showdesktop;maximumize;mousepoll;text;notification;place;resize;tile;png;inotify;grid;decoration;wall;imgjpeg;move;winrules;workarounds;ring;putplus;put;wallpaper;showmouse;obs;scale;expo;freewins;
s0_vsize = 2
as_show_desktop_edge = BottomRight
s0_hsize = 2
[switcher]
as_next_key = Disabled
[staticswitcher]
as_next_key = Disabled
[ring]
as_next_key = <Alt>Tab
as_prev_key = <Shift><Alt>Tab
[scale]
as_initiate_edge =
as_initiate_all_edge = TopRight
[tile]
as_animate_type = 2
[wallpaper]
[workarounds]
as_sticky_alldesktops = true
as_qt_fix = true
as_legacy_fullscreen = true
[notification]
as_timeout = 0
[place]
s0_mode = 1
[obs]
as_brightness_increase_key = <Control><Primary>u
as_brightness_decrease_key = <Control><Primary>d
[winrules]
s0_size_matches = ;
s0_size_width_values = -32767;
s0_size_height_values = -32767;
s0_maximize_match = & !(title="Apt History") & (state=)
[putplus]
s0_avoid_offscreen = true
[move]
as_opacity = 60
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: Compiz problem
I had no problems with Compiz when it was initially run, all of FX and window decorations worked fine, it was only when I rebooted when the problems started.
One point I forgot to mention is after the reboot none of the window decorations worked. My guess is something is set by the Emerald theme manager which sticks after a reboot, and when emerald doesn't run at startup it causes the window decorations to be AWOL.
This is just a guess though...
One point I forgot to mention is after the reboot none of the window decorations worked. My guess is something is set by the Emerald theme manager which sticks after a reboot, and when emerald doesn't run at startup it causes the window decorations to be AWOL.
This is just a guess though...
Re: Compiz problem
Yes emerald draws the system titlebar. As you can see from the first couple lines of the default.ini I posted emerald is called when the desktop loads if compiz initializes. I have fusion-icon set to start in Sessions and Startup which loads compiz as well.
Code: Select all
[decoration]
as_command = emerald --replace
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: Compiz problem
I've got that.
The problem seems to be when Compiz has been run but is not set to autostart after a reboot. It seems like the default compositor is lacking a setting to correctly display window decorations.
If you've got a spare USB stick run MX 17 live, add Compiz to it and run it, then reboot with no startup settings for Compiz. If it's my PC then you will have no problems, but if you do encounter similar issues then it seems Compiz throws a spanner in the works somewhere.
The problem seems to be when Compiz has been run but is not set to autostart after a reboot. It seems like the default compositor is lacking a setting to correctly display window decorations.
If you've got a spare USB stick run MX 17 live, add Compiz to it and run it, then reboot with no startup settings for Compiz. If it's my PC then you will have no problems, but if you do encounter similar issues then it seems Compiz throws a spanner in the works somewhere.
Re: Compiz problem
If it is a Live USB without persistence any settings including startupwill be lost. So I fail to see how any compiz is still on the system. Unless you messed with the files on the Live USB from another running system.
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: Compiz problem
I set the live USB to have persistence (static).
I don't have the knowledge to mess with files on the live USB - you have probably guessed that
I don't have the knowledge to mess with files on the live USB - you have probably guessed that
Re: Compiz problem
I have not messed with persistence since early MX 16 so I am out of ideas.colin_b wrote:I set the live USB to have persistence (static).
I don't have the knowledge to mess with files on the live USB - you have probably guessed that
Forum Rules
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Guide - How to Ask for Help
richb Administrator
System: MX 23 KDE
AMD A8 7600 FM2+ CPU R7 Graphics, 16 GIG Mem. Three Samsung EVO SSD's 250 GB
Re: Compiz problem
I used the MX create live USB tool - this allowed me to have persistence.
- dolphin_oracle
- Developer
- Posts: 20010
- Joined: Sun Dec 16, 2007 1:17 pm
Re: Compiz problem
Remember that compiz is not just a compositor like compton but a full blown window manager. So when you disable it's autostart you need to makr sure the system is still starting a different window manager (presumably xfwm) .
Which can be done from the fusion icon menus.
Which can be done from the fusion icon menus.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.