Florian Kulzer wrote:
> I think another advantage of using [xkg]dm is avoiding the
> CTRL-ALT-F1, CTRL-Z attack against the X screen lock
> (if you leave your computer unattended and somebody else could
> walk along and use the keyboard).
Kent West wrote:
> Or just append an ampersand to your star
Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> > I think another advantage of using [xkg]dm is avoiding the
> > CTRL-ALT-F1, CTRL-Z attack against the X screen lock (if you leave
> > your computer unattended and somebody else could walk along and use
> > the keyboard).
>
> So switch to vt2, lo
Jose Luis Rivas Contreras wrote:
> Dave Walker escribió:
> >> That raises the question, though, about what happined to terminal 1.
> >> Why won't it respond, and why does it appear to be comatose???
>
> >>
> If you don't want this to happen then you should use gdm or xdm or kdm,
> then you just sta
On Sat, Mar 31, 2007 at 19:59:35 -0400, Douglas Allan Tutty wrote:
> On Sun, Apr 01, 2007 at 12:40:54AM +0200, Florian Kulzer wrote:
> > On Sat, Mar 31, 2007 at 17:29:13 -0400, Jose Luis Rivas Contreras wrote:
> > > >
> > > > That raises the question, though, about what happined to terminal 1.
> >
On Sun, Apr 01, 2007 at 12:40:54AM +0200, Florian Kulzer wrote:
> On Sat, Mar 31, 2007 at 17:29:13 -0400, Jose Luis Rivas Contreras wrote:
> > >
> > > That raises the question, though, about what happined to terminal 1.
> > > Why won't it respond, and why does it appear to be comatose???
> > >
>
On 3/31/07, Florian Kulzer <[EMAIL PROTECTED]> wrote:
On Sat, Mar 31, 2007 at 17:29:13 -0400, Jose Luis Rivas Contreras wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dave Walker escribió:
> >
> > That raises the question, though, about what happined to terminal 1.
> > Why won't it
On Sat, Mar 31, 2007 at 17:29:13 -0400, Jose Luis Rivas Contreras wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dave Walker escribió:
> >
> > That raises the question, though, about what happined to terminal 1.
> > Why won't it respond, and why does it appear to be comatose???
> >
"Dave Walker" <[EMAIL PROTECTED]> wrote:
> On 3/31/07, Andrei Popescu <[EMAIL PROTECTED]> wrote:
> > "Dave Walker" <[EMAIL PROTECTED]> wrote:
> >
> > > Running Gnome in terminal 1 as normally privileged user.
> > > Initialized by startx.
> > >
> > > Switch to terminal 2 (CTRL ALT F2) and log
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Walker escribió:
>
> That raises the question, though, about what happined to terminal 1.
> Why won't it respond, and why does it appear to be comatose???
>
> Dave W.
>
>
If you don't want this to happen then you should use gdm or xdm or kdm,
On Sat, Mar 31, 2007 at 03:54:54PM -0500, Dave Walker wrote:
> On 3/31/07, Andrei Popescu <[EMAIL PROTECTED]> wrote:
> >"Dave Walker" <[EMAIL PROTECTED]> wrote:
>--
> Thanks, Andrei what you explained was exactly what I found. X
> was not running in terminal 1 at all as I expected, but was
On 3/31/07, Andrei Popescu <[EMAIL PROTECTED]> wrote:
"Dave Walker" <[EMAIL PROTECTED]> wrote:
> Running Gnome in terminal 1 as normally privileged user. Initialized
> by startx.
>
> Switch to terminal 2 (CTRL ALT F2) and log in as same user as in
> terminal 1. No commands issued in termina
"Dave Walker" <[EMAIL PROTECTED]> wrote:
> Running Gnome in terminal 1 as normally privileged user. Initialized
> by startx.
>
> Switch to terminal 2 (CTRL ALT F2) and log in as same user as in
> terminal 1. No commands issued in terminal 2.
>
> Switch back terminal 1 (CTRL ALT F1), and X h
Running Sarge 3.1r5 (all up to date), kernel 2.4.27-2-386 and Gnome desktop.
The following situation is repeatable, behaving in the same manner each time:
Running Gnome
13 matches
Mail list logo
