From: superiums <superiums@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: GLIB problems
Date: Sat, 22 Oct 2022 06:32:21 +0200 [thread overview]
Message-ID: <20221022043221.TXBbzVlWvUitf_TCqmLlgDBsvdkXTBSQf93mPK7VQ-I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39752@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 768 bytes --]
New comment by superiums on void-packages repository
https://github.com/void-linux/void-packages/issues/39752#issuecomment-1287612891
Comment:
gvfs problem was solved by config greetd:
/etc/greetd/config.toml
```
command = "tuigreet -t --remember --remember-user-session --asterisks -g 'BE COUCIOUSNESS' --cmd 'dbus-launch --exit-with-session wayfire' "
```
instead of let greetd use the sway/wayfire session file.
so , gvfs fails due to dbus communication.
by the way ,
``` firejail firefox ``` fails also due to this problem.
hope this helpful to others who occurs this problem.
- parole still not solved.
- lxdm still fails , in another pc, fresh installed system. report `Authorization required, but no authorization protocol specified`
next prev parent reply other threads:[~2022-10-22 4:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 5:04 [ISSUE] " superiums
2022-10-06 6:06 ` sgn
2022-10-06 6:07 ` sgn
2022-10-06 8:11 ` oreo639
2022-10-06 8:12 ` oreo639
2022-10-06 8:12 ` sgn
2022-10-06 8:12 ` oreo639
2022-10-06 8:13 ` oreo639
2022-10-06 8:13 ` oreo639
2022-10-06 8:14 ` oreo639
2022-10-06 8:15 ` oreo639
2022-10-06 8:15 ` oreo639
2022-10-06 8:17 ` oreo639
2022-10-06 8:22 ` oreo639
2022-10-06 8:22 ` oreo639
2022-10-06 9:31 ` paper42
2022-10-06 11:56 ` superiums
2022-10-08 12:09 ` superiums
2022-10-21 10:17 ` superiums
2022-10-22 4:32 ` superiums [this message]
2022-10-22 4:35 ` superiums
2022-12-13 7:11 ` sgn
2022-12-13 7:12 ` sgn
2022-12-13 7:14 ` sgn
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=20221022043221.TXBbzVlWvUitf_TCqmLlgDBsvdkXTBSQf93mPK7VQ-I@z \
--to=superiums@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).