You are not logged in.
I'm having problems with Xorg.bin after logging out of a DE (XFCE and gnome as well).
The screen goes black and the process Xorg.bin (/usr/bin/Xorg.bin :0 -audit 0 -auth /var/lib/mdm/:0.Xauth -nolisten tcp vt7) hangs using 100% on one CPU core.
The same happens if I try to switch a VT.
I tried different login managers including GDM, LightDM and MDM and the issue is present in all of them so the problem is with X.
Actually on GDM and LightDM this occurs less often but with MDM it happens always.
Here's the Xorg.0.log: http://pastebin.com/e2ThTJp4
System is a vm inside vmware using xf86-video-vmware drivers and open-vm-tools & open-vm-tools-dkms.
I did an -Syu.
Any idea?
Thanks!
cat.7 - where crosstalk is not an issue anymore :'(
Offline
Additional info,
I just discovered this happens only if the VM screen/console has been resized or opened in full screen.
If I keep the VM console as a window, xorg behaves normally, i.e. I can logout&switch VTs normally and the login manager appears.
cat.7 - where crosstalk is not an issue anymore :'(
Offline
I have same problem, same if no resize logout works as expected. What is going on!!!
Offline
I have the same problem, and I'm really surprised that this isn't being reported more often, and that it hasn't already been fixed. It's affecting me on Arch, and on openSUSE Factory. There's either something wrong with Xorg 1.16, VMware, or a combination of both.
What I did to "solve" the problem was to do a fresh install, but before installing anything, I make a few modifications to /etc/pacman.conf.
First, I comment out the official Arch repos, and add the "Arch Rollback Machine" repos to /etc/pacman.conf
[core]
SigLevel = PackageRequired
Server=http://seblu.net/a/arm/2014/07/27/$repo/os/$arch
[extra]
SigLevel = PackageRequired
Server=http://seblu.net/a/arm/2014/07/27/$repo/os/$arch
[community]
SigLevel = PackageRequired
Server=http://seblu.net/a/arm/2014/07/27/$repo/os/$arch
July 27th was the last day that I could track down before all the changes, so I updated my system to what was in the official Arch repos as of July 27th.
Once the system is updated, I switch back to using the official repos and add the following entries into pacman.conf so Xorg wouldn't be updated:
IgnorePkg=xorg-server
IgnorePkg=xorg-server-common
IgnorePkg=xf86-input-evdev
IgnorePkg=xf86-video-vmware
IgnorePkg=xorg-server-xvfb
IgnoreGroup=xorg
Now everything stays totally up to date, except I'm locked on Xorg 1.15 until this situation gets resolved.
Offline
Does it behave properly with xorg 1.15? Which 1.15 is it exactly? There are numerous updates.
Offline
I haven't had any issues since I made sure to keep Xorg at 1.15. The version on my system is 1.15.2, which is what is in the Arch Rollback Machine repos as of July 27.
Offline
What are your versions of mesa, x11-drivers/xf86-video-vmware, open-vm-tools?
Offline
1.15.2 is indeed working, never mind about my request for versions
Offline
I don't know what's going on, and I'm amazed that this isn't being reported all over the place because it's affecting EVERY distribution I try. For example just today I did a totally clean install of Arch, the new openSUSE 13.2 (and Factory)... If you try to restart or shutdown after having maximized the VMware Player window, or full-screening it, Xorg.bin will hang with 100% CPU usage.
Xorg 1.16, the xf86-video-vmware driver, and open-vm-tools DO NOT work together.
Who exactly can this bug be reported to?
Last edited by antnythr (2014-11-07 02:56:12)
Offline
Who exactly can this bug be reported to?
If you think it's an Xorg bug: https://bugs.freedesktop.org is the place to go.
Offline
Of course the site is down at the moment
It turns out the problem is specifically with Xorg 1.16 and the xf86-video-vmware driver. Totally independent of open-vm-tools (problem exists when it's not even installed).
I found the bug posted to the Debian mailing list (https://bugs.debian.org/cgi-bin/bugrepo … bug=765490). So that's Arch, openSUSE, and Debian that are affected. I assume that means every distribution with Xorg 1.16 is affected.
Every fresh install of Arch that uses Xorg (on a virtual machine with VMWare) will be affected so I wonder why this has been so under reported.
Offline