gksudo GnomeUI Warning

That warning is still in Dapper Drake Flight CD 2.

Thanks for your bugreport.

I can't reproduce this problem on a current dapper.

Cheers,
 Michael

On 3/31/06, Michael Vogt <email address hidden> wrote:
> I can't reproduce this problem on a current dapper.

I am running dapper. From a terminal, just type (i.e.)

gksudo gedit

and I am getting this (in the terminal):

(gedit:10047): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols
specified are supported and host-based authentication failed.

Thanks, I can confirm it now too. Sorry.

I can confirm this to! I run ubuntu dapper, dist-upgraded from breezy. It occurs with both gksu and gksudo, wether using sudo-mode or not. It's only a problem when running graphical applications, pure terminal ones do not seem to trigger the warning. This is very inconvenient since also the system-tools seem to use this, and therefore do not work (when called from the menu, they always give a wrong password error, when called from a terminal, they show this warning in the terminal: Warning: Tried to connect to session manager, Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed)

a few examples (same results with gksu or gksudo) :
gksu xterm: warning + root rights
gksudo whoami: no warning, root rights
gksu time-admin: warning, password error, NO root rights
time-admin: asks for password and root rights (WITHOUT gksu or gksudo)

a bugfix or workaround would be most welcome...

Tried typing "xhost +localhost" as the user running the X server then restarting X?

On 7/28/06, Gilbert <email address hidden> wrote:
> Tried typing "xhost +localhost" as the user running the X server then
> restarting X?

Yes. Nothing changed.. Still the same message:
~ $ gksudo gedit
(gedit:4870): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols
specified are supported and host-based authentication failed.

Writing to say that this issue is still present in Edgy. I first noticed it today while installing programs through automatix. Should I at all be alarmed, or is this just what it says it is: A warning (as in low-level error message but nothing much...)?

I too have seen this in Edgy... First when I was playing around in the terminal and then in automatix...

I have the same with Edgy amd64 but not only in terminal, lunch from GUI administration menu not autorised.

Messages in terminal :
~$ gksu network-admin
(network-admin:28817): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

(network-admin:28817): Liboobs-CRITICAL **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files

(network-admin:28817): Liboobs-CRITICAL **: There was an unknown error communicating with the backends: The name org.freedesktop.SystemToolsBackends was not provided by any .service files

GUI message boxe : (in frensh..)

"Chargement de la configuration impossible
Vous n'étes pas autorisés à accéder à la configuration système."

I managed to create this situation into a perfectly working system. I installed mediawiki1.7 from Ubuntu repositories and all the depending sw. After that the system was not able to run sudo nor gksudo commands.

Also, I installed MediaWiki 1.7 and the depending sw with Synaptic, after that I continued in terminal following this guide:

http://meta.wikimedia.org/wiki/Running_MediaWiki_on_Debian_GNU/Linux

and gave the command

apt-get install apache2-mpm-prefork libapache2-mod-php5 php5-gd php5-mysql mysql-server php5-cli

After this command sudo broke.

Hope this helps.

