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

Bug#936035: marked as done (xfwm4: fails to load due to missing libxfconf-0.so.2)

Your message dated Thu, 29 Aug 2019 19:08:11 +0200
with message-id <18ccdd14c3a84d8ce121067c7f1610c4b6271467.camel@debian.org>
and subject line Re: Bug#936035: xfwm4: fails to load due to missing libxfconf-0.so.2
has caused the Debian Bug report #936035,
regarding xfwm4: fails to load due to missing libxfconf-0.so.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

936035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936035
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
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
    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.

Theppitak Karoonboonyanan

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500,
'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=th_TH.utf8, LC_CTYPE=th_TH.utf8 (charmap=UTF-8),
LANGUAGE=th_TH.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfwm4 depends on:
ii  libc6                     2.28-10
ii  libcairo2                 1.16.0-4
ii  libepoxy0                 1.5.3-0.1
ii  libgdk-pixbuf2.0-0        2.38.1+dfsg-1
ii  libglib2.0-0              2.60.6-2
ii  libgtk-3-0                3.24.10-1
ii  libpango-1.0-0            1.42.4-7
ii  libpangocairo-1.0-0       1.42.4-7
ii  libstartup-notification0  0.12-6
ii  libwnck-3-0               3.32.0-1
ii  libx11-6                  2:1.6.7-1
ii  libxcomposite1            1:0.4.4-2
ii  libxdamage1               1:1.1.5-1
ii  libxext6                  2:1.3.3-1+b2
ii  libxfce4ui-2-0            4.14.1-1+b1
ii  libxfce4util7             4.14.0-1
ii  libxfconf-0-3             4.14.1-1
ii  libxfixes3                1:5.0.3-1
ii  libxi6                    2:1.7.9-1
ii  libxinerama1              2:1.1.4-2
ii  libxpresent1              1.0.0-2+b10
ii  libxrandr2                2:1.5.1-1
ii  libxrender1               1:0.9.10-1

Versions of packages xfwm4 recommends:
ii  librsvg2-common  2.44.14-1

Versions of packages xfwm4 suggests:
ii  xfce4  4.14

-- no debconf information

--- End Message ---
--- Begin Message ---
Hash: SHA256

On Thu, 2019-08-29 at 23:37 +0700, Theppitak Karoonboonyanan wrote:
> Thanks to your test command suggestion, I find my report was a false alarm.
> And I'm terribly sorry for that.
> The one that drags libxfconf-0.so.2 in is libxfce4kbd-private-3.so.0,
> which appears to be from /usr/local/lib, not from an installed deb!
> I can't recall when I built and installed the local version.
> The file date says some time in 2018.

That was my gut feeling as well :) Thanks for the confirmation, I'm closing
the bug.

- -- 


--- End Message ---

Reply to: