https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #4 from RJVB ---
Well, this is strange, I'm convinced that DrKonqi showed me a backtrace of the
same bug, but I must have gotten confused.
I am positive though that it didn't suggest bug 415340 - evidently I would not
have filed another
https://bugs.kde.org/show_bug.cgi?id=439216
--- Comment #1 from RJVB ---
And FWIW, PageView::capability() needs to check every one of the QActions in
the d-ptr before accessing them, because aViewContinuous, aViewMode and
aTrimMargins can all turn out to be a nullptr.
Add a qDebug if you want
Version: 5.9.8
Frameworks Version: 5.60.0
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Windowing system: X11
Distribution: Ubuntu 14.04.6 LTS
-- Information about the crash:
- What I was doing when the application crashed:
I had checked the Print Preview and closed it by hitting
https://bugs.kde.org/show_bug.cgi?id=415012
--- Comment #5 from RJVB ---
No, neither did I miss the fact there are no guarantees.
This is an issue tracker, used among others for reporting what could be bugs
that need triaging. I consider it a courtesy to attach a patch if I have one
https://bugs.kde.org/show_bug.cgi?id=415012
--- Comment #3 from RJVB ---
So sue me ... or remove the possibility to attach them.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=393119
RJVB changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #3 from RJVB
https://bugs.kde.org/show_bug.cgi?id=415012
--- Comment #1 from RJVB ---
Created attachment 124423
--> https://bugs.kde.org/attachment.cgi?id=124423=edit
patch to make things work
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=415012
Bug ID: 415012
Summary: okularkirigami with Qt 5.9.8
Product: okular
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: crash
https://bugs.kde.org/show_bug.cgi?id=402997
RJVB changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=402997
--- Comment #1 from RJVB ---
Created attachment 117342
--> https://bugs.kde.org/attachment.cgi?id=117342=edit
fatal PDF document
--
You are receiving this mail because:
You are the assignee for the bug.
Operating System: Linux 4.14.23-ck1-mainline-core2-rjvb x86_64
Distribution: Ubuntu 14.04.5 LTS
-- Information about the crash:
- What I was doing when the application crashed:
Opening the attached PDF document crashes Okular5 systematically.
Okular built from git/master
https://bugs.kde.org/show_bug.cgi?id=392106
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEE
https://bugs.kde.org/show_bug.cgi?id=392106
Bug ID: 392106
Summary: opening (e)PS files from the commandline
Product: okular
Version: unspecified
Platform: Compiled Sources
OS: All
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=368382
RJVB <rjvber...@gmail.com> changed:
What|Removed |Added
CC||oliv...@churlaud.com
-
https://bugs.kde.org/show_bug.cgi?id=368382
--- Comment #1 from RJVB <rjvber...@gmail.com> ---
Created attachment 100965
--> https://bugs.kde.org/attachment.cgi?id=100965=edit
patch for mobile/components/CMakeLists.txt
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=368382
Bug ID: 368382
Summary: libokularplugin : superfluous link to okularpart cause
loader error on OS X
Product: okular
Version: unspecified
Platform: Compiled Sources
https://bugs.kde.org/show_bug.cgi?id=348000
RJVB rjvber...@gmail.com changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/okul
https://bugs.kde.org/show_bug.cgi?id=348000
Bug ID: 348000
Summary: print preview crashes Okular
Product: okular
Version: unspecified
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
Keywords:
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #21 from RJVB rjvber...@gmail.com ---
Yes, probably. Not sure if it makes any difference though (clearly
OKULAR_EXPORT expands to KDE_EXPORT in this case ... or the keyword is only of
importance for the ViewerInterface class).
--
You
https://bugs.kde.org/show_bug.cgi?id=345765
RJVB rjvber...@gmail.com changed:
What|Removed |Added
CC||rjvber...@gmail.com
--- Comment #19
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #9 from RJVB rjvber...@gmail.com ---
Yes, well, I tried that with ktimetracker and failed, probably mostly because I
have no idea how a cast can fail (or what a dynamic_cast really does, and how).
Is this a feature that relies on Qt tech
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #7 from RJVB rjvber...@gmail.com ---
Maybe I ought to return false when !viFace?
--
You are receiving this mail because:
You are the assignee for the bug.
___
Okular-devel mailing list
Okular
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #6 from RJVB rjvber...@gmail.com ---
Looks like it's that indeed. I had to add the block to canOpenDocs too
part= Okular::Part(0x7ffb3e05f9f0)
okular(56591) Shell::canOpenDocs: part= Okular::Part(0x7ffb3e05f9f0)
dynamic_castOkular
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #3 from RJVB rjvber...@gmail.com ---
Here's the backtrace requested. Okular was invoked as
/Applications/MacPorts/KDE4/okular.app/Contents/MacOS/okular
https://some.web.site/courriersweb/affichagepdf:pdf/2014239153763 --icon okular
-caption
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #4 from RJVB rjvber...@gmail.com ---
Running Okular with all its debug domains activated through kdebugdialog didn't
teach me anything useful (no output at all).
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.kde.org/show_bug.cgi?id=345765
Bug ID: 345765
Summary: [OS X] okular crashing opening PDF from URL
Product: okular
Version: 0.20.3
Platform: Compiled Sources
OS: OS X
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=345765
--- Comment #2 from RJVB rjvber...@gmail.com ---
Ouch.
I can rebuild okular trying to ensure that it keeps its debug info, but
triggering the bug again is going to be complicated to do exactly the same way.
That PDF was a confirmation of an action I
27 matches
Mail list logo
