http://bugzilla.novell.com/show_bug.cgi?id=529489
User jsmeix@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=529489#c1
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|NEW |NEEDINFO
Info Provider| |pilotgi@gmail.com
--- Comment #1 from Johannes Meixner 2009-08-11 01:43:07 MDT ---
Regarding third party driver software in general
(here in particular the cupswrapper from Brother):
When it is the third party driver software which fails,
there is nothing we can do (in particular when the
third party software contains proprietary stuff,
usually a proprietary library which contains all
what is really interesting for such a driver)
and in this case all you can do is to report
the issue to Brother.
To find out whether or not it is the Brother driver
which fails, provide a CUPS error_log as follows, see
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
"If problems are encountered:"
1.
Set the "LogLevel debug" in /etc/cups/cupsd.conf.
2.
Stop cupsd.
3.
Move /var/log/cups/error_log* to another location (or delete it)
in order to avoid having to search through gigantic log files.
4.
Start cupsd.
5.
Do one single tespage print from YaST.
and wait one minute.
6.
Save the current CUPS error_log state:
cp /var/log/cups/error_log /tmp/error_log.bug529489
7.
Attach /tmp/error_log.bug529489 to this bug report
as MIME type "text/plain".
Regarding your question about the YaST configuration page:
All three entries are listed as "Brother HL5370DW for CUPS"
ony with different locations "[...]" where to find them.
Therefore - as far as I can imagine - there are three PPD files
(printer + driver description files) at different locations
which are for the same "Brother HL5370DW for CUPS" driver, compare
http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
"PPD Files" versus "The Filter (includes the Driver)".
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.