[Touch-packages] [Bug 1903954] [NEW] when Printing a lot of jobs with high speed, OS get message timeout, job stop with "pending"
Public bug reported: Bug Description Ubuntu 16.04LTS OS Version： 16.04 CUPS Version： 2.2.7 application: ORCA V5.0 when Printing a lot of jobs with high speed, OS get message timeout, job stop with "pending" We(RICOH printer driver developer) are report a problem from our printer users: I print ORCAfile with Ubuntu 16.04, CUPS 2.2.7 environment. I print a lot of jobs with default speed mode,jobs can be printed, but when I print with high speed mode, job suddenly stop with "pending", I figure out when all the print jobs can not be printed, I reprint one job but it can be printed ok I view the "CUPS Error Log", it shows that there is one points which maybe the reasons that makes the print job "pending" Reasons: we find the error job number,it happned when get printers massage,waiting time 12 seconds,but normal job use 1 second Error job D [11/Sep/2020:09:57:28 +0900] [Job 9531] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3) … d [11/Sep/2020:09:57:30 +0900] select_timeout(0): 11 seconds to start pending jobs … D [11/Sep/2020:09:57:40 +0900] [Job 9531] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4) … d [11/Sep/2020:09:57:42 +0900] select_timeout(0): 11 seconds to start pending jobs … D [11/Sep/2020:09:57:52 +0900] [Job 9531] Waiting for status monitor to stop Normal job D [11/Sep/2020:09:56:35 +0900] [Job 9530] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3) … D [11/Sep/2020:09:56:36 +0900] [Job 9530] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4) … D [11/Sep/2020:09:56:36 +0900] [Job 9530] Waiting for status monitor to stop when printer receive data,the default waiting time is 15 seconds, but when the OS print job as the waiting time more than 15 seconds without sending data, then the printer cannel the job Drivers: https://support.ricoh.com/bbv2/html/dr_ut_d/ipsio/history/w/bb/pub_j/dr_ut_d/4101033/4101033231/V503/5216152/ricohsg3200_7200_5.0.3-0_i386/history.htm Our question is: 1. why there were 12 seconds waitting time? 2. Do you have any plan to improve the performance of printing on Ubuntu 16.04? 3. Do you have any workaround before this problems fixed? ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1903954 Title: when Printing a lot of jobs with high speed, OS get message timeout, job stop with "pending" Status in cups package in Ubuntu: New Bug description: Bug Description Ubuntu 16.04LTS OS Version： 16.04 CUPS Version： 2.2.7 application: ORCA V5.0 when Printing a lot of jobs with high speed, OS get message timeout, job stop with "pending" We(RICOH printer driver developer) are report a problem from our printer users: I print ORCAfile with Ubuntu 16.04, CUPS 2.2.7 environment. I print a lot of jobs with default speed mode,jobs can be printed, but when I print with high speed mode, job suddenly stop with "pending", I figure out when all the print jobs can not be printed, I reprint one job but it can be printed ok I view the "CUPS Error Log", it shows that there is one points which maybe the reasons that makes the print job "pending" Reasons: we find the error job number,it happned when get printers massage,waiting time 12 seconds,but normal job use 1 second Error job D [11/Sep/2020:09:57:28 +0900] [Job 9531] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3) … d [11/Sep/2020:09:57:30 +0900] select_timeout(0): 11 seconds to start pending jobs … D [11/Sep/2020:09:57:40 +0900] [Job 9531] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4) … d [11/Sep/2020:09:57:42 +0900] select_timeout(0): 11 seconds to start pending jobs … D [11/Sep/2020:09:57:52 +0900] [Job 9531] Waiting for status monitor to stop Normal job D [11/Sep/2020:09:56:35 +0900] [Job 9530] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.3) … D [11/Sep/2020:09:56:36 +0900] [Job 9530] CUPS_SC_CMD_SNMP_GET: 38 (.1.3.6.1.4.1.367.3.2.1.2.18.2.1.7.1.4) … D [11/Sep/2020:09:56:36 +0900] [Job 9530] Waiting for status monitor to stop when printer receive data,the default waiting time is 15 seconds, but when the OS print job as the waiting time more than 15 seconds without sending data, then the printer cannel the job Drivers: https://support.ricoh.com/bbv2/html/dr_ut_d/ipsio/history/w/bb/pub_j/dr_ut_d/4101033/4101033231/V503/5216152/ricohsg3200_7200_5.0.3-0_i386/history.htm Our question is: 1. why there were 12 seconds waitting time? 2. Do you have any plan to improve the performance of printing on Ubuntu 16.04? 3. Do you have any workaround before
[Touch-packages] [Bug 1903950] [NEW] [ZenBook 13 UX331UAL, Realtek ALC294, Speaker, Internal] fails after a while
Public bug reported: Audio is not working. plays for 2 second and then stops ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumar 870 F pulseaudio /dev/snd/pcmC0D0p: kumar 870 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:29:12 2020 InstallationDate: Installed on 2020-11-12 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 12 12:14:07 kumar-ZenBook-13-UX331UAL dbus-daemon[633]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=870 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook 13 UX331UAL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX331UAL.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX331UAL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX331UAL.308:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnZenBook13UX331UAL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX331UAL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook 13 UX331UAL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1903950 Title: [ZenBook 13 UX331UAL, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Audio is not working. plays for 2 second and then stops ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kumar 870 F pulseaudio /dev/snd/pcmC0D0p: kumar 870 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:29:12 2020 InstallationDate: Installed on 2020-11-12 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Nov 12 12:14:07 kumar-ZenBook-13-UX331UAL dbus-daemon[633]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=1000 pid=870 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [ZenBook 13 UX331UAL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX331UAL.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX331UAL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX331UAL.308:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnZenBook13UX331UAL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX331UAL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook 13 UX331UAL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879206] Re: cups hplip not install printer
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Expired Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I can confirm, 1Mii b10 works pretty well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Thank you for the advice! I'm going to purchase and see if it works with my setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903829] Re: laptop screen turns off when I connect an external monitor
Maybe the system is remembering the external monitor as a configuration where the laptop screen was once turned off. So switching to that configuration involves turning off the laptop screen. To fix that try deleting all memory of the monitor configurations: rm ~/.config/monitors.xml ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: multimonitor ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903829 Title: laptop screen turns off when I connect an external monitor Status in mutter package in Ubuntu: Incomplete Bug description: When I connect the hdmi cable from my monitor the laptop screen starts to darken this only happens when I connect the external monitor. when I switch to mirror the external monitor starts flickering and the laptop monitor turns off completely. When I switch to join displays, the laptop monitor turns off completely and the external monitor stays on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 02:50:28 2020 DistUpgraded: 2020-11-11 02:37:02,636 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2020-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=c86cce5a-02e9-41bc-9097-dd5e168a82d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-11 (0 days ago) dmi.bios.date: 12/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0Y2FDT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd12/23/2019:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0Y2FDT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing
** Summary changed: - "Analog Stereo Duplex" profile keeps disappearing + [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing -- 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/1903903 Title: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing Status in pulseaudio package in Ubuntu: New Bug description: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903484] Re: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1903484 Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 Status in six package in Ubuntu: New Bug description: Plz fix this bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-six 1.14.0-2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 5 21:00:52 2020 Dependencies: DuplicateSignature: package:python-six:1.14.0-2 Setting up python-six (1.14.0-2) ... /var/lib/dpkg/info/python-six.postinst: 6: pycompile: not found dpkg: error processing package python-six (--configure): installed python-six package post-installation script subprocess returned error exit status 127 ErrorMessage: installed python-six package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-10-22 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: six Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1903484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903484] Re: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to six in Ubuntu. https://bugs.launchpad.net/bugs/1903484 Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 Status in six package in Ubuntu: New Bug description: Plz fix this bug ProblemType: Package DistroRelease: Ubuntu 20.04 Package: python-six 1.14.0-2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 5 21:00:52 2020 Dependencies: DuplicateSignature: package:python-six:1.14.0-2 Setting up python-six (1.14.0-2) ... /var/lib/dpkg/info/python-six.postinst: 6: pycompile: not found dpkg: error processing package python-six (--configure): installed python-six package post-installation script subprocess returned error exit status 127 ErrorMessage: installed python-six package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-10-22 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: six Title: package python-six 1.14.0-2 failed to install/upgrade: installed python-six package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/six/+bug/1903484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797734] Re: slow calculator startup
ubuntu-meta (1.444) focal; urgency=medium * Refreshed dependencies * Added gnome-calculator, gnome-characters, gnome-logs to desktop-minimal-recommends, desktop-recommends and removed the snap versions * Added plymouth-theme-spinner to desktop-minimal-recommends, desktop- recommends * Removed gnome-software-plugin-snap from desktop-minimal-recommends, desktop-recommends * Removed plymouth-theme-ubuntu-logo from desktop-minimal-recommends, desktop-recommends * Removed ubuntu-software from desktop-minimal-recommends, desktop- recommends and replaced with snap:snap-store -- Ken VanDine Tue, 25 Feb 2020 16:10:18 -0500 ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-calculator (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797734] Re: slow calculator startup
^^^ The issue was resolved in Ubuntu 20.04. If you need a fix for Ubuntu 18.04 then please see comment #4. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
The one in #48 wouldn't, it wouldn't act as a sound card. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I think this works: https://smile.amazon.co.uk/gp/product/B086L2WNPG/ref=ppx_yo_dt_b_asin_title_o04_s00?ie=UTF8=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
would something like https://www.amazon.com/dp/B07J5WFPXX/ref=cm_sw_r_cp_apa_fabt1_IciRFb2QMGBDJ work? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
ubuntu 20.04, kernel Linux 5.4.0-52-generic samsung galaxy buds, cant switch to hsp/hfp thinkpad x1 carbon. laptop has intel BT 8087:0a2b, /lib/firmware/intel/ibt-12-16.sfi is used. tried to get "new" from here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tree/intel but it has same fw file as i have on my system -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
On Tue, Nov 10, 2020 at 03:12:30PM -, Sebastien Bacher wrote: >Thanks for the work but it there any work to upstream those changes? I'm >not happy to carry a sleep(1) hack in our package unless there is a >strong reason and we are working on a way to replace it by a better >solution The changes come from the Pi Foundation originally (though I've tidied them up a tiny bit). They're not interested in upstreaming them themselves, though they expressed no objections to my attempting to do so when I raised the question. I realize I'll probably have a bit of a battle on my hands with something like the patch involving sleep(1), but I would note that the sleep(1) hack is in the hciattach_bcm43xx module so it is not something that would be applied to every single Bluetooth module, only to those compatible with the BCM43xx line. While 1 second is obviously a suspiciously round number for the delay, I would further note that it's immediately after a firmware load over the controlling UART and that that UART can (in certain configurations) be the Pi's mini-UART which has some (minimal) buffering, but lacks any hardware flow control. Finally, these patches were also intended to work on the relatively slow, single core Pi Zero. Obviously we don't support the Zero, and thus it's possible *we* might be able to either do away with that sleep, or at least reduce the delay required, but given this is one-off initialization, and the delay is all of 1 second, I'm not convinced it's worth investing the time required to figure out the minimum. Also, I would assume in the interests of upstreaming the patch, the delay should be as widely applicable as possible. Anyway, I'll upstream what I can and we'll have to carry whatever's left over. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@igor871 Very interested to learn more about such Bluetooth audio cards. Years ago I had a Plantronics headset (Voyager?) that came with a USB dongle that presented itself as a USB sound card to the operating system, and it was perfect (two-way HD audio). But the dongle (Plantronics BT300 and BT600) is only compatible with Plantronics headsets from what I understand. I've looked at the Creative Labs USB Bluetooth sound cards (BT-W2 and BT-W3), but the first one requires the FastStream codec to provide high quality two way audio, which is rare, and the second just includes an analog mic that you plug into to your laptop's mic-in port - hardly a solution (I may as well use my laptop's in-built mic). They do support two way audio with your headset's mic, but only in classic HFP mode, which is what we already have. Are you aware of any other solutions? I would pay good money for a USB dongle that presents itself as a sound card to the OS and supports HFP 1.6 HD two way audio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903916] [NEW] Default keys cannot be restored from keyserver
Public bug reported: Hi all, the default keys for trustworthy software sources are gone (or at least won't display) in software-properties-gtk in Groovy Gorilla MATE. I tried to recreate them by using the button in bottom right corner. After entering system password no change seems to be done. However, keyserver de.archive.ubuntu.com seems to work for updates. Can this be fixed easily? Kind regards Stefan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 22:06:38 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-09-25 (778 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to groovy on 2020-11-01 (10 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903916 Title: Default keys cannot be restored from keyserver Status in software-properties package in Ubuntu: New Bug description: Hi all, the default keys for trustworthy software sources are gone (or at least won't display) in software-properties-gtk in Groovy Gorilla MATE. I tried to recreate them by using the button in bottom right corner. After entering system password no change seems to be done. However, keyserver de.archive.ubuntu.com seems to work for updates. Can this be fixed easily? Kind regards Stefan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 22:06:38 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-09-25 (778 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to groovy on 2020-11-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903909] Re: Audio keeps on popping and "bitcrunching" (digital output) at semi-random constant intervals
For now, after I unplugged the other one, it seems that this problem was caused due to having the external RME Fireface UFX connected into firewire, although it was not in use and not selected as my default card (I had chosen the internal built-in audio in all settings I could think of.) It probably has to do something with the kernel probing for whether not the soundcard is "still there", or some kind of similar override/priority conflict in the audio layer. Note that my previous Ubuntu build with 20.04.1LTS and the 5.4.x kernel tree did not even recognize the sound card, and as mentioned in my previous bug report considering that, my entire audio went suddenly dead with a mundane apt update. Finding absolutely no solution to that whatsoever, I just updated to 20.10 and got my audio back (AND my second, external RME sound card was visible to Ubuntu.) I have now had the external RME card unplugged for a while now and there's no more digital audio glitching. So, the fundamental issue is NOT solved, but this is the workaround for now. -- 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/1903909 Title: Audio keeps on popping and "bitcrunching" (digital output) at semi- random constant intervals Status in pulseaudio package in Ubuntu: New Bug description: This is with both of my sound cards, no matter which one I choose, the digital audio output is either popping with loud snaps or "frequency- modulating" (sounds around the same like someone would've filtered everything into a very narrow bandwidth for a couple of seconds.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 22:21:38 2020 SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-11 (0 days ago) dmi.bios.date: 06/26/2012 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-206 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-206:cvn:ct2:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-11-11T22:18:21.176026 mtime.conffile..etc.pulse.default.pa: 2020-11-11T17:20:02.886116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903909] [NEW] Audio keeps on popping and "bitcrunching" (digital output) at semi-random constant intervals
Public bug reported: This is with both of my sound cards, no matter which one I choose, the digital audio output is either popping with loud snaps or "frequency- modulating" (sounds around the same like someone would've filtered everything into a very narrow bandwidth for a couple of seconds.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 22:21:38 2020 SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-11 (0 days ago) dmi.bios.date: 06/26/2012 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-206 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-206:cvn:ct2:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-11-11T22:18:21.176026 mtime.conffile..etc.pulse.default.pa: 2020-11-11T17:20:02.886116 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903909 Title: Audio keeps on popping and "bitcrunching" (digital output) at semi- random constant intervals Status in pulseaudio package in Ubuntu: New Bug description: This is with both of my sound cards, no matter which one I choose, the digital audio output is either popping with loud snaps or "frequency- modulating" (sounds around the same like someone would've filtered everything into a very narrow bandwidth for a couple of seconds.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 22:21:38 2020 SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-11 (0 days ago) dmi.bios.date: 06/26/2012 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-206 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-206:cvn:ct2:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-11-11T22:18:21.176026 mtime.conffile..etc.pulse.default.pa: 2020-11-11T17:20:02.886116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs
This was inspected at systemd github incident-pages. Automount (executed as root) requires the target machine to be in /root/.ssh/known_hosts file. Unfortunately, the failing mount does not seem to give any helpful log or error messages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902891 Title: "Too many levels of symbolic links” error when using systemd to mount sshfs Status in systemd package in Ubuntu: Confirmed Bug description: I have asked question at askubuntu about "Too many levels of symbolic links” error when trying to use systemd to mount sshfs (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic- links-error-when-using-systemd) I have not got any responses, so I am submitting a bug report. If this is not a bug, please advice how to mount sshfs share with systemd. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:17:04 2020 InstallationDate: Installed on 2019-11-03 (367 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81H1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902891/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: rsync uses lchmod and fails in Ubuntu >= 20.10 if /proc isn't mounted
** Also affects: glibc (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu Groovy)
Importance: Undecided
Status: New
--
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
Status in glibc source package in Groovy:
New
Status in rsync source package in Groovy:
New
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 1902891] Re: "Too many levels of symbolic links” error when using systemd to mount sshfs
This was inspected at systemd github incident-pages. Automount (executed at root) requires the target machine to be in /root/.ssh/known_hosts file. Unfortunately, the failing mount does not seem to give any helpful log or error messages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1902891 Title: "Too many levels of symbolic links” error when using systemd to mount sshfs Status in systemd package in Ubuntu: Confirmed Bug description: I have asked question at askubuntu about "Too many levels of symbolic links” error when trying to use systemd to mount sshfs (https://askubuntu.com/questions/1286375/too-many-levels-of-symbolic- links-error-when-using-systemd) I have not got any responses, so I am submitting a bug report. If this is not a bug, please advice how to mount sshfs share with systemd. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:17:04 2020 InstallationDate: Installed on 2019-11-03 (367 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 81H1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-03-28 (220 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1902891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903903] Re: "Analog Stereo Duplex" profile keeps disappearing
One other thing to mention is that I have a one-line modification in the pulseaudio configuration: --- analog-output-speaker.conf 2019-03-01 21:10:29.369583080 -0800 +++ analog-output-speaker.conf 2019-03-01 21:08:36.091753082 -0800 @@ -86,7 +86,7 @@ ; else there will be a spike when plugging in headphones [Element Headphone] switch = off -volume = off +volume = merge [Element Headphone2] switch = off Without it, plugging/unplugging a headphone into the audio jack causes the volume to be set to 0. The idea for the fix picked from https://wiki.archlinux.org/index.php/MSI_GE63VR description, but instead of [Element Speaker] I had to modify [Element Headphone]. This fix worked since I first installed Kubuntu 18.10 on this laptop. -- 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/1903903 Title: "Analog Stereo Duplex" profile keeps disappearing Status in pulseaudio package in Ubuntu: New Bug description: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903903] [NEW] "Analog Stereo Duplex" profile keeps disappearing
Public bug reported: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903903 Title: "Analog Stereo Duplex" profile keeps disappearing Status in pulseaudio package in Ubuntu: New Bug description: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor
Bug stlil present in Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/378783 Title: xdg-open *.desktop opens text editor Status in GLib: New Status in gvfs: New Status in glib2.0 package in Ubuntu: Triaged Bug description: Binary package hint: xdg-utils In order to reproduce it execute "xdg-open *.desktop" (choose any .desktop file, e.g. one from /usr/share/applications). Actually your favorite text editor will open the file. Expected result: It'll be executed. Because of this bug, desktop entries with the new "#!/usr/bin/env xdg- open" shebang feature were opened in the text editor when executed from command line. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/378783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903896] [NEW] [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all
Public bug reported: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903896 Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: The sound was working just fine. I didn't work with my laptop for about half an hour and I didn't change anything that I can think of. But suddenly, there were no sounds anymore. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 21:20:12 2020 InstallationDate: Installed on 2020-10-14 (27 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: a_roudgar 1713 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [VivoBook Flip 14 TP410UF, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP410UF.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP410UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP410UF.302:bd07/26/2018:svnASUSTeKCOMPUTERINC.:pnVivoBookFlip14TP410UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP410UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook Flip 14 TP410UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797734] Re: slow calculator startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903889] [NEW] package libpng12-0 (not installed) failed to install/upgrade: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier
Public bug reported: Ubuntu v20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpng12-0 (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: libpng12-0:amd64: Install libssl1.0.0:amd64: Install xfonts-75dpi:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 11 11:24:36 2020 ErrorMessage: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libpng Title: package libpng12-0 (not installed) failed to install/upgrade: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libpng (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 libpng in Ubuntu. https://bugs.launchpad.net/bugs/1903889 Title: package libpng12-0 (not installed) failed to install/upgrade: impossible d'installer une nouvelle version de « /lib/x86_64-linux- gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type Status in libpng package in Ubuntu: New Bug description: Ubuntu v20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpng12-0 (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: libpng12-0:amd64: Install libssl1.0.0:amd64: Install xfonts-75dpi:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 11 11:24:36 2020 ErrorMessage: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libpng Title: package libpng12-0 (not installed) failed to install/upgrade: impossible d'installer une nouvelle version de « /lib/x86_64-linux-gnu/libpng12.so.0 »: Aucun fichier ou dossier de ce type UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1903889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903886] [NEW] Wrong driver is chosen
Public bug reported: When adding an Epson Stylus SX235W (and possibly others) to Ubuntu 20.04 there is no error, but prints are heavily misaligned: colors are vertically off of centimetres. Driver is epson-201108w and model is recognized as "Epson Stylus Scan 2500 foomatic/stcolor" If before installing the printer, you install the package printer- driver-gutenprint, it will be recognized as "Epson Stylus SX215+Gutenprint v5.3.3" and will work correctly. As an additional note: in my previous Ubuntu 20.04 installation the printer installed but had an error on printing and I installed the package looking at CUPS logs. In a fresh installation, no error is shown, the prints work but with totally misaligned colors. I think this is a regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 17:47:53 2020 InstallationDate: Installed on 2020-10-27 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON-Epson-Stylus-SX235: dnssd://Epson%20Stylus%20SX235._pdl-datastream._tcp.local/ Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 004: ID 062a:4180 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/EPSON-Epson-Stylus-SX235.ppd'] failed with exit code 2: grep: /etc/cups/ppd/EPSON-Epson-Stylus-SX235.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=7b9265a8-c279-4d43-852e-8f18f0c7cb8e ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2020 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 86C1 dmi.board.vendor: HP dmi.board.version: 89.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd07/31/2020:svnHP:pnHP250G7NotebookPC:pvrType1ProductConfigId:rvnHP:rn86C1:rvr89.35:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN HP 200 dmi.product.name: HP 250 G7 Notebook PC dmi.product.sku: 1F3N0EA#ABZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1903886 Title: Wrong driver is chosen Status in cups package in Ubuntu: New Bug description: When adding an Epson Stylus SX235W (and possibly others) to Ubuntu 20.04 there is no error, but prints are heavily misaligned: colors are vertically off of centimetres. Driver is epson-201108w and model is recognized as "Epson Stylus Scan 2500 foomatic/stcolor" If before installing the printer, you install the package printer- driver-gutenprint, it will be recognized as "Epson Stylus SX215+Gutenprint v5.3.3" and will work correctly. As an additional note: in my previous Ubuntu 20.04 installation the printer installed but had an error on printing and I installed the package looking at CUPS logs. In a fresh installation, no error is shown, the prints work but with totally misaligned colors. I think this is a regression. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 17:47:53 2020 InstallationDate: Installed on 2020-10-27 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lpstat: device for EPSON-Epson-Stylus-SX235: dnssd://Epson%20Stylus%20SX235._pdl-datastream._tcp.local/ Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 004: ID 062a:4180 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G7 Notebook PC Papersize: a4 PpdFiles: Error:
[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483
I attached the core dump, like you asked ** Attachment added: "core.ssh.0.2ec456d6193048749c85e045f700231e.952027.1605108402.lz4" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1903516/+attachment/5433492/+files/core.ssh.0.2ec456d6193048749c85e045f700231e.952027.1605108402.lz4 -- 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/1903516 Title: aborted (core dumped) when using ConnectTimeout > 2147483 Status in openssh package in Ubuntu: Incomplete Bug description: The ssh client fails with the message "Aborted (core dumped)" when setting the ConnectTimeout to 2147484 or higher. lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 docker container) openssh-client version: 1:8.2p1-4ubuntu0.1 I expected that either the connect timeout would be used correctly, or that it would fail with a proper error message saying the connect timeout can't be higher than 2147483. What happened: $ ssh -o "ConnectTimeout=2147484" localhost Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1903516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483
Thank you for taking the time to file a bug report. Could you please provide the core dump file to help us investigate your problem? Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1903516 Title: aborted (core dumped) when using ConnectTimeout > 2147483 Status in openssh package in Ubuntu: Incomplete Bug description: The ssh client fails with the message "Aborted (core dumped)" when setting the ConnectTimeout to 2147484 or higher. lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 docker container) openssh-client version: 1:8.2p1-4ubuntu0.1 I expected that either the connect timeout would be used correctly, or that it would fail with a proper error message saying the connect timeout can't be higher than 2147483. What happened: $ ssh -o "ConnectTimeout=2147484" localhost Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1903516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols
** Tags added: fr-920 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Bug description: Please backport the following bugfix into Ubuntu LTS: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e Some relevant historic links: Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736 glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960 In s390 kernel context, this bug manifests itself as random errors and infinite loops, so it's fairly severe. These are the current versions of binutils: Package binutils xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x xenial-updates (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4 [security]: amd64 i386 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x bionic-updates (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x focal (20.04LTS) (devel): GNU assembler, linker and binary utilities 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x groovy (devel): GNU assembler, linker and binary utilities 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The patch applies fine to 2.26 and 2.30 (except for tests, but we don't need them). We don't need it on 2.32+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit
** Tags added: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1874824 Title: pgrep reports error "cannot allocate" when run without stack limit Status in procps package in Ubuntu: Confirmed Status in procps package in Debian: New Bug description: If you have no stack limit (ulimit -S -s unlimited), any pgrep call will fail with an error: > pgrep vim pgrep: cannot allocate 4611686018427387903 bytes If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very slow: > time pgrep vim 2196 real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444 The relevant upstream bug report could be: https://gitlab.com/procps-ng/procps/-/issues/152 Archlinux bug report: https://bugs.archlinux.org/task/66093 procps: Installed: 2:3.3.16-1ubuntu2 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903849] [NEW] vim ftbfs
Public bug reported: see https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1 blocking the perl transition ** Affects: vim (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs rls-hh-incoming ** Changed in: vim (Ubuntu) Status: New => Confirmed ** Changed in: vim (Ubuntu) Importance: Undecided => High ** Tags added: ftbfs rls-hh-incoming ** Description changed: see https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1 + + blocking the perl transition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1903849 Title: vim ftbfs Status in vim package in Ubuntu: Confirmed Bug description: see https://launchpad.net/ubuntu/+source/vim/2:8.2.1913-1ubuntu1 blocking the perl transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1903849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903818] Re: [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1903818 Title: [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Only dummy output, plugged headphones doesn't work neither, but bluetooth speaker does work, after the bluetooth speaker has been connected, the analog output appears ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: basile 1806 F pulseaudio /dev/snd/controlC0: basile 1806 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 09:49:13 2020 InstallationDate: Installed on 2020-11-04 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: basile 1806 F pulseaudio /dev/snd/controlC0: basile 1806 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-11T09:44:06.857625 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903829] Re: laptop screen turns off when I connect an external monitor
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903829 Title: laptop screen turns off when I connect an external monitor Status in xorg package in Ubuntu: New Bug description: When I connect the hdmi cable from my monitor the laptop screen starts to darken this only happens when I connect the external monitor. when I switch to mirror the external monitor starts flickering and the laptop monitor turns off completely. When I switch to join displays, the laptop monitor turns off completely and the external monitor stays on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 02:50:28 2020 DistUpgraded: 2020-11-11 02:37:02,636 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2020-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=c86cce5a-02e9-41bc-9097-dd5e168a82d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-11 (0 days ago) dmi.bios.date: 12/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0Y2FDT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd12/23/2019:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0Y2FDT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1903829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS
I can confirm this problem for Ubuntu 20.04 and 20.10 on a Thinkpad X260. The bluetooth button in the Bluetooth settings does nothing after it is automatically turned off. However, I can enable Bluetooth again by turning it off and on again Bluetooth in the menu top bar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1774640 Title: Bluetooth turns off automatically Ubuntu 18.04 LTS Status in bluez package in Ubuntu: Confirmed Bug description: Whenever I start up my laptop and connect my JBL-speaker, the device stays connected. However, when I turn de speaker off, and try to reconnect to the speaker, the Bluetooth automatically turns off. I then need to restart my laptop and then only Bluetooth works again. --- ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-27 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X555LAB Package: bluez 5.48-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.503 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1A:7D:DA:71:0A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:55347 acl:67 sco:0 events:7591 errors:0 TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1774640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903829] [NEW] laptop screen turns off when I connect an external monitor
You have been subscribed to a public bug: When I connect the hdmi cable from my monitor the laptop screen starts to darken this only happens when I connect the external monitor. when I switch to mirror the external monitor starts flickering and the laptop monitor turns off completely. When I switch to join displays, the laptop monitor turns off completely and the external monitor stays on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 02:50:28 2020 DistUpgraded: 2020-11-11 02:37:02,636 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0839] InstallationDate: Installed on 2020-11-11 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Latitude 3490 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=c86cce5a-02e9-41bc-9097-dd5e168a82d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-11-11 (0 days ago) dmi.bios.date: 12/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0Y2FDT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd12/23/2019:svnDellInc.:pnLatitude3490:pvr:rvnDellInc.:rn0Y2FDT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3490 dmi.product.sku: 0839 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 -- laptop screen turns off when I connect an external monitor https://bugs.launchpad.net/bugs/1903829 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903818] [NEW] [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
You have been subscribed to a public bug: Only dummy output, plugged headphones doesn't work neither, but bluetooth speaker does work, after the bluetooth speaker has been connected, the analog output appears ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: basile 1806 F pulseaudio /dev/snd/controlC0: basile 1806 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 09:49:13 2020 InstallationDate: Installed on 2020-11-04 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: basile 1806 F pulseaudio /dev/snd/controlC0: basile 1806 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-11T09:44:06.857625 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- [Swift SF314-42, ATI R6xx HDMI, Digital Out, HDMI] No sound at all https://bugs.launchpad.net/bugs/1903818 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I am having the same issue with ubuntu 20.04 - super annoying! I even bought new headphones (the same model) but having the same troubles... Bose support cannot really help and they are "not aware of the issue" -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899262] Re: Broken dbus GetAll message to wpa supplicant interface properties
** Changed in: wpa (Ubuntu) Importance: Undecided => High ** Changed in: wpa (Ubuntu) Status: New => In Progress -- 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/1899262 Title: Broken dbus GetAll message to wpa supplicant interface properties Status in wpa package in Ubuntu: In Progress Bug description: dbus-send is able to read the properties of interface using GetAll. Those information include interface name, status, encryption method, etc. The regression was introduced when someone try to have the Station attribute supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+subscriptions -- Mailing list: https://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 1903048] Re: [SRU] Bluetooth won't activate on the pi 400
Hi, I implemented the fix detailed in the test case yesterday and the bug still existed. I've double checked again this morning and done a full-upgrade just to check nothing new was waiting and the bug still exists on this Mate 20.10 install. Yesterday after applying the fix I started getting random "System problem detected, report this?" popups but none so far today. Blueman Applet is set as a startup item and both blueman-applet and blueman-tray appear as running processes but running blueman-manager or blueman-adapters from the command line both fail with the message 'Blueman applet needs to be running' The Bluetooth panel item isnt shown. OS: Ubuntu MATE 20.10 aarch64 Host: Raspberry Pi 400 Rev 1.0 Kernel: 5.8.0-1007-raspi Tony On 11/11/2020 04:32, Launchpad Bug Tracker wrote: > This bug was fixed in the package bluez - 5.55-0ubuntu2 > > --- > bluez (5.55-0ubuntu2) hirsute; urgency=medium > >* Added patches from the Raspberry Pi Foundation > - d/p/raspi-bcm43xx-load-firmware.patch > - d/p/raspi-bcm43xx-3wire.patch > - d/p/raspi-cypress-305-bdaddr.patch >* These patches fix Bluetooth operation on the Pi 400 (LP: #1903048) > > -- Dave Jones Thu, 05 Nov 2020 13:39:07 > + > > ** Changed in: bluez (Ubuntu Hirsute) > Status: Fix Committed => Fix Released > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903048 Title: [SRU] Bluetooth won't activate on the pi 400 Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Hirsute: Fix Released Bug description: [Impact] Without these patches, Bluetooth is inoperable on the recently released Raspberry Pi 400. [Test Case] * Boot the Ubuntu Desktop for Pi image on a Pi 400. * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is not enabled and attempting to activate it fails * sudo add-apt-repository ppa:waveform/pi-bluetooth * sudo apt update * sudo apt install bluez * sudo reboot * Start the Settings application and switch to the Bluetooth tab * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, mobile phones, headphones, etc.) can connect and operate correctly [Regression Potential] Extremely low (on groovy in particular, this has the same version of bluez as hirsute). The only significant risk is to non-Pi platforms or dongles which also use the Broadcom 43xx (or Cypress 305) chips for Bluetooth which might be inadvertently affected by these patches. [Original Description] The new Pi 400 has a slightly different Wifi/BT chip to the Pi4. Whilst wifi works happily, Bluetooth fails to operate. This doesn't appear to be an issue with either the firmware (the latest versions from upstream Raspbian have been tried), or the kernel (a known-good raspi kernel has been tested under Ubuntu), but with Bluez itself. Specifically, tracing the initialization with btmon on Raspbian and Ubuntu, the stack consistently fails when attempting to "Set Default PHY" on the latter. Curiously, under Ubuntu the adapter also appears to lack a MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols
According to the affected binutils versions and the communication with IBM it's sufficient to get this fixed in Bionic. ** Also affects: binutils (Ubuntu) Importance: Undecided Status: New ** No longer affects: binutils-s390x-cross (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Importance: Undecided => High ** Also affects: binutils (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: binutils (Ubuntu) Status: New => Fix Released ** Changed in: binutils (Ubuntu Bionic) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Changed in: ubuntu-z-systems Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1903814 Title: [binutils] Prevent GOT access rewrite for certain symbols Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Bionic: New Bug description: Please backport the following bugfix into Ubuntu LTS: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e Some relevant historic links: Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736 glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960 In s390 kernel context, this bug manifests itself as random errors and infinite loops, so it's fairly severe. These are the current versions of binutils: Package binutils xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386 2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x xenial-updates (devel): GNU assembler, linker and binary utilities 2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4 [security]: amd64 i386 2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x bionic-updates (devel): GNU assembler, linker and binary utilities 2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x focal (20.04LTS) (devel): GNU assembler, linker and binary utilities 2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x groovy (devel): GNU assembler, linker and binary utilities 2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x The patch applies fine to 2.26 and 2.30 (except for tests, but we don't need them). We don't need it on 2.32+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903808] Re: GSettings like mouse acceleration are not restored after suspend
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1899509, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1899509 Mouse/touchpad settings not applied on hotplug/reconnect -- 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/1903808 Title: GSettings like mouse acceleration are not restored after suspend Status in xorg package in Ubuntu: New Bug description: I have customised some options like mouse acceleration and compose keys using gsettings. # Disable mouse acceleration gsettings set org.gnome.desktop.peripherals.mouse accel-profile flat gsettings set org.gnome.desktop.peripherals.mouse speed 0 # Enable Compose key gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps']" After around end of August, those settings were not active anymore after suspending. A workaround was to open gnome-tweaks and change the settings to another value and back to the desired value again. If there is something I can do to locate the problem, please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..3c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3c: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 06:38:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-51-generic, x86_64: installed evdi, 1.7.0, 5.4.0-52-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2278] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2278] InstallationDate: Installed on 2020-05-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N3S4AH00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-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: 04/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S4AH00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET87W(1.65):bd04/07/2020:svnLENOVO:pn20N3S4AH00:pvrThinkPadT490:rvnLENOVO:rn20N3S4AH00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S4AH00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1898447] Re: HDMI sound output disappears after sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 ** This bug has been marked a duplicate of bug 1888598 pulseaudio breaks hdmi audio on sleep/wake in ubuntu 20.10 -- 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/1898447 Title: HDMI sound output disappears after sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am using an Nvidia graphics card with HDMI output. The sound output choice for HDMI is missing from either pavucontrol or the GNOME settings sound settings after waking the computer up from sleep. Running `pacmd list-cards` does show the HDMI sound output listed. I can bring the output back as a choice if I run `pulseaudio -k`, but I will lose the choice to select this output if I put the computer to sleep, leaving me only with the S/PDIF output from my motherboard. I didnt see this issue prior to what I suspect was an `apt upgrade`. Description: Ubuntu 20.04.1 LTS Release: 20.04 Kernel: 5.4.0-48-generic Desktop Environment: GNOME 3.36.3 pulseaudio: Installed: 1:13.99.1-1ubuntu3.6 Candidate: 1:13.99.1-1ubuntu3.6 Version table: *** 1:13.99.1-1ubuntu3.6 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages Hardware Info: CPU: AMD Ryzen 9 3950x GPU: Nvidia RTX 2080ti (Driver 450.66 ) Motherboard: Gigabyte X570 AORUS MASTER --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umayr 4915 F pulseaudio /dev/snd/pcmC0D3p: umayr 4915 F...m pulseaudio /dev/snd/controlC1: umayr 4915 F pulseaudio /dev/snd/controlC2: umayr 4915 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-12 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Tags: focal Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903808] Re: GSettings like mouse acceleration are not restored after suspend
*** This bug is a duplicate of bug 1899509 *** https://bugs.launchpad.net/bugs/1899509 ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903808 Title: GSettings like mouse acceleration are not restored after suspend Status in xorg package in Ubuntu: New Bug description: I have customised some options like mouse acceleration and compose keys using gsettings. # Disable mouse acceleration gsettings set org.gnome.desktop.peripherals.mouse accel-profile flat gsettings set org.gnome.desktop.peripherals.mouse speed 0 # Enable Compose key gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps']" After around end of August, those settings were not active anymore after suspending. A workaround was to open gnome-tweaks and change the settings to another value and back to the desired value again. If there is something I can do to locate the problem, please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..3c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3c: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 06:38:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-51-generic, x86_64: installed evdi, 1.7.0, 5.4.0-52-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2278] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2278] InstallationDate: Installed on 2020-05-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N3S4AH00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-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: 04/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S4AH00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET87W(1.65):bd04/07/2020:svnLENOVO:pn20N3S4AH00:pvrThinkPadT490:rvnLENOVO:rn20N3S4AH00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S4AH00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1903808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903808] [NEW] GSettings like mouse acceleration are not restored after suspend
You have been subscribed to a public bug: I have customised some options like mouse acceleration and compose keys using gsettings. # Disable mouse acceleration gsettings set org.gnome.desktop.peripherals.mouse accel-profile flat gsettings set org.gnome.desktop.peripherals.mouse speed 0 # Enable Compose key gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps']" After around end of August, those settings were not active anymore after suspending. A workaround was to open gnome-tweaks and change the settings to another value and back to the desired value again. If there is something I can do to locate the problem, please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..3c.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3c: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 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 06:38:24 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-51-generic, x86_64: installed evdi, 1.7.0, 5.4.0-52-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2278] Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2278] InstallationDate: Installed on 2020-05-02 (192 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20N3S4AH00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-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: 04/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET87W (1.65 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3S4AH00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2IET87W(1.65):bd04/07/2020:svnLENOVO:pn20N3S4AH00:pvrThinkPadT490:rvnLENOVO:rn20N3S4AH00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3S4AH00 dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 -- GSettings like mouse acceleration are not restored after suspend https://bugs.launchpad.net/bugs/1903808 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
