Re: "cannot open display: :0.0" error when using schroot

[Bob McGowan <bob_mcgowan@symantec.com>]

Aniruddha wrote:
> On Fri, 2008-08-22 at 09:43 -0700, Bob McGowan wrote:
> > What does 'xhost' say when you run it as the "normal" user (before you 
> > do the schroot)?
> >
> > You may need to do an 'xhost local:' to allow any local (only your host 
> > system logins) user to connect to the display.  You will need the 
> > DISPLAY=:0.0 exported in the schroot environment, at least.
>
> Thanks for the help! Here's the output of those commands:
>
> > ~$ xhost
> > access control enabled, only authorized clients can connect
>
> ~$ xhost local:
> > non-network local connections being added to access control list
>
> $ schroot  -p nero
> > I: [sid-1516ecae-815d-4eb3-ab8c-c7a94befa26f chroot] Running command:
> > “nero”
> > Gtk-Message: Failed to load module "gnomebreakpad":
> > libgnomebreakpad.so: cannot open shared object file: No such file or
> > directory
> >
> > (nero:23894): Gtk-WARNING **: cannot open display: :0.0
>
>
> Regards,
>
> Aniruddha

I'd guess "libgnomebreakpad.so" is not accessible from within the 
schroot environment.

And without it, GTK and nero can't do anything affecting the display.

*However*, this is all guesswork, my knowledge of schroot (or chroot, 
for that matter) is pretty minimal.

What I do know is that a chroot is an isolated area that needs to have 
all the support files, executables and libraries set up correctly within 
the chroot environment for things to work.  After all, it is a jail, 
intended to keep the user from accessing things above the jail's root 
directory.

Don't know if my ramblings will be of any help ;(, good luck may be the 
only thing further I can say.

--
Bob McGowan

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature