From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ken Raeburn Newsgroups: gmane.emacs.bugs Subject: bug#22932: 25.0.92; X protocol error: BadRequest (invalid request code or no such operation) on protocol request 149 Date: Tue, 8 Mar 2016 15:43:38 -0500 Message-ID: References: <83d1r6uulk.fsf@gnu.org> <8337s1rl3a.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11401b3cd2d89c052d8fa2ba X-Trace: ger.gmane.org 1457469867 16568 80.91.229.3 (8 Mar 2016 20:44:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 8 Mar 2016 20:44:27 +0000 (UTC) Cc: 22932@debbugs.gnu.org To: john.eismeier@emc.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 08 21:44:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1adOUF-0001x4-AC for geb-bug-gnu-emacs@m.gmane.org; Tue, 08 Mar 2016 21:44:11 +0100 Original-Received: from localhost ([::1]:37225 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adOUE-0003SD-MF for geb-bug-gnu-emacs@m.gmane.org; Tue, 08 Mar 2016 15:44:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33791) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adOUA-0003S4-Kz for bug-gnu-emacs@gnu.org; Tue, 08 Mar 2016 15:44:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1adOU6-0005mL-9E for bug-gnu-emacs@gnu.org; Tue, 08 Mar 2016 15:44:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:42966) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1adOU6-0005mF-69 for bug-gnu-emacs@gnu.org; Tue, 08 Mar 2016 15:44:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1adOU6-000295-1c for bug-gnu-emacs@gnu.org; Tue, 08 Mar 2016 15:44:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Ken Raeburn Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 08 Mar 2016 20:44:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22932 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 22932-submit@debbugs.gnu.org id=B22932.14574698268216 (code B ref 22932); Tue, 08 Mar 2016 20:44:02 +0000 Original-Received: (at 22932) by debbugs.gnu.org; 8 Mar 2016 20:43:46 +0000 Original-Received: from localhost ([127.0.0.1]:40093 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1adOTq-00028S-2o for submit@debbugs.gnu.org; Tue, 08 Mar 2016 15:43:46 -0500 Original-Received: from mail-lb0-f180.google.com ([209.85.217.180]:34007) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1adOTo-00028G-QW for 22932@debbugs.gnu.org; Tue, 08 Mar 2016 15:43:45 -0500 Original-Received: by mail-lb0-f180.google.com with SMTP id xr8so34435138lbb.1 for <22932@debbugs.gnu.org>; Tue, 08 Mar 2016 12:43:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=permabit.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=Q3JWtZUrzi6TJw4+TXgSgtML13vKvXFMpQb4AEntZmE=; b=TxedM9pwSjAt69ebTckptF9P8MQAyAP7mxezu5AY2WkGjD9CFGYmdCFLnfgD1h3mDP FHog9tY4AhWyc15Sro0Ptbiotkf3TK80PwPLtJ6tWvONFuIOKPKQPjzpuCQ+HvW7Y0Gy 2jK8Jpi1mXxVH9g+Wj3YCNZqLk5Y2crLC6mDg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=Q3JWtZUrzi6TJw4+TXgSgtML13vKvXFMpQb4AEntZmE=; b=E3Q+jTFKuo/GBmliagWac+xzyqk2hGF1yqXOKqL3LJnwqUL+xIcTmUFncDSTrcCq1L QvriztaIHj3oII4nIB3N15stsaZ+3/FSLLXxy6YI1C+EA3rfnrHXt8wS5Oi0+ZGef73e rR/LeE6ZX/JWBXohDccqXq1uwAxn8hLHCcBVF1l5TUvWG3n12Rjb5b2ij2gtZpeQpZN1 ctiJA/saX5kYRli+vv2rMO2TacFs4GQe0SuqYNzsHnXfYM/MTPF9p8macoYRnePDplnM QViMb1c3h62hIhoW+A7xIUCGwl0Rq4XMtTX2xNBJxRmztSwgEkfP/FaZQ3IIFQ45tjqM pY8w== X-Gm-Message-State: AD7BkJK1rG3qG46oOTimwrAanUvgNR2TTjF/JedLTHHI+7732fjemLZu6sbvzlfIp43oxxFYJIfOnnD6Zt68/piv X-Received: by 10.25.158.72 with SMTP id h69mr10951916lfe.8.1457469818839; Tue, 08 Mar 2016 12:43:38 -0800 (PST) Original-Received: by 10.112.63.72 with HTTP; Tue, 8 Mar 2016 12:43:38 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:114605 Archived-At: --001a11401b3cd2d89c052d8fa2ba Content-Type: text/plain; charset=UTF-8 On Tue, Mar 8, 2016 at 3:10 PM, John Eismeier wrote: > > Ken, > > I am running Ubuntu 14.04 LTS. > > > xrandr -v > xrandr program version 1.4.1 > Server reports RandR version 1.2 > How odd! I'm running Ubuntu 12.04 LTS at work and its X server reports support for 1.3. > > What should I do next ? I still need to run this revision of the OS > with our current product development strategy. > Well, I think I see where the issue is. The code as written -- at least in that function -- assumes that if your libraries have the newer function, then your server supports it. That doesn't seem to be the case here. In reading up on this today, I've already run across a few web pages showing which RandR requests were added in 1.3 and how to test the protocol version supported by the server. If you want to dig into X11 programming you're welcome to help out :-), otherwise I'll try to make some time this evening to look into coding the run-time protocol version checks. In the meantime, if you want something that just runs without crashing this way, you could disable the use of the XRANDR extension. The configure script isn't set up to make that easy from the command line, but you could edit the config files generated. After running configure, look in src/config.h for the line: #define HAVE_XRANDR 1 ... and comment it out. Then finish building Emacs normally. From a quick test on my system that seems to work okay, though I don't know off the top of my head what functionality might be diminished by losing the xrandr support. Ken --001a11401b3cd2d89c052d8fa2ba Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Mar 8, 2016 at 3:10 PM, John Eismeier <john.eismeier@emc.com&g= t; wrote:

Ken,

I am running Ubuntu 14.04 LTS.


xrandr=C2=A0 -v
xrandr program version=C2=A0 =C2=A0 =C2=A0 =C2=A01.4.1
Server reports RandR version 1.2

How od= d! I'm running Ubuntu 12.04 LTS at work and its X server reports suppor= t for 1.3.
=C2=A0

What should I do next ?=C2=A0 I still need to run this revision of the OS with our current product development strategy.

Well, I think I see where the issue is. The code as written -- at l= east in that function -- assumes that if your libraries have the newer func= tion, then your server supports it. That doesn't seem to be the case he= re.

In reading up on this today, I've already = run across a few web pages showing which RandR requests were added in 1.3 a= nd how to test the protocol version supported by the server. If you want to= dig into X11 programming you're welcome to help out :-), otherwise I&#= 39;ll try to make some time this evening to look into coding the run-time p= rotocol version checks.

In the meantime, if you wa= nt something that just runs without crashing this way, you could disable th= e use of the XRANDR extension. The configure script isn't set up to mak= e that easy from the command line, but you could edit the config files gene= rated. After running configure, look in src/config.h for the line:

#define HAVE_XRANDR 1

= ... and comment it out. Then finish building Emacs normally. From a quick t= est on my system that seems to work okay, though I don't know off the t= op of my head what functionality might be diminished by losing the xrandr s= upport.

Ken
--001a11401b3cd2d89c052d8fa2ba--