🚀 go-pugleaf

Patrick Wiseman ha scritto:
> Running 'sudo gnome-terminal' (which is the equivalent) reports
> 'Failed to contact the GConf daemon; exiting.'  How do I fix this?  Is
> it some idiotic "security feature"?  (I get really steamed when fear
> overrides function!)
>
> Patrick
>
>

Workaround: launch a terminal and sudo $favorite_shell
(possibly with a keyboard shortcut)
-------------------
As for your solution not working: my *guess* is that to launch a
gnome-terminal you need some per-user helper program (gconf) which
cannot be run because root has no X session open - and that's a good
thing(tm), beause you don't want anyone else but you to be able to
create/close/modify windows or any other gui object on your screen.
But then again - it's just my guess.

Patrick Wiseman ha scritto:
> Running 'sudo gnome-terminal' (which is the equivalent) reports
> 'Failed to contact the GConf daemon; exiting.'  How do I fix this?  Is
> it some idiotic "security feature"?  (I get really steamed when fear
> overrides function!)
>
> Patrick
>
>

A solution that really solves it: create a new profile, and have it
running something other than the default command, like "su -" or "sudo
/bin/bash -i -l" or...

On Sun, Jun 14, 2009 at 4:19 AM, Andrei Popescu<andreimpopescu@gmail.com> wrote:
> On Sat,13.Jun.09, 09:32:52, Patrick Wiseman wrote:
>> Running 'sudo gnome-terminal' (which is the equivalent) reports
>
> How do you know that? I thought gksu was used for that. Try:
>
> gksu gnome-terminal

That yields:

** (gnome-terminal:14228): WARNING **: Failed to connect to the
session manager: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based
authentication failed

Failed to contact the GConf daemon; exiting.

Which, I suppose, is slightly more informative.  But the fact remains
that Root Terminal in the Accessories menu is, for some reason,
disabled.  (This is on a fully up-to-date, amd64, testing system.)

Patrick

--Ns7jmDPpOpCD+GE/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat,13.Jun.09, 09:32:52, Patrick Wiseman wrote:
> Running 'sudo gnome-terminal' (which is the equivalent) reports

How do you know that? I thought gksu was used for that. Try:

gksu gnome-terminal

Regards,
Andrei
-- 
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)

--Ns7jmDPpOpCD+GE/
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBCAAGBQJKNLKHAAoJEHNWs3jeoi3pKToH/3HJVnNdpCYxGujqxUsbosgs
DRqq6R+J0q9IaYu7ISFG9kX4WsK/vFMeBBXlZ5m+NZM7aEYxc8Rs6ElgPub/glFd
1QwoTlnIhSO/VfuySXzjLdaL1T9UuJJqN/aj996KiEahDn5WG06Pj7SMtcQ2ywI2
lpGIhNbW6eFwMUSEhp4TPb2h8FgUYXEuV4YTTL2j8MgqUPzD32yP3seSaKYkR6GF
BrZHUzP0LWdEwvNv2qGtopDsv8/hJkjI/uleGiYQ77HDtatHIOwqmuhBFkP5yDUS
61WlSpLP8QqoQIn7hz5YhaOc6bbOmz+gV6xMEbNhEzQAdCmJHyQHhynUOD5BHlA=VT+J
-----END PGP SIGNATURE-----

--Ns7jmDPpOpCD+GE/--

On Sun, Jun 14, 2009 at 08:16:26AM -0400, Patrick Wiseman wrote:
> On Sun, Jun 14, 2009 at 4:19 AM, Andrei Popescu<andreimpopescu@gmail.com> wrote:
> > On Sat,13.Jun.09, 09:32:52, Patrick Wiseman wrote:
> >> Running 'sudo gnome-terminal' (which is the equivalent) reports
> >
> > How do you know that? I thought gksu was used for that. Try:
> >
> > gksu gnome-terminal
>
> That yields:
>
> ** (gnome-terminal:14228): WARNING **: Failed to connect to the
> session manager: Authentication Rejected, reason : None of the
> authentication protocols specified are supported and host-based
> authentication failed
>
> Failed to contact the GConf daemon; exiting.
>
> Which, I suppose, is slightly more informative.  But the fact remains
> that Root Terminal in the Accessories menu is, for some reason,
> disabled.  (This is on a fully up-to-date, amd64, testing system.)

