[Touch-packages] [Bug 2056627] Re: PHPStorm crashes when opening a project
Also occurs with https://lmstudio.ai/ which is also AppImage based. I think the feature is broken in general ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056627 Title: PHPStorm crashes when opening a project Status in apparmor package in Ubuntu: Confirmed Bug description: Filing mostly in case anyone else hits this and is looking for workarounds: Since the Update to 24.04 PHPStorm crashes on open for me. I think when it tries to preview a markdown file, like a README.md which is shown when opening a project. ``` [0309/094602.913394:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /home/user/bin/phpstorm/jbr/lib/chrome-sandbox is owned by root and has mode 4755. ``` Workaround 1 (wont persist reboots, needs root): sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0 sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 Workaround 2 (persists and doesn't need root): thanks to https://youtrack.jetbrains.com/issue/IDEA-313202/IDE- crashes-due-to-chrome-sandbox-is-owned-by-root-and-has-mode-error- when-IDE-is-launching-the-JCEF-in-a- sandbox#focus=Comments-27-7059083.0-0 * Run `/bin/phpstorm.sh dontReopenProjects` (to avoid it crashing on start) * ctrl+shift+a * type "Registry..." and select it * disable the "ide.browser.jcef.sandbox.enable" option * Restart phpstorm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056627/+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 1915226] Re: network-manager continuous inappropriate site surveys
Kroger is conducting a customer satisfaction survey to learn about customers' actual experience during their Kroger store visit. As a token of appreciation from the company, the management is offering 50 fuel points for free to the customers who participated in the survey on the https://kroger-feedback.online/ official site. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1915226 Title: network-manager continuous inappropriate site surveys Status in network-manager package in Ubuntu: New Bug description: this message is flooding my kernel ring RTW: ERROR [RFK-CHK] RF-K not allowed due to ifaces under site-survey network details are as follows. ~$ ifconfig eno1: flags=4163 mtu 1500 inet 192.168.0.10 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::d323:619a:9114:8f78 prefixlen 64 scopeid 0x20 ether 48:0f:cf:5f:e6:12 txqueuelen 1000 (Ethernet) RX packets 49088 bytes 15509621 (15.5 MB) RX errors 0 dropped 0 overruns 0 frame RTL8811CU0 TX packets 36480 bytes 5212324 (5.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xd100-d102 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 204584 bytes 11022005 (11.0 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 204584 bytes 11022005 (11.0 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlx001325ad55e1: flags=4163 mtu 1500 inet 192.168.1.103 netmask 255.255.255.0 broadcast 192.168.1.255 inet6 fe80::9a15:f995:c011:c29e prefixlen 64 scopeid 0x20 ether 00:13:25:ad:55:e1 txqueuelen 1000 (Ethernet) RX packets 62335 bytes 9276176 (9.2 MB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 4605 bytes 645037 (645.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eno1 is through motherboard wlx001325ad55e1 is though USB: Volans VL-UW60-FD using a RTL8811CU chip (see https://www.volans.com.au/product/vl-uw60-fd/) Both cable and wireless connections are working well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 10 12:06:18 2021 InstallationDate: Installed on 2021-01-14 (26 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev eno1 proto dhcp metric 100 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 metric 600 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1915226/+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 2048405] Re: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/
With community support on Libera IRC's #ubuntu Andi and I were able to determine the root cause of this issue was apparently a read-only /usr file system (caused by a user-initiated system configuration change). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/2048405 Title: multiple packages failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system Status in sqlite3 package in Ubuntu: Invalid Bug description: The auto software updater appeared and asked if I wanted to install new packages. I said yes, it started working and then showed me several of the automatic "a problem has occurred" boxes. I clicked "send" on each. The three bug titles it attempted to make were: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read- only file system package distro-info 1.5 failed to install/upgrade: unable to create '/usr/bin/debian-distro-info.dpkg-new' (while processing './usr/bin/debian-distro-info'): Read-only file system package distro-info-data 0.58ubuntu0.1 failed to install/upgrade: unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system This here is the libsqlite bug. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: libsqlite3-0 3.42.0-1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Jan 5 17:18:15 2024 DpkgHistoryLog: Start-Date: 2024-01-05 17:18:15 Commandline: aptdaemon role='role-commit-packages' sender=':1.5257' Upgrade: openssh-client:amd64 (1:9.3p1-1ubuntu3.1, 1:9.3p1-1ubuntu3.2), gir1.2-udisks-2.0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), udisks2:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), libudisks2-0:amd64 (2.10.1-1ubuntu1, 2.10.1-1ubuntu1.1), gnome-shell-extension-desktop-icons-ng:amd64 (46+really47.0.5-1, 46+really47.0.7-0ubuntu1), libsqlite3-0:amd64 (3.42.0-1, 3.42.0-1ubuntu0.1), python3-distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), distro-info-data:amd64 (0.58ubuntu0.1, 0.58ubuntu0.2), distro-info:amd64 (1.5, 1.5ubuntu0.23.10.1), gnome-characters:amd64 (45.0-1, 45.0-1ubuntu1) DuplicateSignature: package:libsqlite3-0:3.42.0-1 Unpacking distro-info-data (0.58ubuntu0.2) over (0.58ubuntu0.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Pziscw/0-distro-info-data_0.58ubuntu0.2_all.deb (--unpack): unable to create '/usr/share/distro-info/debian.csv.dpkg-new' (while processing './usr/share/distro-info/debian.csv'): Read-only file system ErrorMessage: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system InstallationDate: Installed on 2023-10-18 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: sqlite3 Title: package libsqlite3-0 3.42.0-1 failed to install/upgrade: unable to create '/usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6.dpkg-new' (while processing './usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6'): Read-only file system UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/2048405/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
I'm not the original bug reporter, but thought the extra diagnostics may assist. -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722767/+files/ProcEnviron.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722766/+files/ProcCpuinfoMinimal.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722765/+files/PaInfo.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722764/+files/Dependencies.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722763/+files/CurrentDmesg.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722762/+files/AudioDevicesInUse.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2011385/+attachment/5722761/+files/AlsaInfo.txt -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.10 InstallationDate: Installed on 2023-04-04 (233 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-base 1.0.25+dfsg-0ubuntu7 PackageArchitecture: all ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RebootRequiredPkgs: Error: path contained symlinks. Tags: mantic Uname: Linux 6.5.0-10-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-10-24 (30 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2023 dmi.bios.release: 1.6 dmi.bios.vendor: Razer dmi.bios.version: 1.06 dmi.board.name: SO690 dmi.board.vendor: Razer dmi.board.version: 4 dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnRazer:bvr1.06:bd01/18/2023:br1.6:efr1.8:svnRazer:pnBlade16-RZ09-0483:pvr9.04:rvnRazer:rnSO690:rvr4:cvnRazer:ct10:cvr:skuRZ09-0483UWJ4: dmi.product.family: 1A583006 Razer Blade dmi.product.name: Blade 16 - RZ09-0483 dmi.product.sku: RZ09-0483UWJ4 dmi.product.version: 9.04 dmi.sys.vendor: Razer ** Tags added: apport-collected mantic -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: New Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Also affects: ubuntu-pro
Importance: Undecided
Status: New
** Changed in: ubuntu-pro
Assignee: (unassigned) => Tom Moyer (tom-tom)
** Also affects: ubuntu-pro/18.04
Importance: Undecided
Assignee: Tom Moyer (tom-tom)
Status: New
** Changed in: ubuntu-pro/18.04
Importance: Undecided => Medium
** Changed in: ubuntu-pro/18.04
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in Ubuntu Pro:
In Progress
Status in Ubuntu Pro 18.04 series:
In Progress
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
Incomplete
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Other Info]
All of these patches are included in upstream release 1.1.1b
- lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch
Fixes the shlibloadtest that was updated as part of #0005
- lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch
Patch adds the OPENSSL_INIT_NO_ATEXIT option
- lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch
Additional fixes for shlibloadtest
- lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch
Additional fixes for shlibloadtest
- lp1983100-0005-Test-atexit-handlers.patch
Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest
- lp1983100-0006-Introduce-a-no-pinshared-option.patch
This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not
defined then the atexit() handler is run
- lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch
This patch ensures that atexit() is only called when on non-Windows systems
as Windows uses _onexit() during library unloading
All seven patches are required to ensure the correct logic and
operation of the OPENSSL_INIT_NO_ATEXIT option.
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-pro/+bug/1983100/+subscription
[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on a Razer Blade 16 - other reports across the linux eco system: https://bbs.archlinux.org/viewtopic.php?id=285121 https://www.linuxquestions.org/questions/showthread.php?s=5778bfa3e63dcd856bc4b35c608837e9&p=6419132#post6419132 https://www.reddit.com/r/pop_os/comments/110vjt3/pop_on_razer_blade_18/ https://github.com/pop-os/linux/issues/246 ** Bug watch added: github.com/pop-os/linux/issues #246 https://github.com/pop-os/linux/issues/246 -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 1964763] Re: QtChooser doesn't support qt6
If you are using cmake you might get your builds to find the desired flavor by setting CMAKE_PREFIX_PATH to something like /usr/lib/x86_64-linux-gnu/cmake/Qt6 or /usr/lib/x86_64-linux-gnu/cmake/Qt5 either on the command line or by exporting that variable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 Status in qtchooser package in Ubuntu: Won't Fix Bug description: qtchooser doesn't run qt6 applications because it doesn't have a qt6.conf/6.conf file yet. In order to work, it must have two files `/usr/lib/x86_64-linux- gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux- gnu/qtchooser/6.conf` with this content: ``` /usr/lib/qt6/bin /usr/lib/x86_64-linux-gnu ``` Without it, lupdate, lrelease, and any other qt6 tools show this error: `could not find a Qt installation of ''` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+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 1952977] Re: Invalid security certificates everywhere in KDE
Linux putin 5.19.0-41-generic #42~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue
Apr 18 17:40:00 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
x11vnc --version
x11vnc: 0.9.16 lastmod: 2019-01-05
OpenSSL 3.0.2 15 Mar 2022 (Library: OpenSSL 3.0.2 15 Mar 2022)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1952977
Title:
Invalid security certificates everywhere in KDE
Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Bug description:
Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
errors like this https://imgur.com/a/7Kyt8U6
This causes problems for discover, downloading widgets, using the
weather widget, using the kde browser integrations, downloading tabs
for ksysguard, etc.
you can get console errors like this
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/chad/%25F")
adding empty sources model QStandardItemModel(0x5646c6ed2e80)
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl:
QSslSocket: cannot resolve SSL_get_peer_certificate
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libqt5network5 5.15.2+dfsg-14
Uname: Linux 5.15.5-051505-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Dec 1 21:43:08 2021
InstallationDate: Installed on 2021-11-26 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211126)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+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 1952977] Re: Invalid security certificates everywhere in KDE
Hello, I came here searching for a fix to what seems like the same
issue: using x11vnc between two Kubuntu machines and getting:
x11vnc[740]: 29/05/2023 21:58:53 SSL: accept_openssl: cookie from
ssl_helper[14222] FAILED. 0
However it is 2023 so maybe my issue is separate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1952977
Title:
Invalid security certificates everywhere in KDE
Status in qtbase-opensource-src package in Ubuntu:
Fix Released
Bug description:
Upgrading 5.15.2+dfsg-13 to 5.15.2+dfsg-14 results in security cert.
errors like this https://imgur.com/a/7Kyt8U6
This causes problems for discover, downloading widgets, using the
weather widget, using the kde browser integrations, downloading tabs
for ksysguard, etc.
you can get console errors like this
org.kde.plasma.discover: Trying to open unexisting file
QUrl("file:///home/chad/%25F")
adding empty sources model QStandardItemModel(0x5646c6ed2e80)
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
org.kde.plasma.libdiscover: Couldn't find a category for "fwupd-backend"
qt.network.ssl: QSslSocket: cannot resolve SSL_CTX_load_verify_dir
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5:
QML Binding: Binding loop detected for property "value"
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot call unresolved function
SSL_CTX_load_verify_dir
qt.network.ssl: An error encountered while to set root certificates location:
""
qt.network.ssl: QSslSocket: cannot resolve EVP_PKEY_base_id qt.network.ssl:
QSslSocket: cannot resolve SSL_get_peer_certificate
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libqt5network5 5.15.2+dfsg-14
Uname: Linux 5.15.5-051505-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Dec 1 21:43:08 2021
InstallationDate: Installed on 2021-11-26 (5 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64
(20211126)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1952977/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
This updated debdiff (openssl-atexit-v2.debdiff) includes the DEP-3
headers, cleans up the patch names by prepending lp1983100- to each
patch, and is rebased on the latest release in bionic-security.
** Description changed:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that does
not have support for the OPENSSL_NO_ATEXIT functionality from 1.1.1b
(openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background threads
are still running when exit() is called, which can cause SIGSEGV if a
background thread interacts with OpenSSL after/while it has unloaded.
For that reason, we always initialize OpenSSL 1.1.1 with the
OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only has no
effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published into
the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
+ [Other Info]
+ All of these patches are included in upstream release 1.1.1b
+ - lp1983100-0001-Fix-shlibloadtest-to-properly-execute-the-dso_ref-te.patch
+ Fixes the shlibloadtest that was updated as part of #0005
+
+ - lp1983100-0002-Implement-OPENSSL_INIT_NO_ATEXIT.patch
+ Patch adds the OPENSSL_INIT_NO_ATEXIT option
+
+ - lp1983100-0003-Don-t-link-shlibloadtest-against-libcrypto.patch
+ Additional fixes for shlibloadtest
+
+ - lp1983100-0004-Fix-rpath-related-Linux-test_shlibload-failure.patch
+ Additional fixes for shlibloadtest
+
+ - lp1983100-0005-Test-atexit-handlers.patch
+ Adds test for OPENSSL_INIT_NO_ATEXIT option and updates the shlibloadtest
+
+ - lp1983100-0006-Introduce-a-no-pinshared-option.patch
+ This patch includes tests to ensure that if OPENSSL_INIT_NO_ATEXIT is not
defined then the atexit() handler is run
+
+ - lp1983100-0007-Support-_onexit-in-preference-to-atexit-on-Windows.patch
+ This patch ensures that atexit() is only called when on non-Windows systems
as Windows uses _onexit() during library unloading
+
+ All seven patches are required to ensure the correct logic and operation
+ of the OPENSSL_INIT_NO_ATEXIT option.
+
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around various
initializations that were supposed to happen once when running threaded
but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
** Patch added: "openssl-atexit-v2.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/openssl/+bug/1983100/+attachment/5670692/+files/openssl-atexit-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
Incomplete
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have s
[Touch-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
This can be a dupe of bug 1970066 -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 1983100] Re: dotnet build intermittently crashes with segfault on Ubuntu 18.04
** Changed in: openssl (Ubuntu Bionic)
Assignee: Nicolas Bock (nicolasbock) => Tom Moyer (tom-tom)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1983100
Title:
dotnet build intermittently crashes with segfault on Ubuntu 18.04
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
Incomplete
Bug description:
[Impact]
Bionic's OpenSSL 1.1.1 package
(https://launchpad.net/ubuntu/bionic/+source/openssl) is the only
version of openssl 1.1.1 on any distro that we've encountered that
does not have support for the OPENSSL_NO_ATEXIT functionality from
1.1.1b (openssl/openssl@c2b3db2).
The threading model in .NET has the possibility that background
threads are still running when exit() is called, which can cause
SIGSEGV if a background thread interacts with OpenSSL after/while it
has unloaded. For that reason, we always initialize OpenSSL 1.1.1 with
the OPENSSL_NO_ATEXIT flag (which, of all the distros we run on only
has no effect on Bionic).
We feel that the stability of applications on Ubuntu 18.04 would be
improved if the functionality of OPENSSL_NO_ATEXIT was merged into the
bionic openssl 1.1.1 package, even if the constant isn't published
into the header for the dev package.
Context:
https://github.com/dotnet/runtime/issues/48411#issuecomment-1178405101
[Test Plan]
The described behavior can be reproduced by passing the
OPENSSL_NO_ATEXIT to the OPENSSL_init_ssl() call. The application will
terminate with a SEGFAULT. More concretely, a minimal reproducer is:
#include
#include
#include
#ifndef OPENSSL_INIT_NO_ATEXIT
#define OPENSSL_INIT_NO_ATEXIT 0x0008L
#endif
static void print_error_string()
{
printf("print_error_string:\n");
printf("ERR_reason_error_string(0) => %s\n", ERR_reason_error_string(0));
}
int main(int argc, char* argv[])
{
// register this handler first, so it runs last.
atexit(print_error_string);
OPENSSL_init_ssl(
OPENSSL_INIT_ADD_ALL_CIPHERS |
OPENSSL_INIT_ADD_ALL_DIGESTS |
OPENSSL_INIT_LOAD_CONFIG |
OPENSSL_INIT_NO_ATEXIT |
OPENSSL_INIT_LOAD_CRYPTO_STRINGS |
OPENSSL_INIT_LOAD_SSL_STRINGS,
NULL);
print_error_string();
return 0;
}
Building
$ sudo apt install libssl-dev
$ gcc test.c -lssl -lcrypto
$ ./a.out
print_error_string:
ERR_reason_error_string(0) => (null)
print_error_string:
Segmentation fault (core dumped)
[Where problems could occur]
The patches adds an option to the OPENSSL_init_crypto() function to
disable the default behavior of calling of a cleanup function on
application exit. The patch also includes a few bug fixes around
various initializations that were supposed to happen once when running
threaded but were not.
These changes have the potential for regressions and it is conceivable
that they lead to incorrect behavior. However, I have also backported
and included all new testing functions in the hope that the changed
behavior will get appropriate testing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1983100/+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 2007050] Re: Microsoft Surface keyboard not available during initrd
Thanks to oerheks for pointing me to a related (though AMD there) report at https://github.com/linux-surface/linux-surface/issues/839#issuecomment-1140287888 Placing the following in /etc/initramfs-tools/modules #-- Starts here -- surface_hid_core surface_hid surface_aggregator_registry surface_aggregator pinctrl_tigerlake 8250_dw #-- Ends here -- then running sudo update-initramfs -c -k $(uname -r) and finally rebooting works around it for me. It appears that whatever detects the modules to be included in the (default) "MOST" set when generating an initrd will need updating. (It may be possible to reduce the above list of modules to specifically include in the initrd can be reduced, yet - let me know if you want me to work this out.) ** Bug watch added: github.com/linux-surface/linux-surface/issues #839 https://github.com/linux-surface/linux-surface/issues/839 ** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Summary changed: - Microsoft Surface keyboard not available during initrd + Check for Microsoft Surface keyboard modules when generating initrd -- 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/2007050 Title: Check for Microsoft Surface keyboard modules when generating initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: With 22.04 LTS, fully updated, freshly built initrd's for both 5.15 (linux-generic-hwe-22.04) and 5.19 (linux-generic-hwe-22.04-edge) kernels, the embedded keyboard of a Microsoft Surface 4 Laptop model 1950 (Intel Gen 11), namely "Microsoft Surface 045E:09AE Keyboard", is not available during early boot, such as for entering a full disk encryption passphrase. Just pressing enter at said prompt has no effect. Connecting an external keyboard via USB and typing the passphrase from there works around it. The keyboard works fine on the fully booted system. Secure boot is disabled on this system. -- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 13 00:53:34 2023 Dependencies: adduser 3.118ubuntu5 apt 2.4.8 apt-utils 2.4.8 busybox-initramfs 1:1.30.1-7ubuntu3 ca-certificates 20211016ubuntu0.22.04.1 coreutils 8.32-4.1ubuntu1 cpio 2.13+dfsg-7 debconf 1.5.79ubuntu1 debconf-i18n 1.5.79ubuntu1 dmsetup 2:1.02.175-2.1ubuntu4 dpkg 1.21.1ubuntu2.1 gcc-12-base 12.1.0-2ubuntu1~22.04 gettext-base 0.21-4ubuntu4 gpgv 2.2.27-3ubuntu2.1 grub-common 2.06-2ubuntu7.1 grub-gfxpayload-lists 0.7 grub-pc 2.06-2ubuntu7.1 grub-pc-bin 2.06-2ubuntu7.1 grub2-common 2.06-2ubuntu7.1 init-system-helpers 1.62 initramfs-tools 0.140ubuntu13.1 initramfs-tools-bin 0.140ubuntu13.1 initramfs-tools-core 0.140ubuntu13.1 klibc-utils 2.0.10-4 kmod 29-1ubuntu1 libacl1 2.3.1-1 libapt-pkg6.0 2.4.8 libattr1 1:2.5.1-1build1 libaudit-common 1:3.0.7-1build1 libaudit1 1:3.0.7-1build1 libblkid1 2.37.2-4ubuntu3 libbrotli1 1.0.9-2build6 libbz2-1.0 1.0.8-5build1 libc6 2.35-0ubuntu3.1 libcap-ng0 0.7.9-2.2build3 libcap2 1:2.44-1build3 libcom-err2 1.46.5-2ubuntu1.1 libcrypt1 1:4.4.27-1 libdb5.3 5.3.28+dfsg1-0.8ubuntu3 libdevmapper1.02.1 2:1.02.175-2.1ubuntu4 libefiboot1 37-6ubuntu2 libefivar1 37-6ubuntu2 libffi8 3.4.2-4 libfreetype6 2.11.1+dfsg-1ubuntu0.1 libfuse3-3 3.10.5-1build1 libgcc-s1 12.1.0-2ubuntu1~22.04 libgcrypt20 1.9.4-3ubuntu3 libgmp10 2:6.2.1+dfsg-3ubuntu1 libgnutls30 3.7.3-4ubuntu1.1 libgpg-error0 1.43-3 libgssapi-krb5-2 1.19.2-2ubuntu0.1 libhogweed6 3.7.3-1build2 libidn2-0 2.3.2-2build1 libk5crypto3 1.19.2-2ubuntu0.1 libkeyutils1 1.6.1-2ubuntu3 libklibc 2.0.10-4 libkmod2 29-1ubuntu1 libkrb5-3 1.19.2-2ubuntu0.1 libkrb5support0 1.19.2-2ubuntu0.1 liblocale-gettext-perl 1.07-4build3 liblz4-1 1.9.3-2build2 liblzma5 5.2.5-2ubuntu1 libmount1 2.37.2-4ubuntu3 libnettle8 3.7.3-1build2 libnsl2 1.3.0-2build2 libp11-kit0 0.24.0-6build1 libpam-modules 1.4.0-11ubuntu2.3 libpam-modules-bin 1.4.0-11ubuntu2.3 libpam0g 1.4.0-11ubuntu2.3 libpcre2-8-0 10.39-3ubuntu0.1 libpng16-16 1.6.37-3build5 libseccomp2 2.5.3-2ubuntu2 libselinux1 3.3-1build2 libsemanage-common 3.3-1build2 libsemanage2 3.3-1build2 libsepol2 3.3-1build1 libsmartcols1 2.37.2-4ubuntu3 libssl3 3.0.2-0ubuntu1.8 libstdc++6 12.1.0-2ubuntu1~22.04 libsystemd0 249.11-0ubuntu3.6 libtasn1-6 4.18.0-4build1 libtext-charwidth-perl 0.04-10build3 libtext-iconv-perl 1.7-7build3 libtext-wrapi18n-perl 0.06-9 libtinfo6 6.3-2 libtirpc-common 1.3.2-2ubuntu0.1 libtirpc3 1.3.2-2ubuntu0.1 libudev1 249.11-0ubuntu3.6 libunistring2 1.0-1 libuuid1 2.37.2-4ubuntu3 libxxhash0 0.8.1-1 libzstd1 1.4.8+dfsg-3build1 linux
[Touch-packages] [Bug 2003703] [NEW] package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: I have tried to fix but to no avail. Please send fix to electron_...@protonmail.com ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxcb-record0:amd64 1.14-3ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: python3-setuptools:amd64: Install python3-pkg-resources:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Jan 23 06:19:00 2023 DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DuplicateSignature: package:libxcb-record0:amd64:1.14-3ubuntu3 Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ... dpkg: error processing package libxcb-record0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0505] InstallationDate: Installed on 2022-09-16 (128 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron N5040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=d2132e07-1c79-4672-8cc8-f180b680d7ba ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libxcb Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to jammy on 2022-12-30 (23 days ago) dmi.bios.date: 08/22/2011 dmi.bios.release: 254.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0THYJV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.ec.firmware.release: 254.3 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/22/2011:br254.3:efr254.3:svnDellInc.:pnInspironN5040:pvrA03:rvnDellInc.:rn0THYJV:rvrA03:cvnDellInc.:ct8:cvrA03:skuTobefilledbyO.E.M.: dmi.product.name: Inspiron N5040 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A03 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/2003703 Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxcb package in Ubuntu: New Bug description: I have tried to fix but to no avail. Please send fix to electron_...@protonmail.com ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxcb-record0:amd64 1.14-3ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: python3-setuptools:amd64: Install python3-pkg-resources:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Jan 23 06:19:00 2023 DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DuplicateSignature: package:libxcb-record0:amd64:1.14-3ubuntu3 Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ... dpkg: error processing package libxcb-record0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphic
[Touch-packages] [Bug 2003703] Re: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
Thank you, in advance, for your line by line assistance in helping me. electron_...@protonmail.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/2003703 Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxcb package in Ubuntu: New Bug description: I have tried to fix but to no avail. Please send fix to electron_...@protonmail.com ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libxcb-record0:amd64 1.14-3ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 AptOrdering: python3-setuptools:amd64: Install python3-pkg-resources:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Mon Jan 23 06:19:00 2023 DistUpgraded: 2022-12-30 12:11:30,358 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DuplicateSignature: package:libxcb-record0:amd64:1.14-3ubuntu3 Setting up python3-setuptools (59.6.0-1.2ubuntu0.22.04.1) ... dpkg: error processing package libxcb-record0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0505] InstallationDate: Installed on 2022-09-16 (128 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Inspiron N5040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=d2132e07-1c79-4672-8cc8-f180b680d7ba ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: libxcb Title: package libxcb-record0:amd64 1.14-3ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to jammy on 2022-12-30 (23 days ago) dmi.bios.date: 08/22/2011 dmi.bios.release: 254.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0THYJV dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.ec.firmware.release: 254.3 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/22/2011:br254.3:efr254.3:svnDellInc.:pnInspironN5040:pvrA03:rvnDellInc.:rn0THYJV:rvrA03:cvnDellInc.:ct8:cvrA03:skuTobefilledbyO.E.M.: dmi.product.name: Inspiron N5040 dmi.product.sku: To be filled by O.E.M. dmi.product.version: A03 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/2003703/+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 1780985] Re: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content
$ apport-unpack _usr_bin_gjs-console.1000.crash Guest79 Traceback (most recent call last): File "/usr/bin/apport-unpack", line 74, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['separator'] has no binary content ... is what brought me here. This is the kind of bug I do not understand why it does not get higher priority. It is a - seemingly easy to fix - bug in a core Ubuntu utility, which is relevant for bug reporting and analysis, thus a tool with a potential to improve the distributions' quality on a relevant scale. It would seem like it should be of central interest to Canonical that these tools receive much development attention and are of high quality. To the contrary, apport is in a sad state (see its bug tracker), and has been for a decade, and unless it gets serious quality time, it seems wrong to continue to waste massive (scale) CPU cycles and prompt users about (not) reporting crashes and bugs at all. Sorry for using this bug tracker as a means of providing generic software quality feedback - I know I should not, but I also know other places would not get developer attention, or feedback would be treated more in a PR (and I do not mean pull request) way, while here, there is at least a bit of a chance for quality feedback. -- 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/1780985 Title: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content Status in apport package in Ubuntu: Confirmed Bug description: Sometimes apport creates a crash file with an empty field for 'ProcEnviron'. In that situation, I want to be able to continue extracting fields from the crash file rather than aborting. Workaround is to add some made up values for ProcEnviron in the crash file, such as " LANG=en_US.UTF-8 ". ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportLog: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jul 10 08:02:35 2018 ExecutablePath: /usr/bin/apport-unpack InstallationDate: Installed on 2018-04-27 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-unpack /var/crash/_usr_bin_kdeinit5.1000.crash crash_files/ Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonArgs: ['/usr/bin/apport-unpack', '/var/crash/_usr_bin_kdeinit5.1000.crash', 'crash_files/'] PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: apport Title: apport-unpack crashed with ValueError in extract_keys(): ['ProcEnviron'] has no binary content UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio bluetooth cdrom dialout dip floppy lpadmin netdev plugdev sambashare scanner sudo systemd-journal tty vboxusers video wireshark modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-05-18T07:41:41.681859 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780985/+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 1986936] Re: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages
This may be the wrong place to confirm this, and I don't know what package the link libQt5Core.so is supposed to be a part of, but I can confirm that this particular symlink was missing immediately after upgrading to 22.04 from 20.04. No others were missing on my system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1986936 Title: No libQt5Core.so, libQt5Widgets.so and libQt5Gui.so symlinks in the corresponding :i386 packages Status in qtbase-opensource-src package in Ubuntu: New Bug description: While trying to link against corresponding libraries to get i386 executable like that: > g++ -m32 -o filename . -lQt5Widgets -lQt5Gui -lQt5Core ... I get the following errors: > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: cannot find -lQt5Widgets: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Widgets.so when searching for -lQt5Widgets > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: cannot find -lQt5Gui: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Gui.so when searching for -lQt5Gui > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core > /usr/bin/ld: cannot find -lQt5Core: No such file or directory > /usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libQt5Core.so when searching for -lQt5Core despite corresponging packages are installed (libqt5gui5:i386 and same for widgets and core). Inspection of /usr/lib/i386-linux-gnu/ reveals that there is no symlinks named exactly libQt5Core.so (and same for two other libs). Adding those symlinks by hand completely solves the problem. I believe however that those symlinks must be installed by corresponding .debs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1986936/+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 1983046] [NEW] Incorrect username for systemd-journal-upload.service
Public bug reported: Starting the systemd-journal-upload service fails. The username specified in the Ubuntu systemd-journal-upload.service does not exist after the systemd-journal-remote package is installed. Ubuntu systemd-journal-upload.service: User=systemd-journal-upload Corrent systemd-journal-upload.service: User=systemd-journal-remote ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-journal-remote 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 28 17:44:06 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to jammy on 2022-07-28 (0 days ago) modified.conffile..etc.systemd.journal-upload.conf: [modified] mtime.conffile..etc.systemd.journal-upload.conf: 2022-07-28T07:02:44.608776 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1983046 Title: Incorrect username for systemd-journal-upload.service Status in systemd package in Ubuntu: New Bug description: Starting the systemd-journal-upload service fails. The username specified in the Ubuntu systemd-journal-upload.service does not exist after the systemd-journal-remote package is installed. Ubuntu systemd-journal-upload.service: User=systemd-journal-upload Corrent systemd-journal-upload.service: User=systemd-journal-remote ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd-journal-remote 249.11-0ubuntu3.4 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 28 17:44:06 2022 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to jammy on 2022-07-28 (0 days ago) modified.conffile..etc.systemd.journal-upload.conf: [modified] mtime.conffile..etc.systemd.journal-upload.conf: 2022-07-28T07:02:44.608776 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1983046/+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 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon
It may be fixed for kinetic but it's still very much not fixed for jammy! That still has the broken 1.7.5 release... -- 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/1969976 Title: DynamicUser=1 doesn't get along with services that need dbus-daemon Status in Fwupd: Fix Released Status in systemd: New Status in fwupd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in fwupd source package in Focal: Confirmed Status in systemd source package in Focal: Won't Fix Status in fwupd source package in Impish: Confirmed Status in systemd source package in Impish: Won't Fix Status in fwupd source package in Jammy: Confirmed Status in systemd source package in Jammy: Won't Fix Bug description: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an upstream issue introduced by stable systemd. https://github.com/systemd/systemd/issues/22737 The problem also occurs in Ubuntu 22.04 with a newer systemd release. As discussed in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61 it's a tradeoff of issues. So within Ubuntu something probably needs to be done about fwupd-refresh.service. One proposal is to remove DynamicUser=yes from the systemd unit, but this will mean fwupdgmr refresh runs as root. It's relatively sandboxed by other security mechanisms, but still not ideal. Could we repurpose any other service account? Or alternatively we can make a new fwupd service account that this systemd unit uses. To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1969976/+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 1978428] [NEW] PCI/internal sound card not detected ALC4080 ASUS Z690 MB
Public bug reported: I have a fresh install of Ubuntu 22.04 Jammy on my ASUS Z690 motherboard with an intel i7 12700K. Ever since the fresh install I am unable to have any sound play through the rear or front audio jacks. I believe it is a problem with ubuntu not being able to recognize the sound card on the MB since this hardware seems to be very very new. It also seems that snd-hda-intel is unable to find any codecs for the sound card or even identify the onboard sound card. Here is the output of dmesg | grep 'snd': [5.426209] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [5.426494] snd_hda_intel :01:00.1: enabling device ( -> 0002) [5.426528] snd_hda_intel :01:00.1: Disabling MSI [5.426531] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.438789] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f [7.446910] snd_hda_intel :00:1f.3: No response from codec, disabling MSI: last cmd=0x000f [8.458944] snd_hda_intel :00:1f.3: Codec #0 probe error; disabling it... [9.470934] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f [9.471592] snd_hda_intel :00:1f.3: no codecs initialized [9.711743] usbcore: registered new interface driver snd-usb-audio I then tried updating the kernel to 5.18.2 but that was to no luck and the issue still persists. It seems alsa is not able to identify the card. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 5.18.2-051802-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 12 19:32:33 2022 InstallationDate: Installed on 2022-05-28 (15 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/10/2021 dmi.bios.release: 7.7 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0707 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z690-A GAMING WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0707:bd11/10/2021:br7.7:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-AGAMINGWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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: ASUS mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-12T19:13:55.032469 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/1978428 Title: PCI/internal sound card not detected ALC4080 ASUS Z690 MB Status in alsa-driver package in Ubuntu: New Bug description: I have a fresh install of Ubuntu 22.04 Jammy on my ASUS Z690 motherboard with an intel i7 12700K. Ever since the fresh install I am unable to have any sound play through the rear or front audio jacks. I believe it is a problem with ubuntu not being able to recognize the sound card on the MB since this hardware seems to be very very new. It also seems that snd-hda-intel is unable to find any codecs for the sound card or even identify the onboard sound card. Here is the output of dmesg | grep 'snd': [5.426209] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [5.426494] snd_hda_intel :01:00.1: enabling device ( -> 0002) [5.426528] snd_hda_intel :01:00.1: Disabling MSI [5.426531] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [6.438789] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x000f [7.446910] snd_hda_intel :00:1f.3: No response from codec, disabling MSI: last cmd=0x000f [8.458944] snd_hda_intel :00:1f.3: Codec #0 probe error; disabling it... [9.470934] snd_hda_intel :00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x000f [9.471592] snd_hda_intel :00:1f.3: no codecs initialized [9.711743] usbcore: registered new interface driver snd-usb-audio I then tried updating the kernel to 5.18.2 but that was to no luck and the issue still persists. It seems alsa is
[Touch-packages] [Bug 1971492] [NEW] package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt
Public bug reported: Nothing obviously wrong that I could tell ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: rfkill:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 3 06:05:52 2022 DpkgHistoryLog: Start-Date: 2022-05-03 06:05:50 Commandline: /usr/bin/unattended-upgrade Upgrade: rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2018-12-10 (1239 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2021-12-15 (139 days ago) mtime.conffile..etc.pam.d.lightdm: 2018-12-10T13:15:57.713002 ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1971492 Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt Status in lightdm package in Ubuntu: New Bug description: Nothing obviously wrong that I could tell ProblemType: Package DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 AptOrdering: rfkill:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 3 06:05:52 2022 DpkgHistoryLog: Start-Date: 2022-05-03 06:05:50 Commandline: /usr/bin/unattended-upgrade Upgrade: rfkill:amd64 (2.34-0.1ubuntu9.1, 2.34-0.1ubuntu9.3) ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2018-12-10 (1239 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: lightdm Title: package lightdm 1.30.0-0ubuntu4~20.04.2 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to focal on 2021-12-15 (139 days ago) mtime.conffile..etc.pam.d.lightdm: 2018-12-10T13:15:57.713002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1971492/+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 1964763] Re: QtChooser doesn't support qt6
This is a debdiff for qtchooser applicable to qtchooser_66-2build1. I built this in pbuilder and it builds successfully, and I installed it, the patch works as intended. ** Patch added: "1-qtchooser_66-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+attachment/5585108/+files/1-qtchooser_66-2ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1964763 Title: QtChooser doesn't support qt6 Status in qtchooser package in Ubuntu: Confirmed Bug description: qtchooser doesn't run qt6 applications because it doesn't have a qt6.conf/6.conf file yet. In order to work, it must have two files `/usr/lib/x86_64-linux- gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux- gnu/qtchooser/6.conf` with this content: ``` /usr/lib/qt6/bin /usr/lib/x86_64-linux-gnu ``` Without it, lupdate, lrelease, and any other qt6 tools show this error: `could not find a Qt installation of ''` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+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 1964741] [NEW] date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59
Public bug reported: When calculating a timestamp for a time between 02:00 and 02:59 in some locales, date will report "invalid date". This only occurs if the system time is currently during the day that standard time transitions to daylight time. Example: OS Version information: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal System Locale is: America/Chicago System time the command was issued: Sun 13 Mar 2022 10:15:18 PM CDT Command issued: date +%s -d 'tomorrow 02:50' System Response: date: invalid date 'tomorrow 02:50' If the command issued is changed such that the calculated time is anything other than a time between 02:00 and 02:59 the output is normal. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1964741 Title: date command produces "invalid date" on day of DST change when calculating a time between 02:00 and 02:59 Status in coreutils package in Ubuntu: New Bug description: When calculating a timestamp for a time between 02:00 and 02:59 in some locales, date will report "invalid date". This only occurs if the system time is currently during the day that standard time transitions to daylight time. Example: OS Version information: Distributor ID: Ubuntu Description:Ubuntu 20.04.4 LTS Release:20.04 Codename: focal System Locale is: America/Chicago System time the command was issued: Sun 13 Mar 2022 10:15:18 PM CDT Command issued: date +%s -d 'tomorrow 02:50' System Response: date: invalid date 'tomorrow 02:50' If the command issued is changed such that the calculated time is anything other than a time between 02:00 and 02:59 the output is normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1964741/+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 1960544] Re: External Monitors Not Detected Anymore
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] Re: External Monitors Not Detected Anymore
You are right, updating the kernel did solve the problem. Thanks a lot for your swift answer! -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: Invalid Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1960544] [NEW] External Monitors Not Detected Anymore
Public bug reported: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Description changed: - Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the - update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, - libglapi, libdrm etc.), external monitors (here connected via DELL USB - Dock) are not detected anymore. I had to restore the old version with - Timeshift. + On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm + etc.), external monitors (here connected via DELL USB Dock) are not + detected anymore. I had to restore the old version with Timeshift. ** Description changed: - On Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of + On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of - mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm - etc.), external monitors (here connected via DELL USB Dock) are not - detected anymore. I had to restore the old version with Timeshift. + mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), + external monitors (here connected via DELL USB Dock) are not detected + anymore. I had to restore the old version with Timeshift. ** Description changed: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), - external monitors (here connected via DELL USB Dock) are not detected + external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- 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/1960544 Title: External Monitors Not Detected Anymore Status in mesa package in Ubuntu: New Bug description: On Ubuntu 20.04 on a DELL XPS13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl*, libdrm* etc.), external displays (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1960544/+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 1692302] Re: Can't connect on external monitor or projector
Same here with Ubuntu 20.04 on a DELL XPS 13 (with i915 Chip): after the update of mesa-vulkan-drivers from 21.0.3 to 21.2.6 (incl. libgl, libglapi, libdrm etc.), external monitors (here connected via DELL USB Dock) are not detected anymore. I had to restore the old version with Timeshift. -- 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/1692302 Title: Can't connect on external monitor or projector Status in mesa package in Ubuntu: New Bug description: after update the mesa driver, my notebook (HP af118au AMD a8-7410 radeon R5) can't connect on projector or external monitor, but this update make some game can running more smooth and playable, I hope this problem can fix immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1692302/+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 1955985] Re: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same"
patched with version openssh-client version 8.7p1-4 ** Changed in: openssh (Ubuntu) Status: Confirmed => Fix Released -- 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/1955985 Title: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same" Status in openssh package in Ubuntu: Fix Released Bug description: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 openssh-client (1:8.7p1-3) I expected it to install normally. The installation crashed. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1955985/+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 1955985] Re: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same"
also having this issue Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same Use 'update-alternatives --help' for program usage information. dpkg: error processing package openssh-client (--configure): installed openssh-client package post-installation script subprocess returned e rror exit status 2 -- 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/1955985 Title: installation crashes with error "Setting up openssh-client (1:8.7p1-3) ... update-alternatives: and can't be the same" Status in openssh package in Ubuntu: Confirmed Bug description: Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 openssh-client (1:8.7p1-3) I expected it to install normally. The installation crashed. E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1955985/+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 1934933] [NEW] cloud-init dhclient apparmor denied with noexec on /var/tmp
Public bug reported:
Hello - we are seeing an issue on multiple Azure hosts where there is a
long delay during bootup. This appears to be related to an apparmor
issue with dhclient executed via cloud-init when /var is mounted noexec.
Because /var is noexec, the original dhclient is executed rather than
the copy in /var/tmp/cloud-init, which causes the AppArmor profile to be
applied.
This prevents the instance from being able to record the DHCP lease
information to /var/tmp/cloud-init/cloud-init-dhcp-*, which prevents the
instance from being able to obtain goalstate information, and with
cloud-init 21.2-3 or later, results in an extended delay during boot due
to a recent change in azure.py (https://github.com/canonical/cloud-
init/pull/842).
This issue does not occur in default Ubuntu installations (including the
Ubuntu 20.04 default Azure image), as the dhcp.py script in cloud-init
behaves differently, copying /usr/sbin/dhclient to /var/tmp/cloud-init
/cloud-init-dhcp-x/dhclient when /var allows executables, and the
apparmor profiles then do not apply to the copied executable.
The syslog will show the following entry when the instance boots up:
cloud-init[820]: 2021-07-07 14:50:40,661 - dhcp.py[WARNING]: dhclient did not
produce expected files: dhcp.leases, dhclient.pid
The cloud-init.log file will show this entry when this issue is occurring.
Since the instance has no IP address at this stage of the boot process, an
unreachable network is to be expected:
azure.py[DEBUG]: Failed HTTP request with Azure endpoint
http://168.63.129.16/machine/?comp=goalstate during attempt 240 with exception:
HTTPConnectionPool(host='168.63.129.16', port=80): Max retries exceeded with
url: /machine/?comp=goalstate (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is
unreachable'))
With the timeouts in azure.py described above, the instance will not
boot for around 20 minutes until all 240 connection attempts are
completed.
This is logged in /var/log/audit/audit.log, showing that the dhclient process
executed from cloud-init is unable to write the dhclient.pid and dhcp.leases
files that are needed to continue the datasource retrieval process:
type=AVC msg=audit(1625678140.496:1898): apparmor="DENIED" operation="open"
profile="/{,usr/}sbin/dhclient" name="/proc/8537/task/8540/comm" pid=8537
comm="dhclient" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Adding the following file resolves the issue:
/etc/apparmor.d/local/sbin.dhclient
/var/tmp/cloud-init/cloud-init-dhcp-*/dhclient.pid lrw,
/var/tmp/cloud-init/cloud-init-dhcp-*/dhcp.leases lrw,
This allows dhclient executed via cloud-init to write the dhclient.pid
and dhcp.leases files to /var/tmp/cloud-init and the instance to boot
normally.
** Affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1934933
Title:
cloud-init dhclient apparmor denied with noexec on /var/tmp
Status in isc-dhcp package in Ubuntu:
New
Bug description:
Hello - we are seeing an issue on multiple Azure hosts where there is
a long delay during bootup. This appears to be related to an apparmor
issue with dhclient executed via cloud-init when /var is mounted
noexec. Because /var is noexec, the original dhclient is executed
rather than the copy in /var/tmp/cloud-init, which causes the AppArmor
profile to be applied.
This prevents the instance from being able to record the DHCP lease
information to /var/tmp/cloud-init/cloud-init-dhcp-*, which prevents
the instance from being able to obtain goalstate information, and with
cloud-init 21.2-3 or later, results in an extended delay during boot
due to a recent change in azure.py (https://github.com/canonical
/cloud-init/pull/842).
This issue does not occur in default Ubuntu installations (including
the Ubuntu 20.04 default Azure image), as the dhcp.py script in cloud-
init behaves differently, copying /usr/sbin/dhclient to /var/tmp
/cloud-init/cloud-init-dhcp-x/dhclient when /var allows
executables, and the apparmor profiles then do not apply to the copied
executable.
The syslog will show the following entry when the instance boots up:
cloud-init[820]: 2021-07-07 14:50:40,661 - dhcp.py[WARNING]: dhclient did not
produce expected files: dhcp.leases, dhclient.pid
The cloud-init.log file will show this entry when this issue is occurring.
Since the instance has no IP address at this stage of the boot process, an
unreachable network is to be expected:
azure.py[DEBUG]: Failed HTTP request with Azure endpoint
http://168.63.129.16/machine/?comp=goalstate during attempt 240 with exception:
HTTPConnectionPool(host='168.63.129.16', port=80): Max retries exceeded with
url: /machine/?comp=goalstate (Caused by
NewConnectionError(': Failed to establ
[Touch-packages] [Bug 1933531] [NEW] mv command deleted source file without moving to destination
Public bug reported: I mv'd a file to a directory where I had group write permissions, but a file existed owned by another user. I was asked if I wanted to override the permissions. I said "y". The ownership was changed on the destination file to me, but the mod time and contents of the file were not changed and the source file was deleted. I tried to duplicate the behavior, but it worked as it should with a test file. toma@admn1:~$ ls -ld /opt/scripts drwxrwxr-- 3 ansible ansible 4096 Jun 24 16:25 /opt/scripts toma@admn1:~$ mv GeneratePortList.pl /opt/scripts/ mv: replace '/opt/scripts/GeneratePortList.pl', overriding mode 0755 (rwxr-xr-x)? y toma@admn1:~$ ls -l /opt/scripts/GeneratePortList.pl -rwxr-xr-x 1 toma domain users 2855 Jul 16 2018 /opt/scripts/GeneratePortList.pl I have mv aliased to mv -i so I can confirm that the existing destination file was not owned by me since I was not prompted to overwrite the file. Both source and destination are in the same file system. I cannot find the source file anywhere. toma@admn1:~$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 toma@admn1:~$ uname -a Linux admn1.aaisdirect.com 5.4.0-1048-aws #50-Ubuntu SMP Mon May 3 21:44:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux toma@admn1:~$ apt-cache policy coreutils coreutils: Installed: 8.30-3ubuntu2 Candidate: 8.30-3ubuntu2 Version table: *** 8.30-3ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 8.28-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1933531 Title: mv command deleted source file without moving to destination Status in coreutils package in Ubuntu: New Bug description: I mv'd a file to a directory where I had group write permissions, but a file existed owned by another user. I was asked if I wanted to override the permissions. I said "y". The ownership was changed on the destination file to me, but the mod time and contents of the file were not changed and the source file was deleted. I tried to duplicate the behavior, but it worked as it should with a test file. toma@admn1:~$ ls -ld /opt/scripts drwxrwxr-- 3 ansible ansible 4096 Jun 24 16:25 /opt/scripts toma@admn1:~$ mv GeneratePortList.pl /opt/scripts/ mv: replace '/opt/scripts/GeneratePortList.pl', overriding mode 0755 (rwxr-xr-x)? y toma@admn1:~$ ls -l /opt/scripts/GeneratePortList.pl -rwxr-xr-x 1 toma domain users 2855 Jul 16 2018 /opt/scripts/GeneratePortList.pl I have mv aliased to mv -i so I can confirm that the existing destination file was not owned by me since I was not prompted to overwrite the file. Both source and destination are in the same file system. I cannot find the source file anywhere. toma@admn1:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 toma@admn1:~$ uname -a Linux admn1.aaisdirect.com 5.4.0-1048-aws #50-Ubuntu SMP Mon May 3 21:44:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux toma@admn1:~$ apt-cache policy coreutils coreutils: Installed: 8.30-3ubuntu2 Candidate: 8.30-3ubuntu2 Version table: *** 8.30-3ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 8.28-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1933531/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
For gnome-control-center, this bug report was watching https://bugzilla.gnome.org/show_bug.cgi?id=692666 so far. While still relevant, the Gnome Project has stopped using this bug tracker and has since shifted to their Gitlab instance for bug tracking. A closely related upstream bug report, which should have higher relevance for Ubuntu (after shifting to XWayland), is https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1016, so I've updated the remote watch for gnome-control-center. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1016 ** Changed in: gnome-control-center Importance: Medium => Unknown ** Changed in: gnome-control-center Remote watch: bugzilla.gnome.org/ #692666 => gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1016 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed Status in gnome-control-center: Unknown Status in GTK+: New Status in Mir: Fix Released Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Won't Fix Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1903890] Re: libffi7 missing from Ubuntu (pip's python3-openssl appears to be built against the wrong version of libffi)
I've confirmed that my use case (the original report of this ticket) is
resolved in 21.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1903890
Title:
libffi7 missing from Ubuntu (pip's python3-openssl appears to be built
against the wrong version of libffi)
Status in libffi package in Ubuntu:
Fix Released
Status in pyopenssl package in Ubuntu:
Incomplete
Status in libffi source package in Groovy:
Incomplete
Status in pyopenssl source package in Groovy:
Incomplete
Bug description:
Ubuntu groovy and up upgraded to libffi8ubuntu1, thus making Ubuntu
incompatible with 3rd-party binaries that desire to use libffi7.
Let's backport and provide libffi7 runtime library only, for those.
Not sure how that would work with ctypes though.
---
I've just upgraded to Ubuntu 20.10 which comes with python3-openssl
version 19.0.1-2. It breaks (at least some) Python applications that
use the `requests` library to access HTTPS URLS. For instance, this
stack trace (note that I have clipped the first few frames from the
stack as they are proprietary):
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py",
line 76, in get
return request('get', url, params=params, **kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py",
line 61, in request
return session.request(method=method, url=url, **kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line
530, in request
resp = self.send(prep, **send_kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py", line
643, in send
r = adapter.send(request, **kwargs)
File
"/home/tkcook/.local/lib/python3.8/site-packages/requests/adapters.py", line
439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 670,
in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 381,
in _make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 978,
in _validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 342, in
connect
self.ssl_context = create_urllib3_context(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 289, in
create_urllib3_context
context.verify_mode = cert_reqs
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line
438, in verify_mode
self._ctx.set_verify(_stdlib_to_openssl_verify[value], _verify_callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 1119, in
set_verify
self._verify_helper = _VerifyHelper(callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 337, in __init__
self.callback = _ffi.callback(
SystemError: ffi_prep_closure(): bad user_data (it seems that the version of
the libffi library seen at runtime is different from the 'ffi.h' file seen at
compile-time)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1903890/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
I have the same issue. On 20.04, pulse audio creates of the HDMI/DP device on wake after sleep, and starts using it even though I previously configured the earlier copy of itself to "Off" using pavucontrol. This is particularly annoying because it the device is built into my monitor, is crappy, and there is no way to physically turn off the device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake
I have the same issue. On 20.04, pulse audio creates of the HDMI/DP device on wake after sleep, and starts using it even though I previously configured the earlier copy of itself to "Off" using pavucontrol. This is particularly annoying because it the device is built into my monitor, is crappy, and there is no way to physically turn off the device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1888598 Title: Pulseaudio breaks HDMI audio on sleep/wake Status in pulseaudio package in Ubuntu: Confirmed Bug description: on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs with pulseaudio after putting my system to sleep and then waking it up. these bugs aren't present on a fresh boot, only after resuming from sleep: - it forgets which sound output device it's set to, and always reverse to the motherboard's S/PDIF output. - I have two devices connected to my video card, one is a displayport monitor, and one is a home theater receiver via HDMI. it confuses the two, and randomly switches which device it thinks is capable of surround sound. - it sometimes refuses to switch to the correct audio device, and just resets any choice back to the internal S/PDIF, until the system is rebooted. as you can imagine, this a pretty frustrating state of affairs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 3387 F pulseaudio /dev/snd/pcmC1D7p: tessa 3387 F...m pulseaudio /dev/snd/controlC2: tessa 3387 F pulseaudio /dev/snd/controlC0: tessa 3387 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 22 18:38:42 2020 InstallationDate: Installed on 2020-07-15 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902109]
Also rsync in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=1894485
--
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/1902109
Title:
rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
Status in GLibC:
Confirmed
Status in glibc package in Ubuntu:
New
Status in rsync package in Ubuntu:
Triaged
Bug description:
Rsync in Ubuntu 20.10 fails when /proc isn't mounted, while it worked before.
This happens because AC_CHECK_FUNC(lchmod) returns "yes" in 20.10, while it
returned "no" before.
Steps to reproduce:
# Emulate /proc not being mounted
$ mount --bind / /mnt
$ chroot /mnt rsync -a /bin/ls .
rsync: [receiver] failed to set permissions on "/.ls.CDExhu": Operation not
supported (95)
rsync error: some files/attrs were not transferred (see previous errors)
(code 3) at main.c(1330) [sender=3.2.3]
I reported this issue upstream in
https://github.com/WayneD/rsync/issues/109 but the rsync developer
says it's a problem in libc, and it might well be.
Simple C code to reproduce the problem without rsync:
printf("lchmod returned: %d\n", lchmod("/tmp/ls", 0755));
If /tmp/ls is e.g. mode=0123, and needs to be changed, lchmod fails
when /proc isn't mounted, yet it succeeds if it is mounted.
Python had a similar issue, and they ended up avoiding
AC_CHECK_FUNC(lchmod) under Linux:
https://bugs.python.org/issue34652
https://github.com/python/cpython/commit/69e96910153219b0b15a18323b917bd74336d229#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810R3140
```c
if test "$MACHDEP" != linux; then
AC_CHECK_FUNC(lchmod)
fi
```
So I'm not sure which package is causing the bug here. Should autoconf
return false? Should libc implement lchown without the bug? Or should
rsync skip lchmod under Linux, like python did?
To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1902109/+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 1900335] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Relevant lines from DpkgTerminalLog.txt: Setting up linux-firmware (1.187.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic [..] cp: cannot stat '/etc/ykluks.cfg': No such file or directory E: /usr/share/initramfs-tools/hooks/yubikey-luks failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 You have yubikey-luks installed, which hooks into update-initramfs and attempts to load a configuration file /etc/ykluks.cfg - which does not exist. As a result, the hook, update-initramfs, and configuring the linux-firmware package (which triggers an update-initramfs) fail. This is probably a configuration issue. It could also *possibly* be a bug in yubikey-luks (*may* want to just warn if this configuration file is missing), so I'm reassigning to that for now. Note that yubikey-luks is in universe, so community maintained. ** Package changed: initramfs-tools (Ubuntu) => yubikey-luks (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1900335 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in yubikey-luks package in Ubuntu: New Bug description: This happened during an upgrade from Ubuntu LTS 18.04 to 20.04. A `dpkg --configure -a` afterwards worked without trouble - bad interaction of install scripts? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkloos 1861 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 18 15:31:24 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (230 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 13 7390 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-18 (0 days ago) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/07/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yubikey-luks/+bug/1900335/+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 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
So, as has been previously stated here, and as is documented in section 5 of the journald.conf man page (install man-db, run 'man 5 journald.conf'), journald will, by default, limit the journals' disk allocation to either a maximum of 10% of available disk space, or to the absolute size of 4GB, whichever is lower. Example 1: You have a 120 GB disk, 70 GB are in use, leaving 50 GB. 10% of 50 GB are 5 GB, but the absolute value of 4 GB is lower, so journald will at most take 4 GB storage on this system (and dynamically less, if the disk grows fuller). Example 2: You have a 20 GB disk, 12 GB are in use, leaving 8 GB. 10% of 8 GB are 800 MB, which is less than 4 GB, so journald will at most take 800 MB storage on this system (and dynamically more or less, if disk allocation changes). Benjamin is now reporting 4.1 GB allocated, which is more than 4 GB, and with the details above, this is unexpected. What could be the reason? These limits are applied both when journald starts, and when vacuuming takes place. So if Benjamins' logs have grown by 100 MB since journald started, this can easily explain this situation. They will be reduced to 4 GB (or less, if the disk runs full) again next time vacuuming takes place (such as when journald is restarted). So unless these limits are considered a problem (why? disk space is cheap, and you can modify them as needed if you're on a special (embedded?) platform), I don't see a problem here. -- 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/1790205 Title: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+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 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Working for me too. Many thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Focal: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa ships an invalid network-manager configuration that triggers warnings * Test case $ journalctl | grep no-mac-addr-change should not have errors listed * Regression potential the change removes configurations which are not needed (since they set the value to the same one as the default) and in the wrong section, it shouldn't have any visible impact Hi, NetworkManager warns that no-mac-addr-change.conf contains unknown configuration directives: # journalctl | grep no-mac-addr-change Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 10-globally-managed-devices.conf, default-wifi-powersave-on.conf) Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' Apr 25 09:24:50 vougeot NetworkManager[573]: [1556177090.0596] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: wpasupplicant 2:2.6-21ubuntu3 Uname: Linux 5.0.9-050009-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sat Apr 27 13:15:27 2019 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+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 1877440] Re: /lib/NetworkManager/conf.d values in wrong section
*** This bug is a duplicate of bug 1826639 *** https://bugs.launchpad.net/bugs/1826639 > Thank you for your bug report, the configuration comes > from wpa and has been fixed in > https://salsa.debian.org/debian/wpa/-/commit/00ec8743 Many thanks. And apologies for not running "dpkg -S ..." and mis- classifying the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1877440 Title: /lib/NetworkManager/conf.d values in wrong section Status in wpa package in Ubuntu: Fix Committed Bug description: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1877440/+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 1875910] Re: Command to update mirror list
** Changed in: launchpad Status: New => Triaged ** Changed in: launchpad Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1875910 Title: Command to update mirror list Status in Launchpad itself: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: I see a lot of issues regarding outdated Ubuntu.mirrors file, I think there should be a command that imports the list of mirrors from https://launchpad.net/ubuntu/+archivemirrors and updates the templates/Ubuntu.mirrors file, then in the UI add a button that can update the list of Mirrors. I don't see the point of needing a new release every time the list needs to be updated. I want a mirror that was updated yesterday, because is the closest to my location, but it is not in the list, and as you can see there are lots of issues from people that could have been avoided with this. This is not really a bug, but a feature. Also could be great if there was some kind of filter, like if you select now in Ubuntu 19.10 a ftp mirror and update it will fail, and the UI gets broken (you can't even close the window, you have to kill it), so doing this update should just import those mirrors that are safe to use. To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1875910/+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 1877440] [NEW] /lib/NetworkManager/conf.d values in wrong section
Public bug reported: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1877440 Title: /lib/NetworkManager/conf.d values in wrong section Status in network-manager package in Ubuntu: New Bug description: $ g ^VER /etc/os-release VERSION="20.10 (Groovy Gorilla)" VERSION_ID="20.10" VERSION_CODENAME=groovy $ apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu3 Candidate: 1.22.10-1ubuntu3 Version table: *** 1.22.10-1ubuntu3 500 500 http://ch.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status $ cat /lib/NetworkManager/conf.d/no-mac-addr-change.conf # Certain drivers are known not to support changing the MAC address. # Disable touching the MAC address on such devices. # # See man NetworkManager.conf # # https://bugzilla.gnome.org/show_bug.cgi?id=777523 [device-mac-addr-change-wifi] match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no wifi.cloned-mac-address=preserve ethernet.cloned-mac-address=preserve "wifi.cloned-mac-address" and "ethernet.cloned-mac-address=preserve" should be in a "[connection]" section. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1877440/+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 1876632] [NEW] Corrupted fonts in display output when using multiple users
Public bug reported: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: Corrupted fonts in display output when using multiple users Status in xorg package in Ubuntu: New Bug description: I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersio
[Touch-packages] [Bug 1875407] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 09:59:42 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-12 (1567 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1875407 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 09:59:42 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-12 (1567 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1875407/+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 1874832] [NEW] QCoreApplications sets QTextCodec::codecForLocale() incorrectly
Public bug reported: With ICU versions >= 61 QTextCodec::codecForLocale() always returns the utf-8 codec with mib 106 regardless of the value of the environmental variable LC_ALL or the available locales. On bionic, which included ICU 60, codecForLocale() returned the correct codec. On eoan and focal, which include ICU 63 and ICU 66, the utf-8 codec is always returned. The change in behavior is expected due to a documented change in ICU https://github.com/unicode-org/icu/commit/d7482c9720b4f71dd9dad0. However, Qt has not accounted for this change in ICU. I note that Qt 5.12.8 from https://download.qt.io/archive/qt/5.12/5.12.8/ is packaged with an older version of ICU so the combination works correctly. But on Ubuntu eoan and focal the included version of ICU is not compatible with the included Qt. The included file localetrouble.tar contains 1) demo: a script that builds two tests cases and runs them 2) focal.log: the results of running the demo script on focal 3) bionic.log: the results of running the demo script on bionic 4) test1.cc: a minimal Qt Core application that tries to use the codec from the current locale. 5) test1.pro: Qt pro file used to build test1.cc 6) test2.cc: a test program that shows why Qt fails to detect the correct locale. These two lines are executed by QCoreApplicationPrivate::initLocale() and *QIcuCodec::defaultCodecUnlocked(). 7) test2.pro: Qt pro file used to build test2.cc The expected results of test1 are that codecForLocale is set based on LC_ALL to en_US.iso88591: env LC_ALL=en_US.iso88591 ./test1 QTextCodec::codecForLocale(): "ISO-8859-1" , mib 4 LC_ALL: en_US.iso88591 The actual results on focal are: env LC_ALL=en_US.iso88591 ./test1 QTextCodec::codecForLocale(): "UTF-8" , mib 106 LC_ALL: en_US.iso88591 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qtbase5-dev 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 14:45:36 2020 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "bug demonstration and analysis" https://bugs.launchpad.net/bugs/1874832/+attachment/5359537/+files/localetrouble.tar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1874832 Title: QCoreApplications sets QTextCodec::codecForLocale() incorrectly Status in qtbase-opensource-src package in Ubuntu: New Bug description: With ICU versions >= 61 QTextCodec::codecForLocale() always returns the utf-8 codec with mib 106 regardless of the value of the environmental variable LC_ALL or the available locales. On bionic, which included ICU 60, codecForLocale() returned the correct codec. On eoan and focal, which include ICU 63 and ICU 66, the utf-8 codec is always returned. The change in behavior is expected due to a documented change in ICU https://github.com/unicode-org/icu/commit/d7482c9720b4f71dd9dad0. However, Qt has not accounted for this change in ICU. I note that Qt 5.12.8 from https://download.qt.io/archive/qt/5.12/5.12.8/ is packaged with an older version of ICU so the combination works correctly. But on Ubuntu eoan and focal the included version of ICU is not compatible with the included Qt. The included file localetrouble.tar contains 1) demo: a script that builds two tests cases and runs them 2) focal.log: the results of running the demo script on focal 3) bionic.log: the results of running the demo script on bionic 4) test1.cc: a minimal Qt Core application that tries to use the codec from the current locale. 5) test1.pro: Qt pro file used to build test1.cc 6) test2.cc: a test program that shows why Qt fails to detect the correct locale. These two lines are executed by QCoreApplicationPrivate::initLocale() and *QIcuCodec::defaultCodecUnlocked(). 7) test2.pro: Qt pro file used to build test2.cc The expected results of test1 are that codecForLocale is set based on LC_ALL to en_US.iso88591: env LC_ALL=en_US.iso88591 ./test1 QTextCodec::codecForLocale(): "ISO-8859-1" , mib 4 LC_ALL: en_US.iso88591 The actual results on focal are: env LC_ALL=en_US.iso88591 ./test1 QTextCodec::codecForLocale(): "UTF-8" , mib 106 LC_ALL: en_US.iso88591 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qtbase5-dev 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 14:45:36 2020 ProcEnviron:
[Touch-packages] [Bug 1874393] [NEW] openswan VPN no longer works after upgrade to 20.04
Public bug reported: #nmcli con up 6cff80a9-24e9-4b19-89f1-1324ef966ceb Error: Connection activation failed: The VPN service 'org.freedesktop.NetworkManager.openswan' was not installed. #dpkg -l|grep -i swan ii libcharon-extauth-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libstrongswan 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-standard-plugins5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (standard plugins) ii network-manager-strongswan1.4.5-2.1 amd64network management framework (strongSwan plugin) ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-nm 5.8.2-1ubuntu3 amd64strongSwan plugin to interact with NetworkManager Where has the openswan plugin gone ? It's still an option in nm-applet ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 23 08:39:32 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.11.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.11.0/24 dev wlan0 proto kernel scope link src 192.168.11.50 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2017-10-16T20:52:50.502869 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1874393 Title: openswan VPN no longer works after upgrade to 20.04 Status in network-manager package in Ubuntu: New Bug description: #nmcli con up 6cff80a9-24e9-4b19-89f1-1324ef966ceb Error: Connection activation failed: The VPN service 'org.freedesktop.NetworkManager.openswan' was not installed. #dpkg -l|grep -i swan ii libcharon-extauth-plugins 5.8.2-1ubuntu3 amd64strongSwan charon library (extended authentication plugins) ii libstrongswan 5.8.2-1ubuntu3 amd64strongSwan utility and crypto library ii libstrongswan-standard-plugins5.8.2-1ubuntu3 amd64strongSwan utility and crypto library (standard plugins) ii network-manager-strongswan1.4.5-2.1 amd64network management framework (strongSwan plugin) ii strongswan-libcharon 5.8.2-1ubuntu3 amd64strongSwan charon library ii strongswan-nm 5.8.2-1ubuntu3 amd64strongSwan plugin to interact with NetworkManager Where has the openswan plugin gone ? It's still an option in nm-applet ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Apr 23 08:39:32 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.11.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.11.0/24 dev wlan0 proto kernel scope link src 192.168.11.50 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2017-10-16T20:52:50.502869 nmcli-nm: RUNNING VERSION ST
[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343 ** Bug watch added: Linux Kernel Bug Tracker #204343 https://bugzilla.kernel.org/show_bug.cgi?id=204343 -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc
There is no easy way to gracefully handle weak crypto. It has been known for more than five years that 1024 bit (or rather <2048 bit) DH primes need to be considered weak and should not be used - https://weakdh.org/ - GnuTLS > 3.2 does the right thing in having services which still have not taken action to use contemporary (non weak) crypto fail by default, so that users will become aware of the fact they are (were) connecting insecurely, and these services can be more easily identified and fixed. In some cases, using clients (and software versions of client) which support higher TLS protocol versions can work around this problem (if remote servers support strong ciphers on higher TLS protocol versions; example: https://www.ssllabs.com/ssltest/analyze.html?d=mail.nhs.net&hideResults=on ). It *may* be possible to continue to allow for insecure connections by setting the GnuTLS priority string to include LEGACY as per https://gnutls.org/manual/html_node/Priority-Strings.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnutls28 package in Ubuntu: Confirmed Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
It affects disco. Was a fix released? ** Tags added: disco -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: New Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193 The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1787297] Re: Clock : incorrect date format in panel
The format you are complaining about is American NOT English. I have noticed the same problem, running Gnome Flashback under Ubuntu 18.04, today. System settings show the correct English regional format (eg Thu 12 Dec 2019 18:29:30) but, in the indicator, I get Thu Dec 12 2019 18:29:30. Extremely annoying. gsettings set com.canonical.indicator.datetime custom-time-format "%a %d %b %Y %H:%M:%S" has no effect nor can I find an appropriate valid string to enter in locations. Is this now being handled elsewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in panel Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953
I'm currently traveling for work, but will verify the fix this evening hopefully. Thanks On Thu, Nov 14, 2019, 10:41 Dan Streetman wrote: > @drdabbles can you please verify the fix in systemd in proposed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1847527 > > Title: > Backport systemd-journal-remote fix PR #11953 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+subscriptions > -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal upload, because it added a check to verify the Content-Length header, but the upload may use Transfer-Encoding of 'chunked' which does not specify Content-Length. [test case] setup 2 systems, A and B. Install systemd-journal-remote on both. On A: $ sudo systemctl edit systemd-journal-remote.service in the editor, add: [Service] ExecStart= ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ Then enable/start the socket: $ sudo systemctl enable systemd-journal-remote.socket $ sudo systemctl start systemd-journal-remote.socket Optionally, start the service and verify it is running (not required, since the socket will start the service): $ sudo systemctl start systemd-journal-remote.service $ sudo systemctl status systemd-journal-remote.service | grep Active Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago On B: Edit the file /etc/systemd/journal-upload.conf: [Upload] URL=http://192.168.122.184:19532 Replacing the IP address with the actual ip addr of node A. Then enable/start the service: $ sudo systemctl enable systemd-journal-upload.service $ sudo systemctl start systemd-journal-upload.service Check for failure: ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 UTC. -- Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service. Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to http://192.168.122.184:19532/upload failed with code 411: gth Required Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main process exited, code=exited, status=1/FAILURE Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Failed with result 'exit-code'. [regression potential] this limits the Transfer-Encoding to only be either unspecified, or 'chunked'. Any other value will fail. However, journal-upload.c does not ever use any other Transfer-Encoding than 'chunked', and this fix comes from upstream and has not changed since applied there. Any regression would likely result in the failure to upload a remote journal. [other info] the commit that caused this is not included in Bionic, and the commit to fix this is already in Eoan; this is needed only in Disco. original description: -- I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1685754] Re: gnome-terminal unduly forces umask=0022
** Changed in: gnome-terminal
Importance: Medium => Unknown
** Changed in: gnome-terminal
Status: Confirmed => Unknown
** Changed in: gnome-terminal
Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Unknown
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Kodi devs-team were very conservative they would not help and asked me to wait Ubuntu fix the bug. Kodi is a reference to a bug that affects every graphical software installed. I'm observing every new mesa and kernels upgrades, I'll keep informing. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
No, Kodi does not crash anymore with x-swat and since official mesa 19.0.8-0ubuntu0~18.04.2 But it's followed by another problem, it's not 100% solved. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Just tested your ppa with mesa 19.2.1-1ubuntu1~18.04.1~ppa2, thank you Since mesa 19.0.8-0ubuntu0~18.04.2 the image produced by Ubuntu with all media players and browsers is very dark, like the contrast and black levels were adjusted at a very low value. It became worse than before, including yours from x-swat. I noticed this contrast darkness increases progressively with each kernel upgrade, starting from 5.0.0-27 to 5.0.0-32; I'm using 4.18.0-15 to minimize this effect. I tested a Radeon R7 250 card, compatible with A-10 series APUs, and got the exact same bug. So the problem is not only with AMD APUs, but with the entire AMD R7 Graphics series, if not all AMD stack. You guys need to test more AMD hardware. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1191895] Re: networking eventually brought down due to inactivity
Is this something which could be supported by now? gnome-control-center -> power seems to offer a setting to manage wi-fi power saving but in the end this is just a wi-fi on/off switch which immediately brings the device down/up (bug 1751954). Looking through the details of an existing NM wireless configuration profile there are no related (power saving) features exposed on the GUI. "nmcli connection show $UUID" lists a 802-11-wireless.powersave (default: 0) setting. https://developer.gnome.org/NetworkManager/stable/settings-802-11-wireless.html Is this what brings the interface down after some ~ 10 minutes of user input inactivity / ~ 5 minutes of blank screen? If so, could this be exposed on the GUI? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1191895 Title: networking eventually brought down due to inactivity Status in network-manager package in Ubuntu: Confirmed Bug description: For various reasons, I like to be able to ssh in to my nexus 4. I have noticed with current saucy (and raring before it), after some time of inactivity the screen goes blank (fine), but then occasionally after some more time after that, networking is brought down (wifi) if there is no network activity. If I continuously ping the device, networking stays up. If I keep the screen from blanking, networking stays up. The current behavior is different than the behavior on android, where I can get various notifications for facebook, email, etc when the screen is blank. HARDWARE=mako JENKINS_BUILD=saucy-11 UBUNTU=ubuntu-touch-saucy-armhf ubuntu/platform-api=:68 hybris=0.1.0+git20130606+c5d897a-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1191895/+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 1848900] Re: blank display with Eoan Ermine live DVD on Rysen 2200G
** Attachment added: ""journalctl -b -1" (failed boot) for other user" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log ** Summary changed: - blank display with Eoan Ermine live DVD on Rysen 2200G + Blank display with Eoan Ermine live DVD on Ryzen 3 2200G -- 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/1848900 Title: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg package in Ubuntu: New Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 d
[Touch-packages] [Bug 1848900] Re: blank display with Eoan Ermine live DVD on Rysen 2200G
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G (Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2 08/08/2018) today, whose log of a failed (standard) boot (to black screen) showed kernel: WARNING: CPU: 2 PID: 255 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] which seems to be discussed at https://bugs.freedesktop.org/show_bug.cgi?id=109628 ** Bug watch added: freedesktop.org Bugzilla #109628 https://bugs.freedesktop.org/show_bug.cgi?id=109628 -- 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/1848900 Title: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg package in Ubuntu: New Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xser
[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953
@ddstreet any configuration that ships lots to a remote host will trigger this. The server always responds with the bug, so the configuration effectively doesn't matter. As long as one host is attempting to send journals to another in Disco, this bug will be triggered. Examples configs: ### # Server 1 Config # ### $ cat /etc/systemd/system/systemd-journal-remote.service [Unit] Description=Journal Remote Sink Service Documentation=man:systemd-journal-remote(8) man:journal-remote.conf(5) Requires=systemd-journal-remote.socket [Service] ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 --output=/var/log/journal/remote/ LockPersonality=yes LogsDirectory=journal/remote MemoryDenyWriteExecute=yes NoNewPrivileges=yes PrivateDevices=yes PrivateNetwork=yes PrivateTmp=yes ProtectControlGroups=yes ProtectHome=yes ProtectHostname=yes ProtectKernelModules=yes ProtectKernelTunables=yes ProtectSystem=strict RestrictAddressFamilies=AF_UNIX AF_INET AF_INET6 RestrictNamespaces=yes RestrictRealtime=yes RestrictSUIDSGID=yes SystemCallArchitectures=native User=systemd-journal-remote WatchdogSec=3min # If there are many split up journal files we need a lot of fds to access them # all in parallel. LimitNOFILE=524288 [Install] Also=systemd-journal-remote.socket ### # Server 2 Config # ### $ cat /etc/systemd/journal-upload.conf [Upload] URL=http://server1:19532 -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in openstack-ansible: New Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Disco: New Bug description: I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job
I'm experiencing this in 19.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1073669 Title: Bluetooth won't stay disabled after reboot due to early upstart job Status in rfkill package in Ubuntu: Confirmed Bug description: Using a Dell XPS 13 with Ubuntu 12.04. In order to restore RF interfaces to their previous state between boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill- store.conf (run while shutting down) and rfkill-restore.conf (run when starting up). However, while rfkill-restore.conf starts on the Upstart local-filesystems signal, there is a high probability that the RF kill switches in /sys/class/rfkill/ still won't yet be populated (i.e. every time on the Dell XPS 13). This results in behavior like the following: 1. Disable bluetooth via applet. 2. Reboot. 3. Login. 4. Observe bluetooth is re-enabled! Bluetooth should have stayed disabled, but since the kill switches weren't present when rfkill-restore was run, the kill switch states were not restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1847527] Re: Backport systemd-journal-remote fix PR #11953
For those that may try to search for this bug in the future, the error I received was Error 411: gth required The issue is that libmicrohttpd exhibits a bug when Content-Length is omitted, even if Transfer-Encoding is set to "chunked". The HTTP/1.1 spec allows Content-Length to be omitted when the length is unknown as long as Transfer-Encoding: Chunked is specified. The proper behavior would be for journald to return an error to the client when it has received too much data. -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1847527/+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 1847527] [NEW] Backport systemd-journal-remote fix PR #11953
Public bug reported: I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Bug watch added: github.com/systemd/systemd/issues #11571 https://github.com/systemd/systemd/issues/11571 ** Also affects: systemd via https://github.com/systemd/systemd/issues/11571 Importance: Unknown Status: Unknown ** Summary changed: - Backport journal-remote fix PR #11953 + Backport systemd-journal-remote fix PR #11953 -- 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/1847527 Title: Backport systemd-journal-remote fix PR #11953 Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I'm requesting that systemd 240 receive the fix in upstream PR 11953 found here https://github.com/systemd/systemd/pull/11953 This fixes remote journal shipping using systemd components. I believe only Disco (19.04) is impacted by this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1847527/+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 1772512] Re: Unable to install i386 and amd64 arch at the same time
hi guys, on ubuntu bionic 18.04 amd64 I still can't install libsdl2-dev:i386 and libsdl2-dev:amd64 because of that libxkbcommon- dev:i386 and libxkbcommon-dev:amd64 can't coexist. Is there any progress so far? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Committed Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Thank you for your assistance. Let me know when it's figured out. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Using Kodi as reference for the behaviour of VDPAU hw acceleration on the system: The latest version of mesa doesn't work and makes Kodi crash when opening any video. I figured that when I downgrade every package of mesa to version 18.2.8, kodi is now able to run videos, but still without vdpau. The behaviour improved, but without hw acceleration. https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging I meant that when I upgrade mesa with this package, I encounter the same behaviour of the version 18.2.8 I downgraded. Using Oibaf's ppa is the only to get vdpau acceleration working, but the image is too dark, it doesn't have the bells and whistles specifically optimized for Ubuntu. I wrote earlier that I tested disco with success, vdpau runs well and nothing's necessary to add. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
I suggest you mark the importance of this bug as Critical, because it affects every single user of AMD APUs. We have no HW Acceleration. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Not yet mate. Installing the packages from this ppa have the same effect of downgrading them. Kodi responds better, still there's no HW Acceleration. I've just tested a Nvidia card using noveau and proprietary drivers, it worked well. But it was borrowed, I'll have to return it unfortunately ;( -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Please Timo, there's really a problem with AMD APUs We are running our systems without HW Acceleration support -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Should I create a new bug report on linux-firmware package? -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
I've tested Ubuntu 18.04.2 on 2 machines with different hardware: - One Laptop with Intel CPU integrated graphics, it works well. - A Laptop with an AMD APU, the problem is the same. I use a Kaveri AMD APU on my main PC and the other person affected on this bug, another AMD APU. So we have 3x problematic APU vs. 1x working Intel. Recent updates came misconfigured for AMD APUs, and we're running our entire systems without VDPAU hw acceleration, not only kodi. FYI: I've tested Disco Dingo, it has not problem with my APU. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Oh, I see incoming updates for mesa 19.0.8 in bionic as well. They're still under final adjustments then, I hope it fix my issue. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Please ignore the solution I commented, I committed a mistake and had vdpau disabled. But there's this update that hasn't been released by the server. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
What's happening here? Everything I download from this server http://mirrors.edge.kernel.org/ubuntu/pool/main/u/ubuntu-meta/ Firefox accuses of having a virus or malware and eliminate the files. It's an official Ubuntu North America server. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
https://lists.ubuntu.com/archives/bionic-changes/2019-July/021427.html -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Solution's found: ubuntu-meta (1.417.3) bionic; urgency=medium * Added dbus-x11 to wsl-recommends (LP: #1837466) -- Balint Reczey Wed, 24 Jul 2019 01:21:39 +0200 I found in the server this latest version of ubuntu-desktop and installed the .deb file. Indeed we see a correction for X11/xorg and everything works now. However, I find odd that this package was uploaded on Thu Jul 25 21:52:21 to be sent as an update: https://lists.ubuntu.com/archives/bionic-changes/2019-July/021433.html http://mirrors.edge.kernel.org/ubuntu/pool/main/u/ubuntu-meta/ But I received on my system this one [ubuntu/bionic-updates] ubuntu-meta 1.417.2 (Accepted) Uploaded on Thu Jul 25 19:44:55 UTC 2019 And probably everyone else! -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Timo, I think the problem is with xorg-server, along with mesa, it was present on the latest updates when the crash came up. When kodi tries to load a video, its window simply closes. If switch to Wayland, it works. But everything is very buggy with this server, it's inoperable. Maybe there are missing guidelines for my specific AMD APU? -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+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 1833671] Re: bond interfaces stop working after restart of systemd-networkd
I've just updated the two machines where I was seeing this to 237-3ubuntu10.25 and in both cases the update was successful and managed to complete without disconnecting the network. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network] Address=1.2.3.4/32 restart networkd, or reboot, and verify the bond is up: root@lp1833671:~# ip a 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff inet 1.2.3.4/32 scope global bond0 valid_lft forever preferred_lft forever inet6 fe80::4030:62ff:fecc:362b/64 scope link valid_lft forever preferred_lft forever restart networkd and check /var/log/syslog: root@lp1833671:~# systemctl restart systemd-networkd root@lp1833671:~# cat /var/log/syslog ... Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier [regression potential] this changes how bond slaves are managed, so regressions could affect any configurations using bonding. [other info] the patch is already included in d, and ifupdown manages networking in x, so this is needed only for b. [original description] Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833671/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Currently I found that downgrading these packages: libgl1-mesa-dri_18.2.8-0ubuntu0~18.10.2_amd64.deb mesa-vdpau-drivers_18.2.8-0ubuntu0~18.10.2_amd64.deb I can run Kodi with every single Ubuntu package updated, including libdrm-amdgpu. **Note: from oibaf's ppa I need only libdrm-amdgpu1 libdrm-common libdrm2 libgl1-mesa-dri vdpau-driver-all mesa-vdpau-drivers upgraded to have it running well. I'll give disco a try, but personally I prefer LTS versions for a more solid UI experience. I'll be here, patiently waiting for the next updates to see if I got it fixed. ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
How could I make mesa-vdpau-drivers work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
I've tested Ubuntu Studio Bionic Beaver 18.04, and since it receives all the same updates from default Ubuntu, the results were identical. As to disco dingo, I really prefer to go with the more polished LTS versions as a personal choice of mine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
As I said, the closest package to linux-image-hwe-edge I found for installation is: sudo apt install --install-recommends linux-image-generic-hwe-18.04-edge That gives me the Kernel version uname -r 5.0.0-20-generic Unfortunately kodi didn't work, only with the removal of mesa-vdpau- drivers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
I've found a different problem situation: I first applied the downgrade of libdrm-amdgpu1 2.4.97-1ubuntu1~18.04.1 to 2.4.95-1ubuntu1~18.04.1, on the first launch of a newly installed Ubuntu 18.04.2 without any of the 400 updates packages available. This way I got package Kodi working. Now, after I update everything to the latest version, with libdrm- amdgpu1 as well, I can no longer downgrade it. If I force it, the system will crash. I've figured that the removal of mesa-vdpau-drivers (which also removes vdpau-driver-all) gets kodi running normally again, even with VDPAU activated on settings/player. So that's the new solution for kodi's bug. If I downgrade mesa-vdpau-drivers_19.0.2-1ubuntu1.1~18.04.1_amd64.deb mesa-vdpau-drivers_18.2.8-0ubuntu0~18.10.2_amd64.deb kodi still won't run, only removing mesa-vdpau-drivers. This package didn't receive any update since 18.04.1 and had always been working. I detected that the only packages required for kodi that received upgrades is libllvm8 (has no issues) and libdrm-amdgpu1, giving me the conclusion that the bug really is with libdrm-amdgpu1. Trying your advices with mesa-vdpau-drivers installed: Yes, the currently installed version of libgl1-mesa-dri is 19.0.2. Installing the repo didn't work sudo add-apt-repository ppa:ubuntu-x-swat/updates The following packages will be upgraded: libegl-mesa0 libegl1-mesa libgbm1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglx-mesa0 libwayland-egl1-mesa libxatracker2 mesa-va-drivers mesa-vdpau-drivers kodi's bug still remains. I've also heard from a 19.04 user that kodi runs, maybe it's a bug caused with some hardware models or to 18.04 specific. Is that correct? sudo apt install --install-recommends linux-image-generic-hwe-18.04-edge I tried it and still nothing man. Once again, kodi will only run with the removal of mesa-vdpau-drivers. Thank you for your time, I really appreciate your assistance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1837170] [NEW] Kodi package crash after the update of libdrm-amdgpu1
Public bug reported: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. ** Affects: libdrm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: New Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+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 1792643] Re: apport does not upload wayland or gnome-shell crash data
This issue seems to have occurred to me today (and several times previously) - when I returned to my computer after a while (the screen had entered power saving mode), the gnome-shell process (on XWayland) failed. Neither after logging in to gnome-shell / Xwayland nor after logging out and back into gnome-shell / Xorg was I prompted to submit a bug report about it, even though there was /var/crash/_usr_bin_gnome- shell.1000.crash. Killing and restarting whoopsie and update-notifier did not change it. Manually generating and submitting the report using apport-cli /var/crash/_usr_bin_gnome-shell.1000.crashdid succeed for me, however (however the automation to do so failed). -- 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/1792643 Title: apport does not upload wayland or gnome-shell crash data Status in apport package in Ubuntu: Confirmed Bug description: uname -a Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 In trying to upload .crash data for bug 1789962 "gnome-shell segfaults in Wayland when display is turned off while Kodi running" I determined that apport-cli and friends were never able to upload the .crash files. The URL where they should appear is: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 Earlier, I did upload the .crash files directly and was told by the defect reviewer that: _usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols) _usr_bin_gnome-shell.1000.crash: Stack trace is missing You can see the other bug for details, here is the last comment that I added (so far): I deleted all entries in /var/crash and /var/lib/whoopsie. I recreated the problem ls -l /var/crash total 92136 -rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 _usr_bin_gnome-shell.1000.crash -rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 _usr_bin_Xwayland.1000.crash -rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 _usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash *** Error: Invalid problem report No such file or directory Press any key to continue... fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash *** 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 (40.6 MB) E: Examine locally 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/E/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. < Deleted lots and lots of ellipsis > echo $? 0 total 4 ls -l /var/lib/whoopsie -rw--- 1 root root 128 Sep 13 18:39 whoopsie-id sudo cat /var/lib/whoopsie/whoopsie-id 39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 Checked the URL: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 No entries since 08/11. None for wayland, gnome-shell or Kodi. I checked for over 5 minutes. So perhaps something is going bad on my end, but I just don't know what or how to debug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1792643/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection
Hi. I am just a fellow Ubuntu user, but I am afraid this bug report is most likely not something anyone could solve, because so many different chipsets and issues are being discussed here (I assume this is also why no developers felt inclined to touch it so far). I very much recommend that anyone still experiencing wireless issues should (look for, and if none exists) file a new bug against their wireless driver, and anyone with Ethernet issues should (look for, and if none exists) file a new bug against their Ethernet driver. Your drivers will usually be listed in the output of one of these commands: lspci -knn lsusb You are also welcome to check back with community support to check whether a fix (or a workaround) is already available for your very issue, or just to get help with filing a bug report that is specific and can get handled more easily. https://ubuntu.com/support/community-support If TylerKinkade's issue (where both Wireless and Ethernet disconnect at the same time, on a now supported Ubuntu version) persists then it is more likely a platform (hardware / mainboard / ACPI / firmware) specific issue and should be treated as such, affecting Inspiron 5567 with this specific Ubuntu version (was 16.04.1 originally). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 10
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
This command was reported to successfully work around this bug: sudo sed -i 's/^Automatically/# Automatically/g' /var/lib/dpkg/info /base-files.postinst It changes any lines starting with "Automatically" into comments, which lets the script finish properly when you run: sudo dpkg --configure base-files Or just run this afterwards: sudo apt -f install -- 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/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+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 1835095] Re: Lubuntu initrd images leaking cryptographic secret when disk encryption is used
** Information type changed from Public to Public Security -- 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/1835095 Title: Lubuntu initrd images leaking cryptographic secret when disk encryption is used Status in initramfs-tools package in Ubuntu: New Bug description: Hello! I've had a short discussion about this issue on lubuntu irc, and I was asked to open a bug report. Basically I only tested this on lubuntu 19.04 x64 live image on a UEFI system, I haven't tested other ubuntu flavors. Anyway, I was poking around with disk encryption, and I noticed that lubuntu live image uses a graphical installation tool called Calamares. This tool has an option to encrypt the hard disk during installation, and the encryption setup that is used is the newer one with /boot folder as part of the encrypted rootfs. Traditionally the installers used to setup encryption where there is a main LUKS- encrypted rootfs volume on the HDD and a separate unencrypted /boot partition where the grub config files, the kernel and the initrd images reside. Ever since grub2 added support for LUKS several distros have apparently moved to the newer scheme which is very similar to the one that was first described by Pavel Kogan in his blog. A) https://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/ B) https://www.pavelkogan.com/2015/01/25/linux-mint-encryption/ This new scheme stores the rootfs (including the /boot folder) on a single LUKS-encrypted partition with two keyslots in use. One of the keyslots is normally a passphrase that is used in the first stage by the grub2 EFI image as pre-boot authentication. It serves to decrypt the rootfs, access the contents of /boot and copy the config, kernel and initrd image to RAM. Once done, grub2 then forgets the passphrase and closes the encrypted volume. The system will continue to boot, but at this point the rootfs will now have to be decrypted a second time - this time by the kernel/initrd so it can be mounted. Normally this is the point where the user would be asked to enter a passphrase for the second time, but for convenience reasons (to automate the process) a second LUKS keyslot and a keyfile are used instead. The file /crypto_keyfile.bin is generated during the installation phase. This is the secret keyfile that is used to unlock the other LUKS keyslot and decrypt the rootfs. It is properly protected with owner set to root:root and file permissions 600 (-rw---). Unfortunately the key is not of much use while it resides inside the encrypted volume that it is supposed to decrypt. This is where initramfs-tools comes into play. I believe there is a special hook inside /usr/share/initramfs-tools/hooks that is responsible for copying this crypto_keyfile.bin file into appropriate initrd image. This image that now contains the secret keyfile is copied into RAM during the first decryption stage by the grub2. While the original secret keyfile /crypto_keyfile.bin is protected: $ ls -l / ... -rw--- 1 root root 2048 jul 2 18:34 crypto_keyfile.bin ... $ sha1sum /crypto_keyfile.bin sha1sum: /crypto_keyfille.bin: Permission denied $ sudo sha1sum /crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /crypto_keyfile.bin The second copy (the one inside initramfs image) is not: $ ls -l /boot ... -rw-r--r-- 1 root root 68149041 jul 2 18:35 initrd.img-5.0.0-13-generic As you can see, the initramfs images that are generated by mkinitramfs will have the user:group set to root:root, but their access flags will be 644 (-rw-r--r--). This means that any user or even a script that has read access to the file system can read and extract the secret keyfile from an initramfs image. Run as user: $ unmkinitramfs /boot/initrd.img-5.0.0-13-generic /tmp $ sha1sum /tmp/main/crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /tmp/main/crypto_keyfile.bin Would there be any adverse effects, if we were to set mkinitramfs (i.e. via a hook) to always set file permissions of initramfs images to 600 whenever this type of disk encryption is used? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835095/+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 1833829] Re: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
** Summary changed: - High memory usage by Xorg. + High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 -- 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/1833829 Title: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 Status in xorg package in Ubuntu: New Bug description: After some continued use of the system (Kubuntu (18.04)) Xorg accumulates a lot of RAM space. From that the space only increments and doesn't decrease. Hardware Specs : 1. Intel core-i5 6300 HQ 2. Nvidia GTX 960M Software Specs : 1. Kubuntu 18.04 2. KDE Plasma shell version 5.12.7 Something interesting to note is that I have not experienced the same behavior from Xorg when I switch the GPU to Intel's Integrated graphics. It is entirely possible that I might not have been able to trigger those situation with Intel, because after seeing logs I couldn't make out why this was happening. Also for the timeline I have used the system for over an year without any such issue arising. It was the second week of June 2019 to present day I have seen this problem. Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jun 23 05:06:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:0706] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706] InstallationDate: Installed on 2019-06-21 (1 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) 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 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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/1833829/+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 1833671] [NEW] bond interfaces stop working after restart of systemd-networkd
Public bug reported: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 ** Affects: systemd (Ubuntu) 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd package in Ubuntu: New Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1833671/+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 1833593] [NEW] fstrim.timer always triggers at 00:00, use RandomizedDelaySec
Public bug reported: fstrim.timer always triggers at 00:00: $ systemctl list-timers fstrim.timer NEXT LEFTLAST PASSED UNIT ACTIVATES Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days ago fstrim.timer fstrim.service 1 timers listed. Pass --all to see loaded but inactive timers, too. This can be an issue if concurrent runs cause increased I/O load on multiple servers which are part of the same system architecture (I have no hard facts via monitoring on this, but assume this can be an issue). /lib/systemd/system/fstrim.timer does not try to randomize the start time. systemd.timer(5) suggests that RandomizedDelaySec can be used to introduce variable start times, allowing for balancing out the (suspected increased) I/O load across multiple systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 19:52:17 2019 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1833593 Title: fstrim.timer always triggers at 00:00, use RandomizedDelaySec Status in util-linux package in Ubuntu: New Bug description: fstrim.timer always triggers at 00:00: $ systemctl list-timers fstrim.timer NEXT LEFTLAST PASSED UNIT ACTIVATES Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days ago fstrim.timer fstrim.service 1 timers listed. Pass --all to see loaded but inactive timers, too. This can be an issue if concurrent runs cause increased I/O load on multiple servers which are part of the same system architecture (I have no hard facts via monitoring on this, but assume this can be an issue). /lib/systemd/system/fstrim.timer does not try to randomize the start time. systemd.timer(5) suggests that RandomizedDelaySec can be used to introduce variable start times, allowing for balancing out the (suspected increased) I/O load across multiple systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 19:52:17 2019 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1833593/+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 1832802] Re: disco: curl error while loading shared libraries: libssl.so.1.0.0
*** This bug is a duplicate of bug 1832801 *** https://bugs.launchpad.net/bugs/1832801 ** This bug has been marked a duplicate of bug 1832801 disco: curl error while loading shared libraries: libssl.so.1.0.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832802 Title: disco: curl error while loading shared libraries: libssl.so.1.0.0 Status in curl package in Ubuntu: New Bug description: Linux 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DISTRIB_RELEASE=19.04 DISTRIB_DESCRIPTION="Ubuntu 19.04" curl: Installed: 7.64.0-2ubuntu1.1 Candidate: 7.64.0-2ubuntu1.1 Version table: *** 7.64.0-2ubuntu1.1 1001 1001 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.64.0-2ubuntu1 1001 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/main amd64 Packages When I run curl, I get the following error: curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory On other disco machines I'm not experiencing this issue. I apt purged openssl/libssl/curl and re-installed, but the error persists. I'm sure my system has some issue, but I'm unable to figure it out, and this felt like a bug as curl was working before upgrade to disco. I tried proposed packages to see if openssl 1.1.1b-1ubuntu2.2 instead of 1.1.1b-1ubuntu2 would make any difference, but the error persists. me@mbp:/usr/lib/x86_64-linux-gnu$ curl curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory me@mbp:/usr/lib/x86_64-linux-gnu$ which curl /usr/bin/curl me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep curl ii curl 7.64.0-2ubuntu1.1 amd64command line tool for transferring data with URL syntax ii libcurl3-gnutls:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (OpenSSL flavour) ii python3-pycurl 7.43.0.2-0.1 amd64Python bindings to libcurl (Python 3) me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep ssl ii android-libboringssl8.1.0+r23-2 amd64Google's internal fork of OpenSSL for the Android SDK rc docbook-dsssl 1.79-9.1 all modular DocBook DSSSL stylesheets, for print and HTML ii libflac++6v5:amd64 1.3.2-3 amd64Free Lossless Audio Codec - C++ runtime library ii libflac8:amd64 1.3.2-3 amd64Free Lossless Audio Codec - runtime C library ii libflac8:i386 1.3.2-3 i386 Free Lossless Audio Codec - runtime C library ii libio-socket-ssl-perl 2.060-3 all Perl module implementing object oriented interface to SSL sockets ii libnet-smtp-ssl-perl1.04-1 all Perl module providing SSL support to Net::SMTP ii libnet-ssleay-perl 1.85-2ubuntu3 amd64Perl module for Secure Sockets Layer (SSL) ii libssl-dev:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - development files ii libssl1.1:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - shared libraries ii libssl1.1:i386 1.1.1b-1ubuntu2.2 i386 Secure Sockets Layer toolkit - shared libraries ii libwavpack1:amd64 5.1.0-5ubuntu0.1amd64audio codec (lossy and lossless) - library ii libwavpack1:i386 5.1.0-5ubuntu0.1
[Touch-packages] [Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04
The mouse has a left-click button, a right-click button and a scrollwheel in between that is clickable. -- 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/1832133 Title: Mouse unresponsive on Ubuntu 18.04 Status in xorg package in Ubuntu: New Bug description: Hi there, I submitted this bug report following advice in https://wiki.ubuntu.com/DebuggingMouseDetection I dual-boot Windows 10 and Ubuntu 18.04 (on a HP Pavillion Touchsmart 15 Notebook PC 15-n090sa, bought in 2014). I use Ubuntu every day, and rarely boot up Windows. I use an optical mouse attached to my computer by USB cable. It works perfectly on Windows. But on Ubuntu, it will work OK for a couple of seconds, but then become less and less responsive, to the point where it barely works at all. I have a touchpad that works perfectly in both Windows and Ubuntu. Result of lsb_release -rd: Description: Ubuntu 18.04.2 LTS. Release: 18.04 I am using Xdiagnose version 3.8.8 Please help! Tom. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 17:03:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7600G] [103c:216b] InstallationDate: Installed on 2018-01-22 (502 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=f7ecd954-9bbe-4c06-9514-a1366c47b763 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 216B dmi.board.vendor: Hewlett-Packard dmi.board.version: 30.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.16:bd11/13/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216B:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion TS 15 Notebook PC dmi.product.version: 088110305E0620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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 xserver.bootTime: Wed Oct 31 01:15:25 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1832133/+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
