[okular] [Bug 527998] New: Okular 26.11.70 crashes on load of PDF files on macOS Tahoe 26.7.2 Was working on 26.7.1
Joseph Apuzzo
bugzilla_noreply at kde.org
Thu Oct 29 13:11:03 GMT 2026
https://bugs.kde.org/show_bug.cgi?id=527998
Bug ID: 527998
Summary: Okular 26.11.70 crashes on load of PDF files on macOS
Tahoe 26.7.2 Was working on 26.7.1
Classification: Applications
Product: okular
Version First unspecified
Reported In:
Platform: macOS (DMG)
OS: macOS
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: okular-devel at kde.org
Reporter: japuzzo at gmail.com
Target Milestone: ---
Created attachment 197789
--> https://bugs.kde.org/attachment.cgi?id=197789&action=edit
macOS crash report
***
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Do not paste LLM output.
Please remove this comment after reading and before submitting - thanks!
***
DESCRIPTION
Crash on PDF load
STEPS TO REPRODUCE
1. Start Okular
2. Open PDF
3. OS Crash
OBSERVED RESULT
Okular crashes and asked to restart in which it will
EXPECTED RESULT
Okular load and display PDF file
SOFTWARE/OS VERSIONS
OS: macOS Tahoe 26.7.2 (25G332) arm64
Host: MacBook Pro (16-inch, 2024, Three Thunderbolt 5 ports)
BIOS (mBoot): 20457.41.3
Board: J616sAP
Kernel: Darwin 25.6.0
CPU: Apple M4 Pro (10+4) @ 4.51 GHz
GPU: Apple M4 Pro (20) @ 1.58 GHz [Integrated]
Memory: 37.07 GiB / 48.00 GiB (77%)
ADDITIONAL INFORMATION
Okular 26.11.70 on Apple silicon terminated on its main thread with
EXC_BREAKPOINT / SIGTRAP; macOS reports a pointer-authentication trap while
CoreGraphics checks an image’s color space.
The stack points to image conversion in the Qt/macOS UI path:
QImage::toCGImage() leads into CoreGraphics, during
QGuiApplication::setOverrideCursor(), while Okular is opening a document. That
suggests an invalid image or color-space object being passed through the
Qt-to-macOS graphics bridge.
The trace doesn’t establish why that object was invalid, and it doesn’t show a
clear PDF-rendering failure. The most useful distinction to test is whether
Okular crashes opening any document or only one specific file; the former
points more toward the app/UI graphics path, while the latter may indicate a
document-specific trigger.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Okular-devel
mailing list