Bug 1026297

Summary: [abrt] gtkpod-2.1.3-2.fc19: __pthread_mutex_trylock: Process /usr/bin/gtkpod was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: barrodaniele8 <barrodaniele8>
Component: gtkpodAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: chkr, gwync
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/95152166e732a504c3a360e6eeafe96b68498409
Whiteboard: abrt_hash:f7e60948e917b0539b20066dc40ed94b6ecb64b4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:01:50 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 barrodaniele8@gmail.com 2013-11-04 11:27:36 UTC
Version-Release number of selected component:
gtkpod-2.1.3-2.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 3
cmdline:        gtkpod
crash_function: __pthread_mutex_trylock
executable:     /usr/bin/gtkpod
kernel:         3.11.6-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 __pthread_mutex_trylock at pthread_mutex_trylock.c:33
 #1 g_mutex_trylock at gthread-posix.c:254
 #2 _try_lock at file_convert.c:292
 #3 conversion_scheduler at file_convert.c:1671
 #9 gtk_clipboard_store at gtkclipboard.c:2118
 #10 _gtk_clipboard_store_all at gtkclipboard.c:2154
 #11 gtk_main at gtkmain.c:1172

Potential duplicate: bug 973400

Comment 1 barrodaniele8@gmail.com 2013-11-04 11:27:43 UTC
Created attachment 819084 [details]
File: backtrace

Comment 2 barrodaniele8@gmail.com 2013-11-04 11:27:46 UTC
Created attachment 819085 [details]
File: cgroup

Comment 3 barrodaniele8@gmail.com 2013-11-04 11:27:49 UTC
Created attachment 819086 [details]
File: core_backtrace

Comment 4 barrodaniele8@gmail.com 2013-11-04 11:27:53 UTC
Created attachment 819087 [details]
File: dso_list

Comment 5 barrodaniele8@gmail.com 2013-11-04 11:27:56 UTC
Created attachment 819088 [details]
File: environ

Comment 6 barrodaniele8@gmail.com 2013-11-04 11:27:59 UTC
Created attachment 819089 [details]
File: exploitable

Comment 7 barrodaniele8@gmail.com 2013-11-04 11:28:01 UTC
Created attachment 819090 [details]
File: limits

Comment 8 barrodaniele8@gmail.com 2013-11-04 11:28:06 UTC
Created attachment 819091 [details]
File: maps

Comment 9 barrodaniele8@gmail.com 2013-11-04 11:28:09 UTC
Created attachment 819092 [details]
File: open_fds

Comment 10 barrodaniele8@gmail.com 2013-11-04 11:28:12 UTC
Created attachment 819093 [details]
File: proc_pid_status

Comment 11 barrodaniele8@gmail.com 2013-11-04 11:28:15 UTC
Created attachment 819094 [details]
File: var_log_messages

Comment 12 Fedora End Of Life 2015-01-09 20:27:09 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 13 Fedora End Of Life 2015-02-17 19:01:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.