You are not logged in.
I have two computers (A & B) on latest Arch + updates + GnomeShell. Both are with wayland disabled.
A + B: /var/lib/AccountsService/users/e
[User]
Language=en_US.UTF-8
XSession=gnome-xorg
Icon=/var/lib/AccountsService/icons/e
SystemAccount=falseA+B: /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
# Uncoment the line below to force the login screen to use Xorg
#WaylandEnable=false
[security]
[xdmcp]
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=trueOn both computers is running teamviewerd service. I can connect from computer B to computer A and do what I want, but from A to B it behaves like on wayland - still image and I cant do anything. I can move with mouse and it is moving on the second computer, but it is not visible inside teamviewer.
I also noticed on B computer (the remote which I am unable to control) in GDM there's only Gnome & Gnome Classic. There's missing Gnome on Xorg option. On computer A it is preset.
So please, what can it be? It looks like Wayland is still preset over Xorg therefore I am unable to use teamviewer on the second computer.
Thanks for any advice
Last edited by 5ulo (2017-12-04 10:44:34)
Offline
just choose gnome on X in the gdm screen
ezik
Offline
@Shulamy, as you can see in my post I mentioned there's no option Gnome on X inside the cog menu in GDM! And as you can see /var/lib/AccountsService/users/e is telling me that I am already in gnome-xorg
Offline
The /etc/gdm/custom.conf you posted has a comment sign before "WaylandEnable=false" .
I suggest you doublecheck that file on the troublesome computer.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks Lone_Wolf. I tried all the variants. UnCommented -> freezed (still) image
Tried to connect from Phone and from computer A. Config files are the same (WaylandEnable=false).
I'm so desperate I started to diff config files between computer A & B. No luck for now
Edit:
according to this thread on r/Archlinux I am already on Xorg (no Gnome-Xorg option under the GDM cog) and also $XDG_SESSION_TYPE returns x11
Last edited by 5ulo (2017-12-03 23:39:26)
Offline
The /etc/gdm/custom.conf you posted has a comment sign before "WaylandEnable=false" .
I suggest you doublecheck that file on the troublesome computer.
That is only about how GDM is run, that's independent of the desktop session. E.g. I run GDM on Wayland, but run GNOME on X.org.
... there's no option Gnome on X inside the cog menu in GDM!
Does /usr/share/xsessions/gnome-xorg.desktop exist? But according to your other comments this does not seem to be a Wayland issue if you are sure you are not running GNOME on Wayland.
Offline
@phw yes, gnome-xorg.desktop exists
As I see it now, it looks like x11 problem. Found no information about Teamviewer and freezed still image of the remote desktop.
Offline
So.. maybe a solution... in /etc/X11/xorg.conf.d/20-intel.conf switched from glamor to uxa on computer B. So now computer A is running glamor, computer B uxa.. I can connect to both computers via Teamviewer now.
Option "AccelMethod" "uxa"
#Option "AccelMethod" "glamor"Disadvantage of the uxa method - the mouse cursor in teamviewer android is huge.. and I mean REALLY huge https://imgur.com/a/VbBoh. Anyway.. I'm happy for now..
Offline
Afaik xf86-video-intel doesn't support glamor, modesetting driver (comes with xorg-server) does though and defaults to glamor .
You may want to check xorg logs & conf files on both systems to verify they're configured correctly.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@Lone_Wolf Thanks for the infos about glamor.
I made few more tests right now. With AccelMethod on both computers:
uxa - Teamviewer working
sna - screen not refreshing
I have found any related errors in xorg log. So I suppose the not-refrehsing remote desktop screen in teamviewer has something to do with the sna acceleration method.
Last edited by 5ulo (2017-12-04 12:54:31)
Offline
Sna has problems on many intel videocards, reverting to uxa used to be a common workaround.
Keep in mind though that uxa is old and i doubt newer intel chipsets support it anymore.
Partially due to the sna problems, sane default for intel chipsets has become the modesetting / glamor driver.
I suggest you remove xf86-video-intel and related conf files to test how well your cards work with that.
Last edited by Lone_Wolf (2017-12-05 12:18:12)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline