Bug 312587

Summary:	Crashes after Hibernate Using MySQL backend
Product:	[Applications] kmymoney	Reporter:	michael papet <mpapet>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	fvilas
Priority:	NOR
Version:	4.6.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:	4.6.3

Description michael papet 2013-01-04 04:53:31 UTC

Error in function void MyMoneyStorageSql::close(bool) : starting commit unit Driver = QMYSQL, Host = 192.168.1.33, User = mythtv, Database = kmymoney Driver Error: QMYSQL: Unable to begin transaction Database Error No 2013: Lost connection to MySQL server during query Text: Lost connection to MySQL server during query QMYSQL: Unable to begin transaction Error type 2 Executed: Query error No -1: Driver not loaded Driver not loaded Error type 1 void MyMoneyStorageSql::close(bool) in file /build/buildd-kmymoney_4.6.2-3.1-amd64-N_PinZ/kmymoney-4.6.2/kmymoney/mymoney/storage/mymoneystoragesql.cpp line 870

Reproducible: Always

Steps to Reproduce:
1. Launch kmymoney
2. Use Kmymoney4 a bit.
3.  Put the laptop into hibernation. (eg. the network connection drops)
4.  Wake the laptop up with kmymoney4 still running.
5. Crash
Actual Results:  
Error in function void MyMoneyStorageSql::close(bool) : starting commit unit Driver = QMYSQL, Host = 192.168.15.33, User = mythtv, Database = kmymoney Driver Error: QMYSQL: Unable to begin transaction Database Error No 2013: Lost connection to MySQL server during query Text: Lost connection to MySQL server during query QMYSQL: Unable to begin transaction Error type 2 Executed: Query error No -1: Driver not loaded Driver not loaded Error type 1 void MyMoneyStorageSql::close(bool) in file /build/buildd-kmymoney_4.6.2-3.1-amd64-N_PinZ/kmymoney-4.6.2/kmymoney/mymoney/storage/mymoneystoragesql.cpp line 870

Expected Results:  
The application needs to re-initialize the database connection somehow when the network connection is broken.  Not a simple task.

Great app bugs and all!

Comment 1 Fernando Vilas 2013-01-07 00:19:08 UTC

This looks like the same bug as 294046 (reported by you about a year ago). It was fixed in 4.6.3. Can you retry with the latest version and re-open the bug if it is still a problem.

Comment 2 Fernando Vilas 2013-01-07 00:19:27 UTC


*** This bug has been marked as a duplicate of bug 294046 ***