Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Jun 2008 22:29:29 -0400
From:      Tim Kellers <timothyk@wallnet.com>
To:        Warren Liddell <shinjii@maydias.com>
Cc:        "Edwin L. Culp" <eculp@casasponti.net>, freebsd-questions@freebsd.org
Subject:   Re: Howto get k3b to detect my Burner
Message-ID:  <4866F389.9080605@wallnet.com>
In-Reply-To: <200806291207.51736.shinjii@maydias.com>
References:  <200806281902.47156.shinjii@maydias.com> <200806290934.29645.shinjii@maydias.com> <20080628205436.57696utq5kx3stgk@pontinet.casasponti.net> <200806291207.51736.shinjii@maydias.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Warren Liddell wrote:
>> I don't think that is the problem.  Have you tried it as root just as
>> a test even though it gives you warnings.
>>
>> I don't know what else to suggest right now.
>>
>> ed
>>     
>
> k3b wont run as root & i guess k3b just dosent like my burner
>
> # k3b
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
>
> kdeinit: Can't connect to the X Server.
> kdeinit: Might not terminate at end of session.
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
>
> kded: cannot connect to X server :0.0
> kded: ERROR: KUniqueApplication: Registering failed!
> kded: ERROR: Communication problem with kded, it probably crashed.
> Xlib: connection to ":0.0" refused by server
> Xlib: No protocol specified
>
> k3b: cannot connect to X server :0.0
> ERROR: KUniqueApplication: Registering failed!
> ERROR: Communication problem with k3b, it probably crashed.
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
>
>
>   
Before you try to run k3b as root,  from an xterm (or konsole) in KDE. 
as your normal user, type:
xhost  localhost

(you should get a message like: "localhost being added to access control 
list")

then su to root and try running k3b.

One note:  I have had trouble allowing other hosts (or users) to connect 
to my X server session when I've used kdm as a login manager.  Rather 
than dig through the configuration, I usually switch to xdm ( edit 
/etc/ttys) when I need to allow other connections.

Tim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4866F389.9080605>