Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] aa-notify needs python dbus module
Date: Tue, 20 Jul 2021 16:40:30 +0200	[thread overview]
Message-ID: <20210720144030.QikRISEKiraHOo6RxZARkpHM6esYFUZEO0J5sM88hC4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32052@inbox.vuxu.org>

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

Closed issue by AgnishRoy on void-packages repository

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

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.12.17_1 x86_64 GenuineIntel uptodate hold rrFFF
* affected package(s):   apparmor-3.0.1_5
* related package(s): python3-notify2-0.3.1_2

### Expected behaviour
aa-notify should run as normal user (i.e. without sudo) with desired flags.

### Actual behaviour
aa-notify emits an error: NoModuleFoundError: No module named 'dbus'

### Steps to reproduce the behaviour
1. Install apparmor userspace tools. Enable apparmor.
2. Install and enable audit framework.
3. Add your _user_ to whatever group audit.log uses (found and set in `/etc/audit/auditd.conf`).
4. Reboot
5. Verify that both apparmor and audit framework are up and running.
6. Launch your desktop
7. Try to run aa-notify tailing /var/log/audit.log
8. Notice the error.

### My notes
- I solved it by installing `python3-dbus` package which would be needed by python3-notify2
- To permanently solve it,  one may add python3-dbus as a runtime dependency of apparmor in the template.


      reply	other threads:[~2021-07-20 14:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20  5:58 [ISSUE] " AgnishRoy
2021-07-20 14:40 ` ericonr [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=20210720144030.QikRISEKiraHOo6RxZARkpHM6esYFUZEO0J5sM88hC4@z \
    --to=ericonr@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).