From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] sddm and Consolekit
Date: Sun, 12 Jan 2020 14:13:40 +0100 [thread overview]
Message-ID: <20200112131340.W82iu9tBLWcgFnN71ibD0cQc0dB6vqW21W02CZAx1bk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-1742@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
Closed issue by Hoshpak on void-packages repository
https://github.com/void-linux/void-packages/issues/1742
Description:
continuation of https://github.com/voidlinux/void-packages/issues/8048
@the-maldridge since you fell victim to a netsplit on freenode before I could reply, here are my current findings:
sddm-0.18.0 still doesn't work with ConsoleKit2 out of the box. It correctly detects the ConsoleKit interface but then the process stalls until it is terminated without any error messages, the DM is not launched.
I had more luck after trying to compile sddm with the changes proposed in https://github.com/sddm/sddm/pull/923 . The patched sddm binary sucessfully launches with ConsoleKit2 running and elogind absent. The shutdown and reboot buttons in sddm work and I can launch a lxqt session from sddm. I don't know if there's any other functionality to test for ConsoleKit. With these patches, sddm-0.18.0 works more or less the same way 0.15.0 did before.
prev parent reply other threads:[~2020-01-12 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-1742@inbox.vuxu.org>
2019-09-06 6:59 ` voidlinux-github
2019-10-13 3:08 ` voidlinux-github
2019-10-13 4:47 ` voidlinux-github
2019-10-13 6:46 ` voidlinux-github
2019-11-08 5:39 ` voidlinux-github
2019-11-10 10:04 ` voidlinux-github
2020-01-12 13:13 ` voidlinux-github
2020-01-12 13:13 ` voidlinux-github [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=20200112131340.W82iu9tBLWcgFnN71ibD0cQc0dB6vqW21W02CZAx1bk@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).