Hi Joe,

You can turn off metadata writing in ubuntu 11.10, by unsetting a
dconf key. To do this, first make sure that you have installed the
dconf-tools package. Next, open a terminal window and execute the
command:

$ dconf-editor

When the dconf-editor opens, in the left-hand navigation tree,
navigate to apps > shotwell > preferences > files. In the main pane,
you should see a list of all of the configuration options for the
shotwell.preferences.files schema. One of those options is titled
"commit-metadata." Uncheck the box to the right to disable the option.
This will turn metadata writing off and should allow you to launch
Shotwell normally.

Lucas


On Tue, Nov 8, 2011 at 3:57 AM, Joe Irvine <[email protected]> wrote:
> Good call. It appears to be a certain photo. How do I turn off the metadata
> writes when I can't get Shotwell to launch? Is there a way to remove this
> tag change from the list of changes to be written so I can skip the file?
> GNU gdb (Ubuntu/Linaro 7.3-0ubuntu2) 7.3-2011.08
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-linux-gnu".
> For bug reporting instructions, please see:
> <http://bugs.launchpad.net/gdb-linaro/>...
> Reading symbols from /usr/bin/shotwell...done.
> (gdb) run
> Starting program: /usr/bin/shotwell
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb5c27b70 (LWP 3724)]
> [New Thread 0xb52ffb70 (LWP 3725)]
> [New Thread 0xb4afeb70 (LWP 3726)]
> [New Thread 0xb42fdb70 (LWP 3727)]
> [New Thread 0xb3969b70 (LWP 3728)]
> [New Thread 0xb3168b70 (LWP 3729)]
> [New Thread 0xb2967b70 (LWP 3730)]
> [New Thread 0xb2166b70 (LWP 3731)]
> [New Thread 0xb1965b70 (LWP 3732)]
> [Thread 0xb1965b70 (LWP 3732) exited]
> [Thread 0xb2967b70 (LWP 3730) exited]
> [Thread 0xb3168b70 (LWP 3729) exited]
> [Thread 0xb3969b70 (LWP 3728) exited]
> [New Thread 0xb3969b70 (LWP 3733)]
> [New Thread 0xb3168b70 (LWP 3734)]
> [Thread 0xb3168b70 (LWP 3734) exited]
> [Thread 0xb2166b70 (LWP 3731) exited]
> shotwell: tiffcomposite.cpp:1049: virtual uint32_t
> Exiv2::Internal::TiffBinaryArray::doCount() const: Assertion `typeSize != 0'
> failed.
> [New Thread 0xb2166b70 (LWP 3736)]
> [New Thread 0xb3168b70 (LWP 3737)]
> [New Thread 0xb2967b70 (LWP 3738)]
> [New Thread 0xb1965b70 (LWP 3739)]
> [New Thread 0xb06f7b70 (LWP 3740)]
> [New Thread 0xae6ffb70 (LWP 3745)]
> Program received signal SIGABRT, Aborted.
> [Switching to Thread 0xae6ffb70 (LWP 3745)]
> 0x00130416 in __kernel_vsyscall ()
> (gdb) backtrace fulll [K
> #0  0x00130416 in __kernel_vsyscall ()
> No symbol table info available.
> #1  0x00f07c8f in raise () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> #2  0x00f0b2b5 in abort () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> #3  0x00f00826 in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> #4  0x01139b1e in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #5  0x0113bfe1 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #6  0x0114f2ba in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #7  0x0114f40f in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #8  0x0113bf97 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #9  0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #10 0x0113be29 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #11 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #12 0x0113bf2d in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #13 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #14 0x0113bd2f in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #15 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #16 0x0113bd7f in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #17 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #18 0x0113bf2d in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #19 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #20 0x0113be29 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #21 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #22 0x0113bf2d in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #23 0x0113bc60 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #24 0x01145eb8 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #25 0x010bbbfd in Exiv2::ExifParser::encode(std::vector<unsigned char,
> std::allocator<unsigned char> >&, unsigned char const*, unsigned int,
> Exiv2::ByteOrder, Exiv2::ExifData const&) () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #26 0x010cff41 in ?? () from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #27 0x010d13ea in Exiv2::JpegBase::writeMetadata() ()
>    from /usr/lib/libexiv2.so.10
> No symbol table info available.
> #28 0x00187cd8 in ?? () from /usr/lib/libgexiv2.so.0
> No symbol table info available.
> #29 0x00188365 in gexiv2_metadata_save_file () from /usr/lib/libgexiv2.so.0
> No symbol table info available.
> #30 0x080fa2f3 in photo_metadata_write_to_file (self=0xe509580,
>     file=0xe57bc10, error=0xae6fefec) at src/photos/PhotoMetadata.c:1034
>         _tmp0_ = 0xe5d8b88 "/home/joe/Pictures/2009/07/05/dsc03961.jpg"
>         _tmp1_ = 0xe5d8b88 "/home/joe/Pictures/2009/07/05/dsc03961.jpg"
>         _inner_error_ = 0x0
>         __PRETTY_FUNCTION__ = "photo_metadata_write_to_file"
> #31 0x080ffdb7 in jfif_metadata_writer_real_write_metadata (base=0xdc63548,
>     metadata=0xe509580, error=0xae6ff04c) at src/photos/JfifSupport.c:1197
>         self = <optimized out>
>         _tmp0_ = 0xe57bc10
>         _tmp1_ = 0xe57bc10
>         _inner_error_ = 0x0
>         __PRETTY_FUNCTION__ = "jfif_metadata_writer_real_write_metadata"
> #32 0x080ec85f in photo_file_metadata_writer_write_metadata
> (self=0xdc63548,
>     metadata=0xe509580, error=0xae6ff04c) at
> src/photos/PhotoFileAdapter.c:745
> No locals.
> #33 0x08237cf0 in photo_persist_master_metadata (self=0x9cbb708,
>     metadata=0xe509580, state=0xae6ff0ac, error=0xae6ff0a8) at
> src/Photo.c:9248
>         _state = 0x0
>         result = 0
>         _tmp0_ = 0x9cba1b0
>         master_reader = 0x9cba1b0
>         _tmp1_ = <optimized out>
>         _tmp2_ = <optimized out>
>         _tmp3_ = <optimized out>
>         _tmp4_ = <optimized out>
>         _tmp5_ = <optimized out>
>         _tmp6_ = 0x0
>         _tmp7_ = <optimized out>
>         _tmp8_ = <optimized out>
>         _inner_error_ = 0x0
>         __PRETTY_FUNCTION__ = "photo_persist_master_metadata"
> #34 0x083012c3 in metadata_writer_commit_job_commit_master
> (error=0xae6ff0a4,
>     self=0xe57bb80) at src/MetadataWriter.c:2195
>         _tmp7_ = 0x0
>         _tmp5_ = <optimized out>
>         _tmp4_ = <optimized out>
>         _tmp6_ = 0x0
>         _tmp8_ = <optimized out>
>         _tmp1_ = <optimized out>
>         _tmp3_ = <optimized out>
>         _inner_error_ = 0x0
>         _tmp0_ = <optimized out>
>         _tmp2_ = <optimized out>
>         metadata = <optimized out>
> #35 metadata_writer_commit_job_real_execute (base=0xe57bb80)
>     at src/MetadataWriter.c:2136
>         self = 0xe57bb80
>         _inner_error_ = 0x0
> #36 0x080ba25f in background_job_execute (self=0xe57bb80)
>     at src/threads/BackgroundJob.c:579
> No locals.
> #37 0x080b8be0 in workers_thread_start (self=0xc29f750,
>     ignored=<optimized out>) at src/threads/Workers.c:449
>         job = 0xe57bb80
>         empty = 1
>         _tmp1_ = <optimized out>
>         _inner_error_ = 0x0
> #38 _workers_thread_start_gfunc (data=0xe57bb80, self=0xc29f750)
>     at src/threads/Workers.c:235
> No locals.
> #39 0x00ce0a27 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> No symbol table info available.
> #40 0x00cde5f4 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
> No symbol table info available.
> #41 0x00ec5d31 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
> No symbol table info available.
> #42 0x00fac0ce in clone () from /lib/i386-linux-gnu/libc.so.6
> No symbol table info available.
> Backtrace stopped: Not enough registers or memory available to unwind
> further
> (gdb) quit
> A debugging session is active.
> Inferior 1 [process 3721] will be killed.
> Quit anyway? (y or n)
> On Mon, Nov 7, 2011 at 3:32 PM, Lucas Beeler <[email protected]> wrote:
>>
>> Hi Joe,
>>
>> First, what do you mean by "rebuilding" the database? Do you mean
>> deleting the database file entirely and then reimporting all of your
>> photos?
>>
>> Second, the error that you quoted:
>>
>> > shotwell: tiffcomposite.cpp:1049: virtual
>> > uint32_t Exiv2::Internal::TiffBinaryArray::doCount()
>> > const: Assertion `typeSize != 0' failed.
>>
>> Doesn't look like it's database related. It looks as if Shotwell can't
>> write metadata to a certain TIFF image in your library. As a temporary
>> workaround, you might want to try turning metadata writing off. More
>> importantly though, it'd be useful to see on which photo Shotwell is
>> failing and to get a copy of that photo. We might be able to determine
>> which photo is causing Shotwell to crash by looking at Shotwell's log
>> file. To learn how to turn on logging in Shotwell and capture a log
>> file, see the "I found a bug in Shotwell. How can I report it?"
>> section of the Shotwell FAQ here:
>> http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ.
>>
>> Lucas
>>
>> On Mon, Nov 7, 2011 at 9:38 AM, Adam Dingle <[email protected]> wrote:
>> > Joe,
>> >
>> > - what version of Shotwell are you running?  What operating system
>> > version
>> > are you running?
>> >
>> > - How do you know that the database is corrupted?  Is Shotwell printing
>> > an
>> > error message and/or exiting?  If so, what does the error message look
>> > like?
>> >
>> > adam
>> >
>> > On 11/07/2011 07:28 AM, Joe Irvine wrote:
>> >>
>> >> I am going through a mass re-upload of my photos from Shotwell to
>> >> Picasa.
>> >> As I am uploading them, I am tagging them so I know where I left off. I
>> >> am
>> >> noticing that I keep getting database corruption when tagging the
>> >> photos,
>> >> however. I am saving the tags in the photo metadata, so re-building the
>> >> database fixes it for a little while, but with over 25000 photos it
>> >> takes
>> >> hours to rebuild every time this happens. Is there a way to avoid this
>> >> database corruption?
>> >>
>> >
>> > _______________________________________________
>> > Shotwell mailing list
>> > [email protected]
>> > http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
>> >
>> _______________________________________________
>> Shotwell mailing list
>> [email protected]
>> http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
>
>
>
> --
>
> Thanks,
>
> Joe
>
_______________________________________________
Shotwell mailing list
[email protected]
http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell

Reply via email to