cups smb printing backend no longer works

At least two more other people suffer from this bug, see here:
http://ubuntuforums.org/showthread.php?t=160041

Please confirm + fix! :)

Additional:
/var/log/cups/error_log in Normal mode:
I [14/Apr/2006:10:52:37 +0200] Job 1 queued on "HP-DeskJet-950C" by "bazon".
I [14/Apr/2006:10:52:37 +0200] Started filter /usr/lib/cups/filter/pstops (PID 8454) for job 1.
I [14/Apr/2006:10:52:37 +0200] Started filter /usr/lib/cups/filter/foomatic-rip (PID 8455) for job 1.
I [14/Apr/2006:10:52:37 +0200] Started backend /usr/lib/cups/backend/smb (PID 8456) for job 1.
E [14/Apr/2006:10:52:37 +0200] PID 8456 crashed on signal 11!
I [14/Apr/2006:10:52:37 +0200] Hint: Try setting the LogLevel to "debug" to find out more.
E [14/Apr/2006:10:52:44 +0200] PID 8455 stopped with status 9!
I [14/Apr/2006:10:52:44 +0200] Hint: Try setting the LogLevel to "debug" to find out more.
I [14/Apr/2006:10:52:44 +0200] Saving printers.conf...

/var/log/cups/error_log in debug mode:

D [14/Apr/2006:11:24:50 +0200] cupsdAcceptClient: 6 from localhost (Domain)
D [14/Apr/2006:11:24:50 +0200] cupsdReadClient: 6 POST /printers/HP-DeskJet-950C HTTP/1.1
D [14/Apr/2006:11:24:50 +0200] cupsdAuthorize: No authentication data provided.
D [14/Apr/2006:11:24:50 +0200] print_job: auto-typing file...
D [14/Apr/2006:11:24:50 +0200] print_job: request file type is application/postscript.
D [14/Apr/2006:11:24:50 +0200] check_quotas: requesting-user-name = "bazon"
D [14/Apr/2006:11:24:50 +0200] print_job: requesting-user-name = "bazon"
D [14/Apr/2006:11:24:50 +0200] Adding default job-sheets values "none,none"...
I [14/Apr/2006:11:24:50 +0200] Adding start banner page "none" to job 3.
I [14/Apr/2006:11:24:50 +0200] Adding end banner page "none" to job 3.
I [14/Apr/2006:11:24:50 +0200] Job 3 queued on "HP-DeskJet-950C" by "bazon".
D [14/Apr/2006:11:24:50 +0200] Job 3 hold_until = 0
D [14/Apr/2006:11:24:50 +0200] Discarding unused job-created event...
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob() id = 3, file = 0/1
D [14/Apr/2006:11:24:50 +0200] job-sheets=none,none
D [14/Apr/2006:11:24:50 +0200] banner_page = 0
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: argv = "HP-DeskJet-950C","3","bazon","Testseite","1","","/var/spool/cups/d00003-001"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[0]="CUPS_CACHEDIR=/var/cache/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[1]="CUPS_DATADIR=/usr/share/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[2]="CUPS_DOCROOT=/usr/share/cups/doc-root"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[3]="CUPS_FONTPATH=/usr/share/cups/fonts"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[4]="CUPS_REQUESTROOT=/var/spool/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[5]="CUPS_SERVERBIN=/usr/lib/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[6]="CUPS_SERVERROOT=/etc/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[7]="CUPS_STATEDIR=/var/run/cups"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[8]="PATH=/usr/lib/cups/filter:/bin:/usr/bin"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[9]="SOFTWARE=CUPS/1.2svn"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[10]="TMPDIR=/var/spool/cups/tmp"
D [14/Apr/2006:11:24:50 +0200] cupsdStartJob: envp[11]="TZ=Europe/Berlin"
D [14/Apr/2006:11:24:50 +0200] cupsdSt...

Can confirm that this affects me too. What drivers is everyone using to connect? Could it be related to a specific kind of printer? I'm trying to use it with the HPLIP drivers.

I have experienced this with two different printers and three different drivers. (Laserjet 4L with both "HP" and "HP LIP"; and a Canon printer with the Turbojet printers.) I don't think this is a driver-specific issue.

I tried all accesable drivers, too, so I don't think it's adriver thing, too.

What is common in all 3 crash reports is:

(PID of cups backend) crashed on signal 11!

As this worked before in breezy I hope it should be easy to fix...
(...but I'm not the one who knows how...)

Confirming this bug.
When printing a test page the following appears in the error_log file:
E [14/Apr/2006:21:36:40 +0100] PID 4914 crashed on signal 11!
E [14/Apr/2006:21:36:45 +0100] PID 4913 stopped with status 9!

The bug has appeared since 8th of April.

The bug may be in smbspool: from the terminal --

$ DEVICE_URI="smb://user:topsecret@GROUP/SOMEPC/Canon"
$ export DEVICE_URI
$ echo something | smbspool 99 me test 1 ""
Segmentation fault

This does not occur on another linux system I tried: instead of "Segmentation fault" one should get something like:

     cli_full_connection: failed to connect to SOMEPC<20> (0.0.0.0)

The version of smbspool that I have is from the package smbclient 3.0.22-1ubuntu1 (dapper), which I installed on April 10. In all other respects, samba appears to be working fine.

I can confirm that smbspool is the problem. I unpacked the copy of smbspool from the older package smbclient-3.0.21b-1ubuntu1, and replaced /usr/bin/smbspool. Reverting to the older version of smbspool cures the problem.

So this bug should be labelled as belonging to package smbclient. (But unlike bugzilla, this launchpad doesn't seem to have a way for me to change the package.)

I opened a new Bug #39662 on the package smbclient (because I have no apparent way of indicating otherwise that this bug is in the package smblcient).

+1
A set-up which worked perfectly in Breezy is completely non-functional in Dapper, with no manual changes made to the set-up. Trying to print to a WinXP shared printer across a LAN and samba etc.

Same problem here:
it's ubuntu dapper flight 6 amd64.
My cups log file is full of:

E [19/Apr/2006:16:33:06 +0200] PID 5854 crashed on signal 11!
E [19/Apr/2006:16:33:06 +0200] cupsdAuthorize: Local authentication certificate not found!
E [19/Apr/2006:16:33:06 +0200] cupsdAuthorize: Local authentication certificate not found!

I can confirm this bug. I was using Kubuntu and all of a sudden my printing stopped working after a certain upgrade.

I reinstalled to ubuntu today, completely fresh, same exact problem with any network/smb printing.

Another desktop on a seprate network with a completely fresh install and absolutely separated from this one in every fashion is having the same issue.

I have configured printing via smb many, many times and all at once everything stopped working for me. This occured before the release of flight 6, but flight 5 had fine printing until a particular update.

To add to my previous comment, I am using nothing but postscript drivers. This is obviously not a driver issue, but rather a SMB problem

The following is a copy of a comment i accidentally added to bug #39662.

I've located the error. It's due to the ubuntu-setlocale.patch that was applied in version 3.0.22-1ubuntu1. That patch uses a table which is filled in at initialisation time to look up the uppercase version of all unicode letters. If this table is not yet initialised, it will result in a segfault.

I think the proper way to fix this is to always check if a certain initialisation function has been called before allowing anything at all to happen, but I suppose that decision is up to the samba developers. For now this patch which just adds a call to load_case_tables() in the beginning of smbspool.c, will probably do just fine. This approach is also used by smbclient and smbmount.

The attached file replaces the current ubuntu-setlocale.patch currently present in debian/patches in the samba source package.

Adam could you evaluate the proposed patch ?

I've compiled it with the proposed patch and put it into our repository. You can try it yourself:
http://www.linux2go.dk//ubuntu/pool/main/s/samba/smbclient_3.0.22-1ubuntu1linux2go1_i386.deb

I too can confirm this bug. Even on the beta version of Dapper (fully updated as of 04/23/06) I can not print to my HP PSC 750 on a fully updated Windows XP SP2 machine. Same symptoms -- document is "sent" to printer, a pause of about four or five seconds, and then a print fail icon and a paused printer.

The patch given by Soren Hansen is working for me

I cannot get the patched smbclient to install:

$ sudo dpkg -i smbclient_3.0.22-1ubuntu1linux2go1_i386.deb
(Reading database ... 128287 files and directories currently installed.)
Preparing to replace smbclient 3.0.22-1ubuntu1 (using smbclient_3.0.22-1ubuntu1linux2go1_i386.deb) ...
Unpacking replacement smbclient ...
dpkg: dependency problems prevent configuration of smbclient:
 smbclient depends on samba-common (= 3.0.22-1ubuntu1linux2go1); however:
  Version of samba-common on system is 3.0.22-1ubuntu1.
dpkg: error processing smbclient (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 smbclient

Due to the failed attempt to install the patched smbclient package (see previous post), my system is now broken !
Cannot update anymore, cannot remove or reinstall the smbclient package, it's just broken.
Removing or fixing the smbclient package will also remove ubuntu-desktop and kubuntu-desktop and that's not what I want really !

Heh... Sorry about that. :-)
If you go to: http://www.linux2go.dk//ubuntu/pool/main/s/samba/

and fetch the samba, samba-common and smbfs packages and install them too, everything should be fine. When a new version shows up in ubuntu it will automatically replace these packages.

either that, or you can add our repository to your sources.list:

deb http://www.linux2go.dk/ubuntu dapper main

no problem, I'll add the repository and try again.

Note that this bug hasn't slipped under the radar or anything; I'm just investigating other similar bugs caused by this same patch, so I can fix them all at once, rather than one at a time.

Broken system is fixed again by manually downloading and installing the samba, samba-common en smbfs packages.
Adding deb http://www.linux2go.dk/ubuntu dapper main to the repositories and trying to install the 3 packages through apt didn't work (complaining about dependencies with samba-common)

Anyway, everything seems to be working again. Now let's hope the patched version fixes the printing problems :-)

Thanks Soren for the prompt assistance !

I can confirm this no printing/pause printing to my network printer as well on my Epson CX3700.

I tried the patch by Soren, however got the following error in package installer:
Error: Dependency is not satisfiable: samba-common

Hey John, see my posts above:
You should also download samba, samba-common and smbfs from http://www.linux2go.dk//ubuntu/pool/main/s/samba/

After installing the patch, the "crashed on signal 11" errors seem to have disappeared, however printing still isn't working for me:
(I removed the existing printer, re-added it and then tried to print some document)

E [25/Apr/2006:09:08:26 +0200] cupsdAuthorize: Local authentication certificate not found!
E [25/Apr/2006:09:08:26 +0200] cupsdAuthorize: Local authentication certificate not found!
E [25/Apr/2006:09:08:26 +0200] cupsdAuthorize: Local authentication certificate not found!
E [25/Apr/2006:09:08:30 +0200] cupsdAuthorize: Local authentication certificate not found!
E [25/Apr/2006:09:08:30 +0200] CUPS-Delete-Printer: Unauthorized
E [25/Apr/2006:09:10:12 +0200] CUPS-Add-Modify-Printer: Unauthorized
E [25/Apr/2006:09:11:44 +0200] [Job 6] Session setup failed: NT_STATUS_LOGON_FAILURE
E [25/Apr/2006:09:11:44 +0200] [Job 6] No ticket cache found for userid=1000
E [25/Apr/2006:09:11:44 +0200] [Job 6] Can not get the ticket cache for gds
E [25/Apr/2006:09:11:44 +0200] [Job 6] perl: warning: Setting locale failed.
E [25/Apr/2006:09:11:44 +0200] [Job 6] perl: warning: Please check that your locale settings:
E [25/Apr/2006:09:11:44 +0200] [Job 6] LANGUAGE = (unset),
E [25/Apr/2006:09:11:44 +0200] [Job 6] LC_ALL = (unset),
E [25/Apr/2006:09:11:44 +0200] [Job 6] LANG = "en_US"
E [25/Apr/2006:09:11:44 +0200] [Job 6] are supported and installed on your system.
E [25/Apr/2006:09:11:44 +0200] [Job 6] perl: warning: Falling back to the standard locale ("C").
E [25/Apr/2006:09:11:44 +0200] [Job 6] Session setup failed: NT_STATUS_LOGON_FAILURE
E [25/Apr/2006:09:11:45 +0200] [Job 6] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [25/Apr/2006:09:11:45 +0200] [Job 6] Unable to connect to CIFS host, will retry in 60 seconds...
E [25/Apr/2006:09:11:45 +0200] [Job 6] foomatic-rip version $Revision: 3.43.2.15 $ running...
E [25/Apr/2006:09:11:45 +0200] [Job 6] Parsing PPD file ...
E [25/Apr/2006:09:11:45 +0200] [Job 6] *cupsFilter: "application/vnd.cups-postscript 0 foomatic-rip"
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option ColorSpace
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option PageSize
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option PageRegion
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option ImageableArea
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option PaperDimension
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option InputSlot
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option MediaType
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option Resolution
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option EconoMode
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option HalftoningAlgorithm
E [25/Apr/2006:09:11:45 +0200] [Job 6] Added option Font
E [25/Apr/2006:09:11:45 +0200] [Job 6]
E [25/Apr/2006:09:11:45 +0200] [Job 6] Parameter Summary
E [25/Apr/2006:09:11:45 +0200] [Job 6] -----------------
E [25/Apr/2006:09:11:45 +0200] [Job 6]
E [25/Apr/2006:09:11:45 +0200] [Job 6] Spooler: cups
E [25/Apr/2006:09:11:45 +0200] [Job 6] Printer: HL-1250
E [25/Apr/2006:09:11:45 +0200] [Job 6] PPD file: /etc/cups/ppd/HL-1250.ppd
E [25/Apr/2006:09:11:45 +0200] [Job 6] Printer model: Brother HL-1250 Foomatic/hl125...

santo, I think you're experiencing a different issue. With my patch printing works like a charm for me.
You can check your /etc/cups/printers.conf to see if your username and password are actually set properly.

Tried as you said "You should also download samba, samba-common and smbfs" - but downloading the debs and using the deb installer in dapper gives me errors on all the files when trying to install them, and I don't know how to do it any other way :(

Happy to report success:

Soren suggested: "you can add our repository to your sources.list:
deb http://www.linux2go.dk/ubuntu dapper main"

Did that, installed the samba stuff from that repository and now I have a perfect printer through my network.. :)
Thank you for this fix :)

