It could also be that you have a adsl modem what does not resolve all
the names for you as you want, like say a Tomson modem, but if you are
correct in this, why does it do what it has to do, with the ' user-pre'
addition in my case and probably someone elses' .
regards.
On wo, 2009-07-08 at 15:4
I've attached my smb.conf file, if it helps. -- Scott
** Attachment added: "smb.conf"
http://launchpadlibrarian.net/28840002/smb.conf
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a member of Ubuntu
S
Hi Thierry,
I tried what you suggested and had the same problem. However, I did
discovered something. It seems that it is the *name* of the share that
is causing the problem rather than what it is pointing to. On my system,
anything shared using the name "shared" is read-only, whether it points
to
** Branch linked: lp:ubuntu/karmic/amavisd-new
--
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
I appreciate the attempts Ubuntu people have made to reproduce the
problem, and I'm baffled that myself and my users are still easily
reproducing the problem.
I once again reproduced the problem on one of my Ubuntu configurations,
and observed through "/proc//limits" that the limits are
"unlimited
A backport of 5.0.38 doesn't produce a mysqld crash:
math...@t-mysqld-d:~$ mysql -u root
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 5.0.38-Ubuntu_0ubuntu1-log Ubuntu 7.04 distribution
Type 'help;' or '\h' for help. Type '\c' to clear th
On hardy and above the server doesn't crash. Instead the following error
is reported:
ERROR 1436 (HY000): Thread stack overrun: 250312 bytes used of a 262144
byte stack, and 12000 bytes needed. Use 'mysqld -O thread_stack=#' to
specify a bigger stack.
Marking bug Fixed Released for hardy and ab
Both hardy (5.0.51a) and karmic (5.0.75) don't allow the use of such a
query:
mysql> SELECT * FROM (SELECT mu.User FROM mysql.user mu UNION SELECT mu.user
FROM mysql.user mu ORDER BY mu.User) a;
ERROR 1054 (42S22): Unknown column 'mu.User' in 'order clause'
which seems to be right behavior.
Mar
I've tried to put together a test case in the bug description, but
apparently I've overlooked something in the setup that isn't covered
very clearly in the samba howtos, because even 'wbinfo -g' fails for me
when trying to run this test.
** Description changed:
Binary package hint: samba
I
On Tue, Jun 23, 2009 at 01:32:18PM -, Adrien Cunin wrote:
> given that it's been in -proposed for more than 3
> months with no negative feedback (nor positive, right), would it be
> possible to assume it's safe to move it to -updates?
The lack of positive feedback makes this a risk, since this
(err, yes, obviously that approach only works with netboot not CD)
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-iscsi in ubuntu.
--
Ubuntu-server-bugs mail
open-iscsi-udeb isn't in the installer initrd, but instead is retrieved
from the archive at run-time; so booting the installer with apt-
setup/proposed=true (once this has built and published) should be
sufficient.
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You rece
Adrien,
Please note that the SRU verification team consists of a handful of
folks trying to do verifications across a wide range of packages; for
bugs that require deep configurations to reproduce (like setting up an
entire NT4 domain), it's far better if users of the package test the
uploads sinc
Colin, as the bug is in the installer part of the package, I would need
an ISO to test. Or can I test using the netboot installer?
--
iSCSI install fails under hardy
https://bugs.launchpad.net/bugs/236640
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Accepted into hardy-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
iSCSI in
Public bug reported:
Binary package hint: winbind
Winbind has lost LDAP support because ldap.so is missing from
/usr/lib/samba/idmap/ldap.so
I discovered this when trying to use winbind to map to LDAP:
/var/log/samba/log.winbind-idmap reported the following:
[2009/07/08 17:10:26, 5] lib/module
I do not have the problem Kevin reports above; iscsi=true works just
fine for me. I tested using the karmic server CD image dated
08-Jul-2009 10:32 from the same location he does.
I am pleased to report the iSCSI installer support works just fine now for me.
The iSCSI dialog come up fine, the
** Attachment added: "debdiff for 8.3.2-1ubuntu1"
http://launchpadlibrarian.net/28822809/drbd-merge.debdiff
** Changed in: drbd8 (Ubuntu)
Importance: Undecided => Medium
** Changed in: drbd8 (Ubuntu)
Status: New => Confirmed
--
Please merge drbd8 2:8.3.2-1 (main) from Debian unsta
** Attachment added: "debdiff for 8.3.2-1ubuntu1"
http://launchpadlibrarian.net/28822687/drbd-merge.debdiff
** Attachment removed: "debdiff for 8.3.2-1ubuntu1"
http://launchpadlibrarian.net/28822687/drbd-merge.debdiff
** Summary changed:
- Please merge drbd8 2:8.3.2-1ubuntu1 (main) from D
Public bug reported:
Changes:
drbd8 (2:8.3.2-1ubuntu1) karmic; urgency=low
.
* Resync with Debian package, drop all previous Ubuntu changes
* Closes: LP #397143
.
[ New Ubuntu packaging ]
.
* debian/control:
- replace Maintainer field
- remove dpatch from Build-Depends
No information available that would let us address this, and no other
reports of uninstallability. Closing.
** Changed in: samba (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: samba (Ubuntu)
Assignee: 3n!Gma (wm3) => (unassigned)
--
Could not install 'smbclient'
https://b
I just acquired karmic-server-i386.iso from http://cdimage.ubuntu.com
/ubuntu-server/daily/current/ and booted with the iscsi=true commandline
option. I was not prompted for any iscsi information, nor is "Configure
iSCSI" present in the installer main menu.
--
iSCSI install fails under hardy
http
** Branch linked: lp:ubuntu/gutsy-updates/gnutls13
** Branch linked: lp:~ubuntu-branches/ubuntu/gutsy/gnutls13/gutsy-
proposed
** Branch linked: lp:~ubuntu-branches/ubuntu/hardy/gnutls13/hardy-
security
** Branch linked: lp:~ubuntu-branches/ubuntu/hardy/gnutls13/hardy-
proposed
--
gnutls regre
Etienne,
I'm preparing an SRU upload of open-iscsi for hardy including the latest
fixes that you've indicated, which I'll be uploading today. In the
meantime, would it be possible for you to do a full install test with
the latest karmic daily, which includes the fixes from open-iscsi
2.0.870.1-0u
dnsmasq takes care of so many headaches for a small network, this
problem was really killing me since firestarter is probably the best gui
front-end to iptables I've found.
But the above problem was plaguing me and the fix to user-pre above
didn't seem to help.
In case anyone does what I did, I w
This bug was fixed in the package gnutls13 - 2.0.4-1ubuntu2.5
---
gnutls13 (2.0.4-1ubuntu2.5) hardy-security; urgency=low
* Fix for certificate chain regressions introduced by fixes for
CVE-2008-4989
* debian/patches/91_CVE-2008-4989.diff: updated to upstream's final
2.4.2
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28800437/Dependencies.txt
** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/28800438/DpkgTerminalLog.txt
--
package samba-common 2:3.3.2-1ubuntu3.1 failed to install/upgrade: Unterprozess
post-in
Public bug reported:
Binary package hint: samba
update fail
ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: Unterprozess post-installation script gab den Fehlerwert 1 zurück
Package: samba-common 2:3.3.2-1ubuntu3.1
SourcePackage: samba
Title: package samba-commo
For the openldap/hardy SRU:
I have:
(1) reproduced the acceptance of the v1 certificates as
outlined in Mathias' test case by the ldap clients with ldap
2.4.9-0ubuntu0.8.04.2 and gnutls13 2.0.4-1ubuntu2.
(2) reproduced the rejection of v1 certificates by the ldap clients
wi
For the gnutls/hardy SRU:
I have reproduced the acceptance of rsa/md2 v1 certificates by the
version of gnutls13 in hardy-updates, 2.0.4-1ubuntu2.3, and can confirm
that the version of gnutls13 in hardy-proposed does not accept rsa/md2
certificates. I have added a testcase for this situation in th
Please add a test case for SRU verification.
--
[SRU] pam_winbind Use incorrect value for password expiry calculation
https://bugs.launchpad.net/bugs/393450
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-serve
Accepted samba into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: samba (Ubuntu Jaunty)
32 matches
Mail list logo
