Upgraded. Now Input is broken in xorg.

fundies · 2014-07-31 16:53:16

I upgraded my system today and now when I "startx" my keyboard and mouse are completly unresponsive. However, they work correctly on the console.

.xinitrc
exec startxfce4

Xorg.0.log
http://sprunge.us/YVDf

I'm on kernel 3.15.7-1-ARCH running xorg-server 1.16.0-6. How do I fix my input?

Last edited by fundies (2014-07-31 16:53:31)

shoober420 · 2014-07-31 17:03:19

I'm having this very same bug. If you want a workaround until it gets fixed, check out my thread on how to make it usable without downgrading to 1.15. Do you by chance have no files in your xorg.conf.d folder?

Last edited by shoober420 (2014-07-31 17:03:57)

fundies · 2014-07-31 17:21:29

I have no xorg configs.

shoober420 · 2014-07-31 17:30:14

So you have no .conf files in your xorg.conf.d folder? Neither do I. I added some manually, but supposedly there are supposed to be some in there already. What window manager do you use?

fundies · 2014-07-31 17:40:11

I attempted to write a config for input but they're still unresponsive when I startx, Also I use xfce4.

Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection

Section "InputDevice"
Identifier "logitech-kbd"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "logitech"
Option "XkbLayout" "us"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd"
EndSection

Section "InputDevice"
Identifier "logitech-mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse"
EndSection

Last edited by fundies (2014-07-31 17:40:32)

shoober420 · 2014-07-31 17:44:55

fundies wrote:

Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection

The section this command is supposed to go under, is "ServerLayout".

fundies · 2014-07-31 17:46:46

shoober420 wrote:

fundies wrote:
Section "ServerFlags"
Option "AutoAddDevices" "false"
EndSection
The section this command is supposed to go under, is "ServerLayout".

No difference in behavior

Last edited by fundies (2014-07-31 17:48:04)

shoober420 · 2014-07-31 17:50:39

Did you install the xf86-input-mouse and xf86-input-keyboard packages?

fundies · 2014-07-31 17:57:40

yes

shoober420 · 2014-07-31 18:08:31

Try adding "AllowEmptyInput" "False" to the "ServerLayout" section and see if you have input after that.

shoober420 · 2014-08-02 07:12:48

Hey fundies, look at what tty you belong to when your at the login screen. For example, I belong to tty1. When you start Xserver, you must use the same virtual terminal as what the real terminal is using. So it my case, since I use tty1, I must use vt1 to have Xserver working correctly. This fixed my issue with having no input.

So say, you login from tty3, that means you must use vt3 when you startx.

startx -- -nolisten tcp vt1

Last edited by shoober420 (2014-08-03 04:07:51)

falconindy · 2014-08-02 17:09:52

shoober420 wrote:

Hey fundies, try adding vt1 to your string to launch Xserver. It totally fixed my problem. Thank Procyon for the fix if it helps you.
startx -- -nolisten tcp vt1

It's entirely possible to refer to the similar mention in news post on the front page without using pejorative language.

shoober420 · 2014-08-02 17:33:46

The news page says nothing about getting X to work if you have no input. The key thing here is the vt command line parameter, which is no where to be found on the news page. Only the mentions of where the new conf files are stored. It says nothing about fixing input for X by using vt command, and matching the variable with the tty you loghed in from.

Last edited by shoober420 (2014-08-03 04:08:56)

falconindy · 2014-08-02 17:46:13

TFN wrote:

must be launched from the same virtual terminal as was used to log in

Different words, similar point. Your "workaround" has the downside of not being as generic as the news item. If I login on tty2 (maybe I reserve tty1 for kernel output), then using "vt1" with startx is going to be absolutely wrong. Furthermore, Arch ships an xinitrc.d snippet which launches X correctly on the same VT (using $XDG_VTNR), so your hack shouldn't be necessary.

shoober420 · 2014-08-02 17:56:43

falconindy wrote:

TFN wrote:
must be launched from the same virtual terminal as was used to log in
Different words, similar point.

I login from tty1, so that doesn't help. It clearly says tty1 at the top where I login. This is probably a 1.16 bug. Xorg chooses the best vt to use when logging in, maybe 1.16 doesn't use the best one because there's a bug.

