What is this uncontroversial change ?
If it's "Please set in smb.conf: usershare path =
/var/lib/samba/usershares", I fail to see what having it in the
configuration file but not created on the filesystem would change to the
error message you are observing. I tried "net usershare info" with the
us
*** This bug is a duplicate of bug 357994 ***
https://bugs.launchpad.net/bugs/357994
Mick: I've made this bug a duplicate of a public one so please follow up
on bug 357994.
** This bug is no longer a duplicate of bug 356009
mount.cifs crashed with SIGSEGV in main() in the absence of comman
** This bug is no longer a duplicate of bug 356009
mount.cifs crashed with SIGSEGV in main() in the absence of command-line
parameters
** Summary changed:
- mount.cifs crashed with SIGSEGV in main()
+ Running mount.cifs without any parameter crashes with SIGSEGV in main()
** Changed in: samb
OK, summing it up (again):
- You boot a Jaunty beta LiveCD
- Running "smbclient -L " successfully lists the shares on NAS
box
- Running "findsmb" successfully shows NAS box
- Running "smbtree -N" doesn't list the NAS box
- Double-Clicking on "Windows network" in Nautilus Places/Network brings a
"
This should have been fixed in 3.3.1, so the problem should be gone in Jaunty.
Could anyone affected please confirm that this is fixed in Jaunty ?
--
cifs mounts: unable to move dangling symlinks (case of svn ceckout with
symlinks)
https://bugs.launchpad.net/bugs/117727
You received this bug not
*** This bug is a duplicate of bug 326768 ***
https://bugs.launchpad.net/bugs/326768
** This bug is no longer a duplicate of bug 358173
Database connection issues with Mythbuntu 9.04 x64
** This bug has been marked a duplicate of bug 326768
mysql thinks it has crashed when it hasn't
--
*** This bug is a duplicate of bug 326768 ***
https://bugs.launchpad.net/bugs/326768
** This bug has been marked a duplicate of bug 326768
mysql thinks it has crashed when it hasn't
--
Database connection issues with Mythbuntu 9.04 x64
https://bugs.launchpad.net/bugs/358173
You received t
It means this bug (not able to connect as guest using CIFS) was fixed.
Reading man mount.cifs shows that you should use sec=none on connections
with the NULL user ("guest" connections), so that's not a bug that will
be fixed.
--
cifs doesn't support connecting as guest
https://bugs.launchpad.net/
** Also affects: mythbuntu
Importance: Undecided
Status: New
--
mysql thinks it has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
--
Ubun
Adding mythbuntu. It seems to me that the " & wait" should make things
more reliable and predictable rather than less, so I must be missing
something. Any danger in removing the " & wait"?
** Changed in: mythbuntu
Importance: Undecided => Critical
** Changed in: mythbuntu
Status: New
Public bug reported:
A user found it hard to share files on an external hard drive. Although
it is not clear which package to file the bug against, I guess samba is
a reasonable starting point.
The user wanted to share files on an external usb hard drive. nautilus-
share made that part easy, exce
Public bug reported:
Binary package hint: dovecot-imapd
Apr 14 15:14:36 xxx dovecot: Panic: IMAP(x...@yyy.de): file istream-zlib.c:
line 102 (i_stream_zlib_read): assertion failed: (errno != 0)
Apr 14 15:14:36 xxx dovecot: IMAP(x...@yyy.de): Raw backtrace: imap
[0xb80660c1] -> imap [0xb8066153]
The uncontrovorsial changes are the ones I already elaborated.
Please let me know if you did not understand my English and I will try
to explain things once again.
Obviously the bug report asking for the directory to be created on the
filesystem has not been filed.
I will file it shortly, unless
I can confirm this behavior in a default configured amavisd-new
1:2.6.2-2ubuntu1.
That said I'm not sure if I agree on this being a bug. There are plenty
of legitimate cases where people might send an attachment of the
forbidden type. Simply throwing them away without letting anyone know
might not
True, but it's far more common that it's bad content sent from a forged
address. Not sending backscatter is a clear best pracice these days.
More experienced admins might set up a quarantine/release system
(amavisd-new supports this), but such a system is too complex for a
default. I think no ba
OK, I ran a bunzip over all mails in this folder, but the error remains.
Then I deleted the dovecot*-Files in that folder and I am able to acces
that folder without the panic.
It seems to me that the panic was triggered by the cache-Files
--
Dovecot - zlib got a panic
https://bugs.launchpad.ne
Thanks. I'll see if I can get this in between the RC and release.
** Changed in: amavisd-new (Ubuntu)
Milestone: None => ubuntu-9.04
Assignee: (unassigned) => Scott Kitterman (kitterman)
--
Default Ubuntu configuration is backscatter source in Jaunty
https://bugs.launchpad.net/bugs/360
fidel,
ldap-auth-config exists and is even installed on your system.
Please follow the instructions at:
https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html#openldap-auth-config
that is, run:
sudo dpkg-reconfigure ldap-auth-config
not just:
sudo ldap-auth-config
Thanks.
Marking as i
OK, this bug is about "net usershare info" returning an error by
default, resulting in nautilus-share spurious messages. You suggest
adding "usershare path = /var/lib/samba/usershares" to smb.conf.
However, in default installs, "net usershare info" returns exactly the
same error with or without tha
19 matches
Mail list logo
