Comme demandé dans le premier message du tutoriel
Retour utilisable de commande
Pour
ajouter toi-même les balises code à ton précédent message #4 :
- Cliquer sur le lien « Modifier » en bas à droite du message
- Sélectionner le texte
- Cliquer sur le <> de l'éditeur de message
moko138 a écrit1) Les balises-code sont les < > (crochets bleus) de la barre de mise en forme.
En séparant bien les retours :
comme
cela.
cat /etc/lsb-release && uname -i && groups && lsusb
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
x86_64
azerty adm cdrom sudo dip plugdev lpadmin lxd sambashare
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 043d:013f Lexmark International, Inc.
Bus 001 Device 004: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 003: ID 04ca:0030 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
C- Concernant le scanner :
dpkg -l | grep sane
ii libsane:amd64 1.0.29-0ubuntu5.2 amd64 API library for scanners
ii libsane-common 1.0.29-0ubuntu5.2 all API library for scanners -- documentation and support files
ii libsane-hpaio:amd64 3.20.3+dfsg0-2 amd64 HP SANE backend for multi-function peripherals
ii sane-utils 1.0.29-0ubuntu5.2 amd64 API library for scanners -- utilities
sudo sane-find-scanner -q
found USB scanner (vendor=0x043d [Lexmark], product=0x013f [5600-6600 Series]) at libusb:001:005
could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
scanimage -L
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).
ls /etc/sane.d/
abaton.conf dmc.conf Lexmark08_1_0_0.conf s9036.conf
agfafocus.conf epjitsu.conf lexmark.conf saned.conf
apple.conf epson2.conf ma1509.conf sceptre.conf
artec.conf epson.conf magicolor.conf sharp.conf
artec_eplus48u.conf epsonds.conf matsushita.conf sm3840.conf
avision.conf escl.conf microtek2.conf snapscan.conf
bh.conf fujitsu.conf microtek.conf sp15c.conf
canon630u.conf genesys.conf mustek.conf st400.conf
canon.conf gphoto2.conf mustek_pp.conf stv680.conf
canon_dr.conf gt68xx.conf mustek_usb.conf tamarack.conf
canon_pp.conf hp3900.conf nec.conf teco1.conf
cardscan.conf hp4200.conf net.conf teco2.conf
coolscan2.conf hp5400.conf p5.conf teco3.conf
coolscan3.conf hp.conf pie.conf test.conf
coolscan.conf hpsj5s.conf pieusb.conf u12.conf
dc210.conf hs2p.conf pixma.conf umax1220u.conf
dc240.conf ibm.conf plustek.conf umax.conf
dc25.conf kodakaio.conf plustek_pp.conf umax_pp.conf
dell1600n_net.conf kodak.conf qcam.conf xerox_mfp.conf
dll.conf kvs1025.conf ricoh.conf
dll.d leo.conf rts8891.conf
cat /etc/sane.d/dll.conf
# dll.conf - Configuration file for the SANE dynamic backend loader
#
# Backends can also be enabled by configuration snippets under the dll.d/
# directory -- third party backends can drop their configuration file in
# this in this directory, named after the backend.
ls /lib/udev/rules.d | grep libsane
60-libsane.rules
#
# The next line enables the network backend; comment it out if you don't
# need to use a remote SANE scanner over the network -- see sane-net(5)
# and saned(8) for details.
net
abaton
agfafocus
apple
artec
artec_eplus48u
as6e
avision
bh
canon
canon630u
canon_dr
#canon_pp
cardscan
coolscan
#coolscan2
coolscan3
#dc210
#dc240
#dc25
dell1600n_net
dmc
epjitsu
#epson
epson2
epsonds
escl
fujitsu
genesys
#gphoto2
gt68xx
hp
hp3500
hp3900
hp4200
hp5400
hp5590
hpljm1005
hpsj5s
hs2p
ibm
kodak
kodakaio
kvs1025
kvs20xx
kvs40xx
leo
lexmark
ma1509
magicolor
matsushita
microtek
microtek2
mustek
#mustek_pp
mustek_usb
mustek_usb2
nec
niash
#p5
pie
pieusb
pint
pixma
plustek
#plustek_pp
#pnm
qcam
ricoh
ricoh2
rts8891
s9036
sceptre
sharp
sm3600
sm3840
snapscan
sp15c
#st400
#stv680
tamarack
teco1
teco2
teco3
#test
u12
umax
umax1220u
#umax_pp
v4l
xerox_mfp
Lexmark08_1_0₀
Voir règles du forum > balises BB code
Balise CODE :
C'est la balise à utiliser pour donner de longs messages d'erreurs, des contenus de fichiers de configuration, des commandes à taper, etc … Elle permet des messages plus "compacts", et est moins ambiguë que d'autres polices sur certains caractères.
Mais pas pour la totalité du message, il fallait mettre les balises sur chaque pavé.