You are not logged in.
https://i.imgur.com/qrKlf21.png
I switched from Plasma 5 to i3 and this keeps happening. Not sure if i removed something I shouldn't and I really don't know where to look for problems. Any guidance is appreciated. Thanks!
The weird characters only happening when writing on a "Rofi" menu. If i write anywhere else everything works normally.
Besides that, my touchpad doesn't work normally. I can't press left click / right click but I can scroll with two fingers.
Mod edit: Links or thumbnails only please -- V1del
Last edited by V1del (2018-06-20 17:44:19)
Offline
Please only post thumbnails or links to images: https://wiki.archlinux.org/index.php/Co … s_and_code
Make sure all your fonts are properly configured, as for configuring the touchpad you will want to read https://wiki.archlinux.org/index.php/Libinput however there are currently some known issues with libinput and touchpads, so you might want to check if a downgrade to e.g. 1.11.0 restores functionality you think should be there without explicit configuration.
Offline
I've tried downgrading libinput but without luck as suggested on many other posts.
I don't think its a font config error, because its not the display but the actual characters. Seems to be like a config error on the keyboard layout but it only affects rofi (?). This throws me off a bit
Offline
setxkbmap -query -v
Offline
Output of: setxkbmap -query -v
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+latam+inet(evdev)+capslock(swapescape)
geometry: pc(pc105)
rules: evdev
model: pc105
layout: latam
options: caps:swapescape
Offline
Nope. (I thought this may be due to a multi-layout setup)
How do you invoke rofi? Does it also happen if you call it from an interactive shell?
Sidenote: please always wrap command output in "code" tags, thanks.
Offline
Nope. (I thought this may be due to a multi-layout setup)
How do you invoke rofi? Does it also happen if you call it from an interactive shell?Sidenote: please always wrap command output in "code" tags, thanks.
I have a keybind set on my i3-config to execute this:
rofi -dmenu -i -p "search: "
Yes it also happens if rofi is invoked from an interactive shell.
This happens sometimes and then it sometimes fixes all by itself after 10-15 mins or sometimes i have to relog (restart X with startx) so it fixes for a while and then it happens again.
Also when this happens, I can't Left/Right click properly either with touchpad or my mouse.
Last edited by marini (2018-06-22 17:00:36)
Offline
Errr… so the effect isn't permanent and not initially?
Was the setxkbmap output from this condition or when the system was "good"? Is there a difference?
Also what do you mean by "properly" when discussing clicks? Do the clicks generate no events or unexpected events?
Did you check them in xev or is this problem limited to rofi likewise?
Also please paste an xorg log from after this occurred (in doubt some xorg.0.log.old if you had to restart the server)
Offline
Yes, it's not permament. Sometimes everything is fine.
Yes the output of setxkbm is the same in both cases.
Its kind of weird. The clicks are recognized inside of, for example, chromium or other applications but I can't click properly on the "tabs" section of chromium but works normally on the actual webpages (although I can't drag-click to select text when this occurs) for example or on the URL bar.
When this happens I try to run xev (with and without sudo just in case) and It doesn't recognize the click events (keyboard events do work normally).
Only the keyboard problem is limited to rofi. The clicking issue is not.
Xorg.0.log https://pastebin.com/eae5RAMe
Xorg.0.log.old https://pastebin.com/umavcG7P
Offline
At least there's an obvious pattern - at some point you're loosing all input devices and they then get re-attached.
I assume you're setting the layout etc. w/ some command in your xinitrc (so they won't be applied on re-attachment), but what's even more worrying is the optimus configuration and the existence of a /etc/X11/xorg.conf that seems pretty much to be generated by nvidia-xconfig?
Did you read and follow https://wiki.archlinux.org/index.php/Optimus in any direction (and which)?
What do your xinitrc and /etc/X11/xorg.conf look like?
Offline
Yes my xorg.conf is generated by nvidia-xconfig and yes i followed the arch wiki guide for Optimus but didn't get it to work till I saw some posts in the forum and around google.
Is this related though? Or did i configure it improperly?
xinitrc
#!/bin/sh
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
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto
i3
setxkbmap -layout latam -option caps:swapescape
/etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 384.69 (buildmeister@swio-display-x86-rhel47-06) Wed Aug 16 20:57:01 PDT 2017
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
EndSection
Section "Module"
Load "modesetting"
Load "glx"
EndSection
Section "InputDevice"
# generated from default
Identifier "Keyboard0"
Driver "keyboard"
EndSection
Section "InputDevice"
# generated from default
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "no"
Option "ZAxisMapping" "4 5"
EndSection
Section "Device"
Identifier "nvidia"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "nvidia"
DefaultDepth 24
Option "AllowEmptyInitialConfiguration"
SubSection "Display"
Depth 24
Modes "nvidia-auto-select"
EndSubSection
EndSection
Offline
The last line in your xinitrc won't apply until i3 terminates, so this will likely also be invoked by some i3 config script?
At least remove the two input devices from the xorg.conf (this is just garbage nvidia keeps writing there - the referenced drivers are rotting dead) and instead configure your keyboard correctly:
/etc/X11/xorg.conf.d/11-keyboard.conf
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
# MatchProduct "<model vendor name>" # optional, fetch the name from xinput
Option "XkbLayout" "latam"
Option "XkbOptions" "caps:swapescape"
Driver "libinput"
EndSection
Offline
Yes the i3 config is the one that actually calls the setxkbmap.
I added the 11-keyboard.conf file and removed the input devices and their references from the xorg.conf but the error keeps happening.
What else could be causing the problem?
Offline
Some IM like fcitx?
https://wiki.archlinux.org/index.php/In … ut_methods
ps aux
Offline
Nope, I have none installed.
Offline
Some rofi bug, maybe triggered by your specific config.
Tried to reproduce this w/ the default config and possibly not in dmenu mode?
Offline
Yes I've tried using it with default configs and without dmenu mode but the result is still the same.
Offline