Description of problem: Mageia 7-x86-64 fully updated. When launching xscanimage from the Plasma menu or from the CLI, it simply crashes wit segmentation fault. If you happen to have two scanning devices connected, then the dialogue appears to select one of the devices, but then - no matter which you choose - the crash occurs. Version-Release number of selected component (if applicable): How reproducible: Always.
(In reply to Herman Viaene from comment #0) > Description of problem: > Mageia 7-x86-64 fully updated. 7 or 8 ? ;) I think this is on 8 because you report this with 8 as version above. XSaneImage comes from sane-frontends RPM. Reproduced on my system. No evident segfault: no UI at all. No lines in system journal. Thanks for reporting this bug. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it)
Source RPM: (none) => sane-frontends-1.0.14-27.mga8.src.rpmAssignee: bugsquad => pkg-bugsCC: (none) => geiger.david68210, jani.valimaa, ouaurelienKeywords: (none) => FOR_ERRATA8
Workaround: use simple-scan.
OOOhh no. In facts it runs fine in Mageia 8: Under gdb: (gdb) run Starting program: /usr/bin/xscanimage [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff5602640 (LWP 36291)] [xscanimage] No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by sane-find-scanner (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [Thread 0x7ffff5602640 (LWP 36291) exited] [Inferior 1 (process 36287) exited normally] (gdb) q Strange behaviour to not tell user that there is no scanner available: you must switch it ON before. Now that I switch it ON: (gdb) run Starting program: /usr/bin/xscanimage [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7ffff5602640 (LWP 39486)] ** (xscanimage:39481): WARNING **: 14:18:41.870: Invalid borders specified for theme pixmap: /usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png, borders don't fit within the image [Thread 0x7ffff5fccd00 (LWP 39481) exited] [Inferior 1 (process 39481) exited normally] It displays its main UI and I am able to scan, also to quit it. So this is for M7?
Keywords: FOR_ERRATA8 => (none)
7 it is, changed version on top of page
Version: 8 => 7
OK. I don't have now a 7 system. Leaving this for packagers. Updating SRPM.
Source RPM: sane-frontends-1.0.14-27.mga8.src.rpm => sane-frontends-1.0.14-23.mga7.src.rpm
Hi Herman Thank you for reporting here. Initial discussion: https://forums.mageia.org/en/viewtopic.php?f=24&t=13924 My scanner is an Epson Perfection 1660 photo, from last millenium. Experiment: If /etc/sane.d/dll.conf does not contain the line epson2 then xscanimage replies it do not find the scanner. If the line is there, and scanner connected and switched on, it segfaults. My /etc/sane.d/dll.d folder is empty. Not a problem for me personally, as i prefer xsane, that works perfectly, as every year This is on my mga7-64 Plasma + multi-DE workstation
CC: (none) => fri
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Just checked: still segmentation fault in M 8.
Version: 7 => 8CC: (none) => marja11
Doh, we could probably blame the heat... Fresh entered: Bug 30702 *** This bug has been marked as a duplicate of bug 30702 ***
Resolution: (none) => DUPLICATEStatus: NEW => RESOLVED
Not really. It did work on M8 since then, I've used it every so often.
I meant the dozing effect heat have on our grey matter between ears :)
I got that, but I objected declaring this a duplicate of 30702. Since this bug has somehow been handled, it is marked resolved. The new bug 30702 manifests itself in the same way, but its root cause may be completely different.
OK. Lets see if we can get a new complete stack, and what fun it brings.
(In reply to Herman Viaene from comment #10) > Not really. It did work on M8 since then, I've used it every so often. (In reply to Herman Viaene from comment #12) > I got that, but I objected declaring this a duplicate of 30702. Since this > bug has somehow been handled, it is marked resolved. The new bug 30702 > manifests itself in the same way, but its root cause may be completely > different. I agree, not only because you report that the issue in this report got fixed, but also because, even if it would be the same issue, then bug 30702 would be a duplicate of this one and not the other way around
Resolution: DUPLICATE => FIXED
Yes FIXED is better. As for when we mark a bug duplicate, we sometimes mark the old one as dupe, when the newer have more up to date symptoms, tests etc. Not logical by the name, but effective.