Bug 462403 - When trying to "verify" an smb printer connection the gui admin window closes
Summary: When trying to "verify" an smb printer connection the gui admin window closes
Keywords:
Status: CLOSED DUPLICATE of bug 458790
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-15 22:16 UTC by Bruno Wolff III
Modified: 2008-09-22 13:47 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-09-22 13:47:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bruno Wolff III 2008-09-15 22:16:13 UTC
Description of problem:
I am trying to set up a remote printer using the gui interface (gnome desktop) for a printer on a windows machine and am trying to using an smb connection to it. When I hit the ""verify" button the admin window closes. I am not sure if the printer information is correct. No printer is set up when i do this. I had been able to use the printer before upgrading from F9 to rawhide (F10). I don't have the old cups configuration info saved.

Version-Release number of selected component (if applicable):
cups-1.3.8-6.fc10.x86_64 though i am not sure this is cups problem as it may be whatever provides the gui for gnome.

How reproducible:
The behavior happens all of the time.

Steps to Reproduce:
1.Try to create a new printer using smb in the gnome system administration interface.
2.
3.
  
Actual results:
Admin window closes

Expected results:
Being able to finish setting up the printer

Additional info:

Comment 1 Tim Waugh 2008-09-22 10:35:41 UTC
What does 'rpm -q libsmbclient' say?

Comment 2 Bruno Wolff III 2008-09-22 13:29:07 UTC
[bruno@cerberus ~]$ rpm -q libsmbclient
libsmbclient-3.2.1-0.19.fc10.x86_64

Comment 3 Tim Waugh 2008-09-22 13:47:26 UTC

*** This bug has been marked as a duplicate of bug 458790 ***


Note You need to log in before you can comment on or make changes to this bug.