Bug 2460123

Summary: [abrt] xsane: g_type_check_instance_is_fundamentally_a(): xsane killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mark <redhat>
Component: xsaneAssignee: Nils Philippsen <nphilipp>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 43CC: andrew.kavalov, jridky, nphilipp, redhat, zdohnal
Target Milestone: ---Flags: fedora-admin-xmlrpc: mirror+
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard: abrt_hash:a8d81a7fa98b263174d4e1367330ac87cdca6785;VARIANT_ID=kde;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-04-22 14:48:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: proc_pid_status
none
File: maps
none
File: limits
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: backtrace none

Description Mark 2026-04-21 14:55:46 UTC 
Description of problem:
tried to launch xsane from the command line: received the following error message and the option to report it:

(xsane:5518): GdkPixbuf-WARNING **: 14:35:12.682: Error loading XPM image loader: Image type “legacy-xpm” is not supported
Segmentation fault         (core dumped) xsane

Version-Release number of selected component:
xsane-0.999-79.fc43

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         xsane killed by SIGSEGV
journald_cursor: s=fd33adabb53c4f558ee22f54832fda8c;i=57579e;b=7dd44c5fde6a4de0aa571275f3702c69;m=230911c6;t=64fcf3b47fd4c;x=45e61433d0e7eefb
executable:     /usr/bin/xsane
cmdline:        xsane
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.konsole-2128.scope/tab(2295).scope
rootdir:        /
uid:            1000
kernel:         6.18.15-400.asahi.fc43.aarch64+16k
package:        xsane-0.999-79.fc43
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: g_type_check_instance_is_fundamentally_a

Truncated backtrace:
Thread no. 1 (1 frames)
 #0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:3915
Comment 1 Mark 2026-04-21 14:55:48 UTC 
Created attachment 2137791 [details]
File: proc_pid_status
Comment 2 Mark 2026-04-21 14:55:50 UTC 
Created attachment 2137792 [details]
File: maps
Comment 3 Mark 2026-04-21 14:55:51 UTC 
Created attachment 2137793 [details]
File: limits
Comment 4 Mark 2026-04-21 14:55:52 UTC 
Created attachment 2137794 [details]
File: environ
Comment 5 Mark 2026-04-21 14:55:53 UTC 
Created attachment 2137795 [details]
File: open_fds
Comment 6 Mark 2026-04-21 14:55:54 UTC 
Created attachment 2137796 [details]
File: mountinfo
Comment 7 Mark 2026-04-21 14:55:55 UTC 
Created attachment 2137797 [details]
File: os_info
Comment 8 Mark 2026-04-21 14:55:57 UTC 
Created attachment 2137798 [details]
File: cpuinfo
Comment 9 Mark 2026-04-21 14:55:58 UTC 
Created attachment 2137799 [details]
File: core_backtrace
Comment 10 Mark 2026-04-21 14:55:59 UTC 
Created attachment 2137800 [details]
File: exploitable
Comment 11 Mark 2026-04-21 14:56:00 UTC 
Created attachment 2137801 [details]
File: dso_list
Comment 12 Mark 2026-04-21 14:56:02 UTC 
Created attachment 2137802 [details]
File: backtrace
Comment 13 Zdenek Dohnal 2026-04-22 14:48:00 UTC 
Hi,

there are several issues caused by bad gdk-pixbuf2 update.

*** This bug has been marked as a duplicate of bug 2436839 ***
Comment 14 NM 2026-04-22 15:13:27 UTC 
I observe same issues in FC 6.19.12-200.fc43.x86_64