Both keysym resolve and connection lost when attempting to run startx

synftw · 2019-09-12 19:38:57

Hello everyone. First time posting, but I'm in a real bind. I installed Arch fresh last night then installed and set up bspwm. Everything was working great and I continued to configure a bit in bspwm and it was running perfectly. Today I attempt to run startx and I'm unable to get past these keyboard/keycodes issues. I've spent hours trying to research a solution but alas I'm too much of anoob to know what I'm doing.

I created a log of the startx execution. I can provide anything requested. Thanks for taking a look.

EDIT: The outstanding errors are now highlighted below. Thanks for the help getting me this far! I guess the warning messages are related to wayland and not important:

xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)

> Internal error: Could not resolve keysym XF86MonBrightnessCycle
> Internal error: Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
xinit: connection to X server lost

X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux Archbox2.0 4.19.72-1-lts #1 SMP Tue Sep 10 16:48:44 CEST 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=f6b5d3db-6178-4d3d-a889-9c55dbc6e2d1 rw loglevel=3 quiet
Build Date: 30 June 2019  09:52:01AM
 
Current version of pixman: 0.38.4
	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/syn/.local/share/xorg/Xorg.0.log", Time: Thu Sep 12 21:55:10 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

Last edited by synftw (2019-09-12 23:15:38)

Swiggles · 2019-09-12 20:16:17

This sounds like a configuration issue. Could you please show your users bspwm configuration files and your ~/.xinitrc?

Please try to move/rename the sxhkd config and start again.

mv ~/.config/sxhkd{,_backup}
startx

Last edited by Swiggles (2019-09-12 20:17:00)

seth · 2019-09-12 20:43:30

> Error:            Can't find file "querty" for symbols include
>                   Exiting

"qwerty" - you put a bogus keyboard layout somewhere causing the termination of something and that something is probably bspwm or sxhkd

synftw · 2019-09-12 21:28:01

Swiggles wrote:

This sounds like a configuration issue. Could you please show your users bspwm configuration files and your ~/.xinitrc?

#! /bin/sh

sxhkd &

bspc monitor -d I II III IV V VI VII VIII IX X

bspc config border_width         2
bspc config window_gap          12

bspc config split_ratio          0.52
bspc config borderless_monocle   true
bspc config gapless_monocle      true

bspc rule -a Gimp desktop='^8' state=floating follow=on
bspc rule -a Chromium desktop='^2'
bspc rule -a mplayer2 state=floating
bspc rule -a Firefox desktop^2 floating=on
bspc rule -a Kupfer.py focus=on
bspc rule -a Screenkey manage=off

panel &

if [ -d /etc/X11//xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

# parcellite &
# stalonetray &
sxhkd &
exec bspwm &
xbindkeys

Also I fixed the querty issue, it's back to "us" now.

jasonwryan · 2019-09-12 21:30:14

Arch Wiki xinit article wrote:

Remember that lines following a command using exec would be ignored.

Swiggles · 2019-09-12 21:31:02

sxhkd &

Is in both files. Wouldn't it cause some issues?

synftw · 2019-09-12 21:49:38

jasonwryan wrote:

Arch Wiki xinit article wrote:
Remember that lines following a command using exec would be ignored.

That took care of a few more errors!

here's what the startx looks like now:

X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux Arch Linux
Current Operating System: Linux Archbox2.0 4.19.72-1-lts #1 SMP Tue Sep 10 16:48:44 CEST 2019 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=f6b5d3db-6178-4d3d-a889-9c55dbc6e2d1 rw loglevel=3 quiet
Build Date: 30 June 2019  09:52:01AM
 
Current version of pixman: 0.38.4
	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/syn/.local/share/xorg/Xorg.0.log", Time: Thu Sep 12 21:46:23 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

synftw · 2019-09-13 23:44:17

Still wondering how I could best resolve this issue. Is it the keysym issues preventing X from starting, or should I pursue the xinit connection issue?

Trilby · 2019-09-14 00:25:25

Both of your xorg logs quite clearly state that the server terminated successfully. There is no "error" present - at least not one problematic for running X. Your xinitrc is just does nothing.

You exec and background, so the xinitrc exits as soon as it starts (possibly leaving bspwm zombie processes running). Once xinitrc is done, X shuts down successfully. Fix your xinitrc.

Arch Linux

#1 2019-09-12 19:38:57

Both keysym resolve and connection lost when attempting to run startx

#2 2019-09-12 20:16:17

Re: Both keysym resolve and connection lost when attempting to run startx

#3 2019-09-12 20:43:30

Re: Both keysym resolve and connection lost when attempting to run startx

#4 2019-09-12 21:28:01

Re: Both keysym resolve and connection lost when attempting to run startx

#5 2019-09-12 21:30:14

Re: Both keysym resolve and connection lost when attempting to run startx

#6 2019-09-12 21:31:02

Re: Both keysym resolve and connection lost when attempting to run startx

#7 2019-09-12 21:49:38

Re: Both keysym resolve and connection lost when attempting to run startx

#8 2019-09-13 23:44:17

Re: Both keysym resolve and connection lost when attempting to run startx

#9 2019-09-14 00:25:25

Re: Both keysym resolve and connection lost when attempting to run startx

Board footer