I'm hearing impaired. Where others have no issues following talks or dicussions, I often fail even grasp the bottom line what it's about. I've got hearing aids, but they help only so much. I also have an add-on device for my hearing aids that acts like a bluetooth headset. Unfortunately, making this thing work under my Linux desktop has been an ongoing, frustrating struggle. On the contrary, it works flawlessly with Android devices of different generations, and even with my lowly Gigaset phone. Actually, the thing works better with older kernels/Linux versions than with current TW.

openSUSE now has a lot of black magic around building distributions for :Factory and :Leap

Project description

With many Proof of Concepts (PoCs) going on for SUSE Cloud, the development team has observed that we have no clear path on how Sales Engineers (SEs) and sometimes dedicated support engineers (xSE) can receive technical support to successfully complete the projects, often leading to escalation calls and even firefighting on-site visits by developers. Goal of that project is to come up with a best practice guide and to eventually set expectations on what's possible from a development point of view. Results should be documented in a central internal location and announced to all relevant parties.

VNC protocol transfers key symbols (= basically characters), not key codes (= "coordinates" on keyboard). Therefore pressing the same keys may result in sending different commands over VNC depending on the keyboard layout and state of modifiers on the client side. The server however can not directly send the key symbol to the application, it must instead find or create key code that will translate to that symbol and send that.