Re: 'Run Command' problems
On Monday 18 July 2005 17:22, Kevin Krammer wrote: On Monday 18 July 2005 13:41, Jan De Luyck wrote: On Monday 18 July 2005 11:27, Kevin Krammer wrote: On Monday 18 July 2005 07:04, Jan De Luyck wrote: Yes, I know that.. But I'm just wondering what might have caused the problem, since I haven't changed a thing myself, only the 'usual' upgrades through apt-get. In which directory are the programs you can only start from an interactive shell? They're all in /usr/bin :p Uh, now that is strange ;) Ahum. It's fixed now :P It was because the konqueror package wasn't installed that the 'Run Command' went astray. Vewwy weird. I fixed it now that konqueror is installable again :) (xorg fixes) Thanks anyway ;p Jan -- A raccoon tangled with a 23,000 volt line today. The results blacked out 1400 homes and, of course, one raccoon. -- Steel City News -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 'Run Command' problems
On Monday 18 July 2005 07:04, Jan De Luyck wrote: Yes, I know that.. But I'm just wondering what might have caused the problem, since I haven't changed a thing myself, only the 'usual' upgrades through apt-get. In which directory are the programs you can only start from an interactive shell? Earlier the 'Run command' box also showed the icon of the program you were (trying to) start, that it has stopped doing too. I guess something broke in unstable ;p but that's to be expected from now and then. Ah well, i'll just keep launching things from the xterm then for now. I think displaying the icon depends on Run command being able to find it :) Cheers, Kevin pgpC3UnODiqBq.pgp Description: PGP signature
Re: 'Run Command' problems
On Monday 18 July 2005 11:27, Kevin Krammer wrote: On Monday 18 July 2005 07:04, Jan De Luyck wrote: Yes, I know that.. But I'm just wondering what might have caused the problem, since I haven't changed a thing myself, only the 'usual' upgrades through apt-get. In which directory are the programs you can only start from an interactive shell? They're all in /usr/bin :p Earlier the 'Run command' box also showed the icon of the program you were (trying to) start, that it has stopped doing too. I guess something broke in unstable ;p but that's to be expected from now and then. Ah well, i'll just keep launching things from the xterm then for now. I think displaying the icon depends on Run command being able to find it :) Yup. But, strangely, it doesn't find _any_ icon, but can start certain programs. Jan -- I'm ZIPPY the PINHEAD and I'm totally committed to the festive mode. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 'Run Command' problems
On Monday 18 July 2005 13:41, Jan De Luyck wrote: On Monday 18 July 2005 11:27, Kevin Krammer wrote: On Monday 18 July 2005 07:04, Jan De Luyck wrote: Yes, I know that.. But I'm just wondering what might have caused the problem, since I haven't changed a thing myself, only the 'usual' upgrades through apt-get. In which directory are the programs you can only start from an interactive shell? They're all in /usr/bin :p Uh, now that is strange ;) Yup. But, strangely, it doesn't find _any_ icon, but can start certain programs. Hmm. Can you check if this also happens if you create a new user account? To rule out that it is some kind of problem with the existing user's setup. Cheers, Kevin pgpKqeLjt5iED.pgp Description: PGP signature
'Run Command' problems
Hello all, Since shortly, I get a lot of 'Could not run the specified command' when using the 'Run command' box (ALT-F2). The commands in question are prefectly valid (they work perfectly from an xterm), and it started off recently that it doesn't find half of the commands anymore. Any ideas? Any library that might have been replaced? Jan -- Spelling is a lossed art. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 'Run Command' problems
On Sunday 17 July 2005 19:39, Jan De Luyck wrote: Hello all, Since shortly, I get a lot of 'Could not run the specified command' when using the 'Run command' box (ALT-F2). The commands in question are prefectly valid (they work perfectly from an xterm), and it started off recently that it doesn't find half of the commands anymore. Could be a different environment, i.e. a different PATH for KDE and the shell inside xterm. This can happen when additional directories are added to PATH in shell config files that are only read by interactive shells such as the one in terminals, but not the shell running startkde. Cheers, Kevin pgpOGyFZlr7iL.pgp Description: PGP signature
Re: 'Run Command' problems
On Monday 18 July 2005 02:21, Kevin Krammer wrote: On Sunday 17 July 2005 19:39, Jan De Luyck wrote: Hello all, Since shortly, I get a lot of 'Could not run the specified command' when using the 'Run command' box (ALT-F2). The commands in question are prefectly valid (they work perfectly from an xterm), and it started off recently that it doesn't find half of the commands anymore. Could be a different environment, i.e. a different PATH for KDE and the shell inside xterm. This can happen when additional directories are added to PATH in shell config files that are only read by interactive shells such as the one in terminals, but not the shell running startkde. Yes, I know that.. But I'm just wondering what might have caused the problem, since I haven't changed a thing myself, only the 'usual' upgrades through apt-get. Earlier the 'Run command' box also showed the icon of the program you were (trying to) start, that it has stopped doing too. I guess something broke in unstable ;p but that's to be expected from now and then. Ah well, i'll just keep launching things from the xterm then for now. Jan -- Caution: breathing may be hazardous to your health. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
