[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
Assuming the config file is correct, the next step would be to report the problem to the developers at: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues and then tell us the new issue ID. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: Incomplete Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
Yes PulseAudio should be able able to handle it but it also looks like the cause of this bug. Please try temporarily moving that file to a different directory and logging in again. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: Incomplete Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
After the patch is merged to upstream (at least linux-next), I will backport it to ubuntu kernel. @Michael, BTW, what version of sof-firmware did you install? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899361] Re: udisk prevent disk from standby, standby timer is broken
@John Reid, sir, your comment is pure gold. My HDDs haven't slept in a LOOONG time. I wouldn't mind it if it wasn't for a fanless, HTPC NAS... that is in my living room. Thank you. :~$ sudo hdparm -C /dev/sda /dev/sda: drive state is: standby :~$ sudo hdparm -C /dev/sdb /dev/sdb: drive state is: standby -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1899361 Title: udisk prevent disk from standby, standby timer is broken Status in udisks package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: It seems udisks tries to access my HDD every 10 minute. So when I set standby timer less than 10 minutes, It can't go to standby. Probably the disk shouldn't be checked when it's on standby. This bug has been reported before (+bug #1281588) and seems to be fixed, But I'm experiencing this again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udisks2 2.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE CustomUdevRuleFiles: wolfram-vernierlink-libusb.rules Date: Sun Oct 11 19:38:48 2020 InstallationDate: Installed on 2020-10-02 (8 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook S15 X510UF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=2dccc476-4ac0-4ab2-9742-bde2ad020de3 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X510UF.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X510UF 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.:bvrX510UF.304:bd09/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBookS15X510UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX510UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook S dmi.product.name: VivoBook S15 X510UF 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/udisks/+bug/1899361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938096] [NEW] touchpad lagging after resume from suspend
Public bug reported: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Description changed: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 - - Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. + Right after a clean reboot, the touchpad works fine. No issues + whatsoever. But after resuming from even its first suspend after a clean + boot, the touchpad feels less responsive, choppy or even laggy. Very + strange. I have tried removing and re-inserting some HID kernel modules, + "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found + anything that fixes it yet. The trackpoint works flawlessly all the + time, so that is the current backup when I don't have an external mouse + connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. + + The journal has a lot of these errors after resuming: + + juli 27 00:17:41 machine touchegg[1003]: libinput error: event11 - + SYNA8009:00 06CB:CE57 Touchpad: kernel bug: Touch jump detected and + discarded. ** Description changed: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the latest 5.13.5 and 5.14.0rc2 kernels from the mainline PPA, and even tried bumping the libinput10 to 1.18.0 from the impish repos today to no avail I'm afraid. - - The journal has a lot of these errors after resuming: - - juli 27 00:17:41 machine touchegg[1003]: libinput error: event11 - - SYNA8009:00 06CB:CE57 Touchpad: kernel bug: Touch jump detected and - discarded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: touchpad lagging after resume from suspend Status in libinput package in Ubuntu: New Bug description: Hardware: Thinkpad X1 Carbon, 9th generation Touchpad: SYNA8009:00 06CB:CE57 Right after a clean reboot, the touchpad works fine. No issues whatsoever. But after resuming from even its first suspend after a clean boot, the touchpad feels less responsive, choppy or even laggy. Very strange. I have tried removing and re-inserting some HID kernel modules, "psmouse", and setting i915.psr_enabled=0 in kernelstubs. Haven't found anything that fixes it yet. The trackpoint works flawlessly all the time, so that is the current backup when I don't have an external mouse connected. My installed OS is Pop!_Os 21.04, but I have tested and confirmed this on a live USB with Ubuntu 21.04 as well and the issue do present itself. I have also tried upgrading to the
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Intel merged the bug fix for this issue two hours ago: https://github.com/thesofproject/linux/pull/3059 When will this get pushed out in the standard Ubuntu 21.04 kernel update? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Yes On 7/26/21 2:05 PM, Perry Steger wrote: > Excellent, Michael! Sound in and out? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Excellent, Michael! Sound in and out? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938077] [NEW] drag'n'drop file to terminal adds newline before closing quote
Public bug reported: When I drag and drop a file from Krusader to gnome-terminal, it quotes the filename with single quotes but adds a newline before the closing quote. I then have to do Ctrl-C to correct the quoting before I can go on with my command. In case it's not clear, here is how it looks in Terminal: $ file '/tmp/20180102_161315.jpg > ' This however doesn't happen when drag'n'dropping from the Files application. And it doesn't happen either when dropping the file from Krusader into Konsole. Ubuntu 20.04.2, gnome-terminal 3.36.2-1ubuntu1~20.04, Krusader 2.7.2, KDE Frameworks 5.68.0, Qt 5.12.8 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938077 Title: drag'n'drop file to terminal adds newline before closing quote Status in gnome-terminal package in Ubuntu: New Bug description: When I drag and drop a file from Krusader to gnome-terminal, it quotes the filename with single quotes but adds a newline before the closing quote. I then have to do Ctrl-C to correct the quoting before I can go on with my command. In case it's not clear, here is how it looks in Terminal: $ file '/tmp/20180102_161315.jpg > ' This however doesn't happen when drag'n'dropping from the Files application. And it doesn't happen either when dropping the file from Krusader into Konsole. Ubuntu 20.04.2, gnome-terminal 3.36.2-1ubuntu1~20.04, Krusader 2.7.2, KDE Frameworks 5.68.0, Qt 5.12.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1938077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Got the kernel compiled this morning with the patch and I have sound. (5.14-rc2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937922] Re: gtk4 not built for i386
@Steve: I suppose this is now a request to add gtk4 to the whitelist, so I subscribed ubuntu-archive. I can't tell if any of the current i386 packages will use gtk4. But ibus needs gtk4 when building to be able to enable gtk4 support, and it would be convenient to not need to special case i386 and with that create a permanent Ubuntu/Debian delta. So at least for now it would be great if gtk4 could be added to the list explicitly. ** Changed in: ibus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: New Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937922] Re: gtk4 not built for i386
** Tags removed: regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: Incomplete Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937922] Re: gtk4 not built for i386
"regression-update" is a tag for SRUs, not appropriate here. Otherwise, nothing in this bug report has flagged it to the attention of the ubuntu-archive team, who are the only people that can add packages to the i386 whitelist. The general process we've been using is to ask folks on #ubuntu-release, but if you're going to file a bug about the i386 whitelist, please subscribe ubuntu-archive. Do we need gtk4 explicitly added to the whitelist, or will something else that's currently built on i386 in the archive be using gtk4 in the impish release? (For reference, gtk+3.0 is not manually whitelisted for i386.) ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: Incomplete Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
thanks @mblack154 can you try the patch in a312717 https://github.com/thesofproject/linux/commit/a312717b3d2a911a103e09dd313e533bb58d0dd0 You may need to rename the RT711_JD2 as SOF_RT711_JD_SRC_JD2 since a recent commit changed the JD definition. https://lore.kernel.org/alsa-devel/20210712203240.46960-7-pierre-louis.boss...@linux.intel.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1708933] Re: Can't add a Microsoft account to GNOME Online Accounts
After logging in, I see the "windows Network" added under Files > Other Locations. However, it has no access to the account. Gives the following error when clicking on it: "Unable to access location, Failed to retrieve share list from server: No such file or directory" Google account is added successfully though! Any solution? ** Attachment added: "Screenshot from 2021-07-26 18-20-53.xcf" https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+attachment/5513746/+files/Screenshot%20from%202021-07-26%2018-20-53.xcf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1708933 Title: Can't add a Microsoft account to GNOME Online Accounts Status in gnome-online-accounts package in Ubuntu: New Bug description: In artful: 1) Open Settings->Online Accounts 2) Click on "Microsoft" under "Add an account" 3) See an authorization window pop up, enter my user/password for Microsoft Live 4) Click next, see it ask whether it's OK to give GNOME various permissions 5) Click yes, see the window disappear But at this point, no Microsoft account appears in the active-accounts section. It just seems to have closed the window and done nothing. Is there a way to get better logging for this and try again? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 6 10:03:55 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-09 (1669 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: Upgraded to artful on 2017-07-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1708933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Please don't modify that in /etc/grub.d, set GRUB_RECORDFAIL_TIMEOUT=5 in the /etc/default/grub file (or in an /etc/default/grub.d snippet). /etc/grub.d file changes are last resort, that file changes and incorporating those changes with your own ones will be annoying. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: Invalid Status in libx11 package in Ubuntu: Invalid Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias:
[Desktop-packages] [Bug 1737278] Re: gvfsd-dav crashed with SIGSEGV in g_closure_invoke()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1737278 Title: gvfsd-dav crashed with SIGSEGV in g_closure_invoke() Status in gvfs package in Ubuntu: Confirmed Bug description: It seems that gvfsd-dav crashed. I played with it when connecting to a dav created by enabling file sharing on the local machine. I turned it off, it must have crashed after that, but I only got the report now. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.34.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 9 01:11:06 2017 ExecutablePath: /usr/lib/gvfs/gvfsd-dav InstallationDate: Installed on 2017-12-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/gvfs/gvfsd-dav --spawner :1.15 /org/gtk/gvfs/exec_spaw/12 SegvAnalysis: Segfault happened at: 0x560529675aad:mov(%rax),%rax PC (0x560529675aad) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gvfsd-dav crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to bionic on 2017-12-08 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1737278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937922] Re: gtk4 not built for i386
https://irclogs.ubuntu.com/2021/07/26/%23ubuntu-desktop.html#t12:23 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: New Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
As to sshd_config: I will, when the case arises again. Unfortunately, I don't use sshd in my boxes on a regular basis and so often discover only changes that possibly happened a long time ago. I remember a nasty change from "PasswordAuthentication no" to "#PasswordAuthentication yes", but honestly it was quite some time ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: Invalid Status in libx11 package in Ubuntu: Invalid Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14
[Desktop-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
As to grub.cfg:
I set GRUB_TIMEOUT=5 in my /etc/default/grub, but the timeout for efi
was reset to 30 on every update. I didn't know that files in
/etc/default/grub.d are supposed to be changed, but I now changed
if [ \$grub_platform = efi ]; then
set timeout=${GRUB_RECORDFAIL_TIMEOUT:-30}
if [ x\$feature_timeout_style = xy ] ; then
set timeout_style=menu
fi
fi
in /etc/grub.d/00_header to ... GRUB_RECORDFAIL_TIMEOUT:-5 ... and hope
that this helps in the future.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1929854
Title:
Vital and critical configuration files get overridden by system
updates without warning
Status in grub2 package in Ubuntu:
Invalid
Status in libx11 package in Ubuntu:
Invalid
Status in openssh package in Ubuntu:
Incomplete
Bug description:
• In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines
of special compose keys defined.
• In my /boot/grub/grub.cfg I have a very complicated special setup for my
various boot configurations, and a 5-sec timout for my EFI-config.
• My /etc/ssh/sshd_config contains a well-balanced configuration
All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING
or ASKING BACK by ubuntu system setups (discover).
I set all of them to read-only by root and no-access for group and
other users, but they still get overridden by every other system
update. I even have a shutdown process in place which should actually
make sure that changes to these files are reverted by writing a backup
copy over any newly installed override — unfortunately, everything I
did to run either a custom shutdown process or a startup process with
systemd turned out to not work and be a nightmare to make work.
How somebody could be as bold as to override vital configuration files
like this without even asking for consent is one of the strange
miracles in this world which I'll probably never understand. However,
if "ubuntu" is really what it translates to, it should take a little
bit more care about pre-existing configurations on systems on which it
is set up and running well — until one system update suddenly
jeopardizes the functioning of the entire system. I'm pretty sure
these are not the only configuration files which are carelessly just
overridden. They're just the ones every other update breaks my system
and inflinges on my the costs of hours of research until I find out
that — of course — it was an overridden critical system configuration
again. The really mean thing is that you don't notice anything when
you run the update … only next time you start your system and of
course are not aware anymore that you did a system update, the new
(absolutely wrong and/or insufficent) settings are in place and shoot
you in the leg.
Take an example from gentoo's etc-update feature which lets you merge
new configuration files with pre-existing ones using a diff3-update.
I went away from gentoo for other reasons, but I always praised that
feature.
Please make sure immediately that critical configuration files do not
get overridden if they are non-writable by root, and then gradually
introduce a system that merges changes to configuration files with the
current situation on the target system. Or at least present the
configs that would be changed in a particular directory, so that
anybody who is interested in preserving local settings could merge
them in a suitable way.
Thanks
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature:
[Desktop-packages] [Bug 1937922] Re: gtk4 not built for i386
I think wasn't built as per missing pango build on i386, that's now fixed so shoudl just trigger a rebuild of gtk4 itself. Probably though an upload though. ** Tags added: regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1937922 Title: gtk4 not built for i386 Status in ibus package in Ubuntu: New Bug description: I'm trying to enable GTK 4 when building ibus: https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages Up to now ibus has been built also on i386, but gtk4 has not been built on that arch, so the i386 build fails due to missing build dependencies. Is it time to stop building ibus on i386? Or can we build gtk4 on i386 (it was successfully built on Debian's i386)? At least some step needs to be taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879043] Re: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()
*** This bug is a duplicate of bug 184 *** https://bugs.launchpad.net/bugs/184 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1879043 Title: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background() Status in gnome-shell package in Ubuntu: Confirmed Bug description: It might be bug 184. This is a new installation. During the installation After each change I made Suspend and restarted the computer and checked if gnome-shell had crashed. Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab, Applications Menu, OpenWeather and Dash to Panel without crash. The last thing I did before the crash was to "install" Gmail and Google Calender and put all my favorite applications in the panel. Left the computer to suspend, after 15 minutes, and restarted the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 16 11:11:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800043] Re: nautilus cannot write on nfs file share base dir
Same here with Mint 20.2 (Ubuntu 20.04) and Nemo 5.0.3 and Nautilus 3.36.3. With PCManFM 1.3.1 and command line no issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800043 Title: nautilus cannot write on nfs file share base dir Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) Nautilus is not able to perform any write access to it (write, delete, make new directory,...). I can do all of this operations by using shell commands (touch, cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if I start it with root privileges. Even stranger is the following: even though nautilus cannot write into the mounted shares it is able to write into its subfolders. This bug seems to affect others as well: https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share Ubuntu version: 18.04.1 LTS - amd64 Nautilus version: 1:3.26.4-0~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1800043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
I created the custom default.pa. It adds only two commands when compared to default /etc/pulse/default.pa: load-module module-native-protocol-tcp auth-ip-acl=192.168.100.51 set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo The first one I need for network access of pulseaudio from a separate server (https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Network/#authorization) and the second one sets up the profile for the integrated alsa_card.pci-_00_1b.0 to use it only for input. I use an USB device for output. Pulseaudio should be able to handle these. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800043] Re: nautilus cannot write on nfs file share base dir
I am having the same issue with Ubuntu 20.04. I am using version GNOME nautilus 3.36.3. Via the command line I have no issue. The problem only seems to be in nautilus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1800043 Title: nautilus cannot write on nfs file share base dir Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) Nautilus is not able to perform any write access to it (write, delete, make new directory,...). I can do all of this operations by using shell commands (touch, cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if I start it with root privileges. Even stranger is the following: even though nautilus cannot write into the mounted shares it is able to write into its subfolders. This bug seems to affect others as well: https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share Ubuntu version: 18.04.1 LTS - amd64 Nautilus version: 1:3.26.4-0~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1800043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
I enable -proposed and do a dist-upgrade, made sure 21.0.3-0ubuntu0.2 is
installed, then reboot and run stress-ng:
$ stress-ng --stack 0 --timeout 300
stress-ng: info: [1936] dispatching hogs: 8 stack
stress-ng: info: [1936] successful run completed in 300.88s (5 mins, 0.88 secs)
The desktop session didn't crash so it's still alive.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
Triaged
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
Fix Committed
Status in mesa source package in Hirsute:
Fix Committed
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936643] Re: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview
And proposed the fix for Ubuntu again: https://salsa.debian.org/gnome- team/gnome-shell/-/merge_requests/51 ** No longer affects: mutter (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1936643 Title: Logging in to GNOME 40.2.0 causes desktop icon extension to show as application in Activities overview Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Opinion Bug description: In Ubuntu 21.10 Impish Indri, I have done today's updates, including GNOME 40, and when I rebooted, I saw the desktop icons in the Activities overview that has the grey gears icon and the gibberish name. However, when I clicked on it, I'm taken to the desktop. When I open the Activities overview again, that "application" didn't show up. I suspect that this "application" came from a GNOME extension that handles desktop icons, called gnome-shell-extension-desktop-icons-ng. Because I thought that it loaded AFTER the Activities overview opened at log in. This repeats every time I reboot or just log off and log back in. Steps to reproduce: 1. Update the Impish system to the latest version 2. Reboot 3. Log in Expected results: The "application" that came from the desktop icon shell extension doesn't appear in the Activities overview Actual results: This "application" shows up in the overview with the grey gears icon and the gibberish name every time a user signs in to the new GNOME 40 desktop lsb_release -rd: Description: Ubuntu Impish Indri (development branch) Release: 21.10 apt-cache policy gnome-shell: gnome-shell: Installed: 40.2-1ubuntu1 Candidate: 40.2-1ubuntu1 Version table: *** 40.2-1ubuntu1 500 500 http://sy.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status If there is any more information needed, let me know. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 16 15:07:53 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-02-02 (163 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1936643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937988] Re: The image is distrorted while use iGPU rendering and output via AMD GPU
@Jeremy, this is the PPA for testing on Focal: https://launchpad.net/~xueshengyao/+archive/ubuntu/mesa based on the latest focal-updates' version: 20.2.6-0ubuntu0.20.04.1 mesa (20.2.6-0ubuntu0.20.04.1dri1) focal; urgency=medium * test build for backport upstream merge request: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942 see patches/loader_add_dri_image_use_scanout.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937126] Re: bug found
Please choose one of those issues for this bug to be about. Each problem should get a separate bug. Please also run: gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text file here, as well as a screenshot or photo of the problem. --- Escolha um desses problemas para tratar este bug. Cada problema deve ter um bug separado. Execute tamb�m: gsettings list-recursively org.gnome.shell > settings.txt e anexe o arquivo de texto resultante aqui, bem como uma captura de tela ou foto do problema. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1937126 Title: bug found Status in gnome-shell package in Ubuntu: Incomplete Bug description: I downloaded version 21.04 of ubuntu, then I realized that when I downloaded the gnome shell tweaking tool, I realized that when I changed the theme of the dock and added in the top bar the option to show the option of locations on the system, it leaves my language after performing some accesses in the application menu this behavior appears. I also noticed that by accessing the applications menu the dock that I modified to appear in the lower corner of the screen is now also displayed on the left side of my monitor. I apologize for the English, but I live in Brazil and I am not fluent in this language. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 16:23:56 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a] InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN50WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.ec.firmware.release: 1.50 dmi.modalias: dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937126] Re: bug found
Bom dia!, na verdade o bug em si n�o est� no xorg mas sim na wayland, pe�o desculpa pelo erro na escolha no formul�rio. Basicamente ap�s um per�odo de sess�o logado o painel na barra superior onde adicionei uma extens�o para me mostrar os locais em meu computador deixa de ficar traduzido para o portugu�s-br e volta para o ingl�s. Observei tamb�m de que quando isso ocorre acontece um bug na doca o qual tamb�m modifiquei por extens�o e a deixei na parte inferior da tela, contudo ao acessar o menu de aplicativos ela acaba aparecendo na parte esquerda do meu monitor ficando vis�veis duas docas uma abaixo e uma ao lado. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1937126 Title: bug found Status in gnome-shell package in Ubuntu: Incomplete Bug description: I downloaded version 21.04 of ubuntu, then I realized that when I downloaded the gnome shell tweaking tool, I realized that when I changed the theme of the dock and added in the top bar the option to show the option of locations on the system, it leaves my language after performing some accesses in the application menu this behavior appears. I also noticed that by accessing the applications menu the dock that I modified to appear in the lower corner of the screen is now also displayed on the left side of my monitor. I apologize for the English, but I live in Brazil and I am not fluent in this language. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 16:23:56 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:3f1a] InstallationDate: Installed on 2021-07-17 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=fce98fbf-751a-4700-bbe5-628c5a913425 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 1.50 dmi.bios.vendor: LENOVO dmi.bios.version: ASCN50WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IWL dmi.ec.firmware.release: 1.50 dmi.modalias: dmi:bvnLENOVO:bvrASCN50WW:bd11/24/2020:br1.50:efr1.50:svnLENOVO:pn81S9:pvrLenovoIdeaPadS145-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IWL: dmi.product.family: IdeaPad S145-15IWL dmi.product.name: 81S9 dmi.product.sku: LENOVO_MT_81S9_BU_idea_FM_IdeaPad S145-15IWL dmi.product.version: Lenovo IdeaPad S145-15IWL dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
@Kai-Heng Feng: Yes, but I meant to ask if the *additional* dependencies (gir1.2-clutter-gst-3.0 and gir1.2-gtkclutter-1.0) are required, i.e. is there a need to change the gnome-shell-extension-desktop-icons uploads as well? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
A quick workaround is to install the gnome-terminal version >= 3.38.2. E.g. 3.38.3 from debian repos here: https://packages.debian.org/bullseye/gnome-terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal source package in Hirsute: Confirmed Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937957] Re: external hyperlink keyboard freeze
** Description changed: When no FireFox windows are currently open and an external hyperlink, - say from a pdf or doc, is used then the created window freezes the - keyboard. New tabs as well as new opened windows experience the same - issue as long as the original window is still open. Windows key + F9 and - Windows key + Shift have no effect. Some of the Ctrl functions still - work in the window/s and the keyboard freeze is only localized to + specifically those opened with Evince, is used then the created window + freezes the keyboard. New tabs as well as new opened windows experience + the same issue as long as the original window is still open. Windows key + + F9 and Windows key + Shift have no effect. Some of the Ctrl functions + still work in the window/s and the keyboard freeze is only localized to FireFox. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 90.0+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.4.0-80.90~18.04.1-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.24 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: denmark1731 F pulseaudio - /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: denmark1731 F pulseaudio + /dev/snd/pcmC0D0p: denmark1731 F...m pulseaudio BuildID: 20210705185941 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Jul 25 22:31:20 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2021-01-08 (198 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IpRoute: - default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp2s0 scope link metric 1000 - 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 + default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 + 169.254.0.0/16 dev wlp2s0 scope link metric 1000 + 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.115 metric 600 ProcEnviron: - LANGUAGE=en_ZA:en - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_ZA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_ZA:en + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_ZA.UTF-8 + SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: - Profile1 (Default) - LastVersion=None/None (Out of date) - Profile0 - LastVersion=90.0/20210705185941 (In use) + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire 5733 dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnAcer:bvrV1.08:bd03/21/2012:svnAcer:pnAspire5733:pvrV1.08:rvnAcer:rnAspire5733:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Intel_Mobile dmi.product.name: Aspire 5733 dmi.product.sku: Calpella_CRB dmi.product.version: V1.08 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1937957 Title: external hyperlink keyboard freeze Status in firefox package in Ubuntu: New Bug description: When no FireFox windows are currently open and an external hyperlink, specifically those opened with Evince, is used then the created window freezes the keyboard. New tabs as well as new opened windows experience the same issue as long as the original window is still open. Windows key + F9 and Windows key + Shift have
[Desktop-packages] [Bug 1938015] [NEW] package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460
Public bug reported: I wanted download nvidia-470 with command sudo apt-get install nvidia-470 nvidia-settings ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 26 14:01:32 2021 ErrorMessage: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460 460.32.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-07-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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.4 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460 460.32.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1938015 Title: package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460 460.32.03-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I wanted download nvidia-470 with command sudo apt-get install nvidia-470 nvidia-settings ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 26 14:01:32 2021 ErrorMessage: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460 460.32.03-0ubuntu0.20.04.1 InstallationDate: Installed on 2021-07-26 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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.4 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/usr/bin/nvidia-bug-report.sh», который уже имеется в пакете nvidia-utils-460 460.32.03-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1938015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938010] [NEW] package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
Public bug reported: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires : chromium-codecs-ffmpeg-extra gstreamer1.0-vaapi libgstreamer-plugins-bad1.0-0 Veuillez utiliser « sudo apt autoremove » pour les supprimer. Les NOUVEAUX paquets suivants seront installés : chromium-browser 0 mis à jour, 1 nouvellement installés, 0 à enlever et 17 non mis à jour. Il est nécessaire de prendre 48,3 ko dans les archives. Après cette opération, 164 ko d'espace disque supplémentaires seront utilisés. Réception de :1 http://fr.archive.ubuntu.com/ubuntu focal-updates/universe amd64 chromium-browser amd64 1:85.0.4183.83-0ubuntu0.20.04.2 [48,3 kB] 48,3 ko réceptionnés en 0s (185 ko/s) Préconfiguration des paquets... Sélection du paquet chromium-browser précédemment désélectionné. (Lecture de la base de données... 22 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap erreur : cannot install "chromium": cannot query the store for updates: got unexpected HTTP status code 403 via POST to "https://api.snapcraft.io/v2/snaps/refresh; dpkg: erreur de traitement de l'archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb (--unpack) : new chromium-browser package pre-installation script subprocess returned error exit status 1 Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jul 26 09:32:32 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-07-21 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1938010 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: New Bug description: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires : chromium-codecs-ffmpeg-extra gstreamer1.0-vaapi libgstreamer-plugins-bad1.0-0 Veuillez utiliser « sudo apt autoremove » pour les supprimer. Les NOUVEAUX paquets suivants seront installés : chromium-browser 0 mis à jour, 1 nouvellement installés, 0 à enlever et 17 non mis à jour. Il est nécessaire de prendre 48,3 ko dans les archives. Après cette opération, 164 ko d'espace disque supplémentaires seront utilisés. Réception de :1 http://fr.archive.ubuntu.com/ubuntu focal-updates/universe amd64 chromium-browser amd64 1:85.0.4183.83-0ubuntu0.20.04.2 [48,3 kB] 48,3 ko réceptionnés en 0s (185 ko/s) Préconfiguration des paquets... Sélection du paquet chromium-browser précédemment désélectionné. (Lecture de la base de données... 22 fichiers et répertoires déjà installés.) Préparation du dépaquetage de .../chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap erreur : cannot install "chromium": cannot query the store for updates: got unexpected HTTP status code 403 via POST to "https://api.snapcraft.io/v2/snaps/refresh; dpkg: erreur de traitement de l'archive
[Desktop-packages] [Bug 1936966] Re: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards
The template dialog has an unfortunate setting of WM_CLASS(STRING) = "soffice", "Soffice" compared to the main windows of e.g. LibreOffice Impress WM_CLASS(STRING) = "libreoffice", "libreoffice-impress" Although I thought bamf is able to match windows based on their (parent-) pid by using e.g. _NET_WM_PID(CARDINAL) which do match in this case. ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1936966 Title: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards Status in LibreOffice: New Status in bamf package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with Unity and MATE desktops 2. Add LO PPA, install full LO by sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update sudo apt-get install libreoffice 3a. Launch Libreoffice Impress, wait the Select a Template window to appear on task bar/window list 3b. Launch Libreoffice Writer, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3c. Launch Libreoffice Calc, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3d. Launch Libreoffice Draw, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list Expected results: * all Template windows use correct desktop/panel/window icons on task bar/window list Actual results: * all Template windows use wrong desktop/panel/window icons on task bar/window list Details: libreoffice1:7.1.4~rc2-0ubuntu0.18.04.1~lo1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1936966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
And you could try: sudo apt install build-essential sudo apt-get build-dep linux-image- (the running kernel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Where could I get that patch, let me build the testing kernel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937854] Re: Keyboard shortcut Super+Alt+Up is hardcoded to show activities overview
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1937854 Title: Keyboard shortcut Super+Alt+Up is hardcoded to show activities overview Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: ### Affected version Ubuntu 21.10 (dev), Wayland, Gnome 40.2.0, gnome-shell 40.2-1ubuntu1 ### Bug summary The keyboard shortcut `Super+Alt+Up` seems to be hardcoded to something along the lines of showing activities overview, and cannot be removed or used for any other action, even if it's shown as assigned to one. ### Steps to reproduce 1. Open system preferences, and navigate to Keyboard -> Keyboard Shortcuts -> Customize Shortcuts -> System 2. Verify that no action has `Super+Alt+Up` set, removing/changing any actions if it's already assigned. 3. Optional: assign `Super+Alt+Up` to some other action. 4. Press `Super+Alt+Up` ### What did you expect to happen Either the action which `Super+Alt+Up` is shown to be assigned to, or nothing if no action has that shortcut assigned. ### What happened The activities overview is shown. ### Upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4497 - maintainers indicated this is most likely cause by a downstream modification. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 12:54:57 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2019-11-17 (614 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) _Edit: fix `Super+Up`-> `Super+Alt+Up`_ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1937854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937932] Re: Blank Screen and Unable to get into windows while opening laptop lid after Sleep.
Also what is the "error" in > blank screen with error. ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1937932 Title: Blank Screen and Unable to get into windows while opening laptop lid after Sleep. Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: While opening laptop display lid open ubuntu failed to open and stuck on blank screen with error. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Jul 25 15:02:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3a34] Subsystem: Lenovo GP107M [GeForce MX350] [17aa:3a34] InstallationDate: Installed on 2021-07-21 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82A1 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=178639d7-12e5-45ac-a728-0643b1c58d44 ro quiet splash i915.enable_psr=0 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
That wiki is not owned by Ubuntu so we can't fix the instructions it gives. As for any and all crashes in Ubuntu, please follow these instructions: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash Status in gnome-shell package in Ubuntu: Incomplete Bug description: I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in https://wiki.gnome.org/Projects/GnomeShell/Debugging which say to do the following in an ssh login or separate VT: gnome_session=$(pgrep -u $USER gnome-session) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) gdb ...etc... However three problems came up, two minor (wrong instructions), the other major: (1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ". In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters): $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/') UID PIDPPID CSZ RSS PSR STIME TTY TIME CMD jima97439725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu jima98288066 0 24031 6148 8 13:41 ?00:00:00 /usr/libexec/gnome-session-ctl --monitor jima98388066 0 129272 18176 7 13:41 ?00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (2) The instructions specify this gdb command: call gjs_dumpstack () However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type (3) Most importantly, a crash: Immediately upon starting the new gnome-shell process (with option --replace) a white screen appears with "Oh No... something went wrong..." forcing me log out. The crash happens whether using an independent VT or an ssh login. Afterwards I typed Control-C to get control in gdb, and produced the attached backtraces but they don't seem useful (see attached typescript file). /var/syslog might be useful. I will attach the portion beginning just before starting the new gnome-shell The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome- shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, but is about how using the debug instructions in the wiki are incorrect and when fixed seem to cause a crash on their own. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jul 25 13:41:54 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-20 (5 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
It sounds like the error is coming from: /home/jarnos/.config/pulse/default.pa so I would recommend just deleting that custom config file if you can't figure out where the error is. If the file reappears and you didn't manually create it then we would need to find out which app is creating the file. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: Incomplete Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937854] Re: Keyboard shortcut Super+Alt+Up is hardcoded to show activities overview
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4497 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4497 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4497 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1937854 Title: Keyboard shortcut Super+Alt+Up is hardcoded to show activities overview Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: ### Affected version Ubuntu 21.10 (dev), Wayland, Gnome 40.2.0, gnome-shell 40.2-1ubuntu1 ### Bug summary The keyboard shortcut `Super+Alt+Up` seems to be hardcoded to something along the lines of showing activities overview, and cannot be removed or used for any other action, even if it's shown as assigned to one. ### Steps to reproduce 1. Open system preferences, and navigate to Keyboard -> Keyboard Shortcuts -> Customize Shortcuts -> System 2. Verify that no action has `Super+Alt+Up` set, removing/changing any actions if it's already assigned. 3. Optional: assign `Super+Alt+Up` to some other action. 4. Press `Super+Alt+Up` ### What did you expect to happen Either the action which `Super+Alt+Up` is shown to be assigned to, or nothing if no action has that shortcut assigned. ### What happened The activities overview is shown. ### Upstream bug report https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4497 - maintainers indicated this is most likely cause by a downstream modification. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jul 23 12:54:57 2021 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2019-11-17 (614 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) _Edit: fix `Super+Up`-> `Super+Alt+Up`_ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1937854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937914] Re: [HP Probook 450 G6] Laptop Monitor Turns off During Startup
** Summary changed: - Laptop Monitor Turns off During Startup + [HP Probook 450 G6] Laptop Monitor Turns off During Startup ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [HP Probook 450 G6] Laptop Monitor Turns off During Startup + [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1937914 Title: [HP Probook 450 G6] Laptop Monitor Turns off During Startup, but older kernel versions work Status in linux package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1937988] Re: The image is distrorted while use iGPU rendering and output via AMD GPU
@Shengyao, Thanks, would you please share the ppa you tested here that we could give it a try? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937919] Re: Fails to start pulseaudio (No card found by this name or index.)
** Attachment removed: "default.pa" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1937919 Title: Fails to start pulseaudio (No card found by this name or index.) Status in pulseaudio package in Ubuntu: New Bug description: First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the volume control in Xfce panel shows mute after I start session, but I can not change it. This does not happen every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 25 00:21:17 2021 InstallationDate: Installed on 2019-12-05 (597 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-07-10 (379 days ago) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
