Bug 141951 - printer list is empty un yast configuration
Summary: printer list is empty un yast configuration
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Alpha 4
Hardware: PC SUSE Other
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-07 20:03 UTC by Rihards Olups
Modified: 2006-01-09 17:23 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Rihards Olups 2006-01-07 20:03:55 UTC 
when a locally connected printer is added in yast printer configuration screen, it does not show up in printer listing.
the printer can be seen in applications and cups web management interface and it works.

this seems very similar to bug 113570, but that was filed against 10.0beta3 (and the issue it was linked as dupe against was marked as fixed for 10.0rc1)

this actually is a system upgraded to factory-2006.01.06.
Comment 1 Michael Gross 2006-01-09 15:30:15 UTC 
Please provide the output of `hwinfo --printer' as well as your YaST2 logs (/var/log/YaST2/).
Comment 2 Rihards Olups 2006-01-09 17:17:41 UTC 
turns out, 'factory' upgrade dbus package was not compatible with hwinfo :)
hwinfo required libdbus-1.so.1, while package did not create a symlink to libdbus-1.so.2.

after manually creating the symlink hwinfo and yast both successfully show the printer.

if required, i can still provide hwinfo output and yast logs, but i don't think that would help.

sorry for this problem, i have suse installed only for a week - in future i will try always running hwinfo before reporting a problem :)
Comment 3 Michael Gross 2006-01-09 17:22:19 UTC 
OK then I consider this as fixed ;)
Comment 4 Michael Gross 2006-01-09 17:23:33 UTC 
Rihards: Please reopen this if this update you are talking about is an official SUSE-YOU-update, because in that case we should fix this here.