Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginLinux NewsClick the above for your daily dose of Linux news. Food for ThoughtWindows Error: 002 - No error yet ... Spam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
Crashed X - Hard re-bootRunning 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 in terminal 1 as normally privileged user. Initialized Switch to terminal 2 (CTRL ALT F2) and log in as same user as in Switch back terminal 1 (CTRL ALT F1), and X has crashed. Gnome is X will not respond to CTRL ALT BACKSPACE (which normally closes the The only workable recovery I have found is to switch to terminal 2, su A hard re-boot - power on - (ouch!) brings back the system with How do I recover "gracefully" from an X crash like this? Anybody have Following is the last few lines from var/log/XFree86.0.log GetModeLine - scrn: 0 clock: 0 Thanks all -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
Crashed X - Hard re-boot
"Dave Walker" 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 has crashed. Gnome is
X (usually) runs on terminal 7. Try (Ctrl+)Alt+F7. And yes, it has
happened to me as well ;)
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
Crashed X - Hard re-boot
On 3/31/07, Andrei Popescu wrote:
> "Dave Walker" 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 has crashed. Gnome is
>
> X (usually) runs on terminal 7. Try (Ctrl+)Alt+F7. And yes, it has
> happened to me as well ;)
>
> Regards,
> Andrei
> --
Thanks, Andrei........ what you explained was exactly what I found. X
was not running in terminal 1 at all as I expected, but was "hiding"
(from me at least) in terminal 7.
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.
--
Crashed X - Hard re-boot
On Sat, Mar 31, 2007 at 03:54:54PM -0500, Dave Walker wrote:
> On 3/31/07, Andrei Popescu wrote:
> >"Dave Walker" 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 "hiding"
> (from me at least) in terminal 7.
>
> 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 VC1 you ran startx. X spits its stderr to VC1 and continues to do so
as long as it is running. It paints a display on the next available VC
(standard debian has this as VC7). The Ctrl-Alt-Backspace works when
you are viewing the X system in VC7. In VC1, X is spitting its output
but isn't reading input on that VC.
I _have_ had a case where X wouldn't respond to _any_ magic keystrokes.
This is another reason why I have a getty running on a serial port. I
can always log in from another computer via a null-modem cable.
Doug.
--
Crashed X - Hard re-boot
-----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,
then you just start gdm and terminal 1 is free ;-)
Jose Luis,
- --
ghostbar @ linux/debian 'sid' x86 - #382503
WeBlog: http://ghostbar.ath.cx/ - http://talug.org.ve
http://debian.org.ve - irc.debian.org #debian-ve
San Cristóbal, Venezuela.
Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGDtKpOKCtW8rKsRgRAjexAJ0UaFnHVFwf7GXDFtMx5ayJAaBA2wCfXiDZ
8hWFaHKmBToueyoXJuEilB4=
=a5gm
-----END PGP SIGNATURE-----
--
Crashed X - Hard re-boot
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 start gdm and terminal 1 is free ;-)
Or just append an ampersand to your startx command, as in "startx &".
You'll still get messages on VT1, but at least you'll have a normal
prompt available.
--
Kent
--
Crashed X - Hard re-boot
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 startx command, as in "startx &".
> You'll still get messages on VT1, but at least you'll have a normal
> prompt available.
Or even do a "startx & exit" in order to avoid the attack mentioned by
Florian Kulzer when locking the display.
-- Regards, Jörg-Volker.
--
Crashed X - Hard re-boot
"Dave Walker" wrote:
> On 3/31/07, Andrei Popescu wrote:
> > "Dave Walker" 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 has crashed. Gnome is
> >
> > X (usually) runs on terminal 7. Try (Ctrl+)Alt+F7. And yes, it has
> > happened to me as well ;)
> >
> > Regards,
> > Andrei
> > --
> Thanks, Andrei........ what you explained was exactly what I found. X
> was not running in terminal 1 at all as I expected, but was "hiding"
> (from me at least) in terminal 7.
>
> That raises the question, though, about what happined to terminal 1.
> Why won't it respond, and why does it appear to be comatose???
It's about the same as with starting programs that don't detach from
the terminal they were started from (the majority). Press Ctrl-c and you
will get your terminal back, but also kill X/the program.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--
Crashed X - Hard re-boot
On 3/31/07, Florian Kulzer 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 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,
> > then you just start gdm and terminal 1 is free ;-)
>
> 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).
>
> --
> Regards,
> Florian
>
Thanks once again, all
I think I can see why the program is called X - it begins in VC1 and
sneaks over VC7 - sort of like a plot in X-Files or X as in
X-perimental!
I'll give gdm a try - I didn't know of its existence.
Dave W.
Crashed X - Hard re-boot
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???
> > >
> > If you don't want this to happen then you should use gdm or xdm or kdm,
> > then you just start gdm and terminal 1 is free ;-)
>
> 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, log in, and run vlock -a
After all, what happens if X dies when you're using *dm?
Doug.
--
Crashed X - Hard re-boot
Douglas Allan Tutty 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, log in, and run vlock -a
IIRC you can disable the Ctrl+Alt+Fn in xorg.conf
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
--