Važno

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.

Uvod za izvještavanje o bugovima

Ovaj vodič uključuje koračne upute za izvještavanje o grešaka i problemima koje susrećete u Jamiju.

Ugradite svoje okruženje

• Pripremite se za gubitak podataka, rezervirate svoj račun i povežite svoj račun sa što više uređaja.

• U slučaju da se u starijim verzijama prijave greške/probleme nisu korisne, postoji mogućnost da su već popravljene u novim verzijama.

Kako prijaviti bug

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

1. Izaberite pravi projekt za objavljivanje vašeg broja u:

   • 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. Ako imate više problema, molimo vas da podnesete odvojene izvještaje o grešcima.

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

4. Računati korake za reprodukciju greška:

   • 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. Opisite svoje okoliš (s) navodeći sljedeće:

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

Napisivanje jasnog povjema

Kako biste opisali bug koristeći oko 10 riječi? Ovo je prvi dio vašeg izvještaja o bugovima koji će programer vidjeti.

Dobar sažetak treba brzo i jedinstveno identificirati izvješće o grešci.

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"

Napisivanje preciznih koraka za reprodukciju

• Kako programer može reproducirati bug na svom uređaju?

  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.

• Što bi trebalo uključiti u izvještaj o bugovima?

  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

Uvijek mogu reprodukirati slijedeći ove korake:

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

Molimo uključite:

• Jami daemon (jamid ili libjami ili libring) i klijent debug dnevnik.

• The core dump, if one was produced.

Expected result

A description of the expected or desired behavior.

Obavljanje dodatnih informacija

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

Ugrađivanje

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. Sada imate datoteku koja sadrži dnevnik klijenta

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

U skladu s člankom 4. stavkom 1. stavkom 1. točka 1.

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. Pobrinite se da se ne radi o klijenatu Jami ili demonskim slučajevima: provjerite pokretom ps aux 〇 grep jami u terminalu.

   • Jami možda još uvijek radi, čak i ako nema otvorenih prozora, ovisno o vašim preferencama.

   • Ako se ili klijent ili daemon pokreće, prekini ih koristeći kill PID.

2. U jednom terminalu, pokrenite demona s jamid -d -c

   • Ovaj izvršljiv se obično ne nalazi u PATH, a u Debian/Trisquel/Ubuntu paketi, nalazi se na /usr/lib/x86_64-linux-gnu/jamid -d -c ili /usr/libexec/jamid -d -c.

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

Da biste dobili povratnu trag, možete pokrenuti program unutar GDB:

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

Kada se sruši, možete napisati bt (ili još bolje, thread primijeniti sve bt) zatim pritisnite Enter.

macOS

1. Navigajte na /Applications/Jami.app/Contents/MacOS/.

2. Dvostruko kliknite na Jami, a on će lansirati Jami i otisnuti log na terminal.

3. Kopiraj dnevnik iz terminala u datoteku.

Alternativno, možete pokrenuti /<put do Jami>/Jami.app/Contents/MacOS/Jami -d iz terminala.

Prozori

1. Open the command prompt (cmd.exe)

2. Run Jami.exe with the following options:

   • -d otvoriti zasebno prozor konzole za primanje dnevnika

   • -f za pisanje dnevnika u % lokaliziranim podacima%\jami\jami.log