I do not know about testing ... but
* Did you set up password for root or was it just for user?
* Did you set up gksu to use su or sudo?

Osamu

On Mon, Jun 15, 2009 at 09:36:34AM -0400, Patrick Wiseman <pwiseman@gmail.com> was heard to say:
> On Mon, Jun 15, 2009 at 9:11 AM, Matus UHLAR -
> fantomas<uhlar@fantomas.sk> wrote:
> > why do you want to sun gnome-terminal under sudo, instead of running su/sudo
> > in gnome terminal?
>
> Doing the former allows me to open new tabs as root, doing the latter
> (with 'su') requires that I provide my root password every time; using
> 'sudo' requires that I provide 'sudo command' every time.  It's just a
> lot less convenient, but still doable, which is why the security
> excuse is BS.  It's yet another example of sacrificing function to
> fear.

  It looks like you can create a profile for gnome-terminal that tells
it to launch a custom command instead of your login shell (say,
"sudo bash").  I don't know if you can tell gnome-terminal that all
the tabs in a window should get a particular profile, but it might be
worth exploring.

  Daniel

On Mon, Jun 15, 2009 at 9:11 AM, Matus UHLAR -
fantomas<uhlar@fantomas.sk> wrote:
> On 13.06.09 09:32, Patrick Wiseman wrote:
>> Running 'sudo gnome-terminal' (which is the equivalent) reports
>> 'Failed to contact the GConf daemon; exiting.'  How do I fix this?  Is
>> it some idiotic "security feature"?  (I get really steamed when fear
>> overrides function!)
>
> why do you want to sun gnome-terminal under sudo, instead of running su/sudo
> in gnome terminal?

Doing the former allows me to open new tabs as root, doing the latter
(with 'su') requires that I provide my root password every time; using
'sudo' requires that I provide 'sudo command' every time.  It's just a
lot less convenient, but still doable, which is why the security
excuse is BS.  It's yet another example of sacrificing function to
fear.

Patrick

On Mon, Jun 15, 2009 at 9:50 AM, Tony Baldwin<photodharma@gmail.com> wrote:
> Patrick Wiseman wrote:
>>
>> On Mon, Jun 15, 2009 at 9:11 AM, Matus UHLAR -
>> fantomas<uhlar@fantomas.sk> wrote:
>>>
>>> On 13.06.09 09:32, Patrick Wiseman wrote:
>>>>
>>>> Running 'sudo gnome-terminal' (which is the equivalent) reports
>>>> 'Failed to contact the GConf daemon; exiting.'  How do I fix this?  Is
>>>> it some idiotic "security feature"?  (I get really steamed when fear
>>>> overrides function!)
>>>
>>> why do you want to sun gnome-terminal under sudo, instead of running
>>> su/sudo
>>> in gnome terminal?
>>
>> Doing the former allows me to open new tabs as root, doing the latter
>> (with 'su') requires that I provide my root password every time; using
>> 'sudo' requires that I provide 'sudo command' every time.  It's just a
>> lot less convenient, but still doable, which is why the security
>> excuse is BS.  It's yet another example of sacrificing function to
>> fear.
>>
>> Patrick
>>
>>
>
> Did you try
> gksu gnome-terminal
> ?
> If not, do try.

Yes - with gksu set to sudo-mode, it fails silently (i.e. no warning,
but no terminal either); with sudo-mode off, I get:

** (gnome-terminal:22316): WARNING **: Failed to connect to the
session manager: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based
authentication failed

Failed to contact the GConf daemon; exiting.

Patrick

On 13.06.09 09:32, Patrick Wiseman wrote:
> Running 'sudo gnome-terminal' (which is the equivalent) reports
> 'Failed to contact the GConf daemon; exiting.'  How do I fix this?  Is
> it some idiotic "security feature"?  (I get really steamed when fear
> overrides function!)

why do you want to sun gnome-terminal under sudo, instead of running su/sudo
in gnome terminal?

--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
"The box said 'Requires Windows 95 or better', so I bought a Macintosh".