[Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: blk_update_request: I/O error, dev sr0, sector 661504 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 82688, async page read Description:Ubuntu 20.04.3 LTS Release:20.04 Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING EDGE WIFI (MS-7C91) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.70 date: 06/29/2021 Drive: /dev/sr0 Vendor : ASUS Model : DRW-24F1ST d Revision: 2.00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Similar problem occurred during upgrade to linux-firmware (1.187.20); initial install failed, but was able to successfully install after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] Re: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Appears to have installed successfully after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945845] [NEW] package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 linux-firmware: Installed: 1.187.16 Candidate: 1.187.17 Version table: 1.187.17 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages *** 1.187.16 100 100 /var/lib/dpkg/status 1.187 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages Installation failed during system update. Unpacking libgl1-mesa-dev:amd64 (21.0.3-0ubuntu0.3~20.04.2) over (21.0.3-0ubuntu 0.3~20.04.1) ... Errors were encountered while processing: /tmp/apt-dpkg-install-hJ8TxR/47-linux-firmware_1.187.17_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2654 F pulseaudio curts 3716 F pulseaudio /dev/snd/controlC0: gdm2654 F pulseaudio curts 3716 F pulseaudio CasperMD5CheckResult: skip Date: Fri Oct 1 19:32:59 2021 Dependencies: ErrorMessage: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (222 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IwConfig: lono wireless extensions. enp42s0 no wireless extensions. tun0 no wireless extensions. MachineType: Micro-Star International Co., Ltd. MS-7C91 PackageArchitecture: all ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz root=UUID=7A200ADA-3790-4EBA-8897-FF422F2FB377 quiet splash rootflags=subvol=@ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG B550 GAMING EDGE WIFI (MS-7C91) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.50:bd01/14/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGB550GAMINGEDGEWIFI(MS-7C91):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C91 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945845 Title: package linux-firmware 1.187.16 failed to install/upgrade: unable to open '/lib/firmware/qcom/a530_zap.mdt.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
$ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: linux-headers-5.11.0-34-generic linux-hwe-5.11-headers-5.11.0-34 The following NEW packages will be installed: linux-headers-5.11.0-34-generic The following packages will be upgraded: linux-hwe-5.11-headers-5.11.0-34 1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 57 not fully installed or removed. Need to get 0 B/13.1 MB of archives. After this operation, 90.4 MB of additional disk space will be used. Do you want to continue? [Y/n] y Setting up libgcrypt20:amd64 (1.8.5-5ubuntu1.1) ... Setting up libsystemd0:amd64 (245.4-4ubuntu3.13) ... Setting up libgcrypt20:i386 (1.8.5-5ubuntu1.1) ... Setting up systemd-timesyncd (245.4-4ubuntu3.13) ... Setting up systemd (245.4-4ubuntu3.13) ... Installing new version of config file /etc/dhcp/dhclient-enter-hooks.d/resolved ... (Reading database ... 263621 files and directories currently installed.) Preparing to unpack .../linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_al l.deb ... Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) over (5.11.0-3 4.36~20.04.1) ... Preparing to unpack .../linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_amd 64.deb ... Unpacking linux-headers-5.11.0-34-generic (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /var/cache/apt/archives/linux-headers-5.11.0-34-g eneric_5.11.0-34.36~20.04.1_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo. dpkg-new': Operation not permitted Errors were encountered while processing: /var/cache/apt/archives/linux-headers-5.11.0-34-generic_5.11.0-34.36~20.04.1_am d64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] Re: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation
This is with the NVIDIA 460 driver. At present, I can't successfully switch to the 470 driver, because it tries to use the 5.11.0-34.36 kernel files as part of the install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943092] [NEW] package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operati
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 \linux-headers-5.11.0-34-generic: Installed: (none) Candidate: 5.11.0-34.36~20.04.1 Version table: 5.11.0-34.36~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages Install failed during latest kernel update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-34-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 8 20:26:11 2021 DuplicateSignature: package:linux-headers-5.11.0-34-generic:(not installed) Unpacking linux-hwe-5.11-headers-5.11.0-34 (5.11.0-34.36~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-26WFDo/10-linux-hwe-5.11-headers-5.11.0-34_5.11.0-34.36~20.04.1_all.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-hwe-5.11-headers-5.11.0-34.list-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-02-21 (199 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943092 Title: package linux-headers-5.11.0-34-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-34-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1943092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934538] [NEW] Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade
Public bug reported: Description:Ubuntu 20.04.2 LTS Release:20.04 linux-modules-nvidia-460-5.8.0-59-generic: Installed: 5.8.0-59.66~20.04.1 Candidate: 5.8.0-59.66~20.04.1 Version table: *** 5.8.0-59.66~20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages 100 /var/lib/dpkg/status During the upgrade to the 5.8.0-59-generic kernel in Ubuntu 20.04, apt showed an upgrade to the NVIDIA 460 driver as withheld. Proceeding with the 5.8.0-59-generic upgrade breaks the installed NVIDIA 460 driver and causes the Nouveau driver to load after reboot. Manually installing package linux-modules-nvidia-460-5.8.0-59-generic allows the updated NVIDIA 460.80 driver to complete installation and makes the Ubuntu 20.04 installation whole and completely up-to-date again after a subsequent reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-460-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 2 15:04:08 2021 InstallationDate: Installed on 2021-02-21 (131 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-restricted-modules-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934538 Title: Package linux-modules-nvidia-460-5.8.0-59-generic not included in kernel 5.8.0-59-generic upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-5.8/+bug/1934538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Well, it would do exactly what I need if I can convince the XanMod developers to adjust their naming scheme. I do not build the new kernels myself (https://xanmod.org/#install_via_apturl). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Thank you for the feedback. I will notify the XanMod Developers Forum. I am just a humble user trying to get the Grub2 menu on my system to update properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] Re: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
** Patch added: "grub-mkconfig_lib.patch" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+attachment/5456433/+files/grub-mkconfig_lib.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912970] [NEW] Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 I am submitting a patch for /usr/share/grub/grub-mkconfig_lib to fix the usage of GRUB_FLAVOUR_ORDER in method version_test_gt(). I have installed the XanMod-LTS kernel in my Ubuntu 20.04 installation. The Ubuntu 20.04 kernel is currently 5.8.0-38-generic and the current xanmod1 kernel is 5.4.91-xanmod1. The sort routine in /usr/share/grub/grub-mkconfig_lib will sort the Ubuntu kernel ahead of the xanmod1 kernel due to the higher version number when assigning the default Ubuntu menu entry at the beginning of the grub2 menu. If /etc/default/grub is updated to include the following entry, it should change the sort order: # Set xanmod1 as the preferred flavour for the default Ubuntu menu entry GRUB_FLAVOUR_ORDER="xanmod1 generic" Unfortunately, there is a trivial bug in method version_test_gt() in /usr/share/grub/grub-mkconfig_lib that prevents this from working. I have attached a patch that corrects it. Once the bug is fixed, the desired sort order is achieved and the 5.4.91-xanmod1 kernel is made the default Ubuntu menu entry. $ sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... using custom appearance settings Found background image: /usr/share/images/grub/Movie_TRON-Legacy_131740_1600x1200.tga Found linux image: /boot/vmlinuz-5.4.91-xanmod1 Found initrd image: /boot/initrd.img-5.4.91-xanmod1 Found linux image: /boot/vmlinuz-5.4.89-xanmod1 Found initrd image: /boot/initrd.img-5.4.89-xanmod1 Found linux image: /boot/vmlinuz-5.8.0-38-generic Found initrd image: /boot/initrd.img-5.8.0-38-generic Found linux image: /boot/vmlinuz-5.8.0-36-generic Found initrd image: /boot/initrd.img-5.8.0-36-generic ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: grub2 ** Package changed: gvfs (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912970 Title: Fix for GRUB_FLAVOUR_ORDER in grub-mkconfig_lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1912970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908464] [NEW] Digikam cannot play h264 videos on raspberry pi
Public bug reported: Videos loaded from my samsung 10e will display thumbnails and can be played in VLC but cannot be played in the built in player in digikam. I inspected the video and it claims to be h264. I know the device plays h264 hardware accelerated on youtube, and from what I can tell, VLC as well. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: digikam 4:6.4.0+dfsg-3build2 ProcVersionSignature: Ubuntu 5.8.0-1010.13-raspi 5.8.17 Uname: Linux 5.8.0-1010-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Dec 16 18:47:55 2020 ImageMediaBuild: 20201022 SourcePackage: digikam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: digikam (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908464 Title: Digikam cannot play h264 videos on raspberry pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1908464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908459] [NEW] Dolphin extremely slow to start on Raspberry Pi
Public bug reported: Dolphin takes ~7+ seconds to start after launch. It appears to be spinning on scanning for DRI devices. It is not io bound or cpu bound, it's just doing a lot of scanning of the file system for what appears to be rendering devices (out of my element here) and it REALLY shows up as a delay on a pi device. This is a 4b with 8 gig of ram and I can verify that this behavior is not in debian stable but is present in debian testing (when I shoehorned it in on, lol), and from what I can tell, the same thing happens on my x86 machines, but they're just so fast in comparison that this doesn't show up. Strace logs are attached. I also reported this directly to the KDE team (not ubuntu) as I'm not sure if this is a software or setup thing. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dolphin 4:20.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1010.13-raspi 5.8.17 Uname: Linux 5.8.0-1010-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Dec 16 17:53:55 2020 ExecutablePath: /usr/bin/dolphin ImageMediaBuild: 20201022 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: dolphin UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (tracker-miner-fs:2024): Tracker-CRITICAL **: 09:43:02.257: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Files': D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is already taken, perhaps the application is already running? (tracker-extract:2020): Tracker-CRITICAL **: 09:43:03.035: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Extract': D-Bus service name:'org.freedesktop.Tracker1.Miner.Extract' is already taken, perhaps the application is already running? (tracker-miner-fs:1687): Tracker-CRITICAL **: 12:28:50.140: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Files': D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is already taken, perhaps the application is already running? (tracker-extract:1690): Tracker-CRITICAL **: 12:28:51.743: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Extract': D-Bus service name:'org.freedesktop.Tracker1.Miner.Extract' is already taken, perhaps the application is already running? ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy ** Attachment added: "Strace with timestamp of issue." https://bugs.launchpad.net/bugs/1908459/+attachment/5444338/+files/dolphin-ts.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908459 Title: Dolphin extremely slow to start on Raspberry Pi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1908459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908456] [NEW] Plasma system monitor sensor widget fails to load sensors after reboot
Public bug reported: This may be raspberry pi specific. When selecting system sensors for a line graph such as core temperature or core frequencies, upon reboot/login the sensors do not register until you open the configuration for the widget and at least open the sensors detail tab. Additionally, this tab is extremely slow the first time you click it (and after reboot). If you have two of these widgets going that have missing sensor data, the act of going into the details and enduring the slowness will make both of the widgets work on the next log-in. It is my assumption that it is doing something system wide like creating devices or loading modules directory or indirectly, but whatever the reason, after one widget config visits the sensors detail tab, they all work immediately after successive logout/login. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: plasma-workspace 4:5.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-1010.13-raspi 5.8.17 Uname: Linux 5.8.0-1010-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Dec 16 15:47:00 2020 ExecutablePath: /usr/bin/plasmashell ImageMediaBuild: 20201022 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: plasma-workspace UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (tracker-miner-fs:2024): Tracker-CRITICAL **: 09:43:02.257: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Files': D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is already taken, perhaps the application is already running? (tracker-extract:2020): Tracker-CRITICAL **: 09:43:03.035: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Extract': D-Bus service name:'org.freedesktop.Tracker1.Miner.Extract' is already taken, perhaps the application is already running? (tracker-miner-fs:1687): Tracker-CRITICAL **: 12:28:50.140: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Files': D-Bus service name:'org.freedesktop.Tracker1.Miner.Files' is already taken, perhaps the application is already running? (tracker-extract:1690): Tracker-CRITICAL **: 12:28:51.743: Could not request DBus name 'org.freedesktop.Tracker1.Miner.Extract': D-Bus service name:'org.freedesktop.Tracker1.Miner.Extract' is already taken, perhaps the application is already running? ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908456 Title: Plasma system monitor sensor widget fails to load sensors after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1908456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
Further potentially useful information about the behavior after PPA install: If you remove a device via the ui, it leaves a ghosted version that may or may not be able to reconnect if the device tries to. You must remove this ghosted device (two removes in total) and then it appears to allow a fresh pair that works perfectly. No actual need to restart bluetooth. I tried raspberry pi os (debian port) and this mouse works perfectly and is very snappy / perfect in bluetooth mode, just like with the USB receiver. No amount of hcitool and other tricks (kernel min interval changes) for mouse speed really resolve the issue (nor did it tend to accept the changes I tried). To me, it feels that the poll speed is too high as it does the thing that a usb mouse will do if the poll speed is too high: rubber banding and cursor dances when it finally catches up. It's usable, but sub-optimal. For now, I'm sticking with USB for usability but am around to try things on the BT side. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
Additionally, I've noted that I really need to disable/re-enable bluetooth to re-associate with the same device that I've unpaired, even with PPA. My BT mouse is usable, but significantly more laggy than the same mouse used via it's 2.4ghz usb, and I use this same model mouse in BT with win10 and linux on other machines with great results. Not sure this isn't a more general issue though, but figured I'd mention it, even if it is somewhat off-topic for this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
I also just installed on a pi 4 and had the same issue -- devices worked but would not persist across reboots, and then successive re-adds were... strange, unreliable, etc. Lots of "it appears to work but doesn't." Tried the PPA packages and it worked at first, but was seriously inconsistent at adding and removing devices. I downgraded the PPA packages back to originals and still couldn't reliably add devices. I re-upgraded to PPA packages and the bluetooth was essentially working less than ever. Since it felt like a software issue, like configurations and "sessions" were being munged, I killed BT, searched around and wiped out /var/lib/bluetooth/* (which appeared to have multiple base addresses???) and then I was able to clean out gnome's ui and re-add and things now persist across reboots. To me, this seems like the PPA fixes the issue, but the original packages created a state where there were multiple stale / conflicting states in /var/lib/bluetooth that you must disabled bt, clean, then re-enable / reboot and things work. It almost feels like the original packages had the BT adapter changing addresses each boot or similar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
Well, I see the 20.04.1 live image still has a problem installing (NVIDIA?) drivers during the initial install that was in the original 20.04 release. I shall try again without the drivers install option. I was trying a minimal clean install this time if that makes any difference for the analysis. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890912] Re: Plasma desktop icons won't double tap open with synaptics driver
Marking as invalid because, for whatever reason, the bug doesn't reproduce for me now on a new test user, and the behavior appears to be related to my previous user configuration. I'll investigate further and figure out what's going on and report a bug if warranted. ** Changed in: kde-cli-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890912 Title: Plasma desktop icons won't double tap open with synaptics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1890912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890912] [NEW] Plasma desktop icons won't double tap open with synaptics driver
Public bug reported: Original Use Case: Fresh Kubuntu 20.04 install. Restored home directory backup. Installed xserver-xorg-input-synaptics 1.9.1-1ubuntu3 because I prefer its scrolling behavior and general feel with my laptop's touch pad. Double tap on desktop icons fails to open reliably (maybe works once). Confirmed that double tap opens things and operates normally everywhere else I tested. Testing Performed / Variables Eliminated / Use Case Reproduced: Fresh user created. Double tap works as expected with synaptics driver. Adjusted touchpad settings in system settings, applied. Double tap on desktop is now broken. Double click with button still works however. Tried reverting all settings for touchpad, but nothing fixes across multiple logins. Issue is resolved by removing ~/.config/touchpadrc and logging in again. Double tap works as expected, but any change via touchpad settings dialog will break again. Current Workaround: Remove touchpadrc and live with default settings or remove synaptics driver and have less touchpad features / tuning / less ideal scrolling behavior, IMHO of course. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kde-cli-tools 4:5.18.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Aug 8 12:14:07 2020 ExecutablePath: /usr/bin/kcmshell5 InstallationDate: Installed on 2020-08-07 (1 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kde-cli-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890912 Title: Plasma desktop icons won't double tap open with synaptics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Just following up to note that this still reproduces (cpu core hang and backtrace) on Eoan with the backport-iwlwifi-dkms package removed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
@You-Sheng, I have done that. It has ran all day without issue. Having said that, I am very confused because I previously had the issue with Eoan with all updates but no backport-iwlwifi-dkms installed. I don't know what has changed. In the apport information, it seems to confirm this--updated stock generic kernel with issue. I'm so confused at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Current results... Eoan iso live boot: cores hang and recover Eoan install + all updates: cores hang and recover Eoan install + all updates + backport iwlwifi ppa: cannot associate Eoan install + all updates + backport iwlwifi from Eoan: Kernel panic Bionic + all updates: Everything works fine. Not sure where to go from here, but wanted to communicate the results of all the testing I did. Is there some special version of the linux-firmware package I should be using? Wayne -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
** Attachment added: "dmesg showing the boot that used the suggested ppa backport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+attachment/5311841/+files/dmesg.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
** Attachment added: "Relevant syslog from failed auth." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+attachment/5311840/+files/network-auth-fail.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
I tried the PPA and authentication failed to the network. I think the applicable messages are as follows: Dec 11 15:24:28 malt NetworkManager[888]: [1576099468.0140] device (wlp6s0): supplicant interface state: associating -> associated Dec 11 15:24:28 malt NetworkManager[888]: [1576099468.0140] device (p2p-dev-wlp6s0): supplicant management interface state: associating -> associated Dec 11 15:24:28 malt NetworkManager[888]: [1576099468.0206] device (wlp6s0): supplicant interface state: associated -> 4-way handshake Dec 11 15:24:28 malt NetworkManager[888]: [1576099468.0206] device (p2p-dev-wlp6s0): supplicant management interface state: associated -> 4-way handshake Dec 11 15:24:28 malt wpa_supplicant[889]: nl80211: kernel reports: NLA_F_NESTED is missing Dec 11 15:24:28 malt wpa_supplicant[889]: wlp6s0: WPA: Failed to set PTK to the driver (alg=3 keylen=16 bssid=9c:3d:cf:1e:d1:05) Dec 11 15:24:28 malt kernel: [ 543.037235] wlp6s0: deauthenticating from 9c:3d:cf:1e:d1:05 by local choice (Reason: 1=UNSPECIFIED) Dec 11 15:24:28 malt wpa_supplicant[889]: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=9c:3d:cf:1e:d1:05 reason=1 locally_generated=1 Dec 11 15:24:28 malt wpa_supplicant[889]: wlp6s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Dec 11 15:24:28 malt wpa_supplicant[889]: wlp6s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="chewies-5G" auth_failures=1 duration=10 reason=WRONG_KEY Dec 11 15:24:28 malt wpa_supplicant[889]: wlp6s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="chewies-5G" auth_failures=2 duration=20 reason=CONN_FAILED I am adding the full syslog relevant section and dmesg from previous boot with the ppa version loaded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
@You-Sheng, I honestly have been VERY out of the loop on linux kernel/hardware since the 2.4-2.6 days. I've been stuck in AWS for years ;) Can you verify I'm understanding the situation correctly? It appears that the kernel in Eoan contains a driver that contains this issue, and the backport-iwlwifi package will receive the fix first in the form of a "much more recent driver from intel" made possible by DKMS? Is this interpretation correct? I'll go ahead and try this PPA and verify if it fixes the issue! Thinking about it a bit, does this mean that the firmware eaon ships is incompatible with the upstream kernel's driver, or that the upstream kernel driver just has a bug? Are the firmware / kernels tied together, and how do we get the right firmware that will work with the backport- iwlwifi packages? Thanks in advance for the clarification. Trying to come up to speed again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Please note that I went ahead and reinstalled on another drive and completely updated, so there is a system ready to go with this issue--I just have to boot into it. It's a slow USB external drive, so, gross, but it works. Also, I'm a former c developer with some kernel dev experience in the past. I'm a bit (lot) rusty, but just so you're aware, I can probably deliver some value in troubleshooting this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311221/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
apport information ** Tags added: apport-collected eoan ** Description changed: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-12-09 (0 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-24-generic N/A + linux-backports-modules-5.3.0-24-generic N/A + linux-firmware1.183.2 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/31/2015 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F9 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Z97-HD3 + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: Gigabyte Technology Co., Ltd. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: Z97-HD3 + dmi.product.sku: To be filled by O.E.M. + dmi.product.version: To be filled by O.E.M. + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311208/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311218/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311212/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311213/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311210/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311209/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311222/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311215/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311220/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311217/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311219/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311216/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311211/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1855637/+attachment/5311214/+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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855637] [NEW] Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Public bug reported: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "dmesg output from when the issue happens." https://bugs.launchpad.net/bugs/1855637/+attachment/5310915/+files/intel-wifi-dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1855637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847862] [NEW] gdebi UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte
Public bug reported: Tried to use gdebi to install dependencies for daemonsync_2.2.0.0059_amd64.deb sync server (https://www.daemon- tools.cc/products/daemonsync) on Ubuntu 18.04.3 LTS (4.15.0-65-generic). Gdebi execution failed while building the dependency tree. sudo gdebi daemonsync_2.2.0.0059_amd64.deb Reading package lists... Done Building dependency tree Reading state information... Done Reading state information... Done Traceback (most recent call last): File "/usr/bin/gdebi", line 103, in debi.show_description() File "/usr/share/gdebi/GDebi/GDebiCli.py", line 96, in show_description print(self._deb["Description"]) File "/usr/share/gdebi/GDebi/DebPackage.py", line 39, in __getitem__ return self._sections[item] UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte ** Affects: gdebi (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/1847862 Title: gdebi UnicodeDecodeError: 'utf-8' codec can't decode byte 0x92 in position 504: invalid start byte To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1847862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847088] [NEW] Cups appends extra page with %EndDocument %%EOF to every print
Public bug reported: I am using cups with a printer connected via samba. The Printer is a Kyocera Taskalfa 5021ci. Every print I make through cups results in a last page with only %%EndDocument %%EOF on it. I've tried to debug this further and if I print with smbclient directly like this: $smbclient -W DOMAIN -U USER //server/printer Unable to initialize messaging context Enter NET.CHALMERS.SE\jochens's password: Try "help" to get a list of possible commands. smb: \> print test.pdf putting file test.pdf as test.pdf (1947.9 kb/s) (average 1947.9 kb/s) smb: \> it works without the extra page. I've tried to find the filter that adds the extra page but can not find it. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/log/cups/error_log with debugging turned on" https://bugs.launchpad.net/bugs/1847088/+attachment/5295138/+files/error_log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847088 Title: Cups appends extra page with %EndDocument %%EOF to every print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792085] Re: MTP not working/very slow on Bionic
Hi everyone. The slow access is also observed by me on Xubuntu 18.04. It affects all tools using MTP (Thunar, Shotwell) when opening folders with many files. In all cases the application stops responding and some (like Thunar) eventually crash entirely. Neither disabling nor enabling previews in Thunar has any effect. As reported by the others, it works just fine with Xubuntu 16.04. Also, the output of "dmesg -w" shows no issue. It shows that the device connects fine -- once after hooking it up to USB and the second time after allowing the MTP access on Android. I will try to get the "journalctl" log output on Sunday, when I get access to the affected machine again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1792085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766969] Re: DNS cannot be resolved in Hotel Hotspot
I have the latest systemd recommended by #1727237, and this issue still occurs at Starbucks as well. The Starbucks WIFI defect is #1767900 which appears to be a duplicate of this one. ii systemd237-3ubuntu10 amd64system and service manager I'm in a Starbucks now. #1727237 (the systemd above) does not fix my issue. aruba.odyssys.net is still not resolved using the stub- resolv.conf file (linked from /etc/resolv.conf). cd /etc sudo /bin/rm resolv.conf sudo /bin/ln -s ../run/systemd/resolve/resolv.conf resolv.conf Using the original resolv.conf however, as per the changes above, does work. I did not make any changes to /etc/hosts. The real resolv.conf above contains the google nameservers and is sufficient to resolve aruba.odyssys.net. nameserver 8.8.8.8 nameserver 8.8.4.4 search home -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766969 Title: DNS cannot be resolved in Hotel Hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767701] Re: amdgpu WQHD resolution not working
** Attachment added: "xorg log when booting kernel 4.16.5" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767701/+attachment/5129595/+files/xorg_4.16.5.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767701 Title: amdgpu WQHD resolution not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767701] [NEW] amdgpu WQHD resolution not working
Public bug reported: After upgrade to bionic the highest detected resolution of my monitor was 1920x1200 instead of the 2560x1440 that it is capable of and that worked previously. My graphics card is a Radeon RX480 and this seems to be related to the AMDGPU DC changes in kernel 4.15. Passing amdgpu.dc=0 as boot parameter fixes the issue and the correct resolution is detected. This is also fixed on latest 4.16.5 upstream kernel from the kernel ppa, i.e. the maximum resolution is correctly detected without amdgpu.dc=0 as boot parameter. attached are the xorg files after booting the 4.15 and 4.16.5 kernels both without amdgpu.dc=0. The main difference seems to be the probed modes. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "xorg log when booting kernel 4.15" https://bugs.launchpad.net/bugs/1767701/+attachment/5129594/+files/xorg_4.15.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767701 Title: amdgpu WQHD resolution not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747281] Re: 18.04 nvidia driver installation failure
Successful installation & reboot with the following configuration: [38.228] X.Org X Server 1.19.6 Release Date: 2017-12-20 [38.229] X Protocol Version 11, Revision 0 [38.229] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [38.229] Current Operating System: Linux panther2 4.15.0-12-generic #13-Ubun tu SMP Thu Mar 8 06:24:47 UTC 2018 x86_64 [38.229] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic roo t=UUID=d4cab1b0-82f2-4610-9727-0b9494262bee ro quiet splash vt.handoff=1 [38.229] Build Date: 13 March 2018 10:09:13AM [38.229] xorg-server 2:1.19.6-1ubuntu3 (For technical support please see htt p://www.ubuntu.com/support) [38.229] Current version of pixman: 0.34.0 ** Changed in: software-properties (Ubuntu) Status: Confirmed => 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/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752950] Re: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
Description:Ubuntu Bionic Beaver (development branch) Release:18.04 4.15.0-11-generic #12-Ubuntu SMP Fri Feb 23 18:39:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752950 Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1752950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747281] Re: 18.04 nvidia driver installation failure
This report pre-dates #1752053 and was submitted because the initial NVIDIA driver installation failed. Bug #1752053 reports and already installed NVIDIA driver being broken by a more recent update. Not convinced these are duplicates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 953875] Re: Encrypted swap no longer mounted at bootup
I am running Ubuntu 14.04.5 LTS and the offset parameter to preserve the UUID simply does not work for me. A later version of Ubuntu on the same PC shows there is a PARTUUID for the encrypted swap partition, but this is not visible in 14.04. The UUID for the cryptswap partition is always lost after reboot of 14.04. Reverting back to using a device ID in conjunction with the solution in Comment #22 works, but I would like to add an additional piece of helpful information. I have a multi-disk system and periodically the /dev/sd_ drive IDs re-order themselves. Normally, UUIDs would solve this problem, but we can't use a UUID in this instance. This post pointed me in the direction of a solution (https://gebloggendings.wordpress.com/2016/06/14/cryptsetup- etccrypttab-a-workaround-for-gpt-partuuid-support/). Turns out you can use the /dev/disk/by-id alias for the partition ID in /etc/crypttab, as these drive IDs are also unique, i.e. drive make, model & serial number. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953875 Title: Encrypted swap no longer mounted at bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/953875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745060] Re: dashtodock package crashes gnome-shell when extension is enabled
Installing gnome-shell-extensions is not required to replicate this bug. 1) Install the gnome-shell-extension-dashtodock package; the detailed installation shell reports that portions of this package were replaced by gnome-shell-extension-ubuntu-dock. 2) Start the Tweak tool and select the extensions tab; Tweak tool will freeze and eventually abort. 3) Logout and login. 4) Start the Tweak tool and select the extensions tab; DashToDock is now included in the list of extensions. 5) Disable Ubuntu Dock; dock is not removed from the screen. 6) Enable DashToDock; eventually gnome-shell session aborts and GDM login screen is displayed. 7) Login; gnome-shell session starts to come up, but then aborts and GDM login screen is displayed. Traceback from syslog: Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: == Stack trace for conte xt 0x56332099b170 == Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #0 0x563320dc3d38 i /u sr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/theming.js:200 (0x 7f88ba230340 @ 201) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #1 0x7ffddc31b5d0 I re source:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #2 0x563320dc3c80 i /u sr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/theming.js:79 (0x7 f88ba22fef0 @ 451) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #3 0x7ffddc31c1e0 I re source:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #4 0x7ffddc31c2a0 b re source:///org/gnome/gjs/modules/_legacy.js:18 (0x7f88f40c2808 @ 36) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #5 0x7ffddc31c360 b re source:///org/gnome/gjs/modules/_legacy.js:114 (0x7f88f40c2d58 @ 178) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #6 0x563320dc3b60 i /u sr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:363 (0x 7f88ba21a450 @ 2158) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #7 0x7ffddc31cff0 I re source:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #8 0x7ffddc31d0c0 b re source:///org/gnome/gjs/modules/_legacy.js:18 (0x7f88f40c2808 @ 36) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #9 0x7ffddc31d180 b re source:///org/gnome/gjs/modules/_legacy.js:114 (0x7f88f40c2d58 @ 178) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #10 0x563320dc3a98 i / usr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:1744 ( 0x7f88ba220a28 @ 259) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #11 0x7ffddc31de10 I r esource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #12 0x563320dc3a08 i / usr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/docking.js:1678 ( 0x7f88ba220890 @ 115) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #13 0x7ffddc31ea10 I r esource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #14 0x7ffddc31eac0 b r esource:///org/gnome/gjs/modules/_legacy.js:18 (0x7f88f40c2808 @ 36) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #15 0x7ffddc31eb70 b r esource:///org/gnome/gjs/modules/_legacy.js:114 (0x7f88f40c2d58 @ 178) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #16 0x563320dc3980 i / usr/share/gnome-shell/extensions/dash-to-d...@micxgx.gmail.com/extension.js:16 ( 0x7f88bb8e2c48 @ 20) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #17 0x563320dc38d0 i r esource:///org/gnome/shell/ui/extensionSystem.js:129 (0x7f88d86b4670 @ 408) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #18 0x563320dc3838 i r esource:///org/gnome/shell/ui/extensionSystem.js:171 (0x7f88d86b4780 @ 241) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #19 0x563320dc37b8 i r esource:///org/gnome/shell/ui/extensionSystem.js:318 (0x7f88d86b4e68 @ 13) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #20 0x7ffddc31ff10 b r esource:///org/gnome/gjs/modules/signals.js:126 (0x7f88f40e2b38 @ 386) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #21 0x563320dc36d8 i r esource:///org/gnome/shell/misc/extensionUtils.js:184 (0x7f88d86b5a28 @ 360) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #22 0x7ffddc320ba0 I r esource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f88f40c2bc0 @ 71) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #23 0x563320dc3640 i r esource:///org/gnome/gjs/modules/lang.js:97 (0x7f88f40d8450 @ 101) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #24 0x7ffddc322050 b r esource:///org/gnome/shell/misc/fileUtils.js:27 (0x7f88d86b5e68 @ 323) Feb 6 18:45:40 panther2 org.gnome.Shell.desktop[3863]: #25 0x563320dc3580 i r esource:///org/gnome/shell/misc/extensionUtils.js:189 (0x7f88d86b5ab0 @
[Bug 1747281] Re: 18.04 nvidia driver installation failure
Wrong package picked up?! ** Package changed: gnome-shell-extension-dashtodock (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747281] [NEW] 18.04 nvidia driver installation failure
Public bug reported: Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Despite the recent switch to Xorg from Wayland, the NVIDIA driver installed via the Additional Drivers tab in software-properties-gtk still does not properly install the driver. Although the initial install appears to successfully complete, the system does not load properly on the next reboot and yields an unusable system; GDM login is never displayed. Looking at the log from the reboot following the NVIDIA driver install, the Nouveau driver appears to still be in use for video, while the NVIDIA driver is associated with HDMI audio: Feb 3 12:23:38 panther2 kernel: [2.097370] nouveau :01:00.0: NVIDIA GF1 16 (0cf200a1) Feb 3 12:23:38 panther2 kernel: [2.212100] usb 4-1: new full-speed USB devi ce number 2 using ohci-pci Feb 3 12:23:38 panther2 kernel: [2.226839] nouveau :01:00.0: bios: vers ion 70.26.3a.00.01 Feb 3 12:23:38 panther2 kernel: [2.376254] nouveau :01:00.0: fb: 1024 M iB GDDR5 Feb 3 12:23:38 panther2 kernel: [3.676249] [TTM] Zone kernel: Available gr aphics memory: 2019142 kiB Feb 3 12:23:38 panther2 kernel: [3.676250] [TTM] Initializing pool allocato r Feb 3 12:23:38 panther2 kernel: [3.676255] [TTM] Initializing DMA pool allo cator Feb 3 12:23:38 panther2 kernel: [3.676270] nouveau :01:00.0: DRM: VRAM: 1024 MiB Feb 3 12:23:38 panther2 kernel: [3.676272] nouveau :01:00.0: DRM: GART: 1048576 MiB Feb 3 12:23:38 panther2 kernel: [3.676276] nouveau :01:00.0: DRM: TMDS table version 2.0 Feb 3 12:23:38 panther2 kernel: [3.676277] nouveau :01:00.0: DRM: DCB v ersion 4.0 Feb 3 12:23:38 panther2 kernel: [3.676280] nouveau :01:00.0: DRM: DCB o utp 00: 02000300 Feb 3 12:23:38 panther2 kernel: [3.676282] nouveau :01:00.0: DRM: DCB o utp 01: 01000302 00020030 Feb 3 12:23:38 panther2 kernel: [3.676284] nouveau :01:00.0: DRM: DCB o utp 02: 04011380 Feb 3 12:23:38 panther2 kernel: [3.676285] nouveau :01:00.0: DRM: DCB o utp 03: 08011382 00020030 Feb 3 12:23:38 panther2 kernel: [3.676287] nouveau :01:00.0: DRM: DCB o utp 04: 02022362 00020010 Feb 3 12:23:38 panther2 kernel: [3.676288] nouveau :01:00.0: DRM: DCB c onn 00: 1030 Feb 3 12:23:38 panther2 kernel: [3.676290] nouveau :01:00.0: DRM: DCB c onn 01: 00010130 Feb 3 12:23:38 panther2 kernel: [3.676291] nouveau :01:00.0: DRM: DCB c onn 02: 2261 Feb 3 12:23:38 panther2 kernel: [3.677453] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). Feb 3 12:23:38 panther2 kernel: [3.677454] [drm] Driver supports precise vb lank timestamp query. Feb 3 12:23:38 panther2 kernel: [3.728374] nouveau :01:00.0: DRM: MM: u sing COPY0 for buffer copies Feb 3 12:23:38 panther2 kernel: [3.847607] nouveau :01:00.0: DRM: alloc ated 1920x1080 fb: 0x6, bo 8e45e7246000 Feb 3 12:23:38 panther2 kernel: [3.859190] fbcon: nouveaufb (fb0) is primar y device Feb 3 12:23:38 panther2 kernel: [3.859275] Console: switching to colour fra me buffer device 240x67 Feb 3 12:23:38 panther2 kernel: [3.859314] nouveau :01:00.0: fb0: nouve aufb frame buffer device Feb 3 12:23:38 panther2 kernel: [3.936124] [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) LoadModule: "gl x" Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Loading /usr/li b/xorg/modules/extensions/libglx.so Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) Module glx: ven dor="X.Org Foundation" Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011compiled for 1.1 9.6, module version = 1.0.0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: #011ABI class: X.Org Server Extension, version 10.0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nvidia as autoconfigured driver 0 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nouveau as autoconfigured driver 1 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nvidia as autoconfigured driver 2 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched nouveau as autoconfigured driver 3 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched modeset ting as autoconfigured driver 4 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched fbdev a s autoconfigured driver 5 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Matched vesa as autoconfigured driver 6 Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (==) Assigned the dr iver to the xf86ConfigLayout Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (II) LoadModule: "nv idia" Feb 3 12:24:08 panther2 /usr/lib/gdm3/gdm-x-session[1234]: (WW) Warning, couldn 't open module nvidia Feb 3 12:24:08 panther2 /usr
[Bug 1747281] Re: 18.04 nvidia driver installation failure
Associate with the correct package. ** Package changed: ubuntu => software-properties (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747281] Re: 18.04 nvidia driver installation failure
Additional syslog data. ** Attachment added: "nvidia_failed_install.log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1747281/+attachment/5048817/+files/nvidia_failed_install.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747281 Title: 18.04 nvidia driver installation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1747281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745600] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of pac
Public bug reported: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 Failure occurred during software update; Proposed updates enabled. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13 Uname: Linux 4.13.0-30-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 01:51:15 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental3ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-hPW4rc/084-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2018-01-13 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745600 Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1745600/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745060] [NEW] dashtodock package crashes gnome-shell when extension is enabled
Public bug reported: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 gnome-shell-extension-dashtodock: Installed: (none) Candidate: 62-1 Version table: 62-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages Having previously installed gnome-shell-extensions because the "Applications Menu" URL extension was broken, I uninstalled the URL version of DashToDock, which worked correctly in 18.04 alpha1. I then installed the gnome-shell-extension-dashtodock package. When I enabled dashtodock in the Gnome Tweek tool, there was a delay during which gnome-shell froze up, and then I was dumped out to GDM. Subsequent attempts to login quickly resulted in gnome-shell crashing and being returned to GDM. I also tried enabling the extension using a clean, unused user home directory in case there was incompatible extension data left over after uninstalling the URL version of the extension (see below), but gnome- shell still froze up and crashed out to GDM. I had expected the package version of DashToDock to perform the same as the URL version. The reason for switching was because an Ubuntu development forum user had informed me the URL gnome extensions were deprecated. Recovery from the failure: - Boot into a recovery console or another Linux install. - Temporarily replace the user's home directory with a clean, unused user home directory. - Boot 18.04 and login with the unused user home directory that does not have dashtodock enabled. - Uninstall gnome-shell-extension-dashtodock. - Boot into a recovery console or another Linux install. - Restore user's home directory and reboot. I then successfully enabled Ubuntu dock, but was surprised to see it use my last settings from the URL version of DashToDock extension. There is probably a more clever way to recover from this failure by disabling dashtodock from a recovery console, but I'm not that well versed in Gnome3. ** Affects: gnome-shell-extension-dashtodock (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/1745060 Title: dashtodock package crashes gnome-shell when extension is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1745060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1725441] Re: Synaptic package manager not working in 17.10
*** This bug is a duplicate of bug 1551951 *** https://bugs.launchpad.net/bugs/1551951 This worked for me and I thank you. Has to be entered at each use. Patch in Wayland or synaptic would be better. This does solve problem. On 12/2/17 7:36 AM, Brad Shackelford wrote: > *** This bug is a duplicate of bug 1551951 *** > https://bugs.launchpad.net/bugs/1551951 > > The fix listed by Mushfequr Rahman worked for me > > Run the following in Terminal > xhost +si:localuser:root > > Thanks > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725441 Title: Synaptic package manager not working in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1725441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713993] [NEW] cifs mount error when specifying prefixpath and having as part of the path
Public bug reported: Recently some of my cifs mounts have stopped working. This could have happened due to an upgrade on the server (over which I do not have any control) or if there was a package update to cifs-utils. The issue I am seeing is if I try to mount a subdirectory of the network share, by appending the path to the unc when mounting, the mount fails with mount error(22): invalid argument $mount.cifs -vvv //sol.ita.chalmers.se/groups/mc2-common-photonics -o credentials=/etc/smbcredentials /mnt/PhotonicsGroup/ domain=NET mount.cifs kernel mount options: ip=129.16.226.60,unc=\\sol.ita.chalmers.se\groups,user=jochens,,domain=NET,prefixpath=mc2-common-photonics,pass= mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) If I specify the prefixpath via an option the mount succeeds. $mount.cifs -vvv //sol.ita.chalmers.se/groups/ -o credentials=/etc/smbcredentials,prefixpath=mc2-common-photonics /mnt/PhotonicsGroup/ domain=NET mount.cifs kernel mount options: ip=129.16.226.60,unc=\\sol.ita.chalmers.se\groups,prefixpath=mc2-common-photonics,user=jochens,,domain=NET,pass= I don't really see any difference between the mount options, so I don't understand what's going on. Also smbclient and gvfs can mount the path without issues. $ mount.cifs -V mount.cifs version: 6.6 $ lsb_release -rd Description:Ubuntu 17.04 Release:17.04 $ uname -a Linux MC2-F093 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:55:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: cifs-utils (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/1713993 Title: cifs mount error when specifying prefixpath and having as part of the path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1713993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700963] [NEW] Vitables incompatible with python-tables
Public bug reported: The vitables version 2.1-1 which is included in 17.04 fails when starting with the exception: Creating the Query results file... Traceback (most recent call last): File "/usr/share/vitables/vitables/h5db/dbDoc.py", line 115, in openH5File h5file = tables.openFile(self.filepath, self.mode) AttributeError: 'module' object has no attribute 'openFile' Please, if you think it is a bug, report it to developers. File creation failed due to unknown reasons! Please, have a look to the last error displayed in the logger. If you think it's a bug, please report it to developers. This is due to python-tables 3.3.0-5 distributed with ubuntu which changes API and vitables is not compatible. This is fixed upstream see https://github.com/uvemas/ViTables/issues/54 for upstream bug report. ** Affects: vitables (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/1700963 Title: Vitables incompatible with python-tables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vitables/+bug/1700963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog
*** This bug is a duplicate of bug 1280300 *** https://bugs.launchpad.net/bugs/1280300 Yep still get it in 17.04, also to be noted is that while using vmware, the desktop does not lock until I click on something else, causing the vm to lose input focus. So I can leave my computer for far longer than the set lock time and it will not lock until somebody clicks somewhere on the unity launcher or another window. IDK how this has existed since 2011, this is a glaring security bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/830348 Title: desktop contents briefly visible on resume from suspend before lock dialog To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/830348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149837] Missed voice message: 9:59AM
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/149837 Title: update-manager crashed with ImportError in module>() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/149837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 331675] Re: try it
Greetings, Have you ever tried that stuff before? It's something gorgeous, just take a look http://comprehensive.rebelselector.com/c4c5 ulischroeder -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/331675 Title: package linux-image-2.6.28-8-generic 2.6.28-8.24 failed to install/upgrade: subprocess post-installation script returned error exit status 2 (ImportError: No module named NvidiaDetector) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/331675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655450] Re: monitors not disconnected after undocking
Also confirmed fixed on 4.10.0-041000rc3-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655450 Title: monitors not disconnected after undocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655450] Re: monitors not disconnected after undocking
This happened after upgrade to 16.10 I believe (unfortunately I am not 100% sure about this). I can confirm that this is fixed using 4.9.2-040902-generic from mainline kernels. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream ** Description changed: - I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking station. The laptop is connected through the docking station to 2 external monitors when docked. When undocking the laptop, the laptop does not detect that the monitors have been disconnected (leaving X in a somewhat unworkable state). Even worse, when undocking with thelid closed (which would previously have resulted in suspend) the laptop now starts working hard and the fan starts spinning up (which is particularly bad when forgetting about this and placing the laptop in a bag). The laptop also becomes very unresponsive to X actions, e.g. xrandr --query takes a a couple of seconds, switching to the console takes > 10s. + I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking station. The laptop is connected through the docking station to 2 external monitors when docked. When undocking the laptop, the laptop does not detect that the monitors have been disconnected (leaving X in a somewhat unworkable state). Even worse, when undocking with thelid closed (which would previously have resulted in suspend) the laptop now starts working hard and the fan starts spinning up (which is particularly bad when forgetting about this and placing the laptop in a bag). The laptop also becomes very unresponsive to X actions, e.g. xrandr --query takes a a couple of seconds, switching to the console takes > 10s. This seems to be related to the following Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1392885 which reports almost identical issues. I have not been able to try a new kernel yet to see if issues are fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-30-generic 4.8.0-30.32 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jschrod2726 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jschrod2726 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 10 21:28:42 2017 HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c InstallationDate: Installed on 2016-10-01 (101 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 13d3:5248 IMC Networks - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 13d3:5248 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FB006AMS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=a43e313c-5c49-4859-a1aa-4446f2b9c455 ro quiet splash RelatedPackageVersions: - linux-restricted-modules-4.8.0-30-generic N/A - linux-backports-modules-4.8.0-30-generic N/A - linux-firmware1.161.1 + linux-restricted-modules-4.8.0-30-generic N/A + linux-backports-modules-4.8.0-30-generic N/A + linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB006AMS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB006AMS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB006AMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB006AMS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655450 Title: monitors not disconnected after undocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656218] [NEW] QT4 apps fail with symbol lookup error
Public bug reported: Running 16.10 several Qt4 apps fail for me with symbol lookup errors. Two examples are: $ kcachegrind kcachegrind: symbol lookup error: kcachegrind: undefined symbol: _ZNK12QApplication17isSessionRestoredEv $ python -m pyqtgraph Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 163, in _run_module_as_main mod_name, _Error) File "/usr/lib/python2.7/runpy.py", line 111, in _get_module_details __import__(mod_name) # Do not catch exceptions initializing package File "/usr/lib/python2.7/dist-packages/pyqtgraph/__init__.py", line 13, in from .Qt import QtGui File "/usr/lib/python2.7/dist-packages/pyqtgraph/Qt.py", line 104, in from PyQt4 import QtGui, QtCore, uic ImportError: /usr/lib/python2.7/dist-packages/PyQt4/QtGui.x86_64-linux-gnu.so: undefined symbol: _ZN15QSessionManager16staticMetaObjectE I suspect this applies to many more qt4 packages (and I've found several similar bugs, e.g. #1534421). Some googling seems to indicate that this due to a version mismatch? ** Affects: kdepim (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/1656218 Title: QT4 apps fail with symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1656218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655450] [NEW] monitors not disconnected after undocking
Public bug reported: I have a Lenovo X1 Carbon (4th gen) and using the Lenovo one-link+ docking station. The laptop is connected through the docking station to 2 external monitors when docked. When undocking the laptop, the laptop does not detect that the monitors have been disconnected (leaving X in a somewhat unworkable state). Even worse, when undocking with thelid closed (which would previously have resulted in suspend) the laptop now starts working hard and the fan starts spinning up (which is particularly bad when forgetting about this and placing the laptop in a bag). The laptop also becomes very unresponsive to X actions, e.g. xrandr --query takes a a couple of seconds, switching to the console takes > 10s. This seems to be related to the following Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1392885 which reports almost identical issues. I have not been able to try a new kernel yet to see if issues are fixed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-30-generic 4.8.0-30.32 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jschrod2726 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 10 21:28:42 2017 HibernationDevice: RESUME=UUID=de3940cc-d877-44b6-9b33-16a8abd6701c InstallationDate: Installed on 2016-10-01 (101 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:5248 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FB006AMS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-30-generic.efi.signed root=UUID=a43e313c-5c49-4859-a1aa-4446f2b9c455 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB006AMS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB006AMS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB006AMS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB006AMS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655450 Title: monitors not disconnected after undocking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312236] Re: No dvorak layout option
@iamsylvie, I have a device that I can test on. However, I am not able to build the ubuntu-keyboard project at this time on Ubuntu 16.04. (I might be able to with a VM of with 15.04.) I think the special characters could either stay where they are or do the same move from a full-sized keyboard to dvorak layout (e.g. '[' to '/' and ']' to '='). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312236 Title: No dvorak layout option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1312236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537398] Re: build fails - cannot find feature maliit-defines
I have a similar issue when trying to build ubuntu-sdk-15.04 armhf on Ubuntu 16.04.1: config.pri:15: Cannot find feature maliit-defines Project ERROR: Cannot find /var/lib/lxd/containers/device-armhf/rootfs/usr/share/qt5/mkspecs/features/maliit-defines.prf. Probably Maliit framework not installed The only maliit-defines.prf that I have on my file system is: /usr/lib/x86_64-linux-gnu/qt5/mkspecs/features/maliit-defines.prf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1537398 Title: build fails - cannot find feature maliit-defines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1537398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86184] Re: Can't change cursor style using Compiz.
Thanks for letting me know. On Tue, Nov 15, 2016, 6:15 PM G.P.M wrote: > ** Tags removed: desktop-bugscrub-triaged wily > ** Tags added: no-one-seems-to-care > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (459647). > https://bugs.launchpad.net/bugs/86184 > > Title: > Can't change cursor style using Compiz. > > Status in compiz package in Ubuntu: > Confirmed > > Bug description: > Binary package hint: compiz > > With compiz running, choosing a nondefault cursor style, such as > "redglass" or any of the other packaged options, only seems to > actually change the cursor when it is over Firefox. Over every other > window or the desktop the default cursor persists stubbornly. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/86184/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/86184 Title: Can't change cursor style using Compiz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/86184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565077] Re: Rhythmbox missing a GStreamer plug-in
It was a clean install of 16.04 and I encountered this very early on, i.e. I had not installed many additional packages yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565077 Title: Rhythmbox missing a GStreamer plug-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1565077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565077] Re: Rhythmbox missing a GStreamer plug-in
I should clarify it was a clean install of Ubuntu Gnome 16.04. Perhaps the problem is in the Gnome branch, but not the main, Unity branch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565077 Title: Rhythmbox missing a GStreamer plug-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1565077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566359] Re: Date and Time conflict with Windows 8.1 dual boot with Ubuntu 16.04 Daily Build
Previously, (e.g. 14.04) this could be fixed by adding "UTC=no" to the '/etc/default/rcS' file. This does not appear to work in 16.04 with the 4.4.0-18-generic kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566359 Title: Date and Time conflict with Windows 8.1 dual boot with Ubuntu 16.04 Daily Build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1566359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565077] [NEW] Rhythmbox missing a GStreamer plug-in
Public bug reported: Rhythmbox was not able to play some of my FLAC files until I installed the gstreamer1.0-pulseaudio plug-in. Description:Ubuntu Xenial Xerus (development branch) Release:16.04 rhythmbox: Installed: 3.3-1ubuntu6 Candidate: 3.3-1ubuntu6 Version table: *** 3.3-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Playback stopped and the track was marked with a warning symbol. Opening the track properties dialog showed a GStreamer missing plug-in error message. Recommended the gstreamer1.0-pulseaudio plug-in be added to the 16.04 desktop distro to improve the out-of-box experience for less experienced users. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 1 21:05:20 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-31 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gstreamer rhythmbox xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565077 Title: Rhythmbox missing a GStreamer plug-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1565077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1493888] Re: FGLRX incompatible with gcc 5
Thanks Philip. The link to Ubuntu 15.10 boot hangs when starting lightdm helped me too. I had my system set to auto login to my user account but I could not log out or disable the auto login without having lightdm hang on startup. Now I can logout again! According to that link, in the Ubuntu 15.10 release notes, they said to uninstall fglrx before upgrading to 15.10. That would have avoided the problem lightdm hanging. I still have an issue where Ctrl-Alt-F1 to F6 do not work for me when fglrx is installed but that is probably a separate issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with gcc 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404623] Re: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
This error occurred while the Ubuntu Software Center was trying to automatically repair something on my system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404623 Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1404623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1479913] Re: SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol
I updated to the 3.19.0-26 kernel today and the fglrx-core package failed to install when dkms tried to install it. Switching to the fglx packages here in the proposed branch solved my issue. It would seem that these packages need to be promoted from the proposed branch since others will have issues with upgrading to the kernel. (Booting to the old kernel did not work. I guess that when the dkms failed to run for the new kernel, it also didn't run for the old kernel.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479913 Title: SRU request: fglrx.ko fails because of backported GPL-only 'pci_ignore_hotplug' symbol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1479913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385931] Re: package virtualbox (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
> this seems to be a problem of the official virtualbox, not the debian one, so I can't help :) Or some kind of conflict. It seems at least my problem was not doing a purge on the manually installed virtualbox-4.3 before installing virtualbox from Ubuntu. However, my error was different than what was initially reported! Anyway, the fix for me was to do: sudo apt-get purge virtualbox-4.3 && sudo apt-get install virtualbox This is the error I get if I just do a remove (not a purge) on virtualbox-4.3: Reading package lists... Done Building dependency tree Reading state information... Done virtualbox is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up virtualbox (4.3.18-dfsg-2ubuntu1) ... insserv: script virtualbox: service vboxdrv already provided! insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package virtualbox (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of virtualbox-qt: virtualbox-qt depends on virtualbox (= 4.3.18-dfsg-2ubuntu1); however: Package virtualbox is not configured yet. Package virtualbox-4.3 which provides virtualbox is not installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385931 Title: package virtualbox (not installed) 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/1385931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385931] Re: package virtualbox (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Do you have any other virtualbox in your system? Yes Did you correctly clean them up? No I had this issue happen by installing virtualbox-4.3_4.3.22-98236~Ubuntu~raring_amd64.deb using dpkg and then attempting to install the virtualbox package. However, even if I remove virtualbox-4.3 before installing virtualbox, the problem still occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385931 Title: package virtualbox (not installed) 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/1385931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
Affects me as well: Ubuntu 14.04 and Galaxy S3. Toggling USB debugging off and back on again had no effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310566] Re: indicator-multiload is not displayed
I tried raising this issue on bugzilla.gnome.org, but their opinion is that it is not a GNOME Shell problem (Comment #7) since the indicator-multiload graphs are displayed in a panel: https://bugzilla.gnome.org/show_bug.cgi?id=741887 Obviously, something changed somewhere between Ubuntu 12.04 & 14.04, but I do not currently have the necessary insight to know where the root cause is. Kind regards, Curt ** Bug watch added: GNOME Bug Tracker #741887 https://bugzilla.gnome.org/show_bug.cgi?id=741887 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310566 Title: indicator-multiload is not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1310566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1404295] [NEW] nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build
Public bug reported: Failed during update process ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.113-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-28-generic Date: Fri Dec 19 10:49:24 2014 InstallationDate: Installed on 2014-04-07 (256 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageVersion: 331.113-0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-25 (55 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1404295 Title: nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1404295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
Forgot to mention I am using Gnome3 shell, not Unity or KDE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
I tried applying the patch in comment 22 to my 14.04 installation (3.13.0-39-generic, upgraded from 12.04) and rebooting, but it didn't solve the problem with my Logitec webcam microphone. I still get the same error. ubuntu-drivers-common 1:0.2.91.7 is the currently installed version. Are they any other scripts that might be doing the same thing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310566] Re: indicator-multiload is not displayed
Used this in conjunction with Ubuntu 12.04 and Gnome Shell to display CPU, Network, and Disk graphs in the top bar . After upgrading to 14.04 and continuing to use Gnome Shell, the graphs no longer work, but the right click pull-down does work. Additionally, only one graph is now shown, despite having selected three, and it does not update properly. Please fix this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310566 Title: indicator-multiload is not displayed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/1310566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348430] [NEW] btrfs send does not work for snapshots in subvolumes
Public bug reported: If I create a snapshot, of a subvolume and try to use btrfs send it fails with "No such file or directory" # sudo btrfs sub create /testvol Create subvolume '//testvol' # sudo btrfs btrfs btrfsck btrfs-debug-treebtrfs-image btrfs-select-super btrfstune btrfs-calc-size btrfs-convert btrfs-find-root btrfs-map-logical btrfs-show-superbtrfs-zero-log # sudo btrfs sub list / ID 257 gen 16298 top level 5 path @ ID 276 gen 16298 top level 257 path testvol # sudo btrfs sub snap -r /t testvol/ tmp/ # sudo btrfs sub snap -r /testvol/ /test-snap Create a readonly snapshot of '/testvol/' in '//test-snap' # sudo btrfs sub list / ID 257 gen 16299 top level 5 path @ ID 276 gen 16299 top level 257 path testvol ID 277 gen 16299 top level 257 path test-snap # sudo btrfs send /test-snap/ > /dev/null At subvol /test-snap/ ERROR: open @/test-snap failed. No such file or directory This error has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=69401 Because ubuntu creates /home and / on subvolumes this currently prevents backup solutions based on btrfs send. ** Affects: btrfs-tools (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/1348430 Title: btrfs send does not work for snapshots in subvolumes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1348430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181944] Re: BTRFS is always full formatted
This just happened to my on Trusty Beta and killed my home partition. I used to do this routinely on all my systems and it has never been a problem before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181944 Title: BTRFS is always full formatted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1181944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653872] Re: KMS with Radeon HD4350 causes system to lock up completely
Unfortunately I do not own a PC with AMD card anymore, so I can't test. Cheers Jochen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/653872 Title: KMS with Radeon HD4350 causes system to lock up completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/653872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157643] Re: procps fail to start
With SpiderOak 5.0.4 installed and the nepomuk entry for 'fs.inotify.max_user_watches = 524288' commented out, the latest procps update (1:3.2.8-11ubuntu6.3) installed without error on my Ubuntu 12.04 desktop and upstart successfully started. I'll try uncommenting the nepomuk entry now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157643] Re: procps fail to start
Latest upgrade attempt for 12.04 (no work-arounds) was not successful. Additional info: cat /etc/sysctl.d/*.conf /etc/sysctl.conf | sudo sysctl -p - kernel.printk = 4 4 1 7 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 kernel.kptr_restrict = 1 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 net.ipv4.tcp_syncookies = 1 kernel.yama.ptrace_scope = 1 vm.mmap_min_addr = 65536 fs.inotify.max_user_watches = 524288 error: "Invalid argument" setting key "fs.inotify.max_user_watches" grep fs.inotify.max_user_watches /etc/sysctl.d/*.conf /etc/sysctl.d/30-nepomuk-inotify-limit.conf:fs.inotify.max_user_watches = 524288 /etc/sysctl.d/30-spideroak.conf:fs.inotify.max_user_watches = 65536 Now, the curious item here is the nepomuk entry. I may have launched it once just to look at it, but I do not actively use this application. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157643 Title: procps fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1157643/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240203] [NEW] package procps 1:3.2.8-11ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Problem occurred during btsync PPA upgrade I believe. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: procps 1:3.2.8-11ubuntu6.1 ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50 Uname: Linux 3.2.0-54-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Tue Oct 15 20:07:24 2013 DuplicateSignature: package:procps:1:3.2.8-11ubuntu6.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: procps Title: package procps 1:3.2.8-11ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-05-03 (530 days ago) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240203 Title: package procps 1:3.2.8-11ubuntu6.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/procps/+bug/1240203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973951] Re: package mysql-server-5.5 5.5.22-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
@smaudet: great analyse, To be sure, i verified first that mysqld_get_param is missing and after that commented out the lines from pre_start and mysql is operational again. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973951 Title: package mysql-server-5.5 5.5.22-0ubuntu1 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/mysql-5.5/+bug/973951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590686] Re: "Affect:" toolbar label should be renamed/removed
Sorry, not four years, only two. I read the date wrong. Who puts the year in front of the month and day?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/590686 Title: "Affect:" toolbar label should be renamed/removed To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/590686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590686] Re: "Affect:" toolbar label should be renamed/removed
It is now four years later. I recently discovered Inkscape, and have begun using it to edit SVG images. And this afternoon I was finally so annoyed by the "Affect" label that I reported it as a bug in need of fixing. I was soon notified that I was reporting a duplicate of this error, Bug #590686. And here I now am, reading over the text of the above messages. The messages suggest that the error has been fixed. Well, boys and girls, it is still here. Inkscape 0.48.4 r9939. I am using Windows 7 on a 64 bit system. I am a native English speaker. I am a grammar nazi. And I am incredulous that this problem is apparently still being reproduced. WTF??? Hey, though: it's not like Adobe Illustrator CS6 isn't replete with its own stockpile of linguistic mishaps. Looks to me like nobody thinks it's important to have their software vetted by someone with a degree in English anymore before distributing it to the public. Adobe has been around long enough to know better. Christ, how can programmers still be making these kinds of mistakes? Doesn't anyone check their work? Did they all get a C in English?? (Can you hear me laughing? I am laughing here... Sort of.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/590686 Title: "Affect:" toolbar label should be renamed/removed To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/590686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs