[Touch-packages] [Bug 1884455] Re: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset
That is a very good observation about not having to be on startup!! After I disabled both vmware.service and virtualbox.service, I cleaned-up: delete the '/root' and then make sure to mount it from the zfs dataset. Then I shutdown the system yesterday evening (2020-06-25). When I started the system this morning (2020-06-26): I saw that again the zfs dataset could not be mounted because a '/root' already exists, this time with an empty ".cache" folder in it. So it seems you were right about the vwmware or virtualbox that they use pulseaudio as root. But that is not the real issue: problem is with the ".cache" folder which is created at shutdown 'after' the zfs dataset is unmounted, just like you said. I'm not sure how to investigate what happens at shutdown, but I'll try to find out. Meanwhile it's clear this not a pulseaudio issue ==> this ticket should be closed (I'm not sure if I can do that, or you or someone else needs to do it). Daniel, thank you very much for your quick and very helpful responses: I appreciate it a lot! Filesystem details after a night of shutdown: - root@minighost:~# pwd /root root@minighost:~# ls -la total 10 drwxr-xr-x 3 root root 3 Jun 26 07:12 . drwxr-xr-x 34 root root 38 Jun 25 20:12 .. drwx-- 2 root root 2 Jun 25 20:23 .cache root@minighost:~# tree -a . └── .cache 1 directory, 0 files root@minighost:~# - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884455 Title: pulseaudio creates /root/.config/pulse/ before zfs-mount.service can mount the /root dataset Status in pulseaudio package in Ubuntu: Incomplete Bug description: I use 'zfs' and have /root as its own dataset which is mounted during startup by 'zfs-mount.service'. At one of the latest upgrades, the 'zfsutils-linux' package failed to update because the service 'zfs-mount' service had an issue and could not mount the '/root' dataset because the '/root' directory was not empty (temporary solution was to rename /root and call 'zfs mount' again). Further investigation shows that everytime at startup, the /root directory is created before the 'zfs-mount.service' has a chance to mount the 'root' dataset. The culprit seems to be something pulseaudio related: the content of /root folder after startup is as follows: - root@minighost:~# tree -a /root . ├── .cache └── .config └── pulse └── fe1417537ae0451abdb60c5df28fe825-runtime -> /tmp/pulse-PKdhtXMmr18n 4 directories, 0 files root@minighost:~# - Extra details: - Ubuntu release: - root@minighost:~# lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 - - status of 'zfs-mount.service' is the following: - root@minighost:~# systemctl status zfs-mount ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-06-21 12:56:08 CEST; 6h ago Docs: man:zfs(8) Process: 2062 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2062 (code=exited, status=1/FAILURE) Jun 21 12:56:08 minighost systemd[1]: Starting Mount ZFS filesystems... Jun 21 12:56:08 minighost zfs[2062]: cannot mount '/root': directory is not empty Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Jun 21 12:56:08 minighost systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Jun 21 12:56:08 minighost systemd[1]: Failed to start Mount ZFS filesystems. root@minighost:~# - - software versions: - root@minighost:~# apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.3 Candidate: 1:13.99.1-1ubuntu3.3 Version table: *** 1:13.99.1-1ubuntu3.3 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@minighost:~# apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.1 Candidate: 0.8.3-1ubuntu12.1 Version table: *** 0.8.3-1ubuntu12.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.8.3-1ubuntu12 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide
[Expired for avahi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: avahi (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1874021 Title: avahi-browse -av is empty, mdns not working in arduino ide Status in avahi package in Ubuntu: Expired Bug description: When I started the arduino IDE my port list is empty. This list relies on multicast DNS which is served by avahi. When running the avahi-browse -av command on ubuntu 18.04 I get a list of al mdns devices. On ubuntu 20.04 the're no mdns devices reported. The avahi-daemon is running. And when executing netstat -nlp | grep 5353 I see avahi-daemon is listening. When also running tcpdump port 5353 I see mdns packages arriving. But still avahi-browse -av is empty. iptables -A shows no rules and policies are accept ufw is disabled I also removed apparmor but also that didn't make any difference. On both ubuntu 18.04 and 20.04 the avahi version is 0.7. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: avahi-daemon 0.7-4ubuntu7 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
Hi Yuri, there was no recent change in regard to lvm handling in libvirt or lvm itself that would obviously be related. Which Ubuntu release are you on - and between which package versions did you upgrade? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount Status in lvm2: New Status in libvirt package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New Status in lvm2 package in Fedora: Confirmed Bug description: When using automatic suspend at reboot/shutdown, it makes sense to store the suspend data on a separate partition to ensure there is always enough available space. However this does not work, as the partition gets unmounted before or during libvirt suspend. Steps to reproduce: 1. Use Ubuntu 18.04.02 LTS 2. Install libvirt + qemu-kvm 3. Start a guest 4. Set libvirt-guests to suspend at shutdown/reboot by editing /etc/default/libvirt-guests 5. Create a fstab entry to mount a separate partition to mount point /var/lib/libvirt/qemu/save. Then run sudo mount /var/lib/libvirt/qemu/save to mount the partition. 6. Reboot Expected result: The guest suspend data would be written to the /var/lib/libvirt/qemu/save, resulting in the data being stored at the partition specified in fstab. At boot, this partition would be mounted as specified in fstab and libvirt-guest would be able to read the data and restore the guests. Actual result: The partition gets unmounted before libvirt-guests suspends the guests, resulting in the data being stored on the partition containing the root file system. During boot, the empty partition gets mounted over the non-empty /var/lib/libvirt/qemu/save directory, resulting in libvirt-guests being unable to read the saved data. As a side effect, the saved data is using up space on the root partition even if the directory appears empty. Here is some of the relevant lines from the journal: Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: Deactivating block devices: Jun 14 00:00:04 libvirt-host systemd[1]: Unmounted /var/lib/libvirt/qemu/save. Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [UMOUNT]: unmounting libvirt_lvm-suspenddata (dm-3) mounted on /var/lib/libvirt/qemu/save... done Jun 14 00:00:04 libvirt-host libvirt-guests.sh[4349]: Running guests on default URI: vps1, vps2, vps3 Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [MD]: deactivating raid1 device md1... done Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending guests on default URI... Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:05 libvirt-host blkdeactivate[4343]: [LVM]: deactivating Volume Group libvirt_lvm... skipping Jun 14 00:00:10 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: 5.989 GiB Jun 14 00:00:15 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:20 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1832859/+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 1885242] Re: intel graphics
Please describe the problem you are experiencing. ** 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/1885242 Title: intel graphics Status in Ubuntu: Incomplete Bug description: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY25PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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/+bug/1885242/+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 1885242] [NEW] intel graphics
Public bug reported: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-da0xxx dmi.product.sku: 5AY25PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885242 Title: intel graphics Status in xorg package in Ubuntu: New Bug description: intel graphics ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 26 08:52:02 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84a6] InstallationDate: Installed on 2020-06-16 (9 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 004: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN Adapter Bus 001 Device 003: ID 0408:5362 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-da0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=133d6e95-26aa-4120-a8c3-12d394f42ef4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84A6 dmi.board.vendor: HP dmi.board.version: 80.43 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/10/2020:svnHP:pnHPLaptop15-da0xxx:pvrType1ProductConfigId:rvnHP:rn84A6:rvr80.43:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook
[Touch-packages] [Bug 1878371] Re: Displays overlap
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1878371 Title: Displays overlap Status in xorg package in Ubuntu: New Bug description: Displays were correct under 19.10, upgraded to 20.04. I have 2 monitors. Mon1: Right, Portrait is 1920x1080. Mon2: Left, Landscape is 3840x2160. The display to Mon2 overlaps Mon1 display by approx 90%. Moving cursor to far right causes display 2 on Mon2 to slide left. Moving cursor to far left causes display 2 to slide right over the top of display 1. Both displays in settings are correct. The problem appears as if the window for display 2 is a port on a screen approx 5000x2160. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 09:31:07 2020 DistUpgraded: 2020-05-12 14:33:26,654 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-51-generic, x86_64: installed nvidia, 390.132, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:858b] InstallationDate: Installed on 2017-03-02 (1167 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05430fcd-4b22-4784-bef0-4438e1c00dd8 ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 11/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9904 dmi.board.asset.tag: Default string dmi.board.name: X99-A II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9904:bd11/30/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-08-17T11:15:24.518740 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue May 12 21:39:37 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1876621] Re: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1876621 Title: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes Status in xorg package in Ubuntu: New Bug description: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/1876621/+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 1877939] Re: Unwanted desktop panning when using two displays
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1877939 Title: Unwanted desktop panning when using two displays Status in xorg package in Ubuntu: New Bug description: I use two displays. One has a resolution of 3840x2160, and another one is to the right of that with a resolution of 1080x1920 in "Portrait Left" mode. I use "Join Displays" in Settings > Displays. When I configure this setup using Settings > Displays, my main desktop ends up being too big, extending to the secondary monitor to the right. When I move my mouse to the right edge of the secondary screen, the desktop pans. When I arrange the secondary monitor to the left of my main display, this bug does not occur. Secondary monitor on the right (bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+3840+0 right (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 708mm x 399mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) Secondary monitor on the left (no bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 4920 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+0+0 right (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+1080+0 (normal left inverted right x axis y axis) 708mm x 399mm 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) The only difference between these two situations is that I dragged the monitor from the right to the left in Settings > Displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 09:03:00 2020 DistUpgraded: 2020-05-10 23:03:38,881 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-51-generic, x86_64: installed nvidia, 435.21, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106 [GeForce RTX 2060 Rev. A] [103c:6903] InstallationDate:
[Touch-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Touch-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1881342 Title: Display settings are completely broken in 20.04 Status in xorg package in Ubuntu: New Bug description: This is after doing a fresh Ubuntu 20.04 installation, on my machine equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait mode. This used to work properly in Ubuntu 19.10, but is utterly broken in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work anymore. It'd be much easier to show what's going on with a video, so here goes: https://youtu.be/OHxKWfSxhsE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881342/+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 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
*** This bug is a duplicate of bug 1874217 *** https://bugs.launchpad.net/bugs/1874217 ** This bug is no longer a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape ** This bug has been marked a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same issue here - I can't switch to HSP/HFP mode on Ubuntu 20.04 uname -r 5.4.0-39-generic pulseaudio --version pulseaudio 13.99.1 Device 38:18:4C:94:DE:B2 (public) Name: WH-1000XM3 Alias: WH-1000XM3 Class: 0x00240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Vendor specific (-deca-fade-deca-deafdecacaff) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (7b265b0e-2232-4d45-bef4-bb8ae62f813d) UUID: Vendor specific (81c2e72a-0591-443e-a1ff-05f988593351) UUID: Vendor specific (931c7e8a-540f-4686-b798-e8df0a2ad9f7) UUID: Vendor specific (96cc203e-5068-46ad-b32d-e316f5e069ba) UUID: Vendor specific (b9b213ce-eeab-49e4-8fd9-aa478ed1b26b) UUID: Vendor specific (f8d1fbe4-7966-4334-8024-ff96c9330e15) Modalias: usb:v054Cp0CD3d0422 ManufacturerData Key: 0x012d ManufacturerData Value: 04 00 01 31 00 01 b3 ee e4 3f 00 60 d0 00 00 00 ...1.?.` 00 00 00 ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832859] Re: during shutdown libvirt-guests gets stopped after file system unmount
This seems like a new problem to my after 6/24/20 update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1832859 Title: during shutdown libvirt-guests gets stopped after file system unmount Status in lvm2: New Status in libvirt package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New Status in lvm2 package in Fedora: Confirmed Bug description: When using automatic suspend at reboot/shutdown, it makes sense to store the suspend data on a separate partition to ensure there is always enough available space. However this does not work, as the partition gets unmounted before or during libvirt suspend. Steps to reproduce: 1. Use Ubuntu 18.04.02 LTS 2. Install libvirt + qemu-kvm 3. Start a guest 4. Set libvirt-guests to suspend at shutdown/reboot by editing /etc/default/libvirt-guests 5. Create a fstab entry to mount a separate partition to mount point /var/lib/libvirt/qemu/save. Then run sudo mount /var/lib/libvirt/qemu/save to mount the partition. 6. Reboot Expected result: The guest suspend data would be written to the /var/lib/libvirt/qemu/save, resulting in the data being stored at the partition specified in fstab. At boot, this partition would be mounted as specified in fstab and libvirt-guest would be able to read the data and restore the guests. Actual result: The partition gets unmounted before libvirt-guests suspends the guests, resulting in the data being stored on the partition containing the root file system. During boot, the empty partition gets mounted over the non-empty /var/lib/libvirt/qemu/save directory, resulting in libvirt-guests being unable to read the saved data. As a side effect, the saved data is using up space on the root partition even if the directory appears empty. Here is some of the relevant lines from the journal: Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: Deactivating block devices: Jun 14 00:00:04 libvirt-host systemd[1]: Unmounted /var/lib/libvirt/qemu/save. Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [UMOUNT]: unmounting libvirt_lvm-suspenddata (dm-3) mounted on /var/lib/libvirt/qemu/save... done Jun 14 00:00:04 libvirt-host libvirt-guests.sh[4349]: Running guests on default URI: vps1, vps2, vps3 Jun 14 00:00:04 libvirt-host blkdeactivate[4343]: [MD]: deactivating raid1 device md1... done Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending guests on default URI... Jun 14 00:00:05 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:05 libvirt-host blkdeactivate[4343]: [LVM]: deactivating Volume Group libvirt_lvm... skipping Jun 14 00:00:10 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: 5.989 GiB Jun 14 00:00:15 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... Jun 14 00:00:20 libvirt-host libvirt-guests.sh[4349]: Suspending vps1: ... To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1832859/+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 1874501] Re: vgscan --mknodes creates block device multipath nodes in /dev/mapper
lvm2 is buggy, but we're just gonna tip toe around it. probert/curtin/subiquity are fixed, and lvm2 can keep it's trap open for the next software to walk into it. ** Changed in: lvm2 (Ubuntu Groovy) Status: Fix Committed => Won't Fix ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Also affects: subiquity Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu) Status: Fix Committed => Won't Fix ** Changed in: subiquity Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874501 Title: vgscan --mknodes creates block device multipath nodes in /dev/mapper Status in subiquity: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in lvm2 package in Ubuntu: Won't Fix Status in lvm2 source package in Groovy: Won't Fix Bug description: Description:Ubuntu 20.04 LTS Release:20.04 # apt-cache policy multipath-tools multipath-tools: Installed: 0.8.3-1ubuntu2 Candidate: 0.8.3-1ubuntu2 Version table: *** 0.8.3-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages 100 /var/lib/dpkg/status /dev/mapper/mpatha is symlink which points to ../../dm-X device /dev/mapper/mpath is block device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: multipath-tools 0.8.3-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: s390x CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Thu Apr 23 17:32:12 2020 LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release s390x (20200423.1) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: multipath-tools UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.multipath.conf: defaults { user_friendly_names yes skip_kpartx no verbosity 4 } mtime.conffile..etc.multipath.conf: 2020-04-23T15:47:28.659850 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1874501/+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 1882583] Re: [SRU] Enable support for Victoria Cloud Archive
A new package version with this fix has been uploaded to the focal unapproved queue. -- 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/1882583 Title: [SRU] Enable support for Victoria Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Triaged Status in software-properties source package in Groovy: Fix Released Bug description: Please add support for: cloud-archive:victoria cloud-archive:victoria-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the victoria cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:victoria sudo add-apt-repository cloud-archive:victoria-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882583/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
Here is an app that is used to make video so if you want to make funny video so click on the link to download it from here https://www.myapklab.com/dubsmash-app-free-download-version-latest-for- android/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: Fix Released Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1877939] Re: Unwanted desktop panning when using two displays
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1877939 Title: Unwanted desktop panning when using two displays Status in xorg package in Ubuntu: New Bug description: I use two displays. One has a resolution of 3840x2160, and another one is to the right of that with a resolution of 1080x1920 in "Portrait Left" mode. I use "Join Displays" in Settings > Displays. When I configure this setup using Settings > Displays, my main desktop ends up being too big, extending to the secondary monitor to the right. When I move my mouse to the right edge of the secondary screen, the desktop pans. When I arrange the secondary monitor to the left of my main display, this bug does not occur. Secondary monitor on the right (bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+3840+0 right (normal left inverted right x axis y axis) 527mm x 296mm panning 1920x1920+3840+0 tracking 5760x2160+0+0 border 0/0/0/0 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 708mm x 399mm panning 4680x2160+0+0 tracking 5760x2160+0+0 border 0/0/0/0 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) Secondary monitor on the left (no bug): minnozz@lux:~$ xrandr Screen 0: minimum 8 x 8, current 4920 x 2160, maximum 32767 x 32767 DVI-D-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected 1080x1920+0+0 right (normal left inverted right x axis y axis) 527mm x 296mm 1920x1080 60.00*+ 59.9450.00 1600x1200 60.00 1600x900 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-0 connected primary 3840x2160+1080+0 (normal left inverted right x axis y axis) 708mm x 399mm 3840x2160 60.00*+ 29.9824.00 1024x768 60.00 800x600 60.32 640x480 59.94 DP-1 disconnected (normal left inverted right x axis y axis) The only difference between these two situations is that I dragged the monitor from the right to the left in Settings > Displays. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 11 09:03:00 2020 DistUpgraded: 2020-05-10 23:03:38,881 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-51-generic, x86_64: installed nvidia, 435.21, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU106 [GeForce RTX 2060 Rev. A] [103c:6903] InstallationDate:
[Touch-packages] [Bug 1879209] Re: Display settings configures dual display resolution incorrectly
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1879209 Title: Display settings configures dual display resolution incorrectly Status in xorg package in Ubuntu: New Bug description: I have two displays side-by-side: one that is 2560x1440 in landscape and a second that is 1280x1024 in portrait. In earlier versions of Ubuntu (definitely in 18.04 and 19.10) I was able to configure this using Display Settings in the default windowing environment. After upgrading to Ubuntu 20.04 it seems Display Settings is computing an incorrect horizontal resolution for the combined display. This results in a display that is too wide for the monitors that pans when I mouse toward the edges. xrandr is reporting that it's trying to make a display that is 3840x1440 (2560+1280) instead of 3584x1440 (2560+1024), so I assume something is doing the math before considering the smaller display is in portrait instead of landscape. here is the output from xrandr: $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1440, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 connected 1024x1280+2560+0 left (normal left inverted right x axis y axis) 376mm x 301mm panning 1280x1280+2560+0 tracking 3840x1440+0+0 border 0/0/0/0 1280x1024 60.02*+ 75.02 1280x960 60.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 640x480 75.0072.8159.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm panning 2816x1440+0+0 tracking 3840x1440+0+0 border 0/0/0/0 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0059.9450.0029.9725.0023.98 1680x1050 59.95 1600x1200 60.00 1280x1024 75.0260.02 1280x720 60.0059.9450.00 1200x960 59.90 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-5 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 17 20:35:03 2020 DistUpgraded: 2020-04-24 00:21:43,329 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM200 [GeForce GTX 980 Ti] [10de:17c8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM200 [GeForce GTX 980 Ti] [1043:8546] InstallationDate: Installed on 2018-09-17 (608 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6f78923c-30a0-48fc-a273-9b33bfc359f0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (23 days ago) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name:
[Touch-packages] [Bug 1878371] Re: Displays overlap
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1878371 Title: Displays overlap Status in xorg package in Ubuntu: New Bug description: Displays were correct under 19.10, upgraded to 20.04. I have 2 monitors. Mon1: Right, Portrait is 1920x1080. Mon2: Left, Landscape is 3840x2160. The display to Mon2 overlaps Mon1 display by approx 90%. Moving cursor to far right causes display 2 on Mon2 to slide left. Moving cursor to far left causes display 2 to slide right over the top of display 1. Both displays in settings are correct. The problem appears as if the window for display 2 is a port on a screen approx 5000x2160. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.132 Fri Nov 1 00:40:14 PDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed May 13 09:31:07 2020 DistUpgraded: 2020-05-12 14:33:26,654 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-51-generic, x86_64: installed nvidia, 390.132, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:858b] InstallationDate: Installed on 2017-03-02 (1167 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUS All Series ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=05430fcd-4b22-4784-bef0-4438e1c00dd8 ro elevator=deadline quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-12 (0 days ago) dmi.bios.date: 11/30/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 9904 dmi.board.asset.tag: Default string dmi.board.name: X99-A II dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr9904:bd11/30/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-AII:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-08-17T11:15:24.518740 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue May 12 21:39:37 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1876621] Re: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1876621 Title: Settings panel applies a bad display configuration if side monitor is rotated, may fail to revert changes Status in xorg package in Ubuntu: New Bug description: In my configuration, the main monitor is landscape and the secondary monitor, to the right, is portrait. The most common result appears to be the primary display as seen by the DE being far wider than the actual monitor, and the second monitor being disabled entirely. Hitting "revert changes" usually doesn't actually change things back. Further, the xrandr CLI tool behaves strangely until the side monitor is removed from the layout entirely. Things behave as expected if the side monitor is set to landscape. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Sun May 3 15:11:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP102 [GeForce GTX 1080 Ti] [3842:6393] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=216c25da-8351-4944-9308-cf9b4ec2ba88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2004 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87M-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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/1876621/+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 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1881342] Re: Display settings are completely broken in 20.04
*** This bug is a duplicate of bug 1874567 *** https://bugs.launchpad.net/bugs/1874567 ** This bug is no longer a duplicate of bug 1874217 [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors ** This bug has been marked a duplicate of bug 1874567 [nvidia] Rotating secondary monitor to portrait fails, results in landscape -- 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/1881342 Title: Display settings are completely broken in 20.04 Status in xorg package in Ubuntu: New Bug description: This is after doing a fresh Ubuntu 20.04 installation, on my machine equipped with 3 monitors using an SLI of nvidia GTX 980. My 3 monitors are 1 4k monitor in landscape mode, and 2 1080p monitors in portrait mode. This used to work properly in Ubuntu 19.10, but is utterly broken in 20.04. Portrait mode doesn't work anymore, and scaling doesn't work anymore. It'd be much easier to show what's going on with a video, so here goes: https://youtu.be/OHxKWfSxhsE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881342/+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 1669517] Re: apt-key del must absolutely detect all errors, and then provide NON-zero return code and error message
We will not be changing the behavior here. apt-key del working if they key was not present in the keyring is important to maintain, so that we do not break the maintainer scripts using it (which should be tested, and should be the only users of this). ** Changed in: apt (Ubuntu) Status: Triaged => Won't Fix -- 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/1669517 Title: apt-key del must absolutely detect all errors, and then provide NON- zero return code and error message Status in apt package in Ubuntu: Won't Fix Bug description: Currently, 'apt-key del' does NOT detect that the keyid given in parameter is invalid : It displays 'OK' and provides a return code equal to zero (see log below). I consider that letting erroneously believe that a GPG key has been successfully removed is a security issue. In fact 'apt-key del' must absolutely detect all errors, and then provide NON-zero return code and error message. # wget -q -O - https://oss.oracle.com/el4/RPM-GPG-KEY-oracle | apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg add - OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del 1024D/B38A8516 OK # echo $? 0 # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del B38A8516 OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list # ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.19 ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49 Uname: Linux 4.4.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 2 17:34:07 2017 InstallationDate: Installed on 2014-11-03 (849 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1669517/+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 1571506] Re: update-initramfs should include firmware from /lib/firmware/updates
@Qiang Yu In Ubuntu, none of the linux-firmware packages ship anything in /updates directly. /lib should only contain files managed by dpkg / installed from the Ubuntu Archive. We ship all up to date firmware for all devices. I do not think it is reasonable to start supporting /updates directory, and thus suggesting that users drop-in firmware files there, which are not managed by dpkg. Ubuntu, releases firmware updates for AMD hardware, if we are missing any firmware updates for AMD, you can contact secur...@ubuntu.com ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Won't Fix -- 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/1571506 Title: update-initramfs should include firmware from /lib/firmware/updates Status in initramfs-tools package in Ubuntu: Won't Fix Bug description: according to the kernel doc http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/firmware_class/README Linux kernel will search firmware from "/lib/firmware/updates/" UTS_RELEASE, "/lib/firmware/updates", "/lib/firmware/" UTS_RELEASE, "/lib/firmware" But the add module function in initramfs-tools won't search the "/lib/firmware/updates". This problem applies to all Ubuntu releases. Attach patch to fix this. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Mon Apr 18 14:24:29 2016 InstallationDate: Installed on 2014-04-23 (725 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: initramfs-tools 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/1571506/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
Eoan and later d-i, new installer, curtin do not install /etc/kernel-img.conf. Upgraded systems keep having it (ie. installed with bionic or xenial, and upgraded). Can you please let me know if _removing_ /etc/kernel-img.conf breaks $ sudo make install, and if adding /etc/kernel-img.conf back fixes $ sudo make install? Cause the expectation is that `/etc/kernel-img.conf` should not be there, yet everything should still work correctly. I think somewhere something is reading "link_in_boot=yes" and was not updated with the new implicit default to always assume that on recent ubuntu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks
** Tags removed: rls-ff-incoming ** Tags added: rls-ff-notfixing -- 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/1867007 Title: zfs-initramfs fails with multiple rpool on separate disks Status in grub2 package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in zfs-linux package in Ubuntu: Fix Released Bug description: == Test Case == 1. On a multi disks setup, install Ubuntu with ZFS on disk 1 2. Reboot and make sure everything works as expected 3. Do a second installation and install Ubuntu with ZFS on disk 2 4. Reboot * Expected Result * GRUB should display all the machines available and let the user select which installation to boot * Actual result * - Only one machine is listed - initramfs crashes because there are several pool with the same name but different IDs and import the pools by name - Same problem in the systemd generator which will try to import all the rpools. == Original Description == I had an Ubuntu old installation that used a ZFS root, using the layout described in the ZFS on Linux docs. Consequently, the pool name for my Ubuntu installation was "rpool". I'm currently encountering an issue with that pool that only allows me to mount it read-only. So, I'd like to replicate the datasets from there to a new device. On the new device, I've set up a ZFS system using the Ubuntu 20.04 daily installer (March 9, 2020). This setup creates a new pool named "rpool". So, with both devices inserted, I have two distinct pools each named "rpool", one of which will kernel panic if I try to mount it read-write. ZFS is fine with having multiple pools with the same name. In these cases, you use `zfs import` with the pool's GUID and give it a distinct pool name on import. However, the grub config for booting from ZFS doesn't appear to handle multiple pools with the same rpool name very well. Rather than using the pool's GUID, it uses the name, and as such, it's unable to boot properly when another pool with the name "rpool" is attached to the system. I think it'd be better if the config were written in such a way that `update-grub` generated boot config bound to whatever pool it found at the time of its invocation, and not start searching through all pools dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system with a ZFS root that boots just fine. But, the moment I attach the old pool, also named "rpool", I'm no longer able to boot up my system even though I haven't removed the good pool and I haven't re-run `update- grub`. Instead of booting, I'm thrown into the grub command line. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I normally don't like this, but it's a one-character change so it's easier to start with the solution: diff -u -r1.1 /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf --- /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf +++ /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf @@ -1,2 +1,2 @@ [connectivity] -uri=http://connectivity-check.ubuntu.com/ +uri=http://connectivity-check.ubuntu.com./ Making this name absolute instead of relative avoids spurious resolutions of "connectivity-check.ubuntu.com.your_domain." This removes a fair amount of NXDOMAIN error noise in journalctl. Observing the issue and the fix requires 3 terminals: 1. tcpdump -i any 'port domain' 2. journalctl --boot -u systemd-resolved -f 3. nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe the NXDOMAIN noise over a couple few minutes Now make the hostname absolute with the trailing dot above and run: systemctl reload NetworkManager Wait 1 min for things to stabilize. Test again: nmcli c down "Wired connection 1"; nmcli c up "Wired connection 1" => observe non-zero but significantly reduced NXDOMAIN noise over a couple few minutes Originally reported at https://askubuntu.com/a/1242611/117217 Plenty of people annoyed by NXDOMAIN warnings, just Google it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1880258/+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 1883027] Re: dump_acpi_tables.py: fix incorrect output and change format
** Tags removed: rls-ff-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/1883027 Title: dump_acpi_tables.py: fix incorrect output and change format Status in Apport: Confirmed Status in apport package in Ubuntu: In Progress Status in apport source package in Focal: In Progress Status in apport source package in Groovy: In Progress Bug description: [Impact] dump_acpi_tables.py does not always generate 4-char table names (which is defined by ACPI spec), and it can miss or duplicate data of ACPI tables in /sys/firmware/acpi/tables. [Test Case] Tested with ACPI tables from Dell's Precision 3530. The outputs are almost the same as ones from "acpidump". The difference is the order of ACPI tables in the output but the order is not important. 1. run dump_acpi_tables.py 2. run acpidump 3. compare the outputs Note: acpidump is from acpica-tools [Regression Potential] Formats were changed to be the same as outputs from "acpidump", but known tools, such as acpiexec and fwts, by default reads outputs from acpidump and they do not reply on spaces and upper/lower cases. [Other Info] See original bug reports as below: dump_acpi_tables.py generates log files that is similar as the output from "acpidump" in acpica-tools. The output can be passed to other utilities in acpica-tools and fwts. It, however, has some subtle differences and some errors. Summary: 1. ACPI tables have 4-char signatures - meaning SSDT's are SSDT, not SSDT1, SSDT2 and so on. Each table is unique by its table ID. Original: SSDT1, SSDT2, SSDT3 ... Changed: SSDT, SSDT, SSDT ... 2. (Minor) acpidump outputs are all in upper cases 3. (Minor) acpidump offset are aligned by data, not address Original: FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D SAVCRDCANCRNrNPM 1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43 VRDC Changed: FFF0: 53 41 56 43 52 44 43 41 4E 43 52 4E 72 4E 50 4D SAVCRDCANCRNrNPM 1: 56 0A 04 00 0C FC FF FF FF 0A 03 0A 03 52 44 43 VRDC 4. (Bug) dump_acpi_tables.py generates an extra line when data sizes are multiple of 16 bytes Original: 05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 00.HPSD.SPSD 05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 00.HPSD.SPSD Corrected: 05F0: 30 30 0B 00 08 00 A4 48 50 53 44 A4 53 50 53 44 00.HPSD.SPSD 5. (Bug) dump_acpi_tables.py misses an line when data sizes are multiple of 15 bytes Original: 07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43 B..\/._SB_UBTCCC Corrected: 07E0: 42 0A 87 5C 2F 03 5F 53 42 5F 55 42 54 43 43 43 B..\/._SB_UBTCCC 07F0: 49 33 86 5C 2E 5F 53 42 5F 55 42 54 43 0A 80 I3.\._SB_UBTC.. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1883027/+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 1860620] Re: ubuntu-desktop-minimal should not depend on mysql libs
this should be looked at by the Desktop Team. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860620 Title: ubuntu-desktop-minimal should not depend on mysql libs Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: After upgrading to 20.04 I decided to remove packages that I don't need or use. I was surprised to find that mysql client, server and common packages were installed, as I could not remember having installed mysql -- I don't use it or develop for it... When I removed them, ubuntu-desktop-minimal went along for the ride: c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common mysql-server-core-5.7 Reading package lists... Done Building dependency tree Reading state information... Done Package 'mysql-client-core-5.7' is not installed, so not removed Package 'mysql-server-core-5.7' is not installed, so not removed The following package was automatically installed and is no longer required: libgsound0 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* mysql-common* ubuntu-desktop-minimal* 0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded. After this operation, 28.4 MB disk space will be freed. (Reading database ... 381127 files and directories currently installed.) Removing ubuntu-desktop-minimal (1.443) ... Removing gnome-control-center (1:3.34.1-1ubuntu3) ... Removing colord (1.4.4-1ubuntu1) ... Removing libsane:amd64 (1.0.27-3.2ubuntu3) ... Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ... Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ... Removing mysql-common (5.8+1.0.5ubuntu2) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.32.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for man-db (2.9.0-2) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for udev (244-3ubuntu1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu1) ... (Reading database ... 380812 files and directories currently installed.) Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ... Purging configuration files for colord (1.4.4-1ubuntu1) ... And, reinstalling ubuntu-desktop-minimal wants to brings them back, even with recommends and suggests turned off: c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install- --no-install-recommends --no-install-suggests c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install-suggests Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common Suggested packages: colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip Recommended packages: gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker sane-utils firefox hplip The following NEW packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common ubuntu-desktop-minimal 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6,114 kB of archives. After this operation, 28.4 MB of additional disk space will be used. Do you want to continue? [Y/n] This seems really wrong... and looks like a transitive dependency, as I don't see it in apt-get showpkg ubuntu-desktop-minimal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop-minimal 1.443 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux ashmem_linux ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 19:26:53 2020 InstallationDate: Installed on 2018-08-26 (514 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1860620/+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 1872560] Re: integer overflow in whoopsie 0.2.69
** Changed in: whoopsie (Ubuntu) Status: Confirmed => Incomplete -- 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/1872560 Title: integer overflow in whoopsie 0.2.69 Status in whoopsie package in Ubuntu: Incomplete Bug description: Hi, I have found a security issue on whoopsie 0.2.69 and earlier. ## Vulnerability in whoopsie - whoopsie 0.2.69 and earlier have a heap-based buffer overflow vulnerability. - An attacker can cause a denial of service (memory corruption and application crash) via a crafted .crash file. ## Basic When a program has been crashed, Linux system tries to create a '.crash' file on '/var/crash/' directory with python script located in '/usr/share/apport/apport'. The file contains a series of system crash information including core dump, syslog, stack trace, memory map info, etc. After the creation of '.crash' file, whoopsie extracts the above information from the '.crash' file and encodes it into binary json (bson) format. Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error Report system. ## Vulnerability Unfortunately, we have found a heap-based buffer overflow vulnerability during the encoding, when whoopsie attempts to bsonify with crafted crash file. The data in '.crash' file is stored in key-value form and the whoopsie separately measures the length of 'key' and 'value' to allocate memory region during the encoding. A heap-based buffer overflow can occur when an integer overflow happens on a variable that contains length of 'key'. FYI, a issue to that raised by 'value' is well covered by performing exception handling. @[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663] const uint32_t len = strlen( name ) + 1; - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file. @[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627] b->data = bson_realloc( b->data, new_size ); - Unexpected small memory region is allocated due to above integer overflow. @[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680] bson_append( b, name, len ); - Memory corruption happens when unexpected small memory region is allocated. ## Attack Scenario 1) Create a fake.crash file - '.crash' file is composed of the following format: 'key : value'. - To cause the overflow attack, the size of 'key' should be in double amount of INT32_MAX. - The size of 'value' doesn’t matter, but not zero length. $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash $ cat fake.crash AAA … AA : B 2) Trigger the whoopsie to read the fake.crash file - Just create 'fake.upload' file by touch command. - Or launch apport-gtk gui or apport-bug cli application. 3) Check out the result - After a while, the whoopsie has been killed by segmentation fault. Sincerely, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: pam (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed Status in gdm: New Status in gdm3 package in Ubuntu: Confirmed Status in pam package in Ubuntu: Invalid Bug description: the pam profile for gdm-smartcard is missing. gdm refuses to login with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are pregenerated into debian/ and installed from there; gdm-smartcard is left out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 14:30:30 2020 InstallationDate: Installed on 2016-05-23 (1376 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+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 1818968] Re: can't select text from the start of a line on a terminator shell
** Changed in: gtk Status: New => Fix Released -- 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/1818968 Title: can't select text from the start of a line on a terminator shell Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Ever since yaru became the default theme, I'm not able to select text from the start of the line anymore, instead it'll try to resize the split terminator shell. To reproduce: - open terminator - split the window vertically - try to select text on the right side terminal - notice you can't select the first character, instead it will try to resize the split To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1818968/+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 146398] Re: gdebi ignores Replaces directive in case of Conflict
Here is an updated foo-packages.tar.gz file to reproduce this issue. The updates mostly deal with changes in Debian policy such as adding debian/compat and updating DH_COMPAT. The new foo-packages.tar.gz also contains pre-built packages which you are free to use or delete and rebuild. ** Attachment added: "Test packages" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/146398/+attachment/5387168/+files/foo-packages.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/146398 Title: gdebi ignores Replaces directive in case of Conflict Status in python-apt package in Ubuntu: Triaged Bug description: Binary package hint: gdebi I have encountered this problem with the CrossOver Office (http://www.codeweavers.com/products/cxoffice/) packages. They come in multiple flavors, but only one can be installed at a given time. The more capable flavors use the 'Replaces' directive to smoothly 'upgrade' the less capable ones.This works fine with dpkg, but gdebi instead gives me an error as if the Replaces directive was not there (this directive is described in section 7.5.2 of the Debian Policy Manual). I have reproduced the situation with dummy packages so you have all the details. You can get them there: * source (1.4KB) http://fgouget.free.fr/tmp/gdebi/foo-packages.tar.gz * basic package (1.2KB) http://fgouget.free.fr/tmp/gdebi/foo_1.0.0-1_i386.deb * sophisticated package (1.2KB) http://fgouget.free.fr/tmp/gdebi/foo-pro_1.0.0-1_i386.deb Here is how to reproduce the problem: $ sudo gdebi foo_1.0.0-1_i386.deb Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Package for testing gdebi's Replaces support This is the package to be replaced by the more 'sophisticated' version. Do you want to install the software package? [y/N]:y Selecting previously deselected package foo. (Reading database ... 151236 files and directories currently installed.) Unpacking foo (from foo_1.0.0-1_i386.deb) ... Setting up foo (1.0.0-1) ... $ sudo gdebi foo-pro_1.0.0-1_i386.deb Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done This package is uninstallable Conflicts with the installed package 'foo' So gdebi does not want to replace the foo package with foo-pro. I think it should maybe warn the user but still allow him to proceed. With dpkg there is no issue: $ dpkg -i foo-pro_1.0.0-1_i386.deb Selecting previously deselected package foo-pro. dpkg: considering removing foo in favour of foo-pro ... dpkg: yes, will remove foo in favour of foo-pro. (Reading database ... 151239 files and directories currently installed.) Unpacking foo-pro (from foo-pro_1.0.0-1_i386.deb) ... Setting up foo-pro (1.0.0-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/146398/+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 146398] Re: gdebi ignores Replaces directive in case of Conflict
This 12+ years old bug is still present in gdebi 0.9.5.7 (as shipped in Ubuntu 16.10 to the current 20.04 and Debian 10 for instance). Given that gdebi 0.9.5.7 was released in 2015 I have to ask the question: Is gdebi still maintained? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/146398 Title: gdebi ignores Replaces directive in case of Conflict Status in python-apt package in Ubuntu: Triaged Bug description: Binary package hint: gdebi I have encountered this problem with the CrossOver Office (http://www.codeweavers.com/products/cxoffice/) packages. They come in multiple flavors, but only one can be installed at a given time. The more capable flavors use the 'Replaces' directive to smoothly 'upgrade' the less capable ones.This works fine with dpkg, but gdebi instead gives me an error as if the Replaces directive was not there (this directive is described in section 7.5.2 of the Debian Policy Manual). I have reproduced the situation with dummy packages so you have all the details. You can get them there: * source (1.4KB) http://fgouget.free.fr/tmp/gdebi/foo-packages.tar.gz * basic package (1.2KB) http://fgouget.free.fr/tmp/gdebi/foo_1.0.0-1_i386.deb * sophisticated package (1.2KB) http://fgouget.free.fr/tmp/gdebi/foo-pro_1.0.0-1_i386.deb Here is how to reproduce the problem: $ sudo gdebi foo_1.0.0-1_i386.deb Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done Package for testing gdebi's Replaces support This is the package to be replaced by the more 'sophisticated' version. Do you want to install the software package? [y/N]:y Selecting previously deselected package foo. (Reading database ... 151236 files and directories currently installed.) Unpacking foo (from foo_1.0.0-1_i386.deb) ... Setting up foo (1.0.0-1) ... $ sudo gdebi foo-pro_1.0.0-1_i386.deb Reading package lists: Done Reading state information: Done Reading state information: Done Reading state information: Done This package is uninstallable Conflicts with the installed package 'foo' So gdebi does not want to replace the foo package with foo-pro. I think it should maybe warn the user but still allow him to proceed. With dpkg there is no issue: $ dpkg -i foo-pro_1.0.0-1_i386.deb Selecting previously deselected package foo-pro. dpkg: considering removing foo in favour of foo-pro ... dpkg: yes, will remove foo in favour of foo-pro. (Reading database ... 151239 files and directories currently installed.) Unpacking foo-pro (from foo-pro_1.0.0-1_i386.deb) ... Setting up foo-pro (1.0.0-1) ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/146398/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
Yeah I have considered it as nice drive-by improvement unrelated to this bug - and thanks for doing so. I just had sorted out some lose ends on rsyslog and they both where part of it. Since this didn't work last time it is not closed yet, but open at low prio. As explained TBH I think we won't do it (this bug) as SRU a second time. Oh yeah lets set Won't Fix to reflect that as well. ** Changed in: rsyslog (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: rsyslog (Ubuntu Eoan) Status: In Progress => Won't Fix ** Changed in: rsyslog (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Won't Fix Status in rsyslog source package in Disco: Won't Fix Status in rsyslog source package in Eoan: Won't Fix Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debianutils in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Triaged Status in debianutils package in Ubuntu: New Status in linux-base package in Ubuntu: New Bug description: When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+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 1885125] Re: merge 8.2006.0-1 and include apparmor fixes
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/rsyslog/+git/rsyslog/+merge/386381 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1885125 Title: merge 8.2006.0-1 and include apparmor fixes Status in rsyslog package in Ubuntu: In Progress Bug description: While checking for an upload for https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 I found that there is a new version 8.2006.0-1. Let us give this merge a shot to get groovy up to date ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1885125/+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 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps
** Tags added: id-5eeb87fddafe19544a50da51 -- 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/1861082 Title: [SRU] ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store Server: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Bug description: [Impact] Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap. [Test Case] Install subiquity snap: # sudo snap install subiquity --classic subiquity 20.06.1 aus Canonical✓ installiert # snap list | grep subiquity subiquity 20.06.1 1938 latest/stable canonical* classic ubuntu-bug subiquity results in message: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You are about to report a bug against the deb package, but you also a have snap published by canonical installed. You can contact them via https://bugs.launchpad.net/subiquity for help. Do you want to continue with the bug report against the deb? What would you like to do? Your options are: Y: Yes N: No C: Cancel === New/Expected Result === ubuntu-bug should ask the user if he/she wants to report the bug against the snap or deb package, if both are installed. If the snap is chosen, the "Snap" and "SnapSource" fields should be part of the report: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: subiquity 20.06.1 (stable) snap 2: subiquity (1938) deb package C: Cancel Please choose (1/2/C): 1 . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (46.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V Make sure the following two fields are part of the generated report: == Snap = subiquity 20.06.1 (stable) == SnapSource = subiquity [Regression Potential] Small; the change adds a new add_snap_info() method to report.py and is triggered in the ui.py logic only in cases which would have otherwise lead to an error message. Furthermore, the change has been uploaded to Groovy some while ago where it is being used and tested. [Original Bug Report] Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
** Tags added: id-5ed6b0877aa3de39fa0b89e6 -- 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/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Bionic: Invalid Status in glibc source package in Bionic: Invalid Status in initramfs-tools source package in Bionic: New Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: Fix Released Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+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 1885127] [NEW] ethernet interfaces explicity excluded from management in globally-managed-devices.conf
Public bug reported: The file `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` included with this package (installed via apt in 19.10 environment) contains the line: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma ``` In my system (laptop with no native ethernet), this results in the inability to easily use USB/ethernet adapters. After manually modifying: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet ``` the USB/ethernet adapter is detected and configured automatically by NetworkManager ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1885127 Title: ethernet interfaces explicity excluded from management in globally- managed-devices.conf Status in network-manager package in Ubuntu: New Bug description: The file `/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf` included with this package (installed via apt in 19.10 environment) contains the line: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma ``` In my system (laptop with no native ethernet), this results in the inability to easily use USB/ethernet adapters. After manually modifying: ``` unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma,except:type:ethernet ``` the USB/ethernet adapter is detected and configured automatically by NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885127/+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 1885125] Re: merge 8.2006.0-1 and include apparmor fixes
upload/8.2001.0-1ubuntu1 has the former delta already split -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1885125 Title: merge 8.2006.0-1 and include apparmor fixes Status in rsyslog package in Ubuntu: In Progress Bug description: While checking for an upload for https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 I found that there is a new version 8.2006.0-1. Let us give this merge a shot to get groovy up to date ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1885125/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
@Christian, https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 was a 'drive-by' merge proposal not associated with any LP (is that OK?). As such, I don't consider it related to this bug which can be closed now AFAICT. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-riscv - 5.4.0-27.31 --- linux-riscv (5.4.0-27.31) focal; urgency=medium * focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798) * Add support for Ambiq micro AM1805 RTC chip (LP: #1876667) - [config] riscv: disable am-1805 RTC driver * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config][focal/linux-riscv] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() - mm: limit boost_watermark on small zones - ceph: demote quotarealm lookup warning to a debug message - staging: gasket: Check the return value of gasket_get_bar_index() - coredump: fix crash when umh is disabled - iocost: protect iocg->abs_vdebt with iocg->waitq.lock - batman-adv: fix batadv_nc_random_weight_tq - batman-adv: Fix refcnt leak in
[Touch-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
This bug was fixed in the package linux-kvm - 5.4.0-1015.15 --- linux-kvm (5.4.0-1015.15) focal; urgency=medium [ Ubuntu: 5.4.0-37.41 ] * CVE-2020-0543 - SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2 - SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id - SAUCE: x86/cpu: Add 'table' argument to cpu_matches() - SAUCE: x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation - SAUCE: x86/speculation: Add SRBDS vulnerability and mitigation documentation - SAUCE: x86/speculation: Add Ivy Bridge to affected list linux-kvm (5.4.0-1012.12) focal; urgency=medium * focal/linux-kvm: 5.4.0-1012.12 -proposed tracker (LP: #1878795) * rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 (LP: #1875665) - [Config] Turn off CONFIG_RT_GROUP_SCHED [ Ubuntu: 5.4.0-34.38 ] * focal/linux: 5.4.0-34.38 -proposed tracker (LP: #1880118) * debian/scripts/file-downloader does not handle positive failures correctly (LP: #1878897) - [Packaging] file-downloader not handling positive failures correctly * Focal update: v5.4.41 upstream stable release (LP: #1878649) - USB: serial: qcserial: Add DW5816e support - nvme: refactor nvme_identify_ns_descs error handling - nvme: fix possible hang when ns scanning fails during error recovery - tracing/kprobes: Fix a double initialization typo - net: macb: Fix runtime PM refcounting - drm/amdgpu: move kfd suspend after ip_suspend_phase1 - drm/amdgpu: drop redundant cg/pg ungate on runpm enter - vt: fix unicode console freeing with a common interface - tty: xilinx_uartps: Fix missing id assignment to the console - devlink: fix return value after hitting end in region read - dp83640: reverse arguments to list_add_tail - fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks - ipv6: Use global sernum for dst validation with nexthop objects - mlxsw: spectrum_acl_tcam: Position vchunk in a vregion list properly - neigh: send protocol value in neighbor create notification - net: dsa: Do not leave DSA master with NULL netdev_ops - net: macb: fix an issue about leak related system resources - net: macsec: preserve ingress frame ordering - net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() - net_sched: sch_skbprio: add message validation to skbprio_change() - net: stricter validation of untrusted gso packets - net: tc35815: Fix phydev supported/advertising mask - net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() - net/tls: Fix sk_psock refcnt leak when in tls_data_ready() - net: usb: qmi_wwan: add support for DW5816e - nfp: abm: fix a memory leak bug - sch_choke: avoid potential panic in choke_reset() - sch_sfq: validate silly quantum values - tipc: fix partial topology connection closure - tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 - bnxt_en: Fix VF anti-spoof filter setup. - bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. - bnxt_en: Improve AER slot reset. - bnxt_en: Return error when allocating zero size context memory. - bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). - net/mlx5: DR, On creation set CQ's arm_db member to right value - net/mlx5: Fix forced completion access non initialized command entry - net/mlx5: Fix command entry leak in Internal Error State - net: mvpp2: prevent buffer overflow in mvpp22_rss_ctx() - net: mvpp2: cls: Prevent buffer overflow in mvpp2_ethtool_cls_rule_del() - HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices - sctp: Fix bundling of SHUTDOWN with COOKIE-ACK - Revert "HID: wacom: generic: read the number of expected touches on a per collection basis" - HID: usbhid: Fix race between usbhid_close() and usbhid_stop() - HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT - USB: uas: add quirk for LaCie 2Big Quadra - usb: chipidea: msm: Ensure proper controller reset using role switch API - USB: serial: garmin_gps: add sanity checking for data length - tracing: Add a vmalloc_sync_mappings() for safe measure - crypto: arch/nhpoly1305 - process in explicit 4k chunks - KVM: s390: Remove false WARN_ON_ONCE for the PQAP instruction - KVM: VMX: Explicitly clear RFLAGS.CF and RFLAGS.ZF in VM-Exit RSB path - KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER - KVM: arm64: Fix 32bit PC wrap-around - arm64: hugetlb: avoid potential NULL dereference - drm: ingenic-drm: add MODULE_DEVICE_TABLE - ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() - epoll: atomically remove wait entry on wake up - eventpoll: fix missing wakeup for ovflist in ep_poll_callback - mm/page_alloc: fix watchdog soft lockups during
[Touch-packages] [Bug 1884281] Re: UC20 images do not use predictable interface names on RPi4
The default for both core20 and server is 'net.ifnames=0' which disables persistent network interface names so it's expected to see eth0 and wlan0. cat /proc/cmdline coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:08:85:96 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc console=tty1 console=ttyS0,115200 quiet splash However, if I drop 'net.ifnames=0' from cmdline.txt I *do* get a persistent name on a 3B+ but *not* on a 4B. On a Pi 3B: $ udevadm info /sys/class/net/enxb827eb3eabfb P: /devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/net/enxb827eb3eabfb L: 0 E: DEVPATH=/devices/platform/soc/3f98.usb/usb1/1-1/1-1.1/1-1.1.1/1-1.1.1:1.0/net/enxb827eb3eabfb E: INTERFACE=enxb827eb3eabfb E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=5428547 E: ID_MM_CANDIDATE=1 E: ID_NET_NAMING_SCHEME=v245 E: ID_NET_NAME_MAC=enxb827eb3eabfb E: ID_OUI_FROM_DATABASE=Raspberry Pi Foundation E: ID_VENDOR=0424 E: ID_VENDOR_ENC=0424 E: ID_VENDOR_ID=0424 E: ID_MODEL=7800 E: ID_MODEL_ENC=7800 E: ID_MODEL_ID=7800 E: ID_REVISION=0300 E: ID_SERIAL=0424_7800 E: ID_TYPE=generic E: ID_BUS=usb E: ID_USB_INTERFACES=:ff00ff: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=lan78xx E: ID_USB_CLASS_FROM_DATABASE=Vendor Specific Class E: ID_VENDOR_FROM_DATABASE=Microchip Technology, Inc. (formerly SMSC) E: ID_PATH=platform-3f98.usb-usb-0:1.1.1:1.0 E: ID_PATH_TAG=platform-3f98_usb-usb-0_1_1_1_1_0 E: ID_NET_DRIVER=lan78xx E: ID_NET_LINK_FILE=/usr/lib/systemd/network/73-usb-net-by-mac.link E: ID_NET_NAME=enxb827eb3eabfb E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enxb827eb3eabfb E: TAGS=:systemd: $ udevadm test-builtin net_id /sys/class/net/enxb827eb3eabfb Load module index Parsed configuration file /usr/lib/systemd/network/99-default.link Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link Created link configuration context. Using default interface naming scheme 'v245'. ID_NET_NAMING_SCHEME=v245 ID_NET_NAME_MAC=enxb827eb3eabfb ID_OUI_FROM_DATABASE=Raspberry Pi Foundation Unload module index Unloaded link configuration context. /usr/lib/systemd/network/73-usb-net-by-mac.link is the systemd policy file that handles the renaming of eth0. On a Pi 4B: $ udevadm info /sys/class/net/eth0 P: /devices/platform/scb/fd58.ethernet/net/eth0 L: 0 E: DEVPATH=/devices/platform/scb/fd58.ethernet/net/eth0 E: INTERFACE=eth0 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=2348632 E: ID_MM_CANDIDATE=1 E: ID_NET_NAMING_SCHEME=v245 E: ID_NET_NAME_MAC=enxdca632088596 E: ID_OUI_FROM_DATABASE=Raspberry Pi Trading Ltd E: ID_PATH=platform-fd58.ethernet E: ID_PATH_TAG=platform-fd58_ethernet E: ID_NET_DRIVER=bcmgenet E: ID_NET_LINK_FILE=/usr/lib/systemd/network/99-default.link E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/eth0 E: TAGS=:systemd: $ udevadm test-builtin net_id /sys/class/net/eth0 Load module index Parsed configuration file /usr/lib/systemd/network/99-default.link Parsed configuration file /usr/lib/systemd/network/73-usb-net-by-mac.link Created link configuration context. Using default interface naming scheme 'v245'. ID_NET_NAMING_SCHEME=v245 ID_NET_NAME_MAC=enxdca632088596 ID_OUI_FROM_DATABASE=Raspberry Pi Trading Ltd Unload module index Unloaded link configuration context. systemd can't handle the platform attached bcmgenet driver of the Pi 4B so hence no renaming. I've created the following systemd file $ cat /etc/systemd/network/73-platform-net-by-mac.link [Match] Path=platform-*.ethernet [Link] NamePolicy=mac rebooted and ended up with a persistent net name for eth0: $ udevadm info /sys/class/net/enxdca632088596 P: /devices/platform/scb/fd58.ethernet/net/enxdca632088596 L: 0 E: DEVPATH=/devices/platform/scb/fd58.ethernet/net/enxdca632088596 E: INTERFACE=enxdca632088596 E: IFINDEX=2 E: SUBSYSTEM=net E: USEC_INITIALIZED=2337681 E: ID_MM_CANDIDATE=1 E: ID_NET_NAMING_SCHEME=v245 E: ID_NET_NAME_MAC=enxdca632088596 E: ID_OUI_FROM_DATABASE=Raspberry Pi Trading Ltd E: ID_PATH=platform-fd58.ethernet E: ID_PATH_TAG=platform-fd58_ethernet E: ID_NET_DRIVER=bcmgenet E: ID_NET_LINK_FILE=/etc/systemd/network/73-platform-net-by-mac.link E: ID_NET_NAME=enxdca632088596 E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enxdca632088596 /sys/subsystem/net/devices/enxdca632088596 E: TAGS=:systemd: Don't know if that's the right way to do this. Also, wlan0 still has a non-persistent name, so that needs to be addressed too if we want to go that route. ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/1884281 Title: UC20 images do not use predictable interface names on RPi4 Status in snapd:
[Touch-packages] [Bug 1885125] [NEW] merge 8.2006.0-1 and include apparmor fixes
Public bug reported: While checking for an upload for https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 I found that there is a new version 8.2006.0-1. Let us give this merge a shot to get groovy up to date ... ** Affects: rsyslog (Ubuntu) Importance: Undecided Assignee: Christian Ehrhardt (paelzer) Status: In Progress ** Changed in: rsyslog (Ubuntu) Status: New => In Progress ** Changed in: rsyslog (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1885125 Title: merge 8.2006.0-1 and include apparmor fixes Status in rsyslog package in Ubuntu: In Progress Bug description: While checking for an upload for https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 I found that there is a new version 8.2006.0-1. Let us give this merge a shot to get groovy up to date ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1885125/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
Let us kill the SRU - given what happened last time and that this is a a) disabled by default profile and b) user fixable by editing a conffile If it is ok with you I'd better focus on merging the latest version + your improvement in https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 ** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1874641] Re: Can't create writecache LV
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1874641 Title: Can't create writecache LV Status in lvm2 package in Ubuntu: Confirmed Bug description: #lvconvert --type writecache --cachesettings 'low_watermark=0 high_watermark=10 writeback_jobs=2048' --cachevol cache ssd WARNING: Unrecognised segment type writecache Invalid argument for --type: writecache Error during parsing of command line. lvm2 package was build without key --with-writecache=internal #lvm version LVM version: 2.03.07(2) (2019-11-30) Library version: 1.02.167 (2019-11-30) Driver version: 4.41.0 Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --exec-prefix= --bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 --with-cache=internal --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run --with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd --enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock --enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline --enable-udev_rules --enable-udev_sync #lsmod | grep dm_writecache dm_writecache 36864 0 #lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 #apt-cache policy lvm2 lvm2: Installed: 2.03.07-1ubuntu1 Candidate: 2.03.07-1ubuntu1 Version table: *** 2.03.07-1ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Apr 24 07:48:49 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) # lvs LVVG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert cache ssd -wi-a- <5.00g data ssd -wi-a- <10.00g To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1874641/+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 1868129] Re: I can't attach a writecache to LV
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1868129 Title: I can't attach a writecache to LV Status in lvm2 package in Ubuntu: Confirmed Bug description: #lvconvert --type writecache --cachesettings 'low_watermark=0 high_watermark=10 writeback_jobs=2048' --cachevol cache ssd/data WARNING: Unrecognised segment type writecache Invalid argument for --type: writecache Error during parsing of command line. I see that lvm2 package was build without key --with- writecache=internal #lvm version LVM version: 2.03.07(2) (2019-11-30) Library version: 1.02.167 (2019-11-30) Driver version: 4.41.0 Configuration: ./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --exec-prefix= --bindir=/bin --libdir=/lib/x86_64-linux-gnu --sbindir=/sbin --with-usrlibdir=/usr/lib/x86_64-linux-gnu --with-optimisation=-O2 --with-cache=internal --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --with-default-pid-dir=/run --with-default-run-dir=/run/lvm --with-default-locking-dir=/run/lock/lvm --with-thin=internal --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --enable-applib --enable-blkid_wiping --enable-cmdlib --enable-dmeventd --enable-dbus-service --enable-lvmlockd-dlm --enable-lvmlockd-sanlock --enable-lvmpolld --enable-notify-dbus --enable-pkgconfig --enable-readline --enable-udev_rules --enable-udev_sync # lsmod | grep dm_writecache dm_writecache 36864 0 #cat /etc/os-release NAME="Ubuntu" VERSION="20.04 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Focal Fossa (development branch)" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal #uname -a Linux sw-sed-ubuntu 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux #apt info lvm2 Package: lvm2 Version: 2.03.07-1ubuntu1 Priority: optional ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Thu Mar 19 16:06:17 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200317) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1868129/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand
On Thursday, June 25 2020, Łukasz Zemczak wrote: > Thank you for the verification Sergio! Could you please note down which > package version has been used for verification and what kind of > verification has been performed? Hi Łukasz, The package version I tested is 1:7.2p2-4ubuntu2.10. I performed the steps listed in the "Test Case" section of the SRU above. Everything worked as expected: $ ssh root@127.0.0.1 Warning: Permanently added '127.0.0.1' (ECDSA) to the list of known hosts. Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 5.4.0-31-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage The programs included with the Ubuntu system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. $ Thanks! -- Sergio GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1877454 Title: openssh-server hangs with AuthorizedKeysCommand Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Bug description: [Impact] On a default Xenial install, when sshd is configured to obtain the list of allowed keys using AuthorizedKeysCommand (or the list of allowed certificate principals using AuthorizedPrincipalsCommand), and if the command pointed by Authorized{Keys,Principals}Command generates a lot of output, sshd will hang while reading this same output. In a nutshell, the problem happens when the subprocess generates enough data to fill the pipe's buffer; in this scenario, sshd will wait(2) on the subprocess, which will be blocked trying to write the rest of the output. [Test Case] In order to reproduce the bug, one can: $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454 $ lxc shell openssh-server-bug1877454 # ssh-keygen (no need to choose a passphrase for the key, just hit ENTER on all prompts) # cat > authkeyscommand.sh << __EOF__ #!/bin/bash cat /root/.ssh/id_rsa.pub echo head -c 1M < /dev/urandom __EOF__ # chmod +x authkeyscommand.sh # cat >> /etc/ssh/sshd_config << __EOF__ AuthorizedKeysCommand /root/authkeyscommand.sh AuthorizedKeysCommandUser root __EOF__ # systemctl reload sshd.service # ssh root@127.0.0.1 You will notice that ssh will stay there waiting for sshd's reply, which won't come. The expected result would be for ssh to succeed. [Regression Potential] Since the affected code deals with executing a subprocess, reading its output through a pipe, and then relying on wait(2) to determine whether the subprocess exited correctly; and considering that this code is written in C without the help of features like RAII and with the use of goto statements, we are not able to disconsider the chances of making a mistake and forgetting to free a resource or to properly read/write from/to pipes, for example. This is, after all, the reason the bug happened in the first place. Having said that, openssh contains extensive tests and the code is well organized and relatively easy to follow. Upon close inspection, there doesn't seem to be an evident problem with the backported fixes. As usual when dealing with a somewhat older distribution, there is always the possibility of encountering problems because we will be recompiling openssh using the most recent versions of its build dependencies. [Original Description] Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1884635] Re: lxc 1:4.0.2-0ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1884635 Title: lxc 1:4.0.2-0ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2 Status in linux package in Ubuntu: In Progress Status in lxc package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/l/lxc/20200619_210334_814e1@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/l/lxc/20200619_213805_39c53@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/l/lxc/20200619_210431_b275f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/l/lxc/20200619_210417_54a16@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884635/+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 1885111] Re: 3 ports disabled
Thank you for taking the time to report this bug and help make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read 'How to report bugs effectively' http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => cups (Ubuntu) ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1885111 Title: 3 ports disabled Status in cups package in Ubuntu: Incomplete Bug description: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCW1AGG dmi.product.version: C6031Z7V dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jan 3 08:58:12 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1885111/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
OK then. Just needs sanity checking. Which mean I need to build a bionic machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
OK then. Just needs sanity checking. Which means I need to build a bionic machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1885111] [NEW] 3 ports disabled
Public bug reported: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1AGG:pvrC6031Z7V:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCW1AGG dmi.product.version: C6031Z7V dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Jan 3 08:58:12 2019 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.3 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1885111 Title: 3 ports disabled Status in xorg package in Ubuntu: New Bug description: The printer (which is now broken) we used seem to disable the ports. I don't know how to fix this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jun 25 09:53:44 2020 DistUpgraded: 2019-01-03 13:59:44,209 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a2a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation GT216M [GeForce GT 230M] [104d:905e] InstallationDate: Installed on 2016-12-22 (1281 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCCW1AGG ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=a904e50d-625f-4d72-929f-b72fcad907ef ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-03 (538 days ago) dmi.bios.date: 09/22/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0190Y5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A
[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
the test got retried and is green now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxau in Ubuntu. https://bugs.launchpad.net/bugs/1559650 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() Status in libxau package in Ubuntu: Fix Released Status in libxau source package in Bionic: Fix Committed Status in libxau source package in Eoan: Fix Released Status in libxau source package in Focal: Fix Released Bug description: [Impact] gnome-shell crashes a lot. Over 42000 times in bionic so far: https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7 [Test Case] None known yet. Just keeping an eye on the above link for regressions. [Regression Potential] Low. The same fix has been released to newer distros for the past 2 years already. [Other Info] ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Wed Mar 16 17:15:11 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2016-03-13 (6 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) ProcCmdline: gnome-shell --mode=gdm --wayland --display-server ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb $0x0,(%r12) PC (0x7f1ff33f46ab) ok source "$0x0" ok destination "(%r12)" (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at vsnprintf_chk.c:55 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand
Thank you for the verification Sergio! Could you please note down which package version has been used for verification and what kind of verification has been performed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1877454 Title: openssh-server hangs with AuthorizedKeysCommand Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: Fix Committed Bug description: [Impact] On a default Xenial install, when sshd is configured to obtain the list of allowed keys using AuthorizedKeysCommand (or the list of allowed certificate principals using AuthorizedPrincipalsCommand), and if the command pointed by Authorized{Keys,Principals}Command generates a lot of output, sshd will hang while reading this same output. In a nutshell, the problem happens when the subprocess generates enough data to fill the pipe's buffer; in this scenario, sshd will wait(2) on the subprocess, which will be blocked trying to write the rest of the output. [Test Case] In order to reproduce the bug, one can: $ lxc launch ubuntu-daily:xenial openssh-server-bug1877454 $ lxc shell openssh-server-bug1877454 # ssh-keygen (no need to choose a passphrase for the key, just hit ENTER on all prompts) # cat > authkeyscommand.sh << __EOF__ #!/bin/bash cat /root/.ssh/id_rsa.pub echo head -c 1M < /dev/urandom __EOF__ # chmod +x authkeyscommand.sh # cat >> /etc/ssh/sshd_config << __EOF__ AuthorizedKeysCommand /root/authkeyscommand.sh AuthorizedKeysCommandUser root __EOF__ # systemctl reload sshd.service # ssh root@127.0.0.1 You will notice that ssh will stay there waiting for sshd's reply, which won't come. The expected result would be for ssh to succeed. [Regression Potential] Since the affected code deals with executing a subprocess, reading its output through a pipe, and then relying on wait(2) to determine whether the subprocess exited correctly; and considering that this code is written in C without the help of features like RAII and with the use of goto statements, we are not able to disconsider the chances of making a mistake and forgetting to free a resource or to properly read/write from/to pipes, for example. This is, after all, the reason the bug happened in the first place. Having said that, openssh contains extensive tests and the code is well organized and relatively easy to follow. Upon close inspection, there doesn't seem to be an evident problem with the backported fixes. As usual when dealing with a somewhat older distribution, there is always the possibility of encountering problems because we will be recompiling openssh using the most recent versions of its build dependencies. [Original Description] Please consider applying this change to openssh-server distributed in Xenial (16.04). Without it, sshd can sporadically hang when making use of the `AuthorizedKeysCommand` option. https://github.com/openssh/openssh- portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Yea... I've turn it on and off using monitor switch button many times without luck... but in my case I had to PULL OUT THE POWER PLUG. I know how it sounds and how weird it is but just after that it was fixed and it didn't work before. I really don't know why, but it helped me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Hi, I tried power on and off the monitor multiple times, but nothing helped, still blank screen. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+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 1885013] Re: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-4.18.0-17-generic Fatal: open /initrd.img: No such file or directory run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1 ** Package changed: initramfs-tools (Ubuntu) => lilo (Ubuntu) -- 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/1885013 Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in lilo package in Ubuntu: New Bug description: Problem occurred during a (longer) system update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.9 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Wed Jun 24 21:21:05 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-07-08 (1813 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.9 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lilo/+bug/1885013/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
** Merge proposal linked: https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382345 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: In Progress Status in rsyslog source package in Disco: In Progress Status in rsyslog source package in Eoan: In Progress Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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