From: Tcll <Tcll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: XFCE PolicyKit Agent error
Date: Tue, 31 Mar 2020 18:18:50 +0200 [thread overview]
Message-ID: <20200331161850.Gb-39vSPwsYrCCudsFEkrP068cctYzOd89yRpMpwW5M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20245@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
New comment by Tcll on void-packages repository
https://github.com/void-linux/void-packages/issues/20245#issuecomment-606729647
Comment:
hopefully my issue caused an unnotified fix (I've been waiting for a response on the matter)
I'll try again when I'm able to test, as I'm currently using the machine I tested with for other things atm.
(the machine I'm installing to can't boot USB drives, and I'm having an issue burning CDs with my primary as they can't be read)
and regarding that elogind bit, I actually tried running elogind as a runit service and was greeted with repeating errors in the tty...
I found out it doesn't work as a runit service, but as a dbus service, and that's the issue I'm reporting here.
and yeah dbus-elogind force-installs dbus
found that out when going through some reddit issues other people were having:
https://www.reddit.com/r/voidlinux/comments/cm7pt1/exercise_caution_ongoing_issues_with_polkit/
I don't have ConsoleKit2, so I didn't worry about that option
hopefully the issue is fixed now :)
next prev parent reply other threads:[~2020-03-31 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 15:52 [ISSUE] " Tcll
2020-03-31 12:52 ` furryfixer
2020-03-31 13:22 ` furryfixer
2020-03-31 16:18 ` Tcll [this message]
2020-03-31 16:21 ` xtraeme
2020-07-06 14:53 ` Tcll
2020-07-06 17:58 ` Tcll
2020-07-06 20:35 ` Tcll
2020-07-06 20:38 ` Tcll
2020-08-15 23:53 ` Piraty
2020-08-15 23:53 ` [ISSUE] [CLOSED] " Piraty
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=20200331161850.Gb-39vSPwsYrCCudsFEkrP068cctYzOd89yRpMpwW5M@z \
--to=tcll@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).