Bug 215909 - mc freezes when one tries to enter directory with \n at the end
Summary: mc freezes when one tries to enter directory with \n at the end
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mc
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jindrich Novy
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On: 215907
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-16 10:48 UTC by David Kovalsky
Modified: 2014-03-31 23:44 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-11-23 09:51:17 UTC


Attachments (Terms of Use)

Description David Kovalsky 2006-11-16 10:48:09 UTC
+++ This bug was initially created as a clone of Bug #215907 +++

+++ This bug was initially created as a clone of Bug #215906 +++

Version-Release number of selected component (if applicable):
mc-4.6.1a-30.fc6

How reproducible:
always

Steps to Reproduce:
1.
[guest@makaham TESTING]$ mkdir 'FOO
> '

2.
mc

3.
try to enter 'FOO?' directory
  

Actual results:
mc freezes

Expected results:
mc does not freeze and makes me a nice cup of coffee :-)

Comment 1 David Kovalsky 2006-11-16 10:56:15 UTC
You can create a directory with \n by doing F7 -> FOO<SHIFT+ENTER><ENTER>, but
in my case this does not work in xterm, I have to switch to text mode -> CTRL+ALT+F1

Comment 2 Fedora Update System 2006-11-22 16:26:18 UTC
mc-4.6.1a-35.fc6 has been pushed for fc6, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 3 Fedora Update System 2006-11-22 16:27:43 UTC
mc-4.6.1a-35.fc5 has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 4 Fedora Update System 2006-11-27 16:21:35 UTC
mc-4.6.1a-35.fc5 has been pushed for fc5, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.