|
Bugzilla – Full Text Bug Listing |
| Summary: | Cannot add a Network (SMB) Printer - KDE4 CD | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Gary Cobb <gecobb> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Johannes Meixner <jsmeix> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Gary Cobb
2008-05-18 11:08:45 UTC
Did this work in beta2? I'm sorry, I don't know. I could never get Beta2 to install well for me. I am a wireless connection user, and I ran into some problems with networking that prevented me from loading the Samba client code. Can you ttache /etc/cups/printers.conf, /var/log/cups/error.log and /etc/cups/ppd/<<queue>>.ppd of your beta3 system? (after you did samba printer installation in cups) Please use attachment facility of bugzilla for this (see below). I never made it far enough to actually add the printer to the cups configuration. I looked for the files you mention, printers.conf and hp5550.ppd don't exist and the error log doesn't have anything useful. In YaST2 there were no available printers, so I used the button to "Add" one. When I got done with the "Add" process and clicked "Finish" (after configuring the SMB printer) there were still no printers in the list of available printers to select and add to cups (I still had a blank list). Sorry, I'm probably not explaining this very well. I don't know how to configure the printer manually, just through the UI, but if you want me to run some commands and send back the output I'll be happy to. As the printer never appears in the cups configuration, I assume it's a YaST2 issue -> reassign and changing bugzilla component accordingly. It's already fixed *** This bug has been marked as a duplicate of bug 386934 *** |