Github messages for voidlinux
 help / color / mirror / Atom feed
From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] weston fails without weston-launch
Date: Mon, 17 Feb 2020 05:56:28 +0100	[thread overview]
Message-ID: <20200217045628.ByVQlQLG-82XCQeLhDsH-AEDMpQowq_gugq3DMWqdrI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12754@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

Closed issue by kanyck on void-packages repository

https://github.com/void-linux/void-packages/issues/12754

Description:
### System
 Void 4.19.56_1 x86_64 GenuineIntel uptodate rF
* package:  
weston-6.0.1_1

### Expected behavior
Weston runs on `weston` command

### Actual behavior
```
fatal: drm backend should be run using weston-launch binary. or your system should provide the logind D-bus API.
fatal: failed to create compositor backend.
```
### Steps to reproduce the behavior
Issue` weston` command. Actually I'm trying to make [this](https://github.com/ehough/docker-kodi) work, so weston-launch won't help (which is working fine, BTW).

This may be relevant:
https://gitlab.freedesktop.org/wayland/weston/issues/204



  parent reply	other threads:[~2020-02-17  4:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-30 10:10 [ISSUE] " voidlinux-github
2019-06-30 11:25 ` voidlinux-github
2019-06-30 12:16 ` voidlinux-github
2019-06-30 12:16 ` voidlinux-github
2019-06-30 12:37 ` voidlinux-github
2019-06-30 12:39 ` voidlinux-github
2019-06-30 19:50 ` voidlinux-github
2019-07-03 17:21 ` voidlinux-github
2020-02-17  4:56 ` xtraeme
2020-02-17  4:56 ` xtraeme [this message]
2020-02-17  8:05 ` mviereck
2020-02-17  8:06 ` xtraeme
2020-02-17  8:09 ` mviereck
2020-02-17  8:11 ` xtraeme

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200217045628.ByVQlQLG-82XCQeLhDsH-AEDMpQowq_gugq3DMWqdrI@z \
    --to=xtraeme@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).