Devuan bug report logs - #580
libguestfs-tools crashed because of unsolved dependcies to libsystemd.so on Devuan

Full log

Message #20 received at 580@bugs.devuan.org (full text, mbox, reply):

Received: (at 580) by bugs.devuan.org; 14 May 2021 13:50:03 +0000
Return-Path: <mark@hindley.org.uk>
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 14 May 2021 13:50:03 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id 921E3F608CD
	for <580@bugs.devuan.org>; Fri, 14 May 2021 15:38:33 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <mark@hindley.org.uk>)
	id 1lhY1O-0001Ac-Jg; Fri, 14 May 2021 14:38:30 +0100
Received: (nullmailer pid 17308 invoked by uid 1000);
	Fri, 14 May 2021 13:38:29 -0000
Date: Fri, 14 May 2021 14:38:29 +0100
From: Mark Hindley <mark@hindley.org.uk>
To: Joerg Schiermeier <devuan-bug@schiermeier-it.de>
Cc: 580@bugs.devuan.org
Subject: Re: bug#580: libguestfs-tools crashed because of unsolved dependcies
 to libsystemd.so on Devuan
Message-ID: <YJ59VQFRq4gjozcG@hindley.org.uk>
References: <162090197558.17855.12706389165560557041.reportbug@Archimedes.fritz.box>
 <YJ2WLvlCITkdcv8K@hindley.org.uk>
 <108933829.20210514140213@schiermeier-it.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <108933829.20210514140213@schiermeier-it.de>
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Joerg,

Sorry, there is a typo in what I wrote

On Fri, May 14, 2021 at 02:02:13PM +0200, Joerg Schiermeier wrote:
> Hello Mark,
> 
> on Thursday, May 13th, 2021 at 23:12 o'clock you wrote:
> 
> MH> You should have either one of
> 
> MH>  /usr/lib/x86_64-linux-gnu/libsytemd.so.0
> $ ls -l /usr/lib/x86_64-linux-gnu/libsytemd.so.0
> ls: cannot access '/usr/lib/x86_64-linux-gnu/libsytemd.so.0': No such file or directory
> 
> MH>  /lib/x86_64-linux-gnu/libsytemd.so.0
> $ ls -l /lib/x86_64-linux-gnu/libsytemd.so.0
> ls: cannot access '/lib/x86_64-linux-gnu/libsytemd.so.0': No such file or directory
> 
> MH> Which is present?

libsystemd.so.0 rather than libsytemd.so.0. Apologies,

> # dpkg -l '*' | grep -i libelogind0
> ii  libelogind0:amd64                                                         241.4-2                                                 amd64        user, seat and session management library
> ii  libelogind0:i386                                                          241.4-2                                                 i386         user, seat and session management library
> 
> Aha, OK.
> 
> So:
> # dpkg -L libelogind0:amd64
> /.
> /usr
> /usr/lib
> /usr/lib/x86_64-linux-gnu
> /usr/lib/x86_64-linux-gnu/libelogind.so.0.25.0
> /usr/share
> /usr/share/doc
> /usr/share/doc/libelogind0
> /usr/share/doc/libelogind0/README.Debian
> /usr/share/doc/libelogind0/changelog.Debian.gz
> /usr/share/doc/libelogind0/copyright
> /usr/lib/x86_64-linux-gnu/libelogind.so.0
> /usr/lib/x86_64-linux-gnu/libsystemd.so.0
>
> and:
> 
> # ls -l /usr/lib/x86_64-linux-gnu/libelogind.so.0
> lrwxrwxrwx. 1 root root 20 Jan  1  2020 /usr/lib/x86_64-linux-gnu/libelogind.so.0 -> libelogind.so.0.25.0
> 
> # ls -l /usr/lib/x86_64-linux-gnu/libsystemd.so.0
> lrwxrwxrwx. 1 root root 15 Jan  1  2020 /usr/lib/x86_64-linux-gnu/libsystemd.so.0 -> libelogind.so.0
> 
> 
> # ls -l /usr/lib/x86_64-linux-gnu/libelogind.so.0.25.0
> -rw-r--r--. 1 root root 830880 Jan  1  2020 /usr/lib/x86_64-linux-gnu/libelogind.so.0.25.0

Which looks correct. I don't understand why guestfsd doesn't find and use the
libsystemd.so.0 symlink.

What does ldd /usr/sbin/guestfsd show?

Mark

Send a report that this bug log contains spam.