Red Hat Bugzilla – Bug 134418
ntpdate killed x server
Last modified: 2007-11-30 17:10:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040929
Description of problem:
When running ntpdate server as root from an xterm (GNOME environment)
X spontaneously restarted.
I was running evolution, rhythmbox, firefox and xterms at the time
(plus various applets)
My clock was out by about 15 minutes at the time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Let clock get out of sync by 15 mnutes
2. Be logged in to gnome session
3. ntpdate servername
Actual Results: Spontaneous restart of xserver.
Expected Results: Time change, perhaps a few minor problems with apps.
Can provide as necessary - let me know what you need.
Just remembered - I saw the response to ntpdate pop up on the terminal
before the crash
2 Oct 12:33:06 ntpdate: adjust time server 10.61.0.113 offset
(Response when trying to trigger this with a small offset)
Let my clock drift by 15 minutes again, and similar results. This time
X recovered, but took several minutes to do so.
During this period, rhythbox stopped playing completely, I was alerted
that X had recovered (no screensaver, using xlock) by my music restarting.
Using rawhide updated 2 hour ago.
Hardware: Dell Inspiron 5000e
Attach your X server log, config file, /var/log/messages, and the output
of lsmod to the report as individual uncompressed file attachments using
the link below.
Setting status to "NEEDINFO", awaiting file attachments requested above.
The problem seems to have stopped between when I reported this and now.
If the problem recurs i'll create a new bug. Close for now.
Ok, I'll set this to "RAWHIDE" for now. If the problem recurs, please
report it to X.Org via http://bugs.freedesktop.org in the "xorg" component,
and supply full details for reproduceability. This will ensure the problem
is visible to maximum number of X developers which will accelerate the
likelyhood of an early resolution.