Description of problem: Try to configure scanner part of Samsung scx-4500w all-in-one printer - method detailed below should work but does not until workaround is done. I did have the scanner working fine with a similar method in F10. Version-Release number of selected component (if applicable): sane-backends-1.0.20-4.fc11.i586 How reproducible: Every time Steps to Reproduce: 1. cd /usr/share/hal/fdi/information/20thirdparty/ 2. added lines in Samsung section of 19-libsane.fdi <!-- Samsung SCX-4500W --> <match key="usb.product_id" int="0x342b"> <append key="info.capabilities" type="strlist">scanner</append> </match> 3. added two lines to /etc/sane.d/xerox_mfp.conf: #Samsung SCX-4500W usb 0x04e8 0x342b 4. Start GIMP and ask to scan. Actual results: Does not find device Expected results: Should find device and open dialog to start scanning Additional info: I have found a work around that indicates a possible config error in the package. I found that the dll.conf files in /etc/sane.d/ were interesting. There were two files in my system - which were: -rw-r--r--. 1 root root 916 2009-10-03 12:13 dll.conf -rw-r--r--. 1 root root 664 2009-06-23 09:04 dll.conf.rpmnew I note that dll.conf was dated later than dll.conf.rpmnew - and the dll.conf file did not include xerox_mfp, whereas the earlier dated dll.conf.rpmnew did include this and in my case this is needed for the driver! So I simply did the following: mv dll.conf dll.conf.orig cp dll.conf.rpmnew dll.conf This makes the contents of the .rpmnew version current, and when I fired up GIMP and asked for a scan - it worked just fine.
Presumably when running the updates after the install of f11, the sane-backends package should have made the original dll.conf become dll.conf.rpmsave and then install the newer file as dll.conf. I am guessing that the wrong date on the dll.conf file in the update rpm caused it to become dll.conf.rpmnew instead of the correct action during the update?
Anybody reading this? It has been a week!
dll.conf is marked "noreplace" in the spec file: %config(noreplace) /etc/sane.d/*.conf It means that when upgrading the package, rpm should NOT replace the config file with the new version if the old version was modified locally by the user. So putting the new version into the *.rpmnew file is the expected result here. I don't see a bug here. Reviewing the proposed changes in *.rpmnew files and deciding whether to merge them has always been the administrator's responsibility in rpm systems.
(In reply to comment #2) > Anybody reading this? It has been a week! I haven't been reading any bug reports during my vacation, which was recorded here: https://fedoraproject.org/wiki/Vacation ;-) (In reply to comment #3) > I don't see a bug here. Reviewing the proposed changes in *.rpmnew files and > deciding whether to merge them has always been the administrator's > responsibility in rpm systems. As I've described in the original bug #512516, in the past, some other packages modified dll.conf in RPM scriptlets which caused this to happen. Unfortunately, there's not much I can do which fixes this automatically, so people will have to manually replace the old dll.conf file by themselves.
I was not aware of the file being amended by RPM scriptlets - but I am pretty certain that I did no changes to dll.conf from the point of f11 install through to the point where I had the problem. In the past I have always expected to have an rpmnew file when I have amended a config file myself - and an rpmsave file when I have not done any changes. I don't see how as an admin for a machine I could have known that in this case something else had modified the .conf file! Certainly I don't even know where to look to find which scriptlet would have done this? Sorry to pester you - I was unaware you were away - but thanks for the vacation wiki link.... I hope you had a good vacation...
Out of interest, do you know what other rpms are modifying dll.conf?
I'd be interested in that also!
That would be the libsane-hpaio package (from hplip).