This continues to be a problem in 0.18.
I set the library location in 'preferences', then imported photos.
Shotwell then crashed catastrophically (i.e. it actually crashed the OS).
Connecting a camera with an empty memory card seems to cause the crash.
When I restarted shotwell, the library locati
We'v e been unable to reproduce this since it was reported, although we
have some suspicion that the GConf to GSettings conversion is behind
some of the reported problems.
I noticed you're running Shotwell 0.12.3. That's quite old and a great
deal of bug work has been done in the interim. I reco
This also affects me. I can not change the default ~/Pictures to
~/Pictures/Camera. Although I have my Pictures directory symlinked to
another hard drive, I also tried setting it to a folder local to the
home drive and I had no luck.
3.2.0-40-generic
Ubuntu 12.04
Shotwell 0.12.3
--
You receive
Unfortunately, we're unable to reproduce this here, even when using the
setup conditions suggested in comments twelve and fifteen (along with
things like deliberately omitting the trailing slash, using '~' instead
of typing out the full path to my home directory, etc.).
For those of you still affe
I can confirm having the bug in 12.04. However, I also managed to get
rid of this.
After setting directory to ~/Pictures/Photos via dconf-settings,
Shotwell behaved as in comment #12, the input field in preferences is
set to "(None)". The structure of the Photos dir was:
2005/
2006/
...
2
I can confirm this is affecting me on 12.10 as well. I have edited my
XDG_PICTURES_DIR (.config/user-dirs.dir) to use a different folder: ~/My
Media/Pictures. I was using F-Spot before but choose not to run the auto
import as over time I had accidentally ended up with two Photo folders
on my system
So, I guess this bug should be summed up as:
Setting the import directory to a path that already contains photos may
fail silently, with Shotwell setting it back either to ~/Pictures or to
(None).
Note that this happened to me after I deleted ~/.shotwell. My (very
uneducated) guess is that the pr
OK, thanks Eric. I made some progress:
gsettings set org.yorba.shotwell.preferences.files auto-import false
This seems to work. Box "watch library directory for new files" is now
unchecked in the preferences dialog, and Shotwell doesn't attempt to import
files when started.
gsettings set org.yo
Pantelis, Shotwell uses dconf now, not gconf. So you need to use
gsettings and dconf-editor to get at Shotwell's stored settings.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/97563
Hi Eric,
~/Pictures/shotwell exists and has correct permissions
gconftool reports that /apps/shotwell/preferences/files/import_dir is set to
~/Pictures/shotwell
gconftool also reports that /apps/shotwell/preferences/files/auto_import is set
to false
However, in its preferences dialog, Shotwell
Yes, ~/Pictures/Photos exists and contains lots and lots of photos from
before Shotwell went senile ;)
I guess one detail I didn't mention is that _some_ folders in my home
folder are symlinks to a larger hard drive (while everything else lives
on an SSD). ~/Pictures and ~/Pictures/Photos, however
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shotwell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs
For those of you experiencing this issue, does the directory you're
pointing to actually exist? AFAIK Shotwell will not create a new folder
for you; if the folder doesn't exist, it will switch to the child
folder.
So for example if you point it at ~/Pictures/shotwell, but only
~/Pictures exists,
I'm changing this back to New because I really think someone should take
a look at it. Many people (me included) store images in ~/Pictures that
they don't want Shotwell to index. Not being able to change the import
directory makes the software effectively useless for them.
** Changed in: shotwell
I can also confirm this. I tried chaning the import directory to
~/Pictures/shotwell multiple times, using both the configuration dialog
and gconf-editor, but Shotwell keeps setting it directory back to
~/Pictures every single time.
--
You received this bug notification because you are a member o
I can confirm the similar problem here, ubuntu 12.04 amd 64, shotwell
0.12.3-0ubuntu0.1, the problem here is the default import directory is
my home, and it is can not changed, even in gconf or the edit preference
window.
--
You received this bug notification because you are a member of Ubuntu
De
I can confirm the same problem. After I changed the import
directory/library location in preferences, Shotwell somehow changed it
back to ~/Pictures some other time I opened it again. However, this is a
rather random behaviour since I can't always reproduce the issue even
after I've done some editi
** Changed in: shotwell (Ubuntu)
Status: New => Triaged
** Changed in: shotwell (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/975636
Odd. I'm also on 12.04 but am completely unable to reproduce this.
I've ticketed this upstream:
http://redmine.yorba.org/issues/5027
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/
** Attachment added: "Screenshot from 2012-04-06 17:45:14.png"
https://bugs.launchpad.net/bugs/975636/+attachment/3019912/+files/Screenshot%20from%202012-04-06%2017%3A45%3A14.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shot
20 matches
Mail list logo
