[Ubuntu Wiki] Update of "DebuggingCompiz" by pvillavi

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by pvillavi:
http://wiki.ubuntu.com/DebuggingCompiz?action=diff&rev1=23&rev2=24

------------------------------------------------------------------------------
  Try different visual effects settings from the appearance preferences (System -> Preferences -> Appearance -> Visual Effects).  If the problem still occurs with effects set to "None" then the problem is no in Compiz but one of the systems mentioned above.
  
  If you have changed the default settings in "!CompizConfig Settings Manager" (package name compizconfig-settings-manager) then try resetting these to the defaults by launching it from from System -> Preferences and clicking on the "Preferences" button and then on the "Reset to defaults" button.
+ 
+ For bugs related to Unity please have a look to [[Unity/FilingBugs]]
  
  = How to file =
  
@@ -46, +48 @@

  
  = Advanced Debugging =
  
+ == Getting a Backtrace ==
+ 
  Install the debugging symbol packages (see DebuggingProgramCrash for how to add the debug repository):
  {{{
  sudo apt-get install compiz-core-dbgsym, compiz-plugins-dbgsym compiz-fusion-plugins-main-dbgsym, compiz-fusion-plugins-extra-dbgsym compizconfig-backend-gconf-dbgsym libcompizconfig0-dbgsym compiz-gnome-dbgsym
  }}}
  
- Run compiz manually by disabling visual effects and running it from the command line:
- {{{
- compiz.real --replace --indirect-rendering ccp
+ {{{ run gdb as: 
+ $ gdb --args compiz --replace
+ ...
+ (gdb) set logging on compiz-crash.txt
+ (gdb) run
+ ...
+ (once it crashes)
+ ...
+ (gdb) thread apply all bt full
+ (gdb) set logging off
  }}}
- You can then run this with a debugger.
+ 
+ Then you can attach that resulting log file (compiz-crash.txt) to the bug report.
+ 
+ == Stale crashers ==
+ 
+ If apport did not automatically report the issue, you can check that a crasher trace has been collected by looking into the {{{/var/crash}}} directory. You should see a filename containing 'compiz'.
+ 
+ {{{ls -altr /var/crash}}} to list them in chronological order.
+ 
+ To manually file a bug report using a crash file:
+  * stay in your current X session
+  * add a window manager from a TTY if needed, ie CTRL-ALT-F1, login, {{{DISPLAY=:0 metacity --replace}}}
+  * then, from your X session, do: {{{apport-bug -c /var/crash/<compiz crash file>}}} and follow the procedure in the web page that should open shortly after you invoke this command. Note that focus issues may prevent the page to appear on the top, but look for a new browser window opened in your workspace.
  
  ----
  CategoryBugSquad CategoryDebugging