Bug 1042696 - [abrt] kipi-plugins-3.5.0-1.fc19: lockInline: Process /usr/bin/scangui was killed by signal 11 (SIGSEGV)
Summary: [abrt] kipi-plugins-3.5.0-1.fc19: lockInline: Process /usr/bin/scangui was ki...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: digikam
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steven M. Parrish
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:4728fb48815d951483784472939...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 05:23 UTC by dario
Modified: 2015-02-17 19:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:37:28 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (51.20 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: cgroup (141 bytes, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: core_backtrace (18.77 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: dso_list (28.86 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: environ (1.69 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: exploitable (82 bytes, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: maps (128.20 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: open_fds (2.30 KB, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details
File: proc_pid_status (937 bytes, text/plain)
2013-12-13 05:23 UTC, dario
no flags Details

Description dario 2013-12-13 05:23:20 UTC
Version-Release number of selected component:
kipi-plugins-3.5.0-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        scangui --icon scanner -caption 'Acquisizione di immagini'
crash_function: lockInline
executable:     /usr/bin/scangui
kernel:         3.11.9-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: Dec 13 05:59:52 odino-valhalla abrt-hook-ccpp[2522]: Saved core dump of pid 2335 (/usr/bin/scangui) to /var/tmp/abrt/ccpp-2013-12-13-05:59:51-2335 (108134400 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 lockInline at thread/qmutex.h:187
 #1 QMutexLocker at thread/qmutex.h:109
 #2 QThread::isRunning at thread/qthread.cpp:471
 #3 KSaneIface::KSaneWidgetPrivate::setTLX at /usr/src/debug/libksane-4.11.3/libksane/ksane_widget_private.cpp:584
 #4 QMetaObject::activate at kernel/qobject.cpp:3547
 #5 fValueRead at /usr/src/debug/libksane-4.11.3/x86_64-redhat-linux-gnu/libksane/ksane_opt_fslider.moc:102
 #6 KSaneIface::KSaneOptFSlider::readValue at /usr/src/debug/libksane-4.11.3/libksane/options/ksane_opt_fslider.cpp:106
 #7 KSaneIface::KSaneOptFSlider::setValue at /usr/src/debug/libksane-4.11.3/libksane/options/ksane_opt_fslider.cpp:156
 #8 KSaneIface::KSaneWidgetPrivate::oneFinalScanDone at /usr/src/debug/libksane-4.11.3/libksane/ksane_widget_private.cpp:969
 #9 QObject::event at kernel/qobject.cpp:1194

Comment 1 dario 2013-12-13 05:23:27 UTC
Created attachment 836133 [details]
File: backtrace

Comment 2 dario 2013-12-13 05:23:29 UTC
Created attachment 836134 [details]
File: cgroup

Comment 3 dario 2013-12-13 05:23:32 UTC
Created attachment 836135 [details]
File: core_backtrace

Comment 4 dario 2013-12-13 05:23:34 UTC
Created attachment 836136 [details]
File: dso_list

Comment 5 dario 2013-12-13 05:23:36 UTC
Created attachment 836137 [details]
File: environ

Comment 6 dario 2013-12-13 05:23:38 UTC
Created attachment 836138 [details]
File: exploitable

Comment 7 dario 2013-12-13 05:23:41 UTC
Created attachment 836139 [details]
File: limits

Comment 8 dario 2013-12-13 05:23:44 UTC
Created attachment 836140 [details]
File: maps

Comment 9 dario 2013-12-13 05:23:46 UTC
Created attachment 836141 [details]
File: open_fds

Comment 10 dario 2013-12-13 05:23:48 UTC
Created attachment 836142 [details]
File: proc_pid_status

Comment 11 nucleo 2013-12-13 12:54:40 UTC
How crash can be reproduced?

Comment 12 dario 2013-12-13 17:59:04 UTC
(In reply to nucleo from comment #11)
> How crash can be reproduced?

only when I save the second image.

Comment 13 nucleo 2013-12-14 03:34:01 UTC
I saved second image after second scanning but can't reproduce crash.

Comment 14 Fedora End Of Life 2015-01-09 20:50:45 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 15 Fedora End Of Life 2015-02-17 19:37:28 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.