TigerVNC 1.3.80 crashing gnome-terminal in RHEL7

287 views
Skip to first unread message

Richa

unread,
May 15, 2015, 12:33:37 PM5/15/15
to tigervn...@googlegroups.com
I built tigervnc-1.3.80 from source on RHEL7. The vnc works fine but when I open gnome-terminal and click mouse or press keys on the terminal, it crashes. I get the following error:

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'encoding' from schema 'org.gnome.Terminal.Legacy.Profile'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'title' from schema 'org.gnome.Terminal.Legacy.Profile'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'title' from schema 'org.gnome.Terminal.Legacy.Profile'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'word-chars' from schema 'org.gnome.Terminal.Legacy.Profile'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): GLib-GIO-CRITICAL **: g_settings_get: the format string may not contain '&' (key 'monospace-font-name' from schema 'org.gnome.desktop.interface'). This call will probably stop working with a future version of glib.

(gnome-terminal-server:3188): Gdk-ERROR **: The program 'gnome-terminal-server' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadImplementation (server does not implement operation)'.
(Details: serial 994 error_code 17 request_code 132 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 the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

What exactly is it that I'm doing wrong?

Pierre Ossman

unread,
May 18, 2015, 4:43:29 AM5/18/15
to Richa, tigervn...@googlegroups.com
On Fri, 15 May 2015 09:33:36 -0700 (PDT)
Richa <richa.sh...@gmail.com> wrote:

> I built tigervnc-1.3.80 from source on RHEL7. The vnc works fine but
> when I open gnome-terminal and click mouse or press keys on the
> terminal, it crashes. I get the following error:
>
> ...
>
> What exactly is it that I'm doing wrong?
>

This looks like an X error rather than anything VNC related, so it
probably has something to do with the Xorg code you are using rather
than TigerVNC. Still, 1.3.80 is some old development code so you should
try with a stable release instead.

Rgds
--
Pierre Ossman Software Development
Cendio AB https://cendio.com
Teknikringen 8 https://twitter.com/ThinLinc
583 30 Linköping https://facebook.com/ThinLinc
Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

RICHA SHARMA

unread,
May 22, 2015, 7:11:01 AM5/22/15
to Pierre Ossman, tigervn...@googlegroups.com
Thanks Pierre for the reply. I built tigervnc 1.4.3 on RHEL7 and crash issue is resolved now.
Currently, I am getting ~15-20 seconds black screen before gnome-session is getting opened in the viewer. Is this a known issue?

Thanks,
Richa

Pierre Ossman

unread,
Jun 3, 2015, 7:21:23 AM6/3/15
to RICHA SHARMA, tigervn...@googlegroups.com
On Fri, 22 May 2015 16:41:00 +0530
RICHA SHARMA <richa.sh...@gmail.com> wrote:

> Thanks Pierre for the reply. I built tigervnc 1.4.3 on RHEL7 and crash
> issue is resolved now.
> Currently, I am getting ~15-20 seconds black screen before
> gnome-session is getting opened in the viewer. Is this a known issue?
>

Not something I'm aware of, no. Can you test with another desktop
environment so we can see if it is specifically gnome that has problems?
Reply all
Reply to author
Forward
0 new messages