[Touch-packages] [Bug 1910584] [NEW] ifup is iterating over all vlan sub vlan interfaces for ens interfaces
You have been subscribed to a public bug: I expect that a single ifup call with just one vlan interface will NOT bring up all sub vlan interfaces too but on my ubuntu 18.04.02 I do see this root@dsr-router-1:~# ifup ens19.2023 ens19.2023 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config ens19.2023.4 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 4 to IF -:ens19.2023:- ens19.2023.4090 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Added VLAN with VID == 4090 to IF -:ens19.2023:- root@dsr-router-1:~# more is written at> https://askubuntu.com/questions/1305801 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ifup is iterating over all vlan sub vlan interfaces for ens interfaces https://bugs.launchpad.net/bugs/1910584 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown 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 1846180] Re: 1910 software-properties larger screen size
I changed respective translations to shorter ones. They should be available in Focal with next language pack's update. Russian Ubuntu Translators don't forget to test it, more info: https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Russian Ubuntu Translators (ubuntu-l10n-ru) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1846180 Title: 1910 software-properties larger screen size Status in software-properties package in Ubuntu: Fix Committed Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Screen size 1366x768, Russian language. Update settings go beyond the edge of the screen. The window cannot be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1846180/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
my problem is I think likely better covered by https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709 -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] python3-apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] python3-distupgrade/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] python3-problem-report/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] systemd-sysv/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] ubuntu-release-upgrader-core/bionic-updates 1:18.04.28 all [upgradable from: 1:18.04.27] udev/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] root@uu-systemd-onshutdown:~# reboot Session terminated, terminating shell...Terminated root@uu-systemd- rbalint@yogi:~$ rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# tail /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Preparing to unpack .../libsystemd0_237-3ubuntu10.6_amd64.deb ... Unpacking libsystemd0:amd64 (237-3ubuntu10.6) over (237-3ubuntu10.3) ... Setting up libsystemd0:amd64 (237-3ubuntu10.6) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up systemd (237-3ubuntu10.6) ... Failed to try-restart systemd-networkd.service: Transaction is destructive. See system logs and 'systemctl status systemd-networkd.service' for
[Touch-packages] [Bug 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
TTFN: To add to (and correct) my earlier comments: after the updating shown there, the machine had to be rebooted manually. Checking /var/log/apt/term.log it appears that the upgrade did complete successfully: Log started: 2021-01-07 13:28:19 (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... Setting up libnss-systemd:i386 (237-3ubuntu10.43) ... Setting up libpam-systemd:i386 (237-3ubuntu10.43) ... Processing triggers for libc-bin (2.27-3ubuntu1.4) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for dbus (1.12.2-1ubuntu1.2) ... Processing triggers for ureadahead (0.100.0-21) ... Log ended: 2021-01-07 13:29:10 ... this even though the (ssh) interface died at the point where systemd was being set up. The system now runs systemd 237-3ubuntu10.43. But based on past experience I think the same thing will happen the next time there is a version upgrade of systemd. -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libudev1/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] lxd/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] lxd-client/bionic-updates 3.0.2-0ubuntu1~18.04.1 amd64 [upgradable from: 3.0.1-0ubuntu1~18.04.1] openssh-client/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4] openssh-sftp-server/bionic-updates,bionic-security 1:7.6p1-4ubuntu0.1 amd64 [upgradable from: 1:7.6p1-4]
[Touch-packages] [Bug 1867147] Re: Failed to add UUID: Busy (0x0a)
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1867147 Title: Failed to add UUID: Busy (0x0a) Status in bluez package in Ubuntu: Expired Bug description: dmesg Bluetooth: hci0: command 0x0c24 tx timeout rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: hci1: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: no bluetoothctl Failed to start discovery: org.bluez.Error.InProgress lsusb Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) lshw *-usb descrição: USB controller produto: Cannon Lake PCH USB 3.1 xHCI Host Controller fabricante: Intel Corporation ID físico: 14 informações do barramento: pci@:00:14.0 versão: 10 largura: 64 bits clock: 33MHz capacidades: pm msi xhci bus_master cap_list configuração: driver=xhci_hcd latency=0 recursos: irq:124 memória:eb22-eb22 *-usbhost:0 produto: xHCI Host Controller fabricante: Linux 5.3.0-40-generic xhci-hcd ID físico: 0 informações do barramento: usb@1 nome lógico: usb1 versão: 5.03 capacidades: usb-2.00 configuração: driver=hub slots=16 speed=480Mbit/s *-usb:0 descrição: Interface sem fio bluetooth produto: JL AC69 A10 fabricante: Cambridge Silicon Radio, Ltd ID físico: 1 informações do barramento: usb@1:1 versão: 25.20 capacidades: bluetooth usb-2.00 configuração: driver=btusb maxpower=100mA speed=12Mbit/s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.3 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:18:43 2020 InstallationDate: Installed on 2019-06-19 (266 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP EliteDesk 800 G4 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=885446d9-2945-4958-a7f0-1eadecf23697 ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q01 Ver. 02.06.03 dmi.board.name: 83E1 dmi.board.vendor: HP dmi.board.version: KBC Version 07.D2.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ01Ver.02.06.03:bd02/15/2019:svnHP:pnHPEliteDesk800G4SFF:pvr:rvnHP:rn83E1:rvrKBCVersion07.D2.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G4 SFF dmi.product.sku: 5ZA60LP#AC4 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1867147/+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 1902907] Re: Developer Options shows 'groovy-proposed' instead of 'hirsute-proposed' (software-properties-gtk on 21.04 Hirsute Hippo)
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902907 Title: Developer Options shows 'groovy-proposed' instead of 'hirsute- proposed' (software-properties-gtk on 21.04 Hirsute Hippo) Status in software-properties package in Ubuntu: Expired Bug description: When testing Hirsute Hippo (21.04), I found that software-properties- gtk shows 'groovy-proposed' instead of 'hirsute-proposed'. This is from a live session in VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Nov 4 16:16:14 2020 LiveMediaBuild: Ubuntu Unity 21.04 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1902907/+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 1910636] [NEW] update icu-data which is bundled in tzdata to 2020f
Public bug reported: The 2020f upload of tzdata did not include an update of the ICU timezone data because it was not yet up to date. It has now been updated so we should update tzdata with that new information. tzdata (2020f-1ubuntu1) hirsute; urgency=medium * Merge from Debian unstable (LP: 1909698). Remaining changes: - Ship ICU timezone data files which are utilized by php and keep them at 2020d as they have not yet been updated. ** Affects: tzdata (Ubuntu) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Focal) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Groovy) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Affects: tzdata (Ubuntu Hirsute) Importance: Undecided Assignee: Brian Murray (brian-murray) Status: In Progress ** Also affects: tzdata (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: tzdata (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: tzdata (Ubuntu Hirsute) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Groovy) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Focal) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: tzdata (Ubuntu Hirsute) Status: New => In Progress ** Changed in: tzdata (Ubuntu Groovy) Status: New => In Progress ** Changed in: tzdata (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1910636 Title: update icu-data which is bundled in tzdata to 2020f Status in tzdata package in Ubuntu: In Progress Status in tzdata source package in Focal: In Progress Status in tzdata source package in Groovy: In Progress Status in tzdata source package in Hirsute: In Progress Bug description: The 2020f upload of tzdata did not include an update of the ICU timezone data because it was not yet up to date. It has now been updated so we should update tzdata with that new information. tzdata (2020f-1ubuntu1) hirsute; urgency=medium * Merge from Debian unstable (LP: 1909698). Remaining changes: - Ship ICU timezone data files which are utilized by php and keep them at 2020d as they have not yet been updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1910636/+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 1910537] Re: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI
> Their guess is that the linux notebook is not setting EDID > configuration correctly and thus not recognized by the ATEM, > while the cheap LCD screen propably does not care about EDID > and just plays everything, therefore a wrong EDID information > would not matter. EDIDs work the other way round. An EDID is not "set" by Linux. It is hard-coded in the monitor and only read by the computer. However it is sadly common for monitor manufacturers (probably not Blackmagic) to ship monitors that advertise faulty EDID data. That's probably what an "EDID manager" is to fix, but I don't know of and have no experience with any on Linux. I would like to analyse the EDID being advertised by your ATEM, but Xrandr.txt seems to show it was not plugged into HDMI when you logged this bug. Please plug it in and then run: xrandr --verbose > xrandr2.txt and attach the resulting file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910537 Title: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI Status in Ubuntu: Incomplete Bug description: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
[Touch-packages] [Bug 1910538] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 ** This bug is no longer a duplicate of bug 1910539 [nvidia] Cannot set scale of screen ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- 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/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1910538/+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 1910539] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1870736 *** https://bugs.launchpad.net/bugs/1870736 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 1870736, 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. ** Tags added: nvidia xrandr-scaling ** Summary changed: - Cannot set scale of screen + [nvidia] Cannot set scale of screen ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** This bug has been marked a duplicate of bug 1870736 [nvidia] Screen scaling 125% gives 200% -- 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/1910539 Title: [nvidia] Cannot set scale of screen Status in mutter package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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:
[Touch-packages] [Bug 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.16.04 --- tzdata (2020f-0ubuntu0.16.04) xenial; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. -- Brian Murray Wed, 06 Jan 2021 08:24:52 -0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.16.04 --- tzdata (2020f-0ubuntu0.16.04) xenial; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. -- Brian Murray Wed, 06 Jan 2021 08:24:52 -0800 ** Changed in: tzdata (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Released Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.18.04 --- tzdata (2020f-0ubuntu0.18.04) bionic; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. -- Brian Murray Wed, 06 Jan 2021 08:11:57 -0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.18.04 --- tzdata (2020f-0ubuntu0.18.04) bionic; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. -- Brian Murray Wed, 06 Jan 2021 08:11:57 -0800 ** Changed in: tzdata (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: tzdata (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Released Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1713017] Re: Enable MIDI support
as far as I can see in the bluez package source, the midi option is enabled now, so it *could* be closed... But even though it's on, I dont get it working, so I cannot confirm for sure. Expectation is: when connecting to a device, I get an alsa sequencer client, but I dont see that happening. But also I am not sure if I use it correctly, as i see nearly no documentation about it, despite one place that said what I mentioned above in what I expect to happen. I dont even know for sure if this direction is supposed to be unidirectional or bi-directional. (e.g. if my laptop can be the midi host, device or both). I'll keep trying. If anyone has a pointer to docs how it is really supposed to work, so i can confirm, it would be helpful and this ticket could be closed. -- 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/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.04 --- tzdata (2020f-0ubuntu0.20.04) focal; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. * ICU timezone data files are still version 2020d as they have not yet been updated by upstream. -- Brian Murray Tue, 05 Jan 2021 16:30:37 -0800 ** Changed in: tzdata (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Released Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1647285] Re: SSL trust not system-wide
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sssd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1647285 Title: SSL trust not system-wide Status in ca-certificates package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nss package in Ubuntu: Confirmed Status in p11-kit package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: When I install a corporate CA trust root with update-ca-certificates, it doesn't seem to work everywhere. Various things like Firefox, Evolution, Chrome, etc. all fail to trust the newly-installed trusted CA. This ought to work, and does on other distributions. In p11-kit there is a module p11-kit-trust.so which can be used as a drop-in replacement for NSS's own libnssckbi.so trust root module, but which reads from the system's configured trust setup instead of the hard- coded version. This allows us to install the corporate CAs just once, and then file a bug against any package that *doesn't* then trust them. See https://fedoraproject.org/wiki/Features/SharedSystemCertificates for some of the historical details from when this feature was first implemented, but this is all now supported upstream and not at all distribution-specific. There shouldn't be any significant work required; it's mostly just a case of configuring and building it to make use of this functionality. (With 'alternatives' to let you substitute p11-kit-trust.so for the original NSS libnssckbi.so, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1647285/+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 1909698] Update Released
The verification of the Stable Release Update for tzdata has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-0ubuntu0.20.10 --- tzdata (2020f-0ubuntu0.20.10) groovy; urgency=medium * New upstream version (LP: #1909698), affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. * ICU timezone data files are still version 2020d as they have not yet been updated by upstream. -- Brian Murray Tue, 05 Jan 2021 16:08:38 -0800 ** Changed in: tzdata (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Released Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message
** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910604 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.12, the problem page at https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910604/+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 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message
This is a variation of LP: #1899195 however in this case the executable path has a space in the name e.g. /usr/lib/plexmediaserver/Plex Media Server which ends up being split into multiple arguments: ['/usr/share/apport/apport', '1700', '11', '0', '1', '1700', '!usr!lib!plexmediaserver!Plex', 'Media', 'Server'] Which is more than apport expects. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910604 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.12, the problem page at https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910604/+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 1910604] Re: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message
Here's the Traceback: Traceback (most recent call last): File "/usr/share/apport/apport", line 458, in options = parse_arguments() File "/usr/share/apport/apport", line 404, in parse_arguments parser.print_usage() File "/usr/lib/python3.6/argparse.py", line 2370, in print_usage self._print_message(self.format_usage(), file) File "/usr/lib/python3.6/argparse.py", line 2381, in _print_message file.write(message) AttributeError: 'NoneType' object has no attribute 'write' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910604 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.12, the problem page at https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910604/+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 1910604] [NEW] /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.12, the problem page at https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1910604 Title: /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@458:parse_arguments:print_usage:_print_message Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu27.12, the problem page at https://errors.ubuntu.com/problem/9b24bfd33f42cf15ca4956317629b13c340448e4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1910604/+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: apt (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: apt (Ubuntu Focal) Status: Triaged => Fix Committed ** Changed in: apt (Ubuntu Groovy) Status: Triaged => Fix Released ** Changed in: apt (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: apt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Unknown 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. So what we do is change that to a warning. [Test case] Not available right now. Issues can flare up and then disappear again. [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 /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: '1.1.4-1build1' not found." /plugininstall.py: Downloads verified successfully ubiquity: Error in function: install /plugininstall.py: Exception during installation: /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) /plugininstall.py: ProblemType: Bug DistroRelease:
[Touch-packages] [Bug 997737] Re: Detroit is not in Canada, 12.04
Still a bug in 20.04, evident when installing Linux Mint 20. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/997737 Title: Detroit is not in Canada, 12.04 Status in tzdata package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: I installed Ubuntu 12.04 over the weekend. When it asked me to select my location or time zone or whatever, I selected Detroit, Michigan, Eastern Time Zone. When I booted up, I saw that my locale settings were for Canada, rather than the US. So, I had Canadian date format, units, and currency. I changed it to US per this askubuntu thread: http://askubuntu.com/questions/133011/set-default-language-to-english-us-in-12-04 Not sure where this geography information is stored, but this fixed the problem for me after the fact. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/997737/+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 1867400] Re: apport crashed with AttributeError in _print_message(): 'NoneType' object has no attribute 'write'
*** This bug is a duplicate of bug 1899195 *** https://bugs.launchpad.net/bugs/1899195 ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1899195 /usr/share/apport/apport:AttributeError:/usr/share/apport/apport@451:parse_arguments:print_usage:_print_message -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1867400 Title: apport crashed with AttributeError in _print_message(): 'NoneType' object has no attribute 'write' Status in apport package in Ubuntu: New Bug description: d ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu20 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CrashReports: 640:0:119:25768:2020-03-13 16:01:33.222412109 -0600:2020-03-13 16:01:34.222412109 -0600:/var/crash/_usr_share_apport_apport.0.crash Date: Fri Mar 13 16:01:34 2020 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2018-02-07 (765 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 1383 11 0 1 1383 !usr!bin!gnome-shell (deleted) ProcEnviron: Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/share/apport/apport', '1383', '11', '0', '1', '1383', '!usr!bin!gnome-shell', '(deleted)'] PythonDetails: N/A SourcePackage: apport Title: apport crashed with AttributeError in _print_message(): 'NoneType' object has no attribute 'write' UpgradeStatus: Upgraded to focal on 2020-03-13 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1867400/+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 1909698] Re: new upstream release 2020f
This bug was fixed in the package tzdata - 2020f-1ubuntu1 --- tzdata (2020f-1ubuntu1) hirsute; urgency=medium * Merge from Debian unstable (LP: #1909698). Remaining changes: - Ship ICU timezone data files which are utilized by php and keep them at 2020d as they have not yet been updated. tzdata (2020f-1) unstable; urgency=medium * New upstream version with no impact on the content of the debian package, except for the version number. tzdata (2020e-1) unstable; urgency=medium * New upstream version, affecting the following future timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. -- Brian Murray Tue, 05 Jan 2021 14:17:21 -0800 ** Changed in: tzdata (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1909698 Title: new upstream release 2020f Status in tzdata package in Ubuntu: Fix Released Status in tzdata source package in Xenial: Fix Committed Status in tzdata source package in Bionic: Fix Committed Status in tzdata source package in Focal: Fix Committed Status in tzdata source package in Groovy: Fix Committed Bug description: New upstream version, affecting the following timestamp: - Volgograd switches to Moscow time on 2020-12-27 at 02:00. The ICU timezone data has not yet been updated upstream so those changes will be included in a later SRU. Verification is done with 'zdump'. The first timezone that gets changed in the updated package is dumped with "zdump -v $region/$timezone_that_changed" (this needed to be greped for in /usr/share/zoneinfo/). [For example: "zdump -v Africa/Casablanca".] This is compared to the same output after the updated package got installed. If those are different the verification is considered done. $region/$timezone = Europe/Volgograd Additionally, an upstream update of tzdata removed the "old" SystemV timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier releases. Subsequently, these should be checked for using the following: diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-) Nothing should be returned by the above command. [Original Description] https://www.iana.org/time-zones tzdata 2020f already exists, please update the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1909698/+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 1907850] Re: Cache not generated for all translations
** Tags removed: rls-hh-incoming ** Also affects: apt (Ubuntu Hirsute) Importance: Undecided Status: Confirmed -- 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/1907850 Title: Cache not generated for all translations Status in apt package in Ubuntu: Confirmed Status in apt source package in Hirsute: Confirmed Bug description: [Impact] In bug 1161743 we discovered that if a system is configured with multiple locales, only the locales of the user who generated the apt-cache will be available for translated descriptions. [Test case] # apt install locales-all # get the locale # export LANG=sv_SE.UTF-8 # locale LANG=sv_SE.UTF-8 LANGUAGE= LC_CTYPE="sv_SE.UTF-8" LC_NUMERIC="sv_SE.UTF-8" LC_TIME="sv_SE.UTF-8" LC_COLLATE="sv_SE.UTF-8" LC_MONETARY="sv_SE.UTF-8" LC_MESSAGES="sv_SE.UTF-8" LC_PAPER="sv_SE.UTF-8" LC_NAME="sv_SE.UTF-8" LC_ADDRESS="sv_SE.UTF-8" LC_TELEPHONE="sv_SE.UTF-8" LC_MEASUREMENT="sv_SE.UTF-8" LC_IDENTIFICATION="sv_SE.UTF-8" LC_ALL= # apt update # apt-cache show tasksel | grep Desc Description-sv: tool for selecting tasks for installation on Debian systems Description-md5: cbbb747708986d11ea77c80b9b038fec # apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: sv File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec [...] So far so good, but now assume the root user actually has C configured as locale, and e.g. runs apt-cache show (or apt-daily.service does an update): root@g:~# rm /var/cache/apt/*.bin root@g:~# LANG=C apt-cache show tasksel [...] Description-en: tool for selecting tasks for installation on Debian systems This package provides 'tasksel', a simple interface for users who want to configure their system to perform a specific task. root@g:~# apt-cache showpkg tasksel Package: tasksel Versions: 3.34ubuntu16 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages MD5: cbbb747708986d11ea77c80b9b038fec Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en MD5: cbbb747708986d11ea77c80b9b038fec This should show the sv locale as well given that it's still around (also we are still running with LANG=sv_SE.UTF-8), but it only generated the cache with the english language description in here. [Where problems could occur] Unknown so far, we've not investigated the cause or solution yet. [Other Info] N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1907850/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
** Merge proposal linked:
https://code.launchpad.net/~fheimes/ubuntu/+source/elfutils/+git/elfutils/+merge/395949
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
In Progress
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
In Progress
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1910576] [NEW] [MIR] libbpf (dependency of iproute2)
Public bug reported: [MIR] libbpf (dependency of iproute2) ** Affects: iproute2 (Ubuntu) Importance: High Assignee: Kernel Packages (kernel-packages) Status: New ** Affects: libbpf (Ubuntu) Importance: High Assignee: Kernel Packages (kernel-packages) Status: Incomplete ** Tags: hirsute rls-hh-incoming ** Also affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu) Importance: Undecided => High ** Changed in: libbpf (Ubuntu) Importance: Undecided => High ** Tags added: rls-hh-incoming ** Changed in: iproute2 (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) ** Changed in: libbpf (Ubuntu) Assignee: (unassigned) => Kernel Packages (kernel-packages) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: New Status in libbpf package in Ubuntu: Incomplete Bug description: [MIR] libbpf (dependency of iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1907956] Re: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install
** Also affects: ubiquity (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags removed: rls-hh-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1907956 Title: ubiquity crash on whoopsie removal, Xubuntu 21.04 minimal install Status in ubiquity package in Ubuntu: New Status in whoopsie package in Ubuntu: New Status in ubiquity source package in Hirsute: New Status in whoopsie source package in Hirsute: New Bug description: Xubuntu hirsute 20201213 minimal install crashed on whoopsie removal but finished installing. This is 1907951 with hopefully more crash information. Related logs identified: Dec 13 12:37:05 xubuntu ubiquity: Purging configuration files for whoopsie (0.2.73) ... Dec 13 12:37:05 xubuntu ubiquity: #015 Dec 13 12:37:05 xubuntu ubiquity: Running in chroot, ignoring command 'daemon-reload'#015 Dec 13 12:37:05 xubuntu ubiquity: message repeated 2 times: [ Running in chroot, ignoring command 'daemon-reload'#015] Dec 13 12:37:05 xubuntu ubiquity: rm: Dec 13 12:37:05 xubuntu ubiquity: cannot remove '/var/lib/whoopsie/whoopsie-id' Dec 13 12:37:05 xubuntu ubiquity: : No such file or directory Dec 13 12:37:05 xubuntu ubiquity: #015 Dec 13 12:37:05 xubuntu ubiquity: dpkg: error processing package whoopsie (--purge): Dec 13 12:37:05 xubuntu ubiquity: #015 Dec 13 12:37:05 xubuntu ubiquity: installed whoopsie package post-removal script subprocess returned error exit status 1 Dec 13 12:37:05 xubuntu ubiquity: #015 Looks like it's a bug in the postrm script: #! /bin/sh set -e #DEBHELPER# if [ "$1" = "purge" ]; then deluser --quiet --system whoopsie > /dev/null || true chmod g-s /var/crash >/dev/null 2>&1 chgrp root /var/crash >/dev/null 2>&1 rm /var/lib/whoopsie/whoopsie-id >/dev/null fi exit 0 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.3 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.456 Date: Sun Dec 13 07:40:33 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201213) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1907956/+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 1910567] [NEW] Wget cannot download from ftp.gnu.org using Let's Encrypt R3 CA certificate
Public bug reported:
I'm working on Ubuntu 18.05, x86_64, fully patched. The system has been
through both apt-get upgrade and dist-upgrade. The system provides Wget
1.19.4
The program below fails to download from ftp.gnu.org using Let's Encrypt
R3 CA certificate. Let's Encrypt R3 is the issuer for ftp.gnu.org. It is
about the best trust anchor you can choose (sans pinning the host's
public key).
If I use Daniel Stenberg's cacert.pem
(https://curl.haxx.se/docs/caextract.html), then the download succeeds.
I'm not a fan of using the CA Zoo when I know the Issuing CA in advance.
There's no reason to trust every PKI in the world.
If I use a newer version of Wget built with an OpenSSL backend, then the
download succeeds. For example, Wget 1.20.3 and Wget 1.21 with an
OpenSSL backend work fine.
-
$ ./wget-test.sh
Failed to download Ncurses
# Hmm... Add --debug to Wget command
$ ./wget-test.sh
Setting --quiet (quiet) to 1
Setting --quiet (quiet) to 1
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --output-document (outputdocument) to ncurses-6.1.tar.gz
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
Setting --ca-certificate (cacertificate) to lets-encrypt-roots.pem
DEBUG output created by Wget 1.19.4 on linux-gnu.
Reading HSTS entries from /home/jwalton/.wget-hsts
URI encoding = ‘UTF-8’
Caching ftp.gnu.org => 209.51.188.20 2001:470:142:3::b
Created socket 4.
Releasing 0x5590bdacd590 (new refcount 1).
Initiating SSL handshake.
Handshake successful; connected socket 4 to SSL handle 0x5590bdad1fd0
certificate:
subject: CN=ftp.gnu.org
issuer: CN=R3,O=Let's Encrypt,C=US
Closed 4/SSL 0x5590bdad1fd0
Failed to download Ncurses
$ cat ./wget-test.sh
#!/usr/bin/env bash
{
# This is the new "Let's Encrypt Authority R3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIFFjCCAv6gAwIBAgIRAJErCErPDBinU/bWLiWnX1owDQYJKoZIhvcNAQELBQAw
TzELMAkGA1UEBhMCVVMxKTAnBgNVBAoTIEludGVybmV0IFNlY3VyaXR5IFJlc2Vh
cmNoIEdyb3VwMRUwEwYDVQQDEwxJU1JHIFJvb3QgWDEwHhcNMjAwOTA0MDAwMDAw
WhcNMjUwOTE1MTYwMDAwWjAyMQswCQYDVQQGEwJVUzEWMBQGA1UEChMNTGV0J3Mg
RW5jcnlwdDELMAkGA1UEAxMCUjMwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7AhUozPaglNMPEuyNVZLD+ILxmaZ6QoinXSaqtSu5xUyxr45r+XXIo9cP
R5QUVTVXjJ6oojkZ9YI8QqlObvU7wy7bjcCwXPNZOOftz2nwWgsbvsCUJCWH+jdx
sxPnHKzhm+/b5DtFUkWWqcFTzjTIUu61ru2P3mBw4qVUq7ZtDpelQDRrK9O8Zutm
NHz6a4uPVymZ+DAXXbpyb/uBxa3Shlg9F8fnCbvxK/eG3MHacV3URuPMrSXBiLxg
Z3Vms/EY96Jc5lP/Ooi2R6X/ExjqmAl3P51T+c8B5fWmcBcUr2Ok/5mzk53cU6cG
/kiFHaFpriV1uxPMUgP17VGhi9sVAgMBAAGjggEIMIIBBDAOBgNVHQ8BAf8EBAMC
AYYwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMBMBIGA1UdEwEB/wQIMAYB
Af8CAQAwHQYDVR0OBBYEFBQusxe3WFbLrlAJQOYfr52LFMLGMB8GA1UdIwQYMBaA
FHm0WeZ7tuXkAXOACIjIGlj26ZtuMDIGCCsGAQUFBwEBBCYwJDAiBggrBgEFBQcw
AoYWaHR0cDovL3gxLmkubGVuY3Iub3JnLzAnBgNVHR8EIDAeMBygGqAYhhZodHRw
Oi8veDEuYy5sZW5jci5vcmcvMCIGA1UdIAQbMBkwCAYGZ4EMAQIBMA0GCysGAQQB
gt8TAQEBMA0GCSqGSIb3DQEBCwUAA4ICAQCFyk5HPqP3hUSFvNVneLKYY611TR6W
PTNlclQtgaDqw+34IL9fzLdwALduO/ZelN7kIJ+m74uyA+eitRY8kc607TkC53wl
ikfmZW4/RvTZ8M6UK+5UzhK8jCdLuMGYL6KvzXGRSgi3yLgjewQtCPkIVz6D2QQz
CkcheAmCJ8MqyJu5zlzyZMjAvnnAT45tRAxekrsu94sQ4egdRCnbWSDtY7kh+BIm
lJNXoB1lBMEKIq4QDUOXoRgffuDghje1WrG9ML+Hbisq/yFOGwXD9RiX8F6sw6W4
avAuvDszue5L3sz85K+EC4Y/wFVDNvZo4TYXao6Z0f+lQKc0t8DQYzk1OXVu8rp2
yJMC6alLbBfODALZvYH7n7do1AZls4I9d1P4jnkDrQoxB3UqQ9hVl3LEKQ73xF1O
yK5GhDDX8oVfGKF5u+decIsH4YaTw7mP3GFxJSqv3+0lUFJoi5Lc5da149p90Ids
hCExroL1+7mryIkXPeFM5TgO9r0rvZaBFOvV2z0gp35Z0+L4WPlbuEjN/lxPFin+
HlUjr8gRsI3qfJOQFy/9rKIJR0Y/8Omwt/8oTWgy1mdeHmmjk7j1nYsvC9JSQ6Zv
MldlTTKB3zhThV1+XWYp6rjd5JW1zbVWEkLNxE7GJThEUG3szgBVGP7pSWTUTsqX
nLRbwHOoq7hHwg==
-END CERTIFICATE-"
# This is the original "Let's Encrypt Authority X3"
# https://letsencrypt.org/certificates/
echo "-BEGIN CERTIFICATE-
MIIEkjCCA3qgAwIBAgIQCgFBQgAAAVOFc2oLheynCDANBgkqhkiG9w0BAQsFADA/
MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT
DkRTVCBSb290IENBIFgzMB4XDTE2MDMxNzE2NDA0NloXDTIxMDMxNzE2NDA0Nlow
SjELMAkGA1UEBhMCVVMxFjAUBgNVBAoTDUxldCdzIEVuY3J5cHQxIzAhBgNVBAMT
GkxldCdzIEVuY3J5cHQgQXV0aG9yaXR5IFgzMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEAnNMM8FrlLke3cl03g7NoYzDq1zUmGSXhvb418XCSL7e4S0EF
q6meNQhY7LEqxGiHC6PjdeTm86dicbp5gWAf15Gan/PQeGdxyGkOlZHP/uaZ6WA8
SMx+yk13EiSdRxta67nsHjcAHJyse6cF6s5K671B5TaYucv9bTyWaN8jKkKQDIZ0
Z8h/pZq4UmEUEz9l6YKHy9v6Dlb2honzhT+Xhq+w3Brvaw2VFn3EK6BlspkENnWA
a6xK8xuQSXgvopZPKiAlKQTGdMDQMc2PMTiVFrqoM7hD8bEfwzB/onkxEz0tNvjj
/PIzark5McWvxI0NHWQWM6r6hCm21AvA2H3DkwIDAQABo4IBfTCCAXkwEgYDVR0T
AQH/BAgwBgEB/wIBADAOBgNVHQ8BAf8EBAMCAYYwfwYIKwYBBQUHAQEEczBxMDIG
CCsGAQUFBzABhiZodHRwOi8vaXNyZy50cnVzdGlkLm9jc3AuaWRlbnRydXN0LmNv
bTA7BggrBgEFBQcwAoYvaHR0cDovL2FwcHMuaWRlbnRydXN0LmNvbS9yb290cy9k
c3Ryb290Y2F4My5wN2MwHwYDVR0jBBgwFoAUxKexpHsscfrb4UuQdf/EFWCFiRAw
VAYDVR0gBE0wSzAIBgZngQwBAgEwPwYLKwYBBAGC3xMBAQEwMDAuBggrBgEFBQcC
ARYiaHR0cDovL2Nwcy5yb290LXgxLmxldHNlbmNyeXB0Lm9yZzA8BgNVHR8ENTAz
MDGgL6AthitodHRwOi8vY3JsLmlkZW50cnVzdC5jb20vRFNUUk9PVENBWDNDUkwu
[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM
Have the same problem, here is the log: ** Attachment added: "Log of systemd" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5450309/+files/lp1905166.log -- 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/1905166 Title: systemd-shutdown cannot detach DM Status in systemd package in Ubuntu: Incomplete Bug description: when powering down the system systemd cannot unmount / systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring reboot: Power down as a result at each startup the filesystem is checked: Press Ctrl+C to cancel all filesystem checks in progress If systemd cannot unmount / that might not be a problem but it should be less noisy and not result in a filesystem check after each reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 11:40:05 2020 MachineType: Dell Inc. Latitude 7410 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0M5G57 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd10/11/2020:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn0M5G57:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09CD dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+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 1904406] Re: autopkgtest hangs in timedated test
This bug was fixed in the package systemd - 247.1-4ubuntu1 --- systemd (247.1-4ubuntu1) hirsute; urgency=medium [ Dan Streetman ] * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch: Fix test use of new cap numbers with 5.8 kernel (LP: #1905044) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c [ Balint Reczey ] * Merge to Ubuntu from Debian unstable * Refresh patches - Dropped changes: * debian/patches/dhcp-Allow-setting-request-options-again.patch (Upstream code has been changed in a similar way) * debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch (Revert-network-prevent-interfaces-to-be-initialized-multi.patch is still kept) * debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch (Present in upstream 247.) * debian/udev.NEWS: Mention udev rules changes in 247 File: debian/udev.NEWS https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633 * Don't start systemd-udev-trigger.service in containers. It fails and is not likely to be useful. File: debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82 * test: use modern qemu numa arguments (LP: #1908259) File: debian/patches/test-use-modern-qemu-numa-arguments.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c systemd (247.1-4) unstable; urgency=medium [ наб ] * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when an explicit path was passed (Closes: #970213) * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation messages and uninstallation to 90-loaderentry.install [ Michael Biebl ] * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699) systemd (247.1-3) unstable; urgency=medium * d/t/timedated: Ignore return code of dbus-monitor in wait_mon() We are not really interested in the return code and error messages from dbus-monitor after killing it, so ignore them to avoid undesired autopkgtest failures. systemd (247.1-2) unstable; urgency=medium [ Michael Biebl ] * Upload to unstable * Revert "d/t/timedated: use /bin/bash to work around job handling issue in dash" [ Balint Reczey ] * debian/tests/timedated: Wait for the killed child only. There may be other children of the script due to autopkgtest machinery and they exit after the script exited. (LP: #1904406) systemd (247.1-1) experimental; urgency=medium * New upstream version 247.1 systemd (247-1) experimental; urgency=medium * New upstream version 247 * Rebase patches * Update symbol versions for the v247 release systemd (247~rc2-3) experimental; urgency=medium * Merge changes from unstable * sd-device: make sd_device_has_current_tag() compatible with udev database generated by older udevd (Closes: #974730) * Add Breaks: udev (<< 247~) to systemd. This ensures that udev is upgraded alongside systemd and both support the new udev tags concept introduced in v247. (Closes: #975554) systemd (247~rc2-2) experimental; urgency=medium * missing: define several syscall numbers for MIPS arch (Closes: #974619) systemd (247~rc2-1) experimental; urgency=medium [ Michael Biebl ] * New upstream version 247~rc2 - tmpfiles: Handle filesystems without ACL support in more cases (Closes: #972135) * Rebase patches * Explicitly disable oomd * Use -Dmode=release as we want a release, not developer, build * Update symbols file for libudev1 and libsystemd0 [ Luca Boccassi ] * systemd-container: install systemd-dissect binary. Required for TEST-50-DISSECT since: https://github.com/systemd/systemd/pull/16046 * d/t/control: install squashfs-tools for upstream test. Required by TEST-50-DISSECT since upstream PR: https://github.com/systemd/systemd/pull/16046 [ Dan Streetman ] * d/control: update meson minimum version https://github.com/systemd/systemd/pull/13842#issuecomment-601105975 * d/t/upstream: convert 'blacklist' term to 'deny-list' Support transition for upstream-ci from https://github.com/systemd/systemd/pull/16262 -- Balint Reczey Wed, 16 Dec 2020 10:27:06 +0100 ** Changed in: systemd (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Touch-packages] [Bug 1905044] Re: systemd 245.4-4ubuntu3.3 ADT test failure with linux-hwe-5.8
This bug was fixed in the package systemd - 247.1-4ubuntu1 --- systemd (247.1-4ubuntu1) hirsute; urgency=medium [ Dan Streetman ] * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch: Fix test use of new cap numbers with 5.8 kernel (LP: #1905044) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c [ Balint Reczey ] * Merge to Ubuntu from Debian unstable * Refresh patches - Dropped changes: * debian/patches/dhcp-Allow-setting-request-options-again.patch (Upstream code has been changed in a similar way) * debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch (Revert-network-prevent-interfaces-to-be-initialized-multi.patch is still kept) * debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch (Present in upstream 247.) * debian/udev.NEWS: Mention udev rules changes in 247 File: debian/udev.NEWS https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633 * Don't start systemd-udev-trigger.service in containers. It fails and is not likely to be useful. File: debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82 * test: use modern qemu numa arguments (LP: #1908259) File: debian/patches/test-use-modern-qemu-numa-arguments.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c systemd (247.1-4) unstable; urgency=medium [ наб ] * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when an explicit path was passed (Closes: #970213) * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation messages and uninstallation to 90-loaderentry.install [ Michael Biebl ] * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699) systemd (247.1-3) unstable; urgency=medium * d/t/timedated: Ignore return code of dbus-monitor in wait_mon() We are not really interested in the return code and error messages from dbus-monitor after killing it, so ignore them to avoid undesired autopkgtest failures. systemd (247.1-2) unstable; urgency=medium [ Michael Biebl ] * Upload to unstable * Revert "d/t/timedated: use /bin/bash to work around job handling issue in dash" [ Balint Reczey ] * debian/tests/timedated: Wait for the killed child only. There may be other children of the script due to autopkgtest machinery and they exit after the script exited. (LP: #1904406) systemd (247.1-1) experimental; urgency=medium * New upstream version 247.1 systemd (247-1) experimental; urgency=medium * New upstream version 247 * Rebase patches * Update symbol versions for the v247 release systemd (247~rc2-3) experimental; urgency=medium * Merge changes from unstable * sd-device: make sd_device_has_current_tag() compatible with udev database generated by older udevd (Closes: #974730) * Add Breaks: udev (<< 247~) to systemd. This ensures that udev is upgraded alongside systemd and both support the new udev tags concept introduced in v247. (Closes: #975554) systemd (247~rc2-2) experimental; urgency=medium * missing: define several syscall numbers for MIPS arch (Closes: #974619) systemd (247~rc2-1) experimental; urgency=medium [ Michael Biebl ] * New upstream version 247~rc2 - tmpfiles: Handle filesystems without ACL support in more cases (Closes: #972135) * Rebase patches * Explicitly disable oomd * Use -Dmode=release as we want a release, not developer, build * Update symbols file for libudev1 and libsystemd0 [ Luca Boccassi ] * systemd-container: install systemd-dissect binary. Required for TEST-50-DISSECT since: https://github.com/systemd/systemd/pull/16046 * d/t/control: install squashfs-tools for upstream test. Required by TEST-50-DISSECT since upstream PR: https://github.com/systemd/systemd/pull/16046 [ Dan Streetman ] * d/control: update meson minimum version https://github.com/systemd/systemd/pull/13842#issuecomment-601105975 * d/t/upstream: convert 'blacklist' term to 'deny-list' Support transition for upstream-ci from https://github.com/systemd/systemd/pull/16262 -- Balint Reczey Wed, 16 Dec 2020 10:27:06 +0100 ** Changed in: systemd (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
[Touch-packages] [Bug 1908259] Re: TEST-36-NUMAPOLICY fails with qemu 5.2
This bug was fixed in the package systemd - 247.1-4ubuntu1 --- systemd (247.1-4ubuntu1) hirsute; urgency=medium [ Dan Streetman ] * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch: Fix test use of new cap numbers with 5.8 kernel (LP: #1905044) https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d55c6f8186cb2cb73f61d6ff5b2e0ded82ef265c [ Balint Reczey ] * Merge to Ubuntu from Debian unstable * Refresh patches - Dropped changes: * debian/patches/dhcp-Allow-setting-request-options-again.patch (Upstream code has been changed in a similar way) * debian/patches/Revert-network-do-not-drop-foreign-config-if-interface-is.patch debian/patches/network-Set-link-state-to-LINK_STATE_PENDING-instead-of-t.patch (Revert-network-prevent-interfaces-to-be-initialized-multi.patch is still kept) * debian/patches/lp1845909/0002-network-add-link-setting_genmode-flag.patch * d/p/lp1905044-test-use-cap_last_cap-for-max-supported-cap-number-n.patch (Present in upstream 247.) * debian/udev.NEWS: Mention udev rules changes in 247 File: debian/udev.NEWS https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9f33f19683c2b864384c2ae59b312b2c844ed633 * Don't start systemd-udev-trigger.service in containers. It fails and is not likely to be useful. File: debian/patches/units-Don-t-start-systemd-udev-trigger.service-in-a-conta.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7b04fe5f98a4d204f73a1ec22884b9b3053a9a82 * test: use modern qemu numa arguments (LP: #1908259) File: debian/patches/test-use-modern-qemu-numa-arguments.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=158106e74d452cf6cd5cd737432cbe6b7d47286c systemd (247.1-4) unstable; urgency=medium [ наб ] * debian/extra/kernel-install.d/85-initrd.install: Don't install initrd when an explicit path was passed (Closes: #970213) * debian/extra/kernel-install.d/85-initrd.install: Match initrd installation messages and uninstallation to 90-loaderentry.install [ Michael Biebl ] * sd-device: keep escaped strings in DEVLINK= property (Closes: #976699) systemd (247.1-3) unstable; urgency=medium * d/t/timedated: Ignore return code of dbus-monitor in wait_mon() We are not really interested in the return code and error messages from dbus-monitor after killing it, so ignore them to avoid undesired autopkgtest failures. systemd (247.1-2) unstable; urgency=medium [ Michael Biebl ] * Upload to unstable * Revert "d/t/timedated: use /bin/bash to work around job handling issue in dash" [ Balint Reczey ] * debian/tests/timedated: Wait for the killed child only. There may be other children of the script due to autopkgtest machinery and they exit after the script exited. (LP: #1904406) systemd (247.1-1) experimental; urgency=medium * New upstream version 247.1 systemd (247-1) experimental; urgency=medium * New upstream version 247 * Rebase patches * Update symbol versions for the v247 release systemd (247~rc2-3) experimental; urgency=medium * Merge changes from unstable * sd-device: make sd_device_has_current_tag() compatible with udev database generated by older udevd (Closes: #974730) * Add Breaks: udev (<< 247~) to systemd. This ensures that udev is upgraded alongside systemd and both support the new udev tags concept introduced in v247. (Closes: #975554) systemd (247~rc2-2) experimental; urgency=medium * missing: define several syscall numbers for MIPS arch (Closes: #974619) systemd (247~rc2-1) experimental; urgency=medium [ Michael Biebl ] * New upstream version 247~rc2 - tmpfiles: Handle filesystems without ACL support in more cases (Closes: #972135) * Rebase patches * Explicitly disable oomd * Use -Dmode=release as we want a release, not developer, build * Update symbols file for libudev1 and libsystemd0 [ Luca Boccassi ] * systemd-container: install systemd-dissect binary. Required for TEST-50-DISSECT since: https://github.com/systemd/systemd/pull/16046 * d/t/control: install squashfs-tools for upstream test. Required by TEST-50-DISSECT since upstream PR: https://github.com/systemd/systemd/pull/16046 [ Dan Streetman ] * d/control: update meson minimum version https://github.com/systemd/systemd/pull/13842#issuecomment-601105975 * d/t/upstream: convert 'blacklist' term to 'deny-list' Support transition for upstream-ci from https://github.com/systemd/systemd/pull/16262 -- Balint Reczey Wed, 16 Dec 2020 10:27:06 +0100 ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.
Re: [Touch-packages] [Bug 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"
And, for clarity, when systemd does hibernate, I haven't had issues restoring: it's just getting systemd to find the correct swap space to use that's been the issue. -- 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/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+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 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"
On Thu, Jan 07, 2021 at 03:23:36PM -, Dimitri John Ledkov wrote: > Also, you do disable secureboot as well right? Because with secureboot > on, even though hybernation image is created, it will be ignored and > not used upon resume. Yep, Secure Boot is disabled on this system. -- 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/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+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 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"
these things are very weird indeed. Also, you do disable secureboot as well right? Because with secureboot on, even though hybernation image is created, it will be ignored and not used upon resume. -- 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/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+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 1910544] Re: Bash search history vi-mode hang the process
I think I solved by removing the .bash_history file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1910544 Title: Bash search history vi-mode hang the process Status in bash package in Ubuntu: New Bug description: Hi, Since a couple of weeks I found my self frustrated. I usually use bash -o vi and use vi commands on the command line. To search bask in the history i type 'Esc+/' and after thtat the search string e.g. 'Esc+/python3' Above search hangs the bash process with heave CPU usage and I need to kill it. Please help. /Joakim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jan 7 14:16:59 2021 InstallationDate: Installed on 2020-10-29 (70 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1910544/+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 1910538] Re: Cannot set scale of screen
*** This bug is a duplicate of bug 1910539 *** https://bugs.launchpad.net/bugs/1910539 ** This bug has been marked a duplicate of bug 1910539 Cannot set scale of screen -- 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/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1910538/+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 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"
> So, looking at the systemd code at https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared /sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the correct device actually was the workaround/fix? The confusing part about this is that I don't believe I set /sys/power/resume when I first booted, so I guess that was set correctly for some reason this time around? (Or maybe something else is going on entirely, of course.) -- 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/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. UpgradeStatus: Upgraded to groovy on 2020-06-22 (196 days ago) dmi.bios.date: 01/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1910252/+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 1910252] Re: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation"
I enabled systemd-logind debug logging, and I saw: Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported by the kernel. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate device. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with lower priority Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files matching resume config were found in /proc/swaps. Jan 06 17:45:18 surprise systemd-logind[73027]: Sent message type=method_return sender=n/a destination=:1.264 path=n/a interface=n/a member=n/a cookie=185 reply_cookie=6 signature=s error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call sender=:1.264 destination=:1.220 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=CanHybridSleep cookie=7 reply_cookie=0 signature=n/a error-name=n/a error-message=n/a Jan 06 17:45:18 surprise systemd-logind[73027]: Sleep mode "disk" is supported by the kernel. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/dm-2: is a candidate device. Jan 06 17:45:18 surprise systemd-logind[73027]: /dev/sda2: ignoring device with lower priority Jan 06 17:45:18 surprise systemd-logind[73027]: No swap partitions or files matching resume config were found in /proc/swaps. However, after a reboot this morning, hibernation does seem to be working, and I instead see: Jan 07 09:29:37 surprise systemd-logind[1798]: Got message type=method_call sender=:1.125 destination=org.freedesktop.login1 path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager member=Hibernate cookie=3 reply_cookie=0 signature=b error-name=n/a error-message=n/a Jan 07 09:29:37 surprise systemd-logind[1798]: Sleep mode "disk" is supported by the kernel. Jan 07 09:29:37 surprise systemd-logind[1798]: /dev/sda2: device matches configured resume settings. Jan 07 09:29:37 surprise systemd-logind[1798]: Hibernation will attempt to use swap entry with path: /dev/sda2, device: 8:2, offset: 0, priority: -3 Jan 07 09:29:37 surprise systemd-logind[1798]: Enough swap for hibernation, Active(anon)=3080788 kB, size=102401108 kB, used=0 kB, threshold=98% So it looks like the issue is that my resume device was not being detected correctly previously, meaning that priority was being used (which resulted in the wrong device being selected). So, looking at the systemd code at https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared /sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the correct device actually was the workaround/fix? -- 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/1910252 Title: `systemctl hibernate` incorrectly reports "Not enough swap space for hibernation" Status in systemd package in Ubuntu: New Bug description: I have plenty of swap space configured in my system: $ cat /sys/power/image_size 6642229248 # ~ 6.2GiB $ swapon NAME TYPE SIZE USED PRIO /dev/dm-2 partition 980M 0B -2 /dev/sda2 partition 97.7G 0B -3 But when I attempt to hibernate: $ sudo systemctl hibernate Failed to hibernate system via logind: Not enough swap space for hibernation I have the swap partition configured as my resume device in my kernel commandline: $ cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 $ ls -l /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 lrwxrwxrwx 1 root root 10 Jan 5 09:08 /dev/disk/by-uuid/73909634-a75d-42c9-8f66-a69138690756 -> ../../sda2 (I'm not really sure how to further debug my issue, any assistance would be appreciated!) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: systemd 246.6-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jan 5 09:33:04 2021 InstallationDate: Installed on 2019-05-07 (608 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7 SourcePackage: systemd
[Touch-packages] [Bug 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
** Changed in: elfutils (Ubuntu Groovy)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
In Progress
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
In Progress
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
MP for groovy is open
** Merge proposal linked:
https://code.launchpad.net/~fheimes/ubuntu/+source/elfutils/+git/elfutils/+merge/395917
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
In Progress
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
In Progress
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1908756] Re: Ubuntu 20.10 - elfutils unwinding broken for s390 compat
A PPA was created and shared that contains a patched elfutils version for
groovy:
Look for elfutils - 0.181-1ubuntu1~ppa1 at
https://launchpad.net/~fheimes/+archive/ubuntu/lp1908756/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1908756
Title:
Ubuntu 20.10 - elfutils unwinding broken for s390 compat
Status in Ubuntu on IBM z Systems:
In Progress
Status in elfutils package in Ubuntu:
Fix Released
Status in elfutils source package in Groovy:
New
Status in elfutils source package in Hirsute:
Fix Released
Bug description:
SRU Bug Template:
=
[Impact]
* There is an endianess problem in pid_memory_read that impacts
s390x.
* Due to this elfutils biarch test fails on s390x doing unwinding for
a 32 bit process.
[Fix]
* e4d985a3c1c873f77d20fa0cd421458cc2824996 e4d985a3 "IBM Z: Fix endianess
problem in pid_memory_read"
[Test Case]
* Have an Ubuntu Server 20.10 system or newer installed on LPAR, z/VM or KVM
that comes with elfutils 0.181 or 0.182.
* Run the test script: 'run-backtrace-native-biarch.sh'
* It either core dumps without the patch in place - look for
"/test-subr.sh: line 84: 376822 Aborted (core dumped)" or succeeds.
[Where problems could occur]
* If the translation is not done right (shift of the upper 4 bytes + down on
big endian 64 bit targets) the situation is broken in the same way, and things
stay the same.
* But in worst case the changes in 'pid_memory_read' of
/libdwfl/linux-pid-attach.c could have a negative impact even on architectures
other than s390x, in case the check for the endiness is wrong.
* But the changes are quite traceable and the additional code that fixes the
endianess problem is really only active on a big endian architecture.
[Other]
* The fix is upstream accepted with elfutils > 0.182.
__
---Problem Description---
libdw unwinding fails for 32 bit binaries.
Elfutils biarch test currently fails on s390x doing unwinding for a 32
bit process.
FAIL: run-backtrace-native-biarch.sh
0x557e7000 0x557eb000 /root/elfutils/tests/backtrace-child-biarch
0x7dba4000 0x7dd51000 /usr/lib/libc-2.32.so
0x7dd53000 0x7dd7 /usr/lib/libpthread-2.32.so
0x7dd7f000 0x7dda6000 /usr/lib/ld-2.32.so
TID 376858:
# 0 0x7dd6668a raise
# 1 0x7fd0ef60 - 1
/root/elfutils/tests/backtrace: dwfl_thread_getframes: No DWARF information
found
backtrace: backtrace.c:114: callback_verify: Assertion `symname != NULL &&
strcmp (symname, "sigusr2") == 0' failed.
./test-subr.sh: line 84: 376822 Aborted (core dumped)
LD_LIBRARY_PATH="${built_library_path}${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH"
$VALGRIND_CMD "$@"
backtrace-child-biarch: no main
FAIL run-backtrace-native-biarch.sh (exit status: 1)
Patch has already been posted and upstream committed:
https://sourceware.org/pipermail/elfutils-devel/2020q4/003149.html
Please pick up the following commit for the next release:
commit e4d985a3c1c873f77d20fa0cd421458cc2824996
Author: Andreas Krebbel
Date: Thu Nov 19 20:32:24 2020 +0100
IBM Z: Fix endianess problem in pid_memory_read
The cached reads lack the big endian adjustments done in the fallback
path.
Signed-off-by: Andreas Krebbel
The patch applies cleanly ontop of elfutils_0.181-1.
strace right now is not built with unwinding support for IBM Z although both
variants should work - libdw and libunwind.
Other distros use libdw from elfutils while Ubuntu on x86 appears to
use libunwind. libdw and libunwind do support IBM Z.
It would be good to build strace with unwinding support for Z.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1908756/+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 1910544] [NEW] Bash search history vi-mode hang the process
Public bug reported: Hi, Since a couple of weeks I found my self frustrated. I usually use bash -o vi and use vi commands on the command line. To search bask in the history i type 'Esc+/' and after thtat the search string e.g. 'Esc+/python3' Above search hangs the bash process with heave CPU usage and I need to kill it. Please help. /Joakim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jan 7 14:16:59 2021 InstallationDate: Installed on 2020-10-29 (70 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1910544 Title: Bash search history vi-mode hang the process Status in bash package in Ubuntu: New Bug description: Hi, Since a couple of weeks I found my self frustrated. I usually use bash -o vi and use vi commands on the command line. To search bask in the history i type 'Esc+/' and after thtat the search string e.g. 'Esc+/python3' Above search hangs the bash process with heave CPU usage and I need to kill it. Please help. /Joakim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bash 5.0-6ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Jan 7 14:16:59 2021 InstallationDate: Installed on 2020-10-29 (70 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1910544/+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 1908818] Re: pure packaging of libnss3
Thanks for taking the time to report this bug and try to make Ubuntu
better.
I have checked and this is happening just in Groovy. I am subscribing
ubuntu-server for further investigation.
** Also affects: nss (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: nss (Ubuntu Groovy)
Status: New => Triaged
** Changed in: nss (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818
Title:
pure packaging of libnss3
Status in nss package in Ubuntu:
Fix Released
Status in nss source package in Groovy:
Triaged
Bug description:
dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to
x86_64-linux-gnu
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+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 1910538] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910538/+attachment/5450200/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910538 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1910537] [NEW] incorrect audio-EDID on HDMI, blocking audio transmission over HDMI
Public bug reported: This is a complicated thing. I have a very specific problem with audio output on HDMI. I want to use an older notebook with Lubuntu 20.04 as a video source for libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the desktop just like a second screen or beamer. Video works well and rock-stable, no problem at all. But not audio. Although I carefully configured audio with pavucontrol to be directed to the HDMI output, the ATEM switcher does not recognize it as an audio source (like when connecting a digital camera) and does not receive or indicate any audio input. Note: But when I use the very same computer, same HDMI cable, same video with a cheap chinese portable LCD screen with speakers (i.e. pull the cable from the ATEM and plug it into the screen) it immediately starts playing both video and audio. So there is evidence that the ubuntu notebook definitely passes it's sound to HDMI and there's really an audio signal on the HDMI. I've opened a bug at Blackmagic Design, and got their reply that they can't help and have never heard of such a problem before. Their guess is that the linux notebook is not setting EDID configuration correctly and thus not recognized by the ATEM, while the cheap LCD screen propably does not care about EDID and just plays everything, therefore a wrong EDID information would not matter. Although I have decades of experience with Linux, I am not too familiar with details of HDMI and the internals of the X11 driver, so I'm not sure where to start debugging, not even, whether this is a problem of Xorg/X11 or pulseaudio. I've checked this with another notebook with much more recent (intel) hardware, which offers dozens of HDMI audio options in the pavucontrol selection menu, but same problem: Video works, but the ATEM does not recognize it as a audio source. Blackmagic Design (they're good in Windows and MacOS, but not Linux) recommended to use an edid manager, whatever this means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Jan 7 13:16:26 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0742] InstallationDate: Installed on 2020-05-16 (235 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer AO756 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05: dmi.product.family: Type1Family dmi.product.name: AO756 dmi.product.sku: Type1Sku0 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug
[Touch-packages] [Bug 1910539] Re: Cannot set scale of screen
This is screenshot after clicking apply (to access print screen had to click keep changes button too) ** Attachment added: "After click on apply" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1910539/+attachment/5450246/+files/Screenshot%20from%202021-01-07%2020-52-00.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/1910539/+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 1910539] [NEW] Cannot set scale of screen
Public bug reported: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.45.01 Thu Nov 5 23:03:56 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 20:41:50 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694] NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] [19da:4509] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0229 dmi.board.asset.tag: Default string dmi.board.name: PRIME B360M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 ** Attachment added: "Before clicking on Apply" https://bugs.launchpad.net/bugs/1910539/+attachment/5450223/+files/Screenshot%20from%202021-01-07%2020-51-50.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910539 Title: Cannot set scale of screen Status in xorg package in Ubuntu: New Bug description: I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor (3840x2160) both 27inch Obviously to extend display correctly (join displays) I need to put my 4k monitor at scale of 125 and 2K monitor at 100% scale. I arrange two monitors side by side, then select 125% on 4K monitor (Fractional scaling is on) and click apply, both my monitors go to wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange bottom and top of each other. also login appears on wrong monitor (secondary) instead of selected primary ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
This is indeed a complex problem and it is hard to do anything
reasonable about a missing GTK frontend when debconf is not initiated
from the terminal.
OTOH I think there is an easy fix for GTK+ to always include an "image-
missing" icon at compile time, but apparently I'm not the first one
coming up with this idea, but something is still broken:
gtk/gtkiconhelper.c:494
if (destination == NULL)
{
GError *error = NULL;
destination = gtk_icon_theme_load_icon (icon_theme,
"image-missing",
width,
flags |
GTK_ICON_LOOKUP_USE_BUILTIN | GTK_ICON_LOOKUP_GENERIC_FALLBACK,
);
/* We include this image as resource, so we always have it available or
* the icontheme code is broken */
g_assert_no_error (error);
g_assert (destination);
symbolic = FALSE;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1627564
Title:
Debconf crash due to assertion failure in ensure_surface_for_gicon
[gtkiconhelper.c:493] (when png loader is missing/during upgrades)
Status in debconf package in Ubuntu:
Confirmed
Status in gtk+3.0 package in Ubuntu:
New
Status in debconf source package in Focal:
Confirmed
Status in gtk+3.0 source package in Focal:
New
Bug description:
https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383
---
bubble opened up indicating there was a failure during the latest
update.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: lightdm-gtk-greeter 2.0.1-2ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7
Uname: Linux 4.4.0-9136-generic i686
ApportVersion: 2.20.3-0ubuntu7
Architecture: i386
Date: Sun Sep 25 20:37:06 2016
ExecutablePath: /usr/sbin/lightdm-gtk-greeter
InstallationDate: Installed on 2016-08-04 (52 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727)
ProcCmdline: /usr/sbin/lightdm-gtk-greeter
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/false
Signal: 6
SourcePackage: lightdm-gtk-greeter
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
[greeter]
theme-name = Lubuntu-dark-panel
mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf:
2016-08-14T22:33:57.293011
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+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 1627564] Re: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades)
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) Status in debconf package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Status in debconf source package in Focal: Confirmed Status in gtk+3.0 source package in Focal: New Bug description: https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689 https://errors.ubuntu.com/problem/9d612b3f25168e76adb91fa4eedc301ffa632383 --- bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1627564/+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 1803391] Re: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode
I have this problem with Ubuntu 18.04 system set up with 'encrypted LVM' (standard Ubuntu recipe as per the alternate installer). Whenever there is systemd upgrade it hangs (whole machine crashes - other logins not possible) and has to be manually rebooted (which is not ideal as the machine is 1500 miles away). Note the installed version of systemd seems to be 237-3ubuntu10.42, obviously I am unable to update it. I have another machine also Ubuntu 18.04 system set up with 'encrypted LVM' which has systemd 237-3ubuntu10.43 and does not have this problem. Latest instance of this problem: # apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 3,414 kB of archives. After this operation, 7,168 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libnss-systemd i386 237-3ubuntu10.43 [111 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libpam-systemd i386 237-3ubuntu10.43 [114 kB] Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 systemd i386 237-3ubuntu10.43 [2,964 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main i386 libsystemd0 i386 237-3ubuntu10.43 [225 kB] Fetched 3,414 kB in 1s (3,309 kB/s) (Reading database ... 151099 files and directories currently installed.) Preparing to unpack .../libnss-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libnss-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libpam-systemd_237-3ubuntu10.43_i386.deb ... Unpacking libpam-systemd:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../systemd_237-3ubuntu10.43_i386.deb ... Unpacking systemd (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Preparing to unpack .../libsystemd0_237-3ubuntu10.43_i386.deb ... Unpacking libsystemd0:i386 (237-3ubuntu10.43) over (237-3ubuntu10.42) ... Setting up libsystemd0:i386 (237-3ubuntu10.43) ... Setting up systemd (237-3ubuntu10.43) ... [system dies] -- 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/1803391 Title: Systemd update installation hangs in unattended-upgrades InstallOnShutdown mode Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Installation of latest systemd update in -security hangs with current versions of unattended-upgrades in supported releases. The u-u-side fix is tracked in LP: #1778219. [Regression Potential] * The daemons, shipped in deb:systemd, are not attempted to be restarted because despite package installation the system is in the middle of shutting down. This means that currently running daemons may be helding up open files on the filesystem, however all process are being stopped and killed as part of shutdown. Hence the worst possible regression from this, is an unclean shutdown, but even that shouldn't happen with this update. [Test Case] Reproduction: rbalint@yogi:~$ lxc launch ubuntu:18.04 uu-systemd-onshutdown Creating uu-systemd-onshutdown Starting uu-systemd-onshutdown rbalint@yogi:~$ lxc shell uu-systemd-onshutdown mesg: ttyname failed: No such device root@uu-systemd-onshutdown:~# apt update -qq 23 packages can be upgraded. Run 'apt list --upgradable' to see them. root@uu-systemd-onshutdown:~# echo 'Unattended-Upgrade::InstallOnShutdown "true";' > /etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown root@uu-systemd-onshutdown:~# apt list --upgradable Listing... Done apport/bionic-updates 2.20.9-0ubuntu7.5 all [upgradable from: 2.20.9-0ubuntu7.4] gettext-base/bionic-updates,bionic-security 0.19.8.1-6ubuntu0.1 amd64 [upgradable from: 0.19.8.1-6] kmod/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libglib2.0-0/bionic-updates 2.56.3-0ubuntu0.18.04.1 amd64 [upgradable from: 2.56.2-0ubuntu0.18.04.2] libglib2.0-data/bionic-updates 2.56.3-0ubuntu0.18.04.1 all [upgradable from: 2.56.2-0ubuntu0.18.04.2] libkmod2/bionic-updates 24-1ubuntu3.1 amd64 [upgradable from: 24-1ubuntu3] libmspack0/bionic-updates,bionic-security 0.6-3ubuntu0.2 amd64 [upgradable from: 0.6-3ubuntu0.1] libnss-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libpam-systemd/bionic-updates,bionic-security 237-3ubuntu10.6 amd64 [upgradable from: 237-3ubuntu10.3] libsystemd0/bionic-updates,bionic-security 237-3ubuntu10.6 amd64
[Touch-packages] [Bug 1907744] Re: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (A
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 Debconf crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) -- 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/1907744 Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) Status in unattended-upgrades package in Ubuntu: New Bug description: I have problems, it has disappeared programs. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: unattended-upgrades 2.3ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Dec 10 19:18:08 2020 ErrorMessage: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) InstallationDate: Installed on 2014-04-19 (2427 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 2.3ubuntu0.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Aborted) UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1907744/+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 1907789] Re: 2.35.50 breaks ld -no-pie
Proposed to drop the -no-pie flag at upstream s390-tools: https://github.com/ibm-s390-tools/s390-tools/pull/106 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
This bug was fixed in the package cyrus-sasl2 - 2.1.27~101-g0780600 +dfsg-3ubuntu2.3 --- cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3ubuntu2.3) bionic; urgency=medium * d/p/lp-1906627-01-Fix-GSS-SPNEGO-mechanism-s-incompatible-behavior.patch: d/p/lp-1906627-02-Drop-unused-parameter-from-gssapi_spnego_ssf.patch: - Fix GSS-SPNEGO implementation to be inter-operable with Microsoft Active Directory, fixing the source of the recent adcli regression. (LP: #1906627) -- Matthew Ruffell Mon, 07 Dec 2020 10:54:47 +1300 ** Changed in: cyrus-sasl2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Released Status in cyrus-sasl2 source package in Bionic: Fix Released Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO. $ apt rdepends libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-mit Reverse Depends: |Suggests: ldap-utils Depends: adcli Conflicts: libsasl2-modules-gssapi-heimdal |Suggests: libsasl2-modules Conflicts: libsasl2-modules-gssapi-heimdal |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules |Suggests: ldap-utils |Depends: msktutil Conflicts: libsasl2-modules-gssapi-heimdal |Depends: libapache2-mod-webauthldap Depends: freeipa-server Depends: freeipa-client Depends: adcli Depends: 389-ds-base |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules While this SRU makes cyrus-sasl2 work with Microsoft implementations of GSS-SPNEGO, which will be the more common usecase, it may change the behaviour when
[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
** Changed in: s390-tools (Ubuntu) Assignee: (unassigned) => Lukas Märdian (slyon) ** Changed in: s390-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: In Progress Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1906627] Update Released
The verification of the Stable Release Update for adcli has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Released Status in cyrus-sasl2 source package in Bionic: Fix Released Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO. $ apt rdepends libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-mit Reverse Depends: |Suggests: ldap-utils Depends: adcli Conflicts: libsasl2-modules-gssapi-heimdal |Suggests: libsasl2-modules Conflicts: libsasl2-modules-gssapi-heimdal |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules |Suggests: ldap-utils |Depends: msktutil Conflicts: libsasl2-modules-gssapi-heimdal |Depends: libapache2-mod-webauthldap Depends: freeipa-server Depends: freeipa-client Depends: adcli Depends: 389-ds-base |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules While this SRU makes cyrus-sasl2 work with Microsoft implementations of GSS-SPNEGO, which will be the more common usecase, it may change the behaviour when connecting to a MIT krb5 server with the GSS- SPNEGO protocol, as krb5 assumes use of confidentiality and integrity modes. This shouldn't be a problem as the krb5 implementation
[Touch-packages] [Bug 1906627] Re: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression
This bug was fixed in the package adcli - 0.8.2-1ubuntu1.2 --- adcli (0.8.2-1ubuntu1.2) bionic; urgency=medium * d/control: Adding specific dependency of libsasl2-modules-gssapi-mit 2.1.27~101-g0780600+dfsg-3ubuntu2.2 to ensure adcli uses fixed GSS-SPNEGO implementation to resolve regression. (LP: #1906627) -- Matthew Ruffell Tue, 08 Dec 2020 12:38:02 +1300 ** Changed in: adcli (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1906627 Title: GSS-SPNEGO implementation in cyrus-sasl2 is incompatible with Active Directory, causing recent adcli regression Status in adcli package in Ubuntu: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Status in adcli source package in Bionic: Fix Released Status in cyrus-sasl2 source package in Bionic: Fix Released Bug description: [Impact] A recent release of adcli 0.8.2-1ubuntu1 to bionic-updates caused a regression for some users when attempting to join a Active Directory realm. adcli introduced a default behaviour change, moving from GSS- API to GSS-SPNEGO as the default channel encryption algorithm. adcli uses the GSS-SPNEGO implementation from libsasl2-modules-gssapi- mit, a part of cyrus-sasl2. The implementation seems to have some compatibility issues with particular configurations of Active Directory on recent Windows Server systems. Particularly, adcli sends a ldap query to the domain controller, which responds with a tcp ack, but never returns a ldap response. The connection just hangs at this point and no more traffic is sent. You can see it on the packet trace below: https://paste.ubuntu.com/p/WRnnRMGBPm/ On Focal, where the implementation of GSS-SPNEGO is working, we see a full exchange, and adcli works as expected: https://paste.ubuntu.com/p/8668pJrr2m/ The fix is to not assume use of confidentiality and integrity modes, and instead use the flags negotiated by GSS-API during the initial handshake, as required by Microsoft's implementation. [Testcase] You will need to set up a Windows Server 2019 system, install and configure Active Directory and enable LDAP extensions and configure LDAPS and import the AD SSL certificate to the Ubuntu client. Create some users in Active Directory. On the Ubuntu client, set up /etc/hosts with the hostname of the Windows Server machine, if your system isn't configured for AD DNS. From there, install adcli 0.8.2-1 from -release. $ sudo apt install adcli Set up a packet trace with tcpdump: $ sudo tcpdump -i any port '(389 or 3268 or 636 or 3269)' Next, join the AD realm using the normal GSS-API: # adcli join --verbose -U Administrator --domain WIN- SB6JAS7PH22.testing.local --domain-controller WIN- SB6JAS7PH22.testing.local --domain-realm TESTING.LOCAL You will be prompted for Administrator's passowrd. The output should look like the below: https://paste.ubuntu.com/p/NWHGQn746D/ Next, enable -proposed, and install adcli 0.8.2-1ubuntu1 which caused the regression. Repeat the above steps. Now you should see the connection hang. https://paste.ubuntu.com/p/WRnnRMGBPm/ Finally, install the fixed cyrus-sasl2 package from -proposed https://launchpad.net/~mruffell/+archive/ubuntu/lp1906627-test $ sudo apt-get update $ sudo apt install libsasl2-2 libsasl2-modules libsasl2-modules-db libsasl2-modules-gssapi-mit Repeat the steps. GSS-SPNEGO should be working as intended, and you should get output like below: https://paste.ubuntu.com/p/W5cJNGvCsx/ [Where problems could occur] Since we are changing the implementation of GSS-SPNEGO, and cyrus- sasl2 is the library which provides it, we can potentially break any package which depends on libsasl2-modules-gssapi-mit for GSS-SPNEGO. $ apt rdepends libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-mit Reverse Depends: |Suggests: ldap-utils Depends: adcli Conflicts: libsasl2-modules-gssapi-heimdal |Suggests: libsasl2-modules Conflicts: libsasl2-modules-gssapi-heimdal |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules |Suggests: ldap-utils |Depends: msktutil Conflicts: libsasl2-modules-gssapi-heimdal |Depends: libapache2-mod-webauthldap Depends: freeipa-server Depends: freeipa-client Depends: adcli Depends: 389-ds-base |Recommends: sssd-krb5-common |Suggests: slapd |Suggests: libsasl2-modules While this SRU makes cyrus-sasl2 work with Microsoft implementations of GSS-SPNEGO, which will be the more common usecase, it may change the behaviour when connecting to a MIT krb5 server with the GSS- SPNEGO protocol, as krb5 assumes use of confidentiality and integrity modes. This shouldn't be a problem as the krb5
[Touch-packages] [Bug 1907789] Re: 2.35.50 breaks ld -no-pie
** Also affects: s390-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: New Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1901609] Re: signond causes qprocess crash
This bug was fixed in the package signon - 8.59+17.10.20170606-0ubuntu2.20.04.1 --- signon (8.59+17.10.20170606-0ubuntu2.20.04.1) focal; urgency=medium * Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd break compatibility with QProcess (LP: #1901609) * Build depend on quilt and integrate into debian/rules. Since this this source uses the legacy v1 format we need to manually wire up patching instead of having dpkg-source handle it -- Harald Sitter Mon, 23 Nov 2020 13:24:59 +0100 ** Changed in: signon (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1901609] Re: signond causes qprocess crash
** Changed in: signon (Ubuntu Focal) Status: Incomplete => Opinion ** Changed in: signon (Ubuntu Focal) Status: Opinion => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Released Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+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 1910525] Re: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Contents of cryptab sda6_crypt UUID=09558fbd-f3e4-4b8f-be73-89821668383a none luks,keyscript=decrypt_keyctl,discard sdb1_crypt UUID=1606b0ca-a544-43e9-ade7-8b33ac930d10 none luks,keyscript=decrypt_keyctl -- 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/1910525 Title: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I have an encrypted filesystem. The system will no longer boot after this and no longer be able to access the encrypted file system. It will bricked at the next reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 7 10:48:04 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-12-23 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1910525/+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 1910525] [NEW] package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I have an encrypted filesystem. The system will no longer boot after this and no longer be able to access the encrypted file system. It will bricked at the next reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 7 10:48:04 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-12-23 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1910525 Title: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I have an encrypted filesystem. The system will no longer boot after this and no longer be able to access the encrypted file system. It will bricked at the next reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 7 10:48:04 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-12-23 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1910525/+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 1910503] Re: latest kernel breaks display full sizing in virtualbox
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~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/+bug/1910503/+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 1910503] Re: latest kernel breaks display full sizing in virtualbox
content of make.log : DKMS make.log for virtualbox-guest-6.1.10 for kernel 5.8.0-34-generic (x86_64) jeu. 07 janv. 2021 09:20:12 CET make: Entering directory '/usr/src/linux-headers-5.8.0-34-generic' CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/VBoxGuest.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/VBoxGuest-linux.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/common/string/strformatrt.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-agnostic.o CC [M] /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.o In file included from /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.c:30: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c: In function ‘rtR0MemAllocExecVmArea’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:171:15: error: implicit declaration of function ‘__get_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration] 171 | pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END); | ^ | get_vm_area /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:171:13: warning: assignment to ‘struct vm_struct *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] 171 | pVmArea = __get_vm_area(cbAlloc, VM_ALLOC, MODULES_VADDR, MODULES_END); | ^ /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/alloc-r0drv-linux.c:204:14: error: implicit declaration of function ‘map_vm_area’; did you mean ‘get_vm_area’? [-Werror=implicit-function-declaration] 204 | if (!map_vm_area(pVmArea, PAGE_KERNEL_EXEC, | ^~~ | get_vm_area In file included from /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.c:33: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeFree’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:596:43: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 596 | down_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:611:41: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 611 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeLockUser’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1079:31: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1079 | down_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1165:33: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1165 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1192:29: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1192 | up_read(>mm->mmap_sem); | ^~~~ | mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c: In function ‘rtR0MemObjNativeMapUser’: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1607:36: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1607 | down_write(>mm->mmap_sem); |^~~~ |mmap_base /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/r0drv/linux/memobj-r0drv-linux.c:1724:34: error: ‘struct mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’? 1724 | up_write(>mm->mmap_sem); | ^~~~ | mmap_base cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:288: /var/lib/dkms/virtualbox-guest/6.1.10/build/vboxguest/combined-os-specific.o] Error 1 make[2]: *** Waiting for unfinished jobs make[1]: *** [scripts/Makefile.build:519:
[Touch-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox
Building initial module for 5.8.0-34-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-guest-dkms.0.crash' Error! Bad return status for module build on kernel: 5.8.0-34-generic (x86_64) Consult /var/lib/dkms/virtualbox-guest/6.1.10/build/make.log for more information. dpkg: error processing package virtualbox-guest-dkms (--configure): installed virtualbox-guest-dkms package post-installation script subprocess returned error exit status 1 0 Setting up virtualbox-guest-utils (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Setting up xmount (0.7.6-2) ... Setting up virtualbox-guest-x11 (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for systemd (245.4-4ubuntu3.3) ... Errors were encountered while processing: virtualbox-guest-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in linux package in Ubuntu: Confirmed Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~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/+bug/1910503/+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 1910503] [NEW] latest kernel breaks display full sizing in virtualbox
Public bug reported: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution 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/1910503 Title: latest kernel breaks display full sizing in virtualbox Status in xorg package in Ubuntu: New Bug description: kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1 going back to kernel 5.4.0-59 makes full size display working again ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 7 09:12:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2020-05-01 (250 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1,
