[Touch-packages] [Bug 1889343] [NEW] package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: sudo apt autoremove will not remove anything from /boot and says error. Cannot update because /boot is full. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: evan 1729 F pulseaudio /dev/snd/controlC0: evan 1729 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 28 21:33:38 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a843350f-5ce1-47bc-9cc4-b6a805932a8b InstallationDate: Installed on 2016-10-23 (1374 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20266 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-07 (82 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.sku: LENOVO_MT_20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1889343 Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: sudo apt autoremove will not remove anything from /boot and says error. Cannot update because /boot is full. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: evan 1729 F pulseaudio /dev/snd/controlC0: evan 1729 F pulseaudio CasperMD5CheckResult: skip Date: Tue Jul 28 21:33:38 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a843350f-5ce1-47bc-9cc4-b6a805932a8b InstallationDate: Installed on 2016-10-23 (1374 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20266 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.2 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-07 (82 days ago) dmi.bios.date: 03/25/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN35WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
Manually download pulseaduio 1:11.1-1ubuntu7.10 and kernel 4.15.0-1093-oem into oem bionic image tested on the target that previously can reproduce this issue. In first boot, plug-in headset, and pop-up windows is properly display. After select headset, the output is correctly selected, and use the test in gnome-control-center it can properly output left/right audio. So I verified passed. ** Changed in: oem-priority Status: Confirmed => Fix Committed -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1889289] Re: All system graphic glitch when play video
This sounds like it might be bug 1767312. Please try the workarounds listed in that bug. ** Tags added: radeon ** Summary changed: - All system graphic glitch when play video + [radeon] All system graphic glitch when play video ** 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/1889289 Title: [radeon] All system graphic glitch when play video Status in Ubuntu: Incomplete Bug description: Some time (not every time) when i play video all system graphic start glitching and showing some color but i can move mouse and click and other functionalities work but i can see thing correctly . i tested different player but didn't work . I didn't had any problem with windows about this . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:34:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobility Radeon HD 4650 [dv6-1190en] [103c:3628] InstallationDate: Installed on 2020-06-29 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad64f332-52bc-4836-8c11-052fd1c85fad ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.44 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.50 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.44:bd04/06/2011:svnHewlett-Packard:pn:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.50:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1889289/+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 1889217] Re: Make digital mic on the AMD renoir machines work under gnome desktop
** Tags added: renoir ** Tags added: focal groovy -- 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/1889217 Title: Make digital mic on the AMD renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1889217/+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 1873961] Autopkgtest regression report (iproute2/4.15.0-2ubuntu1.2)
All autopkgtests for the newly accepted iproute2 (4.15.0-2ubuntu1.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: libreswan/unknown (armhf) ubuntu-fan/0.12.10 (amd64) systemd/237-3ubuntu10.41 (amd64, ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#iproute2 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /*
[Touch-packages] [Bug 1889252] Re: app blinking
Can you provide a video of the problem? Or at least a more detailed description of the problem you see? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1889252 Title: app blinking Status in gnome-shell package in Ubuntu: Incomplete Bug description: automatically blinking when opening app and sometimes the app does not open ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 19:27:10 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889252/+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 1889278] Re: Xorg crash when using my machine; it goes back to the Login Menu
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/1889278 Title: Xorg crash when using my machine; it goes back to the Login Menu Status in Ubuntu: Incomplete Bug description: This usually happens when a memory intensive process happens on my machine, or right after boot. The screen freezes, then sometimes turns black, and then boots me to the login screen if I am lucky again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 11:55:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (21 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 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 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-42-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1889278/+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 1889189] Re: "Authentication Required" window after waking up
*** This bug is a duplicate of bug 1824874 *** https://bugs.launchpad.net/bugs/1824874 ** This bug has been marked a duplicate of bug 1824874 undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed] -- 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/1889189 Title: "Authentication Required" window after waking up Status in xorg package in Ubuntu: Invalid Bug description: Hi. Sometimes (not always) when the computer wakes up after sleep, on the desktop the "Authentication Required" window is shown at an unusuall position, i.e. (top, left) coordinates = (0, 0). (see the attached screenshot) The worst part is that I enter my password and nothing happens and the buttons do not respond. Then I restart the computer to get rid of it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 14:48:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1889189/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
Looks like this is really a PA's defect. you could test this workaround temporarily: edit /etc/pulse/default.pa do some change like this: load-module module-switch-on-connect blacklist="" I will find a physical machine to debug this issue, and try to find a real solution. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) 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: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #956 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/956 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/956 Importance: Unknown Status: Unknown -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" 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" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id :
[Touch-packages] [Bug 1880258] Re: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise
> the vast, VAST majority of the time you see this message it is actually not a NXDOMAIN error. I don't have any extensive data as you seem to have but _for me at home_ (= office now!) and without zero captive portal involved, adding this trailing dot reduces the NXDOMAIN frequency from one message every 5 minutes to a few messages _per day_ (NM's default interval is 300 seconds) The "journalctl --boot -p notice" total also becomes about twice smaller. I filed this bug for a reason. > the NXDOMAIN returned by the upstream nameserver is the *correct* response - > that hostname connectivity-check.ubuntu.com.your_domain really, actually > doesn't exist. Yes of course, hence this one character fix which IMHO also removes one large "distraction" from the main, captive portal issue! > if you see this NXDOMAIN "error" [outside a captive portal] it is almost > always just a normal lookup of a domain that doesn't exist, ... which is for sure very rare on my (admittedly headless) system. Not sure why querying inexistent domains would be frequent on others' systems? > and the error message is simply wrong It says "mitigating _potential_..." so it's not strictly speaking wrong. Agreed it can be misleading but summarizing this fairly complex issue in just one line is quite a challenge. > This is due to a Ubuntu-only patch to systemd Care to share the "best" link(s) about this? I mean links to best bugs and/or relevant source code. An internet search returns too many hits! BTW a good and authoritative bug number in the error message would probably not hurt either, see why above. > network-manager could work around this problematic Ubuntu-only systemd patch, With an Ubuntu-only network-manager patch maybe? Sorry couldn't resist :-) -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Focal: 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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
alright, here's the pa debug log where I did a fresh boot, set audio from s/pdif to the hdmi audio output, then put the machine to sleep and woke it, and then set the audio to the other hdmi output device after the system switched them around. ** Attachment added: "pa.log.xz" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+attachment/5396787/+files/pa.log.xz -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) 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: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices
I tried many combinations of snd-hda-intel models and hdajackretask settings. The following fixed the problem in my Dell Latitude 7389 with Mint 19.3 and kernel 5.4.0. Now, when I plug my headset, I have two working mics (internal and headset) and the output changes to headphone. - /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=dell-headset-multi - hdajackretask (Advanced override) Pin ID: 0x19 Connectivity: Jack Device: Microphone Jack detection: Not Present Channel group: 3 Channel (in group): Channel 24 & 25 Pin ID: 0x1a Connectivity: Not connected Pin ID: 0x21 Connectivity: Jack Device: Headphone Jack detection: Present Channel group: 3 Channel (in group): Channel 30 & 31 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1728093 Title: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289 Ultrabook that has a single 3.5mm jack for both input and output. This installation is in a dual-boot situation with Windows 10. This device has UEFI secure boot enabled. The combo jack works perfectly in Windows 10, however, when I plug in a headset or headphone of any kind, it does not register that anything has been plugged in. The laptop is connected to a Dell dock via USB-C, so there is also USB Audio (Output only) available on the dock, but that also does not work. It worked for one session yesterday on my dock at work, however it does not work at my dock that I have at home. The internal speakers and the microphone built into the lid work fine. The Combo jack also does not work disconnected from the dock. I have installed gnome and gnome-shell, but it does not work in either gnome or unity (I continue to use lightdm so that I can switch back and forth). Neither Unity nor Gnome bring up any kind of "What Did You Plug In" dialog. alsamixer does not have a headphone option as expected pavucontrol does not allow me to select "Headphones" under the Built- in Audio Analog Stereo Port I have attempted to tweak settings in hdajackretask to no success I have attempted to add: options snd_hda_intel model=dell-headset-multi(dell-headset-dock, generic, auto, headset-mic, etc) to no success I have also tried updating my kernel to 4.13.10, to no success. I also tried 17.10 to no success. Outputs: -- uname -sr Linux 4.10.0-37-generic -- aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/car*/co* | grep Codec Codec: Realtek ALC3253 Codec: Intel Kabylake HDMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1728093/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
That is weird, could you please upload the pa.log which contains the log of switching to hdmi audio and suspend/resume. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) 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: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Apparenlty the systemd package in the upload queue will be reviewed. For my test packages, @ddstreet told me that a pure no-change rebuild of systemd would FTBFS on arm64 due to bug #1886197. So I added that patch to this systemd "almost no-change rebuild" patch. ** Patch removed: "lp1889297_bionic_systemd.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1889297/+attachment/5396664/+files/lp1889297_bionic_systemd.debdiff ** Patch added: "lp1889297_bionic_systemd-with-arm64-ftbfs.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1889297/+attachment/5396754/+files/lp1889297_bionic_systemd-with-arm64-ftbfs.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic:
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
With the test packages for kmod and systemd in this PPA [1] I can confirm that udev-udeb now Depends: on libkmod2-udeb. >From the build log: Package: udev-udeb ... Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb Just uploaded kmod to Bionic. [1] https://launchpad.net/~mfo/+archive/ubuntu/lp1889297/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included)
[Touch-packages] [Bug 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus
10100727: The recent upgrade of librsvg2-2:i386 and librsvg2-common:i386 (from 2.40.20-2 to (2.40.20-2ubuntu0.1) "broke" the display of card styles Anglo and Gnomeangelo, in the aisleriot "Klondike" solitaire game. By "broke", I mean that the card faces displayed only in part -- elements were missing. Reverting to the previous version solved the issue. ** Attachment added: "Klondike-librsvg.png" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1644995/+attachment/5396751/+files/Klondike-librsvg.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1644995 Title: specific SVG file breaks Ubuntu 16.04 desktop + nautilus Status in librsvg: Expired Status in librsvg package in Ubuntu: Triaged Bug description: Saving following file on Desktop (Ubuntu 16.04.1) results in: 1. Wallpaper and all icons on the desktop disappear 2. Nautilus starts for ~1sec then breaks with "Floating point exception" I suspect it's related to librsvg. In syslog I have many records similar to this one: kernel: [ 20.076864] traps: nautilus[2270] trap divide error ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in librsvg-2.so.2.40.13[7f63fbdc9000+35000] Here is the file (I can't even attach it here with Firefox, because it makes it crash): http://www.w3.org/2000/svg; xmlns:xlink="http://www.w3.org/1999/xlink; xmlns:ev="http://www.w3.org/2001/xml-events;> https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA; result="pattern" width="4" height="4"/> To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1644995/+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 1659719] Autopkgtest regression report (pam/1.1.8-3.6ubuntu2.18.04.2)
All autopkgtests for the newly accepted pam (1.1.8-3.6ubuntu2.18.04.2) for bionic have finished running. The following regressions have been reported in tests triggered by the package: dovecot/1:2.2.33.2-1ubuntu4.5 (armhf) systemd/237-3ubuntu10.41 (ppc64el) openssh/1:7.6p1-4ubuntu0.3 (arm64, amd64, i386, armhf, s390x, ppc64el) vsftpd/3.0.3-9build1 (arm64) lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#pam [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: New Status in pam source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: New Status in pam source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: New Status in pam source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1888598] Re: pulseaudio has is buggy with hdmi audio and sleep/wake
alright, I see on boot, it changing the configured default when I switch to HDMI audio from p/sdif: 4203:I: [pulseaudio] core.c: configured_default_sink: alsa_output.pci- _01_00.1.hdmi-surround-extra1 -> alsa_output.pci-_01_00.1.hdmi- surround and after suspend/resume, there are no new messages about the configured default. is it's not changing my configured default, but it is still messing up the audio devices after sleep. -- 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/1888598 Title: pulseaudio has is buggy with hdmi audio and sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) 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: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 673119] Re: dash "set -e" breaks "trap action INT"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dash (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/673119
Title:
dash "set -e" breaks "trap action INT"
Status in dash package in Ubuntu:
Confirmed
Bug description:
Binary package hint: dash
With set -e, dash executes only the first command of an INT (Ctrl-C)
trap handler:
#!/bin/sh
set -e
trap 'sorry' INT
trap 'echo EXIT' EXIT
zero() {
return 0;
}
sorry() {
#zero
echo "Ignored 1"; echo "Ignored 2"
sleep 1
echo Back
}
for i in 3 2 1; do
echo "$i"
sleep 1 # || true
done
echo OUT
Actual result:
$ ./x # Press ^C right away
3
^CIgnored 1
EXIT
Expected result:
3
^CIgnored 1
Ignored 2
Back
2
1
OUT
EXIT
By un-commenting the call to function zero, or the "|| true" in the
main loop, the problem disapears.
Bash also exits prematurely, but at least it runs the "trap INT"
handler code to completion.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: dash 0.5.5.1-3ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Nov 9 19:12:41 2010
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/673119/+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 1888685] Re: rsync fails after installing level 3.2.1
Couldn't figure out how to make your example run on my 20.10 (or even 20.04) server systems. Using your example took apart my server/client and made a simple case (using the /mnt/synctest directories) which runs when the server is either 20.04 or 20.10. Will start looking at what to add to make it break. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
** Changed in: kmod (Ubuntu Bionic) Milestone: None => ubuntu-18.04.5 ** Changed in: systemd (Ubuntu Bionic) Milestone: None => ubuntu-18.04.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs by default (without
[Touch-packages] [Bug 1884265] Re: [fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl library.
Hello Dariusz, or anyone else affected,
Accepted ntp into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-
5ubuntu7.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: openssl (Ubuntu)
Status: In Progress => Fix Released
** Changed in: ntp (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1884265
Title:
[fips] ntpq segfaults when attempting to use MD5 from FIPS-openssl
library.
Status in ntp package in Ubuntu:
New
Status in openssl package in Ubuntu:
Fix Released
Status in ntp source package in Bionic:
Fix Committed
Status in openssl source package in Bionic:
In Progress
Bug description:
[Impact]
In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
segfault.
ntpq uses crypto hashes to authenticate its requests. By default it
uses md5. However, when compiled with openssl it creates a lists of
acceptable hashes from openssl that can be used.
This issue is only applicable in bionic and when using fips-openssl.
[Test Steps]
Test case:
sudo apt install ntp
ntpq -p
Segmentation fault (core dumped)
What happens there is ntpq wants to iterate all available digests
(list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
task.
EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
For FIPS mode it adds:
EVP_add_digest(EVP_md5());
What happens later in ntpq is (list_md_fn function inside ntpq.c):
ctx = EVP_MD_CTX_new();
EVP_DigestInit(ctx, EVP_get_digestbyname(name));
EVP_DigestFinal(ctx, digest, _len);
First digest it gets is MD5, but while running EVP_DigestInit for it, it gets
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
#ifdef OPENSSL_FIPS
if (FIPS_mode()) {
if (!(type->flags & EVP_MD_FLAG_FIPS)
&& !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
return 0;
}
}
#endif
Due to type->flags for MD5 being 0 there's an error set
(EVP_R_DISABLED_FOR_FIPS).
After getting back to ntpq.c:
ctx->engine and ctx->digest are not set (due to the mentioned error), hence
inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
causes a segfault (ctx->digest is NULL).
So either MD5 shouldn't be added in FIPS mode or it should have the
EVP_MD_FLAG_FIPS to be properly initialized.
[Regression Potential]
I don't think this should regress ntpq + openssl from the Ubuntu
archive.
Current archive ntpq + openssl behaviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq doesn't check return from EVP_Digest(Init|Final) and assumes all is well
and sticks all digests into its list regardless if it is working or not.
i.e.
ntpq> help keytype
function: set key type to use for authenticated requests, one of:
MD4, MD5, RIPEMD160, SHA1, SHAKE128
If somehow openssl library is corrupted and sends back erroneous
results, its possible the authentication will just not ever work.
Newly fixed archive ntpq + oenssl beahviour:
openssl includes all message digests and hands ntpq a sorted digest-list.
ntpq checks each one and includes each working digest. With a non-corrupted
openssl, everything works fine and ntpq includes each into its list. Ends up
with a list identical to the one above.
If somehow opensll library is corrupted and sends back erroneous
results, ntpq will hopefully catch it by checking return code and
include only those algos that appear to be working. Its
[Touch-packages] [Bug 1889301] [NEW] package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1
Public bug reported: I don't know, it just came up at the initialization proccess. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: ubuntu-minimal:amd64: Remove sudo:amd64: Remove surfshark-vpn:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 27 03:06:04 2020 ErrorMessage: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-24 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1889301 Title: package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1 Status in sudo package in Ubuntu: New Bug description: I don't know, it just came up at the initialization proccess. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: sudo 1.8.31-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 AptOrdering: ubuntu-minimal:amd64: Remove sudo:amd64: Remove surfshark-vpn:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 27 03:06:04 2020 ErrorMessage: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1 InstallationDate: Installed on 2020-05-24 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: sudo Title: package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1889301/+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 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Status in systemd source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Very nice catch @mfo, I'm sorry to have introduced this issue and I'm glad you found it. Thanks for sharing. I'm +1 on both uploads to fix the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs by default (without --add-udeb): From dh_makeshlibs(1): Since debhelper 12.3, dh_makeshlibs will by default
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Currently building the packages on PPA to verify all three parts (kmod, systemd, d-i) work correctly with the changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs by default (without --add-udeb): From dh_makeshlibs(1): Since debhelper 12.3, dh_makeshlibs will by default add an additional udeb line for
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
** Patch added: "lp1889297_bionic_kmod.debdiff" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1889297/+attachment/5396663/+files/lp1889297_bionic_kmod.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs by default (without --add-udeb): From dh_makeshlibs(1): Since debhelper 12.3, dh_makeshlibs
[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
There's a systemd upload for Bionic with this version number already. I guess that is a larger change that may be intended for post-release, while this change is needed for release, so d-i builds w/ new kernels. So, keeping the same number for now, in case this needs to trump that. ** Patch added: "lp1889297_bionic_systemd.debdiff" https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1889297/+attachment/5396664/+files/lp1889297_bionic_systemd.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1889297 Title: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb Status in kmod package in Ubuntu: Invalid Status in kmod source package in Bionic: In Progress Bug description: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT
[Touch-packages] [Bug 1889297] [NEW] Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb
Public bug reported: [Impact] * debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb. * This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. * See the '[Details]' section for the details. :) [Fix] * That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic. Just revert it. * There is no need to "fix" this in Eoan and later (debhelper >= 12.3) * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.) [Test Case] * Try to build debian-installer on Bionic; it FTBFS: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. * Check if libkmod2's shlibs file contains an udeb line: $ dpkg-deb --control libkmod2__.deb dir $ cat dir/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb # this is good. [Regression Potential] * The fix only changes the libkmod2's shlibs file to include an udeb line (so udebs that depend on that library package should depend on the -udeb package.) Thus the regression potential is limited to the installer, and the udeb packages which depend on libkmod2 (udev-udeb only, probably.) Regressions could be seen as failures to load libkmod2.so and/or not finding its dynamic symbols. * There is a no-change rebuild of systemd involved/required, so some dependency updates may potentially impact systemd. [Details] debian-installer currently FTBFS on Bionic because udev-udeb depends on libkmod2 not on libkmod2-udeb: The following packages have unmet dependencies: udev-udeb : Depends: libkmod2 but it is not installable E: Unable to correct problems, you have held broken packages. This regression has been introduced in kmod 24-1ubuntu3.3, and it propagated into udev-udeb in systemd 237-3ubuntu10.40. kmod (24-1ubuntu3.3) bionic; urgency=medium <...> * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not actually contain a library. (Closes: #939779) <...> From dh_makeshlibs(1): --add-udeb=udeb Create an additional line for udebs in the shlibs file and use udeb as the package name for udebs to depend on instead of the regular library package. Before: $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb libkmod2-u32-control $ cat libkmod2-u32-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends: Depends: ..., libkmod2-udeb, ... After: $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb libkmod2-u33-control $ cat libkmod2-u33-control/shlibs libkmod 2 libkmod2 $ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends: Depends: ..., libkmod2, ... That kmod change fixes a FTBFS with newer debhelper on Eoan and later, but it is not required with older debhelper on Bionic: Eoan: $ dpkg -s debhelper | grep Version: Version: 12.6.1ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared libraries but --add-udeb=libkmod2-udeb was passed!? make: *** [debian/rules:120: .stamp-binary] Error 255 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Bionic: $ dpkg -s debhelper | grep Version: Version: 11.1.6ubuntu2 $ dpkg-buildpackpage <...> dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4 dh_shlibdeps -- --warnings=7 <...> dpkg-buildpackage: info: binary and diff upload (original source NOT included) There is no need to "fix" this in Eoan and later, as debhelper >= 12.3 has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb line is added to shlibs by default (without --add-udeb): From dh_makeshlibs(1): Since debhelper 12.3, dh_makeshlibs will by default add an additional udeb line for udebs in the shlibs file, when the udeb has the same name as the deb followed by a "-udeb" suffix <...> Please use the --add-udeb and --no-add-udeb options below when this auto-detection is insufficient. $ dpkg-deb --control libkmod2_26-1ubuntu1.1_amd64.deb libkmod2-eoan-control $ cat libkmod2-eoan-control/shlibs libkmod 2 libkmod2 udeb: libkmod 2 libkmod2-udeb $ dpkg-deb --control libkmod2_27-1ubuntu2_amd64.deb libkmod2-focal-control $ cat libkmod2-focal-control/shlibs libkmod 2 libkmod2 (>= 27) udeb:
[Touch-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: ubuntu-power-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+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 1666203] Re: pam_tty_audit failed in pam_open_session
@David have you tested the version of the package in -proposed and does it work for you? If so could you please provide testing details so that we can release the package. -- 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Fix Released Status in pam source package in Xenial: Fix Committed Status in pam source package in Bionic: Fix Released Status in pam source package in Cosmic: Fix Released Status in pam package in Debian: Fix Released Bug description: [Impact] * Kernel keystroke auditing via pam_tty_audit.so not working * When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. [Test Case] 1) Open a shell & escalate to root 2) Update /etc/pam.d/common-session & /etc/pam.d/common-session-noninteractive and add the following line directly after the line: "session required pam_unix.so": "session required pam_tty_audit.so enable=*" 3) Start a second new shell session on the box and type a variety of commands 4) Exit the second shell session to flush the buffer? 5) In the root shell run "aureport -tty -i". The output should show the commands run in the other shell. [Regression Potential] * Low, we are simply including the missing header file and copy the old status as initialization of new. The fix is already found/part of Debian and Disco. [Pending SRU] All regressions found in Bionic and Cosmic looks like long standing ADT failure. Nothing has been introduce by this particular SRU. [Other Info] # Upstream fix: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee # git describe --contains c5f829931a22c65feffee16570efdae036524bee Linux-PAM-1_2_0~75 # rmadision pam => pam | 1.1.8-1ubuntu2.2 | trusty-updates | source => pam | 1.1.8-3.2ubuntu2 | xenial | source => pam | 1.1.8-3.2ubuntu2.1 | xenial-updates | source => pam | 1.1.8-3.6ubuntu2 | bionic | source => pam | 1.1.8-3.6ubuntu2 | cosmic | source pam | 1.3.1-5ubuntu1 | disco| source [Original Description] Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62):
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
Hello Leo, or anyone else affected, Accepted pam into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pam/1.1.8-3.6ubuntu2.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pam (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- 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/1659719 Title: ssh can't call a binary from a snap without the full path Status in Snappy: Fix Committed Status in livecd-rootfs package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Confirmed Status in pam package in Ubuntu: Fix Released Status in livecd-rootfs source package in Xenial: New Status in openssh source package in Xenial: New Status in pam source package in Xenial: New Status in livecd-rootfs source package in Bionic: New Status in openssh source package in Bionic: New Status in pam source package in Bionic: Fix Committed Status in livecd-rootfs source package in Focal: New Status in openssh source package in Focal: New Status in pam source package in Focal: Fix Committed Status in livecd-rootfs source package in Groovy: Fix Released Status in openssh source package in Groovy: Confirmed Status in pam source package in Groovy: Fix Released Status in openssh package in Debian: New Bug description: [impact] ssh can't call a binary from a snap, it will only work using the full path. [test case] Create a container. Install the go snap (and make sure golang-go is not installed). Run "ssh go version" and check the binary is found. [regression potential] It's a pam change an they are always a bit scary but the code follows the existing pattern for updating PATH in /etc/environment and has been tested in groovy. [original description] Let's say I have the hello snap installed in 192.168.122.24. Then: elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello elopio@192.168.122.24's password: bash: hello: command not found elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello elopio@192.168.122.24's password: Hello, world! To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659719/+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 1577599] Re: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out)
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1577599 Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted / Audio Notification unstable (Popping in/out) Status in alsa-driver package in Ubuntu: Confirmed Bug description: For a better explanation, here is a video I've made. https://youtu.be/8q092XpLT-Y For further diagnostics, here is a ubuntu forum post I've made. http://ubuntuforums.org/showthread.php?t=2322708 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: deviantxs 1672 F...m pulseaudio /dev/snd/controlC2: deviantxs 1672 F pulseaudio /dev/snd/controlC0: deviantxs 1672 F pulseaudio /dev/snd/controlC1: deviantxs 1672 F pulseaudio CurrentDesktop: Unity Date: Mon May 2 16:35:54 2016 InstallationDate: Installed on 2016-04-30 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [CM1855, Realtek ALC892, Green Line Out, Rear] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM1855 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd08/20/2013:svnASUSTeKCOMPUTERINC.:pnCM1855:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnCM1855:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: CM1855 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1577599/+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 1873961] Re: tc filter show tcp_flags wrong mask value
Hello bugproxy, or anyone else affected, Accepted iproute2 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iproute2/4.15.0-2ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: iproute2 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: In Progress Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Fix Committed Bug description: [SRU Justification] Impact: The tc command does not show the correct values for tcp_flags (and ip_tos) on filter rules. This might break other scripts parsing that output but at least confuses users. Fix: Backport of "tc: fix bugs for tcp_flags and ip_attr hex output" from upstream iproute2. Testcase: tc qdisc add dev lo ingress tc filter add dev lo parent : prio 3 proto ip flower ip_tos 0x8/32 tc filter add dev lo parent : prio 5 proto ip flower ip_proto tcp \ tcp_flags 0x909/f00 tc filter show dev lo parent : filter protocol ip pref 3 flower chain 0 filter protocol ip pref 3 flower chain 0 handle 0x1 eth_type ipv4 ip_tos a9606c10 <-- bad, should be 0x8/32 not_in_hw filter protocol ip pref 5 flower chain 0 filter protocol ip pref 5 flower chain 0 handle 0x1 eth_type ipv4 ip_proto tcp tcp_flags 909909 <-- bad, should be 0x909/f00 not_in_hw Note that the ip_tos value in the -j[son] output is correct, while the tcp_flags value is is incorrect in both cases. Risk of Regression: Low: Usually scripts would use the json output and that has at least the ip output correct. And the values shown in the bad case seem to be little useful. So it seems unlikely anybody relied on them. But cannot completely be ruled out. === Original description === ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line
[Touch-packages] [Bug 1889117] Re: switch to wget results in no motd-news in clouds
This bug was fixed in the package base-files - 11ubuntu10 --- base-files (11ubuntu10) groovy; urgency=medium * motd/50-motd-news: use the actual wget version variable in the user-agent string * motd/50-motd-news: handle wget's behavior with a 404 document (LP: #1889117) -- Andreas Hasenack Mon, 27 Jul 2020 16:44:07 -0300 ** Changed in: base-files (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1889117 Title: switch to wget results in no motd-news in clouds Status in base-files package in Ubuntu: Fix Released Bug description: cloud-specific motd news relies on the user-agent string cloud_id / being included in the user-agent. The server, when receiving this string, will try to return the cloud-specific index file, which is `index.txt.`. If that file doesn't exist, then the 404 error document is returned, which happens to be set to the default `index.txt` normal motd-news file. curl happily returns that without flagging this as an error situation (a 404: it needs an extra command-line argument for that). wget, however, fails without printing the error document: $ wget -U cloud_id/aws https://motd.ubuntu.com -O- --2020-07-27 15:45:47-- https://motd.ubuntu.com/ Resolving motd.ubuntu.com (motd.ubuntu.com)... 54.171.230.55, 34.249.145.219, 2a05:d018:91c:3200:c887:2f22:290f:a7c, ... Connecting to motd.ubuntu.com (motd.ubuntu.com)|54.171.230.55|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2020-07-27 15:45:48 ERROR 404: Not Found. Not only that, it will also fail in its exit status: $ echo $? 8 Whereas curl didn't: $ curl -A cloud_id/aws https://motd.ubuntu.com * "If you've been waiting for the perfect Kubernetes dev solution for macOS, the wait is over. Learn how to install Microk8s on macOS." https://www.techrepublic.com/article/how-to-install-microk8s-on-macos/ $ echo $? 0 $ We need to pass --content-on-error, ignore the error status 8 (or all?) and make it quiet (-q): $ wget -U cloud_id/aws https://motd.ubuntu.com -O- --content-on-error -q ; echo $? * "If you've been waiting for the perfect Kubernetes dev solution for macOS, the wait is over. Learn how to install Microk8s on macOS." https://www.techrepublic.com/article/how-to-install-microk8s-on-macos/ 8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1889117/+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 1889289] [NEW] All system graphic glitch when play video
Public bug reported: Some time (not every time) when i play video all system graphic start glitching and showing some color but i can move mouse and click and other functionalities work but i can see thing correctly . i tested different player but didn't work . I didn't had any problem with windows about this . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:34:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobility Radeon HD 4650 [dv6-1190en] [103c:3628] InstallationDate: Installed on 2020-06-29 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad64f332-52bc-4836-8c11-052fd1c85fad ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.44 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.50 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.44:bd04/06/2011:svnHewlett-Packard:pn:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.50:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1889289 Title: All system graphic glitch when play video Status in xorg package in Ubuntu: New Bug description: Some time (not every time) when i play video all system graphic start glitching and showing some color but i can move mouse and click and other functionalities work but i can see thing correctly . i tested different player but didn't work . I didn't had any problem with windows about this . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 21:34:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobility Radeon HD 4650 [dv6-1190en] [103c:3628] InstallationDate: Installed on 2020-06-29 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad64f332-52bc-4836-8c11-052fd1c85fad ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.44 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3628 dmi.board.vendor: Hewlett-Packard dmi.board.version: 18.50 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.44:bd04/06/2011:svnHewlett-Packard:pn:pvrRev1:rvnHewlett-Packard:rn3628:rvr18.50:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Ok. Thanks for the help and guidance. Hugs. -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" 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" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 jackpoll_ms :
[Touch-packages] [Bug 1889252] Re: app blinking
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1889252 Title: app blinking Status in xorg package in Ubuntu: New Bug description: automatically blinking when opening app and sometimes the app does not open ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 19:27:10 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1889252/+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 1889252] [NEW] app blinking
You have been subscribed to a public bug: automatically blinking when opening app and sometimes the app does not open ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 19:27:10 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- app blinking https://bugs.launchpad.net/bugs/1889252 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1889278] Re: Xorg crash when using my machine; it goes back to the Login Menu
Simply using the machine and running gcc while using Visual Studio code is enough to cause the issue. -- 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/1889278 Title: Xorg crash when using my machine; it goes back to the Login Menu Status in xorg package in Ubuntu: New Bug description: This usually happens when a memory intensive process happens on my machine, or right after boot. The screen freezes, then sometimes turns black, and then boots me to the login screen if I am lucky again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 11:55:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (21 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 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 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-42-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1889278/+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 1889278] [NEW] Xorg crash when using my machine; it goes back to the Login Menu
Public bug reported: This usually happens when a memory intensive process happens on my machine, or right after boot. The screen freezes, then sometimes turns black, and then boots me to the login screen if I am lucky again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 11:55:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (21 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 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 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-42-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash 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/1889278 Title: Xorg crash when using my machine; it goes back to the Login Menu Status in xorg package in Ubuntu: New Bug description: This usually happens when a memory intensive process happens on my machine, or right after boot. The screen freezes, then sometimes turns black, and then boots me to the login screen if I am lucky again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 11:55:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (21 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 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 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-42-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement
** Tags removed: rls-ff-incoming -- 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/1886854 Title: Race in load-module snap policy check in classic confinement Status in pulseaudio package in Ubuntu: New Bug description: SUMMARY = When running a snap in classic confinement, that needs access to PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed and sometimes fail with "Access denied". After running "pacmd unload-module module-snap-policy" and unloading the snap policy module, these work reliably. I have verified this in a fresh install of Ubuntu 20.04 in a VM. STEPS TO REPRODUCE = a) Either build a snap with classic confinement that sends these commands on the pulseaudio native protocol socket. (This is how I found the bug) b) Or, what I did here to easier reproduce, abuse the sandbox of a random classic snap: Download the attached bug.tgz with a minimal reproducer. It contains the source code for a program that sends load and unload commands to pulse. Unfortunately `pacmd` has a pid-file check that fails inside the sandbox and doesn't work. The reproducer does essentially the same as "pacmd load/unload-module" though. (a pre-compiled x64 binary is also included in case you don't have a go compiler and dare to run an untrusted binary in a VM) Unpack the tgz, build it, if necessary with "go mod download && go build" Grab a random classic mode snap to use its sandbox as a test bed: $ sudo snap install atom --classic atom 1.48.0 from Snapcrafters installed Open a shell in its sandbox: snap run --shell atom Navigate to the compiled binary and execute it a few times: user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:10 PulseAudio connection created successfully 2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:11 PulseAudio connection created successfully Loaded Module sucessfully at index: 40 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully Loaded Module sucessfully at index: 41 user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:12 PulseAudio connection created successfully 2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:14 PulseAudio connection created successfully 2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 2020/07/08 18:46:15 PulseAudio connection created successfully 2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio error: commandLoadModule -> Access denied Succeeds and fails apparently at random. Now from a non-sandboxed shell, run pacmd unload-module module-snap-policy to unload the snap-policy module from pulseaudio, now run ./bug a few more times. It now succeeds reliably, every time. Side note, with the real program on my actual machine, the race seems to behave slightly differently. It seems not to work the first time an application is started, but closing it and reopening it seems to make it work pretty reliably afterwards. Restarting "snapd", causes the following run the snap to fail again. EXPECTED BEHAVIOUR == The pulseaudio snap policy module should correctly determine and enforce it's policy. ACTUAL BEHAVIOUR The pulseaudio snap policy module seemingly at random denies access when the snap has the permissions to do an operation. ADDITIONAL INFORMATION == $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ 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://ch.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://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to:
[Touch-packages] [Bug 1889206] Re: Regression in USN-4436-1
** Attachment added: "eog displaying issue rendering anglo cardset" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889206/+attachment/5396555/+files/anglo-issue.png ** Bug watch added: gitlab.gnome.org/GNOME/librsvg/-/issues #612 https://gitlab.gnome.org/GNOME/librsvg/-/issues/612 ** Also affects: librsvg via https://gitlab.gnome.org/GNOME/librsvg/-/issues/612 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg: Unknown Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Xenial: Confirmed Status in librsvg source package in Bionic: Confirmed Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1889206/+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 1889206] Re: Regression in USN-4436-1
Can also be tested by running "eog /usr/share/aisleriot/cards/anglo.svgz". See attached screenshot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg: Unknown Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Xenial: Confirmed Status in librsvg source package in Bionic: Confirmed Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1889206/+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 1889217] [NEW] Make digital mic on the AMD renoir machines work under gnome desktop
Public bug reported: This is for tracking purpose. ** Affects: alsa-lib (Ubuntu) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu) Importance: High Status: New ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Affects: alsa-lib (Ubuntu Focal) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu Focal) Importance: High Status: New ** Affects: pulseaudio (Ubuntu Focal) Importance: High Status: New ** Affects: alsa-lib (Ubuntu Groovy) Importance: High Status: New ** Affects: alsa-ucm-conf (Ubuntu Groovy) Importance: High Status: New ** Affects: pulseaudio (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-lib (Ubuntu) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Also affects: alsa-lib (Ubuntu Groovy) Importance: High Status: New ** Also affects: pulseaudio (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: High Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - Make digital mic on the AMD renoir machines work under gnome environment + Make digital mic on the AMD renoir machines work under gnome desktop ** Changed in: alsa-lib (Ubuntu Focal) Importance: Undecided => High ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => High -- 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/1889217 Title: Make digital mic on the AMD renoir machines work under gnome desktop Status in alsa-lib package in Ubuntu: New Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-lib source package in Groovy: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1889217/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 It probably is a kernel driver or firmware's regression, could you run the 19.10's kernel + 19.10's firmware under 20.04 to test? -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1889206] Re: Regression in USN-4436-1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: librsvg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Xenial: Confirmed Status in librsvg source package in Bionic: Confirmed Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889206/+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 1889166] Re: mir: build failure on s390x
I'm not closing this bug, because overriding the build flag is not a fix... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+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 1889166] Re: mir: build failure on s390x
Yep, I created a minimal test case on my laptop, and couldn't figure out why there was this warning in first place. At the end, I ended up in something like this: http://launchpadlibrarian.net/490452795/mir_1.7.1-0ubuntu6_1.7.1-0ubuntu7.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+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 1887964] Re: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found
After more testing, it seems the file is not read because the line in /etc/crypttab doesn't have end of line. This returns empty: hexdump /etc/crypttab | grep 0a This adds end of line, fixing the problem: sudo sed -i -e '$a\' /etc/crypttab -- 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/1887964 Title: VG unavailable after upgrade from 18.04 to 20.04 Cannot process volume group vg01 Volume group "vg01" not found Status in lvm2 package in Ubuntu: Confirmed Status in lvm2 source package in Focal: Confirmed Bug description: After upgrading a laptop configured with LVM from 18.04 to 20.04 the volume group is no longer found. During boot the console shows Volume group "vg01" not found Cannot process volume group vg01 Gave up waiting for suspend/resume device ALERT! /dev/mapper/vg01-root does not exist. Dropping to a shell! Attached dist-upgrade logs and console output. Tried the "vgck --updatemetadata vg01" recommended on this bug report: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874381 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887964/+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 1889059] Re: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams
** Tags added: id-5f1ef5fbb4e583090040ab60 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1889059 Title: [Ubuntu 20.04] zlib on s390x may produce incomplete raw (but not gzip/zlib) streams Status in Ubuntu on IBM z Systems: New Status in zlib package in Ubuntu: New Status in zlib source package in Focal: New Status in zlib source package in Groovy: New Bug description: zlib on s390x may produce incomplete raw (but not gzip/zlib) streams ---uname output--- Linux t35lp56.lnxne.boe 5.8.0-20200703.rc3.git0.52a479d42203.300.fc31.s390x #1 SMP Fri Jul 3 00:46:20 CEST 2020 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Create a raw (negative windowBits value) stream with zlib. EOBS might be missing or truncated. This affects all distro levels that contain hardware acceleration (DFLTCC) patch. I've attached the preliminary fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889059/+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
> One thing that would help with these confusing NXDOMAIN errors in general the vast, VAST majority of the time you see this message it is actually not a NXDOMAIN error. This is due to a Ubuntu-only patch to systemd to work around some select captive portals that are slightly broken, so in any environment outside the broken captive portals (e.g. public wifi that you have to 'click here to accept terms' before getting internet access - and note that not all captive portals are broken) if you see this NXDOMAIN "error" it is almost always just a normal lookup of a domain that doesn't exist, and the error message is simply wrong (this also slows down dns due to forcing fallback to a lower dns protocol level and retry of the already-failed lookup). To clarify specifically for this bug, the lookup of "connectivity- check.ubuntu.com.your_domain" clearly has nothing to do with any "DNS violation", and the NXDOMAIN returned by the upstream nameserver is the *correct* response - that hostname really, actually doesn't exist. network-manager could work around this problematic Ubuntu-only systemd patch, but the real problem is unquestionably that systemd should not have the Ubuntu-only patch that's causing these messages. Fixing this appropriately (i.e. so that systemd still works with the broken captive portal issue) requires access to one of the broken captive portals, so I haven't been able to work on correctly fixing this lately, but it is something I want to do, so we can get rid of the very unfortunate false NXDOMAIN "error" messages. -- 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/1880258 Title: Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce NXDOMAIN warning noise Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in network-manager source package in Focal: 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 1889189] Re: "Authentication Required" window after waking up
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1824874, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1889189 Title: "Authentication Required" window after waking up Status in xorg package in Ubuntu: Invalid Bug description: Hi. Sometimes (not always) when the computer wakes up after sleep, on the desktop the "Authentication Required" window is shown at an unusuall position, i.e. (top, left) coordinates = (0, 0). (see the attached screenshot) The worst part is that I enter my password and nothing happens and the buttons do not respond. Then I restart the computer to get rid of it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 14:48:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1889189/+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 1889206] [NEW] Regression in USN-4436-1
*** This bug is a security vulnerability *** Public security bug reported: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Affects: librsvg (Ubuntu Xenial) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Affects: librsvg (Ubuntu Bionic) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Also affects: librsvg (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: librsvg (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: librsvg (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: librsvg (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: librsvg (Ubuntu Xenial) Status: New => Confirmed ** Changed in: librsvg (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1889206 Title: Regression in USN-4436-1 Status in librsvg package in Ubuntu: New Status in librsvg source package in Xenial: Confirmed Status in librsvg source package in Bionic: Confirmed Bug description: The security fix for librsvg introduced a regression in aisleriot. Steps to reproduce: 1- install gnome-cards-data 2- run "sol" to start Aislerot 3- Switch card layout to "Anglo" 4- Notice some cards are missing graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1889206/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Also having issues here after upgrading to ubuntu 20.04 (it was a clean install, everything worked fine in 19.10) Also having issues after upgrading to 20.04 (A clean install did not help it) Everything worked fine on 19.10. Headphones Boose: QC35 Jabra evolve 65 stereo Laptop: Dell XPS13 9380 Ubuntu 20.04 - 5.4.0-42-generic Bluez - 5.53-0ubuntu3 PulseAudio - 13.99.1 -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1889189] [NEW] "Authentication Required" window after waking up
Public bug reported: Hi. Sometimes (not always) when the computer wakes up after sleep, on the desktop the "Authentication Required" window is shown at an unusuall position, i.e. (top, left) coordinates = (0, 0). (see the attached screenshot) The worst part is that I enter my password and nothing happens and the buttons do not respond. Then I restart the computer to get rid of it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 14:48:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on 2020-04-19 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: ASUSTeK Computer Inc. F82Q ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=ad3f3a2c-64bc-415b-b70c-4da2b1dbf0af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F82Q dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd05/19/2009:svnASUSTeKComputerInc.:pnF82Q:pvr1.0:rvnASUSTeKComputerInc.:rnF82Q:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F82Q dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Screenshot from 2020-07-28 14-35-49.png" https://bugs.launchpad.net/bugs/1889189/+attachment/5396504/+files/Screenshot%20from%202020-07-28%2014-35-49.png ** Description changed: Hi. Sometimes (not always) when the computer wakes up after sleep, on - the desk the "Authentication Required" window is shown at an unusuall + the desktop the "Authentication Required" window is shown at an unusuall position, i.e. (top, left) coordinates = (0, 0). (see the attached screenshot) The worst part is that I enter my password and nothing happens and the buttons do not respond. Then I restart the computer to get rid of it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 14:48:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] -Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] + Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] + Subsystem: ASUSTeK Computer Inc. Mobile 4 Series Chipset Integrated Graphics Controller [1043:1863] InstallationDate: Installed on
[Touch-packages] [Bug 1888992] Re: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones
Please test this kernel: https://people.canonical.com/~hwang4/testdetect/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1888992 Title: [Realtek ALC892, Green Headphone Out, Front] Not detecting/switching to front jack after plugging in headphones Status in alsa-driver package in Ubuntu: New Bug description: I boot my system without any sound devices plugged into any jacks; checking Gnome settings Sound, Output Device is "Dummy Output" (no other options available in drop-down list). I plug in headphones into the front jack and play some audio, but do not hear any sound from the headphones; checking Gnome settings Sound, the Output Device is still "Dummy Output", with no other options available. This is a regression from previous behaviour, when plugging in headphones into the front jack would automatically enable/switch to the front jack and its associated controller "Family 17h (Models 00h- 0fh) HD Audio Controller" (this is the motherboard's onboard audio hardware). I can currently workaround this each time I plug in the headphones by installing and running pavucontrol, and under Configuration selecting "Analogue Stereo Output (unplugged) (unavailable)" - this option becomes "Analogue Stereo Output" after I select it. This seems to be a regression in pulseaudio after an upgrade from from 1:13.99.1-1ubuntu3.3 to 1:13.99.1-1ubuntu3.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/pcmC1D0p: chinf 1741 F...m pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio /dev/snd/timer: chinf 1741 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 12:46:52 2020 InstallationDate: Installed on 2018-10-29 (635 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chinf 1741 F pulseaudio /dev/snd/controlC0: chinf 1741 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-04 (83 days ago) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1888992/+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 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output
Enable the -proposed channel on a bionic machine without internal speaker sudo apt-get update sudo apt install pulseaudio the version 1:11.1-1ubuntu7.10 is installed to the machine. plug a headphone, and select the headset from the popup dialogue, the output device changes to headphone successfully and the sound could output from headphone. it fixes this issue. Verified done. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1882248 Title: [SRU] plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Bug description: This is for pulseaudio bionic: [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, the active profile is Off, after users plug a headset to it and users select the headset from the pop-up dialogue, users expect the profile changes to analog-stereo (headset is on it), but the active_profile is still Off. [Fix] Upstream already has a patch to fix it, cherrypiack that patch to bionic. And that patch is already in the eoan, focal, ... [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and select the headset from UI, the profile changes to analog-stereo, and play some sound, we could hear it from the headset [Regression Risk] Low, this patch is already in the upstream for a long time, and it is already in the eoan and focal. For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+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 1889166] Re: mir: build failure on s390x
Looking at the code, it is written correctly and handles the case where strncpy() "truncates before the terminating nul". It is unfortunate that this triggers a warning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+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 1747878] Re: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provide
** Changed in: pulseaudio (Ubuntu) Assignee: ravishanker vishwakarma (ravishanker) => (unassigned) -- 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/1747878 Title: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is logged since a while on that desktop (default ubuntu install) [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Googling about it: https://stackoverflow.com/questions/37132033/ofono-dbus-introspection-method-not-found https://github.com/pulseaudio/pulseaudio/blob/master/src/modules/bluetooth/backend-ofono.c Also note Debian has more recent version: http://metadata.ftp-master.debian.org/changelogs/main/p/pulseaudio/pulseaudio_11.1-4_changelog note: that install has no 'ofono' package installed; and sound works as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1319 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 7 10:49:34 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1747878/+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 1715764] Re: Flickering Screen
** Package changed: xorg (Ubuntu) => unity (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/1715764 Title: Flickering Screen Status in unity package in Ubuntu: Confirmed Bug description: Screen flickers particularly when I use Discord but have also experienced it with Minecraft. Occasionally have issues with misplaced pixels in slack and mozilla firefox, but much less frequently with firefox. Only have experienced pixels being misplayed whilst being on vox and maybe one or two others I'm forgetting, have not had any issues when using most websites. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 8 00:19:34 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80a1] InstallationDate: Installed on 2016-09-01 (371 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=93999ca7-5b83-4851-969c-5482f1b9ee8d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.77 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A1 dmi.board.vendor: HP dmi.board.version: 91.1C dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.77:bd12/18/2015:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A1:rvr91.1C:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 5 00:34:29 2017 xserver.configfile: default xserver.errors: intel(0): Failed to submit rendering commands (No such file or directory), disabling acceleration. intel(0): When reporting this, please include /sys/class/drm/card0/error and the full dmesg. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1715764/+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 1889166] Re: mir: build failure on s390x
** Description changed: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the - meanwhile I0n giubg to disable that error + meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, - from /<>/src/miral/xcursor.c:26: + from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, - inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, - inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, - inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: + inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, + inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, + inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] - 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); - | ^~ + 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); + | ^~ In function ‘strncpy’, - inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, - inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, - inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: + inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, + inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, + inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] - 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); - | ^~ + 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); + | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I'm probably going to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1
[Touch-packages] [Bug 1747878] Re: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provide
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => ravishanker vishwakarma (ravishanker) -- 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/1747878 Title: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is logged since a while on that desktop (default ubuntu install) [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Googling about it: https://stackoverflow.com/questions/37132033/ofono-dbus-introspection-method-not-found https://github.com/pulseaudio/pulseaudio/blob/master/src/modules/bluetooth/backend-ofono.c Also note Debian has more recent version: http://metadata.ftp-master.debian.org/changelogs/main/p/pulseaudio/pulseaudio_11.1-4_changelog note: that install has no 'ofono' package installed; and sound works as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1319 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 7 10:49:34 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1747878/+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 1889167] Re: mir: build failure on s390x
*** This bug is a duplicate of bug 1889166 *** https://bugs.launchpad.net/bugs/1889166 ** This bug has been marked a duplicate of bug 1889166 mir: build failure on s390x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889167 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889167/+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 1889166] Re: mir: build failure on s390x
** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1889166/+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 1889054] Re: No audio on TRX40 platform
@sohail right, the HDMI is part of my Nvidia card, so it is not built into the motherboard. @Daniel, I have tried with the latest mainline kernel. Still no luck. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1889054 Title: No audio on TRX40 platform Status in alsa-driver package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Confirmed Bug description: Hello, I have Ubuntu 20.04 running on a computer based on AMD Threadripper 3960x, TRX40 platform (Gigabyte TRX40 AORUS PRO). Audio hasn't worked so far. I read about audio problems on this platform from the beginning but they should be fixed in kernel 5.6 according to this https://www.phoronix.com/scan.php?page=news_item=Linux-AMD-TRX40 -Audio-Quirks Kernel bug reports should be related to these ones: https://bugzilla.kernel.org/show_bug.cgi?id=206873 https://bugzilla.kernel.org/show_bug.cgi?id=206543 Since it should be fixed in recent kernel versions, I guess the solution for Ubuntu 20.04 using 5.4 kernel is backporting the fixes. Is Ubuntu planning to do this? Thanks Eduardo ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Jul 27 10:41:15 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2020-03-05 (143 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to focal on 2020-04-06 (111 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: eduardo1907 F pulseaudio /dev/snd/controlC0: eduardo1907 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-05 (144 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-06 (112 days ago) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/24/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: TRX40 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd10/24/2019:svnGigabyteTechnologyCo.,Ltd.:pnTRX40AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnTRX40AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: TRX40 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1889054/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.
Related: bug #1888585 ( https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1888585 ) The error "seahorse (seahorse) glib-watch.c → 195 → timeout_update → Assertion `!t->dead'' failed." is listed with hundreds of occurrences each day at https://errors.ubuntu.com/ but there is no bug report assigned to it there, the "Bug report" column is empty. Should it be associated with this bug report, or perhaps with bug #1888585 ? -- 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/1820584 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. Status in avahi package in Ubuntu: Confirmed Bug description: - Description: Ubuntu Disco Dingo (development branch) Release: 19.04 - seahorse: Installed: 3.32-1 Candidate: 3.32-1 Version table: *** 3.32-1 500 500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status - I have absolutely no idea why or how. Just collected this report from apport-cli. Some times receiving "internal error" reports, no details provided, just "Cancel" or "Send report" options. So, I decided to check apport and there was this report. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: seahorse 3.32-1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 18:09:01 2019 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316) ProcCmdline: /usr/bin/seahorse --gapplication-service Signal: 6 SourcePackage: seahorse StacktraceTop: __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 "glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1889166] [NEW] mir: build failure on s390x
Public bug reported: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs ** Affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889166 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from
[Touch-packages] [Bug 1889167] [NEW] mir: build failure on s390x
Public bug reported: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:726:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:875:10: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 7 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘_XcursorAddPathElt’ at /<>/src/miral/xcursor.c:647:5, inlined from ‘_XcursorBuildFullname’ at /<>/src/miral/xcursor.c:727:5, inlined from ‘xcursor_load_theme’ at /<>/src/miral/xcursor.c:884:11: /usr/include/s390x-linux-gnu/bits/string_fortified.h:106:10: error: ‘strncpy’ output truncated before terminating nul copying 11 bytes from a string of the same length [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors make[3]: *** [src/miral/CMakeFiles/miral-internal.dir/build.make:183: src/miral/CMakeFiles/miral-internal.dir/xcursor.c.o] Error 1 make[3]: *** Waiting for unfinished jobs ** Affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1889167 Title: mir: build failure on s390x Status in mir package in Ubuntu: New Bug description: Hello, looks like we are missing one "+1" from somewhere, but I don't have enough knowledge on this code... can you please have a look? in the meanwhile I0n giubg to disable that error cd /<>/build-s390x/src/miral && /usr/bin/cc -DBOOST_ALL_NO_LIB -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DEGL_NO_X11 -DLOG_NDEBUG=1 -DLTTNG_UST_HAVE_SDT_INTEGRATION -DMESA_EGL_NO_X11_HEADERS -DMIR_DRMMODEADDFB_HAS_CONST_SIGNATURE -DMIR_LOG_COMPONENT_FALLBACK=\"miral\" -DMIR_SERVER_EGL_OPENGL_API=EGL_OPENGL_ES_API -DMIR_SERVER_EGL_OPENGL_BIT=EGL_OPENGL_ES2_BIT -DMIR_SERVER_GLEXT_H="" -DMIR_SERVER_GL_H="" -DMIR_VERSION_MAJOR=1 -DMIR_VERSION_MICRO=1 -DMIR_VERSION_MINOR=7 -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -D_GNU_SOURCE -I/<>/include/core -I/<>/include/common -I/<>/include/cookie -I/<>/src/include/common -I/<>/build-s390x/src/capnproto -I/<>/build-s390x/src/protobuf -I/<>/include/platform -I/<>/include/client -I/<>/include/server -I/<>/src/include/platform -I/<>/include/miral -I/usr/include/uuid -I/<>/include/wayland -I/<>/src/wayland/generated -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -g -Wall -pedantic -Wextra -fPIC -Werror -flto -ffat-lto-objects -fvisibility=hidden -pthread -o CMakeFiles/miral-internal.dir/xcursor.c.o -c /<>/src/miral/xcursor.c In file included from /usr/include/string.h:495, from /<>/src/miral/xcursor.c:26: In function ‘strncpy’, inlined from
[Touch-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
I can't figure out what happened. Please file a new bug here: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues -- 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/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" 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" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Touch-packages] [Bug 1889100] Re: Screen bug
*** This bug is a duplicate of bug 1754284 *** https://bugs.launchpad.net/bugs/1754284 Unfortunately you appear to be using two features that will cause this: Fullscreen windows on the modeset Xorg driver: bug 1754284 Fractional scaling on the modeset Xorg driver: bug 1846398 The only ways to avoid the bars (screen tearing) on a system like yours would be: * Choose 'Ubuntu on Wayland' from the login screen to avoid Xorg; or * Avoid fullscreen windows and avoid fractional scaling, when using Xorg. ** This bug has been marked a duplicate of bug 1754284 Fullscreen windows are tearing in Xorg sessions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1889100 Title: Screen bug Status in xorg package in Ubuntu: New Bug description: I have this weird screen bug that was not present on Windows, the OS I used before Ubuntu. I have reinstalled Ubuntu but this has not fixed the issue. When scrolling or watching a video in full screen, there are two bars that appear in the middle of the screen widthways. The bars are transparent but you can still see the outline of them and they also move around slightly meaning it can be quite distracting. The bars are not there when doing other tasks like general work like web browsing and email unless you scroll. It seems to only be an issue when a large part of the screen has to refresh at any one time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 16:22:20 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3f1a] InstallationDate: Installed on 2020-07-22 (4 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 002: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81VV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1664842e-9af5-44b6-a3c8-f9235f094044 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN21WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.modalias: dmi:bvnLENOVO:bvrCUCN21WW(V1.10):bd05/27/2020:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1889100/+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 1889015] Re: display crashes sometimes when click on firefox or settings
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Tags added: nouveau ** Summary changed: - display crashes sometimes when click on firefox or settings + [nouveau] display crashes sometimes when click on firefox or settings -- 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/1889015 Title: [nouveau] display crashes sometimes when click on firefox or settings (GeForce 6150SE nForce 430) Status in Ubuntu: Incomplete Bug description: display crashes sometimes when click on firefox or settings ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jul 26 16:07:13 2020 DistUpgraded: 2020-07-09 17:13:15,323 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a58] InstallationDate: Installed on 2020-07-09 (17 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 001 Device 002: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion RX885AA-ABA a6000n ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=e43514f2-3e33-49da-9662-a8e8923b87f6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-09 (16 days ago) dmi.bios.date: 02/02/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.01 dmi.board.name: NARRA dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.01:bd02/02/2007:svnHP-Pavilion:pnRX885AA-ABAa6000n:pvr:rvnASUSTekComputerINC.:rnNARRA:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: RX885AA-ABA a6000n dmi.sys.vendor: HP-Pavilion 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.4 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: Sun Jul 26 16:01:21 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1889015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1889013] Re: Xorg freeze
In the cases when you can still move the cursor then that means gnome- shell has frozen but Xorg keeps working. But you might be experiencing multiple different problems. Regardless, the answer is the same :) ... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg freeze + Screen freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (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/1889013 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: Everything is running smooth, I enjoy this software, but it all freezes up randomly. Sometimes I can still move the cursor, other times I cannot do anything but a hard reset. Do not know why, or haven't figured out what specifically I am doing when this happens. Usually just browsing the net or something simple like that when it happens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 14:01:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:099d] InstallationDate: Installed on 2020-07-13 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-532 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=eb592001-0986-4e81-8bae-52faaa85ba41 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_BA dmi.board.vendor: Acer dmi.board.version: V1.16 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.16:bd11/13/2015:svnAcer:pnAspireE5-532:pvrV1.16:rvnAcer:rnZoro_BA:rvrV1.16:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire E5-532 dmi.product.sku: Aspire E5-532_099D_1.16 dmi.product.version: V1.16 dmi.sys.vendor: Acer 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1
Thanks Cliff! Note: the server question you wondered would have been the details how exactly (commands( you do "syncd is enabled and started at boot with the rsyncd.conf". Because in that might lay the details we need. I was setting up a server on my own aligned to your config. The following makes it easy for everyone to try to re-create as it is just copy to get it working - it will work on a fresh install of any Ubuntu with rsync installed. Summary: Host 20.10 - Rsync 3.2.1 Client 20.04 - Rsync 3.1.3 #1 Setup on the Host to prep, config and debug-start rsyncd as demon: # Something to sync mkdir /mnt/testrsync touch /mnt/testrsync/testfile mkdir /mnt/testrsync/testdir touch /mnt/testrsync/testdir/testfile2 # Config cat << EOF > /etc/rsyncd.conf pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [test_dir] path = /mnt/testrsync comment = Test Directory uid = ubuntu gid = ubuntu read only = no list = yes hosts allow = 10.253.194.0/24 auth users = ubuntu secrets file = /etc/rsyncd.scrt strict modes = false EOF cat << EOF > /etc/rsyncd.scrt ubuntu:ubuntu EOF # Start with max debug in local console rsync -vv --daemon --config /etc/rsyncd.conf --no-detach #2 Then on the client try to connect mkdir /mnt/client export RSYNC_PASSWORD=ubuntu rsync -vurptC rsync://ubuntu@10.253.194.39/test_dir /mnt/client receiving incremental file list ./ testfile testdir/ testdir/testfile2 sent 77 bytes received 218 bytes 590.00 bytes/sec total size is 0 speedup is 0.00 Works just fine, at the same time the server says: $ rsync -vv --daemon --config /etc/rsyncd.conf --no-detach --log-file=/dev/stdout 2020/07/28 05:55:52 [7940] rsyncd version 3.2.1 starting, listening on port 873 2020/07/28 05:56:21 [7942] connect from f.lxd (10.253.194.30) 2020/07/28 05:56:21 [7942] rsync allowed access on module test_dir from f.lxd (10.253.194.30) In my case (just like in yours) it recognizes the configured module "test_dir" in my case "Bin_dir" in yours. From there it finds all the content and syncs it. Your error suggests a chroot issue that I can't reproduce even with that setup close to yours. I added "use chroot = yes" to the daemon config but it behaves the same. Might on your upgrade anything else have changed that influences this - like under which user the daemon runs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1
@Cliff - if you run the above simplified case does it work for you? - if it does, could you try making it closer and closer to your setup until you've identified what makes it break? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1888685 Title: rsync fails after installing level 3.2.1 Status in rsync package in Ubuntu: Incomplete Bug description: After installation of rsync.3.2.1 my attempt to sync fails with chroot error. The rsyncd.log indicates that rsync can't find the directories I want to sync. 2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873 2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: No such file or directory (2) 2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or service not known 2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from UNKNOWN (192.168.1.159) 2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings failed: No such file or directory (2) Dropping back to Ubuntu 20.04 and rsync works again. The rsync update was install 7/18. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: rsync 3.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 23 10:28:17 2020 InstallationDate: Installed on 2020-07-06 (16 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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 1888940] Re: RShift + LShift works together with LAlt + LShift to switch language layout
** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** No longer affects: ubuntu-meta (Ubuntu) -- 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/1888940 Title: RShift + LShift works together with LAlt + LShift to switch language layout Status in gnome-settings-daemon package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 1. Have default Ubuntu 20.04 LTS installed 2. Configure two keyboard layouts - English and Russian 3. Configure + as keyboard layout switcher in GNOME Tweaks 4. Press and hold , then do multiple click on Expected results: * nothing, keyboard layout does not change Actual results: * keyboard layout changes as when + was clicked --- Details: ``` $ cat /etc/default/keyboard ; gsettings get org.gnome.desktop.input-sources xkb-options ; gsettings get org.freedesktop.ibus.general.hotkey triggers XKBLAYOUT=us,ru XKBVARIANT=, BACKSPACE=guess ['grp:lalt_lshift_toggle'] ['space'] ``` Note: first seen on https://askubuntu.com/q/1261935 . --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:57:06 2020 InstallationDate: Installed on 2020-04-27 (88 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1888940/+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
