Bug 473476

Summary: Okular crashing (SIGSEGV) when saving a PDF
Product: [Applications] okular Reporter: Bart Ribbers <bribbers>
Component: generalAssignee: Okular developers <okular-devel>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aacid
Priority: NOR    
Version: 23.04.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Okular through Valgrind output

Description Bart Ribbers 2023-08-17 14:22:55 UTC 
SUMMARY
This happens seemingly in KIO, but I only experience it through Okular. Happens every time I make any kind of modification to a PDF and try to save it.

Thread 25 "KIO::WorkerThre" received signal SIGSEGV, Segmentation fault.
[Switching to LWP 9837]
0x00007fffdf1f0789 in ?? () from /usr/lib/qt5/plugins/kf5/kio/kio_file.so
(gdb) bt
#0  0x00007fffdf1f0789 in ?? () from /usr/lib/qt5/plugins/kf5/kio/kio_file.so
#1  0x00007ffff7c07713 in KIO::SlaveBase::dispatch(int, QByteArray const&) () from /usr/lib/libKF5KIOCore.so.5
#2  0x00007ffff7c08326 in KIO::SlaveBase::dispatchLoop() () from /usr/lib/libKF5KIOCore.so.5
#3  0x00007ffff7ca2935 in ?? () from /usr/lib/libKF5KIOCore.so.5
#4  0x00007ffff64ac9db in operator() (__closure=<optimized out>) at thread/qthread_unix.cpp:350
#5  (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=...) at thread/qthread_unix.cpp:287
#6  QThreadPrivate::start (arg=0x7fffe37ab620) at thread/qthread_unix.cpp:310
#7  0x00007ffff7fb8239 in start (p=0x7fffdd1f5860) at src/thread/pthread_create.c:207
#8  0x00007ffff7fba83a in __clone () at src/thread/x86_64/clone.s:22

STEPS TO REPRODUCE
1. Open any PDF
2. Add some kind of annotations
3. Save the PDF

OBSERVED RESULT
Okular crashes instantly

EXPECTED RESULT
Okular saving the file properly

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Alpine Linux edge
(available in About System)
KDE Plasma Version: 5.27.7
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10 with KDE patches
Comment 1 Albert Astals Cid 2023-08-17 22:43:15 UTC 
Your backtrace is not very useful. Get yourself debug symbols and post it again.

Ideally also run this through valgrind and tell us what valgrind says.
Comment 2 Bug Janitor Service 2023-09-01 03:45:31 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bart Ribbers 2023-09-01 09:11:39 UTC 
Created attachment 161324 [details]
Okular through Valgrind output

I did have debug symbols installed, of both Okular and Kio. It didn't change the backtrace unfortunately.

Not sure how useful the Valgrind output is but it's attached.
Comment 4 Albert Astals Cid 2023-09-04 20:13:53 UTC 
Not super useful sadly :(
Comment 5 Bug Janitor Service 2023-09-19 03:45:38 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-10-04 03:47:04 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!