Installed Bodhi a number of times on a number of machines recently. Today though a new install is getting the above line when doing updates. It's the same ISO I've been using all along (and it's Bodhi 4 legacy) but I did burn it to a new usb - so that's the only difference (plus a different machine of course).

Any idea what's going on - if I do sudo apt-get update or upgrade, get Error: Timeout was reached - at the end. If I use eepdater it just tells me I'm up to date.

Yeah I would like to know the fix for this as well, I just reinstalled 4.5 because 5.0 does not work on the same device and started to see this error when upgrading my apps.

sudo /usr/lib/packagekit/packagekitd --verbose
01:23:09 PackageKit dlopening '/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so'
Failed to load the backend: opening module aptcc failed : /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so: symbol _ZN9pkgSystem9LockInnerEv, version APTPKG_5.0 not defined in file libapt-pkg.so.5.0 with link time reference

I found a really old post on some blog but the resolution does not work

sudo apt-get install libapt-pkg4.12=1.1.1bodhi1 apt=1.1.1bodhi1 apt-transport-https=1.1.1bodhi1 apt-utils=1.1.1bodhi1

206 views and no one knows the solution to this?

it isn't a fix, but i recently installed lnav to view system log files. since i am not well versed in that language at all, it is handy that the error messages are red. i believe the default is to show syslog, but it can be used to look at others if needed. maybe seeing some of those error messages will provide further clues as to what is going on?

@cordx Well that's a neat app!! However, it shows the same error only it was easier to find and see than what I pasted above, that took some searching to find.

1 members found this post helpful.

@rfanch3r sorry to hear it wasn't more help. i stumbled into lnav when my moksha started throwing weird errors a few months ago. in the end it was my hdd that was dying so lnav wasn't a whole lot of help with mine either.

i was playing around with synaptic package manager earlier and your question got me wondering if maybe some of the packages you have listed (or even apt itself) might show up with problems that it could fix? for example, when i right-click on apt itself, one of the suggestions at the bottom is to install aptitude. never used it myself, but i thought i read somewhere (just found a link) that it was a front end for apt:

https://help.ubuntu.com/lts/serverguide/aptitude.html

of course a working frontend to a backend that refuses to load may be a moot point. it might be able (though i think it would be easier to see in synaptic) to show you broken or misconfigured packages.

Well it only showed up after I did an apt update/upgrade

i noticed one of the packages in my update this week was for apt. any chance you have a backup you can go back to and see if that helps?

I don't think there is a way to roll an app back via apt. It would be nice if the dev team could make some comment regarding this. Is this a known issue? Are you ignoring this because its now legacy?

This is not a known issue and I haven't been ignoring this because it is legacy or 4.5 or any other reason. I can't duplicate it and am unsure what is wrong. All I could do is google the error you are getting and repeat what I read on the internet. I don't like doing that ...

1 members found this post helpful.

i was hoping maybe you had an offline backup that you could revert to. in case this is still an issue, i found this article that talks about using the --reinstall flag for apt. not sure if that will work with a broken apt backend.

https://debian-administration.org/ar..._fix_problems.

if that doesn't work, there is another suggestion on that page about using dpkg to purge the install and then it can also be used to clean install since i am assuming apt will not be functional. i found my most recent installed packages in /var/cache/apt/archives in their original .deb files. if it were me, i would copy those to a different location to make sure they aren't removed by a purge (not sure exactly how that all works. i would think they stay before autoremove, but just to be safe) if you do in fact decide to go the purge route. /var/log/apt/history.log.1.gz was where my log for that upgrade was. after gunzip i was able to see all of the packages that were in the /archives directory.

this page talks about how to install a .deb with dpkg then fix dependencies (if it works then) with apt:

https://unix.stackexchange.com/quest...kg-i-or-by-apt

I don't know if this is related or not. I've been using eepDater for all my updates, and it's been sort of freezing. I say sort of, because the Cylon eye is still sweeping back and forth, but progress has stopped. However, when you click the info button on eepDater, there is a message after the row of dashes which normally signifies that the update has finished:

-----------------------------
Error: CRI:eina_log ../src/bin/win.c:1762 win_new() unknown log domain -1.
original message level for: WRN

In the Terminology window, it often seems on a Processing triggers line, such as this:
Processing triggers for libc-bin (2.27-3ubuntu1) ...

1 members found this post helpful.

I have seen that but assumed Moshka was going to sleep during the update, since after 'clicking around' a bit, the big green check mark would eventually appear in the eepDater window.

1 members found this post helpful.

Still getting it on a new install from my original dvd burned with bodhi 4. Just ignoring it for now!