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 449827 - Rhythmbox - editing ID3 tags fails with special characters
Rhythmbox - editing ID3 tags fails with special characters
Status: RESOLVED DUPLICATE of bug 381857
Product: rhythmbox
Classification: Other
Component: Programmatic interfaces
0.9.6
Other other
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-21 17:12 UTC by software
Modified: 2014-12-02 01:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description software 2007-06-21 17:12:52 UTC
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Rhythmbox - editing ID3 tags fails with special characters

Distribution: Debian 4.0
Package: rhythmbox
Severity: Normal
Version: GNOME2.14.3 0.9.6
Gnome-Distributor: Debian
Synopsis: Rhythmbox - editing ID3 tags fails with special characters
Bugzilla-Product: rhythmbox
Bugzilla-Component: Programmatic interfaces
Bugzilla-Version: 0.9.6
Description:
Description of Problem:
I download several podcasts from the web, and want to adjust their ID3
tags so my player handles them correctly. While editing the tags in
Rhythmbox, I get a pop-up message that reads "Error while saving song
information. Internal GStreamer problem; file a bug." It only seems to
happen when fields of the ID3 tag have the '#' or '&' character in
them...

Steps to reproduce the problem:
1. download this file: http://www.yog-sothoth.com/docs/yog-radio-1.mp3
2. change the 'Artist' field to 'YSDC'
3. click 'Close' to save the edits - the dialog will pop up.

Actual Results:
No edits take place. The file is unaffected.

Expected Results:
I expected the Artist field to be changed to 'YSDC'.

How often does this happen?
Everytime - regardless of the amount of edits.

Additional Information:
The field being edited does not contain the special character; the
Title field contains the '#' character. Potentially, this could also
be related to the length of each string in the individual fields.
(Size problem.)




------- Bug created by bug-buddy at 2007-06-21 17:12 -------

Comment 1 Jonathan Matthew 2007-06-21 22:48:05 UTC
Works fine here.

The error message indicates that the metadata helper process crashed while trying to update the file.  This is usually a problem in GStreamer somewhere.  What versions of libgstreamer0.10-0, gstreamer0.10-plugins-base, gstreamer0.10-plugins-good, and whatever provides /usr/lib/libtag.so.1 do you have installed?
Comment 2 software 2007-06-23 01:05:31 UTC
libgstreamer0.10-0 version 0.10.10-3 is installed
gstreamer0.10-plugins-base version 0.10.10-4 is installed
gstreamer0.10-plugins-good version 0.10.4-4 is installed
libtag is installed in the libtag1c2a package with version 1.4-4

Is there anything else you might need information on? Being a standard Debian distribution, the updates are a little slower than Ubuntu.

Comment 3 Jonathan Matthew 2007-06-23 14:08:06 UTC
This is quite likely to be a duplicate of bug 381857, which was fixed in gst-plugins-good 0.10.5.  To confirm this:

- bring up the properties window for the file
- open an xterm, run 'gdb /usr/lib/rhythmbox/rhythmbox-metadata `pidof rhythmbox-metadata`' and type 'continue' at the gdb prompt
- edit the file's properties and hit the close button
- type 'thread apply all bt' at the gdb prompt and paste the output into this bug
Comment 4 software 2007-06-23 15:28:37 UTC
(gdb) thread apply all bt

Thread 1 (Thread -1225783616 (LWP 11494))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 poll
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #7 main
  • #0 ??

=================================
Mr. Matthew - looks like you were right about the version of gst-plugins-good. I'll update that library with the later version and see if this addresses the problem.

More as I get it --
Comment 5 André Klapper 2014-12-02 01:32:17 UTC
No reply by reporter; assuming this is a dup of fixed bug 381857.

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