On 10 Sep 2014, at 19:48, Jim Nelson <jim yorba org> wrote:
Michael, I wasn't notified of the new bug. Can you send a link or a bug #?
-- Jim
I’ve been checking for a change of status on the Bugzilla site, but can’t find any trace of it.
Unfortunately, I’ve started Shotwell successfully since then, and ‘shotwell.log’ has been overwritten.
Apparently, I failed to complete the logging of the bug, and I’ll have to reproduce it, probably tomorrow morning.
I’ve been struggling to work out what it is that causes Shotwell to crash when it’s first started from cold, but eventually relents. Is there a background task that is launched by Shotwell when it first starts, and which is eventually completed for the day and no longer interferes with the normal function of Shotwell for the rest of that day?
Incidentally, there is only an occasional message on the screen relating to a crash, and it says that my computer doesn’t have enough memory for it to relay crash-related information to the developers. I’ve got 3GB allocated to this VM, which should surely be adequate, and RAM use is reportedly always < 20%.
Probably not related - I’ve noticed that the Folders section of the sidebar has two subfolders, one marked “/“ and the other “michaelhendry”.
The free descending from the first runs:
/media/psf/Home/Pictures/Shotwell Library/… and from the second:
michaelhendry/Desktop/Parallels Shared Folders/Home/Pictures/Shotwell Library/…
so both end up in the same place eventually. I don’t think any given image file is represented in both directory structures, and the tree an image ends up in relates to the computer (or VM) the image was originally incorporated into the library on (currently /media/…).
I’ll let you know when I’ve next succeeded in catching a bug in the act AND reporting it on Bugzilla, and I’ll remember to take a copy of shotwell.log at that time in case I fail to get it all recorded.
Thanks,
Michael
On Wed, Sep 10, 2014 at 12:27 AM, Michael Hendry <hendry michael gmail com> wrote:
On 9 Sep 2014, at 21:35, Jim Nelson < jim yorba org> wrote: 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)
Thanks, Jim.
I’ve installed the necessary tools, and am running Shotwell through the debugger now.
By a process of trial and error, I’ve found that repeatedly running Shotwell on a cold-booted computer will eventually allow it to get through whatever it is that causes it to crash, and allow it to run normally (albeit with a number of warning messages, depending on what I’m doing).
That’s the state of affairs at the moment - apparently normal running!
I’ll give the procedure another go tomorrow morning (it’s nearly 1 am here), when I expect the crashes will have started again (if the last few days are anything to go by), and report on my findings.
Regards,
Michael
PS Have submitted a bug report on Bugzilla, as suggested.
It wasn’t clear from the Bugzilla interface that both files would be submitted along with the report - I selected them individually, but only the second one’s name was visible when I hit the commit button.
Michael
-- Jim
On Sat, Sep 6, 2014 at 11:58 PM, Michael Hendry <hendry michael gmail com> wrote:
On 4 Sep 2014, at 17:30, Michael Hendry < hendry michael gmail com> wrote:
On 4 Sep 2014, at 16:59, Michael Hendry <hendry michael gmail com> 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
|
