[Touch-packages] [Bug 2064007] [NEW] execve from NetworkManager fails - wrong path in app-armor profile?
Public bug reported: Linux 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ```/etc/os-release PRETTY_NAME="Ubuntu 24.04 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=noble LOGO=ubuntu-logo ``` ```/etc/apparmor.d/sbin.dhclient [...] # Support the new executable helper from NetworkManager. /usr/lib/NetworkManager/nm-dhcp-helper Pxrm, signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper, [...] ``` Starting network manager results in ``` /var/log/syslog:2024-04-28T13:35:22.453634+02:00 dhclient[]: execve (/usr/libexec/nm-dhcp-helper, ...): Permission denied ``` `/usr/lib/NetworkManager/nm-dhcp-helper` does not exist on the system. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/2064007 Title: execve from NetworkManager fails - wrong path in app-armor profile? Status in isc-dhcp package in Ubuntu: New Bug description: Linux 6.8.0-31-generic #31-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 20 00:40:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ```/etc/os-release PRETTY_NAME="Ubuntu 24.04 LTS" NAME="Ubuntu" VERSION_ID="24.04" VERSION="24.04 LTS (Noble Numbat)" VERSION_CODENAME=noble ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=noble LOGO=ubuntu-logo ``` ```/etc/apparmor.d/sbin.dhclient [...] # Support the new executable helper from NetworkManager. /usr/lib/NetworkManager/nm-dhcp-helper Pxrm, signal (receive) peer=/usr/lib/NetworkManager/nm-dhcp-helper, [...] ``` Starting network manager results in ``` /var/log/syslog:2024-04-28T13:35:22.453634+02:00 dhclient[]: execve (/usr/libexec/nm-dhcp-helper, ...): Permission denied ``` `/usr/lib/NetworkManager/nm-dhcp-helper` does not exist on the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2064007/+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 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
** Description changed: Everything's been great for a couple of months on this new machine Yesterday or the day before it started locking up hard, spontaneously, without high load. X11 freezes. Keyboard is unresponsive. Sound still worked for a while once. - I accept updates when they arrive. Recently it's been telling me to do - firmware updates, too. + Other context: + I accept OS updates when they arrive. Recently it's been telling me to do firmware updates, too. It's happening frequently enough that it's not safe for me to do anything much on the computer. I normally use this machine ~14 hours per day. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 19:40:13 2024 DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: - virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed - virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed + virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed + virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: - Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b] + Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b] InstallationDate: Installed on 2022-09-02 (510 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago) dmi.bios.date: 10/30/2023 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: N3PET20W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 21F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4: dmi.product.family: ThinkPad T14s Gen 4 dmi.product.name: 21F6CTO1WW dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4 dmi.product.version: ThinkPad T14s Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Summary changed: - T14s Gen4 Intel under 23.10 started locking up hard + T14s Gen4 Intel under 23.10 started freezing / locking up hard -- 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/2051303 Title: T14s Gen4 Intel under 23.10 started freezing / locking up hard Status in xorg package in Ubuntu: New Bug description: Everything's been great for a couple of months on this new machine Yesterday or the day before it started locking up hard, spontaneously, without high load. X11 freezes. Keyboard is unresponsive. Sound still worked for a while once. Other context: I accept OS updates when they arrive. Recently it's been telling me to do firmware updates, too. It's happening frequently enough that it's not safe for me to do anything much on the computer. I normally use this machine ~14 hours per day. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-ge
[Touch-packages] [Bug 2051303] Re: T14s Gen4 Intel under 23.10 started locking up hard
The last crash before I reported this was just before hard-rebooting around time 2024-01-25 19:30 -- 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/2051303 Title: T14s Gen4 Intel under 23.10 started locking up hard Status in xorg package in Ubuntu: New Bug description: Everything's been great for a couple of months on this new machine Yesterday or the day before it started locking up hard, spontaneously, without high load. X11 freezes. Keyboard is unresponsive. Sound still worked for a while once. I accept updates when they arrive. Recently it's been telling me to do firmware updates, too. It's happening frequently enough that it's not safe for me to do anything much on the computer. I normally use this machine ~14 hours per day. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 19:40:13 2024 DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b] InstallationDate: Installed on 2022-09-02 (510 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago) dmi.bios.date: 10/30/2023 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: N3PET20W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 21F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4: dmi.product.family: ThinkPad T14s Gen 4 dmi.product.name: 21F6CTO1WW dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4 dmi.product.version: ThinkPad T14s Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2051303/+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 2051303] [NEW] T14s Gen4 Intel under 23.10 started locking up hard
Public bug reported: Everything's been great for a couple of months on this new machine Yesterday or the day before it started locking up hard, spontaneously, without high load. X11 freezes. Keyboard is unresponsive. Sound still worked for a while once. I accept updates when they arrive. Recently it's been telling me to do firmware updates, too. It's happening frequently enough that it's not safe for me to do anything much on the computer. I normally use this machine ~14 hours per day. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 19:40:13 2024 DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a1] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] [17aa:230b] InstallationDate: Installed on 2022-09-02 (510 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']} ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-15-generic root=UUID=ebdb1e4f-ba82-441f-bc71-f4507cc97f9d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to mantic on 2024-01-15 (11 days ago) dmi.bios.date: 10/30/2023 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: N3PET20W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 21F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN3PET20W(1.11):bd10/30/2023:br1.11:efr1.8:svnLENOVO:pn21F6CTO1WW:pvrThinkPadT14sGen4:rvnLENOVO:rn21F6CTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21F6_BU_Think_FM_ThinkPadT14sGen4: dmi.product.family: ThinkPad T14s Gen 4 dmi.product.name: 21F6CTO1WW dmi.product.sku: LENOVO_MT_21F6_BU_Think_FM_ThinkPad T14s Gen 4 dmi.product.version: ThinkPad T14s Gen 4 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze mantic 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/2051303 Title: T14s Gen4 Intel under 23.10 started locking up hard Status in xorg package in Ubuntu: New Bug description: Everything's been great for a couple of months on this new machine Yesterday or the day before it started locking up hard, spontaneously, without high load. X11 freezes. Keyboard is unresponsive. Sound still worked for a while once. I accept updates when they arrive. Recently it's been telling me to do firmware updates, too. It's happening frequently enough that it's not safe for me to do anything much on the computer. I normally use this machine ~14 hours per day. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 19:40:13 2024 DistUpgraded: 2024-01-14 20:35:02,530 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: mantic DistroVariant: ubuntu DkmsStatus: virtualbox/7.0.12, 6.5.0-14-generic, x86_64: installed virtualbox/7.0.12, 6.5.0-15-generic, x86_64: installed Ecrypt
[Touch-packages] [Bug 2044654] Re: No debugging symbols found in libgdk-3.so.0
No, I do not. The bug affects debuginfod. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044654 Title: No debugging symbols found in libgdk-3.so.0 Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+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 2044654] Re: No debugging symbols found in libgdk-3.so.0
Also affects libwebkit2gtk-4.0.so.37. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044654 Title: No debugging symbols found in libgdk-3.so.0 Status in gtk+3.0 package in Ubuntu: New Bug description: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+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 2044654] [NEW] No debugging symbols found in libgdk-3.so.0
Public bug reported: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044654 Title: No debugging symbols found in libgdk-3.so.0 Status in gtk+3.0 package in Ubuntu: New Bug description: Attach gdb to a running yelp process! (gdb) share libgdk Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0... (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgtk-3-0 3.24.33-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 13:11:15 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2044654/+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 2044642] [NEW] debuginfod urls should be documented
Public bug reported: Since we do not enable debuginfod by default, it should be documented how to configure it, preferably in the file README.Debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.1-0ubuntu1~22.04 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 11:31:54 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2044642 Title: debuginfod urls should be documented Status in gdb package in Ubuntu: New Bug description: Since we do not enable debuginfod by default, it should be documented how to configure it, preferably in the file README.Debian. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb 12.1-0ubuntu1~22.04 ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 11:31:54 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2044642/+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 2044641] [NEW] Package gdb-doc is in group Development
Public bug reported: The package gdb-doc is in group Development. It should be in group Documentation instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb-doc (not installed) ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 11:17:45 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/2044641 Title: Package gdb-doc is in group Development Status in gdb package in Ubuntu: New Bug description: The package gdb-doc is in group Development. It should be in group Documentation instead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdb-doc (not installed) ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16 Uname: Linux 6.2.0-1016-azure x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 26 11:17:45 2023 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2044641/+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 2023001] Re: sshd not starting because of missing /run/sshd
My naughty chickens have come home to roost! Thanks for the quick diagnosis. -- 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/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 2023001] Re: sshd not starting because of missing /run/sshd
** Attachment added: "Output of "journalctl -b 0 --no-pager -lu systemd-tmpfiles-setup"" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+attachment/5678283/+files/journalctl.txt -- 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/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 2023001] Re: sshd not starting because of missing /run/sshd
systemctl status systemd-tmpfiles-setup says: systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since Tue 2023-06-06 01:46:37 EDT; 23h ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Main PID: 536 (code=exited, status=73) CPU: 62ms Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal. Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal. Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal/0bbe1b93d943a0a5> Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal/0bbe1b93d943a0a5> Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal/0bbe1b93d943a0a5> Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /run (owned by root) during canonicalization of /run/log/journal. Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /run (owned by root) during canonicalization of /run/log/journal. Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal/0bbe1b93d943a0a5> Jun 06 01:46:37 big-bucks systemd-tmpfiles[536]: Detected unsafe path transition / (owned by beland) → /var (owned by root) during canonicalization of /var/log/journal/0bbe1b93d943a0a5> Jun 06 01:46:37 big-bucks systemd[1]: Finished systemd-tmpfiles-setup.service - Create Volatile Files and Directories. -- 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/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 2023001] Re: sshd not starting because of missing /run/sshd
I don't know whether sshd was running immediately after the install; I noticed this problem a couple reboots after the install process was complete. Are there any logs I can check that would be helpful to reconstruct the sequence of events? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: Incomplete Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 2023001] [NEW] sshd not starting because of missing /run/sshd
Public bug reported: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2023001 Title: sshd not starting because of missing /run/sshd Status in openssh package in Ubuntu: New Bug description: I recently upgraded from Ubuntu to 22.04 to 23.04 using do-release- upgrade (twice because I upgraded via 22.10). After doing so, sshd stopped working. The output of "journalctl -xeu ssh.service" includes the line: Jun 06 01:51:05 big-bucks sshd[4544]: Missing privilege separation directory: /run/sshd This fixed the problem: sudo mkdir /run/sshd It seems like either the upgrade sequence or the service startup sequence should have done this automatically. Currently running: ssh/lunar 1:9.0p1-1ubuntu8 all There was also a problem reported with /run/sshd on bug #1991283, but I guess the fix for that didn't prevent this. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ssh (not installed) Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 6 02:37:21 2023 SourcePackage: openssh UpgradeStatus: Upgraded to lunar on 2023-06-04 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2023001/+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 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
I have the same issue as Samuel. I can connect to the hotspot just fine, but the connected devices don't have access to internet. Strangely enough I did find one workaround that fixes the problem for me in this answer: https://askubuntu.com/a/1444778 The -999 priority doesn't seem to matter, but if I set the hotspot to start automatically and then reboot, connected devices can access the internet. Also, if the hotspot is started automatically I can stop and re-start it and things still work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
For those of us who used the workaround method by @nfalse in comment 22, how and when do we undo this workaround so as to be safe and benefit from the released fix? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Confirmed Status in wpa package in Debian: Fix Released Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
Whoops -- actually, my enterprise network was a university's main wifi (wpa.mcgill.ca), not eduroam. I propose to generalize the title of this bug by dropping eduroam or changing it to (e.g. eduroam) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
On a Thinkpad X230 I had this problem after upgrading to 22.04. The recipe in comment 23 by nfalse solved the problem for me. Thank you (though this is only a temporary workaround, given its use of "UnsafeLegacyRenegotiation") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
This seems to be the same as https://bugs.launchpad.net/ubuntu/+source/evolution-data- server/+bug/1952107 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. Status in Evolution: Unknown Status in Ubuntu MATE: New Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: New Bug description: I'm running Ubuntu MATE 20.04; I stick with LTS for this system. I use Evolution for email and calendar. Tonight I got this message: = Failed to connect address book “guy.rouill...@gmail.com : Contacts” Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. == I went to report this on the GNOME bug tracker and found this existing issue: https://gitlab.gnome.org/GNOME/evolution/-/issues/1655 That issue was closed with this comment: == "Andre Klapper Issue found on latest Evolution in Debian 11 (3.38.3-1) That version is ancient and not maintained anymore by GNOME developers. Feel free to file a bug report in your distribution's issue tracker." The version in MATE is even older: 3.36.5-0ubuntu1 So apparently Evolution in MATE is currently not functional. We need to update to a later release. I will update to the newer LTS of MATE when it is released. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-10-05 (1212 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: evolution-data-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Tags: third-party-packages focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+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 1959453] [NEW] package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
Public bug reported: Could not perform a system update upon fresh install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdrm-intel1:amd64 2.4.105-3~20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jan 28 13:13:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libdrm-intel1:amd64:2.4.105-3~20.04.2 Setting up libsystemd0:amd64 (245.4-4ubuntu3.15) ... dpkg: error processing package libdrm-intel1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:883c] InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b710 Chicony Electronics Co., Ltd HP TrueVision HD Camera Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 17-cn0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=445be58c-9730-41e0-9728-2ecc1fcc50d1 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: libdrm Title: package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2021 dmi.bios.release: 15.4 dmi.bios.vendor: AMI dmi.bios.version: F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 883C dmi.board.vendor: HP dmi.board.version: 69.16 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 69.16 dmi.modalias: dmi:bvnAMI:bvrF.04:bd04/01/2021:br15.4:efr69.16:svnHP:pnHPLaptop17-cn0xxx:pvr:rvnHP:rn883C:rvr69.16:cvnHP:ct10:cvrChassisVersion:sku316H8UA#ABA: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 17-cn0xxx dmi.product.sku: 316H8UA#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1959453 Title: package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libdrm package in Ubuntu: New Bug description: Could not perform a system update upon fresh install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libdrm-intel1:amd64 2.4.105-3~20.04.2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Jan 28 13:13:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libdrm-intel1:amd64:2.4.105-3~20.04.2 Setting up libsystemd0:amd64 (245.4-4ubuntu3.15) ... dpkg: error processing package libdrm-intel1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:883c] InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
[Touch-packages] [Bug 1670313] Re: armhf unit tests as root fail on adt tests, never run on builders
thx for this thread -- 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/1670313 Title: armhf unit tests as root fail on adt tests, never run on builders Status in systemd package in Ubuntu: Won't Fix Bug description: armhf unit tests as root fail on adt tests, never run on builders xnox should fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670313/+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 1948538] Re: USB serial devices not available in /dev/serial/by-id/ after upgrade
just to clarify, before the upgrade I had /dev/ttyACM0 and a corresponding entry in /dev/serial/by-id/ for it. I've verified that a fresh image of 20.04 LTS with the same device attached does not exhibit the same issue, and the device shows up as expected. -- 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/1948538 Title: USB serial devices not available in /dev/serial/by-id/ after upgrade Status in systemd package in Ubuntu: New Bug description: it looks like systemd-udevd is crashing with the following error: -- Boot a74cfdb7e237433f9321d32ebe70e086 -- Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:14 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:27 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if [ -e /dev/ttyAMA0 ]; then exit 1; elif cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 97: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:38 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart1 $ALIASES/serial0; then echo 0; elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then echo 1; else exit 1; fi '" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. I'm not sure if this is related, or a red herring. this is on a raspberry pi 4b 2GB that was recently upgraded from 21.04 to 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu70 Architecture: arm64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.mjpg-streamer.rules Date: Sat Oct 23 13:31:46 2021 ImageMediaBuild: 20210421.1 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1d50:614e OpenMoko, Inc. lpc1769 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:E6:E5 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to impish on 2021-10-17 (6 days ago) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1948538/+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 1948538] [NEW] USB serial devices not available in /dev/serial/by-id/ after upgrade
Public bug reported: it looks like systemd-udevd is crashing with the following error: -- Boot a74cfdb7e237433f9321d32ebe70e086 -- Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:14 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:27 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if [ -e /dev/ttyAMA0 ]; then exit 1; elif cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 97: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:38 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart1 $ALIASES/serial0; then echo 0; elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then echo 1; else exit 1; fi '" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. I'm not sure if this is related, or a red herring. this is on a raspberry pi 4b 2GB that was recently upgraded from 21.04 to 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu70 Architecture: arm64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.mjpg-streamer.rules Date: Sat Oct 23 13:31:46 2021 ImageMediaBuild: 20210421.1 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1d50:614e OpenMoko, Inc. lpc1769 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:E6:E5 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to impish on 2021-10-17 (6 days ago) acpidump: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish raspi-image uec-images -- 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/1948538 Title: USB serial devices not available in /dev/serial/by-id/ after upgrade Status in systemd package in Ubuntu: New Bug description: it looks like systemd-udevd is crashing with the following error: -- Boot a74cfdb7e237433f9321d32ebe70e086 -- Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:14 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:27 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if [ -e /dev/ttyAMA0 ]; then exit 1; elif cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'" for PROGRAM (char 97: invalid substitution type), ignoring, but please fix it. Oct 23 13:28:50 Himari systemd-udevd[931]: /usr/lib/udev/rules.d/90-pi-bluetooth.rules:38 Invalid value "/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart1 $ALIASES/serial0; then echo 0; elif cmp -s $ALIASES/uart1 $ALIASES/serial1; then echo 1; else exit 1; fi '" for PROGRAM (char 58: invalid substitution type), ignoring, but please fix it. I'm not sure if this is related, or a red herring. this is on a raspberry pi 4b 2GB that was recently upgraded from 21.04 to 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8 ProcVersionSignature: Ubuntu 5.13.0-1008.9-raspi 5.13.14 Uname: Linux 5.13.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu70 Architecture: arm64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.mj
[Touch-packages] [Bug 1940757] [NEW] Keyboard/configuration
Public bug reported: have-no-space-bar.--no-#six--no-esc--and-other-key--functions--when-i- instaled-Kubontu-20.four ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 21 22:47:59 2021 DistUpgraded: 2020-10-11 03:03:06,479 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] InstallationDate: Installed on 2018-12-30 (965 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite A505 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=82ca8cbd-36b7-461a-b546-3b3631865996 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-11 (314 days ago) dmi.bios.date: 05/25/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd05/25/2010:svnTOSHIBA:pnSatelliteA505:pvrPSAT0U-00M001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite A505 dmi.product.sku: Montevina_Fab dmi.product.version: PSAT0U-00M001 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 24 17:26:30 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.2~20.04.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1940757 Title: Keyboard/configuration Status in xorg package in Ubuntu: New Bug description: have-no-space-bar.--no-#six--no-esc--and-other-key--functions--when-i- instaled-Kubontu-20.four ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Aug 21 22:47:59 2021 DistUpgraded: 2020-10-11 03:03:06,479 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] Subsystem: Toshiba Corporation Mobile 4 Series Chipset Integrated Graphics Controller [1179:ff10] InstallationDate: Installed on 2018-12-30 (965 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: TOSHIBA Satellite A505 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelC
[Touch-packages] [Bug 1493921] Re: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested)
Steve, please open a new report. Thanks! -- 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/1493921 Title: X server fails to set correct mode on resume from sleep (NVIDIA: Setting a mode on head 0 failed: An invalid mode was requested) Status in xorg package in Ubuntu: Won't Fix Bug description: Using a really picky Dell P2415Q monitor through DP->mDP (displayport -> mini displayport) cable, nvidia binary driver version 352.30-0ubuntu1. This is not a laptop, so the Intel integrated VGA is disabled. (No other cards in sysfs.) Really nasty bug, as every time all the running applications detect that the X server went away and exit, logind terminates the session culling everyone, and so on. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.30 Tue Jul 21 18:53:45 PDT 2015 GCC version: gcc version 5.2.1 20150825 (Ubuntu 5.2.1-15ubuntu5) ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 17:56:53 2015 DistUpgraded: 2014-08-06 01:18:55,244 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3614] MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic root=UUID=fba348ec-fc7c-4c7f-b78b-026be76c4568 ro crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2014-08-05 (399 days ago) dmi.bios.date: 10/24/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F18 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF18:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 9 15:10:08 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech G100s Optical Gaming Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493921/+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 1932583] Re: apport-cli requires a terminal to submit
Of course, it would be even better if apport provided an option to skip this dialogue altogether. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1932583 Title: apport-cli requires a terminal to submit Status in apport package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' Description: Ubuntu Impish Indri (development branch) Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Centerapport-noui: Installed: 2.20.11-0ubuntu67 Candidate: 2.20.11-0ubuntu67 Version table: *** 2.20.11-0ubuntu67 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Let apport-cli read S from standard input. 4) What happened instead What would you like to do? Your options are: S: Send report (8.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 717, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 556, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 213, in ui_present_report_details response = dialog.run() File "/usr/bin/apport-cli", line 99, in run response = self.raw_input_char( File "/usr/bin/apport-cli", line 49, in raw_input_char saved_attributes = termios.tcgetattr(file) termios.error: (25, 'Inappropriate ioctl for device') The command '/bin/sh -c ubuntu-bug libkf5i18n-dev' returned a non-zero code: 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1932583/+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 1932583] [NEW] apport-cli requires a terminal to submit
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' Description: Ubuntu Impish Indri (development branch) Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Centerapport-noui: Installed: 2.20.11-0ubuntu67 Candidate: 2.20.11-0ubuntu67 Version table: *** 2.20.11-0ubuntu67 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Let apport-cli read S from standard input. 4) What happened instead What would you like to do? Your options are: S: Send report (8.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 717, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 556, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 213, in ui_present_report_details response = dialog.run() File "/usr/bin/apport-cli", line 99, in run response = self.raw_input_char( File "/usr/bin/apport-cli", line 49, in raw_input_char saved_attributes = termios.tcgetattr(file) termios.error: (25, 'Inappropriate ioctl for device') The command '/bin/sh -c ubuntu-bug libkf5i18n-dev' returned a non-zero code: 1 ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1932583 Title: apport-cli requires a terminal to submit Status in apport package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' Description: Ubuntu Impish Indri (development branch) Release: 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Centerapport-noui: Installed: 2.20.11-0ubuntu67 Candidate: 2.20.11-0ubuntu67 Version table: *** 2.20.11-0ubuntu67 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Let apport-cli read S from standard input. 4) What happened instead What would you like to do? Your options are: S: Send report (8.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): Traceback (most recent call last): File "/usr/bin/apport-cli", line 387, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 717, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 556, in run_report_bug response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 213, in ui_present_report_details response = dialog.run() File "/usr/bin/apport-cli", line 99, in run response = self.raw_input_char( File "/usr/bin/apport-cli", line 49, in raw_input_char saved_attributes = termios.tcgetattr(file) termios.error: (25, 'Inappropriate ioctl for device') The command '/bin/sh -c ubuntu-bug libkf5i18n-dev' returned a non-zero code: 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1932583/+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 1929209] [NEW] external monitor goes black for several seconds at a time, randomly
Public bug reported: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. There are other related behaviours reported in the past, but I am running Ubuntu 20.10. I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (353 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: At times it is completely debilitating; at other times it does not happen for hours. The physical connections are clean and solid. - There are other related behaviours reported in the past. - I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. + There are other related behaviours reported in the past, but I am running Ubuntu 20.10. + I guess the attachments will show that I'm using Intel graphics hardware. The monitor is a very popular Samsung one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 20 16:56:04 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 5500 [17aa:5036] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (847 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli
[Touch-packages] [Bug 1923381] [NEW] regression: no display when waking from suspend
Public bug reported: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: regression: no display when waking from suspend Status in xorg package in Ubuntu: New Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMe
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Clarifying what worked for me across all the servers where I need this config: cat
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
Is it possible this regressed sometime between Bionic and Focal? I am observing this in 20.04. Early in dmesg I see my interface renamed from eth1 to eno2, then my netplan attempts to rename with a match (on name=eno2) to my desired name ("ceph" in this case). I see syslog message: systemd-udevd[844]: eno2: Config file /run/systemd/network/10-netplan- eno2.link matches device based on renamed interface name, ignoring but after boot and login, netplan apply is succsesful. Steps in #11 do not work, even though I verify the link file is in the new initrd.img at usr/lib/systemd/network/10-netplan-eno2.link What _did_ work for me, is editing this file first to refer to the eth1 name instead of eno2 (the file was written, I believe, by netplan). After this I can change my netplan to refer to the desired name with no set-name rule. Obvs. I can cut out some steps as I replicate this solution to the other servers. To summarize: write out /etc/systemd/network/10-netplan-eno2.link in a way that refers to eth1 (instead of eno2) and sets ultimately desired name. update-initramfs. netplan uses desired name without rename rules. I suppose I can/should rename that file to 10-netplan-ceph.link :-) -- 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/1770082 Title: systemd-networkd not renaming devices on boot Status in netplan: Fix Released Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Status in nplan source package in Xenial: Fix Released Status in netplan.io source package in Bionic: Fix Released Status in netplan.io source package in Cosmic: Fix Released Bug description: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: myif0 - Bring down interface : 'ip link set dev ens3 down' - Run 'netplan apply' - Verify that the device is correctly renamed to 'myif0'. - Reboot. - Make sure the device is correctly renamed to 'myif0'. [Regression potential] Changes in rename logic to add udev rules may otherwise impact applying different settings to the network interfaces. Changes in settings on network interfaces, missing parameters (especially on bonds, bridges) should be investigated as potential regressions. Other failures to apply network settings might also happen if there's a race between applying renames via the udev rules, and using the new names to apply configuration changes to the interfaces. === systemd issue === Renaming devices doesn't seem to work. If I disable all other network configuration and create /etc/systemd/network/10-network.link with: [Match] MACAddress=52:54:00:c1:c9:bb [Link] Name=myiface3 I expect this to cause the device with that MAC address to be renamed to myiface3. However, when I reboot, I instead see: $ ip l 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff The device is not renamed. This link file is pretty much identical to Example 2 in https://www.freedesktop.org/software/systemd/man/systemd.link.html. The renaming does work if I boot with net.ifnames=0, and oddly, it also works if I unbind the device and rebind it as netplan apply does. No setting of NamePolicy seems to help. === Original Bug == 'set-name:' doesn't change the name of a network interface on boot, it only works when you do netplan apply. Say I take this 50-cloud-init.yaml file: # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:de:bd:f6 set-name: ens3 Say I change set-name to 'myiface3' and reboot. I expect that the device will be called myiface3 and brought up fine with dhcp. However, instead I see: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft
[Touch-packages] [Bug 1234887] Re: [FFE] Update NetworkManager to 0.9.8.4
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => christopher wayne hess (hess8519) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1234887 Title: [FFE] Update NetworkManager to 0.9.8.4 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Saucy: Invalid Status in network-manager source package in Trusty: Fix Released Bug description: Let's update NetworkManager to 0.9.8.4; which is a bugfix release; minor version number change. Most specifically, multiple fixes for use-after-free and memory leaks, along with fixes for other possible crashes. Full list of commits is below. a450929 release: bump version to 0.9.8.4 578b7c1 release: update NEWS 4a4d58a libnm-glib: bump soname for added functions a00701d libnm-glib: fix annotations again: 0.9.8.4, not 0.9.8.6 46345e0 libnm-glib: change the "Since: 0.9.10" annotations to "Since: 0.9.8.6" 1d6947a ifcfg-rh: fix tests 90c957c build: fix builddir != srcdir when building D-Bus API spec HTML 72e3dd7 core: fix handling of ActiveConnections on Policy dispose() 65590de libnm-util: accept old-style UUIDs as valid a10dea3 agents: don't make method calls with a destroyed proxy 52b3810 core: fix NMPolicy/NMManager refcounting 59c165a build: don't use g_clear_pointer() 636387f trivial: nm_connectivity_check_async() returns void -> use g_return_if_fail() 226b9b1 core: fix warning about unused variable 299081e libnm-glib: Add NMClient:primary-connection and :activating-connection 61a81d1 core: add NMManager:primary-connection and :activating-connection 2489018 core: make NMPolicy a GObject 693112f libnm-glib: support new connectivity property/methods d34e77c core: provide additional network connectivity information a5eeeb7 core: improve NMManager:state transitions with connectivity checking 0d2ccfd core: add LOGD_CONCHECK, log unexpected concheck responses at LOGL_INFO 68356b5 core: build NMConnectivity unconditionally, possibly as a no-op a040f0b core: clean up connectivity code a bit 62e59ed ifcfg-rh: do not write IPV6_DEFAULTGW=:: for missing gateway ee58f2a policy: prevent double-deactivation of an NMActiveConnection after it's removed 49f8da5 wifi: change bgscan threshold parameter (fixes bug 1071942) 82be4aa ifcfg-rh: fix handling of VLAN parent PHYSDEV key f595624 systemd: fix up dispatcher unit install (rh #948433) 8dc646e core: don't log warnings when devices are removed 4f1e7e9 dhcp: kill dhclient on fatal errors 94f5d09 dnsmasq: does handle more than one nameserver per domain 886ee9a keyfile: ignore Emacs interlocking link named .# (rh #987629) 764f0e2 core: fix flushing of routes and updating legacy IPv4 address property 5628350 main: Set umask earlier 1a7e606 main: setenv(GIO_USE_VFS=local) *very* early dc70b48 libnm-glib: fix device description with newer udev versions b73b963 dhcp: don't crash checking lease config if no DHCP client is usable 89cb9e5 build: allow dhcpcd versions higher than 5 dad3e1c nm-online: describe '--timeout' option more exactly (rh #969363) c068709 dispatcher: fix tests after 42577c5269fdf4e9bea442eb96fcba7f8403bda5 42577c5 dispatcher: expose domains in IP4/6 config (bgo #701820) 65edeb9 dispatcher: publish vpn_ip6_config b0f23d2 libnm-util: fix possible crash when IP method is NULL d4d9d36 core: set GError on failure in nm_manager_deactivate_connection() (rh #976627) c38e901 keyfile: do not set GError over the top of a previous GError 3172ff1 dbus: fix dbus_connection_changed_cb() definition to take DBusConnection f324bfb keyfile: fix reading bonding options (bgo #701527) 8e9e392 libnm-util: remove 'downdelay' and 'updelay' when setting 'arp_interval' 261db76 libnm-util: verify() - can't set both IPv4 'disabled' and IPv6 'ignore' method 77b24af libnm-glib: fix the object creation warning for remote connections 665f42f wifi: fix checking AP mode and EAP-FAST support 050c979 agents: don't require root agents to be part of a login session 1c4f777 core: assume root always has a session for connection visibility 9b82977 release: bump version to 0.9.8.2 8d6828a libnm-util: fix 93c1041b9b3f48b42e35401b0dd756538935e870 for handling disabled 62bb5ec release: update NEWS 55ce7fe build: fix reporting of modemmanager-1 compilation status cca0bc9 wired: ignore carrier state for manual/static bridge and bond connections 9c57277 wifi: fix possible crash when IP configuration times out (rh #854073) 93c1041 libnm-util: recognize "disabled" as an IPv6 config method c126d97 modem-manager: read
[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Thanks for the workaround. Can confirm it works, I was just wondering how the key was allowed to expire, and if there is anything being done to make sure it doesn't happen again to this or other keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: The public key used by the debugging symbols repository /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu- dbgsym-keyring expired. $ apt policy ubuntu-dbgsym-keyring ubuntu-dbgsym-keyring: Installed: 2020.02.11.2 Candidate: 2020.02.11.2 Version table: *** 2020.02.11.2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status $ gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg - pub rsa4096 2016-03-21 [SC] [expired: 2021-03-20] F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Error message on "apt update": E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+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 1915793] [NEW] Suggested fix for apt installed packages catalog problem
Public bug reported: After fresh install, running sudo apt-get autoremove results in 30+ packages (over 700mb) being suggested for removal. I innocently did this and ended up with my Plasma desktop being removed.. Luckily I had a snapshot of a VM to go back to... However, This could be a jarring experience for less experienced users installing Daily build of Studio 21.04 A simple fix is to run this command post-install for the Daily Build: sudo apt-mark manual $(sudo apt-get -s autoremove 2>/dev/null | awk '/^Remv / { print $2 }') What this command does is marks all packages marked autoinstall to 'manual install'. This way while you all are adding-on things at the last minute it doesn't cause a problem if a new user innocently runs autoremove. Then when ready for release remove the above command from post-install. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.18 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-36-lowlatency x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth zfs zunicode zavl icp zcommon znvpair prl_vid prl_tg ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 19:54:47 2021 InstallationDate: Installed on 2021-02-04 (11 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1915793 Title: Suggested fix for apt installed packages catalog problem Status in apt package in Ubuntu: New Bug description: After fresh install, running sudo apt-get autoremove results in 30+ packages (over 700mb) being suggested for removal. I innocently did this and ended up with my Plasma desktop being removed.. Luckily I had a snapshot of a VM to go back to... However, This could be a jarring experience for less experienced users installing Daily build of Studio 21.04 A simple fix is to run this command post-install for the Daily Build: sudo apt-mark manual $(sudo apt-get -s autoremove 2>/dev/null | awk '/^Remv / { print $2 }') What this command does is marks all packages marked autoinstall to 'manual install'. This way while you all are adding-on things at the last minute it doesn't cause a problem if a new user innocently runs autoremove. Then when ready for release remove the above command from post- install. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.1.18 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-36-lowlatency x86_64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth zfs zunicode zavl icp zcommon znvpair prl_vid prl_tg ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 16 19:54:47 2021 InstallationDate: Installed on 2021-02-04 (11 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210203) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1915793/+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
Re: [Touch-packages] [Bug 1903396] Re: libnl-route-3-200 unresolved symbols
linux-vdso.so.1 (0x7ffcf0521000) libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200 (0x7f5a697da000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5a697b7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a695c5000) /lib64/ld-linux-x86-64.so.2 (0x7f5a698a) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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 1903396] [NEW] libnl-route-3-200 unresolved symbols
Public bug reported: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Project changed: calibre => libnl3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: New Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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 1888998] [NEW] package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: Upgrade from Ubuntu 18.04 LTS to 20.04. Got this error and the upgrader made a fuzz about reporting it, wanting to open a browser and all that. This isn't my first upgrade from one LTS release to another. Minor errors like this aren't uncommon, I'll fix it manually. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Jul 26 16:01:08 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=/dev/mapper/phosphorus-swap MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-112-generic root=/dev/mapper/hostname-root ro zswap.enabled=1 panic=30 splash quiet noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc N/A RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-07-26 (0 days ago) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1888998 Title: package linux-firmware 1.187.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: Upgrade from Ubuntu 18.04 LTS to 20.04. Got this error and the upgrader made a fuzz about reporting it, wanting to open a browser and all that. This isn't my first upgrade from one LTS release to another. Minor errors like this aren't uncommon, I'll fix it manually. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Jul 26 16:01:08 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=/dev/mapper/phosphorus-swap MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-1
[Touch-packages] [Bug 1672931] Re: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar)
** Changed in: libertine/devel Status: In Progress => Triaged ** Changed in: libertine/devel Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: libertine/devel Milestone: 1.8 => None ** Changed in: libertine/trunk Milestone: 1.8 => None ** Changed in: ubuntu-app-launch (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-app-launch (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) ** Changed in: xorg-server (Ubuntu) Status: In Progress => Triaged ** Changed in: xorg-server (Ubuntu) Assignee: Christopher Townsend (townsend) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1672931 Title: [regression] Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt (and so menus don't appear in the titlebar) Status in Canonical System Image: Confirmed Status in Libertine: Triaged Status in Libertine devel series: Triaged Status in Libertine trunk series: Triaged Status in gtk+3.0 package in Ubuntu: Fix Released Status in libertine package in Ubuntu: Triaged Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Triaged Bug description: Qt & GTK apps on Unity8 are defaulting to Xmir instead of native GTK/Qt on Mir. I noticed a slight change in appearance and performance, but also: dan 25410 0.1 0.2 423316 38996 ?Sl 11:14 0:00 Xmir -rootless -displayfd 3 -mir org.gnome.Calculator dan 25456 1.8 0.5 606084 91736 ?Sl 11:14 0:03 Xmir -rootless -displayfd 3 -mir org.gnome.Nautilus dan 25611 1.7 0.2 345312 35520 ?Sl 11:18 0:00 Xmir -rootless -displayfd 3 -mir webbrowser-app_webbrowser-app_10 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672931/+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 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Still an issue in the latest Ubuntu 20.04 release. User winds up having to click the toggle over and over again while it stubbornly snaps back. Replicated on Many different machines with different hardware. Is there anyone who can not replicate this bug? ** Changed in: bluez (Ubuntu) Status: Expired => 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Confirmed Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+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 1876211] [NEW] Bluetooth connection to headset works for volume buttons but not tests
Public bug reported: bluetooth worked fine under 19.10. Now, when bluetooth connects to my headset, I can hear noises from the increase/ decrease volume keys, but the "test" for Output Device in Sound settings makes sound on my laptop, not the headset. And all applications send sound to the laptop, not the headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 19:39:09 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BX001PUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001PUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001PUS dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: DC:53:60:42:C0:97 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:22321 acl:74 sco:0 events:1206 errors:0 TX bytes:257018 acl:319 sco:0 commands:403 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1876211 Title: Bluetooth connection to headset works for volume buttons but not tests Status in bluez package in Ubuntu: New Bug description: bluetooth worked fine under 19.10. Now, when bluetooth connects to my headset, I can hear noises from the increase/ decrease volume keys, but the "test" for Output Device in Sound settings makes sound on my laptop, not the headset. And all applications send sound to the laptop, not the headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 19:39:09 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-11-26 (156 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BX001PUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=e4714fe0-a682-44bc-b1ba-4cb61352bb03 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-26 (4 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001PUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX001PUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001PUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001PUS dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: DC:53:60:42:C0:97 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:22321 acl:74 sco:0 events:1206 errors:0 TX bytes:257018 acl:319 sco:0 commands:403 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1876211/+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 32906] Re: sudo fails if it cannot resolve the local hostname and no MTA is installed
** Changed in: sudo (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/32906 Title: sudo fails if it cannot resolve the local hostname and no MTA is installed Status in sudo: Fix Released Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Hardy: Fix Released Bug description: On behalf of Adam Williamson [*] adamw@ubuntu510:~$ sudo scp 192.168.2.7:/etc/hosts /etc adamw@ubuntu510:~$ sudo nano /etc/hosts sudo: unable to lookup ubuntu510 via gethostbyname() …yeah, sudo, it’s all very clever until someone loses an eye! I have a bunch of entries in /etc/hosts because of having four local systems plus a bunch of VMware machines etc. So now when I set up a new VMware machine I just copy the /etc/hosts from the real machine over to the VM then edit a couple of lines to match the VM, instead of re-editing it all from scratch. Only, as you can see, this utterly breaks Ubuntu…all I need to do to fix the sudo problem is edit /etc/hosts so 127.0.0.1 is ‘ubuntu510′ (the name of the VM) rather than ‘zen’ (the name of the real machine), but I can’t do it, because sudo doesn’t work… the only way out of this that I can see is single-user mode or the recovery console. Not too smart! Surely sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on? [*] Originally from http://www.happyassassin.net/2006/02/24/how-to-break-ubuntu-in-thirty-seconds/, If you consider that this is relevant and worth discussing, we can add Adam Williamson to the conversation. Otherwise, just mark it as invalid and forget it. TEST CASE: - This only works (i. e. fails) on a system where /usr/sbin/sendmail does NOT exist (standard Ubuntu installation) - open a terminal and do "sudo -i" to get a root shell; do "hostname foo" - open another terminal, and try "sudo ls". Hardy final will fail with "unable to resolve host foo" and not run the ls. - upgrade sudo to the hardy-proposed version and attempt the same. sudo should still complain, but run the ls command. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/32906/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Ok sounds good. Should I expect these to come through as an update through the Software Updater eventually? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: In Progress Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Ok, thanks for keeping me updated, let me know if there's anything I can do to help troubleshoot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Something I just noticed, if it means anything, is that I have a file in ~/.config/evolution/sources that seems to contain what would be my Nextcloud info, but it seems to be missing some information perhaps? I don't have a reference in front of me for what these normally look like. Contents pasted below [Data Source] DisplayName=leggett...@ambrose.leggett.dev Enabled=true Parent= [Authentication] Host= Method=none Port=0 ProxyUid=system-proxy RememberPassword=true User= CredentialName= IsExternal=true [Collection] BackendName=webdav CalendarEnabled=true ContactsEnabled=true Identity=leggettc18 MailEnabled=true AllowSourcesRename=false CalendarUrl= ContactsUrl= [GNOME Online Accounts] AccountId=account_1586225954_0 CalendarUrl=https://leggett...@ambrose.leggett.dev/remote.php/caldav/ ContactsUrl=https://leggett...@ambrose.leggett.dev/remote.php/carddav/ Name= Address= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Absolutely, I've attached a txt file with the contents of `journalctl -b 0`. For the record, my actions for these logs were: 1. Boot 2. Sign in 3. Launch Firefox and navigate to my Nextcloud instance 4. Generate an app specific password (I use two-factor) 5. Add the Nextcloud account in the Online Accounts settings page. 6. Open the calendar app to make sure it didn't miraculously work this time. Worth noting is that I have the exact same issue in two different installations of the same 20.04 daily iso, so its not an issue specific to this particular installation. Tomorrow I'll see if I can set up an Endeavor OS install in a VM to see if it happens on a different distro running Gnome 3.36. Also, just wanted to say this is a small bump in an otherwise stellar looking release. Appreciate all the work you guys do at Canonical. ** Attachment added: "results of `journalctl -b 0` after attempting to add nextcloud account and not having it show up in the calendar app." https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+attachment/5348302/+files/logs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: Incomplete Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
After running another apt update && apt upgrade this problem seems to have resolved itself. I hate mysteries :) ** Attachment added: "Non choppy sound. yay." https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347952/+files/Non%20choppy%20sound.%20yay. -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
** Attachment added: "Choppy sound with Gnome Sound Recorder" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+attachment/5347862/+files/Choppy%20sound%20with%20Gnome%20Sound%20Recorder -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1871137] Re: Recorded audio is super choppy with today's apt upgrade
Install log for today as per request of lotuspsychje@ on ubuntu+1 freenode channel: https://paste.ubuntu.com/p/sxYkf9KtnW/ -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1871137] [NEW] Recorded audio is super choppy with today's apt upgrade
Public bug reported: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Choppy audio WAV from latest 20.04" https://bugs.launchpad.net/bugs/1871137/+attachment/5347811/+files/choppyfocalfossaaudio.wav -- 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/1871137 Title: Recorded audio is super choppy with today's apt upgrade Status in pulseaudio package in Ubuntu: New Bug description: People reported choppy audio coming from me in my morning stand-up call. I thought it might be an issue with our chat system, so I tried recording a sound bite in Audacity both with and without my bluetooth headset. I got the same incredibly choppy sound in either case. I'll attach a clip to the bug if I can so you can see what I mean. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 Date: Mon Apr 6 11:07:37 2020 InstallationDate: Installed on 2020-01-09 (87 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-01-24 (73 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware17R5:pvr1.7.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871137/+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 1871019] [NEW] Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Public bug reported: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts package in Ubuntu: New Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1871019/+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 1869414] [NEW] Running applications always appear on the desktop
Public bug reported: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2019 dmi.bios.vendor: System76 dmi.bios.version: F42a Z5 dmi.board.asset.tag: Default string dmi.board.name: Thelio dmi.board.vendor: System76 dmi.board.version: thelio-r1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: thelio-r1 dmi.modalias: dmi:bvnSystem76:bvrF42aZ5:bd08/22/2019:svnSystem76:pnThelio:pvrthelio-r1:rvnSystem76:rnThelio:rvrthelio-r1:cvnSystem76:ct3:cvrthelio-r1: dmi.product.family: Default string dmi.product.name: Thelio dmi.product.sku: Default string dmi.product.version: thelio-r1 dmi.sys.vendor: System76 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 focal reproducible 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/1869414 Title: Running applications always appear on the desktop Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.04 No matter which virtual desktop is in focus, applications running on other virtual desktop are displayed even if minimized. This makes it impossible to interact with desktop icons without closing all running applications. It is not possible to interact with the application itself when it's displayed erroneously, unless you return to its original virtual desktop. I've reinstalled from two different daily images and have been able to reproduce the problem each time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 14:22:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1458:2311] InstallationDate: Installed on 2020-03-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) MachineType: System76 Thelio ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_4u488c@/vmlinuz-5.4.0-18-generic root=ZFS=rpool/ROOT/ubuntu_4u488c ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fre
[Touch-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Update: a kernel upgrade solved the mic white noise for me. I had been running a 5.0 kernel. Updating to a 5.4 kernel fixed it. -- 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/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1827440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.l
[Touch-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted
Tyler, did you ever find a solution to this? I'm having the same problem with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The only "solution" I've found is to turn off "internal mic boost" using alsa-mixer (hit F5 to show all channels, cursor all the way to the right) and keep the mic capture level below 20%. So it works, but far from ideal since the mic is low (but better than making the person on the other end of a call hearing a shitload of white noise that's produced otherwise). -- 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/1827440 Title: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hopefully all the necessary info is in the extra stuff that automatically got sent. Basically, I didn't do anything fancy, but audio recorded with my microphone (through Skype, and arecord in the Terminal) has tons of static and the voice is distorted or saturated. Booting this computer on Windows doesn't have issues, so that's why I don't think it's the computer, I think it's the OS. Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyler 1499 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 19:04:55 2019 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHS1TG00 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: tyler 1562 F...m pulseaudio /dev/snd/pcmC0D0p: tyler 1562 F...m pulseaudio /dev/snd/controlC0: tyler 1562 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-09 (113 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20KHS1TG00 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET62W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHS1TG00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:c
[Touch-packages] [Bug 1861043] [NEW] Xorg freeze
Public bug reported: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back." Also because I have to hard restart apport never get's called to show exactly why the system is hanging. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03: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 440.44 Sun Dec 8 03:38:56 UTC 2019 GCC version: gcc version 9.2.1 20200123 (Ubuntu 9.2.1-25ubuntu1) ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 27 15:13:07 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.44, 5.4.0-12-generic, x86_64: installed nvidia, 440.44, 5.4.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062b] Subsystem: Dell GM108M [GeForce 840M] [1028:062b] InstallationDate: Installed on 2020-01-14 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) MachineType: Dell Inc. Latitude E5450 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=37b7ed5e-16a1-4e03-ad70-e85dfec9bf53 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0MVKK7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/30/2015:svnDellInc.:pnLatitudeE5450:pvr:rvnDellInc.:rn0MVKK7:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.sku: 062B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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 focal freeze has-fix has-workaround 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/1861043 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: So under high load I can generally cause a freeze in Gnome/Ubuntu. This is somewhat expected and likely should be fixed by some sort of OOM killer. However that's only part of the problem. Virtual Consoles are disabled (`/etc/systemd/logind.conf` `NAutoVTs` by default) and I believe that too to be a bug. In the past I could have Switched VT's logged in and killed of a high memory/cpu process or two. Now I have to hard kill the box and risk loosing in progress work which is ungainly. If there's a worry about "what will new users do if they accidentally hit CTRL+ALT+F\d" maybe instead of disabling it we could change the default login message to have a "Don't know how you got here? Hit CTLR+ALT+F1 to go back
[Touch-packages] [Bug 463796] Re: Alsa doesn't detect external mic
Fix was apparently released, yet for me the problem arose first when I upgraded to 19.10. I now have no access to the microphone on my headset. -- 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/463796 Title: Alsa doesn't detect external mic Status in alsa-driver package in Ubuntu: Fix Released Bug description: I have a Logitech mini-jack headset with a mic. Sound playback works, but recording does not; it only works through the computer's built-in microphone. ProblemType: Bug Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: josh 2688 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0x9240 irq 16' Mixer name : 'IDT 92HD71B7X' Components : 'HDA:111d76b2,103c3600,00100302' Controls : 35 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0x9231 irq 19' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] CheckboxSubmission: 6bacad257d07e21537e077802a955e05 CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c Date: Thu Oct 29 17:31:38 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: fglrx Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/463796/+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 1858439] Re: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232]
This is not just a problem when I dock. In fact, even when I correct the problem by selecting the correct output device in sound settings, it reverts after a while back to the incorrect one (HDMI/Display port) -- 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/1858439 Title: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] Status in alsa-driver package in Ubuntu: New Bug description: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while UpgradeStatus: Upgraded to eoan on 2019-10-31 (66 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1858439/+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 1858439] [NEW] When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232]
Public bug reported: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while UpgradeStatus: Upgraded to eoan on 2019-10-31 (66 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while + When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] -- 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/1858439 Title: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] Status in alsa-driver package in Ubuntu: New Bug description: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driv
[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
Actually, it is not true that this is solved under 19.10. All that has happened is that the latency has shortened to 1-2 seconds. It is *still* the case that during that time, I cannot get the focus in any other window or do anything else in the operating system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this
[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
Yes, I have now very grudgingly upgraded to 19.10 and the problem seems to be resolved. This problem was new at some point in 19.04 (ie did not exist at first with 19.04) and I do not think pressuring eople to upgrade (so soon after a release) is a good solution. On the other hand, strangely, no one else has reported the bug. Thanks, Olivier! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.con
[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
This problem does not affect a brand new user if I create one. So it is maybe to do with having upgraded, and having old settings? How do I reset the relevant settings? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscription
[Touch-packages] [Bug 1773087] Re: Remove python3-apport as dependency of xserver-xorg
sordna, regarding your specific problem, please file a bug against apport via a terminal: ubuntu-bug apport In this new report, please copy/paste the reproduction steps, and result as per terminal command. -- 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/1773087 Title: Remove python3-apport as dependency of xserver-xorg Status in xorg package in Ubuntu: Invalid Bug description: Distro: Bionic Binary Package: xserver-xorg Version: 1:7.7+19ubuntu7 Hello! The package xserver-xorg depends on python3-apport. I don't want to use apport on my systems. Can the dependency be removed? Also, it doesn't work anyway. That's how I noticed that the package is installed: root@00debac04ddf:~# foo Traceback (most recent call last): File "/usr/bin/foo", line 3, in raise Exception Exception Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 145, in apport_excepthook os.O_WRONLY | os.O_CREAT | os.O_EXCL, 0o640), 'wb') as f: FileNotFoundError: [Errno 2] No such file or directory: '/var/crash/_usr_bin_foo.0.crash' Original exception was: Traceback (most recent call last): File "/usr/bin/foo", line 3, in raise Exception Exception Thanks Jörn Heissler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773087/+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 1847152] Re: printf escape sentences are insufficiently documented
No, I do not. I suggest a change in content because the current content is wrong. One correction though: the ‘printf’ library interface does recognise two escape sequences, namely ‘\%’ and ‘\\’. These two are supported by the ‘printf’ command, of course, but all other escape sequences are command-specific and should be documented somehow. Not all of them are documented on the info page, e.g. ‘\n’ is not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1847152 Title: printf escape sentences are insufficiently documented Status in coreutils package in Ubuntu: New Bug description: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1847152/+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 1847152] [NEW] printf escape sentences are insufficiently documented
Public bug reported: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1847152 Title: printf escape sentences are insufficiently documented Status in coreutils package in Ubuntu: New Bug description: The info page for ‘printf’ is misleading because the C ‘printf’ function does not interpret any escape sequences. So, interpreting this specification literally, all escape sequences are differences but not all of them are listed below. In particular, the sequence ‘\e’ is not listed. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 8.30-1ubuntu1 3) What you expected to happen ‘printf’ prints the FORMAT string, interpreting ‘\’ escapes as specified below and interpreting ‘%’ directives to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. 4) What happened instead ‘printf’ prints the FORMAT string, interpreting ‘%’ directives and ‘\’ escapes to format numeric and string arguments in a way that is mostly similar to the C ‘printf’ function. *Note ‘printf’ format directives: (libc)Output Conversion Syntax, for details. The differences are listed below. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: coreutils 8.30-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 7 23:24:39 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1847152/+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 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** No longer affects: mesa (Ubuntu) ** Project changed: mesa => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Unknown => New ** Changed in: mesa (Ubuntu) Remote watch: freedesktop.org Bugzilla #72877 => None ** Changed in: mesa (Ubuntu) Status: New => Triaged ** Description changed: - Hi all, + Upstream report: + https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in mesa package in Ubuntu: Triaged Bug description: Upstream report: https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this transla
[Touch-packages] [Bug 1833114] Re: print page dialog latency when trying to cancel or to save
** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1833114 Title: print page dialog latency when trying to cancel or to save Status in chromium-browser package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Since less than a month ago, using the print page dialog (which for me defaults to saving as PDF) is outlandishly slow. Once opened, if I try to close it (click cancel / press Esc) or to use it (click Save or press Enter), there is no visible response, and my system hangs for 10 seconds. After that though, the operation concludes successfully and things return to normal. This did not used to happen. Closing or submitting the print-to-PDF used to result in the pop-up window closing immediately and the browser regaining responsiveness. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: chromium-browser 74.0.3729.169-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-5: enabled: enabled dpms: On status: connected edid-base64: AP///wAEchAEyHEQUQsZAQSlRyh4PiVfqFRNnyUOT1O/74BxT4FAgYCBwIEAlQCzANHATdAAoPBwPoAwIDUAxY8hAAAaBHQAMPJwWoCwWIoAxY8hAAAa/QAdTB+gPAEKICAgICAg/ABCMzI2SEsKICAgICAgAQwCAxzhT5ACAwQFBgcBERITFBUWHyMJBweDAQAAAjqAGHE4LUBYLEUAxY8hAAAeAR2AGHEcFiBYLCUAxY8hAACeAR0AclHQHiBuKFUAxY8hAAAejArQiiDgLRAQPpYAxY8hAAAYVl4AoKCgKVAwIDUAxI8hAAAa modes: 3840x2160 3840x2160 2560x1440 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-DP-6: enabled: disabled dpms: On status: connected edid-base64: AP///wAQrAngTEFNMAkPAQPOKxt46gGVo1dMnCUSUFSlSwCBgHFPAQEBAQEBAQEBAQEBfC6QoGAaHkAwIDYAsg4RAAAa/wBUNjEzMDUzMjBNQUwK/QA4Sx5TDgAKICAgICAg/ABERUxMIDIwMDVGUFcKAAM= modes: 1680x1050 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card0-DP-7: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0TACYXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTQwSEFOMDEuMyAKAHo= modes: 1920x1080 Date: Mon Jun 17 14:03:12 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: EcryptfsInUse: Yes Env: 'None' 'None' InstallationDate: Installed on 2019-01-24 (144 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: Load-Avg-1min: 3.09 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: Upgraded to disco on 2019-05-29 (19 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1833114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.n
[Touch-packages] [Bug 1838802] [NEW] ca-certificates missing trusted entry from linuxfoundation
Public bug reported: source.codeaurora.org (linuxfoundation) changed their certificate on 30 JUL 2019. When cloning from codeaurora, you now get this error: $ git clone https://source.codeaurora.org/external/imx/libdrm-imx.git/ Cloning into 'libdrm-imx'... fatal: unable to access 'https://source.codeaurora.org/external/imx/libdrm-imx.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none I think this suggests that the issuing CA Authority is not trusted and included in ca-certificates.crt. I've confirmed this certificate validation issue on both ubuntu 16.04 and ubutnu 18.04. I've even upgraded and reinstalled the ca-certificates package and still get the same validation error. I assumed it might be a problem with my clock out of sync, so I synchronized my server time with chrony and the issue persists. I can add the certificate manually to my installation of git and get around the issue, but I suspect that this issue will impact anyone attempting to clone from the linux foundation git servers. I've attached the source.codeaurora.org certificate to this bug report. The certificate shows that the issueing authority is "Sectigo RSA Domain Validation Secure Server CA" ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Attachment added: "source.codeaurora.org.pem" https://bugs.launchpad.net/bugs/1838802/+attachment/5280552/+files/source.codeaurora.org.pem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1838802 Title: ca-certificates missing trusted entry from linuxfoundation Status in ca-certificates package in Ubuntu: New Bug description: source.codeaurora.org (linuxfoundation) changed their certificate on 30 JUL 2019. When cloning from codeaurora, you now get this error: $ git clone https://source.codeaurora.org/external/imx/libdrm-imx.git/ Cloning into 'libdrm-imx'... fatal: unable to access 'https://source.codeaurora.org/external/imx/libdrm-imx.git/': server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none I think this suggests that the issuing CA Authority is not trusted and included in ca-certificates.crt. I've confirmed this certificate validation issue on both ubuntu 16.04 and ubutnu 18.04. I've even upgraded and reinstalled the ca-certificates package and still get the same validation error. I assumed it might be a problem with my clock out of sync, so I synchronized my server time with chrony and the issue persists. I can add the certificate manually to my installation of git and get around the issue, but I suspect that this issue will impact anyone attempting to clone from the linux foundation git servers. I've attached the source.codeaurora.org certificate to this bug report. The certificate shows that the issueing authority is "Sectigo RSA Domain Validation Secure Server CA" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1838802/+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 1836120] [NEW] [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback problem - System sounds work, but no media sound
Public bug reported: The system sound effects are working properly on my Corsair Void RGB Pro usb wired headset, but I cannot listen to audio in videos on Youtube via Chrome or Firefox. I cannot seem to get sound working in other apps as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 18:23:16 2019 InstallationDate: Installed on 2019-07-09 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Hea successful Symptom_Card: Corsair VOID RGB USB Gaming Headset - Corsair VOID RGB USB Gaming Hea Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3P-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.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3P:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3P-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3P dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1836120 Title: [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback problem - System sounds work, but no media sound Status in alsa-driver package in Ubuntu: New Bug description: The system sound effects are working properly on my Corsair Void RGB Pro usb wired headset, but I cannot listen to audio in videos on Youtube via Chrome or Firefox. I cannot seem to get sound working in other apps as well. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 18:23:16 2019 InstallationDate: Installed on 2019-07-09 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Hea successful Symptom_Card: Corsair VOID RGB USB Gaming Headset - Corsair VOID RGB USB Gaming Hea Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: None of the above Title: [USB-Audio - Corsair VOID RGB USB Gaming Hea, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3P-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.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3P:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3P-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3P dmi.product.sku: Default string 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/1836120/+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 1829643] Re: 1 network printer + 3 configurations (copies) disappear
** Attachment removed: "20190519-0814-CEST-apport.cups.k1bxh64q.apport" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829643/+attachment/5264742/+files/20190519-0814-CEST-apport.cups.k1bxh64q.apport ** Changed in: cups (Ubuntu) Importance: Low => Medium ** Changed in: cups (Ubuntu) Status: Confirmed => New ** Tags added: regression-potential -- 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/1829643 Title: 1 network printer + 3 configurations (copies) disappear Status in cups package in Ubuntu: New Bug description: ###- ### NOTE English is not my native language, I do my best ... ###- Distribution is Lubuntu (Ubuntu-19.04). ###- ### NOTE by request ###- # cat /proc/version_signature Ubuntu 5.0.0-15.16-generic 5.0.6 # apt-cache policy cups cups: Installed: 2.2.10-4ubuntu1 Candidate: 2.2.10-4ubuntu1 Version table: *** 2.2.10-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.10-4 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages # lsb_release -rd Description:Ubuntu 19.04 Release:19.04 ###- ### NOTE starting point ###- My printing system for the last 12-15 years based on cups had/has the following setup: * 1 network laser printer "Brother MFC 9142CDN" * 3 "symbolic" printers which are copies of the former, configured to set defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and "labelprinter" (use of manual feed) The "Brother MFC 9142CDN" was instantly discovered and completely PPD configured and successfully tested with a fresh Lubuntu-19.04 install, last week. ###- ### NOTE by request: see attachment for "ubuntu-bug cups" output ###- ###- ### NOTE After first install and fresh configuration my printer setup looks as follows ###- # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O ###- ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot ###- # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print ###- ### NOTE strangely, this one also disappears after some minutes ###- LANG=en lpstat -s no system default destination lpstat: No destinations added. lpstat: No destinations added. ###- ### NOTE printers.conf / printers.conf.O - mind the sizes ### ### printers.conf: no printer definition, just standard comment "DO NOT EDIT ..." ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" description ### while the 3 other printers (monoprinter, colorprinter, labelprinter) are missing ###- # ls -l /etc/cups/printers.conf* -rw--- 1 root lp 111 Mai 19 08:00 printers.conf -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O ###- ### NOTE the PPDs are also lost at this time ###- # ls -l /etc/cups/ppd/ total 0 ###- ### NOTE after my fresh and working configuration, the PPDs looked like this ### ### Only the "Brother_MFC_9142CDN" survives a reboot though it also disappears later. ### Mind the permissions: 664 versus 640 ... don't know why ###- # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O ###- ### NOTE ### ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 copies, ### the DeviceURI is the same for all four. Only the UUID differs ###- UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:
[Touch-packages] [Bug 1829643] Re: 1 network printer + 3 configurations (copies) disappear
FrankStefani, could you please run an apport-collect only once more to gather debugging information against the package cups: apport-collect 1829643 ** Package changed: linux (Ubuntu) => cups (Ubuntu) ** 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/1829643 Title: 1 network printer + 3 configurations (copies) disappear Status in cups package in Ubuntu: Confirmed Bug description: ###- ### NOTE English is not my native language, I do my best ... ###- Distribution is Lubuntu (Ubuntu-19.04). ###- ### NOTE by request ###- # cat /proc/version_signature Ubuntu 5.0.0-15.16-generic 5.0.6 # apt-cache policy cups cups: Installed: 2.2.10-4ubuntu1 Candidate: 2.2.10-4ubuntu1 Version table: *** 2.2.10-4ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.2.10-4 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages # lsb_release -rd Description:Ubuntu 19.04 Release:19.04 ###- ### NOTE starting point ###- My printing system for the last 12-15 years based on cups had/has the following setup: * 1 network laser printer "Brother MFC 9142CDN" * 3 "symbolic" printers which are copies of the former, configured to set defaults for particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and "labelprinter" (use of manual feed) The "Brother MFC 9142CDN" was instantly discovered and completely PPD configured and successfully tested with a fresh Lubuntu-19.04 install, last week. ###- ### NOTE by request: see attachment for "ubuntu-bug cups" output ###- ###- ### NOTE After first install and fresh configuration my printer setup looks as follows ###- # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O ###- ### NOTE Only the first of these (Brother_MFC_9142CDN) survives a reboot ###- # lpstat -s device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print ###- ### NOTE strangely, this one also disappears after some minutes ###- LANG=en lpstat -s no system default destination lpstat: No destinations added. lpstat: No destinations added. ###- ### NOTE printers.conf / printers.conf.O - mind the sizes ### ### printers.conf: no printer definition, just standard comment "DO NOT EDIT ..." ### printers.conf.O: only the physical network printer "Brother_MFC_9142CDN" description ### while the 3 other printers (monoprinter, colorprinter, labelprinter) are missing ###- # ls -l /etc/cups/printers.conf* -rw--- 1 root lp 111 Mai 19 08:00 printers.conf -rw--- 1 root lp 923 Mai 19 07:55 printers.conf.O ###- ### NOTE the PPDs are also lost at this time ###- # ls -l /etc/cups/ppd/ total 0 ###- ### NOTE after my fresh and working configuration, the PPDs looked like this ### ### Only the "Brother_MFC_9142CDN" survives a reboot though it also disappears later. ### Mind the permissions: 664 versus 640 ... don't know why ###- # ls -l ppd/ total 96 -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd -rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O -rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd -rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O -rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd -rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O -rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd -rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O ###- ### NOTE ### ### Apart from the different settings in "/etc/cups/printers.conf" for my 3 copies, ### the DeviceURI is the same for all four. Only the UUID differs ###- UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62 DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/
[Touch-packages] [Bug 554172] Re: system services using "console output" not starting at boot
FrankStefani, given the scope of this closed report was fixed in Ubuntu 10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to do with your problem. However, regarding the problem you are experiencing, it is most helpful if you use the computer the problem is reproducible with and file a new report by running the following from a terminal: ubuntu-bug cups Also, please feel free to subscribe me to it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/554172 Title: system services using "console output" not starting at boot Status in linux package in Ubuntu: Invalid Status in upstart package in Ubuntu: Fix Released Status in linux source package in Lucid: Won't Fix Status in upstart source package in Lucid: Fix Released Status in linux source package in Maverick: Won't Fix Status in upstart source package in Maverick: Fix Released Bug description: Binary package hint: cups Cups is not loading on my machine at boot, must run sudo /etc/init.d/cups start to after booting to print. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cups 1.4.2-10 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 2 13:07:35 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Connection refused MachineType: Dell Inc. Studio XPS 1340 Papersize: letter PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono (recommended) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: cups dmi.bios.date: 09/08/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0Y279R dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.asset.tag: 1234567890 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Studio XPS 1340 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/554172/+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 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
Michael Neuffer, this report has been missing key information since 2014 -> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/comments/33 . Hence, could you please test http://cdimage.ubuntu.com/daily-live/current/ and if reproducible please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information: apport-collect 1268151 -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1827427] [NEW] DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows
Public bug reported: Steps to reproduce: boot into Windows, obtain DHCP IP. either hibernate PC or reboot then boot into Linux; a DHCP IP is not obtainable even if I power cycle my router. To obtain a DHCP IP in Linux on the PC, I must either fully shutdown Windows then cold boot into Linux, or manually reset the ethernet adapter with echo 1 > /sys/bus/pci/devices/:00:19.0/reset The connection then comes good. I can see various DHCPDISCOVER and network-related traffic in journalctl -f during the time the machine is attempting to set an address on the interface, periodically the "activation of network connection failed" error message displays. Other discussion online suggests setting a spoofed, different MAC on the interface I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce this over multiple boots. It has apparently been a longstanding bug, perhaps due to how Windows is setting some aspect of the ethernet controller for a WOL or other boot-related operation. Either way, it's entirely confusing. Perhaps resetting the adapter should occur if this situation arises, particularly in LiveUSB/LiveCD scenarios. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Thu May 2 22:06:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME lan1 cbe6c8b2-dab9-347f-8a1d-613294b87483 ethernet 1556833444 Thu May 2 21:44:04 2019 yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /etc/NetworkManager/system-connections/lan1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet disconnected limited limited /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 disconnected started limited enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1827427 Title: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows Status in network-manager package in Ubuntu: New Bug description: Steps to reproduce: boot into Windows, obtain DHCP IP. either hibernate PC or reboot then boot into Linux; a DHCP IP is not obtainable even if I power cycle my router. To obtain a DHCP IP in Linux on the PC, I must either fully shutdown Windows then cold boot into Linux, or manually reset the ethernet adapter with echo 1 > /sys/bus/pci/devices/:00:19.0/reset The connection then comes good. I can see various DHCPDISCOVER and network-related traffic in journalctl -f during the time the machine is attempting to set an address on the interface, periodically the "activation of network connection failed" error message displays. Other discussion online suggests setting a spoofed, different MAC on the interface I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce this over multiple boots. It has apparently been a longstanding bug, perhaps due to how Windows is setting some aspect of the ethernet controller for a WOL or other boot-related operation. Either way, it's entirely confusing. Perhaps resetting the adapter should occur if this situation arises, particularly in LiveUSB/LiveCD scenarios. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-mana
[Touch-packages] [Bug 1821505] Re: screen cannot be turned back on after some time of inactivity
Hark, thank you for reporting this and helping make Ubuntu better. 1) To confirm a regression, has this always been an issue since you installed "Ubuntu-Server 10.04 LTS" or is this something that started to happen after an update? 2) To clarify, did you personally test the WORKAROUNDs noted in the Bug Description, and confirm this works for your hardware? 2) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Tags added: latest-bios-1.18 ** Description changed: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. - When I restart the display manager via ssh with another computer, the - screen then comes to life again and I can log back in. + WORKAROUND: Type in a terminal: + xset -display :0.0 dpms force off - There is no problem waking the screen when I type "xset -display :0.0 - dpms force off" in a terminal. Moreover typing gnome-screensaver-command - -a in a terminal turns my screen off and after typing this line, the - screen can be woken up by moving the mouse or by hitting a key. + WORKAROUND: Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: + gnome-screensaver-command -a + + WORKAROUND: When I restart the display manager via ssh with another + computer, the screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.18 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: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) -Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] + Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) + Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputLogitech USB Receiver KEYBOARD, id 8 - inputLogitech USB Receiver KEYBOARD, id 9 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputLogitech USB Receiver KEYBOARD, id 8
[Touch-packages] [Bug 1820303] [NEW] Ubuntu 18.04 LTS
Public bug reported: Failure to display prior desktop login GUI (Cinnamon). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 15 11:46:27 2019 DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7] InstallationDate: Installed on 2019-03-11 (4 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK COMPUTER INC. X55U ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago) dmi.bios.date: 08/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55U.423 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55U dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X55U dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Fri Mar 15 11:19:59 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1820303 Title: Ubuntu 18.04 LTS Status in xorg package in Ubuntu: New Bug description: Failure to display prior desktop login GUI (Cinnamon). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 15 11:46:27 2019 DistUpgraded: 2019-03-15 10:30:23,145 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Wrestler [Radeon HD 7340] [1043:14e7] InstallationDate: Installed on 2019-03-11 (4 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: ASUSTeK COMPUTER INC. X55U ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-03-15 (0 days ago) dmi.bios.date: 08/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X55U.423 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X55U dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.ta
Re: [Touch-packages] [Bug 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Hi sir I'm not sure about any of that, but if you click the drop down button in the top right then click the button between the wrench/screwdriver and the lock button and that middle button is the one that stops the obnoxious screen rotation. On Tue, Mar 12, 2019 at 9:56 AM Antonello wrote: > Problem in Elitebook 840 g2 solved by removing/purging iio sensor > package after the first installation (Debian) updated to the testing > version . The problem affected screen and touchpad/mouse. It seems to me > that it is a unnecessary package for laptop with no position sensors is > it not? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1726160 > > Title: > On login, display rotates to wrong orientation [HP Pavilion] > > Status in IIO Sensor Proxy: > Fix Released > Status in systemd: > New > Status in iio-sensor-proxy package in Ubuntu: > Invalid > Status in linux package in Ubuntu: > Confirmed > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I'm using a laptop, and on 17.04 the display always showed correctly, > but after upgrading to 17.10, when I log in the display rotates to > the right (portrait), and I have to open a terminal and run 'xrandr -o > 1' to get it back to the correct (landscape) orientation. In previous > versions 'xrandr -o 0' was landscape, and '1' was portrait the other > way. > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: xorg 1:7.7+19ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > NonfreeKernelModules: nvidia_uvm 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 340.104 Thu Sep 14 > 17:13:13 PDT 2017 >GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) > .tmp.unity_support_test.0: > > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sun Oct 22 15:15:08 2017 > DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, > re-reading > DistroCodename: artful > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed >bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed >nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed >nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) > (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] > [103c:363c] > InstallationDate: Installed on 2017-01-11 (284 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > LightdmDisplayLog: (II) Server terminated successfully (0). Closing log > file. > MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) > dmi.bios.date: 10/05/2010 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: F.1D > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 363C > dmi.board.vendor: Hewlett-Packard > dmi.board.version: 32.25 > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: N/A > dmi.modalias: > dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: > dmi.product.family: 103C_5335KV > dmi.product.name: HP Pavilion dv7 Notebook PC > dmi.product.version: 039D222412102 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 > version.libdrm2: libdrm2 2.4.83-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20170309-0ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+subscriptions >
[Touch-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
Or as one user posted, the official AMDGPU Pro package, which also enables 10bpc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
This bug can only occur if 10bpc is enabled. There is no other possibility. It is clearly a colorspace mismatch between VAAPI and the decode target surface. If disabling 10bpc happens in Ubuntu Mesa packages, then it is clearly someone using unofficial package builds of Mesa which have 10bpc enabled on supporting hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
As already stated above, the correct workaround, for now, is to configure a drirc (probably in a conf.d directory, so it doesn't clash with other settings files) so as to disable 10 bit per channel support for Totem. The same had to be done with Chromium-vaapi, as it also happens with that solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1816811] [NEW] iptables package doesn't flush table on removal of package
Public bug reported: The iptables package isn't flushing all tables on removal of the package and the tables still exist until reboot. Intended behavior should be to flush all tables via a dpkg pre-removal script. I'm not sure of any use case where the intended behavior would be to keep the current rules in place but not have iptables available. root@ip-10-224-187-201:/home/cwarner# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere DROP all -- 127.0.0.0/8 anywhere ACCEPT tcp -- anywhere anywhere state ESTABLISHED ACCEPT udp -- anywhere anywhere state ESTABLISHED ACCEPT icmp -- anywhere anywhere state ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:ssh state NEW ACCEPT udp -- anywhere anywhere udp dpt:bootpc state NEW ACCEPT udp -- anywhere anywhere udp dpt:ntp state NEW ACCEPT udp -- anywhere anywhere udp dpt:323 state NEW Chain FORWARD (policy DROP) target prot opt source destination Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere state NEW,ESTABLISHED ACCEPT udp -- anywhere anywhere state NEW,ESTABLISHED ACCEPT icmp -- anywhere anywhere state NEW,ESTABLISHED root@ip-10-224-187-201:/home/cwarner# apt remove iptables Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: iptables 0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded. After this operation, 1,663 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 91459 files and directories currently installed.) Removing iptables (1.6.0-2ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for man-db (2.7.5-1) ... *Rules are still in place* root@ip-10-224-187-201:/home/cwarner# apt install iptables Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: iptables 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 266 kB of archives. After this operation, 1,663 kB of additional disk space will be used. Get:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 iptables amd64 1.6.0-2ubuntu3 [266 kB] Fetched 266 kB in 0s (7,629 kB/s) Selecting previously unselected package iptables. (Reading database ... 91286 files and directories currently installed.) Preparing to unpack .../iptables_1.6.0-2ubuntu3_amd64.deb ... Unpacking iptables (1.6.0-2ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for man-db (2.7.5-1) ... Setting up iptables (1.6.0-2ubuntu3) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... root@ip-10-224-187-201:/home/cwarner# iptables -L Chain INPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere DROP all -- 127.0.0.0/8 anywhere ACCEPT tcp -- anywhere anywhere state ESTABLISHED ACCEPT udp -- anywhere anywhere state ESTABLISHED ACCEPT icmp -- anywhere anywhere state ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:ssh state NEW ACCEPT udp -- anywhere anywhere udp dpt:bootpc state NEW ACCEPT udp -- anywhere anywhere udp dpt:ntp state NEW ACCEPT udp -- anywhere anywhere udp dpt:323 state NEW Chain FORWARD (policy DROP) target prot opt source destination Chain OUTPUT (policy DROP) target prot opt source destination ACCEPT all -- anywhere anywhere ACCEPT tcp -- anywhere anywhere state NEW,ESTABLISHED ACCEPT udp -- anywhere anywhere state NEW,ESTABLISHED ACCEPT icmp -- anywhere anywhere state NEW,ESTABLISHED Same rules, still in place. ** Affects: iptables (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1816811 Title: iptables package doesn't flush table on removal of package Status in iptables package in Ubuntu: New Bug description: The iptables package isn't flushing all tables on removal of the package and the tables still exist until reboot. Intended behavior sho
[Touch-packages] [Bug 1788018] Re: udevd keeps binding and unbinding some usb device und uses all cpu
Marko Muehlberg (markom2), would you be able to confirm the commit from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 is the root cause for your issue by testing a revert of it following https://wiki.ubuntu.com/Kernel/KernelBisection ? ** Description changed: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. - now I'm running ubuntu desktop from a usb key and it's still the same + now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.624606] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.634706] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) ... + WORKAROUND: Remove file: + /lib/udev/rules.d/97-hid2hci.rules + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CustomUdevRuleFiles: 70-snap.core.rules Date: Mon Aug 20 18:54:48 2018 ExecutablePath: /lib/systemd/systemd-udevd LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Vostro 3300 ProcEnviron: - LANG=C.UTF-8 - PATH=(custom, no user) + LANG=C.UTF-8 + PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 07JC8T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/10/2010:svnDellInc.:pnVostro3300:pvrNotSpecified:rvnDellInc.:rn07JC8T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3300 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Tags added: bios-outdated-a12 regression-release ** This bug is no longer a duplicate of bug 1759836 systemd-udevd consumes 100% of CPU ** No longer affects: systemd (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1788018 Title: udevd keeps binding and unbinding some usb device und uses all cpu Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: It first appeared when I upgraded ubuntu studio to 18.04 udevd started to use all available cpu. now I'm running ubuntu desktop from a usb key and it's still the same udevadm monitor returns: KERNEL[2512.539491] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.540201] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566574] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.566866] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.567499] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594050] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.594310] unbind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) UDEV [2512.596510] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERNEL[2512.620736] bind /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.0 (usb) KERN
[Touch-packages] [Bug 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
It appears it's still there, but only accessible to project members. Which also excludes me. -- 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Confirmed Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+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 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)
Hmm, I did notice something looked a bit weird up there. But now that you mention it I do see the same issue on my thing too (see screenshot). ** Attachment added: "Screenshot from 2019-01-12 10-43-12.png" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304/+attachment/5228723/+files/Screenshot%20from%202019-01-12%2010-43-12.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1765304 Title: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused) Status in gnome-shell package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in ibus source package in Cosmic: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/391 --- tl;dr: starting in Ubuntu 18.04, "ibus" seems to lower and raise Firefox, whenever the user tries to focus an field on a web page. This is not a regression in Firefox, as the same Firefox version runs just fine in Ubuntu 17.10 -- it seems to be a bug in ibus, because it only happens (in 18.04) when the environmental variable GTK_IM_MODULE is at its default value (which is "ibus"). It had this same value in 17.10 but the bug didn't happen there; hence, I'm guessing there was a change in ibus (or a related package) that caused this breakage / lowering+raising. This is pretty bad, because in some cases, the focus-loss can mean users are simply unable to fill in password fields that previously were working fine. (see "ACTUAL RESULTS" below) STEPS TO REPRODUCE #1, via "BitWarden" Firefox extension: = 1. Start Firefox. (fresh profile if you like) 2. Install BitWarden from https://addons.mozilla.org/en-US/firefox/addon/bitwarden-password-manager/ 3. Click the BitWarden toolbar icon to spawn a menu-pane. 4. Click "Log in" at the bottom of that pane. 5. Click the "Master Password" field. ACTUAL RESULTS: The menu pane disappears as soon as the Master Password field receives focus. EXPECTED RESULTS: I should be able to type in a password; pane shouldn't disappear. STEPS TO REPRODUCE #2, via Reddit: = 1. Visit https://www.reddit.com/r/firefox/ (or any reddit page) 2. Click "Log in or sign up in seconds" at the extreme upper right of the page. (click the "Log in" part of that sentence) 3. Try to click the password field (or "tab" into it) and type in some text. ACTUAL RESULTS: Try as you might, the password field never receives focus. EXPECTED RESULTS: Password field should accept focus & let me type text into it. If I run firefox from the command line with env var GTK_IM_MODULE="", then I get "expected results". But with the default value of that env var, I get "actual results" (broken behavior, unable to enter passwords). I initially reported this in Firefox, here: https://bugzilla.mozilla.org/show_bug.cgi?id=1451466 (with a few dependent bugs for the usage-specific STR quoted above). But I think it's a bug in ibus, hence filing here now. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 23:22:05 2018 InstallationDate: Installed on 2018-04-17 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180416) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765304/+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 1726160] Re: On login, display rotates to wrong orientation [HP Pavilion]
Hey all, there is so much technical jargon here and on that github page. I have an HP Pavilion so I'm trying to remove that iio sensor-proxy, but I'm a bit confused. Where should I be looking on that github page for directions to remove the iio sensor-proxy? Thanks! -- 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/1726160 Title: On login, display rotates to wrong orientation [HP Pavilion] Status in IIO Sensor Proxy: Fix Released Status in systemd: New Status in iio-sensor-proxy package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm 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 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/iio-sensor-proxy/+bug/1726160/+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 1801540] Re: Microphone distorted sound on ALC892
Following up that I'm experiencing the same issue on an MSI B450 AM4 motherboard with the same realtek chipset. -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 846873] Re: Certain text invisible in attached PDF file
** Description changed: + Upstream reports: + https://bugzilla.gnome.org/show_bug.cgi?id=741681 + https://gitlab.freedesktop.org/poppler/poppler/issues/153 + 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected via https://launchpadlibrarian.net/79580879/ORelly-Running%20Linux%204th%20Edition.pdf is when one goes to page 58 of the book, at the bottom it shows the entire command, as it does in Adobe Reader: # fdisk /dev/hda 4) What happens instead is it only shows: # WORKAROUND: Open with Chromium's built-in PDF viewer: apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Sep 11 12:21:58 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) KernLog: Sep 11 10:06:44 mars kernel: [345609.072499] type=1400 audit(1315721204.184:23): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince" pid=27132 comm="apparmor_parser" Sep 11 10:06:44 mars kernel: [345609.074807] type=1400 audit(1315721204.184:24): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince-previewer" pid=27132 comm="apparmor_parser" Sep 11 10:06:44 mars kernel: [345609.076412] type=1400 audit(1315721204.184:25): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince-thumbnailer" pid=27132 comm="apparmor_parser" ProcEnviron: LANGUAGE=ru:en LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature_: Ubuntu 2.6.38-11.48-generic 2.6.38.8 SourcePackage: evince UpgradeStatus: Upgraded to natty on 2011-04-15 (148 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/846873 Title: Certain text invisible in attached PDF file Status in poppler package in Ubuntu: Triaged Bug description: Upstream reports: https://bugzilla.gnome.org/show_bug.cgi?id=741681 https://gitlab.freedesktop.org/poppler/poppler/issues/153 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected via https://launchpadlibrarian.net/79580879/ORelly-Running%20Linux%204th%20Edition.pdf is when one goes to page 58 of the book, at the bottom it shows the entire command, as it does in Adobe Reader: # fdisk /dev/hda 4) What happens instead is it only shows: # WORKAROUND: Open with Chromium's built-in PDF viewer: apt-cache policy chromium-browser chromium-browser: Installed: 39.0.2171.65-0ubuntu0.14.04.1.1064 Candidate: 39.0.2171.65-0ubuntu0.14.04.1.1064 Version table: *** 39.0.2171.65-0ubuntu0.14.04.1.1064 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/universe amd64 Packages 100 /var/lib/dpkg/status 34.0.1847.116-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Sep 11 12:21:58 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) KernLog: Sep 11 10:06:44 mars kernel: [345609.072499] type=1400 audit(1315721204.184:23): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince" pid=27132 comm="apparmor_parser" Sep 11 10:06:44 mars kernel: [345609.074807] type=1400 audit(1315721204.184:24): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince-previ
[Touch-packages] [Bug 1554471] Re: Mouse not working
As per https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/comments/9 . ** Changed in: xorg (Ubuntu) Status: Triaged => Invalid -- 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/1554471 Title: Mouse not working Status in xorg package in Ubuntu: Invalid Bug description: I have a Cougar 450M gaming mouse. I am dual booting between Windows 10 and Xubuntu. The mouse works perfectly in Windows but fails dismally in any flavour of Ubuntu (tried Ubuntu, Lubuntu and Xubuntu) including during the OS installation phase. On very rare occasion it will work when I boot into Ubuntu, but 9 out of 10 times the only functions available are the mouse buttons and scroll wheel. There is also a DPI adjustment button on the 450M which cycles through the various available settings and changes colour based on the current DPI setting. I have noted that if you press the button once, the button changes colour as expected, but if you continue to press the button, nothing happens. It seems to freeze on that setting. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 8 10:52:02 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2730] InstallationDate: Installed on 2016-03-03 (4 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Mar 8 10:48:41 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
Adding a comment to indicate that this is a problem with the 10bpc support which is enabled in Radeon graphics. I am unsure if it is enabled in Intel's drivers, so that would explain why it does not occur there. Either VA-API is outputting wrong, the client library is outputting wrong, or all the player applications are wrong. Something appears to be matching the buffers to each other without a conversion, simply because both RGBA32 and RGBA10-10-10-2 have the same number of bytes per pixel, but clearly completely different structure. A workaround is to add the following to the //driconf/device section of /etc/drirc: Clearly, this workaround should not be the only way, since someone in the processing chain clearly wants 10bpc support, and some applications can benefit from it, somehow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1623666] Re: iOS device contents not displayed in Ubuntu
Yes, but this does not grant transparent access to the Documents folders of installed applications. Pairing and libimobiledevice are still needed for that. -- 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/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Actually, for the Bose QC35 II, "Headset" is not missing. See below: Device 2C:41:A1:80:A1:C4 (public) Name: Christopher's Bose QC35 II Alias: Christopher's Bose QC35 II Class: 0x00240418 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Serial Port (1101--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351) UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15) Modalias: bluetooth:v009Ep4020d0251 -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1796614] [NEW] Ubuntu 18.10 - X fails to start on login
Public bug reported: Running startx starts X just fine, but at login I just get a blank screen with a blinking cursor. If I hit Alt+F I can get a console which allows me to login and run 'startx' at which point Gnome starts normally after entering my keychain unlock password. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Oct 7 22:59:13 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Dell Device [1028:0877] NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877] InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=c3d3798c-6179-472a-ba82-55ef94f4d382 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2018 dmi.bios.vendor: Alienware dmi.bios.version: 1.5.0 dmi.board.name: Alienware 17 R5 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.5.0:bd08/10/2018:svnAlienware:pnAlienware17R5:pvr1.5.0:rvnAlienware:rnAlienware17R5:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 17 R5 dmi.product.sku: 0877 dmi.product.version: 1.5.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic crash 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/1796614 Title: Ubuntu 18.10 - X fails to start on login Status in xorg package in Ubuntu: New Bug description: Running startx starts X just fine, but at login I just get a blank screen with a blinking cursor. If I hit Alt+F I can get a console which allows me to login and run 'startx' at which point Gnome starts normally after entering my keychain unlock password. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Oct 7 22:59:13 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Dell Device [1028:0877] NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP104M [GeForce GTX 1070 Mobile] [1028:0877] InstallationDate: Installed on 2018-10-07 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b8c Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 187c:0550 Alienware Corporation Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware Alienware 17 R5 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vml
[Touch-packages] [Bug 1610591] Re: Video acceleration regression for Radeon Xpress 200M (r300) in xorg-lts-xenial & xorg-lts-wily
As per https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1610591/comments/53 . ** No longer affects: xserver-xorg-video-ati (Ubuntu) ** Project changed: xserver-xorg-driver-ati => xserver-xorg-driver-ati (Ubuntu) ** Changed in: xserver-xorg-driver-ati (Ubuntu) Importance: Unknown => Undecided ** Changed in: xserver-xorg-driver-ati (Ubuntu) Status: Unknown => New ** Changed in: xserver-xorg-driver-ati (Ubuntu) Remote watch: freedesktop.org Bugzilla #97228 => None ** No longer affects: xserver-xorg-driver-ati (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1610591 Title: Video acceleration regression for Radeon Xpress 200M (r300) in xorg- lts-xenial & xorg-lts-wily Status in mesa package in Ubuntu: Invalid Bug description: After updating the Ubuntu HWE stack in 14.04 to Xenial (kernel 4.4 and xserver-xorg-video-radeon-lts-xenial), system boots up fine and responsively, but screen is laggy; there is a tremendous performance regression in comparison to xorg-lts-vivid. Lots of video tearing that did not occur when using xserver-xorg-video-radeon-lts-vivid. System is an older Pentium laptop (Packard Bell EasyNote) with a Radeon Xpress 200M chip (r300 driver). Video acceleration was working with DRI2 under the Vivid stack (kernel 3.19-64-lowlatency + xserver-xorg-video-radeon-lts-vivid). I also tried upgrading to the Wily kernel (4.2.0-lowlatency), and video acceleration works fine with the Vivid xorg. I reported this in launchpad previously, and it was dismissed as "invalid" since Wily is EOL. The problem, however, persists in the Xenial stack, so I'm reporting it here. Attached are the respective Xorg.0 logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1610591/+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 1791559] [NEW] Spurious reboot notifications caused by libssl upgrades.
Public bug reported: Upon installing libssl:i386 on Ubuntu LTS 18.04.1 Desktop, I am advised that I need to perform a reboot. I see a single process in my system using a no-longer-existing copy of libssl.so.1.0.0, but I can easily restart that process. Even if this were Server, I could easily just restart the sshd process, from its console if necessary. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1791559 Title: Spurious reboot notifications caused by libssl upgrades. Status in openssl package in Ubuntu: New Bug description: Upon installing libssl:i386 on Ubuntu LTS 18.04.1 Desktop, I am advised that I need to perform a reboot. I see a single process in my system using a no-longer-existing copy of libssl.so.1.0.0, but I can easily restart that process. Even if this were Server, I could easily just restart the sshd process, from its console if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1791559/+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 1553669] Re: Annoying "call from" message when connecting Bose devices
I seems that HSP/HFP doesn't work at all on 18.04. I've tried a variety of different Pulseaudio modules/settings, and also ofono. @vanvugt do you know if a different issue tracks that? -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I only thought to mention the PPA to indicate that the bug still occurs even in fairly bleeding edge Mesa code. I also still think it's either something wrong with gstreamer-vaapi, or something that gstreamer-vaapi is doing different from what mpv does for the same exact video. It should probably be reported to upstream Mesa, just in case it really is their bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
Freedesktop tells me it's a downstream Debian script file. https://gitlab.freedesktop.org/xorg/meta/issues/6 -- 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Incomplete Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
** Attachment added: "For reference, the same video in Totem." https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181989/+files/Screenshot_20180828_205430.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
** Attachment added: "And here's a screen shot of mpv with vaapi, also playing correctly." https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181988/+files/Screenshot_20180828_204952.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I have tested on my Radeon RX480, also AMDGPU drivers, git snapshot from 20180829 from Padoka PPA, and this bug occurs with Totem as well. It should also be noted that the bug does not occur with mpv, either with vdpau or vaapi. ** Attachment added: "Screen shot of mpv plus vdpau and terminal output" https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181987/+files/Screenshot_20180828_204917.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
** Patch added: "Patch to fix ssh-agent startup script" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+attachment/5181938/+files/90x11-common_ssh-agent.patch -- 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: New Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+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 1789523] [NEW] The ssh-agent launcher script fails to relaunch ssh-agent
Public bug reported: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: New Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(