Bug#438196: Sometimes...

2007-09-28 Thread Frédéric Brière
On Thu, Aug 30, 2007 at 01:03:15PM +0200, Yannick P. wrote:
 I have *sometimes* this problem.

The words every developer dreads.  :)


I thought I'd chime in, because this happened to me today.  I tried to
restart xdm, and it claimed that /var/run/xdm.pid didn't exist.  (Maybe
it was true, maybe it wasn't, I admit I didn't bother to check.)

Now, the whole reason I was trying to restart xdm was because I couldn't
log in, due to libpam failing to load.  I'm guessing that libpam0g
0.99.7.1-3 itself failed to restart xdm during the last upgrade, hence
the problem.

In the end, I just killed xdm and started it again without further ado,
as I wasn't thrilled with the idea of trying to find out why a daemon
failed to create a pidfile when it was launched over a month ago.  (God
knows this is far from the first time I've seen flaky start/stop
scripts.)

Sorry, if I'd known I wasn't the only one, I would've investigated a
little further...


-- 
* joeyh installs debian using only his big toe, for a change of pace
-- in #debian-boot



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



Bug#438196: Sometimes...

2007-08-30 Thread Yannick P.
I have *sometimes* this problem.
I do '/etc/init.d/xdm stop' and the system thinks XDM is not running so
it can't stop it (but it's there in tty7 and it works).

And sometimes, '/etc/init.d/xdm stop' works but when I go in tty7, I
have something like ÉÇÔZÈKËÄÅ and I cannot go to the others tty.
But I can have logging informations about dropped packets (like in bug
#218631) and sys-request keys work and show infos.

I don't know if the two problems are linked.
My two cents.

xdm 1:1.1.5-2 and 1:1.1.6-2