Evolution closes suddenly on virtual desktop

Forums / NoMachine for Linux / Evolution closes suddenly on virtual desktop

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #3230
    Avatarsmartin
    Participant

    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.

    #3380
    Avatarfra81
    Moderator

    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.

    #3413
    Avatarsmartin
    Participant

    Thanks for the reply. Any idea when the transition will be completed?

    Regards.

    #3629
    Avatarfra81
    Moderator

    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.

    #4104
    Avatarsmartin
    Participant

    Hi. Any news on this? It’s been 2 months now and still no update (just tried on 4.2.26).

    Regards.

    #4172
    AvatarBritgirl
    Keymaster

    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.

    #4191
    Avatarsmartin
    Participant

    Thanks. Is there any time schedule on NoMachine 5?

    #4254
    AvatarBritgirl
    Keymaster

    By the end of last quarter 2014 would be ideal. We’ll keep you all updated via the forums.

    • This reply was modified 7 years ago by AvatarBritgirl.
    #4937
    AvatarBritgirl
    Keymaster

    An update: we anticipated the transition to the latest version of X.org in 4.3. Download the latest version from the website.

Viewing 9 posts - 1 through 9 (of 9 total)

This topic was marked as solved, you can't post.