On 09/27/2011 12:32 AM, Dougie Nisbet wrote:
On 26/09/2011 20:08, Eric Gregory wrote:
Shotwell configuration is stored in a few places. If you remove
~/.shotwell that should take care of everything important; you might
also use dconf editor to remove (or reset) the /apps/shotwell prefs.
I've installed the package dconf-tools which gives me donf-editor, and
I can see a couple of shotwell settings, even after uninstalling and
deleting. But they look quite innocuous and although I can see an
option to 'reset to defaults' I can't see an option to delete them.
Since I used to be able to run shotwell on my netbook and now I can't,
it's clearly something I've introduced or changed. Perhaps there's
some subtle dependency I've missed or removed. It's frustrating
though. It would be great to be able to totally purge shotwell and
start again.
I think the best way to debug this is to figure out what Shotwell is
doing while consuming 100% CPU. In other words, we need a stack trace.
There are two ways you could get this. You could run Shotwell under
gdb, then press Ctrl+C during the 100% CPU loop and use the 'where'
command to see where it was interrupted. Or you could install the
Sysprof profiler and gather profiling data as Shotwell runs; this should
also reveal the stack trace. In either case you'll want to have debug
symbols installed for important system libraries (GTK, GLib). If you do
this and report the trace to us, it may give insight into what's going
on. Otherwise, as Eric said, we really don't have much to go on here.
adam
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
