From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] connman-1.37 should install connman-dbus.conf and connman-polkit.conf
Date: Sat, 01 Feb 2020 17:20:20 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18713@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
New issue by basiliscos on void-packages repository
https://github.com/void-linux/void-packages/issues/18713
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.16_1 x86_64 GenuineIntel notuptodate rrrmFFFFF
* package:
connman-1.37_3
### Expected behavior
no annoying dbus messages like
```
2020-02-01T18:59:33.746456+03:00 localhost dbus-daemon\[773\]: \[system\] Rejected send message, 3 matched rules; type="method\_call", sender=":1.29" (uid=1000 pid=1597 comm="telegram-desktop ") interface="net.connman.Manager" member="GetTechnologies" error name="(unset)" requested\_reply="0" destination="net.connman" (uid=0 pid=888 comm="connmand -n ")
```
the tools like `connman-gtk`, `cmst` should work without root priveledges
### Actual behavior
userland network configuration tools not work from user
### Steps to reproduce the behavior
just install connman and launch `connman-gtk`
I have found the advice here https://stackoverflow.com/questions/26280616/connman-running-from-within-the-source-code-repository
when I just copied `connman-dbus.conf` and `connman-polkit.conf` into `/etc/dbus-1/system.d/` everything went fine.
next reply other threads:[~2020-02-01 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 16:20 voidlinux-github [this message]
2020-02-03 11:15 ` voidlinux-github
2020-02-03 11:29 ` voidlinux-github
2020-04-19 15:12 ` Val6789
2020-04-19 15:13 ` Val6789
2020-09-02 16:14 ` kedodrill
2021-03-21 7:43 ` apvodney
2022-04-15 2:13 ` github-actions
2022-04-29 2:13 ` [ISSUE] [CLOSED] " github-actions
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18713@inbox.vuxu.org \
--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).