Hi Steven, yes the release is on its way, apart from other releases.
Kind regards, Anselm 2008/7/29 Steven Blatchford <[EMAIL PROTECTED]>: > Hi Anselm, > I was using slock v0.8[1] and received the error below. The code in hg > tip fixed the problem. Anselm can you release v0.9 with these fixes? > > Thanks, > -steve > > > X Error of failed request: BadMatch (invalid parameter attributes) > Major opcode of failed request: 136 (DPMS) > Minor opcode of failed request: 6 (DPMSForceLevel) > Serial number of failed request: 27 > Current serial number in output stream: 28 > > [1] http://code.suckless.org/dl/tools/slock-0.8.tar.gz > > > On 00:46 Thu 10 Apr, Anselm R. Garbe wrote: >>On Wed, Apr 09, 2008 at 11:12:23AM +0200, Anselm R. Garbe wrote: >>> On Tue, Apr 08, 2008 at 02:37:10PM +0200, Peter Hartlich wrote: >>> > >> Also, with the new DPMS code from changeset 31, slock crashes here >>> > >> (X.org server 1.4.0.90, DPMS disabled in xorg.conf): >>> > >> >>> > >> | X Error of failed request: BadMatch (invalid parameter attributes) >>> > >> | Major opcode of failed request: 136 (DPMS) >>> > >> | Minor opcode of failed request: 6 (DPMSForceLevel) >>> > >> | Serial number of failed request: 27 >>> > >> | Current serial number in output stream: 28 >>> > >>> > > Right, should be fixed in hg tip now. Please confirm this due to >>> > > a recheck. >>> > >>> > Still crashes at DPMSForceLevel. It seems that DPMSCapable returns True >>> > even with DPMS disabled... >>> >>> Well, then I need to add an error handler. >> >>I pushed a changeset into hg tip of slock which attempts to fix >>the DPMS issue without using a separate error handler, hence >>please recheck, If the crash still occurs, there is no other >>choice than wether not supporting DPMS or implementing an error >>handler which ignores BadMatch errors due to DPMSForceLevel >>calls. >> >>Kind regards, >>-- >> Anselm R. Garbe >< http://www.suckless.org/ >< GPG key: 0D73F361
