Bug#418718: X suddenly died after installing ntp

2007-04-11 Thread Robert Millan 
Package: xserver-xorg-video-ati
Version: 1:6.6.3-2
Severity: grave
Justification: may cause data loss

Installing ntp on my system, and running it for first time made X die.

I suppose there's code somewhere written with the assumption that time always
goes forwards :-).  No idea how to find it though.  The Xorg logs don't
reveal anything.

I suggest you Conflict with ntp as a workaround.  ntpdate is probably ok,
since X is most likely not running when the network is started.

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)

Versions of packages xserver-xorg-video-ati depends on:
ii  libc6   2.3.6.ds1-13 GNU C Library: Shared libraries
ii  xserver-xorg-core   2:1.1.1-21   X.Org X server -- core server

xserver-xorg-video-ati recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#418718: X suddenly died after installing ntp

2007-04-11 Thread Julien Cristau 
reassign 418718 xserver-xorg-core
severity 418718 important
tags 418718 upstream fixed-upstream
retitle 418718 X crashes when time goes backwards
thanks

On Wed, Apr 11, 2007 at 15:32:04 +0200, Robert Millan wrote:

 I suggest you Conflict with ntp as a workaround.  ntpdate is probably ok,
 since X is most likely not running when the network is started.
 
Rright.

Cheers,
Julien


signature.asc
Description: Digital signature

Bug#418718: X suddenly died after installing ntp

2007-04-11 Thread Brice Goglin 

reassign 415627 xserver-xorg-core
merge 415627 418718
thank you


We have seen several reports like this one. At least #415627 seems similar,
merging then. Also, some people confirmed the same problem when replying to
#412275. But #412275 is actually a freeze of the machine, instead of just
crash or the X server. So it might be a different problem.
Anyway, you might want to read these bugs too.

Also there's been a related fix committed upstream recently (see
https://bugs.freedesktop.org/show_bug.cgi?id=10296) but it might just be a
fix for a recent regression, while all the bugs above seem to have been here
for a while now.

Brice