It does not work for me in hardy (KDE, Kubuntu) :-((
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/132791
Title:
cups smb logon fails quietly
To manage notifications about this bug go to:
https://b
It does not work for me in lucid (KDE, Kubuntu) :-(
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
it works for me in lucid, thanks
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Well, GNOME seems not to know how to prompt for a password anyway, yet.
As it was discovered in bug #283811.
But then, it sounds like the cache is not invalidated on error (else I
suppose it would not retry so much as to deactivate password a while on
the server).
As far I could tell, this cache
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
Status: Incomplete => Confirmed
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
On Thu, Aug 30, 2007 at 06:34:22PM -, Justin wrote:
> The print queue credentials were fine when I created it, but when I was
> forced to change my password by the domain policy it became broken
> quietly. That's why I think it makes sense to alert the user.
I agree that it makes sense. I just
The print queue credentials were fine when I created it, but when I was
forced to change my password by the domain policy it became broken
quietly. That's why I think it makes sense to alert the user.
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug not
Till, what can Samba do to make this information available to the user?
I'm not quite familiar with CUPS's backend API.
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because
The credentials are handled by the "smb" CUPS backend
(/usr/lib/cups/backend/smb) which is provided by the samba package.
Moving to samba ...
Note also that in Gutsy, with gnome-cups-manager being replaced by
system-config-printer one can check the credentials before creating a
print queue to an S
I confirm this bag, Ubuntu Feisty Fawn, printer shared on Windows XP
E [23/Aug/2007:15:01:39 +0400] cupsdAuthorize: Local authentication certificate
not found!
E [23/Aug/2007:15:01:39 +0400] cupsdAuthorize: Local authentication certificate
not found!
E [23/Aug/2007:15:01:39 +0400] cupsdAuthorize
I can confirm this, Ubuntu Feisty Fawn, printer shared on Windows Vista
E [20/Aug/2007:18:08:34 +0300] [Job 140] Session setup failed:
NT_STATUS_LOGON_FAILURE
E [20/Aug/2007:18:08:34 +0300] [Job 140] No ticket cache found for userid=1000
E [20/Aug/2007:18:08:34 +0300] [Job 140] Can not get the ti
** Changed in: cupsys (Ubuntu)
Sourcepackagename: None => cupsys
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
attaching my /var/log/cups/error_log
** Attachment added: "attaching my /var/log/cups/error_log"
http://launchpadlibrarian.net/8844794/error_log
--
cups smb logon fails quietly
https://bugs.launchpad.net/bugs/132791
You received this bug notification because you are a member of Ubuntu
Bugs, w
13 matches
Mail list logo
