I have set up a schroot using this guide:
http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id292205 , but for some reason when I try to run a program I get the following error:

> ~$ schroot -p nero
> W: Group ‘sbuild’ not found
> I: [sid chroot] Running command: “nero�
>
> (nero:456): Gtk-WARNING **: cannot open display: :0.0

I have set up a succesfull schroot before, the only difference now is
that I use sudo.

"DISPLAY=:0" doesn't work either:

> (sid32)root@Desktop:/# export DISPLAY=:0
> (sid32)root@Desktop:/# nero
>
> (nero:4231): Gtk-WARNING **: cannot open display: :0

My schroot.conf
> [sid]
> description=Debian sid (unstable)
> location=/var/chroot/sid
> priority=3
> users=rleigh,aniruddha
> groups=sbuild,aniruddha
> root-groups=root
> aliases=unstable,default

Regards,

Aniruddha



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Aniruddha wrote:
I have set up a schroot using this guide:
http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html#id292205 , but for some reason when I try to run a program I get the following error:



~$ schroot -p nero
W: Group ‘sbuild’ not found
I: [sid chroot] Running command: “nero�

(nero:456): Gtk-WARNING **: cannot open display: :0.0


I have set up a succesfull schroot before, the only difference now is
that I use sudo.

"DISPLAY=:0" doesn't work either:


(sid32)root@Desktop:/# export DISPLAY=:0
(sid32)root@Desktop:/# nero

(nero:4231): Gtk-WARNING **: cannot open display: :0


My schroot.conf

[sid]
description=Debian sid (unstable)
location=/var/chroot/sid
priority=3
users=rleigh,aniruddha
groups=sbuild,aniruddha
root-groups=root
aliases=unstable,default




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.


--
Bob McGowan

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



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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

On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> 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.


Thanks for the help. I tried lots and lots of things (including
everything in this thread:
http://ubuntuforums.org/showthread.php?t=166863 ) to no avail

Who has an idea what might be wrong?


Regards,

Aniruddha



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Sat, Aug 23, 2008 at 08:12:11PM +0200, Aniruddha wrote:
> On Fri, 2008-08-22 at 11:17 -0700, Bob McGowan wrote:
> > 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.
>
>
> Thanks for the help. I tried lots and lots of things (including
> everything in this thread:
> http://ubuntuforums.org/showthread.php?t=166863 ) to no avail
>
> Who has an idea what might be wrong?

Try running with -p to copy the environment, otherwise it's set up
from scratch.

Also make sure your home directory is available in the chroot
(for .Xauthority).


Regards,
Roger

--
.'`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.