[okular] [Bug 411130] New: Searching CHM files crashes Okular

2019-08-21 Thread Enmk
https://bugs.kde.org/show_bug.cgi?id=411130

Bug ID: 411130
   Summary: Searching CHM files crashes Okular
   Product: okular
   Version: 1.8.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-devel@kde.org
  Reporter: v.nem...@gmail.com
  Target Milestone: ---

Application: okular (1.8.0)

Qt Version: 5.12.3
Frameworks Version: 5.61.0
Operating System: Linux 5.0.0-25-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
- What I was doing when the application crashed:
* Downloaded a Python 2.7.16 docs in CHM format from
https://www.python.org/ftp/python/2.7.16/python2716.chm
* Opened the said chm with Okular
* Typed 'set' in search bar
* Navigated search results to a 'Standard library' page
* Clicked the page to open

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fea4d576200 (LWP 30784))]

Thread 4 (Thread 0x7fea20ea4700 (LWP 30789)):
#0  0x7fea45f829f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55b0ab5234b8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55b0ab523468,
cond=0x55b0ab523490) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55b0ab523490, mutex=0x55b0ab523468) at
pthread_cond_wait.c:655
#3  0x7fea21a870aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7fea21a86dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7fea45f7c6db in start_thread (arg=0x7fea20ea4700) at
pthread_create.c:463
#6  0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fea32af2700 (LWP 30788)):
#0  _dl_update_slotinfo (req_modid=2) at ../elf/dl-tls.c:651
#1  0x7fea4d3aa87c in update_get_addr (ti=0x7fea49f6d670) at
../elf/dl-tls.c:799
#2  0x7fea4d3b0a28 in __tls_get_addr () at
../sysdeps/x86_64/tls_get_addr.S:55
#3  0x7fea498e4c26 in get_thread_data () at thread/qthread_unix.cpp:184
#4  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:239
#5  0x7fea49b1bcaa in postEventSourcePrepare (s=0x7fea2c004ba0,
timeout=0x7fea32af1ba4) at kernel/qeventdispatcher_glib.cpp:252
#6  0x7fea43c49b28 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fea43c4a4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fea43c4a6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fea49b1bdcb in QEventDispatcherGlib::processEvents
(this=0x7fea2c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#10 0x7fea49abd03a in QEventLoop::exec (this=this@entry=0x7fea32af1d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#11 0x7fea498e44ca in QThread::exec (this=) at
thread/qthread.cpp:531
#12 0x7fea49f8a015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7fea498e5c72 in QThreadPrivate::start (arg=0x7fea4a201d80) at
thread/qthread_unix.cpp:361
#14 0x7fea45f7c6db in start_thread (arg=0x7fea32af2700) at
pthread_create.c:463
#15 0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fea3b7b8700 (LWP 30787)):
#0  0x7fea491d8bf9 in __GI___poll (fds=0x7fea3b7b7ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fea469fe747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fea46a0036a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fea3e59f578 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fea498e5c72 in QThreadPrivate::start (arg=0x55b0ab27d110) at
thread/qthread_unix.cpp:361
#5  0x7fea45f7c6db in start_thread (arg=0x7fea3b7b8700) at
pthread_create.c:463
#6  0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fea4d576200 (LWP 30784)):
[KCrash Handler]
#6  QWidget::window (this=0x55b0ad940680) at kernel/qwidget.cpp:4330
#7  0x7fea4ab86e4c in QWidgetPrivate::sharedPainter (this=0x55b0ac7c56f0)
at
../../include/QtWidgets/5.12.3/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:985
#8  QWidget::render (this=this@entry=0x55b0ad940680,
painter=painter@entry=0x7ffdd5addcc0, targetOffset=..., sourceRegion=...,
renderFlags=renderFlags@entry=...) at kernel/qwidget.cpp:5185
#9  0x7fea4ab8795b in QWidget::render (this=this@entry=0x55b0ad940680,
target=target@entry=0x55b0acaace40, targetOffset=..., sourceRegion=...,
renderFlags=..., renderFlags@entry=...) at kernel/qwidget.cpp:5126
#10 0x7fea1b92ae42 in copyWidget (r=..., p=p@entry=0x7ffdd5ade348,
widget=widget@ent

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Enmk
https://bugs.kde.org/show_bug.cgi?id=411130

--- Comment #1 from Enmk  ---
Well, actually I've opened a subsection of the 'The Python standard
library'/'Builting types'/'set and frozenset', but any other page may cause a
crash too. It is not always reproducible from the first try, click around the
'Contents'.

It also looks like that setting '100%' zoom mode rather than 'Fit width',
reduces chances of crashing.

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

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Enmk
https://bugs.kde.org/show_bug.cgi?id=411130

--- Comment #2 from Enmk  ---
Backtrace of doing the same in '100%' zoom mode:


Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff1480c8200 (LWP 444))]

