Bug 2116200 - [abrt] rhythmbox: g_type_check_instance_is_a(): rhythmbox killed by SIGSEGV
Summary: [abrt] rhythmbox: g_type_check_instance_is_a(): rhythmbox killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 36
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:59569e4a7959ed2291f9f655fde...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-07 22:56 UTC by Brian J. Murrell
Modified: 2023-05-25 15:30 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 15:30:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (63.70 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: core_backtrace (27.91 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: cpuinfo (2.50 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: dso_list (588 bytes, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: environ (2.60 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: exploitable (82 bytes, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: limits (1.29 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: maps (3.90 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: mountinfo (3.98 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: open_fds (63.98 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details
File: proc_pid_status (1.41 KB, text/plain)
2022-08-07 22:56 UTC, Brian J. Murrell
no flags Details

Description Brian J. Murrell 2022-08-07 22:56:00 UTC
Description of problem:
I was re-uploading existing tracks to an Android device.

Version-Release number of selected component:
rhythmbox-3.4.6-1.fc36

Additional info:
reporter:       libreport-2.17.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1001.slice/user/app.slice/app-gnome-org.gnome.Rhythmbox3-4222.scope
cmdline:        rhythmbox
crash_function: g_type_check_instance_is_a
executable:     /usr/bin/rhythmbox
journald_cursor: s=3c934fc4fd2c43899323402faebb06b1;i=116f;b=5e747ead97854be0874505b59ec4d450;m=7d56d22b;t=5e5adcb328f33;x=68d9e82d75a37921
kernel:         5.18.16-200.fc36.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1001

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_is_a at ../gobject/gtype.c:4081
 #1 _gtk_style_animation_is_static at ../gtk/gtkstyleanimation.c:120
 #2 gtk_css_animated_style_is_static at ../gtk/gtkcssanimatedstyle.c:74
 #3 gtk_css_node_invalidate_timestamp at ../gtk/gtkcssnode.c:1333
 #16 gtk_css_node_invalidate_frame_clock at ../gtk/gtkcssnode.c:1350
 #17 gtk_css_widget_node_queue_callback at ../gtk/gtkcsswidgetnode.c:64
 #18 gtk_widget_on_frame_clock_update at ../gtk/gtkwidget.c:5287
 #19 _g_closure_invoke_va at ../gobject/gclosure.c:893
 #22 _gdk_frame_clock_emit_update at ../gdk/gdkframeclock.c:645
 #23 gdk_frame_clock_paint_idle at ../gdk/gdkframeclockidle.c:547

Comment 1 Brian J. Murrell 2022-08-07 22:56:04 UTC
Created attachment 1904196 [details]
File: backtrace

Comment 2 Brian J. Murrell 2022-08-07 22:56:05 UTC
Created attachment 1904197 [details]
File: core_backtrace

Comment 3 Brian J. Murrell 2022-08-07 22:56:06 UTC
Created attachment 1904198 [details]
File: cpuinfo

Comment 4 Brian J. Murrell 2022-08-07 22:56:07 UTC
Created attachment 1904199 [details]
File: dso_list

Comment 5 Brian J. Murrell 2022-08-07 22:56:08 UTC
Created attachment 1904200 [details]
File: environ

Comment 6 Brian J. Murrell 2022-08-07 22:56:09 UTC
Created attachment 1904201 [details]
File: exploitable

Comment 7 Brian J. Murrell 2022-08-07 22:56:11 UTC
Created attachment 1904202 [details]
File: limits

Comment 8 Brian J. Murrell 2022-08-07 22:56:12 UTC
Created attachment 1904203 [details]
File: maps

Comment 9 Brian J. Murrell 2022-08-07 22:56:13 UTC
Created attachment 1904204 [details]
File: mountinfo

Comment 10 Brian J. Murrell 2022-08-07 22:56:14 UTC
Created attachment 1904205 [details]
File: open_fds

Comment 11 Brian J. Murrell 2022-08-07 22:56:15 UTC
Created attachment 1904206 [details]
File: proc_pid_status

Comment 12 Ben Cotton 2023-04-25 17:44:13 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
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 '36'.

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. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 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 13 Ludek Smid 2023-05-25 15:30:19 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 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.


Note You need to log in before you can comment on or make changes to this bug.