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 760138 - moving the progressbar in soundcloud locks up the whole interface
moving the progressbar in soundcloud locks up the whole interface
Product: rhythmbox
Classification: Other
Component: Plugins (other)
Other Linux
: Normal major
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Reported: 2016-01-04 23:58 UTC by foss.freedom
Modified: 2018-05-24 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---

gdb backtrace (102.23 KB, text/plain)
2016-01-06 21:30 UTC, foss.freedom
rhythmbox -d trace (58.89 KB, text/plain)
2016-01-06 21:31 UTC, foss.freedom

Description foss.freedom 2016-01-04 23:58:30 UTC
To repeat

1. play a song from the music library
2. click on the sound-cloud plugin
3. search for "star wars"
4. double click something that is found - this begins playing
5. move the progressbar - for example half way
6. The whole GUI interface freezes
Comment 1 Jonathan Matthew 2016-01-05 09:14:14 UTC
works fine for me.
Comment 2 foss.freedom 2016-01-06 21:30:35 UTC
Created attachment 318385 [details]
gdb backtrace
Comment 3 foss.freedom 2016-01-06 21:31:14 UTC
Created attachment 318386 [details]
rhythmbox -d trace
Comment 4 foss.freedom 2016-01-06 21:32:56 UTC
I've added a couple of traces.

first is a gdb backtrace captured at the UI freeze.

the second is a rhythmbox -d trace showing starting playing from the library - then single click to soundcloud - search for "star wars" - double click the first result - single click somewhere in the middle in the progress slider bar.
Comment 5 GNOME Infrastructure Team 2018-05-24 18:40:40 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: