[resolu] instalation d'une imprimante photocopieur toshiba

eturnal · Le 04/07/2007, à 17:38

bonjour
je voudrais installer une imprimante fax photocopieur toshiba e-studio45.
j'ai recuperé un driver linux sur le site du fabriquant , l'ai drécompresser dans /usr/local/bin
il y a un setup que je me suis empressé de lancer .
là c'est moins bien , voilà ce que me renvoi la console

root@technique:/usr/local/bin/toshiba2.1/ps/Linux2.1# ./setup
cp: ne peut créer le fichier régulier `/usr/lib/X11/app-defaults/Setup-EFTPS97': Aucun fichier ou répertoire de ce type
cp: ne peut créer le fichier régulier `/usr/lib/X11/app-defaults/Setup-EFTPS97': Aucun fichier ou répertoire de ce type
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfBeginLine
Warning: ... found while parsing ':<Key>osfBeginLine: ManagerGadgetTraverseHome()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfHelp
Warning: ... found while parsing ':<Key>osfHelp: ManagerGadgetHelp()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfPrimaryPaste
Warning: ... found while parsing ':m <Key>osfPrimaryPaste:cut-primary()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfHelp
Warning: ... found while parsing ':<Key>osfHelp: Help()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfCancel
Warning: ... found while parsing ':<Key>osfCancel: MenuEscape()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: ArmAndActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfBeginLine
Warning: ... found while parsing ':c <Key>osfBeginLine: TraverseTab(Home)'
Warning: String to AcceleratorTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfBeginLine
Warning: ... found while parsing ':c <Key>osfBeginLine: TraverseTab(Home)'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfUp
Warning: ... found while parsing '<Key>osfUp: SpinBNext()'
Warning: String to AcceleratorTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfUp
Warning: ... found while parsing ':<Key>osfUp: SpinBNext()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfPrimaryPaste
Warning: ... found while parsing ':m <Key>osfPrimaryPaste:cut-primary()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: ManagerGadgetSelect()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: MenuBarGadgetSelect()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfHelp
Warning: ... found while parsing ':<Key>osfHelp: MenuHelp()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfSelect
Warning: ... found while parsing ':<Key>osfSelect: ArmAndActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: ManagerParentActivate()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfBeginLine
Warning: ... found while parsing ':s c <Key>osfBeginLine: ListBeginDataExtend()'
Warning: String to TranslationTable conversion encountered errors
Warning: translation table syntax error: Unknown keysym name: osfActivate
Warning: ... found while parsing ':<Key>osfActivate: PrimitiveParentActivate()'
Warning: String to TranslationTable conversion encountered errors

neanmoins la fenetre du setup s'ouvre me demandant de specifier un " print queue"
la je ne sais pas dutout ce que cela signifie
me disant aussi qu'il n'y a "no print queue instaled"
par ailleur je n'arrive pas a remplir les cases mon clavier semble inopperant sur cette fenetre

ma distrib c'est une Feisty toute a jour
voici un lien vers le site toshiba et le driver
http://www.toshiba.fr/tfis/notre_offre/drivers.asp

si quelqu'un a une idée j'en serais ravis

Dernière modification par eturnal (Le 18/03/2008, à 18:56)

pmdzlineur · Le 04/07/2007, à 20:22

tu as sans doute un readme
que dit-il ?

eturnal · Le 05/07/2007, à 15:33

salut

voici le fichier d'aide a l'installation
je ne conprend pas bien l'anglais

SETUP INSTALLATION PROGRAM

Depending on your network environment, distribution of clients, and
planned print configuration, you may run only server installations
of the Unix driver, or both client and server installations.

