Bug 310063 - saving mysql database enters mysql, and immediately come back to kmymoney register
Summary: saving mysql database enters mysql, and immediately come back to kmymoney reg...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: database (show other bugs)
Version: 4.6.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
: 324325 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-11-13 23:11 UTC by Russ Fineman
Modified: 2023-02-17 03:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Russ Fineman 2012-11-13 23:11:15 UTC
Enter data in check register (from mysql database on startup) and when done entering data, select file-->Save As Database. After selecting db and inputting password. Kmy money goes out to db abd immediately comes back, no error message. If you enter db from phpmyadmin, the transaction table id empty. If you try again same thing, shutdown Kmymoney and restart from .kmy file, then save as database it writes all data. This does not happen everytime.

Reproducible: Sometimes

Steps to Reproduce:
1. enter database on startup.
2. enter tranactions and save as kmy file.
3. select File save as database and enter Id and password, save
4. Brief connection to db occurs.
5. if you check tranaction file afterward with phpmyadmin or mannual from command line the tranaction table is empty.
6. shutdown kmymoney and restart it (starts fro .kmy file
7. select save as database and then file-->save as database, Enter ID and password, and save, it correctly saves the kmymoney system.


Actual Results:  
Empty tranaction file some times. If you restart kmymoney from database the ledger is blank. 

No kmymoney errors are reported within kmymoney.

Expected Results:  
All data be saved correctly.

No error entries in mysql log or system log.
Comment 1 Cristian Oneț 2014-07-31 08:27:10 UTC
*** Bug 324325 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-11-12 02:55:02 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:49:58 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-18 02:40:50 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-02-02 05:00:40 UTC
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!
Comment 6 Bug Janitor Service 2023-02-17 03:48:30 UTC
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!