Is this fix going to make it into bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772921
Title:
freeipa web ui -- incorrect configuration for awesome fonts
To manage notifications about
This is still a problem in Ubuntu 18.04.
Note: systemd unit files provided by packages should not be modified by
the user after installation, instead systemd's drop-in feature should be
used.
The proper workaround for this bug is to create the file
Using Kubuntu 16.04 on a Thinkpad X240 with Intel graphics this problem
also causes Yakuake ("Quake-style terminal emulator based on KDE Konsole
technology") to remain invisible when activated. It still accepts input
and the window is in focus, it just is not visible.
Switching the compositor
We work around this problem by disabling the clock setup during
installation:
d-i clock-setup/utc boolean true
d-i time/zone string Europe/Vienna
d-i clock-setup/ntp boolean false
d-i clock-setup/ntp-server string pool.ntp.org
And after installation Puppet ensures chrony or ntpd are running.
--
Definitely still a problem with 16.04, especially with unattended
installs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558166
Title:
Xenial installer hangs for a long time with "Setting up the
Over a year later this problem still exists. It is impossible to run a
Postfix server that does (SSL/TLS secured) LDAP lookups on Ubuntu
14.04.3.
I wonder how is this not affecting more people?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Over a year later this problem still exists. It is impossible to run a
Postfix server that does (SSL/TLS secured) LDAP lookups on Ubuntu
14.04.3.
I wonder how is this not affecting more people?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
FWIW, I am content with the updated USN and agree with Won't Fix. Just
wanted to raise the issue here in case I am not the only one bitten by
this change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW, I am content with the updated USN and agree with Won't Fix. Just
wanted to raise the issue here in case I am not the only one bitten by
this change.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bsd-mailx in Ubuntu.
Bug against Bootmail is here:
https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696
What do you suggest instead?
I don't really have a suggestion and I am not disputing that this change
was necessary.
But the USN description doesn't even mention that specifying sendmail
options after
I have implemented the proposed fix in our infrastructure by having
Puppet modify the /usr/sbin/bootmail script and change the last line as
specified above to use the -a option for setting the From: header:
print_mail_text | sed -e s/[^[:print:]]//g | rootsign | mail -s
$subject -a From: Bootmail
Bug against Bootmail is here:
https://bugs.launchpad.net/ubuntu/+source/bootmail/+bug/1414696
What do you suggest instead?
I don't really have a suggestion and I am not disputing that this change
was necessary.
But the USN description doesn't even mention that specifying sendmail
options after
Public bug reported:
bsd-mailx recently had a security update that completely removes support
for specifying classic sendmail options after -- on the command line.
See http://changelogs.ubuntu.com/changelogs/pool/main/b/bsd-mailx/bsd-
mailx_8.1.2-0.2006cvs-1ubuntu0.1/changelog for
Public bug reported:
The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on
Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail
options after -- on the commandline.
This breaks any script that supplies classic sendmail options like -F or
-f on the mail commandline. A
Public bug reported:
The security update of bsd-mailx (8.1.2-0.2006cvs-1ubuntu0.1 on
Ubuntu 12.04) removes bsd-mailx's support for specifying sendmail
options after -- on the commandline.
This breaks any script that supplies classic sendmail options like -F or
-f on the mail commandline. A
After my last comment here over two years ago I haven't had the time and
resources to debug this any more than I already had at that point. We
have since switched to using unencrypted Libvirt connections
(qemu+tcp:///) which is good enough since all virtualisation hosts are
on a separate and
A possible workaround for this problem is to install an entropy
gathering daemon like haveged (apt-get install haveged) to keep
/dev/random supplied with entropy. Requires no additional configuration
and speeds things up tremendously.
--
You received this bug notification because you are a
Installing 3.14.1 as per comment #17 fixed these connectivity issues for
us as well, but it doesn't look like the 3.14.1 kernel made it anywhere
near the 14.04.1 release. There is also no mention of this or any
related bugs in
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.1.
Installing 3.14.1 as per comment #17 fixed these connectivity issues for
us as well, but it doesn't look like the 3.14.1 kernel made it anywhere
near the 14.04.1 release. There is also no mention of this or any
related bugs in
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/ChangeSummary/14.04.1.
Just so that this doesn't get overlooked: I have this problem with
Apache Directory Studio (an Eclipse RCP application) running on Kubuntu
13.10 using KDE 4.12 and the oxygen-gtk engine. It is definitely not
related to Unity directly, though I don't know how many libraries or how
much code
@auspex: the GTK2_RC_FILES workaround should work for this bug, how are
you calling it? Should look like this:
$ GTK2_RC_FILES=/usr/share/themes/Raleigh/gtk-2.0/gtkrc
/path/to/eclipse/or/whatever
Alternatively you can set the GTK2 theme to Raleigh globally and try
starting your crashing
Same here. Freshly updated from Kubuntu 13.04 to Kubuntu 13.10.
Eclipse, or in my case Apache Directory Studio, which is basically
Eclipse, can't be started as the JVM segfaults after a few seconds.
Happens with both OpenJDK 7 and Oracle Java 7.
Changing GTK2 theme to Raleigh makes Eclipse
Just about the same here on a few generic Ubuntu 12.04.2 VMs (using
KVM). Followed the documentation on
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe and
https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html which
basically says: install linux-crashdump, reboot, check /proc/cmdline,
make
Very interestingly, when setting `crashkernel=128M` instead of the
default `crashkernel=384M-2G:64M,2G-:128M`, crashing the machine works
correctly and also leaves a crashdump in /var/crash. Unfortunately
setting the crashkernel parameter requires editing /etc/grub.d/10_linux
directly and can not
Looking further this memory problem is already tracked in bug #785394,
untouched for almost two years now.
So this bug here should serve as a reminder that the official
documentation (https://help.ubuntu.com/lts/serverguide/kernel-crash-
dump.html) is wrong. It should at least contain links to
Public bug reported:
This bug has been reported and recently fixed in Debian
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684863) and discussed
in http://www.spinics.net/lists/netfilter/msg53196.html specifically
in http://www.spinics.net/lists/netfilter/msg53202.html.
libnfnetlink 1.0.0-1
Still a problem on 12.04.1. Removing /var/lib/update-notifier/fsck-at-
reboot and logging out, then back in works. The /etc/motd is updated and
no longer contains this misleading and wrong message about pending
fscks.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Because set +e is set in the status case of the postgresql init
script, running service postgresql status or /etc/init.d/postgresql
status always returns with exit code 0. Even when no clusters are
running the exit code is 0, when it should really be 3, indicating that
the
This is still a problem, both in Lucid and Precise.
** Summary changed:
- [karmic] slapd should start before kerberos kdc and admin servers, possibly
others
+ slapd should start before kerberos kdc and admin servers, possibly others
--
You received this bug notification because you are a
It's funny. I have three machines where I can always reproduce the
behaviour in my original description and two machines where I can
connect and list just fine. All running Precise. The two where it works
are slightly newer, i.e. have been set up some time in the last two
months, whereas the
Serge, at the moment it is a bit difficult but in a few weeks I could
have some spare machines available on which I could install Quantal.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
Serge, at the moment it is a bit difficult but in a few weeks I could
have some spare machines available on which I could install Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989452
Title:
There are currently multiple bugs that deal with virt-manager/virt-
viewer not being able to connect to a VNC console of a Libvirt/KVM
domain, such as #837275, #995320 and this one.
The problem remains, however. On a Precise server (12.04.1) where
/etc/libvirt/qemu.conf has set
vnc_listen =
Addendum: All this with Precise machines (client and server), no Oneiric
or earlier involved.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/989452
Title:
oneiric's virt-viewer
Is this going to make it into 12.04.2?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027987
Title:
Starting libvirtd takes too long because of udevadm settle timeout
To manage notifications about
There are currently multiple bugs that deal with virt-manager/virt-
viewer not being able to connect to a VNC console of a Libvirt/KVM
domain, such as #837275, #995320 and this one.
The problem remains, however. On a Precise server (12.04.1) where
/etc/libvirt/qemu.conf has set
vnc_listen =
Addendum: All this with Precise machines (client and server), no Oneiric
or earlier involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989452
Title:
oneiric's virt-viewer can't connect to
I just reproduced this again, with a byobu 5.20 running locally and a
byobu 5.21 running remotely. Using both KDE's konsole as well as a
regular xterm. I am running Kubuntu and thus KDE (4.8.4 at the moment),
does this matter any?
--
You received this bug notification because you are a member of
Mark, thanks for the suggestion, will look into that. I was under the
impression that pam_sss in /etc/pam.d/common-session was needed for
access control as provided by SSSD, but I was wrong, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is not really a bug. Sure, the resource agent has defaults set that
don't match Ubuntu's, but every relevant parameter can (and probably
should) be set explicitly in the CIB. For example:
primitive p_postgresql ocf:heartbeat:pgsql \
params pgctl=/usr/lib/postgresql/9.1/bin/pg_ctl
Agreed, this is indeed somewhat critical in my opinion. It breaks, for
example, the Pacemaker resource agent for PostgreSQL
(ocf:heartbeat:pgsql), which uses su to start and stop a PostgreSQL
instance. Some packages' postinst scripts also fail because su doesn't
exit correctly, for example
Sorry, no idea where this commit is supposed to be. I was going off the
information in the last entry of the Debian bug report, which contains
this:
* [202939f] Reduce udevadm settle timeout to 10 seconds
(Closes: #663931)
Maybe this is a Debian-only commit that didn't go back into Libvirt?
Ryan, what you are missing out on is Libvirt being able to create
volumes (LVs) in that pool (the VG) on command. I assume you create LVs
manually via lvcreate and then tell Libvirt to use them for VMs? If
Libvirt manages the pool you can use virt-manager, virsh or any of the
APIs/bindings to talk
Public bug reported:
This bug has already been reported in http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=663931 but Libvirt 0.9.8 in Ubuntu Precise suffers
from the same problem.
When an LVM-based storage pool is present libvirtd takes around three
minutes to start up because a timeout
Public bug reported:
Using Byobu 5.20 on Ubuntu 12.04. This problem seems to only occur on
Ubuntu 12.04, not on 10.04. I can't test others.
After starting a byobu instance it is nigh impossible to use the mouse
cursor to do text selections from the terminal window in which byobu
runs. The
I believe you have to add a trailing slash to the remote path to avoid
this bug, like so:
sshfs -o idmap=user remote_lucid:/data/ ~/mnt/lucid_data
See this discussion from a year ago: http://thread.gmane.org/gmane.comp
.file-systems.fuse.sshfs/1182/focus=1189
Why this bug made it into Ubuntu
In my case, the client was indeed 12.04, but I just tested with a 10.04
client (0.9.2-5ubuntu0+dnjl0~lucid0, from
https://launchpad.net/~dnjl/+archive/virtualization) and the problem is
the same. So what I can say is this:
* 12.04 virsh client via TLS to 12.04 libvirt host doesn't work
* 10.04
Public bug reported:
Connecting to a remote Libvirt instance on Ubuntu 12.04 (libvirt 0.9.8)
via, e.g., virsh -c qemu+tls://hostname.example.com/system simply hangs.
I have to terminate virsh with Ctrl+C to get my terminal back.
Connecting to the same remote Libvirt instance via unencrypted TCP
** Attachment added: Libvirt daemon debug logs of a failed/hung remote
connection attempt
https://bugs.launchpad.net/bugs/1001798/+attachment/3154335/+files/libvirt-debug-hang.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Libvirt daemon debug logs of a successful remote
connection attempt
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154337/+files/libvirt-debug-works.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Libvirt daemon strace of failed/hung remote connection
attempt
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154338/+files/libvirt-strace-hangs.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Libvirt daemon strace of successful remote connection
attempt
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1001798/+attachment/3154339/+files/libvirt-strace-works.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sorry, totally forgot to follow up.
It seems tmux alone, in a single instance (no tmux within tmux) breaks
256 colors as well. NB: I have not configured tmux in any way, just
running it like tmux from a fresh SSH shell. I also found that the
problem of broken 256 color support in nested sessions
Just to add something that has nothing to do directly with this bug, but
is related: we have been using SSSD for quite a while now, using Timo
Aaltonen's PPA https://launchpad.net/~sssd/+archive/updates and could
not be happier. In my opinion SSSD is the superior solution for all
things
Just to add something that has nothing to do directly with this bug, but
is related: we have been using SSSD for quite a while now, using Timo
Aaltonen's PPA https://launchpad.net/~sssd/+archive/updates and could
not be happier. In my opinion SSSD is the superior solution for all
things
Is this now really fixed in Lucid? As I have mentioned in comment #29 we
had applied this update from lucid-proposed and and continue to see this
error in /var/log/boot.log:
init: procps (virtual-filesystems) main process (670) terminated with
status 255
The initial problem remains the same, the
Public bug reported:
Using byobu version 5.15/tmux 1.5 on Ubuntu 10.04.4.
It seems that running byobu within an existing byobu session breaks or
disables 256 colors in the inner byobu session.
Scenario:
1) Log into a server (using SSH)
2) Start byobu
3) From a byobu window, ssh into another
To chime in here, there still appears to be the problem that Vim doesn't
understand that the terminal is capable of displaying 256 colors
*unless* one explicitly sets 'set t_Co=256' in ~/.vimrc. I don't know if
Byobu can do anything about that but it seems Vim only understands 256
colors if the
A possible workaround is putting sysctl -p /etc/sysctl.conf in
/etc/rc.local, which is ridiculous and doesn't even solve the problem
that networking and bridges are started *before* the sysctl settings are
applied.
It is even more ridiculous that this bug hasn't had any attention from
anyone
We applied the proposed fix to procps on a test machine but upon
rebooting the problem remained, with the following message appearing in
/var/log/boot.log:
init: procps (virtual-filesystems) main process (670) terminated with
status 255
We use /etc/sysctl.conf to disable frame filtering for
Still a problem in Lucid, making automatic installation and deployment
of VMs (using Cobbler or Foreman) pretty much impossible without manual
intervention. This, of course, defeats the whole point of automatic
installation and deployment.
--
You received this bug notification because you are a
Public bug reported:
A bug in libunistring/libunistring-dev in Ubuntu 10.04 leaves the
_UNUSED_PARAMETER_ macro undefined, resulting in compiler errors when
building or configuring with unistr.h.
See the following bug report for workaround and a patch:
This is still a problem on Ubuntu 10.04.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/541512
Title:
open-iscsi shutdown failure due to missing dir
To manage notifications about this bug go to:
So is there any way the proper fix will make it into Lucid? Or has that
ship sailed?
In the meantime I have applied Sebastian Marsching's method which works
quite well. Thanks for that, Sebastian.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Clint, great to hear, thanks. We have many Lucid servers in production,
but no Maverick or Natty, so the fix getting into Lucid is most
important for us. But if time and resources allow it, backporting the
fix to Maverick and Natty would certainly be nice.
--
You received this bug notification
So is there any way the proper fix will make it into Lucid? Or has that
ship sailed?
In the meantime I have applied Sebastian Marsching's method which works
quite well. Thanks for that, Sebastian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Clint, great to hear, thanks. We have many Lucid servers in production,
but no Maverick or Natty, so the fix getting into Lucid is most
important for us. But if time and resources allow it, backporting the
fix to Maverick and Natty would certainly be nice.
--
You received this bug notification
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571444
Title:
Boot hangs and unable to continue when automount disk in fstab is not
It is now May 2011 and this bug is still present in Ubuntu 10.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/356766
Title:
Changing long passwords causes spurious error
--
ubuntu-bugs
Orticio, this is an English-speaking forum. Please stop asking people to
speak Spanish.
Translated by Google:
Este es un foro de habla Inglés. Por favor, deje de pedir a la gente a
hablar español.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Orticio, this is an English-speaking forum. Please stop asking people to
speak Spanish.
Translated by Google:
Este es un foro de habla Inglés. Por favor, deje de pedir a la gente a
hablar español.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Serge,
why do you think this bug has been fixed? Nowhere is it confirmed that a
fix has been released, not even the associated Red Hat bug has seen any
activity in months.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For what it's worth this is still a problem in 10.04.1 and Postfix
2.7.0-1. Manually copying /dev/random and /dev/urandom to
/var/spool/postfix/dev works around the problem.
I also find it quite strange that this doesn't affect more people. In
fact this bug seems to have been completely
For what it's worth this is still a problem in 10.04.1 and Postfix
2.7.0-1. Manually copying /dev/random and /dev/urandom to
/var/spool/postfix/dev works around the problem.
I also find it quite strange that this doesn't affect more people. In
fact this bug seems to have been completely
This does not seem fixed in 10.04.1. The fix would apparently belong in
Libvirt but the changelogs for the Libvirt package in 10.04.1 don't
indicate anything and no KVM guest processes on my hosts running 10.04.1
show the -balloon virtio flag. I had to use a wrapper script around
Public bug reported:
Binary package hint: postgresql-8.4
The initd-functions of PostgreSQL 8.4.4-0ubuntu10.04 make Heartbeat's
ResouceManager (/usr/share/heartbeat/ResourceManager) believe that
PostgreSQL is running even when it is not, thus breaking clustering of
Postgres instances using
** Attachment added: One-line fix for confusing output of
/etc/init.d/postgresql-8.4 status
https://bugs.launchpad.net/bugs/655431/+attachment/1674266/+files/init.d-functions.patch
--
PostgreSQL init script make Heartbeat's ResourceManager believe PostgreSQL is
running, even when it is
Thanks for the new patch! I tested it just now and it seems to work, but
it's always hard to tell when dealing with race conditions. I'll keep
testing.
Out of interest, the only change (apart from the more verbose way of
testing the $interface variable) is the added break statement, right?
I am
Thanks for the new patch! I tested it just now and it seems to work, but
it's always hard to tell when dealing with race conditions. I'll keep
testing.
Out of interest, the only change (apart from the more verbose way of
testing the $interface variable) is the added break statement, right?
I am
Mika, thank you for the patch and new upstart job. We are trying it out
here and find that the bridged-network job seems to be waiting forever
for a net-device-up signal to be emitted, thus keeping libvirtd-bin
from starting.
I only now have begun reading up on upstart but so far I can't find any
Mika, thank you for the patch and new upstart job. We are trying it out
here and find that the bridged-network job seems to be waiting forever
for a net-device-up signal to be emitted, thus keeping libvirtd-bin
from starting.
I only now have begun reading up on upstart but so far I can't find any
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Fionn, glad you solved your problem, but it is not this particular
problem.
I want to remind everyone that any kind of mounting problems have
nothing to do with the issue this bug report describes, namely
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
Ah, I see. I must have misunderstood your post, sorry. It is interesting
and disturbing that there seem to be so many conditions that could
result in a server not booting correctly.
--
kernel 2.6.32-32
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
This bug is not a duplicate of #571444. At least not in the
characteristic that I and others who reported here have experienced it.
My /etc/fstab was always in the pristine state that is the result of a
fresh
Chiming in again I am cautiously optimistic that with the latest -server
packages (-23 and recently -24) the problem went away. I have installed
and upgraded two identical DL380 G6 servers and performed many
consecutive reboots since and have yet to experience any hangs. I just
rebooted one of the
Charles, that's definitely a bug. I believe there have been efforts in
Plymouth to fix it but you need to the splash screen for those error
messages to be displayed. A default server install, or one where the
kernel is instructed to boot with as much text output as possible
jgreenso, I will try a -generic kernel image hopefully next week or the
week after that, when I get my hands on one of the machines on which we
experienced the problems.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification
Charles, I'll be trying your idea as soon as I get one of the machines
back (next week probably). Maybe I can find some pattern :)
But I really don't think this is in any way fixed. All we know is that
there are at least five people affected by it and no solution has been
posted or linked to
I just want to add that I unfortunately have not been able to test this
further (not even using -generic instead of -server kernels) since the
machines in question needed to go into production. We went back to
Ubuntu 9.10 for that. If I'm lucky I can maybe get one or two of these
machines back in
Charles, thanks for the reply. I do not use dist-upgrade for regular
package upgrades. However there should not be any difference between
dist-upgrade (full-upgrade) and safe-upgrade in this case. The kernel
package gets updated either way.
So you don't seem to see any problems even after a few
Interesting, I hadn't tested using non-server kernel images. Thanks for
the suggestion jgreenso, I'll be trying that on our problematic
machines.
--
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member
I just went through that whole mess again and reinstalled one of the
machines. Unfortunately to no avail. Installation went speedy and fine,
aptitude update and aptitude safe-upgrade as well (this includes
installation of the new kernel image), rebooted three or four times and
now it hangs again.
Public bug reported:
This was also discussed in https://lists.ubuntu.com/archives/ubuntu-
server/2010-May/004172.html
The problem is that the console of a Ubuntu 10.04 (server) virtual
machine/guest becomes incredibly slow and really unusable as soon as it
starts scrolling. This is apparently
Could this bug be related to bug 576001?
--
Hang after update/upgrade of 10.04-beta1-server-i386.iso
https://bugs.launchpad.net/bugs/549751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Charles, this is exactly what I did in the first place. Clean install of
Ubuntu 10.04 Server, then upgrade to -22-server kernel. More often than
not the system would not come up correctly, as described above.
--
kernel 2.6.32-32 makes machine hang during boot
Public bug reported:
On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
profiles as discussed in bug 545795 the hot-attachment of USB devices is
blocked/denied by AppArmor. Hot-attachment means: a KVM-based VM is
running and a USB devices connected to the underlying host is to
** Summary changed:
- AppArmor blocks hot-attaching of USB devices
+ AppArmor blocks hotplugging of USB devices
** Description changed:
On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
- profiles as discussed in bug 545795 the hot-attachment of USB devices is
-
This is becoming a bit scary. I have continued experimenting with the HP
DL380 machines I have here and even now even the even with the kernel
image 2.6.32-21-server makes the machine hang.
I can still SSH into it and look at the process list, see attachment.
Does anything in there look
Public bug reported:
On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
profiles as discussed in bug 545795 the hot-attachment of USB devices is
blocked/denied by AppArmor. Hot-attachment means: a KVM-based VM is
running and a USB devices connected to the underlying host is to
** Summary changed:
- AppArmor blocks hot-attaching of USB devices
+ AppArmor blocks hotplugging of USB devices
** Description changed:
On Ubuntu 10.04 server, after applying the fixes to Libvirt's AppArmor
- profiles as discussed in bug 545795 the hot-attachment of USB devices is
-
1 - 100 of 158 matches
Mail list logo
