KDE is my file browser. I cannot double click to run executables even as root. Is this the way Suse is set up? Can I change it? How?

don't think there's a reason to change the "doubleclicking" thing

what you can do is to Right click your RPM package and the select "action" and then choose "install with yast"

after that it will ask for your root password etc.. and it will install automatically

Actually, I'm not talking about just installing things. I'm talking about sh scripts and binary executables also.

In Mandriva and Xandros you can just double click on executables to run them. It's very annoying having to use the console all the time.

And I can't even use the console for binary files like my programs I built:
error is: cannot execute binary file.

Please help me resolve these two issues.

I should also mention that on Xanadros and Mandriva I did not have to type:
sh to execute a file but with Suse I do. That could be part of the problem.

I don't know what to tell you about double-clicking (are you running Windows? ) but I just browsed to /usr/bin in konqueror (I was curious if click-and-run was removed from KDE 3.5 for some reason?), double-clicked audacity and it launched just fine. Are you sure that:

1. You are actually clicking a binary file or shell script

and

2. that shell script or binary has the "executable" bit set properly? (if all else fails, as a test, chmod a+x)

Yes, I'm sure on all points.

Have you changed the settings in the Kcontrol to allow mouse to select on single click, run on double click? Cause by default, single cliking runs in KDE on SuSE.

That said, even then, I cannot doublt click on scrips to get them to run even with my mouse set up for double clicking rather than single. I didn't know about the right click action either, but I would really like to double click run scripts. Perhaps I will dink around more in kcontrol later, it is probably in there.(As an aside, if you use the gnome viewer instead of KDE it does double click install, so it has to be a KDE setting SuSE sets to off when other distros set it to on).

But in the terminal I can run things with ./ or sh, I don't need or normally use sh though, so perhaps that is something off on your machine... or maybe mine is non default somehow, I dunno.

Some output:
LinuxPc:/data2/LinuxTest/aChOwn # ls -l
total 80
drwxr-xr-x 2 andrew users 4096 Jan 24 14:49 .
drwxr-xr-x 7 andrew users 4096 Jan 24 13:48 ..
-rwxr-xr-x 1 andrew users 66 Jan 24 14:49 Build.sh
-rwxr-xr-x 1 root root 70 Jan 21 20:41 Build.sh~
-rwxr-xr-x 1 andrew users 22007 Jan 18 21:27 aChOwn
-rwxr-xr-x 1 andrew users 30010 Jan 21 23:34 aChOwn_gcc3
-rwxr-xr-x 1 andrew users 4035 Jan 21 23:39 main.cpp
-rwxr-xr-x 1 andrew users 4018 Jan 21 23:36 main.cpp~
LinuxPc:/data2/LinuxTest/aChOwn # sh aChOwn
aChOwn: aChOwn: cannot execute binary file

As you can see, binary files don't execute AT ALL. Non binary files execute ONLY from the command line.

Let me know what you find out please.

Here is what I found out. This is EXTREMELY annoying!

LinuxPc:/data2/LinuxTest/aChOwn # sh ./aChOwn
./aChOwn: ./aChOwn: cannot execute binary file
LinuxPc:/data2/LinuxTest/aChOwn # ./aChOwn
bash: ./aChOwn: Permission denied
LinuxPc:/data2/LinuxTest/aChOwn # chmod aChOwn
chmod: missing operand after `aChOwn'
Try `chmod --help' for more information.
LinuxPc:/data2/LinuxTest/aChOwn # file aChOwn
aChOwn: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, dynamically linked (uses shared libs), not stripped

/data2/LinuxTest/aChOwn is actually:
media:/hda7/LinuxTest/aChOwn

and I can't even open up terminals in media:/
It's a separate partition on the hard drive. I checked to make sure all the file permissions for all the sub dirs were executable, and they are. Apparently, you're not allowed to run executables from any media:/ in Suse. To prove it, I copied the file to the partition where Suse is installed and the program ran from the console. Double clicking still does not work there though.

2 annoying things:
1) can't run executables from other drives
2) can't double click to run executables, no matter where they are.

I'll probably go back to Mandriva if this continues.

I have tried this with Suse 9.3Pro, 10.0 OSS, and 10.0 full version and it never works. Sometimes Yast will open but won't show the RPM I want to install, I have to search for the package and yast still won't install it. I have tried this on many packages and Yast has worked a few times but it is not consistant. Very frustrating that a distro with the corporate power of Novell behind it is so buggy compared to some "one man" distros. Other issues I have had with Suse9.3,10.0, 10.0 OSS- when using Gnome and opening multiple windows (such as when using yast) the 2cd, 3rd, etc windows open part way off screen, right click menu has no options for "move to", "copy to", etc and no wasy way to add them, drag and drop of device and file icons to desktop causes said icons to crash, not open, give errors, etc; KDE problems- right clicking and rpm to "install with yast" hardly ever works, clicking on "MY Computer" icon on desktop by default does NOTHING, no errors, just nothing, etc...dependency hell with RPMs still an issue even with yast. OH well even with these bugs Suse is still far better than Windows.

I know what you mean, there is a program in the non ra**d kde that lets you can the settings, its like desktop setup or something. but it gave you the option to make in windows style, kde style, mac osx style, etc. I guess they removed it