[Touch-packages] [Bug 1893925] Re: WF-SP800N Bluetooth ear pods not detected as sound device
Still a problem in hirsute ** Attachment added: "bluetooth settings UI" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+attachment/5512392/+files/Screenshot%20from%202021-07-21%2009-43-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893925 Title: WF-SP800N Bluetooth ear pods not detected as sound device Status in alsa-driver package in Ubuntu: New Bug description: They seem to pair ok, but don't show up as sound hardware, either microphone or speaker/headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertc3384 F pulseaudio /dev/snd/pcmC0D0p: robertc3384 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 22:00:24 2020 InstallationDate: Installed on 2020-07-07 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934981] [NEW] systemctl suspend-then-hibernate attempts hybrid-sleep instead
Public bug reported: ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934981 Title: systemctl suspend-then-hibernate attempts hybrid-sleep instead Status in systemd package in Ubuntu: New Bug description: ``` systemctl suspend-then-hibernate Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" not supported ``` Note the verb change! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 08:54:01 2021 InstallationDate: Installed on 2021-07-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/username-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2021 dmi.bios.release: 1.5 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0PP9G2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893925] [NEW] WF-SP800N Bluetooth ear pods not detected as sound device
Public bug reported: They seem to pair ok, but don't show up as sound hardware, either microphone or speaker/headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertc3384 F pulseaudio /dev/snd/pcmC0D0p: robertc3384 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 22:00:24 2020 InstallationDate: Installed on 2020-07-07 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1893925 Title: WF-SP800N Bluetooth ear pods not detected as sound device Status in alsa-driver package in Ubuntu: New Bug description: They seem to pair ok, but don't show up as sound hardware, either microphone or speaker/headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robertc3384 F pulseaudio /dev/snd/pcmC0D0p: robertc3384 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 22:00:24 2020 InstallationDate: Installed on 2020-07-07 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886729] [NEW] Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly
Public bug reported: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9 connected 1920x2160+7680+0 (normal left inverted right x axis y axis) 527mm x 296mm 1920x2160 59.99*+ 1920x1200 59.88 which in theory if summed together would be one whole screen. But attempting to configure the output results in an error: xrandr --output DP-1 --auto --left-of eDP-1 --output DP-3-9 --auto --right-of DP-3-8 --output DP-3-8 --auto --right-of eDP-1 xrandr: cannot find crtc for output DP-3-8 I'm not sure if this is an intrinsic limitation of the USB-C->DP dongle, or whether there is something that can be done in the software to deal with this 10 year old hardware hack I have sitting on my desktop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 11:20:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] InstallationDate: Installed on 2020-07-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886729 Title: Dell displayport YJ3Y6 adapter doesn't drive 4K screen properly Status in xorg package in Ubuntu: New Bug description: I have some early dell 4k 60hz screens - the ones which report 2 panels internally for DP 60Hz - horrid hack I know; I recently got a new XPS laptop and put Ubuntu on it. That XPS laptop has two USB-C/thunderbolt ports, so to drive the screens I bought two slightly different DP adapters - one with power passthrough, and a cheaper one that only does DP. The more expensive one 'USB-C to HDMI/DP' drives the monitor happily over DP, though sadly only at 30Hz - can't have everything :/. It reports one monitor as one output: DP-1 in the attached information: DP-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 527mm x 296mm 3840x2160 29.98*+ 30.0029.97 1920x1200 59.88 ... The cheaper one reports the single monitor as two distinct outputs, at 60hz interestingly - DP-3-8 connected (normal left inverted right x axis y axis) 1920x2160 59.99 + DP-3-9
[Touch-packages] [Bug 1268421] Re: Test failures if subunit module is installed
** Changed in: subunit Importance: High = Wishlist ** Summary changed: - Test failures if subunit module is installed + Test failures if tests are run from an installed copy of subunit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1268421 Title: Test failures if tests are run from an installed copy of subunit Status in subunit: Triaged Status in subunit package in Ubuntu: Triaged Bug description: Several tests in the test_subunit_filter.py file run the subunit- filter command as part of the test suite. They find the path to the file by doing: root = os.path.dirname(os.path.dirname(os.path.dirname(os.path.dirname(__file__ Which will fail if the subunit module has been installed to a virtualenv. This logic ought to work in both cases. To reproduce: autoreconf -vi mkdir -p build/py33 virtualenv -p python3.3 build/py33/ve . build/py33/ve/bin/activate easy_install testtools easy_install testscenarios python setup.py install cd build/py33 ../../configure make distcheck Leaving out the 'python setup.py install' makes all the tests work. To manage notifications about this bug go to: https://bugs.launchpad.net/subunit/+bug/1268421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367907] Re: Segfault in gc with cyclic trash
The patch is pretty small, I think this is a good candidate for a SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1367907 Title: Segfault in gc with cyclic trash Status in Messaging API for OpenStack: New Status in Python: Unknown Status in “python3.4” package in Ubuntu: New Bug description: Trusty's python3.4 package is affected by python bug http://bugs.python.org/issue21435. This bug was fixed in http://hg.python.org/cpython/rev/64ba3f2de99c. Trusty should pull this fix into the python3.4 package. Note this definitely affects some python projects. `git clone https://git.openstack.org/openstack/oslo.messaging cd oslo.messaging edit tox.ini file, copy py33 target and rename to py34 tox -repy34` will segfault due to this bug. With previous versions of python unaffected by this bug there is no segfaulting. Now for details: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy python3.4 python3.4: Installed: 3.4.0-2ubuntu1 Candidate: 3.4.0-2ubuntu1 Version table: *** 3.4.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.messaging/+bug/1367907/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268421] Re: Test failures if subunit module is installed
So this indicates that the wrong copy of subunit is being picked up by the test suite in this mode. Would love a patch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1268421 Title: Test failures if subunit module is installed Status in SubUnit: Triaged Status in “subunit” package in Ubuntu: Triaged Bug description: Several tests in the test_subunit_filter.py file run the subunit- filter command as part of the test suite. They find the path to the file by doing: root = os.path.dirname(os.path.dirname(os.path.dirname(os.path.dirname(__file__ Which will fail if the subunit module has been installed to a virtualenv. This logic ought to work in both cases. To reproduce: autoreconf -vi mkdir -p build/py33 virtualenv -p python3.3 build/py33/ve . build/py33/ve/bin/activate easy_install testtools easy_install testscenarios python setup.py install cd build/py33 ../../configure make distcheck Leaving out the 'python setup.py install' makes all the tests work. To manage notifications about this bug go to: https://bugs.launchpad.net/subunit/+bug/1268421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