Strange: after removing all the packages mentioned above (all that mediawiki1.7 are dependent on and the ones mentione in the apt-get command above, gksudo gives the same warning but is able to open gedit in su mode.

Starting gedit with sudo gives no warnings and works.

I get this error too in Feisty when running graphical applications with gksudo:

rune@rune-desktop:~$ gksudo ghex2
(ghex2:7778): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

I have the same problem but this will happen with either sudo or gksudo but NOT with all applications.
For example sudo gedit or gksudo gedit would trigger it but sudo synaptic or gksudo synaptic would work fine.
The same problem is present if you go and click something from System > Administration. Not everything triggers it. (In my case Users and Groups has a problem all the time).

After entering the password you are presented with a blank box that WILL eventually show but it can take some minutes.
The system is perfectly responsive during that time and the CPU usage is like 0%.

I did a clean install and I think this started since the beginning.

Im running fiesty 64 bit having exact same problems as every other user. Either gksudo or sudo both give me problems

GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

Im running fiesty 64 bit having exact same problems as every other user. Either gksudo or sudo both give me problems

--Same with me.
I am now using KDESU, no errors.
I am using the command with adept manager to get root permissions.

I suspect that in Feisty when running graphical applications you should use kdesu.

using gksudo gave a crash! needed a hard boot.

I was having this same issue. It seems to be related to the Keyring Manager... maybe because all my passwords (root, user, and keyring) were the same. I just deleted the keyring and that solved the problem.

I just did a clean install this evening and I've got this bug. Never seen it before on either of my computers, both of which run Ubuntu Feisty. It occurs only with gksu, so far as I've seen.

I've got a clean install of 6.10 with all current updates, plus some gui configuration packages that I've been installing/removing (the gnome art one, pixmap, gnome splashscreen manager, all of which I've also removed) and the ntfs-3g package.

I did a clean install with 7.04. I got the message after (one or more of):
- editing xconf to enable compatible resolution with my LCD
- installing Opera flash plugin (from adobe)

also

my gnome applets started to change order (was this after i restarted gdm?...

Hope this helps to find the bug

i have this in Gutsy 64 bits

(gedit:8565): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

Having the same problem here on Gutsy.
It started after installing Java 6 and the following applications that use Java:
-Jajuk
-Unison-GTK
-Truecrypt + tcgui

When trying to gksu nautilus, it does open the application but without rights and the following:

arno@arno-laptop:~$ gksu nautilus
Gtk-Message: Failed to load module "gnomebreakpad": libgnomebreakpad.so: cannot open shared object file: No such file or directory

(nautilus:8873): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Initializing gnome-mount extension

struggling here with both Ubuntu Edgy & Mandriva free 2007.Spring, running terminal as su.

gedit filename does load and does save despite that ditto message returns in either distro, preceded by
(gedit:####): , where #### 4787 5049 5058 5083 are showing here at the moment.

I'm not sure why the importance of this is still "low", but I ran into this problem just recently, after just installing Opera a few days ago.

Running 8.04 Hardy x86

This would be a great bug to fix. As of now I can't really edit anything in the terminal.

Confirmed in Hardy 8.04.1 amd64

Command:
gvim any

Output:
(gvim:12991): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

There is no problem in editing though.

i have run into this problem in Intrepid.

It came after a video editing tool caused my system to crash or forced me to reboot.

any application started from the command line returns:
(firefox:6804): GnomeUI-WARNING **: While connecting to session manager:
None of the authentication protocols specified are supported.

list of problems I noticed so far:
gone are nautilus bookmarks
gone are firefox bookmarks
can not restore bookmarks from (the .json formats) the bookmark manager in firefox
can not export bookmarks into html in firefox through bookmark manager
can not create new bookmarks in firefox
no updates are made to browsing history which means I
can not go back and forth through browsed pages
can not save files from browser to computer (save prompt does not appear)
starting Azureus (now called VUZE) returns this error:
Save of 'azureus.config' fails
No space left on device
details:
     java.io.IOException: No space left on device
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
 at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
 at org.gudy.azureus2.core3.util.FileUtil.writeResilientFile(FileUtil.java:453)
 at org.gudy.azureus2.core3.util.FileUtil.writeResilientFile(FileUtil.java:429)
 at org.gudy.azureus2.core3.util.FileUtil.writeResilientFile(FileUtil.java:408)
 at org.gudy.azureus2.core3.util.FileUtil.writeResilientConfigFile(FileUtil.java:390)
 at org.gudy.azureus2.core3.config.impl.ConfigurationManager.save(ConfigurationManager.java:233)
 at org.gudy.azureus2.core3.config.impl.ConfigurationManager.save(ConfigurationManager.java:268)
 at org.gudy.azureus2.core3.config.COConfigurationManager.save(COConfigurationManager.java:371)
 at org.gudy.azureus2.core3.util.AEDiagnostics.markDirty(AEDiagnostics.java:460)
 at com.aelitis.azureus.core.impl.AzureusCoreImpl.<init>(AzureusCoreImpl.java:169)
 at com.aelitis.azureus.core.impl.AzureusCoreImpl.create(AzureusCoreImpl.java:102)
 at com.aelitis.azureus.core.AzureusCoreFactory.create(AzureusCoreFactory.java:46)
 at org.gudy.azureus2.ui.swt.Main.<init>(Main.java:80)
 at org.gudy.azureus2.ui.swt.Main.main(Main.java:216)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.gudy.azureus2.ui.common.Main.directLaunch(Main.java:229)
 at org.gudy.azureus2.ui.common.Main.main(Main.java:132)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.aelitis.azureus.launcher.MainExecutor$1.run(MainExecutor.java:37)
 at java.lang.Thread.run(Thread.java:619)

Azureus(Vuze) seems to be perpetually scanning for something. This is indicated by the progress bar at the bottom t...

@Ramy wrote on 2008-11-08: (permalink)

problem got fixed by shutting down for an hour or so and the logging in as another user. i don't understand this fix but that's exactly what happened. It is to note the problem was pervasive no matter how i ran applications, gksu or not.

The line "No space left on device" says all - that was the problem in my case

I had and I have any more the same Problem, but I recognized the the following.
I think, this could be interessting for solving the problem.
I opend a xterm as a normal user called "trebor" and then I give it:
---------------------------------------

trebor@PC-name:~$ su
Passwort:
root@PC-name:/home/trebor# "nautilus --browser --no-desktop"

(nautilus:26319): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

------------------------------------
The effect was, that I could not change rwx of a file in the nautilus-browser !!!!!
Strange, because I am "root" - or not ??

After that I tried this:
-------------------------
root@PC-name:/home/trebor# sudo "nautilus --browser --no-desktop"
Initializing nautilus-share extension
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing nautilus-clamscan extension
Nautilus-Share-Message: REFRESHING SHARES
Nautilus-Share-Message: ------------------------------------------
Nautilus-Share-Message: spawn arg "net"
Nautilus-Share-Message: spawn arg "usershare"
Nautilus-Share-Message: spawn arg "info"
Nautilus-Share-Message: end of spawn args; SPAWNING

Nautilus-Share-Message: returned from spawn: SUCCESS:
Nautilus-Share-Message: exit code 0
Nautilus-Share-Message: caller wants GKeyFile
Nautilus-Share-Message: success from calling net usershare and parsing its output
Nautilus-Share-Message: ------------------------------------------
root@PC-Name:/home/trebor#
-------------------------------------
Now I got the rights to change rwx of a file in the file-browser!
What is going on?

Is there sombody, could help us? We will be delighted !!
with best wishes
trebor

Any news? Encountering same problem on Lenny.

Same here with gedit. very frustrating.

Note : I also had to add "xhost +" to my .gnomerc in order even be able to run an x app in a screen session which I reconnect to after a logout and log in. Related perhaps?

note : I dont even use "gksudo", just "gedit".

shamrock@development:~$ gedit

(gedit:4699): GnomeUI-WARNING **: While connecting to session manager:
Could not open network socket.

(gedit:4699): GLib-GIO-WARNING **: Could not initialize inotify

shamrock@development:

I'm seeing this message when just trying to start xclock from an ordinary user's terminal window. Running Jaunty on a 64-bit AMD system.
Linux attic4 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux

Ian.

Wouldn't it be nice to assign this to somebody? It dates back to 3 years!

No, because it could be solved if it was assigned to someone! :D

What a lame chain of decent reporting and yet nothing gained :(

I cannot reproduce this problem in the current version of Lucid.

Cant confirm it either, but further investigation required...

2010/10/31 Richard James White <email address hidden>

> I cannot reproduce this problem in the current version of Lucid.
>
> --
> gksudo GnomeUI Warning
> https://bugs.launchpad.net/bugs/23917
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gksu” package in Ubuntu: Confirmed
>
> Bug description:
> Running from terminal an application that requires authentication (i.e.
> gksudo
> network-admin) always returns this message:
>
> (network-admin:10511): GnomeUI-WARNING **: While connecting to session
> manager:
> Authentication Rejected, reason : None of the authentication protocols
> specified
> are supported and host-based authentication failed.
>
> Doesn't matter what the application is. Gksudo starts and let the
> application
> run, but what's the matter with that warning?
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/23917/+subscribe
>

--
AVISO DE CONFIDENCIALIDADE: Esta mensagem, assim como os ficheiros
eventualmente anexos, é confidencial e reservada apenas ao conhecimento
da(s) pessoa(s) nela indicada(s) como destinatária(s). Se não é o seu
destinatário, solicitamos que não faça qualquer uso do respectivo conteúdo
e proceda à sua destruição, notificando o remetente.

Now the bug is >6 years old; I'm seeing this in a fresh upgrade to 10.4, when I try to start firefox. See bug 933283 (look, this bug was in the low 5 digits, and now we're about to reach 7 digits! This bug has been around for 2 orders of magnitude!)