You are not logged in.
+1
I love this distro.
Offline
Same here! No workaround needed anymore... txh alot!
Just curious... why is extension XEVIE loaded explicitly?
/var/log/Xorg.0.log informed me that
(II) Initializing built-in extension XEVIE
even without setting it in gdms config.
Regards,
Martin
Offline
Seems to be something GNOME wants:
XEvIE (X Event Interception Extension)
XEvIE is an extension to intercept core keyboard and pointing device input It allows consumation, modification or synthesis of input events before these are sent to their final destination (i.e., interested clients). This feature is required by the GNOME accessibility project.
(source: http://xorg.freedesktop.org/archive/X11 … OTES2.html)
PC: Antec P182B | Asus P8Z77-V PRO | Intel i5 3570k | 16GB DDR3 | GeForce 450GTS | 4TB HDD | Pioneer BDR-207D | Asus Xonar DX | Altec Lansing CS21 | Eizo EV2736W-BK | Arch Linux x86_64
HTPC: Antec NSK2480 | ASUS M3A78-EM (AMD 780G) | AMD Athlon X3 425 | 8GB DDR2 | GeForce G210 | 2TB HDD | Arch Linux x86_64
Server: Raspberry Pi (model B) | 512MB RAM | 750GB HDD | Arch Linux ARM
Offline
I've used libx11 1.0.9x and beta versions of libxcb for a long time before putting the final versions into current. I never noticed any problem, except for the assertion in libgl-dri, which got fixed when I added libxcb 1.0 and libx11 1.1 to the repositories. (FYI: I couldn't reproduce a single problem from the bugreports, only neverwinter nights looks plausible to me, but I don't own that game).
I'll see what freedesktop.org has to say about these things in the upcoming week, so I can backport things from git. I'll add a package of libx11 to testing or unstable in a while which has libxcb support enabled again.
Offline
JGC:
I upgraded (pacman -Syu) two computers couple of days ago, and ran into the gdm problem. When I see a lot of Gnome changes, I usually log out of Gnome, get in a console window, kill the X server then upgrade. This time I forgot to do this and upgraded from a terminal window from within Gnome. Don't know if this had anything to do with it.
Last night, I was deleting a computer and then adding a computer to my folding farm. I ended up doing a complete clean install via FTP on two computers, including Xorg and Gnome. To my surprise, the two clean installs did not experience the gdm problem, even with libx11-1.1-1 installed. I was expecting to have to copy over an old version of libx11 to make things work.
All four computers have Nvidia chipsets, and Nvidia GPUs. Two clean installs worked, and two updates did not. Don't know if that could be a clue to help or not.
Pudge
Offline
# pacman -Ss libx11
testing/libx11 1.1.1-1
X11 client-side library
current/libx11 1.1-2
X11 client-side library
Libx11 from testing has been rebuild (see bug report http://bugs.archlinux.org/task/5896).
And the gdm problem is back for me. Reverting to current/libx11 solves this bug.
Sorry JGC...
Offline
I have the same problem and came here to say that the package in the testing repo is bringing back that problem..
Quis custodiet ipsos custodiet?
Offline
# pacman -Ss libx11 testing/libx11 1.1.1-1 X11 client-side library current/libx11 1.1-2 X11 client-side library
Libx11 from testing has been rebuild (see bug report http://bugs.archlinux.org/task/5896).
And the gdm problem is back for me. Reverting to current/libx11 solves this bug.
Sorry JGC...
Same thing I did yesterday to remedy the problem
Offline
I don't use gdm but I have the same problem with testing/libx11 and vmware-workstation. Reverting to current/libx11 fixes it. I believe the error was:
xcb_lock.c:62: _XGetXCBBuffer: Assertion ((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
The only thing I found on google was:
'Did you configure Xlib with --disable-xthreads? Don't do that. To use
XCB, XTHREADS must be defined when building all libraries that use
Xlibint.h. This doesn't mean that Xlib actually has to support threads,
but the LockDisplay and UnlockDisplay macros must expand to their normal
code. If anybody really wants the ability to disable the rest of the
thread support, that can be arranged.'
Offline
The only thing I found on google was:
'Did you configure Xlib with --disable-xthreads? Don't do that.
PKGBUILD for libx11 doesn't configure it with --disable-xthreads.
to live is to die
Offline
Upgraded to GDM 2.6.14 - problem solved.
Offline
Upgrading to GDM 2.16.4 fixed this problem for me as well.
Offline