- This topic has 8 replies, 3 voices, and was last updated 10 years, 1 month ago by
.
-
Posts
-
Hi,
My Configuration:
Server: Debian Wheezy amd64 (all patches applied) with nomachine-workstation-update_4.2.21_4_amd64.deb, Gnome.
Client: Windows 8.1 (all patches applied) with Enterprise Client 4.2.21_1.
My Problem:
Connect to a virtual desktop on server. Open Evolution. Write a mail and Evolution crashes.
Other data:
Works fine using physical screen connection. Running from the command line I get this output:
(evolution:14105): Gdk-WARNING **: The program ‘evolution’ received an X Window System error.
This probably reflects a bug in the program.
The error was ‘BadValue (integer parameter out of range for operation)’.
(Details: serial 10114 error_code 2 request_code 146 minor_code 26)
(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.)Regards.
This appears to be a problem of this Evolution version when running with older X.org versions. Tests showed that the crash is reproducible also without using NoMachine, in a physical display running the same X.org version as NoMachine’s.
That said, this problem will be automatically solved when the transition to the new X.org will be completed in NoMachine.
Work is in progress, but it is a major change and it will require quite a long period of testing, given the number of different Linux platforms.
So I can’t say exactly. Should be in terms of weeks.
Unfortunately, the transition to the new version of X.org has now been moved to NoMachine 5, so there will be no change with regards to this bug on Evolution until then.
This topic was marked as solved, you can't post.