Bug 1202052

Summary: [abrt] dleyna-server: dls_device_unsubscribe(): dleyna-server-service killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Joseph Bowman <jbowm16>
Component: dleyna-serverAssignee: Debarshi Ray <debarshir>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: code, debarshir, lray+redhatbugzilla, pranav913, rnfano2, tomek
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/26e356f01f3f378467efab65c9f3fd3e884cfe6e
Whiteboard: abrt_hash:adbbffa1b97974c91840e2bd21bafb57c4a6484d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 13:02:45 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: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Joseph Bowman 2015-03-14 20:21:17 UTC 
Description of problem:
This occured when attempting to logon to the Wayland session on Fedora 22 Alpha 3; fully up to date as of March 14 2015. Beyond that, I am not sure.

Version-Release number of selected component:
dleyna-server-0.4.0-7.fc22

Additional info:
reporter:       libreport-2.4.0
backtrace_rating: 4
cmdline:        /usr/libexec/dleyna-server-service
crash_function: dls_device_unsubscribe
executable:     /usr/libexec/dleyna-server-service
kernel:         4.0.0-0.rc1.git0.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 dls_device_unsubscribe at device.c:272
 #1 dls_upnp_unsubscribe at upnp.c:1102
 #2 prv_control_point_stop_service at server.c:1322
 #3 prv_context_quit_cb at libdleyna/core/main-loop.c:61
 #8 dleyna_main_loop_start at libdleyna/core/main-loop.c:155
Comment 1 Joseph Bowman 2015-03-14 20:21:19 UTC 
Created attachment 1001806 [details]
File: backtrace
Comment 2 Joseph Bowman 2015-03-14 20:21:20 UTC 
Created attachment 1001807 [details]
File: cgroup
Comment 3 Joseph Bowman 2015-03-14 20:21:21 UTC 
Created attachment 1001808 [details]
File: core_backtrace
Comment 4 Joseph Bowman 2015-03-14 20:21:22 UTC 
Created attachment 1001809 [details]
File: dso_list
Comment 5 Joseph Bowman 2015-03-14 20:21:22 UTC 
Created attachment 1001810 [details]
File: environ
Comment 6 Joseph Bowman 2015-03-14 20:21:23 UTC 
Created attachment 1001811 [details]
File: limits
Comment 7 Joseph Bowman 2015-03-14 20:21:24 UTC 
Created attachment 1001812 [details]
File: maps
Comment 8 Joseph Bowman 2015-03-14 20:21:25 UTC 
Created attachment 1001813 [details]
File: open_fds
Comment 9 Joseph Bowman 2015-03-14 20:21:26 UTC 
Created attachment 1001814 [details]
File: proc_pid_status
Comment 10 Joseph Bowman 2015-03-14 20:21:27 UTC 
Created attachment 1001815 [details]
File: var_log_messages
Comment 11 Tomasz Torcz 2015-07-15 16:06:03 UTC 
Another user experienced a similar problem:

Nothing

reporter:       libreport-2.6.1
backtrace_rating: 4
cmdline:        /usr/libexec/dleyna-server-service
crash_function: dls_device_unsubscribe
executable:     /usr/libexec/dleyna-server-service
global_pid:     23782
kernel:         4.0.7-300.fc22.x86_64
package:        dleyna-server-0.4.0-7.fc22
reason:         dleyna-server-service killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1001
Comment 12 Fedora End Of Life 2016-07-19 13:02:45 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 13 Debarshi Ray 2016-09-16 14:56:52 UTC 

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