The Mer Wiki now uses your Mer user account and password (create account on https://bugs.merproject.org/)
Nemo/Debugging
From Mer Wiki
< Nemo(Difference between revisions)
(→Tools and Tips to help in debugging) |
|||
| Line 2: | Line 2: | ||
* Log of console output: | * Log of console output: | ||
<pre> | <pre> | ||
| − | more /home/ | + | more /home/nemo/.xsession-errors |
</pre> | </pre> | ||
* Kernel message buffer: | * Kernel message buffer: | ||
| Line 25: | Line 25: | ||
<pre> | <pre> | ||
zypper install contextkit-tests | zypper install contextkit-tests | ||
| − | su - | + | su - nemo |
export DISPLAY=:0 | export DISPLAY=:0 | ||
context-listen <KEY> | context-listen <KEY> | ||
Revision as of 13:15, 15 September 2012
Tools and Tips to help in debugging
- Log of console output:
more /home/nemo/.xsession-errors
- Kernel message buffer:
dmesg
- List of all keys and values in gconf:
gconftool-2 -R /
- Starting dialer with debug output:
killall dialer; dialer -prestart -output-level debug
- For starting any libmeegotouch -based application with debug output use: "-output-level debug"
- Checking available keys in contexkt-kit:
zypper install contextkit-tests context-ls
- Checking value of property in contextkit
zypper install contextkit-tests su - nemo export DISPLAY=:0 context-listen <KEY>
In addition to these see Mer Debugging guide: Debugging
