Bug 1813753

Summary: [abrt] rhythmbox: __poll(): rhythmbox killed by SIGABRT
Product: [Fedora] Fedora Reporter: robert fairbrother <noobusinghacks>
Component: rhythmboxAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: amigadave, caillon+fedoraproject, crvisqr, dwmw2, gnome-sig, john.j5live, mclasen, rhughes, rstrode, sandmann, triad
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0ee6225eb0dea9dade4292434e1b4116b2544088
Whiteboard: abrt_hash:96d53678ed2538cf49ab7f3dd6e7028270b7b4d1;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:14:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description robert fairbrother 2020-03-16 00:57:29 UTC 
Description of problem:
it was frozen so i killed it with ABRT then i had to report it 3 times

Version-Release number of selected component:
rhythmbox-3.4.4-1.fc31

Additional info:
reporter:       libreport-2.12.0
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/gnome-launched-rhythmbox.desktop-295295.scope
cmdline:        rhythmbox
crash_function: __poll
executable:     /usr/bin/rhythmbox
journald_cursor: s=3ea583ffcaf14a97be2b0f431177f960;i=1b82e3;b=1add0bc910ec470b866d6dc01448ffb5;m=1f9e2eeadf;t=5a0eceb5daaa0;x=6a6adbc7b062b5c2
kernel:         5.5.8-200.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 __poll at ../sysdeps/unix/sysv/linux/poll.c:29
 #1 g_main_context_poll at ../glib/gmain.c:4253
 #3 g_main_context_iteration at ../glib/gmain.c:4015
 #4 g_application_run at ../gio/gapplication.c:2559
 #5 rb_application_run at rb-application.c:595
Comment 1 robert fairbrother 2020-03-16 00:57:33 UTC 
Created attachment 1670381 [details]
File: backtrace
Comment 2 robert fairbrother 2020-03-16 00:57:34 UTC 
Created attachment 1670382 [details]
File: core_backtrace
Comment 3 robert fairbrother 2020-03-16 00:57:35 UTC 
Created attachment 1670383 [details]
File: cpuinfo
Comment 4 robert fairbrother 2020-03-16 00:57:36 UTC 
Created attachment 1670384 [details]
File: dso_list
Comment 5 robert fairbrother 2020-03-16 00:57:38 UTC 
Created attachment 1670385 [details]
File: environ
Comment 6 robert fairbrother 2020-03-16 00:57:39 UTC 
Created attachment 1670386 [details]
File: limits
Comment 7 robert fairbrother 2020-03-16 00:57:41 UTC 
Created attachment 1670387 [details]
File: maps
Comment 8 robert fairbrother 2020-03-16 00:57:42 UTC 
Created attachment 1670388 [details]
File: mountinfo
Comment 9 robert fairbrother 2020-03-16 00:58:15 UTC 
Created attachment 1670389 [details]
File: open_fds
Comment 10 robert fairbrother 2020-03-16 00:58:16 UTC 
Created attachment 1670390 [details]
File: proc_pid_status
Comment 11 robert fairbrother 2020-09-30 10:57:09 UTC 
Similar problem has been detected:

may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1883801

reporter:       libreport-2.13.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/gnome-launched-rhythmbox.desktop-415216.scope
cmdline:        rhythmbox
crash_function: __poll
executable:     /usr/bin/rhythmbox
journald_cursor: s=2c413e762bf64ca8a7cef5edd3532cd4;i=dde1;b=80d9e0a176e6421b83358876ed3f6fe2;m=47025a7f80;t=5b0853731a27c;x=96f903c2ee46f008
kernel:         5.8.10-100.fc31.x86_64
package:        rhythmbox-3.4.4-1.fc31
reason:         rhythmbox killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 12 Ben Cotton 2020-11-03 16:29:35 UTC 
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.
Comment 13 Ben Cotton 2020-11-24 15:18:09 UTC 
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.
Comment 14 crvi 2021-04-13 15:44:18 UTC 
> it was frozen so i killed it with ABRT then i had to report it 3 times

From the stack trace, the main thread is still in working state, which means the bug description of a "rhythmbox hang" is incorrect.

It is obvious that rhythmbox was trying to stream a few radio streams as below:

        uri = 0x7fb2180112c0 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://mediaserv30.live-streams.nl:8088/live.m3u&t=.pls"
        uri = 0x7fb1c8025bf0 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8046/listen.pls&t=.pls"
        uri = 0x7fb1f800b420 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8046/listen.pls&t=.pls"
        uri = 0x7fb1d40b2f30 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8046/listen.pls&t=.pls"
        uri = 0x7fb1a0001bd0 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8443/listen.pls&t=.pls"
        uri = 0x558e38285a20 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8443/listen.pls&t=.pls"
        uri = 0x7fb1ec02cd30 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://mediaserv30.live-streams.nl:8088/live.m3u&t=.pls"
        uri = 0x7fb2080047b0 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://uk2.internet-radio.com:30075/live.m3u&t=.pls"
        uri = 0x7fb210001c00 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://mediaserv30.live-streams.nl:8088/live.m3u&t=.pls"
        uri = 0x7fb1f40061e0 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8046/listen.pls&t=.pls"
        uri = 0x7fb1fc004690 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8443/listen.pls&t=.pls"
        uri = 0x7fb1a8001770 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8443/listen.pls&t=.pls"
        uri = 0x7fb1a0001360 "https://www.internet-radio.com/servers/tools/playlistgenerator/?u=http://us2.internet-radio.com:8443/listen.pls&t=.pls"


But that should not cause a rhythmbox process hang, as the streaming / playing is done in separate threads.

If this issue is reproducible still, please provide some steps on how to reproduce it.

Thanks!
Comment 15 Ben Cotton 2021-08-10 12:47:27 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.
Comment 16 Ben Cotton 2022-11-29 16:47:59 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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
'version' of '35'.

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

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 17 Ben Cotton 2022-12-13 15:14:34 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 18 Red Hat Bugzilla 2023-09-18 00:20:31 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days