archive mirror
 help / color / mirror / Atom feed
From: Oliver Rath <>
To: LVM general discussion and development <>
Subject: [linux-lvm] lvmdbusd failure(s) at ubuntu
Date: Mon, 11 Dec 2017 02:53:35 +0100	[thread overview]
Message-ID: <> (raw)

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

Hi list,

Im playing around with the dbus-daemon, which shows me some strange

  * lvmdbusd doesnt run with the message
    # lvmdbusd
    Traceback (most recent call last):
      File "/sbin/lvmdbusd", line 13, in <module>
        from lvmdbusd import main
    ModuleNotFoundError: No module named 'lvmdbusd'
    *but* the module seems to be installed:
    # find /usr/lib/ -iname "lvmdbusd"

    Btw, lvmdbusd seems not to be installed for python2
  * lvmdbusd is a python-script, but the installer says "python is
    deprecated, use dbus instead". Can I use the dbus-interface (Im
    working on some examples in Rust for this) without the lvmdbusd?

Is lvm via dbus possibly out of date and not longer useable?

My system is ubuntu 17.10 with lvm2-git installed:

# lvdisplay --version
  LVM version:     2.02.177(2)-git (2017-11-03)
  Library version: 1.02.146-git (2017-11-03)
  Driver version:  4.37.0
  Configuration:   ./configure --enable-lvmetad --enable-lvmpolld
--enable-dmfilemapd --enable-cmdlib --enable-applib
--enable-dbus-service --enable-notify-dbus --enable-python2_bindings



[-- Attachment #2: Type: text/html, Size: 1730 bytes --]

             reply	other threads:[~2017-12-11  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11  1:53 Oliver Rath [this message]
2017-12-11 12:24 ` [linux-lvm] lvmdbusd failure(s) at ubuntu Marian Csontos
2017-12-13 12:52 ` [linux-lvm] SOLVED [was: lvmdbusd failure(s) at ubuntu] Oliver Rath

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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