| Summary: | search SAMBA printer hangs | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Francesco Presel <f.presel> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | cfeck |
| Priority: | NOR | ||
| Version: | 4.10.4 | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
system-config-printer-kde is no longer maintained by the KDE community. Please switch to the new "print-manager" (part of the KDE 4.10 release), or ask your distribution for continued support. |
When I want to add a new printer (located on a Windows computer), the "search" function hangs, and does not output any printer. I have, instead, to give the path manually, and only then the printer can be installed. Reproducible: Always Steps to Reproduce: 0: if you don't have it yet, install SAMBA and set up the server, using "user" authentication method (I don't know if that's important) 1. Open systemsettings (possibly from terminal; as normal user)-> printer 2. Click on new printer 3. Select "windows printer via SAMBA" 4. Click on the "search" button top right Actual Results: A window comes out, which says "scanning..."; when the mouse is over that window, it has the run cursor. That window remains like that, i.e. no printer is found, until you click on "close". As soon as that window appears, the terminal prints something like Traceback (most recent call last): File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 3372, in on_btnSMBBrowse_clicked self.browse_smb_hosts() File "/usr/share/kde4/apps/system-config-printer-kde/system-config-printer-kde.py", line 3157, in browse_smb_hosts smbc_auth = pysmb.AuthContext (self.SMBBrowseDialog) NameError: global name 'pysmb' is not defined then, no other output comes out Expected Results: It should either find a printer (at least in my case, since giving the path manually worked), or at least stop after some time, saying "no printer found" This bug could be related to this one (which should have a patch available): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712643