Hi Grant,
Shotwell hasn't used GConf to store configuration data since version 0.11.
Versions 0.12.x and later store all of their configuration information in
GSettings. This is in-line with GNOME best practices. For what it's worth,
the source file mentioned here (gconfsettingsbackend.c) is part of the
GConf distribution, not part of Shotwell. So there may be a problem with
the GConf setup on your machine.
Since you're a Gentoo user, I'm sure you're comfortable using the command
line. If you'd like to debug this problem further, I'd recommend running
Shotwell from the command line with log output directed to the terminal.
You can do this by running the following command:
$ SHOTWELL_LOG=1 SHOTWELL_LOG_FILE=:console: shotwell
With logging turned on, the Shotwell configuration system is very verbose
about reporting changes to the configuration database. If you examine your
log file, you should see several lines like this:
L 6405 2012-11-26 12:51:59 [DBG] ConfigurationInterfaces.vala:303:
ConfigurationFacade: engine reports property
'LIBRARY_WINDOW_WIDTH' changed.
I'm curious if you see any indication of configuration activity right
before the system crashes.
Take care,
Lucas
On Sun, Nov 25, 2012 at 1:49 PM, Grant <[email protected]> wrote:
> I can import in place, but if I choose to copy to library, shotwell crashes
> like this:
>
> (shotwell:9130): GConf-CRITICAL **: gconf_engine_pop_owner_usage: assertion
> `engine->owner_use_count > 0' failed
> **
> ERROR:gconfsettingsbackend.c:205:gconf_settings_backend_remove_notifier:
> assertion failed: (notifier && g_str_equal (path, notifier->path))
> Aborted
>
> I'm using 0.13.1 on Gentoo. Should I file a bug?
>
> - Grant
> _______________________________________________
> Shotwell mailing list
> [email protected]
> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
>
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
