Hi,
I'm having a lot of trouble getting Gnome set up. I've run clean installs
several times, here's the current status:
I've successfully installed the base potato config, a bunch of other
packages, and Ximian-Gnome. When I run startx to start X-windows, I get a
cursor and a test-pattern
On Thu, Jan 06, 2000 at 02:56:21PM -0700, Cameron Matheson wrote:
Hey everybody!
Now that I have gotten my scripts and executables to work (thanks to your
help) I was wondering if I could customize the menus in X Windows so that my
games would show up in the menu (I looked for a config file
Hey everybody!
Now that I have gotten my scripts and executables to work (thanks to your
help) I was wondering if I could customize the menus in X Windows so that my
games would show up in the menu (I looked for a config file for something
like that, but I couldn't find anything. The window
Ok, I know how to use Debain packages, but which ones are needed for a semi
full install that will allow use of either KDE or GNOME? If someone can
point to a walkthrough of installation for Debain, or just some advice,
it'd be greatly appreciated.
Hi, people!
I have a problem. I have
tried to install Xwindows on my 486100, but it 'cannot find the packages'. I've
used dpkg to... de-package the files but none of the resulting files run at all.
I've tried doing it from my Win98 partition, but same result. I've used dselect,
but again
On Thu, 22 Oct 1998, Derek McCabe wrote:
Hi, people!
I have a problem. I have tried to install Xwindows on my 486100, but
it 'cannot find the packages'. I've used dpkg to... de-package the files
but none of the resulting files run at all.
What exactly are you trying to do? you should
At 08:50 AM 12/12/97 +0100, Sten Anderson wrote:
Tommy Lakofski [EMAIL PROTECTED] writes:
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
[ I said: ]
It is NOT necessary for the last command to be
On 12 Dec 1997, Sten Anderson wrote:
Tommy Lakofski [EMAIL PROTECTED] writes:
Yes, by using exec to launch a command from a script, the process
associated with the script (/bin/sh) is replaced by the process
associated with the command. This saves a few system resources, since
the script
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
It is NOT necessary for the last command to be started with exec. In
fact, exec should only be used on the window manager, and only if that
is the last command
Tommy Lakofski [EMAIL PROTECTED] writes:
whoops, this should have gone to the list too.
-- Forwarded message --
On Thu, 11 Dec 1997, Hamish Moffatt wrote:
[ I said: ]
It is NOT necessary for the last command to be started with exec. In
fact, exec should only be
At 09:15 AM 12/10/97 -0600, Jens B. Jorgensen wrote:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This would cause the X server
At 04:32 PM 12/10/97 +0100, Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
On Wed, Dec 10, 1997 at 05:51:40AM +0800, Bryan Barcelo wrote:
At 04:32 PM 12/10/97 +0100, Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
Hamish Moffatt [EMAIL PROTECTED] writes:
The window manager should always be last too. Specifically, the last
command should not end in , but it's most useful if that's the window
manager. You could make it xclock or something, but then you'd
have to kill the clock somehow to logout.
Depends
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if that's the window
| manager. You could make it xclock or
Alan Su [EMAIL PROTECTED] writes:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if that's the window
|
Alan Su [EMAIL PROTECTED] writes:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|
|Depends - most window managers will send a message to all active X
|clients when they exit that causes them to shut down.
|
I don't think this is right...I've fiddled a lot with window
On Wed, Dec 10, 1997 at 08:00:30PM -0800, Alan Su wrote:
Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
|Hamish Moffatt [EMAIL PROTECTED] writes:
|
| The window manager should always be last too. Specifically, the last
| command should not end in , but it's most useful if
Hamish Moffatt wrote (Thu, 11 Dec 1997 18:36:55 +1100 ):
|On Wed, Dec 10, 1997 at 08:00:30PM -0800, Alan Su wrote:
| Daniel Martin at cush wrote (Wed, 10 Dec 1997 22:34:52 -0500 ):
| |Hamish Moffatt [EMAIL PROTECTED] writes:
| |
| | The window manager should always be last too. Specifically, the
Sten Anderson wrote (10 Dec 1997 16:32:12 +0100 ):
|Jens B. Jorgensen [EMAIL PROTECTED] writes:
|
| These messages do not indicate a fatal error, only that you haven't
| installed these X extensions. If you're using your own .xinitrc,
| are you sure that the last command uses 'exec' rather than
Alan Su [EMAIL PROTECTED] writes:
Is there something wrong with using exec on an xterm, rather than a
window manager? I'm currently doing that which makes the duration of
an x session depend on the xterm rather than the window manager (which
is what I prefer), and I haven't run into any
Alan Su wrote:
Sten Anderson wrote (10 Dec 1997 16:32:12 +0100 ):
|Jens B. Jorgensen [EMAIL PROTECTED] writes:
|
| These messages do not indicate a fatal error, only that you haven't
| installed these X extensions. If you're using your own .xinitrc,
| are you sure that the last command
Hi Paul,
Sorry to bother you again, but I found the file you said and checked it out
and it seemed okay. I also made changes to the .xinitrc file in my
subdirectory. It worked for fvwm2 but when I replaced fvwm2 with olvwm,
xwindows loads up to the light blue background and then shuts down
Bryan Barcelo wrote:
Hi Paul,
Sorry to bother you again, but I found the file you said and checked it out
and it seemed okay. I also made changes to the .xinitrc file in my
subdirectory. It worked for fvwm2 but when I replaced fvwm2 with olvwm,
xwindows loads up to the light blue
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This would cause the X server to
Sten Anderson wrote:
Jens B. Jorgensen [EMAIL PROTECTED] writes:
These messages do not indicate a fatal error, only that you haven't
installed these X extensions. If you're using your own .xinitrc,
are you sure that the last command uses 'exec' rather than just
running a program? This
Hi! I'm having problems running X Windows after installing it. There's no
default window manager after running 'startx' at the command prompt even
if I specified one during the installation, so I have to type whatever
window manager I want to use at the console after it starts up. Does
anyone
Hello Bryan,yes there is a file that has the windows manager information.
It also tells what order to start them in. But you can only have one
running at a time. Here is mine, it is in /etc/X11/windows-managers
# This file contains a list of available window managers. The default
# Xsession
28 matches
Mail list logo
