Bug 1037744 - [abrt] darktable-1.2.3-1.fc20: g_bit_lock: Process /usr/bin/darktable was killed by signal 11 (SIGSEGV) [NEEDINFO]
Summary: [abrt] darktable-1.2.3-1.fc20: g_bit_lock: Process /usr/bin/darktable was kil...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: darktable
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Edouard Bourguignon
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:420c27f2c866f59342eab096d49...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 17:52 UTC by Martin
Modified: 2014-09-15 00:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-11 13:39:27 UTC
Type: ---
madko: needinfo? (mholec)

Attachments (Terms of Use)
File: backtrace (17.18 KB, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: core_backtrace (5.75 KB, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: dso_list (10.58 KB, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: environ (1.79 KB, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: exploitable (82 bytes, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: limits (1.29 KB, text/plain)
2013-12-03 17:52 UTC, Martin 		no flags Details
File: maps (50.64 KB, text/plain)
2013-12-03 17:53 UTC, Martin 		no flags Details
File: open_fds (494 bytes, text/plain)
2013-12-03 17:53 UTC, Martin 		no flags Details
File: proc_pid_status (931 bytes, text/plain)
2013-12-03 17:53 UTC, Martin 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Martin 2013-12-03 17:52:30 UTC 
Description of problem:
Crash on Darktable startup, just after login to KDE.

Version-Release number of selected component:
darktable-1.2.3-1.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /bin/darktable
crash_function: g_bit_lock
executable:     /usr/bin/darktable
kernel:         3.11.9-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (8 frames)
 #0 g_bit_lock at gbitlock.c:211
 #1 g_variant_lock at gvariant-core.c:223
 #2 g_variant_n_children at gvariant-core.c:931
 #3 g_variant_get_child_value at gvariant-core.c:977
 #4 init_kwallet at /usr/src/debug/darktable-1.2.3/src/common/pwstorage/backend_kwallet.c:214
 #5 dt_pwstorage_kwallet_new at /usr/src/debug/darktable-1.2.3/src/common/pwstorage/backend_kwallet.c:262
 #6 dt_pwstorage_new at /usr/src/debug/darktable-1.2.3/src/common/pwstorage/pwstorage.c:66
 #7 dt_init at /usr/src/debug/darktable-1.2.3/src/common/darktable.c:593
Comment 1 Martin 2013-12-03 17:52:38 UTC 
Created attachment 832226 [details]
File: backtrace
Comment 2 Martin 2013-12-03 17:52:41 UTC 
Created attachment 832228 [details]
File: cgroup
Comment 3 Martin 2013-12-03 17:52:45 UTC 
Created attachment 832230 [details]
File: core_backtrace
Comment 4 Martin 2013-12-03 17:52:50 UTC 
Created attachment 832232 [details]
File: dso_list
Comment 5 Martin 2013-12-03 17:52:53 UTC 
Created attachment 832234 [details]
File: environ
Comment 6 Martin 2013-12-03 17:52:56 UTC 
Created attachment 832236 [details]
File: exploitable
Comment 7 Martin 2013-12-03 17:52:59 UTC 
Created attachment 832238 [details]
File: limits
Comment 8 Martin 2013-12-03 17:53:04 UTC 
Created attachment 832239 [details]
File: maps
Comment 9 Martin 2013-12-03 17:53:09 UTC 
Created attachment 832240 [details]
File: open_fds
Comment 10 Martin 2013-12-03 17:53:12 UTC 
Created attachment 832242 [details]
File: proc_pid_status
Comment 11 Edouard Bourguignon 2014-01-15 07:59:12 UTC 
crash during dt_init could result from bad configuration or bad database in your ~/.config/darktable. Could you try to rename this directory and see if darktable still crash?
Comment 12 Martin 2014-06-11 13:39:27 UTC 
I have new ~/.config/darktable and I haven't seen this crash for a while.
Note You need to log in before you can comment on or make changes to this bug.