Bug 119738
| Summary: | Setup for SMB printer doesn't accept SMB server name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brion Vibber <brion> | ||||
| Component: | system-config-printer | Assignee: | Tim Waugh <twaugh> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | triage | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | bzcl34nup | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-05-06 23:58:27 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Brion Vibber
2004-04-01 21:58:06 UTC
Does it work in non-enforcing mode? If so, could you see what messages are produced in the output from 'dmesg'? I've still got the problem on a fresh install of test3, which allegedly has SElinux off by default. Nothing shows up in /var/log/messages (or in dmesg) during this part of printer configuration. Earlier there was a bunch of stuff of this sort: security_context_to_sid: called before initial load_policy on unknown context system_u: object_r:default_t followed by a bunch of other such lines for all kinds of services. This doesn't look related. As with test2, using the (non-DNS) SMB name causes the neverending unexplained series of authenticate dialogs. Putting in the IP address lets me successfully configure the printer (and I can even print now! yay) On further investigation, the problem with not accepting the SMB name is actually caused by the firewall. The default firewall settings break SMB browsing (bug 113918) and apparently even SMB name resolution. With the firewall off, I can put in the SMB name instead of the IP address; the machine also shows up in the available share list for handier selection. Now, the firewall stuff is a separate bug, but the infinite series of 'Authentication' dialogs is still a problem in system-config-printer. If it could inform the user that it was unable to contact the printer (and perhaps suggest alternatives), that would be a big improvement. Created attachment 99869 [details]
Stick an error message with suggestions between the endless series of dialogs
If can't connect to printer, spits out "Check the machine name, share name,
username, and password. If the firewall is enabled, you may need to use an IP
address for the machine name." before prompting again.
[This is a mass update sent to many bugs that missed earlier such messages due to having their version set to a test version.] This bug was originally filed against a version of Fedora Core which is no longer supported, even for security updates. Many changes have occured since then. Please retest this bug against a still supported version. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. If it still occurs on FC5 or FC6, please assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug will be closed after a few weeks if no information is given indicating that the bug is still present in a supported release. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp |