[Bug 657478] Re: Gwibber causing beam.smp to cause high CPU load and memory usage
I had this repeating on my system even with Maverick. The system is one upgraded from Lucid. Would it be possible that the gwibber is still using the wrong database? Disabling gwibber did help. Also, I think this is a recent problem that has not appeared during the time using Lucid. -- Gwibber causing beam.smp to cause high CPU load and memory usage https://bugs.launchpad.net/bugs/657478 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538917] Re: xen-tools is not available in lucid
I take that back. It was obviously something wrong with verbosity. If the /etc/xen directory is missing, there is no clear output. -- xen-tools is not available in lucid https://bugs.launchpad.net/bugs/538917 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538917] Re: xen-tools is not available in lucid
Axel: I tested the head of that repository. The output I am getting
seems a little bit concerning.
What I did:
$ sudo apt-get install mercurial libfile-slurp-perl libtext-template-perl
$ hg fetch http://noone.org/hg/xen-tools/
$ cd xen-tools
$ sudo make install
$ sudo xen-create-image --hostname dev --size 20G --swap 256M --memory 256M
--dhcp --lvm local
What I got:
Use of uninitialized value $CONFIG{"dir"} in concatenation (.) or string at
/usr/bin/xen-create-image line 1839.
The output directory for creating the xen configuration file within
doesn't exist:
Aborting.
So it seems that the script handles --dir incorrectly. If I specify lvm
in configuration, the trace goes away but the error remains the same. If
I additionally set dir, the empty space is filled with the target dir
but still an error.
Please do set up the PPA so that I will be informed about new changes.
I might look into the code a bit later.
--
xen-tools is not available in lucid
https://bugs.launchpad.net/bugs/538917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372741] Re: [GM45] Compiz does not start when resolution is more than 2048
*** This bug is a duplicate of bug 146298 *** https://bugs.launchpad.net/bugs/146298 I know exactly what you are saying but the case is that we have in our hands a fix that does work on several configurations and on others it does not. So in this bug I am suggesting that, if easily done, we could conditionally fix the issue for any sure-shot platforms we have. This is especially important if the fix for one reason or the other is taking more time than expected. -- [GM45] Compiz does not start when resolution is more than 2048 https://bugs.launchpad.net/bugs/372741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372741] Re: [GM45] Compiz does not start when resolution is more than 2048
This works for me with the patch 103 re-enabled in mesa. However it appears from bug #146859 and bug #359392 that this patch has side effects for some other chips. I have re-enabled the patch 103 in the latest package from proposed in my PPA: https://launchpad.net/~ferrix/+archive/ppa ** Package changed: xserver-xorg-video-intel (Ubuntu) => mesa (Ubuntu) -- [GM45] Compiz does not start when resolution is more than 2048 https://bugs.launchpad.net/bugs/372741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146859] Re: No dri (and therefore no compiz) for virtual screen greater than 2048x2048
I reopened a bug #372741 for GM45 which I marked as duplicate before. -- No dri (and therefore no compiz) for virtual screen greater than 2048x2048 https://bugs.launchpad.net/bugs/146859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372741] Re: [GM45] Compiz does not start when resolution is more than 2048
** This bug is no longer a duplicate of bug 146859 No dri (and therefore no compiz) for virtual screen greater than 2048x2048 -- [GM45] Compiz does not start when resolution is more than 2048 https://bugs.launchpad.net/bugs/372741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146859] Re: No dri (and therefore no compiz) for virtual screen greater than 2048x2048
@aporter: I don't know where the rumors and hunches come from. It is true that I run out of memory before achieving 4096x4096 resolution but that results in a decent error message. I have made the rolled back feature available in my PPA: https://launchpad.net/~ferrix/+archive/ppa The patch is still available in the Ubuntu source package, it has just been commented out in the series file. The reason for the patch to have been disabled is Bug#359392 and there seems to be enough reason to have done so. Be sure to have the official packages available in case you face problems. -- No dri (and therefore no compiz) for virtual screen greater than 2048x2048 https://bugs.launchpad.net/bugs/146859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372741] Re: [GM45] Compiz does not start when resolution is more than 2048
*** This bug is a duplicate of bug 146859 *** https://bugs.launchpad.net/bugs/146859 ** This bug has been marked a duplicate of bug 146859 No dri (and therefore no compiz) for virtual screen greater than 2048x2048 -- [GM45] Compiz does not start when resolution is more than 2048 https://bugs.launchpad.net/bugs/372741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146859] Re: No dri (and therefore no compiz) for virtual screen greater than 2048x2048
** Changed in: mesa (Ubuntu Jaunty) Status: Fix Released => Confirmed -- No dri (and therefore no compiz) for virtual screen greater than 2048x2048 https://bugs.launchpad.net/bugs/146859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146859] Re: No dri (and therefore no compiz) for virtual screen greater than 2048x2048
Obviously the change that fixed this for me has been rolled back. I can confirm that it did not cause a hang on GM45 and I suggest that the patch would be restored conditionally for chips having no problem with it. -- No dri (and therefore no compiz) for virtual screen greater than 2048x2048 https://bugs.launchpad.net/bugs/146859 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 358315] Re: [gm45] [jaunty] intel xrandr dual head auto config only configures part of one screen on Dell Lattitude E4300
Does moving a window across the border enable the mouse to enter the area? Are you using compiz? -- [gm45] [jaunty] intel xrandr dual head auto config only configures part of one screen on Dell Lattitude E4300 https://bugs.launchpad.net/bugs/358315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368518] Re: [GM45, 945] Unable to mirror to external monitor
I was able to repeat this earlier but currently with xserver-xorg-video- intel 2:2.6.3-0ubuntu9.2. This has never occured to me when using xrandr from command line. -- [GM45, 945] Unable to mirror to external monitor https://bugs.launchpad.net/bugs/368518 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372741] [NEW] [GM45] Compiz does not start when resolution is more than 2048
Public bug reported: Binary package hint: xserver-xorg-video-intel Compiz does not start when the resolution is above 2048 in either direction. This behavior has changed in a recent patch where the area above 2048 would not be drawn correctly (and there is a fix for that too). Affected version: xserver-xorg-video-intel 2:2.6.3-0ubuntu9.2 compiz output: --- Detected PCI ID for VGA: Checking for texture_from_pixmap: not present. Trying again with indirect rendering: Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Checking screen 1Comparing resolution (3360x1200) to maximum 3D texture size (2048): Failed. aborting and using fallback: /usr/bin/metacity ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: xserver-xorg-video-intel Compiz does not start when the resolution is above 2048 in either direction. This behavior has changed in a recent patch where the area above 2048 would not be drawn correctly (and there is a fix for that too). + + Affected version: + xserver-xorg-video-intel 2:2.6.3-0ubuntu9.2 compiz output: --- Detected PCI ID for VGA: Checking for texture_from_pixmap: not present. Trying again with indirect rendering: Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Checking screen 1Comparing resolution (3360x1200) to maximum 3D texture size (2048): Failed. aborting and using fallback: /usr/bin/metacity -- [GM45] Compiz does not start when resolution is more than 2048 https://bugs.launchpad.net/bugs/372741 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357982] Re: [GM45] desktop cropped when running compiz (UXA/EXA)
I am having this problem (again). I had it fixed some time ago by a combination of packages I do not remember but an official update broke it. * The screen becomes cropped from the 2048th pixel. * It is impossible to cross the limit with mouse unless it is crossed first by a window. Currently compiz does not start with intel driver on gm45 with more than 2048 pixels and this occurs only when expanding to another monitor on the fly. With my fixed combination, this did not occur on fresh start, but this special case has never worked, so be sure to test with it before marking this as fixed. -- [GM45] desktop cropped when running compiz (UXA/EXA) https://bugs.launchpad.net/bugs/357982 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372598] Re: Virtual Screen Size ignored in Xubuntu
*** This bug is a duplicate of bug 370777 *** https://bugs.launchpad.net/bugs/370777 Confirmed. Fixed the problem for me. -- Virtual Screen Size ignored in Xubuntu https://bugs.launchpad.net/bugs/372598 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369150] Re: Thunderbird splits email addresses with non-ascii characters and a comma in From: field
I filed the bug into upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=490689 It appears that I was wrong about the case sensitivity. Reproducing this requires only an escaped letter, a comma and no quotes. ** Bug watch added: Mozilla Bugzilla #490689 https://bugzilla.mozilla.org/show_bug.cgi?id=490689 -- Thunderbird splits email addresses with non-ascii characters and a comma in From: field https://bugs.launchpad.net/bugs/369150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369150] Re: Thunderbird splits email addresses with non-ascii characters and a comma in From: field
** Package changed: evolution (Ubuntu) => thunderbird (Ubuntu) -- Thunderbird splits email addresses with non-ascii characters and a comma in From: field https://bugs.launchpad.net/bugs/369150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 369150] [NEW] Thunderbird splits email addresses with non-ascii characters and a comma in From: field
Public bug reported: When I receive mail where the sender is of the form "Lastname, Firstname" and the last name contains Finnish umlaut letters ä and ö, the sender is parsed into simply Lastname. Example: Järvinen, Jukka is shown as: Message window: "Järvinen" and "Jukka " Reply window: "Järvinen" Index: "Järvinen" Header: "From: =?iso-8859-1?Q?J=E4rvinen=2C_Jukka?= " Affected version: 2.0.0.21 (20090409) This happens when the mail is sent from Exchange. The only apparent difference in the From header sent from Thunderdird is that ISO-8850-1 is written in upper case. ** Affects: ubuntu Importance: Undecided Status: New -- Thunderbird splits email addresses with non-ascii characters and a comma in From: field https://bugs.launchpad.net/bugs/369150 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217732] Re: package base-files 4.0.1ubuntu4 failed to install/upgrade: unable to stat `./mnt' (which I was about to install)
Solved it actually. When something is mounted on /mnt unpacking fails. I am not sure if the mount needs to be irresponsive at the time (I had a disconnected samba mount). This error isn't obvious and clearly it shouldn't matter if something is mounted on an existing directory while we are trying to create the directory itself. I suggest this be fixed since it seems like a rather simple thing in how the directories are handled and may result in moon- phase bugs such as this. -- package base-files 4.0.1ubuntu4 failed to install/upgrade: unable to stat `./mnt' (which I was about to install) https://bugs.launchpad.net/bugs/217732 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217732] Re: package base-files 4.0.1ubuntu4 failed to install/upgrade: unable to stat `./mnt' (which I was about to install)
This happens also to me also. (Reading database ... 141359 files and directories currently installed.) Preparing to replace base-files 5ubuntu3 (using .../base-files_5ubuntu4_amd64.deb) ... Unpacking replacement base-files ... dpkg: error processing /var/cache/apt/archives/base-files_5ubuntu4_amd64.deb (--unpack): unable to stat `./mnt' (which I was about to install): Input/output error Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/base-files_5ubuntu4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- package base-files 4.0.1ubuntu4 failed to install/upgrade: unable to stat `./mnt' (which I was about to install) https://bugs.launchpad.net/bugs/217732 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213279] Re: cryptsetup: source device not found during boot
This still happens. Here's a snippet from my crypttab. --- 8< --- sdd2_crypt /dev/disk/by-uuid/bd3d4b37-5b8d-4ad6-a21c-c52115c77f88 none luks --- 8< --- With kernel revision 8, I don't get an error but with revision 16 the initramfs reports that the specified file is not found. This is a major regression because this concerns encrypted partitions automagically generated with Gutsy installer. -- cryptsetup: source device not found during boot https://bugs.launchpad.net/bugs/213279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188252] Re: [Hardy] Mono-gac didn't install properly
This is what I got when I updated my Hardy. Setting up mono-gac (1.2.6+dfsg-6ubuntu3) ... * Installing 1 assembly from libgmime2.2-cil into Mono * Installing 4 assemblies from libmono-addins0.2-cil into Mono * Installing 2 assemblies from libmono-addins-gui0.2-cil into Mono * Installing 1 assembly from libndesk-dbus1.0-cil into Mono * Installing 1 assembly from libndesk-dbus-glib1.0-cil into Mono ! Assembly /usr/share/cli-common/policies.d/libmono-addins-gui0.2-cil/policy.0.2.Mono.Addins.Gui.dll does not exist ! Assembly /usr/share/cli-common/policies.d/libmono-addins0.2-cil/policy.0.2.Mono.Addins.dll does not exist ! Assembly /usr/share/cli-common/policies.d/libmono-addins0.2-cil/policy.0.2.Mono.Addins.Setup.dll does not exist dpkg: error processing mono-gac (--configure): subprocess post-installation script returned error exit status 3 -- [Hardy] Mono-gac didn't install properly https://bugs.launchpad.net/bugs/188252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179822] Re: [hardy] Enabling xinerama crashes X
Here's the lspci output for a reference. This setup works perfectly with TwinView configured. Compiz or something prevents nvidia-settings from working, but that has been the case for previous versions as well. ** Attachment added: "lspci output for the record." http://launchpadlibrarian.net/11158347/lspci.txt -- [hardy] Enabling xinerama crashes X https://bugs.launchpad.net/bugs/179822 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179822] Re: [hardy] Enabling xinerama crashes X
My lshw for more information. ** Attachment added: "lshw output" http://launchpadlibrarian.net/11158378/lshw.txt -- [hardy] Enabling xinerama crashes X https://bugs.launchpad.net/bugs/179822 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179822] Re: [hardy] Enabling xinerama crashes X
Didn't work a bit. I had to fall back to the previous versions. I attached the xorg log file. My graphics adapter is a Gigabyte GeForce 8600GT on an ASUS P5K-V motherboard. ** Attachment added: "This is the log generated by any configuration" http://launchpadlibrarian.net/11158307/Xorg.0.log -- [hardy] Enabling xinerama crashes X https://bugs.launchpad.net/bugs/179822 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179822] [hardy] Enabling xinerama crashes X
Public bug reported: I updated to Hardy and my dual head configuration that worked perfectly on Gutsy started crashing. An automatically set up configuration worked okay when I removed xorg.conf and by merging the configurations I found that activating Xinerama was the cause. TwinView works like a charm. ** Affects: linux-restricted-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- [hardy] Enabling xinerama crashes X https://bugs.launchpad.net/bugs/179822 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131133] Re: [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro 1500/1700 pci id 8086:284b
I updated to version 1.0.15rc3. I packaged using the 1.0.14-1ubuntu2 patch and it worked as is. I haven't checked on any other cards but it works as a first aid for D630. The packages for amd64 and 2.6.22-12-generic kernel can be found in the URL below. http://earlypenguin.fi/software/packages/alsa/ -- [gutsy] no sound on Dell Latitude D630/D830/Precision M4300/Vostro 1500/1700 pci id 8086:284b https://bugs.launchpad.net/bugs/131133 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114856] Dell Latitude D610 suspend fix
Public bug reported: Binary package hint: acpi-support In Feisty (and everything previous as far as I know) I had a problem with my Dell Latitude D610. The LCD doesn't come up after I open the lid. A double switch makes things only worse. According to some reference I cannot remember there is a BIOS bug that prevents the screen from coming around after the lid is opened. I resolved the issue by adding 'echo 0x8001 > /proc/acpi/video/VID/LCD/state' to the lid opening script. ** Affects: acpi-support (Ubuntu) Importance: Undecided Status: Unconfirmed -- Dell Latitude D610 suspend fix https://bugs.launchpad.net/bugs/114856 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 114857] Dell Latitude D610 suspend fix
Public bug reported: Binary package hint: acpi-support In Feisty (and everything previous as far as I know) I had a problem with my Dell Latitude D610. The LCD doesn't come up after I open the lid. A double switch makes things only worse. According to some reference I cannot remember there is a BIOS bug that prevents the screen from coming around after the lid is opened. I resolved the issue by adding 'echo 0x8001 > /proc/acpi/video/VID/LCD/state' to the lid opening script. ** Affects: acpi-support (Ubuntu) Importance: Undecided Assignee: Paul Sladen Status: Unconfirmed ** Changed in: acpi-support (Ubuntu) Assignee: (unassigned) => Paul Sladen -- Dell Latitude D610 suspend fix https://bugs.launchpad.net/bugs/114857 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56171] Re: Microsoft LifeCam VX-6000 High Definition Webcam doesn't work at all.
Has anyone actually implemented a driver so far? I won my camera from Microsoft and the best use I can guess is using it in Linux. -- Microsoft LifeCam VX-6000 High Definition Webcam doesn't work at all. https://bugs.launchpad.net/bugs/56171 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
