Bug 1123567 - [abrt] fros: util.py:233:_findSoname_ldconfig:OSError: [Errno 11] Resource temporarily unavailable
Summary: [abrt] fros: util.py:233:_findSoname_ldconfig:OSError: [Errno 11] Resource te...
Alias: None
Product: Fedora
Classification: Fedora
Component: fros
Version: 20
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:42180a16a7fe8e854174463ef21...
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-26 17:15 UTC by Vango Stavro
Modified: 2016-12-01 00:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 21:46:28 UTC

Attachments (Terms of Use)
File: backtrace (895 bytes, text/plain)
2014-07-26 17:15 UTC, Vango Stavro
no flags Details
File: environ (1.90 KB, text/plain)
2014-07-26 17:15 UTC, Vango Stavro
no flags Details

Description Vango Stavro 2014-07-26 17:15:26 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.2.2
cmdline:        /usr/bin/python /usr/bin/fros --is-available
dso_list:       python-libs-2.7.5-13.fc20.x86_64
executable:     /usr/bin/fros
kernel:         3.15.5-200.fc20.x86_64
runlevel:       N 5
type:           Python
uid:            1000

Truncated backtrace:
util.py:233:_findSoname_ldconfig:OSError: [Errno 11] Resource temporarily unavailable

Traceback (most recent call last):
  File "/usr/bin/fros", line 24, in <module>
    XLIB_PATH = util.find_library('X11')
  File "/usr/lib64/python2.7/ctypes/util.py", line 244, in find_library
    return _findSoname_ldconfig(name) or _get_soname(_findLib_gcc(name))
  File "/usr/lib64/python2.7/ctypes/util.py", line 233, in _findSoname_ldconfig
    f = os.popen('/sbin/ldconfig -p 2>/dev/null')
OSError: [Errno 11] Resource temporarily unavailable

Local variables in innermost frame:
abi_type: 'libc6,x86-64'
mach_map: {'ppc64-64': 'libc6,64bit', 'ia64-64': 'libc6,IA-64', 's390x-64': 'libc6,64bit', 'sparc64-64': 'libc6,64bit', 'x86_64-64': 'libc6,x86-64'}
struct: <module 'struct' from '/usr/lib64/python2.7/struct.pyc'>
expr: '\\s+(libX11\\.[^\\s]+)\\s+\\(libc6,x86-64'
machine: 'x86_64-64'
name: 'X11'

Comment 1 Vango Stavro 2014-07-26 17:15:28 UTC
Created attachment 921193 [details]
File: backtrace

Comment 2 Vango Stavro 2014-07-26 17:15:29 UTC
Created attachment 921194 [details]
File: environ

Comment 3 Fedora End Of Life 2015-05-29 12:28:48 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 4 Fedora End Of Life 2015-06-29 21:46:28 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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

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.