Bug 1832484

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Is this issue still reproducible ?

This issue does not occur so often any more in the current Rawhide.

This shouldn't happen. It could be a gstreamer issue. Not sure.

Next time if the issue happens start rhythmbox from terminal, as below and attach rhythmbox.log in the bug report.

$ rhythmbox -d &> rhythmbox.log

Created attachment 1714642 [details]
rhythmbox -d &> rhythmbox.log

Rhythmbox is not responding again. Text Buffering can be seen.

rhythmbox.log contains:

(18:03:20) [0x7f6054004b80] [rb_debug_init_match] rb-debug.c:240: Debugging enabled
(rhythmbox:4242): Rhythmbox-CRITICAL **: 18:03:45.094: Timeout was reached

This doesn't help, as there is no information. There is some other issue here.

Can you try the following in terminal:

1. Install gdb using the following command ( as root ):

# dnf install gdb

2. Install rhythmbox debug symbols using the following command ( as root ):

# dnf install rhythmbox-debuginfo

3. Start rhythmbox ( as normal user ):

$ rhythmbox
 
4. Attach to running rhythmbox process via gdb using the following command ( as normal user ):

$ gdb $(which rhythmbox ) -p $(pgrep -x rhythmbox)

5. Get rhythmbox backtrace information: 

(gdb) thread apply all bt full

6. Attach output of above command as attachment here.

Created attachment 1714647 [details]
(gdb) thread apply all bt full

Thanks for the information.

The backtrace has identified the issue, although a backtrace with debug symbols would be more helpful in fixing the issue faster.

There are 2 issues:

1. The radio stream gets into error state.

2. Rhythmbox hangs when [1] happens, which is a separate upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1806

So, the real issue as far as this bug is concerned, is why do we enter in to error state. 

As I cannot reproduce the issue in latest FC rawhide, can you do the following:

1. Get a backtrace with rhythmbox debug package installed, following the steps described in the previous comment.

2. Try the following again in terminal:

    1. Start rhythmbox using the following command.
 
       $ rhythmbox -d 

    2. Attach the debug output here. It should be a close to 100 lines, 2 lines is not enough.

3. Exact steps for reproducing the issue.

4. Does it happen with all radio stations, or a specific one.

5. The radio station that caused the issue. Can you paste the station URL here. ( Right click -> Properties ).

1. dnf did not find rhythmbox-debuginfo.

3. I just started streaming an Internet radio station over WiFi on HP EliteBook 8730w.

4. It has happened with at least two radio stations.

5. Yesterday I got it twice with http://stream.kaaosradio.fi:8000/stream

1. Are you using normal Fedora -or- Fedora SilverBlue -or- Fedora LTO

2. dnf did not find rhythmbox-debuginfo.

Sorry. Can you try this as root user:

# dnf debuginfo-install rhythmbox

This should enable the debug repos.

3. Yesterday I got it twice with http://stream.kaaosradio.fi:8000/stream

I am not getting any errors in FC34 rawhide. How long after starting the station does it happen ( immediately  -or- 'x' minutes after starting ) 

4. Kindly attach the debug output of the following command. It should be lot of output like: 

$ rhythmbox -d
(13:51:10) [0x5633778fe4f0] [rb_debug_init_match] rb-debug.c:240: Debugging enabled
(13:51:10) [0x5633778fe4f0] [construct_db] rb-shell.c:453: creating database object
(13:51:11) [0x5633778fe4f0] [impl_constructor] rb-ext-db.c:353: creating new metadata store instance album-art
(13:51:11) [0x5633778fe4f0] [rb_shell_constructed] rb-shell.c:1696: Constructing shell
(13:51:11) [0x5633778fe4f0] [construct_widgets] rb-shell.c:536: shell: initializing shell services
(13:51:11) [0x5633778fe4f0] [rb_podcast_manager_constructed] rb-podcast-manager.c:298: podcast timestamp file already exists
(13:51:11) [0x5633778fe4f0] [impl_constructor] rb-ext-db.c:348: found existing metadata store album-art
(13:51:11) [0x5633778fe4f0] [rb_podcast_manager_start_update_timer] rb-podcast-manager.c:580: periodic podcast updates disabled
(13:51:11) [0x5633778fe4f0] [player_settings_changed_cb] rb-shell-player.c:922: track transition time changed
(13:51:11) [0x5633778fe4f0] [player_settings_changed_cb] rb-shell-player.c:913: play order setting changed
...
...
more lines.

Created attachment 1714670 [details]
Cannot reproduce issue in FC 34 rawhide

Cannot reproduce issue in FC 34 rawhide.

For help on getting stack traces, please refer:

https://fedoraproject.org/wiki/StackTraces

1. I am using normal Fedora Workstation.

2. The hanging happens randomly after some streaming or not at all every day, not immediately.

Created attachment 1714675 [details]
rhythmbox -d > rhythmbox.log 2>&1; head -1000 rhythmbox.log  > rhythmbox1000.log

Okay.

1. The log file looks normal ( playing without hang bug ). We need a logs around the time, when the bug happens. I know it is difficult, as it is not frequently reproducible. But try starting rhythmbox via 'rhythmbox -d' for a couple of days. When rhythmbox hangs, close rhythmbox, and attach rhythmbox.log

2. Also, no need to do a "head -1000". We are more interested in the last part of the log ( not the initial part ). If the log file is too big, you can zip it, and attach here.

3. Much easier way would be to do a gdb attach and get backtrace, when rhythmbox hangs. Did "dnf debuginfo-install rhythmbox" install the debug symbols now ?

Thanks !

Created attachment 1714685 [details]
rhythmbox -d > rhythmbox.log 2>&1

Rhythmbox now shows "Server does not support seeking." more often than hangs.

Okay.

"Server does not support seeking." is addressed as part of https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1512.

Can you try and see if you can get the original error. Also, PLEASE DON'T truncate the log file. Attach the zipped version of the log file, if it gets bigger.

Thanks !

Created attachment 1714976 [details]
(gdb) thread apply all bt full after hanging

Created attachment 1714977 [details]
rhythmbox -d > rhythmbox.log 2>&1 when hanging

Great. Will take a look. This is tracked in the following 2 upstream bugs. You can follow it there.

https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/-/issues/763
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1512

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.