Comment 15 for bug 1212987
Revision history for this message
| Davide Parmeggiani (bullfrog-real) wrote | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
So, not sure why this was marked as duplicated the a bug that has absolutely nothing to do with this...
There's no sign of any at-spi2 daemon error in xsession-errors file.
This is happening to me on a regular basis every time I update the NVIDIA proprietary drivers (after a new kernel is pushed so not sure if it's the push or the driver install that messes up something). Pretty much like in #13.
I'd be ok if there was a solution to just restore the menu/wm to a working state. In the past I did the dconf reset solution (and setsid unity) and all was ok.
This time, apparently, it isn't enough.
I'd be very surprise if only 10 users are affected.
Anyone able to dig in and see what is being broken by the process?