PRE-INSTALLATION PROCEDURES
Before running server or client install program, review the
following points:
* Log in as the superuser (root) of the system to ensure that all
files are installed to their correct location.
* The installation program can be executed from the current folder,
or from a local copy of the installation folder. We recommend
making a local copy of the installation folder. It is important
to run it where it is located. For one, it uses the Setup
resource file for defining its Motif-based user interface.
* If a print queue would be re-installed, uninstall it first before
re-installing to ensure that the driver is updated correctly.
The setup installation program provides the capability to un-install
print queues.
* The user interface was developed using Motif 1.2, Motif 2.1
and C programming language. Except for Linux systems, it is required
that the Motif 2.1 or Motif 1.2 be installed on the system where
setup installation program will be used and where the configuration
program will be installed. For safety, use the "install" script
utility for installing as it performs initialization checks before
launching the setup installation program.
* To launch the setup installation program in GUI mode, the
DISPLAY environment variable must be set. The user must manually
set this on the command line. For example, type "DISPLAY = host:0"
on the command line. "host" is the name of the terminal where
setup would be launched. It can also be the IP address of the
said terminal. After assigning value to DISPLAY, export the
environment variable by typing "export DISPLAY" on the command
line. If setup cannot still launch in GUI mode, you may need
to add the terminal as in the hosts file, done by typing
"xhost host" on the command line. Please coordinate with your
system administrator on how to configure your system for running
programs with GUI.
* If DISPLAY is not set, the setup installation program will run
in Text mode. The installation program detects the system
capability for graphics and can run in either Text or GUI mode.
* Man pages must be updated to customize it to your need. Currently,
the man-pages contains a place-holder for the contact info for
troubleshooting. You can update this with a correct contact info.
NOTE: Do not modify application names such as "EFTPS35" as the
installation program automatically parses it.
* Update text files that are used by the driver as Help files for
further customization. These files are the Setup.txt and
F533Readme.txt

install Installation Script
The install script is the installation utility and is the secure
way for installing or un-installing the Unix driver. It performs
initial system checks before actually launching the setup
installation program. Its major role is to check if Motif library
is installed in the target system. This is provided for convenience
to avoid unexpected system errors when launching the setup
installation program directly on systems without Motif support.

The install installation script will show an error message if it
cannot find the Motif library in the system, except for Linux,
where the driver is built to run even on systems without Motif
support. If you are sure that you have Motif installed in the
system, you can use the setup installation program directly.

The install installation script assumes pre-defined libraries
for determining whether the systems supports Motif or not.

The script checks if the libraries below exist in their
specified locations:

Platform Library location
HP-UX /usr/lib/libXm.2
Sun Solaris (SPARC) /usr/lib/libXm.so.4
Sun Solaris (Intel) /usr/lib/libXm.so.4
IBM AIX /usr/lib/libXm.a
Red Hat Linux None

If not, the script will show an appropriate message.
If you think Motif is installed in the system, you can also
try running setup installation program directly on the
command line: ./setup
* If it fails (crashes), please take note of any error
message you get from the system and send it to us. This
would help us update the install script to reflect whatever
library or file the setup installation program may require
to run successfully in your system.
* BUT if setup runs and shows the user interface, that
could mean that it has found the Motif library somewhere
in your system, meaning, you have a different location
than /usr/lib for the Motif library. In this case, you
can modify the install script to reflect this library
path. You can contact us if you like us to do this update
for you - just inform us the correct library path for
your target system.

SYNTAX
./install [-uh] [[q:]<queue>] [s:<server>] [p:<portvalue>]
[t:<insttype>] [g:<guitype>] [cdepth:<dval>]

To run setup directly, use "setup" in the same syntax, as:
./setup [-uh] [[q:]<queue>] [s:<server>] [p:<portvalue>]
[t:<insttype>] [g:<guitype>] [cdepth:<dval>]

If no parameter is specified, this launches the program in
graphical install mode.

Parameters that are enclosed in square brackets are optional.

