Bug 391363 - okular crashes when refreshing deleted document
Summary: okular crashes when refreshing deleted document
Status: RESOLVED DUPLICATE of bug 390214
Alias: None
Product: frameworks-kcoreaddons
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.43.0
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Pyne
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-04 00:11 UTC by Andrius Štikonas
Modified: 2018-04-06 14:00 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrius Štikonas 2018-03-04 00:11:07 UTC
Okular crashes here when I:

1) Open PDF file
2) delete it
3) Click F5 in Okular
Comment 1 null 2018-03-04 07:10:27 UTC
Thanks for the report, but cannot reproduce.

Does this happen for every file and every storage location? Which Okular + Poppler version is this? Could you provide a backtrace?
Comment 2 Albert Astals Cid 2018-03-04 10:23:19 UTC
Seems to me like Milian broke KDirWatch

(gdb) bt
#0  0x00007ffff4702821 in QString::size (this=0x555555fae080) at /usr/include/qt/QtCore/qstring.h:233
#1  0x00007ffff4702d80 in QConcatenable<QString>::size (a=...) at /usr/include/qt/QtCore/qstringbuilder.h:257
#2  0x00007ffff470aaf8 in QConcatenable<QStringBuilder<QString, QLatin1Char> >::size (p=...) at /usr/include/qt/QtCore/qstringbuilder.h:358
#3  0x00007ffff470a91b in QConcatenable<QStringBuilder<QStringBuilder<QString, QLatin1Char>, QString> >::size (p=...) at /usr/include/qt/QtCore/qstringbuilder.h:358
#4  0x00007ffff470a3ee in QStringBuilder<QStringBuilder<QString, QLatin1Char>, QString>::convertTo<QString> (this=0x7fffffffb400) at /usr/include/qt/QtCore/qstringbuilder.h:111
#5  0x00007ffff4709e08 in QStringBuilder<QStringBuilder<QString, QLatin1Char>, QString>::operator QString (this=0x7fffffffb400) at /usr/include/qt/QtCore/qstringbuilder.h:131
#6  0x00007ffff470bdb9 in KDirWatchPrivate::inotifyEventReceived (this=0x555555aa5ed0) at /home/tsdgeos/devel/kde/kcoreaddons/src/lib/io/kdirwatch.cpp:322
#7  0x00007ffff4714afc in KDirWatchPrivate::qt_static_metacall (_o=0x555555aa5ed0, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7fffffffd5a0) at /home/tsdgeos/devel/kde/kcoreaddons/build/src/lib/KF5CoreAddons_autogen/include/moc_kdirwatch_p.cpp:89
#8  0x00007ffff2ffb6c6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5
#9  0x00007ffff3007fa9 in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () from /usr/lib/libQt5Core.so.5
#10 0x00007ffff3008384 in QSocketNotifier::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#11 0x00007ffff3fd2fec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#12 0x00007ffff3fda9c6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#13 0x00007ffff2fcada0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#14 0x00007ffff3027f8e in ?? () from /usr/lib/libQt5Core.so.5
#15 0x00007fffed5c8e38 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#16 0x00007fffed5c9081 in ?? () from /usr/lib/libglib-2.0.so.0
#17 0x00007fffed5c910e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#18 0x00007ffff30272f1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#19 0x00007fffe8de4482 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#20 0x00007ffff2fc93db in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#21 0x00007ffff2fd27d8 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#22 0x0000555555561800 in main (argc=2, argv=0x7fffffffdc38) at /home/tsdgeos/devel/kde/okular/shell/main.cpp:84
Comment 3 Andrius Štikonas 2018-03-04 11:49:49 UTC
(In reply to Henrik Fehlauer from comment #1)
> Thanks for the report, but cannot reproduce.
> 
> Does this happen for every file and every storage location? Which Okular +
> Poppler version is this? Could you provide a backtrace?

Yes, it happens every time here, and backtrace is the same as Albert's. Sorry for not attaching it yesterday, I discovered this just before I went to bed.
Comment 4 Christoph Feck 2018-03-05 19:49:38 UTC

*** This bug has been marked as a duplicate of bug 390214 ***