[Bug 2062655] [NEW] "Enable Animations" system a11y setting does not apply to CSS media query prefers-reduced-motion
Public bug reported: I am able to disable animations by switching off the system setting "Enable Animations" in the Accessibility pane. But it does not apply to the CSS media query prefers-reduced-motion. The MDN page documents this media query and can be used to test the feature. https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced- motion ** Affects: ubuntu-docs (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/2062655 Title: "Enable Animations" system a11y setting does not apply to CSS media query prefers-reduced-motion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/2062655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975866] Re: A continue or break from a subshell inside a loop no longer works.
Gunnar - thanks. I realized that I might have filed it in the wrong place - my apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975866 Title: A continue or break from a subshell inside a loop no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1975866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975866] [NEW] A continue or break from a subshell inside a loop no longer works.
Public bug reported: The following code works in bash on any number of Linux distros, including CentOS 6.10 - 7.8 and Ubuntu 14.04 - 18.04. #!/bin/bash # # Test for continue from subshell issue... # echo SHELL is $SHELL for i in $(seq 5) do ( echo loop $i if [[ $i == 2 ]] ; then echo i = $i - continue continue fi if [[ $i == 4 ]] ; then echo i = $i - exit exit 1 fi echo Loop $i subshell end ) rc=$? echo Loop $i rc $rc done -- The output on all of those machines is: SHELL is /bin/bash loop 1 Loop 1 subshell end Loop 1 rc 0 loop 2 i = 2 - continue Loop 2 rc 0 loop 3 Loop 3 subshell end Loop 3 rc 0 loop 4 i = 4 - exit Loop 4 rc 1 loop 5 Loop 5 subshell end Loop 5 rc 0 --- On a Ubuntu 20.04 machine: SHELL is /bin/bash loop 1 Loop 1 subshell end Loop 1 rc 0 loop 2 i = 2 - continue packages/tmp/looptest: line 14: continue: only meaningful in a `for', `while', or `until' loop Loop 2 subshell end Loop 2 rc 0 loop 3 Loop 3 subshell end Loop 3 rc 0 loop 4 i = 4 - exit Loop 4 rc 1 loop 5 Loop 5 subshell end Loop 5 rc 0 -- If I change the shebang to: #!/bin/sh the behavior is the same as the first example - except - on our machines, we specifically link /bin/sh to bash: $ ls -l /bin/sh lrwxrwxrwx 1 root root 9 May 12 22:04 /bin/sh -> /bin/bash Which seems just... weird. This behavior seems to have started after a recent update to Ubuntu 20.04. I realize that the argument can be made the new behavior is more technically correct, but using a subshell to isolate vars between loops can be very helpful and the fact that this has worked until now is concerning. ** Affects: ubuntu-docs (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/1975866 Title: A continue or break from a subshell inside a loop no longer works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1975866/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970588] Re: screen-shot-record.html doesn't reflect surprisingly swapped print screen key behaviour
Is it possible to view the updated page? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970588 Title: screen-shot-record.html doesn't reflect surprisingly swapped print screen key behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-docs/+bug/1970588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975512] Re: Incorrect instructions for "Screenshots and screencasts"
*** This bug is a duplicate of bug 1970588 *** https://bugs.launchpad.net/bugs/1970588 Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975512 Title: Incorrect instructions for "Screenshots and screencasts" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1975512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659824] Re: screen-shot-record.html is inaccurate
I initially thought my bug report (#1975512) was a duplicate of this one. But this help page now documents the new widget. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659824 Title: screen-shot-record.html is inaccurate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1659824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975512] Re: Incorrect instructions for "Screenshots and screencasts"
** This bug is no longer a duplicate of bug 1659824 screen-shot-record.html is inaccurate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975512 Title: Incorrect instructions for "Screenshots and screencasts" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1975512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975512] Re: Incorrect instructions for "Screenshots and screencasts"
*** This bug is a duplicate of bug 1659824 *** https://bugs.launchpad.net/bugs/1659824 ** This bug has been marked a duplicate of bug 1659824 screen-shot-record.html is inaccurate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975512 Title: Incorrect instructions for "Screenshots and screencasts" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1975512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975512] [NEW] Incorrect instructions for "Screenshots and screencasts"
*** This bug is a duplicate of bug 1659824 *** https://bugs.launchpad.net/bugs/1659824 Public bug reported: Release version: Ubuntu 22.04 LTS Package version: 22.04.5 The descriptions for the keyboard shortcuts seem to be wrong or inaccurate at best. This help page can be found at https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html Format description: First line: key shortcut (between angle brackets) Second line: official description Third line: actual behavior Take a screenshot of the desktop. Open widget in screenshot mode. Take a screenshot of a window. Take a screenshot of the currently focused window. Take a screenshot of an area you select. Take a screenshot of the full screen. Start/Stop recording what is on your screen. Open widget in screencast mode (second press does not stop recording). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-docs 22.04.5 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 18:12:41 2022 InstallationDate: Installed on 2022-05-21 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: Release version: Ubuntu 22.04 LTS Package version: 22.04.5 - The descriptions for the keyboard shortcuts seem to be wrong or - inaccurate at best. + The descriptions for the keyboard shortcuts seem to be wrong or inaccurate at best. + This help page can be found at https://help.ubuntu.com/stable/ubuntu-help/screen-shot-record.html Format description: - First line: key shortcut (between angle brackets) - Second line: official description - Third line: actual behavior + First line: key shortcut (between angle brackets) + Second line: official description + Third line: actual behavior Take a screenshot of the desktop. Open widget in screenshot mode. Take a screenshot of a window. Take a screenshot of the currently focused window. Take a screenshot of an area you select. Take a screenshot of the full screen. Start/Stop recording what is on your screen. Open widget in screencast mode (second press does not stop recording). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-docs 22.04.5 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 18:12:41 2022 InstallationDate: Installed on 2022-05-21 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-docs UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975512 Title: Incorrect instructions for "Screenshots and screencasts" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1975512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1454306] Re: apt-btrfs-snapshot supported reports "Sorry, your system lacks support for the snapshot feature" since update of btrfs-tools to 4.0-2 in debian/testing
I can confirm this still happens on Ubuntu/Xubuntu 20.04 with apt-btrfs- snapshot v353. Is there any intention to 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/1454306 Title: apt-btrfs-snapshot supported reports "Sorry, your system lacks support for the snapshot feature" since update of btrfs-tools to 4.0-2 in debian/testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1454306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634871] Re: apt-btrfs-snapshot reports "Sorry, your system lacks support for the snapshot feature" on btrfs with existing @apt-snapshot-release-upgrade snapshots
I can confirm this still happens on Ubuntu/Xubuntu 20.04 with apt-btrfs- snapshot v353. Is there any intention or when are they planning to 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/1634871 Title: apt-btrfs-snapshot reports "Sorry, your system lacks support for the snapshot feature" on btrfs with existing @apt-snapshot-release-upgrade snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1634871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Indeed, I'm running the daily build and toggling the percentage setting on and off has the expected result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249669] Re: ACE_Atomic_OP export issue
Fixed in ACE 6.4.3 ** Changed in: ace (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/1249669 Title: ACE_Atomic_OP export issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ace/+bug/1249669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249669] Re: ACE_Atomic_OP export issue
This has been fixed in ACE 6.4.3, see https://stackoverflow.com/questions/38953849/libace-and-clang-clang- undefined-reference-to-ace-atomic-opace-thread-mutex?noredirect=1&lq=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249669 Title: ACE_Atomic_OP export issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ace/+bug/1249669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
It happened to me as well on my lenovo ideapad laptop when I upgraded from Xubuntu 19.10 to 20.04, and my 1366x768 resolution ended all garbled. Then, after a while googling for solutions (which there wew so few!), I came up with a weird but functional workaround: I opened the display window, selected the 1366x768 resolution, rotation: inverted and reflection: horizontal and vertical, then applied. Worked! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876480] Re: Ubuntu MATE 20.04 Display issues with AMDGPU
*** This bug is a duplicate of bug 1873895 *** https://bugs.launchpad.net/bugs/1873895 It happened to me as well on my lenovo ideapad laptop when i upgraded from Xubuntu 19.10 to 20.04, and my 1366x768 resolution ended all garbled. Then, after a while googling for solutions (which there wew so few!), I came up with a weird but functional workaround: I opened the display window, selected the 1366x768 resolution, rotation: inverted and reflection: horizontal and vertical, then applied. Worked! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876480 Title: Ubuntu MATE 20.04 Display issues with AMDGPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1876480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
It happened to me as well on my lenovo ideapad laptop with Xubuntu 20.04, and I came with a weird but functional workaround: I opened the display window, selected the 1366x768 resolution, rotation: inverted and reflection: horizontal and vertical, then applied. Worked! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel]
Yesterday i updated my system, i noticed there was updates for plymouth and kernelupdate After that i am back to the beginning again. The workaroung Setting nospash in /etc/default/grub (GRUB_CMDLINE_LINUX_DEFAULT) does not work for me anymore. I now have to open the screen on the notebook to type in my password for LUKS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads [groovy] [focal with groovy hwe kernel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901215] Re: Cannot boot with thunderbolt dock connected before kernel loads
I got the same issue on Thinkpad X1 Carbon 6th & ThinkPad Thunderbolt 3 Dock Gen2 I have seen this issue on other distros like Fedora and Manjaro aswell when using luks and it looks very much that is has something to do with plymouth and kernel version 5.6 and up. I could replicate the issue on focal with kernel 5.8 and 5.9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901215 Title: Cannot boot with thunderbolt dock connected before kernel loads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891789] [NEW] package libpng12-0 (not installed) failed to install/upgrade: no se puede instalar una nueva versión de `/lib/x86_64-linux-gnu/libpng12.so.0': No existe el archivo o el directorio
Public bug reported: error installin ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpng12-0 (not installed) 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 AptOrdering: libpng12-0:amd64: Install libssl1.0.0:amd64: Install xfonts-75dpi:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 15 23:20:27 2020 DpkgTerminalLog: Preparando para desempaquetar .../libpng12-0_1.2.54-1ubuntu1_amd64.deb ... Desempaquetando libpng12-0:amd64 (1.2.54-1ubuntu1) ... dpkg: error al procesar el archivo /var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_amd64.deb (--unpack): no se puede instalar una nueva versión de `/lib/x86_64-linux-gnu/libpng12.so.0': No existe el archivo o el directorio ErrorMessage: no se puede instalar una nueva versión de `/lib/x86_64-linux-gnu/libpng12.so.0': No existe el archivo o el directorio InstallationDate: Installed on 2020-08-16 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libpng Title: package libpng12-0 (not installed) failed to install/upgrade: no se puede instalar una nueva versión de `/lib/x86_64-linux-gnu/libpng12.so.0': No existe el archivo o el directorio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libpng (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/1891789 Title: package libpng12-0 (not installed) failed to install/upgrade: no se puede instalar una nueva versión de `/lib/x86_64-linux- gnu/libpng12.so.0': No existe el archivo o el directorio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1891789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883778] [NEW] Broken pipe: qemu-system-common conflicts with qemu
Public bug reported: me@ubuntuionic:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic 0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded. me@ubuntuionic:~$ sudo apt-get install ipxe-qemu libvirt-daemon Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: ipxe-qemu-256k-compat-efi-roms libvirt-daemon-driver-storage-rbd qemu-block-extra qemu-kvm qemu-system-common qemu-system-x86 qemu-utils seabios Suggested packages: libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-sheepdog libvirt-daemon-driver-storage-zfs libvirt-daemon-system sgabios The following NEW packages will be installed: ipxe-qemu ipxe-qemu-256k-compat-efi-roms libvirt-daemon libvirt-daemon-driver-storage-rbd qemu-block-extra qemu-kvm qemu-system-common qemu-system-x86 qemu-utils seabios 0 upgraded, 10 newly installed, 0 to remove and 4 not upgraded. Need to get 1022 kB/11.1 MB of archives. After this operation, 48.1 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 ipxe-qemu-256k-compat-efi-roms all 1.0.0+git-20150424.a25a16d-0ubuntu2 [545 kB] Get:2 http://ppa.launchpad.net/jacob/virtualisation/ubuntu bionic/main amd64 qemu-block-extra amd64 1:2.12+dfsg-0~18.04~ppa0 [135 kB] Get:3 http://ppa.launchpad.net/jacob/virtualisation/ubuntu bionic/main amd64 libvirt-daemon-driver-storage-rbd amd64 4.7.0-0~18.04~ppa1 [134 kB] Get:4 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 seabios all 1.10.2-1ubuntu1 [128 kB] Get:5 http://ppa.launchpad.net/jacob/virtualisation/ubuntu bionic/main amd64 qemu-kvm amd64 1:2.12+dfsg-0~18.04~ppa0 [80.1 kB] Fetched 1022 kB in 4s (260 kB/s) Selecting previously unselected package qemu-block-extra:amd64. (Reading database ... 226228 files and directories currently installed.) Preparing to unpack .../0-qemu-block-extra_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb ... Unpacking qemu-block-extra:amd64 (1:2.12+dfsg-0~18.04~ppa0) ... Preparing to unpack .../1-qemu-system-common_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb ... Unpacking qemu-system-common (1:2.12+dfsg-0~18.04~ppa0) ... dpkg: error processing archive /tmp/apt-dpkg-install-2F9Ty9/1-qemu-system-common_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb (--unpack): trying to overwrite '/usr/bin/virtfs-proxy-helper', which is also in package qemu-4.2.0 4.2.0-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../2-ipxe-qemu_1.0.0+git-20180124.fbe8c52d-0ubuntu2.2_all.deb ... Unpacking ipxe-qemu (1.0.0+git-20180124.fbe8c52d-0ubuntu2.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-2F9Ty9/2-ipxe-qemu_1.0.0+git-20180124.fbe8c52d-0ubuntu2.2_all.deb (--unpack): trying to overwrite '/usr/share/qemu/pxe-e1000.rom', which is also in package qemu-4.2.0 4.2.0-1 Selecting previously unselected package ipxe-qemu-256k-compat-efi-roms. Preparing to unpack .../3-ipxe-qemu-256k-compat-efi-roms_1.0.0+git-20150424.a25a16d-0ubuntu2_all.deb ... Unpacking ipxe-qemu-256k-compat-efi-roms (1.0.0+git-20150424.a25a16d-0ubuntu2) ... Preparing to unpack .../4-libvirt-daemon_4.7.0-0~18.04~ppa1_amd64.deb ... Unpacking libvirt-daemon (4.7.0-0~18.04~ppa1) ... dpkg: error processing archive /tmp/apt-dpkg-install-2F9Ty9/4-libvirt-daemon_4.7.0-0~18.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/sbin/libvirtd', which is also in package libvirt-6.0.0 0-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package libvirt-daemon-driver-storage-rbd. Preparing to unpack .../5-libvirt-daemon-driver-storage-rbd_4.7.0-0~18.04~ppa1_amd64.deb ... Unpacking libvirt-daemon-driver-storage-rbd (4.7.0-0~18.04~ppa1) ... Selecting previously unselected package seabios. Preparing to unpack .../6-seabios_1.10.2-1ubuntu1_all.deb ... Unpacking seabios (1.10.2-1ubuntu1) ... Preparing to unpack .../7-qemu-system-x86_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb ... Unpacking qemu-system-x86 (1:2.12+dfsg-0~18.04~ppa0) ... dpkg: error processing archive /tmp/apt-dpkg-install-2F9Ty9/7-qemu-system-x86_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb (--unpack): trying to overwrite '/usr/bin/qemu-system-i386', which is also in package qemu-4.2.0 4.2.0-1 No apport report written because MaxReports is reached already dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package qemu-kvm. Preparing to unpack .../8-qemu-kvm_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb ... Unpacking qemu-kvm (1:2.12+dfsg-0~18.04~ppa0) ... Preparing to unpack .../9-qemu-utils_1%3a2.12+dfsg-0~18.04~ppa0_amd64.deb ... Unpacking qemu-utils (1:2.12+dfsg-0~18.04~ppa
[Bug 1882488] [NEW] Install of Ubuntu 20.04 LTS fails partway though
Public bug reported: There were other bugs on the list that were similar to mine, but they were all trying to install other OS versions. I'm trying to install Ubuntu 20.04 LTS on my machine from a USB, and I'm trying to dual boot it with Windows 10. I have already have Win 10 on the same hard drive that I'm trying to put Ubuntu on, it's on an NVME SSD (500 gig model). There are a few interesting things that happen during the installation process that likely help lead to the Ubuntu install crashing before completion. One of them is that when it gets to the install options, there is actually no listing for "Install Ubuntu Alongside Windows". The only options are for "Erase Disk and Install Ubuntu" and "Something Else". So, I click "Something Else". The other interesting thing I've noted is that there is no EFI file detected on my hard drive once you click "Something Else" to manually partition your drive, so I have to make one by selecting EFI partition and giving it 250MB or so. If you try to click the install before you do this, a warning message will pop up that you may ruin the installation, so I always obey the warning. I believe this is part of the problem because it doesn't show to create an EFI file in any of the Ubuntu install guides I've seen, so I strongly believe it leads to the crash. Once I finish manually partitioning, giving ~20gigs for the "/" directory and the rest of my 200GB partition to my "/home" directory, it goes through the install, and then it eventually crashes at the same part every time. "Executing 'grub-install/dev/nvme' failed. "This is a fatal error." The above is what the error message reads. I've even tried to install Ubuntu again, directly after it failed, with half the Ubuntu install still on the hard drive. Hilariously enough, there came an option for "Install Ubuntu 20.04 alongside Ubuntu 20.04" because it detected the other install. I selected that option, but it still failed at the exact same spot, with the exact same error. Once it fails, it will not boot to any Ubuntu partition. In fact, I have to go into "Disks" from my temporary Ubuntu USB, select the Windows 10 partition, and make it bootable in order for Windows 10 to boot. Hope this helps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/l/linux-restricted-modules/linux-modules-nvidia-440-5.4.0-26-generic_5.4.0-26.30+2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445 Date: Sun Jun 7 21:10:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu ** Description changed: There were other bugs on the list that were similar to mine, but they were all trying to install other OS versions. I'm trying to install - Ubuntu 20.04 LTS on my machine, and I'm trying to dual boot it with - Windows 10. I have already have Win 10 on the same hard drive that I'm - trying to put Ubuntu on, it's on an NVME SSD (500 gig model). There are - a few interesting things that happen during the installation process - that likely help lead to the Ubuntu install crashing before completion. - One of them is that when it gets to the install options, there is - actually no listing for "Install Ubuntu Alongside Windows". The only - options are for "Erase Disk and Install Ubuntu" and "Something Else". - So, I click "Something Else". The other interesting thing I've noted is - that there is no EFI file detected on my hard drive once you click - "Something Else" to manually partition your drive, so I have to make one - by selecting EFI partition and giving it 250MB or so. If you try to - click the install before you do this, a warning message will pop up that - you may ruin the installation, so I always obey the warning. I believe - this is part of the problem because it doesn't show to create an EFI - file in any of the Ubuntu install guides I've seen, so I strongly + Ubuntu 20.04 LTS on my machine from a USB, and I'm trying to dual boot + it with Windows 10. I have already have Win 10 on the same hard drive + that I'm trying to put Ubuntu on, it's on an NVME SSD (500 gig model). + There are a few interesting things that happen during the installation + process that likely help lead to the Ubuntu install crashing before + completion. One of them is that when it gets to the install options, + there is actually no listing for "Install Ubuntu Alongside Windows". + The only option
[Bug 1876806] [NEW] package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
Public bug reported: During update from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub-efi-amd64-signed 1.142+2.04-1ubuntu26 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 4 20:33:04 2020 ErrorMessage: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 InstallationDate: Installed on 2019-11-03 (183 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: grub2-signed Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32 UpgradeStatus: Upgraded to focal on 2020-05-04 (0 days ago) ** Affects: grub2-signed (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/1876806 Title: package grub-efi-amd64-signed 1.142+2.04-1ubuntu26 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1876806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
My only backup image was from 17.10, running kernel Kernel 4.13.0-46-generic. I stand corrected on the earbud model. It was an MPOW Flame that time, and not an MPOW T5/M5 model Nonetheless, even in the 17.10 backup image, bluetooth restarts. However, unlike in Disco, my earbuds actually manage to connect. The connection does drop after a couple of seconds, however. Also, I did find something that may be of relevance. I have an old USB Bluetooth dongle. And I plugged that in, and then used Blueman-manager to switch to that adapter and pair my earbuds -- and it works. Does this help further debugging? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Okay, will dig out my old backup images and see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Hi, the same problem occurs, even using a different MPOW model and an Anker brand. I've attached the syslog output in another file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
** Attachment added: "focal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+attachment/5325305/+files/focal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860935] Re: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5)
Additional. I got my hands on a different brand of headphones (Anker) to see if the manufacturer was the issue. I still have the same problem. TL;DR: Clean install of Eoan, bluetooth pairs then bluetooth restarts, over and over. Sometimes, I'm lucky and it will stay connected. Most of the time it restarts. Same machine and headphones work fine under Windows 8.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860935 Title: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860935] [NEW] Unable to pair to Bluetooth earbuds on Eoan (MPOW M5)
Public bug reported: This is a clean install of Eoan (although I have copied the home directory files from my previous installation, though I don't think that should affect this problem) A fresh pairing attempt gives this in the syslog: ``` Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:37 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:38 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:39 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:39 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy Jan 26 20:46:40 johnny-W35xSS-370SS bluetoothd[887]: connect error: Connection refused (111) Jan 26 20:46:40 johnny-W35xSS-370SS bluetoothd[887]: a2dp-source profile connect failed for 9A:25:5B:01:32:A8: Device or resource busy ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnny 1571 F pulseaudio /dev/snd/controlC1: johnny 1571 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jan 26 20:47:40 2020 InstallationDate: Installed on 2020-01-25 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860935 Title: Unable to pair to Bluetooth earbuds on Eoan (MPOW M5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314077/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314074/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314080/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314076/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314079/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
apport information ** Tags added: apport-collected ** Description changed: I am running ubuntu Disco, recently upgraded from Beaver. Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect, then Bluetooth on the machine will restart. This is visible by the Bluetooth applet showing Bluetooth being switched off then on again. This will happen a few times, then bluetooth will lock up, rendering it and the settings applet frozen. Requiring a restart to fix. It is like something in Bluetooth subsystem is crashing out when pairing with the T5 I used to use this MPOW T5 with ubuntu Beaver without issue and am tempted just to roll back to my image from then But here's hoping someone can help identify why this is happening. I am also using this on my Disco installation on my Pixelbook (which was a clean install, not an upgrade), so maybe that's something worth noting. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johnny 2201 F pulseaudio /dev/snd/controlC0: johnny 2201 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:34:49 2019 InstallationDate: Installed on 2018-12-31 (269 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: johnny 2878 F pulseaudio + /dev/snd/controlC0: johnny 2878 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2018-12-31 (352 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + MachineType: Notebook W35xSS_370SS + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-37.40-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-37-generic N/A + linux-backports-modules-5.0.0-37-generic N/A + linux-firmware1.178.6 + Tags: disco + Uname: Linux 5.0.0-37-generic x86_64 + UpgradeStatus: Upgraded to disco on 2019-09-21 (89 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/08/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4.6.5 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: W35xSS_370SS + dmi.board.vendor: Notebook + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 9 + dmi.chassis.vendor: Notebook + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: W35xSS_370SS + dmi.product.sku: Not Applicable + dmi.product.version: Not Applicable + dmi.sys.vendor: Notebook ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314067/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314071/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314078/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314081/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Marking as confirmed as instructed ** 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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
@seb128 re the bluetooth log, how do I obtain that? I've done the apport stuff, does that include the bluetooth log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314068/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314073/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314075/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314072/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314069/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1845689/+attachment/5314070/+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/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
More details that might help debugging. Found this in the syslog: Dec 18 18:58:21 johnny-W35xSS-370SS systemd[1]: systemd-rfkill.service: Succeeded. Dec 18 18:58:24 johnny-W35xSS-370SS kernel: [ 336.791201] input: 00:20:5B:12:1F:B6 as /devices/virtual/input/input34 Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) config/udev: Adding input device 00:20:5B:12:1F:B6 (/dev/input/event20) Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: Applying InputClass "libinput keyboard catchall" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) Using input driver 'libinput' for '00:20:5B:12:1F:B6' Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 70 paused 0 Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) 00:20:5B:12:1F:B6: always reports core events Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "Device" "/dev/input/event20" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "_source" "server/udev" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device removed Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "config_info" "udev:/sys/devices/virtual/input/input34/event20" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) XINPUT: Adding extended input device "00:20:5B:12:1F:B6" (type: KEYBOARD, id 18) Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_model" "pc105" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_layout" "gb" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (**) Option "xkb_variant" "extd" Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (WW) Option "xkb_options" requires a string value Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: is tagged by udev as: Keyboard Dec 18 18:58:24 johnny-W35xSS-370SS /usr/lib/gdm3/gdm-x-session[1858]: (II) event20 - 00:20:5B:12:1F:B6: device is a keyboard Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Dec 18 18:58:24 johnny-W35xSS-370SS org.gnome.Shell.desktop[2085]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Dec 18 18:58:29 johnny-W35xSS-370SS bluetoothd[1134]: /org/bluez/hci0/dev_00_20_5B_12_1F_B6/fd7: fd(37) ready Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 3 threads of 1 processes of 1 users. Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Successfully made thread 6460 of process 2154 owned by '1000' RT at priority 5. Dec 18 18:58:29 johnny-W35xSS-370SS rtkit-daemon[1517]: Supervising 4 threads of 1 processes of 1 users. -- At this point the headset is connected. After a few seconds, bluetooth then restarts: Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [ 353.504506] usb 3-7: Failed to suspend device, error -71 Dec 18 18:58:40 johnny-W35xSS-370SS kernel: [ 353.504570] usb 3-7: USB disconnect, device number 12 Dec 18 18:58:40 j
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
Oh, and it pairs okay under Windows on the same laptop (I dual boot Windows 8 and Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] Re: Bluetooth loops when pairing Connecting MPOW T5 headset
As an experiment took the 19.04 Ubuntu live disk, booted up from that and paired mt MPOW T5. Bluetooth crash looped as well. This eliminates anything I've installed as cause. I suspect something in the driver is not liking the bluetooth device on my machine, since it paired with 19.04 on my Pixelbook okay without crash looping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845689] [NEW] Bluetooth loops when pairing Connecting MPOW T5 headset
Public bug reported: I am running ubuntu Disco, recently upgraded from Beaver. Now when I pair my MPOW T5 bluetooth earbuds, they will pair, connect, then Bluetooth on the machine will restart. This is visible by the Bluetooth applet showing Bluetooth being switched off then on again. This will happen a few times, then bluetooth will lock up, rendering it and the settings applet frozen. Requiring a restart to fix. It is like something in Bluetooth subsystem is crashing out when pairing with the T5 I used to use this MPOW T5 with ubuntu Beaver without issue and am tempted just to roll back to my image from then But here's hoping someone can help identify why this is happening. I am also using this on my Disco installation on my Pixelbook (which was a clean install, not an upgrade), so maybe that's something worth noting. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: johnny 2201 F pulseaudio /dev/snd/controlC0: johnny 2201 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 27 17:34:49 2019 InstallationDate: Installed on 2018-12-31 (269 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to disco on 2019-09-21 (6 days ago) dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W35xSS_370SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/08/2014:svnNotebook:pnW35xSS_370SS:pvrNotApplicable:rvnNotebook:rnW35xSS_370SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W35xSS_370SS dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845689 Title: Bluetooth loops when pairing Connecting MPOW T5 headset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833229] Re: `--extra-index-url` not working for PIP
Can Confirm. Using a private PyPI repo in my company. pip install --extra-index-url=https://pypi.pipelineservices.alertlogic.com alps Collecting alps Exception: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 215, in main status = self.run(options, args) File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 353, in run wb.build(autobuilding=True) File "/usr/lib/python2.7/dist-packages/pip/wheel.py", line 749, in build self.requirement_set.prepare_files(self.finder) File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 380, in prepare_files ignore_dependencies=self.ignore_dependencies)) File "/usr/lib/python2.7/dist-packages/pip/req/req_set.py", line 554, in _prepare_file require_hashes File "/usr/lib/python2.7/dist-packages/pip/req/req_install.py", line 278, in populate_link self.link = finder.find_requirement(self, upgrade) File "/usr/lib/python2.7/dist-packages/pip/index.py", line 465, in find_requirement all_candidates = self.find_all_candidates(req.name) File "/usr/lib/python2.7/dist-packages/pip/index.py", line 423, in find_all_candidates for page in self._get_pages(url_locations, project_name): File "/usr/lib/python2.7/dist-packages/pip/index.py", line 568, in _get_pages page = self._get_page(location) File "/usr/lib/python2.7/dist-packages/pip/index.py", line 683, in _get_page return HTMLPage.get_page(link, session=self.session) File "/usr/lib/python2.7/dist-packages/pip/index.py", line 795, in get_page resp.raise_for_status() File "/usr/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/models.py", line 935, in raise_for_status raise HTTPError(http_error_msg, response=self) HTTPError: 404 Client Error: Not Found for url: https://pypi.org/simple/alps/ File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 554, in _prepare_file require_hashes File "/usr/lib/python3/dist-packages/pip/req/req_install.py", line 278, in populate_link self.link = finder.find_requirement(self, upgrade) File "/usr/lib/python3/dist-packages/pip/index.py", line 465, in find_requirement all_candidates = self.find_all_candidates(req.name) File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates for page in self._get_pages(url_locations, project_name): File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages page = self._get_page(location) File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page return HTMLPage.get_page(link, session=self.session) File "/usr/lib/python3/dist-packages/pip/index.py", line 795, in get_page resp.raise_for_status() File "/usr/share/python-wheels/requests-2.18.4-py2.py3-none-any.whl/requests/models.py", line 935, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://pypi.org/simple/alps/ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 Using WLS form Windows 10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833229 Title: `--extra-index-url` not working for PIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1833229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] Re: Audio stutter after update
Hm, that was a bit early. Now it has "happened" ONCE with the 5.1.0-050100rc2-generic kernel. I think the battery of the laptop was pretty low at the time. Youtube audio went totally out of sync with video. Restarted to 4.15.0-43 to see what that does with youtube. It had pauses in getting the video (the circle going round) but when picture came back it was still in sync with audio. Restarted back to 5.1.0-050100rc2-generic again. Now everything was ok there. Also computer shows i have powersave governor on. Another notebook with (Celeron N3350 and) powersave has no problems at all though. I should probably also try a clean install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] Re: Audio stutter after update
5.1.0-050100rc2-generic, works great, does not have that issue. Thanks, i'm keeping it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] Re: Audio stutter after update
I would'nt say it happens, i'd say its always there constantly. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+attachment/5248540/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] Re: Audio stutter after update
Yes, tried a few back now. 4.15.0-43-generic is the last good one. -44 has the weird things, Youtube video goes slower (or stops for while) and then speeds too much and audio gets out of sync with that. In VLC audio stutter starts at about after first 10 to 12 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] Re: Audio stutter after update
I mean the audio part of the video stutters in VLC. (It's made with android phone and downloaded back from youtube. Codec: H264 - MPEG-4 AVC (part 10) (avc1)) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820409] [NEW] Audio stutter after update
Public bug reported: After some update: Audio stutters in VLC Video and audio stutters in Youtube I think cpu usage might be bigger in VLC too, over 20% vs. below 20% earlier (one thread gets full 100%?) Stuttering kernel at the moment is 4.15.0-46-generic. Kernel version 4.15.0-43-generic definitely worked good. Cant remember if i could get slight stutter from previous version version -45. Tried also lowlatency and 4.18 kernel, bad stuttering in those. (Distro is Lubuntu) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-46-generic. ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meie855 F pulseaudio /dev/snd/controlC1: meie855 F pulseaudio Card0.Amixer.info: Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50' Mixer name : 'Intel Broadwell HDMI' Components : 'HDA:80862808,80860101,0010' Controls : 35 Simple ctrls : 5 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47' Mixer name : 'Conexant CX20751/2' Components : 'HDA:14f1510f,1043181d,00100100' Controls : 20 Simple ctrls : 9 CurrentDesktop: LXDE Date: Sat Mar 16 18:02:18 2019 InstallationDate: Installed on 2018-07-04 (255 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820409 Title: Audio stutter after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818634] [NEW] resolvconf does not work well if using networkd but not resolved
Public bug reported: I'm running Ubuntu Server 18.04, which uses systemd-networkd. If I install resolvconf and disable systemd-resolved, resolvonf keeps putting "nameserver 127.0.0.53" in /etc/resolv.conf. To get rid of that behavior, I disabled resolvconf-pull-resolved.path. Now resolvconf doesn't put any nameservers in /etc/resolv.conf, even though networkd's DHCP client has correctly stored the DNS server in /run/systemd/* and it's also available via "networkctl status". In short, resolvconf has support for dhclient and systemd-resolved, but no support for systemd-networkd without systemd-resolved. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Mar 5 03:15:02 2019 InstallationDate: Installed on 2019-03-04 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: [modified] mtime.conffile..etc.dhcp.dhclient-enter-hooks.d.resolvconf: 2019-03-05T03:09:13.709323 ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818634 Title: resolvconf does not work well if using networkd but not resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1818634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767992] Re: Linux md raid-10 freezes during resync
We had the same issue after updating from Ubuntu 14.04 to 16.04 and then 18.04 (the two consecutive updates were applied on the same day). The filesystem is also XFS. and the setup is with raid10. The bug does not completely froze the system. Many process still run and were able to write to disk. But new processes seems to have trouble with that. Also, some processes that did not write to disk also halted. Example: htop and ps aux Interesting thing is that "ps aux" actually started printing the output and around the middle of the execution, it halted, and Ctrl+C was unable to exit the program. htop, which hangs a few seconds after its execution, showed that the frozen processed were in D (uninterruptible sleep) state. The fix was to downgrade from kernel 4.15.0-34-generic to 4.2.0-34-generic. Although the fix was not perfect, since that fix it happened again once. (but once in 130 days is not as bad) Attached logs: kernel.log with some stracktrace, but they are more or less the same as previously posted.. (the logs were OCR'ed from some screenshots. so beware of some characters. like the 0 which sometimes turns into a 6) ** Attachment added: "kernel errors" https://bugs.launchpad.net/ubuntu/+bug/1767992/+attachment/5237094/+files/errors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1767992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767361] Re: 4.6.6deb5 not working on Bionic as PHP 7.2 is default
FWIW, I patch phpMyAdmin using these two lines after installation: perl -p -i -e "s/\[\'select_expr\'\] == 1\)/\[\'select_expr\'\]\) == 1/g" /usr/share/phpmyadmin/libraries/sql.lib.php perl -p -i -e "s/ count\(/ count\(\(array\)/g" /usr/share/phpmyadmin/libraries/plugin_interface.lib.php I've not seen any negative side effects, but I am not an heavy user either so YMMV -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767361 Title: 4.6.6deb5 not working on Bionic as PHP 7.2 is default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1767361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1799225] Re: ff extracting tar.gz error and stops.
You are correct. I downloaded via dialog box and used Archive Manager. No error message, just stopped. /*If that is the case why are you not using the version provided by Ubuntu in the official repositories which is regularly updated and includes any patches that the Ubuntu developers wish to include to make Firefox work with Ubuntu better? */*I did not know any better. Did a Google search and used the terminal to upgrade FF. I now have FF 63. In addition I have installed Ubuntu 14.14 which cures the suspend problem. Thank you for your reply Paul.*/**/ /**/ On 11/10/18 4:39 AM, Paul White wrote: > Johnny, > > What is asking you to upgrade? What did the error message say? > > >From what you report it sounds like you have downloaded Firefox from the > Mozilla site after being prompted to upgrade by a dialog box. If that is > the case why are you not using the version provided by Ubuntu in the > official repositories which is regularly updated and includes any > patches that the Ubuntu developers wish to include to make Firefox work > with Ubuntu better? > > Please clarify from which source you are obtaining Firefox and its > updates. > > > ** Changed in: firefox (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799225 Title: ff extracting tar.gz error and stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1799225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799225] [NEW] ff extracting tar.gz error and stops.
Public bug reported: I have FF 57 and am asked to upgrade. downloaded tar.gz and archive manager reads the files and begins to extract. then it stops with an error message. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.9 ProcVersionSignature: Ubuntu 3.13.0-137.186-generic 3.13.11-ckt39 Uname: Linux 3.13.0-137-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Oct 22 08:45:33 2018 InstallationDate: Installed on 2017-05-21 (518 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799225 Title: ff extracting tar.gz error and stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796356] Re: armhf chromedriver version doesn't match browser
Below is a python snippet, which should attempt to initialize a webdriver instance. from selenium import webdriver browser = webdriver.Chrome("/usr/lib/chromium-browser/chromedriver") print("chrome driver init done") browser.close() And there's an error: Traceback (most recent call last): File "selenium_t1.py", line 2, in browser = webdriver.Chrome("/usr/lib/chromium-browser/chromedriver") File "/usr/local/lib/python3.5/dist-packages/selenium/webdriver/chrome/webdriver.py", line 67, in __init__ desired_capabilities=desired_capabilities) File "/usr/local/lib/python3.5/dist-packages/selenium/webdriver/remote/webdriver.py", line 90, in __init__ self.start_session(desired_capabilities, browser_profile) File "/usr/local/lib/python3.5/dist-packages/selenium/webdriver/remote/webdriver.py", line 177, in start_session response = self.execute(Command.NEW_SESSION, capabilities) File "/usr/local/lib/python3.5/dist-packages/selenium/webdriver/remote/webdriver.py", line 236, in execute self.error_handler.check_response(response) File "/usr/local/lib/python3.5/dist-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response raise exception_class(message, screen, stacktrace) selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /usr/lib/chromium-browser/chromium-browser is no longer running, so ChromeDriver is assuming that Chrome has crashed.) (Driver info: chromedriver=2.40,platform=Linux 3.4.113-sun8i armv7l) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796356 Title: armhf chromedriver version doesn't match browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1796356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796356] [NEW] armhf chromedriver version doesn't match browser
Public bug reported: Hi, I installed chromium-browser and chromium-driver using apt-get I ran two commands: sudo apt-get install chromium-browser && sudo apt-get install chromium--chromedriver But the versions doesn't seem to match each other. I could not instantiate a simple browser using both Chromium-browser/chromedriver installed by the above command. Tried with selenium module using python and it would just crash. According to this link: https://sites.google.com/a/chromium.org/chromedriver/downloads ChromeDriver must be higher or equal to 2.41 for it to work with Chromium 69. So, I ran the following commands, only to find out that the versions for these packages are not compatible with each other. /usr/lib/chromium-browser/chromedriver --version ChromeDriver 2.40 chromium-browser --version Chromium 69.0.3497.81 Built on Ubuntu , running on Ubuntu 16.04 I would think this is a bug, since the versions are not compatible with each other would render the chromedriver useless but they should be compatible and cooperating just fine. My previous question/discussion submitted in regards to this bug: https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/674688 Additional info that might be helpful: $ uname -a Linux orangepizero 3.4.113-sun8i #4 SMP PREEMPT Wed Nov 22 13:45:28 CET 2017 armv7l armv7l armv7l GNU/Linux $ lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial $ dpkg -l | grep chromium ii chromium-browser 69.0.3497.81-0ubuntu0.16.04.1 armhf Chromium web browser, open-source version of Chrome ii chromium-chromedriver 69.0.3497.81-0ubuntu0.16.04.1 armhf WebDriver driver for the Chromium Browser ii chromium-codecs-ffmpeg-extra 69.0.3497.81-0ubuntu0.16.04.1 armhf Extra ffmpeg codecs for the Chromium Browser $ apt-cache policy chromium-browser chromium-chromedriver chromium-browser: Installed: 69.0.3497.81-0ubuntu0.16.04.1 Candidate: 69.0.3497.81-0ubuntu0.16.04.1 Version table: *** 69.0.3497.81-0ubuntu0.16.04.1 500 500 http://ports.ubuntu.com xenial-security/universe armhf Packages 500 http://ports.ubuntu.com xenial-updates/universe armhf Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://ports.ubuntu.com xenial/universe armhf Packages chromium-chromedriver: Installed: 69.0.3497.81-0ubuntu0.16.04.1 Candidate: 69.0.3497.81-0ubuntu0.16.04.1 Version table: *** 69.0.3497.81-0ubuntu0.16.04.1 500 500 http://ports.ubuntu.com xenial-security/universe armhf Packages 500 http://ports.ubuntu.com xenial-updates/universe armhf Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://ports.ubuntu.com xenial/universe armhf Packages ** Affects: chromium-browser (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/1796356 Title: armhf chromedriver version doesn't match browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1796356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196007] Re: udisksd[2225]: Error performing housekeeping for drive (WD USB 2.0 HDD)
*** This bug is a duplicate of bug 1143495 *** https://bugs.launchpad.net/bugs/1143495 ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196007 Title: udisksd[2225]: Error performing housekeeping for drive (WD USB 2.0 HDD) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/1196007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768017] Re: grub-install crashes when installing ubuntu on btrfs
Ubiquity crashed trying to install grub, the popup appeared asking me to choose a different destination or continue installing without a bootloader, unfortunately the computer was not responsive anymore -> I had to hard-reset the device and install manually. Afterwards the system worked - kind of. Whatever ubiquity does after installing grub (clean up??) was never performed, I had a couple of issues mainly with python related packages, most of them could be fixed by reinstalling them with apt. At some point however I got fed up (I tried installing at least 2 times) and installed Fedora instead... I'm sorry I can't provide more information but I was pretty pissed at that time... cheers 2018-06-06 19:53 GMT+02:00 Phillip Susi : > According to your syslog your computer was rebooted before trying to > install grub. Can you try again? > > > ** Changed in: ubiquity (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768017 > > Title: > grub-install crashes when installing ubuntu on btrfs > > Status in ubiquity package in Ubuntu: > Incomplete > > Bug description: > When installing on btrfs ubuntu automatically creates subvolumes @ and > @home. > When ubiquity comes to installing grub, it failes "failed to install on > /dev/sda". > The pop-up query to choose another drive to install, or continue without > installing a bootloader, doesn't respond. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.14 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Apr 30 14:33:16 2018 > InstallCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic > root=UUID=b2a9bec2-e290-4313-9a30-c5c2f51f95ce ro rootflags=subvol=@ > quiet splash vt.handoff=1 > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/ > 1768017/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768017 Title: grub-install crashes when installing ubuntu on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769829] Re: package cups-browsed 1.8.3-2ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
i have linux mint im new to linux and i have this pop up when im trying to update any help would be appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769829 Title: package cups-browsed 1.8.3-2ubuntu3.4 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/cups-filters/+bug/1769829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768212] [NEW] Package docker.io cannot be purged
Public bug reported: After installing docker.io in Artful, then attempting to purge it, it asks for confirmation, then complains it cannot nuke /var/lib/docker. An almost identical error to this Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856149 /var/lib/docker/nuke-graph-directory.sh: 64: /var/lib/docker/nuke-graph- directory.sh: shopt: not found Running rm -rf /var/lib/docker then trying to purge docker.io again worked and then gave me a warning about /etc/docker not being empty. So rm -rf /etc/docker and purge again then worked. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: docker.io (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 1 10:16:19 2018 InstallationDate: Installed on 2018-04-15 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: docker.io UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768212 Title: Package docker.io cannot be purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1768212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768017] [NEW] grub-install crashes when installing ubuntu on btrfs
Public bug reported: When installing on btrfs ubuntu automatically creates subvolumes @ and @home. When ubiquity comes to installing grub, it failes "failed to install on /dev/sda". The pop-up query to choose another drive to install, or continue without installing a bootloader, doesn't respond. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:33:16 2018 InstallCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-20-generic root=UUID=b2a9bec2-e290-4313-9a30-c5c2f51f95ce ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768017 Title: grub-install crashes when installing ubuntu on btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760915] [NEW] Unable to preseed keyboard selection and skip user creation
Public bug reported: I tried to use my preseed and kickstart configuration files used with 16.04 on the daily 18.04 ubuntu desktop build. Everything is automatic except these three: 1. Prompted for keyboard layout The correct layout is automatically chosen (Norwegian in this case), but I still need to click Continue. This is from my preseed file: d-i console-setup/ask_detect boolean false d-i keyboard-configuration/xkb-keymap select no 2. Prompted for user Should not be prompted for user creation, since this is in my preseed file: user --disabled and this in my kickstart file: user --disabled 3. %pre section of kickstart file is apparently not run The %pre section is set up to change terminal, ask some questions, then change back to the original terminal and continue. This is the main part of it: %pre exec < /dev/tty6 > /dev/tty6 2> /dev/tty6 chvt 6 # Ask questions chvt 1 exec < /dev/tty1 > /dev/tty1 2> /dev/tty1 The boot options used: append file=/cdrom/preseed/tornado.seed ks=cdrom:/isolinux/ks.cfg boot=casper automatic-ubiquity initrd=/casper/initrd.lz quiet splash --- ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "preseed file used" https://bugs.launchpad.net/bugs/1760915/+attachment/5100057/+files/tornado.seed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760915 Title: Unable to preseed keyboard selection and skip user creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1760915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1758796] Re: Kernel Crash
Thanks for getting back to me. I've been running the system as a web server for 8 years round the clock and this is the first and only time I had an unexplained kernel crash. I sent the bug in because I was unable to interpret the dump and I was actually worried someone had hacked my system causing the failure. I'm willing to check the upstream kernel but I've been running on the rebooted system since and have not seen the problem again so I'm not sure how long I'd have to run to verify the new kernel made any difference. If you can tell me either that this was a straight failure and not a hack or tell me how I could break down the dump and understand where and how it failed I'd be ok with closing this out. I just wanted to be sure it wasn't caused by malicious outside activity. The only thing different I noticed from my last automatic server upgrade is that I'm getting periodic java exceptions seemingly trace to gnome when I'm on the system. Which way should I go? Thanks again for getting back to me, John > On Mar 27, 2018, at 5:54 PM, Joseph Salisbury > wrote: > > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.16 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc7 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => High > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > > ** Tags added: kernel-da-key > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1758796 > > Title: > Kernel Crash > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Have the logs around this. Failed while running unattended. > > ProblemType: KernelCrash > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.4.0-117-generic 4.4.0-117.141 > ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 > Uname: Linux 4.4.0-117-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC0: johnny 8301 F pulseaudio > Date: Sun Mar 25 06:09:20 2018 > HibernationDevice: RESUME=UUID=5ed7ec2d-76de-4b8d-b427-f94d429221a5 > InstallationDate: Installed on 2011-12-21 (2285 days ago) > InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) > IwConfig: > lono wireless extensions. > > eth0 no wireless extensions. > MachineType: MSI MS-7680 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic > root=UUID=430a9050-fa68-406c-812c-8a6384c75d43 ro quiet splash > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M > crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: > linux-restricted-modules-4.4.0-117-generic N/A > linux-backports-modules-4.4.0-117-generic N/A > linux-firmware 1.157.17 > RfKill: > > SourcePackage: linux > UpgradeStatus: Upgraded to xenial on 2016-08-18 (583 days ago) > dmi.bios.date: 04/11/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: V17.1 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: H61M-P21 (MS-7680) > dmi.board.vendor: MSI > dmi.board.version: 3.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: MSI > dmi.
[Bug 1758796] [NEW] Kernel Crash
Public bug reported: Have the logs around this. Failed while running unattended. ProblemType: KernelCrash DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-117-generic 4.4.0-117.141 ProcVersionSignature: Ubuntu 4.4.0-117.141-generic 4.4.114 Uname: Linux 4.4.0-117-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: johnny 8301 F pulseaudio Date: Sun Mar 25 06:09:20 2018 HibernationDevice: RESUME=UUID=5ed7ec2d-76de-4b8d-b427-f94d429221a5 InstallationDate: Installed on 2011-12-21 (2285 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MSI MS-7680 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-117-generic root=UUID=430a9050-fa68-406c-812c-8a6384c75d43 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-117-generic N/A linux-backports-modules-4.4.0-117-generic N/A linux-firmware 1.157.17 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-18 (583 days ago) dmi.bios.date: 04/11/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V17.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P21 (MS-7680) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV17.1:bd04/11/2011:svnMSI:pnMS-7680:pvr3.0:rvnMSI:rnH61M-P21(MS-7680):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7680 dmi.product.version: 3.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kernelcrash package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758796 Title: Kernel Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1758796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
It seems that the Thunderbolt 3 to 2 adapter is not supported: https://bugzilla.kernel.org/show_bug.cgi?id=189731 ** Bug watch added: Linux Kernel Bug Tracker #189731 https://bugzilla.kernel.org/show_bug.cgi?id=189731 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1726299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
$ sudo modprobe firewire_ohci $ lsmod | grep firewire firewire_ohci 40960 0 firewire_core 65536 1 firewire_ohci crc_itu_t 16384 1 firewire_core There is no output for 'lspci | grep -i FireWire' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726299 Title: Apple Thunderbolt 2 to FireWire adapter not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1726299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726299] [NEW] Apple Thunderbolt 2 to FireWire adapter not working
Public bug reported: The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt 2 adapter. Ubuntu seems not to recognize the Firewire adapter. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty uname -r 4.10.0-19-generic sudo lshw -short H/W-Pfad Gerät Klasse Beschreibung === system Z170N-Gaming 5 (Default string) /0 busZ170N-Gaming 5 /0/0memory 64KiB BIOS /0/3d memory 16GiB Systemspeicher /0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns) /0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME POT-Creatio /0/43 memory 128KiB L1 Cache /0/44 memory 512KiB L2 Cache /0/45 memory 3MiB L3 Cache /0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz /0/100 bridge Skylake Host Bridge/DRAM Registers /0/100/1bridge Skylake PCIe Controller (x16) /0/100/1/0 displayOland GL [FirePro W2100] /0/100/1/0.1multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series] /0/100/14 busSunrise Point-H USB 3.0 xHCI Controller /0/100/14/0 usb1 busxHCI Host Controller /0/100/14/0/6 input USB Gaming Keyboard /0/100/14/0/d communication Bluetooth-Schnittstelle /0/100/14/1 usb2 busxHCI Host Controller /0/100/14/1/5scsi6 storageStorage Media /0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media /0/100/14/1/5/0.0.0/0/dev/sdb disk 15GB /0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk /0/100/16 communication Sunrise Point-H CSME HECI #1 /0/100/17 storageSunrise Point-H SATA controller [AHCI mode] /0/100/1b bridge Sunrise Point-H PCI Root Port #17 /0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19 /0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20 /0/100/1c bridge Sunrise Point-H PCI Express Root Port #1 /0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c/0/2/0 busDSL6540 USB 3.1 Controller [Alpine Ridge] /0/100/1c/0/2/0/0usb3 busxHCI Host Controller /0/100/1c/0/2/0/0/1 genericThunderbolt 3 (USB-C) to Thunderbolt 2 Adapter /0/100/1c/0/2/0/0/2 input USB Optical Mouse /0/100/1c/0/2/0/1usb4 busxHCI Host Controller /0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015] /0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3 /0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4 /0/100/1c.4 bridge Sunrise Point-H PCI Express Root Port #5 /0/100/1c.4/0enp13s0networkKiller E2400 Gigabit Ethernet Controller /0/100/1c.5 bridge Sunrise Point-H PCI Express Root Port #6 /0/100/1c.5/0wlp14s0networkWireless 8260 /0/100/1c.6 bridge Sunrise Point-H PCI Express Root Port #7 /0/100/1c.7 bridge Sunrise Point-H PCI Express Root Port #8 /0/100/1d bridge Sunrise Point-H PCI Express Root Port #9 /0/100/1f bridge Sunrise Point-H LPC Controller /0/100/1f.2 memory Memory controller /0/100/1f.3 multimedia Sunrise Point-H HD Audio /0/100/1f.4
[Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch
It doesn't matter witch session I use. This bug concerns UBUNTU DEFAULT SESSION. I dont know, why you cannot understand this. I even provide info about patch, which should be disabled to fix this. Once again: 1. Start ubuntu. 2. Install gnome-tweak-tool. 3. Disable "Application Menu" in "Top Bar". 4. NOTICE, THAT IS STILL UBUNTU DEFAULT SESSION 5. Start Rhythmbox. See the menubar. See the settings gear icon. All menubar options accessible through gear icon. Menubar should go away. One thing I'm not sure about - if ubuntu comes with enabled alternative- toolbar plugin by default (if it is - its a mistake, because position slider buggy in this plugin) - you should disable it. If you still has problems with understanding this bug, pleas, contact Daniel van Vugt (vanvugt), he understood whats wrong in similar bug (https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch
Yes, it is (displayed). Screenshot taken on GNOME (not ubuntu session - vanilla gnome wayland session, but i dont think it matters). Since you cant see it, make sure you disabled top bar application menu (Go to Gnome Tweaks -> Top menu section -> "Application Menu" switcher). If you still cant see it, make sure that "alternative toolbar" plugin disabled in rhythmbox. Now you should see the same rhythmbox as on the attached screenshot. You should disable "restore-traditional-menubar.patch" (or fix is somehow, if you want save this menubar for unity session). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720651] Re: Scrollbar drawing broken on wayland sesssion
** Tags added: ui ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720651 Title: Scrollbar drawing broken on wayland sesssion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720654] Re: Totem menu is totally broken
** Tags added: ui ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720654 Title: Totem menu is totally broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch
** Tags added: ui ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch
** Description changed: Standard gnome behavior doesn't allow to draw rhythmbox menubar, because all the controls are available through the "settings (gear) button". Ubuntu 17.10 draws menu, because of unity-compatible patch, you should remove it, to provide true gnome expirience. Menubar is bloatware. Problem occurs if you disable top bar application menu in Gnome Tweaks, and start Rhythmbox after that. See attached screenshot. Please, remove menubar patch. + Ubuntu 17.10, rhythmbox-3.4.1-2ubuntu5. + You should also check other Gnome apps!!! AFAIK, Totem, default video player also has some patch like this, and you even cant hide menubar in fullscreen mode (!). I'm using mpv, so i dont care. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720651] Re: Scrollbar drawing broken on wayland sesssion
** Description changed: Scrollbar drawing broken, with light theme variant on wayland session. See attached screenshot (white line right of scrollbar). To fix this you should remove some unity-compatible patch. + + Ubuntu 17.10, gnome-terminal-3.24.2-0ubuntu4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720651 Title: Scrollbar drawing broken on wayland sesssion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720654] Re: Totem menu is totally broken
** Description changed: Open Totem with disabled "top bar application menu" option in Gnome Tweaks. See this (screenshot). Menu is coming from unity-compatible patch, original gnome behavior - menu should go to button with totem icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN - IN FULLSCREEN MODE WITH MOVIE PLAYING!!! + IN FULLSCREEN MODE WITH MOVIE PLAYING!!! (Ubuntu 17.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720654 Title: Totem menu is totally broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720649] Re: broken gnome expirience caused by unity-compatible patch
Actuall, i also checked and reported totem bug https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654 , but please, consider to check all of gtk3-applications which were patched for unity de. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720654] Re: Totem menu is totally broken
Found correct menu look, flat button in top left corner: https://doc.opensuse.org/documentation/leap/gnomeuser/html/book.gnomeuser/images/totem_a.png ** Description changed: Open Totem with disabled "top bar application menu" option in Gnome Tweaks. See this (screenshot). Menu is coming from unity-compatible patch, original gnome behavior - menu should go to button with totem - icon right of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN + icon left of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720654 Title: Totem menu is totally broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720654] [NEW] Totem menu is totally broken
Public bug reported: Open Totem with disabled "top bar application menu" option in Gnome Tweaks. See this (screenshot). Menu is coming from unity-compatible patch, original gnome behavior - menu should go to button with totem icon right of the "+" button. Worst thing - MENU IS ALWAYS VISIBLE, EVEN IN FULLSCREEN MODE WITH MOVIE PLAYING!!! ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1720654/+attachment/4959888/+files/bugrep-totem.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720654 Title: Totem menu is totally broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1720654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720651] [NEW] Scrollbar drawing broken on wayland sesssion
Public bug reported: Scrollbar drawing broken, with light theme variant on wayland session. See attached screenshot (white line right of scrollbar). To fix this you should remove some unity-compatible patch. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1720651/+attachment/4959869/+files/bugrep-terminal.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720651 Title: Scrollbar drawing broken on wayland sesssion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720649] [NEW] broken gnome expirience caused by unity-compatible patch
Public bug reported: Standard gnome behavior doesn't allow to draw rhythmbox menubar, because all the controls are available through the "settings (gear) button". Ubuntu 17.10 draws menu, because of unity-compatible patch, you should remove it, to provide true gnome expirience. Menubar is bloatware. Problem occurs if you disable top bar application menu in Gnome Tweaks, and start Rhythmbox after that. See attached screenshot. Please, remove menubar patch. You should also check other Gnome apps!!! AFAIK, Totem, default video player also has some patch like this, and you even cant hide menubar in fullscreen mode (!). I'm using mpv, so i dont care. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1720649/+attachment/4959868/+files/bugrep-rh.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720649 Title: broken gnome expirience caused by unity-compatible patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1720649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719211] [NEW] Bad interface name
Public bug reported: Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks ** Affects: ufw (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/1719211 Title: Bad interface name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699920] [NEW] package locales 2.23-0ubuntu9 failed to install/upgrade: package locales is already installed and configured
Public bug reported: The "OS Updates" stops halfway when updating and sends me a notification and option to report failure. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: locales 2.23-0ubuntu9 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Thu Jun 22 20:13:40 2017 DuplicateSignature: package:locales:2.23-0ubuntu9 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package locales (--configure): package locales is already installed and configured ErrorMessage: package locales is already installed and configured InstallationDate: Installed on 2017-05-22 (31 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: dpkg Title: package locales 2.23-0ubuntu9 failed to install/upgrade: package locales is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699920 Title: package locales 2.23-0ubuntu9 failed to install/upgrade: package locales is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1699920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575182] Re: sysinfo crashes on ubuntu 16.04 (since upgrade)
>"Launchpad Janitor (janitor) wrote 5 hours ago: > >This bug was fixed in the package sysinfo - 0.7-10ubuntu1" No, sir, it wasn't. sysinfo ver 0.7.10 is still crashing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575182 Title: sysinfo crashes on ubuntu 16.04 (since upgrade) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysinfo/+bug/1575182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1692100] [NEW] Xorg crash
Public bug reported: every time i login, cpu runs at 100% because of many apport-gtk processes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.6.4-040604-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 19 15:00:39 2017 InstallationDate: Installed on 2015-03-01 (810 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-07-22 (301 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1692100 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614459] Re: daily upgrade on 16.04 hangs
*** This bug is a duplicate of bug 1579135 *** https://bugs.launchpad.net/bugs/1579135 sudo dpkg --configure -a Setting up apparmor (2.10.95-0ubuntu2.6) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults any fixes for this bug yet? i cant update and its screwing up one of my customers sites ** Changed in: apparmor (Ubuntu) Status: Confirmed => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/apparmor/+question/605429 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614459 Title: daily upgrade on 16.04 hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1614459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463243] Re: 20KB write to ~/.config/dconf/user on caps lock or num lock
This bug still continues/exists on xubuntu 16.04 with dconf-service. It happens on my machine when I open more than one instance of mousepad, the I/O disk write increments and the HDD led doesn't stop blinking, until I close one of the instances of mousepad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1463243 Title: 20KB write to ~/.config/dconf/user on caps lock or num lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1463243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group
I've been seeing the same problem - numerous services being shutdown, including cron, ssh and even a script I have running on the console to recover. The syslog shows that various systemd "targets" being shutdown, including: Default, Basic System, Timers, Paths, Sockets... This has correlated to running a script on our system (that has been running for many years on many systems) that finds and sends a kill signal to a ser2net connection before opening a remote console. This has been a nightmare on our Ubuntu 16 systems since upgrading from 14, and nearly a daily occurrence on one of them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610499 Title: /bin/kill in ubuntu16.04 has bug in killing process group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1610499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606078] Re: No sound with Ubuntu 16.04
Perhaps the problem lies in the fact that the kernel my machine is running (4.4.0-38-generic) is not among those listed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606078] Re: No sound with Ubuntu 16.04
Disregard that last message please. User snafu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606078] Re: No sound with Ubuntu 16.04
Additionally, the previously mentioned site for DKMS upgrade suggests the following: "Then check what kernel you're running with the "uname -r" command." However terminal informs: uname-r: command not found Any other suggestions on determining which kernel my machine is running? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606078] Re: No sound with Ubuntu 16.04
After removing the changes made in file /etc/modprobe.d I also tried both packages as described above but neither one resulted in audio from the built in speakers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606078] Re: No sound with Ubuntu 16.04
Might note after adding recommended line, terminal note reads: ** (gedit:5965): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs