Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Simply trying to start xsane causes it to abort. After some research, it appears a recent update to the package gdk-pixbuf2 caused it. I did a dnf downgrade gdk-pixbuf2 and it downgraded version 2.44.6.to 2.44.3. After that xsane starts successfully. Search through dnf history shows that on 4/19/26 this package was upgraded from 2.44.4 to 2.44.6. Version-Release number of selected component: xsane-0.999-79.fc43 Additional info: reporter: libreport-2.17.15 cmdline: /usr/bin/xsane uid: 1000 type: CCpp executable: /usr/bin/xsane backtrace_rating: 4 rootdir: / kernel: 6.19.12-200.fc43.x86_64 journald_cursor: s=64ec336d505f4916a4cd3358f4037934;i=e33e4;b=b3394521dd3243a4902d5c4cdad94185;m=2639d829e0;t=64ff8d731af83;x=a6835be0e7a97fba cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-xsane runlevel: /bin/sh: line 1: runlevel: command not found reason: xsane killed by SIGSEGV crash_function: gtk_image_set_from_pixmap comment: Simply trying to start xsane causes it to abort. After some research, it appears a recent update to the package gdk-pixbuf2 caused it. I did a dnf downgrade gdk-pixbuf2 and it downgraded version 2.44.6.to 2.44.3. After that xsane starts successfully. Search through dnf history shows that on 4/19/26 this package was upgraded from 2.44.4 to 2.44.6. package: xsane-0.999-79.fc43 xsession_errors: Truncated backtrace: Thread no. 1 (4 frames) #0 gtk_image_set_from_pixmap at /usr/src/debug/gtk2-2.24.33-23.fc43.x86_64/gtk/gtkimage.c:858 #1 gtk_image_new_from_pixmap at /usr/src/debug/gtk2-2.24.33-23.fc43.x86_64/gtk/gtkimage.c:606 #2 xsane_init at ../../src/xsane.c:6048 #3 xsane_interface at ../../src/xsane.c:6145 Potential duplicate: bug 2282034
Created attachment 2137784 [details] File: var_log_messages
Created attachment 2137785 [details] File: cpuinfo
Created attachment 2137786 [details] File: core_backtrace
Created attachment 2137787 [details] File: proc_pid_status
Hi, you're right, it is gdk-pixbuf issue - closing as dupe of pixbuf bug. *** This bug has been marked as a duplicate of bug 2436839 ***