Bug 352112 - crash while opening pictures
Summary: crash while opening pictures
Status: RESOLVED FIXED
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: 5.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-09-01 18:43 UTC by Gerhard Lehnhoff
Modified: 2017-12-10 20:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gerhard Lehnhoff 2015-09-01 18:43:29 UTC
Application: gwenview (5.0.0)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-26-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
I tried to open an jpg out of a kmail attachement, however, the program crashed.

-- Backtrace:
Application: Gwenview (gwenview), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fce0aa5d800 (LWP 2042))]

Thread 4 (Thread 0x7fcdf622f700 (LWP 2043)):
#0  0x00007fce05e9d8dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fcdff6f7b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fcdff6f964f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fcdf8153099 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x00007fce0651eb0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007fce0156d6aa in start_thread (arg=0x7fcdf622f700) at pthread_create.c:333
#6  0x00007fce05ea8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fcde9e74700 (LWP 2046)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fcdece89e83 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x00007fcdece896e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x00007fce0156d6aa in start_thread (arg=0x7fcde9e74700) at pthread_create.c:333
#4  0x00007fce05ea8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fcde9673700 (LWP 2047)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fcdece89e83 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#2  0x00007fcdece896e7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
#3  0x00007fce0156d6aa in start_thread (arg=0x7fcde9673700) at pthread_create.c:333
#4  0x00007fce05ea8eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fce0aa5d800 (LWP 2042)):
[KCrash Handler]
#6  QString (other=..., this=0x7ffc7e55ebf0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:811
#7  result (this=0x1bedb00) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qfuture.h:164
#8  result (this=0x1bedaf0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qfuturewatcher.h:122
#9  operator() (__closure=<optimized out>) at ../../../../src/utils/dbusfuture_p.h:169
#10 call (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:494
#11 call<QtPrivate::List<>, void> (arg=<optimized out>, f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:551
#12 QtPrivate::QFunctorSlotObject<DBusFuture::continueWith(const QFuture<T>&, _Continuation&&) [with _ReturnType = QString; _Continuation = KActivities::Manager::serviceOwnerChanged(const QString&, const QString&, const QString&)::<lambda(const QString&)>]::<lambda()>, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=<optimized out>, this_=<optimized out>, r=<optimized out>, a=<optimized out>, ret=<optimized out>) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject_impl.h:192
#13 0x00007fce0678e73a in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fce06516082 in QFutureWatcherBase::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007fce0751eb2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x00007fce07524000 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x00007fce0675cc2b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fce0675ec9b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007fce067b5843 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007fce0104ec3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fce0104ef20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fce0104efcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x00007fce067b5c57 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x00007fce0675a3e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x00007fce0676202c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#26 0x000000000043efad in main (argc=2, argv=<optimized out>) at ../../app/main.cpp:166

Possible duplicates by query: bug 307124.

Reported using DrKonqi
Comment 1 Nate Graham 2017-09-08 23:20:26 UTC

*** This bug has been marked as a duplicate of bug 307124 ***
Comment 2 Christoph Feck 2017-10-25 16:13:23 UTC
Backtrace is not related. Do not trust DrKonqi, despite him having a degree :)
Comment 3 Nate Graham 2017-10-25 16:28:53 UTC
Yeah I'm just now figuring out how to read backtraces. Thanks for your patience. :)
Comment 4 null 2017-12-10 20:26:29 UTC
Testing with KMail 5.6.3, Gwenview 17.12.0 and Frameworks 5.40, this works fine for me. I suspect this has been fixed at some point (in KActivities, possibly), because I cannot reproduce anymore.

Nevertheless, please test again on a newer system and comment if it still crashes for you, then we'd need to reopen.