On Nov 25, 2010, at 1:44 PM, Johann Wöckinger wrote: > Yes, it's also in 2.3.17. > > Am 2010-11-25 21:28, schrieb John Ralls: >> On Nov 24, 2010, at 11:21 AM, Johann Wöckinger wrote: >> >> >>> Hello, >>> >>> since Version 2.3.16RC1, I notice the following message popup on starting >>> gnucash: >>> >>> GnuCash could not get exclusive write permission to postgres://......... >>> >>> with some explaination for reasons for that. >>> >>> It seems, that gnucash does not delete the lock entry in the database >>> (table: gnclock) when closing the application (I found the lock entry still >>> in the database table after closing gnucash), so it comes up with this >>> warning on startup, which can be overridden on selecting "open" - but its >>> somewhat annoying. >>> >>> This behaviour was not observed in former releases of the 2.3.x series. >>> >>> Would be nice to have the former behavior. >>> >> Have you seen this with 2.3.17? It sounds like a duplicate of >> https://bugzilla.gnome.org/show_bug.cgi?id=634392, which was fixed for >> 2.3.17.
Well, that's annoying, because I don't see the problem on my development system. Are you connecting to a local (on the same machine) or network psql server? On what OS are you running Gnucash? If you're connecting to psql on a different machine, what OS is it running? What version of psql? Please start gnucash and find its PID and the hostname of the machine running Gnucash. Then quit Gnucash and, from psql, do "select * from gnclock". Are the hostnames and PIDs the same? At the end of gnucash.trace is there a warning about not finding the lock? Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
