Fresh 22.04 - glxgears is OK but graphics issues with nvidia-settings and nbody/oceanFFT

Summary: After a fresh install of Ubuntu 22.04 and install of the latest cuda, glxgears works fine but there are issues seen on the console and gui for nvidia-settings, and in attempts to run nbody and oceanFFT (after make clean; make).

Attached are nvidia-bug-report.log.gz, some screen-shots, and relevant text from terminal.


Attached file console.log contains the following sections:
console.log (11.4 KB)

  • How Ubuntu 22.04 was installed
  • How cuda was installed
  • Attached nvidia-bug-report.log.gz
    nvidia-bug-report.log.gz (358.9 KB)
  • PASS: nvidia-smi
  • PASS nvcc --version
  • PASS: Refer attached screenshot: no_errors_with_glxgears.jpg
  • ISSUES: nvidia-settings (see message on console)
    (nvidia-settings:3423): GLib-GObject-CRITICAL **: 15:07:28.895: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  • ISSUES: Refer attached screenshot: issues_with_nvidia_settings.jpg
    Missing Prime Profiles
    Missing value for Display Devices
  • PASS ./deviceQuery (after make clean; make)
  • ERROR ./oceanFFT (after make clean; make)
    CUDA error at oceanFFT.cpp:304 code=999(cudaErrorUnknown) "cudaGraphicsGLRegisterBuffer(&cuda_heightVB_resource, heightVertexBuffer, cudaGraphicsMapFlagsWriteDiscard)"
  • ERROR ./nbody (after make clean; make)
    CUDA error at bodysystemcuda_impl.h:191 code=999(cudaErrorUnknown) "cudaGraphicsGLRegisterBuffer(&m_pGRes[i], m_pbo[i], cudaGraphicsMapFlagsNone)"
  • PASS ./randomFog (after make clean; make)



console.log (11.4 KB)


nvidia-bug-report.log.gz (358.9 KB)

Please see this:

Thanks for the pointer, the situation is improving. nvidia-settings still reports a failure for g_object_unref:

~$ nvidia-settings

**(nvidia-settings:3378): GLib-GObject-CRITICAL **: 17:16:00.951: g_object_unref: assertion 'G_IS_OBJECT (object)' failed**

(oceanFFT, nbody, randomFog, and glxgears do run as expected.)

The error is “normal”, nvidia-settings always displays that. Just ignore.
The prime profiles menu is only available is a special patched ubuntu version of nvidia-settings, depending on driver repo you don’t have that.
“Display Devices: none” comes from the fact that the internal display is connected to the intel igpu, not the nvidia gpu, might change if you connect an external monitor. That’s also the reason for “PRIME Display” being displayed. Everything you see is expected.

Thanks for the explanation. But I am puzzled by the following:

since the system was rebooted after doing sudo prime-select nvidia; and after the reboot, it was verified that prime-select was nvidia:

~$ sudo prime-select query

The information in the previous post was collected after the reboot and verification of prime-select.

So what? The nvidia gpu is now primary gpu but the internal display is still physically connected to and driven by the intel gpu. Just the picture is transfered from the nvidia to the intel gpu. which is called “prime”.