[Bug 1956169] Re: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage
As a final check, I reinstalled the package again. Now apt is finding it properly: $ sudo apt-get reinstall libvirt-dev [sudo] password for trinitronx: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 54 not upgraded. Need to get 161 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 libvirt-dev amd64 6.0.0-0ubuntu8.15 [161 kB] Fetched 161 kB in 1s (201 kB/s) (Reading database ... 563591 files and directories currently installed.) Preparing to unpack .../libvirt-dev_6.0.0-0ubuntu8.15_amd64.deb ... Unpacking libvirt-dev:amd64 (6.0.0-0ubuntu8.15) over (6.0.0-0ubuntu8.15) ... Setting up libvirt-dev:amd64 (6.0.0-0ubuntu8.15) ... So it's safe to close this bug. The system was missing universe & multiverse components under the focal-updates pocket, as you suspected. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956169 Title: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1956169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956169] Re: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage
Hmm... yes it seems like universe & multiverse pockets are enabled on this system for main and focal-security. However, it does have debug packages enabled for focal-updates via ddebs.list: $ grep -ri '^deb.*ubuntu\.com' /etc/apt/sources.list* | sort | uniq /etc/apt/sources.list.d/ddebs.list:deb http://ddebs.ubuntu.com focal main restricted universe multiverse /etc/apt/sources.list.d/ddebs.list:deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse /etc/apt/sources.list.d/ddebs.list:deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu focal main restricted /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu focal multiverse /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu focal universe /etc/apt/sources.list:deb http://archive.ubuntu.com/ubuntu focal-updates main restricted /etc/apt/sources.list:deb http://security.ubuntu.com/ubuntu focal-security main restricted universe multiverse /etc/apt/sources.list:deb-src http://archive.ubuntu.com/ubuntu focal-updates main /etc/apt/sources.list:deb-src http://security.ubuntu.com/ubuntu focal-security main restricted universe multiverse I guess that I didn't realize the libvirt-dev package was released in a separate pocket / channel than the other libvirt packages. I've enabled both universe & multiverse for the focal-updates pocket too. Now it's showing up under apt-cache policy: $ apt-cache policy libvirt-dev libvirt-dev: Installed: 6.0.0-0ubuntu8.15 Candidate: 6.0.0-0ubuntu8.15 Version table: *** 6.0.0-0ubuntu8.15 500 500 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 6.0.0-0ubuntu8.3 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 6.0.0-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956169 Title: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1956169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 759725] Re: The kernel is no longer readable by non-root users
The "statoverride" script appears to work on the first run for each kernel. However, any subsequent times the `dpkg-statoverride` command exits with errorcode 2: $ apt-get install something-triggering-dkms Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-96-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic /etc/kernel/postinst.d/statoverride: dpkg-statoverride: error: an override for '/boot/vmlinuz-5.4.0-96-generic' already exists; aborting run-parts: /etc/kernel/postinst.d/statoverride exited with return code 2 dpkg: error processing package linux-image-5.4.0-96-generic (--configure): installed linux-image-5.4.0-96-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-5.4.0-96-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Adding the `--force-statoverride-add` flag fixed the issue: #!/bin/sh # https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 set -e version="$1" if [ -z "$version" ]; then exit 0 fi exec dpkg-statoverride --force-statoverride-add --update --add root root 0644 "/boot/vmlinuz-${version}" After that change, now the kernel dkms trigger succeeds: Setting up linux-image-5.4.0-96-generic (5.4.0-96.109) ... Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.4.0-96-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-96-generic /etc/kernel/postinst.d/statoverride: dpkg-statoverride: warning: an override for '/boot/vmlinuz-5.4.0-96-generic' already exists, but --force specified so will be ignored /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-96-generic Found initrd image: /boot/initrd.img-5.4.0-96-generic Found linux image: /boot/vmlinuz-5.4.0-94-generic Found initrd image: /boot/initrd.img-5.4.0-94-generic Found linux image: /boot/vmlinuz-5.4.0-91-generic Found initrd image: /boot/initrd.img-5.4.0-91-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin Found Ubuntu 20.04.3 LTS (20.04) on /dev/md126p1 done If this is to be added as a postinst.d to the libguestfs-tools package, please don't forget the `--force-statoverride-add` flag... or else we introduce a new dkms / kernel postinst.d trigger idempotency bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956169] Re: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage
I was able to verify that "Depends: " line for libvirt-dev should work based on the source package. Testing a local 'debuild' of libvirt packages seems to work and produced: libvirt-dev_6.0.0-0ubuntu8.15_amd64.deb Build + Sign + Install on my local machine provided a workaround for the missing package. Maybe this was just a missed upload to focal-updates/main repo on last official build? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956169 Title: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1956169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956169] [NEW] Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage
Public bug reported: It looks like libvirt-dev package "Depends:" line needs an update after the libvirt0 package update from focal-updates: $ sudo apt-get install libvirt-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libvirt-dev : Depends: libvirt0 (= 6.0.0-0ubuntu8.3) but 6.0.0-0ubuntu8.15 is to be installed E: Unable to correct problems, you have held broken packages. Trying to upgrade packages does not currently work due to the "Depends: =6.0.0-0ubuntu8.3" version lock on libvirt-dev package: $ sudo apt-get update -qq $ sudo apt-get upgrade libvirt-dev libvirt0 libxen-dev Reading package lists... Done Building dependency tree Reading state information... Done libvirt0 is already the newest version (6.0.0-0ubuntu8.15). libvirt0 set to manually installed. Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libvirt-dev : Depends: libvirt0 (= 6.0.0-0ubuntu8.3) but 6.0.0-0ubuntu8.15 is to be installed E: Broken packages $ sudo apt-cache policy libvirt-dev libvirt0 libxen-dev libvirt-dev: Installed: (none) Candidate: 6.0.0-0ubuntu8.3 Version table: 6.0.0-0ubuntu8.3 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 6.0.0-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages libvirt0: Installed: 6.0.0-0ubuntu8.15 Candidate: 6.0.0-0ubuntu8.15 Version table: *** 6.0.0-0ubuntu8.15 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 6.0.0-0ubuntu8.3 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 6.0.0-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages libxen-dev: Installed: (none) Candidate: 4.11.3+24-g14b62ab3e5-1ubuntu2 Version table: 4.11.3+24-g14b62ab3e5-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages Maintainers: Please update libvirt-dev headers package to match the current version of libvirt0: 6.0.0-0ubuntu8.15 $ dpkg -l libvirt0 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii libvirt0:amd64 6.0.0-0ubuntu8.15 amd64library for interfacing with different virtualization systems Cheers! ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956169 Title: Cannot install libvirt-dev on Ubuntu 20.04 / focal Dependency conflict - needs repackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1956169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217585] Re: System hangs after some time with nouveau and GT240
It appears the same crash symptoms are still happening on Ubuntu 20.04 with xserver-xorg-video-nouveau package and Nvidia GT240 chipset. Details in Launchpad bug #1954335 - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1954335 Package version: $ dpkg -l xserver-xorg-video-nouveau | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==--- ii xserver-xorg-video-nouveau 1:1.0.16-1 amd64X.Org X server -- Nouveau display driver See linked duplicate bug #1954335 for journalctl crash logs, lspci & lshw output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217585 Title: System hangs after some time with nouveau and GT240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1217585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954335] Re: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install
*** This bug is a duplicate of bug 1217585 *** https://bugs.launchpad.net/bugs/1217585 ** This bug has been marked a duplicate of bug 1217585 System hangs after some time with nouveau and GT240 ** Tags added: amd64 ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954335 Title: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1954335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954335] [NEW] nouveau driver frequently freezing / crashing kernel on fresh 20.04 install
*** This bug is a duplicate of bug 1217585 *** https://bugs.launchpad.net/bugs/1217585 Public bug reported: Hello, I'm experiencing frequent crashes that hard-lock the system and kernel completely. Symptoms are: - Frozen screen - No Keyboard or Mouse input accepted - Remote SSH times out as if system is not responding - Kernel does not respond to the "Alt + SysRq + REISUB" key sequence to force a reboot. (kernel was compiled with CONFIG_MAGIC_SYSRQ=y) I tracked down the issue to the nouveau driver (see attached journalctl logs for crash dump) The primary and only PCI Video card in the system is quite old and thus should be well supported: - 01:00.0 VGA compatible controller: NVIDIA Corporation GT215 [GeForce GT 240] (rev a2) lshw output: $ sudo lshw -class display *-display description: VGA compatible controller product: GT215 [GeForce GT 240] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nouveau latency=0 resources: irq:166 memory:ee00-eeff memory:d000-dfff memory:e000-e1ff ioport:e000(size=128) memory:c-d ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl logs from last nouveau crash" https://bugs.launchpad.net/bugs/1954335/+attachment/5546522/+files/2021-12-09-nouveau-kernel-crashbug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954335 Title: nouveau driver frequently freezing / crashing kernel on fresh 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1954335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507170] Re: hfsprogs in Ubuntu 20.04 LTS is very old (2009s), please update to latest 641 release
> I have updated the Debian package to version 540.1.linux3-1 now which is used by Fedora, openSUSE and other distributions. @glaubitz - Excellent! Thanks for your hard work porting this over! > Great! This was synced automatically and built in the current Ubuntu development release, hirsute. @hjd - Great news! I've also just backported this for Focal 20.04 into a PPA: https://launchpad.net/~trinitronx/+archive/ubuntu/hfsprogs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507170 Title: hfsprogs in Ubuntu 20.04 LTS is very old (2009s), please update to latest 641 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hfsprogs/+bug/1507170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797890] Re: Enhancement-Kindle fire HD 8
After testing out the newer version of libmtp v1.1.18, I was able to get even the current version of Calibre working (as long as I unmounted the device from Nautilus / GVFS first!) Here is the initial error if the device is already automounted by GVFS: Device 0 (VID=1949 and PID=0581) is a Amazon Kindle Fire HD8 Plus. libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device Error while trying to open MTPDevice(busnum=1, devnum=36, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX') (Driver: ) Traceback (most recent call last): File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open self.dev = self.create_device(connected_device) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id, libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=36, tried 1 such devices During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/calibre/calibre/gui2/device.py", line 297, in detect_device dev.open(cd, self.current_library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 125, in open BASE.open(self, device, library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 221, in open raise OpenFailed('Failed to open %s: Error: %s'%( calibre.devices.errors.OpenFailed: Failed to open MTPDevice(busnum=1, devnum=36, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX'): Error: Unable to open MTP device with busnum=1 and devnum=36, tried 1 such devices Device 0 (VID=1949 and PID=0581) is a Amazon Kindle Fire HD8 Plus. libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device Error while trying to open MTPDevice(busnum=1, devnum=37, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX') (Driver: ) Traceback (most recent call last): File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open self.dev = self.create_device(connected_device) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id, libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=37, tried 1 such devices During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/calibre/calibre/gui2/device.py", line 297, in detect_device dev.open(cd, self.current_library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 125, in open BASE.open(self, device, library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 221, in open raise OpenFailed('Failed to open %s: Error: %s'%( calibre.devices.errors.OpenFailed: Failed to open MTPDevice(busnum=1, devnum=37, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX'): Error: Unable to open MTP device with busnum=1 and devnum=37, tried 1 such devices Reference: https://sourceforge.net/p/libmtp/bugs/1879/#5c37 To work around Ubuntu's GVFS automount behavior: - Open Nautilus - Find your device's product ID name in the mounted filesystems list - Click the Eject button - Now open Calibre After making sure only Calibre is managing the MTP device, it works fine! Resolution: Update to libmtp >= 1.1.18 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797890 Title: Enhancement-Kindle fire HD 8 To manage notifications about this bug go to: https://bugs.launchpad.net/calibre/+bug/1797890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797890] Re: Enhancement-Kindle fire HD 8
Same issue observed in calibre 4.99.4+dfsg+really4.12.0-1build1 on Focal 20.04 LTS with Kindle Fire HD 8 plus (10th generation) Following the guide here seems to help: https://manual.calibre- ebook.com/faq.html#android-usb If you miss or can't find the USB notification by swiping down: - Swipe down from top of the device's screen - Swipe down again to expand the system control widgets (WiFi, Bluetooth, etc...) - Tap the Gear icon in the lower right to open Settings (OR just tap "Settings" icon from the device's homescreen) - Tap "Connected Devices" - Tap "USB" - Under "Use USB for", tap "File Transfer" Note: When trying to switch "USB controlled by" to "Connected device", it did not seem to work and just says "Couldn't switch". After enabling File Transfer mode, the device was mounted under an unusual path (when compared to most standard USB mass storage devices): /run/user/1000/gvfs/mtp:host=Amazon_XX_/Internal storage The device's product ID and serial number should be listed in place of the X's. After doing this, I opened up Calibre via the command line. It threw this exception error: Device 0 (VID=1949 and PID=0581) is UNKNOWN in libmtp v1.1.17. Please report this VID/PID and the device model to the libmtp development team error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device Error while trying to open MTPDevice(busnum=1, devnum=35, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX') (Driver: ) Traceback (most recent call last): File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open self.dev = self.create_device(connected_device) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id, libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=35, tried 1 such devices During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/calibre/calibre/gui2/device.py", line 297, in detect_device dev.open(cd, self.current_library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 125, in open BASE.open(self, device, library_uuid) File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer return func(self, *args, **kwargs) File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 221, in open raise OpenFailed('Failed to open %s: Error: %s'%( calibre.devices.errors.OpenFailed: Failed to open MTPDevice(busnum=1, devnum=35, vendor_id=6473, product_id=1409, bcd=547, serial='', manufacturer='Amazon', product='XX'): Error: Unable to open MTP device with busnum=1 and devnum=35, tried 1 such devices So in this case it appears to be an error caused by an unrecognizable device in the current version of libmtp: Device 0 (VID=1949 and PID=0581) is UNKNOWN in libmtp v1.1.17. The packages in Ubuntu's official repository are probably due for an update. Updating libmtp would probably enable many new devices to work under Ubuntu. Calibre is currently at version: 5.6.0 libmtp is currently at 1.1.18 ** Changed in: calibre Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797890 Title: Enhancement-Kindle fire HD 8 To manage notifications about this bug go to: https://bugs.launchpad.net/calibre/+bug/1797890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797890] Re: Enhancement-Kindle fire HD 8
** Also affects: calibre (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/1797890 Title: Enhancement-Kindle fire HD 8 To manage notifications about this bug go to: https://bugs.launchpad.net/calibre/+bug/1797890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329389] Re: "Party mode" ununderstandable and undocumented
** Changed in: rhythmbox (Ubuntu) Status: Triaged => In Progress ** Changed in: rhythmbox (Ubuntu) Assignee: (unassigned) => James Cuzella (trinitronx) ** Changed in: hundredpapercuts Assignee: (unassigned) => James Cuzella (trinitronx) ** Changed in: hundredpapercuts Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329389 Title: "Party mode" ununderstandable and undocumented To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329389] Re: "Party mode" ununderstandable and undocumented
** Branch linked: lp:~trinitronx/rhythmbox/fix-party-mode-docs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329389 Title: "Party mode" ununderstandable and undocumented To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329389] Re: "Party mode" ununderstandable and undocumented
Attaching upstream patch with fixed conflicts & updated date ** Patch added: "Upstream Patch from https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/59; https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/329389/+attachment/5376164/+files/0001-Fixes-701-Apply-documentation-patch-for-Party-Mode.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329389 Title: "Party mode" ununderstandable and undocumented To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 329389] Re: "Party mode" ununderstandable and undocumented
I was able to find that this was documented upstream in patch for Gnome bug #572651 Source: https://bugzilla.gnome.org/show_bug.cgi?id=572651 I've applied the patch, fixed the failing patch hunks and created a merge request (GitLab's version of pull request) here: https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/59 Fixes #329389 ** Bug watch added: bugzilla.gnome.org/ #572651 https://bugzilla.gnome.org/show_bug.cgi?id=572651 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/329389 Title: "Party mode" ununderstandable and undocumented To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872402] [NEW] drobo-utils out of date - "No Drobos detected" for newer models of Drobo
Public bug reported: drobo-utils package is out of date with upstream. Ubuntu version: 0.6.1+repack-2 Upstream version: 0.6.2.2 This project needs to be updated to support newer Drobo models with vendor string "Drobo". Older models have a different string "Data Robotics". Details can be found here: http://drobo-utils.sourceforge.net/#no-drobos-discovered Running the following command will result in "No Drobos discovered": $ sudo drobom -v 16 status examining: /dev/sdh id: (15, 0, 0, 0, 'Drobo\x00\x00\x00') rejected: vendor is Drobo (not from DRI) examining: /dev/sdi id: (15, 0, 0, 1, 'Drobo\x00\x00\x00') rejected: vendor is Drobo (not from DRI) returning list: [] No Drobos discovered Updating the package to the pre-built one from SourceForge adds support for newer models of Drobo. https://sourceforge.net/projects/drobo-utils/files/ Confirmed working on Ubuntu 18.04 LTS (bionic)! Running same command after updating drobo-utils to latest works: $ sudo drobom -v 16 status examining: /dev/sda [...SNIP...] examining: /dev/sdh id: (15, 0, 0, 0, 'Drobo\x00\x00\x00') found a Drobo appending new lundevs to devices: [['/dev/sda'], ['/dev/sdb'], ['/dev/sdc'], ['/dev/sdd'],['/dev/sde'], ['/dev/sdf'], ['/dev/sdg']] examining: /dev/sdi id: (15, 0, 0, 1, 'Drobo\x00\x00\x00') found a Drobo appending to lundevs... returning list: [['/dev/sda'], ['/dev/sdb'], ['/dev/sdc'], ['/dev/sdd'], ['/dev/sde'], ['/dev/sdf'], ['/dev/sdg'], ['/dev/sdh', '/dev/sdi']] trying: ['/dev/sda'] trying: ['/dev/sdb'] [...SNIP...] trying: ['/dev/sdh', '/dev/sdi'] cfg: (6, 16, 17592186044416) settings: (1586734106, 8, 'Drobo') found [['/dev/sdh', '/dev/sdi']] cfg: (6, 16, 17592186044416) settings: (1586734106, 8, 'Drobo') /dev/sdh:/dev/sdi /media/Drobo:/media/DroboTimeMachineBackups Drobo 94% full - (['Yellow alert'], 0) ** Affects: drobo-utils (Ubuntu) Importance: Undecided Status: New ** Summary changed: - drobo-utils + drobo-utils out of date - "No Drobos detected" for newer models of Drobo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872402 Title: drobo-utils out of date - "No Drobos detected" for newer models of Drobo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drobo-utils/+bug/1872402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661523] Re: droboview can't retrieve diagnostics from device
The current package version in Ubuntu 16.04 is: 0.6.1+repack-2 Unfortunately it lacks the support for newer Drobo models with vendor id: "Drobo". Older Drobo models have vendor string "Data Robotics", which this version of drobo-utils does not know how to identify still as of 0.6.1+repack-2 Debian package. The upstream project has a prebuilt .deb package with version 0.6.2.2 with support for newer Drobo models: https://sourceforge.net/projects/drobo-utils/ This project's package needs to be updated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661523 Title: droboview can't retrieve diagnostics from device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drobo-utils/+bug/661523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507170] Re: hfsprogs in Ubuntu is very old (2009 release), please update to latest 576 release
@hjd: Thanks for the quick response! As you pointed out, it looks like the upstream bug report has more info and discussion here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765104 So far, no movement since February 2019 from the maintainer and some offers of help from others in maintaining it. I guess we can hope that it can be picked up by another maintainer or two that have some time to do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507170 Title: hfsprogs in Ubuntu is very old (2009 release), please update to latest 576 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hfsprogs/+bug/1507170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49052] Re: no hfs+ journal write support by default (gets mounted as read only)
Still seems to be an issue in modern Ubuntu 18.04.4 bionic LTS. The upstream Apple source for HFS+ projects can be found here: https://opensource.apple.com/source/hfs/ https://opensource.apple.com/source/diskdev_cmds/ Debian package for hfsprogs seems woefully out of date (based on macOS 10.4 diskdev_cmds from ~6 years ago) Also see Launchpad bug #1507170 https://bugs.launchpad.net/ubuntu/+source/hfsprogs/+bug/1507170 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/49052 Title: no hfs+ journal write support by default (gets mounted as read only) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/49052/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507170] Re: hfsprogs in Ubuntu is very old (2009 release), please update to latest 576 release
PING! Any plans for movement on updating this package? Is this package mainly imported from upstream (Debian) ? How can I verify which version of the "diskdev_cmds" project is used on modern macOS? Current macOS version 10.15.4 has binary "fsck_hfs" from "hfs-522.100.5". As evidenced by: strings $(which fsck_hfs ) | grep PROJECT: @(#)PROGRAM:fsck_hfs PROJECT:hfs-522.100.5 However, I'm only seeing up to version 522.0.9 here: https://opensource.apple.com/source/hfs/ It sounds like this particular set of tools, fsck.hfs[plus] & mkfs.hfs[plus], were sourced originally from diskdev_cmds project ( https://opensource.apple.com/source/diskdev_cmds/ ). I'm a bit confused as to whether current Apple macOS even uses the "diskdev_cmds" project at all. Searching their binaries for "PROJECT:diskdev_cmds" yields no results: OLDIFS="$IFS"; IFS=':'; for p in $PATH; do sudo find "$p" -type f -print0 | sudo xargs -0 strings | grep PROJECT: ; done | sort | uniq | grep -i diskdev ; IFS="$OLDIFS" # No results! # Tip: taking off the last '| grep -i diskdev' command from the pipe shows *all* current project versions of macOS command line utilities ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507170 Title: hfsprogs in Ubuntu is very old (2009 release), please update to latest 576 release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hfsprogs/+bug/1507170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580605] Re: gnome-shell crashes often
@fermulator: It looks like it's likely to be https://en.wikipedia.org/wiki/GDK $ sudo find /usr/ -iname 'libgdk-3.so*' -exec dpkg -S '{}' \; libgtk-3-dev:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so libgtk-3-0:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 libgtk-3-0:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0.2200.25 So library filename is "libgdk-3.so.*" while package which owns it is "libgtk-3-0*" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580605 Title: gnome-shell crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1580605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580605] Re: gnome-shell crashes often
So due to differing stacktrace here, I think #911591 is likely a different issue than this one. Different stack library means different codepath. @fermulator: Does seem a bit odd at first glance... does gnome-shell use .NET or C# (gdk-sharp)? libgdk3.0 is a valid package name in Ubuntu, but descriptions all mention it has to do with implementing a .NET interface for GTK+ 3.0 toolkit. URL Homepage for package is: http://www.mono-project.com/GtkSharp Here is package info: $ apt-cache search libgdk libgdk-pixbuf2.0-0 - GDK Pixbuf library libgdk-pixbuf2.0-bin - GDK Pixbuf library (thumbnailer) libgdk-pixbuf2.0-common - GDK Pixbuf library - data files libgdk-pixbuf2.0-dev - GDK Pixbuf library (development files) libgdk-pixbuf2.0-doc - GDK Pixbuf library (documentation) libg3d-plugin-gdkpixbuf - plugin for the LibG3D library libgdk3.0-cil - CLI binding for GDK 3 libgdk3.0-cil-dev - CLI binding for GDK 3 $ apt-cache show libgdk3.0 Package: libgdk3.0-cil Architecture: amd64 Version: 2.99.3-2 Priority: optional Section: universe/cli-mono Source: gtk-sharp3 Origin: Ubuntu Maintainer: Ubuntu DevelopersOriginal-Maintainer: Debian CLI Libraries Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 412 Depends: cli-common (>= 0.5.1), libcairo1.10-cil (>= 2.99.3), libgdk-pixbuf2.0-0 (>= 2.31.1), libgio3.0-cil (>= 2.99.3), libglib2.0-0 (>= 2.43.1), libglib3.0-cil (>= 2.99.3), libgtk-3-0 (>= 3.12.2), libmono-corlib4.5-cil (>= 3.2.8), libpango3.0-cil (>= 2.99.3) Filename: pool/universe/g/gtk-sharp3/libgdk3.0-cil_2.99.3-2_amd64.deb Size: 84008 MD5sum: 4dc47424652bae431389710a6f5628d4 SHA1: f7960a7eb72c28ff5a9352dd603b087991809f7b SHA256: c00f0ad60a8e2c95a819ebb957b77cbdabacefb4dfcef990995db2507408d5bd Homepage: http://www.mono-project.com/GtkSharp Description-en: CLI binding for GDK 3 This package provides the gdk-sharp assembly that allows CLI (.NET) programs to use the GDK 3 library. . GTK# 3.0 is a CLI (.NET) language binding for the GTK+ 3.0 toolkit and related libraries. Description-md5: 1d11935b917caa88ff30761d32191467 Task: edubuntu-desktop-gnome Package: libgdk3.0-cil-dev Architecture: amd64 Version: 2.99.3-2 Priority: optional Section: universe/cli-mono Source: gtk-sharp3 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian CLI Libraries Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 258 Depends: libgdk3.0-cil (= 2.99.3-2), libglib3.0-cil-dev (= 2.99.3-2) Suggests: monodoc-gtk3.0-manual Conflicts: libgtk3.0-cil-dev (<< 2.99.3~) Replaces: libgtk3.0-cil-dev (<< 2.99.3~) Filename: pool/universe/g/gtk-sharp3/libgdk3.0-cil-dev_2.99.3-2_amd64.deb Size: 24638 MD5sum: fb72153afddcc335faf6bea1c7cb7b7b SHA1: 909a16bf9235a9f8484988140e1b1b40909de86a SHA256: c3d1d7eaa30cb7592d7d38903b23eb210e073f22e75012fefab45d22821597f6 Homepage: http://www.mono-project.com/GtkSharp Description-en: CLI binding for GDK 3 This package provides the gdk-sharp assembly that allows CLI (.NET) programs to use the GDK 3 library. . GTK# 3.0 is a CLI (.NET) language binding for the GTK+ 3.0 toolkit and related libraries. . This package contains development files for the gdk-sharp library, and should be used for compilation. Description-md5: 495b937caf517f4282e86d91fa1f1552 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580605 Title: gnome-shell crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1580605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
@dino99 Happy to open a new bug report on this, as it still appears to be an issue in latest Ubuntu 17.10. Usually when reporting bugs, I opt to prefer adding information to an existing bug report that I have high confidence describes the problem I am seeing. I believe this helps to reduce creating many duplicates and to focus community effort on resolving the main underlying problem rather than bug report management overhead from many duplicates or "me too" comments with no helpful debug info. If this is not preferred on this project, or for some reason doesn't fit the developer bug triage process here, that's fine. I'm happy to add information upstream or in another LaunchPad bug. Back to this problem: As it is a segfault reported in upstream gnome-shell which has something to do with OpenGL + resize behavior, I don't believe borked settings are the issue, nothing I've seen yet points towards that, although it'd be nice if the problem could be resolved by a config change instead of code change. This system never had any gnome-shell installed because Unity was there instead. Therefore, no pre-existing gnome-shell configuration can be hanging around. I've posted to upstream bug, but some info was here. To clarify: I do not have an Nvidia optimus nor do I use noveau, but use older nvidia-340 binary drivers. This is the nvidia recommended set of drivers for my card. Another comment in the upstream report mentions the issue may not have as much to do with Nvidia as it does with Xrandr fast video mode changes. I have confirmed this behavior in my own testing, and have a reproduction test case that works pretty reliably for me: Reproduction Command: # Use output and modes that are valid for you... xrandr --output HDMI-0 --mode 1920x1080 ; xrandr --output HDMI-0 --mode 1920x1080 ; xrandr --output HDMI-0 --mode 800x600 ; xrandr --output HDMI-0 --mode 1920x1080 I've tested this a couple times and it looks like I am able to trigger the crash just with fast xrandr commands. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
At first glance, bug may be related to this upstream: https://bugzilla.gnome.org/show_bug.cgi?id=768204 ** Bug watch added: GNOME Bug Tracker #768204 https://bugzilla.gnome.org/show_bug.cgi?id=768204 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580605] Re: gnome-shell crashes often
I've added more details for the crash I am seeing in this bug: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580605 Title: gnome-shell crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1580605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
Adding journalctl logs for gnome-shell crash. After segfault line, gnome-shell crashes and I'm returned to gdm login screen. Once I login, everything works again until next crash, usually caused by OpenGL window resizing or xrandr resolution changes. ** Attachment added: "gnome-shell-crash.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+attachment/5016779/+files/gnome-shell-crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
Bug seems to be reported also elsewhere: - ArchLinux: https://bbs.archlinux.org/viewtopic.php?id=231158 - RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1250128 The RHEL bug report mentions that they have Xorg configured without RandR support. I do see a message in my logs that says gdm has RandR disabled for some reason: Nov 30 15:25:53 saturn /usr/lib/gdm3/gdm-x-session[3918]: (--) RandR disabled I'm not sure why gdm wants to run with it disabled. I don't seem to have a /etc/X11/xorg.conf file anymore... it's been quite some time since I've even had to edit Xorg config in recent Ubuntu versions. Seems like all this is managed by gdm-x-session now? ** Bug watch added: Red Hat Bugzilla #1250128 https://bugzilla.redhat.com/show_bug.cgi?id=1250128 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
As original reporter stated, it usually appears related to OpenGL window resize events. I have also noted that xrandr display resolution changes can trigger the crash. I see errors in dmesg that mention libmutter: [15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp 7ffeccf94a38 error 4 in libmutter-1.so.0.0.0[7f327f243000+142000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580605] Re: gnome-shell crashes often
I am seeing gnome-shell crashes also. However, it usually appears related to OpenGL window resize events as well as xrandr display resolution changes. Errors in dmesg mention libmutter: [15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp 7ffeccf94a38 error 4 in libmutter-1.so.0.0.0[7f327f243000+142000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580605 Title: gnome-shell crashes often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1580605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 911591] Re: gnome-shell crashes when resizing OpenGL window
I can confirm this bug is still happening on: Ubuntu 17.10 (Artful Aardvark) gnome-shell 3.26.1-0ubuntu5 ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/911591 Title: gnome-shell crashes when resizing OpenGL window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670959] Re: systemd-resolved using 100% CPU
Christian: I've tried as I believe you have asked. When in the bad case (I comment out the line: DNSMASQ_EXCEPT=lo and then reboot): - Running this did not resolve the issue: `sudo resolvconf -a lo.dnsmasq` - Running this did not resolve the issue: `echo "nameserver 127.0.0.1" | /sbin/resolvconf -a lo.dnsmasq` So far only the DNSMASQ_EXCEPT=lo line in /etc/default/dnsmasq appears to resolve the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670959] Re: systemd-resolved using 100% CPU
Maybe interesting things to note: 1. When in bad state: - The mentioned ENV var change in /etc/default/dnsmasq and `sudo systemctl restart dnsmasq` immediately resolves the issue 2. When in good state: - Commenting out the ENV var and running `sudo systemctl restart dnsmasq` does not immediately re-cause the issue - After a reboot, the bad state can be observed again (systemd-resolved using 100% of a CPU core) Maybe there is an order of operations thing here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670959] Re: systemd-resolved using 100% CPU
Also seeing this issue in Ubuntu 17.10 (artful) with: dnsmasq-base 2.78-1 systemd 234-2ubuntu12.1 I can confirm that following https://askubuntu.com/a/968309/ resolves the issue! Steps to fix the issue: Added this line to /etc/default/dnsmasq: DNSMASQ_EXCEPT=lo Then restarting dnsmasq: sudo systemctl daemon-reload sudo systemctl restart dnsmasq No more systemd-resolved taking 99-100% of a CPU core! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1670959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 285392] Re: Softreset failed (device not ready)
Since the bug-watch-updater updated this... Just want to make it clear that I was no longer seeing this problem since 16.04. Since then I've upgraded multiple times, and even swapped the motherboard and a lot of hardware out. Still no recurrence of the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/285392 Title: Softreset failed (device not ready) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (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/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1487666] Re: non-fatal error right after login (just upgraded the kernel to 4.1)
After trying to build a different kernel module on Ubuntu 17.04 (Zesty), I can replicate these errors. The first "error" isn't really an error unless the echo statements are triggered if the "test" command fails: test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( [...SNIP...] ) Notice in the part with parentheses that each line is prefixed by: echo >&2 " ... " This behavior of GNU Make is normal. It will print back the commands it runs unless told not to. If you saw this message without 'echo >&2' in front, it would immediately exit afterwards with a message like: make: *** [all] Error 1 This "test -e [...]" command is checking that the mentioned files exist within the Linux Kernel source directory. This directory is mentioned above when Make changes into it: "/usr/src/linux- headers-4.1.0-040100rc2-generic" The two files it is checking exist are therefore: /usr/src/linux-headers-4.1.0-040100rc2-generic/include/generated/autoconf.h # AND: /usr/src/linux-headers-4.1.0-040100rc2-generic/include/config/auto.conf You can look for these files yourself to make sure they exist. If so, this particular output from Make can be ignored. If they don't exist, then you can usually follow the instructions for running "make oldconfig && make prepare" within the Linux Kernel source directory to create them. The second error message you are getting looks like the real one: make[1]: *** No rule to make target 'arch/x86/syscalls/syscall_32.tbl', needed by 'arch/x86/syscalls/../include/generated/asm/syscalls_32.h'. Stop. arch/x86/Makefile:181: recipe for target 'archheaders' failed make: *** [archheaders] Error 2 This error is listed around the Internet surrounding building Linux Kernel modules on Debian (and Fedora) against Linux Kernel source that is missing "syscalls_32.tbl" and "syscalls_32.h" files. These files should exist in the "Vanilla" Linux Kernel source code which can always be found at kernel.org. However, it appears that some distributions such as Debian and Ubuntu are missing these files in their newer "linux-headers-*" packages. This appears to be a packaging bug which can be filed against "linux- headers-*" package. The "linux-headers" packages should include these files in order to build kernel modules using them. The workaround is to get a full copy of the appropriate version of the Linux Kernel source tree by whatever means, and to use this directory to build your modules against. Note that I'm answering this question based on my personal experience with the linux-headers-4.10.0-37-generic package on Ubuntu 17.04 "Zesty Zapus". I'm under the assumption that this file has been missing from the "linux-headers-*" packages for a while now based on the many instances of people running into this error since 2013 posted on the internet. If you can somehow locate the "syscalls_32.tbl" and "syscalls_32.h" files within your /usr/src/linux-headers-4.1.0-040100rc2-generic/ directory, then you should check the bbswitch module's source directory Makefile. Sometimes the way an external Kernel Module's Makefile is written prevents it from finding the right linux-headers or /lib/modules/ directory during build.Other solutions have been posted for changing the way GNU Make is finding the Linux Source directory and the Kernel Module's working directory usually with $$(PWD) or $(shell $PWD). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1487666 Title: non-fatal error right after login (just upgraded the kernel to 4.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1487666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608208] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
unity-scope-virtualbox seems not to affect this bug, but was in my list so I removed it just to be safe. To restore Unity virtualbox search support, reinstall it: sudo apt-get -y install unity-scope-virtualbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608208 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1608208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619996] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1608208 *** https://bugs.launchpad.net/bugs/1608208 Duplicate of Bug #1608208. Please remove all old virualbox packages prior to virtualbox 5 installation. See Bug #1608208 for more detailed commands to run. ** This bug has been marked a duplicate of bug 1608208 package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619996 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1619996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629882] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1608208 *** https://bugs.launchpad.net/bugs/1608208 Duplicate of Bug #1608208. Please remove all old virtualbox packages prior to installation of virtualbox 5. See Bug #1608208 for more detailed commands to run if you need help. ** This bug has been marked a duplicate of bug 1608208 package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629882 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1629882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708315] Re: package virtualbox-guest-utils-hwe 5.0.40-dfsg-0ubuntu1.16.04.1~16.04.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Possible duplicate of Bug #1608208. Try removing all old virtualbox packages prior to installing virtualbox 5. See my comment on Bug #1608208 for detailed commands to run in order to find all the ones you have installed. Hint: Check for "ii" lines in output of: dpkg -l | grep virtualbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708315 Title: package virtualbox-guest-utils-hwe 5.0.40-dfsg- 0ubuntu1.16.04.1~16.04.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1708315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617735] Re: virtualbox failed to install on upgrade from manual install virtualbox-4.3
*** This bug is a duplicate of bug 1608208 *** https://bugs.launchpad.net/bugs/1608208 It appears that you've solved your problem. Great job! Looks like this is a duplicate of Bug #1608208. Fix I found was to uninstall & purge all old virtualbox packages prior to installing the new version, as you've done. ** This bug has been marked a duplicate of bug 1608208 package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617735 Title: virtualbox failed to install on upgrade from manual install virtualbox-4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1617735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613168] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1608208 *** https://bugs.launchpad.net/bugs/1608208 Duplicate of Bug #1608208. Remove and purge all old virtualbox packages. See Bug #1608208 for detailed instructions and commands to run. ** This bug has been marked a duplicate of bug 1608208 package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613168 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1613168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609648] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1608208 *** https://bugs.launchpad.net/bugs/1608208 Duplicate of Bug #1608208. Remove all old virtualbox packages before installing the new one. See Bug #1608208 for detailed instructions & commands to run. ** This bug has been marked a duplicate of bug 1608208 package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609648 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1609648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1608208] Re: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Got same issue when upgrading to virtualbox 5 on Ubuntu 16.04. Fix was to uninstall & purge all old virtualbox packages: # Find your installed old packages with: sudo dpkg -l | grep virtualbox # Uninstall all packages listed: sudo apt-get purge virtualbox-qt virtualbox virtualbox-dkms virtualbox-4.2 virtualbox-4.3 unity-scope-virtualbox sudo apt-get autoremove Then, try re-installing the new virtualbox: sudo apt-get update && sudo apt-get install virtualbox I was using oracle deb repo packages, but should work for others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608208 Title: package virtualbox 5.0.24-dfsg-0ubuntu1.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1608208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299512] Re: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1200950 *** https://bugs.launchpad.net/bugs/1200950 I'm seeing this too upon upgrade to 16.04.3 LTS with Unity. This appears to have been reported many times and marked as duplicate of #1200950 by the Apport Launchpad bot. I'm marking this one also as dupe of #1200950 for Triage because Apport bot must have missed it. ** This bug has been marked a duplicate of bug 1200950 gnome-keyring-daemon crashed with SIGABRT in _g_log_abort() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299512 Title: gnome-keyring-daemon crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1299512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655425] Re: CEC on Raspberry Pi 3 not working
On my Raspberry Pi OpenELEC device, I see that they have cec-client working. However, it's not cec-client 4.0.1, but an older 3.0.1: # cec-client -i libCEC version: 3.0.1, git revision: f3d0ca2 , compiled on Sun May 1 12:14:09 UTC 2016 by step...@buildserver.openelec.tv on Linux 3.19.8-100.fc20.x86_64 (x86_64), features: P8_USB, P8_detect, 'RPi' # cec-client --list-devices libCEC version: 3.0.1, git revision: f3d0ca2 , compiled on Sun May 1 12:14:09 UTC 2016 by step...@buildserver.openelec.tv on Linux 3.19.8-100.fc20.x86_64 (x86_64), features: P8_USB, P8_detect, 'RPi' Found devices: 1 device: 1 com port:RPI vendor id: 2708 product id: 1001 firmware version:1 type:Raspberry Pi On this Raspberry Pi, `cec-client -s` does work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655425 Title: CEC on Raspberry Pi 3 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/1655425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655425] Re: CEC on Raspberry Pi 3 not working
For what it's worth, trying the above posted command `cec-client -s` did not work for me on an x86_64 Intel i7 machine either. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $ uname -a Linux saturn 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux One thing I noticed thanks to an error reported by a mythtv-frontend utility called "mythscreenwizard" was this: $ mythscreenwizard --verbose general --loglevel info --syslog local7 --quiet libcec.so.3: cannot open shared object file: No such file or directory So this mythscreenwizard utility was linked against libcec.so.3 presumably to detect display information over CEC. However, even with libcec and libcec3 packages installed, this utility still reported the same error. The packages themselves appear to be missing the specific filename "libcec.so.3": $ sudo apt-get -yq install libcec libcec4 libcec3 $ dpkg -L libcec /. /usr /usr/share /usr/share/doc /usr/share/doc/libcec /usr/share/doc/libcec/changelog.gz /usr/share/doc/libcec/copyright $ dpkg -L libcec4 | grep lib /usr/share/doc/libcec4 /usr/share/doc/libcec4/changelog.gz /usr/share/doc/libcec4/copyright /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libcec.so.4.0.1 /usr/lib/x86_64-linux-gnu/libcec.so.4 $ dpkg -L libcec3 | grep lib /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libcec.so.3.0.1 /usr/share/doc/libcec3 /usr/share/doc/libcec3/changelog.gz /usr/share/doc/libcec3/copyright /usr/lib/x86_64-linux-gnu/libcec.so.3.0 $ mythscreenwizard --verbose general --loglevel info --syslog local7 --quiet libcec.so.3: cannot open shared object file: No such file or directory After noticing this was missing, I added the symlink: $ cd /usr/lib/x86_64-linux-gnu/ $ sudo ln -s libcec.so.3.0.1 /usr/lib/x86_64-linux-gnu/libcec.so.3 $ ls -l /usr/lib/x86_64-linux-gnu/libcec.so.* $ ls -l /usr/lib/x86_64-linux-gnu/libcec.so.* lrwxrwxrwx 1 root root 15 Oct 20 14:27 /usr/lib/x86_64-linux-gnu/libcec.so.3 -> libcec.so.3.0.1 lrwxrwxrwx 1 root root 15 Feb 20 2016 /usr/lib/x86_64-linux-gnu/libcec.so.3.0 -> libcec.so.3.0.1 -rw-r--r-- 1 root root 629760 Feb 20 2016 /usr/lib/x86_64-linux-gnu/libcec.so.3.0.1 lrwxrwxrwx 1 root root 15 Jan 3 2017 /usr/lib/x86_64-linux-gnu/libcec.so.4 -> libcec.so.4.0.1 -rw-r--r-- 1 root root 629640 Jan 3 2017 /usr/lib/x86_64-linux-gnu/libcec.so.4.0.1 $ mythscreenwizard --verbose general --loglevel info --syslog local7 --quiet # NO MORE ERROR! After this minor fix at least there was no more error. However, the command still did not work: $ cec-client -s autodetect FAILED Not sure what the next issue is, but perhaps I'll poke around a bit to find out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655425 Title: CEC on Raspberry Pi 3 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcec/+bug/1655425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310359] Re: MythBuntu Control Center Plugins Tab Issue
Not sure if it fits the description and errors originally in this bug. However, I do see some issues on the plugins tab with mythbuntu-control- centre 0.64.1 on recently upgraded Ubuntu 16.04 machine. I can reproduce it by clicking on the "Enable/Disable All MythTV Plugins" CheckButton. The error reported by apport is: Traceback (most recent call last): File "/usr/share/mythbuntu/plugins/python/plugins.py", line 133 in toggle_plugins if list[item].flags() & Gtk.SENSITIVE: AttributeError: 'CheckButton' object has no attribute 'flags' Seems that the code expects there to be a 'flags' attribute on the object: 127 def toggle_plugins(self,widget): 128 if widget is not None: 129 if widget.get_name() == 'selectall_plugins_checkbox': 130 toggle=widget.get_active() 131 for list in get_frontend_plugin_dictionary(self), get_backend_plugin_dictionary(self): 132 for item in list: 133 if list[item].flags() & Gtk.SENSITIVE: 134 list[item].set_active(toggle) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310359 Title: MythBuntu Control Center Plugins Tab Issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythbuntu-control-centre/+bug/1310359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219525] Re: Cannot unhide (show hidden) launcher over Remote Desktop (VNC connection over vino or x11vnc)
I am able to reproduce issue when using: VNC Server: Ubuntu trusty 14.04.3 LTS running x11vnc 0.9.13-1.1 $ x11vnc -version x11vnc: 0.9.13 lastmod: 2011-08-10 VNC Clients: - Mac OS X 10.9.5 running Screen Sharing app Version 1.5 (481.1) - Mac OS X 10.10.5 running Screen Sharing app Version 1.6.4 (491.13) Evidence suggests that this problem is not due to any specific VNC server or client. Seems to be a combination of Unity & VNC -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219525 Title: Cannot unhide (show hidden) launcher over Remote Desktop (VNC connection over vino or x11vnc) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1219525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219525] Re: Cannot unhide (show hidden) launcher over Remote Desktop (VNC connection over vino or x11vnc)
Above reproduction was tested using Unity package: unity 7.2.0+14.04.20140416-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219525 Title: Cannot unhide (show hidden) launcher over Remote Desktop (VNC connection over vino or x11vnc) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1219525/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810791] Re: Softreset failed (device not ready) with Gigabyte motherboard
Apologies for not responding sooner (I get waaay too many emails and have filtered automated mailings like the ones sent by launchpad to Gmail labels which generally never get looked at). After upgrading to the next LTS release (12.04) I believe I stopped seeing this bug. Upgraded since to latest LTS release of 14.04, and still not having this issue anymore. Just for the record, I believe this can be called fixed! ** Changed in: linux (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/810791 Title: Softreset failed (device not ready) with Gigabyte motherboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/810791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 902134] Re: k3b: Device in use - It is urged to terminate the program gvfsd-cdda before proceeding.
Verified it still is a problem in: Ubuntu 14.04.1 LTS (Trusty) ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902134 Title: k3b: Device in use - It is urged to terminate the program gvfsd-cdda before proceeding. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/902134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 296867]
Complaints show fear, anger ungratefulness while calm feature requests show peace, gratefulness understanding of a problem. Community giving of FOSS shows kindness compassion, while taking complaining shows an unsatisfied desire for control. True control lies in harmonising with the community, and paradoxically involves letting go of your need for control while also giving the part which is under your control. Heartbleed shows inherent insecurity of a house divided against itself yet it also shows the speed of the Whole to heal itself. Privacy is an illusion... security built on deterministic Laws has little room for true randomness without hiding within Complexity. The appearance of randomness is Chaos, yet within the chaos lies a higher Order. No matter which side you think you are on... you're actually on both, and they are not truly opposed when undivided. On Mon, Apr 28, 2014 at 12:31 PM, Sam Liddicott s...@liddicott.com wrote: I'm feed up of people complaining about people complaining about wilful bad security. This is doubly so considering all the criticism that has gone the way of the OpenSSL people in the wake of Heartbleed. A little more discussion there might have helped, but here it obviously hasn't! When someone gives their time and experience to improve software designs from fatal flaws, often in the evenings with other distractions, they get next to no gratitude and a whole heap of criticism as if their drawing attention to the flaw is worse than the flaw itself. Free software doesn't stop people talking about the naked emperor. If they are not government spies and but just play at spies in their evenings (with other distractions) then that is fine, but if they then make a public gift of it can they really expect people to not talk about it? They don't buy our silence with their wooden horse! We don't use it and we warn others. We actually care about their users! Sam On 28 Apr 2014 18:55, Chris Kerr gingek...@gmail.com wrote: I'm fed up of people complaining about developers. It's *free software*, and if you get anything more than you paid for then you should be grateful (I certainly am). This is doubly so considering all the criticism that has gone the way of the OpenSSL people in the wake of Heartbleed. When someone gives their best effort to produce software as a gift to the community, often working in spare evenings with lots of other distractions which prevent them giving their full focus to the task, they get next to no praise when it works and a whole heap of criticism when they make a tiny mistake. People even accuse them of deliberately inserting the mistake as a government spy. I'm currently writing up my PhD thesis. When I finish, I will have some free time while waiting for my viva voce, and would be willing to spend some of that time trying to fix this, as it is something I would find useful myself and potentially also a helpful addition to my CV. However there are probably plenty of people out there who would do a better job than I, especially since I have mainly used Fortran and Python for the last 4 years so my C/C++ is rather rusty. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/296867 Title: empathy needs to support OTR encryption To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/296867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004829] Re: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all
On this same motherboard (Gigabyte GA-MA74GMT-S2), I had success getting the front panel input to work by adding the following line to /etc/pulse/default.pa load-module module-alsa-source device=hw:0,0 I added this just before the udev auto-detect module: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else Then run: /etc/init.d/pulseaudio restart If you still get no sound input: 1. Run alsamixer 2. Press F4 to go to the Capture screen 3. Right Arrow over to the Input Source column 4. Press Up/Down Arrow until the Front Mic input is selected 5. Make sure your Capture volume is all the way up (adjust Mic Boost to taste but beware if it's too high you'll get distortion) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004829 Title: [GA-MA74GMT-S2, Realtek ALC887-VD, Pink Mic, Front] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1004829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158117] Re: Control centre fails to start because of an obsolete import of a deprecated and removed widget
Still seeing this in Ubuntu 13.10 Saucy Salamander with mythbuntu- control-centre package version: 0.63-0ubuntu2 I can verify that the patch attached to this issue works and the mythbuntu-control-centre app opens after I've applied it! Thanks @Sebastian ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158117 Title: Control centre fails to start because of an obsolete import of a deprecated and removed widget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythbuntu-control-centre/+bug/1158117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539275] Re: gwibber_messages couchdb views use more disk space than needed
Ran baobab today and found that gwibber was using about 30GB of space in my home dir! ~$ ls -sh ~/.local/share/desktop-couch/.gwibber_messages_design/ total 26G 13M 0526a2ae236cc99c2b84d33f1be6cea1.view 2.7G 2f3267703246f5e02533e59714915b7d.view 24G 8873a749eadc0dee755b5fdfdc59c0a1.view Is this really necessary? How long does gwibber save data? Is there a way to turn down the history saving? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539275 Title: gwibber_messages couchdb views use more disk space than needed To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/539275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568762] Re: ubuntu-minimal package is REMOVED when removing ureadahead
Ran across this dependency when installing e4rat. I've created a .deb metapackage for ubuntu-minimal without the ureadahead dependency here: https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead/ DISCLAIMER: I do not guarantee that you won't run into any problems, so if in doubt remove e4rat before upgrade fix your /etc/default/grub manually. !!NOTE Only install this if you really want to and know how to fix things if the upgrade does not work correctly. I haven't tested it as of yet, so just be careful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568762 Title: ubuntu-minimal package is REMOVED when removing ureadahead To manage notifications about this bug go to: https://bugs.launchpad.net/sreadahead/+bug/568762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280571] Re: NetworkManager does not auto-connect to VPNs marked Connect Automatically
Confirmed still in network-manager-vpnc 0.9.4.0-0ubuntu1 on Ubuntu 12.04.1 LTS (Precise Pangolin). Would be really nice if connect automatically checkbox would actually work! I think it's about time someone who knows about this piece, and where to look in order to fix it took it into consideration again ^_^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/280571 Title: NetworkManager does not auto-connect to VPNs marked Connect Automatically To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/280571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990057] [NEW] package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libat
*** This bug is a duplicate of bug 989653 *** https://bugs.launchpad.net/bugs/989653 Public bug reported: Was able to fix this. For more details see: http://askubuntu.com/q/126322/19264 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libatk-adaptor-schemas 2.4.0-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Fri Apr 27 11:21:04 2012 DuplicateSignature: Unpacking libatk-adaptor-schemas (from .../libatk-adaptor-schemas_2.4.0-1ubuntu2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libatk-adaptor-schemas_2.4.0-1ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) SourcePackage: at-spi2-atk Title: package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago) ** Affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990057 Title: package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/990057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990057] Re: package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-
*** This bug is a duplicate of bug 989653 *** https://bugs.launchpad.net/bugs/989653 ** This bug has been marked a duplicate of bug 989653 package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990057 Title: package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/glib-2.0/schemas/org.a11y.atspi.gschema.xml', which is also in package libatk-adaptor 2.2.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/990057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 856205] Re: run the wrong command if enter is hit before the view is refreshed
Thanks for fixing this!!! ^_^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/856205 Title: run the wrong command if enter is hit before the view is refreshed To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/856205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
Trebacz (from Comment #25), I was able to simply uninstall and re-install the package, and it seems to work fine now. I pressed Ctrl+Alt+F1 when I got the blank screen after a reboot, logged in, and did this: sudo apt-get remove nvidia-current sudo apt-get install nvidia-current -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
Update: I found that the root cause of my X11 not starting was due to my nvidia-current package being in a bad state during the upgrade. The video drivers were not installed for the new kernel, which was causing the second issue. After manually doing the move symlink of /var/run and /var/lock, everything seems to be in working order now. I didn't end up messing with the ordering of scripts in runlevel 6 at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
I'm seeing this on a Thinkpad T410 that has been dist-upgraded to Oneric. It started out running a freshly installed Maverick, which I have upgraded up to Oneric now. The system failed to boot after dist-upgrade with dbus error messages like in Bug #811441 I do not have any weird cifs or nfs mounts. I do not run VMWare, only VirtualBox. I do have turboprint installed. Here are the file listings on my system: ls -l /etc/init.d/.legacy-bootordering -rw-r--r-- 1 root root 0 2011-01-18 17:07 /etc/init.d/.legacy-bootordering ls -l /etc/init.d/umountroot -rwxr-xr-x 1 root root 2926 2011-07-13 23:10 /etc/init.d/umountroot ls -l /etc/rc6.d/ total 4 lrwxrwxrwx 1 root root 16 2011-02-19 13:29 K01hdapsd - ../init.d/hdapsd lrwxrwxrwx 1 root root 17 2011-02-19 13:29 K01postfix - ../init.d/postfix lrwxrwxrwx 1 root root 19 2011-02-19 13:29 K02bluetooth - ../init.d/bluetooth lrwxrwxrwx 1 root root 17 2011-07-02 01:45 K09apache2 - ../init.d/apache2 lrwxrwxrwx 1 root root 23 2011-04-04 09:29 K20uml-utilities - ../init.d/uml-utilities lrwxrwxrwx 1 root root 33 2011-04-21 10:24 K20vboxballoonctrl-service - ../init.d/vboxballoonctrl-service lrwxrwxrwx 1 root root 17 2011-04-21 10:39 K20vboxdrv - ../init.d/vboxdrv lrwxrwxrwx 1 root root 25 2011-04-21 10:39 K20vboxweb-service - ../init.d/vboxweb-service lrwxrwxrwx 1 root root 17 2011-07-20 11:50 K20winbind - ../init.d/winbind -rw-r--r-- 1 root root 351 2011-07-13 23:11 README lrwxrwxrwx 1 root root 26 2011-02-19 13:29 S01cryptdisks-early - ../init.d/cryptdisks-early lrwxrwxrwx 1 root root 20 2011-02-19 13:29 S02cryptdisks - ../init.d/cryptdisks lrwxrwxrwx 1 root root 16 2011-02-19 13:29 S03reboot - ../init.d/reboot lrwxrwxrwx 1 root root 18 2011-02-19 13:29 S03sendsigs - ../init.d/sendsigs lrwxrwxrwx 1 root root 18 2011-02-19 13:29 S03umountfs - ../init.d/umountfs lrwxrwxrwx 1 root root 22 2011-02-19 13:29 S03umountnfs.sh - ../init.d/umountnfs.sh lrwxrwxrwx 1 root root 20 2011-02-19 13:29 S03umountroot - ../init.d/umountroot lrwxrwxrwx 1 root root 17 2011-02-19 13:29 S04urandom - ../init.d/urandom lrwxrwxrwx 1 root root 29 2011-04-29 12:19 S10unattended-upgrades - ../init.d/unattended-upgrades lrwxrwxrwx 1 root root 20 2011-10-14 02:13 S35networking - ../init.d/networking -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858122] Re: incomplete migration to /run (shutdown script order has been demolished)
FYI: I had previously upgraded from Maverick - Natty I experienced the issue when upgrading from Natty - Oneric I manually did the following: sudo mv /var/run/* /run/ sudo mv /var/lock/* /run/lock/ sudo rmdir /var/run sudo rmdir /var/lock sudo ln -s /run /var/run sudo ln -s /run/lock /var/lock I rebooted, and X still does not start! Most of the boot process looks ok, except for the following errors: rpcbind: Cannot open '/var/run/rpcbind/rpcbind.xdr' file for reading, errno 2 (No such file or directory) rpcbind: Cannot open '/var/run/rpcbind/portmap.xdr' file for reading, errno 2 (No such file or directory) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858122 Title: incomplete migration to /run (shutdown script order has been demolished) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/858122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 95564] Re: Advanced bash autocompletion for packages does no longer work in feisty
I'm getting a similar error: sudo apt-get purge adobe-pgrep-status: /var/lib/dpkg/status:44726: expected a colon Here is a snippet of this file with the line numbers included: http://pastebin.com/YkSpHjah -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/95564 Title: Advanced bash autocompletion for packages does no longer work in feisty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/95564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483912] Re: When sorting by track number, sometimes track 1 is incorrectly sorted at the bottom
I am seeing this bug for 'various artists' albums being that are not marked as compilations sorted incorrectly. I have *tons* of these in my library. Is there an easy way to auto- detect them and set them having Compilation Album Artist set to 'VA' ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/483912 Title: When sorting by track number, sometimes track 1 is incorrectly sorted at the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/banshee/+bug/483912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721982] Re: Corrupt display for history search in vi-mode, 256-color prompt
I stumbled upon this bug when using a color PS4 prompt to trace bash scripts. Usually it would display fine, but I noticed some strange behavior once the shell level increased enough. Bash repeats the first character of the PS4 prompt to indicate the shell level for scripts that call other scripts (or subshells). Once the shell level increases enough, the characters at the end of the prompt are truncated. This causes display problems, especially if the color off ANSI code is chopped off the end. Many thanks for finding this bug! It was driving me nuts until I used the 'script' command to record my terminal's raw output and found that the prompt was being truncated. With this patch, I still see that rl_message still seems to use a size of 128 and truncates if my system does not have vsnprintf. I compiled bash-static and tested a long PS4 with color codes, and it still seems to truncate for me. How can I check that my system has vsnprintf? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721982 Title: Corrupt display for history search in vi-mode, 256-color prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/721982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 721982] Re: Corrupt display for history search in vi-mode, 256-color prompt
Disregard my last question. I found this output in my build log: checking for standard-conformant vsnprintf... yes It appears that I must have not added my patch to the debian/patches folder the correct way. I didn't see that the patch was applied during the build log, and it was not listed in the stamps/ directory. So yeah, that was my bad ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721982 Title: Corrupt display for history search in vi-mode, 256-color prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/721982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483624] Re: konsole lose focus
I am seeing this In Ubuntu using the Gnome desktop as well. The konsole window gets into a state where it appears that it has focus, but does not respond to keyboard input, and has a 'hollow cursor'. The way I ran into it was by using multiple konsole windows on different desktops and switching between them. I have found a quick way to reproduce this state in Ubuntu Natty 11.04 while using compiz and the wall desktop: 1. On desktop 1, open konsole 1. Press Ctrl+Alt+Down to switch to desktop 2 2. Open another konsole window and maximize it 3. Press Ctrl+Alt+Up and click the 1st konsole window so it has focus 4. Alternate between the desktops using the Ctrl+Alt+ [ Up / Down ] Arrows 5. Eventually, one of the windows will appear with a hollow cursor and not respond to keyboard input The 'hollow cursor' is evidence that the window has indeed lost focus, as evidenced by this changelog entry: Hollow out cursor when losing focus. ( Reference: http://konsole.kde.org/changelogfull.php ) Ideally, we would want the correct konsole window to have focus, depending on which desktop we are on. I am not sure if this is a bug with the compiz window manager, or with konsole. ** Also affects: compiz Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in Ubuntu. https://bugs.launchpad.net/bugs/483624 Title: konsole lose focus To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/483624/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 774746] Re: metallic sound when changing volume
Which packages from the ppa are necessary for testing out the fix for this? I'm seeing this issue on a Thinkpad T410 with this hardware $ lspci | grep -i audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) I'm not sure if I want to pull in unnecessary updates for some packages on this system yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774746 Title: metallic sound when changing volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/774746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 775920] Re: unity wallpaper looks corrupted after login
Confirmed on a Thinkpad T410 using the nvidia proprietary drivers throught synaptic. Wallpaper looks similar to screenshot upon login $ lspci | grep -i nvidia 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 11.04 Release:11.04 Codename: natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/775920 Title: unity wallpaper looks corrupted after login To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/775920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] [NEW] Unity does not redraw
Public bug reported: Sometimes, I am affected by bug 808962 where unity always stays on top of my windows. This is very annoying. In an attempt to workaround this, I opened ccsm and disabled re-enabled Unity (unchecked and then rechecked the compiz plugin). After doing this, I end up with a purple bar on the side of my screen that does not redraw, and is still above all windows. I do not have to experience bug 808962 first for this to happen. It seems like it's an issue after disabling re-enabling it. Sometimes, the unity bar at the top does not redraw correctly either. Steps to reproduce: 1. Open ccsm 2. Disable Unity 3. Re-enable Unity I am running natty on a Thinkpad T410 with the nvidia-proprietary drivers installed through synaptic. $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 11.04 Release:11.04 Codename: natty $ lspci | grep -i nvidia 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) ** Affects: unity (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/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Re: Unity does not redraw
** Attachment added: Screenshot of the problem https://bugs.launchpad.net/bugs/816527/+attachment/2234429/+files/Unity-purple-redraw-issue.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Re: Unity does not redraw
apport information ** Tags added: apport-collected compiz-0.9 natty needs-reassignment possible-manual-nvidia-install regression-update running-unity ubuntu ** Description changed: Sometimes, I am affected by bug 808962 where unity always stays on top of my windows. This is very annoying. In an attempt to workaround this, I opened ccsm and disabled re-enabled Unity (unchecked and then rechecked the compiz plugin). After doing this, I end up with a purple bar on the side of my screen that does not redraw, and is still above all windows. I do not have to experience bug 808962 first for this to happen. It seems like it's an issue after disabling re-enabling it. Sometimes, the unity bar at the top does not redraw correctly either. Steps to reproduce: 1. Open ccsm 2. Disable Unity 3. Re-enable Unity I am running natty on a Thinkpad T410 with the nvidia-proprietary drivers installed through synaptic. $ lsb_release -a Distributor ID: Ubuntu Description: Ubuntu 11.04 Release: 11.04 Codename: natty $ lspci | grep -i nvidia 01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2) 01:00.1 Audio device: nVidia Corporation High Definition Audio Controller (rev a1) + --- + .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' + .proc.driver.nvidia.registry: Binary: + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 275.19 Tue Jul 12 18:13:58 PDT 2011 + GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) + Architecture: amd64 + CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,imgpng,resizeinfo,grid,titleinfo,compiztoolbox,mousepoll,wall,move,switcher,dbus,regex,place,vpswitch,ring,snap,commands,animation,winrules,session,workarounds,unityshell] + CompositorRunning: compiz + DistUpgraded: Log time: 2011-04-29 09:46:33.627246 + DistroCodename: natty + DistroRelease: Ubuntu 11.04 + DistroVariant: ubuntu + DkmsStatus: + nvidia-current, 275.19, 2.6.38-10-generic, x86_64: installed + vboxhost, 4.0.12, 2.6.38-10-generic, x86_64: installed + EcryptfsInUse: Yes + GraphicsCard: + nVidia Corporation GT218 [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) +Subsystem: Lenovo Device [17aa:21d4] + InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) + InstallationMedia_: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) + InstallationMedia__: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) + JockeyStatus: xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, Not in use) + MachineType: LENOVO 2518AJU + NonfreeKernelModules: nvidia + Package: unity 3.8.16-0ubuntu1~natty1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_US:en + LC_COLLATE=en_US.utf8 + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=5c44ca76-926c-44dc-b742-95268046f8ec ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 + ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 + ProcVersionSignature__: Ubuntu 2.6.38-10.46-generic 2.6.38.7 + Renderer: Unknown + Tags: natty running-unity natty running-unity natty running-unity possible-manual-nvidia-install ubuntu regression-update needs-reassignment compiz-0.9 + Uname: Linux 2.6.38-10-generic x86_64 + UpgradeStatus: Upgraded to natty on 2011-04-29 (87 days ago) + UserGroups: adm admin audio cdrom dialout fuse lpadmin plugdev sambashare vboxusers + dmi.bios.date: 10/25/2010 + dmi.bios.vendor: LENOVO + dmi.bios.version: 6IET74WW (1.34 ) + dmi.board.name: 2518AJU + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr6IET74WW(1.34):bd10/25/2010:svnLENOVO:pn2518AJU:pvrThinkPadT410:rvnLENOVO:rn2518AJU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 2518AJU + dmi.product.version: ThinkPad T410 + dmi.sys.vendor: LENOVO + version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 + version.ia32-libs: ia32-libs 20090808ubuntu13 + version.libdrm2: libdrm2 2.4.23-1ubuntu6 + version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 + version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A + version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 + version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Attachment added: .proc.driver.nvidia.params.txt
[Bug 816527] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234433/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234434/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234435/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234436/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] GlConf.txt
apport information ** Attachment added: GlConf.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234437/+files/GlConf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234438/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234439/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234440/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234441/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234442/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234443/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/816527/+attachment/223/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234445/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] XorgConf.txt
apport information ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234446/+files/XorgConf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234447/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234448/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234449/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] monitors.xml.txt
apport information ** Attachment added: monitors.xml.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234450/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] nvidia-installer.log.txt
apport information ** Attachment added: nvidia-installer.log.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234451/+files/nvidia-installer.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] nvidia-settings.txt
apport information ** Attachment added: nvidia-settings.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234452/+files/nvidia-settings.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] peripherals.txt
apport information ** Attachment added: peripherals.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234453/+files/peripherals.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234454/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 816527] xinput.txt
apport information ** Attachment added: xinput.txt https://bugs.launchpad.net/bugs/816527/+attachment/2234455/+files/xinput.txt ** Changed in: unity (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/816527 Title: Unity does not redraw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/816527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 810791] Re: Softreset failed (device not ready) with Gigabyte motherboard
apport information ** Tags added: apport-collected running-unity ** Description changed: I originally reported this in Bug 285392. However, I'm not sure that this is the same bug, or a different one with the same symptom. I am seeing this problem on a Gigabyte GA-MA74GM-S2 motherboard. I have tried changing the BIOS setting for both AHCI and IDE modes. I get the same error upon boot. After a reboot I have been seeing this error randomly all the time. Sometimes it seems to work ok, sometimes not. I have done 2 dist-upgrades from Lucid (10.04.2 LTS ) to Maverick ( 10.10 ) to Natty ( 11.04 ). This bug has been present in all of these versions of Ubuntu. Boot messages follow: The disk drive for / is not ready yet or not present Continue to wait; or Press S to skip mounting or M for manual recovery [ 1.740026] ata3: softreset failed (device not ready) [ 1.740032] ata6: softreset failed (device not ready) [ 1.740058] ata5: softreset failed (device not ready) [ 1.740062] ata4: softreset failed (device not ready) init: udevtrigger main process (467) terminated with status 1 init: udevtrigger post-stop process (471) terminated with status 1 init: udevmonitor main process (466) killed by TERM signal udevd[453]: specified group 'camera' unknown Ever since Lucid, there are 2 problems with this motherboard that I've been having: 1) It doesn't seem to boot correctly from the first HDD if USB-HDD or CDROM are anywhere above in the boot priority list 2) Every so often I still get the softreset and The disk drive for /home is not ready yet or not present errors (This is random.. it's usually /home, /, or whatever other partition happens to complain). AHCI vs IDE modes in the BIOS don't change anything. I'm guessing it's a Gigabyte motherboard issue, or something to do with the ATI SB7x0 chipset. So far I haven't tried compiling a new kernel with CONFIG_SATA_PMP=n yet... but that seems like it might work... References: https://bugzilla.redhat.com/show_bug.cgi?id=468800 http://kerneltrap.org/mailarchive/git-commits-head/2008/6/14/2122314 http://ubuntuforums.org/archive/index.php/t-1052987.html http://lime-technology.com/forum/index.php?topic=2642.msg33590#msg33590 + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. + AplayDevices: aplay: device_list:240: no soundcards found... + Architecture: amd64 + ArecordDevices: arecord: device_list:240: no soundcards found... + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: trinitronx 2433 F pulseaudio + /dev/snd/controlC0: trinitronx 2433 F pulseaudio + CRDA: Error: [Errno 2] No such file or directory + CheckboxSubmission: d6dd0471f36d4aed9362bfdc71eb18b9 + CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 + DistroRelease: Ubuntu 11.04 + HibernationDevice: RESUME=UUID=19b226f0-b1dc-4c53-99c8-c585ffe9d167 + InstallationMedia: Mythbuntu 10.04 Lucid Lynx - Beta amd64 (20100406) + IwConfig: + lono wireless extensions. + + eth0 no wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. GA-MA74GM-S2 + NonfreeKernelModules: nvidia + Package: linux (not installed) + ProcEnviron: + LC_COLLATE=en_US.utf8 + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=fcd55128-66e2-41ad-ab3a-606c165b2102 ro quiet splash noacpi noapm vt.handoff=7 + ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 + RelatedPackageVersions: + linux-restricted-modules-2.6.38-8-generic N/A + linux-backports-modules-2.6.38-8-generic N/A + linux-firmware1.52 + RfKill: + + Tags: natty running-unity + Uname: Linux 2.6.38-8-generic x86_64 + UpgradeStatus: Upgraded to natty on 2011-06-30 (19 days ago) + UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare video + WifiSyslog: + Jul 19 12:52:53 saturn kernel: [260899.520036] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) + Jul 19 12:54:01 saturn kernel: [260967.520038] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) + Jul 19 12:56:02 saturn kernel: [261087.840039] TCP: Peer 77.114.168.45:54569/49317 unexpectedly shrunk window 1213338602:1213342756 (repaired) + dmi.bios.date: 04/17/2008 + dmi.bios.vendor: Award Software International, Inc. + dmi.bios.version: F1 + dmi.board.name: GA-MA74GM-S2 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/17/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA74GM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA74GM-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: + dmi.product.name: GA-MA74GM-S2 + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment