evolution/totem/gthumb crashes when run in vnc session

[Christopher Weber]

1) The release of Ubuntu
   Description: Ubuntu 16.04.1 LTS
   Release: 16.04

2) The version of the package I am using:
   evolution 3.18.5.2-0ubuntu3
   vnc4server 4.1.1+xorg4.3.0-37.3ubuntu2
   xfwm4 4.12.3-1ubuntu2
   fluxbox 1.3.5-2

3) What I expect to happen:
   evolution runs so I can access mail/calendar.

4) What happened:
   I'm running vnc4server with xfce4 as the window manager/desktop.
   When I attempt to start evolution the following happens.

   [cweber@usacwebera ~]: evolution

   (evolution:22961): Gdk-ERROR **: The program 'evolution' received an X Window System error.
   This probably reflects a bug in the program.
   The error was 'BadRequest (invalid request code or no such operation)'.
     (Details: serial 95 error_code 1 request_code 149 (RANDR) minor_code 8)
     (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.)
   Trace/breakpoint trap (core dumped)

   This happened using fluxbox too, but does not happen if I'm at the local
   desktop using either xfce4 or fluxbox. Nor does it happen in an
   ssh session using X Tunnelling.

   Only when in a vnc4 session.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evolution 3.18.5.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Sep 7 14:34:00 2016
InstallationDate: Installed on 2014-11-10 (666 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: evolution
UpgradeStatus: Upgraded to xenial on 2016-08-31 (7 days ago)

[Christopher Weber (chris-weber)]

Looks like this is not evolution specific. Totem throws the same error:

[cweber@usacwebera DISC]: totem --sync /home/cweber/public_html/FX_Trip/VID_20160826_092145_DaiButsuEntryway.mp4

(totem:2477): Gdk-ERROR **: The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 95 error_code 1 request_code 149 (RANDR) minor_code 8)
  (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.)
Trace/breakpoint trap (core dumped)

I'm trying to use apport-retrace to get further information, but at this time I keep running into problems with just about every instruction on how to do it I've read so far.

[Christopher Weber (chris-weber)]

Combining the instructions for apport-retrace (apport-retrace -R -g -S system <CRASHFILE>) with the wiki Backtrace instructions I got the attached.

[Christopher Weber (chris-weber)]

Combining the instructions for apport-retrace (apport-retrace -R -g -S system <CRASHFILE>) with the wiki Backtrace instructions I got the attached.

[Christopher Weber (chris-weber)]

One for totem.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ken Pratt (kenpratt)]

A similar error occurs when one attempts to run evolution on a remote X Desktop. It seems there is a dependency on direct rendering which is not available in either the VNC or remote X windows environments.

Recreate with:

# ssh -X servername [where the server is running Ubuntu 18.04 Desktop]
# evolution
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libEGL warning: DRI2: failed to authenticate

(evolution:25704): Gdk-ERROR **: 06:48:35.588: The program 'evolution' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 207 error_code 1 request_code 153 (DRI2) minor_code 1)
  (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.)
Trace/breakpoint trap (core dumped)

[yoav (yavitzour)]

I experience this as well with evolution over xrdp. Any chance this will be looked at?

[gregrwm (gregrwm)]

been bothered by this for years with gthumb.