Bug#327196: [RP] Re: Bug#327196: Debian ratpoison problem with X.org

2005-10-15 Thread Martin Samuelsson
Shawn Betts @ 2005-10-14 (Friday), 18:02 (+)
 Magnus Henoch [EMAIL PROTECTED] writes:
 
  Martin Samuelsson [EMAIL PROTECTED] writes:
 
  I would assume that it's fixed in cvs, but I'm not completely sure since
  I'm also applying a few patches that might affect things. Is the cause
  known or should I investigate further to create a backport or the bug
  fix?
 
  See the thread at
  http://thread.gmane.org/gmane.comp.window-managers.ratpoison.devel/1519
  .  I think this is the same bug; it was fixed in CVS in February.
 
 Hi Magnus,
 
 Can you test this on a vanilla cvs build? That should answer your
 question. If it's still a problem, let me know.

It is definitly the same problem as in the thread above. It is gone in
cvs, but still present in the debian version.
--
/Martin


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



Bug#327196: Debian ratpoison problem with X.org

2005-09-08 Thread Martin Samuelsson
Package: ratpoison
Version: 1.3.0-7

When running :definekey top XF86Go exec mpc pause in the Debian
packaged version of ratpoison no immediate error is reported. But future
keypresses stops going to their clients and ratpoison says the
following:

ratpoison:events.c:404: error: Impossible: No matching key

If upgrading to my locally built package from cvs and with patches the
problem goes away (version 1.4.0.CVS.jn.20050823-0cos), becuase the
definekey starts giving an error stating the keysum does not exist.

I would assume that it's fixed in cvs, but I'm not completely sure since
I'm also applying a few patches that might affect things. Is the cause
known or should I investigate further to create a backport or the bug
fix?

Or is it maybe time to release a new upstream soon enough?

(I also noticed that replacing XF86Go with DOESNOTEXIST does not trigger
the problem.)
--
/Martin


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