Re: [kmymoney] [Bug 469836] After update kmymoney doesn't start anymore!
On Sonntag, 21. Mai 2023 09:28:59 CEST Herwig Janssen via KMyMoney-devel wrote: > https://bugs.kde.org/show_bug.cgi?id=469836 > > --- Comment #2 from Herwig Janssen --- > Hello, > > I am using the following version of Windows: > Windows 10 > > > Then I tried to start KMM from a command line/console. In "cmd" the following > error message appears afterwards: > > C:\Users\Herwig\AppData\Local\kmymoney\bin>kmymoney.exe > > C:\Users\Herwig\AppData\Local\kmymoney\bin>WebConnect: Try to connect to > WebConnect server > WebConnect: Connect to server failed > WebConnect: Running in server mode [...] > Setting a QCompleter on non-editable QComboBox is not allowed. > Setting a QCompleter on non-editable QComboBox is not allowed. > Could not find QtWebEngineProcess.exe Found this in one or two of the other blueprints in their createPackage section: self.addExecutableFilter(r"bin/(?!(marble-qt|QtWebEngineProcess)).*") Not sure if that is required in adapted form in our blueprint. -- Regards Thomas Baumgart - If a cluttered desk is characteristic of a cluttered mind, what does an empty desk mean 1 a b X - signature.asc Description: This is a digitally signed message part.
Re: [kmymoney] [Bug 469836] After update kmymoney doesn't start anymore!
On 5/22/23 05:27, Thomas Baumgart via KMyMoney-devel wrote: On Sonntag, 21. Mai 2023 09:28:59 CEST Herwig Janssen via KMyMoney-devel wrote: https://bugs.kde.org/show_bug.cgi?id=469836 --- Comment #2 from Herwig Janssen --- Hello, I am using the following version of Windows: Windows 10 Then I tried to start KMM from a command line/console. In "cmd" the following error message appears afterwards: C:\Users\Herwig\AppData\Local\kmymoney\bin>kmymoney.exe C:\Users\Herwig\AppData\Local\kmymoney\bin>WebConnect: Try to connect to WebConnect server WebConnect: Connect to server failed WebConnect: Running in server mode [...] Setting a QCompleter on non-editable QComboBox is not allowed. Setting a QCompleter on non-editable QComboBox is not allowed. Could not find QtWebEngineProcess.exe Found this in one or two of the other blueprints in their createPackage section: self.addExecutableFilter(r"bin/(?!(marble-qt|QtWebEngineProcess)).*") Not sure if that is required in adapted form in our blueprint. It certainly seems worth trying. There seem to be a bunch of recent reports of KMM hanging or failing, on both Linux and Windows, and it's not clear to me how many different problems there actually are. Jack
Re: Using KMyMoney on a device other than my Kubuntu desktop
On 2023.05.18 10:13, Footer via KMyMoney-devel wrote: Greetings, I'm a long time KMyMoney user, some 17+ years! I've loved this program since the day I discovered and installed it, and for that, I give the KMyMoney team a HUGE Thank You!! I am recently retired and traveling more now, so I am away from my desktop and looking for options to use KMyMoney while away from home. The devices I currently own in addition to my desktop: Pixel 7 Pro Chromebook running ChromeOS JingPad (pretty much just a paperweight at this point) Contemplating purchase of the new Pixel Tablet Is it possible to install KMyMoney on any of these devices or is there some other way I should explore for keeping my finances up-to-date on the go? I am not opposed to purchasing another portable device (tablet or laptop) if I could get this solution to work. KDE Slimbook perhaps?? Apologies in advance if this topic is covered elsewhere, I have only just started researching it and haven't found any solutions yet. Thanks! Terry foo...@gmail.com Current Desktop specs: KMyMoney Version 5.0.8 Kubuntu 20.04.6 LTS (Focal Fossa) Linux 5.15.0 KDE Plasma 5.18.8 The first thing I would point out is that 5.0.8 is quite old at this point. The current released version is 5.1.3. It is not absolutely required to upgrade, but if you want to do so, and there is no packaged version for your distribution, you can always use an appImage. (See https://kmymoney.org/appimage.html for more information.) In terms of remote use, KMyMoney should work fine on any laptop. However, note that you have to be very careful about which data file you use. If you copy your .kmy file from desktop to laptop and add/change any data, you need to remember to copy the file back to the desktop. There is no current way to coordinate or synchronize the use of two different files. Next, there is no version available for Android or iOS. It might be interesting to see if it could be built for ChromeOS, but my understanding (rather limited) is that would be as much work as building for Android (if not exactly the same - with the difference of local data storage instead of remote. What has been suggested in the past is to just use some note taking app to record your purchases/transactions in a csv format, and then import when you are back at your desktop. Jack
Re: appimages and windows issues
On 2023.05.20 19:09, Jack via KMyMoney-devel wrote: On the "hanging" discussed on the user mailing list - I cannot replicate it, but the user now confirms that the master branch appimages do work for him, only the 5.1 branch appimages hang. I'm suspecting something related to Qt and WebEngine, but I still have no solid clues. On the Windows crashes - I'm trying to set up a local SUSE build system (in VirtualBox) but the instructions on the snapshots web page is apparently rather out of date. Hopefully I can puzzle it out, but if anyone can provide a quick update (just in an email if not actually updating the page) I'd appreciate it. I think I finally got a bit of a clue. The OSB Windows builds use mingw, so can't use QTWebEngine. However, trying to use QtWebKit (building either libalimia or kmymoney) it errors out with: buildinfo is broken... it says: unresolvable: nothing provides mingw64(icui18n56.dll) needed by mingw64-libqt5-qtwebkit nothing provides mingw64(icuuc56.dll) needed by mingw64-libqt5-qtwebkit These are the same errors I see looking at the OBS pages. Lots of searching suggests that the problem is a version mismatch between libqt5-qtwebkit and whatever package contains the icu libraries. However, while learning my way around zypper and yast, it looks like I had package mingw64-libicu61 installed from the mingw repository. Explicitly deleting that package (and the associated -devel one) has allowed the build to progress. I believe (but at this point am no longer certain) I had explicitly added the mingw64-libicu61 repository, so I don't know if this discovery can help with the actual OSB server configuration. I also know there is no real evidence, but I've been wondering if these two issues are somehow related. Jack
Re: appimages and windows issues
On 2023.05.22 14:42, Jack via KMyMoney-devel wrote: On 2023.05.20 19:09, Jack via KMyMoney-devel wrote: On the "hanging" discussed on the user mailing list - I cannot replicate it, but the user now confirms that the master branch appimages do work for him, only the 5.1 branch appimages hang. I'm suspecting something related to Qt and WebEngine, but I still have no solid clues. On the Windows crashes - I'm trying to set up a local SUSE build system (in VirtualBox) but the instructions on the snapshots web page is apparently rather out of date. Hopefully I can puzzle it out, but if anyone can provide a quick update (just in an email if not actually updating the page) I'd appreciate it. I think I finally got a bit of a clue. The OSB Windows builds use mingw, so can't use QTWebEngine. However, trying to use QtWebKit (building either libalimia or kmymoney) it errors out with: buildinfo is broken... it says: unresolvable: nothing provides mingw64(icui18n56.dll) needed by mingw64-libqt5-qtwebkit nothing provides mingw64(icuuc56.dll) needed by mingw64-libqt5-qtwebkit These are the same errors I see looking at the OBS pages. Lots of searching suggests that the problem is a version mismatch between libqt5-qtwebkit and whatever package contains the icu libraries. However, while learning my way around zypper and yast, it looks like I had package mingw64-libicu61 installed from the mingw repository. Explicitly deleting that package (and the associated -devel one) has allowed the build to progress. I believe (but at this point am no longer certain) I had explicitly added the mingw64-libicu61 repository, so I don't know if this discovery can help with the actual OSB server configuration. Next step. I have built kmymoney5, but trying to build the installer, it says: buildinfo is broken... it says: unresolvable: nothing provides mingw32(libgcc_s_sjlj-1.dll) needed by mingw32-cross-nsis nothing provides mingw32(libstdc++-6.dll) needed by mingw32-cross-nsis nothing provides mingw32(libwinpthread-1.dll) needed by mingw32-cross-nsis nothing provides mingw32(libz.dll) needed by mingw32-cross-nsis I can't tell why the 64 bit build is pulling in anything from mingw32. I also know there is no real evidence, but I've been wondering if these two issues are somehow related. Jack
[kmymoney] [Bug 469420] Print to PDF results in reports with "grayed out" sections, unlike in the past.
https://bugs.kde.org/show_bug.cgi?id=469420 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
[kmymoney] [Bug 468308] KmyMoney 5.1.2 crashes, using OpenSUSE 15.4 with KDE. KmyMoney v.5.1.3 runs good from Konsole.
https://bugs.kde.org/show_bug.cgi?id=468308 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are the assignee for the bug.