-h Prints the usage guide. If no print queue related parameter
is specified, the program will terminate. Otherwise, it will
launch the installation program either in graphical or text
mode, depending on value of the parameter "g".
-u Uninstalls the specified <queue>
[q:]<queue> The name of the local print queue to be set up or
uninstalled. "q:" is optional. Any parameter without the tag
is assumed to be a print queue name. Only the last <queue>,
if there's more than one in parameter, will be used.
s:<server> The destination system server or printer server.
p:<portvalue> The printer port in <server>. <portvalue> is the
name of the printer port. This is "print" by default.
t:<insttype> Identifies the type of action on the print queue(s).
In Install mode, this implies to install a server or client
print queue. <insttype> can be either "server" (default)
or "client".
In Un-install mode, if <insttype> is "all", this un-installs
all print queues. All other values would un-install <queue>,
if it is specified. Not "all" by default.
g:<guitype> Tells whether to run in Graphical-mode or Text -mode.
<guitype> can be either "yes" (GUI, default) or "no" (Text).
cdepth:<dval> <dval> is for depth value. Specifies the color
depth to use to be able to formulate the background color when
running in GUI mode. <dval> can be "no" or any numeric value.
Non-digit values are treated as "no". "no" tells the program
to use system default colors for displaying the user interface.

This cdepth parameter is relevant ONLY if the Background color
setting is removed or commented out in the Setup resource file.
This is unused if Background color setting is in the resource
file.

The parameters can be specified in any order. In text mode,
if a <queue> or <server> is not specified in the command line
parameter, the program will prompt for it.

Example Usage:
./install q:pshakuba s:hakuba p:direct
where pshakuba is the desired print queue name,
hakuba is the network target printer, and
direct is the Fiery direct port in the hakuba printer.
This opens the setup installation program in server install
type and GUI mode.

./install pshakuba
will open the setup installation program in server install
type and print Fiery port. This opens in GUI mode.
The Network Printer field will be empty waiting for user
to specify a target printer.

./install pshakuba s:hakuba g:no
will run the setup installation program in Text mode.
The pshakuba is the desired print queue name. hakuba is
the network target printer. It will ask if the default print
Fiery port will be used. And if not, it will prompt for a
new value.

./install -u t:all g:no
runs the setup installation program in un-install and
text mode to un-install all print queues.

./install pshakuba s:hakuba p:direct cdepth:8
Runs in GUI mode and initialize the print queue,
destination printer and port fields in the user interface.
If Background color setting is removed from the Setup
resource file, this will use the 8-bit color depth
parameter to choose the background color for the user
interface.

GUI MODE
The following buttons allows user to interactively control
the installation and un-installation process.
* Install button
This button starts the installation process. This button is
disabled until all required fields are filled in.
* Delete button
This button deletes selected print queue in the list of
installed print queues. If there is no print queue available,
this button is disabled.
* Uninstall All button
This button deletes all print queues in the list of installed
print queues. If there is no print queue available, this
button is disabled.
* Exit button
This button terminates the installation program.
* Help button
This shows the instructions on how to use the setup
installation program.

Setup resource file
The Setup resource file contains the settings that define the
setup installation program Motif-based user interface. This
file is needed to be in the same location as the setup
installation program itself. Putting it in a separate location
could cause unexpected errors when running the installation
program.

The Background color is set through this resource file. If the
Background setting is removed from or not set in the resource
file, the installation program is also capable of detecting
which background color to use in two ways. First, it uses the
utility xdpyinfo to detect the supported color depths in the
system and adjusts the background color accordingly. Second,
the "cdepth:#" parameter may also be specified in the command
line. # is any numeric number used to detect the supported
color depth in the system. Some possible values are 1, 2, 4,
6, 8, 12, 16, 24 and 32.

Introduction Tab
The Introduction tab shows information about the "setup"
installation program.

General Tab
* Print Queue
o This is the name of the print queue to be created and
associated with the Unix filter.
* Install Type
o The print queue can be a server (default) or client print
queue.
* Network Printer/Network Server
o On server install type, Network Printer is the name of
the remote printer device where the print jobs will be
sent to.
o On client install type, Network Server is the name of the
remote UNIX/Linux server where the print jobs will be
sent to.
* Printer Port/Remote Queue
o On server install type, Printer Port is the Fiery printer
port on the remote printer device.
o On client install type, Remote Queue is the server-type
print queue on the UNIX/Linux Network Server.
o This is print, by default.
* Remote Server OS
o Shown on client type installation, this specifies the
type of operating system in the remote Network Server.
This is needed in an HP-UX installation for enabling
the client print queue.
* Install Manpage
o This enables/disables installation of the documentation
man pages.
* Set as default
o This enables/disables making the print queue the
default print queue.
* Install User Interface setup program
o This enables/disables installation of the configuration
program. NOTE: The user may opt not to install the
configuration program on systems without graphics
capability, for instance, if Motif is not supported.

Advanced Tab
* Enable three-digit request number
o This is for HP-UX client type installation only:
This specifies whether to use or not use the lpadmin
option -ob3 when creating the client print queue in
the HP-UX system. We have observed that sometimes,
-ob3 is required to enable printing in a newly
installed print queue. You may want to try the On or
Off case to check which setting enables printing,
If you still can't print, please inform us.
o Please refer to the manpage of lpadmin for the use of
-ob3 option.

* Driver Path
o For HPUX, Solaris, and AIX, a model script or
backend script is installed on the system on the
directory specified by the Driver Path. This location
may be different from the default location for the
driver files, which is /usr/local/tsbprn, or
/etc/lp/interfaces/tsbprn in Solaris. If the system
requires the scripts to be in a different location,
specify the new location in this field.
* Middle script/Client script
o This is for Linux installations only: This is the name
to give the actual script installed on the system.
By default, this is shfilter-ps.tos for server install
type, and is shfilter.clnt for client install type.
o For server installation type, the label is Middle script.
o For client installation type, the label changes to Client
script.
* CORE Manpage Path
o This specifies the system directory where the CORE filter
man page will be installed.
* UI Manpage Path
o This specifies the system directory where the UI man page
will be installed.
* UI Link Path
o The setup program also installs a symbolic link to the
configuration program in the location specified in
the UI Link Path field. This is /opt by default.
* Temporary files path
o The setup installation program creates temporary files
during installation. If /tmp is unavailable in the system,
this field specifies an alternative location where temporary
files can be created. This is /tmp by default. If you like
the installation program to install the symbolic link in a
different path, say /bin or /usr/bin, you can specify this
new value in the Temporary files path field.
* Pass Thru (reserved)
o This is only for AIX systems without support for the
"rembak" system utility:
* If the bullet is selected, the user can type in a name on the
text field. It will be used as the pass thru name.
* If the bullet is not selected, the setup installation
program will generate (detect) a pass thru name.
NOTE:
* The pass-thru queues are required for sending filtered
jobs from the print queue to the Fiery ports (print,
direct, or hold).
* This is only included as a fallback solution in AIX
systems, which currently does not provide easy access
to Fiery ports. If the current solution of using the
rembak utility fails, pass-thru queues will be created.

Printer List
* Print Queue column
o This enumerates the print queues installed in the system
and that are associated to the Hakuba UNIX print driver.
* Destination column
o This shows to which network server with Fiery printer
port the print queue will send jobs to.
* UI Link column
o This shows the path where the symbolic link to the
configuration program associated to the print queue
can be found.

Printer Status
This displays the status of the currently selected print queue
in the Printer list.

Status Dialog
The Status dialog shows messages describing the progress of
the installation process.

The Done button closes the dialog after a successful
installation or after an error occurs during installation.
It is disabled during the install process.

If a fatal error occurs, the setup installation program
terminates.

Help Dialog
The help button shows the help dialog, which describes
the setup installation program. The text displayed in
this dialog is taken from the Setup.txt that is shipped
with the driver.

