Github messages for voidlinux
 help / color / mirror / Atom feed
* [ISSUE] aa-notify needs python dbus module
@ 2021-07-20  5:58 AgnishRoy
  2021-07-20 14:40 ` [ISSUE] [CLOSED] " ericonr
  0 siblings, 1 reply; 2+ messages in thread
From: AgnishRoy @ 2021-07-20  5:58 UTC (permalink / raw)
  To: ml

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

New 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
  *output of ``xuname`` (part of xtools)*
* 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.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ISSUE] [CLOSED] aa-notify needs python dbus module
  2021-07-20  5:58 [ISSUE] aa-notify needs python dbus module AgnishRoy
@ 2021-07-20 14:40 ` ericonr
  0 siblings, 0 replies; 2+ messages in thread
From: ericonr @ 2021-07-20 14:40 UTC (permalink / raw)
  To: ml

[-- 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.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2021-07-20 14:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-20  5:58 [ISSUE] aa-notify needs python dbus module AgnishRoy
2021-07-20 14:40 ` [ISSUE] [CLOSED] " ericonr

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).