I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers.
On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers.
Both sound like good ideas to me.
On Mon, Apr 29, 2013 at 2:00 PM, Matthias Clasen mclasen@redhat.com wrote:
On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers.
Both sound like good ideas to me.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Patch for control-center.spec attached.
On Mon, Apr 29, 2013 at 2:00 PM, Matthias Clasen mclasen@redhat.com wrote:
On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers.
Both sound like good ideas to me.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Regarding HP printer drivers, it seems that they are intentionally excluded from our live install. https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-minim...
I can't find the commit message that explains why those drivers are removed. Does anyone on this list has any idea what the reason was and if it's still relevant?
On Mon, 2013-04-29 at 14:19 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:00 PM, Matthias Clasen mclasen@redhat.com wrote: On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote: > I recently discovered that if I have a printer attached to a Windows > machine (and shared via samba), it'll unusable on default install, > because samba-client isn't installed by default. > > > control-center's printers panel managed to discover the printer, but > after the driver prompt dialog it gave a cryptic error message and did > not install the printer. > > > After installing samba-client, adding a samba network printer worked > as expected. Therefor I suggest we add samba-client to our default > installation, it's only 1.2MB. > > > Ideally I think it should be added as a Requires in control-center's > spec file, but we could add it to comps instead. If you think adding > this to the default install is a bad idea, control-center should > install it with packagekit whenever users tries to add a Samba > printer. > > > On a related (printing) note, I think it would also make sense to have > hpijs as a default as well, to support more printers.
Both sound like good ideas to me. -- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Regarding HP printer drivers, it seems that they are intentionally excluded from our live install. https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-minim...
I can't find the commit message that explains why those drivers are removed. Does anyone on this list has any idea what the reason was and if it's still relevant?
Probably because they're huge.
On Mon, 2013-04-29 at 13:31 +0200, Bastien Nocera wrote:
On Mon, 2013-04-29 at 14:19 +0300, Elad Alfassa wrote:
Regarding HP printer drivers, it seems that they are intentionally excluded from our live install. https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-minim...
I can't find the commit message that explains why those drivers are removed. Does anyone on this list has any idea what the reason was and if it's still relevant?
Probably because they're huge.
At some point in the past, installing hp printing support packages would clutter the menu with hp logos and items. That could also be the reason.
On Mon, Apr 29, 2013 at 2:35 PM, Matthias Clasen mclasen@redhat.com wrote:
On Mon, 2013-04-29 at 13:31 +0200, Bastien Nocera wrote:
On Mon, 2013-04-29 at 14:19 +0300, Elad Alfassa wrote:
Regarding HP printer drivers, it seems that they are intentionally excluded from our live install.
https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-minim...
I can't find the commit message that explains why those drivers are removed. Does anyone on this list has any idea what the reason was and if it's still relevant?
Probably because they're huge.
At some point in the past, installing hp printing support packages would clutter the menu with hp logos and items. That could also be the reason.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
hpijs (which contains most of the useful drivers) is about 8.5MB. Since we are no longer limited to the archaic size of a CD (our Live Desktop image is around 1GB last time I checked) we can probably add hpijs without worrying about media size
Regarding logos and items in the menu, this does not seem to be the case today: those ugly things now reside in hplip-gui.
On Mon, Apr 29, 2013 at 1:35 PM, Matthias Clasen mclasen@redhat.com wrote:
On Mon, 2013-04-29 at 13:31 +0200, Bastien Nocera wrote:
On Mon, 2013-04-29 at 14:19 +0300, Elad Alfassa wrote:
Regarding HP printer drivers, it seems that they are intentionally excluded from our live install. https://git.fedorahosted.org/cgit/spin-kickstarts.git/tree/fedora-live-minim...
I can't find the commit message that explains why those drivers are removed. Does anyone on this list has any idea what the reason was and if it's still relevant?
Probably because they're huge.
At some point in the past, installing hp printing support packages would clutter the menu with hp logos and items. That could also be the reason.
That's lame. "Clutter menus" vs. "Hardware does not work" ... I'd argue the first is the lesser evil ;)
On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Why does it need samba-client? It's a package containing command-line utilities none of which seem to be used by gnome-control-center.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead.
<snip>
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
On Sat, 2013-04-27 at 15:26 +0300, Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Why does it need samba-client? It's a package containing command-line utilities none of which seem to be used by gnome-control-center.
I have no idea, all I know is that I got an error trying to add a samba printer without this package installed. Same issue happens with system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT POSSIBLE" or something similar, so it must be some lousy cups problem)
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead.
<snip>
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip>
Why does it need samba-client? It's a package containing command-line utilities none of which seem to be used by gnome-control-center.
I have no idea, all I know is that I got an error trying to add a samba printer without this package installed. Same issue happens with system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT POSSIBLE" or something similar, so it must be some lousy cups problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
On Mon, Apr 29, 2013 at 2:48 PM, Bastien Nocera bnocera@redhat.com wrote:
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip> > Why does it need samba-client? It's a package containing > command-line > utilities none of which seem to be used by > gnome-control-center. > I have no idea, all I know is that I got an error trying to add a > samba printer without this package installed. Same issue happens with > system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT > POSSIBLE" or something similar, so it must be some lousy cups > problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Shouldn't printers work even with system-config-printer isn't present on the system tho? There are some people who would really like not to have system-config-printer by default at all.
On Mon, 2013-04-29 at 14:51 +0300, Elad Alfassa wrote: <snip>
Shouldn't printers work even with system-config-printer isn't present on the system tho?
There are some people who would really like not to have system-config-printer by default at all.
system-config-printer exposes a D-Bus interface for some things that the printers panel makes use of.
On Mon, Apr 29, 2013 at 12:51 PM, Elad Alfassa elad@fedoraproject.org wrote:
On Mon, Apr 29, 2013 at 2:48 PM, Bastien Nocera bnocera@redhat.com wrote:
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip> > Why does it need samba-client? It's a package containing > command-line > utilities none of which seem to be used by > gnome-control-center. > I have no idea, all I know is that I got an error trying to add a > samba printer without this package installed. Same issue happens with > system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT > POSSIBLE" or something similar, so it must be some lousy cups > problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Shouldn't printers work even with system-config-printer isn't present on the system tho? There are some people who would really like not to have system-config-printer by default at all.
There's also a lot of people that don't want printing install by default at all but want control-center. Printing and all the driver deps are huge and there's a lot of people that use gnome without ever having a printer configured.
Peter
On Mon, Apr 29, 2013 at 2:03 PM, Bastien Nocera bnocera@redhat.com wrote:
On Mon, 2013-04-29 at 13:55 +0100, Peter Robinson wrote:
There's also a lot of people that don't want printing install by default at all but want control-center.
We don't support that, sorry.
It's worked just fine since around F-14 without any issue. The only hard dependency has been cups-libs because that's what everything links against ans cups-pk-helper which is suppose to automatically pull in appropriate drivers when a print is plugged in/detected. That's why the vast majority of the printer drivers are excluded in the live image because PackageKit is suppose to pull them in if needed and they take up a lot of space.
Peter
On Mon, Apr 29, 2013 at 2:55 PM, Peter Robinson pbrobinson@gmail.com wrote:
On Mon, Apr 29, 2013 at 12:51 PM, Elad Alfassa elad@fedoraproject.org wrote:
On Mon, Apr 29, 2013 at 2:48 PM, Bastien Nocera bnocera@redhat.com wrote:
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip> > Why does it need samba-client? It's a package containing > command-line > utilities none of which seem to be used by > gnome-control-center. > I have no idea, all I know is that I got an error trying to add a > samba printer without this package installed. Same issue happens with > system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT > POSSIBLE" or something similar, so it must be some lousy cups > problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Shouldn't printers work even with system-config-printer isn't present on the system tho? There are some people who would really like not to have system-config-printer by default at all.
There's also a lot of people that don't want printing install by default at all but want control-center. Printing and all the driver deps are huge and there's a lot of people that use gnome without ever having a printer configured.
Huge? Maybe in if you are using a system from the early 90s ... otherwise the size is hardly an issue.
On Mon, 2013-05-13 at 21:06 +0200, drago01 wrote:
Huge? Maybe in if you are using a system from the early 90s ... otherwise the size is hardly an issue.
Peter has several cases where size definitely is an issue on-tap. I'm sure he can trot them out for you again, but it's in the devel@ archives several times. We like to think we can assume everyone has 100GB lying around all the time, but it's still not really the case.
On Mon, May 13, 2013 at 8:27 PM, Adam Williamson awilliam@redhat.com wrote:
On Mon, 2013-05-13 at 21:06 +0200, drago01 wrote:
Huge? Maybe in if you are using a system from the early 90s ... otherwise the size is hardly an issue.
Peter has several cases where size definitely is an issue on-tap. I'm sure he can trot them out for you again, but it's in the devel@ archives several times. We like to think we can assume everyone has 100GB lying around all the time, but it's still not really the case.
Sure can :-)
* Cloud installs like amazon where you pay per mb or gb and you literally want JeOS (Just Enough OS) * OLPC XO-1 has 1Gb of nand, XO-1.5/1.75/4 have configurations of 2/4/8Gb depending on the model or options * A lot of netbooks only have between 4 and 32Gb of storage and you don't want to use all the install for the OS alone * A lot of ARM devices only have a small storage space eg the new shiny Beagle Bone Back only has 2Gb of eMMC storage by default. * Various chromeOS devices only come with small amounts of local storage. Hell even the new $1300 Pixel only comes with 32Gb of storage
Ultimately there's a lot of people that don't even own printers with modern devices that still only come with small amounts of storage. PackageKit is suppose to have the ability to install drivers on demand so we don't need to install all the drivers just in case someone might want to use one of the drivers.
Peter
On Mon, Apr 29, 2013 at 2:48 PM, Bastien Nocera bnocera@redhat.com wrote:
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip> > Why does it need samba-client? It's a package containing > command-line > utilities none of which seem to be used by > gnome-control-center. > I have no idea, all I know is that I got an error trying to add a > samba printer without this package installed. Same issue happens with > system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT > POSSIBLE" or something similar, so it must be some lousy cups > problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Eew, seems to be in cups itself. do_samba_command() is a cups function that is used almost *everywhere* inside that bloody thing that simply forks smbclient or similar command line utilities to get what it wants. Horrible.
I'll file a bug.
On Mon, 2013-04-29 at 13:48 +0200, Bastien Nocera wrote:
On Mon, 2013-04-29 at 14:36 +0300, Elad Alfassa wrote:
On Mon, Apr 29, 2013 at 2:34 PM, Bastien Nocera bnocera@redhat.com wrote:
<snip> > Why does it need samba-client? It's a package containing > command-line > utilities none of which seem to be used by > gnome-control-center. > I have no idea, all I know is that I got an error trying to add a > samba printer without this package installed. Same issue happens with > system-config-printer (just a bit more verbose, saying "CUPS ERROR NOT > POSSIBLE" or something similar, so it must be some lousy cups > problem)
Then it seems to me that cups or system-config-printer are missing the dep, not control-center.
$ FILES=`rpm -ql system-config-printer | grep 'py$'` ; for i in `rpm -ql samba-client | grep /bin/` ; do BASENAME=`basename $i` ; grep -l $BASENAME $FILES && echo $i ; done /usr/share/system-config-printer/troubleshoot/CheckPrinterSanity.py /usr/bin/nmblookup
Looks like system-config-printer might be responsible for the missing dep. Would be better if that wasn't needed though.
Note that I already addressed this for F19 to some extent:
https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=2c04fe5d624...
samba-client is in fact in a default install, but we were explicitly dropping it from the live images to "save some space", presumably because we figured it wasn't really needed.
Dedoimedo noticed this issue in his review of F18, so I looked into it, and got samba-client taken out of live-minimization.ks , which means it won't be removed from the F19 live images.
I don't really mind whether we add a hard dep or not (it might cause some people to complain about bloat and yadda yadda), I just thought it was worth pointing out that this is probably already 'fixed' for most practical cases.
Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
...
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
Adding to comps (gnome-desktop or whatever) to get installed by default should be sufficient (while allowing for those who don't want it)
See also this commit (since f18) to spin-kickstarts
commit 2c04fe5d624c3b9c1d3658b8fe0c8b4a71c910bb Author: Adam Williamson awilliam@redhat.com Date: Sat Jan 26 08:58:40 2013 -0800
drop samba-client from minimization (it's needed for SMB print sharing)
-- rex
On Mon, Apr 29, 2013 at 3:00 PM, Rex Dieter rdieter@math.unl.edu wrote:
Elad Alfassa wrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install,
because
samba-client isn't installed by default.
...
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
Adding to comps (gnome-desktop or whatever) to get installed by default should be sufficient (while allowing for those who don't want it)
See also this commit (since f18) to spin-kickstarts
commit 2c04fe5d624c3b9c1d3658b8fe0c8b4a71c910bb Author: Adam Williamson awilliam@redhat.com Date: Sat Jan 26 08:58:40 2013 -0800
drop samba-client from minimization (it's needed for SMB print sharing)
-- rex
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
I installed fedora 19 from liveCD and samba-client wasn't there. Anyway, bug reported against the cups package... The only issue still standing in this thread is if we should add hpijs to the live media.
On Mon, 2013-04-29 at 15:02 +0300, Elad Alfassa wrote:
I installed fedora 19 from liveCD and samba-client wasn't there.
Well, I just booted Fedora-Live-Desktop-x86_64-19-Beta-TC4-1.iso and did 'rpm -q samba-client', and it is there.
On Mon, May 13, 2013 at 10:00 PM, Adam Williamson awilliam@redhat.comwrote:
On Mon, 2013-04-29 at 15:02 +0300, Elad Alfassa wrote:
I installed fedora 19 from liveCD and samba-client wasn't there.
Well, I just booted Fedora-Live-Desktop-x86_64-19-Beta-TC4-1.iso and did 'rpm -q samba-client', and it is there.
In that case the issue is fixed, awesome :)
-- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net
-- desktop mailing list desktop@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/desktop
Bugs reported: https://bugzilla.redhat.com/show_bug.cgi?id=957727 https://bugzilla.redhat.com/show_bug.cgi?id=957733
Tim said he will look at them when he has the time, and he isn't so keen on making cups depend on samba-client. On the other hand, not having samba-client installed by default and not providing the user with a good error message/automatic installation of missing components is rather bad.
On Sat, Apr 27, 2013 at 3:26 PM, Elad Alfassa elad@fedoraproject.orgwrote:
I recently discovered that if I have a printer attached to a Windows machine (and shared via samba), it'll unusable on default install, because samba-client isn't installed by default.
control-center's printers panel managed to discover the printer, but after the driver prompt dialog it gave a cryptic error message and did not install the printer.
After installing samba-client, adding a samba network printer worked as expected. Therefor I suggest we add samba-client to our default installation, it's only 1.2MB.
Ideally I think it should be added as a Requires in control-center's spec file, but we could add it to comps instead. If you think adding this to the default install is a bad idea, control-center should install it with packagekit whenever users tries to add a Samba printer.
On a related (printing) note, I think it would also make sense to have hpijs as a default as well, to support more printers. -- -Elad Alfassa.
desktop@lists.fedoraproject.org