[Touch-packages] [Bug 1886246] [NEW] Xorg freeze
Public bug reported: Sometimes on my lock screen, my mouse stops for a moment, and also many times certain application freezes and then I have to force quit them. Also, it is not going too fast, it takes much time to boot up. Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 10:22:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-520 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-26-generic root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Bellemere_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: KB dmi.product.name: Aspire ES1-520 dmi.product.sku: Aspire ES1-520_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze 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/1886246 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Sometimes on my lock screen, my mouse stops for a moment, and also many times certain application freezes and then I have to force quit them. Also, it is not going too fast, it takes much time to boot up. Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 10:22:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-520 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-26-generic root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1876354] Re: Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch
[Expired for software-properties (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-properties (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1876354 Title: Fresh installed Ubuntu 20.04 misses a button for login on Ubuntu one account to enable lifepatch Status in software-properties package in Ubuntu: Expired Bug description: Two days ago I have reported a bug describing the complete path starting from the software updater button settings/lifepatch > lifepatch > sign in/lifepatch Then a window was opened Line at top: X [] Ubuntu Single Sign-on Account Next line: same title as above without X [] Next line: Email address: field Next line: (*) I have an Ubuntu Single Sign-on Account Next line: Password: field Next line: ( ) I want to register for an account now Next line: ( ) I've forgotten my password Bottom line: link Privacy Policy There is no button to confirm any action above I looked for help at https://help.ubuntu.com/community/CommunityHelpWiki and clicked on support on the next page https://ubuntu.com/support/community-support I clicked on Lifepatch. Then on https://ubuntu.com/livepatch I found: free for personal use Get Lifepatch. Next page: https://auth.livepatch.canonical.com/?_ga=2.18896568.1031641790.1588091589-177936974.1572286294 Get your Lifepatch token. On the next page I got a key and two command lines to enable Lifepatch https://auth.livepatch.canonical.com/?user_type=ubuntu-user sudo snap install canonical-livepatch sudo canonical-livepatch enable ***key*** (a 32 digits code with letters and numbers) My problem was easily solved using the commands above in a terminal I feel silly that I have reported this two days ago as a bug. I took me two days to find a solution. Now an icon on top toolbar shows that lifepatch is activated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1876354/+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 1875782] Re: tracker-store and tracker-extract using 100% CPU
[Expired for tracker (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tracker (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1875782 Title: tracker-store and tracker-extract using 100% CPU Status in tracker package in Ubuntu: Expired Bug description: After upgrading from Ubuntu 18.04 to Ubuntu 20.04, tracker-store and tracker-extract processes are using 100% CPU. CPU temperature goes above 80 degrees celsius. This is causing fan spinning and computer is very loud because of it. I've tried removing tracker package, but it wants to remove the whole desktop with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1875782/+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 1886245] [NEW] bluetooth freezing after boot
Public bug reported: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description:Ubuntu 20.04 LTS Release:20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:193521 acl:13666 sco:0 events:137 errors:0 TX bytes:5858 acl:61 sco:0 commands:82 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1886245/+attachment/5389533/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886245 Title: bluetooth freezing after boot Status in bluez package in Ubuntu: New Bug description: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description: Ubuntu 20.04 LTS Release: 20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) 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 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
** Patch removed: "procps debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886112/+attachment/5389194/+files/lp1886112_procps_groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. 3) Add a commented out '# kernel.dmesg_restrict = 0' to /etc/sysctl.d/10-kernel-hardening.conf For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by uncommenting the sysctl in /etc/sysctl.d/10-kernel-hardening.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed
The issue appears to be that update-initramfs creates uncompressed images. I have the same error but have been dealing with a different issue of it failing to boot with a custom kernel by UUID which is why I haven't posted a bug report. However, since this issue appears to be related, upon further inspection I find that none of the initramfs images being created are actually compressed at all. file /boot/initrd.img* /boot/initrd.img: symbolic link to initrd.img-5.4.0-40-generic /boot/initrd.img-5.4.0-33-generic: ASCII cpio archive (SVR4 with no CRC) /boot/initrd.img-5.4.0-37-generic: ASCII cpio archive (SVR4 with no CRC) /boot/initrd.img-5.4.0-39-generic: ASCII cpio archive (SVR4 with no CRC) /boot/initrd.img-5.4.0-40-generic: ASCII cpio archive (SVR4 with no CRC) These should all be lz4 images. I tried changing the initramfs config to gzip but it still did not show a compressed file. -- 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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1841745] Re: Update to 1.2.0
** Changed in: libxt (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1841745 Title: Update to 1.2.0 Status in libxt package in Ubuntu: New Status in libxt package in Debian: New Bug description: The new version has non trivial change and is not in Debian/Fedora yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1841745/+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 1886235] Re: EMU 1212m card (emu10k1 driver) stops working after PCI reset
Here's t he information I got from alsa-info: http://alsa-project.org/db/?f=0adb1150463e905a6584004021bacf1f11c850cc ** Summary changed: - EMU 1212m card (emu10k1 driver) stops working after PCI reset + EMU 1212m card (emu10k1 driver) stops working after PCI reset snd_emu10k1 invalid position buffer size -- 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/1886235 Title: EMU 1212m card (emu10k1 driver) stops working after PCI reset snd_emu10k1 invalid position buffer size Status in alsa-driver package in Ubuntu: New Bug description: After using my computer for a day or so and coming back to it, my sound card, EMU 1212m, randomly stops to work. And the only solution I have found is completely turn off the power to the motherboard and wait a few minutes until powering back on. When the card works, I am able to reproduce the problem after typing: sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset Executing that command stops the card from outputting any sound, and I see the following printed in dmesg: [ 73.029029] snd_pcm_update_hw_ptr0: 3153 callbacks suppressed [ 73.029033] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029114] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029122] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.040768] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.046208] snd_emu10k1 :05:04.0: interrupt: PCI error [ 73.046235] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046244] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046250] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046255] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046261] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046266] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] Further resets result in [ 497.663897] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663971] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663997] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.674025] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.684046] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.694065] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 It seems this is a problem with the driver snd_emu10k1 (maybe invalid buffer size?). In the past, I have used this card in earlier Ubuntu's before without any issues. All I had to do was to build and install the latest alsa-firmware, alsa-lib, and alsa-utils from https://www.alsa-project.org/wiki/Download. It's surprising that this card is not natively supported out of the box in 20.04, but even worse, the driver emu10k1 appears to be broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 14:56:03 2020 InstallationDate: Installed on 2020-06-16 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1409 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1409:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
[Touch-packages] [Bug 1234325] Re: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjpeg
libjpeg8:i386 8d-1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: libjpeg8-empty (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1234325 Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: Invalid Bug description: unable to launch gnome session ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libjpeg8 8c-2ubuntu7 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sat Sep 28 02:00:27 2013 DuplicateSignature: package:libjpeg8:8c-2ubuntu7:tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2 ErrorMessage: tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2 InstallationDate: Installed on 2013-09-12 (19 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: tentative de remplacement de « /usr/lib/i386-linux-gnu/libjpeg.so.8 », qui appartient aussi au paquet libjpeg-turbo8:i386 1.2.1-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1234325/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps
** Changed in: apport (Ubuntu) Milestone: ubuntu-20.04.1 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: [SRU] ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store Server: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Bug description: [Impact] Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap. [Test Case] Install subiquity snap: # sudo snap install subiquity --classic subiquity 20.06.1 aus Canonical✓ installiert # snap list | grep subiquity subiquity 20.06.1 1938 latest/stable canonical* classic ubuntu-bug subiquity results in message: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You are about to report a bug against the deb package, but you also a have snap published by canonical installed. You can contact them via https://bugs.launchpad.net/subiquity for help. Do you want to continue with the bug report against the deb? What would you like to do? Your options are: Y: Yes N: No C: Cancel === New/Expected Result === ubuntu-bug should ask the user if he/she wants to report the bug against the snap or deb package, if both are installed. If the snap is chosen, the "Snap" and "SnapSource" fields should be part of the report: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: subiquity 20.06.1 (stable) snap 2: subiquity (1938) deb package C: Cancel Please choose (1/2/C): 1 . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (46.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V Make sure the following two fields are part of the generated report: == Snap = subiquity 20.06.1 (stable) == SnapSource = subiquity [Regression Potential] Small; the change adds a new add_snap_info() method to report.py and is triggered in the ui.py logic only in cases which would have otherwise lead to an error message. Furthermore, the change has been uploaded to Groovy some while ago where it is being used and tested. [Original Bug Report] Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1886235] [NEW] EMU 1212m card (emu10k1 driver) stops working after PCI reset
Public bug reported: After using my computer for a day or so and coming back to it, my sound card, EMU 1212m, randomly stops to work. And the only solution I have found is completely turn off the power to the motherboard and wait a few minutes until powering back on. When the card works, I am able to reproduce the problem after typing: sudo echo 1 > /sys/bus/pci/devices/:05:04.0/reset Executing that command stops the card from outputting any sound, and I see the following printed in dmesg: [ 73.029029] snd_pcm_update_hw_ptr0: 3153 callbacks suppressed [ 73.029033] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029114] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.029122] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.040768] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 73.046208] snd_emu10k1 :05:04.0: interrupt: PCI error [ 73.046235] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046244] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046250] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046255] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046261] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] [ 73.046266] AMD-Vi: Event logged [IO_PAGE_FAULT device=05:00.0 domain=0x0015 address=0x0 flags=0x] Further resets result in [ 497.663897] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663971] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.663997] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.674025] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.684046] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 [ 497.694065] snd_emu10k1 :05:04.0: invalid position: , pos = 16759783, buffer size = 16384, period size = 16384 It seems this is a problem with the driver snd_emu10k1 (maybe invalid buffer size?). In the past, I have used this card in earlier Ubuntu's before without any issues. All I had to do was to build and install the latest alsa-firmware, alsa-lib, and alsa-utils from https://www.alsa-project.org/wiki/Download. It's surprising that this card is not natively supported out of the box in 20.04, but even worse, the driver emu10k1 appears to be broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 14:56:03 2020 InstallationDate: Installed on 2020-06-16 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1409 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X570-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1409:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX570-EGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886235 Title: EMU 1212m card (emu10k1 driver) stops working after PCI reset Status in alsa-driver package in Ubuntu: New Bug description: After using my computer for a day or so and coming back to it, my sound card, EMU 1212m, randomly stops to work. And the only solution I have found is completely turn off
[Touch-packages] [Bug 1184148] Re: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-turbo
libjpeg8:i386 8d-1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: libjpeg8-empty (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1184148 Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-turbo8:i386 1.2.1-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: Invalid Bug description: - ProblemType: Package DistroRelease: Ubuntu 13.04 Package: libjpeg8 8c-2ubuntu7 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Thu May 23 08:24:58 2013 ErrorMessage: intentando sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-turbo8:i386 1.2.1-0ubuntu2 InstallationDate: Installed on 2013-04-15 (39 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu7 failed to install/upgrade: intentando sobreescribir `/usr/lib/i386-linux-gnu/libjpeg.so.8', que está también en el paquete libjpeg-turbo8:i386 1.2.1-0ubuntu2 UpgradeStatus: Upgraded to raring on 2013-04-26 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1184148/+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 1357242] Re: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1
libjpeg8:amd64 8d-1+deb7u1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: libjpeg8-empty (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1357242 Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: Invalid Bug description: When I boot up, the application tells me it crashes. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libjpeg8 8c-2ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 13 22:07:06 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.1 libgcc1 1:4.9.1-0ubuntu1 libjpeg-turbo8 1.3.0-0ubuntu2 multiarch-support 2.19-0ubuntu6.1 DpkgTerminalLog: Preparing to unpack .../libjpeg8_8d-1+deb7u1_amd64.deb ... Unpacking libjpeg8:amd64 (8d-1+deb7u1) over (8c-2ubuntu8) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg8_8d-1+deb7u1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2 DuplicateSignature: package:libjpeg8:8c-2ubuntu8:trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2 InstallationDate: Installed on 2014-06-18 (57 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libjpeg.so.8', which is also in package libjpeg-turbo8:amd64 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1357242/+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 1371271] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: tentative de remplace
libjpeg8 8d-1+deb7u1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: libjpeg8-empty (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1371271 Title: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du paquet libjpeg8:i386 Status in libjpeg8-empty package in Ubuntu: Invalid Bug description: i don't know im a new user on ubuntu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Thu Sep 18 20:06:35 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9.1-0ubuntu1 libjpeg-turbo8 1.3.0-0ubuntu2 multiarch-support 2.19-0ubuntu6.3 DuplicateSignature: package:libjpeg8:8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright]:tentative de remplacement de « /usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du paquet libjpeg8:i386 ErrorMessage: tentative de remplacement de « /usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du paquet libjpeg8:i386 InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libjpeg8/copyright », qui est différent d'autres instances du paquet libjpeg8:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1371271/+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 1756502] Re: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite s
libjpeg8:i386 (8d-1+deb7u1) libjpeg8:amd64 (8d-1+deb7u1) Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: libjpeg8-empty (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1756502 Title: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is different from other instances of package libjpeg8:i386 Status in libjpeg8-empty package in Ubuntu: Invalid Bug description: dont know my system charshes for what ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 16 15:48:52 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu10 DuplicateSignature: package:libjpeg8:8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] Unpacking libjpeg8:i386 (8c-2ubuntu8) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg8_8c-2ubuntu8_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is different from other instances of package libjpeg8:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is different from other instances of package libjpeg8:i386 InstallationDate: Installed on 2018-02-17 (27 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.25 SourcePackage: libjpeg8-empty Title: package libjpeg8 8c-2ubuntu8 [modified: usr/share/doc/libjpeg8/changelog.Debian.gz usr/share/doc/libjpeg8/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg8/copyright', which is different from other instances of package libjpeg8:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1756502/+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 1751489] Re: rsync dies with "inflate returned -3 (0 bytes)"
** Changed in: rsync (Debian) Status: New => Fix Released -- 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/1751489 Title: rsync dies with "inflate returned -3 (0 bytes)" Status in rsync package in Ubuntu: Incomplete Status in rsync package in Debian: Fix Released Bug description: On Ubuntu 16.04, when rsyncing big KVM VM image (17,055,219,712 bytes), sync error happens each time I try to use command rsync -vaz -e ssh host:/path/to/file ./ The full text printed: inflate returned -3 (0 bytes) rsync error: error in rsync protocol data stream (code 12) at token.c(557) [receiver=3.1.1] rsync: connection unexpectedly closed (72 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [generator=3.1.1] On receiving side: Ubuntu 16.04.3 64bit, rsync 3.1.1-3ubuntu1.2 On remote side: Ubuntu 14.04.5 64bit, rsync 3.1.0-2ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1751489/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
https://news.softpedia.com/news/canonical-under-fire-for-putting-ads-in-the-ubuntu-motd-530372.shtml Article like "Canonical Under Fire for Putting Ads in the Ubuntu MOTD" miss the point that motd-news is not only displaying Advertising in the login prompt but it a Privacy Nightmare because it has an hidden Telemetry feature which is enabled by default Without Consent and leak IP Address, System critical informations (Kernel Version, Uptime, CPU Vendor, CPU Model, Idle Time, Uptime) every 12 hours via User-Agent from curl on all Ubuntu Desktop and Ubuntu Server including the current version of Ubuntu. On top of that, motd-news is also a security nightmare as it runs curl as root which can be exploited to gain root on any servers, laptops etc. I recommend that all Ubuntu users open a Terminal and execute the following sudo sed -i -r 's/(ENABLED)=.+/\1=0/' /etc/default/motd-news sudo apt-get -qq -y purge curl N.B. curl is not installed if you explicitly select Ubuntu Minimal during the installation of Ubuntu Desktop so motd-news cannot contact motd.ubuntu.com without curl even if ENABLED=1 by default GDPR : EU's General Data Protection Regulation since daily reporting of computer's infos are proceeded without the user's consent. Cf. GDPR application comments [https://gdpr.eu/eu-gdpr-personal-data/], in particular with respect to Recital 30 [https://gdpr.eu/recital-30 -online-identifiers-for-profiling-and-identification/] Internet protocol (IP) addresses; information that is related to an individual’s tools, applications, or devices, like their computer. Canonical Ltd. has handled my personal information without concent. By collecting twice a day the following informations: - The public IP address where Ubuntu system is used (part of the log of the HTTPS server) - Date / Time when collected (part of the log of the HTTPS server) - Harware info such as CPU Vendor and Model (via /proc/cpuinfo) - The distribution version (via /etc/lsb-release) - The operating system (via uname -o) - The Linux kernel release (via uname -r) - The computer architecture aka machine hardware name (via uname -m) - Cloud Hosting: cloud identifier such as aws, gce, azure, lxd (via cloud-id part of cloud-init) - Total number of seconds the system has been up (via /proc/uptime) - The sum of how much time each core has spent idle in seconds (via /proc/uptime) - Version of curl software (launched as root which is a bad IT practice and a security risk) -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com current Advertising for Canonical Products" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389475/+files/ubuntu-desktop-2004-translate.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2017" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389478/+files/ubuntu-desktop-2004-waybackmachine3.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news force to run via motd-news.service and motd-news.timer" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389472/+files/ubuntu-desktop-2004-terminal3.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2020" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389477/+files/ubuntu-desktop-2004-waybackmachine2.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news ENABLED by default with telemetry every 12h Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389471/+files/ubuntu-desktop-2004-terminal2.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news is unremovable" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389480/+files/ubuntu-desktop-2004-system-failure1.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Privacy has not opt-out for motd-news hidden telemetry in User-Agent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389470/+files/ubuntu-desktop-2004-privacy.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "No, don't send system info NOT RESPECTED BY MOTD-NEWS" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389468/+files/ubuntu-desktop-2004-optout.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com is up since 2017" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389476/+files/ubuntu-desktop-2004-waybackmachine.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd-news exfiltrate system information via User-Agent and IP Address every 12 hours Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389482/+files/ubuntu-desktop-2004-motd-news.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "motd.ubuntu.com hosted in the Amazon EC2 cloud in Dublin, Leinster, Ireland" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389474/+files/ubuntu-desktop-2004-terminal4.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Legal Notice DOES NOT COVER "motd-news" sending IP address, Uptime, Idle time every 12h motd-news.service started during installation Ubuntu Desktop 20.04 Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389469/+files/ubuntu-desktop-2004-legal.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Sample motd.ubuntu.com Ads from 2019" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389479/+files/ubuntu-desktop-2004-waybackmachine4.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
** Attachment added: "Trying to remove motd-news via base-files will kill Ubuntu" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389481/+files/ubuntu-desktop-2004-system-failure2.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
No updates from Canonical's legal departement "A picture is worth a thousand words" ** Attachment added: "motd-news.service started during installation Ubuntu Desktop 20.04 Without Consent" https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+attachment/5389467/+files/ubuntu-desktop-2004.png -- 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/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background Status in base-files package in Ubuntu: Won't Fix Bug description: In package base-files there is a script /etc/update-motd.d/50-motd- news that harvests private hardware data from the machine and transmits it in the background every day. There is no notice, no consent, no nothing. This should be by default disabled until there is informed consent. This solution is simple: 1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 2. Place a comment in the file disclosing the fact that the 50-motd-news script will harvest private hardware data and upload it to motd.ubuntu.com daily if the end-user enables it. Creating databases that maps ip address to specify hardware is a threat to both privacy and security. If an adversary knows the specific hardware and the ip address for that hardware their ability to successfully attack it is greatly increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+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 1808864] Re: Poor translation of zh_CN gpasswd(1) man page
** Changed in: shadow (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-zh-hans in Ubuntu. https://bugs.launchpad.net/bugs/1808864 Title: Poor translation of zh_CN gpasswd(1) man page Status in Ubuntu Translations: New Status in language-pack-zh-hans package in Ubuntu: New Status in shadow package in Ubuntu: In Progress Bug description: man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz The zh_CN version of gpasswd(1) not only is partially done, but also contains an error in the first sentence. The translator confused the verb "administer" with the person "administrator." The section heading, originally "Notes (noun) about group passwords," was translated as "Please note (verb) the group passwords." Even Google translate does better! Translation errors == gpasswd - administer /etc/group and /etc/gshadow gpasswd - 管理员 /etc/group 和 /etc/gshadow ^^ 管理员 -- administrator 管理 -- administer Notes about group passwords 请注意组密码 ^^ 请注意…… -- please note (v.) 关于……的说明 -- notes (n.) about Typos = -h, --help Display help message and exit. -h, --help 现实帮助信息并退出。 显示 Xiǎnshì -- display 现实 Xiànshí -- reality Correct Google translate results (this but unironically) "gpasswd - administer /etc/group and /etc/gshadow" "gpasswd - 管理 /etc/group 和 /etc/gshadow" "Notes about group passwords" "关于组密码的说明" "Display help message and exit." "显示帮助消息并退出。" Notes about my system = $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy passwd passwd: Installed: 1:4.5-1ubuntu1 Candidate: 1:4.5-1ubuntu1 Version table: *** 1:4.5-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1808864/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/386842
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Eoan:
Confirmed
Status in openldap source package in Focal:
Confirmed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/386703
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/386841
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Eoan:
Confirmed
Status in openldap source package in Focal:
Confirmed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** Also affects: openldap (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: openldap (Ubuntu Eoan)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Eoan:
Confirmed
Status in openldap source package in Focal:
Confirmed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** Changed in: openldap (Ubuntu Eoan)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Eoan:
Confirmed
Status in openldap source package in Focal:
Confirmed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/386701
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/386702
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1557157
Title:
apparmor profile denied for saslauthd: /run/saslauthd/mux
Status in openldap package in Ubuntu:
Fix Released
Status in openldap source package in Trusty:
Won't Fix
Status in openldap source package in Xenial:
Confirmed
Status in openldap source package in Bionic:
Confirmed
Status in openldap source package in Focal:
Confirmed
Status in openldap source package in Groovy:
Fix Released
Bug description:
[Impact]
When using openldap with sasl authentication, the slapd process will
communicate with the saslauthd daemon via a socket in
{,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
Ubuntu release from trusty onwards, because slapd's apparmor profile
doesn't contain the necessary directive to allow it to read/write
from/to the socket specified above.
The fix is simple: just add the necessary directive to allow slapd to
read/write from/to the saslauthd socket.
[Test Case]
One can reproduce the problem by doing:
$ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
$ lxc shell openldap-bugbug1557157-groovy
# apt install slapd sasl2-bin ldap-utils apparmor-utils
(As the domain name, use "example.com").
# sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
# cat > /etc/ldap/sasl2/slapd.conf << __EOF__
mech_list: PLAIN
pwcheck_method: saslauthd
__EOF__
# adduser openldap sasl
# aa-enforce /etc/apparmor.d/usr.sbin.slapd
# systemctl restart slapd.service
# systemctl restart saslauthd.service
# passwd root
(You can choose any password here. You will need to type it when
running the next command.)
# ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
-Y PLAIN
The command will fail with something like:
ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
additional info: SASL(-1): generic failure: Password verification
failed
[Regression Potential]
This is an extremely simple and well contained fix, so I don't
envision any possible regressions after applying it. It is important
noticing that, since the problem affects older Ubuntu releases, the
openldap package will have to be rebuilt against possible newer
versions of libraries and other depencencies, which, albeit unlikely,
may cause issues.
[Original Description]
When using slapd with saslauthd the processes communicate via the
{,/var}/run/saslauthd/mux socket (this is the default location for the
saslauthd server from the sasl2-bin package in the
/etc/default/saslauthd config), but the apparmor profile for
usr.sbin.slapd does not allow access to this socket/file.
Syslog message:
apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd"
name="/run/saslauthd/mux" pid=1880
4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
Please add the following line to /etc/apparmor.d/usr.sbin.slapd:
/{,var/}run/saslauthd/mux rw,
Ubuntu version: Ubuntu 14.04.4 LTS
slapd version: 2.4.31-1+nmu2ubu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1841745] Re: Update to 1.2.0
** Bug watch added: Debian Bug tracker #962735 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962735 ** Also affects: libxt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962735 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1841745 Title: Update to 1.2.0 Status in libxt package in Ubuntu: New Status in libxt package in Debian: Unknown Bug description: The new version has non trivial change and is not in Debian/Fedora yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1841745/+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 1886217] Re: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1886217 Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Invalid Bug description: Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula with Supreme FX audio card. No sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 21:25:22 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Maximus Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Maximus Formula dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886217/+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 1886217] [NEW] [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all
Public bug reported: Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula with Supreme FX audio card. No sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 21:25:22 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Maximus Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Maximus Formula dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886217 Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Clean install of Ubuntu 20.04 LTS on motherboard Asus Maximus Formula with Supreme FX audio card. No sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 21:25:22 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmitrys2051 F pulseaudio /dev/snd/controlC1: dmitrys2051 F pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [Maximus Formula, Analog Devices AD1988B, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Maximus Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: Maximus Formula dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
So I'm following up after a long time away from my laptop. I'm currently experiencing an error which says: TLS/SSL support not available; install glib-networking. I'm not sure why this is happening but I'm willing to poke around if you are able to help me. I"m hoping together we can ID the cause. I'm sorry to say that I haven't been willing to even open my laptop because of this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1882636 Title: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Status in glib-networking package in Ubuntu: Incomplete Bug description: OS: Pop!_OS 20.04 LTS x86_64 Host: XPS 13 9370 Kernel: 5.4.0-7634-generic Uptime: 2 hours, 50 mins Packages: 1817 (dpkg), 20 (snap) Shell: bash 5.0.16 Resolution: 1920x1080 DE: GNOME WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-8250U (8) @ 3.400GHz GPU: Intel UHD Graphics 620 Memory: 3322MiB / 15729MiB Summary(cont) - Attempt to input Google account info into online account util and get error--> TLS/SSL support not available; install glib-networking. https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777 Referenced this BUG REPORT ##Downloaded Deb build but I'm having an issue applying appropriate inputs in the provided documentation. Please help!## To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+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 1886204] Re: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card
** 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/1886204 Title: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card Status in xorg package in Ubuntu: New Bug description: Initially, Ubuntu started with far lower resolution than my monitor. I've tried xrandr --newmode command*, it temporarily helps to get back to my original 1600X900 resolution. But now screen sometimes go back to that lower resolution (and randpomly comes back to normal after some time), and xrandr doesn't help. Plus, my screen keeps flickering, sometimes quite frequently. Combined with low resolution, it has become almost unbearable at this point. Things work alright with windows 10 (dual boot). Further details: 1. Sometimes, but not always, simply going to Display Setting by GUI or typing xrandr in command line fixes it. 2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1: probed a monitor but no|invalid EDID" while shutting down or in /var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id" in the log. 3. Using read-edid package, I noticed that while on low res, it can't detect EDID on any bus. However if I keep running this command, at some point it successfully reads & parses EDID. Then, if I go to Display Setting, or after some time automatically- the resolution comes back to normal. 4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change the situation. 5. I've tried Wayland, awesome window manager, lightdm display manager. I'd rather not change the GNOME environment. 6. Tried Ubuntu 18.04.4 (current OS), now its always low resolution. Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor: Samsung SyncMaster E2020 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.7.1-050701-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 20:53:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 6570/7570/8550] [174b:e193] InstallationDate: Installed on 2020-07-02 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~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 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/1886204/+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 1886204] [NEW] Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card
You have been subscribed to a public bug: Initially, Ubuntu started with far lower resolution than my monitor. I've tried xrandr --newmode command*, it temporarily helps to get back to my original 1600X900 resolution. But now screen sometimes go back to that lower resolution (and randpomly comes back to normal after some time), and xrandr doesn't help. Plus, my screen keeps flickering, sometimes quite frequently. Combined with low resolution, it has become almost unbearable at this point. Things work alright with windows 10 (dual boot). Further details: 1. Sometimes, but not always, simply going to Display Setting by GUI or typing xrandr in command line fixes it. 2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1: probed a monitor but no|invalid EDID" while shutting down or in /var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id" in the log. 3. Using read-edid package, I noticed that while on low res, it can't detect EDID on any bus. However if I keep running this command, at some point it successfully reads & parses EDID. Then, if I go to Display Setting, or after some time automatically- the resolution comes back to normal. 4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change the situation. 5. I've tried Wayland, awesome window manager, lightdm display manager. I'd rather not change the GNOME environment. 6. Tried Ubuntu 18.04.4 (current OS), now its always low resolution. Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor: Samsung SyncMaster E2020 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.7.1-050701-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 20:53:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 6570/7570/8550] [174b:e193] InstallationDate: Installed on 2020-07-02 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~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 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 focal resolution ubuntu -- Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card https://bugs.launchpad.net/bugs/1886204 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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
2.3.1-2.1ubuntu4 is the version of libseccomp2 which is available, i.e. $ sudo apt install libseccomp2=2.3.1-2.1ubuntu4 succeeds. That allowed me to uncomment, i.e. enable, the SystemCallFilter in /lib/systemd/system/systemd-resolved.service again and reboot successfully. -- 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/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=, stack_end=0x7ffe78153748) at ../csu/libc-start.c:310 #14 0x563b957164fa in ?? () (gdb) -->8-- and the kernel message buffer lists --8<-- traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 error:0 in libc-2.27.so[7f17ebed7000+1e7000] -->8-- . To me that looked a bit like Bug 669702 of Gentoo (https://bugs.gentoo.org/669702) and indeed one of the (few) updates applied just prior the reboot was the update of libseccomp. I was able to circumvent the problem by disabling (commenting out) the syscall filtering requested by systemd (on my system, only /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be modified). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Apple Inc. Macmini5,1 NonfreeKernelModules: wl Package: systemd 237-3ubuntu10.41 [modified: lib/systemd/system/systemd-resolved.service] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B10.1201241549 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.family: Macmini dmi.product.name: Macmini5,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.4.0-1ubuntu1~18.04 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) NonfreeKernelModules: wl Package: libseccomp2 2.4.3-1ubuntu3.18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
I get the same error as Alex, but for TGA files: ``` tracker-extract[13828]: Call to gst_discoverer_discover_uri(file://[...]/Ale_col.tga) failed: Internal data stream error. ``` The error only occurs with certain TGAs, I shall attaching one below. My current workaround is to add '*.tga' to "/org/freedesktop/tracker/miner/files/ignored-files" in `dconf-editor`. SYSTEM: ``` #lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 #apt-cache policy tracker* tracker-extract: Installed: 2.3.3-2 Candidate: 2.3.3-2 tracker-miner-fs: Installed: 2.3.3-2 Candidate: 2.3.3-2 tracker: Installed: 2.3.4-1 Candidate: 2.3.4-1 ``` ** Attachment added: "Ale_col.tga" https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+attachment/5389438/+files/Ale_col.tga -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
> can you confirm which one you have had to disable the SystemCallFilter? Both files are just symlinks to /lib/systemd/system/systemd-resolved.service. > Also there appear to be a bunch of systemd managed services which have failed > to run I moved snap related services out of the way recently as it isn't used here. systemd complains, but I didn't observe any other ill effects yet. > could you perhaps downgrade libseccomp back to the previous version and see > if this resolves the issue? --8<-- $ sudo apt install libseccomp=2.4.1-0ubuntu0.18.04.2 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package libseccomp tho@deimos:~$ sudo apt install libseccomp2=2.4.1-0ubuntu0.18.04.2 Reading package lists... Done Building dependency tree Reading state information... Done E: Version '2.4.1-0ubuntu0.18.04.2' for 'libseccomp2' was not found -->8-- I attempted to downgrade earlier, but couldn't readily find that original package. Let me have another look (I might have still the original install medium) ... > try and capture a more complete stack trace of the crash Hmmh? The call stack is fairly shallow here (not untypical for non-recursive applications programmed in C), what do you expect is missing? I saved the original core file, but can produce a new one as you described above later. -- 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/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=, stack_end=0x7ffe78153748) at ../csu/libc-start.c:310 #14 0x563b957164fa in ?? () (gdb) -->8-- and the kernel message buffer lists --8<-- traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 error:0 in libc-2.27.so[7f17ebed7000+1e7000] -->8-- . To me that looked a bit like Bug 669702 of Gentoo (https://bugs.gentoo.org/669702) and indeed one of the (few) updates applied just prior the reboot was the update of libseccomp. I was able to circumvent the problem by disabling (commenting out) the syscall filtering requested by systemd (on my system, only /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be modified). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Apple Inc. Macmini5,1 NonfreeKernelModules: wl Package: systemd 237-3ubuntu10.41 [modified: lib/systemd/system/systemd-resolved.service] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B10.1201241549
[Touch-packages] [Bug 1886197] Re: FTBFS in b due to libseccomp change
** Changed in: systemd Status: Unknown => Fix Released -- 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/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. Xenial does not include the __NR__sysctl check so does not need this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+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 1886197] Re: FTBFS in b due to libseccomp change
** Description changed: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. + + Xenial does not include the __NR__sysctl check so does not need this + patch. -- 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/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. Xenial does not include the __NR__sysctl check so does not need this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+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 1886197] Re: FTBFS in b due to libseccomp change
** Description changed: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] - #if __NR__sysctl > 0 - ^~~~ + #if __NR__sysctl > 0 + ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. + + This is fixed upstream by commit + 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and + later, so this is fixed already for Focal and later. ** Bug watch added: github.com/systemd/systemd/issues #14031 https://github.com/systemd/systemd/issues/14031 ** Also affects: systemd via https://github.com/systemd/systemd/issues/14031 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => High ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress -- 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/1886197 Title: FTBFS in b due to libseccomp change Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. This is fixed upstream by commit 4df8fe8415eaf4abd5b93c3447452547c6ea9e5f which is included in v244 and later, so this is fixed already for Focal and later. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1886197/+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 1886197] [NEW] FTBFS in b due to libseccomp change
Public bug reported: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1886197 Title: FTBFS in b due to libseccomp change Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: New Bug description: [impact] systemd FTBFS in b because __NR__sysctl was force-defined by libseccomp in 2.4.1-0ubuntu0.18.04.2, but that force-defining was (correctly) reverted in the latest version 2.4.3-1ubuntu3.18.04.2. On arm64, __NR__sysctl is not defined, so the build now fails, e.g.: https://launchpadlibrarian.net/486997294/buildlog_ubuntu-bionic-arm64.systemd_237-3ubuntu10.42~202007031245~ubuntu18.04.1_BUILDING.txt.gz ../src/test/test-seccomp.c: In function ‘test_protect_sysctl’: ../src/test/test-seccomp.c:251:5: error: "__NR__sysctl" is not defined, evaluates to 0 [-Werror=undef] #if __NR__sysctl > 0 ^~~~ [test case] build systemd on bionic with latest packages (i.e. with latest libseccomp2 package) [regression potential] this adds a defined() check before comparing the __NR__sysctl value, so any regression would be limited to the specific function test_protect_sysctl() which is part of the test framework, thus leading to a failed build or incorrectly passed/failed test. [scope] this is needed only in Bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886197/+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: plug headset won't proper reconfig ouput to it on machine with default output
** Changed in: linux-oem (Ubuntu Bionic) Status: New => 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: 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: New Status in linux-oem source package in Bionic: Fix Committed Status in pulseaudio source package in Bionic: New Bug description: 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 1885730] Re: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor
** Tags added: id-5efdfa465220b783b19272c2 -- 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/1885730 Title: Bring back ondemand.service or switch kernel default governor for pstate - pstate now defaults to performance governor Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Groovy: Confirmed Status in systemd source package in Groovy: New Bug description: In a recent merge from Debian we lost ondemand.service, meaning all CPUs now run in Turbo all the time when idle, which is clearly suboptimal. The discussion in bug 1806012 seems misleading, focusing on p-state vs other drivers, when in fact, the script actually set the default governor for the pstate driver on platforms that use pstate. Everything below only looks at systems that use pstate. pstate has two governors: performance and powerstate. performance runs CPU at maximum frequency constantly, and powersave can be configured using various energy profiles energy profiles: - performance - balanced performance - balanced power - power It defaults to balanced performance, I think, but I'm not sure. Whether performance governor is faster than powersave governor is not even clear. https://www.phoronix.com/scan.php?page=article=linux50-pstate- cpufreq=5 benchmarked them, but did not benchmark the individual energy profiles. For a desktop/laptop, the expected behavior is the powersave governor with balanced_performance on AC and balanced_power on battery. I don't know about servers or VMs, but the benchmark series seems to indicate it does not really matter much performance wise. I think most other distributions configure their kernels to use the powersave governor by default, whereas we configure it to use the performance governor and then switch it later in the boot to get the maximum performance during bootup. It's not clear to me that's actually useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
this affects me for some years now, bosses now complain for me to move to windows as now we are all remote with tons of meetings and this is a big impact on how they see all this linux desktop adoption. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps
Verification done on focal: === Snap only: $ LANGUAGE=en_US apport-cli snap-store *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching snap-store *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (2.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V [...] == Snap = snap-store 3.36.0-80-g208fd61 (latest/stable/ubuntu-20.04) == SnapSource = snap-store [...] === Snap, for snap & deb installed $ LANGUAGE=en_US apport-cli gnome-calculator *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: gnome-calculator 3.36.0+git9.96b95fd2 (stable) snap 2: gnome-calculator 1:3.36.0-1ubuntu1 deb package C: Cancel Please choose (1/2/C): 1 *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (25.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V [...] == Snap = gnome-calculator 3.36.0+git9.96b95fd2 (stable) == SnapSource = ubuntu/+source/gnome-calculator == Tags = focal snap [...] === Deb, for snap & deb installed $ LANGUAGE=en_US apport-cli gnome-calculator *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: gnome-calculator 3.36.0+git9.96b95fd2 (stable) snap 2: gnome-calculator 1:3.36.0-1ubuntu1 deb package C: Cancel Please choose (1/2/C): 2 . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (25.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V [...] == Package = gnome-calculator 1:3.36.0-1ubuntu1 == SourcePackage = gnome-calculator == Tags = focal [...] === Deb only $ LANGUAGE=en_US apport-cli gnome-terminal *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (25.5 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V [...] == Package = gnome-terminal 3.36.2-1ubuntu1~20.04 == SourcePackage = gnome-terminal [...] ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: [SRU] ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store Server: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Bug description: [Impact] Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap. [Test Case] Install subiquity snap: # sudo snap install subiquity --classic subiquity 20.06.1 aus Canonical✓ installiert # snap list | grep subiquity subiquity 20.06.1 1938 latest/stable canonical* classic ubuntu-bug subiquity results in message: #
[Touch-packages] [Bug 1861082] Re: [SRU] ubuntu-bug doesn't know how to file bugs against snaps
@brian-murray subiquity is somehow special cased via `data/package- hooks/subiquity.py` and it was that way even before we added the snap handling. @seth-arnold Yes. Apport can only report bugs automatically if there is a launchpad project provided via the snap's contact field. Snap developers need to adopt their snap meta data accordingly. Good examples are: gnome-calculator gnome-system-monitor subiquity git-ubuntu ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: [SRU] ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store Server: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Committed Bug description: [Impact] Users of Ubuntu 20.04 are not able to easily report bugs against applications provided as a snap. [Test Case] Install subiquity snap: # sudo snap install subiquity --classic subiquity 20.06.1 aus Canonical✓ installiert # snap list | grep subiquity subiquity 20.06.1 1938 latest/stable canonical* classic ubuntu-bug subiquity results in message: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You are about to report a bug against the deb package, but you also a have snap published by canonical installed. You can contact them via https://bugs.launchpad.net/subiquity for help. Do you want to continue with the bug report against the deb? What would you like to do? Your options are: Y: Yes N: No C: Cancel === New/Expected Result === ubuntu-bug should ask the user if he/she wants to report the bug against the snap or deb package, if both are installed. If the snap is chosen, the "Snap" and "SnapSource" fields should be part of the report: # LANGUAGE="en_US" apport-cli subiquity *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ...dpkg-query: no packages found matching subiquity *** You have two versions of this application installed, which one do you want to report a bug against? Choices: 1: subiquity 20.06.1 (stable) snap 2: subiquity (1938) deb package C: Cancel Please choose (1/2/C): 1 . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (46.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): V Make sure the following two fields are part of the generated report: == Snap = subiquity 20.06.1 (stable) == SnapSource = subiquity [Regression Potential] Small; the change adds a new add_snap_info() method to report.py and is triggered in the ui.py logic only in cases which would have otherwise lead to an error message. Furthermore, the change has been uploaded to Groovy some while ago where it is being used and tested. [Original Bug Report] Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659719] Re: ssh can't call a binary from a snap without the full path
That won't be too different from /usr/local/sbin and /usr/local/bin being in the PATH but empty I think. I am not aware of any problem or annoyance caused by nonexisting directories being in the PATH. -- 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: Confirmed Status in snapd package in Ubuntu: Confirmed 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: Confirmed Status in snapd source package in Groovy: Confirmed Bug description: ssh can't call a binary from a snap, it will only work using the full path. 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 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1785383 -- 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/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+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 1886163] Re: systemd-resolved emits totally useless warning
Maybe related: bug 1796501 -- 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/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1886163/+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 1886163] [NEW] systemd-resolved emits totally useless warning
Public bug reported: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.1:bd12/06/2018:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0FRVY0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R230 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R230 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1886163 Title: systemd-resolved emits totally useless warning Status in systemd package in Ubuntu: New Bug description: With systemd-resolved taking care of resolving DNS requests, it will emit following warning message when domain fails to resolve: Jul 02 07:19:22 balancer1 systemd-resolved[1269]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. This warning message is missing information about the process that's trying to resolve a domain and (this part is the more important bit) information about the domain that systemd-resolved is trying to resolve in the first place. If the warning message cannot be made meaningful, it should be dropped for good. I'd prefer to log at least the domain name that was being tried to be resolved. Having pid and name of the process that needed the information would be a plus. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jul 3 11:59:22 2020 InstallationDate: Installed on 2019-05-22 (407 days ago) InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190226) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M MachineType: Dell Inc. PowerEdge R230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=41607337-6732-464c-b97c-429504aa1b23 ro SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-06-01 (31 days ago) dmi.bios.date: 12/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.1 dmi.board.name: 0FRVY0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.asset.tag: lb1.peda.net dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1886161] [NEW] UU is almost useless on itinerant laptops
Public bug reported: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU is almost useless on itinerant laptops Status in unattended-upgrades package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1886151] Re: monitor problem
I can see some strange things happening every few seconds in XorgLog.txt Please try: 1. Deleting your monitor settings by deleting the file: ~/.config/monitors.xml 2. Reboot and tell us if the problem happens again. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: multimonitor -- 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/1886151 Title: monitor problem Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: my second monitor turn off, the appeared with resized set and then just disappear, not able to turn it on again, although the light of the led is on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 09:24:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1357] InstallationDate: Installed on 2020-06-29 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Acer Extensa 215-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Taurus_WC dmi.board.vendor: CML dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Extensa 15 dmi.product.name: Extensa 215-51 dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A 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 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/mutter/+bug/1886151/+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 1885990] Re: server: Match has no effect in include file (upstream 3122)
This is server-next as soon as 8.4 is in groovy, I tagged it already to not forget it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+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 1885990] Re: server: Match has no effect in include file (upstream 3122)
We just fixed bug 1876320 for includes, seems there might be more for it to do. But at the same time I think this is low-prio e.g. I think we can wait until ssh 8.4 hits groovy and then think about a backport instead of adding Delta for it right away. Thank you for the bug Patel. ** Bug watch added: OpenSSH Portable Bugzilla #3122 https://bugzilla.mindrot.org/show_bug.cgi?id=3122 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=3122 Importance: Unknown Status: Unknown ** Changed in: openssh (Ubuntu) Status: New => Triaged ** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1885990 Title: server: Match has no effect in include file (upstream 3122) Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: Hello Ubuntu version: focal 20.04 LTS Version: openssh-server: Installed: 1:8.2p1-4ubuntu0.1 Candidate: 1:8.2p1-4ubuntu0.1 Expected: match statement in included files work as documented in the fine manual What happens: the statements are ignored. If you add Match statements in an included file, it will generate no error but have no effect. The exact same statements work in the main server config file (/etc/ssh/sshd_config) this is to track upstream bug 3122: https://bugzilla.mindrot.org/show_bug.cgi?id=3122 it's fixed but will only be in 8.4 so it affects Ubuntu 20.04 LTS where openssh is at 8.2. I'm not *absolutely* whining for a backport since include files is a new feature for openssl in focal so it's not a regression. Would be nice though :), because include files are standard for any server software in Linux since at least a decade... To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1885990/+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 1886151] [NEW] monitor problem
Public bug reported: my second monitor turn off, the appeared with resized set and then just disappear, not able to turn it on again, although the light of the led is on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 09:24:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1357] InstallationDate: Installed on 2020-06-29 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Acer Extensa 215-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Taurus_WC dmi.board.vendor: CML dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Extensa 15 dmi.product.name: Extensa 215-51 dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886151 Title: monitor problem Status in xorg package in Ubuntu: New Bug description: my second monitor turn off, the appeared with resized set and then just disappear, not able to turn it on again, although the light of the led is on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 09:24:00 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1357] InstallationDate: Installed on 2020-06-29 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Acer Extensa 215-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=4a77fddc-3b20-4cf4-9395-4f25052d3ae9 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Taurus_WC dmi.board.vendor: CML dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd03/31/2020:svnAcer:pnExtensa215-51:pvrV1.09:rvnCML:rnTaurus_WC:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Extensa 15 dmi.product.name: Extensa 215-51 dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A 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 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
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) I don't have .xprofile but i created it my home folder like you suggested and added the text, mine was HDMI3. Unfortunately it doesn't seem to do anything. I also observed that changing the DPI solves the issue on most distros I tried. But i don't like any other DPI than 100%. Also in regard to the workaround posted by me changing to DRI 2, mostly solves the issue on gnome on POP OS, still a few mouse trails but it is bearable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+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 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot
I am confused - in the initial bug report you mention /etc/systemd/system/dbus-org.freedesktop.resolve1.service as the systemd unit but now you also mention /etc/systemd/system/dbus- org.freedesktop.ModemManager1.service - can you confirm which one you have had to disable the SystemCallFilter? Also there appear to be a bunch of systemd managed services which have failed to run - could you perhaps downgrade libseccomp back to the previous version and see if this resolves the issue? I think this would be a better solution *for now* than disabling the syscall filter (plus it will help confirm whether this is definitely a causal factor). sudo apt install libseccomp=2.4.1-0ubuntu0.18.04.2 The other option to try and help debug this would be to try and capture a more complete stack trace of the crash - perhaps something like the following might be enough: 1. Ensure the likely offending version of libseccomp is installed (2.4.3-1ubuntu3.18.04.2) (if you downgraded it above) 2. Uncomment out the SystemCallFilter line from the systemd unit 3. Restart the systemd unit (do not reboot) (assuming it is the dbus one you first mentioned): sudo systemctl restart dbus-org.freedesktop.resolve1.service Then with any luck if systemd does crash it at least not be during boot - and apport should catch the crash and create a crash dump. Then you should be able to report this (either as a separate bug or you could attach it to this bug via `apport-bug /var/crash/` -- 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/1886115 Title: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot Status in libseccomp package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: After applying updates to Ubuntu 18.04 my desktop (apple mini with i5-2415M CPU) failed to complete the boot process. A few seconds into the boot, the last message displayed is "/var mounted". The system then appears to hang indefinitely. Luckily, the 'rescue' boot image allows the boot process to proceed sufficiently far to allow a root shell to be spawned. Unfortunately no log files were written during the unsuccessful attempts to boot. Spawning a 2nd root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to observe the message 'systemd freezing execution' after I closed the first root shell and resumed the boot process. Further a core file was created (belonging to /sbin/init) in the root fs --8<-- (gdb) bt #0 0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78 #1 0x563b957223b7 in ?? () #2 #3 __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103 #4 0x563b9577c22e in ?? () #5 0x563b957672d6 in ?? () #6 0x563b9576ba22 in ?? () #7 0x563b9574f51a in ?? () #8 0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so #9 0x7f16803a53ea in sd_event_dispatch () from /lib/systemd/libsystemd-shared-237.so #10 0x7f16803a5579 in sd_event_run () from /lib/systemd/libsystemd-shared-237.so #11 0x563b9572a49d in ?? () #12 0x563b9571560c in ?? () #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, argv=0x7ffe78153758, init=, fini=, rtld_fini=, stack_end=0x7ffe78153748) at ../csu/libc-start.c:310 #14 0x563b957164fa in ?? () (gdb) -->8-- and the kernel message buffer lists --8<-- traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 error:0 in libc-2.27.so[7f17ebed7000+1e7000] -->8-- . To me that looked a bit like Bug 669702 of Gentoo (https://bugs.gentoo.org/669702) and indeed one of the (few) updates applied just prior the reboot was the update of libseccomp. I was able to circumvent the problem by disabling (commenting out) the syscall filtering requested by systemd (on my system, only /etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be modified). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-30 (460 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Apple Inc. Macmini5,1 NonfreeKernelModules: wl Package: systemd 237-3ubuntu10.41 [modified: lib/systemd/system/systemd-resolved.service] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-62-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/24/2012
[Touch-packages] [Bug 1874962] Re: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other
libpango-1.0-0:1.42.4-7~deb10u1 Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: pango1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874962 Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other instances of package libpango-1.0-0:amd64 Status in pango1.0 package in Ubuntu: Invalid Bug description: Rendering issues with the monospace default font (DejaVu Mono Book) led me to try and downgrade the libpango packages, which in turn caused this problem with the system packages. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpango-1.0-0 1.42.4-7~deb10u1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 23:15:13 2020 DuplicateSignature: package:libpango-1.0-0:1.42.4-7~deb10u1 Unpacking libpangocairo-1.0-0:amd64 (1.44.7-2ubuntu4) over (1.42.4-7~deb10u1) ... dpkg: error processing archive /var/cache/apt/archives/libpangocairo-1.0-0_1.44.7-2ubuntu4_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpangocairo-1.0-0/copyright', which is different from other instances of package libpangocairo-1.0-0:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other instances of package libpango-1.0-0:amd64 InstallationDate: Installed on 2014-09-11 (2052 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) 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-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: pango1.0 Title: package libpango-1.0-0 1.42.4-7~deb10u1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpango-1.0-0/NEWS.gz', which is different from other instances of package libpango-1.0-0:amd64 UpgradeStatus: Upgraded to focal on 2020-04-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1874962/+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