TEXT MODE
If the program fails to detect support for X-Windows in the
Unix/Linux system, or if g:no is specified in the command
line parameters, the program will run in Text mode.

Installation mode
Syntax: ./install [[q:]<queue>] [s:<server>] [p:<portvalue>]
[t:<insttype>] g:no

The g:no parameter launches the installation program in
Text mode.

If <queue> and <server> is not specified, the installation
program will prompt for them. If <portvalue> is not specified,
the program will show the default, which is "print", and will
ask if a different value will be used. If <insttype> is not
specified, the default installed print queue type is "server".

The program will also prompt for other settings such as
manpage path, middle script name, temporary files location,
or UI Link path. Follow screen prompts to specify non-default
settings.

Whenever a yes/no type question is asked, the upper-case
letter identifies the default response. For example, y/N,
N is the default. You can just press the Return (or Enter)
key to use the default setting.

After all information is specified, the program begins the
install process. Status and error messages are shown to guide
user through the install process.

Uninstallation mode
Usage: ./install -u [q:<queue>] [t:<insttype>] g:no

The g:no parameter launches the program in Text mode.

If only -u is specified it will list down all installed print
queues related to the driver, and let you choose which print
queue to un-install.

If <queue> is specified, it will un-install the <queue> if
it is installed in the system. If not, it will list down all
installed print queues related to this driver.

If t:all is specified, it will un-install all installed and
related print queues, even if <queue> is specified.

If <queue> is not specified in the parameters, the program
will list down installed print queues and allows for choosing
which queue to un-install.

POST INSTALLATION PROCEDURES
The setup installation program assumes lpsched is running
when the program is invoked. It will disable the lp scheduler
during the installation process. Restart the scheduler
manually after installation, if necessary.

In GUI installation mode, a successfully set up print queue
is added and selected in the setup Printer List field. In
text installation mode, you can use lpstat -v (-W for AIX
systems) to verify if the print queue has been successfully
installed in the system. lpstat lists down the print queues
available in the system.

Platform Specific Checks
Linux: Shell
For Linux systems, it is assumed that the Korn shell
exists in /bin. If Korn (ksh) does not exist in /bin,
the /usr/local/tsbprn/shfilter-ps.tos file may be
modified to reflect the supported shell in the system.
If, for example, Borne Again (bash) shell is available,
edit the first line in shfilter-ps.tos file, replacing
#!/bin/ksh with #!/bin/bash.

SunOS: windex
For SunOS, installing the manpages may require an extra
step: updating of the windex file. This file is an index
of all manpages in a given main directory for manpages.
Only those manpages with entries in the windex file will
be available and shown when the man command is used. If
a manpage has no entry in the windex file, the said
manpage may not be displayed using the man command.
If windex exists in the main manpage directory, an entry
for the manpage must be added into it. If it does not
exist in the main manpage directory, all manpages within
the subdirectories will be available to the man command.

If the windex file exists, the setup installation program
updates it automatically each time the manpages are
installed. The installation program makes a backup copy
of the windex by renaming the file as windex.orig, done
before updating the windex file. It is recommended that
you save a copy of the windex file somewhere else so
that it will not be lost as the setup installation program
may update the windex file several times depending on how
many print queues and manpages are being installed.

The setup installation program does not create a windex
file if it is originally not found in the main manpage
directory.

pmdzlineur · Le 06/07/2007, à 01:07

bon, ça aurait été bien de mettre tout ça entre code

comme ça

print queue semble être la liste d' impression
si on te demande un nom met print queue tu verras .
Sinon il n 'y a pas de répertoire /usr/lib/X11/app-defaults
donc tu peux essayer

cd /usr/lib/X11/

sudo mkdir app-defaults

sudo chmod 775 app-defaults

et réessayer

sinon pour le setup je ne sais pas s'il ne faut pas faire

sudo ./setup

pour être en root

Dernière modification par pmdzlineur (Le 06/07/2007, à 01:08)

eturnal · Le 06/07/2007, à 16:41

