|
# |
|
|
Темы: 32 Сообщения: 152 Участник с: 12 октября 2011 |
Не могу ничем отсканировать, вылетает через несколько секунд после запуска программ, раньше все работало, в убунте на этом же компе все норм
$simple-scan -d [+0,00s] DEBUG: simple-scan.vala:582: Starting Simple Scan 3.6.0, PID=32025 [+0,00s] DEBUG: Connecting to session manager [+0,04s] DEBUG: ui.vala:1404: Restoring window to 600x400 pixels [+0,14s] DEBUG: scanner.vala:1378: sane_init () -> SANE_STATUS_GOOD [+0,14s] DEBUG: scanner.vala:1384: SANE version 1.0.23 [+0,14s] DEBUG: scanner.vala:1445: Requesting redetection of scan devices [+0,14s] DEBUG: scanner.vala:753: Processing request Ошибка сегментирования (core dumped) $hp-scan -g
HP Linux Imaging and Printing System (ver. 3.12.11)
Scan Utility ver. 2.2
Copyright (c) 2001-14 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
hp-scan[702]: debug: getDeviceUri(None, None, ['hpaio'], {'scan-type': (<built-in function gt>, 0)}, , True)
hp-scan[702]: debug: Mode=0
hp-scan[702]: debug: hp:/usb/HP_LaserJet_Professional_M1132_MFP?serial=000000000QH30D85SI1c: back_end:hp is_hp:True bus:usb model:HP_LaserJet_Professional_M1132_MFP serial:000000000QH30D85SI1c dev_file: host: zc: port:1
hp-scan[702]: debug: Cache miss: hp_laserjet_professional_m1132_mfp
hp-scan[702]: debug: Reading file: /usr/share/hplip/data/models/models.dat
hp-scan[702]: debug: Searching for section [hp_laserjet_professional_m1132_mfp] in file /usr/share/hplip/data/models/models.dat
hp-scan[702]: debug: Found section [hp_laserjet_professional_m1132_mfp] in file /usr/share/hplip/data/models/models.dat
hp-scan[702]: debug: {'hpaio:/usb/HP_LaserJet_Professional_M1132_MFP?serial=000000000QH30D85SI1c': ['HP_LaserJet_Professional_M1132_MFP_2']}
Using device: hpaio:/usb/HP_LaserJet_Professional_M1132_MFP?serial=000000000QH30D85SI1c
warning: No destinations specified. Adding 'file' destination by default.
Ошибка сегментирования (core dumped)
$ xsane Ошибка сегментирования (core dumped) |
|
Natrio |
# |
|
Темы: 48 Сообщения: 4769 Участник с: 08 января 2011 |
Откатите пакет sane на предыдущую версию и попробуйте тогда. |
|
aspiring |
# |
|
Темы: 32 Сообщения: 152 Участник с: 12 октября 2011 |
странно, поставил старую:
sudo pacman -U sane-1.0.22-9-x86_64.pkg.tar.xz потом, как и ожидалось — западло: simple-scan simple-scan: error while loading shared libraries: libgphoto2.so.2: cannot open shared object file: No such file or directory ставлю обратно sudo pacman -S simple-scan и все заработало, возможно нужно было просто переустановить саню,
— респект! |
|
aspiring |
# |
|
Темы: 32 Сообщения: 152 Участник с: 12 октября 2011 |
Сегодня опять вылезла та же ошибка, поставил предыдущю версию
sudo pacman -U sane-1.0.23-2-x86_64.pkg.tar.xz пока работает |
I had problems with segmentation fault in Xsane with my HP4200 USB scanner after upgrading to Ubuntu 20.04 from Ubuntu 18.04.
I found many google suggestions to no avail. I configured and compiled the back end for the HP4200 and it was still crashing.
I enabled the debug messages in the source code and found that the debug messages were telling me that it was crashing always in the same place
a subroutine called do_fine_calibration in the hp4200.c file. In that subroutine memset is called and it appeared that that was where the crash occurred.
If memset is called with a null pointer it tries to access non existent memory. I tried to find if Ubuntu 20.04 did something different in memory management but found nothing.
Anyway it seemed that this code was setting up a large array called registro for which a pointer didn’t seem to exist!
I’m not a memory management guru but after some study i decided to change the registro declaration to set it to 0 when declared
(about line 1377 — int registro[30][5460 * 3] = {0}; with my change)
and then eliminate the code section (line 1496 — about 1505) that memsets the registro array to 0.
After a re ./configuration, make sudo make install and firing up scanimage for a scan, lo and behold the motor took off and began to scan again!
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
LM 20.1 update Xsane segmentation fault [SOLVED -sort of]
Recently updated from Mint 19.3 to 20.1. Xsane worked fine in 19.3. In 20.1, Xsane detects the Epson V370 Photo scanner and opens normally. «Acquire Image» works fine — but as soon as the scan has completed — Xsane shuts down. Running Xsane from command line gives a segmentation fault (core dump) at the point where Xsane closes down. I have deleted the .sane directory, re-installed both sane and xsane — but still get the same result.
Running Xsane from within GIMP 2.10 also causes the shutdown.
Running Epson Scan 2 works fine. Running xscanimage from inside GIMP via «device dialog»works fine but from the epsonscan2 option throws up the following message GIMP message before opening the Epson Scan 2 windows normally
Plug-in crashed: «xsane»
(/usr/lib/gimp/2.0/plug-ins/xsane)
The dying plug-in may have messed up GIMP’s internal state. You may want to save your images and restart GIMP to be on the safe side.
As sane is common to both Epson Scan 2 and Xsane — this appears to be an Xsane problem. I suspect that the Xsane upgrade from 19.3 to 20.1 is the problem — but re-installing Xsane doesn’t seem to fix the problem. Where else should I look?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
Re: LM 20.1 update Xsane segmentation fault
Post
by Micromet »
Returning to this problem: running xsane from terminal produces:
(xsane:9050): Gtk-WARNING **: 16:37:42.019: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.019: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.020: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.020: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.021: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.021: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gtk-WARNING **: 16:37:42.021: Unable to locate theme engine in module_path: «murrine»,
(xsane:9050): Gdk-CRITICAL **: 16:37:51.485: IA__gdk_drawable_unref: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed
(xsane:9050): Gdk-CRITICAL **: 16:37:51.485: IA__gdk_drawable_unref: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed
Then xsane opens and allows me to scan an item before disappearing with the — «Segmentation fault (core dumped)» message
Should I be looking at these Gdk-CRITICAL messages as the culprits? And any idea on how I fix them?
-
jontrv
- Level 2
- Posts: 76
- Joined: Thu Mar 03, 2016 11:47 am
- Location: UK
Re: LM 20.1 update Xsane segmentation fault
Post
by jontrv »
Which version of ‘sane-utils’ do you have, and which kernel ?
The sane-utils in the repository (version 1.0.29-0ubuntu5.2) does not work correctly with kernels in 5.8 series.
My problem was that xsane (version 0.999-8ubuntu2.1) claimed to be scanning, but never actually did anything.
The fix *then* was to install the latest daily release of sane-backends (then 1.0.31). Since that time http://www.sane-project.org/ has released 1.0.32.
I do not know if you will find a fix there, but it may well be possible.
JT:
-
mikeflan
- Level 15
- Posts: 5739
- Joined: Sun Apr 26, 2020 9:28 am
- Location: Houston, TX
Re: LM 20.1 update Xsane segmentation fault
Post
by mikeflan »
Help — About gives:
Xsane version: 0.999
xsane -v in terminal gives:
Code: Select all
$ xsane -v
xsane-0.999 (c) 1998-2013 Oliver Rauch
E-mail: Oliver.Rauch@xsane.org
package xsane-0.999
compiled with GTK-2.24.31
with color management function
with GIMP support, compiled with GIMP-2.8.20
XSane output formats: jpeg, pdf(compr.), png, pnm, ps(compr.), tiff, txt
LM 19.3 Cinnamon version 4.4.8
Linux Kernel: 5.4.0-72-generic
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
Re: LM 20.1 update Xsane segmentation fault
Post
by Micromet »
sane-utils = 1.0.29-0ubuntu5.2
kernel = 5.4.0-73-generic — so not the problematic 5.8 series
Your mention of sane-backends got me thinking.
I have a sane-project/sane-git PPA as a software source — I thought that might be screwing things up — so un-tcked that, restart — Xsane does same fault
Xsane will go through the motions of both preview and scan and shows the scanned image just before it crashes out.
As Xsane recognises my Epson scanner and goes through the action of scanning to produce an image — I don’t think it can be a sane-backend problem
I took the hint about the murrine thene engine being missing. Only item in Synaptic PM was gtk2-engines-murrinei386 — so installed that — no better but that did add murrine-themes and gtk2-engines-murrine to Synaptic. So installed those 2 and removed the i386 version. The Gtk Warnings have now gone — but still left with the Gdk Critical ones and xsane still crashes after scanning. So getting there.
There’s a whole bunch of gdk associated libs in Synaptic which aren’t installed and also some which are — difficult to know where to go next.
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
Re: LM 20.1 update Xsane segmentation fault
Post
by Micromet »
This is the offending line from my syslog — and it’s exactly repeatable on each xsane attempt — I have no idea what I am looking at but will investigate
kernel: [ 2134.497283] xsane[5170]: segfault at 0 ip 00007f9e27b1cf5b sp 00007ffcbaf85020 error 4 in libc-2.31.so[7f9e27abd000+178000]
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
Re: LM 20.1 update Xsane segmentation fault
Post
by Micromet »
Continuing on: I have no idea what the Strace PID output from a running Xsane is showing me — but the last few lines are:
recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(6, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, 0x7ffddd321c60) = 0
openat(AT_FDCWD, «», O_RDONLY) = -1 ENOENT (No such file or directory)
— SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} —
+++ killed by SIGSEGV (core dumped) +++
If anyone can either interpret this output or provide either Strace commands or some other debugging approach for me to investigate — I’d be grateful. While I don’t need to solve this — as other scanning software works OK — this sort of thing bugs me until I get it fixed or I give up.
-
Micromet
- Level 2
- Posts: 60
- Joined: Tue Jan 08, 2019 10:27 am
Re: LM 20.1 update Xsane segmentation fault
Post
by Micromet »
Ok — didn’t solve the segmentation fault — but resolved the Xsane problem. I uninstalled all the other Scanning software that I had installed in the desperate seeking of an app that would work. Also uninstalled Xsane again. Having cleared all that out of the way — then re-installed Xsane — and it now works. So don’t know which scanning software was causing the Xsane problem — or why — personally I don’t care and haven’t got the energy to find out.
-
Redsandro
- Level 4
- Posts: 201
- Joined: Sun Jul 17, 2011 6:40 pm
- Contact:
Re: LM 20.1 update Xsane segmentation fault [SOLVED -sort of]
Post
by Redsandro »
Google brought me here. I have a similar issue.
I recently upgraded from Mint 20 to Mint 21, and epsonscan2 does not work anymore.
It does start the default dialog when there is no scanner connected, but if the scanner is connected and the program attempts to start, it will throw the same message:
«epsonscan2» Segmentation fault (core dumped)
Originally installed and re-installed from epsonscan2-bundle.
I can’t take OP’s lead and remove xsane, because it was never installed.
Глубокоуважаемые участники форума!
Сегодня столкнулся с такой проблемой:
В SL8
unameПри запуске xsane (независимо от пользователи или от root) выдаёт «Ошибка сегментирования».
4.19.35-un-def-alt0.M80P.1 #1 SMP PREEMPT Thu Apr 18 17:42:53 UTC 2019 x86_64 GNU/Linux
В логах
journalctl -fЧто можно сделать?
апр 23 17:38:29 drdav.localdomain kernel: xsane[7104]: segfault at 0 ip 00007f71d9de0ffe sp 00007ffdcd143cc0 error 4 in libc-2.23.so[7f71d9d7b000+199000]
апр 23 17:38:29 drdav.localdomain kernel: Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 85 f6 41 54 55 53 0f 8e 3c 01 00 00 83 fe 01 48 89 fd 41 89 f0 0f 84 25 01 00 00 48 89 d3 <8b> 12 89 d0 25 00 80 00 00 75 5b 4c 8b 8b 88 00 00 00 64 4c 8b 14
« Последнее редактирование: 26.04.2019 09:47:41 от drdav »
Записан
А с каким сканером пытаетесь работать и ставили ли софт со сторонних сайтов?
Записан
Спасибо за отклик.
Сканер Benq S2W 3300U
Bus 001 Device 003: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W 3300U/4300U Кстати, на LiveUSB SL8 он работает, да и когда устанавливал систему xsane достаточно корректно с ним работала.
Установка по инструкци: редактирование snapscan.conf с указанием пути к firmware «/usr/share/sane/snapscan/u176v042.bin»
Возможно, всё случилось после последнего обновления!?
Записан
Советую по ВиКи делать. Запускать из консоли. Проверять сначала через scanimage. Такие падения бывают когда проприетарный бэкэнд ссылается на библиотеку, которая у нас может называться иначе, так что зачастую достаточно сделать нужный симлинк. Например, собранные под Debian тарболы могут промахиваться мимо нашей libm. Ещё важную роль играет то, используете вы saned (sane-server) или нет. При прямом подключении по usb первым делом смотрите lsusb и ls -l /dev/bus/usb/XXX/YYY на предмет того, как отработали правила udev, кто владеет устройством. Сам юзер д.б. добавлен в группу scanner.
Записан
To moan or to solve — that is the question!
Благодарю за отклик!
Повторюсь… Возможно, всё случилось после последнего обновления!? На LiveUSB SL8 он работает, да и когда устанавливал систему xsane достаточно корректно с ним работала
# lsusb
Bus 002 Device 002: ID 04a5:20b0 Acer Peripherals Inc. (now BenQ Corp.) S2W 3300U/4300U
# ls -l /dev/bus/usb/002/002Юзер в группе scanner
crw-rw-r-- 1 root scanner 189, 129 апр 24 14:18 /dev/bus/usb/002/002
# sane-find-scanner -q
found USB scanner (vendor=0x04a5 [Color], product=0x20b0 [ FlatbedScanner 23]) at libusb:002:002
# scanimage -L
Ошибка сегментирования
# journalctl -f
апр 24 14:20:14 drdav.localdomain kernel: scanimage[2068]: segfault at 0 ip 00007f2fb0fd7ffe sp 00007fffac89e360 error 4 in libc-2.23.so[7f2fb0f72000+199000]
апр 24 14:20:14 drdav.localdomain kernel: Code: 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 85 f6 41 54 55 53 0f 8e 3c 01 00 00 83 fe 01 48 89 fd 41 89 f0 0f 84 25 01 00 00 48 89 d3 <8b> 12 89 d0 25 00 80 00 00 75 5b 4c 8b 8b 88 00 00 00 64 4c 8b 14
Подключил вместо вышеуказанного Mustek 1200 CIS LPT — результат тот же.
# xsaneВот, как-то так…
Ошибка сегментирования
Записан
У меня проблемы с xsane как-то давно были после установки драйверов для сканера от производителя оборудования, сейчас уже даже не вспомню подробностей. Такие пакеты как раз могут поломать xsane и не только. В общем вспоминайте, что устанавливали НЕ из бранча.
Записан
Сноси Винду, переходи на Линукс ! 
# scanimage -L
Ошибка сегментирования
Обновление привело к ошибке опосредовано. Раньше был нужный .so-файл, используемый бэкэндом, теперь он поменялся или его не стало. В действительности проблема связана с тем, что драйвер «не из репо». Каждый выполняемый файл этого бэкэнда проверьте с помощью ldd и найдёте битую ссылку. Поправить её будет, скорее всего, несложно. И ещё: можно использовать ключик -v в этой команде, но в данном случае до её работы не доходит, всё сваливается на загрузке бэкэнда. Поэтому самый быстрый способ найти проблему:
apt-get install straceВ выводе ищите сообщения о невозможности открыть файл /usr/lib*.so ближе к концу журнала.
strace scanimage -v -L 2>&1 | tee scan.log
Записан
To moan or to solve — that is the question!
Спасибо за ответы. Не из бранча установлен лишь hplip plugin.
Записан
Так а что в отладочном журнале scan.log?
Записан
To moan or to solve — that is the question!
Благодарю за ответы!
В отладочном журнале scan.log следующее:
Записан
В отладочном журнале scan.log следующее:
Очень хорошо! А что показывают команды:
rpm -qf /usr/lib64/sane/libsane-hpgt2500.so.1
ldd /usr/lib64/sane/libsane-hpgt2500.so.1
rpm -q hplip
cat /var/lib/hp/hplip.state
« Последнее редактирование: 25.04.2019 12:22:37 от klark973 »
Записан
To moan or to solve — that is the question!
Спасибо!
Команды показывают следующее:
# rpm -qf /usr/lib64/sane/libsane-hpgt2500.so.1
предупреждение: файл /usr/lib64/sane/libsane-hpgt2500.so.1 не принадлежит ни одному из пакетов
# ldd /usr/lib64/sane/libsane-hpgt2500.so.1
linux-vdso.so.1 (0x00007fffa349b000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f4a4dfea000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f4a4dde6000)
libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007f4a4dbcd000)
libc.so.6 => /lib64/libc.so.6 (0x00007f4a4d82a000)
/lib64/ld-linux-x86-64.so.2 (0x00007f4a4e524000)
libudev.so.1 => /lib64/libudev.so.1 (0x00007f4a4d605000)
librt.so.1 => /lib64/librt.so.1 (0x00007f4a4d3fd000)
libmount.so.1 => /lib64/libmount.so.1 (0x00007f4a4d1a9000)
libblkid.so.1 => /lib64/libblkid.so.1 (0x00007f4a4cf5f000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f4a4cd38000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007f4a4cb33000)
libpcre.so.3 => /lib64/libpcre.so.3 (0x00007f4a4c8ef000)
# rpm -q hplip
hplip-3.19.3-alt1
# cat /var/lib/hp/hplip.state
[plugin]
installed = 1
eula = 1
version = 3.19.1[code]
Записан
Битых ссылок нет, однако установлена старая версия плагина (hplip-plugin 3.19.1) и обновилась версия hplip (3.19.3-alt1), скорее всего, падает плагин, причём падает молча. Плагин ставился «не из репо», через hp-setup -i под рутом. Надо просто запустить заново эту команду, чтобы переустановить имеющиеся МФУ/принтеры HP, свежая версия плагина должна подтянуться. После этого попробуйте ещё раз что-то отсканировать.
Записан
To moan or to solve — that is the question!
Благодарю!
Плагин новый установил
# cat /var/lib/hp/hplip.stateНо, к сожалению, xsane не запускается.
[plugin]
installed = 1
eula = 1
version = 3.19.3
Записан
Но, к сожалению, xsane не запускается.
Есть ли у вас такой файлик в системе: /usr/share/sane/snapscan/u176v046.bin ? Это его бинарная прошивка. Вообще странно, что спотыкается о кусок hplip-plugin‘а:
Спойлер
[hpgt2500_plugin_9]
src=scan/sane/libsane-hpgt2500-$ARCH.so.1.0.22
trg=/usr/lib64/sane/libsane-hpgt2500-$ARCH.so.1.0.22
link=/usr/lib64/x86_64-linux-gnu/sane/libsane-hpgt2500.so
…
[hpgt2500_plugin_10]
src=scan/sane/libsane-hpgt2500-$ARCH.so.1.0.22
trg=/usr/lib64/sane/libsane-hpgt2500-$ARCH.so.1.0.22
link=/usr/lib64/x86_64-linux-gnu/sane/libsane-hpgt2500.so.1
Версии не те. А главное, этот сканер ставится иначе. Что у вас в файле: /etc/sane.d/snapscan.conf? Есть ли такой вообще? Какая версия: rpm -q sane? Какая версия rpm -q libusb? Установлен ли rpm -q sane-server? Я бы начал с этого:
lsusb # смотрим XXX YYY сканера после перетыканияТут нужен вывод последней команды. Надо понять, по каким правилам udev он вообще сейчас определяется.
udevadm test $(udevadm info -q path -n /dev/bus/usb/XXX/YYY)
Записан
To moan or to solve — that is the question!
I had problems with segmentation fault in Xsane with my HP4200 USB scanner after upgrading to Ubuntu 20.04 from Ubuntu 18.04.
I found many google suggestions to no avail. I configured and compiled the back end for the HP4200 and it was still crashing.
I enabled the debug messages in the source code and found that the debug messages were telling me that it was crashing always in the same place
a subroutine called do_fine_calibration in the hp4200.c file. In that subroutine memset is called and it appeared that that was where the crash occurred.
If memset is called with a null pointer it tries to access non existent memory. I tried to find if Ubuntu 20.04 did something different in memory management but found nothing.
Anyway it seemed that this code was setting up a large array called registro for which a pointer didn’t seem to exist!
I’m not a memory management guru but after some study i decided to change the registro declaration to set it to 0 when declared
(about line 1377 – int registro[30][5460 * 3] = {0}; with my change)
and then eliminate the code section (line 1496 – about 1505) that memsets the registro array to 0.
After a re ./configuration, make sudo make install and firing up scanimage for a scan, lo and behold the motor took off and began to scan again!