Bug 1241925
Summary: | rhythmbox segfaults after closing | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Simon <msimon> |
Component: | rhythmbox | Assignee: | Bastien Nocera <bnocera> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | isenfeld, jprajzne, leonard-rh-bugzilla, mcepl, mclasen, pza, tpelka |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 06:04:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1295396, 1297830, 1313485 |
Description
Martin Simon
2015-07-10 12:35:16 UTC
version of component: rhythmbox-2.99.1-4.el7.x86_64 Also experienced this after upgrading to this version. Clearing the DB, etc didn't help. (In reply to Phil Anderson from comment #2) > Also experienced this after upgrading to this version. Clearing the DB, etc > didn't help. There are no fixes in rhythmbox for RHEL 7.2, targetting this for 7.3 instead. Possible duplicate (w/backtraces) is bug 1260578, isn't it? It seems the fix I propose for bug 1241924 also fixes this issue. https://git.gnome.org/browse/rhythmbox/commit/?id=b65b762176f159a65b4468cf4bc4635de8872573 Without this patch indeed rhythmbox segfaults on exit. With the patch applied this segfault also disappears. So even though it is not clear when looking at the problem descriptions I do believe this to be a duplicate of 1241924. Rhythmbox was rebased in bug 1298233. Can you please retest with the new build to see whether this fixes your problem? Using the build rhythmbox-3.3.1-1.el7 I'm longer able to reproduce the crash. It seems that the rebase fixed the bug. Marking as MODIFIED, as the build is already done. Just that RB still produces a lot of warnings. Does any of these make some sense? matej@mitmanek: rpms$ rhythmbox (rhythmbox:17522): libsoup-CRITICAL **: soup_server_quit: assertion 'priv->listeners != NULL' failed (rhythmbox:17522): GLib-GObject-CRITICAL **: object SoupServer 0x2f5b2a0 finalized while still in-construction (rhythmbox:17522): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead. (rhythmbox:17522): libsoup-CRITICAL **: soup_server_quit: assertion 'priv->listeners != NULL' failed (rhythmbox:17522): GLib-GObject-CRITICAL **: object SoupServer 0x2f5b340 finalized while still in-construction (rhythmbox:17522): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead. (rhythmbox:17522): libsoup-CRITICAL **: soup_server_quit: assertion 'priv->listeners != NULL' failed (rhythmbox:17522): GLib-GObject-CRITICAL **: object SoupServer 0x2f5b480 finalized while still in-construction (rhythmbox:17522): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Please use GInitable instead. (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist (rhythmbox:17522): Gtk-WARNING **: Duplicate child name in GtkStack: Add to Playlist Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (rhythmbox:17522): Gtk-WARNING **: mnemonic "s" wasn't removed for widget (0x267a690) matej@mitmanek: rpms$ The bug is no longer present. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2408.html |