on both my bodhi 5.0 (appcenter and legacy) installs, at the end of the update process through eepdater the terminal session (automatically launched in 5, but i thought i had to do so in 4.5) fails to close or indicate that it is finished. after i notice it hasn't moved on for about 5 minutes or so, i usually just x out of the window. i have been wary of ctrl c because i didn't want to interrupt anything.

before i x out, i have checked the eepdater window (after having previously clicked on details at the bottom) and it shows the following:

https://imgur.com/a/8N3AjMP

immediately after x-out, the eepdater window continues through the process of listing get and fetch then finishes up and says everything is up to date. i have run update && upgrade after just to make sure all went well and it seems to have done so.

not a huge issue in the least, but could see where it might be confusing and just wanted to see if there might be some kind of fix possible

this was also mentioned by @bobl01 (13th post down) and @RonCam in another thread and i thought i would start a new one because it was buried:

https://www.linuxquestions.org/quest...ed-4175641260/

been a problem for a long time - use terminal update and dist upgrade. do not remeber the reason why but since i use terminal no issues.

1 members found this post helpful.

terminal also works just fine for me. i don't recall this happening in 4.5 (just updated to 5 a couple months ago) is part of the reason i brought it up. that and because it came up in another thread. if i recall correctly, in 4.5 the terminal session didn't automatically launch. i would often click the details button to watch what happened, but that one always closed itself out (or at least indicated that the install was finished? i don't remember exactly). i wanted to see if any of the developers might have a possible solve.

happened in 4.5. i had a thread on it charles and waiter and sef and ylee added to it. no long lost.

been using bodhi since 4? maybe a late version of 3.

1 members found this post helpful.

i enjoyed 4.5 (i think i started with 4.4?), but my hdd died so i decided to try 5.0. i like it very much as well. little quirks here and there seem to be par for the course no matter the distro

i had a look through some of my files and i did not find the reason but i guess it was an ubuntu/debian thing or else an enlightenment thing. sorry i cannot find it. thought i would have had the whole thread copies somewhere.

1 members found this post helpful.

not a worry in the least. like i said in my original post, once i understood what was happening i wasn't particularly concerned. just wanted to make a note of it. i appreciate your looking though

That's one of the useless (for me) apps I purged right after install. I have one PC with 10GB hard drive so removed everything I never use on it, then decided to do the same to my others once no problems observed.

1 members found this post helpful.

the thinking behind this approach is starting to make more sense to me now. as a fairly new linux user with only about 18 months under my belt, i had been wondering (like another member posted in a different thread) if eepdater did anything special or was just a nice gui version of update && upgrade. out of curiosity, i have always clicked on the details button as it goes through the process and it seems to be just so (minus the autoclean/autoremove i usually throw in at the end of a terminal u&u for good measure).

This is the problem that I have no both Bodhi 5 and Bodhi 4.5 machines.

When sudo apt-get update && sudo apt-get upgrade is used, it times out in the end.

There has been no new apps installed when this problem started.

1 members found this post helpful.

I just started using the update-upgrade method in terminal and was curious to view a differential comparison as is offered when the update differs from an existing file.

You have to use Q to get out of this mode, not(!!) <Ctrl>C.

There's no prompt for the proper keypress to do this and the answer was found only after an extensive online search. Not exiting properly can halt the terminal session, leave processes running, and you'll be locked-out of continuing until all this is repaired.

1 members found this post helpful.