Suse 10.3 - "Su returned with an error."

English Network/Internet
1

I was setting up a network between a Suse 10.3 and xp machines and followed the instruction from the website: How To Samba With Suse 10.3 And Windows XP
I created a shortcut on the desktop to turn off the suse firewall. For the Application Command I used: /sbin/SuSEfirewall2 stop

In Advanced Options, User, I checked Run as a different user, User name: root

When I used it it came back with:
"X Error-KDE su … su returned with an error.

When I try to open Yast it has same error.When I use the Updater to install updates I get same error.

I can use a terminal, login as root and enter Yast2. But don’t know what to change to solve the problem.

Any help will be appreciated!!!
thanx!!!

2

This is just a guess but, since you normally run as root by using su or sudo, ‘Run as different user’ may only refer to non-root users.

Alternatively, if you ask to run anything as root, you normally get a request for the root password - if you are not getting this request, what you have done has interfered with the normal process of allowing you to run as root.

3

“Alternatively, if you ask to run anything as root, you normally get a request for the root password - if you are not getting this request, what you have done has interfered with the normal process of allowing you to run as root.”

Thats it exactly!
But I’m new to linux and I don’t know what I did to interfere with the normal process. And what to do to return to the normal process.

Thanks for the help!

4

On Sat, 16 Aug 2008 21:26:03 GMT
LittleMuskie <LittleMuskie@no-mx.forums.opensuse.org> wrote:

>
> I was setting up a network between a Suse 10.3 and xp machines and
> followed the instruction from the website: ‘How To Samba With Suse 10.3
> And Windows XP’ (http://www.tweakhound.com/linux/samba/page_1.htm)
> I created a shortcut on the desktop to turn off the suse firewall. For
> the Application Command I used: /sbin/SuSEfirewall2 stop

I would recommend using YaST to turn off the firewall if you don’t need it.
If you’re trying to turn it off to use samba… then open the appropriate
ports to allow samba through (137,139,445) (or just check the little “open
firewall ports” checkbox in the YaST Samba Server setup module.)

If you are behind a hardware firewall (router/gateway) then it is not
absolutely necessary to also run a firewall on each machine. But you are
welcome to run your systems as you wish.

> In Advanced Options, User, I checked Run as a different user, User
> name: root
>
> When I used it it came back with:
> "X Error-KDE su … su returned with an error.

If you must use this method, leave the username blank to run as root. It’s
a quirk. Examine the entry for ‘YaST’ in the kmenu as an example of how to
do this.

> When I try to open Yast it has same error.When I use the Updater to
> install updates I get same error.

Did you change those entries also? See previous answer

> I can use a terminal, login as root and enter Yast2. But don’t know
> what to change to solve the problem.

Note that to run a program as root in KDE, it is far easier to specify the
command to run as:

kdesu xeyes

then to set command to ‘xeyes’ and check the advanced settings ‘run as
different user’. A bit more understandable too, as the indication to run
this program as root is much more noticable.

Loni

–
L R Nix
lornix@lornix.com

5

Went ahead and read the information on the webpage given… the author has
some slighty confusing sections (as an example, he uses 10.10.10.x and
then also references 192.168.x.x… using a class A subnet for home use? holy
cow! how many systems this guy got? But not a problem though, just possibly
confusing)

He also locks down machines instead of keeping them using dhcp. Yes, it can
make some things easier. Can (rarely) cause issues if your DHCP server
doesn’t check to see if an address is in use before assigning it. The samba
filesharing system is designed to share addresses to other machines.

I don’t see the need for the desktop “firewall on” and “firewall off”
shortcuts.

The firewall, if one uses one, should always be on. Considering that an
unprotected windows machine on the internet can be infected in 20 minutes or
less: (I had one get infected less than 2 minutes after I booted it for the
first time. Yes, it was ‘naked on the net’… but I was getting the updates
to fix the firewall… ironic?)

http://tinyurl.com/55ejat
http://blogs.chron.com/techblog/archives/2008/07/average_time_to_infection_4_minutes_1.html

http://tinyurl.com/6s6h2r
http://it.slashdot.org/article.pl?sid=08/07/15/0123245

(and for all you guys rushing to reply and chide me for using tinyurl’s after
my discourse in the chit-chat forum… I can see the use for them.)

While acknowledging the fact that a linux box is dramatically less likely to
be infected in the same timeframe, in the same ‘naked on the net’
circumstances, it could happen. (You could also suddenly experience quantum
tunneling and reappear on the other side of the earth too…)

If you worry enough to run a firewall INSIDE your hardware firewall…
then you should take the SAME precautions with ALL of your machines
regardless of their OS. Would you turn off the windows firewall for a random
period of time? Didn’t think so.

No, I don’t use firewalls behind my hardware firewall. This is MY opinion
and preference. <removed my pithy example> I don’t feel the need, and
firewalls tend to complicate matters when you’re dealing with trusted
machines.

Loni

–
L R Nix
lornix@lornix.com

6

Loni, Thanks for the replies!

I use a Verizon USB U-750 to connect to the internet, no hardwall firewall.

I was trying to transfer the Suse 11.iso immage about 4.2gig from one computer to the other to burn it. The connection is with a patch cable, no router.

I thought setting up a small network with samba would be the easiest. But, I have never done this and tried to follow “http://www.tweakhound.com/linux/samba/page_1.htm”
instructions. I too found it confusing!

When I was finished I could see the files on the XP machine but could not ‘mount’ it to transfer files. I rebooted the machines, no luck still unable to ‘mount’ the XP machine. So I tried using the fancy shortcut to disable the firewall. That is when I got the “Su returned with an error” message. I don’t know if it was the “shortcut” or some other setting that was changed to cause the problem?

"Note that to run a program as root in KDE, it is far easier to specify the
command to run as:

kdesu xeyes

then to set command to ‘xeyes’ and check the advanced settings ‘run as
different user’. A bit more understandable too, as the indication to run
this program as root is much more noticable."

I went to “Konsole” typed in “kdesu xeyes” came back with “Su returned with an error”.
I used “Terminal Program - Super User Mode” entered the password and then typed in “xeyes”. A pair of eyes appeared and locked the terminal.
Reopened the Super User Mode Term. and entered Yast. Could not find “Advanced settings” or ‘run as different user’.

Where do I find these settings?

Thanks!
Scott

7

On Mon, 18 Aug 2008 02:16:03 GMT
LittleMuskie <LittleMuskie@no-mx.forums.opensuse.org> wrote:

> That is when I got the “Su returned with an error” message.

This seems to be related to kdesurc. Please delete the kdesurc file with the
following commands (kde and kde4)

rm .kde/share/config/kdesurc
rm .kde4/share/config/kdesurc

And either log out and then back in, or reboot.

This should resolve that problem.

> I went to “Konsole” typed in “kdesu xeyes” came back with “Su returned
> with an error”.
> I used “Terminal Program - Super User Mode” entered the password and
> then typed in “xeyes”. A pair of eyes appeared and locked the
> terminal.

If you had clicked on the terminal you started xeyes from, you could press
ctrl-c to stop the program. Tried to find an example program that wouldn’t
confuse people, guess I failed.

> Reopened the Super User Mode Term. and entered Yast. Could not find
> “Advanced settings” or ‘run as different user’.
> Where do I find these settings?

{Sigh} They’re in the kmenu setup… right click on Geecko, the little green
lizard thingy that calls up the menu…no… RIGHT click… select menu
editor.

  • Click on the +] next to ‘System’
  • then on the +] next to ‘Configuration’
  • then on “Administrator Settings”

