Tähtis

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.

Bug-aruandluse juhend

See juhend sisaldab samm-sammut juhiseid vigade ja probleemide kohta, mida sa Jami’s kohtud.

Seadista oma keskkond

• Ole valmis andmete kaotamiseks. Varusta oma konto ja seada oma konto võimalikult paljudele seadmetele.

• Aseta Jami uusima versiooni (või isegi beetaversiooni). Vanemate versioonide puhul on vigade/probleemide kohta teatamine vähem kasulik ja on tõenäoline, et seda on juba uusemates versioonides parandatud.

Kuidas saan teatada veast

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

1. Oma veast teavitamiseks vali õige projekt:

   • The Jami client for Android (Jami client for Android and Android TV devices)

   • The Jami client for iOS (Jami client for iPhone and iPad devices)

   • The desktop Jami client (Jami client, based on the Qt framework, for GNU/Linux, macOS, and Windows platforms)

   • If you know what you are doing, you may choose one of the other projects

2. Kui teil on mitu probleemi, esitage eraldi vigade raportid.

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

4. Selgitage, kuidas segadust paljendada:

   • 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.

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

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

7. Kirjelda oma keskkonda, täpsustades järgmist:

   • 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?

     • Kas sa kasutad LTE-ühendust?

     • Kas sa kasutad WiFi-ühendust?

   • Other details if required:

     • SIP provider,

     • Hardware,

     • etc.

Kirjutada selge kokkuvõte

Kuidas kirjeldaksite viga umbes 10 sõna abil? See on esimene osa teie vigaaruandes, mida arendaja näeb.

Hea kokkuvõte peaks kiiresti ja ainulaadselt tuvastama vigadearuande.

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"

Täpseid sammude kirjutamine, mida teha.

• Kuidas saab arendaja oma seadmes selle viga paljustada?

  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.

• Mida peaksite sisaldama bug-aruandes?

  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

Ma võin alati paljundada järgides neid sammu:

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

Palun lisa:

• Jami daemon (jamid või libjami või libring) ja kliendi defeg logid.

• The core dump, if one was produced.

Expected result

A description of the expected or desired behavior.

Lisateave esitamine

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

Pärisõidukid

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. Sul on nüüd faili, mis sisaldab kliendi logit.

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

Klassilised logid (põhimõtteliselt registreeritakse ainult >= hoiatuste logid):

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. Veenduge, et ei ole Jami kliendi või daemon esinemisi käivitakse: kontrollige käivitades ps aux 〇 grap jami terminaalis.

   • Jami võib ikka veel käia, isegi kui aknad on lahti, sõltuvalt teie eelistustest.

   • Kui kas kliend või daemon töötab, lõpetage nad kasutades kill PID.

2. Ühes terminaalis alustada daemon jamid -d -c

   • See täidetav ei ole tavaliselt PATH, ja Debian/Trisquel/Ubuntu paketes asub see /usr/lib/x86_64-linux-gnu/jamid -d -c või /usr/libexec/jamid -d -c.

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

Et saada tagasisidet, saate programmi GDB sees käivitada:

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

Kui see katkeb, võite kirjutada bt (või veelgi parem, thread rakendada kõik bt) ning siis paista Enter.

macOS

1. Navigeerige /Applications/Jami.app/Contents/MacOS/.

2. Kaks klikka Jami, see paneb Jami tööle ja trükib terminalli log.

3. Kopeeri log terminalt failile.

Alternatiivina võite rakendada /<tee Jami>/Jami.app/Contents/MacOS/Jami -d terminaalt.

Aknad

1. Open the command prompt (cmd.exe)

2. Run Jami.exe with the following options:

   • -d avada eraldi konsooli aken logide vastuvõtmiseks

   • -f kirjutada logid %localappdata%\jami\jami.log