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
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
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
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, marki
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 bu
** 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 maili
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 [1
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/3
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
> Yo
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
** 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
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.
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-b
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
+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/l
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
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" mes
** 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
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 insta
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 ba
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
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:5
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
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
-
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
-
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 fir
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 dis
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
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/de
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:
** 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
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
http
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 print
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
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:
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/desk
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 m
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
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 m
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
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
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
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 cu
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
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 w
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 th
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) th
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 s
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
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 b
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-bug
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 develop
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?
--
c
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
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 pos
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
56 matches
Mail list logo
