Hello everybody,
I have facing the following problem:
Shotwell is apparently not starting unless I start it from the terminal
using 'shotwell --no-startup-progress'.
If no option is specified, the 'Loading Shotwell' window stays stuck
around 50% forever and eating 100% CPU (I tried leaving it there for a
hour before killing it).
Of course this didn't just suddenly started. I have installed a faster
drive on my computer and reinstalled my system, and moved my home folder
to the new drive. However I have left part of the photos on the old
drive, making symbolic links to 'left behind' folders.
My 'Pictures folder', the one that Shotwell point at, is now:
2011->/extra/michele/Pictures/Camera/2011
2012->/extra/michele/Pictures/Camera/2012
2013
where '/extra' is the mount point of my old home folder and '2013' is
the only folder that I have moved on the new disk for the moment.
I have perfectly replicated the folders structure in my new home. And
when I start with 'shotwell --no-startup-progress' all the photos are
there, all the albums are there and Shotwell works as magnificently as
always.
Shortly:
$ shotwell -->> 'Loading window' stuck, CPU at 100%, Shotwell has
apparently no intention to start
$ shotwell --no-startup-progress -->> Shotwell starts in seconds and
everything seems fine.
I'm running Ubuntu 12.10 64bit, Shotwell is updated from the Yorba's PPA.
Any idea, please?
Any way to see what Shotwell is really doing during the load window? (is
there any '--verbose' option?)
Thank you,
Michele
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