Ok Soren, I'll check it later today as I'm currently in windows (yes, indeed) to get my job done...

> Happy to report success:
>
> Soren suggested: "you can add our repository to your sources.list:
> deb http://www.linux2go.dk/ubuntu dapper main"

worked also for me!
(After deleting the quick-fix proposed in the thread before...)

Thanks!

I checked /etc/cups/printers.conf as suggested and it looks OK (username & password are correctly set), but still no go :-(

+1, and I can confirm that the patched version is working OK

I can confirm that this resolves printing to Windows 2000.

Thanks Soren! Work for me too...(printing via Windows Xp professional)

Sorens packages resolve this bug for me too (but you also have to download smbclient and libsmbclient, since these contain /usr/bin/smbspool!). Thanks for finding the fix.

I recently upgraded from 5.10 to dapper beta and experienced the same problem, namely "pause" after each print attempt. After I inserted "deb http://www.linux2go.dk/ubuntu dapper main" and did an update, which downloaded the SMB files, my printing was restored. QUESTION: Is this fix going to make it into the final release of dapper?

Bug is confirmed and it's being worked on. It even has Major 'severity' set up. So, yes, it will be fixed before Dapper get's out.

It could well a relationship between this bug and bug #39990. Those two issues occurred at the same time. The anaylsis at that bug has indicated that name service lookups using wins lead to a segmentation fault (as reported in mannheim's post).

Regards

Erich

I have installed the patch from

http://www.linux2go.dk/ubuntu

It didn't work in my installation.

(Ubuntu with wins installed using a remote printer on an XP box). The Windows printer still is stalled.

Regards

Erich

I have tried the the patch from

http://www.linux2go.dk/ubuntu

on another machine. It didn't work there either.

I can't print via samba/WindowsXP either, using Dapper.

I get a lot of "E [02/May/2006:17:18:20 +0200] cupsdAuthorize: Local authentication certificate not found!" in /var/log/cups/error_log too, so I would think that this is the same problem.

I've double-checked the settings in /etc/cups/printers.conf and also tried using gnome-cups-manager.

However, since I'm on amd64, the i386-patch isn't installable here.
Are there any solutions in the horizon, apart from downgrading smb?

Thanks

Patch proposed on "http://www.linux2go.dk/ubuntu" works for me.

Using a USB HP Printer connected with a Ubuntu Server shared with Samba with 6 Ubuntu Breezy Desktop and 1 Ubuntu Dapper Desktop, 1 Win2k Desktop
Only this patch resolve the problem of printer going in pause on the Dapper Desktop.
Thanks for this temporary support.

As I did already report, the patch on http://www.linux2go.dk/ubuntu doesn't work for me. There is a difference between Jnifoo's setup and my setup: Like in the original bug report, my shared printer is connected to a Windows box, not to an Ubuntu box.

Regards

Erich

samba from linux2go repositories fixed it for me too.

While adding linux2go via update fixed my problem, I now find that I needed to load Samba in the offricial Ubuntu and it won't load. I am going to add the linux2go repository back in, reload and see if I can then back out linux2go. Getting Samba working correctly is more important to me, at this time, then being able to print.

Hi,
Just wanted to add a "me too" to the list of successes. I added the linux2go repositories, updated the samba packages, removed and added the printer and voila!

Linux box: Ubuntu Dapper flight 6 on an AMD64
Windoze box: Win XP pro, also an AMD64
Printer: Samsung ML-1510 connected to Win XP; I use CUPS and pretty much all recommended settings.

I haven't experienced any other difficulties with samba.

Tak for hjælpen, Søren :-)
Cheers,
Jan

