[Touch-packages] [Bug 1854733] Re: Canon LPB 6030
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1854733 Title: Canon LPB 6030 Status in cups package in Ubuntu: Expired Bug description: printter driwer das not work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-70.79~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Dec 2 14:09:33 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: 2019-12-02 10:56:18 startup archives install 2019-12-02 10:57:25 startup archives install ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2019-01-21 (315 days ago) InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=d23c244f-cbd5-450e-a02a-2772583abebf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.11 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.31 dmi.chassis.asset.tag: CZC10542JV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.11:bd11/25/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.31:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 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/cups/+bug/1854733/+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 1861538] Re: Intel Graphic Card not working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861538 Title: Intel Graphic Card not working Status in xorg package in Ubuntu: New Bug description: When I try to use the Intel GPU, I get an error : Error creating authentification agent : Error opening current controlling terminal for the process ('/dev/tty'): No such device or address. In the additional drivers section of Ubuntu, it says : Intel corporation :Unknown, indicating the GPU is not recognised. I also have an Nvidia MX250. I am using an IdeaPad S540 (Lenovo). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Fri Jan 31 19:20:55 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fec] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:3fec] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81V0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=d99c97c8-389d-482a-ad51-724da1184054 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CKCN11WW(V1.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S540-14IML Touch dmi.modalias: dmi:bvnLENOVO:bvrCKCN11WW(V1.01):bd07/19/2019:svnLENOVO:pn81V0:pvrLenovoIdeaPadS540-14IMLTouch:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS540-14IMLTouch: dmi.product.family: IdeaPad S540-14IML Touch dmi.product.name: 81V0 dmi.product.sku: LENOVO_MT_81V0_BU_idea_FM_IdeaPad S540-14IML Touch dmi.product.version: Lenovo IdeaPad S540-14IML Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861538/+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 1861538] [NEW] Intel Graphic Card not working
You have been subscribed to a public bug: When I try to use the Intel GPU, I get an error : Error creating authentification agent : Error opening current controlling terminal for the process ('/dev/tty'): No such device or address. In the additional drivers section of Ubuntu, it says : Intel corporation :Unknown, indicating the GPU is not recognised. I also have an Nvidia MX250. I am using an IdeaPad S540 (Lenovo). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None Date: Fri Jan 31 19:20:55 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3fec] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:3fec] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81V0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=d99c97c8-389d-482a-ad51-724da1184054 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CKCN11WW(V1.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S540-14IML Touch dmi.modalias: dmi:bvnLENOVO:bvrCKCN11WW(V1.01):bd07/19/2019:svnLENOVO:pn81V0:pvrLenovoIdeaPadS540-14IMLTouch:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS540-14IMLTouch: dmi.product.family: IdeaPad S540-14IML Touch dmi.product.name: 81V0 dmi.product.sku: LENOVO_MT_81V0_BU_idea_FM_IdeaPad S540-14IML Touch dmi.product.version: Lenovo IdeaPad S540-14IML Touch dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- Intel Graphic Card not working https://bugs.launchpad.net/bugs/1861538 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861540] [NEW] typo in man page
Public bug reported: "respectively" is wrongly spelled: -l Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. The destination and port to listen on can be specified either as non- optional arguments, or with options -s and -p *respctively*. This is corrected on 19.10 onwards at least; but given this is on an LTS release, opening the bug. Found and reported by "sabrina" via email. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Feb 1 01:07:19 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libbsd0 0.8.7-1ubuntu0.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 SourcePackage: netcat-openbsd UpgradeStatus: Upgraded to bionic on 2018-07-28 (552 days ago) ** Affects: netcat-openbsd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1861540 Title: typo in man page Status in netcat-openbsd package in Ubuntu: New Bug description: "respectively" is wrongly spelled: -l Used to specify that nc should listen for an incoming connection rather than initiate a connection to a remote host. The destination and port to listen on can be specified either as non- optional arguments, or with options -s and -p *respctively*. This is corrected on 19.10 onwards at least; but given this is on an LTS release, opening the bug. Found and reported by "sabrina" via email. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: netcat-openbsd 1.187-1ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sat Feb 1 01:07:19 2020 Dependencies: gcc-8-base 8.3.0-6ubuntu1~18.04.1 libbsd0 0.8.7-1ubuntu0.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 SourcePackage: netcat-openbsd UpgradeStatus: Upgraded to bionic on 2018-07-28 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1861540/+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 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1861446] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1861446 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts
This is actually because the linux source package doesn't reference 5.4.0-12 rather 5.4.0-9. See https://launchpad.net/ubuntu/+source/linux and 'apt-cache showsrc linux'. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861446 Title: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts Status in apport package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The issue was filed against linux-signed-5.4 (Ubuntu) rather than linux (Ubuntu), and none of the logs usually included with kernel bug reports were included. After the bug was changed from linux-signed-5.4 to linux, I was prompted to run apport-collect by the kernel team's triagebot and that worked successfully: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity My guess is that apport needs to be updated to understand a change in kernel packaging. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu16 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportLog: ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashReports: 640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash 600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash 640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash Date: Thu Jan 30 18:44:47 2020 PackageArchitecture: all ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1861446/+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 1861532] [NEW] brightness control not working
Public bug reported: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=084301b5-fdae-4c92-811e-0536a3b7555b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-17IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81Q4:pvrLegionY540-17IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLegionY540-17IRH: dmi.product.family: Legion Y540-17IRH dmi.product.name: 81Q4 dmi.product.sku: LENOVO_MT_81Q4_BU_idea_FM_Legion Y540-17IRH dmi.product.version: Legion Y540-17IRH dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861532 Title: brightness control not working Status in xorg package in Ubuntu: New Bug description: after selecting nvidia-driver-435 in livepatch- additional drivers the brightness control stops working after the first reboot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 22:00:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 4.15.0-76-generic, x86_64: installed nvidia, 435.21, 5.3.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3ffc] InstallationDate: Installed on 2020-01-31 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q4 ProcKernelCmdLine:
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
I don't think bnxt_en exposes the disable_tpa parameter. Be that as it may, I think the tpa_aborts may be a red herring. TPA aggregates TCP flows and you are seeing the issue with ICMP. In which direction(s) of traffic flow do you see the losses? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I
[Touch-packages] [Bug 1852474] Re: cups not printing if authentication required by server
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: Confirmed Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1852474/+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 1858972] Re: python-apt uses MD5 for validation
** Summary changed: - placeholder + python-apt uses MD5 for validation ** Description changed: - Placeholder bug. + Only MD5 is checked (most versions) + + In stable releases, and unstable, they only check MD5 sums of the files they download. 1.9.0 was broken as it still refered to the md5 field, but the field went away, so it would raise an exception if you tried to use it - so that's safe :D + + experimental (1.9.1) checks all hash sums, but only if some are present - it would happily accept an empty list of hashes - 1.9.2 will fix this issue by checking that the list of hashes is "usable", as it's called in apt, completing the proper fix. + + The only versions not affected by this are the ones in Ubuntu eoan and focal, as they hardcoded SHA256 instead of MD5 as a workaround to code failing because MD5 went away. ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1858972 Title: python-apt uses MD5 for validation Status in python-apt package in Ubuntu: Fix Released Bug description: Only MD5 is checked (most versions) In stable releases, and unstable, they only check MD5 sums of the files they download. 1.9.0 was broken as it still refered to the md5 field, but the field went away, so it would raise an exception if you tried to use it - so that's safe :D experimental (1.9.1) checks all hash sums, but only if some are present - it would happily accept an empty list of hashes - 1.9.2 will fix this issue by checking that the list of hashes is "usable", as it's called in apt, completing the proper fix. The only versions not affected by this are the ones in Ubuntu eoan and focal, as they hardcoded SHA256 instead of MD5 as a workaround to code failing because MD5 went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1858972/+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 1861528] [NEW] screen corruption/UI glitching
Public bug reported: The user interface in ubuntu 19.10-20.04 is having glitches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 19:48:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: HP-Pavilion KE568AA-ABA m8357c ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd12/12/2007:svnHP-Pavilion:pnKE568AA-ABAm8357c:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KE568AA-ABA m8357c dmi.product.sku: KE568AA#ABA dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1861528 Title: screen corruption/UI glitching Status in xorg package in Ubuntu: New Bug description: The user interface in ubuntu 19.10-20.04 is having glitches. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu13 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.438 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 31 19:48:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: HP-Pavilion KE568AA-ABA m8357c ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.04 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.04:bd12/12/2007:svnHP-Pavilion:pnKE568AA-ABAm8357c:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: KE568AA-ABA m8357c dmi.product.sku: KE568AA#ABA dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1 version.xserver-xorg-input-evdev:
[Touch-packages] [Bug 1858973] Re: python-apt downloads from untrusted sources where apt does not
** Summary changed: - placeholder + python-apt downloads from untrusted sources where apt does not ** Description changed: - Placeholder bug. + ptyhon-apt never checked whether the hashes it got were signed in the + first place. So, python-apt is happy to download files from unsigned + repositories when it shouldn't. + + Making the code only fetch trusted packages means that using it on + untrusted packages will fail. There might be use cases broken by this. ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1858973 Title: python-apt downloads from untrusted sources where apt does not Status in aptdaemon package in Ubuntu: Fix Released Status in python-apt package in Ubuntu: Fix Released Bug description: ptyhon-apt never checked whether the hashes it got were signed in the first place. So, python-apt is happy to download files from unsigned repositories when it shouldn't. Making the code only fetch trusted packages means that using it on untrusted packages will fail. There might be use cases broken by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1858973/+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 1861481] Re: language-options causes live CD sessions to be untranslated
I actually meant the locale command without options, but I still think you provided the info we need. ;) On 2020-01-31 19:48, Alkis Georgopoulos wrote: > It's not /etc/default/locale, in all the cases only LANG is there > and not LANGUAGE. LightDM does set LANGUAGE for some reason through an Ubuntu specific patch, and it might explain it. The weird thing is that LightDM has done that since long before 19.10. Anyway, maybe we should simply stop LightDM from messing with LANGUAGE when run in a live session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
I'm speculating that pango 1.44 dropping support for bitmap fonts might be a cause: https://gitlab.gnome.org/GNOME/pango/issues/386 ** Package changed: fontconfig (Ubuntu) => pango1.0 (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/pango/issues #386 https://gitlab.gnome.org/GNOME/pango/issues/386 ** Description changed: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) - I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: + ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 - (the window displays but immediately locks up.) + (the window displays but immediately locks up.)~~ + UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation ** Description changed: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) - ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: - https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 - (the window displays but immediately locks up.)~~ - UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present. + gnome-font-viewer does not list any of the installed bitmap fonts. While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in pango1.0 package in Ubuntu: New Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here:
[Touch-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
I semi-guessed at package 'fontconfig' to associate. Advice welcome. ** Package changed: ubuntu => fontconfig (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) Status in fontconfig package in Ubuntu: New Bug description: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 (the window displays but immediately locks up.) While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1861340/+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 1861340] [NEW] All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
You have been subscribed to a public bug: For years I've installed a bitmap font for my terminals, but since I upgraded to Focal (development branch) today, it (and other bitmap fonts) no longer work. The font is 'Dina', from here: http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7 I have always installed it using a script: # install dina sudo mkdir -p /usr/share/fonts/Dina cd /usr/share/fonts/Dina sudo unzip ~/Downloads/Dina.zip # enable bitmap fonts sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf # rebuild the cache fc-cache -f -v # Set as default mono font gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8" This has always worked in the past, through many versions of Ubuntu, including 19.10. I installed Focal today, using `sudo do-release-upgrade -d`. Now the above script does not make Dina visible in font selectors such as that produced by the Tweaks / Fonts / [Monospace Text] button. Terminals that were previously configured to use that font now display the "box of hex digits" characters (what are they called?) I cannot run 'gnome-font-viewer' to check things out, presumably due to some variant of: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819 (the window displays but immediately locks up.) While trying to find a fix, I tried a few changes to the above script, which did not help: * Unzip to "$HOME/.fonts" instead * Trying other symlinks in the fonts config.d: ( cd /etc/fonts/conf.d sudo rm -f 70-no-bitmaps.conf sudo ln -sf ../conf.avail/70-yes-bitmaps.conf ) (tried with both 'yes-bitmaps' and 'force-bitmaps') * fc-cache -r # "really" force cache re-creation ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) https://bugs.launchpad.net/bugs/1861340 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated
I.e. from what I can see, the basic difference is that since 19.10, something sets LANGUAGE=en. While in the Italian session that has a langpack in the live iso, LANGUAGE=it. It's not /etc/default/locale, in all the cases only LANG is there and not LANGUAGE. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] Re: language-options causes live CD sessions to be untranslated
Hi Gunnar, here are the results: Output of Ubuntu MATE 20.04 today's daily build: $ env | grep LANG LANGUAGE=en GDM_LANG=en LANG=el_GR.UTF-8 $ locale -a C C.UTF-8 de_AT.utf8 de_BE.utf8 de_CH.utf8 de_DE.utf8 de_IT.utf8 de_LI.utf8 de_LU.utf8 el_GR.utf8 en_AG en_AG.utf8 en_AU.utf8 en_BW.utf8 en_CA.utf8 en_DK.utf8 en_GB.utf8 en_HK.utf8 en_IE.utf8 en_IL en_IL.utf8 en_IN en_IN.utf8 en_NG en_NG.utf8 en_NZ.utf8 en_PH.utf8 en_SG.utf8 en_US.utf8 en_ZA.utf8 en_ZM en_ZM.utf8 en_ZW.utf8 es_AR.utf8 es_BO.utf8 es_CL.utf8 es_CO.utf8 es_CR.utf8 es_CU es_CU.utf8 es_DO.utf8 es_EC.utf8 es_ES.utf8 es_GT.utf8 es_HN.utf8 es_MX.utf8 es_NI.utf8 es_PA.utf8 es_PE.utf8 es_PR.utf8 es_PY.utf8 es_SV.utf8 es_US.utf8 es_UY.utf8 es_VE.utf8 fr_BE.utf8 fr_CA.utf8 fr_CH.utf8 fr_FR.utf8 fr_LU.utf8 it_CH.utf8 it_IT.utf8 POSIX pt_BR.utf8 pt_PT.utf8 ru_RU.utf8 ru_UA.utf8 $ /usr/share/language-tools/language-options de_CH de_DE en en_AU en_CA en_GB en_US es_AR es_CL es_CO es_CR es_DO es_EC es_ES es_MX es_NI es_PA es_PE es_PR es_SV es_US es_UY es_VE fr_CA fr_FR it_IT pt_BR pt_PT ru Output of Ubuntu MATE 18.04.3 iso: $ env | grep LANG LANG=el_GR.UTF-8 $ locale -a C C.UTF-8 de_AT.utf8 de_BE.utf8 de_CH.utf8 de_DE.utf8 de_IT.utf8 de_LI.utf8 de_LU.utf8 el_GR.utf8 en_AG en_AG.utf8 en_AU.utf8 en_BW.utf8 en_CA.utf8 en_DK.utf8 en_GB.utf8 en_HK.utf8 en_IE.utf8 en_IL en_IL.utf8 en_IN en_IN.utf8 en_NG en_NG.utf8 en_NZ.utf8 en_PH.utf8 en_SG.utf8 en_US.utf8 en_ZA.utf8 en_ZM en_ZM.utf8 en_ZW.utf8 es_AR.utf8 es_BO.utf8 es_CL.utf8 es_CO.utf8 es_CR.utf8 es_CU es_CU.utf8 es_DO.utf8 es_EC.utf8 es_ES.utf8 es_GT.utf8 es_HN.utf8 es_MX.utf8 es_NI.utf8 es_PA.utf8 es_PE.utf8 es_PR.utf8 es_PY.utf8 es_SV.utf8 es_US.utf8 es_UY.utf8 es_VE.utf8 fr_BE.utf8 fr_CA.utf8 fr_CH.utf8 fr_FR.utf8 fr_LU.utf8 it_CH.utf8 it_IT.utf8 POSIX pt_BR.utf8 pt_PT.utf8 ru_RU.utf8 ru_UA.utf8 zh_CN.utf8 zh_SG.utf8 $ /usr/share/language-tools/language-options de_CH de_DE en en_AU en_CA en_GB en_US es_AR es_CL es_CO es_CR es_DO es_EC es_ES es_MX es_NI es_PA es_PE es_PR es_SV es_US es_UY es_VE fr_CA fr_FR it_IT pt_BR pt_PT ru zh_CN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] Re: language-options causes live CD sessions to be untranslated
@Alkis: Since it sounds as if you have access to both a 18.04 and a 19.10 ISO, can you please check what the locale command outputs in the live session of respective release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
I couldn't load kernel 5.5 because secure boot was turned on. My bad, sorry. I was able to test the sound with kernel 5.5 after disable secure boot but there is no improvement. The audio is still bad. I'm attaching another file. It sounds like it's a cassette player running out of battery. ** Attachment added: "bad-sound2.m4a" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+attachment/5324432/+files/bad-sound2.m4a -- 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/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+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 1860985] Re: packagekitd using 100% CPU
It's off again, this time an opensuse repository. I would remove it about now but it seems it can't be removed without breaking other stuff. The following packages will be REMOVED apturl gnome-packagekit gnome-software gnome-software-plugin-flatpak gnome-software-plugin-snap gstreamer1.0-packagekit muon muon-discover muon-notifier muon-updater nautilus-share package-update-indicator packagekit pk-update-icon plasma-discover software-properties-common software-properties-gtk software-properties-qt ubuntu-desktop ubuntu-desktop-minimal ubuntu-software Good grief, it's got its tentacles in to loads. How do I disable it, how do I make it check for updates every few hours not seconds, how do I tell it not to retry broken PPAs insessently consuming 100% CPU. How do I turn this wretched thing off?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: Incomplete Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1861481] Re: language-options causes live CD sessions to be untranslated
No, sorry, that's not it, I removed it and restarted lightdm and I still had LANGUAGE=en in the live session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] Re: language-options causes live CD sessions to be untranslated
In Ubuntu 20.04 live CD, in .xsession-errors, I see this line: dbus-update-activation-environment: setting LANGUAGE=en Maybe that's to blame here; looking more... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] Re: language-options causes live CD sessions to be untranslated
Gunnar, yes, the live sessions are properly translated up to and including 19.04 (and of course 18.04 too). Starting from 19.10, all child processes of lightdm have LANGUAGE=en, so the session is untranslated. But this only happens for languages that don't have the langpack installed. Running /usr/share/language-tools/language-options in the Ubuntu 18.04 live CD does NOT show el_GR in the output though. But if that script hasn't changed, and lightdm hasn't changed... what did change and broke this in the 19.10 live CDs? :/ I wonder if the lightdm patch changed, and it used to call locale -a, and it was changed to call the language-options script in 19.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] Re: language-options causes live CD sessions to be untranslated
Well, the point with the language-options script is to only list languages where the language-packs are present. It has been that way for many cycles, and AFAIK nothing special happened in this respect in 19.10. @Alkis: Are you claiming that it worked otherwise in e.g. 18.04? With that said, I understand that it's not an optimal approach wrt the live session for a flavor. If we are going to change this somehow (I have no idea how ATM), it should reasonably be done without changing the language-options script. The latter was written with a real install in mind at first hand. ** Changed in: accountsservice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Incomplete Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1860432] Re: juju agent fails to start on focal
** Tags added: id-5e33211d5d925144089cd85f -- 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/1860432 Title: juju agent fails to start on focal Status in juju: Fix Committed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: Confirmed Bug description: during bootstrap, add-machine, deploy Juju fails on Focal due to systemd not finding the service. ll /etc/systemd/system jujud-machine-1.service -> /lib/systemd/system/jujud-machine-1/jujud-machine-1.service which is linked and calls ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh The fact that it's in a jujud-machine-1 folder vs /system itself appears to be causing systemd to not be able to run it. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1860432/+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 1859858] Re: udev has truncated ID_SERIAL value for scsi disk
** Tags added: id-5e3321e6edacef1db146c8bf -- 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/1859858 Title: udev has truncated ID_SERIAL value for scsi disk Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: 1. root@ubuntu:/home/ubuntu# cat /etc/cloud/build.info build_name: server serial: 20200106 root@ubuntu:/home/ubuntu# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 2. root@ubuntu:/home/ubuntu# apt-cache policy systemd systemd: Installed: 244-3ubuntu1 Candidate: 244-3ubuntu1 Version table: *** 244-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. ID_SERIAL value should be 322dc58dc023c7008 4. ID_SERIAL value is 3 -- Launching a qemu VM with the same extra scsi disk like so: -drive file=extra_disk_1.img,id=drv4,if=none,format=raw,index=4,cache=unsafe \ -device scsi-hd,drive=drv4,serial=0x22dc58dc023c7008,wwn=0x22dc58dc023c7008 On Focal udevadm info output: root@ubuntu:/home/ubuntu# udevadm info --query=property /dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVNAME=/dev/sdc DEVTYPE=disk MAJOR=8 MINOR=32 SUBSYSTEM=block USEC_INITIALIZED=1497555 SCSI_TPGS=0 SCSI_TYPE=disk SCSI_VENDOR=QEMU SCSI_VENDOR_ENC=QEMU\x20\x20\x20\x20 SCSI_MODEL=QEMU_HARDDISK SCSI_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 SCSI_REVISION=2.5+ ID_SCSI=1 ID_SCSI_INQUIRY=1 ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_REVISION=2.5+ ID_TYPE=disk SCSI_IDENT_SERIAL=0x22dc58dc023c7008 SCSI_IDENT_LUN_VENDOR=0x22dc58dc023c7008 SCSI_IDENT_LUN_NAA_EXT=22dc58dc023c7008 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 ID_BUS=scsi ID_SERIAL=3 ID_SERIAL_SHORT=22dc58dc023c7008 MPATH_SBIN_PATH=/sbin DM_MULTIPATH_DEVICE_PATH=0 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_FS_UUID=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_ENC=b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 ID_FS_UUID_SUB=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_UUID_SUB_ENC=e06d861c-c6e2-497c-b14f-265ae37060e2 ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_BTRFS_READY=1 DEVLINKS=/dev/disk/by-id/scsi-3 /dev/disk/by-id/scsi-0QEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-SQEMU_QEMU_HARDDISK_0x22dc58dc023c7008 /dev/disk/by-uuid/b20cf5c1-15ae-48a7-a5d9-dfcfd37df494 /dev/disk/by-id/scsi-322dc58dc023c7008 TAGS=:systemd: On Bionic: root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20200112 root@ubuntu:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ubuntu:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.33 Candidate: 237-3ubuntu10.33 Version table: *** 237-3ubuntu10.33 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10.29 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@ubuntu:~# udevadm info --query=property /dev/sdc DEVLINKS=/dev/disk/by-uuid/13a8a15f-4f6b-4904-b307-339b825c445b /dev/disk/by-path/pci-:00:03.0-scsi-0:0:2:0 /dev/disk/by-id/wwn-0x22dc58dc023c7008 /dev/disk/by-id/scsi-322dc58dc023c7008 DEVNAME=/dev/sdc DEVPATH=/devices/pci:00/:00:03.0/virtio0/host2/target2:0:2/2:0:2:0/block/sdc DEVTYPE=disk ID_BTRFS_READY=1 ID_BUS=scsi ID_FS_TYPE=btrfs ID_FS_USAGE=filesystem ID_FS_UUID=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_ENC=13a8a15f-4f6b-4904-b307-339b825c445b ID_FS_UUID_SUB=81178585-f7c0-429a-b02d-aeb2f245342c ID_FS_UUID_SUB_ENC=81178585-f7c0-429a-b02d-aeb2f245342c ID_MODEL=QEMU_HARDDISK ID_MODEL_ENC=QEMU\x20HARDDISK\x20\x20\x20 ID_PATH=pci-:00:03.0-scsi-0:0:2:0 ID_PATH_TAG=pci-_00_03_0-scsi-0_0_2_0 ID_REVISION=2.5+ ID_SCSI=1 ID_SCSI_SERIAL=0x22dc58dc023c7008 ID_SERIAL=322dc58dc023c7008 ID_SERIAL_SHORT=22dc58dc023c7008 ID_TYPE=disk ID_VENDOR=QEMU ID_VENDOR_ENC=QEMU\x20\x20\x20\x20 ID_WWN=0x22dc58dc023c7008 ID_WWN_WITH_EXTENSION=0x22dc58dc023c7008 MAJOR=8 MINOR=32 SUBSYSTEM=block TAGS=:systemd: USEC_INITIALIZED=2069797 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 244-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
[Touch-packages] [Bug 1861230] Re: _sasl_plugin_load failed
Hi, don't worry about it. Regressions can be serious. Let's mark this bug as incomplete then, and it will auto-expire on its own if no further information is added to it. If you ever see this again, or have more data, feel free to add a comment here. Cheers, thanks for getting back to us with the results. ** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1861230 Title: _sasl_plugin_load failed Status in cyrus-sasl2 package in Ubuntu: Incomplete Bug description: We are seeing the following in the journal after upgrading to these sets of packages: libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-db/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 Here are the errors: Jan 28 15:58:43 my-hostname sssd[20949]: Starting up Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on sasl_canonuser_init Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
Perhaps the hash is missing in debian/openssh-server.ucf-md5sum? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: New Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1813266] Re: udhcpd: not dying on SIGTERM
This has been open for over a year, with a fix indicated from the very beginning. Is there any chance that patch can be applied? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1813266 Title: udhcpd: not dying on SIGTERM Status in busybox package in Ubuntu: Confirmed Bug description: udhcpd in bionic does not stop on SIGTERM due to an upstream change. This was corrected by the following patch: https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084 Please apply and backport/SRU this change to bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1813266/+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 1859483] Re: busybox udhcpd does not honour SIGTERM
*** This bug is a duplicate of bug 1813266 *** https://bugs.launchpad.net/bugs/1813266 ** This bug has been marked a duplicate of bug 1813266 udhcpd: not dying on SIGTERM -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1859483 Title: busybox udhcpd does not honour SIGTERM Status in busybox package in Ubuntu: New Bug description: busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the udhcpd daemon does not react properly to SIGTERM. That bug if fixed in upstream busybox as of 1.29.0, commit 3293bc146985c56790033409facc0ad64a471084 . That patch should be back- ported to the busybox 1.27.2 - I believe it applies cleanly (it did when we hit this on our Yocto-based embedded systems). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1859483/+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 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> NICs between systems? Are OS / kernel and driver > versions the same on both systems? Yes, identical distro release, kernel, and most of the software stack (I have not obtained and examined the full sw stack). Configuration of networking settings is also the same. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
Thanks very much for helping on this, Edwin! Please let me know if there's anything specific you need. I'm asking them to disable any IPv6, LLDP traffic in their environment, and retest and collect information again. Also, I'd like to disable tpa, would this be at all useful: modprobe bnx disable_tpa=1 ?? -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> There are more than one variable at play here. > Does the problem follow the NIC if you swap the > NICs between systems? Are OS / kernel and driver > versions the same on both systems? Unfortunately, I've not been able to get them to try permutations or switches, as yet, as this is still a production system/environment. I'll try and obtain more information about it. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G
[Touch-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
> The mtr packet loss is an interesting result. What mtr options did you use? Is this a UDP or ICMP test? The mtr command was: mtr --no-dns --report --report-cycles 60 $IP_ADDR so ICMP was going out. -- 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/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting
[Touch-packages] [Bug 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: New Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1861481] Re: language-options causes live CD sessions to be untranslated
Gunnar, you know probably that script best, could you maybe have a look to what changed in 19.10 to create the issue? ** Changed in: accountsservice (Ubuntu) Importance: Undecided => High ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: New Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1861481] [NEW] language-options causes live CD sessions to be untranslated
Public bug reported: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! ** Affects: accountsservice (Ubuntu) Importance: High Status: New ** Tags: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: New Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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 1860522] Re: Mesa 19.2.8 stable release
This bug was fixed in the package mesa - 19.2.8-0ubuntu0~18.04.1 --- mesa (19.2.8-0ubuntu0~18.04.1) bionic; urgency=medium * New bugfix release. (LP: #1860522) * Revert-meson-fix-logic-for-generating-.pc-files-with.patch: Dropped, fixed upstream. * rules: GLESv2 libs aren't built anymore, drop removing them. * mesa-common-dev: Drop mangled GL/GLX headers, they're not generated anymore. -- Timo Aaltonen Wed, 22 Jan 2020 11:57:11 +0200 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860522 Title: Mesa 19.2.8 stable release Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Status in mesa source package in Eoan: Fix Released Bug description: [Impact] 19.10 released with mesa 19.2.1. We need the last point release of the 19.2.x series in eoan and backported for bionic. [Test case] Check on intel/radeon hw that things still work fine. [Regression potential] This is the last update of the series, all regressions should be shaken off at this point by upstream CI/community To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860522/+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