[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Bug#35434: application started via kfm doesn't find it's files
From:       Carsten Pfeiffer <carpdjih () cetus ! zrz ! tu-berlin ! de>
Date:       2001-11-29 2:43:55
[Download RAW message or body]

On Tue, Nov 27, 2001 at 05:00:11PM -0000, gnor@x-mail.net wrote:

> Package: kfile
> Version: KDE 2.2.2 
> Severity: normal
> Installed from:    SuSE RPMs
> Compiler:          Not Specified
> OS:                Linux
> OS/Compiler notes: Not Specified
> 
> kde 2.1.2 kfm parsec launcher doesn't find parsec executable in same
> directory

What do you mean "doesn't find"? It doesn't start when you click onto it?
Does it have the executable bit set?

> Dear KDE and KFM maintainers!
> 
> This is an original SuSE 7.2 distribution.
> 
> For the moment, everything is installed to be weeded later.
> 
> According to /proc/version it is a 2.4.4-4GB kernel out of the box.
> 
> KDE Control Center talks of Release 2 4 4 4 and Version  2 1 2.

Contrary to this, your bugreport talks of KDE 2.2.2.

> the parsec version is:
> 
> parsec_lan_build0196.tar.gz
> 
> It is installed into /opt/parsec.

Do you have that in your PATH? Or did you enter that directory and
clicked on the parsec binary?

Can you be a little bit more specific what you do?

> All files are in this directory except some *.con files in the ./cons
> subdirectory.
> 
> References will be made to this directory unless otherwise specified.
> 
> Documentation recommends to run ./launcher for initial setup.
> 
> Launcher comes up faithfully, presenting it's setup dialogue.
> 
> You close it, after twiddling the parameters, and see the graphical
> Launcher menu.
> 
> Pressing the "Play Game" button reveals not the game, but a complaint
> of not finding ./parsec, the symlink to ./parsec_x in this case,
> because of not being in the same directory. (???)

Ahh, you start "launcher", which tries to start "parsec", but doesn't
find it, because it's not in the path? If you ask me, this is a bug
in "launcher", it shouldn't assume that $PWD is /opt/parsec. On the other
hand, konqueror might set the cwd to his current directory, when launching
apps.

> A few of the other window managers that offer a file manager in their
> menu that doesn't refuse to work for "root" ( I am *not* a toddler, but
> want the multiplexing of a GUI in addition to the consoles! ) fire it
> up faithfully.

Konqueror doesn't complain, I think that's a SuSE addition (and a useful one).
 
> A final try in Kconsole worked fine again, but the characters in
> Kconsole were strangely
> 
> d o u b l e   s p a c e d. (???)

Please file a bugreport to konsole next time. You might try selecting
a different font.
 
> My ancient NT4SP5 stuffs Unicode characters byte-wise into my unqp
> filter under NTFS, but will faithfully export Win-ANSI/ISO to FAT12 on
> floppies and DOS/Win16 applications. Strangely, Win32 console programs
> use the OEM mapping by default.
> 
> So you should look very hard at the interface between 16-bit charsets
> and 8-bit charsets in KDE and/or complain to the appropriate kernel,
> application, tool, etc. developers.

Cheers
Carsten Pfeiffer

[prev in list] [next in list] [prev in thread] [next in thread]