You are not logged in.
Hi,
kmymoney doesn't behave correctly, it shows a partial blank welcome screen on my system that is configured to run GNOME on wayland with Nvidia drivers (GeForce GTX 1060). It also display a bunch of following errors :
[8333:8376:0603/102018.586466:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT
[8333:8376:0603/102018.586509:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[8333:8376:0603/102018.586520:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[8333:8376:0603/102018.586531:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub
kmymoney depends on qt5-webengine and after some tests, I found that ghostwriter that also depends on qt5-webengine displays the same error. But it is not the case for nextcloud-client nor scenarist both depending also on qt5-webengine.
All the packages (kmymoney, GNOME, wayland, nvidia drivers 550.78-7) come from arch standard repositories (no test repo) and are up to date.
The system is configured for wayland with Nvidia drivers as explained in the Wiki.
GRUB_CMDLINE_LINUX_DEFAULT="nvidia.NVreg_PreserveVideoMemoryAllocations=1 nvidia-drm.modeset=1 nvidia-drm.fbdev=1 loglevel=3 quiet"
...
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)
...
BINARIES=(setfont)
...
# fja 09/11/2023 (removing kms prevents nouveau to be in initramfs)
HOOKS=(base udev autodetect microcode modconf keyboard keymap consolefont block filesystems fsck)
...
QT_QPA_PLATFORM="wayland;xcb"
LIBVA_DRIVER_NAME=nvidia
Launching kmymoney through Xwayland (QT_QPA_PLATFORM="xcb") doesn't work either ; menus and icons zones are rapidly replaced with black areas).
Up to now, the only solution I found to use kmymoney is to login with Xorg GNOME session but it is awkward.
I'll appreciate any help to use kmymoney
Last edited by farfouille64 (2024-06-15 13:36:56)
Offline
Unfortunately, the update of Nvidia driver package to version 550.90.07-1 doesn't solve the problem for native wayland or through Xwayland.
Offline
There are many reports of nvidia 550 having issues , try nvidia 535 from AUR .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
After installing nvidia 535 from AUR, kmymoney still shows the same errors in pure wayland but it seems to work using xwayland (QT_QPA_PLATFORM="xcb").
I will give a try with nouveau driver because I don't feel confident with nvidia drivers coming from AUR.
Many thanks for your help.
Offline
Hi,
I might have a better solution for this issue. Even though I have only tried it on nixos, I'm rather certain it will also work on arch and other distros, and this thread is what people will find on google when they try to start kmymoney on a wayland + NVIDIA combination.
I'm also on an NVIDIA GPU on hyprland (wayland) with recent drivers and I'm confident this is a GPU driver related issue.
Try starting kmymoney with:
QMLSCENE_DEVICE=softwarecontext QT_OPENGL=software kmymoney
This will disable GPU accelearation (idea from Reddit), but it will still run natively on wayland (confirmed by looking at hyprctl clients).
I found this by launching kmymoney from an ubuntu distrobox which surprisingly worked, while the official package didn't. I figured that this is probably due to distrobox containers not having GPU acceleration enabled, hence I looked how to disable it.
I also tested ghostwriter (which was mentioned in the first post) and it does work as well (it even brings a --disable-gpu command line switch which does it for you)
Hope this helps!
Sidenote: Other applications suffering from this issue like Renderdoc (Github) or Jellyfin (Github) might also work like this but I doubt that any GPU intense application will perform nicely with doftware rendering. For kmymoney I don't see any drawbacks.
Offline
Try starting kmymoney with:
QMLSCENE_DEVICE=softwarecontext QT_OPENGL=software kmymoney
I can confirm that this solution also works on my up to date Arch installation.
Thank you LordOfCode
Offline