| 2008-10-16 15:32:40 |
Charlie Kravetz |
cupsys: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. There has been no communication for over two months, I am setting the report to incomplete until the needed information can be attached.
It would be helpful to attach the cupsys log: This is a file where CUPSYS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start solving problems. To be useful, you must change the logging level:
1.Select "System" -> "Administration" -> "Printing" in the main menu of your desktop. The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left. Then check the check box "Save debugging information for troubleshooting" and click "Apply".
2. In /etc/cups/cupsd.conf, find the line "LogLevel ..."; change it to" LogLevel debug"; save.
3. 'sudo /etc/init.d/cupsys restart'
4. Try to print something.
5. Add /var/log/cups/error_log as an attachment to the bug report.
|
|
| 2008-12-03 17:25:23 |
Charlie Kravetz |
cupsys: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. There has been no communication for over two months, I am setting the report to incomplete until the needed information can be attached.
It would be helpful to attach the cupsys log: This is a file where CUPSYS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start solving problems. To be useful, you must change the logging level:
1.Select "System" -> "Administration" -> "Printing" in the main menu of your desktop. The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left. Then check the check box "Save debugging information for troubleshooting" and click "Apply".
2. In /etc/cups/cupsd.conf, find the line "LogLevel ..."; change it to" LogLevel debug"; save.
3. 'sudo /etc/init.d/cupsys restart'
4. Try to print something.
5. Add /var/log/cups/error_log as an attachment to the bug report.
|
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|
