[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 125977] New: When running 'konsole /path/to/script.sh',
From: hans chen <hanswchen () gmail ! com>
Date: 2006-04-20 19:49:13
Message-ID: 20060420214912.125977.hanswchen () gmail ! com
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=125977
Summary: When running 'konsole /path/to/script.sh', and script.sh
doesn't exist, konsole complains about pseudo teletype
Product: konsole
Version: 1.6.2
Platform: Slackware Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: konsole-devel kde org
ReportedBy: hanswchen gmail com
Version: 1.6.2 (using KDE KDE 3.5.2)
Installed from: Slackware Packages
OS: Linux
Run 'konsole -e /no/script.sh' in a terminal. I get the error message:
"A Fatal Error Has Occurred
Konsole is unable to open a PTY (pseudo teletype). It is likely that this is due to \
an incorrect configuration of the PTY devices. Konsole needs to have read/write \
access to the PTY devices."
And the terminal output:
"konsole: WARNING: Unable to open a pseudo teletype!
Uh oh.. can't get terminal attributes.."
I think this error message is very confusing. The only problem is that the script \
doesn't exist! If I run Eterm instead of Konsole, I get this error message:
"Eterm: Error: execvp() failed, cannot execute "/no/script.sh": No such file or \
directory"
Much clearer. Much more correct. Much better.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic