[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
** Changed in: samba (Ubuntu) Target: None = ubuntu-8.04 -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. ** Changed in: samba (Ubuntu) Status: Confirmed = Fix Released Target: ubuntu-8.04 = None -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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... ** Changed in: samba (Ubuntu) Status: Invalid = Confirmed -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. ** Changed in: samba (Ubuntu) Status: Confirmed = Invalid -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 39484] Re: cups smb printing backend no longer works
I need to verify it's still an issue. On Nov 13, 2007 2:41 PM, Nicolas Valcárcel [EMAIL PROTECTED] 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 -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
** Changed in: samba (Ubuntu) Assignee: Adam Conrad (adconrad) = Ubuntu Server Team (ubuntu-server) -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://bugs.launchpad.net/bugs/39484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
typo above, ofcourse it should mean 6.10 i was probably already thinking of 7.04 so i mixed it up, -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
6.04? Do you mean 6.06 perhaps? Is it properly up-to-date? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
+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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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! -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
** Also affects: samba (Baltix) Importance: Undecided Status: Unconfirmed -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. ** Changed in: samba (Ubuntu) Status: Fix Released = Confirmed -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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! -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
This bug is STILL occuring on my computer... Should it be fixed by now? Kind Regards, Matthew -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: [Bug 39484] Re: cups smb printing backend no longer works
On Tue, Jul 04, 2006 at 11:39:50PM -, 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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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:[EMAIL PROTECTED]@ASOFSVR/Kyoc_Up line as well as all other information remains constant when the printer is in either state. Cheers again -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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:[EMAIL PROTECTED]@ASOFSVR/Kyoc_Up line as well as all other information remains constant when the printer is in either state. Cheers again -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
just noticed that it works, problem was that the printer was replaced with another model :D and not dapper, sorry! -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
** Bug 40990 has been marked a duplicate of this bug -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
SMB printing is now working fine here too (Dapper/PPC64) -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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! -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 PROTECTED] Tue, 16 May 2006 22:36:17 +1000
Reporters, can you please confirm?
--
cups smb printing backend no longer works
https://launchpad.net/bugs/39484
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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! -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
Fixed in 3.0.22-1ubuntu2. ** Changed in: samba (Ubuntu) Status: In Progress = Fix Released -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
fix is working on my 2 machines Regards Erich -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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?? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: [Bug 39484] Re: cups smb printing backend no longer works
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 +, 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?? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
What problems do you have when printing from Windows to CUPS? Do you use IPP or SMB protocol? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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?? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
Ed, the fix is supposed to be contained in the version you have, but apparently it's incomplete. Adam, any idea? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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). -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. :-) -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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. -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: [Bug 39484] Re: cups smb printing backend no longer works
On Fri, 2006-05-12 at 21:24 +, 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 PROTECTED] gnupg pub 1024D/0E6B06FF -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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? -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39484] Re: cups smb printing backend no longer works
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 -- cups smb printing backend no longer works https://launchpad.net/bugs/39484 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
