Op dinsdag 27 december 2022 17:25:42 CET schreef Jeff:
> On 27/12/2022 16:21, Geert Janssens wrote:
> > Is there a way to get gnucash 4.13 installed on your system (and not via
> > flatpak ?) That would be another useful test.
>
>
> I just built a deb for 4.13 and indeed the problem is fixed.
>
On 27/12/2022 16:21, Geert Janssens wrote:
Can you post the output of
cd /usr/share/glib-2.0/schemas
stat -c'%w %n' org.gnucash.* gschemas.compiled
2022-12-26 10:04:03.695021388 +0100
org.gnucash.GnuCash.deprecated.gschema.xml
2022-12-26 10:04:03.699021454 +0100
Op dinsdag 27 december 2022 14:27:33 CET schreef Jeff:
> On 27/12/2022 13:30, Geert Janssens wrote:
>
> > I'm not sure what the typical paths on Debian are, but on Fedora the
> > schemas for system packages end up in
> >
> > /usr/share/glib-2.0/schemas/
> >
> > While locally built schemas
On 27/12/2022 13:30, Geert Janssens wrote:
I'm not sure what the typical paths on Debian are, but on Fedora the
schemas for system packages end up in
/usr/share/glib-2.0/schemas/
While locally built schemas typically end up in
/usr/local/share/glib-2.0/schemas/
If there are schema files in
On 27/12/2022 13:41, Jeff wrote:
Thanks for the help. I guess something I did created a second gsettings
schema a couple of days ago.
In the mean time, how do I identify and remove the second gsettings schema?
Regards
Jeff
OpenPGP_signature
Description: OpenPGP digital signature
On 27/12/2022 13:30, Geert Janssens wrote:
Typically you'd have plenty of errors or warnings about this in the
gnucash.trace file (which John suggested to check for).
This was fixed for gnucash 4.13 only. So perhaps you are suffering from
this bug ?
Oh yes. In /tmp/gnucash.trace I see:
*
Hi,
There is a bug ins gnucash 4.12 and earlier in which settings may not be
retrieved/set when
there is more than one path on your system with gsettings schemas.
I'm not sure what the typical paths on Debian are, but on Fedora the schemas
for system
packages end up in
On 26/12/2022 19:26, R Losey wrote:
This is probably a dumb question, but do your preferences file still
exist? And are they readable/writeable by you? And the permissions of
the parent directory (or directories) haven't been changed?
I've been trying to work out where the changes land.
When
On 26/12/2022 18:21, john wrote:
You can make sure that you have a dbus-daemon running with `ps -A | grep
dbus-daemon`. But the Gsettings docs claim that dbus-daemon doen't need
to be running for reads, only for writes.
Yup. It's running.
org.gnucash.general is obsolete. We changed the
This is probably a dumb question, but do your preferences file still exist?
And are they readable/writeable by you? And the permissions of the parent
directory (or directories) haven't been changed?
When you make a small minor tweak to preferences, does the timestamp change
on the preferences
Am 26.12.22 um 09:51 schrieb Jeff:
On 24/12/2022 22:26, Frank H. Ellenberger wrote:
Under Linux the prefs are stored using dconf:
https://wiki.gnucash.org/wiki/Configuration_Locations#GSettings
Thanks! dconf was updated on the 17th, but I'd used it daily since then,
and when I first had
> On Dec 26, 2022, at 1:06 AM, Jeff wrote:
>
> Hi John,
>
> On 24/12/2022 22:39, john wrote:
>> The prefs are managed by dconf and I think on Linux it needs a dbus daemon
>> running. The latter's logs go in /var/log/daemon.log; I'd expect the GLib
>> gconf frontend errors to show up in the
Hi John,
On 24/12/2022 22:39, john wrote:
The prefs are managed by dconf and I think on Linux it needs a dbus daemon
running. The latter's logs go in /var/log/daemon.log; I'd expect the GLib gconf
frontend errors to show up in the trace file.
Weirdly, /var/log/daemon.log only has entries
On 24/12/2022 22:26, Frank H. Ellenberger wrote:
Under Linux the prefs are stored using dconf:
https://wiki.gnucash.org/wiki/Configuration_Locations#GSettings
Thanks! dconf was updated on the 17th, but I'd used it daily since then,
and when I first had the problems on the 22nd.
It's weird -
> On Dec 24, 2022, at 11:06 AM, Jeff wrote:
>
> Hi Michael,
>
> Thanks for the reply.
>
> On 24/12/2022 17:57, Michael or Penny Novack wrote:
>> The "what happened" is obvious, no longer accessing the files where this
>> information is stored (note recent discussions about where these are
Am 24.12.22 um 20:06 schrieb Jeff:
Hi Michael,
Thanks for the reply.
On 24/12/2022 17:57, Michael or Penny Novack wrote:
The "what happened" is obvious, no longer accessing the files where
this information is stored (note recent discussions about where these
are with regard to back-up).
Hi Michael,
Thanks for the reply.
On 24/12/2022 17:57, Michael or Penny Novack wrote:
The "what happened" is obvious, no longer accessing the files where this
information is stored (note recent discussions about where these are
with regard to back-up). You are back to the defaults.
I had
On 12/24/2022 7:00 AM, Jeff wrote:
Hi all,
I am a >10 year (daily) gnucash user, in the last few years on Debian
testing. I've not had to change the preferences in years.
A couple of days ago, gnucash stopped respecting all settings:
* the previous set of accounts was not automatically
Hi all,
I am a >10 year (daily) gnucash user, in the last few years on Debian
testing. I've not had to change the preferences in years.
A couple of days ago, gnucash stopped respecting all settings:
* the previous set of accounts was not automatically loaded
* the previous set of accounts was
19 matches
Mail list logo
