Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-02-01 Thread Mick
On Sunday 01 Feb 2015 00:18:40 Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough,

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-02-01 Thread Alan McKinnon
On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-02-01 Thread Alan McKinnon
On 01/02/2015 17:07, Peter Humphrey wrote: On Sunday 01 February 2015 14:17:04 Alan McKinnon wrote: On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-02-01 Thread Peter Humphrey
On Sunday 01 February 2015 14:17:04 Alan McKinnon wrote: On 01/02/2015 02:18, Adam Carter wrote: If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-02-01 Thread Peter Humphrey
On Sunday 01 February 2015 18:00:23 Alan McKinnon wrote: On 01/02/2015 17:07, Peter Humphrey wrote: I think of it simply like this: su switches user, and that's all; su - gives you the full environment of the user you switch to. Indeed, that is the heart of it. Your version above is

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Alec Ten Harmsel
On 01/31/2015 05:29 PM, Joseph wrote: When I run meld as root I get a strange errors: what happens when you don't run as root? GConf Error: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Adam Carter
On Sun, Feb 1, 2015 at 9:29 AM, Joseph syscon...@gmail.com wrote: When I run meld as root I get a strange errors: GConf Error: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security

[gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Joseph
When I run meld as root I get a strange errors: GConf Error: Client failed to connect to the D-BUS daemon: 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

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Joseph
On 02/01/15 11:06, Adam Carter wrote: On Sun, Feb 1, 2015 at 9:29 AM, Joseph [1]syscon...@gmail.com wrote: When I run meld as root I get a strange errors: GConf Error: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Adam Carter
If you've su'd to root, try 'su -' instead. Thank you, that was it? What difference does it make and why on some boxes it has to be su - and on others simple su works. Read 'man su'. I dont really understand this stuff well enough, but a 'login shell', that is, one started by /bin/login,

Re: [gentoo-user] meld - GConf Error: Client failed to connect to the D-BUS

2015-01-31 Thread Joseph
On 01/31/15 17:57, Alec Ten Harmsel wrote: On 01/31/2015 05:29 PM, Joseph wrote: When I run meld as root I get a strange errors: what happens when you don't run as root? GConf Error: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the