Bug 50429 - Running invalid programs silently fails
Summary: Running invalid programs silently fails
Status: CLOSED WORKSFORME
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-11-08 21:49 UTC by Chris Howells
Modified: 2008-11-20 16:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Howells 2002-11-08 21:49:00 UTC
Version:            (using KDE KDE 3.0.8)
Installed from:    Compiled From Sources
Compiler:          gcc 2.95.4 (Debian woody) 
OS:          Linux

This bug was first noticed via minicli, according to dfaure on kde-core-devel it's a kdesu bug...

In mincli, enter a program name which doesn't actually exist (e.g. "asdsadsadl"), and hit run as other user button. The program silently fails to run without being told that the program does not exist.

This seems to happen as well from the command line with kdesu, e.g. kdesu -u foo ssdaldasdad.
Comment 1 Nicolas L. 2005-08-21 22:39:50 UTC
i just tested and kdesu told me that the command i used was invalid so i think that this bug can be close 

someone can confirm ?
Comment 2 Chris Howells 2006-05-29 02:50:53 UTC
No, bug still exists in 3.5.
Comment 3 Daniel Hahler 2007-04-18 01:45:16 UTC
I can confirm it, for "Run as a different user".

Make sure you reproduce it like the following:
1. Alt-F2
2. Enter "ssdaldasdad"
3. Click "Options >>" to display options
4. Check "Run as a different user"
5. Enter username and password of another user (or your current one)
6. Click Run

This does not happen with "kdesu" from the command line though (as the original reporter says):
$ kdesu -u daniel ssdaldasdad
sh: ssdaldasdad: not found
(also I get a popup "Command 'ssdaldasdad' not found.")

Kubuntu Feisty (KDE 3.5.6)
Comment 4 Nicolas L. 2007-04-27 20:45:23 UTC
confirmed here too
Comment 5 FiNeX 2008-11-20 16:14:14 UTC
this has been fixed in current trunk: if the command is not valid, the user is informed with a messagebox.