FS#11906 - [gksu] Problem launching apps

Attached to Project: Arch Linux
Opened by Joeny Ang (biloky) - Tuesday, 28 October 2008, 04:14 GMT
Last edited by Hugo Doria (hdoria) - Saturday, 03 October 2009, 12:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Hugo Doria (hdoria)
Architecture All
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
Problem launching apps via gksu. Apps like firestarter, for instance will spit out the following error message and will refuse to run:

A proper configuration for Firestarter was not found. If you are running Firestarter from the directory you built it in, run 'make install-data-local' to install a configuration, or simply 'make install' to install the whole program.
Firestarter will now close.

gedit, will return the following message on the console but will continue to run.

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

gparted, on the other hand, will run without problems.

Came across a patch on the the net suggesting that Gnome 2.24 apps be run using dbus. Here's the link:
frugalware-git@frugalware.org/msg21999.html"> http://www.mail-archive.com/frugalware-git@frugalware.org/msg21999.html

Running the above mentioned apps using "gksu dbus-launch ..." instead of just "gksu ...", will output a warning about failure to connect to the session manager.... but will run normally.

Additional info:
* gksu 2.0.0-4
* libgksu 2.0.7-1
* gnome-keyring 2.24.1-1

Steps to reproduce:
# gksu firestarter
This task depends upon

Closed by  Hugo Doria (hdoria)
Saturday, 03 October 2009, 12:55 GMT
Reason for closing:  Upstream
Comment by André Fettouhi (A.Fettouhi) - Tuesday, 28 October 2008, 07:24 GMT
Same problem here.

Regards

André
Comment by erythrocyte (erythrocyte) - Tuesday, 28 October 2008, 12:01 GMT
I confirm this problem too. A discussion on the forums is here http://bbs.archlinux.org/viewtopic.php?id=57454 .
Comment by Glenn Matthys (RedShift) - Friday, 12 December 2008, 19:15 GMT
What's the status of this issue?
Comment by Glenn Matthys (RedShift) - Friday, 12 December 2008, 19:16 GMT
Added JGC because he maintains libgksu, it may be related.
Comment by André Fettouhi (A.Fettouhi) - Saturday, 13 December 2008, 13:48 GMT
I can start firestarter as root, i.e.

su -
firestarter

then it runs but gksu firestarter won't run.

Regards

André
Comment by Hugo Doria (hdoria) - Saturday, 13 December 2008, 14:57 GMT
I think this is related to Orbit. Can someone confirm?

The solution made by the frugalware team is not so clean and i will only use if we are sure that this is not related to Orbit (as suggested in the error message)
Comment by André Fettouhi (A.Fettouhi) - Monday, 15 December 2008, 13:31 GMT
Here is the thread where the discussion about the problems with firestarter is going:

http://bbs.archlinux.org/viewtopic.php?id=57454

I'll try some of the suggestions tonight when I get home from work.

Regards

André
Comment by André Fettouhi (A.Fettouhi) - Monday, 15 December 2008, 18:50 GMT
Well both of them woerk, I can start firestarter by running

sudo firestarter

and

gksu dbus-launcher firestarter

Regards

André
Comment by Hugo Doria (hdoria) - Friday, 19 December 2008, 15:37 GMT
It works here too. Anyone else with this problem?
Comment by Dale Blount (dale) - Thursday, 19 February 2009, 20:26 GMT
Sorry, I missed your request to see if anyone else had the problem...


$ gksu gnome-terminal

(gnome-terminal:26940): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
**
ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
Comment by Lucas Salies Brum (sistematico) - Monday, 06 April 2009, 13:02 GMT
Same problem...
Comment by Lucas Salies Brum (sistematico) - Tuesday, 07 April 2009, 18:53 GMT
(lucas@c3po ~)$ gksu gnome-terminal

** (gnome-terminal:3346): WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported

Failed to get the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Falling back to non-factory mode.
Failed to contact the GConf daemon; exiting.
Comment by Lucas Salies Brum (sistematico) - Tuesday, 07 April 2009, 18:56 GMT
After installation of Gnome 2.26 GConf of root is completely clean.
Comment by Alessandro Doro (adoroo) - Tuesday, 07 April 2009, 22:37 GMT
@sistematico: look at http://bugs.archlinux.org/task/14107#comment42340 for the gconf problem.
Comment by Dale Blount (dale) - Tuesday, 26 May 2009, 15:18 GMT
My error message has transformed to the one Lucas is getting. I also tried the fix for GConf segfaults from #14107 with no success.

Loading...