j'ai crée le repertoire app-defaults
avec les droits indiqués
quand je relance le setup je suis toujours dans la meme problematique
a savoir qu'il faut que je determine une print queue
l'aure souci c'est que je ne peut pas interagire avec mon clavier sur la fenetre du setup
en fait je crois qu'il faut determiner cette fameuse "print queue" avant mais comment?
donc je cherche le soucis pour moi etant vraiment le language...
enfin je ferais part de mes futures experiences

eturnal · Le 07/07/2007, à 17:50

bon ça ne marche toujours pas mais j'ai avancé .

quand je lance l'intall il me renvoie cette erreur:

Segmentation fault (core dumped)

cela dit

le programme d'intall a besoin de deux arguments mini c'est:

le nom de la print queue j'ai mis : psestudio45

et le nom du serveur la c'est plus problematique car c'est un poste unique
j'ai donc mis : localhosts
c'est peut etre la que ça coince , mais je ne vois pas quoi mettre d'autre

pmdzlineur · Le 08/07/2007, à 20:42

1) tu cliques sur Code et tu écris ENTRE les balise ;-)
2) c' est

localhost

sans s à la fin
sinon tu peux peut-être mettre

127.0.0.1

c' est l' IP de localhost
ou

xhost host

pas facile ce readme
bon courage
a+

Dernière modification par pmdzlineur (Le 08/07/2007, à 20:46)

pmdzlineur · Le 09/07/2007, à 16:22

on trouve une explication à to erreur là
http://www.ai.univ-paris8.fr/~jalb/langimp/erreurs.html

eturnal · Le 11/07/2007, à 18:03

salut

d'abord merci pour tes conseils d'utilisation pour le forum ;-)

il s'agit bien d'une erreur de compilation ; tres bien la page d'explication et en français , que du bonheure .
seulement je n'ai pas vu de "fichier.c" de plus gdb ne reconnais pas le fichier core ...
et je ne suis vraiment pas de taille à debuger un programme et encore moins un pilote .
du cote du fabricant je n'ai rien vu non plus qui puisse faire avancer le truc....
donc pour utiliser la machine en inprimante il va falloir passer par windows, et là j'enrage a mort (de plus il y a une foule de pilotes ).le seul soucis c'est que certains des softs que j'utilises n'existent pas, ou sont payant ...

sinon un grand merci a toi , si j'ai d'autres info , je ferais suivre , pour le moment je lache l'affaire.

A++

pmdzlineur · Le 11/07/2007, à 19:30

avant de lacher l' affaire je t' ai trouvé ça dans cups
http://www.cups.org/ppd.php?L+I360+T+Q

va voir, ton driver est repertorié dans cups

sinon, dans ton navigateur essaie de mettre
http://localhost:631/
tu tomberas sur le cups portable, on ne sait jamais

sinon, essaie de mettre ton .ppd obtenu plus haut dans /etc/cups qq chose (je chercherai) selon ce qui est dit là
http://www.lea-linux.org/cached/index/Admin-admin_imp-cups.html

Dernière modification par pmdzlineur (Le 11/07/2007, à 19:43)

eturnal · Le 28/08/2007, à 16:48

merci bien de tes conseils .
j'ai recuperé le fichier ppd
je peut donc lancer des impression seulement ça imprime n'importe quoi , et sans arrets. je dois arreter l'impression manuellement ? n'y aurait-il pas quelques bibliotéque a rajouter?

pmdzlineur · Le 28/08/2007, à 17:18

déjà tu peux aller voir dans administration
fais dans ton navigateur :
http://localhost:631/
puis va dans administration pour réglages

sinon, regarde ton /etc/cups/cupsd.conf
le mien (une hp)

#
#
#   Sample configuration file for the Common UNIX Printing System (CUPS)
#   scheduler.  See "man cupsd.conf" for a complete description of this
#   file.
#

# Log general information in error_log - change "info" to "debug" for
# troubleshooting...
LogLevel warning

