Hi,
here is the gnucash.trace generated by one complete session (start,
overriding lock message, close):
----------------------------------------------------------
* 08:47:27 CRIT <gnc.backend.dbi> [pgsql_error_fn()] DBI error:
FEHLER: Relation »gnclock« existiert bereits
* 08:47:27 CRIT <gnc.backend.dbi> gnc_dbi_set_error: assertion
`dbi_conn != NULL' failed
* 08:47:28 CRIT <gnc.backend.dbi> [pgsql_error_fn()] DBI error:
FEHLER: Relation »gnclock« existiert bereits
* 08:47:28 CRIT <gnc.backend.dbi> gnc_dbi_set_error: assertion
`dbi_conn != NULL' failed
* 08:47:28 WARN <qof.engine> [gnc_iso8601_to_timespec_gmt()] mktime
failed to handle daylight saving: tm_hour=0 tm_year=70 tm_min=0 tm_sec=0
tm_isdst=-1 for string=1970-01-01 00:00:00
..... ~4500 Entrys like the above
* 08:48:08 WARN <gnc.backend.dbi> [gnc_dbi_unlock()] No lock table in
database, so not unlocking it.
----------------------------------------------------------
can it be, that gnucash tries to create the lock table (not only the
lock entry) in each session ?
regards,
Johann
Am 2010-11-26 23:17, schrieb John Ralls:
On Nov 26, 2010, at 1:04 PM, Johann Wöckinger wrote:
Hi,
ok, here are the results:
after launch, while locked popup is displayed:
hostname | pid
----------+------
orion | 3364
after dismissing the dialog by selecting open, though:
hostname | pid
----------+-------
orion | 28168
after closing gnucash:
hostname | pid
----------+-------
orion | 28168
Aha. So the lock record isn't getting deleted. Is there a warning about that at
the end of the gnucash.trace?
Regards,
John Ralls
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
