The scrolledwindow/scrollbar warnings may be a red herring; sometimes
these kinds of warnings appear with different themes/custom GTK
modifications (i.e. global menu). I don't recall anyone else reporting
them.
The Directory Subimage / top pointer / IFD warnings are from Exiv2 and
are nothing to worry about.
The "unable to fetch preview" warnings indicate what you think they
indicate, your thumbnails are being generated on-demand.
The get_pixbuf_with_options assertion is, obviously, an issue. The
source of the issue appears to be:
gdk_pixbuf_scale_simple: assertion 'GDK_IS_PIXBUF (src)
If you could follow the instructions at
https://wiki.gnome.org/Apps/Shotwell/ReportingABug, that would be a
huge help.
-- Jim
On Sat, Sep 6, 2014 at 11:58 PM, Michael Hendry
<[email protected]> wrote:
On 4 Sep 2014, at 17:30, Michael Hendry <[email protected]>
wrote:
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
I thought Shotwell had mended itself yesterday, as it didn’t crash
for many hours, and I was able to do a lot of tidying up and tagging
jobs.
Full of confidence, I shut Shotwell down and rebooted Ubuntu - the
crashes came back.
Starting up my iMac this morning, I had another go, and here’s what
happened (I started it using the command-line “date >>
crash.log;shotwell 2>>crash.log;date >> crash.log”).
Sun Sep 7 07:28:54 BST 2014
(shotwell:2390): Gtk-WARNING **: GtkScrolledWindow 0x124a8180 is
mapped but visible child GtkScrollbar 0x98db798 is not mapped
(shotwell:2390): Gtk-WARNING **: GtkScrolledWindow 0x124a8180 is
mapped but visible child GtkScrollbar 0x98db798 is not mapped
(shotwell:2390): Gtk-WARNING **: GtkScrolledWindow 0x124a8180 is
mapped but visible child GtkScrollbar 0x98db798 is not mapped
(shotwell:2390): Gtk-WARNING **: GtkScrolledWindow 0x124a8180 is
mapped but visible child GtkScrollbar 0x98db798 is not mapped
(shotwell:2390): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple:
assertion 'GDK_IS_PIXBUF (src)' failed
L 2390 2014-09-07 07:30:21 [CRT] dimensions_for_pixbuf: assertion
'GDK_IS_PIXBUF (pixbuf)' failed
**
ERROR:/build/buildd/shotwell-0.18.1/src/Photo.vala:3428:photo_get_pixbuf_with_options:
assertion failed:
(scaled_to_viewport.approx_equals(Dimensions.for_pixbuf(pixbuf),
SCALING_FUDGE))
Sun Sep 7 07:30:28 BST 2014
Sun Sep 7 07:33:18 BST 2014
**
ERROR:/build/buildd/shotwell-0.18.1/src/Photo.vala:3330:photo_get_pixbuf_with_options:
assertion failed: (pixbuf != null)
Sun Sep 7 07:36:21 BST 2014
My (apparently) successful run yesterday generated a large number of
warnings like those above, and also...
L 8654 2014-09-06 15:02:36 [CRT] Directory SubImage1: Next pointer is
out of bounds; ignored.
…
L 5689 2014-09-06 13:06:31 [CRT] Iop pointer references previously
read Photo directory. Ignored.
L 5689 2014-09-06 13:06:31 [CRT] Directory Thumbnail: IFD exceeds
data buffer, cannot read entry count.
…
Part of the tidying up process I went through yesterday involved the
recreation of about 15000 thumbnails, which I dealt with by scrolling
slowly through the whole library, following the generation of lots of
messages like this:
L 3922 2014-09-05 18:35:53 [CRT] EventDirectoryItem.vala:109: Unable
to fetch preview for Event [669/88896] Sun 7 Jan, 2001: Failed to
open file
'/home/michaelhendry/.cache/shotwell/thumbs/thumbs360/thumb0000000000006702.jpg':
No such file or directory
(I had copied the database across from a previous installation of
Ubuntu, but hadn’t copied the thumbnails).
I have a suspicion that the problem is with the photo.db database -
is there a utility or a procedure which would allow me to check its
integrity?
I have spent many tens of hours on my Shotwell library, and am
prepared to spend many more if necessary, to continue to use it.
Michael
_______________________________________________
shotwell-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/shotwell-list
