On 4 Sep 2014, at 16:59, Michael Hendry <[email protected]> wrote:
> I’ve recently upgraded to Ubuntu 14.04, and installed Shotwell 0.18.1. > > After a short spell of “Updating library” there is a period during which I > can use Shotwell, but after a total of about a minute, the display greys out, > and the program shuts down. > > If I run Shotwell from the command line I get this: > > > (shotwell:3394): Gtk-WARNING **: GtkScrolledWindow 0x11707130 is mapped but > visible child GtkScrollbar 0x8b54798 is not mapped > > (shotwell:3394): Gtk-WARNING **: GtkScrolledWindow 0x11707130 is mapped but > visible child GtkScrollbar 0x8b54798 is not mapped > > (shotwell:3394): Gtk-WARNING **: GtkScrolledWindow 0x11707130 is mapped but > visible child GtkScrollbar 0x8b54798 is not mapped > > (shotwell:3394): Gtk-WARNING **: GtkScrolledWindow 0x11707130 is mapped but > visible child GtkScrollbar 0x8b54798 is not mapped > ** > ERROR:/build/buildd/shotwell-0.18.1/src/Photo.vala:3330:photo_get_pixbuf_with_options: > assertion failed: (pixbuf != null) > Aborted (core dumped) > > > Any advice? Suggestions as to further investigation? > > Regards > > Michael > Here are a couple of further examples... michaelhendry@ubuntu:~$ date;shotwell;date Thu Sep 4 17:20:55 BST 2014 (shotwell:2483): Gtk-WARNING **: GtkScrolledWindow 0x1173c168 is mapped but visible child GtkScrollbar 0x8b88798 is not mapped (shotwell:2483): Gtk-WARNING **: GtkScrolledWindow 0x1173c168 is mapped but visible child GtkScrollbar 0x8b88798 is not mapped ** ERROR:/build/buildd/shotwell-0.18.1/src/Photo.vala:3330:photo_get_pixbuf_with_options: assertion failed: (pixbuf != null) Aborted (core dumped) Thu Sep 4 17:22:15 BST 2014 michaelhendry@ubuntu:~$ date;shotwell;date Thu Sep 4 17:22:28 BST 2014 ** ERROR:/build/buildd/shotwell-0.18.1/src/Photo.vala:3330:photo_get_pixbuf_with_options: assertion failed: (pixbuf != null) Aborted (core dumped) Thu Sep 4 17:24:34 BST 2014 michaelhendry@ubuntu:~$ …which might help to explain the problem. Looking at memory use - when Shotwell is first run, about 12% of the available RAM is taken up, and this doesn’t go back down after the crash. Subsequent runs of Shotwell seem not to affect RAM usage, which remains around 12%. Michael _______________________________________________ shotwell-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/shotwell-list
