Libnfc:Troubleshooting

From NFC Tools
(Difference between revisions)
Jump to: navigation, search
(I couldn't find the solution)
Line 12: Line 12:
 
* If you're confident you've unveiled a new bug, you can [https://code.google.com/p/libnfc/issues/entry file a new bugreport] and document it as well as possible.
 
* If you're confident you've unveiled a new bug, you can [https://code.google.com/p/libnfc/issues/entry file a new bugreport] and document it as well as possible.
 
* In the other cases, you can [http://www.libnfc.org/community/ use the Forum] to expose your issue and remember: the better you describe it the better chances you'll have a correct answer!
 
* In the other cases, you can [http://www.libnfc.org/community/ use the Forum] to expose your issue and remember: the better you describe it the better chances you'll have a correct answer!
 +
If you think it is useful to provide the trace of a bogus execution, use the environment variable LIBNFC_LOG_LEVEL=3, e.g.:
 +
LIBNFC_LOG_LEVEL=3 nfc-list
 
[[Category:Libnfc]]
 
[[Category:Libnfc]]

Revision as of 01:03, 29 December 2013

Having troubles?
Here are a few hints to help you out.

First check the FAQs.

Known issues

Check on the bugtracking page for known issues

Forum

Search on the Forum as this was maybe previously discussed.

I couldn't find the solution

If you couldn't find your answer in the above resources you have the following options:

  • If you're confident you've unveiled a new bug, you can file a new bugreport and document it as well as possible.
  • In the other cases, you can use the Forum to expose your issue and remember: the better you describe it the better chances you'll have a correct answer!

If you think it is useful to provide the trace of a bogus execution, use the environment variable LIBNFC_LOG_LEVEL=3, e.g.:

LIBNFC_LOG_LEVEL=3 nfc-list
Personal tools
Namespaces

Variants
Actions
Navigation
Documentation
Misc
Toolbox
Partners