# Administrator user group...
SystemGroup lpadmin

# Only listen for connections from the local machine.
Listen localhost:631
Listen /var/run/cups/cups.sock

# Show shared printers on the local network.
Browsing Off
BrowseOrder allow,deny
BrowseAllow @LOCAL
BrowseAddress @LOCAL

# Default authentication type, when authentication is required...
DefaultAuthType Basic

# Restrict access to the server...
<Location />
  Order allow,deny
  Allow localhost
  Allow @LOCAL
</Location>

# Restrict access to the admin pages...
<Location /admin>
  Order allow,deny
  Allow localhost
</Location>

# Restrict access to configuration files...
<Location /admin/conf>
  AuthType Basic
  Require user @SYSTEM
  Order allow,deny
  Allow localhost
</Location>

# Set the default printer/job policies...
<Policy default>
  # Job-related operations must be done by the owner or an adminstrator...
  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  # All administration operations require an adminstrator to authenticate...
  <Limit Pause-Printer Resume-Printer Set-Printer-Attributes Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Add-Printer CUPS-Delete-Printer CUPS-Add-Class CUPS-Delete-Class CUPS-Accept-Jobs CUPS-Reject-Jobs CUPS-Set-Default>
    AuthType Basic
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  <Limit All>
    Order deny,allow
  </Limit>
</Policy>

#
#

#
# Printcap: the name of the printcap file.  Default is /etc/printcap.
# Leave blank to disable printcap file generation.
#

Printcap /var/run/cups/printcap

#
# PrintcapFormat: the format of the printcap file, currently either
# BSD or Solaris.  The default is "BSD".
#

#PrintcapFormat BSD
#PrintcapFormat Solaris

#
# PrintcapGUI: the name of the GUI options panel program to associate
# with print queues under IRIX.  The default is "/usr/bin/glpoptions"
# from ESP Print Pro.
#
# This option is only used under IRIX; the options panel program
# must accept the "-d printer" and "-o options" options and write
# the selected printer options back to stdout on completion.
#

#PrintcapGUI /usr/bin/glpoptions

Dernière modification par pmdzlineur (Le 28/08/2007, à 17:33)

eturnal · Le 10/01/2008, à 18:27

bon voila , j'ai enfin resolu le probleme:
cet appareil reconnais deux protocoles le postscrip (ps) et le pcl .
seulement l'extention ps n'est pas installée sur l'imprimante.
le fichier ppd ,plus haut cité, est fait pour le protocole ps .
j'ai donc utilisé un fichier ppd d'un autre fabricant prévus pour le pcl :
HP laserjet serie PCL 6 CUPS
cela fonctione tres bien , j'ai toutes les obtions disponible sur le copieur.
ce fut long mais cela m'a permis de mieux comprendre le systeme d'impression sur linux.
un grand merci à pmdzlineur.

pmdzlineur · Le 10/01/2008, à 23:35

de rien et bravo
c'est vrai que quand on s'en sort on est très content

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 04/07/2007, à 17:38

[resolu] instalation d'une imprimante photocopieur toshiba

#2 Le 04/07/2007, à 20:22

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#3 Le 05/07/2007, à 15:33

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#4 Le 06/07/2007, à 01:07

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#5 Le 06/07/2007, à 16:41

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#6 Le 07/07/2007, à 17:50

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#7 Le 08/07/2007, à 20:42

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#8 Le 09/07/2007, à 16:22

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#9 Le 11/07/2007, à 18:03

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#10 Le 11/07/2007, à 19:30

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#11 Le 28/08/2007, à 16:48

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#12 Le 28/08/2007, à 17:18

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#13 Le 10/01/2008, à 18:27

Re : [resolu] instalation d'une imprimante photocopieur toshiba

#14 Le 10/01/2008, à 23:35

Re : [resolu] instalation d'une imprimante photocopieur toshiba

Pied de page des forums