New answers tagged

2

The messages show that you have a conflict between a 32-bit package and a 64-bit package. That could have happened as a result of mixing repositories from different places (there's not enough information in the question to clarify this). However, you may be able to remove the 32-bit package without disturbing anything that you actually need. Rather than ...


0

Possible workaround would be to rename that directory, and force installation like this, sudo mv /usr/share/doc/libssl1.0.0 /usr/share/doc/libssl1.0.0.backup sudo apt-get -f install Or this might also fix your problem, apt-get install libssl1.0.0 libssl1.0.0:i386


1

The line deb http://ftp.uk.debian.org/debian/ jessie main contrib non-free in your /etc/apt/sources.list is a duplicate/extension of deb http://ftp.uk.debian.org/debian/ jessie main Delete the shorter line. At least in theory, there could be also more duplications with lines in /etc/apt/sources.list.d/* files.


2

I've solved the issue. At the command line I entered apt-get update and it responded there's a problem with something (sorry I should have taken notes) and then suggested to enter something at the command line. I'm under the impression that my computer went to sleep before the install was done and the actions I was told to take resolved the problem. I ...


0

It's impossible to diagnose such vague problems over the Internet. Look at the system logs for clues. If that doesn't help (but it probably will), trace the FTP server to see what it's doing — analyzing the trace is a lot more difficult than reading log messages though. It's unlikely that the problem is related to the failed upgrade, but it is possible that ...


3

The Python that ships with CentOS 7 comes in an RPM, under normal situations it is best to leave that version installed and install a different/newer version of Python in a separate location, otherwise strange issues can occur when system level applications that use Python are run (not all the time but it might be best since you are new to Linux to avoid ...


0

The Failed to parse message is probably emitted by the DBus code in systemd. Try starting or configuring dbus. If that isn't possible, try disabling systemd's LSB hook like _SYSTEMCTL_SKIP_REDIRECT=true dpkg --configure procps


0

I've got the patch for firegl_public.c working on the latest kernel: --- ../firegl_public.c 2016-06-04 23:00:11.938899758 -0400 +++ firegl_public.c 2016-06-06 21:30:45.942122307 -0400 @@ -136,6 +136,9 @@ #include <asm/processor.h> #include <asm/tlbflush.h> // for flush_tlb_page #include <asm/cpufeature.h> +#if LINUX_VERSION_CODE >= ...


0

You need to install the dnfplugin system upgrade package, From the terminal type the following command : sudo dnf install dnf-plugin-system-upgrade --enablerepo=updates-testing then download the updated packages: sudo dnf system-upgrade download --releasever=23 --allowerasing The --allowerasing will erase packages which dependencies cannot be satisfied....


0

The fedup is obsoleted since Fedora 22, the DNF system upgrade should be used to update from Fedora 22 to Fedora 23.


2

As SmokeDispenser says, it depends on exactly which distribution you're using. In most cases you'd be better off upgrading to a supported release... You can always try adding the Debian security updates to your apt setup, they probably won't break anything. First you need to determine which version of Debian your distribution is based on; then if it's ...


1

I fixed it... sudo apt-get install --reinstal fonts-cantarell


1

All the bugs referenced in /usr/share/doc/dictionaries-common/README.problems are rather old, but then so is the release of the distribution you're using. The fix_db.pl script itself is quite safe, and in any case it leaves a backup — you can run it, and then compare the contents of /var/cache/debconf/config.dat and /var/cache/debconf/config.dat-old, and /...


1

Ended up updating to the F24 beta, as it's being frozen anyways. This fixed the problem, and I'm now running on the 4.7 kernel.


0

I'd try dnf reinstall kernel or (better) dnf reinstall kernel-4.4.9-300 since it's possible that dnf has status saying that the given set of files is complete.



Top 50 recent answers are included