Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1206818 - sup cannot be started, cannot load curses
Summary: sup cannot be started, cannot load curses
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-sup
Version: 21
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Shreyank Gupta
QA Contact: Fedora Extras Quality Assurance
: 1236623 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-28 20:14 UTC by Jan Včelák
Modified: 2015-12-02 17:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-12-02 10:38:01 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Ruby 8584 0 None None None Never

Description Jan Včelák 2015-03-28 20:14:43 UTC
Description of problem:

$ sup
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- curses (LoadError)
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/gems/gems/sup-0.10.2/lib/sup.rb:7:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/gems/gems/sup-0.10.2/bin/sup:15:in `<top (required)>'
	from /bin/sup:23:in `load'
	from /bin/sup:23:in `<main>'

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. start sup

Actual results:

sup fails to start

Expected results:

sup starts

Additional info:

Comment 1 Vít Ondruch 2015-05-12 12:41:17 UTC
Curses was removed from Ruby and it is now distributed as independent gem [1].


Comment 2 Vít Ondruch 2015-09-02 17:02:37 UTC
*** Bug 1236623 has been marked as a duplicate of this bug. ***

Comment 3 Fedora Update System 2015-09-03 05:38:30 UTC
ruby-ncurses-1.3.1-16.fc23 rubygem-sup-0.21.0-3.fc23 has been submitted as an update to Fedora 23.

Comment 4 Fedora Update System 2015-09-04 07:34:13 UTC
ruby-ncurses-1.3.1-16.fc23, rubygem-sup-0.21.0-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update rubygem-sup ruby-ncurses'. You can provide feedback for this update here:

Comment 5 Fedora Update System 2015-09-07 16:36:02 UTC
ruby-ncurses-1.3.1-16.fc23, rubygem-sup-0.21.0-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 6 Jan Včelák 2015-09-07 20:04:53 UTC
Please, can you provide an update for F22 as well?

Comment 7 Vít Ondruch 2015-09-08 06:05:04 UTC
Well ...

Comment 8 Fedora End Of Life 2015-11-04 16:01:40 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 '21'.

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 21 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 9 Fedora End Of Life 2015-12-02 10:38:04 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.