Github messages for voidlinux
 help / color / mirror / Atom feed
From: harrisonthorne <harrisonthorne@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Can't start Plasma
Date: Sun, 04 Apr 2021 03:08:10 +0200	[thread overview]
Message-ID: <20210404010810.xoVV0IXDAVvaOZy2-haAHzyuoc4H4VctelOYjok6Bq4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29231@inbox.vuxu.org>

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

Closed issue by harrisonthorne on void-packages repository

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

Description:
### System

* xuname: `Void 5.10.19_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFFFFFFFFFF`
* package: `kde5-5.21.0_1`

### Expected behavior

Plasma should start, display, and be usable.

### Actual behavior

`startplasma-wayland` command fails with:

```
not a reply org.freedesktop.locale1 QDBusMessage(type=Error, service="org.freedesktop.DBus", error name="org.freedesktop.DBus.Error.ServiceUnknown", error message="The name org.freedesktop.locale1 was not provided by any .service files", signature="s", contents=("The name org.freedesktop.locale1 was not provided by any .service files") )
startplasmacompositor: Could not start D-Bus. Can you call qdbus?
```

Trying to execute `qdbus` results in:

```
qdbus: could not find a Qt installation of ''
```

### Steps to reproduce the behavior

From a display manager, try launching the "Plasma (Wayland)" session. Or, run `startplasma-wayland` from a TTY. The TTY method was used to obtain the output above.

Note: I have `dbus-elogind` installed and the `dbus` service is enabled.

      parent reply	other threads:[~2021-04-04  1:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04 21:23 [ISSUE] " harrisonthorne
2021-04-04  1:08 ` harrisonthorne
2021-04-04  1:08 ` harrisonthorne [this message]

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=20210404010810.xoVV0IXDAVvaOZy2-haAHzyuoc4H4VctelOYjok6Bq4@z \
    --to=harrisonthorne@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).