Bug 513034

Summary:	kmymoney floods syslog
Product:	[Applications] kmymoney	Reporter:	cgku
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	NEEDSINFO WAITINGFORINFO
Severity:	normal
Priority:	NOR
Version First Reported In:	5.1.3
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description cgku 2025-12-07 02:19:19 UTC

SUMMARY
Extremely high amount of syslog events

STEPS TO REPRODUCE
1. Start kmymoney

OBSERVED RESULT
The syslog is flooded with the following messages, repeated one-or-more times per second, until / is completely full.  
kmymoney [21802:21825:1206/175547.862915:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT

kmymoney [21802:21825:1206/175547.862918:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. 

kmymoney [21802:21825:1206/175547.862920:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context

kmymoney [21802:21825:1206/175547.862921:ERROR:gpu_channel.cc(449)] GouChannel: Failed to create SharedImageStub

Multiple gigabytes of logs are generated each hour the application is open.
I can readily reproduce the issue and it generates easily over 20GB/hour.

EXPECTED RESULT
Minimal syslogs under normal conditions

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Kubuntu 25.10
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.17.0-7-generic (64-bit)
Graphics Platform:  Wayland

ADDITIONAL INFORMATION
As a workaround, launch the program with the following command:
QMLSCENE_DEVICE=softwarecontext QT_OPENGL=software kmymoney

This appears to address the issue (with the added benefit of fixing the issue with the home page not displaying).  However, this triggers these apparmor message:  

audit: type=1400 audit(1765073552.135:1072): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=36422 comm="kmymoney" requested="userns_create" target="unprivileged_userns" execpath="/usr/bin/kmymoney"

audit: type=1400 audit(1765073552.137:1073): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=36432 comm="kmymoney" capability=21  capname="sys_admin"

qt.qpa.wayland: Wayland does not support QWindow::requestActivate()

Thanks for everyones' hard work.  I hope this can be squashed quickly.  Kmymoney is the best!

Comment 1 Jack 2025-12-07 20:47:24 UTC

5.1.3 is no longer maintained, so the first thing for you to try is using a newer version.  KMyMoney 5.2.1 was released in August.  If that is not available for Ubuntu 25.10, you can try using an Appimage.  The "stable" version is built from the 5.2 branch of git, which has some bug-fixes applied to the released version.
Minor point - you need to report the software versions from the Components tab of the Help/About KMyMoney dialog, as 5.1.3 still uses Qt5 and the associated KDE libraries.
Out of curiosity, is this a new installation, or did the problem start after an upgrade?  If the latter, do you know what was upgraded?  It seem likely that something in one of the underlying libraries changed  (QT5, KDE Frameworks5, ...) and although it would be interesting to know which, there is really nothing the KMM team can do about it.  You might also want to report to an Ubuntu list or forum, as I have not heard this reported elsewhere.

Comment 2 cgku 2025-12-09 00:10:59 UTC

I'm on the latest version in the repo.  I attempted to use the appimage but get FUSE errors; which may be part of a bigger issue already reported in 25.10.  I'll need more time to troubleshoot that and will respond once I have more details.
  
Understood.  Here is the information from inside kmymonkey:  KDE Frameworks Version 5.116.0, Qt Version 5.15.17 (built against 5.15.17).

This was first noticed after upgrading the OS from Kubuntu 25.04 to 25.10.  This was a major release update.  Hundreds have updates were done.

Thanks!

Comment 3 Jack 2025-12-09 00:24:41 UTC

I would consider reporting the FUSE issues to Ubuntu, if you haven't already.  Have you seen those errors with anything other than an Appimage?
Based on no real info, I would not be surprised if the Appimage complained due to any incompatibility with fuse.  On my Gentoo system, I have both fuse versions 2.9.9 and 3.17.4 installed, so the appimage likely depends on one of them, and if Ubuntu upgraded, that may well lead to the problems you see.
I would also consider reporting the KMyMoney failure to Ubuntu, and it seems more likely to me that it is triggered by something upgraded between 25.04 and 25.10.  I'm wondering whether or not they actually rebuilt KMyMoney for all the new/u;graded libraries.

Comment 4 Bug Janitor Service 2025-12-24 03:46:35 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!