[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/607311
This appears to be resolved in Ubuntu server bug #570456 if I am reading
the thread correctly:
http://www.mail-archive.com/ubuntu-server-
b...@lists.ubuntu.com/msg38649.html
Seems there is an unimplemented cp15 register write (c9, c12, {0, 0})
with Ubuntu OMAP image that is at the root of the
Perhaps I'm being dumb, but I can't see the relevance?
On Thu, Sep 09, 2010 at 03:56:38PM -, freecode wrote:
This appears to be resolved in Ubuntu server bug #570456 if I am reading
the thread correctly:
http://www.mail-archive.com/ubuntu-server-
b...@lists.ubuntu.com/msg38649.html
You're not being dumb - my mistake. I managed to find the issue locally.
The two are unrelated as the issue actually traced down to a
misconfigured share in AD and not the same issue as above. Call this one
a mea culpa - and never mind the report.
--
mount.cifs fails with cannot allocate memory
This appears to be resolved in Ubuntu server bug #570456 if I am reading
the thread correctly:
http://www.mail-archive.com/ubuntu-server-
b...@lists.ubuntu.com/msg38649.html
Seems there is an unimplemented cp15 register write (c9, c12, {0, 0})
with Ubuntu OMAP image that is at the root of the
Perhaps I'm being dumb, but I can't see the relevance?
On Thu, Sep 09, 2010 at 03:56:38PM -, freecode wrote:
This appears to be resolved in Ubuntu server bug #570456 if I am reading
the thread correctly:
http://www.mail-archive.com/ubuntu-server-
b...@lists.ubuntu.com/msg38649.html
You're not being dumb - my mistake. I managed to find the issue locally.
The two are unrelated as the issue actually traced down to a
misconfigured share in AD and not the same issue as above. Call this one
a mea culpa - and never mind the report.
--
mount.cifs fails with cannot allocate memory
What version are you copying from?
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
mount.cifs fails with cannot allocate memory
https://bugs.launchpad.net/bugs/607311
You received this bug notification because you
Server is a ReadyNAS Duo running RAIDiator 4.1.6 [1.00a043].
Client is Ubuntu 10.04 x86.
On further experiment I was able to fix the problem by deleting and
recreating the share on the server.
--
mount.cifs fails with cannot allocate memory
https://bugs.launchpad.net/bugs/607311
You received
What version are you copying from?
** Changed in: samba (Ubuntu)
Importance: Undecided = Low
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
mount.cifs fails with cannot allocate memory
https://bugs.launchpad.net/bugs/607311
You received this bug notification because you
Server is a ReadyNAS Duo running RAIDiator 4.1.6 [1.00a043].
Client is Ubuntu 10.04 x86.
On further experiment I was able to fix the problem by deleting and
recreating the share on the server.
--
mount.cifs fails with cannot allocate memory
https://bugs.launchpad.net/bugs/607311
You received
12 matches
Mail list logo
