gedit failes to open from after su

[stone head]

After gaining administrator rights with ¨su¨, i get the following error when trying to run gedit -

[root@stone head]# gedit

(gedit:3007): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported

g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Terminated


as a normal user, gedit works fine.
I installed fedora 15 beta a week ago, and besides normal yum updates, i enabled rpm-fusion.

[Koppenaal]

su -lc 'gedit'

---or:---

su -
gedit

[stone head]

su -lc 'gedit' ---This worked for me.

I´m still curious as to why it doesn´t work normally.

[jpollard]

su doesn't give you all administrator rights - only file access control.

SELinux still rules, and you don't have roots security context without doing su - or su -l.

su alone only switches the effective UID/GID. It does not alter the real UID/GID or SELinux process labels.

[DavidMcCann]

It's nothing to do with SEL: it happens if you don't use it and in distros that don't have it.

If you just use "su", you have the priviliges of the super user, but if you use "su -" it's as if you've actually logged in as root. So, for example, you may have different environment variables depending on which you used. They also handle PAM differently, which is what troubles some programs, like Gedit. For the whole story,
info coreutils 'su invocation'
man pam

[screamin_jesus]

Another method is installing beesu and opening gedit via alt + f2:

beesu gedit '/path/to/file'

[JohnVV]

think of the - dash as a typing shortcut for loging in as root ( full root account)