Bug#872398: closed by Julien Cristau (Re: Bug#872398: x11-xkb-utils: setxkbmap, when run at startup, has no effect)

2022-04-22 Thread Christopher Cramer
On Fri, Apr 22, 2022 at 02:48:03PM +, Debian Bug Tracking System wrote:
> Closing this old report.  It's not a bug in x11-xkb-utils, but probably
> in the X server, where changes made before the first keypress get (or
> used to get?) overwritten.  IIRC we had a number of reports about that
> over the years.

The bug seems to have been fixed anyway. The problem went away, and I
totally forgot about it.



Bug#872398: x11-xkb-utils: setxkbmap, when run at startup, has no effect

2017-08-16 Thread Christopher Cramer
Package: x11-xkb-utils
Version: 7.7+3+b1
Severity: normal

This is my .xsession (which is executed by xdm):

xsetroot -solid black
xset -b
xset s 0
xset s off
xset dpms 0 0 0
xset -dpms
xset r rate 250 30
setxkbmap -keycodes evdev -types default -compat 
'basic+misc+iso9995+ledcaps(group_lock)' -symbols 
'pc+us+kh:2+level3(ralt_switch)+ctrl(nocaps)'
xkbset -bell -feedback sticky -twokey latchlock
xkbset exp '=sticky'
ssh-agent &
export _JAVA_AWT_WM_NONREPARENTING=1
exec ratpoison

It all used to work perfectly. But at some point, the setxkbmap command
stopped having any effect when run from the .xsession file. I notice
this immediately after Ratpoison has started because I am used to hitting
the Caps Lock key, intending for it to be remapped as Control, to enter
a Ratpoison command. But instead it acts as Caps Lock. It is as if the
setxkbmap command was never run at all.

However, if I enter that same command manually (in bash, running in
urxvt), it works. The .xsession file is definitely being executed,
because the effects of all the other commands are happening.  I tried
also putting the command into the Ratpoison startup file, .ratpoisonrc,
but it didn't work there either.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages x11-xkb-utils depends on:
ii  libc62.24-14
ii  libx11-6 2:1.6.4-3
ii  libxaw7  2:1.0.13-1+b2
ii  libxkbfile1  1:1.0.9-2
ii  libxt6   1:1.1.5-1

x11-xkb-utils recommends no packages.

x11-xkb-utils suggests no packages.

-- no debconf information



Bug#827984: assertion failure with multiple GPUs and Xinerama enabled

2016-06-24 Thread Christopher Cramer
On Fri, Jun 24, 2016 at 11:15:05AM +0900, Michel Dänzer wrote:
> Does the attached patch fix this?

Well, it doesn't die with an assertion failure anymore.

But the behavior is not what I would expect - the screens are all
mirrored. Maybe that is a separate issue, though.



Bug#827984: assertion failure with multiple GPUs and Xinerama enabled

2016-06-23 Thread Christopher Cramer
Package: xserver-xorg-video-radeon
Version: 1:7.7.0-1
Severity: normal

I have a FirePro 2450, which is a single card that has two GPUs and shows up
as two separate PCI devices, with two DVI outputs per GPU.

Xinerama seems to be unofficially deprecated these days, but anyway the X
server dies on assertion failure when Xinerama is enabled with multiple
GPUs.

I have Xinerama commented out in xorg.conf below, but the failure only
occurs when that line is uncommented. The second Device section is
commented out because I only actually have three monitors.

I would be very happy to gather any further information, or test anything.

The PCI listing below is missing the second device (as it is not 
"VGA-compatible"):
04:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 
[FirePro 2450]

This is the output of startx:

X.Org X Server 1.18.3
Release Date: 2016-04-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux chiba 4.6.0-1-amd64 #1 SMP Debian 4.6.2-1 
(2016-06-15) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.6.0-1-amd64 
root=UUID=157516c6-17ed-42eb-9339-774d57b22ad3 ro quiet
Build Date: 05 April 2016  07:00:43AM
xorg-server 2:1.18.3-1 (http://www.debian.org/support) 
Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/tsuyoshi/.local/share/xorg/Xorg.1.log", Time: Wed Jun 22 
17:56:01 2016
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
(II) [KMS] Kernel modesetting enabled.
(II) [KMS] Kernel modesetting enabled.
Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion 
`key->initialized' failed.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

Here is a backtrace:

Reading symbols from /usr/lib/xorg/Xorg...Reading symbols from 
/usr/lib/debug/.build-id/4c/eb67899a8a459f80a13558c62ec29727d131b5.debug...done.
done.
[New LWP 4230]
[New LWP 4231]
[New LWP 4232]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg :0 -core vt1 -keeptty -auth 
/tmp/serverauth.YVMB8aqSkm'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7fa75f914458 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
[Current thread is 1 (Thread 0x7fa761b7fa00 (LWP 4230))]
#0  0x7fa75f914458 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x7fa75f9158da in __GI_abort () at abort.c:89
#2  0x7fa75f90d387 in __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fa75b3ec350 "key->initialized", 
file=file@entry=0x7fa75b3ec324 "/usr/include/xorg/privates.h", 
line=line@entry=122, 
function=function@entry=0x7fa75b3edf40 <__PRETTY_FUNCTION__.10025> 
"dixGetPrivateAddr") at assert.c:92
#3  0x7fa75f90d432 in __GI___assert_fail 
(assertion=assertion@entry=0x7fa75b3ec350 "key->initialized", 
file=file@entry=0x7fa75b3ec324 "/usr/include/xorg/privates.h", 
line=line@entry=122, 
function=function@entry=0x7fa75b3edf40 <__PRETTY_FUNCTION__.10025> 
"dixGetPrivateAddr") at assert.c:101
#4  0x7fa75b39c74d in dixGetPrivateAddr (key=, 
key=, privates=0x563fb3b312c8) at 
/usr/include/xorg/privates.h:122
#5  0x7fa75b3d7435 in dixGetPrivateAddr (key=, 
key=, privates=) at ../../src/radeon_kms.c:295
#6  dixLookupPrivate (key=, privates=) at 
/usr/include/xorg/privates.h:165
#7  RADEONCreateScreenResources_KMS (pScreen=0x563fb3b30ef0) at 
../../src/radeon_kms.c:244
#8  0x563fb2ce473e in xf86CrtcCreateScreenResources (screen=0x563fb3b30ef0) 
at ../../../../hw/xfree86/modes/xf86Crtc.c:716
#9  0x563fb2c75abe in dix_main (argc=7, argv=0x7ffd5dd6af98, 
envp=) at ../../dix/main.c:225
#10 0x7fa75f9015f0 in __libc_start_main (main=0x563fb2c5ff60 , 
argc=7, argv=0x7ffd5dd6af98, init=, fini=, 
rtld_fini=, stack_end=0x7ffd5dd6af88) at libc-start.c:291
#11 0x563fb2c5ff99 in _start ()

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jun 16 14:03 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Apr  5 03:05 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] RV620 [FirePro 2450] [1002:95cd]

Xorg X server configuration file status:

-rw-r--r-- 1 root root 829 Jun 22 22:16 /etc/X11/xorg.conf

Contents of /etc/X11/xorg.conf:
---
Section "ServerFlags"
#   Opti

Bug#692396: seems to be fixed

2012-12-23 Thread Christopher Cramer
The problem no longer appears in 2:1.12.4-4. I don't see anything in
the changelog that seems like it could be related, so I may have filed
it under the wrong package.


-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121223131920.ga3...@tokyo.foo