[Expired for shotwell (Ubuntu) because there has been no activity for 60
days.]
** Changed in: shotwell (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: shotwell (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016859
Title:
shotwell crashes on startup
To manage notifications about this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shotwell (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016859
Title:
Good morning, one and all,
We've committed a fix for this upstream (please see
http://redmine.yorba.org/projects/shotwell/repository/revisions/51336040742ad51936c1d2d92fa1d092cad73a54
for details); those of you who've been affected by this and are
comfortable building applications from source,
Another user reported a similar crash a few months back. We have a
ticket for this upstream at
http://redmine.yorba.org/issues/4805
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016859
Title:
Hi Roland,
My name is Clinton, and I'm one of the developers currently assigned to
Shotwell.
I took a quick stab at trying to get the TombstoneTable into that same
state (two rows with the same fully qualified path- and file-name, but
with different IDs) wiht various combinations of importing
FWIW, I added a debug print to Tombstone.vala right before the assertion
that fails:
bool is_removed = file_map.unset(tombstone.get_file());
if (!is_removed)
debug(is_removed == false for %s,
tombstone.get_name());
FWIW, I added a debug print to Tombstone.vala right before the assertion
that fails:
bool is_removed = file_map.unset(tombstone.get_file());
if (!is_removed)
debug(is_removed == false for %s,
tombstone.get_name());
So I added the following to the insert side of that
Tombstone.vala:notify_contents_altered() function:
if (file_map.has_key(tombstone.get_file()))
debug(already have file for %s!,
tombstone.get_name());
and now in the log I see
L 6394 2012-06-28 01:57:38
I did
$ echo .dump | sqlite3 ~/.shotwell/data/photo.db | grep
IMG_6016_CR2_shotwell.jpg
INSERT INTO TombstoneTable
VALUES(862,'/home/roland/Pictures/CanonT1i-images/2012/06/05/IMG_6016_CR2_shotwell.jpg',4635334,NULL,1340417401,0);
INSERT INTO TombstoneTable
Not a problem... here's the log
** Attachment added: shotwell.log
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+attachment/3205712/+files/shotwell.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And here's the gdb backtrace. Unfortunately Ubuntu seems to strip
everything from shotwell so I'm not sure how useful this is...
** Attachment added: shotwell.gdb
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1016859/+attachment/3205713/+files/shotwell.gdb
--
You received this
Hi Roland,
We'd like to open an upstream bug for this issue, but in order to do
that, we really need both a stack trace at the time of the crash and the
Shotwell log file. To learn how to generate these two diagnostic files,
see the I found a bug in Shotwell. How can I report it? section of the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016859
Title:
shotwell crashes on startup
To manage notifications about this bug go to:
FWIW, even
$ shotwell --no-runtime-monitoring --no-startup-progress
**
ERROR:/build/buildd/shotwell-0.12.3/src/Tombstone.vala:38:tombstone_source_collection_real_notify_contents_altered:
assertion failed: (_tmp29_)
Aborted (core dumped)
hits the same crash.
--
You received this bug
15 matches
Mail list logo
