[Bug 357569] Re: please set usershare path
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 usershare path explicitely defined and got the exact same error as without it. Could you elaborate ? -- please set usershare path https://bugs.launchpad.net/bugs/357569 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 359669] Re: mount.cifs crashed with SIGSEGV in main() - SmbMount - smbfs
*** 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 command-line parameters ** This bug has been marked a duplicate of bug 357994 mount.cifs crashed with SIGSEGV in main() -- mount.cifs crashed with SIGSEGV in main() - SmbMount - smbfs https://bugs.launchpad.net/bugs/359669 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 357994] Re: mount.cifs crashed with SIGSEGV in main()
** 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: samba (Ubuntu) Importance: Undecided = Low ** Changed in: samba (Ubuntu) Status: New = Confirmed -- Running mount.cifs without any parameter crashes with SIGSEGV in main() https://bugs.launchpad.net/bugs/357994 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
OK, summing it up (again): - You boot a Jaunty beta LiveCD - Running smbclient -L NASBOXIPADDRESS 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 Unable to mount location / Failed to retrieve share list from server error box. My guess is that your NAS box doesn't properly implement the local master browser for the windows networking domain. Clicking 'Windows Network' or running smbtree -N query the local master browser. Please test: - Run smbtree -b -N - Open location smb://NASBOXIPADDRESS/ in Nautilus directly -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 117727] Re: cifs mounts: unable to move dangling symlinks (case of svn ceckout with symlinks)
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 notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 356789] Re: Upcoming recordings not displaying unless recording in progress
*** 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 -- Upcoming recordings not displaying unless recording in progress https://bugs.launchpad.net/bugs/356789 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu (via bug 326768). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 358173] Re: Database connection issues with Mythbuntu 9.04 x64
*** 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 this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu (via bug 326768). -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 98658] Re: cifs doesn't support connecting as guest
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/bugs/98658 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
** 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
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 = Confirmed ** Changed in: mythbuntu Milestone: None = jaunty-rc -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 361066] [NEW] Difficult to share external hard drives
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, except that when I tried to access the share, I got a not-very-helpful generic error message from nautilus. So I tried to use smbclient directly, and got only NT_STATUS_BAD_NETWORK_NAME errors, even though 'smbclient -L' revealed the share existing normally. After checking the samba log on the user's laptop it appeared that the shared path (/media/USB-DISK) did not exist! But it certainly did. Eventually I realised that the problem was that the 'nobody' user could not access /media/USB-DISK because hal's default policy is to mount disks so that they are only readable by the mounting user. So the next step was to add the mount options 'fmask=111,dmask=000' to the volume, which was ok to do in nautilus, and then remount the disk. But I still got NT_STATUS_BAD_NETWORK_NAME errors on the client. I thought that maybe I would have to restart samba to persuade it to try and look in /media/USB-DISK again, but that didn't work--and then, the share disappeared from the output of smblcient -L entirely! At this point I ran 'net usershare list' on the server and got the following output: info_fn: file /var/lib/samba/usershares/blah is not a well formed usershare file. info_fn: Error was Path not allowed. Hm, not very clear. At this point I gave up and began to write this bug report. Meanwhile, my user rebooted, and then examined the share properties in nautilus. Now, they got an error saying that the share would not work because 'usershare owner only' needed to be set to false. After changing the option and restarting samba, I was then able to access the share. Phew! So I think there are a couple of different bugs here: 1. Unclear error messages from samba if it is unable to access a shared directory 2. No warning from nautilus-share if samba can't access a shared directory 3. nautilus-share did not recognise that the situation had changed and did not present the useful message until the user had restarted ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- Difficult to share external hard drives https://bugs.launchpad.net/bugs/361066 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 361070] [NEW] Dovecot - zlib got a panic
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] - imap [0xb8065955] - /usr/lib/dovecot/modules/imap/lib20_zlib_plugin.so [0xb7e3914e] - imap(i_stream_read+0x38) [0xb806b0c8] - imap(i_stream_read_data+0x4b) [0xb806b1ab] - imap(message_parse_header_next+0x83) [0xb805d093] - imap [0xb805a4a0] - imap [0xb805ab6f] - imap(i_stream_read+0x38) [0xb806b0c8] - imap(i_stream_read_data+0x4b) [0xb806b1ab] - imap(message_get_body_size+0x6d) [0xb806022d] - imap [0xb7fec8d9] - imap(imap_fetch+0x16e) [0xb7fea3ee] - imap(cmd_fetch+0x26e) [0xb7fe310e] - imap(cmd_uid+0x6d) [0xb7fe6f4d] - imap [0xb7fe7abe] - imap [0xb7fe7b6b] - imap [0xb7fe8195] - imap(client_input+0x77) [0xb7fe8687] - imap(io_loop_handler_run+0xfd) [0xb806ebcd] - imap(io_loop_run+0x30) [0xb806dec0] - imap(main+0x4bb) [0xb7ff13fb] - /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e5a685] - imap [0xb7fe1301] The mails are bzip2-compressed. Description:Ubuntu 8.10 Release:8.10 If you need further information, please send me a mail. ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New -- Dovecot - zlib got a panic https://bugs.launchpad.net/bugs/361070 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 357569] Re: please set usershare path
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 you have beaten me to it. But do you have anything else to add to this particular issue which might be relevant? Thanks, Anand On Tue, Apr 14, 2009 at 9:37 AM, Thierry Carrez thierry.car...@ubuntu.com wrote: 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 usershare path explicitely defined and got the exact same error as without it. Could you elaborate ? -- please set usershare path https://bugs.launchpad.net/bugs/357569 You received this bug notification because you are a direct subscriber of the bug. -- please set usershare path https://bugs.launchpad.net/bugs/357569 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360689] Re: Default Ubuntu configuration is backscatter source in Jaunty
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 always be a good idea. ** Changed in: amavisd-new (Ubuntu) Status: New = Incomplete -- Default Ubuntu configuration is backscatter source in Jaunty https://bugs.launchpad.net/bugs/360689 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360689] Re: Default Ubuntu configuration is backscatter source in Jaunty
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 backscatter is a good default approach. It's easy enough to change for people experienced enough to manage the consequences. ** Changed in: amavisd-new (Ubuntu) Status: Incomplete = Confirmed -- Default Ubuntu configuration is backscatter source in Jaunty https://bugs.launchpad.net/bugs/360689 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 361070] Re: Dovecot - zlib got a panic
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.net/bugs/361070 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 360689] Re: Default Ubuntu configuration is backscatter source in Jaunty
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/360689 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 333460] Re: [Hardy][LDAP]client authentication broken
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 incomplete. ** Changed in: libpam-ldap (Ubuntu) Status: New = Incomplete -- [Hardy][LDAP]client authentication broken https://bugs.launchpad.net/bugs/333460 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libpam-ldap in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
