[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-25 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=470230

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-25 Thread Mikal
https://bugs.kde.org/show_bug.cgi?id=470230

--- Comment #5 from Mikal  ---
I copied all the older 23.03.0-1 poppler dependencies from another machine
(archlinux calls them poppler, poppler-glib and poppler-qt5) and downgraded all
3 of them from 23.05.0-1 and the issue with PDFs stopped happening. I then
updated the deps again to 23.05.0-1 and I could continue to open PDFs
successfully. Perhaps something silently broke my poppler binaries during a
routine update, I'm not sure.

In any case, the issue is resolved and I can't recreate it anymore. This can be
closed now, if it somehow returns I will attach the new traces.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-25 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=470230

--- Comment #4 from Albert Astals Cid  ---
Yeah that is what i wanted but i'm still puzzled how it would crash there.

Can you run 

valgrind okular myfile.pdf

from a terminal and paste the output of valgrind here? (install valgrind first
if you do not have it installed and be patient, valgrind is slow)

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-24 Thread Mikal
https://bugs.kde.org/show_bug.cgi?id=470230

--- Comment #3 from Mikal  ---
(In reply to Albert Astals Cid from comment #1)
> Install the debug symbols thing in archlinux and give us a better backtrace.
> 
> https://wiki.archlinux.org/title/Debugging/Getting_traces

Thanks for looking at my report. I attached the trace, is this what you are
looking for?

gdb output this poppler memory access error before doing the full trace:

Thread 1 (Thread 0x7197df80 (LWP 7395) "okular"):
#0  NameToCharCode::add (this=0x56964410, name=0x7fffb091cf8d , c=119) at
/usr/src/debug/poppler/poppler-23.05.0/poppler

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-24 Thread Mikal
https://bugs.kde.org/show_bug.cgi?id=470230

--- Comment #2 from Mikal  ---
Created attachment 159229
  --> https://bugs.kde.org/attachment.cgi?id=159229=edit
Debug Trace

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 470230] Okular instantly crashes when opening any PDF file

2023-05-24 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=470230

Albert Astals Cid  changed:

   What|Removed |Added

 CC||aa...@kde.org
 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Albert Astals Cid  ---
Install the debug symbols thing in archlinux and give us a better backtrace.

https://wiki.archlinux.org/title/Debugging/Getting_traces

-- 
You are receiving this mail because:
You are watching all bug changes.