i was going to add that even though updates ran on install i did do apt update and upgrade after i was done removin=g a few things and adding the stuff i needed.

i found the line in the .desktop file (NoDisplay=true) that hid it from the menu as rbtylee mentioned in his reply. thank you both for your help.

one of the reasons i mentioned it missing from the desktop menu in the first place is that it feels relatively buried in the settings menu and to me it seems like there might be a bit of a disconnect between the elementary designation/name since most things are moksha labeled now. i even forgot/wasn't sure that changing the scaling there would increase the font in terminology which was impossibly small to begin with for me. i had in my own reinstall notes that i thought it was probably just a duplicate of the regular scaling option in the settings "look" tab.

thank you for taking a look and providing helpful feeback/info.

i found the setting under the audio tab titled "Mute Input" (in case anyone else was looking) and it did what you said. one of the reasons i mentioned it to begin with (other than that i didn't remember it from past releases) was that it wasn't a "clean" sound (on my system it sounded glitchy whereas all other system sounds are fine and clear) so it felt like it detracted more than added to the ux. just my two cents

after i checked the box for mute input, it worked as expected regarding the input sounds. however, after just a couple of seconds the check mark disappears from the menu. while that isn't particularly a problem for me since i didn't want the sound, it seems to make it impossible to re-enable the sound (i was unable to do so as an experiment) if someone were to want that choice.

Sounds suspiciously like a bug with efl or elementary_config (a part of efl) or perhaps our theme. I will have to look at it and see what I think if I can duplicate it.

1 members found this post helpful.

in general i don't do much system theming or customization. i tend to keep the default background image even just because it works and i don't have to fool with it. i switched to crux because it was easier to see some of the icons at the top of libre office writer.

that being said, i decided to try some to see if i could help out a little. i tried to download the buuf deuce icons from the appcenter and keep getting "package not found" even though i allowed the dialog to update and i also updated through the terminal.

after that i tried the rosa icons and the blues and greys seem to pair decently well with crux. i actually like the new flat, green icons (and green icons in general) but had trouble spotting firefox in my taskbar just by shape. rosa fixed that.

Yesterday, I did a bare metal installation with the HWE iso of 5.1, on a laptop with UEFI running in UEFI mode. It installed fine and flawlessly, alongside an existing Windows 10.

2 members found this post helpful.

Cool

Great to know Several people have reported this so I am assuming it has no or very few UEFI installation problems.

1 members found this post helpful.

Thanks indeed for all your kind works and recommendations and rather impressive testing

As to the update upgrade popup idea I sorta hate popups even our own quickstart. Not that I am removing our quickstart on first boot. However I have been considering moving it to the application menu somewhere and not hid as Help in the About Operating System menu. Seems an unlikely place to look for it.

As you have probably noticed, the quickstart does include how to update altho it is in need of updating itself and recommends eepDater. eepDater caused much confusion and I removed that app for now instead of dedicating what would end up being too much time to fixing it. But much in the quickstart needs work from its appearance to the text. My original plan was to work on the text today but after having a very hard time getting python3-efl, version 1.23 packaged for testing, I doubt I will get that completed today. I am not really the best candidate for updating the text as I tend to be overly verbose, encyclopedic and haven't really mastered the art of the kind of terseness and simplicity the guide is written in. I have been unable to get ahold of our unofficial "head of documentation." I suppose he is missing in action and now considered a former Team member.

But nonetheless as there is no one else but me to do it, me or Štefan and English is not Štefans native language it sorta falls upon me. I will do my best to keep it simple and perhaps link to more comprehensive articles or wikis if I feel the need. Even If I have to also supply those But regarding the appearance, our plans are for Štefan to try and get the css updated to better match our theme. And a long term plan would be to somehow fix it so that it also supports localization. Long term plan meaning not for this release, unless someone other than me takes on this task.

Back to the popup idea on updating, how about a notification instead of another application popping up or another tab on the browser?

1 members found this post helpful.

ylee. 1. is there a text copy ot full copy with images that one could work from? what sorts of stuff need to updated? any other questions relevant would be great to have answers to. thanks.

i too am not into popup sort of stuff. I agree with you.

neater and cleaner is better and not cluttering...

1 members found this post helpful.

it is found here: https://github.com/BodhiDev/bodhi5pa...dhi-quickstart

Much of the text is out of date and the images need updated and the appearance needs changed to better match our theme.

1 members found this post helpful.

Fine as well.

2 members found this post helpful.

My todays very first work on Quick Start guide. Played with styles and colors to match ArcGreen theme. As I have no art education, lets hope I did not do any color interferences...

https://i.imgur.com/bjd5bub.jpg
https://i.imgur.com/DyMXKmI.jpg

Stefan

1 members found this post helpful.

ok - I had a couple of look-sees and not sure i have a handle enough on Bodhi to try to help out on this. I was hoping that since i do not code i could at least do something along an edit line or so but I would probably botch it all up. Sorry Ylee. In addition, all of that html stuff is way the hell beyond my scope.

My two cents: I'm not a native English speaker, so I'm not really qualified for a job like this. But I think that in general most Quickstart Guides are far too elaborate, and therefore get skipped by most people (I tend to do that, anyway). You know: TL;DNR (Too Long; Did Not Read).

So I think an effective Quick Start guide could perhaps be reduced to just one short page, with the following contents:

1. A very short welcome (one or two sentences), something like: "Welcome, thanks for choosing Bodhi, have fun";

2. A short explanation of how to deal with Bodhi (one or two sentences), along the lines of: "Bodhi is mean and lean, it's up to you to fatten it up with the things you want";

3. One or two lines about how to update it (no graphical updater, sudo apt-get update && sudo apt-get dist-upgrade);

4. One line with a link to the documentation of the project ("Want to find out more? Visit our documentation");

5. One line with a link to Bodhi's support forum ("Need friendly help? Get it here")

Simple and effective. Like the project itself.

2 members found this post helpful.