Description of problem:

I have noticed the problem on this particular bug

>>> from bugzilla import Bugzilla
>>> BugzillaXmlrpc = 'https://bugzilla.redhat.com/xmlrpc.cgi'
>>> bugzilla = Bugzilla(url=BugzillaXmlrpc)
>>> bugzilla._proxy.Bug.history({'ids':[1614166]})
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1233, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python2.7/site-packages/bugzilla/_backendxmlrpc.py", line 138, in _ServerProxy__request
    ret = ServerProxy._ServerProxy__request(self, methodname, params)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1591, in __request
    verbose=self.__verbose
  File "/usr/lib/python2.7/site-packages/bugzilla/_backendxmlrpc.py", line 106, in request
    return self.__request_helper(url, request_body)
  File "/usr/lib/python2.7/site-packages/bugzilla/_backendxmlrpc.py", line 69, in __request_helper
    raise e
bugzilla.exceptions.BugzillaError: not well-formed (invalid token): line 6, column 0

Leos Pol did some debugging of the issue and identified that

the issue is in comment 13, specifically character right after the first "ll" command. There is a sequence of (0x0A) (0x03) (0x0A). 0x0As are \n, 0x03 Ctrl+C.
When the commenter copied the terminal output, he also copied it with ctrl+c. Something like this has to be escaped and not break XML traffic.


Version 5.0.4rh53