Shotwell 0.10 Released

Yorba has released version 0.10 of Shotwell, our digital photo organizer.  This release includes the following changes:

  • Dynamic view of photo library through saved search feature
  • Automatic database backup
  • Adjust date/time for videos
  • Added Valadate testing framework
  • Shotwell video thumbnailer eliminates Totem dependency
  • Crop tool is now more flexible
  • Filenames no longer used as titles on Facebook and Picasa uploads
  • Translation corrections
  • Many bug fixes
Creating a search

Download a source tarball from the Shotwell home page at:
http://www.yorba.org/shotwell/

Binaries of both packages for Ubuntu Natty and Maverick are available at Yorba’s Launchpad PPA:
https://launchpad.net/~yorba/+archive/ppa

17 thoughts on “Shotwell 0.10 Released”

  1. After installing the latest release from this site using your PPA, when I launch Shotwell the Welcome window, the3 screen freezes and my cpu jumps to 100% and system memory jumps to 60%. This is not proper behaviour, how do I resolve this?

  2. What is the purpose of not depending on Totem ? Had Totem some trouble rendering Thumbnails ?
    Totem is part of GNOME, do Shotwell aims to be desktop agnostic ?
    Or maybe is it related to Ubuntu’s decision to integrate Banshee ?
    Thanks and keep on your great work (and don’t forget bug#2498 for later releases please 😉

    1. We only depended on Totem for generating video thumbnails. For various reasons, this upset some users, so we developed our own video thumbnailer (based largely on GStreamer sample code) as a replacement.

      1. thank you for the kind answer though it’s a bit weird to read on the ticket “some of our users understandable don’t like Shotwell’s dependency on Totem and all the packages that Totem in turn depends on” without pointing any references…

  3. Shotwell freezes on startup from sime time, leaving me with unusable pictures database. I tried to uninstall and reinstall it, moving the shotwell dir etc (linux mint debian edition) with no success… 🙁

    Should I file a bug?

      1. The stack trace indicates a crash somewhere within libcairo. Could you install debug symbols for libcairo, libgtk-x11, and libaurora — then run this test again?

        1. Thanks for the reply.
          I’m not really sure of which packetes I have to install since

          * apt-cache search libcairo | grep dbg
          libcairo2-dbg – The Cairo 2D vector graphics library (debugging symbols)

          * apt-cache search libgtk | grep x11
          libgtkglextmm-x11-1.2-0 – C++ bindings for GtkGLExt (Shared libraries)
          libgtkglextmm-x11-1.2-dev – C++ bindings for GtkGLExt (Development files)
          libgtkglextmm-x11-1.2-doc – C++ bindings for GtkGLExt (Documentation)

          * apt-cache search aurora| grep dbg
          libigstk4-dbg – debugging symbols for libigstk4

          I installed libcairo2-dbg, libgtkglextmm-x11-1.2-dev and libigstk4-dbg.

          Here’s the result after that:
          http://88.43.36.100/~mrjive/tmp/shotwell/shotwell.gdb
          http://88.43.36.100/~mrjive/tmp/shotwell/shotwell.log

          Thanks again!

          1. Something’s wrong with the debugger output there. Seems like a breakpoint got set accidentally?

            In general you should only have to install the “dbg” packages to get debugging symbols. Although some packages may not have them, as you noticed.

  4. Don’t really know why, but latest upgrade solved the issue (Shotwell 0.11.1 on linux mint debian edition)

    Thanks anyway!

    davide

Comments are closed.

Leave a Reply

Your email address will not be published. Required fields are marked *