Bug 498427

Summary:	okular crashes opening files from menu or shortcut
Product:	[KDE Neon] neon	Reporter:	Mark Elston <melston1777>
Component:	Snaps	Assignee:	Neon Bugs <neon-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	aacid, christoph, kde, sgmoore
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Mark Elston 2025-01-09 13:20:25 UTC

SUMMARY
With okular open I tried to brows to a file and open it.  However, anytime I select the File|Open menu item (or Ctrl-O) okular crashes.

The same thing happens when I try to use the Configure Annotations menu item (and perhaps other menu items that I haven't tried yet).


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 24.04
KDE Plasma Version: 
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1

Comment 1 Albert Astals Cid 2025-01-09 21:24:08 UTC

The form when filling a bug tells you that for crashes we want a backtrace.

Where's the backtrace?

Comment 2 Mark Elston 2025-01-09 22:57:35 UTC

I never saw a backtrace anywhere, nor was there a core file generated.  Is there a process to retrieve a backtrace I can use?

Comment 3 Mark Elston 2025-01-09 23:00:32 UTC

Ok.  I ran it from the command-line.  Here is what it prints out:

/usr/share/libdrm/amdgpu.ids: No such file or directory
kf.config.core: Watching absolute paths is not supported "/snap/okular/162/kf6/usr/share/color-schemes/BreezeLight.colors"
(okular:43117): GLib-GIO-WARNING **: 17:58:06.538: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-io-error-quark, 14)
(okular:43117): GLib-GIO-ERROR **: 17:58:06.638: No GSettings schemas are installed on the system
Trace/breakpoint trap (core dumped)

However, there is no core file generated where I ran it from.

Comment 4 Mark Elston 2025-01-10 02:44:55 UTC

In fact, there are exactly eight amdgpu.ids files on my system, including  `/usr/share/libdrm/amdgpu.ids'.

Comment 5 Sune Vuorela 2025-01-10 08:12:50 UTC

(In reply to Mark Elston from comment #2)
> I never saw a backtrace anywhere, nor was there a core file generated.  Is
> there a process to retrieve a backtrace I can use?

try `coredumpctl`

Comment 6 Mark Elston 2025-01-10 14:39:23 UTC

The backtrace from `coredumpctl gdb` doesn't look too promising:

(gdb) bt
#0  0x0000715b136780df in g_log_structured_array ()
   from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x0000715b136783cc in g_log_default_handler ()
   from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x0000715b13678670 in g_logv ()
   from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x0000715b13678953 in g_log ()
   from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x0000715b0fe81422 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x0000715b101d11fa in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x0000715b101d1b98 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x0000715b101d3bc3 in g_object_new_valist ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x0000715b101d3f4f in g_object_new ()
   from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0

Comment 7 Bug Janitor Service 2025-01-25 03:47:14 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

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

Comment 8 Scarlett Moore 2025-06-11 12:57:18 UTC

This has been fixed since 25.04.1