LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Bodhi (https://www.linuxquestions.org/questions/bodhi-92/)
-   -   Bug in Bodhi 5.1: Terminology always starts first command with a capital letter (https://www.linuxquestions.org/questions/bodhi-92/bug-in-bodhi-5-1-terminology-always-starts-first-command-with-a-capital-letter-4175672584/)

Kiezel 04-05-2020 05:09 AM

Bug in Bodhi 5.1: Terminology always starts first command with a capital letter
 
I think I've found a bug: in Bodhi 5.1, Terminology always starts the first command with a capital letter. Which usually makes the command I try to execute invalid, which is rather annoying....

It's not an important bug, but perhaps it can be fixed easily?

the_waiter 04-05-2020 08:26 AM

This happens for me but only in Virtual machine. Does it behave badly under real HW?

rrashkin 04-05-2020 08:50 AM

Not for me.

Kiezel 04-05-2020 09:36 AM

Quote:

Originally Posted by the_waiter (Post 6108028)
This happens for me but only in Virtual machine. Does it behave badly under real HW?

Indeed I'm running it in a VM. Strange, that it apparently doesn't happen on a bare metal installation.... If it only happens in a VM, then it's of course even less important.

the_waiter 04-05-2020 10:24 AM

We know about this. Not sure why happening. Probably Ylee could know. He is a boss here :)

rbtylee 04-05-2020 02:36 PM

Quote:

Originally Posted by Kiezel (Post 6107980)
I think I've found a bug: in Bodhi 5.1, Terminology always starts the first command with a capital letter. Which usually makes the command I try to execute invalid, which is rather annoying....

It's not an important bug, but perhaps it can be fixed easily?

Ok from comments below it is clear you are referring to a old and known virtual box issue. Here is the issue:
  • Install bodhi in a virtualbox Vm
  • When one starts Bodhi in the VM and it boots into moksha, the first keypress regardless of the app it happens in will be as if the caps key is pressed.

This has happened as far as i remember for as long as I have been using Bodhi and only happens in a Virtualbox VM as far as I know. (doesn't happen in a VMware VM for example). It is an annoyance and before we forked enlightenment into moksha I had sorta hoped the e-devs would address this issue or a change in Virtualbox would make it go away.

Now since we have forked e17 into Moksha I suppose if this issue does get addressed it will be done by a bodhi developer ... and that seems mostly likely to be me. So I prioritize issues I look at and this one is low priority.

Quote:

Originally Posted by the_waiter (Post 6108080)
We know about this. Not sure why happening. Probably Ylee could know. He is a boss here :)

Hmm I did look at it one day long enough to see WHY it is happening. But not long enough to play around with fixing it. There was no obvious clear way for me to fix this issue that stood out when I looked at it. So I left it at that: Something to look at latter when I feel I have the time to closely examine it and possible fixes. Since it is not some major issue like a segfault or something just flat out not working, it is going to remain low priority for me. Patches accepted of course.

Kiezel 04-05-2020 04:35 PM

Quote:

Originally Posted by rbtylee (Post 6108181)
it is going to remain low priority for me.

I agree with that assessment. Thanks for the explanation. :)


All times are GMT -5. The time now is 03:28 PM.