Thread 7 (Thread 0x7ff112ffd700 (LWP 498)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff112ffcbe0, expected=0, futex_word=0x56105d01db94) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff112ffcca0, mutex=0x56105d01db40,
cond=0x56105d01db68) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105d01db68, mutex=0x56105d01db40,
abstime=0x7ff112ffcca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105d01db40, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105d01db40) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105b73dce0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105b73dcd0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105b73dcd0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff112ffd700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7ff113fff700 (LWP 497)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff113ffebe0, expected=0, futex_word=0x56105b079d14) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff113ffeca0, mutex=0x56105b079cc0,
cond=0x56105b079ce8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105b079ce8, mutex=0x56105b079cc0,
abstime=0x7ff113ffeca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105b079cc0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105b079cc0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105b777ec0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105b777eb0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105b777eb0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff113fff700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7ff1137fe700 (LWP 496)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff1137fdbe0, expected=0, futex_word=0x56105c175734) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff1137fdca0, mutex=0x56105c1756e0,
cond=0x56105c175708) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105c175708, mutex=0x56105c1756e0,
abstime=0x7ff1137fdca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105c1756e0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105c1756e0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105c1d11e0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105c1d11d0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105c1d11d0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff1137fe700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7ff11baed700 (LWP 449)):
#0  0x7ff140ad49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x561059d53b98) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x561059d53b48,
cond=0x561059d53b70) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x561059d53b70, mutex=0x561059d53b48) at
pthread_cond_wait.c:655
#3  0x7ff11c6d00aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7ff11c6cfdd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7ff140ace6db in start_thread (arg=0x7ff11baed700) at

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=411130

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Albert Astals Cid  ---
I can reproduce just browsing to page 4 or 5

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

[okular] [Bug 411090] Okular crashed when printing document

2019-08-21 Thread Todor Todorov
https://bugs.kde.org/show_bug.cgi?id=411090

--- Comment #3 from Todor Todorov  ---
I can confirm that after upgrade to Fedora 30 (Qt 5.12.4) the problem is no
more reproducible. You can close this bug if no plans to fix it in Qt 5.11.3

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

[okular] [Bug 411090] Okular crashed when printing document

2019-08-21 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=411090

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UPSTREAM

--- Comment #4 from Albert Astals Cid  ---
I can't speak for The Qt Project, but as far as i know Qt 5.11.4 isn't planned 
and time travel hasn't been invented yet so it can not be fixed in Qt 5.11.3 ;)

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

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=411130

--- Comment #4 from Albert Astals Cid  ---
My initial guess is that the problem is that some pages are crazy tall and
something gets confused in khtml when that happens.

Which using khtml in itself is a big issue since it's basically dead tech, so
the fix long term is movign away from html, short term i don't know if there's
any fix for this particular crash :/

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

[okular] [Bug 410844] Okular segfault

2019-08-21 Thread Tobias Deiminger
https://bugs.kde.org/show_bug.cgi?id=410844

Tobias Deiminger  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED

--- Comment #11 from Tobias Deiminger  ---
I was able to reproduce the issue on a KDE neon User Edition 5.16. As assumed
in comment 10, the crash is caused by a negative page index.

The negative page value eventually stems from the freshly generated
MobiDocument. If we iterate over all QTextBlocks in the MobiDocument, and check
newDocument->documentLayout()->blockBoundingRect(nth_QTextBlock), we see there
are lots of blocks with negative top and bottom values, like left = 20.00,
top = -33553713.00, right = 580, bottom = -33553695.00.

This is not the case if I do the same on my "normal" development machine, where
all top/bottom values are positive for the same .mobi file.

The Okular mobi generator seems mostly unchanged for years. Therefore I'd
suspect an upstream regression. KDE Neon ships libqmobipocket.so.2.0.0 from
kdegraphics-mobipocket 19.08.0, while on my dev machine I have it from
kdegraphics-mobipocket 19.04.0.

I'm going to open a merge request to catch negative page indexes, and will
further investigate in what's going on upstream.

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

[okular] [Bug 410844] Okular segfault

2019-08-21 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=410844

--- Comment #12 from Albert Astals Cid  ---
Bad Qt? Which one has it 5.12.3?

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

[okular] [Bug 410844] Okular segfault

2019-08-21 Thread Tobias Deiminger
https://bugs.kde.org/show_bug.cgi?id=410844

--- Comment #13 from Tobias Deiminger  ---
(In reply to Albert Astals Cid from comment #12)
> Bad Qt? Which one has it 5.12.3?

Yes.

$ dpkg -l libqt5gui5:amd
ii  libqt5gui5:amd645.12.3+dfsg-1+18.04+bionic+build58

How to go on, should we inform Neon devs?

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