p.s. it could have been once i got into it through the menu and set things up it showed up. however - i must say that before install it do try to get online and get it all working and then do the install so it is already hooked up to the wifi. then it does appear - but the exact situation i cannot be clear.

1 members found this post helpful.

Ah! That jogs my memory. Yes, it may have originally been a Menu item.

In any event, the problem has been debugged, so I will try to remember it, for the next time.

Thanks!

sorry i cannot be specific - just do not have time to redo my system and i am very anal about all of the setup options i have and in my case both daily thinkpad and faster better office thinkpad's are identical as such with layout and apps and files etc. as much as is possible.

:-)

Stefan, one of the Bodhi devs, had a great list of little improvements for the ISO refresh of Bodhi 5.1
1. Include the new themes.
2. Move the Installer Icon to a more noticeable place.
3. Auto produce the default user directories that users have become familiar with. (This is a little thing, but a nice "finish" and "polish" touch.)
4. (Could this be considered) Have Network Manager Applet on the shelf and working in the live environment if possible.
- In my Linux communities that I hang out in this has been mentioned any number of times and caused those same people who ran into it to not install Bodhi on their hard drive because they believed they would not be able to get wireless working easily after the install, which we know is not the case. I've also noticed that this issue gets raised frequently by new users in the Discord channel so it would be nice to fix just to cut down one of the more common issues new users struggle with, but I don't know what needs to be done to make this work. I did not even notice it because I rarely spend time with a distro's live environment. If I go through the trouble of downloading a distro I put it onto the hardware right away.
5. A fix for the esudo/PolicyKit Agent. Would an easy fix be to just install and use the gnome PolicyKit agent which is the suggested current work around, and pull away from esudo? Personally I liked esudo's look and feel and it did the one thing you needed it to do, but if being based on Ubuntu will cause this to break when PolicyKit is upgraded, perhaps it would be better for users to just switch to the gnome agent. I've been using openSUSE Enlightenment 22 and this is an issue for them too. Currently on their system if you need a GUI tool to run in root they use xdg to open a terminal window and ask for a password which looks way worse than esudo/PolicyKit-1-gnome.

If the team were able to address those 5 things for the ISO refresh I think we would have a great tool to encourage new users to give Bodhi a try. Bodhi continues to amaze me as a lightweight distro, and a great community where the developers are active and engaged. I'm very thankful for this labor of love by the Bodhi team.

Resolution Issues: This was mentioned by someone, I will admit that I have resolution issues too with one external monitor that I attach to my laptops. I have discovered that the issue is not caused by Bodhi. I have it with every distro I've tried Ubuntu based or openSUSE if they are running a display manager other than kwin which is used by KDE (I have no idea why KDE just works, this is magic to me, but not helpful since I prefer Moksha). I also know that a resolution manager won't fix my issue if Bodhi added one because the monitor's specs are not being correctly interpreted. I have to run a series of xrandr commands to fix it. Thankfully, Moksha makes it easy to run a start up bash script to fix my external monitor display. I'm not sure what the resolution issues were, but I have found that a bash script with the proper xrandr commands is a nice work around for my issues, maybe that could help others too.

1 members found this post helpful.

I'd like to add the following:
- Fixing eepdater so that it doesn't hang.
- A complete redesign of AppCenter, so that one doesn't need to mouse around painfully installing one app at a time. Either get rid of it, or make it work such that you can set multiple tick boxed on one page and install them all in one go.
- After a new install, warn users in no uncertain terms that they MUST do apt update and upgrade as soon as they've successfully connected to the internet.

the eepdater hangs when there is the decision y or no etc... i.e. disk space or else - other things as in today's upgrade where you need to choose use new boot or old whixh i was told always chose the current used one - and that seems to be the issue. i tried enter and a lot of other stuff but a recent find accidentally in terminal i found a week or 2 ago was i hit tab and that got me to another place where enter did work - so just a random last minute thought maybe try hitting tab when it freezes and then maybe you can have a choice that will work with enter.... i know - i know be more specific but i can't. i know very little and then i have not encountered that since i do not use eepdater since issues with 4.5 -and 5.

i had a discussion with charles when i had this issue way back when and he had no suggestions to get the eepfater to take a choice. we even discussed the arow keys etc. by the way.,

he said use terminolgy and ever since i have done it that way.

The install button is still in the Desktop folder. But you have to turn on the desktop to see it. Or use the file manager and navigate to it. It is also in the menu.

2 members found this post helpful.

thanks randy.

1 members found this post helpful.

one more thing to consider:
add xdg autostart or not?
(personally i'm fine without it, but it's common and newbies might wonder why their newly installed program won't autostart)

This would be an emphatic NO from me. To many apps add stuff to the /etc/xdg/autostart directory, I certainly would not want all that stuff starting at boot.

Besides this is not the Enlightenment way. If the e-devs had wanted that stuff to be automatically added to startup they would have did so a long time ago certainly before Bodhi forked e17. Not that Bodhi has to necessarily follow what the e-devs intended, but in this case and probably many other cases they were certainly right.

These apps are found in the Settings menu under Apps -> Startup Applications under the System tab. If the user insist on adding them. Any newbies that "wonder why their newly installed program won't autostart" need to get with the program and learn how to use E17/Moksha or ask on the forums or elsewhere or choose another distro or DE.

Note: in most cases I believe in following the freedesktop.org specifications. But in this case I don't think it is appropriate for Moksha.

1 members found this post helpful.