Ed Comer: If you're having trouble getting rid of our package, you can either remove our repository from your sources.list and run:
apt-get install packagename/dapper

Or, you can find the exact version number you want with e.g. "apt-cache showpkg smbclient". At the top you can see the available versions. Currently, there's 3.0.22-1ubuntu1linux2go1 and 3.0.22-1ubuntu1. If you want the latter, just run:
apt-get install smbclient=3.0.22-1ubuntu1

and hey presto! :-D

the packages from linux2go did not resolve this issue for me, the symptoms are exactly the same as they were before

Problem solved with the packages from linux2go.

Printer : HP LJ 4050
Windows 2000 Server, hidden samba server protected by username and password.
Kubuntu Dapper Drake

Thanks a lot (thought the problem came from me, I did not install a smb printer for a looooooong time, but my new university lab uses windows server solutions, instead of the debian servers used in my old lab. It was much more simple using cups ... Anyway, it works here with the patch, thanks a lot !

Soren Hansen: Thanks for the suggestion. I removed linux2go and added the standard Dapper package that would not load with the partial linux2go present. My printing is broken again but Samba now works. This week I have to perform an experiment with Samba as-is, but afterwords I may try re-loading Linux2go again and see if Samba will continue to work.

So, has the patch been applied to the main Ubuntu packages yet? I've tried the Linux2Go packages, and they've fixed the problem for me, but I'm curious as to the status of this bug being fixed in the main packages, especially with Dapper ready to ship in a little over three weeks. It would look bad to have to release this shiny new version of Ubuntu and then tell users they need to install unsupported third party packages just to print to their Windows machine.

There is no point in migrating a patch into the core distribution just because it solves the problem sometimes (or even in most cases). Since the patch doesn't resolve the issue in all cases, to my opinion it is still important to figure out the root cause of the problem.

The logs in two early postings to the bug report show a segmentation fault (signal 11). I am currently having segmentation faults in various places related to Windows networking, not only in smb printing and the linux2go-package doesn't solve any of those issues. On the other hand, the linux2go package works sometimes. So what's the difference? Any recommendations where to start reseraching?

Regards

Erich

On Fri, 2006-05-12 at 21:24 +0000, Erich Pawlik wrote:
> The logs in two early postings to the bug report show a segmentation
> fault (signal 11). I am currently having segmentation faults in various
> places related to Windows networking, not only in smb printing and the
> linux2go-package doesn't solve any of those issues.

That's why the bug is open on "samba". I believe that Adam has a
solution to it, the bug is marked as in progress, so be patient, and
hopefully a fix will be uploaded soon.

Matt
--
<email address hidden>
gnupg pub 1024D/0E6B06FF

I do not totally agree. Maybe it sometimes fails but for another reason (i.e. another bug). Why not fix it for the obvious first?

Look at the first post by Soren, where ubuntu-setlocale.patch is attached with explanation on why it can go wrong. Why not at least fix this known problem first?

I disagree with Alan's opinion. I admit that until this samba bug appeared I was using Dapper for real work. On the other hand, Dapper is still beta - I understand that the priority is to fix the bugs for Ubuntu 06.06, not for an intermediate beta. As Alan has pointed out, we shouldn't push developers to produce a premature fix.

Another point from a bug management perspective: If there are two different error scenarios, we should have two different bug reports. Somebody understanding which issue is being fixed by the linux2go package should file a new bug report with a clear description of the bug fixed in this package.

Regards

Erich

Erich: Agreed. If you're experiencing segmentation faults in other parts of Samba, you should file new bugs for that (or see if there's one already open with the same symptoms).

