Another way to do it is to run 'su -m'. I had some problem trying to execute some
X-windows programs as root when I was a simple user and that solved it. Of course YMMV.
On Mon, 17 Feb 2003 15:20:01 +0200
Voicu Liviu [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
On Tuesday 18 February 2003 02:10, Peter Ruskin wrote:
/var/db/pkg/category/ebuild/USE, for example:
/var/db/pkg/gnome-base/bonobo-1.0.22/USE
I has been stored for a LONG LONG time, but does it actually get used, and
how. As far as I know the sticky variable bugs (#13616 among others) are
On Tuesday 18 Feb 2003 09:18, Paul de Vrieze wrote:
On Tuesday 18 February 2003 02:10, Peter Ruskin wrote:
/var/db/pkg/category/ebuild/USE, for example:
/var/db/pkg/gnome-base/bonobo-1.0.22/USE
I has been stored for a LONG LONG time, but does it actually get used,
and how. As far as I know
When stopping vim in an su - xterm/aterm session, I always get:
Xlib: connection to :0.0 refused by server
Xlib: No protocol specified
How can I fix this?
--
Collins Richey - Denver Area
Athlon-XP gentoo 1.4_rc2 kde 3.1
--
[EMAIL PROTECTED] mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 17 February 2003 15:22, Collins wrote:
When stopping vim in an su - xterm/aterm session, I always get:
Xlib: connection to :0.0 refused by server
Xlib: No protocol specified
How can I fix this?
Before you login with su do:
$ xhost
On Monday 17 February 2003 12:36 pm, D. Wollmann wrote:
On Monday 17 February 2003 07:22, Collins wrote:
When stopping vim in an su - xterm/aterm session, I always get:
Xlib: connection to :0.0 refused by server
Xlib: No protocol specified
How can I fix this?
In addition to the
On Monday 17 Feb 2003 20:41, Collins wrote:
Or, as I just did, `USE=-X emerge vim` and file a bugzilla about
this. Problem is gone permanently, or until the next time I need to
emerge vim!
Collins,
Next time will probably be OK - your USE setting will be remembered.
Peter
--
Gentoo-1.4.2.8
On Mon, Feb 17, 2003 at 03:47:40PM -0500, Peter Ruskin wrote:
On Monday 17 Feb 2003 20:41, Collins wrote:
Or, as I just did, `USE=-X emerge vim` and file a bugzilla about
this. Problem is gone permanently, or until the next time I need to
emerge vim!
Collins,
Next time will probably
On Tuesday 18 Feb 2003 00:10, Tyler Trafford wrote:
On Mon, Feb 17, 2003 at 03:47:40PM -0500, Peter Ruskin wrote:
On Monday 17 Feb 2003 20:41, Collins wrote:
Or, as I just did, `USE=-X emerge vim` and file a bugzilla about
this. Problem is gone permanently, or until the next time I need
