Hello, On May 1 20:46 Volker Kuhlmann wrote (shortened):
3) The "list of installed drivers" (printer pppd files) is built after the printer can be configured during installation in the hardware config step. Does this constellation make sense? ... The system had no printer connected. If yast offers to configure one, it can only be for a network printer on another host.
No. YaST cannot know for sure if there is no local printer connected. A local connected printer may be switched off (in particular Epson USB printers cannot be detected when the device is switched off).
Still, should all the usual printer model descriptions (ppd files) be available here?
Yes. On a standard system it should be possible to set up a printer. In particular when you want to print directly on a network printer (i.e. when there is no CUPS print server in between) or when you want to print via SMB share or via iPrint server, you need to run the printer driver on your local machine. Perhaps I misunderstand it and you mean https://bugzilla.novell.com/show_bug.cgi?id=253257 ?
If yes, the list of available files, which is created later when SuSEconfig runs, should already be available here, thus that part of SuSEconfig needs to be run (damn, that takes ages). If not, it would be useful for installing a printer file from another media.
The YaST printer database is not created via SuSEconfig but via the YaST printer setup tool. Perhaps it only looks wrong? Perhaps the YaST printer setup tool only shows some initial stuff (e.g. its entry in the hardware config screen) and then it creates its printer database so that it only looks as if it creates its printer database too late? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org