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 776275 - Cannot file bug report containing particular python backtrace
Cannot file bug report containing particular python backtrace
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-12-19 14:26 UTC by Michael Catanzaro
Modified: 2016-12-19 14:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Catanzaro 2016-12-19 14:26:13 UTC
This is a test bug report to see if I can file a bug. If you see this bug then I can indeed file a bug!
Comment 1 Michael Catanzaro 2016-12-19 14:27:01 UTC
Wow I can totally file bugs!
Comment 2 Michael Catanzaro 2016-12-19 14:37:07 UTC
Let's repurpose this to track the real issue. I cannot file a bug against NetworkManager containing the following text (the lines between the quotes):

"""
I'm not sure what changed here, since I tested this just yesterday and it seemed to be working fine, but NetworkManager is broken in JHBuild again. The error is:

/home/mcatanzaro/src/jhbuild/checkout/NetworkManager/libnm/generate-setting-docs.py:191: Warning: cannot retrieve class for invalid (unclassed) type 'void'
  setting = new_func()
Traceback (most recent call last):
  • File "/home/mcatanzaro/src/jhbuild/checkout/NetworkManager/libnm/generate-setting-docs.py", line 191 in <module>
    setting = new_func()
TypeError: could not get a reference to type class

It happens with both python2 and python3.
"""

When I attempt to file this bug, I get an HTTP 500 internal server error response.

Andrea found this partial backtrace:

Dec 19 14:23:06 bugzilla bugzi[5538]: [error] Undef to trick_taint at /srv/http/bugzilla.gnome.org/Bugzilla/Util.pm line 44\n\tBugzilla::Util::trick_taint(undef) called at /srv/http/bugzilla.gnome.org/Bugzilla/Object.pm line 268\n\tBugzilla::Object::_do_list_select('Bugzilla::Extension::TraceParser::Trace', 'stack_hash = ?', 'ARRAY(0x7ff711549818)', undef) called at /loader/0x7ff70ef22570/Bugzilla/Extension/TraceParser/Trace.pm line 99\n\tBugzilla::Extension::TraceParser::Trace::_do_list_select('Bugzilla::Extension::TraceParser::Trace', 'stack_hash = ?', 'ARRAY(0x7ff711549818)', undef) called at /srv/http/bugzilla.gnome.org/Bugzilla/Object.pm line 246\n\tBugzilla::Object::match('Bugzilla::Extension::TraceParser::Trace', 'HASH(0x7ff7115a5968)') called at /loader/0x7ff70ef22570/Bugzilla/Extension/TraceParser/Trace.pm line 293\n\tBugzilla::Extension::TraceParser::Trace::identical_traces('Bugzilla::Extension::TraceParser::Trace=HASH(0x7ff711c39fd8)') called at /srv/http/bugzilla.gnome.org/extensions/TraceParser/Extension.pm line 71\n\tBugzilla::Extension::TraceParser::_check_duplicate_trace('Bugzilla::Extension::TraceParser::Trace=HASH(0x7ff711c39fd8)', 'Bugzilla::Bug=HASH(0x7ff71159cce8)', 'Bugzilla::Comment=HASH(0x7ff7115b75b0)') called at /srv/http/bugzilla.gnome.org/extensions/TraceParser/Extension.pm line 53\n\tBugzilla::Extension::TraceParser::bug_end_of_create('Bugzilla::Extension::TraceParser=HASH(0x7ff710edc3e8)', 'HASH(0x7ff7115425c0)') called at /srv/http/bugzilla.gnome.org/Bugzilla/Hook.pm line 18\n\tBugzilla::Hook::process('bug_end_of_create', 'HASH(0x7ff7115425c0)') called at /srv/http/bugzilla.gnome.org/Bugzilla/Bug.pm line 716\n\tBugzilla::Bug::create('Bugzilla::Bug', 'HASH(0x7ff70e4fd090)') called at /srv/http/bugzilla.gnome.org/post_bug.cgi line 129\n\tModPerl::ROOT::Bugzilla::ModPerl::ResponseHandler::srv_http_bugzilla_2egnome_2eorg_post_bug_2ecgi::handler('Apache2::RequestRec=SCALAR(0x7ff711451560)') called at /usr/lib64/perl5/vendor_perl/ModPerl/RegistryCooker.pm line 204\n\teval {...} called at /usr
Comment 3 Michael Catanzaro 2016-12-19 14:51:15 UTC

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