Bug 24661

Tested a few more times on the same machine and installation, with different desktop environments.  Reproducible.

Checked glmark2 2017.07 (same source rpm) with nvidia 390.116 on Xfce from the mga7beta3 round 2 iso and that worked perfectly - exactly the same software but a slightly different environment.

Tried the Xfce Live iso for mageia7 beta3 round 3 and installed glmark2.
That worked fine.

Assigning to the registered glmark2 maintainer.

Assignee: bugsquad => ghibomgx
CC: (none) => marja11

So to resume: you are using nvidia390-390.116-1.mga7 drivers.

rpm -q glmark2 returns:

glmark2-2017.07-3.20190327.mga7

it works always on (either as LIVE ISO or hard disk):

- XFCE

but FAILs on:

- Mate
- some other environment

?

Is system 32 or 64bit?

64-bit only.  No 32-bit hardware to test this.

glmark2-2017.07-3.20190327.mga7

Initial tests were on fresh installation on a Skylake machine with Mate.  glmark2 fails under Mate and several other DEs; Plasma, GNOME, Xfce, Cinnamon and Enlightenment.  That machine is running nvidia 418.56 for GTX1080Ti card.

Just checked an older machine running nvidia 390.116, Xfce only, and there it works fine.  That system was installed from the Xfce Live iso and  glmark2 also worked during the Live session.  nvidia card is GTX555.

Shall look for a mga7 partition on *this* machine (GTX970).

OK, found a Cauldron installation and installed the current version of glmark2.
$ rpm -q glmark2
glmark2-2017.07-3.20190327.mga7

glmark2 runs fine under Mate.  nvidia 410.93 with GeForce GTX970.
The only Plasma installation on that machine was running X under nouveau but glmark2 worked in compatibility mode.

Found another recent mga7 installation on a laptop.
glmark2 runs OK on that as well.  nvidia 418.56 for GTX965M and Plasma.

Conclusions so far:

Desktop environment agnostic.
Runs fine on three different nvidia machines.
For some reason it does not like the Skylake machine, so it could be hardware specific, which could also implicate the nvidia driver.

Any further diagnostic tests should be confined to the Skylake machine.

Darn.  Spoke too soon.  Just finished a 1500 package scheduled update on the  GTX970 machine (that partition had not been booted for a while).
$ glmark2
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  28
  Current serial number in output stream:  29

However, the system needs rebooting, for glibc etc.

Lost the nvidia driver on the GTX970 machine - continuous series of reboots - always ended up at nouveau so that partition is no use for testing,  Sticking to tthe original decision from now on - confining the tests to the skylake machine.

Scrub that decision.  Back to the GTX970 machine.  New mga6 upgrade to mga7 installation.  glmark2 fails.

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  150 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  41
  Current serial number in output stream:  40

Would xdpyinfo help?

name of display:    :0
version number:    11.0
vendor string:    Mageia
vendor release number:    12004000
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  window 0x1600088, revert to Parent
number of extensions:    29
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DPMS
    DRI2
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    NV-CONTROL
    NV-GLX
    Present
    RANDR
    RECORD
    RENDER
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-DGA
    XFree86-VidModeExtension
    XINERAMA
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    3840x2160 pixels (602x341 millimeters)
  resolution:    162x161 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32
  root window id:    0x1ea
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x20
  default number of colormap cells:    256
  preallocated pixels:    black 0, white 16777215
  options:    backing-store WHEN MAPPED, save-unders NO
  largest cursor:    256x256
  current input event mask:    0xfa8033
    KeyPressMask             KeyReleaseMask           EnterWindowMask          
    LeaveWindowMask          ExposureMask             StructureNotifyMask      
    SubstructureNotifyMask   SubstructureRedirectMask FocusChangeMask          
    PropertyChangeMask       ColormapChangeMask       
  number of visuals:    132
  default visual id:  0x21
  visual:
    visual id:    0x21
    class:    TrueColor
    depth:    24 planes
    available colormap entries:    256 per subfield
    red, green, blue masks:    0xff0000, 0xff00, 0xff
    significant bits in color specification:    11 bits
.....

The latest update seems to have solved this.  Tested on one machine so far but it can be marked as solved.

Resolution: (none) => FIXED
Status: NEW => RESOLVED