Red Hat Bugzilla – Bug 63721
xemacs started in X survives restarting X
Last modified: 2007-04-18 12:42:06 EDT
Description of Problem:
If I startx, then start xemacs, and then quit X (either ctrl-alt-backspace) or
via the gnome logout menu item, when I return to the console,
xemacs is still running. If I start X again, xemacs will
start to take 99% of cpu time.
Version-Release number of selected component (if applicable):
So far everytime I've tried.
Steps to Reproduce:
1. start x
2. start xemacs
3. exit x
xemacs continues to run
xemacs would be killed.
Can't reproduce at all, tried with gnome, kde in gdm and with startx, exiting
with log out and with ctrl-alt-backspace
Dunno, it does it for me with fvwm/gnome and startx on
my laptop, fvwm/gnome/startx on my home machine, and fvwm/gnome/gdm
on my test box. Also with sawfish/gnome/gdm on my testbox.
tristan.devel.redhat.com to see it...
Does it happen on a fresh install of the final when running in the default gnome
or kde environments?
dunno, I dont use any of those enviroments. The test box
was a clean install from a tree about a week old (xemacs-21.4.6-7)
but pulled up2date with whatever the latest in the RHN servers are.
The laptop and home machine are both upgrades (one from 7.2+, the
other from 7.1)
test machine doesnt seem to do it with a pristine new user setup
It seems to fail in every other enviroment I have access to however...
Still never seen it happen. Reopen if you find a way to reproduce it on a
current system with standard components.