bug_report.md

name	Bug report
about	Create a report
title
labels	bug
assignees

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Backtrace

• Install gdb and gdbserver: For example on openSUSE zypper in gdb gdbserver
• Open two terminals.
• Terminal 1: Start gdbserver gdbserver localhost:port path/to/profanity e.g. gdbserver localhost:1234 ./build_run/profanity
• Terminal 2: Start gdb gdb path/to/profanity e.g. gdb ./build_run/profanity
• Terminal 2: Attach to server target remote localhost:port e.g. target remote localhost:1234
• Terminal 2: Enable logging to file set logging enabled on and set logging file my.log
• Terminal 2: Type c
• Terminal 1: Use profanity to reproduce the crash
• Terminal 2: Show the backtrace bt or bt full
• Copy the backtrace here, either from gdb or from your logfile (my.log)

Environment

• Give us the version and build information output generated by profanity -v
• If you could not yet build profanity, mention the revision you try to build from
• Operating System/Distribution
• glib version
• libstrophe version
• omemo backend
• Some bugs might be due to specific implementation in the server. /serversoftware example.domain can be helpful

Reporter (optional)