Soren: Disagreed. My point was that either we forget about the linux2go patch and let Adam do his work or that the people requesting that the patch is moved into the Ubuntu repository post a new bug with a narrower error picture.

Sorry, as a quality assurance professional I am pretty picky about bug management procedures.

The linux2go patch isn't a fix for this issue.. So, the request to move this patch into the standard distro isn't justified, since the patch failed on retest on my two Ubuntu boxes (and I did check error pictures as far as it is posisble with my limited knowledge of cups and samba internals).

There are other smb seg fault issues open on launchpad, but none of them is related to the smb printing backend. Any bug I would file would be a dupliycate of this issue.

Erich, this bug is about the smb printing backend, as the title clearly says. The bug description is a segfault in the process launched by /usr/lib/cups/backend/smb. That file is a symlink to smbspool.

The segfault in smbspool is easily reproducible by the one-liner "echo something | smbspool 99 me test 1 ", as described in my earlier comment. Any fix for the segfault in smbspool is a fix for this bug.

Indeed there are probably other bugs in smb at present; and indeed, some may have the same underlying cause as this one. But Adam's earlier post addresses that and should allay concern.

I have a pretty good understanding of this issue (well, the issue fixed by my patch). It was introduced by a patch pulled in from CVS. However, that particular patch was flawed and makes smbspool segfault upon startup. The "linux2go" patch fixes that particular issue. I believe that any remaining segfaults are symptoms of a different issue.

I don't have the black belt in bug management and QA, etc., but I think I see your point. However, I think the best - although not strictly by the almighty book of QA procedures - way to go about this is to maybe change the description of this bug to match the issue fixed by my patch. However, you're the expert and I'm really a lot more interested in fixing bugs than managing bugs. :-)

Erich, I coincide with your concerns even when I commented. However, I got different conclusions, for a reason that I was lazy to write down clearly.

I have to say that the fix is not premature. It is not that we make a random modification to seem to fix the problem. We have identified (one of) the root cause for the crash. Once the patch gets reviewed, it can't make CUPS worse than before, yet it solves at least part of the problem. How can the patch/fix be considered premature?

If this bug is really that severe (breaks all cups-on-samba functionality, where cups and samba are both in main) across 2 dapper betas, I think it should go into release notes.

The bug "introduced in CVS, pulled in from there, and fixed by Soren's patch attached earlier" is a _blocker_ (in QA terms) bug. Its presence makes any cups-on-samba printing fail. Without the patch getting applied first, how can we give debug traces for the crash even after the patch is applied?

Why can't we fork into another bug? Because as mannheim says, this bug is really for this issue. We got 100% reproducible "cups smb printing backend no longer works". Now we have "bug A", which makes cups-on-samba fail for sure, and we have "bug B", which sometimes causes it fail. Which one do you think qualify for this bug title?

2 bug reports for 2 issues? Agree. IMHO we should apply the patch and mark this bug fixed. Then it should be the people who still fail to open another bug to describe and discuss the prerequisite for the crash to continue appearing.

My opinion:
If there isn't another patch by Adam soon, the fix from linux2go should be added to the official repos as soon as possible:

1. The patch worked for me on different computers. So it is an improvement.

2. This bug is nasty as it disables a basic function. Such things shouldn't be in the "rock stable" dapper release IMHO.

3. Even if it doesn't fix the problem in all cases, that's even more a reason to include it in the repos: The fix should be tested on a even more broad base before including it in the official release and it is not much time for that left!

4. When there appear unsolved issues, they should be filed as another second bug, I agree.

