[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, 2019-08-29 at 17:31 +0700, Theppitak Karoonboonyanan wrote:
> Package: xfwm4
> Version: 4.14.0-1
> Severity: serious
> Justification: Policy 3.5
> 
> Dear Maintainer,
> 
> xfwm4 fails to start:
> 
> $ xfwm4
> xfwm4: error while loading shared libraries: libxfconf-0.so.2: cannot
> open shared object file: No such file or directory
> $ ldd /usr/bin/xfwm4 | grep libxfconf
>     libxfconf-0.so.3 => /usr/lib/x86_64-linux-gnu/libxfconf-0.so.3
> (0x00007f74ba2f5000)
>     libxfconf-0.so.2 => not found
> $
> 
> Fortunately, installing libxfconf-0-2 does make it load successfully,
> but it's not listed as a dependency.
> 
> Actually, this bug can be grave (rendering the package unusable)
> when libxfconf-0-2 is faded out.

Hi,

xfwm4 4.14.0-1 (in sid and unstable) is only linked against libxfconf-0.3, not
libxfconf-0.2, so it's definitely not where the problem lies. Xfce 4.14 just
migrated to testing so that could explain your issue (which is likely
transient), but it shouldn't have happened anyway.

Can you install the pax-utils package (and only that package, please try not
to upgrade anything else) and give us the output of lddtree (so we have an
idea from where exactly the link comes from). My guess would be libxfce4ui, so
if you could give us the output of dpkg -l |grep libxfce4ui in the same reply
it'd be nice.

Regards,
- -- 
Yves-Alexis
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl1nthwACgkQ3rYcyPpX
RFtJdggAwHZABAc+x8sq0L8u6uihUu74OJZkJkqZMNbImDBrpc/e8hrvDFwJBOrN
uU/o83cFnsG+gUzyZCGJEuID8QbY+GsTmHCPzTGBScK2sSV7igpJgkBDH7JR7GQd
SOGloR8ui4tkWXAxYHVs640FGMmnc6wDmuLfewWtF85unSUJKY/hILEO3S4Ew32o
g5E2fsyPeJ3Rxbv01IQmDg3OwMW/MkdWOOaCZxWSbfTD7BGHayFXVdZacGJrSMVW
ao3qC6XoGHjR9rc0thHRTNORcEidcnHP8fjWa+AVnCDPv2WX2EomiCPTqy1pBoRk
eE47hTHBrZEjujPBwWJJZFvJxfRhZg==
=xCEb
-----END PGP SIGNATURE-----


Reply to: