Author Topic: Drawing issues on RHEL7.6  (Read 443 times)

tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Drawing issues on RHEL7.6
« on: January 09, 2019, 03:35:47 pm »
When I launch SlickEdit from a terminal, I get a lot of spew like this:

5001$ QNativeImage: Unable to attach to shared memory segment.
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
load glyph failed err=24 face=0x5232bf0, glyph=0
QFontEngine: Glyph neither outline nor bitmap format=0
load glyph failed err=24 face=0x5232bf0, glyph=0
QFontEngine: Glyph neither outline nor bitmap format=0
.....
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
  Major opcode: 62 (X_CopyArea)
  Resource id:  0x0
...


And when The window opens, the buffer window is filled with a light blue, and the menu bar starts out drawn, but each menu blinks out when I mouse over it, and doesn't redraw. If I move the cursor in the buffer window, the line with the cursor draws correctly, but may or may not be replaced by blue at any time.

This is a new issue, and I haven't changed anything. I am connecting to the host machine with VNC.

Thanks,

Tim.


Slick Info:

SlickEdit Pro 2018 (v23.0.0.11 64-bit)

Build Date: November 26, 2018
Emulation: CUA

OS: Linux
OS Version: Red Hat Enterprise Linux Server release 7.6 (Maipo)
Kernel Level: 3.10.0-862.9.1.el7.x86_64
Build Version: #1 SMP Wed Jun 27 04:30:39 EDT 2018
Processor Architecture: x86_64

X Server Vendor: The X.Org Foundation
Memory: 91% Load, 33442MB/36411MB Virtual
Shell Information: slickedit/23.0.0.11/bin/secsh -i
Screen Size: 3840 x 2115

Project Type: VHDL: Model Technology ModelSim
Language: .bash_profile (Plain Text)
Encoding: Automatic

Installation Directory: slickedit/23.0.0.11/
Configuration Directory: .slickedit/23.0.0/
Migrated from: .slickedit/22.0.2/

Hotfixes:
/.slickedit/23.0.0/hotfixes/hotfix_se2300_1_cumulative.zip (Revision: 1)



patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1007
  • Hero Points: 86
Re: Drawing issues on RHEL7.6
« Reply #1 on: January 09, 2019, 05:29:36 pm »
Do the mesages it go away when you launch SlickEdit with the QT_X11_NO_MITSHM=1?  It's not unusual to see something like this when you run SE as root, and machine policy prevents X shared memory from being used when the user is root.  Not seen it with VNC before.

ie:
Code: [Select]
QT_X11_NO_MITSHM=1 /opt/se_install_path/bin/vs +new ...

tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Re: Drawing issues on RHEL7.6
« Reply #2 on: January 09, 2019, 05:41:17 pm »
Hi Patrick,

I'm not root, so I don't run anything as root.

I tried adding QT_X11_NO_MITSHM=1, and I still got the QFontEngine and load glyph error lines from my original post. I did not get the X Error or shared memory errors, and everything seemed to be drawing properly. I went back and launched without the QT_X11_NO_MITSHM=1, and it behaved the same - no draw errors on screen, but still listed QFont and load gliph errors.

Since I posted I discovered other GUI apps having issues, so I restarted my VNC server instance on the host machine. I think that may have been the cause of the BadDrawable errors. I'm guessing the glyph erorrs are fonts it can't find?

-Tim

tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Re: Drawing issues on RHEL7.6
« Reply #3 on: January 09, 2019, 07:40:08 pm »
OK, so a few more launches on the same VNC session, and it's back.  I tired the new env variable and it seemed to help.

So what exactly does QT_X11_NO_MITSHM=1 do? And what could have changed to require this? I've been using SE on this machine for a year without problems.

-Tim

patrick

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1007
  • Hero Points: 86
Re: Drawing issues on RHEL7.6
« Reply #4 on: January 09, 2019, 08:32:07 pm »
Turns off the X11 shared memory extension.  It allows image data to be transferred over a shared memory segment, rather than the  X11 protocol socket when the client and X server are on the same machine. 

You can query for the extension to see if it's there, but in the cases we've seen it's not a matter of the extension not being there, but something lower level security layer preventing the shared memory from being created.  That env variable prevents Qt from using the extension even if it's available.

I need to take a closer look at vnc changelogs and docs to see what could be up.  I run SE from terminals all the time, but not over vnc, so this is the first I've heard of anything like this.


tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Re: Drawing issues on RHEL7.6
« Reply #5 on: January 09, 2019, 08:57:11 pm »
Interesting. For now I'll just set the env variable in my shell, and go from there. I'll also ping the sysadmin and see if there have been any new security things done. Security is particularly strict in my environment, so they may have tweaked something.

If it helps, we're running TigerVNC 1.8.0 as the server and I've got 1.9.80 as the client on my Mac. This setup hasn't changed in a very long time, but the broken draw behavior is a recent failure.

-Tim

rgloden

  • Senior Community Member
  • Posts: 163
  • Hero Points: 5
Re: Drawing issues on RHEL7.6
« Reply #6 on: January 10, 2019, 03:40:10 am »
RHEL 7.6 is fairly new ... you might ask when your admins updated to 7.6.

tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Re: Drawing issues on RHEL7.6
« Reply #7 on: January 10, 2019, 10:14:30 pm »
The RHEL7.6 update is a couple of months old, so I don't think the problem was introduced specifically with 7.6. There may be some config changes I'm not aware of. I'll see what the sysadmin says. I've noticed that it's affecting other applications as well (Dolphin in particular), so I think they changed something.

ddietrich

  • New Community Member
  • Posts: 1
  • Hero Points: 1
Re: Drawing issues on RHEL7.6
« Reply #8 on: January 26, 2019, 03:38:48 pm »
I have been seeing this same issue for a couple of months.  It seems like it started after our ITS department did one of their monthly system updates (yum update) - maybe in November.  It only happens on VNC connections.
After that system update, there now seems to be a shared memory issue which looks like a leak of some sort.  I have noticed that these messages occur when all of the shared memory segments are allocated.

tim_k

  • Senior Community Member
  • Posts: 140
  • Hero Points: 11
  • -Tim
Re: Drawing issues on RHEL7.6
« Reply #9 on: January 28, 2019, 09:29:43 pm »
I've left  QT_X11_NO_MITSHM=1 in my login script, and so far no more issues. It's helped with other apps as well. I haven't heard from the IT guys on what may have changed to cause this. Time for another ping, perhaps.

-Tim