SLES 12 xrdpVNC problems

Hello,

I using VNC to connect to our SLES servers remotely.
At SLES12 I have some GUI problems:

1st gedit:
I can’t open gedit. I get following error:

QUOTE: Gdk-ERROR **: The program ‘gedit’ received an X Window System error.
This propably reflectes bug in the program.
The error ‘BadImplementation (server does not implement operation)’.
(Details: serial 604 error_code 17 reques_code 132 (XInputExtension) minor code 46)
(Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it.
To debug your program, run it with GDK_SYNCHRONIZE environment variable to change this behavior. You can geht a meaningful backtrace from your debugger if you break on the gdk_x_error() funktion.)[/QUOTE]

2nd terminal:
If I try to open the menu (File, Edit, View, Terminal, Help) the terminal crashes immediately.

3rd xrdp:
If I log in via xrdp, the system language is english, instead of german (default).
The language in the Region and Speech menu is german.

The problems also occurs with xrdp and not with VMware console

Best regards,
Christian

Christianmolecki,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team
http://forums.suse.com

[QUOTE=christianmolecki;26673]Hello,

I using VNC to connect to our SLES servers remotely.
At SLES12 I have some GUI problems:

1st gedit:
I can’t open gedit. I get following error:

2nd terminal:
If I try to open the menu (File, Edit, View, Terminal, Help) the terminal crashes immediately.

3rd xrdp:
If I log in via xrdp, the system language is english, instead of german (default).
The language in the Region and Speech menu is german.

The problems also occurs with xrdp and not with VMware console

Best regards,
Christian[/QUOTE]

I recently installed SLES12 and configured VNC. Seeing same issue. Any resolution?

/var/log/message output:

2015-03-16T16:15:14.109122+05:30 linux-0qcg org.gnome.Terminal[10931]: (gnome-terminal-server:11244): Gdk-ERROR **: The program ‘gnome-terminal-server’ received an X Window System error.
2015-03-16T16:15:14.109467+05:30 linux-0qcg org.gnome.Terminal[10931]: This probably reflects a bug in the program.
2015-03-16T16:15:14.109710+05:30 linux-0qcg org.gnome.Terminal[10931]: The error was ‘BadImplementation (server does not implement operation)’.
2015-03-16T16:15:14.109948+05:30 linux-0qcg org.gnome.Terminal[10931]: (Details: serial 444 error_code 17 request_code 132 (XInputExtension) minor_code 46)
2015-03-16T16:15:14.110188+05:30 linux-0qcg org.gnome.Terminal[10931]: (Note to programmers: normally, X errors are reported asynchronously;
2015-03-16T16:15:14.110426+05:30 linux-0qcg org.gnome.Terminal[10931]: that is, you will receive the error a while after causing it.
2015-03-16T16:15:14.110664+05:30 linux-0qcg org.gnome.Terminal[10931]: To debug your program, run it with the GDK_SYNCHRONIZE environment
2015-03-16T16:15:14.110953+05:30 linux-0qcg org.gnome.Terminal[10931]: variable to change this behavior. You can then get a meaningful
2015-03-16T16:15:14.111236+05:30 linux-0qcg org.gnome.Terminal[10931]: backtrace from your debugger if you break on the gdk_x_error() function.)
2015-03-16T16:15:14.112075+05:30 linux-0qcg kernel: [ 1331.342439] traps: gnome-terminal-[11244] trap int3 ip:7fae284d1139 sp:7fffbb39f9c0 error:0traps:

Hi,

using SLE Classic as windows manager is a workaround.
You can change the window manager on the login screen, if you enter the password (the gear wheel)

Edit (10 minutes expired):

you have to use IceWM not Sle Classic.

Good afternoon,

I have the same problem, did you find a resolution?

David J.

Hello David,

the problem still occurs. I don’t have a solution, just a workaround (see above).

Christian M.