[sisyphus] hp sj2200c and sane

[sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

Привет,

Еще одна поптыка заставить работать сканер работавший в сизифе какое-то
время.
Сканер HP ScanJet 2200c (USB). В мастере (и в сизифе одно время) работал.
На сайте sane давно давно в списке полностью поддерживаемых.

Ныне (уже несколько месяцев) он не работает.
Посколько я не знаю как нынче все с usb сканерами устроено (а гугление
выводит только на /dev/usbscanner или права на /proc/bus/usb/...

И так имеем:
morsov@alexey ~ $ sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.
  # Also you need support for SCSI Generic (sg) in your operating system.
  # If using Linux, try "modprobe sg".

found USB scanner (vendor=0x03f0 [Hewlett-Packard], product=0x0605 [HP ScanJet 2200C], chip=LM9832/3)
 at libusb:001:014

morsov@alexey ~ $ ll -d /proc/bus/usb/001/014 
-rw-rw---- 1 root scanner 57 Апр 25 12:51 /proc/bus/usb/001/014

Судя по информации с сайта sane для этого сканера используется plustek.conf
В нем у меня device auto. Пробовал туда прописывать vendor/product id - не помогает.
Пробовал закоментировать в dll.conf все кроме plustek. Тоже не помогает.
Пользователь включен в группу scanner (да и из под рута тоже не видит).

scanimage -L уверяет что устройства не найдено (и xsane), но оно есть, оно обнаруживается
пересоздается в /proc/bus/usb и в логах тоже его при передергивании видно отчетливо.

Вопрос что делать куда копать? Хочу сканер (задолбало уже ради сканирования странички 
грузить vmware с оффтопиком).

-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[playing] Yoko Kanno - ARJUNA into the another world - (2001)

Я почти уверен, что проблема не в этом.
		-- ldv in devel@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

Re: [sisyphus] hp sj2200c and sane

[Vitaly Lipatov]

On Tuesday 25 April 2006 13:05, Alexey Morsov wrote:
>
> scanimage -L уверяет что устройства не найдено (и xsane), но
Покажите из-под root:
# SANE_DEBUG_PLUSTEK=20 scanimage -L

И grep -v "^#" /etc/sane.d/plustek.conf 


-- 
Lav
Виталий Липатов
Санкт-Петербург
GNU! ALT Linux Team! WINE! LaTeX! LyX! http://freesource.info

Re: [sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 12859 bytes --]

On Tue, Apr 25, 2006 at 11:11:34PM +0400, Vitaly Lipatov wrote:
> On Tuesday 25 April 2006 13:05, Alexey Morsov wrote:
> >
> > scanimage -L уверяет что устройства не найдено (и xsane), но
> Покажите из-под root:
> # SANE_DEBUG_PLUSTEK=20 scanimage -L
> 
> И grep -v "^#" /etc/sane.d/plustek.conf 

root@alexey ~ # SANE_DEBUG_PLUSTEK=20 scanimage -L
[sanei_debug] Setting debug level of plustek to 20.
[plustek] Plustek backend V0.50-7, part of sane-backends 1.0.17
[plustek] Retrieving all supported and conntected devices
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0013
[plustek] Checking for 0x07b3-0x0011
[plustek] Checking for 0x07b3-0x0010
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0015
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0016
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0017
[plustek] Checking for 0x07b3-0x0007
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x000f
[plustek] Checking for 0x07b3-0x0005
[plustek] Checking for 0x07b3-0x0014
[plustek] Checking for 0x07b3-0x0012
[plustek] Checking for 0x0400-0x1000
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0400-0x1001
[plustek] Checking for 0x0458-0x2007
[plustek] Checking for 0x0458-0x2008
[plustek] Checking for 0x0458-0x2009
[plustek] Checking for 0x0458-0x2013
[plustek] Checking for 0x0458-0x2015
[plustek] Checking for 0x0458-0x2016
[plustek] Checking for 0x03f0-0x0505
[plustek] Checking for 0x03f0-0x0605
[plustek] Checking for 0x04b8-0x010f
[plustek] Checking for 0x04b8-0x011d
[plustek] Checking for 0x1606-0x0050
[plustek] Checking for 0x1606-0x0060
[plustek] Checking for 0x1606-0x0160
[plustek] Checking for 0x049f-0x001a
[plustek] Checking for 0x04a9-0x2206
[plustek] Checking for 0x04a9-0x2207
[plustek] Checking for 0x04a9-0x2208
[plustek] Checking for 0x04a9-0x220d
[plustek] Checking for 0x04a9-0x220e
[plustek] Checking for 0x04a9-0x2220
[plustek] Available and supported devices:
[plustek] Device: >libusb:001:003< - 0x03f0x0x0605
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] ># or<
[plustek] ># device libusb:bbb:ddd<
[plustek] ># where bbb is the busnumber and ddd the device number<
[plustek] ># make sure that your user has access to /proc/bus/usb/bbb/ddd<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] ># [usb]<
[plustek] ># device /dev/usbscanner<
[plustek] >#<
[plustek] ># or simply<
[plustek] ># [usb]<
[plustek] >#<
[plustek] ># or if you want a specific device but you have no idea about the<
[plustek] ># device node or you use libusb, simply set vendor- and product-ID<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device auto<
[plustek] >#<
[plustek] ># NOTE: autodetection is safe, as it uses the info it got<
[plustek] >#       from the USB subsystem. If you're not using the<
[plustek] >#       autodetection, you MUST have attached that device<
[plustek] >#       at your USB-port, that you have specified...<
[plustek] >#<
[plustek] ><
[plustek] >[usb] 0x03f0 0x0605<
[plustek] next device is a USB device (0x03F0-0x0605)
[plustek] ... next device
[plustek] ><
[plustek] >#<
[plustek] ># options for the previous USB entry<
[plustek] >#<
[plustek] ># switch lamp off after xxx secs, 0 disables the feature<
[plustek] ># (can also be set via frontend)<
[plustek] >option lampOff 300<
[plustek] Decoding option >lampOff<
[plustek] ><
[plustek] ># warmup period in seconds, 0 means no warmup, -1 means auto-warmup<
[plustek] ># (can also be set via frontend)<
[plustek] >option warmup -1<
[plustek] Decoding option >warmup<
[plustek] ><
[plustek] ># 0 means leave lamp-status untouched, not 0 means switch off<
[plustek] ># on sane_close<
[plustek] ># (can also be set via frontend)<
[plustek] >option lOffOnEnd 1<
[plustek] Decoding option >lOffOnEnd<
[plustek] ><
[plustek] >#<
[plustek] ># options to tweak the image start-position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] >#<
[plustek] ># for the normal scan area<
[plustek] >#<
[plustek] >option posOffX 0<
[plustek] Decoding option >posOffX<
[plustek] >option posOffY 0<
[plustek] Decoding option >posOffY<
[plustek] ><
[plustek] ># for transparencies<
[plustek] >option tpaOffX 0<
[plustek] Decoding option >tpaOffX<
[plustek] >option tpaOffY 0<
[plustek] Decoding option >tpaOffY<
[plustek] ><
[plustek] ># for negatives<
[plustek] >option negOffX 0<
[plustek] Decoding option >negOffX<
[plustek] >option negOffY 0<
[plustek] Decoding option >negOffY<
[plustek] ><
[plustek] >#<
[plustek] ># for setting the calibration strip position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] ># -1 means use built in<
[plustek] ># (can also be set via frontend)<
[plustek] >option posShadingY -1<
[plustek] Decoding option >posShadingY<
[plustek] >option tpaShadingY -1<
[plustek] Decoding option >tpaShadingY<
[plustek] >option negShadingY -1<
[plustek] Decoding option >negShadingY<
[plustek] ><
[plustek] >#<
[plustek] ># to invert the negatives, 0 disables the feature<
[plustek] >#<
[plustek] >option invertNegatives 0<
[plustek] Decoding option >invertNegatives<
[plustek] ><
[plustek] >#<
[plustek] ># to disable the internal sensor speedup function,<
[plustek] ># 1 disables the feature<
[plustek] >#<
[plustek] >option disableSpeedup 0<
[plustek] Decoding option >disableSpeedup<
[plustek] ><
[plustek] >#<
[plustek] ># to save/restore coarse calibration data<
[plustek] ># (can also be set via frontend)<
[plustek] >option cacheCalData 0<
[plustek] Decoding option >cacheCalData<
[plustek] ><
[plustek] >#<
[plustek] ># use alternate calibration routines<
[plustek] >#<
[plustek] >option altCalibration 0<
[plustek] Decoding option >altCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping whole calibration step<
[plustek] >#<
[plustek] >option skipCalibration 0<
[plustek] Decoding option >skipCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping entire fine calibration step<
[plustek] ># coarse calibration is done<
[plustek] >#<
[plustek] >option skipFine 0<
[plustek] Decoding option >skipFine<
[plustek] ><
[plustek] >#<
[plustek] ># discard the result of the fine white calibration<
[plustek] >#<
[plustek] >option skipFineWhite 0<
[plustek] Decoding option >skipFineWhite<
[plustek] ><
[plustek] ># for replacing the gain values found during coarse<
[plustek] ># calibration<
[plustek] ># (can also be set via frontend)<
[plustek] >option red_gain   -1<
[plustek] Decoding option >red_gain<
[plustek] >option green_gain -1<
[plustek] Decoding option >green_gain<
[plustek] >option blue_gain  -1<
[plustek] Decoding option >blue_gain<
[plustek] ><
[plustek] ># for replacing the offset values found during coarse<
[plustek] ># calibration<
[plustek] ># (can also be set via frontend)<
[plustek] >option red_offset   -1<
[plustek] Decoding option >red_offset<
[plustek] >option green_offset -1<
[plustek] Decoding option >green_offset<
[plustek] >option blue_offset  -1<
[plustek] Decoding option >blue_offset<
[plustek] ><
[plustek] >#<
[plustek] ># for replacing the default lampoff settings, this<
[plustek] ># works only for CIS devices like CanoScan LiDE20<
[plustek] ># (can also be set via frontend)<
[plustek] >option red_lampoff   -1<
[plustek] Decoding option >red_lampoff<
[plustek] >option green_lampoff -1<
[plustek] Decoding option >green_lampoff<
[plustek] >option blue_lampoff  -1<
[plustek] Decoding option >blue_lampoff<
[plustek] ><
[plustek] >#<
[plustek] ># for adjusting the default gamma values<
[plustek] ># (can also be set via frontend)<
[plustek] >option redGamma         1.0<
[plustek] Decoding option >redGamma<
[plustek] >option greenGamma       1.0<
[plustek] Decoding option >greenGamma<
[plustek] >option blueGamma        1.0<
[plustek] Decoding option >blueGamma<
[plustek] >option grayGamma        1.0<
[plustek] Decoding option >grayGamma<
[plustek] ><
[plustek] >#<
[plustek] ># to enable TPA (EPSON or UMAX, if autodetection fails)<
[plustek] ># 0 means default behaviour as specified in the internal tables<
[plustek] ># 1 means enable (needed for UMAX 3450)<
[plustek] >option enableTPA 0<
[plustek] Decoding option >enableTPA<
[plustek] ><
[plustek] >#<
[plustek] ># model override functionality, currently only available for<
[plustek] ># Mustek devices, using NSCs' vendor ID: 0x0400 and<
[plustek] ># also their product ID: 0x1000 (LM9831) 0x1001 (LM9832)<
[plustek] >#<
[plustek] ># mov/PID    |    0x1000   |   0x1001<
[plustek] ># ---------------------------------------<
[plustek] ># 0 (default)| BearPaw1200 | BearPaw 2400<
[plustek] ># 1          |   ignored   | BearPaw 1200<
[plustek] >#<
[plustek] >option mov 0<
[plustek] Decoding option >mov<
[plustek] ><
[plustek] >#<
[plustek] ># and of course the device-name<
[plustek] >#<
[plustek] ># device /dev/usbscanner<
[plustek] >device auto<
[plustek] Decoding device name >auto<
[plustek] ><
[plustek] >#<
[plustek] ># to define a new device, start with a new section:<
[plustek] ># [usb]<
[plustek] >#<
[plustek] attach (auto, 0xafd86350, (nil))
[plustek] Device configuration:
[plustek] device name  : >auto<
[plustek] USB-ID       : >0x03F0-0x0605<
[plustek] model ovr.   : 0
[plustek] warmup       : -1s
[plustek] lampOff      : 300
[plustek] lampOffOnEnd : yes
[plustek] cacheCalData : no
[plustek] altCalibrate : no
[plustek] skipCalibr.  : no
[plustek] skipFine     : no
[plustek] skipFineWhite: no
[plustek] invertNegs.  : no
[plustek] dis.Speedup  : no
[plustek] pos_x        : 0
[plustek] pos_y        : 0
[plustek] pos_shading_y: -1
[plustek] neg_x        : 0
[plustek] neg_y        : 0
[plustek] neg_shading_y: -1
[plustek] tpa_x        : 0
[plustek] tpa_y        : 0
[plustek] tpa_shading_y: -1
[plustek] red gain     : -1
[plustek] green gain   : -1
[plustek] blue gain    : -1
[plustek] red offset   : -1
[plustek] green offset : -1
[plustek] blue offset  : -1
[plustek] red lampoff  : -1
[plustek] green lampoff: -1
[plustek] blue lampoff : -1
[plustek] red Gamma    : 1.00
[plustek] green Gamma  : 1.00
[plustek] blue Gamma   : 1.00
[plustek] gray Gamma   : 1.00
[plustek] ---------------------
[plustek] usbDev_open(auto,0x03F0-0x0605) - 0x806ded8
[plustek] sanei_access_lock failed: 11
[plustek] open failed: -1
[plustek] sane_get_devices (0xafd88478, 0)

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[plustek] sane_exit
root@alexey ~ # grep -v "^#" /etc/sane.d/plustek.conf


[usb] 0x03f0 0x0605

option lampOff 300

option warmup -1

option lOffOnEnd 1

option posOffX 0
option posOffY 0

option tpaOffX 0
option tpaOffY 0

option negOffX 0
option negOffY 0

option posShadingY -1
option tpaShadingY -1
option negShadingY -1

option invertNegatives 0

option disableSpeedup 0

option cacheCalData 0

option altCalibration 0

option skipCalibration 0

option skipFine 0

option skipFineWhite 0

option red_gain   -1
option green_gain -1
option blue_gain  -1

option red_offset   -1
option green_offset -1
option blue_offset  -1

option red_lampoff   -1
option green_lampoff -1
option blue_lampoff  -1

option redGamma         1.0
option greenGamma       1.0
option blueGamma        1.0
option grayGamma        1.0

option enableTPA 0

option mov 0

device auto


-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[playing] Yoko Kanno - Cowboy Bebop - Ask DNA Single - AsK DNA (2001)

Ставить отдельные пакеты из Сизифа на Мастер 2.4 - верный путь
к подрыву системы. Правда, иногда apt'у удаётся это предупредить.
		-- ktirf in sisyphus@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

Re: [sisyphus] hp sj2200c and sane

[Vitaly Lipatov]

On Wednesday 26 April 2006 11:29, Alexey Morsov wrote:

> [plustek] sanei_access_lock failed: 11
> [plustek] open failed: -1
Проблема в невозможности установить блокировку.
Покажите 
$ rpm -q sane
$ ls -l /var/lock/sane
и
# SANE_DEBUG_SANEI_ACCESS=4 scanimage -L

-- 
Lav
Виталий Липатов
Санкт-Петербург
GNU! ALT Linux Team! WINE! LaTeX! LyX! http://freesource.info

Re: [sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]

On Thu, Apr 27, 2006 at 12:40:55AM +0400, Vitaly Lipatov wrote:
> On Wednesday 26 April 2006 11:29, Alexey Morsov wrote:
> 
> > [plustek] sanei_access_lock failed: 11
> > [plustek] open failed: -1
> Проблема в невозможности установить блокировку.
> Покажите 
> $ rpm -q sane

> $ ls -l /var/lock/sane
morsov@alexey ~ $ rpm -q sane          
sane-1.0.17-alt0.1
morsov@alexey ~ $ ls -l /var/lock/sane 
итого 0

> и
> # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L

t@alexey ~ # ls -l /var/lock/sane                  
total 0
root@alexey ~ # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L
[sanei_debug] Setting debug level of sanei_access to 4.
[sanei_access] sanei_access_init: >plustek<
[sanei_access] sanei_access_lock: devname >libusb:001:003<, timeout: 5
[sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
[sanei_access] sanei_access_lock: open >/var/lock/sane/sane/LCK..libusb:001:003< failed: No such file or directory

Соответственно (не знаю уж почему ее там нет), сделал:

root@alexey ~ # mkdir -m 775 /var/lock/sane/sane
root@alexey ~ # chown root.scanner /var/lock/sane/sane 
root@alexey ~ # ls -l /var/lock/sane 
total 0
drwxrwxr-x 2 root scanner 6 Apr 27 12:05 sane
root@alexey ~ # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L
[sanei_debug] Setting debug level of sanei_access to 4.
[sanei_access] sanei_access_init: >plustek<
[sanei_access] sanei_access_lock: devname >libusb:001:003<, timeout: 5
[sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
[sanei_access] sanei_access_lock: success
[sanei_access] sanei_access_unlock: devname >libusb:001:003<
[sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
[sanei_access] sanei_access_unlock: devname >libusb:001:003<
[sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
device `plustek:libusb:001:003' is a Hewlett-Packard Scanjet 2200c USB flatbed scanner

Теперь снова все работает. Спасибо.
Это у меня такая бяка была или это кто-то чего-то недосоздал (багу вешать)?

-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[playing] Yoko Kanno - Cowboy Bebop - Ask DNA Single - COSMIC DARE (PRETTY WITH A PISTOL) (2001)

> Но дам неплохой совет - прежде чем тестировать патчи нужно
> вытащить mysql из chroot...
Но прежде чем использовать - втащить обратно в чрут.
		-- ldv in sisyphus@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

Re: [sisyphus] hp sj2200c and sane

[Anton Farygin]

Alexey Morsov wrote:
> On Thu, Apr 27, 2006 at 12:40:55AM +0400, Vitaly Lipatov wrote:
>> On Wednesday 26 April 2006 11:29, Alexey Morsov wrote:
>>
>>> [plustek] sanei_access_lock failed: 11
>>> [plustek] open failed: -1
>> Проблема в невозможности установить блокировку.
>> Покажите 
>> $ rpm -q sane
> 
>> $ ls -l /var/lock/sane
> morsov@alexey ~ $ rpm -q sane          
> sane-1.0.17-alt0.1
> morsov@alexey ~ $ ls -l /var/lock/sane 
> итого 0
> 
>> и
>> # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L
> 
> t@alexey ~ # ls -l /var/lock/sane                  
> total 0
> root@alexey ~ # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L
> [sanei_debug] Setting debug level of sanei_access to 4.
> [sanei_access] sanei_access_init: >plustek<
> [sanei_access] sanei_access_lock: devname >libusb:001:003<, timeout: 5
> [sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
> [sanei_access] sanei_access_lock: open >/var/lock/sane/sane/LCK..libusb:001:003< failed: No such file or directory
> 
> Соответственно (не знаю уж почему ее там нет), сделал:
> 
> root@alexey ~ # mkdir -m 775 /var/lock/sane/sane
> root@alexey ~ # chown root.scanner /var/lock/sane/sane 
> root@alexey ~ # ls -l /var/lock/sane 
> total 0
> drwxrwxr-x 2 root scanner 6 Apr 27 12:05 sane
> root@alexey ~ # SANE_DEBUG_SANEI_ACCESS=4 scanimage -L
> [sanei_debug] Setting debug level of sanei_access to 4.
> [sanei_access] sanei_access_init: >plustek<
> [sanei_access] sanei_access_lock: devname >libusb:001:003<, timeout: 5
> [sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
> [sanei_access] sanei_access_lock: success
> [sanei_access] sanei_access_unlock: devname >libusb:001:003<
> [sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
> [sanei_access] sanei_access_unlock: devname >libusb:001:003<
> [sanei_access] sanei_access: lockfile name >/var/lock/sane/sane/LCK..libusb:001:003<
> device `plustek:libusb:001:003' is a Hewlett-Packard Scanjet 2200c USB flatbed scanner
> 
> Теперь снова все работает. Спасибо.
> Это у меня такая бяка была или это кто-то чего-то недосоздал (багу вешать)?

Вешать багу.

Rgds,
Rider

Re: [sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 537 bytes --]

On Thu, Apr 27, 2006 at 01:49:52PM +0400, Anton Farygin wrote:
> Вешать багу.
Хотелось бы уточнитьна кого?
На sane или libsane ?

-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[paused] Yoko Kanno - Cowboy Bebop: Vitaminless - Doggy Dog ()

> Кстати, а зачем нам вообще ещё нужен 2.9x в Сизифе?
> Может выкинуть их вообще?
Хотя бы затем, чтобы не забыть про проблему с apt'ом. :)
		-- ldv in devel@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

Re: [sisyphus] hp sj2200c and sane

[Anton Farygin]

Alexey Morsov wrote:
> On Thu, Apr 27, 2006 at 01:49:52PM +0400, Anton Farygin wrote:
>> Вешать багу.
> Хотелось бы уточнитьна кого?
> На sane или libsane ?

Явно на libsane

Rgds,
Rider

Re: [sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

On Thu, Apr 27, 2006 at 03:16:36PM +0400, Anton Farygin wrote:
> Явно на libsane
#9481


-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[playing] Yoko Kanno - Cowboy Bebop - Ask DNA Single - AsK DNA (2001)

> [...] использовать в пакетах /etc/ld.so.conf.d/ ВМЕСТО
> традиционных записей в /etc/ld.so.conf пока рано.
Ok. Некоторые из нас уже успели заиспользовать "ВМЕСТО" эту
функциональность. В связи с этим ждите новую сборку XFree86.
		-- rider in devel@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

Re: [sisyphus] hp sj2200c and sane

[Vitaly Lipatov]

On Thursday 27 April 2006 12:07, Alexey Morsov wrote:
> On Thu, Apr 27, 2006 at 12:40:55AM +0400, Vitaly Lipatov wrote:
> > On Wednesday 26 April 2006 11:29, Alexey Morsov wrote:
> > > [plustek] sanei_access_lock failed: 11
> > > [plustek] open failed: -1
> >
> > Проблема в невозможности установить блокировку.
> > Покажите
> > $ rpm -q sane
> >
> > $ ls -l /var/lock/sane
>
> morsov@alexey ~ $ rpm -q sane
> sane-1.0.17-alt0.1
...
> Теперь снова все работает. Спасибо.
> Это у меня такая бяка была или это кто-то чего-то недосоздал
> (багу вешать)?
У вас старый sane, в Сизифе уже 2 месяца как всё исправлено.

-- 
Lav
Виталий Липатов
Санкт-Петербург
GNU! ALT Linux Team! WINE! LaTeX! LyX! http://freesource.info

Re: [sisyphus] hp sj2200c and sane

[Alexey Morsov]

[-- Attachment #1: Type: text/plain, Size: 627 bytes --]

On Thu, Apr 27, 2006 at 11:40:15PM +0400, Vitaly Lipatov wrote:

> У вас старый sane, в Сизифе уже 2 месяца как всё исправлено.
Слава богу если так.
А при dist-update таки он бы поправил бы пути к lock файлу (ведь пакет уже
стоит)?


-- 

С уважением,
Алексей Морсов
системный администратор ЗАО "ИК "Риком-Траст"

ICQ: 196-766-290
Jabber: samurai@www.fondmarket.ru
www.ricom.ru
www.fondmarket.ru

[playing] Yoko Kanno - Cowboy Bebop - Tank! THE! BEST! - PIANO BLACK (2004)

> Штатно - vmware-config.pl не видит хидеров
штатно - использовать kernel-modules-vmware от wrar@
		-- lakostis in devel-kernel@

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 481 bytes --]