Thanks for reporting the issue. When the hang happens, if you are able to ssh into the computer from another machine or if you can switch to a TTY with Control-Alt-F1, you could help us find the cause. ssh might be more helpful than the TTY route though.
After starting compiz, waiting until it hangs X, and sshing in or switching to a TTY, what does the "top" command show you? Is compiz using a lot of CPU? If so, a compiz backtrace (while it is running) would be really helpful. To get a backtrace, first have a look at this page to add the repository for debug packages: https://wiki.ubuntu.com/DebuggingProgramCrash After adding the repository mentioned there, in synaptic hit "reload" and search for "compiz". When you see the results, for each already installed package there, install the corresponding -dbgsym package if there is one. Here, I have a script to get a compiz backtrace: http://erkinbah.googlepages.com/gdb-compiz-backtrace.sh After downloading the script, starting compiz, waiting until it hangs X, and sshing in or switching to TTY, you can run the script as follows: bash gdb-compiz-backtrace.sh The script should write the name of the backtrace file it dumps. Thanks. -- compiz hangs X server on startup https://bugs.launchpad.net/bugs/276237 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
