On Wed, Apr 8, 2015 at 11:16 AM, Pekka Paalanen
wrote:
> try removing that tab from your .ini.
I tried with spaces, with tab, and without; But probably when I first
tried without indentation, I didn’t save, because: After removing the
tab, now it works!
> Should probably fix that one day...
Don
On Wed, Apr 8, 2015 at 8:20 AM, Pekka Paalanen
wrote:
> if you check Weston's output, it says which config file it is reading.
> Is it reading the one you are editing?
To create the attached log file I ran:
$ weston-launch –-verbose >/tmp/weston.log 2>&1
Starting `xterm` from within the Wes
On Tue, Apr 7, 2015 at 7:39 PM, Jasper St. Pierre
wrote:
> Menus appear fine on my machine.
I just tried again, after updating my Arch system yesterday: Some of the
menus work, for example the view menu. Others are accessible as well
when clicking the middle mouse button, but they are placed in o
Should I report this somewhere?
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
When I click on a menu in [Xfig][1] running in xwayland, then it doesn’t
appear. The same Xfig installation in X.org runs fine.
I start Wayland directly from the console, i.e. with DRI/KMS:
$ weston-launch
`weston.ini`:
[core]
modules=xwayland.so
System:
* VMware Player guest
