From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix@gnu.org
Subject: Re: Wayland setup
Date: Tue, 13 Mar 2018 20:50:33 +0100 [thread overview]
Message-ID: <a8414388-4626-0f0a-8003-ccd42639dbfa@freenet.de> (raw)
In-Reply-To: <528f623e-8a05-413c-f7bc-bd3f9a82c14d@freenet.de>
[-- Attachment #1: Type: text/plain, Size: 2495 bytes --]
On 12.03.2018 21:54, Thorsten Wilms wrote:
> ---
> #! /bin/sh
>
> if test -z "${XDG_RUNTIME_DIR}"; then
> export XDG_RUNTIME_DIR=/tmp/${UID}-runtime-dir
> if ! test -d "${XDG_RUNTIME_DIR}"; then
> mkdir "${XDG_RUNTIME_DIR}"
> chmod 0700 "${XDG_RUNTIME_DIR}"
> fi
> fi
> ---
Of course it doesn't work, since it runs in its own shell and export
takes care of children, not parents, sheesh!
I have been pasting the export/mkdir/chmod into the console, instead.
So what's the canonical way to add that to ~/.bash_profile or ~/.bashrc,
if that seems more appropriate? Or how else to meat those preconditions
for weston-launch?
Adding my user to the already existing "input" group got rid of "Error
opening device /dev/input/eventX: Permission denied".
strace revealed another error, "de-latin1-nodeadkeys" in weston.ini
couldn't be found, going with just "de" causes silence on that front.
Much of the (attached) strace output suggests things go their way, but then:
---
[18:35:32.835] warning: neither EGL_EXT_swap_buffers_with_damage or
EGL_KHR_swap_buffers_with_damage is supported. Performance could be
affected.
[18:35:32.835] EGL_KHR_surfaceless_context available
radeon: Failed to allocate a buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 2
radeon: flags : 4
radeon: Failed to allocate a buffer:
radeon: size : 65536 bytes
radeon: alignment : 4096 bytes
radeon: domains : 2
radeon: flags : 4
[18:35:32.837] EGL version: 1.5 (DRI2)
---
---
[18:35:32.931] failed to bind to /tmp/.X11-unix/X0: No such file or
directory
Failed to process Wayland connection: Connection reset by peer
failed to create display: Connection reset by peer
---
Creating and `chmod 0700`ing /tmp/.X11-unix/X0 did not lead to a
successful run.
The very end:
---
wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 539
close(5) = 0
close(3) = 0
ioctl(0, _IOC(0, 0x4b, 0x51, 0), 0) = -1 ENOTTY (Inappropriate ioctl
for device)
ioctl(0, KDSKBMODE, 0x3) = 0
ioctl(0, KDSETMODE, 0) = 0
ioctl(4, DRM_IOCTL_DROP_MASTER, 0) = -1 EACCES (Permission denied)
ioctl(0, VT_SETMODE, 0x7ffd806628f0) = 0
exit_group(1) = ?
+++ exited with 1 +++
---
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
[-- Attachment #2: strace_weston-launch_4.txt.bz2 --]
[-- Type: application/x-bzip, Size: 7042 bytes --]
next prev parent reply other threads:[~2018-03-13 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 12:59 Wayland setup Thorsten Wilms
2018-03-05 13:47 ` Andreas Enge
2018-03-07 13:06 ` Oleg Pykhalov
2018-03-11 17:07 ` Thorsten Wilms
2018-03-12 17:19 ` Thorsten Wilms
2018-03-12 19:05 ` Gábor Boskovits
2018-03-12 20:54 ` Thorsten Wilms
2018-03-13 19:50 ` Thorsten Wilms [this message]
2018-03-13 21:22 ` Gábor Boskovits
2018-03-14 21:10 ` Thorsten Wilms
2018-03-15 1:08 ` Marius Bakke
2018-03-15 10:29 ` Thorsten Wilms
2018-03-15 10:06 ` Thorsten Wilms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8414388-4626-0f0a-8003-ccd42639dbfa@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).