After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773986 - Bugzilla fails to accept bug reports containing a stack trace in the description
Bugzilla fails to accept bug reports containing a stack trace in the description
Status: RESOLVED DUPLICATE of bug 744491
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-11-05 16:56 UTC by Forest
Modified: 2016-11-05 18:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Forest 2016-11-05 16:56:26 UTC 
When I submit a new bug report containing a python traceback in the bug description, bugzilla fails, producing an error 500 page.

When I submit the same report without the traceback, it works.
Comment 1 Forest 2016-11-05 16:56:55 UTC 
Example traceback that triggered the problem earlier today:

Traceback (most recent call last):

+ Trace 236834

  • File "/usr/lib/python2.7/dist-packages/meld/diffmap.py", line 138 in do_draw 
    width, height)
cairo.Error: invalid value (typically too big) for the size of the input (surface, pattern, etc.) 






Comment 2


Forest





          2016-11-05 16:59:37 UTC
        



Looks like bugzilla is doing some special parsing of stack traces. I'm going post the same one again, this time with indentation, to see if the result looks different in the posted comment.

    Example traceback:

    Traceback (most recent call last):




+
Trace
    236835






    

  • 
          File "/usr/lib/python2.7/dist-packages/meld/diffmap.py",
          line 138
            in do_draw

    width, height)     cairo.Error: invalid value (typically too big) for the size of the input (surface, pattern, etc.)
    

    • 













Comment 3


André Klapper





          2016-11-05 18:50:08 UTC
        




*** This bug has been marked as a duplicate of bug 744491 ***