Bug 1729920

Summary: [abrt] dleyna-renderer: g_hash_table_lookup_node(): dleyna-renderer-service killed by SIGSEGV
Product: [Fedora] Fedora Reporter: hamid jahadi <jahadi.hamid>
Component: dleyna-rendererAssignee: Debarshi Ray <debarshir>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: debarshir
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4097ed3f700e9345579486b922b00aef5eb7b0ed
Whiteboard: abrt_hash:835241be642a7c495a2dbd149d5e507763bd4f85;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 16:10:05 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: cgroup
none
File: core_backtrace
none
File: cpuinfo none

Description hamid jahadi 2019-07-15 10:30:37 UTC
Version-Release number of selected component:
dleyna-renderer-0.6.0-4.fc30

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        /usr/libexec/dleyna-renderer-service
crash_function: g_hash_table_lookup_node
executable:     /usr/libexec/dleyna-renderer-service
journald_cursor: s=6ea543c672dc4666acac12c25e3d864c;i=85f2;b=5035ea74231b4e2891809217f275b2eb;m=1532a5173b;t=58db5579654be;x=e39b1498b56e8666
kernel:         5.1.16-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 g_hash_table_lookup_node at ../glib/ghash.c:471
 #1 g_hash_table_lookup at ../glib/ghash.c:1507
 #2 dleyna_task_queue_task_completed at libdleyna/core/task-processor.c:453
 #3 dlr_async_task_complete at async.c:48
 #9 dleyna_main_loop_start at libdleyna/core/main-loop.c:158

Potential duplicate: bug 1688623

Comment 1 hamid jahadi 2019-07-15 10:30:41 UTC
Created attachment 1590691 [details]
File: backtrace

Comment 2 hamid jahadi 2019-07-15 10:30:43 UTC
Created attachment 1590692 [details]
File: cgroup

Comment 3 hamid jahadi 2019-07-15 10:30:45 UTC
Created attachment 1590693 [details]
File: core_backtrace

Comment 4 hamid jahadi 2019-07-15 10:30:46 UTC
Created attachment 1590694 [details]
File: cpuinfo

Comment 5 Ben Cotton 2020-04-30 21:33:36 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 '30'.

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 30 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 6 Ben Cotton 2020-05-26 16:10:05 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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 7 Debarshi Ray 2020-10-19 19:57:56 UTC

*** This bug has been marked as a duplicate of bug 1824719 ***