[Bug 1914711] Re: package u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 failed to install/upgrade: installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1
I'm seeing this error also, though as far as I can tell, it doesn't preclude the installation or upgrade of other packages I've installed or upgraded so far. On my system (an RPi4, 8GB, with Ubuntu 20.10 installed with Berryboot), /boot/firmware exists, but it's just a plain directory and not a mounted filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914711 Title: package u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 failed to install/upgrade: installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/u-boot/+bug/1914711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780829] [NEW] linux 3.13.0-151 causes win7 qemu-KVM VM to fail boot
Public bug reported: After my system was upgraded from linux 3.13.0-149 -> 3.13.0-151, my windows 7 virtual machine fails to boot. I tried both my existing disk image, and the windows 7 installer. Both either hang early in the boot process or enter a reboot loop. The windows 10 installer boots fine. I'm launching qemu-kvm through libvirt using virsh. I'll attach the XML file for the virtual machine here, but I tried simplifying it down as far as possible and the problem still reproduces. I also tried 3.13.0-153 when it became available, but the issue remains. For now, I've downgraded back to 3.13.0-149 as a work-around, but this doesn't seem like a feasible long-term solution. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jajones2982 F pulseaudio CurrentDesktop: KDE Date: Mon Jul 9 10:19:31 2018 HibernationDevice: RESUME=UUID=305bcf8e-aef9-4db2-b918-60c1298edd59 InstallationDate: Installed on 2014-08-28 (1410 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=4ebf72df-8d67-4a16-ac60-022899788a4f ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-D3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug trusty ** Attachment added: "libvirt VM definition" https://bugs.launchpad.net/bugs/1780829/+attachment/5161481/+files/win7.xml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780829 Title: linux 3.13.0-151 causes win7 qemu-KVM VM to fail boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766689] [NEW] package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: This cccurred when upgrading to 18.04 final beta. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.7+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 BootEFIContents: fw fwupx64.efi Date: Tue Apr 24 13:48:57 2018 EFIBootMgr: Error: command ['efibootmgr', '-v'] failed with exit code 2: EFI variables are not supported on this system. EFITables: Apr 24 13:53:28 faster-eeyore fwupd[2654]: disabling plugin because: failed to startup uefi: UEFI firmware updating not supported ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-10-18 (187 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: shim-signed Title: package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-04-23 (0 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766689 Title: package shim-signed 1.34.7+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1766689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724698] [NEW] install failed after giving up on reinstalling packages
Public bug reported: I was using the Kubuntu 17.10 from a couple of days ago to install, written to a USB flash drive, to install 17.10 on my desktop (an attempt at upgrade failed--I was doing other things while the upgrade (from the command line) was preparing packages for installation, and when I returned, I just saw the glowing kubuntu graphic boot display, sitting there and making no progress, so I decided to try a plain install). It spent a long time trying to restore (or perhaps update is the better word?) packages that it saw already installed, and then a pop-up appeared, saying that it couldn't complete that part, and I could just reinstall packages manually after the install completed. I clicked to close that window, and just after that it came up saying the install failed, so I should submit an error report on ubiquity, which I am doing now. /var/log/installer/syslog doesn't exist; attaching /var/log/partman. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.386 CurrentDesktop: KDE Date: Wed Oct 18 17:16:53 2017 LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1724698/+attachment/4975332/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724698 Title: install failed after giving up on reinstalling packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1724698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682978] Re: Random Screen Rotation
Today I grabbed the daily build of 17.10 and booted into it from a USB drive. It still rotates--but at times I can't predict, the screen will blank out and then come back rotated. (Should I create a new bug for 17.10?) I should mention that this happens on my laptop, an HP Pavilion with AMD graphics. On my desktop, which has an Nvidia 960, it doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682978 Title: Random Screen Rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682978] Re: Random Screen Rotation
For me, it's counterclockwise. I tried setting the "lock rotation" option referenced in https://askubuntu.com/questions/874487/ubuntu- gnome-16-10-screen-orientation-spontaneously-changes (had to switch to Unity 8 to find it), but it didn't make a difference when I logged back in under Cinnamon, the windowing environment I usually use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682978 Title: Random Screen Rotation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562238] Re: grub-efi-amd64-siged failed to install
After reporting, I realized I'd forgotten to mark the partition as
bootable. Doing so did not by itself solve the problem.
Contrary to https://help.ubuntu.com/community/UEFI ("Mount point:
/boot/efi (remark: no need to set this mount point when using the manual
partitioning, the Ubuntu installer will detect it automatically)"),
explicitly specifying the mount point let the install proceed without
problem. Perhaps that page could be corrected, and perhaps the installer
could note the absence of an EFI system partition?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562238
Title:
grub-efi-amd64-siged failed to install
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1562238/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1562238] [NEW] grub-efi-amd64-siged failed to install
Public bug reported: I am trying to install 16.04 to use UEFI rather than legacy BIOS. I looked at the instructions and created a 200 MiB FAT32 partition as it said I should. I did not specify a mount point--it said that the installation would cause it to be mounted at /boot/efi. I expected the install to complete without complaint, but instead got (line breaks on the popup window may have caused me to mistranscribe): grub-efi-amd64-signed failed to install into / target/. Without the GRUB bootloader, the installed system will not boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.51 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.368 Date: Fri Mar 25 21:51:51 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.51 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1562238 Title: grub-efi-amd64-siged failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1562238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521024] Re: Upgrade halts with invalid UPS low battery warning
Happened to me when upgrading from 15.10 to 16.04 Beta 2. The UPS battery was fully charged, but during the upgrade the battery icon showed the battery as fully discharged and the computer was shut down before the upgrade completed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521024 Title: Upgrade halts with invalid UPS low battery warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1521024/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found"
While I did not install grub myself, I did put it on the wrong drive, as I noticed when reinstalling. Corrected that (and told it not to install proprietary drivers during the initial install, so it wouldn't try something that didn't (quite) work on a recently acquired 750Ti graphics card and I could see what was going on all through the install), and all was well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found"
Had the same problem this morning. After problems trying to get the 334.21 NVIDIA driver installed on Mint for a new 750Ti card, I decided to just install the Ubuntu 14.04 and then use a PPA with the driver I'd found. The install went smoothly, I *think*. Part way through, the graphics on the screen were stretched vertically so I could no longer see informational messages or prompts; I just hit ENTER once the installation seemed to be done, and the DVD ejected and the system rebooted after I closed the try and hit ENTER again. Everything looked normal until the lines error: symbol `grub_term_highlight_color' not found. grub rescue> appeared. I have NEVER installed grub myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in "error: symbol 'grub_term_highlight_color' not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071808] Re: glabels font selection extremely slow
** Description changed: I am using Ubuntu 12.10 (64-bit), and the glabels version I'm using is 3.0.0-3ubuntu1. I don't believe this is the same bug as #300550, because while I do have quite a few fonts installed, I've not seen this level of slowness until upgrading to 12.10; glabels 3.0.0 does have a new font selection widget. + (UPDATE: just checked my wife's computer. She has a considerable number + of fonts installed, but we haven't upgraded her yet. The 12.04 glabels + took about four or five seconds from click to putting up a list of fonts + to choose from.) When I use glabels and attempt to set the font for a text object, if I choose "Proportional Fonts", "Fixed-width fonts", or "All fonts", glabels takes a very long time to respond. (I can't say just how long, because I typically give up after several minutes.) I suspect it's waiting until it has rendered all those little "Aa" samples before displaying any of the fonts to choose from, but that's just a guess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071808 Title: glabels font selection extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glabels/+bug/1071808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1071808] [NEW] glabels font selection extremely slow
Public bug reported: I am using Ubuntu 12.10 (64-bit), and the glabels version I'm using is 3.0.0-3ubuntu1. I don't believe this is the same bug as #300550, because while I do have quite a few fonts installed, I've not seen this level of slowness until upgrading to 12.10; glabels 3.0.0 does have a new font selection widget. When I use glabels and attempt to set the font for a text object, if I choose "Proportional Fonts", "Fixed-width fonts", or "All fonts", glabels takes a very long time to respond. (I can't say just how long, because I typically give up after several minutes.) I suspect it's waiting until it has rendered all those little "Aa" samples before displaying any of the fonts to choose from, but that's just a guess. ** Affects: glabels (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1071808 Title: glabels font selection extremely slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glabels/+bug/1071808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820485] Re: ubiquity stops installation at 'Configuring target system'
I am seeing this as well; grabbed the i386 ISO yesterday (2011-10-16), and my netbook has been sitting in "Configuring target system" for something like half an hour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820485 Title: ubiquity stops installation at 'Configuring target system' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/820485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518533] Re: Unable to mount location Not Authorized after nautilus upgrade
Strange. After updating and rebooting, I can once again mount the Cowon S9. Attached is the diff between dpkg.log before and dpkg.log after. ** Patch added: "dpkg.log.diff" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/518533/+attachment/1621356/+files/dpkg.log.diff -- Unable to mount location Not Authorized after nautilus upgrade https://bugs.launchpad.net/bugs/518533 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 518533] Re: Unable to mount location Not Authorized after nautilus upgrade
Yesterday this started happening to me. Until then I was able to connect my Cowon S9 and have it mount automatically, but now I get an "Unable to mount COWON S9 Not Authorized" popup. I typically connect it and use gpodder to get current podcast episodes on it each weekday before work, so most likely whatever changed to break it happened between the morning of September 20th around 9:00 a.m. CDT and the morning of September 21st around 9:00 a.m. CDT. I attach /var/log/dpkg.log to show what I installed or upgraded during that interval. ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/518533/+attachment/1621344/+files/dpkg.log -- Unable to mount location Not Authorized after nautilus upgrade https://bugs.launchpad.net/bugs/518533 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 550655] Re: support for Nvidia GT220 is missing
Confirmed; works like a charm. Thank you! -- support for Nvidia GT220 is missing https://bugs.launchpad.net/bugs/550655 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 550655] Re: support for Nvidia GT220 is missing
Make that n; I can't put -1 of something in the file. :) -- support for Nvidia GT220 is missing https://bugs.launchpad.net/bugs/550655 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 550655] Re: support for Nvidia GT220 is missing
So for card #n, n - 1 0x, and then a 0xfff2. Got it; thanks! -- support for Nvidia GT220 is missing https://bugs.launchpad.net/bugs/550655 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 550655] Re: support for Nvidia GT220 is missing
Yes, I added the repository to my sources.list, installed the linux- alsa-driver-modules-2.6.xx-xx that matches the kernel installed on the computer, and added the line options snd-hda-intel enable_msi=0 probe_mask=0x,0xfff2 to /etc/modprobe.d/sound.conf (had to reboot twice; I mistyped enable_msi the first time around). What determines the probe_mask value one should use? The particular graphics card I have is a PNY card, I believe the PNY VCGGT2201XEB-S. -- support for Nvidia GT220 is missing https://bugs.launchpad.net/bugs/550655 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 550655] Re: support for Nvidia GT220 is missing
I made the changes described in comment #6, after disabling the on motherboard graphics/sound, and my system now indeed recognizes the audio device(s) on the GT220 card: $ aplay -l List of PLAYBACK Hardware Devices card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 7: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 8: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 9: NVIDIA HDMI [NVIDIA HDMI] Subdevices: 1/1 Subdevice #0: subdevice #0 $ lspci | grep Audio 02:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) ...but despite all that, no sound coming out of the speakers of the TV my computer is connected to. Have I overlooked something? -- support for Nvidia GT220 is missing https://bugs.launchpad.net/bugs/550655 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 164475] Re: users-admin deletes privileges granted to ADS domain users with the command line utility (adduser)
I can confirm that the problem Antje H. describes is still present in Karmic Koala. -- users-admin deletes privileges granted to ADS domain users with the command line utility (adduser) https://bugs.launchpad.net/bugs/164475 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 420747] Re: ClearWeatherScreenlet.py crashed with TypeError in show_error()
My situation appears to match Mihai's; despite the report, I can still change size, switch format, etc. -- ClearWeatherScreenlet.py crashed with TypeError in show_error() https://bugs.launchpad.net/bugs/420747 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331681] Re: Error initializing camera: -60: Could not lock the device
I'm seeing the same problem (the "Error initializing camera: -60: Could not lock the device") with Jaunty Jackalope beta and a Kodak Z712 IS. Under Intrepid Ibex, it worked like a charm. -- Error initializing camera: -60: Could not lock the device https://bugs.launchpad.net/bugs/331681 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 359620] [NEW] linux kernel 2.6.28-11-generic fails to find /dev/disk/by-uuid/[number] and drops to shell
Public bug reported: I am running Jaunty Jackalope beta, and updated this morning, which apparently included an update to the 2.6.28-11 kernel. When I restarted, the boot failed, with the message ALERT! /dev/disk/by-uuid/cf103646-c12b-4573-89ed-cf0387df4cd8 does not exist. Dropping to a shell! and then I was put in a busybox shell. Rebooting and choosing 2.6.28-3-rt allowed me to boot. Looking at /boot/grub/menu.lst, I see the very same uuid for all choices of Linux kernel. 2.6.28-3-rt found it, 2.6.28-11 did not. I'm not sure why. As the newer kernel gives up long before I can run uuname et al., it is not clear whether the output of the commands listed in the guidelines makes sense. Please let me know if it does, and I will happily attach the output. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 NonfreeKernelModules: nvidia Package: linux-generic 2.6.28.11.14 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta Uname: Linux 2.6.28-3-rt x86_64 ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- linux kernel 2.6.28-11-generic fails to find /dev/disk/by-uuid/[number] and drops to shell https://bugs.launchpad.net/bugs/359620 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 359620] Re: linux kernel 2.6.28-11-generic fails to find /dev/disk/by-uuid/[number] and drops to shell
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25249767/Dependencies.txt -- linux kernel 2.6.28-11-generic fails to find /dev/disk/by-uuid/[number] and drops to shell https://bugs.launchpad.net/bugs/359620 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 299024] [NEW] kompozer crashes when you click on "Format"
Public bug reported: I am using Ubuntu Studio 8.10, 64-bit version. To reproduce the bug: start kompozer, type some text in the new page, highlight it and click "Format". kompozer will crash. ** Affects: kompozer (Ubuntu) Importance: Undecided Status: New -- kompozer crashes when you click on "Format" https://bugs.launchpad.net/bugs/299024 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 213444] [NEW] Hardy Heron beta nfs reports internal error when I attempt to mount with NFS
Public bug reported: Using Ubuntu Studio based on Hardy Heron beta, 64-bit w/AMD Athlon 64 x2. The other computer involved is a 32-bit Sempron running Gutsy Gibbon. I followed instructions on http://czarism.com/easy-peasy-ubuntu- linux-nfs-file-sharing to make a directory on the Gutsy system availalble on the Hardy beta system, and got the following message when I attempted the mount: mount.nfs: internal error I double checked the commands and the IP addresses/ranges involved, and they appear to be correct. At the Gutsy end: nfs-common and nfs-kernel-server are 1:1.1.1~git-20070709-3ubuntu1, portmap is 6.0-1ubuntu1. At the Hardy end: 1:1.1.2-2ubuntu2 and 6.0-4 for the same packages, respectively. ** Affects: ubuntu Importance: Undecided Status: New -- Hardy Heron beta nfs reports internal error when I attempt to mount with NFS https://bugs.launchpad.net/bugs/213444 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 51991] Re: Xorg process freezes, uses 100% of CPU. Can be killed by remote terminal.
I have a homebrew system with Sempron 2400+ 512 MB RAM 160 GB hard drive ECS KT600A motherboard I had difficulties with the nVidia MX400 AGP graphics card I was using, and upgraded to an MX4000 card. (This was with Breezy Badger.) I then started to have the bug reported here: display locks, x.org uses 99+% of the CPU, keyboard unresponsive, the mouse cursor still moves, but the system can be accessed via ssh and x.org killed. Using the nv driver corrected the problem, but gave lousy graphics performance. I switched to an ATI card, but couldn't get decent performance from it. I switched back to the MX400 card. I now run Dapper Drake. I recalled that I have an MX4000 PCI card that I could try... and installed it and switched to it. I got glx to work...and boom. After a bit of trying out the GL screensavers to check that they were working nicely, I went on to do some other stuff and bang... the screen froze, but the mouse could still move. This time it was slightly different: after about five minutes or so delay, x.org finally paid attention to ctrl-alt-bs and restarted. If you look on the nvidia Linux forum you will find that people have had this problem with the nvidia proprietary driver for YEARS. See http://www.nvnews.net/vbulletin/showthread.php?t=31858 and http://www.nvnews.net/vbulletin/showthread.php?t=73231 for more info. I have another system with an Athlon 2100, and a K7S5A motherboard. I used the MX4000 card that made the KT600A system freeze...and had no trouble whatsoever. That system now runs Dapper Drake just fine. (OK, compiz dies on it, but compiz is still highly experimental. If I go back to metacity, all is well.) -- Xorg process freezes, uses 100% of CPU. Can be killed by remote terminal. https://launchpad.net/bugs/51991 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