falconindy wrote:

Your "workaround" has the downside of not being as generic as the news item. If I login on tty2 (maybe I reserve tty1 for kernel output), then using "vt1" with startx is going to be absolutely wrong.

If you never had input issues when upgrading to 1.16, then you wouldn't need to use my workaround in the first place. Maybe all you need to do is specify the specific vt you want to run in. So for example, if you want to run in vt2, you can use the following.

startx -- -nolisten tcp vt2

Xserver 1.16 must not be choosing the correct vt at login.

falconindy wrote:

Furthermore, Arch ships an xinitrc.d snippet which launches X correctly on the same VT (using $XDG_VTNR), so your hack shouldn't be necessary.

If 1.16 has a bug in it, a xinitrc.d snippet won't do any good now will it? Some of my config files weren't even loading. My mouse acceleration conf wasn't loading, so I doubt the 30-dbus file in xinitrc.d was loading either. If there is a bug in 1.16, then the workaround would of course be necessary. If I didn't use it, I would still be stuck with xf86-input* This also isn't my workaround, a user by the name of Procyon found this fix.

Last edited by shoober420 (2014-08-02 18:16:13)

Procyon · 2014-08-02 19:58:56

falconindy wrote:

TFN wrote:
must be launched from the same virtual terminal as was used to log in
Different words, similar point. Your "workaround" has the downside of not being as generic as the news item. If I login on tty2 (maybe I reserve tty1 for kernel output), then using "vt1" with startx is going to be absolutely wrong. Furthermore, Arch ships an xinitrc.d snippet which launches X correctly on the same VT (using $XDG_VTNR), so your hack shouldn't be necessary.

I don't have xorg-xinit installed. I think that's what the devs are presuming.

I still think the news article is a bit lazy though. I start X with just Xorg and the sentence "Must be launched from the same virtual terminal" isn't hint enough that I need Xorg vt$XDG_VTNR.

shoober420 · 2014-08-03 04:03:08

Procyon wrote:

I don't have xorg-xinit installed. I think that's what the devs are presuming.
I still think the news article is a bit lazy though. I start X with just Xorg and the sentence "Must be launched from the same virtual terminal" isn't hint enough that I need Xorg vt$XDG_VTNR.

It is a very vague announcement. It doesn't provide any helpful information on what command to use, or anything on how to fix it if it doesn't start on the same virtual terminal. Adding something like, "Use the vtfoo command line parameter to choose the correct virtual terminal. It should be the same that you log in from when starting you machine. so "foo", being the number that's in tty when you get to the login prompt on your machine." Thats what I call, an announcement. I'm sure someone could word it better then I did, but even I made a more logical announcement then what is currently there.

berbae · 2014-08-03 09:22:40

shoober420 wrote:

but even I made a more logical announcement then what is currently there

I don't think saying this is the best way to get a good opinion of you here, especially when you just begin to use Arch and to post here.

Once again if you login using systemd-logind, the XDG_VTNR variable is set to the tty number where you logged in; and that variable is used when you run 'startx' in this same tty so that the vt$XDG_VTNR is automatically added to the Xorg.bin command line as well as the '-nolisten tcp' part.
Here is what I have using only 'startx':

berbae     551   544  0 10:32 tty1     00:00:00 /bin/sh /usr/bin/startx
berbae     568   551  0 10:32 tty1     00:00:00 xinit /home/berbae/.xinitrc -- /etc/X11/xinit/xserverrc :0 -auth /tmp/serverauth.3DqeWxsrM0
root       569   568  2 10:32 ?        00:00:36 /usr/bin/Xorg.bin -nolisten tcp :0 -auth /tmp/serverauth.3DqeWxsrM0 vt1

if the XDG_VTNR is not set for you then there is a problem with your installation.
Before running startx what is the output of 'echo $XDG_VTNR' in the console where you logged in?
You can also look at your current session id with 'loginctl' then run 'loginctl show-session <session id>'.
This has nothing to do with a supposed bug of xorg-server 1.16.

@Procyon
Launching the xorg server directly using the Xorg command is not a usual practice; it's a more common usage to run 'xinit' or 'startx' which is a wrapper to 'xinit'.

