Bug 1462492 - Rhythmbox can't read Ogg Vorbis tags after files have been tagged by certain applications.
Rhythmbox can't read Ogg Vorbis tags after files have been tagged by certain ...
Status: NEW
Product: Fedora
Classification: Fedora
Component: rhythmbox (Show other bugs)
26
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: David King
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-18 01:00 EDT by Ryan Farmer
Modified: 2017-06-18 01:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Farmer 2017-06-18 01:00:35 EDT
Description of problem:

After I edit the tags on Ogg Vorbis files using Easytag, Picard, or Foobar2000 Rhythmbox often can't read the tags. Rhythmbox won't import the files into my music library or sometimes can't play back the file at all.

I've tried using Easytag to tag FLAC files to see if the same issue happens with FLAC, and it does not.

It also doesn't happen when I use Easytag to tag an MP3.


Version-Release number of selected component (if applicable):

3.4.1


How reproducible:

Tag some Ogg Vorbis files with Easytag, Picard, or Foobar2000 and then try to import them into Rhythmbox.


Actual results:

Many of the files will no longer be imported by Rhythmbox or will end up imported under "Unknown". Also, trying to fix the files by editing the tags with Rhythmbox doesn't work. 

Expected results:

Rhythmbox imports the files correctly. 

Additional info:

On files that I tried to tag with Rhythmbox, I opened some of them in Foobar2000 and it shows random junk in the tag fields. So not only is Rhythmbox still not seeing them, it's actually making the problem worse.

Note You need to log in before you can comment on or make changes to this bug.