Arch Linux

sergec

Member

Registered: 2007-01-23

Posts: 9

Opening ark as a different user in a konsole

Hi everybody

Coming from gentoo, I was used to run for instance ark as a different user in konsole belonging to another user.
Let me be clearer...
Let's say I logged as serge in KDE.
The user john wants to run 'ark" in konsole from serge's session, he will do:

[serge@mypc ~]$ su john
Password:
[john@mypc serge] $

Now if he runs 'ark':

[john@mypc serge]$ ark kink-0.2.1.tar.bz2

he will get:

No protocol specified
kdeinit: Can't connect to the X Server.
kdeinit: Might not terminate at end of session.
No protocol specified
kded: cannot connect to X server :0
DCOP aborting call from 'anonymous-19230' to 'kded'
kded: ERROR: Communication problem with kded, it probably crashed.
No protocol specified
ark: cannot connect to X server :0
DCOP aborting call from 'anonymous-19221' to 'ark'
ERROR: Communication problem with ark, it probably crashed.
[john@mypc serge]$

How to make it work?

Thank you for your help

Serge

Last edited by sergec (2007-11-10 20:06:55)

Ramses de Norre

Member

From: Leuven - Belgium

Registered: 2007-03-27

Posts: 1,289

Re: Opening ark as a different user in a konsole

Try running xhost + first, that'll turn off X' access control.

Dusty

Schwag Merchant

From: Medicine Hat, Alberta, Canada

Registered: 2004-01-18

Posts: 5,986

Website

Re: Opening ark as a different user in a konsole

That is, run xhost + before you su.

If it works, you can put the command in your ~/.bashrc so its run at every login.

Its probably safer to run xhost +localhost than xhost + -- it technically allows users to connect even from a different computer.

Dusty

---

** Arch Linux Apparel and more ** Arch Linux stickers, laptop bags, jewelery ** I wrote a book on Python 3 ** and one on mental health **

Ramses de Norre

Member

From: Leuven - Belgium

Registered: 2007-03-27

Posts: 1,289

Re: Opening ark as a different user in a konsole

Or use sudo, which doesn't require you to turn off the access control.
xhost + was in fact only a suggestion to check whether the problem lies there.