Member Avatar for Slavi

Hey guys,
not sure how but my conky manager pretty much just dissapeared earlier today and I had to download the package and reinstall it again. However upon installation some dependancies were not met ..
//I had apparently fixed this issue in the passed but I can't find nor remember how I did it ..
This is the issue:

The following packages have unmet dependencies:
 conky-manager : Depends: libglib2.0-0 (>= 2.35.9) but 2.33.12+really2.32.4-5 is installed

I just downloaded the latest version of libglib2 from Click Here and tried to install it but I get error that

dpkg: regarding libglib2.0-0_2.42.1-1_amd64.deb containing libglib2.0-0:amd64:
 libglib2.0-0:amd64 breaks glib-networking (<< 2.33.12)
  glib-networking:amd64 (version 2.32.3-1) is present and installed.

dpkg: error processing libglib2.0-0_2.42.1-1_amd64.deb (--install):
 installing libglib2.0-0:amd64 would break glib-networking:amd64, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 libglib2.0-0_2.42.1-1_amd64.deb

so I was wondering basically what to do to fix it ..

Also I ran conky manager and I have a widget running in the background but the package manager just shows that there are unmet dependencies and I can't install new packages through apt-get, returns an error that there are broken dependencies and to try apt-get install -f, however that only gives me the option to remove conky manager

OS - Kali Linux

  • 2 Contributors
  • 1 Reply
  • 757 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by craftsmanofmich

Dani AI

Generated

— short, practical summary for anyone who finds this thread later (and for who reported the same problem).

This error almost always means the Conky Manager you installed was built against a newer GLib than the one in your Kali installation. Manually installing a libglib binary from Debian sid/testing will quickly create version glitches (other packages that expect older GLib — glib-networking, GNOME bits, etc. — will conflict), so the real issue is mixed package sources rather than a single broken .deb. Kali uses a curated rolling set that is intended to be consistent; mixing unsupported Debian archives (or sid) can “bork” the package graph. (slideshare.net)

Immediate checks (do these before trying to force anything):

  • See which versions are installed and which repository is offering candidates.
  • Confirm what repos are enabled (look for Debian/sid entries).

Use these two quick inspections:

apt policy libglib2.0-0 glib-networking conky-manager
grep -h '^deb' /etc/apt/sources.list /etc/apt/sources.list.d/*

That will show whether conky-manager or libglib was pulled from a non-Kali source. (ostechnix.com)

Safe resolution paths (ranked by safety):

  • Remove the foreign .deb and install a Conky Manager package built for your Kali release (or install the distro-provided Conky packages). This avoids upgrading core libraries.
  • If you need a newer Conky Manager feature, rebuild or backport Conky Manager against the Kali libraries (create a local .deb from source in a Kali chroot). This prevents system-wide ABI changes. (debian.org)
  • If you forcibly upgrade libglib system-wide, be prepared that many dependent packages will need upgrades too — that’s what causes the cascading breakage seen in similar cases. If that path is chosen, do it only by enabling a consistent archive (not random .debs) or in a disposable chroot/container. (unix.stackexchange.com)

If a previous post by already fixed this locally, the above checklist explains why: avoid mixing sid binaries and prefer rebuilding/backporting or installing the distro-matching package.

Member Avatar for craftsmanofmich

how did you fix this? I have the same problem...

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.