[Touch-packages] [Bug 1854441] Re: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1854441 Title: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Nov 29 08:07:35 2019 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-24 (35 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1854441/+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 1854441] [NEW] package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Nov 29 08:07:35 2019 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-24 (35 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1854441 Title: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: libnss3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Nov 29 08:07:35 2019 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-10-24 (35 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.183.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1854441/+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 1843352] Re: systemd package version 237-3ubuntu10.28 breaks local network DNS resolution
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- 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/1843352 Title: systemd package version 237-3ubuntu10.28 breaks local network DNS resolution Status in systemd package in Ubuntu: Expired Bug description: After upgrading to the latest package the systemd-resolved service fails to resolve names for local network.Manually invoking nslookup works fine. The only suspicious output from journalctl seems: systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. The latest change in that package is: * SECURITY UPDATE: Unprivileged users are granted access to privileged systemd-resolved D-Bus methods - d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch: drop trusted annotation from bus_open_system_watch_bind() - CVE-2019-15718 -- Chris Coulson Thu, 29 Aug 2019 23:30:33 +0100 Please revert this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843352/+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 1854403] [NEW] Need updated libimobiledevice and dependencies to access iOS 13 devices
Public bug reported: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New ** Affects: libplist (Ubuntu) Importance: Undecided Status: New ** Affects: libusbmuxd (Ubuntu) Importance: Undecided Status: New ** Affects: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Also affects: usbmuxd (Ubuntu) Importance: Undecided Status: New ** Also affects: libusbmuxd (Ubuntu) Importance: Undecided Status: New ** Also affects: libplist (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: New Status in libplist package in Ubuntu: New Status in libusbmuxd package in Ubuntu: New Status in usbmuxd package in Ubuntu: New Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1838154] Re: alt-tabbing starts to kill something
** Description changed: - It looks like you just have to avoid alt-tabbing. >:] + The following settings get rid of some kind of flickering + or slow-down during typing and so on. - __ - Additional info: 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) + + 3. Avoid alt-tabbing. >:] + + __ + + Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) ** Summary changed: - alt-tabbing starts to kill something + Something hinders XFCE performance. >:] ** Description changed: - The following settings get rid of some kind of flickering or slow-down during typing and so on. - 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) 3. Avoid alt-tabbing. >:] + + 4. Rename Temptlates to "# Templates". __ Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) ** Description changed: The following settings get rid of some kind of flickering or slow-down during typing and so on. 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) 3. Avoid alt-tabbing. >:] - 4. Rename Temptlates to "# Templates". + 4. Rename Templates to "# Templates". __ Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) -- 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/1838154 Title: Something hinders XFCE performance. >:] Status in wayland: New Status in Xfce4 Desktop: New Status in Xfwm4: New Status in X.Org X server: New Status in xorg package in Ubuntu: New Status in xfwm4 package in Fedora: Unknown Bug description: The following settings get rid of some kind of flickering or slow-down during typing and so on. 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) 3. Avoid alt-tabbing. >:] 4. Rename Templates to "# Templates". __ Additional info: two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
** Attachment added: "headphones" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308568/+files/headphones -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
The only other Bluetooth headphones I've had access to recently were a pair of Bose QC35 (1st generation). They showed up in the list of visible BT devices, but my laptop couldn't connect to them at all, despite numerous attempts. As a result, I bought the Sonys and got rid of the Bose. If you take a look at bug 1724919, you'll see that other people have the same problem with other models of headphones. Attached is a copy of /var/log/syslog since last boot, with minor cleaning. Note that just after booting I wanted to use the headphones for real, so I manually ran the attached 'headphones' script to disconnect the headphones, reconnect them, and force A2DP mode. Then at 18:09:17, I deliberately recreated the bug by connecting the headphones, and unsuccessfully trying to set A2DP in the sound settings. ** Attachment added: "syslog_cleaned.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+attachment/5308567/+files/syslog_cleaned.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
That's not /really/ helpful anyway. You'd have installed an extra application, for a wholly unrelated issue, and still have to set the profile to A2DP yourself. Alistair, there are messages in your logs that seem to point to a firmware issue: Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Furthermore, I see some slightly unusual messages that point to an issue with the firmware (usually) as well: Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 It's possible the hardware gets confused by losing the connection that was initially there. I realize this might not be /so/ helpful, but have you also tried with another model of bluetooth headphones, assuming you have something available? Please see if you can attach the full contents of /var/log/syslog after reproducing the issue (with a different model or with the usual Sonys); once you've made sure that it doesn't contain sensitive data. I'd need to know when you started each attempt so we can see exactly how the system reacts to it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Could you please attach the PPD files of your printer, once of a Ubuntu version in which the duplex works correctly (19.04 for example) and once for a Ubuntu version where duplex printing does not work correctly (19.10 for example). Could you also supply a CUPS error_log for one working job (from 19.04 for example) and one non-working job (from 19.10 for example). Follow the instructions of the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Also run the command driverless to get your printer's IPP URI and then run ipptool -tv get-printer-attributes-2.0.test > attrs.txt If attrs.txt contains only a few lines or is empty, run ipptool -tv get-printer-attributes.test > attrs.txt This you only need to do on 19.10, not on both systems. Please attach your PPDs, error_logs, and attrs.txt, one by one. Do not compress them and do not package them together. ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: Incomplete Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1
[Touch-packages] [Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
How do I run blueman after installing it? $ blueman Command 'blueman' not found, did you mean: command 'bluemon' from deb bluemon (1.4-7) Try: sudo apt install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
Sounds similar to https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1577197 Can you install blueman, connect to the headset, right click on the headset in blueman, go to audio profile, select off, disconnect headset then reconnect and can you set the audio profile to A2DP then -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1853374] Re: pulseaudio disables GP107GL output every so often
Interestingly, both PCs have webcams (both Logitech, but different models) and if I unplug that on PC2 and switch, there isn't a problem. I'll try doing it some more next week and see if that's consistent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853374 Title: pulseaudio disables GP107GL output every so often Status in pulseaudio package in Ubuntu: New Bug description: Since upgrading to 19.10, the sound output on this PC stops. Looking at the volume control's 'sound settings', the GP107GL High Definition Audio Controller (digital stereo HMDI 2 output) is disabled. Doing pluseaudio -k restores it. Possibly relevant from syslog: Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 4 Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 3 Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data byte 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: Confirmed Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+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 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
http://patchwork.ozlabs.org/patch/1202263/ Upstream change submitted to fix this. ** Changed in: linux-hwe-edge (Ubuntu) Status: Invalid => In Progress ** Changed in: linux-hwe-edge (Ubuntu Bionic) Status: Invalid => In Progress ** Description changed: + [Impact] + selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. + + [Test case] + Run the script directly and verify there are no failures. + sudo ./tools/testing/selftests/net/pmtu.sh + + [Regression potential] + No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. + + + + 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] - Upgrading iproute2 to 5.2 fixes this. ** Changed in: linux-hwe-edge (Ubuntu) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-hwe-edge (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: In Progress Status in iproute2 source package in Bionic: New Status in linux-hwe-edge source package in Bionic: In Progress Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh
[Touch-packages] [Bug 1854001] Re: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3
The log only shows the SKIPs. I managed to reproduce one FAIL that I have seen as well: TEST: ipv6: list and flush cached exceptions[FAIL] can't list cached exceptions This one ended up being caused by the script itself and a difference in behavior between different versions of iproute2. Recent iproute2, when introducing json output support for ip route, ended up removing the newline for IPv6, while keeping it for IPv4. The script author assumed the newest behavior, but also accounted for the two lines per entry for IPv4. iproute2, however, has a -oneline option that could just have been used in this case and that would fix the whole problem. Using it fix the FAIL, while we still have the SKIPs, which would require a new version of iproute2, at least on -backports. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1854001 Title: pmtu net kernel selftests are skipped on bionic linux-hwe-edge 5.3 Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: In Progress Status in iproute2 source package in Bionic: New Status in linux-hwe-edge source package in Bionic: In Progress Bug description: [Impact] selftests will incorrectly indicate a failure, taking the time of developers to verify a false positive, and preventing us from finding real bugs in the corresponding code. [Test case] Run the script directly and verify there are no failures. sudo ./tools/testing/selftests/net/pmtu.sh [Regression potential] No kernel code was changed, only the test. The fix could cause false positives to happen with newer versions of iproute2, but those were tested as well. 11:52:44 DEBUG| [stdout] # selftests: net: pmtu.sh 11:52:44 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] 11:52:44 DEBUG| [stdout] # vxlan4 not supported 11:52:44 DEBUG| [stdout] # TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] 11:52:46 DEBUG| [stdout] # TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv4 over geneve4: PMTU exceptions [SKIP] 11:52:47 DEBUG| [stdout] # geneve4 not supported 11:52:47 DEBUG| [stdout] # TEST: IPv6 over geneve4: PMTU exceptions [SKIP] 11:52:48 DEBUG| [stdout] # TEST: IPv4 over geneve6: PMTU exceptions [ OK ] 11:52:49 DEBUG| [stdout] # TEST: IPv6 over geneve6: PMTU exceptions [ OK ] 11:52:51 DEBUG| [stdout] # TEST: IPv4 over fou4: PMTU exceptions [ OK ] 11:52:52 DEBUG| [stdout] # TEST: IPv6 over fou4: PMTU exceptions [ OK ] 11:52:53 DEBUG| [stdout] # TEST: IPv4 over fou6: PMTU exceptions [ OK ] 11:52:54 DEBUG| [stdout] # TEST: IPv6 over fou6: PMTU exceptions [ OK ] 11:52:55 DEBUG| [stdout] # TEST: IPv4 over gue4: PMTU exceptions [ OK ] 11:52:57 DEBUG| [stdout] # TEST: IPv6 over gue4: PMTU exceptions [ OK ] 11:52:58 DEBUG| [stdout] # TEST: IPv4 over gue6: PMTU exceptions [ OK ] 11:52:59 DEBUG| [stdout] # TEST: IPv6 over gue6: PMTU exceptions [ OK ] 11:53:00 DEBUG| [stdout] # TEST: vti6: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: PMTU exceptions [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti6: default MTU assignment [ OK ] 11:53:03 DEBUG| [stdout] # TEST: vti4: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU setting on link creation [ OK ] 11:53:04 DEBUG| [stdout] # TEST: vti6: MTU changes on link changes [ OK ] 11:53:04 DEBUG| [stdout] # vxlan4 not supported 11:53:04 DEBUG| [stdout] # TEST: ipv4: cleanup of cached exceptions [SKIP] Upgrading iproute2 to 5.2 fixes this. To manage
[Touch-packages] [Bug 1838154] Re: alt-tabbing starts to kill something
** Project changed: null-and-void => xorg (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/1838154 Title: alt-tabbing starts to kill something Status in wayland: New Status in Xfce4 Desktop: New Status in Xfwm4: New Status in X.Org X server: New Status in xorg package in Ubuntu: New Status in xfwm4 package in Fedora: Unknown Bug description: It looks like you just have to avoid alt-tabbing. >:] __ Additional info: 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1838154/+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 1849859] Re: error when connecting to smb server
I looked at the existing bug reports, but I don't think any of the patches fix the problem. Furthermore, I tried debian's 4.11.1 samba package, and got the same error. I now emailed samba-technical@ with a question: https://lists.samba.org/archive/samba-technical/2019-November/134602.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1838154] [NEW] alt-tabbing starts to kill something
You have been subscribed to a public bug: It looks like you just have to avoid alt-tabbing. >:] __ Additional info: 1. Snapping settings: 1 (top) 1 (bottom) 0 (left) 2 (right) 2. Send message trick lowers temperature. :-) two spaces bug - https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716 https://bugzilla.redhat.com/show_bug.cgi?id=1754300#c2 Templates bug - https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1836462 https://bugzilla.redhat.com/show_bug.cgi?id=1729666 :-) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: wayland Importance: Undecided Status: New ** Affects: xfdesktop Importance: Undecided Status: New ** Affects: xfwm4 Importance: Undecided Status: New ** Affects: xorg-server Importance: Undecided Status: New ** Affects: xfwm4 (Fedora) Importance: Unknown Status: Unknown -- alt-tabbing starts to kill something https://bugs.launchpad.net/bugs/1838154 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Because no-one is willing to re-open this bug, I have opened new bug 1854392 for this same problem on newer versions of Ubuntu such as 19.10. Those who are affected by this problem, please add a note to bug 1854392 stating that you're affected. https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392 -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1854392] [NEW] Bluetooth headphones won't use A2DP on reconnect
Public bug reported: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-04 (55 days ago) dmi.bios.date: 08/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET56W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET56W(1.35):bd08/30/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:3713310 acl:385 sco:2759 events:508913 errors:0 TX bytes:432771109 acl:506248 sco:2734 commands:2514 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T09:41:27.085337 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect Status in bluez package in Ubuntu: New Bug description: *** This bug is the same as bug 1724919, but is NOT A DUPLICATE because that bug was closed because it was reported for Ubuntu 17.10, which is out of support. This bug is for newer versions, such as 19.10. PLEASE DO NOT MARK THIS BUG AS A DUPLICATE. *** On Ubuntu 19.10 on my Thinkpad T470s, my Sony WH-1000XM3 headphones pair using Bluetooth with no problems, and use A2DP by default. If I then power off the headphones and power them back on, they reconnect but use HSP/HFP and sound terrible. If I manually go into the sound settings, A2DP is offered as an option, but selecting it doesn't take effect. The headphones remain stuck in HSP/HFP mode. Unpairing the headphones and re-pairing them again selects A2DP by default, until the next time I switch the headphones off. Then they're back to stuck in HSP/HFP until I unpair them once again. I therefore need to unpair and re-pair them every time I want to use them, which is a nuisance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Nov 28 13:28:52 2019 InstallationDate: Installed on 2017-08-16 (833 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb
[Touch-packages] [Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal
Ready for review and sponsoring in Debian: https://salsa.debian.org /gnome-team/librsvg/merge_requests/5 ** Changed in: librsvg (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal Status in librsvg package in Ubuntu: In Progress Bug description: focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and librsvg 2.44.15 fails to build from source with this version. It built fine with rustc 1.37 (although there was a unit test failure on ppc64el, which prevented it from leaving focal-proposed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942022). The upstream commit that addresses this is https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8. I backported it and added another patch to update the vendored crates in the source tarball accordingly, and the build succeeds again, but unit tests consistently fail, on all architectures. The upstream commit message says « Although you should rather be using the 2.46 branch of librsvg as 2.44 is EOL », so we should probably update librsvg in debian to 2.46 indeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+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 1852772] Re: test_updates_interval fails on focal
I see no objection at all; that fix looks obviously correct and does fix
the test.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
Status in software-properties package in Ubuntu:
Triaged
Bug description:
==
FAIL: test_updates_interval (tests.test_dbus.TestDBus)
--
Traceback (most recent call last):
File "/build/software-properties-0.98.6/tests/test_dbus.py", line 332, in
test_updates_interval
self.assertTrue('APT::Periodic::Update-Package-Lists "1";' in config)
AssertionError: False is not true
Looking closer, while in the SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py, days is of
dbus.Int32 type. A simple print output shows:
days=dbus.Int32(1)
D-Bus is statically typed, unlike python. More details at:
https://dbus.freedesktop.org/doc/dbus-python/tutorial.html#data-types
I think once we're in the dbus method (SetUpdateInterval() method in
softwareproperties/dbus/SoftwarePropertiesDBus.py) we can convert the
dbus.Int32 to an int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+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 1846821] Re: Qt print dialog has wrong default page size
This bug was fixed in the package qtbase-opensource-src - 5.9.5+dfsg- 0ubuntu2.4 --- qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.4) bionic; urgency=medium * Fix default paper size in the print dialog (LP: #1846821). -- Dmitry Shachnev Thu, 31 Oct 2019 00:00:50 +0300 ** Changed in: qtbase-opensource-src (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Released Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1846821] Update Released
The verification of the Stable Release Update for qtbase-opensource-src has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: Confirmed Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1849859] Re: error when connecting to smb server
Ok, I think I got something. It's working in bionic, and in eoan I got: root@nsnx:~# /usr/lib/cups/backend/smb smb://10.10.1.6/ds216laser 34 root "Test Page" 1 "job-uuid=urn:uuid:efa8b6df-0724-3252-4657-11e6ac474646 job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1574951400 time-at-processing=1574952123" .bashrc kerberos_ccache_is_valid: Failed to get default principal from ccache: FILE:/tmp/krb5cc_0 DEBUG: This backend requires credentials! DEBUG: get_exit_code(nt_status=NT_STATUS_ACCESS_DENIED [c022]) ATTR: auth-info-required=none DEBUG: Unable to connect to CIFS host: NT_STATUS_ACCESS_DENIEDroot@nsnx:~# That's something I can work with. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1854371] [NEW] Input lag with Razer Naga Trinity mouse
Public bug reported: When pressing multiple keys on my keyboard (Roccat isku FX) and pressing repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga Trinity) at the same time, the system freeze while doing this. All become normal again when I stop doing this. While freezing, I can see the Xorg process going up to 60/70% of the CPU. Not sure if it is a Xorg or driver related problem, or anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 15:25:50 2019 DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-22-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:1385] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 eoan performance ubuntu ** Summary changed: - Input lag with Razer Naga Trinity + Input lag with Razer Naga Trinity mouse -- 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/1854371 Title: Input lag with Razer Naga Trinity mouse Status in xorg package in Ubuntu: New Bug description: When pressing multiple keys on my keyboard (Roccat isku FX) and pressing repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga Trinity) at the same time, the system freeze while doing this. All become normal again when I stop doing this. While freezing, I can see the Xorg process going up to 60/70% of the CPU. Not sure if it is a Xorg or driver related problem, or anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
I can confirm this bug on a different printer; Brother MFC-L2720DW. It runs over the network, and without any drivers or any special setup. No matter if I choose long or short edge, it will print as if I selected short edge. This worked in 19.04, so it seems the issue has been introduced in 19.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: Confirmed Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
** Changed in: snapd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Won't Fix Status in systemd source package in Xenial: Fix Released Status in snapd source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in snapd source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] # make snapd-env-generator executable if it is not $ sudo chmod +x /usr/lib/systemd/system-environment-generators/snapd-env-generator # reboot, then test the effect of the fix $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1849859] Re: error when connecting to smb server
Hm, scratch that, it also didn't work with bionic, so I must be doing something wrong. I'm gonna need reproduction steps I'm afraid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1099788] Re: I can't uninstall completely whoopsie
I have a similar issue while removing whoopsie within a preseed
installation, so whoopsie will be removed before it is started the first
time.
$ sudo apt purge whoopsie
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
whoopsie*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 227602 files and directories currently installed.)
Purging configuration files for whoopsie (0.2.69) ...
rm: cannot remove '/var/lib/whoopsie/whoopsie-id': No such file or directory
dpkg: error processing package whoopsie (--purge):
installed whoopsie package post-removal script subprocess returned error exit
status 1
Errors were encountered while processing:
whoopsie
E: Sub-process /usr/bin/dpkg returned an error code (1)
As you can see, the post-removal script is missing the whoopsie-id file. After
creating the dir and file, the post-removal script runs fine.
Tested under Ubuntu focal.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1099788
Title:
I can't uninstall completely whoopsie
Status in whoopsie package in Ubuntu:
Invalid
Bug description:
$ sudo aptitude -y purge whoopsie
The following packages will be REMOVED:
whoopsie{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
(Reading database ... 331880 files and directories currently installed.)
Removing whoopsie ...
Purging configuration files for whoopsie ...
dpkg: error processing whoopsie (--purge):
subprocess installed post-removal script returned error exit status 1
No apport report written because MaxReports is reached already
Errors were
encountered while processing:
whoopsie
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: whoopsie (not installed)
Uname: Linux 3.7.2-999-i7 x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
Date: Tue Jan 15 12:29:07 2013
InstallationDate: Installed on 2013-01-10 (4 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release
amd64(20121023)
MarkForUpload: True
ProcEnviron:
LANGUAGE=es_ES:en
TERM=xterm
PATH=(custom, no user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1099788/+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 1854355] Re: LUKS partition on LVM with two disks has wrong device name
** Package changed: xubuntu-meta (Ubuntu) => lvm2 (Ubuntu) ** Description changed: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) - + Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. - Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. - + Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. + Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part - └─nvme0n1p3_crypt 253:00 952.7G 0 crypt - ├─ubuntu--vg-root 253:10 930.4G 0 lvm / - └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] + └─nvme0n1p3_crypt 253:00 952.7G 0 crypt + ├─ubuntu--vg-root 253:10 930.4G 0 lvm / + └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk - - The LUKS partition doesn’t appear to under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. - + + The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on + nvme1n1p3 which can be seen when running a luksDump command. + Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1854355 Title: LUKS partition on LVM with two disks has wrong device name Status in lvm2 package in Ubuntu: New Bug description: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to be under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1854355/+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 1854355] [NEW] LUKS partition on LVM with two disks has wrong device name
You have been subscribed to a public bug: Ubuntu release: Ubuntu Desktop 18.04.2 LTS Kernel: 5.0.0-36-generic Storage devices: two NVMe SSDs (1TB and 512GB) Ubuntu Desktop install – selected the options to use disk encryption and LVM The largest disk (1TB) is used for the Ubuntu install and this has the device name /dev/nvme0n1 in the Ubiquity installer. Install completes and upon rebooting the operating system asks for the encryption passphrase for the LUKS partition (nvme0n1p3_crypt) which does decrypt as expected. Now when logging in and running lsblk it shows the LUKS partition to be in the wrong place. The 1TB disk now has the name nvme1n1 but the LUKS partition on that disk has the name nvme0n1p3_crypt. Output of lsblk: nvme1n1 259:00 953.9G 0 disk ├─nvme1n1p1 259:10 512M 0 part /boot/efi ├─nvme1n1p2 259:20 732M 0 part /boot └─nvme1n1p3 259:30 952.7G 0 part └─nvme0n1p3_crypt 253:00 952.7G 0 crypt ├─ubuntu--vg-root 253:10 930.4G 0 lvm / └─ubuntu--vg-swap_1 253:20 976M 0 lvm [SWAP] nvme0n1 259:40 477G 0 disk The LUKS partition doesn’t appear to under nvme0n1p3 but it does on nvme1n1p3 which can be seen when running a luksDump command. Output of luksDump: root@USERPC:~# cryptsetup luksDump /dev/nvme0n1p3 | grep -i "slot 0" Device /dev/nvme0n1p3 doesn't exist or access denied. root@USERPC:~# cryptsetup luksDump /dev/nvme1n1p3 | grep -i "slot 0" Key Slot 0: ENABLED The implications of this so far in my case is not being able to find the correct LUKS partition device name via custom scripts to populate/modify key slots (e.g. 'dmsetup ls' returns the device name nvme0n1p3_crypt). There has not been an issue with Ubuntu decrypting the disk before the login screen. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- LUKS partition on LVM with two disks has wrong device name https://bugs.launchpad.net/bugs/1854355 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. -- 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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Suddenly my mic stopped working too, it is a ThinkPad T480s. It worked a couple of weeks ago last time I tried it. When setting the input level to max, I can see a faint signal on the visual input bar. Any suggestion how to see what is wrong? -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: New Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1854336] [NEW] GNOME apps in Kubuntu 19.10 doesn't respect GNOME window settings
Public bug reported: All GNOME/Gtk apps in Kubuntu 19.10 ignore gnome settings, both from gui and cli tool. i.e. setting schema button-layout in org.gnome.desktop.wm.preferences from default 'appmenu:close' to custom 'close,minimize,maximize:' doesn't have any effect - gtk window widgets are always on the right, while KDE ones are on left, as set in KDE settings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 28 11:13:01 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5059] InstallationDate: Installed on 2019-10-29 (29 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20GKS0HQ00 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R0CET27W (1.15 ) dmi.board.asset.tag: dmi.board.name: 20GKS0HQ00 dmi.board.vendor: LENOVO dmi.board.version: S dmi.chassis.asset.tag: dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0CET27W(1.15):bd09/05/2016:svnLENOVO:pn20GKS0HQ00:pvrThinkPad13:rvnLENOVO:rn20GKS0HQ00:rvrS:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad 13 dmi.product.name: 20GKS0HQ00 dmi.product.sku: LENOVO_MT_20GK_BU_Think_FM_ThinkPad 13 dmi.product.version: ThinkPad 13 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: eoan gtk kde kubuntu ubuntu ** Attachment added: "Screenshot_20191128_111939.png" https://bugs.launchpad.net/bugs/1854336/+attachment/5308424/+files/Screenshot_20191128_111939.png -- 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/1854336 Title: GNOME apps in Kubuntu 19.10 doesn't respect GNOME window settings Status in xorg package in Ubuntu: New Bug description: All GNOME/Gtk apps in Kubuntu 19.10 ignore gnome settings, both from gui and cli tool. i.e. setting schema button-layout in org.gnome.desktop.wm.preferences from default 'appmenu:close' to custom 'close,minimize,maximize:' doesn't have any effect - gtk window widgets are always on the right, while KDE ones are on left, as set in KDE settings. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 28 11:13:01 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5059] InstallationDate: Installed on 2019-10-29 (29 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20GKS0HQ00 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1854182] Re: help
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1854182 Title: help Status in xorg package in Ubuntu: Incomplete Bug description: laguntza, mesedez ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 27 17:30:17 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82G33/G31 Express Integrated Graphics Controller [103c:2a6f] InstallationDate: Installed on 2016-11-10 ( days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP-Pavilion FR555AA-ABE m9461es ProcEnviron: PATH=(custom, no user) LANG=eu_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=85a86e65-b1aa-4527-b923-c1438c9e466f ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnFR555AA-ABEm9461es:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FR555AA-ABE m9461es dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 20 21:04:01 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1854182/+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 1749657] Re: screen is flickering
Thank you for your bug report. Reassigning to the kernel since it's probably a video driver issue. You might have better chance on improved support for modern hardware on 18.04 rather than 16.04 though ** Package changed: xorg (Ubuntu) => linux (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/1749657 Title: screen is flickering Status in linux package in Ubuntu: Confirmed Bug description: Screen is flickering on my dell xps 15 running Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 15 10:12:15 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-33-generic, x86_64: installed bbswitch, 0.8, 4.13.0-35-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-33-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-35-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-09-27 (140 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-35-generic.efi.signed root=UUID=63cbf25f-ad34-40e1-af90-25ddd40ccb0d ro quiet splash acpi=force vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749657/+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 1655189] Re: Cannot record videos into Theora
Launchpad has imported 7 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=99342. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-01-10T12:35:09+00:00 Alberto Salvia Novella wrote: HOW TO REPRODUCE: Record a video using the Theora codec. RESULT: In the recording the image is frozen or broken, as seen in the following samples from various programs: - Guvcview: (https://goo.gl/Csxg2u) - RecordMyDesktop: (https://goo.gl/T2vamz) - Transmageddon: (https://goo.gl/JnGCgV) RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - Happens in a computer using Intel graphics (https://goo.gl/m85BZt), but not in another using Radeon graphics (https://goo.gl/xSHD1Z). - Doesn't happen when using other codecs: (https://goo.gl/M6cR4D). - The guvcview application shows some errors in stderr: (https://goo.gl/PiD9B3) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 01:17:54 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 libogg0 1.3.2-1 multiarch-support 2.23-0ubuntu5 InstallationDate: Installed on 2013-01-25 (1445 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: libtheora UpgradeStatus: Upgraded to xenial on 2016-08-05 (157 days ago) Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/10 On 2017-01-10T12:42:11+00:00 Chris Wilson wrote: Start with Xorg.0.log, glxinfo, vainfo and details on how you record the video. Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/11 On 2017-01-10T12:51:25+00:00 Alberto Salvia Novella wrote: Created attachment 128850 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/12 On 2017-01-10T12:53:16+00:00 Alberto Salvia Novella wrote: Created attachment 128851 glxinfo.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/13 On 2017-01-10T12:55:01+00:00 Alberto Salvia Novella wrote: Created attachment 128852 vainfo.txt Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/14 On 2017-01-10T12:57:49+00:00 Alberto Salvia Novella wrote: What I did to record those videos was mostly to clic on the "Record" button from the various applications. Which where a web-cam recorder, a desktop recorder, and a video converter. Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/15 On 2019-11-27T13:47:09+00:00 Martin-peres-n wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/134. Reply at: https://bugs.launchpad.net/ubuntu/+source/libtheora/+bug/1655189/comments/16 ** Changed in: xorg-server Importance: Unknown => Medium ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues #134 https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/134 -- 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/1655189 Title: Cannot record videos into Theora Status in guvcview: Confirmed Status in recordmydesktop: Confirmed Status in theora: Unknown Status in X.Org X server: Unknown Status in libtheora package in Ubuntu: Triaged Status in xorg package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Record a video using the Theora codec. RESULT: - In the recording the image is frozen or broken. RELEVANT DETAILS: - Doesn't matter which application you use to record or play the video. - I'm attaching samples from various programs. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libtheora0 1.1.1+dfsg.1-8 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux
