[Touch-packages] [Bug 1940712] [NEW] binutils-common contains several zero-byte manpages
Public bug reported: binutils-common 2.37-1ubuntu1 contains several zero-byte manpages (those showing up with 20 bytes when packed with gzip): $ dpkg-query -L binutils-common | grep /usr/share/man/man1/ | xargs ls -Sl -rw-r--r-- 1 root root 6707 Jul 19 08:20 /usr/share/man/man1/ld.gold.1.gz -rw-r--r-- 1 root root 622 Jul 19 08:20 /usr/share/man/man1/dwp.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/addr2line.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ar.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/as.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/c++filt.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/elfedit.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/gprof.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ld.bfd.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/nm.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/objcopy.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/objdump.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ranlib.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/readelf.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/size.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/strings.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/strip.1.gz lrwxrwxrwx 1 root root 12 Jul 19 08:20 /usr/share/man/man1/gold.1.gz -> ld.gold.1.gz lrwxrwxrwx 1 root root 11 Jul 19 08:20 /usr/share/man/man1/ld.1.gz -> ld.bfd.1.gz ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: binutils-common 2.37-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 20 21:15:08 2021 Dependencies: InstallationDate: Installed on 2016-11-26 (1728 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RebootRequiredPkgs: linux-image-5.13.0-14-generic linux-base SourcePackage: binutils UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago) ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1940712 Title: binutils-common contains several zero-byte manpages Status in binutils package in Ubuntu: New Bug description: binutils-common 2.37-1ubuntu1 contains several zero-byte manpages (those showing up with 20 bytes when packed with gzip): $ dpkg-query -L binutils-common | grep /usr/share/man/man1/ | xargs ls -Sl -rw-r--r-- 1 root root 6707 Jul 19 08:20 /usr/share/man/man1/ld.gold.1.gz -rw-r--r-- 1 root root 622 Jul 19 08:20 /usr/share/man/man1/dwp.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/addr2line.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ar.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/as.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/c++filt.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/elfedit.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/gprof.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ld.bfd.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/nm.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/objcopy.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/objdump.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/ranlib.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/readelf.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/size.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/strings.1.gz -rw-r--r-- 1 root root 20 Jul 19 08:20 /usr/share/man/man1/strip.1.gz lrwxrwxrwx 1 root root 12 Jul 19 08:20 /usr/share/man/man1/gold.1.gz -> ld.gold.1.gz lrwxrwxrwx 1 root root 11 Jul 19 08:20 /usr/share/man/man1/ld.1.gz -> ld.bfd.1.gz ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: binutils-common 2.37-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 20 21:15:08 2021 Dependencies: InstallationDate: Installed on 2016-11-26 (1728 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RebootRequiredPkgs: linux-image-5.13.0-14-generic linux-base SourcePackage: binutils UpgradeStatus
[Touch-packages] [Bug 1944951] [NEW] delayed display update / konsole artifacts
Public bug reported: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu ** Attachment added: "screenshot-konsole-artifacts.jpg" https://bugs.launchpad.net/bugs/1944951/+attachment/5527627/+files/screenshot-konsole-artifacts.jpg -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: New Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neithe
[Touch-packages] [Bug 1944951] Re: delayed display update / konsole artifacts
I went back to konsole 20.04.0 (built from upstream sources) and still see these artifacts. Consequently, something else in the xorg/KDE software stack must be responsible; I'm not sure how to proceed with debugging, though. -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: New Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+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 1944951] Re: delayed display update / konsole artifacts
Additional notes: - Nice reproducer: rsync --progress (the progress output is constantly littered with artifacts) - Artifacts vanish (temporarily) when I press e.g. the ALT key. -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: New Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+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 1944951] Re: delayed display update / konsole artifacts
Update: This isn't a konsole-only issue. I'm seeing this in LibreOffice Writer as well. -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: New Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+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 1944951] Re: delayed display update / konsole artifacts
"Fixed" by completely clearing ~/.config/ . -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: New Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+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 1944951] Re: delayed display update / konsole artifacts
Yes! The artifacts reappear when I hit Shift-Alt-F12. Good catch! -- 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/1944951 Title: delayed display update / konsole artifacts Status in xorg package in Ubuntu: Confirmed Bug description: Since one of the recent Impish updates, konsole shows artifacts and reacts slowly. In fact, it looks like screen updates are pipelined on pixel-group granularity somehow, and the pipeline isn't drained completely: When more text goes to the terminal (e.g., I type something), existing artifacts vanish, but new ones (in the new text) appear. Unfortunately, I don't see any of the previous konsole .deb releases (e.g. 4:21.08.1-1 or 4:21.08.0-1) on the Ubuntu mirrors, so I cannot go back and simply check whether the newest konsole updates are the culprit. I'm actually not sure whether konsole is responsible at all, I originally intended to file against xorg; however, I see those artifacts in neither xterm nor gnome-terminal. Find attached a screenshot (taken with an external camera; these artifacts cannot be recorded using a screenshot tool such as imagemagick's "import") where I ran "ls" in /tmp, and cleared the terminal with ^L afterwards. The screen is still littered with remains of the "ls" output. It took a few tries to get artifacts this pronounced, though; usually they only concern small parts of the terminal. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Sep 24 08:09:18 2021 DistUpgraded: 2021-08-08 15:09:23,066 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:5050] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:5050] InstallationDate: Installed on 2016-11-26 (1762 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root resume=/dev/mapper/vgubuntu-swap nouveau.runpm=0 mitigations=off i915.i915_enable_fbc=0 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-08-08 (46 days ago) dmi.bios.date: 10/24/2019 dmi.bios.release: 2.30 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET90W (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrR07ET90W(2.30):bd10/24/2019:br2.30:efr1.5:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:skuLENOVO_MT_20FX_BU_Think_FM_ThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.1-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1944951/+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 1871710] [NEW] WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
Public bug reported:
When I create a shared WiFi ("hotspot") in the "Connections - System
Settings Module" with enabled WPA/WPA2 security, I cannot get Windows 10
clients to connect. Android 10 connects to this shared WiFi without
problems. Using the "Hotspot" button behind the system-tray network
icon works with Windows 10 clients (but creates an open/unencrypted
WiFi).
STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz"). Mode:
"Access Point".
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.
OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build
18363.418) asks for an eight-digit PIN instead of a password, unlike for other
WiFis. It is, however, also possible to click a link below and enter the
previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network
("Keine Verbindung mit diesem Netzwerk möglich"). This is reproducible with
different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without
problems.
EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10
does, or just as Windows 10 does to the unencrypted AP.
SOFTWARE/OS VERSIONS
Windows: Windows 10 Education, 1909, Build 18363.418
macOS:
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.4 (4:5.18.4.1-0ubuntu1)
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
I haven't tried this with earlier Kubuntu versions, but got one report
that this bug cannot be reproduced with Ubuntu 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 8 22:35:27 2020
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-11-26 (1229 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IpRoute:
default via 192.168.178.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.178.0/24 dev wlp3s0 proto kernel scope link src 192.168.178.69 metric
600
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-03-06 (33 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-11-20T11:33:29
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled disabled
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Bug watch added: KDE Bug Tracking System #419745
https://bugs.kde.org/show_bug.cgi?id=419745
--
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/1871710
Title:
WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows
10 client
Status in network-manager package in Ubuntu:
New
Bug description:
When I create a shared WiFi ("hotspot") in the "Connections - System
Settings Module" with enabled WPA/WPA2 security, I cannot get Windows
10 clients to connect. Android 10 connects to this shared WiFi
without problems. Using the "Hotspot" button behind the system-tray
network icon works with Windows 10 clients (but creates an
open/unencrypted WiFi).
STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz"). Mode:
"Access Point".
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.
OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build
18363.418) asks for an eight-digit PIN instead of a password, unlike for other
WiFis. It is, however, also possible to click a link below and enter the
previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network
("Keine Verbindung mit diesem Netzwerk möglich"). This is reproducible with
different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without
problems.
EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10
does, or just as Window
[Touch-packages] [Bug 1871710] Re: WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
KDE bug report: https://bugs.kde.org/show_bug.cgi?id=419745
--
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/1871710
Title:
WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows
10 client
Status in network-manager package in Ubuntu:
New
Bug description:
When I create a shared WiFi ("hotspot") in the "Connections - System
Settings Module" with enabled WPA/WPA2 security, I cannot get Windows
10 clients to connect. Android 10 connects to this shared WiFi
without problems. Using the "Hotspot" button behind the system-tray
network icon works with Windows 10 clients (but creates an
open/unencrypted WiFi).
STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz"). Mode:
"Access Point".
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.
OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build
18363.418) asks for an eight-digit PIN instead of a password, unlike for other
WiFis. It is, however, also possible to click a link below and enter the
previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network
("Keine Verbindung mit diesem Netzwerk möglich"). This is reproducible with
different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without
problems.
EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10
does, or just as Windows 10 does to the unencrypted AP.
SOFTWARE/OS VERSIONS
Windows: Windows 10 Education, 1909, Build 18363.418
macOS:
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.4 (4:5.18.4.1-0ubuntu1)
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
I haven't tried this with earlier Kubuntu versions, but got one report
that this bug cannot be reproduced with Ubuntu 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 8 22:35:27 2020
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-11-26 (1229 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IpRoute:
default via 192.168.178.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.178.0/24 dev wlp3s0 proto kernel scope link src 192.168.178.69
metric 600
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-03-06 (33 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-11-20T11:33:29
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871710/+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 1871710] Re: WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
In my KDE bug report (https://bugs.kde.org/show_bug.cgi?id=419745) I
filed against systemsettings/kcm_networkmanagement; I'm actually not
sure whether network-manager was the right package to file against, are
you?
--
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/1871710
Title:
WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows
10 client
Status in network-manager package in Ubuntu:
New
Bug description:
When I create a shared WiFi ("hotspot") in the "Connections - System
Settings Module" with enabled WPA/WPA2 security, I cannot get Windows
10 clients to connect. Android 10 connects to this shared WiFi
without problems. Using the "Hotspot" button behind the system-tray
network icon works with Windows 10 clients (but creates an
open/unencrypted WiFi).
STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz"). Mode:
"Access Point".
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.
OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build
18363.418) asks for an eight-digit PIN instead of a password, unlike for other
WiFis. It is, however, also possible to click a link below and enter the
previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network
("Keine Verbindung mit diesem Netzwerk möglich"). This is reproducible with
different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without
problems.
EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10
does, or just as Windows 10 does to the unencrypted AP.
SOFTWARE/OS VERSIONS
Windows: Windows 10 Education, 1909, Build 18363.418
macOS:
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.4 (4:5.18.4.1-0ubuntu1)
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
I haven't tried this with earlier Kubuntu versions, but got one report
that this bug cannot be reproduced with Ubuntu 19.10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Apr 8 22:35:27 2020
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-11-26 (1229 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
IpRoute:
default via 192.168.178.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.178.0/24 dev wlp3s0 proto kernel scope link src 192.168.178.69
metric 600
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-03-06 (33 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-11-20T11:33:29
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871710/+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 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails
software-properties-gtk works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1872551 Title: kubuntu-driver-manager: nvidia driver version switch fails Status in software-properties package in Ubuntu: New Bug description: Switching the Nvidia driver version with kubuntu-driver-manager doesn't work anymore: Selecting a different driver version (nvidia- driver-440 instead of the currently selected / installed -390) and clicking "Apply Changes" has no effect and produces this error message in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 895, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined Steps to reproduce: - sudo kubuntu-driver-manager - Under "Additional Drivers", select a different Nvidia driver version (in my case: 440 instead of 390) - Click "Apply Changes" - (observe error message in the terminal) Expected result: - No error message - Nvidia driver version 440 gets installed Actual result: - Error message - No change in the installed Nvidia driver version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-driver-manager (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 23:41:56 2020 InstallationDate: Installed on 2016-11-26 (1234 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: kubuntu-driver-manager UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872551] Re: software-properties-qt: nvidia driver version switch fails
aptdaemon has been installed from the start. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1872551 Title: software-properties-qt: nvidia driver version switch fails Status in software-properties package in Ubuntu: Confirmed Bug description: Switching the Nvidia driver version with kubuntu-driver-manager doesn't work anymore: Selecting a different driver version (nvidia- driver-440 instead of the currently selected / installed -390) and clicking "Apply Changes" has no effect and produces this error message in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 895, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined Steps to reproduce: - sudo kubuntu-driver-manager - Under "Additional Drivers", select a different Nvidia driver version (in my case: 440 instead of 390) - Click "Apply Changes" - (observe error message in the terminal) Expected result: - No error message - Nvidia driver version 440 gets installed Actual result: - Error message - No change in the installed Nvidia driver version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-driver-manager (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 23:41:56 2020 InstallationDate: Installed on 2016-11-26 (1234 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: kubuntu-driver-manager UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872551] Re: software-properties-qt: nvidia driver version switch fails
The patch in comment #9 solves the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1872551 Title: software-properties-qt: nvidia driver version switch fails Status in software-properties package in Ubuntu: Confirmed Bug description: Switching the Nvidia driver version with kubuntu-driver-manager doesn't work anymore: Selecting a different driver version (nvidia- driver-440 instead of the currently selected / installed -390) and clicking "Apply Changes" has no effect and produces this error message in the terminal: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 895, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined Steps to reproduce: - sudo kubuntu-driver-manager - Under "Additional Drivers", select a different Nvidia driver version (in my case: 440 instead of 390) - Click "Apply Changes" - (observe error message in the terminal) Expected result: - No error message - Nvidia driver version 440 gets installed Actual result: - Error message - No change in the installed Nvidia driver version ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-driver-manager (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 23:41:56 2020 InstallationDate: Installed on 2016-11-26 (1234 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: kubuntu-driver-manager UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)
Related (and fixed in Debian?): https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=956281 ** Bug watch added: Debian Bug tracker #956281 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956281 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872875 Title: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken) Status in libva package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 System selects wrong intel driver (iris_drv_video.so). Therefore cannot use vaapi hardware decoding vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1872875/+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 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)
This also affects OBS Studio (focal package obs-studio), which fails to record using VAAPI hardware encoding due to this bug. Workaround: Start obs with the LIBVA_DRIVER_NAME environment variable set to the driver matching your Intel hardware, e.g. the following for my Intel Skylake CPU. LIBVA_DRIVER_NAME=i965 obs ** Also affects: libva via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956281 Importance: Unknown Status: Unknown ** Also affects: obs-studio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872875 Title: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken) Status in Libva: Unknown Status in libva package in Ubuntu: Confirmed Status in obs-studio package in Ubuntu: New Bug description: Ubuntu 20.04 System selects wrong intel driver (iris_drv_video.so). Therefore cannot use vaapi hardware decoding vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1872875/+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 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)
OBS Studio error message w/o the workaround, to help others find the aforementioned temporary solution: "Starting the output failed. Please check the log for details." info: [FFMPEG VAAPI encoder: 'streaming_h264'] settings: device: /dev/dri/renderD128 rate_control: CBR profile: 578 level:40 qp: 0 bitrate: 2500 maxrate: 2500 keyint: 60 width:1920 height: 1080 b-frames: 0 [h264_vaapi @ 0x55bae7f246c0] Driver does not support any RC mode compatible with selected options (supported modes: CQP). warning: [FFMPEG VAAPI encoder: 'streaming_h264'] Failed to open VAAPI codec: Invalid argument -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872875 Title: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken) Status in Libva: Unknown Status in libva package in Ubuntu: Confirmed Status in obs-studio package in Ubuntu: New Bug description: Ubuntu 20.04 System selects wrong intel driver (iris_drv_video.so). Therefore cannot use vaapi hardware decoding vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1872875/+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 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)
** Changed in: libva (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872875 Title: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken) Status in Libva: Fix Released Status in libva package in Ubuntu: Fix Released Status in obs-studio package in Ubuntu: Invalid Bug description: Ubuntu 20.04 System selects wrong intel driver (iris_drv_video.so). Therefore cannot use vaapi hardware decoding vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1872875/+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 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)
Regarding comment #6: Unfortunately the libva fix doesn't fix the obs- studio issue for me. I reported a separate bug. --> https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1873400 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1872875 Title: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken) Status in Libva: Fix Released Status in libva package in Ubuntu: Fix Released Status in obs-studio package in Ubuntu: Invalid Bug description: Ubuntu 20.04 System selects wrong intel driver (iris_drv_video.so). Therefore cannot use vaapi hardware decoding vainfo: libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1872875/+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 1310040] Re: viewing voip flows in wireshark causes wireshark to crash
*** This bug is a duplicate of bug 1311173 *** https://bugs.launchpad.net/bugs/1311173 ** This bug has been marked a duplicate of bug 1311173 VoIP call flow analyses cause wireshark crashes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1310040 Title: viewing voip flows in wireshark causes wireshark to crash Status in cairo package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages 100 /var/lib/dpkg/status wireshark: Installed: 1.10.6-1 Candidate: 1.11.3+svn20140414163130~4daf6f38-0ubuntu1~trusty1~ppa0 Version table: 1.11.3+svn20140414163130~4daf6f38-0ubuntu1~trusty1~ppa0 0 500 http://ppa.launchpad.net/dreibh/ppa/ubuntu/ trusty/main i386 Packages *** 1.10.6-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe i386 Packages 100 /var/lib/dpkg/status I expect to be able to view flows of voip calls. On a pcap with voip calls, selecting one or more voip calls and clicking flow causes wireshark to crash with the following Gdk:ERROR:/build/buildd/gtk+3.0-3.10.8/./gdk/gdkcairo.c:193:gdk_cairo_surface_paint_pixbuf: assertion failed: (cairo_image_surface_get_format (surface) == CAIRO_FORMAT_RGB24 || cairo_image_surface_get_format (surface) == CAIRO_FORMAT_ARGB32) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1310040/+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 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I'm seeing this as well on a machine with a clean 17.04 installation that was upgraded to 17.10, using KDE (sound: Intel HDA). Steps in comment #2 fixed this problem, at least temporarily. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) 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 artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
Update: After reinstalling pulseaudio, alsa-base, pulseaudio-module- bluetooth and plasma-pa (for KDE's volume control applet), the problem reappeared. Commenting out "load-module module-switch-on-connect" in /etc/pulse/default.pa (see comment #4) seems to fix the issue permanently; the module still seems to be loaded due to some other means of triggering the load (see output of: pactl list modules). -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) 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 artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1777709] [NEW] ubuntu-bug xserver-xorg-video-intel shows bogus dialog
Public bug reported: Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up a bogus dialog after a few seconds: [i] text [Yes] [No] [Cancel] There seems to be a descriptive message missing in place of the "text" placeholder. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 19 20:53:42 2018 InstallationDate: Installed on 2016-11-26 (570 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-03-14 (97 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/109 Title: ubuntu-bug xserver-xorg-video-intel shows bogus dialog Status in apport package in Ubuntu: New Bug description: Running "ubuntu-bug xserver-xorg-video-intel" as a normal user pops up a bogus dialog after a few seconds: [i] text [Yes] [No] [Cancel] There seems to be a descriptive message missing in place of the "text" placeholder. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jun 19 20:53:42 2018 InstallationDate: Installed on 2016-11-26 (570 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-03-14 (97 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/109/+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 299158] Re: Liberation Mono, Droid Sans Mono: Combining diacritics out of place
This is still broken in Ubuntu 18.04 bionic. It's notoriously annoying with text or filenames coming from OSX, which keeps diacritics separate from the character they're combined with, also for characters that have a distinct unicode code point for the combined variant. ** Also affects: ttf-bitstream-vera (Ubuntu) Importance: Undecided Status: New ** Also affects: fonts-noto (Ubuntu) Importance: Undecided Status: New ** Also affects: oxygen-fonts (Ubuntu) Importance: Undecided Status: New ** Also affects: fonts-tlwg (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Liberation Mono, Droid Sans Mono: Combining diacritics out of place + DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
My test case: echo -e 'a\u0308a' Correct rendering: äa (That's what I see with: Courier, Cousine, DejaVu Sans Mono, FreeMono, Hack, Monospace) Incorrect rendering: aä (That's what I see with: Andale Mono, Bitstream Vera Sans Mono, Courier 10 Pitch, Courier New, Liberation Mono, Mitra Mono, Nimbus Mono L, Noto Mono, Oxygen Mono, Tlwg Mono, Tlwg Typo, Ubuntu Mono) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Correction: "Hack Bold" renders correctly, "Hack Regular" doesn't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
** Also affects: fonts-hack (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: New Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1752053] Re: nvidia-390 fails to boot graphical display
For me this is still broken with -proposed packages although this bug has "Fix Released" status: When I have xserver-xorg-video-nvidia-390 390.48-0ubuntu1 installed, the system boots into a back screen. Without, LightDM comes up as expected. lspci excerpt (on a ThinkPad T460p): 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 02:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940MX] (rev a2) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display
Additional side effect: Bionic sometimes fails to come back from S3 and stays frozen with a black screen. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display
Seems to have been fixed by a recent update; boots into SDDM now as expected, using nvidia-drivers-390. -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1733103] [NEW] DNS hostname resolution fails intermittently
Public bug reported: Since upgrading to 17.10, hostname resolution (via, e.g., Firefox or the "host" command-line tool) does not work reliably anymore. Once hostname resolution fails (Firefox 57: "Hmm. We're having trouble finding that site."), manually resolving the host via "systemd-resolve" succeeds and temporarily allows Firefox to also resolve that host. After a few minutes, resolution of the same host fails again. Example with command-line "host" utility: $ host www.heise.de ;; connection timed out; no servers could be reached $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search fritz.box $ systemd-resolve www.heise.de www.heise.de: 2a02:2e0:3fe:1001::772e:2:85 193.99.144.85 -- Information acquired via protocol DNS in 273.2ms. -- Data is authenticated: no $ host www.heise.de www.heise.de has address 193.99.144.85 www.heise.de has IPv6 address 2a02:2e0:3fe:1001::772e:2:85 $ systemd-resolve --status Global DNS Servers: 192.168.178.1 DNS Domain: fritz.box DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 4 (wlp3s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: fd00::cece:1eff:fe61:2ece Link 3 (enp0s20f0u5c2) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp0s31f6) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no [... wait 2-3 minutes ...] $ host www.heise.de ;; connection timed out; no servers could be reached $ systemd-resolve www.heise.de www.heise.de: 2a02:2e0:3fe:1001::772e:2:85 193.99.144.85 -- Information acquired via protocol DNS in 284.2ms. -- Data is authenticated: no $ host www.heise.de www.heise.de has address 193.99.144.85 www.heise.de has IPv6 address 2a02:2e0:3fe:1001::772e:2:85 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Sat Nov 18 19:32:56 2017 InstallationDate: Installed on 2016-11-26 (357 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FXS05500 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/vgubuntu-root ro kopt=root=/dev/mapper/vgubuntu-root SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-21 (28 days ago) dmi.bios.date: 09/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET79W (2.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET79W(2.19):bd09/04/2017:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1733103 Title: DNS hostname resolution fails intermittently Status in systemd package in Ubuntu: New Bug description: Since upgrading to 17.10, hostname resolution (via, e.g., Firefox or the "host" c
[Touch-packages] [Bug 1733103] Re: DNS hostname resolution fails intermittently
Note that on my machine (clean 16.10 install, upgraded to 17.04 and later 17.10), DNS resolution already partially broke in 17.04 (involving the switch to systemd-resolve). With Ubuntu 17.04, DNS resolution was broken after suspending, moving to a different WiFi, and resuming the machine. This could be manually fixed by manually running dhclient. This does not fix the abovementioned issue, though. ** Description changed: Since upgrading to 17.10, hostname resolution (via, e.g., Firefox or the "host" command-line tool) does not work reliably anymore. Once hostname resolution fails (Firefox 57: "Hmm. We're having trouble finding that site."), manually resolving the host via "systemd-resolve" succeeds and temporarily allows Firefox to also resolve that host. After a few minutes, resolution of the same host fails again. Example with command-line "host" utility: $ host www.heise.de ;; connection timed out; no servers could be reached - $ cat /etc/resolv.conf + $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search fritz.box $ systemd-resolve www.heise.de www.heise.de: 2a02:2e0:3fe:1001::772e:2:85 - 193.99.144.85 + 193.99.144.85 -- Information acquired via protocol DNS in 273.2ms. -- Data is authenticated: no $ host www.heise.de www.heise.de has address 193.99.144.85 www.heise.de has IPv6 address 2a02:2e0:3fe:1001::772e:2:85 + $ systemd-resolve --status Global - DNS Servers: 192.168.178.1 - DNS Domain: fritz.box - DNSSEC NTA: 10.in-addr.arpa - 16.172.in-addr.arpa - 168.192.in-addr.arpa - 17.172.in-addr.arpa - 18.172.in-addr.arpa - 19.172.in-addr.arpa - 20.172.in-addr.arpa - 21.172.in-addr.arpa - 22.172.in-addr.arpa - 23.172.in-addr.arpa - 24.172.in-addr.arpa - 25.172.in-addr.arpa - 26.172.in-addr.arpa - 27.172.in-addr.arpa - 28.172.in-addr.arpa - 29.172.in-addr.arpa - 30.172.in-addr.arpa - 31.172.in-addr.arpa - corp - d.f.ip6.arpa - home - internal - intranet - lan - local - private - test + DNS Servers: 192.168.178.1 + DNS Domain: fritz.box + DNSSEC NTA: 10.in-addr.arpa + 16.172.in-addr.arpa + 168.192.in-addr.arpa + 17.172.in-addr.arpa + 18.172.in-addr.arpa + 19.172.in-addr.arpa + 20.172.in-addr.arpa + 21.172.in-addr.arpa + 22.172.in-addr.arpa + 23.172.in-addr.arpa + 24.172.in-addr.arpa + 25.172.in-addr.arpa + 26.172.in-addr.arpa + 27.172.in-addr.arpa + 28.172.in-addr.arpa + 29.172.in-addr.arpa + 30.172.in-addr.arpa + 31.172.in-addr.arpa + corp + d.f.ip6.arpa + home + internal + intranet + lan + local + private + test Link 4 (wlp3s0) - Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 -LLMNR setting: yes + Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: no - DNSSEC supported: no - DNS Servers: fd00::cece:1eff:fe61:2ece + DNSSEC setting: no + DNSSEC supported: no + DNS Servers: fd00::cece:1eff:fe61:2ece Link 3 (enp0s20f0u5c2) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: no - DNSSEC supported: no + DNSSEC setting: no + DNSSEC supported: no Link 2 (enp0s31f6) - Current Scopes: none -LLMNR setting: yes + Current Scopes: none + LLMNR setting: yes MulticastDNS setting: no - DNSSEC setting: no - DNSSEC supported: no + DNSSEC setting: no + DNSSEC supported: n
[Touch-packages] [Bug 1662244] Re: lightdm causes all greeters to fail to start
Please reopen. This just bit me on 17.10, using some manually configured soft and hard memlock limits in /etc/security/limits.conf: * softmemlock 262144 * hardmemlock 262144 As these limits *increase* max locked memory from 64 to 262144 kB, it took me quite some time (and a lucky google hit on this bug report) to locate this as the cause. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start Status in Light Display Manager: Invalid Status in LightDM GTK+ Greeter: Invalid Status in lightdm package in Ubuntu: Invalid Status in unity-greeter package in Ubuntu: Invalid Bug description: lightdm is failing to start. Best guess is because of unity-session- manager. This is from .xsession-errors. dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment upstart: click-user-hooks main process (4028) terminated with status 1 upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon respawning too fast, stopped upstart: indicator-application main process ended, respawning upstart: indicator-application main process ended, respawning upstart: indicator-application respawning too fast, stopped xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name upstart: dbus main process (4023) killed by TERM signal I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've reverted kernel versions and that didn't work. I've moved aside $HOME/.cache and that didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 6 10:21:29 2017 InstallationDate: Installed on 2015-07-20 (566 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+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 1662244] Re: lightdm causes all greeters to fail to start
This is BTW almost exactly the same what 'hugepages' does -- *increasing* memlock limits to 262144 kB. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start Status in Light Display Manager: Invalid Status in LightDM GTK+ Greeter: Invalid Status in lightdm package in Ubuntu: Invalid Status in unity-greeter package in Ubuntu: Invalid Bug description: lightdm is failing to start. Best guess is because of unity-session- manager. This is from .xsession-errors. dbus-update-activation-environment: setting _=/usr/bin/dbus-update-activation-environment upstart: click-user-hooks main process (4028) terminated with status 1 upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon main process ended, respawning upstart: unity-settings-daemon respawning too fast, stopped upstart: indicator-application main process ended, respawning upstart: indicator-application main process ended, respawning upstart: indicator-application respawning too fast, stopped xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03a00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x03c00084 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name xbrlapi: window 0x0484 changed to NULL name upstart: dbus main process (4023) killed by TERM signal I've tried to move aside $HOME/.config/dconf/user and that didn't work. I've reverted kernel versions and that didn't work. I've moved aside $HOME/.cache and that didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 6 10:21:29 2017 InstallationDate: Installed on 2015-07-20 (566 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to yakkety on 2016-12-14 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+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 1254884] Re: Pulseaudio: incoherent muting of ALSA channels (mutes master, headphone and speaker, but unmutes only master)
The newly added workaround ("xfce4-mixer (or Xfce Audio Mixer in panel):
Choose Playback:...(PulseAudio Mixer) instead of (Alsa mixer) as sound
card in properties") fixes the symptoms for me.
--
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/1254884
Title:
Pulseaudio: incoherent muting of ALSA channels (mutes master,
headphone and speaker, but unmutes only master)
Status in PulseAudio sound server:
Unknown
Status in pulseaudio package in Ubuntu:
Confirmed
Status in xfce4-volumed package in Ubuntu:
Invalid
Bug description:
with certain audio hardware (those where alsamixer shows separate
"headphone" and "speaker" channels) pressing of the mute button on
laptop keyboards causes mute of all three channels: master, headphone
and speaker. unfortunately, pressing the button again to unmute (or
deselecting mute in the xfce audio mixer panel applet) unmutes only
the master channel, leaving headphone and speaker muted. there is no
other way than opening alsamixer in a terminal (or open mixer controls
from the applet) and manually clicking the two remaining channels to
unmute.
Update: another workaround when using xfce4-mixer (or Xfce Audio Mixer
in panel): Choose Playback:...(PulseAudio Mixer) instead of (Alsa
mixer) as sound card in properties.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: xfce4-volumed 0.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Mon Nov 25 22:33:06 2013
InstallationDate: Installed on 2013-11-07 (17 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MarkForUpload: True
SourcePackage: xfce4-volumed
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1254884/+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 1226932] Re: Unable to Connect to Wi-Fi with Saved Password
Is the correct password mentioned in /etc/NetworkManager/system- connections/eduroam (or whichever SSID is affected in your case) in a "password=MYPASSWORD" line? In my case I didn't have such a line, and replacing "password-flags=1" with "password=MYPASSWORD" fixed automatic connecting for me. -- 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/1226932 Title: Unable to Connect to Wi-Fi with Saved Password Status in “network-manager” package in Ubuntu: Confirmed Bug description: It's been months. Before this my Wi-Fi used to work fine. Now I cannot connect to Wi-Fi at my office as long as I let Ubuntu remember the password. The "Wi-Fi Network Authentication Required" dialog keeps popping up asking me to enter my password. It's acting like when you enter a wrong password. And yes, I am sure the password is correct. Because if I select "Ask for this password every time", then usually it connects without a problem after I enter the same password. I guess it's worth mentioning that it still fails sometimes, even I let it ask for password. It just keeps failing and asking for password again and again. In such cases I turn off the WLAN adapter with the hardware switch, and then turn it back on. This usually fixes it. This only happens at office. Everything works fine at home. And my Android phone connects to the same office Wi-Fi without a problem. The Wi-Fi security settings are as following: Security: WPA & WPA2 Enterprise Authentication: Protected EAP (PEAP) Anonymouse identity: CA certificate: (None) PEAP version: Automatic Inner authentication: MSCHAPv2 Username: ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Wed Sep 18 11:58:28 2013 InstallationDate: Installed on 2012-08-12 (402 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) IpRoute: default via 150.236.220.1 dev wlan0 proto static 10.0.0.0/8 dev tun0 scope link 150.236.220.0/23 dev wlan0 proto kernel scope link src 150.236.221.32 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.56.0/24 dev vboxnet0 proto kernel scope link src 192.168.56.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-04-26 (144 days ago) http_proxy: http://localhost:3128/ nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enableddisableddisabled no_proxy: localhost,127.0.0.0/8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1226932/+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 1270791] Re: Enterprise wifi password is unnecessarily asked on boot
I have the same issue, but using Xfce4. Another workaround is to manually edit /etc/NetworkManager/system-connections/eduroam (or whichever SSID is affected in your case) and to replace "password- flags=1" with "password=MYPASSWORD", this allows automatic connection for me. -- 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/1270791 Title: Enterprise wifi password is unnecessarily asked on boot Status in “network-manager” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: Lightdm does not store my wifi password, for classic wifi is ok it stores every password, but for eap/peap wifi configuration it doesn't store any password and it asks me every time wifi password before login. Bug recognized in ubuntu 13.04 and 13.10 and probably in ubuntu 14.04 (testing). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 20 11:52:45 2014 InstallationDate: Installed on 2013-12-28 (22 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1270791/+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
