Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
jami-docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
savoirfairelinux
jami-docs
Commits
5002a291
Commit
5002a291
authored
3 years ago
by
Andreas Traczyk
Committed by
Amin Bandali
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Update Bug report guide
Change-Id: I810c0d7038506c1d56108dfe5b73793b5ebb4e30
parent
3f239018
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
guides/how-to-report-bugs.md
+6
-6
6 additions, 6 deletions
guides/how-to-report-bugs.md
with
6 additions
and
6 deletions
guides/how-to-report-bugs.md
+
6
−
6
View file @
5002a291
...
...
@@ -35,7 +35,8 @@ if you don't have one already.
2
\.
If you have multiple issues, please file separate bug reports.
It will be much easier to keep track of them that way.
3
\.
Title is an explicit summary of the bug (e.g.: header bar is too big due to icon size)
3
\.
The title is an explicit summary of the bug (e.g.: header bar is
too big due to icon size)
4
\.
Figure out the steps to reproduce the bug:
...
...
@@ -52,7 +53,7 @@ It will be much easier to keep track of them that way.
5
\.
Make sure your software is up to date. Ideally, test an
in-development version to see whether your bug has already been fixed.
6
\.
Try to isolate from environment and reproduce (i.e. test on
6
\.
Try to isolate from
the
environment and reproduce (i.e. test on
multiple devices).
7
\.
Describe your environment(s) by specifying the following:
...
...
@@ -120,7 +121,7 @@ I can always reproduce by following these steps:
2. Start a new conversation with anyone
3. Click the file transfer icon
Expected results: A window opens and ask me to choose a file to send.
Expected results: A window opens and ask
s
me to choose a file to send.
Actual results: When I click the file transfer icon, nothing happens.
```
...
...
@@ -136,7 +137,7 @@ Obtained Result
Please include:
+
The daemon and client debug logs.
+
The
Jami
daemon
(jamid or libjami or libring)
and client debug logs.
+
The core dump if one was produced.
Expected Result
...
...
@@ -215,7 +216,7 @@ To gather logs via your phone using Jami itself:
To gather logs via your computer using the Android Debug Bridge (adb):
+
You need to have adb setup on your computer.
+
You need to have adb set
up on your computer.
+
Launch Jami on your smartphone and then execute
+
```adb logcat *:D | grep `adb shell ps | egrep 'cx.ring' | cut -c10-15` > logring.txt```
+
You now have a file containing the log of the client
...
...
@@ -227,4 +228,3 @@ options:
+
`-d`
to open a separate console window to receive logs
+
`-f`
to write logs to
`%localappdata%\jami\jami.log`
+
`-c`
to print logs directly to the Visual Studio debug output window
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment