Bug 2213448

Created attachment 1969681 [details]
File: core_backtrace

Created attachment 1969682 [details]
File: environ

Created attachment 1969683 [details]
File: cpuinfo

Created attachment 1969684 [details]
File: open_fds

Created attachment 1969685 [details]
File: proc_pid_status

Created attachment 1969686 [details]
File: exploitable

Created attachment 1969687 [details]
File: os_info

Created attachment 1969688 [details]
File: dso_list

Created attachment 1969689 [details]
File: backtrace

Created attachment 1969690 [details]
File: maps

Created attachment 1969691 [details]
File: mountinfo

Created attachment 1969692 [details]
File: limits

Attempted exiting the program without saving my scans.


reporter:       libreport-2.17.11
type:           CCpp
reason:         simple-scan killed by SIGSEGV
journald_cursor: s=5210615ba23b434787c8682bc5513d51;i=a4fb9;b=2aacb1d53ffb4063aef3b12578998e95;m=1a046cf3e;t=601fb98a68a80;x=167650ac2b19074f
executable:     /usr/bin/simple-scan
cmdline:        /usr/bin/simple-scan
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-gnome-simple\x2dscan-14367.scope
rootdir:        /
uid:            1000
kernel:         6.4.6-200.fc38.x86_64
package:        simple-scan-44.0-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: gtk_application_impl_uninhibit
comment:        Attempted exiting the program without saving my scans.

Heppened when closing the scanning window, after the click on "Do not save" when asked.
Before, the scanner was frozzen, the scan was to early in its boot process and was unresponsive. Consequence in simplescan was blank square window instead of scan, re-starting the scan was unhelpfull.
Managed to get scan finally running after closing and re-opening simplescan.


reporter:       libreport-2.17.11
cmdline:        /usr/bin/simple-scan
executable:     /usr/bin/simple-scan
kernel:         6.6.2-101.fc38.x86_64
type:           CCpp
runlevel:       N 5
journald_cursor: s=9163d6964425479b9af2979d40e69819;i=f2cd0c;b=374543df32fc47259c9fef003dbe39be;m=549bc9170;t=60b63ef3c17fb;x=ad94228fc614ba2
reason:         simple-scan killed by SIGSEGV
backtrace_rating: 4
crash_function: gtk_application_impl_uninhibit
uid:            1000
rootdir:        /
package:        simple-scan-44.0-1.fc38

I was scanning old (paper) articles through simple-scan in Fedora 38 (KDE). Other applications in use at the same time: Dolphin, Okular and Mozilla Firefox (all of them updated to the last version). I scanned about 100 pages, when the application unexpectedly freezed (but the scanner was still running), then produced a sign saying it had stopped. This has happened several times in this month and the only way I could find to start the work again is to close everything and restart anew (which is a nuisance)


reporter:       libreport-2.17.11
type:           CCpp
reason:         simple-scan killed by SIGSEGV
journald_cursor: s=786c4c494cf74287b2b53ff45db91b0d;i=2849a3;b=40c3eb9b38ec4be59030efcdb753dcf9;m=10364aee7;t=60c3cb8ff09a1;x=98b188fd4976f49b
executable:     /usr/bin/simple-scan
cmdline:        /usr/bin/simple-scan
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-simple\x2dscan-6ad548db2a13479da25bafc780327d6d.scope
rootdir:        /
uid:            1000
kernel:         6.6.4-100.fc38.x86_64
package:        simple-scan-44.0-1.fc38
runlevel:       N 5
backtrace_rating: 4
crash_function: gtk_application_impl_uninhibit
comment:        I was scanning old (paper) articles through simple-scan in Fedora 38 (KDE). Other applications in use at the same time: Dolphin, Okular and Mozilla Firefox (all of them updated to the last version). I scanned about 100 pages, when the application unexpectedly freezed (but the scanner was still running), then produced a sign saying it had stopped. This has happened several times in this month and the only way I could find to start the work again is to close everything and restart anew (which is a nuisance)

Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.