Your message dated Tue, 24 Apr 2007 08:55:40 +0200 with message-id <462DA9EC.7080205@ens-lyon.org> and subject line Bug#420548: crash on running ntpdate has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: crash on running ntpdate
- From: Harald Dunkel <harald@CoWare.com>
- Date: Mon, 23 Apr 2007 08:53:07 +0200
- Message-id: <[🔎] 462C57D3.9070904@coware.com>
Package: xserver-xorg Version: 7.1.0-18 Hi folks, If I run "ntpdate pool.ntp.org" to fix the clock in my PC (it is running too fast), then the Xserver crashes. The log file says: Backtrace: 0: X(xf86SigHandler+0x6d) [0x4802ed] 1: /lib/libc.so.6 [0x2b27479e64c0] 2: X(WaitForSomething+0xa12) [0x5447e2] 3: X(Dispatch+0x8b) [0x44801b] 4: X(main+0x44d) [0x430f6d] 5: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b27479d3314] 6: X(FontFileCompleteXLFD+0x9a) [0x43026a] Fatal server error: Caught signal 11. Server aborting This is reproducible. Platform is amd64 (lenny), i.e. libc6 2.5-3. Linux sion 2.6.20.7 #1 SMP PREEMPT Sat Apr 14 08:35:36 CEST 2007 x86_64 GNU/Linux Regards Harri
--- End Message ---
--- Begin Message ---
- To: 420548-done@bugs.debian.org
- Subject: Re: Bug#420548: crash on running ntpdate
- From: Brice Goglin <Brice.Goglin@ens-lyon.org>
- Date: Tue, 24 Apr 2007 08:55:40 +0200
- Message-id: <462DA9EC.7080205@ens-lyon.org>
- In-reply-to: <[🔎] 462D8AC9.1090705@coware.com>
- References: <[🔎] 462C57D3.9070904@coware.com> <[🔎] 462C5D79.7050902@ens-lyon.org> <[🔎] 462C6793.5040800@coware.com> <[🔎] 462C6A46.7040900@ens-lyon.org> <[🔎] 462D8AC9.1090705@coware.com>
Version: 2:1.3.0.0-1 It looks like this bug is fixed in xserver-xorg-core 1.3.0.0. Brice
--- End Message ---