On 8/6/19 12:29 AM, Curt wrote:
On 2019-08-06, Ed wrote:
On 2019-08-06 09:02+0300, Andrei POPESCU wrote:
On Lu, 05 aug 19, 21:56:55, Ed wrote:
How do you run two login managers though so that you can have two users
share the same computer without having to log out? In other words,
whilst I
On Thu, Aug 22, 2019 at 07:58:51PM +0300, Andrei POPESCU wrote:
It should be possible to run something like
startx -- :1
to open a second X instance on the virtual console. You have to figure
out how to start the second X on the other display.
It's not that easy with one multiport video
On Mi, 21 aug 19, 16:01:17, Franklin, Jason wrote:
> Greetings,
>
> I'm working on a project that requires me to debug a running screen locker.
>
> Currently, my workflow involves switching between the screen locker and
> virtual
> console #1 (/dev/tty1) using Ctrl-Alt-F1 and Ctrl-Alt-F7.
rhkra...@gmail.com wrote:
> On Thursday, August 22, 2019 10:08:16 AM Dan Ritter wrote:
> > Franklin, Jason wrote:
> > > Greetings,
> > >
> > > I'm working on a project that requires me to debug a running screen
> > > locker.
> > >
> > > Currently, my workflow involves switching between the
On Thursday, August 22, 2019 10:08:16 AM Dan Ritter wrote:
> Franklin, Jason wrote:
> > Greetings,
> >
> > I'm working on a project that requires me to debug a running screen
> > locker.
> >
> > Currently, my workflow involves switching between the screen locker and
> > virtual console #1
Franklin, Jason wrote:
> Greetings,
>
> I'm working on a project that requires me to debug a running screen locker.
>
> Currently, my workflow involves switching between the screen locker and
> virtual
> console #1 (/dev/tty1) using Ctrl-Alt-F1 and Ctrl-Alt-F7. This way, I can
> interact
On Wed, Aug 21, 2019 at 04:01:17PM -0400, Franklin, Jason wrote:
I'm working on a project that requires me to debug a running screen locker.
Currently, my workflow involves switching between the screen locker and virtual
console #1 (/dev/tty1) using Ctrl-Alt-F1 and Ctrl-Alt-F7. This way, I can
Greetings,
I'm working on a project that requires me to debug a running screen locker.
Currently, my workflow involves switching between the screen locker and virtual
console #1 (/dev/tty1) using Ctrl-Alt-F1 and Ctrl-Alt-F7. This way, I can
interact with the screen locker until I hit a break
On 2019-08-06 10:31-0400, Gene Heskett wrote:
> I did, created a user test, logged in, but when I came back to the
> machine 10 minutes later, the screen was locked and showing gene as
> the default login.
dm-tool did work to switch the user. That solves a problem for now.
Please don't see
On Tuesday 06 August 2019 09:22:15 Curt wrote:
> On 2019-08-06, deloptes wrote:
> > Curt wrote:
> >> LightDM's dm-tool command can be used to allow multiple users to be
> >> logged in on separate ttys. The following will send a signal
> >> requesting that the current session be locked and then
On Tue 06 Aug 2019 at 07:11:04 (+0100), Ed wrote:
> On 2019-08-05 16:59-0500, David Wright wrote:
> > Perhaps this is all to do with your DM. I use startx, and since
> > stretch the Xserver runs "on top of" the VC that started it, and
> > as the user, not root. In the past, Xservers ran as root on
On 2019-08-06, Curt wrote:
>>
>> it says multiple users - not the same user
>>
>>
>
> curty@einstein:~/glimmer$ man dm-tool
>
> switch-to-greeter
>Switch to the greeter suitable for logging into a new
>session.
>
> Says "logging into a new *session*." (emphasis mine).
On 2019-08-06, deloptes wrote:
> Curt wrote:
>
>> LightDM's dm-tool command can be used to allow multiple users to be logged
>> in on separate ttys. The following will send a signal requesting that the
>> current session be locked and then will initiate a switch to LightDM's
>> greeter, allowing
Curt wrote:
> LightDM's dm-tool command can be used to allow multiple users to be logged
> in on separate ttys. The following will send a signal requesting that the
> current session be locked and then will initiate a switch to LightDM's
> greeter, allowing a new user to log in to the system.
it
On 2019-08-06, Ed wrote:
> On 2019-08-06 09:02+0300, Andrei POPESCU wrote:
>> On Lu, 05 aug 19, 21:56:55, Ed wrote:
>> >
>> > How do you run two login managers though so that you can have two users
>> > share the same computer without having to log out? In other words,
>> > whilst I go and
On 2019-08-06 09:02+0300, Andrei POPESCU wrote:
> On Lu, 05 aug 19, 21:56:55, Ed wrote:
> >
> > How do you run two login managers though so that you can have two users
> > share the same computer without having to log out? In other words,
> > whilst I go and make dinner I want to allow someone
On 2019-08-05 16:59-0500, David Wright wrote:
> Perhaps this is all to do with your DM. I use startx, and since
> stretch the Xserver runs "on top of" the VC that started it, and
> as the user, not root. In the past, Xservers ran as root on VC7,
> VC8, …
Does lightdm or gdm act as your greeter? I
On Lu, 05 aug 19, 21:56:55, Ed wrote:
>
> How do you run two login managers though so that you can have two users
> share the same computer without having to log out? In other words,
> whilst I go and make dinner I want to allow someone else to sit here,
> without having to shut applications
On Mon 05 Aug 2019 at 21:56:55 (+0100), Ed wrote:
> On 2019-08-05 13:11+0200, deloptes wrote:
> > IMO you can not run multiple X sessions from the same user. I am not
> > 100% sure, but I can imagine what would happen with the session
> > manager.
>
> I have done in the past, one 'ed' would run
On 2019-08-05 13:11+0200, deloptes wrote:
> IMO you can not run multiple X sessions from the same user. I am not
> 100% sure, but I can imagine what would happen with the session
> manager.
I have done in the past, one 'ed' would run xfce and another would run
evilwm. However, the majority of
On 2019-08-05 09:57-, Curt wrote:
> On 2019-08-04, Ed wrote:
> > Hello,
> >
> > For years I would happily ctrl-alt-f<1-6> for an additional x.org
> > session by running 'startx' and another window manager. Until now-ish.
> >
> > What I have observed is that x sessions started from a text
On 2019-08-05, Felix Miata wrote:
> Curt composed on 2019-08-05 11:29 (UTC):
>
>> Maybe this is the bug we're looking for:
>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834270
>
>> Fix (Simon says):
>
>> * removing the call to /usr/bin/clear_console from ~/.bash_logout
>> (console is
On 2019-08-05 11:11-0400, Felix Miata wrote:
>
> > Fix (Simon says):
>
> > * removing the call to /usr/bin/clear_console from ~/.bash_logout
> > (console is cleared anyway nowadays)
> > * replacing the call to /usr/bin/clear_console with /usr/bin/reset in
> > ~/.bash_logout
Why would
Curt composed on 2019-08-05 11:29 (UTC):
> Maybe this is the bug we're looking for:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834270
> Fix (Simon says):
> * removing the call to /usr/bin/clear_console from ~/.bash_logout
> (console is cleared anyway nowadays)
> * replacing the
On 2019-08-04, Ed wrote:
>
> 1. log in via lightdm/gdm
> 2. switch to a text console
> 3. run startx and use the window manager for a moment or two
> 4. switch back to first session
Maybe this is the bug we're looking for:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834270
Fix
Ed wrote:
> For years I would happily ctrl-alt-f<1-6> for an additional x.org
> session by running 'startx' and another window manager. Until now-ish.
>
> The way to reproduce the problem is as follows:
>
> 1. log in via lightdm/gdm
> 2. switch to a text console
> 3. run startx and use the
On 2019-08-04, Ed wrote:
> Hello,
>
> For years I would happily ctrl-alt-f<1-6> for an additional x.org
> session by running 'startx' and another window manager. Until now-ish.
>
>
> What I have observed is that x sessions started from a text console can
> cooperate with each other, it seems
On 2019-08-04 20:06-0400, Felix Miata wrote:
> Works on 32 bit Buster on host m7ncd here, with one little glitch that
> Ctrl-Alt-F3
I've not tried 32bit. I'll get the ISO and give that a whirl.
> memory currently lacks any connective dots between
>
On 2019-08-04 22:54+0100, nektarios wrote:
> Indeed the problem seems reproducible for debian Stretch with sddm
> display manager.
> The only logs appearing are from KDE applications (nothing in X11 logs):
Could this be systemd? My only thoughts are that systemd starts the x
server on a vt, but
Ed composed on 2019-08-04 21:01 (UTC+0100):
> For years I would happily ctrl-alt-f<1-6> for an additional x.org
> session by running 'startx' and another window manager. Until now-ish.
> The way to reproduce the problem is as follows:
> 1. log in via lightdm/gdm
> 2. switch to a text
On Sun, 4 Aug 2019 18:36:44 -0400
Cindy Sue Causey wrote:
> On 8/4/19, nektarios wrote:
> > On Sun, 4 Aug 2019 21:01:57 +0100
> > Ed wrote:
> >>
> >> What I have observed is that x sessions started from a text console
> >> can cooperate with each other, it seems limited to lightdm/gdm
> >>
On 8/4/19, nektarios wrote:
> On Sun, 4 Aug 2019 21:01:57 +0100
> Ed wrote:
>>
>> What I have observed is that x sessions started from a text console
>> can cooperate with each other, it seems limited to lightdm/gdm logins
>> only.
>>
>> Something happened between jobs which meant I didn't need
On 8/4/19, Ed wrote:
> For years I would happily ctrl-alt-f<1-6> for an additional x.org
> session by running 'startx' and another window manager. Until now-ish.
>
> The way to reproduce the problem is as follows:
>
> 1. log in via lightdm/gdm
> 2. switch to a text console
> 3. run startx
On Sun, 4 Aug 2019 21:01:57 +0100
Ed wrote:
> Hello,
>
> For years I would happily ctrl-alt-f<1-6> for an additional x.org
> session by running 'startx' and another window manager. Until now-ish.
>
> The way to reproduce the problem is as follows:
>
> 1. log in via lightdm/gdm
> 2.
Hello,
For years I would happily ctrl-alt-f<1-6> for an additional x.org
session by running 'startx' and another window manager. Until now-ish.
The way to reproduce the problem is as follows:
1. log in via lightdm/gdm
2. switch to a text console
3. run startx and use the window manager
Yeah, but why does it take several seconds?
Have you tried another DE/WM combination?
So, really in fact, you want to run KDE at a higher resolution than what
your card is capable of?
I don't know why the virtual consoles go BLANK only after about 20 seconds,
it seems to be a problem
(tty7) to virtual-consoles (tty1 .. tty6) and login
in text-mode -- after a few seconds, theese virtual-consoles will go BLANK.
A few seconds? That is weird. What happens if you start in single user
mode and login as root?
--
If you're not careful, the newspapers will have you hating the people
Hello Chris,
perhaps I do not understand your proposal ... if I switch to runlevel=1
(that's the single user mode, isn't it?) there is no X running, so I can
login as root only in text-mode (console).
X (or graphical user interface such as KDE) is only available at runlevel 2 up
to runlevel
On Mon, Nov 19, 2012 at 09:57:03PM +0100, Herbert Schwarzer wrote:
Hello Chris,
perhaps I do not understand your proposal ... if I switch to runlevel=1
(that's the single user mode, isn't it?) there is no X running, so I can
login as root only in text-mode (console).
Correct. That
Following issue occurs (in both flavours Squeeze as well as Wheezy):
Running amd64 KDE-Environment.
It does not matter running nouveau-graphics-driver or nvidia-graphics-driver
(the Debian way ...)
If I switch from KDE-GUI (tty7) to virtual-consoles (tty1 .. tty6) and login
in text-mode
to set up virtual consoles in the
network install of Debian Squeeze 6.0???
snip
OK. You've been following a bit of a red-herring there, but that's only
to be expected. Virtual Terminals, themselves are controlled by the
kernel, but most relevant is the program that runs on the virtual
Does any one know of - info source to set up virtual consoles in the
network install of Debian Squeeze 6.0
that comes from here:
http://www.debian.org/CD/netinst/
it is installed and functional.
I am not using a GUI.
I am using the command line only.
if i do press simultaneously the ctrl
On Thu, Oct 04, 2012 at 07:08:49AM -0700, james gray wrote:
Does any one know of - info source to set up virtual consoles in the
network install of Debian Squeeze 6.0�
that comes from here:
[1]http://www.debian.org/CD/netinst/
it is installed and functional.
I am
Does any one know of - info source to set up virtual consoles in the
network install of Debian Squeeze 6.0
that comes from here:
http://www.debian.org/CD/netinst/
it is installed and functional.
I am not using a GUI.
I am using the command line only.
if i do press simultaneously the ctrl
Howdy,
On Thu, Oct 04, 2012 at 03:38:14PM +0100, Darac Marjal wrote:
On Thu, Oct 04, 2012 at 07:08:49AM -0700, james gray wrote:
Does any one know of - info source to set up virtual consoles in the
network install of Debian Squeeze 6.0???
snip
OK. You've been following a bit of a red
.
jfbterm
fbterm-ucimf
fbterm
bogl-bterm
apt-get show fbterm tells me fbterm is installed, but I don't see any
.fbtermrc files in the user directories when I login to the virtual
consoles.
user@deb:~$ dmesg
...
[ 38.475382] [drm] Initialized via 2.11.1 20070202 for :01:00.0 on minor 0
For reasons I don't care to debate, I have set my system's default
language to Japanese. When I go to work in the virtual console windows
(for instance, apt-get), I tend to get messages that should be in
Japanese, but the Japanese is replaced by the Unicode replacement
characters (?), which is no
On Sun, Dec 25, 2011 at 09:10:48PM +0900, Joel Rees wrote:
For reasons I don't care to debate, I have set my system's default
language to Japanese. When I go to work in the virtual console windows
(for instance, apt-get), I tend to get messages that should be in
Japanese, but the Japanese is
Joel Rees wrote:
For reasons I don't care to debate, I have set my system's default
language to Japanese.
snip
Did you install with Japanese as the default language, or did you
install as some other language and change the default?
Hugo
--
To UNSUBSCRIBE, email to
Hi,
On Sun, Dec 25, 2011 at 09:10:48PM +0900, Joel Rees wrote:
For reasons I don't care to debate, I have set my system's default
language to Japanese. When I go to work in the virtual console windows
(for instance, apt-get), I tend to get messages that should be in
Japanese, but the Japanese
(Forgot to reply to list.)
On 12/25/11, hvw59601 hvw59...@care2.com wrote:
Joel Rees wrote:
For reasons I don't care to debate, I have set my system's default
language to Japanese.
snip
Did you install with Japanese as the default language, or did you
install as some other language and
.fbtermrc files in the user directories when I login to the virtual
consoles.
Do you have a recommendation?
Try one of these with appropriate font packages. I think you can get
Japanese display.
The man page for fbterm doesn't seem to be telling me how to set it
up. I'm going to have to re-read
This happens on etch, which I try to keep up-to-date. sarge is, as
usual, pefectly stable, quite boring, and very useful.
I'm using gdm as my login manager. I have six virtual consoles
configured. Graphics is an AIT-Raden-all-in-wonder 8500 card. RAM is
1G. CPU is an athlon.
a few months
Hello Hendrik.
I'm using gdm as my login manager. I have six virtual consoles
configured. Graphics is an AIT-Raden-all-in-wonder 8500 card. RAM is
1G. CPU is an athlon.
a few months ago, I started experiencing this problem. Sometimes, when
changing virtual consoles with ctrl-alt-f
On Fri, Sep 01, 2006 at 12:36:02AM +0200, Mathias Brodala wrote:
Hello Hendrik.
I'm using gdm as my login manager. I have six virtual consoles
configured. Graphics is an AIT-Raden-all-in-wonder 8500 card. RAM is
1G. CPU is an athlon.
a few months ago, I started experiencing
On Sunday, 19.03.2006 at 23:11 -0500, Mitchell Laks wrote:
i reported this a few weeks ago on this list (dont you remember???)
(search for the header on my email
I don't remember and I don't find it by searching for your email address
either!
ctl-alt-F2 or F3 not switching to tty2 or tty3:
One quick test to try would be to start xev, put the mouse inside, then
press C-A-F1. If you get the F1 keycode on the console output, it would
at least indicate that X is ignoring the special meaning and that the
problem isn't happening at a different layer.
Jerry Quinn
--
To UNSUBSCRIBE,
Dave Ewart wrote:
On Sunday, 19.03.2006 at 22:37 +0100, Florian Kulzer wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using
On Sun, Mar 19, 2006 at 08:02:02PM +, Dave Ewart wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl-Alt-F1, Ctrl-Alt
On Monday, 20.03.2006 at 17:04 +0100, Florian Kulzer wrote:
I have played around a bit in the meantime and found that it is easily
possible to redefine the keyboard behavior in a way which breaks the VT
switching; all that is needed is messing with the keysymbols for the
CTRL and ALT key.
Dave Ewart wrote:
On Monday, 20.03.2006 at 17:04 +0100, Florian Kulzer wrote:
[...]
left CTRL: keycode 37 (keysym 0xffe3, Control_L)
left ALT: keycode 64 (keysym 0xffe9, Alt_L)
F1:keycode 67 (keysym 0xffbe, F1)
[...]
I get the same keysyms, certainly and the same keycodes as
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl-Alt-F1, Ctrl-Alt-F2 etc.
The 'getty's appear to be running OK, but I can't
Dave Ewart wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl-Alt-F1, Ctrl-Alt-F2 etc.
The 'getty's appear to be running
On Sunday, 19.03.2006 at 15:26 -0600, Kent West wrote:
Dave Ewart wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl
Dave Ewart wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl-Alt-F1, Ctrl-Alt-F2 etc.
The 'getty's appear to be running
On Sunday, 19.03.2006 at 22:37 +0100, Florian Kulzer wrote:
I recently upgraded this desktop from Sarge to Etch and pretty-much
everything has worked as well as before, or better, which is great.
However, I find that I can no longer switch between virtual consoles
using Ctrl-Alt-F1, Ctrl
hi
i reported this a few weeks ago on this list (dont you remember???)
(search for the header on my email
ctl-alt-F2 or F3 not switching to tty2 or tty3: running kde.
hasn't gone away yet.
Mitchell laks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
On Wed, 2004-06-23 at 16:16, Greg Folkert wrote:
On Wed, 2004-06-23 at 14:49, Carl D. Blake wrote:
So the problem
seems to be strictly with the display.
An interesting item is that after awhile (an hour or so) when I take
another look at the console, I'll press the shift key on the
On Thu, 2004-06-24 at 07:24, Greg Folkert wrote:
On Wed, 2004-06-23 at 16:16, Greg Folkert wrote:
On Wed, 2004-06-23 at 14:49, Carl D. Blake wrote:
So the problem
seems to be strictly with the display.
An interesting item is that after awhile (an hour or so) when I take
another
You could run savetextmode on a machine with as close a configuration
as possible, copy the files over and try it, but check the risks in
doing this, as it is a server that you don't want to reboot, let alone
crash.
On Thu, 24 Jun 2004 08:45:52 -0700, Carl D. Blake [EMAIL PROTECTED] wrote:
I did
I've lost the ability to switch virtual consoles on my Woody system.
One of the sysadmins logged in as the backup user through the kdm
desktop and when he logged out the monitor went dark. Now we can't
switch to a virtual console using Ctrl-Alt-Fn, nor can we switch to the
kdm desktop with Ctrl
On Wed, 2004-06-23 at 08:48, Carl D. Blake wrote:
I've lost the ability to switch virtual consoles on my Woody system.
One of the sysadmins logged in as the backup user through the kdm
desktop and when he logged out the monitor went dark. Now we can't
switch to a virtual console using Ctrl
. Blake wrote:
I've lost the ability to switch virtual consoles on my Woody system.
One of the sysadmins logged in as the backup user through the kdm
desktop and when he logged out the monitor went dark. Now we can't
switch to a virtual console using Ctrl-Alt-Fn, nor can we switch to the
kdm
On Wed, 2004-06-23 at 10:46, Ricky Clarkson wrote:
Perhaps you could take down the X server using /etc/init.d/xdm stop
(or gdm or kdm if you use those). That might give the monitor time to
adjust itself, which restarting X wouldn't do.
I tried that, didn't help.
If that gives you a shell,
On Wed, 2004-06-23 at 14:49, Carl D. Blake wrote:
So the problem
seems to be strictly with the display.
An interesting item is that after awhile (an hour or so) when I take
another look at the console, I'll press the shift key on the keyboard
and the kdm display will appear. I can then log
On Wed, Jun 23, 2004 at 10:26:27AM -0700, Carl D. Blake wrote:
On Wed, 2004-06-23 at 08:48, Carl D. Blake wrote:
I've lost the ability to switch virtual consoles on my Woody system.
One of the sysadmins logged in as the backup user through the kdm
desktop and when he logged out the monitor
On Wed, 2004-06-23 at 16:16, Greg Folkert wrote:
On Wed, 2004-06-23 at 14:49, Carl D. Blake wrote:
So the problem
seems to be strictly with the display.
An interesting item is that after awhile (an hour or so) when I take
another look at the console, I'll press the shift key on the
Ken Bloom [EMAIL PROTECTED] writes:
I've observed on my machine over the last several months that it
takes an inordinately long time after I log off of one of my
machine's virtual consoles before the getty restarts, prints
/etc/issue and is ready to accept logins again. Occasionally, I get
I've observed on my machine over the last several months that it takes
an inordinately long time after I log off of one of my machine's
virtual consoles before the getty restarts, prints /etc/issue and is
ready to accept logins again. Occasionally, I get a situation where
init reports the getty
Ken Bloom wrote:
I've observed on my machine over the last several months that it takes
an inordinately long time after I log off of one of my machine's
virtual consoles before the getty restarts, prints /etc/issue and is
ready to accept logins again. Occasionally, I get a situation where
init
On Fri, 05 Mar 2004 16:11:06 +0100, Kent West wrote:
Ken Bloom wrote:
I've observed on my machine over the last several months that it takes an
inordinately long time after I log off of one of my machine's virtual
consoles before the getty restarts, prints /etc/issue and is ready to
accept
On Fri, 05 Mar 2004 16:11:06 +0100, Kent West wrote:
Ken Bloom wrote:
I've observed on my machine over the last several months that it takes an
inordinately long time after I log off of one of my machine's virtual
consoles before the getty restarts, prints /etc/issue and is ready to
accept
On Thu, Mar 04, 2004 at 11:40:48PM -0800, Ken Bloom wrote:
| I've observed on my machine over the last several months that it takes
| an inordinately long time after I log off of one of my machine's
| virtual consoles before the getty restarts, prints /etc/issue and is
| ready to accept logins
On Fri, Mar 05, 2004 at 10:31:30PM -0500, Derrick 'dman' Hudson wrote:
On Thu, Mar 04, 2004 at 11:40:48PM -0800, Ken Bloom wrote:
| I've observed on my machine over the last several months that it takes
| an inordinately long time after I log off of one of my machine's
| virtual consoles
on Tue, Nov 04, 2003 at 12:58:34PM +0100, Miernik ([EMAIL PROTECTED]) wrote:
Currently Unicode mode come's up as default on the first console, but
for consoles 2 to 6 I need to run unicode_start on every console. What
is the proper Debian way to have unicode mode on all vc's by default?
Currently Unicode mode come's up as default on the first console, but
for consoles 2 to 6 I need to run unicode_start on every console. What
is the proper Debian way to have unicode mode on all vc's by default?
Second thing: I have created a polish unicode keymak myslef in
On Tue, 2002-04-16 at 13:07, Karsten M. Self wrote:
on Mon, Apr 15, 2002, Roach, Mark R. ([EMAIL PROTECTED]) wrote:
This is a very strange variation on a problem I experienced
occasionally in mandrake. My console windows are now filled with
vertical lines. Mostly purples, but all sorts of
on Mon, Apr 15, 2002, Roach, Mark R. ([EMAIL PROTECTED]) wrote:
This is a very strange variation on a problem I experienced
occasionally in mandrake. My console windows are now filled with
vertical lines. Mostly purples, but all sorts of other colors too.
nothing I type shows up on the
This is a very strange variation on a problem I experienced occasionally
in mandrake. My console windows are now filled with vertical lines.
Mostly purples, but all sorts of other colors too. nothing I type shows
up on the screen. It looks like some kind of test pattern.
I used to, in mandrake,
again. At first I thought the login problems were due
to the recent pam issue, but I've done several dist-upgrades (tracking
sid) since then, and a login after reboot works fine, as do virtual
consoles before and, for a while at least, after starting X.
One other thing, which may or may
[EMAIL PROTECTED] wrote:
Type 'linux single' at the LILO prompt (press Shift to get the
prompt). You'll boot into single user mode.
This is what I needed.
To remove the X/Gnome display manager from your startup scripts, try
'/etc/init.d/xdm' remove (or '/etc/init.d/gdm remove' if you're
I selected xdm on install but loaded the gnome packages on install. I
want to run Gnome so how do I get gdm and remove xdm?
apt-get install gdm?
Precisely. It should remove xdm and substitude gdm seamlessly...
Cheers
Tiarnan
[EMAIL PROTECTED] wrote:
I selected xdm on install but loaded the gnome packages on install. I
want to run Gnome so how do I get gdm and remove xdm?
apt-get install gdm?
Precisely. It should remove xdm and substitude gdm seamlessly...
Wow, I like this Debian stuff.
Thanks for the
Hi,
I don't know if this is because of a laptop keyboard or what but since
my X setup doesn't work I can't do anything after boot.
I try the ctrl-alt-bs to kill the x server and that doesn't work. I also
try ctrl-alt-f2 etc to get a virtual console so I can kill X and that
doesn't work.
What is
On Tue, Mar 06, 2001 at 03:26:04PM -0700, Eric Richardson wrote:
Hi,
I don't know if this is because of a laptop keyboard or what but since
my X setup doesn't work I can't do anything after boot.
I try the ctrl-alt-bs to kill the x server and that doesn't work. I also
try ctrl-alt-f2 etc to
William T Wilson [EMAIL PROTECTED] writes:
Yup - allocate 13-24 and you can use right-alt + F1-12
Rock on. I will never run out of logins again! :}
apt-get install screen ;)
moritz
--
/* Moritz Schulte [EMAIL PROTECTED]
* http://hp9001.fh-bielefeld.de/~moritz/
* PGP-Key
on Sat, Nov 11, 2000 at 11:28:42PM -0500, William T Wilson ([EMAIL PROTECTED])
wrote:
So suppose I wanted to have more than 12 virtual consoles on my system,
but I only have 12 F-keys to select them with.
I know the kernel supports up to 255... is there any way to use more than
12?
Also
So suppose I wanted to have more than 12 virtual consoles on my system,
but I only have 12 F-keys to select them with.
I know the kernel supports up to 255... is there any way to use more than
12?
Yup - allocate 13-24 and you can use right-alt + F1-12
from 25 upwards you need to use alt + left/right arrow to get to them
At 11:28 PM 11/11/00 -0500, you wrote:
So suppose I wanted to have more than 12 virtual consoles on my system,
but I only have 12 F-keys to select them with.
I know
On Sun, 12 Nov 2000, C. Falconer wrote:
Yup - allocate 13-24 and you can use right-alt + F1-12
Rock on. I will never run out of logins again! :}
1 - 100 of 113 matches
Mail list logo
