Bug 1068995

Summary: [abrt] totem: find_media(): totem killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Elad Alfassa <elad>
Component: totemAssignee: Bastien Nocera <bnocera>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bnocera
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b8e2e013a6a2e0b482d5fdf3f3c8cfb311a2e0cb
Whiteboard: abrt_hash:20ed5ff98e9928c8be6dc1b96934a05b023b1867
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:03:54 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Elad Alfassa 2014-02-23 22:13:11 UTC 
Description of problem:
Start totem.

Version-Release number of selected component:
totem-3.11.90-2.fc21

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        totem
crash_function: find_media
executable:     /usr/bin/totem
kernel:         3.13.3-201.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 find_media at totem-grilo.c:1101
 #1 content_changed at totem-grilo.c:1130
 #2 content_changed_cb at totem-grilo.c:1184
 #7 grl_source_notify_change_list at grl-source.c:4433
 #8 container_changed_cb at grl-upnp.c:329
 #9 emit_notification at gupnp-service-proxy.c:1742
 #10 emit_notifications_for_doc at gupnp-service-proxy.c:1773
 #11 emit_notifications at gupnp-service-proxy.c:1823
 #15 g_main_context_iteration at gmain.c:3773
 #16 grl_wait_for_async_operation_complete at grl-sync.c:36
Comment 1 Elad Alfassa 2014-02-23 22:13:18 UTC 
Created attachment 866789 [details]
File: backtrace
Comment 2 Elad Alfassa 2014-02-23 22:13:21 UTC 
Created attachment 866790 [details]
File: cgroup
Comment 3 Elad Alfassa 2014-02-23 22:13:24 UTC 
Created attachment 866791 [details]
File: core_backtrace
Comment 4 Elad Alfassa 2014-02-23 22:13:26 UTC 
Created attachment 866792 [details]
File: dso_list
Comment 5 Elad Alfassa 2014-02-23 22:13:29 UTC 
Created attachment 866793 [details]
File: environ
Comment 6 Elad Alfassa 2014-02-23 22:13:31 UTC 
Created attachment 866794 [details]
File: exploitable
Comment 7 Elad Alfassa 2014-02-23 22:13:34 UTC 
Created attachment 866795 [details]
File: limits
Comment 8 Elad Alfassa 2014-02-23 22:13:37 UTC 
Created attachment 866796 [details]
File: maps
Comment 9 Elad Alfassa 2014-02-23 22:13:40 UTC 
Created attachment 866797 [details]
File: open_fds
Comment 10 Elad Alfassa 2014-02-23 22:13:42 UTC 
Created attachment 866798 [details]
File: proc_pid_status
Comment 11 Elad Alfassa 2014-02-23 22:13:44 UTC 
Created attachment 866799 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:31:25 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:03:54 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.