File: bugs.page

package info (click to toggle)
geary 46.0-13
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 15,092 kB
  • sloc: javascript: 972; ansic: 722; sql: 247; xml: 183; python: 30; makefile: 28; sh: 24
file content (50 lines) | stat: -rw-r--r-- 1,680 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
<page xmlns="http://projectmallard.org/1.0/"
      type="guide"
      id="bugs">

  <info>
    <link type="guide" xref="index#contribute"/>
    <link type="next" xref="limits"/>
  </info>

  <title>Need help with Geary?</title>

  <section id="getting-support">
    <title>Getting support</title>

    <p>If you are having trouble using Geary, please <link
    href="https://wiki.gnome.org/Apps/Geary/Contact">get in
    touch</link> with the Geary community about the problem.</p>
  </section>

  <section id="reporting-bugs">
    <title>Reporting bugs</title>

    <p>If you suspect you have found a bug in Geary, please follow the
    <link href="https://wiki.gnome.org/Apps/Geary/ReportingABug">bug
    reporting guidelines</link> so the problem can be diagnosed and
    fixed.</p>

    <p>To help diagnose the problem as fast as possible, please
    include the following information:</p>

    <list>
      <item><p>Geary version and installation method (Package?
      Flathub?  Source code?)</p></item>
      <item><p>Your desktop (GNOME? KDE? Something else?)</p></item>
      <item><p>Your operating system and version (Ubuntu 16.04? Fedora
      28? Rolled your own?)</p></item>
      <item><p>Email provider (Gmail, Yahoo!, Outlook.com, or someone
      else?)</p></item>
      <item><p>Steps to reproduce the bug</p></item>
      <item><p>What happened?</p></item>
      <item><p>What did you expect to happen?</p></item>
    </list>

    <p>Log files can be accessed via the Geary Inspector, press
    <keyseq><key>Alt</key><key>I</key></keyseq> to open it, select and
    save any relevant log files, and attach them to the bug
    report.</p>
  </section>

</page>