@Leo
It has happened a second time, where logging off and on seem to fix it again.
If you log off and on, would it then be in the .xsession-errors.old?
If so, then there are a number of things going on and I'm not sure how
to really debug things. I'm getting this message:
Starting gtk-window-dec
@Leo
I did update some. But I am pretty sure the only thing that was updated since
was Handbrake. I'll wait on it for a few days and record when it happens. When
I booted up this morning it seemed fine so maybe it was just a one time thing.
--
[regression-release] Neither compiz nor metacity no
Sorry, me again.
Here it was play by play...
1) I did post #34 from Bug #572617
Result: Everything seemed fixed, but I lost a lot of settings for other
programs.
2) I restored the old config folder and removed the gnome-session
folder. I disabled to the workaround.
Result: It seemed fixed. I r
** Attachment added: "Here is the new gnome-session"
http://launchpadlibrarian.net/49865020/gnome-session.new.tar.gz
--
[regression-release] Neither compiz nor metacity nor nautilus are run at start
https://bugs.launchpad.net/bugs/467668
You received this bug notification because you are a me
@Leo
Update
It has returned. I have no idea why. After last time I rebooted a couple
of times and it did seem to be fixed. Today I get home and turn on my
computer and it's back. Now for an even larger mystery, I logged off and
on, and it went away. I checked to make sure I didn't have the
workar
**Edit**
Like normal meaning there aren't any problems...
--
[regression-release] Neither compiz nor metacity nor nautilus are run at start
https://bugs.launchpad.net/bugs/467668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
des
@Leo
I did as you said and everything seems to be working like normal.
Cheers,
Rob
--
[regression-release] Neither compiz nor metacity nor nautilus are run at start
https://bugs.launchpad.net/bugs/467668
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which i
@Leo
The fix you posted on the other page (Bug #572617) seemed to fix it for me.
Thanks a bunch!
The only issue to those using it: you will loose a lot of settings and you will
have to manually restore them. In this case it wasn't too confusing or tedious.
Cheers,
Rob
--
[regression-release] N