On the right, you’ll see how the developers have set up the Yast2 menu entry
to be run as root.

Don’t change anything, as it might not work when you need it next time.

Loni

–
L R Nix
lornix@lornix.com

8

***> That is when I got the “Su returned with an error” message.

This seems to be related to kdesurc. Please delete the kdesurc file with the
following commands (kde and kde4)

rm .kde/share/config/kdesurc
rm .kde4/share/config/kdesurc

And either log out and then back in, or reboot.

This should resolve that problem.***

Tried this in the Konsole and Term. Prog. - Super User Mode.
“rm: cannot remove ‘.kde/share/config/kdesurc’: No such file or directory”
Was the reply. I rebooted the computer and when I try to enter Yast through the Kde menu I still get the “Su returned with an error.”

Any other ideas Loni?

Since this seams to be a Kde issue maybe I should post in the “Applications” forum?

9

On Tue, 19 Aug 2008 02:26:03 GMT
LittleMuskie <LittleMuskie@no-mx.forums.opensuse.org> wrote:

>
> -> THAT IS WHEN I GOT THE “SU RETURNED WITH AN ERROR” MESSAGE.
>
> THIS SEEMS TO BE RELATED TO KDESURC. PLEASE DELETE THE KDESURC FILE
> WITH THE
> FOLLOWING COMMANDS (KDE AND KDE4)
>
> RM .KDE/SHARE/CONFIG/KDESURC
> RM .KDE4/SHARE/CONFIG/KDESURC
>
> AND EITHER LOG OUT AND THEN BACK IN, OR REBOOT.
>
> THIS SHOULD RESOLVE THAT PROBLEM.-
>
> Tried this in the Konsole and Term. Prog. - Super User Mode.
> “rm: cannot remove ‘.kde/share/config/kdesurc’: No such file or
> directory”
> Was the reply. I rebooted the computer and when I try to enter Yast
> through the Kde menu I still get the “Su returned with an error.”
>
> Any other ideas Loni?
>
> Since this seams to be a Kde issue maybe I should post in the
> “Applications” forum?
>
>

No, no other ideas at this time, experiencing brain fugue.

Might try the applications forum.

Loni

–
L R Nix
lornix@lornix.com

10

I don’t know if it’s the same case, but I had this kind of problem in 10.2 - not able to start Yast from GUI/kdesu - after editing the sudoers file, and that through Yast itself…

It seems that the sudoers file sintax is very strict. I copíed back the original file from another install and all was well again.

Eventually I was able to set the rule correctly, but I think that even blank lines (or the lack of) may cause problems. I didn’t check further, however.