On Thu Jul 20, 2023 at 04:31:55PM +0100, Stuart Henderson wrote: > On 2023/07/20 17:27, Rafael Sadowski wrote: > > Let's start with a quote from an old try: > > > > "Our Xorg server doesn't run under the same uid as the client, the client > > needs to create the shared memory area with mode 0666. > > > > We are doing the same in misc/screen-shm. Of course, the consequence > > here would be to do it for all Qt applications." > > > > -- https://marc.info/?l=openbsd-ports&m=167110468109188&w=2 > > > > There was a veto from sthen@, which was perfectly okay and right. For > > error analysis and to exclude that this function is not used, I need the > > shm mode from time to time. I would like to solve it with an environment > > variable (QT_OPENBSD_SHM_MODE). > > From that mail, > > "What are the consequences of leaving this as-is? (i.e. what's broken > now that changing this would fix?)" >
Nothing is broken and nothing is would fix for now. It just helps me to debug Qt application or large ecosystem like KDE plasma. When I increase the debug level I see that shm could not be init and therefore I can not exclude that exactly this is a problem. Long story short: It helps me not to always have to build Qt myself.
