Thanks for the tip. I tried that over here and it didn't help, but I
think I have a different bug over here (mine is related to SMP guests),
so I just filed bug 714335 to track mine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also want to mention that the guests are fully-updated 64-bit Ubuntu
Lucid Server VMs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/714335
Title:
KVM SMP Linux Guests Hang
--
ubuntu-bugs
Could you please tell us if the VMs that won't boot are SMP VMs? I know
it's the SMP kernel but what I mean is, is KVM giving the VM more than
one CPU? If they are SMP VMs, could you please try to make them single-
CPU and try to boot them, then let us know what happens? I am seeing a
bug with
Could you please tell us if the VMs that won't boot are SMP VMs? I know
it's the SMP kernel but what I mean is, is KVM giving the VM more than
one CPU? If they are SMP VMs, could you please try to make them single-
CPU and try to boot them, then let us know what happens? I am seeing a
bug with
In my case, I identified the source of my sound problems with
Pulseaudio: I had installed the randomsound package, and it conflicts
with Pulseaudio and causes the audio controller to stop being
recognized. If I remember correctly there is already a bug somewhere in
Launchpad for this (I think I
To: brianknoll2...@yahoo.com
Date: Saturday, November 13, 2010, 12:12 PM
On 11/13/2010 08:44 PM, Brian Knoll wrote:
In my case, I identified the source of my sound problems with
Pulseaudio: I had installed the randomsound package, and it conflicts
with Pulseaudio and causes the audio controller to stop
Attaching X.org log
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/500887/+attachment/1709881/+files/Xorg.0.log
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received
apport information
** Tags added: apport-collected
** Description changed:
Pressing the Synaptics enable/disable button on the notebook disables
the Synaptics functionality, as it should. However, pressing it again
does not re-enable the Synaptics function. The function cannot be
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709884/+files/CurrentDmesg.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709885/+files/Dependencies.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709886/+files/Lspci.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are a
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709887/+files/Lsusb.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are a
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709888/+files/PciDisplay.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709889/+files/ProcCpuinfo.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709890/+files/ProcInterrupts.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709891/+files/ProcModules.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709892/+files/RelatedPackageVersions.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709893/+files/UdevDb.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are a
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709894/+files/UdevLog.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709895/+files/XorgLog.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709896/+files/XorgLogOld.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because
apport information
** Attachment added: Xrandr.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709897/+files/Xrandr.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are a
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709898/+files/setxkbmap.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709899/+files/xdpyinfo.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/500887/+attachment/1709900/+files/xkbcomp.txt
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are
Syslog file
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/500887/+attachment/1709936/+files/syslog
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug
Should I do this before or after the synaptics device is deactivated?
Or, third option, after it's deactivated, then reactivated (even
though it doesn't actually come back)?
Just let me know which way would help the most.
--
Synaptics Button Press Disables Synaptics Function Until Reboot
Yes, this bug still exists in both Lucid and Maverick. The device is an
eMachines notebook.
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I reset status back to New since the nature of the bug has changed and
there is new information. Incomplete didn't seem appropriate any
more.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
Pulseaudio Does Not Start Correctly When Randomsound Package is Installed
I think I figured out what the problem was. The problem was that I had
the randomsound package installed. When this package is installed,
there is a race condition and the sound components don't initialize
properly. I'm not 100% certain whether the bridged network is actually
needed in order to
I updated the bug title to correctly reflect the current idea of what
actually triggers this bug.
--
Pulseaudio Does Not Start Correctly When Randomsound Package is Installed
https://bugs.launchpad.net/bugs/577509
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: randomsound
Installing the randomsound package causes Pulseaudio to stop
functioning at the next reboot. The sound hardware is no longer
detected when this package is installed. Removing the randomsound
package resolves the issue.
There is a
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/49818564/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/49818565/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49818566/BootDmesg.txt
**
Thanks for helping with this. I have verified that the problem does
indeed occur with the upstream 2.6.32-02063211-generic #02063211 kernel,
and I have removed the needs-upstream-testing tag from this ticket, as
requested.
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
I changed the status to confirmed after testing against the upstream
kernel, because invalid didn't seem appropriate any more. If that
wasn't correct, please let me know which status you would prefer, and/or
change it to another status. Thanks!
** Tags added: apport-collected
** Description
I've collected additional data from the failed state, using the upstream
kernel, and attached it to this case.
--
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
You received this bug notification because you are a member of Ubuntu
Bugs,
I have now also tested this issue against the 2.6.34-020634rc6-generic
#020634rc6 upstream kernel, and I confirm that the problem also exists
when using that kernel.
** Description changed:
Binary package hint: pulseaudio
On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the
I think I might have found something: For me, this failure to detect my
audio hardware seems to occur much more frequently when I have a bridged
network set up on my eth0 device. If I don't do that, my audio is
usually fine. If I DO set up a bridge on my eth0, however, then when I
reboot I
Public bug reported:
Binary package hint: pulseaudio
On an install of Ubuntu Lucid 10.04 LTS AMD64, I could reboot the system
and it would come back up and consistently have audio. However, once I
configured a bridged network on my eth0 device in
/etc/network/interfaces, the system would no
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/48069135/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/48069136/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/48069137/ArecordDevices.txt
Changing affected package at the request of Daniel T. Chen
** Package changed: pulseaudio (Ubuntu) = linux-meta (Ubuntu)
--
Pulseaudio Does Not Start Correctly When Using Bridged Networking
https://bugs.launchpad.net/bugs/577509
You received this bug notification because you are a member of
When I tried to change the package name to linux, Launchpad stopped me
and said that there were too many matches, so it wouldn't allow it.
That's when I changed the package name to linux-2.6.32-22-server, and
then Launchpad automatically reassigned it to linux-meta.
I'm happy to change it to
This is confirmed on an AMD64 install of Ubuntu Lucid Lynx 10.04.
** Changed in: amarok (Ubuntu)
Status: New = Confirmed
--
Amarok will not create music collection
https://bugs.launchpad.net/bugs/542725
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I urge everybody on this bug to listen to Daniel T. Chen and go look at
but 557421 to see if it looks like that might be the same bug you are
experiencing, and if so, then add yourself to the list of affected users
for that bug.
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/557421
--
Daniel, I tried to test your PPA package on my AMD64 system, but after
adding your PPA to my Software Sources, I got the following error:
Failed to fetch
http://ppa.launchpad.net/crimsun/ppa/ubuntu/dists/lucid/main/binary-amd64/Packages.gz
404 Not Found
Some index files failed to download,
Public bug reported:
Binary package hint: pulseaudio
There is no audio in Lucid AMD64 with this audio controller.
The sound worked when I first installed, then simply stopped working. I
can get sound if I forcibly remove Pulseaudio, but of course I'd rather
not take that drastic step. I am
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/45815047/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/45815048/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/45815049/ArecordDevices.txt
I just tried something: If I do an alsa force-reload, then I get my
audio back and in my sound properties, under Hardware, it shows the
actual hardware device. Of course, if I reboot, I lose my sound again.
Perhaps this will help someone on the audio team track down where the
problem is. Please
After rebooting several times and reproducing the situation, where I
don't get sound until I run alsa force-reload, I rebooted one more
time, and this time when I ran alsa force-reload I did not get my
audio back. I also don't see the hardware listed under the sound
properties. So apparently
*** This bug is a duplicate of bug 559442 ***
https://bugs.launchpad.net/bugs/559442
If you look in your sound properties, under Hardware, there should be
a Dummy Output listed instead of the actual sound hardware you have.
I have several Lucid AMD64 machines doing this.
** Changed in:
I just reinstalled from the Alternate Release Candidate ISO image, and
my desktop installation worked fine for a few hours, then I noticed that
I didn't get sound any more. I'm not sure if I rebooted before the
sound went away, or what, but it had worked right from the install, then
went away.
This doesn't seem to be fixed in Lucid Beta 2. I'm getting this problem
on Lucid Beta 2 machines still.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Released = Confirmed
--
dummy output, no sound on HDA Intel internal sound card
https://bugs.launchpad.net/bugs/545592
You received
I just tried removing pulseaudio completely (which unfortunately does
remove the ubuntu-desktop package as a dependency, but that's okay for
my purposes) and I got my sound back. I have done this twice now and it
worked both times. If I put pulseaudio back in, I lose sound.
--
I rebooted my system (AMD64 Lucid) this morning and now find that no
sound hardware is detected any more. I see the volume icon, but it's
blank (for lack of a better way to describe it; it looks hollow) and
in the properties for the volume control, under Hardware, all I have
is a Dummy Device.
** Changed in: alsa-driver (Ubuntu)
Status: New = Confirmed
--
No sound in Lucid Lynx Beta 2
https://bugs.launchpad.net/bugs/558910
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:
This occurs when quotas are enabled. I have seen this on AMD64 systems;
I am unsure if it occurs on i386 or not.
To reproduce, do this:
1. Enable journaled quota support with
usrquota,grpquota,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0
filesystem options
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/41723054/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/41723055/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41723056/BootDmesg.txt
**
I got this same error on the AMD64 platform, so that platform is also
affected.
--
does not terminate at computer shutdown
https://bugs.launchpad.net/bugs/539802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I just changed the description of the bug to remove the requirement that
the guest be virtio-based in order to trigger the bug. I can also
confirm that I have, now, seen the failure under guests that were ide-
based and scsi-based, as well as virtio-based guests.
** Summary changed:
- Grub
Public bug reported:
Binary package hint: grub
Grub does not install if Lucid is installed onto a KVM guest using
virtio disks. The installation will progress to the point where the
boot loader is supposed to be installed, and an error message will pop
up saying that grub failed to install. If
** Changed in: ubuntu
Status: New = Confirmed
--
Lucid Alpha 2 server iso install fails at bootloader in KVM
https://bugs.launchpad.net/bugs/524434
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:
Binary package hint: xorg
This usually happens when the system is idle for some time. I haven't
yet checked to see if disabling the screen saver (which is OpenGL)
helps, although I plan to try that.
ProblemType: Bug
Architecture: amd64
Date: Mon Jan 18 10:26:10 2010
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38042717/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38042718/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38042719/Dependencies.txt
**
I want to mention that the system, other than the video, does stay
responsive when this situation occurs. I see the render error and GPU
hung error in my logs and the console becomes useless because there is
no longer any video after this happens, but the system itself keeps
running. I generated
Public bug reported:
Binary package hint: evolution
Evolution suddenly exited. No interactive activity was being performed
by the user at the time.
ProblemType: Crash
Architecture: amd64
Date: Thu Jan 14 08:30:24 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37883563/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/37883564/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/37883565/ProcMaps.txt
** Attachment
I am curious as to what you're running into, as I've run into a problem
myself trying to build the package for all of the targets.
The problem I've run into when trying to build the package from source
is that it doesn't seem to build all of the targets that the old
(0.11.x) package did. So I
This merge would resolve an issue with the virtualbox modules not
building in the 3.0.8 currently in Lucid, by upgrading to a version that
includes fixes for this issue.
** Changed in: virtualbox-ose (Ubuntu)
Status: New = Confirmed
--
Please merge virtualbox-ose 3.1.2-dfsg-1 (universe)
Additional information: Bug #498219 is a request to merge a newer
version of virtualbox into Lucid, which would resolve this issue if it
gets merged.
--
[lucid] VirtualBox kernel module fails to build against Linux = 2.6.32
https://bugs.launchpad.net/bugs/474625
You received this bug
I am curious as to what you're running into, as I've run into a problem
myself trying to build the package for all of the targets.
The problem I've run into when trying to build the package from source
is that it doesn't seem to build all of the targets that the old
(0.11.x) package did. So I
I want to add that importing 3.0.10 is mentioned as the resolution to
ticket #474625, which means that ticket is one of the drivers for
needing this import. The implication is that Lucid users won't be able
to run Virtualbox without going out and getting the sources themselves,
or otherwise
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
** Changed in: ubuntu
Status: New = Confirmed
--
Synaptics Button Press Disables Synaptics Function Until Reboot
https://bugs.launchpad.net/bugs/500887
You received this bug notification
Public bug reported:
Binary package hint: qemu-kvm
KSM is supported by the current Lucid kernel. However, the current
version of the qemu-kvm package, 0.11, does not support KSM. Therefore,
memory usage will be suboptimal, as this key feature is disabled for KVM
VM guests unless a high enough
** Summary changed:
- qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)
+ qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
--
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
You received
** Summary changed:
- qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
+ qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
** Description changed:
Binary package hint: qemu-kvm
- KSM is supported by the current Lucid kernel. However, the
Public bug reported:
Binary package hint: qemu-kvm
KSM is supported by the current Lucid kernel. However, the current
version of the qemu-kvm package, 0.11, does not support KSM. Therefore,
memory usage will be suboptimal, as this key feature is disabled for KVM
VM guests unless a high enough
** Summary changed:
- qemu-kvm 0.12.1.1 needed (KSM not available in current 0.11 version)
+ qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
--
qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
https://bugs.launchpad.net/bugs/500272
You received
** Summary changed:
- qemu-kvm 0.12.1.1 needed for KSM support (key virtualization feature)
+ qemu-kvm 0.12.1.1 needed for KSM support (key KVM virtualization feature)
** Description changed:
Binary package hint: qemu-kvm
- KSM is supported by the current Lucid kernel. However, the
Public bug reported:
Binary package hint: seahorse-plugins
I got this bug while browsing websites. I notice the apport system
created a description mentioning seahorse-plugins but I was actually
using Firefox; I'm not sure what caused that.
I am on an AMD64 system, as specified in the tags.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34138075/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/34138076/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34138077/ProcMaps.txt
** Attachment
Public bug reported:
Binary package hint: seahorse-plugins
I got this bug while browsing websites. I notice the apport system
created a description mentioning seahorse-plugins but I was actually
using Firefox; I'm not sure what caused that.
I am on an AMD64 system, as specified in the tags.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34138067/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/34138068/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34138069/ProcMaps.txt
** Attachment
101 - 182 of 182 matches
Mail list logo
