Quote:
Originally Posted by notzed
I think "manually set it back to auto" just means to use the xconf-query command to set it to "auto" rather than "xpresent".
For what it's worth I set mine to xpresent months ago and had no trouble with it (slackware64-current). I'm using xdm and it dumps output from stuff it runs to ~/.xsession-errors which is where i'd look first but if you're not using that i dunno where they go. I see a file .xfce4-session.verbose-log as well which might be related but i don't know anything about it.
|
thanks, ye I startx from text mode, no xdm.
The craziest thing is that removing all xfce packages with pkgtool and installing them from install USB didn't fix it. Once even KDE failed to run properly (blank screen with only mouse pointer) after I issued those commands but it "fixed iteslf" on second run) which leads me to think xfwm actually breaks something more than itself. Im out of ideas other than reinstall whole system. I'll try setting it to auto again then. If it doesn't work I'll reinstall OS, then test again which command exactly breaks it, when I know which one it is I'll just reinstall again and set it all up as good as i can without using this command. Turning compositing off completely with.
Code:
xfconf-query -c xfwm4 -p /general/use_compositing -t bool -s false
works -no transparency and shadows but can live with that if it's really xfce's fault not mine nor can I do something about it.
I remember some thread about performance problems with glx happen because noveau uses vsync and glx uses it's own vsync and they interfeere with eachother or something but it's veague memory Im not sure what it really was or I just misunderstood something.