[Touch-packages] [Bug 1928526] [NEW] DHCP Cluster crashes randomly
Public bug reported: We're running in to a case that's very similar to https://bugs.launchpad.net/dhcp/+bug/1872118 where the DHCP server periodically crashes. Crashes sometimes take days to happen on relatively busy DHCP servers. There's not an obvious reason, however the logs end up showing (hostnames and email address changed slightly to keep meaning, but not disclose everything). May 14 05:22:17 is-landlord-04.wm.edu sh[305109]: ../../../../lib/isc/unix/socket.c:4359: fatal error: select() failed: Bad file descriptor May 14 05:22:27 hostname.wm.edu systemd[1]: isc-dhcp-server.service: Main process exited, code=killed, status=6/ABRT May 14 05:22:32 is-landlord-04.wm.edu sSMTP[1645996]: Sent mail for nore...@wm.edu (221 2.0.0 Service closing transmission channel) uid=0 username=root ou> May 14 05:22:32 is-landlord-04.wm.edu systemd[1]: isc-dhcp-server.service: Failed with result 'signal'. May 14 05:22:37 is-landlord-04.wm.edu systemd[1]: isc-dhcp-server.service: Scheduled restart job, restart counter is at 25. May 14 05:22:37 is-landlord-04.wm.edu systemd[1]: Stopped ISC DHCP IPv4 server. May 14 05:22:37 is-landlord-04.wm.edu systemd[1]: Started ISC DHCP IPv4 server. $ sudo cat _usr_sbin_dhcpd.0.crash ProblemType: Crash Architecture: amd64 Date: Fri May 14 05:22:21 2021 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/sbin/dhcpd ExecutableTimestamp: 1615303185 ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf ProcEnviron: Error: [Errno 13] Permission denied: 'environ' ProcMaps: Error: [Errno 13] Permission denied: 'maps' ProcStatus: Name: dhcpd Umask: 0022 State: D (disk sleep) Tgid: 305109 Ngid: 0 Pid: 305109 PPid: 1 TracerPid: 0 Uid: 116 116 116 116 Gid: 119 119 119 119 FDSize:256 Groups: NStgid:305109 NSpid: 305109 NSpgid:305109 NSsid: 305109 VmPeak: 422372 kB VmSize: 356836 kB VmLck:0 kB VmPin:0 kB VmHWM: 289404 kB VmRSS: 258028 kB RssAnon: 255560 kB RssFile: 2468 kB RssShmem: 0 kB VmData: 282632 kB VmStk: 132 kB VmExe: 592 kB VmLib: 5352 kB VmPTE: 584 kB VmSwap:2496 kB HugetlbPages: 0 kB CoreDumping: 1 THP_enabled: 1 Threads: 4 SigQ: 0/3521 SigPnd: ShdPnd: SigBlk: SigIgn:1000 SigCgt:00018000 CapInh: CapPrm: CapEff: CapBnd:003f CapAmb: NoNewPrivs:0 Seccomp: 0 Speculation_Store_Bypass: thread vulnerable Cpus_allowed: , Cpus_allowed_list: 0-63 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0001 Mems_allowed_list: 0 voluntary_ctxt_switches: 94 nonvoluntary_ctxt_switches:831 Signal: 6 Uname: Linux 5.4.0-71-generic x86_64 UserGroups: N/A Because of the similarities with #1872118 we started by checking various package versions: $ sudo dpkg -l | grep -i isc- ii isc-dhcp-client 4.4.1-2.1ubuntu5.20.04.1 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.4.1-2.1ubuntu5.20.04.1 amd64common manpages relevant to all of the isc-dhcp packages ii isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.1 amd64ISC DHCP server for automatic IP address assignment ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ubuntu1 amd64Exported ISC Shared Library $ sudo dpkg -l | grep -i bind9-libs ii bind9-libs:amd64 1:9.16.1-0ubuntu2.8 amd64Shared Libraries used by BIND 9 $ sudo dpkg -l | grep -i libisc-* ii libisc-export1105:amd64 1:9.11.16+dfsg-3~ubuntu1 amd64Exported ISC Shared Library ii libisccfg-export163 1:9.11.16+dfsg-3~ubuntu1 amd64Exported ISC CFG Shared Library $ sudo dpkg -l | grep -i libirs-* ii libirs-export161 1:9.11.16+dfsg-3~ubuntu1 amd64Exported IRS Shared Library $ sudo dpkg -l | grep -i libdns-* ii libdns-export11091:9.11.16+dfsg-3~ubuntu1 amd64Exported DNS Shared Library Finally, we're running Ubuntu 20.04.2: $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 Let us know what else can be provided to help confirm or troubleshoot the issue. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: Ne
[Touch-packages] [Bug 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: Expired Status in mesa package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB 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 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+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 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
[Expired for linux-hwe-5.8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Incomplete => Expired -- 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/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: Expired Status in mesa package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB 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 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+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 1918619] Re: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake)
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- 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/1918619 Title: [i915] Horizontal noise-like screen corruption (Gen9 Kaby Lake) Status in linux-hwe-5.8 package in Ubuntu: Expired Status in mesa package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: I use to press Alt+Tab to switch between windows (or frames, whatever) and I noticed today that when I switch to another window the up bar blinks. I already had a display problem once, so I knew it was better with a external video. EDIT: I remember having this problem a year ago perhaps, and it disappear if I reboot my computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 10:45:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:39e9] InstallationDate: Installed on 2020-11-15 (115 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 80V0 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/03/2018 dmi.bios.release: 2.20 dmi.bios.vendor: LENOVO dmi.bios.version: 3PCN20WW(V2.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 510S-13IKB 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 510S-13IKB dmi.ec.firmware.release: 2.20 dmi.modalias: dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:br2.20:efr2.20:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB: dmi.product.family: IDEAPAD dmi.product.name: 80V0 dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB dmi.product.version: Lenovo ideapad 510S-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1918619/+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 1440381] Re: please build bindings for Python3
** Changed in: samba (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tdb in Ubuntu. https://bugs.launchpad.net/bugs/1440381 Title: please build bindings for Python3 Status in ldb package in Ubuntu: Fix Released Status in samba package in Ubuntu: Fix Released Status in talloc package in Ubuntu: Fix Released Status in tdb package in Ubuntu: Fix Released Status in samba package in Debian: Fix Released Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. please build bindings for Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldb/+bug/1440381/+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 1928524] [NEW] GPU intel
Public bug reported: GPU problems, lagging games and gpu not showing in drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Ikke tilgang: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 15 02:03:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0534] InstallationDate: Installed on 2021-04-13 (31 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Latitude E6430 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=00e21584-3dfe-4482-8797-e2f18f29cc3e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0CPWYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/12/2013:br4.6:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0CPWYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-2~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~kisak1~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928524 Title: GPU intel Status in xorg package in Ubuntu: New Bug description: GPU problems, lagging games and gpu not showing in drivers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Ikke tilgang: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 15 02:03:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0534] InstallationDate: Installed on 2021-04-13 (31 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Latitude E6430 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=00e21584-3dfe-4482-8797-e2f18f29cc3e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2013 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0CPWYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/12/2013:br4.6:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0CPWYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6430 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-2~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~kisak1~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928524/+subscripti
[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
Assuming that this may require apparmor changes, I added an apparmor (Ubuntu) bug task. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Ubuntu Kylin: New Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: New Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1928360/+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 1920130] Re: System icons missing in kubuntu 21.04
Hi Owen, Thanks a lot for sharing the log. Indeed, qt5-default seems to be the cause of this bug. In https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=976389#15 I explained in more detail my understanding of why this is happening. The fix should land in Impish (development release) in a few hours, and then I will look at a fix for Hirsute (21.04). ** Package changed: qtdeclarative-opensource-src (Ubuntu) => qtdeclarative-opensource-src-gles (Ubuntu) ** Changed in: qtdeclarative-opensource-src-gles (Ubuntu) Status: Won't Fix => Fix Committed ** Also affects: qtdeclarative-opensource-src-gles (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtdeclarative-opensource-src-gles package in Ubuntu: Fix Committed Status in qtdeclarative-opensource-src-gles source package in Hirsute: New Status in qtdeclarative-opensource-src-gles package in Debian: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/p
[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
Hello udippel, or anyone else affected,
Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.33 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags removed: verification-done
** Tags added: verification-needed verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
Fix Committed
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
In Progress
Status in apt source package in Hirsute:
Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
Fix Released
Bug description:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release
upgrader being unable to handle interrupts after it did the initial
update - the default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message.
For your sources.list file to be restored you'll need the version of
apt from bionic-proposed installed before starting the upgrade.
[Where problems could occur]
apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
ubuntu-release-upgrader: The change is wrapping a bunch of code in a
try: except: block so if the indentation was off the pyflakes /
pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make
[Touch-packages] [Bug 1927738] Re: Bluetooth doesn't work in Ubuntu 21.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => bluez (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1927738 Title: Bluetooth doesn't work in Ubuntu 21.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth doesn't work in Ubuntu 21.04 after update ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 7 16:32:21 2021 InstallationDate: Installed on 2020-04-08 (394 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-15 (22 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1927738/+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 1927738] [NEW] Bluetooth doesn't work in Ubuntu 21.04
You have been subscribed to a public bug: Bluetooth doesn't work in Ubuntu 21.04 after update ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 7 16:32:21 2021 InstallationDate: Installed on 2020-04-08 (394 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to hirsute on 2021-04-15 (22 days ago) VarLogDistupgradeTermlog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute -- Bluetooth doesn't work in Ubuntu 21.04 https://bugs.launchpad.net/bugs/1927738 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
On Fri, May 14, 2021 at 01:36:12PM -, Stephane Chazelas wrote:
>The important backtrace in there is the one from thread 11:
>
>#0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0
>No symbol table info available.
>#1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2
>No symbol table info available.
>#2 0x7fb287895848 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30
>No symbol table info available.
This is a valid issue, but are we certain it's the same one? The
reporter talked about sched_yield and their backtraces included several
threads of back_monitor waiting on some kind of lock.
>https://bugs.openldap.org/show_bug.cgi?id=8650#c12 explains that it's
>https://github.com/openldap/openldap/commit/7b5181da8cdd47a13041f9ee36fa9590a0fa6e48
>that is responsible for the issue.
>
>https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e
>reverted that commit, but that one did not make it into bionic.
Indeed. :( I didn't notice this went unfixed in an LTS, I'm sorry for
missing that.
>So cherry picking
>https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e
>should fix it.
In this version it's a Debian patch, so probably just remove the
offending patch from d/patches, rather than import the revert?
On Fri, May 14, 2021 at 02:18:47PM -, Stephane Chazelas wrote:
>Yes,
>https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503
>can't be directly applied there. There have been other changes in
>between in that section including changes in API, so it would take more
>effort to backport that fix.
Right. I'm not confident I can backport that correctly, so I'd feel
safer just doing the revert. However, sssd should also be tested, to
ensure the version in bionic isn't affected by ITS#9210
(https://bugs.openldap.org/show_bug.cgi?id=9210).
COMPLETELY UNTESTED debdiff attached.
** Bug watch added: bugs.openldap.org/ #9210
https://bugs.openldap.org/show_bug.cgi?id=9210
** Attachment added: "openldap_2.4.45+dfsg-1ubuntu1.11.debdiff"
https://bugs.launchpad.net/bugs/1926265/+attachment/5497610/+files/openldap_2.4.45+dfsg-1ubuntu1.11.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
** Description changed:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release upgrader
being unable to handle interrupts after it did the initial update - the
default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
time.sleep(1)
except BaseException as e:
print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
[[ubuntu-release-upgrader]]
1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
2) At the "Do you want to start the upgrade?" question say Y.
3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
4) Press "Ctrl+C"
Your /etc/apt/sources.list file will now have focal in it instead of
bionic although the upgrade has quit. With the version of ubuntu-
release-upgrader in -proposed you will not see the "Ctrl+C" message. For
your sources.list file to be restored you'll need the version of apt
from bionic-proposed installed before starting the upgrade.
- [Where problems could occur]apt: This specific change removes the two
- lines that SIG_DFL the signal handlers after running scripts. AFAWCT
- those lines are unnecessary - the code that calls it temporarily sets
- the handlers to SIG_IGN but restores previous handlers at the end; it
- was wrongly refactored decades ago. A regression could occur in that
- those signals will now continue to be ignored if we missed a spot.
+ [Where problems could occur]
+ apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
+
+ ubuntu-release-upgrader: The change is wrapping a bunch of code in a
+ try: except: block so if the indentation was off the pyflakes /
+ pycodestyle tests would fail but autopkgtest will catch that.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through
an adequate pipe? Are you sitting with full batteries; better a power
supply?" would be convenient; since I am using my PC for urgent duties,
and didn't want to fiddle with unexpected upgrade bugs.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
In Progress
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upg
[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list
** Description changed:
[Impact]
Calling update() or installing packages from apt clients resets their SIGINT
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have
set for them.
In case of ubuntu-release-upgrader, this results in the release upgrader
being unable to handle interrupts after it did the initial update - the
default libc handler will run and the program exits.
[Test plan]
[[apt]]
As a standalone test for apt, we can test the following script:
import apt
import time
apt.Cache().update()
print("WAITING")
try:
- time.sleep(1)
+ time.sleep(1)
except BaseException as e:
- print("Seen", repr(e))
+ print("Seen", repr(e))
print("END")
Pressing Ctrl+C while WAITING is printed should print Seen
KeyboardInterrupt, and importantly, also the END line.
- [Where problems could occur]
- apt: This specific change removes the two lines that SIG_DFL the signal
handlers after running scripts. AFAWCT those lines are unnecessary - the code
that calls it temporarily sets the handlers to SIG_IGN but restores previous
handlers at the end; it was wrongly refactored decades ago. A regression could
occur in that those signals will now continue to be ignored if we missed a spot.
+ [[ubuntu-release-upgrader]]
+ 1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
+ 2) At the "Do you want to start the upgrade?" question say Y.
+ 3) When you see the "Lock screen disabled" message you will also see
"Inhibiting until Ctrl+C is pressed".
+ 4) Press "Ctrl+C"
+
+ Your /etc/apt/sources.list file will now have focal in it instead of
+ bionic although the upgrade has quit. With the version of ubuntu-
+ release-upgrader in -proposed you will not see the "Ctrl+C" message. For
+ your sources.list file to be restored you'll need the version of apt
+ from bionic-proposed installed before starting the upgrade.
+
+ [Where problems could occur]apt: This specific change removes the two
+ lines that SIG_DFL the signal handlers after running scripts. AFAWCT
+ those lines are unnecessary - the code that calls it temporarily sets
+ the handlers to SIG_IGN but restores previous handlers at the end; it
+ was wrongly refactored decades ago. A regression could occur in that
+ those signals will now continue to be ignored if we missed a spot.
[Original bug report]
As a long-time-user of ?ubuntu, with apt-get as tool of choice for
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu
version; just all packages including new ones. Version updates had to be
initiated manually, and I was always asked if I really wanted the new ?ubuntu
version. Sounds appropriate.
Last night when it (dist-upgrade), it just gave me 20.04. No questions asked.
I for one consider this kind of intrusive, though.
It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a
number of times earlier; just to *check* if the upgrade was on offer; but this
is only a guess.
In *any* case, a pop-up asking "Are you sure? Are you connected through
an adequate pipe? Are you sitting with full batteries; better a power
supply?" would be convenient; since I am using my PC for urgent duties,
and didn't want to fiddle with unexpected upgrade bugs.
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
+ ProblemType: BugDistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.25
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Oct 1 11:48:39 2020
InstallationDate: Installed on 2019-03-14 (566 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
- PackageArchitecture: all
- SourcePackage: ubuntu-release-upgrader
+ PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
VarLogDistupgradeAptlog:
Log time: 2020-09-29 19:44:28.696289
Log time: 2020-09-29 19:44:33.573481
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1898026
Title:
interruption of dist-upgrade can leave you next release in
sources.list
Status in apt package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Bionic:
New
Status in ubuntu-release-upgrader source package in Bionic:
New
Status in apt source package in Focal:
New
Status in ubuntu-release-upgrader source package in Focal:
In Progress
Status in apt source package in Groovy:
Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
[Touch-packages] [Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
#VERIFICATION BIONIC On a bionic machine that has PASSNO set to 0 for all entries, installed initramfs-tools from -proposed. # lsinitramfs /boot/initrd.img-5.9.0-rc5+ | grep fsck sbin/fsck.ext4 sbin/fsck sbin/e2fsck fsck utilities are included. ** Tags removed: verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy ** Tags added: verification-done verification-done-bionic verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
#VERIFICATION GROOVY On a groovy machine that has PASSNO set to 0 for all entries, installed initramfs-tools from -proposed. # lsinitramfs /boot/initrd.img-5.8.0-50-generic | grep fsck usr/sbin/e2fsck usr/sbin/fsck usr/sbin/fsck.ext4 fsck utilities are included. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0
#VERIFICATION FOCAL On a focal machine that has PASSNO set to 0 for all entries, installed initramfs-tools from -proposed. # lsinitramfs /boot/initrd.img-5.4.0-72-generic | grep fsck usr/sbin/e2fsck usr/sbin/fsck usr/sbin/fsck.ext4 fsck utilities are included. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1917780 Title: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0 Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in initramfs-tools source package in Focal: Fix Committed Status in initramfs-tools source package in Groovy: Fix Committed Bug description: [Impact] * initramfs-tools does not include fsck in initrd if MNT_PASS equals zero in the fstab entries. This has lead to the following situation : when dropping to initramfs shell during boot due to fs errors, we are not able to run fsck manually because it is not included in initrd. fsck should be included regardless of the MNT_PASS value. [Test Plan] * change /etc/fstab with PASSNO set to 0 for all entries * update-initramfs -u * lsinitramfs that is just generated * observe that it includes fsck utilities for the filesystems in /etc/fstab. I.e. fsck.ext4 e2fsck must exist [Where problems could occur] * The initramfs size will increase slightly upon upgrade, for the same initramfs-tools default options & kernel. However, one can control and remove fsck binaries (or include more of them) by setting FSTYPE variable in the initramfs settings. [scope] this is required for b/f/g this is fixed already in h and i [other info] debian MR is open: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+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 1928488] [NEW] Receiving error for /var/cache/apt/archives/fonts-noto-cjk compressed data is corrupt
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ???@???-OMEN:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking inSoftware Center ???-OMEN:~$ apt-cache policy fonts-noto-cjk fonts-noto-cjk: Installed: 1:20190410+repack1-2 Candidate: 1:20201206-cjk+repack1-1 Version table: 1:20201206-cjk+repack1-1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages *** 1:20190410+repack1-2 100 100 /var/lib/dpkg/status ???@???-OMEN:~$ apt-cache policy fonts-noto-extra fonts-noto-extra: Installed: 20200323-1build1 Candidate: 20201225-1build1 Version table: 20201225-1build1 500 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu hirsute/universe i386 Packages *** 20200323-1build1 100 100 /var/lib/dpkg/status 3) What you expected to happen I went to execute the upgrade from Ubuntu 21.03 to 21.04 and now cosistently receiving this error. 4) What happened instead Continually reciving this error whenever I run Software Update or APT UPGRADE ???@???-OMEN:~$ sudo apt upgrade -y Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: fonts-noto-cjk fonts-noto-extra 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/128 MB of archives. After this operation, 11.3 MB of additional disk space will be used. (Reading database ... 235767 files and directories currently installed.) Preparing to unpack .../fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb ... Unpacking fonts-noto-cjk (1:20201206-cjk+repack1-1) over (1:20190410+repack1-2) ... dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto -cjk_1%3a20201206-cjk+repack1-1_all.deb' (size=55140504) member 'data.tar': lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/fonts-noto-cjk_1%3a202012 06-cjk+repack1-1_all.deb (--unpack): cannot copy extracted data for './usr/share/fonts/opentype/noto/NotoSerifCJK-Bo ld.ttc' to '/usr/share/fonts/opentype/noto/NotoSerifCJK-Bold.ttc.dpkg-new': unex pected end of file or stream Preparing to unpack .../fonts-noto-extra_20201225-1build1_all.deb ... Unpacking fonts-noto-extra (20201225-1build1) over (20200323-1build1) ... dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/fonts-noto -extra_20201225-1build1_all.deb' (size=72415620) member 'data.tar': lzma error: compressed data is corrupt dpkg-deb: error: subprocess returned error exit status 2 dpkg: error processing archive /var/cache/apt/archives/fonts-noto-extra_20201225 -1build1_all.deb (--unpack): cannot copy extracted data for './usr/share/fonts/truetype/noto/NotoSerifGeorgi an-ExtraCondensed.ttf' to '/usr/share/fonts/truetype/noto/NotoSerifGeorgian-Extr aCondensed.ttf.dpkg-new': unexpected end of file or stream Errors were encountered while processing: /var/cache/apt/archives/fonts-noto-cjk_1%3a20201206-cjk+repack1-1_all.deb /var/cache/apt/archives/fonts-noto-extra_20201225-1build1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: apt 2.2.3 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 14 11:11:23 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - rvinger@rvinger-OMEN:~$ lsb_release -rd - Description: Ubuntu 21.04 - Release: 21.04 + ???@???-OMEN:~$ lsb_release -rd + Description: Ubuntu 21.04 + Release: 21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking inSoftware Center - rvinger@rvinger-OMEN:~$ apt-cache policy fonts-noto-cjk - fonts-noto-cjk: -Installed: 1:20190410+repack1-2 - Candidate: 1:20201206-cjk+repack1-1 - Version table: -1:20201206-cjk+repack1-1 500 -
Re: [Touch-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
Thank you for your information/times../ EH On Fri, May 14, 2021, 8:25 AM Dimitri John Ledkov < 1914...@bugs.launchpad.net> wrote: > sru-release comments: > > virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, > arm64) -> autopkgtest failures are a false negative. It only is built > and supported on amd64 > > sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in > focal > > zfs-linux/riscv64 - ftbfs is not a regression, never built on riscv64 in > focal > > iptables-netflow - needs 3 more days to age > > Thus everything is ready to be released to -updates & -security > > ** Changed in: acpi-call (Ubuntu) >Status: New => Fix Released > > ** Changed in: backport-iwlwifi-dkms (Ubuntu) >Status: New => Fix Released > > ** Changed in: zfs-linux (Ubuntu) >Status: New => Fix Released > > ** Changed in: virtualbox-hwe (Ubuntu) >Status: New => Fix Released > > ** Changed in: virtualbox (Ubuntu) >Status: New => Fix Released > > ** Changed in: v4l2loopback (Ubuntu) >Status: New => Fix Released > > ** Changed in: sysdig (Ubuntu) >Status: New => Fix Released > > ** Changed in: rtl8812au (Ubuntu) >Status: New => Fix Released > > ** Changed in: r8168 (Ubuntu) >Status: New => Fix Released > > ** Changed in: oss4 (Ubuntu) >Status: New => Fix Released > > ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) >Status: New => Fix Released > > ** Changed in: lttng-modules (Ubuntu) >Status: New => Fix Released > > ** Changed in: lime-forensics (Ubuntu) >Status: New => Fix Released > > ** Changed in: liblzf (Ubuntu) >Status: New => Fix Released > > ** Changed in: iptables-netflow (Ubuntu) >Status: New => Fix Released > > ** Changed in: gost-crypto (Ubuntu) >Status: New => Fix Released > > ** Changed in: evdi (Ubuntu) >Status: New => Fix Released > > ** Changed in: dm-writeboost (Ubuntu) >Status: New => Fix Released > > ** Changed in: dahdi-linux (Ubuntu) >Status: New => Fix Released > > ** Changed in: bcmwl (Ubuntu) >Status: New => Fix Released > > -- > You received this bug notification because you are subscribed to apt in > Ubuntu. > Matching subscriptions: dragonhahney > https://bugs.launchpad.net/bugs/1914279 > > Title: > linux from security may force reboots without complete dkms modules > > Status in acpi-call package in Ubuntu: > Fix Released > Status in apt package in Ubuntu: > Invalid > Status in backport-iwlwifi-dkms package in Ubuntu: > Fix Released > Status in bcmwl package in Ubuntu: > Fix Released > Status in dahdi-linux package in Ubuntu: > Fix Released > Status in dkms package in Ubuntu: > Fix Released > Status in dm-writeboost package in Ubuntu: > Fix Released > Status in evdi package in Ubuntu: > Fix Released > Status in gost-crypto package in Ubuntu: > Fix Released > Status in iptables-netflow package in Ubuntu: > Fix Released > Status in liblzf package in Ubuntu: > Fix Released > Status in lime-forensics package in Ubuntu: > Fix Released > Status in linux package in Ubuntu: > Triaged > Status in linux-meta package in Ubuntu: > Triaged > Status in lttng-modules package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Fix Released > Status in openafs package in Ubuntu: > New > Status in oss4 package in Ubuntu: > Fix Released > Status in r8168 package in Ubuntu: > Fix Released > Status in rtl8812au package in Ubuntu: > Fix Released > Status in sysdig package in Ubuntu: > Fix Released > Status in unattended-upgrades package in Ubuntu: > Invalid > Status in update-manager package in Ubuntu: > Invalid > Status in v4l2loopback package in Ubuntu: > Fix Released > Status in virtualbox package in Ubuntu: > Fix Released > Status in virtualbox-hwe package in Ubuntu: > Fix Released > Status in zfs-linux package in Ubuntu: > Fix Released > Status in acpi-call source package in Focal: > Fix Committed > Status in backport-iwlwifi-dkms source package in Focal: > Fix Committed > Status in bcmwl source package in Focal: > Fix Committed > Status in dahdi-linux source package in Focal: > Fix Committed > Status in dm-writeboost source package in Focal: > Fix Committed > Status in evdi source package in Focal: > Fix Committed > Status in gost-crypto source package in Focal: > Fix Committed > Status in iptables-netflow source package in Focal: > Fix Committed > Status in liblzf source package in Focal: > Fix Committed > Status in lime-forensics source package in Focal: > Fix Committed > Status in lttng-modules source package in Focal: > Fix Committed > Status in nvidia-graphics-drivers-340 source package in Focal: > Fix Committed > Status in oss4 source package in Focal: > Fix Committed > Status in r8168 source package in Focal: > Fix Committed > Status in rtl8812au source package in Focal: > Fix Committed > Status in sysdi
[Touch-packages] [Bug 1928481] [NEW] Please integrate cron with systemd instead of legacy /etc/init.d
Public bug reported: I would like to manage cron with standard systemd resources, such as "systemctl". Please integrate cron with systemd. As a workaround, I have to use raw /etc/init.d for this. ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1928481 Title: Please integrate cron with systemd instead of legacy /etc/init.d Status in cron package in Ubuntu: New Bug description: I would like to manage cron with standard systemd resources, such as "systemctl". Please integrate cron with systemd. As a workaround, I have to use raw /etc/init.d for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1928481/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: Cristian (christianmateescu) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cd
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
> It can be reproduced by running on a client:
>
> gdb --args ldapsearch -H ldaps://ldap.example.com -x
>
> Then in gdb:
>
> break write
> run
> continue
I can no longer reproduce it after I rebuild and install the libldap
package with
https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e
applied.
Note that since the above is enough to render slapd unresponsive for 15
minutes, it could be considered as a serious DoS vulnerability.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openldap (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
Confirmed
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1914279] Re: linux from security may force reboots without complete dkms modules
sru-release comments: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) -> autopkgtest failures are a false negative. It only is built and supported on amd64 sysdig/riscv64 - ftbfs is not a regression, never built on riscv64 in focal zfs-linux/riscv64 - ftbfs is not a regression, never built on riscv64 in focal iptables-netflow - needs 3 more days to age Thus everything is ready to be released to -updates & -security ** Changed in: acpi-call (Ubuntu) Status: New => Fix Released ** Changed in: backport-iwlwifi-dkms (Ubuntu) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox (Ubuntu) Status: New => Fix Released ** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Released ** Changed in: sysdig (Ubuntu) Status: New => Fix Released ** Changed in: rtl8812au (Ubuntu) Status: New => Fix Released ** Changed in: r8168 (Ubuntu) Status: New => Fix Released ** Changed in: oss4 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Fix Released ** Changed in: lttng-modules (Ubuntu) Status: New => Fix Released ** Changed in: lime-forensics (Ubuntu) Status: New => Fix Released ** Changed in: liblzf (Ubuntu) Status: New => Fix Released ** Changed in: iptables-netflow (Ubuntu) Status: New => Fix Released ** Changed in: gost-crypto (Ubuntu) Status: New => Fix Released ** Changed in: evdi (Ubuntu) Status: New => Fix Released ** Changed in: dm-writeboost (Ubuntu) Status: New => Fix Released ** Changed in: dahdi-linux (Ubuntu) Status: New => Fix Released ** Changed in: bcmwl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: Fix Released Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in bcmwl package in Ubuntu: Fix Released Status in dahdi-linux package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: Fix Released Status in evdi package in Ubuntu: Fix Released Status in gost-crypto package in Ubuntu: Fix Released Status in iptables-netflow package in Ubuntu: Fix Released Status in liblzf package in Ubuntu: Fix Released Status in lime-forensics package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: Fix Released Status in r8168 package in Ubuntu: Fix Released Status in rtl8812au package in Ubuntu: Fix Released Status in sysdig package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubunt
[Touch-packages] [Bug 1928475] [NEW] Xorg freeze when booting up
Public bug reported: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute ubuntu wayland-session -- 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/1928475 Title: Xorg freeze when booting up Status in xorg package in Ubuntu: New Bug description: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.ve
[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers
** Description changed: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h - $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz + $ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by apt 2.1.20. The build fails with: 0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of them is required for this operation The simple Dockerfile to reproduce the error - "docker build -t foo ." FROM amd64/ubuntu:hirsute MAINTAINER Florian Lohoff USER root RUN apt-get update \ && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \ && curl https://syncthing.net/release-key.txt | apt-key add - Breaking it down it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container. So adding keys in unpriviledged container or possibly kubernetes will not work anymore. Flo -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in Ubuntu on IBM z Systems: New Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in docke
[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Yes,
https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503
can't be directly applied there. There have been other changes in
between in that section including changes in API, so it would take more
effort to backport that fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
cherry picking
https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e
should fix this particular issue but reintroduce
https://bugs.openldap.org/show_bug.cgi?id=8650.
It may be necessary to pick
https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503
as well but as that's much more recent, I can't tell if it's valid on
top of the package used in bionic. I'm going to do some tests.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1926265
Title:
slapd enter in infinite loop on sched_yield syscall
Status in openldap package in Ubuntu:
New
Bug description:
On a production server, sometimes slapd become unbresponsive, some threads
loops in sched_yield syscall and consumme all CPU.
To recover, slapd needs to restart.
No related information is reported in log file.
All same issues in OpenLDAP upstream project are old and fixed.
So maybe this issue affects only Ubuntu package.
It occurs randomly, so I have no steps to reproduce.
OS : Bionic
Openldap version:
libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
libldap-common 2.4.45+dfsg-1ubuntu1.10
slapd 2.4.45+dfsg-1ubuntu1.10
Modules loaded:
olcModuleLoad: {0}back_bdb
olcModuleLoad: {1}syncprov
olcModuleLoad: {2}back_monitor
olcModuleLoad: {3}memberof.la
olcModuleLoad: {4}refint.la
olcModuleLoad: {5}rwm
olcModuleload: {6}back_ldap
Backend is BDB. slapd run in (single) master - (multi) slave mode.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1928346] Re: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
Hi Alex! Please refer to the below Image! [image: Screenshot from 2021-05-14 19-21-46.png] Regards, *Rajthilak R* / +91 91593 82738 - M.Sc., Information Technology Anna University, Chennai. India. On Fri, May 14, 2021 at 6:00 AM Alex Murray <1928...@bugs.launchpad.net> wrote: > Thanks for reporting this issue - can you please try running the > following in a terminal and see if this resolves the problem: > > sudo apt-get install -f --reinstall libseccomp2 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1928346 > > Title: > package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > > Status in libseccomp package in Ubuntu: > New > > Bug description: > Broken in mid of upgrade from 20.10 to 21.04 > > ProblemType: Package > DistroRelease: Ubuntu 21.04 > Package: libseccomp2:amd64 2.5.1-1ubuntu1 > ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 > Uname: Linux 5.8.0-53-generic x86_64 > ApportVersion: 2.20.11-0ubuntu50.6 > Architecture: amd64 > CasperMD5CheckResult: skip > Date: Thu May 13 19:56:07 2021 > ErrorMessage: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > InstallationDate: Installed on 2018-12-12 (883 days ago) > InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 > (20180731) > Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, > 3.8.6-0ubuntu1 > PythonDetails: N/A > RelatedPackageVersions: >dpkg 1.20.9ubuntu1 >apt 2.1.10ubuntu0.3 > SourcePackage: libseccomp > Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to > install/upgrade: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1928346/+subscriptions > ** Attachment added: "Screenshot from 2021-05-14 19-21-46.png" https://bugs.launchpad.net/bugs/1928346/+attachment/5497529/+files/Screenshot%20from%202021-05-14%2019-21-46.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1928346 Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libseccomp package in Ubuntu: New Bug description: Broken in mid of upgrade from 20.10 to 21.04 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libseccomp2:amd64 2.5.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu May 13 19:56:07 2021 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-12-12 (883 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.1.10ubuntu0.3 SourcePackage: libseccomp Title: package libseccomp2:amd64 2.5.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1928346/+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 1926265] Re: slapd enter in infinite loop on sched_yield syscall
The important backtrace in there is the one from thread 11: #0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 No symbol table info available. #2 0x7fb287895848 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #3 0x7fb28788f96a in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #4 0x7fb287896d03 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #5 0x7fb28789991c in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #6 0x7fb2878a10cb in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #7 0x7fb28789d572 in gnutls_handshake () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #8 0x7fb289304199 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 No symbol table info available. #9 0x7fb289301abb in ldap_pvt_tls_accept () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 No symbol table info available. #10 0x556b843e6f69 in connection_read (cri=, s=430) at ../../../../servers/slapd/connection.c:1375 debug symbols are missing there, but I have the exact same problem and get: #0 0x7f2a01101474 in __libc_read (fd=40, buf=0x7f29dc142ecb, nbytes=5) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f2a01db0518 in sb_debug_read (sbiod=0x7f29dc10e940, buf=0x7f29dc142ecb, len=5) at ../../../../libraries/liblber/sockbuf.c:829 #2 0x7f2a00558848 in _gnutls_stream_read (ms=0x7f29e8ffb41c, pull_func=0x7f2a01ff1da0 , size=5, bufel=, session=0x7f29dc008060) at buffers.c:344 #3 _gnutls_read (ms=0x7f29e8ffb41c, pull_func=0x7f2a01ff1da0 , size=5, bufel=, session=0x7f29dc008060) at buffers.c:424 #4 _gnutls_io_read_buffered (session=session@entry=0x7f29dc008060, total=5, recv_type=recv_type@entry=4294967295, ms=0x7f29e8ffb41c) at buffers.c:579 #5 0x7f2a0055296a in recv_headers (ms=, record=0x7f29e8ffb470, htype=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, type=GNUTLS_HANDSHAKE, record_params=0x7f29dc1279f0, session=0x7f29dc008060) at record.c:1045 #6 _gnutls_recv_in_buffers (session=session@entry=0x7f29dc008060, type=type@entry=GNUTLS_HANDSHAKE, htype=htype@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, ms=, ms@entry=0) at record.c:1173 #7 0x7f2a00559d03 in _gnutls_handshake_io_recv_int (session=session@entry=0x7f29dc008060, htype=htype@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, hsk=hsk@entry=0x7f29e8ffb580, optional=optional@entry=0) at buffers.c:1412 #8 0x7f2a0055c91c in _gnutls_recv_handshake (session=session@entry=0x7f29dc008060, type=type@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, optional=optional@entry=0, buf=buf@entry=0x7f29e8ffb830) at handshake.c:1465 #9 0x7f2a005640cb in _gnutls_recv_client_kx_message (session=session@entry=0x7f29dc008060) at kx.c:563 #10 0x7f2a00560572 in handshake_server (session=0x7f29dc008060) at handshake.c:3327 #11 gnutls_handshake (session=0x7f29dc008060) at handshake.c:2629 #12 0x7f2a01ff2199 in tlsg_session_accept (session=0x7f29dc1133f0) at tls_g.c:363 #13 0x7f2a01fefabb in ldap_pvt_tls_accept (sb=0x7f299c0051a0, ctx_arg=0x55d92cbca560) at tls2.c:425 and I've tracked it down to: https://bugs.openldap.org/show_bug.cgi?id=8650#c12 Basically, what we see is one thread stuck in a busy loop doing read()s on the TCP socket which all return immediately with EAGAIN as the fd is in non-blocking mode. In my cases, the client go offline just after sending the TLS client hello. That lasts for 15 minutes or about, probably until some timeout after which the TCP connection is eventually considered dead. It can be reproduced by running on a client: gdb --args ldapsearch -H ldaps://ldap.example.com -x Then in gdb: break write run continue Then the client is paused after sending the TLS "client hello". https://bugs.openldap.org/show_bug.cgi?id=8650#c12 explains that it's https://github.com/openldap/openldap/commit/7b5181da8cdd47a13041f9ee36fa9590a0fa6e48 that is responsible for the issue. https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e reverted that commit, but that one did not make it into bionic. So cherry picking https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e should fix it. ** Bug watch added: bugs.openldap.org/ #8650 https://bugs.openldap.org/show_bug.cgi?id=8650 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall Status in openldap package in Ubuntu: New Bug description: On a production server, sometimes slapd become unbresponsive, some threads loops in sched_yi
[Touch-packages] [Bug 1928470] [NEW] Duplicate image of Icons on Desktop
Public bug reported: After I upgraded to Hirsute Hippo the first time I opened the desktop I noticed that the desktop icons looked blurry. I tried to move them and then I realised that there was an image underneath the icon which replicated the icon image. These images could not be moved or deleted even if the desktop background was changed. Also on restarting they appeared under with new location of the icons. I deleted all the icons I could on the desktop via files and was just left with the default trash and home icons but the same problem still happened although the other icons were now completely gone. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 14:19:56 2021 DistUpgraded: 2021-05-14 12:54:25,361 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [1028:05bd] InstallationDate: Installed on 2021-03-06 (68 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Latitude E6440 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_wzumu3@/vmlinuz-5.11.0-17-generic root=ZFS=rpool/ROOT/ubuntu_wzumu3 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-14 (0 days ago) dmi.bios.date: 06/13/2019 dmi.bios.release: 65.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: A24 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6440 dmi.product.sku: 05BD dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105+git2105101700.cfbea7~oibaf~g version.libgl1-mesa-dri: libgl1-mesa-dri 21.2~git2105121014.7db79f~oibaf~g version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages ubuntu wayland-session -- 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/1928470 Title: Duplicate image of Icons on Desktop Status in xorg package in Ubuntu: New Bug description: After I upgraded to Hirsute Hippo the first time I opened the desktop I noticed that the desktop icons looked blurry. I tried to move them and then I realised that there was an image underneath the icon which replicated the icon image. These images could not be moved or deleted even if the desktop background was changed. Also on restarting they appeared under with new location of the icons. I deleted all the icons I could on the desktop via files and was just left with the default trash and home icons but the same problem still happened although the other icons were now completely gone. Thanks for your help. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 14:19:56 2021 DistUpgraded: 2021-05-14 12:54:25,361 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_p
[Touch-packages] [Bug 1927255] Re: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927255 Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted (20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got a Rodecaster Pro USB device that has been causing trouble before and already lead to quirk handling in the kernel for the sample rate, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/sound/usb/format.c?h=v5.8#n412 The Rodecaster is running fine on my laptop, but on my desktop, only audio input is working. The audio output is distorted. It's played kind of very slowly. Interestingly, if the source is a video file, the video plays slower, e.g. YouTube in a browser. I have never seen anything like that before. I have tried to figure out what the cause might be and I think I have reached the end of where I can get to on my own. I have documented most things at https://ubuntuforums.org/showthread.php?t=2461568 Putting my last step it in a nutshell: I have booted both my computers with a plain Ubuntu 21.04 from a pen drive (it uses kernel version 5.11.0-16-generic) to make sure it's not some different configuration that I have set up over the years on my systems (both Ubuntu 20.04 with kernel 5.8.18). I attached the Rodecaster. It runs fine on my laptop, but not on my desktop (used the output test from). I then detected the card number with aplay -l I killed pulseaudio with pulseaudio -k I then played the same sample (encoded in 48000 Hz in PCM signed 32 bit little endian format) using aplay -f S32_LE -c 2 -r 48000 -D hw:x ~/sample.wav where x is the appropriate card number and the rest of the arguments meet the Rodecaster's narrow specification. It's playing fine on the laptop, but distorted on the desktop. As far as I understand using aplay this way without a plugin should send the file directly to the device, so I assume there's something on the way from aplay to the Rodecaster that's interfering (kernel or even some piece of hardware) - and that definitely is where my expertise ends (rather a little before :-)). I'll gladly contribute any information that could be useful and I will willingly help to debug this problem if it may be related to the kernel. If there's anything I can do, please let me know. Cheers, Oliver ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.18-050818-generic x86_64 NonfreeKernelModules: blackmagic_io nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed May 5 18:28:46 2021 InstallationDate: Installed on 2020-05-15 (355 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Pro failed Symptom_Card: RODECaster Pro - RODECaster Pro Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - RODECaster Pro, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.40 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1927255/+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 1928338] Re: package openssh-client 1:8.4p1-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
Hi jitmanyu, Thanks for taking the time to report the bug. However, I can't seem to reproduce this in a Focal container. I tried to install openssh-client (and openssh-server) as well, tried to play with it for a while, removed it, re-installed; then purged it, re-installed again, but can't seem to reproduce the issue that you're quite facing? I wonder if this is an issue because of some local config issue or something? If so, you can find assistance here: http://www.ubuntu.com/support/community. And I also wonder if simply reinstalling the openssh-client will fix the problem you're facing? cf: apt reinstall openssh-client or equivalent? However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New" again. Thanks, again! ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1928338 Title: package openssh-client 1:8.4p1-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssh package in Ubuntu: Incomplete Bug description: ef ProblemType: Package DistroRelease: Ubuntu 21.04 Package: openssh-client 1:8.4p1-5ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu May 13 18:03:15 2021 DuplicateSignature: package:openssh-client:1:8.4p1-5ubuntu1 Setting up gnome-shell-extension-desktop-icons (20.04.0+git20200908-5build1) ... dpkg: error processing package openssh-client (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-12-30 (134 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_8.4p1 Ubuntu-5ubuntu1, OpenSSL 1.1.1j 16 Feb 2021 SourcePackage: openssh Title: package openssh-client 1:8.4p1-5ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1928338/+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 1902898] Re: power-button action inconsistent between user session and greeter
Hello dann, or anyone else affected, Accepted ubuntu-settings into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/20.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-settings (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Committed Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal&id=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => Cristian (christianmateescu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Fix Released Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for /cd
[Touch-packages] [Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
** Changed in: db5.3 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable Status in db5.3 package in Ubuntu: Fix Committed Bug description: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+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 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Thank you, LGTM! $ dput ubuntu ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes D: Setting host argument. Checking signature on .changes gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes: Valid signature from 5889C17AB1C8D890 Checking signature on .dsc gpg: ../db5.3_5.3.28+dfsg1-0.8ubuntu1.dsc: Valid signature from 5889C17AB1C8D890 Uploading to ubuntu (via sftp to upload.ubuntu.com): Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1.dsc: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1.debian.tar.xz: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1_source.buildinfo: done. Uploading db5.3_5.3.28+dfsg1-0.8ubuntu1_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to db5.3 in Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable Status in db5.3 package in Ubuntu: New Bug description: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+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 1928421] Re: OBS recorder software shows black screen and records blank screen
*** This bug is a duplicate of bug 1838967 *** https://bugs.launchpad.net/bugs/1838967 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1838967, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => obs-studio (Ubuntu) ** Summary changed: - OBS recorder software shows black screen and records blank screen + OBS recorder software shows black screen and records blank screen in Wayland sessions ** This bug has been marked a duplicate of bug 1838967 OBS Studio (from APT) records black screen instead of image in Wayland sessions -- 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/1928421 Title: OBS recorder software shows black screen and records blank screen in Wayland sessions Status in obs-studio package in Ubuntu: New Bug description: something is very much wrong with the whole wayland thing. Needs a lot of improvements. Every ubuntu upgrade is like a downgrade. Creates more problem than it solves . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:38:09 2021 DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] InstallationDate: Installed on 2016-11-07 (1648 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) dmi.bios.date: 12/27/2016 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 73.16 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: 1JH54PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Mar 31 09:20:55 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1928421/+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 1928420] Re: Dual pointers and tracking speed slow from wacom tablet
** 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/1928420 Title: Dual pointers and tracking speed slow from wacom tablet Status in xorg package in Ubuntu: New Bug description: As soon as I plug in my wacom tablet. There are two pointers. The real problem is after upgrading to ubuntu 21.04 The tracking speed from tablet i.e., pointer speed or pen speed is very slow. Please help with the adjustment of pointer speed from tablet. It might be wayland problem but we need adjustment option to work on the creative apps. Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:08:16 2021 DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] InstallationDate: Installed on 2016-11-07 (1648 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) dmi.bios.date: 12/27/2016 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 73.16 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: 1JH54PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Mar 31 09:20:55 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928420/+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 1928421] Re: OBS recorder software shows black screen and records blank screen
** 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/1928421 Title: OBS recorder software shows black screen and records blank screen Status in xorg package in Ubuntu: New Bug description: something is very much wrong with the whole wayland thing. Needs a lot of improvements. Every ubuntu upgrade is like a downgrade. Creates more problem than it solves . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:38:09 2021 DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] InstallationDate: Installed on 2016-11-07 (1648 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) dmi.bios.date: 12/27/2016 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 73.16 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: 1JH54PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Mar 31 09:20:55 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928421/+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 1928420] [NEW] Dual pointers and tracking speed slow from wacom tablet
You have been subscribed to a public bug: As soon as I plug in my wacom tablet. There are two pointers. The real problem is after upgrading to ubuntu 21.04 The tracking speed from tablet i.e., pointer speed or pen speed is very slow. Please help with the adjustment of pointer speed from tablet. It might be wayland problem but we need adjustment option to work on the creative apps. Thanks ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:08:16 2021 DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] InstallationDate: Installed on 2016-11-07 (1648 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) dmi.bios.date: 12/27/2016 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 73.16 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: 1JH54PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Mar 31 09:20:55 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- Dual pointers and tracking speed slow from wacom tablet https://bugs.launchpad.net/bugs/1928420 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 1928421] [NEW] OBS recorder software shows black screen and records blank screen
You have been subscribed to a public bug: something is very much wrong with the whole wayland thing. Needs a lot of improvements. Every ubuntu upgrade is like a downgrade. Creates more problem than it solves . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:38:09 2021 DistUpgraded: 2021-05-13 15:59:12,750 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] InstallationDate: Installed on 2016-11-07 (1648 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-13 (0 days ago) dmi.bios.date: 12/27/2016 dmi.bios.release: 15.35 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 73.16 dmi.modalias: dmi:bvnInsyde:bvrF.23:bd12/27/2016:br15.35:efr73.16:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: 1JH54PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Mar 31 09:20:55 2021 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.9-2ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- OBS recorder software shows black screen and records blank screen https://bugs.launchpad.net/bugs/1928421 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 1928327] Re: logrotate on 20.04 is ancient and misses important bugfixes
Frankly that went over my head, so unsure how to respond. :) I used a VM to test (manually updating by installing a deb) and all issues disappeared - that was my "test". I suppose that's not good enough according to your comment. Perhaps let's just close this issue? I'll need to wait for ubuntu 22. (BTW: when you work on a new ubuntu version, do you just upgrade to the latest package version, or do you follow the same approach you explained above? i.e. you never just upgrade to "latest".) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1928327 Title: logrotate on 20.04 is ancient and misses important bugfixes Status in logrotate package in Ubuntu: New Bug description: Ubuntu focal/20.04 has logrotate version 3.14.0 which is ancient. There have been multiple important bugfixes since then (https://github.com/logrotate/logrotate/releases). Ubuntu hirsute/21.04 does include the latest version, but that isn't an LTS version, so is not an option for many of us. Please consider adding the latest version to the 20.04 apt repository? (I'm aware of workarounds such as installing manually, building from source, etc. But like most users I prefer to rely on the apt repositories.) Thanks!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1928327/+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
