This bug was not fixed, the part that needs fixing is the 'can_connect'
function
Patch attached.
** Attachment added: "repatch"
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/732953/+attachment/2081311/+files/repatch
--
You received this bug notification because you are a member of
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/768753
Title:
package samba (not installed) failed to install/upgrade: arquivo tar
do sistema de arquivos corrompido - arquivo de pacot
Public bug reported:
Binary package hint: samba
When installing on my system
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: samba (not installed)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Apr 22 00:04:52 2
this is no longer an issue i notice samba was working about 2 weeks
ago when i thought I was checking it in vain guess this must have been
resolved by an update
On Mon, Jan 24, 2011 at 7:46 AM, Chuck Short wrote:
> Thank you for taking the time to report this bug and helping to make Ubuntu
> bet
Public bug reported:
cyrus-sasl2-heimdal 2.1.23.dfsg1-5.1ubuntu1 is uninstallable with cyrus-
sasl2 2.1.23.dfsg1-5ubuntu3, and ftbfs due to heimdal changes, from what
I can see. I suspect the only way forward on this is to get cyrus-sasl2
2.1.23.dfsg1-6 (or, likely, newer) into natty which merges
Ok so after looking at it now, it seems that the issue is
self.process_repos() when issuing the following command:
cobbler import --name=natty-i386 --path=/mnt --breed=ubuntu --os-
version=natty
Apparently there's some kind of incompatibilities as there are two
functions with the same name. One d
** Changed in: cobbler (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cobbler in Ubuntu.
https://bugs.launchpad.net/bugs/765224
Title:
import from mini.iso fails
*sigh* Three years after this was first reported, another round of
server installs, and still no package.
Ondrej, There are applications that use php embed other than phc -- I
need it for plphp -- php for postgresql databases.
Out of curiousity... since I'm not a package maintainer, how much extr
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/768506
Title:
CIFS VFS Server is slowing down shutdown
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify se
Public bug reported:
Binary package hint: samba
Since I upgraded to Natty, the computer takes a very long time to shut
down (approximately 5 minutes). I made a movie from the shutdown
messages and I think the CIFS server is not stopped correctly. I see the
following message (for a split second):
Sounds good, for d-i not having the repo present is non-fatal (it'll
just grab packages from the internet), for Anaconda based distros (RH,
Fedora etc) I think it requires the complete tree.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hmmm - not sure what happened during the installation but your system
appears to be running the most up-to-date version of ntp and is
correctly sync'ed with two time servers.
Its possible that we might find more information in
/var/log/apt/term.log; please could you attach this file to this bug
re
What appears to be is that the import expects the .disk folder
regardless of whether you are specifying the distro or not. Since bug
#765254 won't be fixed, I guess that the best approach would be to patch
the current code to ignore the check of the .disk folder (or try to
obtain the information fr
Do not worry I provide the output of the commands:
# apt-cache policy ntp
ntp:
Instalados: 1:4.2.6.p2+dfsg-1ubuntu5
Candidato: 1:4.2.6.p2+dfsg-1ubuntu5
Tabla de versión:
*** 1:4.2.6.p2+dfsg-1ubuntu5 0
500 http://mx.archive.ubuntu.com/ubuntu/ natty/main i386 Packages
100 /v
In fact, it's exactly that.
from: cobbler/modules/manage_import_debian_ubuntu.py
def repo_finder(self, distros_added):
for distro in distros_added:
self.logger.info("traversing distro %s" % distro.name)
# FIXME : Shouldn't decide this the value of self.netwo
If I specify a os-version it imports the distro and adds distro and profiles to
cobbler correctly, however I get a nice traceback.
There must be some code expecting the dists dir somewhere that relies on this
for a repo?
Installing after is just fine, although you need to link your profile to a s
This is a problem with the content of the branch, as created by a
person, not anything Launchpad did.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: bzr-builder
Status: New => Invalid
** Changed in: launchpad
Status: New => Invalid
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash, as I
call it, on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6
package.
Will still be monitoring this, and may even install it on a few more machines,
today.
--
You received this bug notification becaus
*** This bug is a duplicate of bug 736757 ***
https://bugs.launchpad.net/bugs/736757
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of
the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package.
Will still be monitoring this, and may even install it on
It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of
the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package.
This particular "rpc_pipe_np_smb_conn" crash, as I call it, is covered here
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/753330.
So once t
Sorry, I was out of the office for a while and was not able to handle
this request
I used elasticfox, and yes added ssh port:
sysadmin@europe:~$ euca-describe-groups
GROUP build build Build group
PERMISSION build build ALLOWS icmp-1 -1 FROMCIDR
0.0.0.0/3
Hi Guys.
I updated from Maverick, I believe it was working beforehand. But there
is a chance I had chosen to ignore the error before this recent upgrade.
The results of running apt-cache policy eucalyptus-common:
eucalyptus-common:
Installed: 2.0.1+bzr1256-0ubuntu4
Candidate: 2.0.1+bzr1256-0
Hi Carlos
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
As per Torsten's comment it would be great to see the output of euca-
describe-groups for the security group associated with the instances you
are trying to access.
Thanks
** Changed in: eucalyptus (Ub
Thank your information~
2011/4/20 Scott Kitterman
> This is not a package bug. The invalid hostname checks are there by
> design and will stay.
>
> ** Changed in: postfix (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are a direct subscrib
it would be useful to understand whether the eucalyptus components that
you have installed on the system where functional before you upgraded.
Please could you also validate whether eucalyptus-common is installed
with the following command:
apt-cache policy eucalyptus-common
Thanks
--
You rece
Hi Ben
Did you upgrade to natty from lucid of maverick? Its not clear from the
logs and the error messages relate to upgrading of the database that
supports eucalyptus which should only occur when upgrading from lucid.
Thanks
--
You received this bug notification because you are a member of Ub
*** This bug is a duplicate of bug 736757 ***
https://bugs.launchpad.net/bugs/736757
Marking as duplicate of bug 736757 after feedback on lucid -proposed
package indicated that issue was resolved.
** This bug has been marked a duplicate of bug 736757
[SRU] PANIC (pid 18442): internal error
Setting importance to medium as this as a moderate impact on a core
application with no easy workaround.
** Changed in: samba (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
** Changed in: samba (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/765249
Title:
tarmode exclude no longer working
--
Ubuntu-server-bug
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/765249
Title:
tarmode exclude no longer working
--
Ubuntu-server-bugs ma
I was able to confirm the same behaviour in smbclient on lucid, maverick
and natty installations.
Inclusion seems to work OK - exclusion does not.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.
** Bug watch added: Debian Bug tracker #373850
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373850
** Also affects: samba (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373850
Importance: Unknown
Status: Unknown
** Bug watch added: Samba Bugzilla #4734
https:
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It seems that there was an error caused by a corrupted archive. Please
execute the following commands, as it will clear your package cache, in
a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get
Error from log:
Preparing to replace smbclient 2:3.5.8~dfsg-1ubuntu1 (using
.../smbclient_2%3a3.5.8~dfsg-1ubuntu2_amd64.deb) ...
Unpacking replacement smbclient ...
dpkg-deb (subprocess): data: internal gzip read error: ': data error'
dpkg-deb: error: subprocess returned error exit status 2
dpkg
** Attachment added: "xorg_fixup.log"
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/766983/+attachment/2078975/+files/xorg_fixup.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.laun
There is also apt-term.log but it is 3.7mb seems a bit large to be
uploading here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/766983
Title:
package eucalyptus-java-common 2.0
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/766983/+attachment/2078974/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "main.log"
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/766983/+attachment/2078973/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bu
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/766983/+attachment/2078972/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/766983/+attachment/2078966/+files/apt.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It would appear that your installation is not configured with a valid
hostname - you will need to resolve this before postfix will install
correctly.
You can do this either by editing /etc/postfix/main.cf to set t
Error from log:
Setting up postfix (2.6.5-3ubuntu0.1) ...
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).
After modifying main.cf, be sure to run '/etc/init.d/postfix re
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It would appear that you installation is not configured with a valid
hostname (see error message in comment #2).
You will need to resolve this issue before postfix will startup
correctly. You can do this by editi
Error from log:
Postfix configuration was not changed. If you need to make changes, edit
/etc/postfix/main.cf (and others) as needed. To view Postfix configuration
values, see postconf(1).
After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.
Running newaliases
newaliases: warn
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It would appear that something went wrong when you upgraded to the
latest development release; as a result the eucalyptus-java-common
package is not installed correctly and hence you keep getting this error
message
Error from log:
Setting up eucalyptus-java-common (2.0.1+bzr1256-0ubuntu4) ...
stop: Unknown instance:
eucalyptus stop/waiting
# UPGRADE INFORMATION
#
# Old Version: 1.6.2
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Unfortunately there is not much information to help diagnose what went
wrong in the attached logs.
Please could you run the following commands in a terminal and attach the
output of each to this bug report:
apt-
Hi Lupe,
since we now have an apcsmart maintainer, I'm forwarding this issue to
him.
@Michal: could you please have a look at this issue [1], and give us your
feeling?
cheers,
Arnaud
--
[1] https://bugs.launchpad.net/bugs/535583
2011/2/15 Lupe Christoph
> On Tuesday, 2011-02-15 at 13:16:58 -0
This should never have been marked Incomplete in the first place.
** Changed in: openssh (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/67
49 matches
Mail list logo
