Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Attaches backtrace and other data encoded|
|Product:||[Fedora] Fedora||Reporter:||Milan Crha <mcrha>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||abrt-devel-list, dvlasenk, iprikryl, jfilak, jmoskovc, kklic, mlichvar, mmilata, mnowak, mtoman|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|:||908755 908756 908762 (view as bug list)||Environment:|
|Last Closed:||2013-02-14 09:33:37 EST||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
|Bug Blocks:||908755, 908756, 908762|
Description Milan Crha 2013-02-06 02:48:30 EST
I just got a rawhide report (bug #908143) and the first two attachments are unreadable, one of them is backtrace. They are encoded in base64 (and seem to be incomplete).
Comment 1 Jakub Filak 2013-02-07 04:34:37 EST
fixed in git commit b911a7075296f1560f3ea56ef4739159d5349ce8 Author: Jakub Filak <firstname.lastname@example.org> Date: Thu Feb 7 09:07:14 2013 +0100 reporter-bugzilla: use base64 XMLRPC type for encoded data instead of string type - obsolete: 'bugzilla.addAttachment' accepted base64 data in string variable and stored them in database decoded - current: 'Bug.add_attachment' accepts base64 data but it must be stored in base64 type, otherwise server doesn't decode the data and stores them as they are - related to issue #117 Signed-off-by: Jakub Filak <email@example.com> Signed-off-by: Jiri Moskovcak <firstname.lastname@example.org>
Comment 2 Milan Crha 2013-02-07 04:39:13 EST
Does it solve the strip issue too? I took the encoded string and after decode it didn't show full backtrace to me.
Comment 3 Jakub Filak 2013-02-07 05:26:47 EST
(In reply to comment #2) > Does it solve the strip issue too? I took the encoded string and after > decode it didn't show full backtrace to me. I hope so ;) We tested it and the backtrace was ok. Anyway, an update was pushed to the rawhide. If you have time to update the package and re-test, please do so and report the results here.
Comment 4 Jakub Filak 2013-02-14 09:33:37 EST
This particular bug was fixed and a update package was published for download for this Fedora release.