Bug 783018 - Emacs self-insert-command isn't working.
Summary: Emacs self-insert-command isn't working.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 16
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Karel Klíč
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-19 05:15 UTC by Chris Moller
Modified: 2013-03-03 23:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-14 01:48:57 UTC
Type: ---


Attachments (Terms of Use)

Description Chris Moller 2012-01-19 05:15:52 UTC
Description of problem:

At least, that's the effect--typing any normal key that's supposed to insert a character into either the buffer or the mini-buffer produces no result at all.  Control keys, like arrow keys and Ctrl-X, Ctrl-C sequences work.

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

23.3-8.fc16 (the default for the release), 

23.3-19.fc17 (from koji, per a suggestion in one of those two bugs referenced below), 

xemacs-21.5.31-2.fc16, 

the latest FSF emacs.


How reproducible:

100%


Steps to Reproduce:
1.  Start emacs
2.  Type something in the buffer.
3.  Observe that nothing shows up in the buffer
4.  Hit Ctrl-X, Ctrl-C
5.  Observe that those keystrokes are interpreted properly.
  
Actual results:

No response to self-inserting keystrokes.


Expected results:

Ordinary keys should show up in the buffer


Additional info:

All of the above on a newly installed Fedora release 16 (Verne) 3.1.6-1.fc16.i686.PAE #1 SMP

23.3-19.fc17 built from source with rpmbuild--the Fedora 17 dependencies weren't met in a Fedora 16 box.

This may be related to bzs 691825 and/or 752936

I gave this a Severity high because, really, emacs /ought/ to work.

Comment 1 Karel Klíč 2012-02-21 15:47:57 UTC
Can you please check whether /usr/bin/emacs-nox from the emacs-nox package works as expected?

Comment 2 Fedora End Of Life 2013-01-16 23:25:33 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-14 01:49:09 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.