Summary: | Assertion failed: dpy->xcb->reply_data != NULL while running xmodmap | ||
---|---|---|---|
Product: | xorg | Reporter: | Yevgeniy <YLitvinenko> |
Component: | * Other | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | critical | ||
Priority: | high | CC: | peter.hutterer |
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Solaris | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Yevgeniy
2009-09-20 11:18:06 UTC
which version of the server are you running and what's the full command you passed into xmodmap? (In reply to comment #1) > which version of the server are you running and what's the full command you > passed into xmodmap? xserver from git commit 24716b9254fa7d609792596723a192bb044a7d3f Date: Fri Aug 28 22:52:48 2009 -0400 From Xorg.0.log: X.Org X Server 1.6.99.1 Release Date: (unreleased) X Protocol Version 11, Revision 0 Build Operating System: SunOS 5.11 i86pc Current Operating System: SunOS solaris 5.11 snv_122 i86pc Build Date: 31 August 2009 10:56:48PM 'xmodmap -display' runs without the error. It prints usage and available options. 'xmodmap -display :0.1' :0.1 incorrect display gives message xmodmap: unable to open display ':0.1' 'xmodmap -display :0.0' (:0.0 - correct display) and all other options (and without any options) give the error. I've just cloned xserver from git and built it. Error the same. 'git log' shows last commit - commit d3a3c904e5e3b5e8bb3c51ca6a563880ff589bf3 Date: Mon Sep 21 09:41:46 2009 +1000 Yevgeniy, are you still seeing this with xserver 1.7.x releases? (Looks like bug 20357 BTW) Now I am using Xorg 1.7.4 provided with OpenSolaris b132 so my check may be incorrect. But xmodmap (compiled from source) works fine. I checked that xmodmap uses X libraries compiled from source (not provided with OS) Thanks for the update, let's assume it's been fixed. Please reopen if you see it again. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.