shotwell crash with ERROR:src/folders/Branch.c:982:folders_branch_remove_entry: assertion failed: (folder_entry.count > 0)

Bug #1363251 reported by Fabrice Boyrie
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Shotwell
Invalid
Medium
shotwell (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After manualy erasing some files in shotwell image directory, there are random crashes with the message:

shotwell crash with ERROR:src/folders/Branch.c:982:folders_branch_remove_entry: assertion failed: (folder_entry.count > 0)

If I strace shtowell, the sequence before crash is

[pid 12866] lstat("/home/.../Images/V/DSC06111.JPG", <unfinished ...>
[pid 12866] <... lstat resumed> 0x7f69b9e179c0) = -1 ENOENT (No such file or directory)
[pid 12744] access("/home/.../.local/share/shotwell/data/photo.db-journal", F_OK) = -1 ENOENT (No such file or directory)
[pid 12744] fstat(8, {st_mode=S_IFREG|0644, st_size=18259968, ...}) = 0
[pid 12744] fstat(8, {st_mode=S_IFREG|0644, st_size=18259968, ...}) = 0
[pid 12744] access("/home/.../.local/share/shotwell/data/photo.db-wal", F_OK) = -1 ENOENT (No such file or directory)
[pid 12744] fstat(8, {st_mode=S_IFREG|0644, st_size=18259968, ...}) = 0
[pid 12744] stat("/home/.../.local/share/shotwell/data/photo.db", {st_mode=S_IFREG|0644, st_size=18259968, ...}) = 0
[pid 12744] open("/home/.../.local/share/shotwell/data/photo.db-journal", O_RDWR|O_CREAT|O_CLOEXEC, 0644) = 15
[pid 12744] fstat(15, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
[pid 12744] fstat(15, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
[pid 12744] stat("/var/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0
[pid 12744] access("/var/tmp", R_OK|W_OK|X_OK) = 0
[pid 12744] access("/var/tmp/etilqs_6Zfy0Wy6Q6KlmXR", F_OK) = -1 ENOENT (No such file or directory)
[pid 12744] open("/var/tmp/etilqs_6Zfy0Wy6Q6KlmXR", O_RDWR|O_CREAT|O_EXCL|O_NOFOLLOW|O_CLOEXEC, 0600) = 16
[pid 12744] fstat(16, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0
[pid 12744] fstat(16, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0

/home/.../Images/V/DSC06111.JPG was manually removed

In the preference I've tried to select option to detect new files, but no changes.

lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04

apt-cache policy shotwell
shotwell:
  Installé : 0.18.0-0ubuntu4.1
  Candidat : 0.18.0-0ubuntu4.1
 Table de version :
 *** 0.18.0-0ubuntu4.1 0
        500 http://fr.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.18.0-0ubuntu4 0
        500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

Changed in shotwell:
importance: Unknown → Medium
status: Unknown → Invalid
Changed in shotwell (Ubuntu):
status: New → Invalid
importance: Undecided → Low
Revision history for this message
Marc Brevoort (kleinebre) wrote :
Download full text (4.3 KiB)

I've run into this error as well.
Here's what I get when running it from gdb:

mrjb@mrjb-desktop:~$ gdb shotwell
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from shotwell...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/shotwell
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe92d2700 (LWP 5214)]
[New Thread 0x7fffcbc63700 (LWP 5215)]
[New Thread 0x7fffbe746700 (LWP 5216)]
[New Thread 0x7fffbdf45700 (LWP 5217)]
[New Thread 0x7fffbd744700 (LWP 5218)]

(shotwell:5210): Pango-WARNING **: /usr/lib/x86_64-linux-gnu/pango/1.8.0/modules/pango-basic-fc.so: cannot open shared object file: No such file or directory
[New Thread 0x7fffb7fff700 (LWP 5219)]
[New Thread 0x7fffb77fe700 (LWP 5220)]
[Thread 0x7fffb7fff700 (LWP 5219) exited]
[New Thread 0x7fffb7fff700 (LWP 5221)]
[Thread 0x7fffb7fff700 (LWP 5221) exited]
[New Thread 0x7fffb7fff700 (LWP 5222)]
[Thread 0x7fffb7fff700 (LWP 5222) exited]
[New Thread 0x7fffb7fff700 (LWP 5223)]
[Thread 0x7fffb7fff700 (LWP 5223) exited]
[New Thread 0x7fffb7fff700 (LWP 5224)]
[New Thread 0x7fffb6885700 (LWP 5225)]
[New Thread 0x7fffb6084700 (LWP 5226)]
[New Thread 0x7fffb5883700 (LWP 5227)]
[New Thread 0x7fffb5082700 (LWP 5228)]
[New Thread 0x7fffb4881700 (LWP 5229)]
[Thread 0x7fffb7fff700 (LWP 5224) exited]
[Thread 0x7fffb5883700 (LWP 5227) exited]
[Thread 0x7fffb6084700 (LWP 5226) exited]
[Thread 0x7fffb5082700 (LWP 5228) exited]
[Thread 0x7fffb6885700 (LWP 5225) exited]
[New Thread 0x7fffb6885700 (LWP 5230)]
[New Thread 0x7fffb5082700 (LWP 5231)]
[New Thread 0x7fffb6084700 (LWP 5232)]
[New Thread 0x7fffb5883700 (LWP 5233)]
**
ERROR:src/folders/Branch.c:982:folders_branch_remove_entry: assertion failed: (folder_entry.count > 0)

Program received signal SIGABRT, Aborted.
0x00007ffff3c56bb9 in __GI_raise (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007ffff3c56bb9 in __GI_raise (sig=sig@entry=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007ffff3c59fc8 in __GI_abort () at abort.c:89
#2 0x00007ffff4271165 in g_assertion_message ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff42711fa in g_assertion_message_expr ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x0000000000581949 in ?? ()
#5 0x0000000000581f2b in ?? ()
#6 0x00007ffff451c3b8 in g_closure_invoke ()
   from /u...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.