BodhiThis forum is for the discussion of Bodhi Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
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:
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.
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.
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.
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).
Last edited by cordx; 11-13-2018 at 02:32 PM.
Reason: missing words
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.