You are not logged in.
Hello everyone,
I'm having an issue trying to install the Intel XWayland package ('xf86-video-intel-xwayland-git') from AUR.
The ./configure step runs with no errors. However, the build step gives me the following error:
sna_accel.c: In function 'migrate_dirty_tracking':
sna_accel.c:15226:3: error: too many arguments to function 'DamageUnregister'
DamageUnregister(&dirty->src->drawable, dirty->damage);
^
In file included from /usr/include/xorg/pixmapstr.h:53:0,
from /usr/include/xorg/xf86str.h:40,
from /usr/include/xorg/xf86.h:44,
from ../../src/intel_options.h:4,
from sna_accel.c:32:
/usr/include/xorg/damage.h:77:2: note: declared here
DamageUnregister(DamagePtr pDamage);
Following the AUR comments' instructions, I run the commands:
cd src/xf86-video-intel
git cherry-pick 524a45da56e2a052ffafa3887891caa90ba39f76
cd ../..
makepkg -esi
... and then, when trying to build it again, it gives me the following output:
CC intel_driver.lo
intel_driver.c: In function 'I830LeaveVT':
intel_driver.c:1178:6: error: 'xorgWayland' undeclared (first use in this function)
if (xorgWayland)
^
intel_driver.c:1178:6: note: each undeclared identifier is reported only once for each function it appears in
intel_driver.c: In function 'I830EnterVT':
intel_driver.c:1200:6: error: 'xorgWayland' undeclared (first use in this function)
if (xorgWayland)
I've searched for this error, but all I found was a Phoronix forum comment.
After that, I tried to build it with the '--disable-sna' flag, but the output is exactly the same.
I have XWayland package installed ('xwayland-git' from AUR). Actually, my goal is to test GNOME on Wayland.
Any help on this issue?
Best regards,
feaneron
Last edited by feaneron (2014-05-03 18:30:14)
Offline
AFAIK, the individual XWayland DDX's are dead. They're using Glamor for everything, and it's included with the server build.
Offline
Thanks for the quick reply, Scimmia.
In fact, I was able to compile without problems Intel Glamor ('xf86-video-intel-glamor-git' from AUR).
However, XWayland + Intel Glamor gives me a frozen GDM.
I'll mark this thread as solved anyway.
Offline
Have you tried it without messing with the driver at all? Like I said, the required DDX is included with the server now.
Offline
XWayland now works by using the development version of the X Server which has XWayland merged and using a wayland compositor like weston, mutter patched for the new XWayland DDX. There is no need for a special xf86-video-*-wayland driver anymore.
Offline
It seems that the development version of X server is not enough to run GNOME on Wayland.
When I log in, the screen gets black and returns to GDM.
Offline
Yes, because the xwayland patch to mutter for the new xwayland implementation was applied after the Gnome 3.12 release.
Offline
Even Mutter Wayland 3.12.1 does not have the XWayland patch? I have gnome-unsable enabled, shouldn't it work?
Offline
I tried to install 'mutter-git' from AUR. It gives me a black screen when starting GDM.
Is there any way actually to test GNOME on Wayland with Arch Linux?
Offline
I built some xwayland things on a vmware virtual machine and also got frozen gdm (the Xorg stack seems broken, wondering why), but I'm able to launch gnome on wayland using
gnome-session --session=gnome-waylandin the VT.
I used this git snapshot to replace mutter-wayland package. Support for the new xwayland ddx need some changes and it is not merged into 3.12 series. However, mutter in 3.13 is undergoing great changes so I chose an earlier snapshot just after the support for xwayland ddx happens to avoid potential problems.
Offline
Even Mutter Wayland 3.12.1 does not have the XWayland patch? I have gnome-unsable enabled, shouldn't it work?
Gnome unstable doesn't track the development branch throughout the development cycle. It's more like a staging area to get things working before moving a new release into [testing] and from there to [extra] that why [gnome-unstable] doesn't contain any packages at that point. Point releases are for bug fixes not for new features.
After 3.12 mutter-wayland was also merged into mutter. So for the 3.14 release there won't be a mutter and mutter-wayland package anymore. Something to keep in mind when updating to development branches of Gnome.
Last edited by blackout23 (2014-05-01 15:15:11)
Offline
I'm marking this thread as SOLVED since the original question was properly answered.
I'll start another thread about GNOME on Wayland.
Offline