Hi,
Trying to use the System Updater, it always just stops after downloading and unpacking some packages but before it finishes the process, apparently. I see this error message:

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

I saw another poster here with the same problem. Someone told him to just use apt-get in terminology. OK, I can do that, but the thing is, all the packages I tried updating with System Updater, were they updated or not?
They don't show up in System Updater anymore. But, the process didn't seem to have finished. And I didn't write down their names, so there's no way I can try to update then again with terminology. What would be the state of those packages? Will they cause malfunctioning of bodhi or the apps?

Thanks a lot

Can you please run the following from the command line and paste the output here (within CODE tags - see https://www.linuxquestions.org/quest...og.php?b=36313):

This is the result:

Thanks. I'm surprised not to see the Ubuntu security repo in there though. Perhaps that's a Bodhi thing.

Anyway, now let's bring your system up to date:

Thanks for using the CODE tags by the way - much appreciated.

Thanks

Is the issue now resolved?

Well, I did what you told me, and during the updating a message showed up in the terminal window, something about the Grub file being locally modified, and would it keep that or update it with the file from the package manager. I chose the later.

Now, everytime I try to suspend or switch off or whatever, a window pops up with this message:

"Moksha has had an error while writing its config file. The file is not writable. Perhaps the disk is read-only or you lost permission to your files. The file where the error ocurred was "home/mydrive/.e/e/config/profile.cfg.temp". The file has been deleted to avoid corrupt data."

And it cannot suspend itself or anything. I'm seeing I'll just have to re-install bodhi 5.0.0...

Ok, let us know how it goes.

Just as an aside, I always go for the status quo in any Grub update choices (i.e. I choose to keep the local file) and it has worked for me so far.

1 members found this post helpful.

you should have kept the old one.... ver pick the new one from my experiences and what others who know know.

also always update and dist-upgrade using terminal. there is a bug from ubuntu/debian or enlightenment - been there since 4.5


run sudo apt- get



then run sudo apt-get dist-upgrade hit Y for yes for using more hd space. all will work.

when asked to use the new boot or old always keep what you have that works.

I just rebooted the computer and everything seems to be fine.

Cool. Let us know if that situation changes.

If you want to, you can mark this thread as "Solved" (see "Thread Tools" at the top of the thread).