Reinstalling is usually the last resort; the user is encouraged to troubleshoot the original issue and to refrain from 'reinstalling' as this will become a habit or a nasty carryover from other OS experiences. Your time -- and ours -- would be better spent doing something else. Try gohlip's approach this time and then we can proceed from there.
Try searching these forums for mouse problems, but include the keyword Synaptic or trackpad. I seem to recall that having BOTH the trackpad and an external mouse creates an issue like yours and the trackpad has to use something else instead of the default Synaptic--hence the extra step involved. Or choose one instead of sticking with both. This is why I have stayed with tracpoints and dell's cheap imitation of the red eraserhead, but that is a personal preference. Like not bringing a mouse on the road at all.
Try a search with Glidepoint or Alps because the drivers (these are branded products) were intended for these trackpads. Hope this brings you to a solution, before you toss that mouse.
Maybe it still has the SecureBoot still on? SmartDuck had to fiddle with it to bypass this, and that's probably why it is stuck in that loop. It looks like you cannot go there -- but this is where you should point it to the stick instead, as another route to complete the boot process. Just a guess but worth a shot.
This is unfortunate--Fedora even has a wiki entry for their 'Bodhi' and a build system called koji.
A suggestion -- Fedora can include a small note in their wiki that there is also a distro called Bodhi (provide a link or URL, complete with a desktop screenshot and the t-shirts bearing the Bodhi logo) that should not be confused for their issue tracking system, which appears to have reached a mature stage with thousands of entries already, and has been in place since Fedora 25 or thereabouts. It would take some effort to go under a different name; a similar effort on our side involves more than just a change of identity.
But it is only a suggestion; the decision, or plan of action, is up to our project leader
There is no need to apologize. You are welcome, and at least you were able to see things for yourself this way. I am sure there will be someone out there that will appreciate that you posted your findings here, instead of just ignoring the thread.
Entrance themes are no longer supported -- this happened right before e18 started, if memory serves. Moksha makes use of lxdm for logging in. That theme deserves to be ported; it has been ignored for ten years. One login is sufficient for me.
You know I never did quite figure out that "hover" configuration layer, until now. Thanks for the pro-tip with the keybind, too! It's like the post-its can be hidden, until they keybind reminds you that they were 'in your face' all along...
No worries; these are enough. Fix it in nvidia control center -- your x,y coordinates for the secondary are forcing a level secondary monitor, when in reality it is raised to the height of your primary. They are not making sense. This is what should be shown for the second monitor
1920x1080+2560+1440 for viewport out. Position for the ancor monitor should be 2560+1440 instead of 2560+0. Absolute is fine, except in this case it is absolutely wrong. It is placed where the bottom left corner touches the upper righthand corner of the Acer/primary. Putting it at 2560+0 throws it out of whack, and programs placed on anything but primary are rendered unusable.
Hit Save to X configuration file. Try Gohlip's suggestion after to get familiar with xrandr, but I prefer you fix nvidia settings first, though I think his xrandr is missing the --position parameter (at first glance). I think it will place the secondary to the right, but not elevate it i.e. there won't be a "lower" or "upper"
The forum will be sufficient for our needs, but it gets messy if you try all things at once. Their assistance is appreciated.
As a test if the nvidia settings are spot-on, try this: for Window placement, select place windows under the mouse, and put the new window or application on the raised secondary. Put a terminology screen there, not maxed, not full screen, and make sure that you can type or right-click on it to select a font or theme (in terminology). If clicking or typing gets no response it can only mean one thing--you're missing something.
Now hit PrintScreen. It would be nice to see, say a browser on one screen and the nyanology theme in terminology, on the other.
Arandr is good, but knowing how to use xrandr is even better, for a guy with dual DVI, it can be your Swiss Army knife. But if you know your Xorg.conf you should be fine; there is a place for specifying the layout. The nvidia control center can fine tune it. All these should sync--the only thing that is absolute should be where (0,0) is; it begins at the lower lefthand corner of the primary screen.