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 692158 - Rhythmbox crashes when changing internet radio station genre
Rhythmbox crashes when changing internet radio station genre
Status: RESOLVED FIXED
Product: rhythmbox
Classification: Other
Component: Internet Radio
2.98
Other Linux
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 693672 695651 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-01-21 00:40 UTC by mark.z.harrison
Modified: 2016-09-19 04:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Output of "rhythmbox -d" (236.60 KB, application/x-bzip)
2013-01-21 00:40 UTC, mark.z.harrison
Details

Description mark.z.harrison 2013-01-21 00:40:23 UTC
Created attachment 233973 [details]
Output of "rhythmbox -d"

When editing the genres of internet radio stations, if the last station in a certain genre is moved to another genre, rhythmbox crashes with the following message:

(rhythmbox:15132): RhythmDB-WARNING **: trying to sync properties of non-editable file
**
RhythmDB:ERROR:rhythmdb-property-model.c:855:rhythmdb_property_model_delete_prop: assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))
Aborted (core dumped)

For a specific example, the Rock'n'Roll genre contains two stations:
Absolute Classic Rock (Broadband)
Absolute Classic Rock (Modem)

Right-click one, select "Properties..." and change the genre to "Rock".  This works fine.  But, do the same to the other one, and rhythmbox crashes.  If a genre has only one station, changing the genre causes a crash as well.

I've attached the complete output of "rhythmbox -d".
Comment 1 Jonathan Matthew 2013-02-17 21:37:42 UTC
*** Bug 693672 has been marked as a duplicate of this bug. ***
Comment 2 mark.z.harrison 2013-02-20 10:38:53 UTC
This bug is not present in 2.97.
Comment 3 Jonathan Matthew 2013-03-04 13:23:26 UTC
commits 6a157fd and fa4a7ff fix this.
Comment 4 Jonathan Matthew 2013-03-11 20:38:36 UTC
*** Bug 695651 has been marked as a duplicate of this bug. ***