FYI, my original Debian PR was just merged into the upstream 1.26-wip
branch: https://salsa.debian.org/nginx-team/nginx/-/merge_requests/73
Presumably this will work its way down here at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Mitchell,
Well, I'm using 1.25 ubuntu package directly from the nginx repo, and
this patch works just fine with that – it's only a simple addition to a
UFW config file, not complicated.
You probably know this, but nginx's versioning system is slightly weird:
even numbers (like 1.24) are
Public bug reported:
New feature, not a bug
nginx 1.25 adds support for QUIC + HTTP/3, which is typically deployed over UDP
port 443. This option is not included in the provided UFW applications, so this
PR adds it. Note that it is not done as a standalone app (i.e. with only QUIC)
because
I'm seeing this in Vivid -> Wily too, but in a Xen VM, not an LXC
container. None of the above suggestions worked, it logs the same errors
as Serge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this in Vivid -> Wily too, but in a Xen VM, not an LXC
container. None of the above suggestions worked, it logs the same errors
as Serge.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
For password hashing, bcrypt *is* better, by design. There's absolutely
no ambiguity here, the consensus is fully in favour of bcrypt. Hashes
like SHA512 are general purpose, designed to run really fast, whereas
bcrypt is explicitly for secure hashing and is deliberately, tuneably
slow. There are
Please ignore my last comment. bcrypt is undoubtedly better than a
single round of SHA512 as a password hash (what I was on about), but
SHA512 is not the same thing as the multiple rounds used in SHA512-CRYPT
that's in libc and in Ulrich's paper.
--
You received this bug notification because you
As far as I've been able to tell, the PHP mysqlnd extension provides a
sort of compatibility layer that gets used by both the mysql and mysqli
extensions, the net result being that mysqlnd is no use on its own, and
can only be used in conjunction with the mysql or mysqli extensions.
Thus the
Public bug reported:
==
# aptitude install phpmyadmin
The following NEW packages will be installed:
dbconfig-common{a} php5-mysql{ab} phpmyadmin
0 packages upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 5,879 kB of archives. After unpacking 17.6
History repeating - 3 years later and I'm seeing exactly this problem in
a new 12.04 install! I've got a glusterFS volume that mounts via NFS -
it shows in /proc/mounts but not df or mount output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm seeing this same thing in a VM, though significantly worse. This
could be down to the VM not having real hardware access, but it's acting
as others describe - all the text looks ok apart from the menu bar. In
my case I'm getting rough green fringes where shadows would be. Screen
shot shows it
I don't know why this was marked as invalid. I was requesting the
backport for Lucid (hence my reference to 4.11). I know it doesn't apply
to Maverick and Natty, but it DOES apply to Lucid, which is still in
LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Well I didn't post it as an SRU - I'd not heard of them until my
original backport request was changed into one. I'm not in a position to
supply or recommend a particular fix or patch for this, other than it
seems to need to be version 0.6.3-3.2 or later, so I can't sensibly do
step 3.
I've asked
OK, I have feedback from my ISP. Their kernel does not include dmi, on
the basis that it's been deprecated since 2005!
They've worked around this problem by installing the natty libvirt
package which does not suffer this problem.
I guess a backport request would be appropriate.
Sorry to trouble
OK, I have feedback from my ISP. Their kernel does not include dmi, on
the basis that it's been deprecated since 2005!
They've worked around this problem by installing the natty libvirt
package which does not suffer this problem.
I guess a backport request would be appropriate.
Sorry to trouble
Apport says this:
Package libvirt not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.
Press any key to continue...
No pending crash reports. Try --help for more information.
What it's saying is technically correct because there is no
That search finds nothing.
The kernel is supplied and configured by my ISP - the stock kernel is
not stable - I've asked them to contribute to this report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Apport says this:
Package libvirt not installed and no hook available, ignoring
*** Updating problem report
No additional information collected.
Press any key to continue...
No pending crash reports. Try --help for more information.
What it's saying is technically correct because there is no
That search finds nothing.
The kernel is supplied and configured by my ISP - the stock kernel is
not stable - I've asked them to contribute to this report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm attempting to install kvm-qemu with libvirt on Ubuntu Lucid amd64 on
a quad-core i7. It's a brand-new clean install, fully updated and
rebooted. I've been following the Ubuntu KVM docs (from
https://help.ubuntu.com/community/KVM/Installation), but I'm getting
this
That doesn't really work since it collects info only on libvert itself,
which is a virtual package and returns nothing. I don't know quite which
bit of libvert this should be attached to - maybe libvert-bin?
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
I'm attempting to install kvm-qemu with libvirt on Ubuntu Lucid amd64 on
a quad-core i7. It's a brand-new clean install, fully updated and
rebooted. I've been following the Ubuntu KVM docs (from
https://help.ubuntu.com/community/KVM/Installation), but I'm getting
this
That doesn't really work since it collects info only on libvert itself,
which is a virtual package and returns nothing. I don't know quite which
bit of libvert this should be attached to - maybe libvert-bin?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yup, it's a bug. It was fixed in Debian last October and only made it
into aptitude 0.6.3-3.2 in Natty, so both Lucid and Maverick suffer from
this problem:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557580
I filed a backport request: https://bugs.launchpad.net/lucid-
backports/+bug/795602
I'm running the updated upstart and plymouth-free grub2 config on two newly
installed amd64 boxes (bog-standard Dell 2950s) with today's 2.6.32-24-server
kernel, and I'm still finding a whole bunch of services fail to start (cron,
apache2, mysql, fail2ban, sysstat, postfix, openntpd,
Public bug reported:
Binary package hint: pigz
Given pigz' aim to replace gzip, it should provide complete
command-compatibility with gzip, so that the only change necessary change in
shell scripts should be changing /bin/gzip to /usr/bin/pigz.
The help page for pigz mentions an --rsyncable /
To reproduce the error:
touch blah
pigz -R blah
pigz abort: invalid option: rsyncable not implemented yet: -R
--
--rsyncable option breaks scripts
https://bugs.launchpad.net/bugs/632462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This still happens on Lucid, but there's a less complicated fix for
this. The status moule is normally enabled with `a2enmod status`. All
that seems to be required to fix munin after that is to add
'ExtendedStatus On' to /etc/apache2/mods-enabled/status.conf so it looks
like this:
IfModule
This still happens on Lucid, but there's a less complicated fix for
this. The status moule is normally enabled with `a2enmod status`. All
that seems to be required to fix munin after that is to add
'ExtendedStatus On' to /etc/apache2/mods-enabled/status.conf so it looks
like this:
IfModule
Public bug reported:
Version 0.4+dfsg-1 installed on Lucid x64.
Emits a warning when run:
#pyfiglet hello
/usr/lib/pymodules/python2.6/pyfiglet.py:193: DeprecationWarning:
object.__init__() takes no parameters
str.__init__(self, *args, **kwargs)
╻ ╻┏━╸╻ ╻ ┏━┓
┣━┫┣╸ ┃ ┃ ┃ ┃
╹
FYI, I supplied a VM I built to Soren off-site. He found it ran OK. I
asked for a VM built using the same config on a known-good server that I
could try. So far the story is:
VMs I build won't run poperly on this server
VMs built elsewhere (using different config) do run on this server
VMs I
FYI, I supplied a VM I built to Soren off-site. He found it ran OK. I
asked for a VM built using the same config on a known-good server that I
could try. So far the story is:
VMs I build won't run poperly on this server
VMs built elsewhere (using different config) do run on this server
VMs I
Here's the debug log. I see a lot of debug-level notices about missing
methods, but it doesn't seem to be leading to any actual errors, like
this:
2010-05-06 01:03:47,288 DEBUG : Calling install_bootloader method in
VMBuilder.plugins.libvirt plugin.
2010-05-06 01:03:47,289 DEBUG : No such
Here's the debug log. I see a lot of debug-level notices about missing
methods, but it doesn't seem to be leading to any actual errors, like
this:
2010-05-06 01:03:47,288 DEBUG : Calling install_bootloader method in
VMBuilder.plugins.libvirt plugin.
2010-05-06 01:03:47,289 DEBUG : No such
** Attachment added: Screen shot 2010-05-05 at 16.38.55.png
http://launchpadlibrarian.net/47877692/Screen%20shot%202010-05-05%20at%2016.38.55.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
Public bug reported:
I'm running vmbuilder 0.12.3-0ubuntu1 on Lucid server. vmbuilder
apparently runs and assembles a machine image without error, but the
resulting VM just doesn't run properly, going extremely slowly (about 50
mins to reach a login prompt, though login isn't possible as it
** Attachment added: Screen shot 2010-05-05 at 16.36.51.png
http://launchpadlibrarian.net/47877680/Screen%20shot%202010-05-05%20at%2016.36.51.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
I'd guess so since kvm insists on running as root! I've had the same problem
with the vm folder and image owned by me and root, so I guess it's not that.
Do you have a known-good config I can use to generate a VM image to test with,
possibly compare it with the image created on a machine that
If I run run.sh without sudo it says this:
open /dev/kvm: Permission denied
Could not initialize KVM, will disable KVM support
That said, it does open a qemu window, but it shows the same errors as
previously reported.
Re ownership, I've tried running with the folder owned by me, and
changed it
Public bug reported:
I'm running vmbuilder 0.12.3-0ubuntu1 on Lucid server. vmbuilder
apparently runs and assembles a machine image without error, but the
resulting VM just doesn't run properly, going extremely slowly (about 50
mins to reach a login prompt, though login isn't possible as it
** Attachment added: Screen shot 2010-05-05 at 16.36.51.png
http://launchpadlibrarian.net/47877680/Screen%20shot%202010-05-05%20at%2016.36.51.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
** Attachment added: Screen shot 2010-05-05 at 16.38.55.png
http://launchpadlibrarian.net/47877692/Screen%20shot%202010-05-05%20at%2016.38.55.png
--
VMs built with vm-builder won't run
https://bugs.launchpad.net/bugs/575839
You received this bug notification because you are a member of
I'd guess so since kvm insists on running as root! I've had the same problem
with the vm folder and image owned by me and root, so I guess it's not that.
Do you have a known-good config I can use to generate a VM image to test with,
possibly compare it with the image created on a machine that
If I run run.sh without sudo it says this:
open /dev/kvm: Permission denied
Could not initialize KVM, will disable KVM support
That said, it does open a qemu window, but it shows the same errors as
previously reported.
Re ownership, I've tried running with the folder owned by me, and
changed it
I managed to find a KVM appliance image (there don't seem to be many around)
here:
http://ica-atom.org/docs/index.php?title=ICA-AtoM_virtual_appliance
This VM works with respectable performance and no errors on my server, so it
looks like kvm is in the clear. The only thing that was different in
I'd hope not, since it more or less renders Lucid's entire headline
cloud offering useless...
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I'd hope not, since it more or less renders Lucid's entire headline
cloud offering useless...
--
--firstboot option broken in 0.12.2-0ubuntu3
https://bugs.launchpad.net/bugs/536942
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Sorry I didn't see your question earlier.
I'm now running the release version of 10.04:
Linux 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64
GNU/Linux
This particular machine isn't very high powered, but it should be at least
usable. It has a single quad-core L5320 Xeon
There are two files in there. One called ubuntu.xml that refers to an image
file created in a folder called ubuntu-kvm (i.e. a default, as you suspected),
the other called vm1.xml, which is what I specified as my hostname.
I'm also curious that that file is in the libvirt folder instead of
There are two files in there. One called ubuntu.xml that refers to an image
file created in a folder called ubuntu-kvm (i.e. a default, as you suspected),
the other called vm1.xml, which is what I specified as my hostname.
I'm also curious that that file is in the libvirt folder instead of
I've now tried this without the -o option (having spotted the
self.vm.overwrite is the root of the problem), but that didn't make any
difference. Any chance of getting some attention to this as it's a
complete showstopper for me. It means my entire UEC / JeOS
virtualization plans are on hold.
Yay! That did it! I added a --hostname and it just worked, so thanks very much.
I don't think it's to do with whether a VM already exists as I have none in my
folder and have been wiping /tmp files between each build (because it doesn't
clean up after dying). In my case it should have nothing to
Public bug reported:
This is just a small feature request. While vmbuilder is running, it
constructs the new VM in /tmp under a randomly generated folder name
like 'tmpkJv90L'. When it's finished, it moves the completed image file
to the location given by the --dest option, however, it retains
I'm wary of making changes there as that page is for the older shell
script version of vmbuilder and I don't know if the same things apply -
I don't want to break things for Intrepid users just because Lucid is
different.
I also noticed that hostname is missing from the man page too.
I'm also
Yay! That did it! I added a --hostname and it just worked, so thanks very much.
I don't think it's to do with whether a VM already exists as I have none in my
folder and have been wiping /tmp files between each build (because it doesn't
clean up after dying). In my case it should have nothing to
Public bug reported:
This is just a small feature request. While vmbuilder is running, it
constructs the new VM in /tmp under a randomly generated folder name
like 'tmpkJv90L'. When it's finished, it moves the completed image file
to the location given by the --dest option, however, it retains
Public bug reported:
Binary package hint: ubuntu-docs
This is for this page: http://doc.ubuntu.com/ubuntu/serverguide/C/jeos-
and-vmbuilder.html
This guide omits a description of the --hostname option, and vmbuilder
(on Lucid) won't work without it (see bug 562189), so NONE of the
examples in
I'm wary of making changes there as that page is for the older shell
script version of vmbuilder and I don't know if the same things apply -
I don't want to break things for Intrepid users just because Lucid is
different.
I also noticed that hostname is missing from the man page too.
I'm also
I've now tried this without the -o option (having spotted the
self.vm.overwrite is the root of the problem), but that didn't make any
difference. Any chance of getting some attention to this as it's a
complete showstopper for me. It means my entire UEC / JeOS
virtualization plans are on hold.
Indeed - this went away when I removed the proxy option, thanks for the
pointer. The proxy log shows timeouts from the repo.
Now I'm stuck with bug 562189 again.
--
vm-builder fails to resolve package dependency in vanilla system
https://bugs.launchpad.net/bugs/562575
You received this bug
Still there with libvirt 0.7.5-5ubuntu25
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
Indeed - this went away when I removed the proxy option, thanks for the
pointer. The proxy log shows timeouts from the repo.
Now I'm stuck with bug 562189 again.
--
vm-builder fails to resolve package dependency in vanilla system
https://bugs.launchpad.net/bugs/562575
You received this bug
Still there with libvirt 0.7.5-5ubuntu25
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Still present in Lucid:
dpkg-reconfigure unattended-upgrades
(say yes)
update-rc.d: warning: unattended-upgrades start runlevel arguments (none) do
not match LSB Default-Start values (0 6)
update-rc.d: warning: unattended-upgrades stop runlevel arguments (0 6) do not
match LSB Default-Stop
ok, after a full-upgrade and a reboot before building a vm, I'm still
getting similar errors, however, it seems to be intermittent - I did one
build that was chock-full of dependency failures (in debootstrap.log),
then did another one which didn't but had other problems, though missing
packages
ok, after a full-upgrade and a reboot before building a vm, I'm still
getting similar errors, however, it seems to be intermittent - I did one
build that was chock-full of dependency failures (in debootstrap.log),
then did another one which didn't but had other problems, though missing
packages
Unfortunately it was just hiding, and it's back again with libvirt
0.7.5-5ubuntu23. Same config, same error.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which
Still there with libvirt 0.7.5-5ubuntu24.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
--
Ubuntu-server-bugs
Unfortunately it was just hiding, and it's back again with libvirt
0.7.5-5ubuntu23. Same config, same error.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still there with libvirt 0.7.5-5ubuntu24.
--
AttributeError: 'Libvirt' object has no attribute 'vm'
https://bugs.launchpad.net/bugs/562189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Running vmbuilder with this command:
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
--pass default \
--ip 192.168.176.100 \
--mirror
I noticed that libvirt got updated to 0.7.5-5ubuntu22 today, and it's
possible that this bug has been fixed by it, however, I'm not sure as
I've got another bug instead that may just be obscuring it...
--
AttributeError: 'Libvirt' object has no attribute 'vm'
Public bug reported:
Using this vmbuilder command (note no additional packages requested,
just creating a completely vanilla system):
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
Public bug reported:
Running vmbuilder with this command:
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
--pass default \
--ip 192.168.176.100 \
--mirror
I noticed that libvirt got updated to 0.7.5-5ubuntu22 today, and it's
possible that this bug has been fixed by it, however, I'm not sure as
I've got another bug instead that may just be obscuring it...
--
AttributeError: 'Libvirt' object has no attribute 'vm'
Public bug reported:
Using this vmbuilder command (note no additional packages requested,
just creating a completely vanilla system):
vmbuilder kvm ubuntu \
--suite lucid \
--flavour virtual \
--arch amd64 \
-o \
--libvirt qemu:///system \
--part vmbuilder.partition \
--user user \
--name user \
I'm getting this on 10.04 beta2 with 2.6.32-19-virtual (in the VM, built
with vmbuilder) and 2.6.32-19-server on the host on boot of a VM,
rendering virtualization completely inoperable, 100% failure rate. I'm
running qemu-kvm 0.12.3+noroms-0ubuntu5
--
Virtual machine soft lockup - CPU gets
Public bug reported:
Binary package hint: ubuntu-docs
On this page: http://doc.ubuntu.com/ubuntu/serverguide/C/jeos-and-
vmbuilder.html there's this example:
sudo vmbuilder kvm ubuntu --suite lucid --flavour virtual --arch i386 -o \
--libvirt qemu:///system --ip 192.168.0.100 --part
*** This bug is a duplicate of bug 536942 ***
https://bugs.launchpad.net/bugs/536942
** This bug has been marked a duplicate of bug 536942
--firstboot option broken in 0.12.2-0ubuntu3
--
vmbuilder: error: no such option: --firstboot
https://bugs.launchpad.net/bugs/550687
You received
*** This bug is a duplicate of bug 536942 ***
https://bugs.launchpad.net/bugs/536942
** This bug has been marked a duplicate of bug 536942
--firstboot option broken in 0.12.2-0ubuntu3
--
vmbuilder: error: no such option: --firstboot
https://bugs.launchpad.net/bugs/550687
You received
This is still happening for me in Jaunty. Seems that there's no
workaround in the installer as the busybox consoles don't seem to know
what xfs_freeze is.
--
grub-install hangs with xfs root/boot
https://bugs.launchpad.net/bugs/8058
You received this bug notification because you are a member of
I've run into what Roland is describing, and I quite agree that the
status output (or perhaps another command like 'ufw rules') should match
input commands. I once set a rule that was wrong and it took me ages to
figure out exactly the right syntax to remove it - it should not even be
necessary
** Also affects: trac (Ubuntu)
Importance: Undecided
Status: New
--
python-pysqlite2 version clash with libsqlite3 on dapper
https://bugs.launchpad.net/bugs/148047
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
python 2.5.1, libapache2-mod-python 3.2.10, python-pysqlite2 2.3.2-1,
apache2 2.2.3-3.2build1, trac 0.10.3-1.
Using all standard ubuntu packages, nothing odd. Hitting trac's start
page gives an immediate apache2 segfault which appears to be in python-
pysqlite2. I also tried
** Also affects: trac (Ubuntu)
Importance: Undecided
Status: New
--
Segfault/double-free crash in python-pysqlite2 in apache2
https://bugs.launchpad.net/bugs/152129
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: python-pysqlite2
Until recently I had a working trac install on dapper LTS. trac depends
upon python-pysqlite2, which in turn depends on libsqlite3. It appears
that in some recent update, python-pysqlite2 was built against a
different and incompatible
86 matches
Mail list logo