But I really would like Dapper to be released without this bug fixed....

Quoting Adam Conrad:

"Note that this bug hasn't slipped under the radar or anything; I'm just investigating other similar bugs caused by this same patch, so I can fix them all at once, rather than one at a time."

Please, stop spaming the buglist. Nothing in your discussion is productive. Dapper will not get released with bug marked as "Major". If you wish to continue your discussion, please use sounder mailing list or private emails.

This should have been fixed in

samba (3.0.22-1ubuntu2) dapper; urgency=low

  * After much faff about fixing this properly and getting fixes
    submitted upstream (some of which has happened), I've concluded
    that getting every case_tables usage in the code nailed down
    before release just isn't going to happen, so applying a more
    global bandaid (ubuntu-setlocale-fixes.patch) instead to stop
    the SEGVs completely (closes: launchpad.net/{39990,39484,39956})
  * Snag a patch from upstream SVN to stop winbindd from panicking
    when not joined to a domain (closes: launchpad.net/32614)
  * Mangle patch fuzz for previous patch to make it apply cleanly.

 -- Adam Conrad <email address hidden> Tue, 16 May 2006 22:36:17 +1000

Reporters, can you please confirm?

I've had the similar problems and now it seems to work. I don't know if the problem was my typo or Gnomes printer configuration tools, but the user password in printers.conf was replaced by the detected connection name of the printer connected to. Some nanoing with the config file and restarting cups afterwards fixed it. THANK YOU!

Fixed in 3.0.22-1ubuntu2.

fix is working on my 2 machines

Regards

Erich

Still no joy! Each day I load all of the Dapper update, thus my machine is up to date, yet I still cannot print via my Windows box as I could with linux2go. I checked my installed version and it is 3.0.22-1ubuntu3, which, I assume, was loaded as part of the official updates. Is the fix mentioned by Martin Pitt part of the normal updates or am I supposed to search for 3.0.22-1ubuntu2, or the setlocale patch, or what??

As of this update I can now print from Linux to Windows using two
different drivers on two different prints. It seems that the problem
left is from Windows to a cups server on Linux.

On Wed, 2006-05-17 at 15:04 +0000, Ed Comer wrote:
> Still no joy! Each day I load all of the Dapper update, thus my machine
> is up to date, yet I still cannot print via my Windows box as I could
> with linux2go. I checked my installed version and it is 3.0.22-1ubuntu3,
> which, I assume, was loaded as part of the official updates. Is the fix
> mentioned by Martin Pitt part of the normal updates or am I supposed to
> search for 3.0.22-1ubuntu2, or the setlocale patch, or what??
>

What problems do you have when printing from Windows to CUPS? Do you use IPP or SMB protocol?

No. My wording wasn't clear enough. My problem that remains is printing from a Ubuntu Dapper machine TO a printer on windows XP machine. It worked fine using linux2go but not the official Ubuntu libraries downloaded via update. However, my loaded version is 3.0.22-1ubuntu3, not 3.0.22-1ubuntu2 as mentioned by Martin Pitt. Like I said previously, is the fix mentioned by Martin Pitt part of the normal updates or am I supposed to search for 3.0.22-1ubuntu2, or the setlocale patch, or what??

Ed, the fix is supposed to be contained in the version you have, but apparently it's incomplete. Adam, any idea?

Can confirm that the latest samba package updates have fixed it for me, too. I can print from my Kubuntu machine to the Windows machine with my printer.

SMB printing is now working fine here too (Dapper/PPC64)

Joy at last! After seeing that it was working for others I felt that something was wrong with my load, so I did a complete removal for all of SAMBA and CUPS. Then I did an install for SAMBA and CUPS and it now works!! I can, once again, print to the printer on my XP box. Thanks!

OK. I can confirm my Epson Stylus Photo R300 is printing again in Windows XP with smb after the last update of SAMBA and CUPS, Dapper386. I'm so glad....

i can confirm this bug too, since dapper, i'm unable to use printers at school! (and other ubuntu users have the same problem too)

please fix this soon

just noticed that it works, problem was that the printer was replaced with another model :D and not dapper, sorry!

Can it be confirmed if this bug is still being worked on? I have seen the "Fix released" but I am still having the exact problem with my Dapper 6.06 install. It occured when I did my distro update from 5.10 and I have tried a complete default install as well as adding the printer from our NT domain after a full update of 6.06. The printers connection only lasts until cupsys is restarted, then the user/password info gets dropped and the printer goes to Paused.

Regards

On Tue, Jul 04, 2006 at 11:39:50PM -0000, HarveyB wrote:
> Can it be confirmed if this bug is still being worked on?

To the best of our knowlegde it had been fixed.

> I have seen the "Fix released" but I am still having the exact problem
> with my Dapper 6.06 install. It occured when I did my distro update
> from 5.10 and I have tried a complete default install as well as
> adding the printer from our NT domain after a full update of 6.06. The
> printers connection only lasts until cupsys is restarted, then the
> user/password info gets dropped and the printer goes to Paused.

This sounds like a different issue. The issue handled in this bug was
smbspool segfaulting so any samba printers effectively were not working.

