PDA

View Full Version : Koctave doesn't work


anoir
September 30th, 2006, 09:30 AM
Hi.

I installed koctave from the universe repository of dapper. It just worked fine first time, but I cannot run it successfully again. After splash screen, a dialog comes up and the whole application quits automatically. The dialog says,

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.


I have no idea about what this means... The same thing happens in kde session as well. Octave seems to work flawlessly.

Does anybody have some ideas about this?

akniss
September 30th, 2006, 12:29 PM
Googleing the error message brings up quite a few hits... it looks like the 'pseudo teletype' message usually comes up when konsole is told to run a script that does not exist. Could you possibly check to see what scripts koctave is trying to run when you start it up?

anoir
October 1st, 2006, 05:57 AM
Thanks for reply.

Attached at the end of this post is the error message displayed when I try to run koctave from GNOME Terminal. There are some entries which resemble my case.

http://ubuntuforums.org/archive/index.php/t-177333.html
In this case the way koctave fails is little different from mine.

http://www.ubuntuforums.org/showthread.php?t=264427
It works here even with the same kind of error.

As for pty device, mount shows
devpts on /dev/pts type devpts (rw,gid=5,mode=620)


Did anyone successfully run koctave?


X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
Link points to "/tmp/ksocket-rion"
Link points to "/tmp/kde-rion"
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
kbuildsycoca running...
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kOctaveui.rc
ScimInputContextPlugin()
WARNING: please edit ~/.scim/global and change /DefaultConfigModule to kconfig
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
Uh oh.. can't write data..
kOctave: WARNING: Unable to open a pseudo teletype!
Uh oh.. can't get terminal attributes..
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
Launched ok, pid = 5252
~ScimInputContextPlugin()
rion@athlon:~$ X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x32002cc
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x32002cc
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 18
Minor opcode: 0
Resource id: 0x32002cc
ICE default IO error handler doing an exit(), pid = 5249, errno = 0

mips
October 1st, 2006, 02:04 PM
Works fine in Kubuntu.

u04f061
October 10th, 2006, 02:10 PM
i am using koctave with kubuntu. it works fine on my pc. try to reinstall it.

anoir
October 10th, 2006, 08:07 PM
Thanks for reports.

It seems that koctave works fine with kubuntu installation, while at least in my case ubuntu with kubuntu-desktop has an issue.

I'll try to install kubuntu from scratch when I can afford that much time(maybe around new year...).

majestros
April 24th, 2007, 07:55 PM
installing kdebase with synaptic solved my problem, koctave works fine now.

After I noticed someone posting their error messages from the terminal, I ran it from the terminal and my errors specifically mentioned "do you have kdebase installed correctly?"

After installing kdebase and its associated packages, it works fine.

anoir
April 24th, 2007, 10:25 PM
Thanks for your information!

Now with feisty fresh install, I also got the error message that asks for kdebase.

After installing kdebase, koctave runs fine in GNOME as well, although it has some errors (I think this kind of error message often show up when I launch other KDE apps from terminal as well).


X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
Major opcode: 147
Minor opcode: 3
Resource id: 0x0
Failed to open device
kbuildsycoca running...
DCOP Cleaning up dead connections.
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kOctaveui.rc
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
kdecore (KProcess): WARNING: _attachPty() 12

bsingh79
May 29th, 2007, 08:19 PM
I'm using Koctave on kubuntu..it was working fine until I tried to reconfigure its settings to change the start up directory..

I've already tried reinstalling and installing kdebase..both don't seem to have fixed the error

Could anyone please help me fix this problem?

The error message is :
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.

I'm getting the following error when I run it thru terminal:

X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kOctaveui.rc
ScimInputContextPlugin()
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
Uh oh.. can't write data..
kOctave: WARNING: Unable to open a pseudo teletype!
Uh oh.. can't get terminal attributes..
~ScimInputContextPlugin()
bsingh@bsingh-laptop:~/code/octave_files$ koctave
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file kOctaveui.rc
ScimInputContextPlugin()
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
kOctave: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file editorui.rc
Uh oh.. can't write data..
kOctave: WARNING: Unable to open a pseudo teletype!
Uh oh.. can't get terminal attributes..
~ScimInputContextPlugin()

u04f061
May 29th, 2007, 09:04 PM
does koctave works for octave2.9?

sawjew
May 29th, 2007, 09:08 PM
Koctave is old and no longer developed. If you want a new interface for octave check out Qtoctave https://forja.rediris.es/projects/csl-qtoctave/.

I am currently using this and it works fine on Ubuntu and it is highly configurable.

rockets
June 5th, 2007, 11:59 PM
does koctave works for octave2.9?

I installed octave 2.9 and koctave forced octave 2.1 also.
I launched kOctave, went to Settings-Configure and pointed the path to /usr/bin/octave2.9.
It appears to work...

vikasmk
October 7th, 2007, 03:22 AM
i use ubuntu 7.04 , and i installed koctave recently. i just cant seem to run any programs on it.
whenever i write a program and hit save and run koctave closes and that's it .nothing happens. can any one help me????

sawjew
October 7th, 2007, 03:41 AM
For Koctave to work correctly on Ubuntu you need to install kdebase; sudo apt-get install kdebase

After that it should work properly, however I would strongly recommend trying Qtoctave which I mentioned a couple of posts back. Follow the link in that post and download the source and compile and install it. Koctave hasn't been actively developed for years whereas Qtoctave is under constant development and, in my opinion, is a lot more useful than Koctave.

If you are not happy with compiling from source it is quite easy, especially if you use Checkinstall which enables you to uninstall with Apt/Synaptic like anything else.

LaserJock
October 8th, 2007, 02:15 AM
Quick note, qtoctave is in Debian http://packages.debian.org/qtoctave and if you download the .debs you can probably install them OK (haven't tested any though so I'm just guessing).

Given that qtoctave is packaged up and the dead upstream for koctave I think I'll be removing koctave from Hardy and syncing qtoctave over from Debian.

-LaserJock