Bug 394429 - Okular crashed after reboot
Summary: Okular crashed after reboot
Status: RESOLVED DUPLICATE of bug 395765
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.4.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-05-19 02:51 UTC by Dennis Irrgang
Modified: 2018-07-18 19:33 UTC (History)
0 users

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 Dennis Irrgang 2018-05-19 02:51:35 UTC
Application: okular (1.4.1)

Qt Version: 5.10.0
Frameworks Version: 5.45.0
Operating System: Linux 4.16.8-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:
I updated TW the evening before. After booting this morning it said it couldn't open a file and crashed.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5a04570180 (LWP 3497))]

Thread 3 (Thread 0x7f59e91de700 (LWP 3523)):
#0  0x00007f5a00299179 in poll () at /lib64/libc.so.6
#1  0x00007f59fac78429 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f59fac7853c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f5a00bd7a2b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7f59e4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x00007f5a00b7e95a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7f59e91ddd90, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x00007f5a009a5baa in QThread::exec() (this=this@entry=0x7f5a0126bd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:522
#6  0x00007f5a00ffba35 in QDBusConnectionManager::run() (this=0x7f5a0126bd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:178
#7  0x00007f5a009aaba0 in QThreadPrivate::start(void*) (arg=0x7f5a0126bd60 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:376
#8  0x00007f59fd27a59b in start_thread () at /lib64/libpthread.so.0
#9  0x00007f5a002a3a1f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f59f254f700 (LWP 3508)):
#0  0x00007f5a00299179 in poll () at /lib64/libc.so.6
#1  0x00007f59fd6a2387 in  () at /usr/lib64/libxcb.so.1
#2  0x00007f59fd6a3faa in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007f59f551a0a9 in QXcbEventReader::run() (this=0x55a1e454e1c0) at qxcbconnection.cpp:1370
#4  0x00007f5a009aaba0 in QThreadPrivate::start(void*) (arg=0x55a1e454e1c0) at thread/qthread_unix.cpp:376
#5  0x00007f59fd27a59b in start_thread () at /lib64/libpthread.so.0
#6  0x00007f5a002a3a1f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f5a04570180 (LWP 3497)):
[KCrash Handler]
#6  0x00007f5a029aa6a0 in  () at /usr/lib64/libKF5ConfigCore.so.5
#7  0x00007f5a029bf3a4 in KConfigGroup::readEntry(char const*, QVariant const&) const () at /usr/lib64/libKF5ConfigCore.so.5
#8  0x000055a1e39a7863 in KConfigGroup::readEntry<int>(char const*, int const&) const (defaultValue=@0x7fff0d4e499c: 0, key=0x55a1e39ae562 "ActiveTab", this=0x7fff0d4e4a50) at /usr/include/KF5/KConfigCore/kconfiggroup.h:728
#9  0x000055a1e39a7863 in Shell::readProperties(KConfigGroup const&) (this=0x55a1e46f4d00, group=...) at /usr/src/debug/okular-18.04.1-1.1.x86_64/shell/shell.cpp:392
#10 0x00007f5a036e99f8 in KMainWindow::readPropertiesInternal(KConfig*, int) () at /usr/lib64/libKF5XmlGui.so.5
#11 0x00007f5a036e9a42 in KMainWindow::restore(int, bool) () at /usr/lib64/libKF5XmlGui.so.5
#12 0x000055a1e39a2be3 in kRestoreMainWindows<Shell>() () at /usr/include/KF5/KXmlGui/kmainwindow.h:719
#13 0x000055a1e39a0312 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/okular-18.04.1-1.1.x86_64/shell/main.cpp:66

Reported using DrKonqi
Comment 1 Christoph Feck 2018-07-18 19:33:03 UTC

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