Vigtigt

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.

Anmeldelsesvejledning

Denne vejledning indeholder trinvis instruktioner til at rapportere fejl og problemer, du møder i Jami.

Indstil dit miljø

• Vær klar til datatab, sikkerhedskopier din konto og forbinder din konto med så mange enheder som muligt.

• Installer den nyeste version (eller endda en beta-version) af Jami. At rapportere fejl/problemer i forhold til ældre versioner er mindre nyttigt, og der er en sandsynlighed for, at det allerede er blevet rettet i nyere versioner.

Hvordan indberette en bug

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

1. Vælg det rigtige projekt til at sende dit nummer i:

   • 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. Hvis du har flere problemer, skal du indgive separate fejlrapporter.

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

4. Find ud af, hvordan du reproducerer buggen:

   • 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. Beskriv dit miljø ved at angive følgende:

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

Skrive et klart resumé

Hvordan ville du beskrive buggen med ca. 10 ord? Dette er den første del af din bug-rapport en udvikler vil se.

Et godt resumé bør hurtigt og ensartet identificere en fejlrapport. Det skal forklare problemet, ikke din foreslåede løsning.

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"

Skrive præcise trin til at reproducere

• Hvordan kan en udvikler reproducere buggen på sin egen enhed?

  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.

• Hvad skal du medtage i en bug-rapport?

  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

Jeg kan altid reproducere ved at følge disse trin:

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

Indfør følgende:

• Jami daemon (jamid eller libjami eller libring) og klient debug logs.

• The core dump, if one was produced.

Expected result

A description of the expected or desired behavior.

Tilvejebringelse af yderligere oplysninger

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

Bogen

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. Du har nu en fil indeholdende loggen af klienten

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

Klassiske logs (i standard logs er kun >= advarselslogs logget):

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. Sørg for, at der ikke kører nogen Jami-klient eller dæmon-instanser: tjek ved at køre ps aux ̊ grep jami i en terminal.

   • Jami kan stadig køre, selvom der ikke er vinduer åbne, afhængigt af dine præferencer.

   • Hvis enten klient eller daemon kører, skal du afslutte dem ved hjælp af kill PID.

2. I en terminal starter daemon med jamid -d -c

   • Denne udførbar er normalt ikke i PATH, og i Debian/Trisquel/Ubuntu pakker, er den placeret på /usr/lib/x86_64-linux-gnu/jamid -d -c eller /usr/libexec/jamid -d -c.

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

For at få et backtrace, kan du køre programmet inde i GDB:

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

Når det styrter, kan du skrive bt (eller endnu bedre, thread anvende alle bt) og derefter trykke på Enter.

macOS

1. Navigere til /Applications/Jami.app/Contents/MacOS/.

2. Det vil starte Jami og printe loggen til terminal.

3. Kopier loggen fra terminal til en fil.

Alternativt kan du køre /<path til Jami>/Jami.app/Contents/MacOS/Jami -d fra terminal.

Vinduer

1. Open the command prompt (cmd.exe)

2. Run Jami.exe with the following options:

   • -d til at åbne et separat vindue på konsolen for at modtage logger

   • -f til at skrive logs til % lokalt data%\jami\jami.log