重要

We are currently a small number of developers active on the project. As such, we cannot answer and tag all of the opened issues immediately, but we do notice and read them. Good bug reports provide us important feedback, which we thank you for and always appreciate.

虫報告ガイド

このガイドには,ジャミで遭遇するバグや問題を報告するためのステップ・バイ・ステップ指示が含まれています.

環境を整え

  • データを失くする準備をしてください. アカウントをバックアップして,できるだけ多くのデバイスにリンクしてください.

  • 古いバージョンに対してバグ/問題報告はあまり役に立たないため,新しいバージョンでは既に修正されている可能性が高い.

虫を報告する方法

  1. Only required once: Create a Jami GitLab account.

  2. 発行を投稿する適切なプロジェクトを選択してください

  3. 複数の問題がある場合は,別々のバグ報告を提出してください. その方法で追跡することがはるかに簡単になります.

  4. The title is an explicit summary of the bug (for example, the header bar is too big due to icon size).

  5. バグを複製するための手順を計算します

    • If you have precise steps to reproduce it (great!), you're on your way to creating a helpful bug report.

    • If you can reproduce it occasionally but not after following specific steps, please provide additional information about the issue to help others understand and try to reproduce it.

    • If you can not reproduce the problem, there may be little chance of it being reasonably fixable. If you do report it, please provide as much information/clues about its occurrence as possible.

  6. Ensure your software is up to date. Ideally, test an in-development version to see whether your bug has already been fixed.

  7. Attempt to isolate from the environment and reproduce (that is, test on multiple devices).

  8. 環境を記述する:

    • Operating system and version

    • Precise device model (important for mobile devices)

    • Stable or beta version of Jami

    • What build you are using (F-Droid, Google Play, App Store, dl.jami.net, your own build, etc.). If you have built your own version of Jami, please specify the exact Jami Daemon version and client version (you can obtain it using jamid -v and jami -v; but note that our packages are updated quite often) and the Git commit.

    • Network conditions:

      • Are both devices on the same local network?

      • Different networks?

      • Is one or both behind NAT?

      • Are you using LTE?

      • Are you using WiFi?

    • Other details if required:

      • SIP provider,

      • Hardware,

      • etc.

明確な要約を書くこと

開発者が見る最初の部分です. 開発者には,このバグが表示されるのは,

よい概要は,エラー 報告を迅速かつユニークに識別し,問題を説明すべきであり,提案された解決策ではない.

Good: "Cancelling a file transfer crashes Jami"
Bad: "Software crashes"

Good: "All calls hang up after 32 seconds"
Bad: "Not able to call my friends"

複製するための正確なステップを書き出す

  • 開発者は コンピュータでバグを 作り出すことができるのか?

    Steps to reproduce are the most important part of any bug report. If a developer is able to reproduce the bug, the bug is very likely to be fixed. If the steps are unclear, it might not even be possible to know whether the bug has been fixed. We are totally aware that some bugs may look obvious to you, but they are probably related to your environment. The more precise you are, the quicker the bug can be fixed.

  • 虫の報告に何を含めるべきか?

    Indicate whether you can reproduce the bug at will, occasionally, or not at all. Describe your method of interacting with Jami in addition to the intent of each step. After your steps, precisely describe the observed (actual) result and the expected result. Clearly separate facts (observations) from speculations.

Good

私は常にこれらのステップに従って再生することができます:

1. Start Jami by clicking on the desktop icon.
2. Start a new conversation with anyone.
3. Click the file transfer button.

Expected results: A window opens and asks me to choose a file to send.
Actual results: When I click the file transfer button, nothing happens.

Bad

Attempt to transfer a file.
It doesn't work.

Obtained result

記入してください

  • ジュミデモン (ジミドまたはリブジミまたはリブリング) とクライアントのデバッグログ.

  • The core dump, if one was produced.

Expected result

A description of the expected or desired behavior.

追加情報提供

The following information is requested for most bug reports. You can save time by providing this information below the expected results.

記録

Android

To gather logs via the Android device using Jami:

  1. Tap Conversations.

  2. Tap the ⋮ (three-dot) menu on the top right.

  3. Tap Settings.

  4. Tap Diagnostic logs.

To gather logs via a computer using the Android Debug Bridge (adb):

  1. The adb is required to be set up on your computer.

  2. Launch Jami on your smartphone and then execute adb logcat *:D | grep `adb shell ps | egrep 'cx.ring' | cut -c10-15` > logring.txt

  3. 顧客の記録を含むファイルが

Desktop Jami client based on the Qt framework (GNU/Linux, macOS, Windows)

  1. Open the General tab in the settings.

  2. In the Troubleshoot section, click the Open logs button.

  3. Turn on the View logs switch.

  4. Click the Copy button.

  5. Paste the result and explain the scenario in the issue.

GNU/Linux

クラシックログ (デフォルトログでは >=警告のみが記録されます):

journalctl --since "24h ago" | grep jami

Full log: The Jami client (GUI) and daemon are separate processes. To obtain logs from both processes, start each process manually, one at a time.

  1. チェックは `ps aux ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ

    • ジャミは窓が開かないとしても まだ走っているかもしれない あなたの好みに応じて.

    • ヽ kill PID` を使って終了します.

  2. ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ ヽ

    • この実行可能は通常は PATH でないし,Debian/Trisquel/Ubuntu パッケージでは, /usr/lib/x86_64-linux-gnu/jamid -d -c または /usr/libexec/jamid -d -c で位置している.

  3. In another terminal, start the client, using jami -d.

プログラムを実行して GDB に戻る

gdb -ex run --args jami -d, or gdb -ex run --args /usr/libexec/jamid -cd, depending on the component you need to debug.

クラッシュすると, bt (またはさらに良く, thread を bt をすべて適用) と入力して, Enter を押します.

macOS

  1. /Applications/Jami.app/Contents/MacOS/へ移動する.

  2. ジャミをダブルクリックすると ジャミを起動し 端末へのログを印刷します

  3. 端末からファイルにログをコピーする

ターミナルから /<パスがJami>/Jami.app/Contents/MacOS/Jami -d を実行できます.

窓

  1. Open the command prompt (cmd.exe)

  2. Run Jami.exe with the following options:

    • -d ログを受け取るための別々のコンソールウィンドウを開く

    • -f %ローカルppdata%\jami\jami.log にログを書く