shoober420 · 2014-08-03 11:56:39

berbae wrote:

if the XDG_VTNR is not set for you then there is a problem with your installation.
Before running startx what is the output of 'echo $XDG_VTNR' in the console where you logged in?
You can also look at your current session id with 'loginctl' then run 'loginctl show-session <session id>'.
This has nothing to do with a supposed bug of xorg-server 1.16.

I followed the wiki on how to install Arch, step by step. There is no way, that theres something wrong with my installation. Unless, the wiki article on the installation process needs redone. Its very possible that the reason Xserver doesn't select the proper vt, is because of a bug. Remember, I'm not the only one with this issue. If I was, then I would consider it being on my side, but thats not the case.

When I login before starting Xserver, and issue the "echo $XDG_VTNR" command, it reads "1". After that, my output of "loginctl" is the following.

   SESSION        UID USER             SEAT
        c1       1000 foo              seat0

My output for "loginctl show-session", is this.

Id=c1
Name=foo
Timestamp=Sun 2014-08-03 03:42:33 EDT
TimestampMonotonic=26148278
VTNr=1
TTY=tty1
Remote=no
Service=login
Scope=session-c1.scope
Leader=183
Audit=0
Type=tty
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=1407051776365868
IdleSinceHintMonotonic=49086687

Last edited by shoober420 (2014-08-03 11:57:35)

Trilby · 2014-08-03 12:38:47

shoober420 wrote:

I followed the wiki on how to install Arch, step by step. There is no way, that theres something wrong with my installation.

No, you didn't. You really didn't. Nearly every post you've made on these forums since you started has displayed a complete and utter inability to read any documentation. Nearly every such post has also highlighted how you've diverged from the documentation in the wiki (eg, manually creating a lib32 directory and symlinking libraries, running makepkg as root, etc, etc).

It's bad enough when your nonsense is restricted to your own threads, but now you've branched out to creating threads with "advice" to other users that is not only nonsensical, but may even hinder their progress or be harmful. And now you are also hijacking another reasonable user's thread.

These are habits that need to break. And as stern input from nearly every moderator and admin on this forum (including several closed threads) has not made the point, you clearly need more time to absorb this information. If/when you return from your temporary ban, be sure to have taken time to review your own posting behavior and take a new approach before posting again.

Arch Linux

#1 2014-07-31 16:53:16

Upgraded. Now Input is broken in xorg.

#2 2014-07-31 17:03:19

Re: Upgraded. Now Input is broken in xorg.

#3 2014-07-31 17:21:29

Re: Upgraded. Now Input is broken in xorg.

#4 2014-07-31 17:30:14

Re: Upgraded. Now Input is broken in xorg.

#5 2014-07-31 17:40:11

Re: Upgraded. Now Input is broken in xorg.

#6 2014-07-31 17:44:55

Re: Upgraded. Now Input is broken in xorg.

#7 2014-07-31 17:46:46

Re: Upgraded. Now Input is broken in xorg.

#8 2014-07-31 17:50:39

Re: Upgraded. Now Input is broken in xorg.

#9 2014-07-31 17:57:40

Re: Upgraded. Now Input is broken in xorg.

#10 2014-07-31 18:08:31

Re: Upgraded. Now Input is broken in xorg.

#11 2014-08-02 07:12:48

Re: Upgraded. Now Input is broken in xorg.

#12 2014-08-02 17:09:52

Re: Upgraded. Now Input is broken in xorg.

#13 2014-08-02 17:33:46

Re: Upgraded. Now Input is broken in xorg.

#14 2014-08-02 17:46:13

Re: Upgraded. Now Input is broken in xorg.

#15 2014-08-02 17:56:43

Re: Upgraded. Now Input is broken in xorg.

#16 2014-08-02 19:58:56

Re: Upgraded. Now Input is broken in xorg.

#17 2014-08-03 04:03:08

Re: Upgraded. Now Input is broken in xorg.

#18 2014-08-03 09:22:40

Re: Upgraded. Now Input is broken in xorg.

#19 2014-08-03 11:56:39

Re: Upgraded. Now Input is broken in xorg.

#20 2014-08-03 12:38:47

Re: Upgraded. Now Input is broken in xorg.

Board footer