linux-kernel - Re: [2.6.25-rc6] possible regression: X server dying

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 09 Apr 2008 13:57:41 +0200
From:	Tilman Schmidt <tilman@...p.cc>
To:	Ray Lee <ray-lk@...rabbit.org>
CC:	Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
	pavel@....cz
Subject: Re: [2.6.25-rc6] possible regression: X server dying

Ray Lee schrieb:
> If you think it's one of the screensavers but don't know which one,
> then open up a bash shell and do a
> 
> for i in /usr/lib/xscreensaver/*; do echo $i; $i ; done
> 
> hitting control-c to break out of the screensaver when you think it's
> been cleared of any wrongdoing.

Good idea. I did one pass through the screensavers that way, letting
each one run a couple of seconds until it seemed to become repetitive.
None of this crashed my X server, which at least seems to tell me that
it is not one particular screensaver always triggering the problem.

But: twice during that test I was called away, left the thing running,
and came back to find the X server had exited again, apparently after
the "real" screensaver had kicked in. Twice in a day, that's much more
than ever before. So you may have found me a way to trigger the crash
with greater probability.

Thanks,
T.

-- 
Tilman Schmidt                    E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)

Download attachment "signature.asc" of type "application/pgp-signature" (251 bytes)