[Kde-imaging] [kipiplugins] [Bug 345369] New: KDE Scanner GUI crashes when saving scanned image

gargamel704 at hotmail.de gargamel704 at hotmail.de
Fri Mar 20 19:29:52 UTC 2015


https://bugs.kde.org/show_bug.cgi?id=345369

            Bug ID: 345369
           Summary: KDE Scanner GUI crashes when saving scanned image
           Product: kipiplugins
           Version: 4.8.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: UNCONFIRMED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: AcquireImages
          Assignee: kde-imaging at kde.org
          Reporter: gargamel704 at hotmail.de

Application: scangui (4.8.0)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.19.1-2-desktop x86_64
Distribution: "openSUSE 20150318 (Tumbleweed) (x86_64)"

-- Information about the crash:
To use the scanner I use the hplip app. I did nothing while the scanning
process was running. I only tried to save the scanned image. Exactly the same
issue happend on openSUSE 13.2.

The crash can be reproduced every time.

-- Backtrace:
Application: Bilder scannen (scangui), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f49b0d9b800 (LWP 29463))]

Thread 3 (Thread 0x7f499d2e6700 (LWP 29630)):
#0  0x00007f49adb3b4cd in poll () at /lib64/libc.so.6
#1  0x00007f49a8c7abe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f49a8c7acec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007f49ae2b501e in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#4  0x00007f49ae286daf in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#5  0x00007f49ae2870a5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#6  0x00007f49ae18449f in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007f49ae2686b3 in  () at /usr/lib64/libQtCore.so.4
#8  0x00007f49ae186b7f in  () at /usr/lib64/libQtCore.so.4
#9  0x00007f49aa4f24b4 in start_thread () at /lib64/libpthread.so.0
#10 0x00007f49adb43a4d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f492d650700 (LWP 29669)):
[KCrash Handler]
#5  0x00007f49ada903c7 in raise () at /lib64/libc.so.6
#6  0x00007f49ada9179a in abort () at /lib64/libc.so.6
#7  0x00007f49ac528d58 in  () at /usr/lib64/libpng16.so.16
#8  0x00007f49ac528dc6 in  () at /usr/lib64/libpng16.so.16
#9  0x00007f49ac523e01 in  () at /usr/lib64/libpng16.so.16
#10 0x00007f49ac53ffac in png_set_IHDR () at /usr/lib64/libpng16.so.16
#11 0x00007f49b02c6bba in KIPIPlugins::KPWriteImage::write2PNG(QString const&)
() at /usr/lib64/libkipiplugins.so.4.8.0
#12 0x0000000000409b6b in  ()
#13 0x00007f49ae186b7f in  () at /usr/lib64/libQtCore.so.4
#14 0x00007f49aa4f24b4 in start_thread () at /lib64/libpthread.so.0
#15 0x00007f49adb43a4d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f49b0d9b800 (LWP 29463)):
#0  0x00007f49adb3759d in read () at /lib64/libc.so.6
#1  0x00007f49a8cbb750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f49a8c7a714 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x00007f49a8c7ab7b in  () at /usr/lib64/libglib-2.0.so.0
#4  0x00007f49a8c7acec in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x00007f49ae2b4ffe in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
at /usr/lib64/libQtCore.so.4
#6  0x00007f49ae86a706 in  () at /usr/lib64/libQtGui.so.4
#7  0x00007f49ae286daf in
QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#8  0x00007f49ae2870a5 in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at
/usr/lib64/libQtCore.so.4
#9  0x00007f49ae28c4f9 in QCoreApplication::exec() () at
/usr/lib64/libQtCore.so.4
#10 0x0000000000406d91 in  ()
#11 0x00007f49ada7d8c5 in __libc_start_main () at /lib64/libc.so.6
#12 0x0000000000406e09 in _start ()

Reported using DrKonqi

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Kde-imaging mailing list