Description of problem: - Started scanning at 4800dpi - Was gone for a coffee - By returning, XSane has crashed Version-Release number of selected component: xsane-0.999-29.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: xsane crash_function: __memmove_sse2_unaligned_erms executable: /usr/bin/xsane journald_cursor: s=deaa87c5231d409baee22892d13e899f;i=34226;b=6d3bf30f62994d2092c210d4ab63be99;m=1bd73df1;t=583e4fd51c25a;x=3809b321d5189c04 kernel: 4.20.14-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memmove_sse2_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:460 #1 xsane_viewer_read_image at ../../src/xsane-viewer.c:2547 #2 xsane_viewer_new at ../../src/xsane-viewer.c:3121 #3 xsane_scan_done at ../../src/xsane-scan.c:1226 #4 xsane_read_image_data at ../../src/xsane-scan.c:551 #5 xsane_start_scan at ../../src/xsane-scan.c:1869 #6 xsane_scan_dialog at ../../src/xsane-scan.c:2169 #11 gtk_real_button_released at gtkbutton.c:1712 #16 gtk_button_button_release at gtkbutton.c:1604 #18 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:84 Potential duplicate: bug 1595682
Created attachment 1543494 [details] File: backtrace
Created attachment 1543495 [details] File: cgroup
Created attachment 1543496 [details] File: core_backtrace
Created attachment 1543497 [details] File: cpuinfo
Created attachment 1543498 [details] File: dso_list
Created attachment 1543499 [details] File: environ
Created attachment 1543500 [details] File: exploitable
Created attachment 1543501 [details] File: limits
Created attachment 1543502 [details] File: maps
Created attachment 1543503 [details] File: open_fds
Created attachment 1543504 [details] File: proc_pid_status
Hi Steve, thank you for reporting the issue! Unfortunately, I do not have a scanner with 4800dpi support, so I'm not able to reproduce, but Tristan made a good point in previous report - the program falls when it is trying to create named file. I'll see what I can do.
*** Bug 1595682 has been marked as a duplicate of this bug. ***
It seems window widget is not big enough to store row of 4800dpi... I would like to confirm my theory - would you mind trying this scratch build https://koji.fedoraproject.org/koji/taskinfo?taskID=33457353 ?
Zdenek, this scratch build also crashes at the end of scanning.
Probably not enough space again... it was only one shot to try to prove my theory. Would you mind providing coredump when xsane crashes and xsane files from /tmp? You get coredump when you set 'ulimit -c unlimited', delete content of /proc/sys/kernel/core_pattern, put 'core' string into the file and run xsane. When xsane crashes, coredump will be created in current directory (look like <PID>.core). f.e. https://radek.io/2012/02/11/core-dumps-in-fedora/
The desired coredump of xsane (650MB): https://send.firefox.com/download/cf02c62a23/#WjFCvkXJGWFkfB5mp4axWA
Thank you! Would you mind providing xsane files from /tmp too? Because there are specific settings in that files which I can help me a little.
These /tmp files (xsane-preview-level*) are all 0 bytes big, they are empty.
Hmm... when I debugged xsane I had a file named 'xsane-conversion-<my-scanner>' there... would you mind run xsane in gdb, set breakpoint on xsane_viewer_read_image, run the binary and look into /tmp if there is a similar file?
Ah, you mean this file. I thought this is an image (1.1GB): https://send.firefox.com/download/8a6dc30258/#WZAOCb4fv9DF1_KKxC3i0w
Thank you for the file! I had hope we have somehow similar machines, so coredump would work for me and I could play with it without any more info needed from you, but no luck with it... would you mind installing gtk2-debuginfo, creating a coredump as in https://bugzilla.redhat.com/show_bug.cgi?id=1688085#c16 , open it in gdb (gdb /usr/bin/xsane core.<PID>), run 'bt full', copying its output into a text file and attaching the file in the bugzilla as attachment?
Created attachment 1544368 [details] Output of gdb > bt full
I'm deeply sorry - I forgot to mention you need to have xsane-debuginfo installed too (I thought you already have, since backtrace from abrt has debug symbols). Would you mind repeating the last comment with xsane-debuginfo installed?
I'm sorry too, but xsane-debuginfo is (was) already installed.
Hmm... because there is not any xsane function in the latest backtrace you attached... are you sure you opened it like: $ gdb /usr/bin/xsane <your_coredump_file> ?
I forgot to make a new coredump. In progress...
So this is very strange. Xsane (0.999.30) is not crashing anymore. I can not reproduce this bug again. But why?
Tristan had a theory about xsane will crash when your /tmp (and / in matter of speaking) gets full with xsane tmp file (since pixmap with 4800dpi has over 1GB...), do not you have now more space in /tmp?
No, i have not more space in tmp. My tmp is about 8 GB, where about 2 gb is needed for the scan. The rest is unused.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.