From: John Eismeier <john.eismeier@emc.com>
To: Ken Raeburn <raeburn@permabit.com>
Cc: 22932@debbugs.gnu.org, john.eismeier@emc.com
Subject: bug#22932: 25.0.92; X protocol error: BadRequest (invalid request code or no such operation) on protocol request 149
Date: Tue, 08 Mar 2016 17:04:41 -0500 [thread overview]
Message-ID: <uddsi00r5hi.fsf@eismej-u14.spgear.lab.emc.com> (raw)
In-Reply-To: <CAJJWxE9FqXLt-vRjq2tAR9QyZh-Y+e1+ZSH8e6+Ydy9VBmb5TQ@mail.gmail.com>
Sure Ken, How did I end of with old xrandr ?
dpkg -l |grep xrandr
ii libnx-xrandr2:a 2:3.5.0.32-0 amd64 nx-X11 RandR extension library
ii libxrandr-dev:a 2:1.4.2-1 amd64 X11 RandR extension library (develop
ii libxrandr2:amd6 2:1.4.2-1 amd64 X11 RandR extension library
that is why, using X2go server...
xdpyinfo
name of display: :50
version number: 11.0
vendor string: The X.Org Foundation
vendor release number: 70000000
X.Org version: 7.0.0
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst
number of supported pixmap formats: 7
supported pixmap formats:
--
-- John
next prev parent reply other threads:[~2016-03-08 22:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 13:41 bug#22932: 25.0.92; X protocol error: BadRequest (invalid request code or no such operation) on protocol request 149 John Eismeier
2016-03-07 16:21 ` Eli Zaretskii
2016-03-08 13:04 ` John Eismeier
2016-03-08 14:36 ` John Eismeier
2016-03-08 16:27 ` Eli Zaretskii
2016-03-08 20:01 ` Ken Raeburn
2016-03-08 20:10 ` John Eismeier
2016-03-08 20:33 ` Eli Zaretskii
2016-03-08 20:43 ` Ken Raeburn
2016-03-08 20:47 ` Ken Raeburn
2016-03-08 22:04 ` John Eismeier [this message]
2016-03-08 22:16 ` Ken Raeburn
2016-03-08 22:39 ` John Eismeier
2016-03-09 3:42 ` Ken Raeburn
2016-03-09 13:15 ` John Eismeier
2016-03-10 9:42 ` John Eismeier
2016-03-10 20:19 ` Ken Raeburn
2016-03-10 20:33 ` Eli Zaretskii
2016-03-10 20:41 ` John Eismeier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uddsi00r5hi.fsf@eismej-u14.spgear.lab.emc.com \
--to=john.eismeier@emc.com \
--cc=22932@debbugs.gnu.org \
--cc=raeburn@permabit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).