Public bug reported:
Binary package hint: postfix
Release information:
Description:Ubuntu hardy (development branch)
Release:8.04
Package information:
postfix:
Installato: 2.5.1-2
Candidato: 2.5.1-2
Tabella versione:
*** 2.5.1-2 0
500 http://it.archive.ubuntu.com
Public bug reported:
I was upgrading from natty to oneiric
ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: samba 2:3.5.8~dfsg-1ubuntu2.3
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion:
--
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/876003
Title:
package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade:
ErrorMessage: package samba is not ready for
Please find attached a diff for fixing the bug.
This patch introduces the *lxc-ip* Python script, initially developed in
lp:lpsetup, and used to retrieve the ip address of a running container.
It also updates *lxc-start-ephemeral* to use lxc-ip and an increased number of
connection retries.
The
Is this fixed in ubuntu 10.04.3?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/350936
Title:
Should shut down domains on system shutdown
To manage notifications about this bug go to:
As a further note, Squid 2.6 is not supported anymore by the Squid developers;
the currently supported versions are 2.7.STABLE5 and 3.0.STABLE11.
If recompilation from source, we recommend to choose one of the two - which one
depends on the needed features.
See
Had the same issue and a debugging session demonstrated that the problem occurs
while marshalling the environInfo management-certificate setting. It ended up I
was using the wrong path to the certificate (management-certificate-path
pointed to the cer file rather than the pem file).
I'd suggest
Don't think so. It's part of the independence of libvirt from the the
actual virtualization technology (KVM, ...) to permit updates without
shutdown of guests.
2010/11/4 Valentijn Sessink valent...@sessink.nl:
Hmm. If libvirt shuts down the virtual machines it monitors, then these
virtual
2010/6/24 Soren Hansen so...@ubuntu.com:
why does libvirt-bin still stop before the libvirt-shutdown-guests job
has finished the script?
Good question. Upstart shouldn't be killing it, but something else
might. I can't imagine what, though.
I'm not sure Upstart isn't supposed to kill them.
I have seen the commit that implements this functionality and it's, as
usual, a sysvinit script. Unfortunately, I think this is a use case
where upstart can't do anything yet and the only solution (without
moving back to a sysvinit script) is doing an ugly workaround in
/etc/init.d/sendsigs. I've
Public bug reported:
Binary package hint: bacula
Ubuntu 10.04
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: bacula 5.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
** Attachment added: AptOrdering.txt
https://bugs.launchpad.net/bugs/636897/+attachment/1576898/+files/AptOrdering.txt
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/636897/+attachment/1576899/+files/Dependencies.txt
** Attachment added: Df.txt
2010/9/17 Martin Pitt martin.p...@ubuntu.com:
cups (1.4.4-5) unstable; urgency=low
[ Martin Pitt ]
* ubuntu-upstart.dpatch: Drop the dependency on starting smbd, it causes
samba to hang on package upgrades or manual restarts. There doesn't seem
to be a good way to express this
2010/9/17 John Morrissey j...@horde.net:
The attached file updates libvirt-bin's upstart job to gracefully shut
down VMs when the system shuts down. You can alter the shutdown timeout
(SHUTDOWN_TIMEOUT, default: 300s) and list of virsh(1) URIs to use
(URIS, default: qemu:///system) in
Clap! :)
2010/9/29 Andy a...@xillean.com:
It is a dismal situation when at this point there is still no official simple
way from Canonical to
gracefully shutdown KVM VMs if the host has to go down for any reason such as
a UPS issued shutdown command.
--
Should shut down domains on system
I have the same problem !!!
lm sensor doesn't work !
I tried with grub with: GRUB_CMDLINE_LINUX=acpi_enforce_resources=lax
But with sudo update-grub2 i had this:
/etc/default/grub: 9: acpi_enforce_resources=lax: not found
--
lm-sensors don't work
https://bugs.launchpad.net/bugs/478762
You
Hello !
Today i solved in this way:
sudo gedit /etc/default/grub
and i modified the old string:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash
in
GRUB_CMDLINE_LINUX_DEFAULT=acpi_enforce_resources=lax quiet splash
Now it's all right !
But i hope that is being to solve in official way, beacuse many
What problems ?
I would know these problems, because if it can do me problem I edited the grub
as it was before. ;-)
Bye
Francesco bat
--
lm-sensors don't work
https://bugs.launchpad.net/bugs/478762
You received this bug notification because you are a member of Ubuntu
Server Team, which
In data 21 dicembre 2009 alle ore 23:25:33, Jeremy Nickurak
ubuntu-b...@trk.nickurak.ca ha scritto:
That's a work-around... but the warning would seem to suggest that this
isn't safe. Is there an API/ABI/socket/sysfile that we're supposed to
used? Until that's the case, this is a regression.
I'm using libvirt-bin 0.7.5-5ubuntu25 and the bug is still there. Is the
fix lost somewhere?
My /var/log/libvirt/qemu/storage.log have these lines:
usb_create: no bus specified, using usb.0 for usb-host
husb: open device 6.2
/dev/bus/usb/006/002: Permission denied
husb: open device 6.2
Just to confirm something is still not working for me:
$ sudo apt-cache showpkg libvirt-bin
Package: libvirt-bin
Versions:
0.7.5-5ubuntu25
Adding the generic (and unsafe) line:
/dev/bus/usb/*/[0-9]* rw,
to /etc/apparmor.d/abstractions/libvirt-qemu and reloading profiles
works for me so it
I used virt-manager:
domain type='kvm' id='5'
namestorage/name
uuid0175b337-5faf-42ba-d6a7-bb60ec8da4ad/uuid
memory1572864/memory
currentMemory1572864/currentMemory
vcpu1/vcpu
os
type arch='x86_64' machine='pc-0.12'hvm/type
boot dev='hd'/
/os
features
acpi/
apic/
Yes, that worked! :)
--
apparmor driver blocks access to hostdev and pcidev devices
https://bugs.launchpad.net/bugs/545795
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
CUPS starts after SAMBA; printers are not available
https://bugs.launchpad.net/bugs/494141
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
2 problems here:
- cups is still an old sysvinit script;
- samba is an upstart job but doesn't have any dependencies on cups.
Moreover I think it's the samba upstart job that should assert start
after cups, and not cups to worry about starting before samba. So for
sure this actually a deficiency
Just to be clear, what is exactly the cups bug (other than not being an
upstart job yet)? I don't know if upstart already have stanzas like
start before/after (because it's clear that samba is not really
dependent on cups, but if present cups should be started before samba),
but it seems more easy
Or maybe is a problem in cups not promptly giving a dynamic list of
printers available runtime? Sorry, but there were no explanation and I
was curious about this. :)
--
CUPS starts after SAMBA; printers are not available
https://bugs.launchpad.net/bugs/494141
You received this bug notification
I'm not sure it can be done hacking upstart job. When libvirt was a
sysvinit script in ubuntu 9.10, I used this [1] script adding it in
stop function. In Lucid, if I add the same script to /etc/init
/libvirt-bin.conf with the stanza:
pre-stop exec shut-guests.sh 21 /var/log/shut-guests.log
This
Workaround:
Add the lines:
/usr/local/bin/shut-guests.sh 21 /var/log/shut-guests.log
/sbin/initctl emit guests-shutted
just after do_stop() { in /etc/init.d/sendsings
*and* changing the line:
stop on (runlevel [!2345])
on file /etc/init/libvirt-bin.conf to:
stop on
2010/5/5 Soren Hansen so...@ubuntu.com:
It's important to remember that libvirt intentionally does not kill VM's
on termination. This enables us to upgrade libvirt without interruping
running VM's, so we want to only conditionally shut down VM's.
Correct.
What I've
done on one of my Hardy
2010/5/20 PryGuy p...@inbox.ru:
I'm all sorry, this was a mistake. I'm really surprised an ordinary user
can change it. Sorry again.
(OT)
Hehehe, actually Launchpad works better than others BTS because gives
more freedom to users. If you did a mistake, don't worry but be more
careful next time
We just released on PyPi the new 1.2.0 release of quickstart.
Juju core 1.17.2 introduced sudo support for local environments, which required
changes to how quickstart works: calling sudo is now handled by juju itself,
and for this reason quickstart no longer requires to request sudo privileges
We just released quickstart 1.3 implementing the --distro-only flag.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1273865
Title:
[MIR] juju-quickstart, python-jujuclient,
** Summary changed:
- [FFe] Upgrade juju-quickstart to new upstream release 1.2.0
+ [FFe] Upgrade juju-quickstart to new upstream release 1.3.0
** Description changed:
We just released on PyPi the new 1.2.0 release of quickstart.
Juju core 1.17.2 introduced sudo support for local
I attached a prototype for a possible fix.
It seems to work, containers addresses are now included in the mega-watcher for
machines.
The only issue, even after applying that patch, is that the NetworkScope for
LXC addresses is an empty string, while I expected it to be public, e.g.:
** Changed in: juju-quickstart (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does
** Changed in: juju-quickstart (Ubuntu)
Status: Fix Committed = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1301464
Title:
The mega-watcher for machines does
change in the list of dependencies.
The feature is properly tested (both unit tests and live tests in a real MAAS
controller).
Here is the changelog since 1.4.2:
juju-quickstart (1.4.4) trusty; urgency=low
* Support creating and using MAAS (Metal As A Service) environments.
-- Francesco
is properly tested (quickstart still have 100% unit tests
coverage).
Here is the full changelog:
juju-quickstart (1.4.3) trusty; urgency=low
* Support for overriding the Juju executable with the JUJU env var.
* Add support for Ubuntu 14.10 (utopic).
* Base dependencies update.
-- Francesco
Please also note that juju-quickstart is in unverse.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359944
Title:
[FFE] Update juju-quickstart to support MAAS as a
I forgot to mention that juju-quickstart is in universe.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1359938
Title:
[FFE] request to update juju-quickstart to support
Public bug reported:
At the system startup it appears. The problem should be in the Kernel,
which is not supported yet.
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: openvswitch-datapath-dkms 2.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux
If I understand this correctly, this seems to be an issue related to a backward
incompatible change in the Python websocket client library. Its API changed in
version 1.13, trusty has 1.12, vivid updated to 1.18 [1].
Basically they introduced SSL certs validation by default [2]. Quickstart
I am marking this bug as invalid, since (if I am correct) newer versions
of quickstart already fixed this bug: PPA users have been using python-
websocket 1.18 and quickstart for quite a while now. Please feel free to
reopen this if I am missing something.
** Changed in: juju-quickstart (Ubuntu)
Quickstart 2.0 includes functional tests.
In order to run them, some pre-requisites must be satisfied.
See
http://bazaar.launchpad.net/~juju-gui/juju-quickstart/trunk/view/head:/HACKING.rst#L70
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Juju Quickstart is deprecated and replaced by Juju 2.0 automatic credentials
gathering and native bundle support.
We are no longer actively developing quickstart and therefore we ask for the
package to be not included in xenial.
Thanks.
** Affects: juju-quickstart (Ubuntu)
I'm sorry if this is not the place to report this, but running localedef
into a lxc ubuntu container it's affecting quantal right now.
The log line is
[26775.302073] type=1400 audit(1353478924.553:73): apparmor=DENIED
operation=chmod info=Failed name lookup - deleted entry error=-2
parent=14028
47 matches
Mail list logo
