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 599873 - TagLib.Tag sometimes returns "\0" strings
TagLib.Tag sometimes returns "\0" strings
Status: RESOLVED WONTFIX
Product: taglib-sharp
Classification: Other
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: taglib-sharp-maint
taglib-sharp-maint
Depends on:
Blocks:
 
 
Reported: 2009-10-28 02:43 UTC by Alexander Kojevnikov
Modified: 2018-08-17 19:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Alexander Kojevnikov 2009-10-28 02:43:20 UTC 
For mp3 file from bug 599806, TagLib# returns a "\0" string for FirstComposer, Conductor and Copyright. It should rather trim NULL bytes and return an empty string.
Comment 1 Alexander Kojevnikov 2009-12-29 07:40:26 UTC 
Another sample mp3 file can be found in bug 605570
Comment 2 zulu99 2012-12-01 13:34:05 UTC 
Just encountered the same problem in Basenji. Taglib# returns "\0" strings for gif comments. Please see the following bugreport, sample files are attached (ranting2.gif).
https://bugs.launchpad.net/basenji/+bug/1084428
Comment 3 zulu99 2012-12-01 13:39:59 UTC 
To be more precise, the bug does not only affect empty strings, the strings I'm talking about have actual content and are terminated by '\0'. Concatenating those strings and passing them to non-managed dependencies will result in data loss (as in my case).
Comment 4 André Klapper 2018-08-17 19:50:22 UTC 
taglib-sharp has moved to Github a while ago.
Furthermore, GNOME Bugzilla will be shut down and replaced by gitlab.gnome.org.

If the problem reported in this Bugzilla ticket is still valid, please report
it to https://github.com/mono/taglib-sharp/issues instead. Thank you!

Closing this report as WONTFIX as part of Bugzilla Housekeeping.