Does the printer in fact work from the time where you configure it until
cupsys is restarted?

How do you determine that the user/password info gets dropped?

Cheers, Søren

Yes the printer works fine when I first set it up until cupsys gets restarted. When I do a cupsys restart the printer still shows as being "Ready" however sending a print job to it results in a "Printer Paused" result.

I noticed when I started the gnome-cups-manager from a terminal that when I first installed the printer and opened up the properties menu a list of ppd info gets printed to the terminal and the last of the info is the connection details. When cupsys is restarted the connection details gets dropped.

Example
When I have established a connection to the windows printer the last of the terminal information after opening up the Properties box is

** (gnome-printer-view:8176): WARNING **: method :'smb'
user :'#$'
host :'ASOFSVR'
port :0
resource :'/Kyoc_Up'

After doing a /etc/init.d/cupsys restart I now get this when the Properties menu is opened

** (gnome-printer-view:8401): WARNING **: method :'smb'
user :''
host :''
port :0
resource :'/'

Cheers

Actually I should also note that the /etc/cups/printer.conf information does not change after the printer is initially set up. The "DeviceURI smb://harvey:!@#$@ASOFSVR/Kyoc_Up" line as well as all other information remains constant when the printer is in either state.

Cheers again

This bug is STILL occuring on my computer... Should it be fixed by now?

Kind Regards,
Matthew

Dito here... No idea what's going wrong.

This the latest tail from my /var/log/cups/error_log

E [10/Jul/2006:15:59:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:33 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:38 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:41 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:41 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:41 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:43 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:44 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:47 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:47 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:47 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:48 +0200] cupsdAuthorize: Local authentication certificate not found!
E [10/Jul/2006:15:59:50 +0200] cupsdAuthorize: Local authentication certificate not found!

I am using a fresh install of Kubuntu Edgy and have the same problem:

E [07/Nov/2006:14:13:50 +0100] cupsdAuthorize: Local authentication certificate not found!

I am unable to use deb http://www.linux2go.dk/ubuntu dapper main (but perhaps I misunderstand it).

Sjors

I've reproduce this error in current edgy version. It's strange, as I have two edgy machines connected to the same network, with the same configuration, and one of them segfaults and the other doesn't.

I also get the cupsdAuthorize: Local authentication certificate not found!

Last week I was able to print to my HP1020 and my HP 5L which was installed on my wife's Windows XP box. Then I nuked Windows, installed Edubuntu (fiesty), and it also worked. Then I wanted to do some file sharing and installed Samba, and suddenly my printers stopped working. I cannot get either of them going on my Edubuntu box, or on my Ubuntu box which has samba installed.

Today I tried to remove Samba completely, but I was still not able to get the printer going.

Is there any way I can resolve this issue? (Is it still seen as a bug?)

Still getting "cupsdAuthorize: Local authentication certificate not found!"

I have a box originally with a fresh install of Edgy, and all updated patches.

Using samba 3.0.22-1ubuntu4

I have tried uninstalling and reinstalling Samba and Cupsys with apt but continue to get the "cupsdAuthorize" message.

Any help is greatly appreciated.

Have this problem in Edgy with all latest updates installed too.

In my case solution was very simple - password for printer access contain symbol "<".

After I have removed this very special (for unix shell) symbol - printer start working again!

+1

im experiencing the same problem, i can not use a printer share on linux at all, i already tried:

 WinXP (shared printer) to Suse 10.2 (client)
 WinXP (shared printer) to Ubuntu 6.04 (client)
 Suse 10.2 (share via Samba) to Ubuntu 6.04 (client)

neither worked. I always get the:
Ready: /usr/lib/cups/backend/smb failed
or
Paused: /usr/lib/cups/backend/smb failed
error!

i have done all the lates updates!

YET !!!!!!:::

 Suse 10.2 (share via Samba) to WinXP client works perfect!
I just had to choose the right driver. no authentication needed at all. I could start printing immediately.

6.04? Do you mean 6.06 perhaps? Is it properly up-to-date?

typo above, ofcourse it should mean 6.10.... i was probably already thinking of 7.04 so i mixed it up,....

Weirdly this just started happening to two fairly static (non-updated) ubuntu 6.06's that a client has. The linux2go patch seems no longer available and I have just updated samba smfs, and associated libraries, so I may have to go through and run all the patches for the machine incase I missed one. But the next question is, is it resolved. and Why did it start happening on both machines at the same time.

does this bug is still present in gutsy? use samba and a remote printer and it works fine

I need to verify it's still an issue.

On Nov 13, 2007 2:41 PM, Nicolas Valcárcel <email address hidden> wrote:

> does this bug is still present in gutsy? use samba and a remote printer
> and it works fine
>
> --
> cups smb printing backend no longer works
> https://bugs.launchpad.net/bugs/39484
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
It is in games that many men discover their paradise.
-- Robert Lynd

No one has confirmed this bug is still on hardy, marking it as invalid, please feel free to reopen the bug report if someone can reproduce it on hardy.

Yes, it is still happening in Hardy Heron 8.04.

I am trying to connect to a printer via SMB and this is the error that I'm getting:

E [16/Apr/2008:14:33:51 +1000] CUPS-Add-Modify-Printer: Unauthorized
E [16/Apr/2008:14:36:19 +1000] cupsdAuthorize: Local authentication certificate not found!
E [16/Apr/2008:14:36:19 +1000] Resume-Printer: Unauthorized
E [16/Apr/2008:14:36:22 +1000] [Job 12] No ticket cache found for userid=0
E [16/Apr/2008:14:36:22 +1000] [Job 12] Can not get the ticket cache for root
E [16/Apr/2008:14:36:22 +1000] [Job 12] Session setup failed: NT_STATUS_LOGON_FAILURE
E [16/Apr/2008:14:36:22 +1000] [Job 12] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [16/Apr/2008:14:36:22 +1000] [Job 12] Unable to connect to CIFS host, will retry in 60 seconds...
E [16/Apr/2008:14:36:34 +1000] PID 26905 (/usr/lib/cups/filter/foomatic-rip) crashed on signal 9!
E [16/Apr/2008:14:36:34 +1000] PID 26906 (/usr/lib/cups/backend/smb) crashed on signal 9!
E [16/Apr/2008:14:36:34 +1000] [Job 12] No ticket cache found for userid=0
E [16/Apr/2008:14:36:34 +1000] [Job 12] Can not get the ticket cache for root
E [16/Apr/2008:14:36:34 +1000] [Job 12] Session setup failed: NT_STATUS_LOGON_FAILURE
E [16/Apr/2008:14:36:34 +1000] [Job 12] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [16/Apr/2008:14:36:34 +1000] [Job 12] Unable to connect to CIFS host, will retry in 60 seconds...
E [16/Apr/2008:14:36:41 +1000] [Job 13] No ticket cache found for userid=0
E [16/Apr/2008:14:36:41 +1000] [Job 13] Can not get the ticket cache for root
E [16/Apr/2008:14:36:41 +1000] [Job 13] Session setup failed: NT_STATUS_LOGON_FAILURE
E [16/Apr/2008:14:36:41 +1000] [Job 13] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [16/Apr/2008:14:36:41 +1000] [Job 13] Unable to connect to CIFS host, will retry in 60 seconds...
E [16/Apr/2008:14:38:53 +1000] [Job 14] No ticket cache found for userid=0
E [16/Apr/2008:14:38:53 +1000] [Job 14] Can not get the ticket cache for root
E [16/Apr/2008:14:38:53 +1000] [Job 14] Session setup failed: NT_STATUS_LOGON_FAILURE
E [16/Apr/2008:14:38:53 +1000] [Job 14] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [16/Apr/2008:14:38:53 +1000] [Job 14] Unable to connect to CIFS host, will retry in 60 seconds...
E [16/Apr/2008:14:39:23 +1000] [Job 15] No ticket cache found for userid=0
E [16/Apr/2008:14:39:23 +1000] [Job 15] Can not get the ticket cache for root
E [16/Apr/2008:14:39:23 +1000] [Job 15] Session setup failed: NT_STATUS_LOGON_FAILURE
E [16/Apr/2008:14:39:23 +1000] [Job 15] Tree connect failed (NT_STATUS_ACCESS_DENIED)
E [16/Apr/2008:14:39:23 +1000] [Job 15] Unable to connect to CIFS host, will retry in 60 seconds...

This bug is a segfault of the smb cups backend that was fixed in Ubuntu 6.06. Please do not use it as a generic dumping ground for reporting issues with smb printing problems. In particular, "Local authentication certificate not found!" is *not* an error message indicating the presence of this bug.

socceroos, your log clearly shows that you are unable to authenticate to the print server. That's unrelated to this bug, and most likely not a bug at all but a configuration error.

Closing this bug again.

If you have a look at the original bug report at the top of this page you can see how I would figure that it is related (uuuh, the same error?). Whats more, I'm not spamming this bug with my own, if you read this post please (just above mine): "No one has confirmed this bug is still on hardy, marking it as invalid, please feel free to reopen the bug report if someone can reproduce it on hardy."

I added this because I'm still experiencing problems adding SMB printers and this bug was so close to the one I was going to report that I thought it would be best to add something here rather than open up a 'duplicate' report.

I can confirm that this bug return again in dapper from last upgrade of samba to 3.0.22. Before that, I could print from other dapper and windows XP to dapper print server, but recently it stopped with message in linux client printer:

Ready: /usr/lib/cups/filter/foomatic-rip failed

And using debug, it shows the problem is:

error writing spool : NT_STATUS_ACCESS_DENIED

I have sent an email to samba mailing list about this problem as I thought it is samba related issue, not ubuntu.

David

I just realised that I have not upgraded samba. I upgraded many other things but samba. So, should we reopen this bug for dapper?

David

After I downgraded cupsys from cupsys_1.2.2-0ubuntu0.6.06.9_i386 to cupsys_1.2.2-0ubuntu0.6.06_i386, it works again. Should I open a new bug report for cupsys or just re-open this bug?

David