[Desktop-packages] [Bug 1902540] Re: hirsute fails on add-apt-repository
Fixed by https://launchpad.net/ubuntu/+source/python-apt/2.1.3ubuntu3 migrating after some work on dependencies. Note cloud and lxd images do not yet contain this, so you'll need to update before add-apt-repository or wait another day or two. Thanks everyone. ** Changed in: python-apt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1902540 Title: hirsute fails on add-apt-repository Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Invalid Bug description: On a fully updated hirsute add-apt-repository fails, example: root@h:~# sudo add-apt-repository ppa:ci-train-ppa-service/4321 Traceback (most recent call last): File "/usr/bin/add-apt-repository", line 330, in addaptrepo = AddAptRepository() File "/usr/bin/add-apt-repository", line 35, in __init__ self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 91, in get_sources raise NoDistroTemplateException( aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/hirsute The PPA seems not to matter (all trigger it) and if I manually add PPA sources list and GPG key it works. So maybe software-properties just needs to learn about hirsute? Or is there another components (like distro-info or such) that needs a bump for this to work? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1902540/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Sorry for doubler post, I forgot to add attachment. ** Attachment added: "/dev after command" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901922/+attachment/5431794/+files/tree.after.txt -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Another thing that brings the soundcard correctly up is running the following sequence of commands: udevadm control --reload-rules && udevadm trigger I took a snapshot of the /dev tree before and after the command. There are no significant differences. ** Attachment added: "/dev before command" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901922/+attachment/5431791/+files/tree.before.txt -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
@Marcu, do you mean if you go back to 1.2.2-1ubuntu1 the issue resolves itself? -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
If that that would be a regression from bug #1899745 Hui could you investigate if that's correct? ** Tags added: regression-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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
> I suspect libasound2:amd64 (1.2.2-2.1ubuntu2, 1.2.2-2.1ubuntu2.1) beeing responsible, since this is the only sound related update that I installed today. Could you try to install back the old version (the deb files are on https://launchpad.net/ubuntu/+source/alsa- lib/1.2.2-2.1ubuntu2/+build/19854508) and confirm if it resolves your issue? ** Tags added: focal regression-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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
@Gunnar, if you want to go with a revert it shouldn't need to block on hirsute since we aren't going to go that way in the new serie but rather cherrypick the new pango fix (we could do that now in Debian and sync over, let know if you need help with an upload) -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: New Status in gnome-terminal source package in Groovy: Triaged Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an upstream commit which fixes it. [Test case] * Install the binaries built from gtk+3.0 in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows regular fonts only. [ Regression risk ] The upstream commit was written explicitly to fix this issue, so the regression risk should be low. Please note that the only affected file is gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself ought to limit the regression risk. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1903207] Re: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ )
Thank you for the bug report and the patch pointer! ** Changed in: rhythmbox (Ubuntu) Status: New => Fix Committed ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1903207 Title: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ ) Status in rhythmbox package in Ubuntu: Fix Committed Bug description: Playback fails when crossfade is enabled in gstreamer 1.18+ Upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1835 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903207/+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 1902915] Re: (Snap) Cannot add an attachment to the message
Thanks the reply. > Maybe I'm missing something. It's a snap, can you explain why I need to install a debian package to get it working. The software is self contained in the snap but it does rely on the system to provide a standard environment. The same way than the snap doesn't include a desktop environment or a display server, if you tried to start it on ubuntu server you would get an error that it can't open a display. The portals are installed by default and a Recommends from the desktop for some cycles. Making them a depends of snapd would be wrong because they are only useful for some desktop software though. There is space for improvement there though, you are probably not the only one that are going to end up with a system where important components are missing for a reason or another. I'm going to reassign to snapd suggesting that it should at least display some informative warning in those cases, perhaps offer to install the require component. ** Package changed: thunderbird (Ubuntu) => snapd (Ubuntu) ** Changed in: snapd (Ubuntu) Status: Incomplete => New ** Summary changed: - (Snap) Cannot add an attachment to the message + snapd doesn't ensure portals are available even when they are needed ** Description changed: - When writing a new mail, I cannot add an attachment to the message. - - Steps to reproduce. - 1 - Click write - 2 - Click attach + * Steps to reproduce + - install the thunderbird snap + - remove xdg-desktop-portal-gtk + - start thunderbird + - write an email + - click on attach Expected: A file choose dialog should appear. Actual : Nothing is shown. + + The snap relies on the portal to be available and is failing because + it's not. Could snapd somewhow display some warnings explaining the + issue or better offer to install the portals when needed? + + -- $lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $snap info thunderbird name: thunderbird summary: Mozilla Thunderbird email application publisher: Canonical✓ store-url: https://snapcraft.io/thunderbird contact: https://launchpad.net/distros/ubuntu/+source/thunderbird license: unset description: | - Thunderbird is a free and open source email, newsfeed, chat, and calendaring client, that’s easy - to set up and customize. One of the core principles of Thunderbird is the use and promotion of - open standards - this focus is a rejection of our world of closed platforms and services that - can’t communicate with each other. We want our users to have freedom and choice in how they - communicate. + Thunderbird is a free and open source email, newsfeed, chat, and calendaring client, that’s easy + to set up and customize. One of the core principles of Thunderbird is the use and promotion of + open standards - this focus is a rejection of our world of closed platforms and services that + can’t communicate with each other. We want our users to have freedom and choice in how they + communicate. commands: - - thunderbird + - thunderbird snap-id: k1Ml1O9GzSO2QftV0ZlWSbUfQ78nN460 tracking: latest/stable refresh-date: yesterday at 23:37 CET channels: - latest/stable:78.4.0 2020-11-03 (92) 69MB - - latest/candidate: ↑ - latest/beta: ↑ - latest/edge: 78.4.0 2020-11-03 (92) 69MB - + latest/stable:78.4.0 2020-11-03 (92) 69MB - + latest/candidate: ↑ + latest/beta: ↑ + latest/edge: 78.4.0 2020-11-03 (92) 69MB - installed: 78.4.0(92) 69MB - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902915 Title: snapd doesn't ensure portals are available even when they are needed Status in snapd package in Ubuntu: New Bug description: * Steps to reproduce - install the thunderbird snap - remove xdg-desktop-portal-gtk - start thunderbird - write an email - click on attach Expected: A file choose dialog should appear. Actual : Nothing is shown. The snap relies on the portal to be available and is failing because it's not. Could snapd somewhow display some warnings explaining the issue or better offer to install the portals when needed? -- $lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $snap info thunderbird name: thunderbird summary: Mozilla Thunderbird email application publisher: Canonical✓ store-url: https://snapcraft.io/thunderbird contact: https://launchpad.net/distros/ubuntu/+source/thunderbird license: unset description: | Thunderbird is a free and open source email, newsfeed, chat, and calendaring client, that’s easy to set up and customize. One of the core principles of Thunderbird is the use and promotion of open standards - this focus is a rejection
[Desktop-packages] [Bug 1881603] Re: [snap] Cannot open attached file from e-mail
In case anyone else hits this problem and is wondering about the root cause, it seems to be because snaps generally can't access data from other applications, so when Thunderbird drops a file into This doesn't happen with the non-snap version of LibreOffice distributed through the Ubuntu archive and available via `apt install`, so switching to that is a workaround. -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1881603] Re: [snap] Cannot open attached file from e-mail
In case anyone else hits this problem and is wondering about the root cause, it seems to be because snaps generally can't access data from other applications, so when Thunderbird drops a file into /tmp LibreOffice can't "see" it. This isn't unique to LibreOffice, it causes problems for other snaps as well (e.g. Chromium). This doesn't happen with the non-snap version of LibreOffice distributed through the Ubuntu archive and available via `apt install`, so switching to that is a workaround, albeit at a lower version (6.4.2 instead of 7.0.2.2). There are a few Ask Ubuntu posts with additional information and other workarounds: https://askubuntu.com/questions/1123537/cant-open-file-attachment-with- libreoffice-snap https://askubuntu.com/questions/1046890/libreoffice-cant-access-tmp- files-in-18-04 https://askubuntu.com/questions/1215305/how-can-i-grant-a-snap- application-access-to-tmp-via-command-line -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
** Package changed: metacity (Ubuntu) => gnome-shell (Ubuntu) -- 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/1903224 Title: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used Status in gnome-shell package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903224/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged
Hello hugh, or anyone else affected, Accepted system-config-printer into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /system-config-printer/1.5.12-0ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: system-config-printer (Ubuntu Groovy) Status: Incomplete => Fix Committed ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Fix Committed Status in system-config-printer source package in Groovy: Fix Committed Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
@Marcus, could you please upload the log of pa-info (pa-info > pa-info.txt) both with alsa-utils 1.2.2-1ubuntu1 and ubuntu2? -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1893300] Re: The status of cups still shows idle when the printer has been unplugged
Hello hugh, or anyone else affected, Accepted system-config-printer into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /system-config-printer/1.5.12-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: system-config-printer (Ubuntu Focal) Status: Incomplete => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Fix Committed Status in system-config-printer source package in Groovy: Fix Committed Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+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 1881603] Re: [snap] Cannot open attached file from e-mail
Sorry I mixed my tabs and though that was about thunderbird, libreoffice should probably start using portals as well to resolve the issue ** Changed in: libreoffice (Ubuntu) Status: Fix Released => Confirmed -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Thore, Please try this libasound2 (ubuntu 20.04): sudo add-apt-repository ppa:hui.wang/pa-testing sudo apt install libasound2 This will install the testing kernel 1.2.2-2.1ubuntu2.1+testamd -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Thore, Please try this libasound2 (ubuntu 20.04): sudo add-apt-repository ppa:hui.wang/pa-testing sudo apt install libasound2 This will install the testing version 1.2.2-2.1ubuntu2.1+testamd -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1902853] Re: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control
The fix (upgrading to HWE) doesn't change the Mesa lib version, so while it could be caused by a newer Mesa interacting badly with the older kernel or xorg, I feel like it seems more like to be kernel or xorg. 18.04 is LTS, and this is somewhat of a trap for those doing CI testing of desktop applications, so I'd be happy to help a little more in trying to identify if a fix can be taken back. A bisect seems like it'd be a huge effort however so I'm ruling that out for now. I still reckon if I knew which process picks up the message that xcb_glx_create_context_attribs_arb_checked sends I could take a closer look and find why it rejects the extension value. Happen to know how to track that? -- 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/1902853 Title: Failure to create core GL context with llvmpipe when using GLX_ARB_context_flush_control Status in libsdl2 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: When using llvmpipe on the non-HWE xorg version GL core context creation fails when using "GLX_ARB_context_flush_control" even though the driver reports that the extension is supported. Apologies if xorg is the wrong package here, this could be a libgl1 -mesa-dri/glx bug instead, it's unclear to me where the fault lies in the graphics stack. xserver-common: Installed: 2:1.19.6-1ubuntu4.7 Candidate: 2:1.19.6-1ubuntu4.7 linux-generic: Installed: 4.15.0.122.109 Candidate: 4.15.0.122.109 Steps to reproduce on Ubuntu Server: 1. Install Ubuntu 18.04 server edition in a VM, or other hardware without a physical graphics device 2. Install the desktop with "sudo apt install ubuntu-desktop" 3. Reboot 4. Compile and run the attached file Steps to reproduce on Ubuntu Desktop: 1. Install Ubuntu 18.04 desktop edition in a VM, or other hardware without a physical graphics device 2. Remove the HWE packages with "apt remove *-hwe-18.04" and then "apt install xserver-xorg-core ubuntu-desktop xserver-xorg xserver-xorg-video-all xserver-xorg-input-all libgl1-mesa-dri libgl1-mesa-glx" to get things back to normal 3. Reboot 4. Compile and run the attached file Both examples produce: "Could not create GL context: BadValue (integer parameter out of range for operation)" For both cases, upgrading to (or staying on) the HWE stack allows creating the core 3.3 context successfully. Debugging: I've stepped all the way into libxcb for the context creation at src/glx.c:3258, with a call to "xcb_glx_create_context_attribs_arb_checked", but haven't managed to link this up to a received request in another process. The request is rejected with BadValue. BadVaue in this instance could mean one of two things according to GL spec: 1. The GLX_RENDER_TYPE attribute is invalid 2. An attribute or it's bitmask are not recognized. We can likely rule out 1 as GLX_RENDER_TYPE is correctly set to opengl. Option 2 allows looking at it at a higher level. SDL2 adds `GLX_CONTEXT_RELEASE_BEHAVIOUR_ARB=GLX_CONTEXT_RELEASE_BEHAVIOUR_FLUSH_ARB` to the attributes (at src/video/x11/SDL_x11opengl.c:720) by default when it detects the `GLX_ARB_context_flush_control` extension is present, which should be a no-op and the default setting. `glxinfo` and other gl functions all show that `GLX_ARB_context_flush_control` is present, but removing that usage from the attributes list (by removing lines 720 to 726 avoids the issue and we are given a valid GL context. Due to this, I think something in the graphics stack is rejecting the usage of GLX_ARB_context_flush_control, even though it's claiming to support it through other gl calls. The llvmpipe GL driver reports core support up to 3.3 as well, so this shouldn't be an issue. I also suspect it's simply something that's been fixed more recently, as installing the newer HWE versions of xorg (and the kernel) fixes the issue. I wouldn't expect to have to upgrade to the HWE stack to be able to get a working GL context this way, so I'm reporting this to check if it's a known issue or if there's a fix that can be made. The attached file depends on "libsdl2-dev" and can be compiled and run with: "g++ main.cpp -I/usr/include/SDL2 -lSDL2 -lGL && ./a.out" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:16:16 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsys
[Desktop-packages] [Bug 1881603] Re: [snap] Cannot open attached file from e-mail
Or wait, you try to open the file from thunderbird in an email and it fails to open in libreoffice's snap (but works with the deb?) -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1881603] Re: [snap] Cannot open attached file from e-mail
The issue is fixed now, the current snap revision uses the desktop portals which provides a picker on the real filesystem which allows to access any location the normal user can browser (the program still doesn't have access so it can't go read things it shouldn't, it requires user interaction to go pick from the selector) ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1900906] Re: Can't use dead keys or input e.g. Chinese characters in GNOME shell
Wow, thanks! -- 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/1900906 Title: Can't use dead keys or input e.g. Chinese characters in GNOME shell Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: I'm running an up-to-date Ubuntu Focal. I have a standard Spanish keyboard. Under X, if I try to input an accentuated character, such as á or ü, in places like the search field in the overview or when writing a folder name in the app grid, nothing appears. Under Wayland, it fails each time on the first input of an accentuated character, then it works. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-01 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Package: ibus PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-52-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-09-29 (22 days ago) UserGroups: sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1900906/+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 141081] Re: Firefox opens 2 extra tabs on middle button click
This issue just started to happen to me. Sometimes opens two or even three tabs of the same thing. -- 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/141081 Title: Firefox opens 2 extra tabs on middle button click Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox Whenever i click the middle mouse button (scroll wheel) on a weblink to open a new tab firefox opens 2 additional tabs of the same thing. ProblemType: Bug Architecture: i386 Date: Wed Sep 19 16:48:46 2007 DistroRelease: Ubuntu 7.04 Package: firefox 2.0.0.6+1-0ubuntu1 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 141081] Re: Firefox opens 2 extra tabs on middle button click
Firefox: 82.0 (64-bit) Ubuntu 20.04.1 LTS -- 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/141081 Title: Firefox opens 2 extra tabs on middle button click Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox Whenever i click the middle mouse button (scroll wheel) on a weblink to open a new tab firefox opens 2 additional tabs of the same thing. ProblemType: Bug Architecture: i386 Date: Wed Sep 19 16:48:46 2007 DistroRelease: Ubuntu 7.04 Package: firefox 2.0.0.6+1-0ubuntu1 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I looked into the apt history and I actually updated the following sound related updates (these are the old version numbers that seemed to work) - libasound2:amd64=1.2.2-2.1ubuntu2 - libasound2:i386=1.2.2-2.1ubuntu2 - libasound2-data:all=1.2.2-2.1ubuntu2 - alsa-utils:amd64=1.2.2-1ubuntu1 I could roll alsa-utils back since, this version 1.2.2-1ubuntu1 is still in the repos. That does NOT resolve the issue, I already did that before even posting here. Then I downloaded libasound2_1.2.2-2.1ubuntu2_amd64.deb from the link you provided. I get the following message: $ sudo dpkg -i ./libasound2_1.2.2-2.1ubuntu2_amd64.deb [sudo] password for thore: dpkg: warning: downgrading libasound2:amd64 from 1.2.2-2.1ubuntu2.1 to 1.2.2-2.1ubuntu2 (Reading database ... 309601 files and directories currently installed.) Preparing to unpack libasound2_1.2.2-2.1ubuntu2_amd64.deb ... De-configuring libasound2:i386 (1.2.2-2.1ubuntu2.1) ... Unpacking libasound2:amd64 (1.2.2-2.1ubuntu2) over (1.2.2-2.1ubuntu2.1) ... dpkg: error processing package libasound2:amd64 (--install): package libasound2:amd64 1.2.2-2.1ubuntu2 cannot be configured because libasound2:i386 is at a different version (1.2.2-2.1ubuntu2.1) dpkg: error processing package libasound2:i386 (--install): package libasound2:i386 1.2.2-2.1ubuntu2.1 cannot be configured because libasound2:amd64 is at a different version (1.2.2-2.1ubuntu2) Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Errors were encountered while processing: libasound2:amd64 libasound2:i386 I don't know what's wrong, but it is not working. Kind regards Thore -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modali
[Desktop-packages] [Bug 1903281] [NEW] Evince's slow to select text on PDF/A - 2b format pdf type
Public bug reported: I'm using Ubuntu 20.10, since then I noticed that in pdf document with format PDF/A - 2b, text selection is very slow. What you expected to happen It should've been normal to select text like any other document and no slowness. I've used Ubuntu 20.04 too, also the same thing there. What happened instead It's slow to select text inside the doc. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: evince 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 11:48:06 2020 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: I'm using Ubuntu 20.10, since then I noticed that in pdf document with format PDF/A - 2b, text selection is very slow. What you expected to happen It should've been normal to select text like any other document and no - slowness. + slowness. I've used Ubuntu 20.04 too, also the same thing there. What happened instead It's slow to select text inside the doc. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: evince 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 11:48:06 2020 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: - + ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1903281 Title: Evince's slow to select text on PDF/A - 2b format pdf type Status in evince package in Ubuntu: New Bug description: I'm using Ubuntu 20.10, since then I noticed that in pdf document with format PDF/A - 2b, text selection is very slow. What you expected to happen It should've been normal to select text like any other document and no slowness. I've used Ubuntu 20.04 too, also the same thing there. What happened instead It's slow to select text inside the doc. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: evince 3.38.0-1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 11:48:06 2020 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) KernLog: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1903281/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Hui Wang I get this $ sudo add-apt-repository ppa:hui.wang/pa-testing $ sudo apt install libasound2 Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libasound2 : Depends: libasound2-data (>= 1.2.2-2.1ubuntu2.1+testamd) but 1.2.2-2.1ubuntu2.1 is to be installed Breaks: libasound2:i386 (!= 1.2.2-2.1ubuntu2.1+testamd) but 1.2.2-2.1ubuntu2.1 is to be installed libasound2:i386 : Breaks: libasound2 (!= 1.2.2-2.1ubuntu2.1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). Then $ sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: libasound2 libasound2:i386 libasound2-data The following packages will be upgraded: libasound2 libasound2:i386 libasound2-data 3 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. 2 not fully installed or removed. Need to get 770 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Is this the famous dependency hell everyone is talking about? -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO
[Desktop-packages] [Bug 1903283] [NEW] Nautilus does not start and if it does takes crazy long time to do so
Public bug reported: When starting nautilus (either via clocking the button or using the terminal) after startup, nautilus does not start at all. Starting it via the terminal results in a Timeout error. I can though see the process in the system monitor. If I terminate the process via "End process" and then start nautilus again, the nautilus window appears after around 20 seconds. I then get the same behavior if I want to save a file from within an application. E.g. if I click "save file to" within inkscape, it will take around 20s until the file manager window open. I purged nautilus and reinstalled it already, but it did not help. I also followed a stackoverflow answer, saying that you have to sudo apt-get purge xdg-desktop-portal-gtk Right after I did that, nautilus was starting immediately. But after a reboot the effect was gone and I was back with the old problem. Sper annoying. Best Joachim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 10:56:51 2020 InstallationDate: Installed on 2020-04-23 (196 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-08-31 (66 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1903283 Title: Nautilus does not start and if it does takes crazy long time to do so Status in nautilus package in Ubuntu: New Bug description: When starting nautilus (either via clocking the button or using the terminal) after startup, nautilus does not start at all. Starting it via the terminal results in a Timeout error. I can though see the process in the system monitor. If I terminate the process via "End process" and then start nautilus again, the nautilus window appears after around 20 seconds. I then get the same behavior if I want to save a file from within an application. E.g. if I click "save file to" within inkscape, it will take around 20s until the file manager window open. I purged nautilus and reinstalled it already, but it did not help. I also followed a stackoverflow answer, saying that you have to sudo apt-get purge xdg-desktop-portal-gtk Right after I did that, nautilus was starting immediately. But after a reboot the effect was gone and I was back with the old problem. Sper annoying. Best Joachim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 10:56:51 2020 InstallationDate: Installed on 2020-04-23 (196 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-08-31 (66 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903283/+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 1861358] Re: tracker search hangs and never returns results
This is to confirm that the package in 'proposed' works. I installed tracker 2.3.6-0-ubuntu1 from 'focal-proposed' and when running 'tracker search something' I get actual search results (and no more Glib warnings). ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1861358 Title: tracker search hangs and never returns results Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: Fix Committed Bug description: * Impact the tracker search utility isn't working * Test case $ tracker search something it should return results if there are any matching items * regression potential it's a build flag change, just check that the tracker search works including in the desktop and nautilus -- When I run $ tracker search -f Bruni I see the following output on console - (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register existing type 'TrackerLanguage' (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot add private field to invalid (non-instantiatable) type '' (tracker search:2): GLib-CRITICAL **: 00:31:10.761: g_once_init_leave: assertion 'result != 0' failed (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed - The program hangs and never returns. Sending Control-C brings me back to prompt ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: tracker 2.3.0-1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Jan 30 00:31:59 2020 ExecutablePath: /usr/bin/tracker InstallationDate: Installed on 2016-11-05 (1180 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: tracker UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1861358/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hi Olivier, As per your comment here: https://discourse.ubuntu.com/t/desktop-team- updates-monday-2nd-november-2020/19154/7 I tried this with the latest/edge version of the snap: $ snap info chromium ... tracking: latest/edge refresh-date: today at 10:13 CET channels: latest/stable:86.0.4240.183 2020-11-04 (1382) 252MB - latest/candidate: 86.0.4240.183 2020-11-04 (1382) 252MB - latest/beta: 87.0.4280.47 2020-11-05 (1385) 254MB - latest/edge: 88.0.4315.5 2020-11-06 (1386) 256MB - installed: 88.0.4300.0 (1380) 256MB - I'm on Ubuntu 20.04.1 and when I run it, I see the following errors: $ LIBVA_MESSAGING_LEVEL=2 snap run chromium ... libva info: VA-API version 1.9.0 libva info: Trying to open /snap/chromium/1380/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: va_openDriver() returns -1 libva info: Trying to open /snap/chromium/1380/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: va_openDriver() returns -1 [130715:130715:1106/111245.061240:ERROR:vaapi_wrapper.cc(549)] vaInitialize failed: unknown libva error ... I don't really get why it's searching for the *_drv_video.so when the files there all of the *_dri.so kind: $ ls /snap/chromium/1380/usr/lib/x86_64-linux-gnu/dri/ i915_dri.so kms_swrast_dri.so r200_dri.so radeon_dri.so virtio_gpu_dri.so i965_dri.so nouveau_dri.sor300_dri.so radeonsi_dri.so vmwgfx_dri.so iris_dri.so nouveau_vieux_dri.so r600_dri.so swrast_dri.so I do have an Intel HD Graphics 620 and here is my vainfo: $ vainfo libva info: VA-API version 1.7.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_7 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 20.1.1 () vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc VAProfileNone : VAEntrypointStats VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointFEI VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointFEI VAProfileH264High : VAEntrypointEncSliceLP VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointFEI VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice VAProfileVP9Profile0: VAEntrypointVLD VAProfileVP9Profile2: VAEntrypointVLD -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM
[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
I built a testing package of libasound2 for 20.10, please install and test it: sudo add-apt-repository ppa:hui.wang/pa-testing sudo apt install libasound2 This will install the alsa-lib 1.2.3.2-1ubuntu3+testamd reboot. -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I already tested the testing package with 20.04, it worked. And this is the testing package for 20.10, I don't know if this could fix the issue for 20.10 or maybe 20.10 needs more patches. I built a testing package of libasound2 for 20.10, please install and test it: sudo add-apt-repository ppa:hui.wang/pa-testing sudo apt install libasound2 This will install the alsa-lib 1.2.3.2-1ubuntu3+testamd reboot. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1903283] Re: Nautilus does not start and if it does takes crazy long time to do so
Thank you for your bug report. Could you do $ journalctl -f trigger the issue and copy any error from the log? do you have other softwares having a such slowness? It could be useful to get a gdb backtrace during the time nothing is happening (as described on the already running section of https://wiki.ubuntu.com/Backtrace) ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1903283 Title: Nautilus does not start and if it does takes crazy long time to do so Status in nautilus package in Ubuntu: Incomplete Bug description: When starting nautilus (either via clocking the button or using the terminal) after startup, nautilus does not start at all. Starting it via the terminal results in a Timeout error. I can though see the process in the system monitor. If I terminate the process via "End process" and then start nautilus again, the nautilus window appears after around 20 seconds. I then get the same behavior if I want to save a file from within an application. E.g. if I click "save file to" within inkscape, it will take around 20s until the file manager window open. I purged nautilus and reinstalled it already, but it did not help. I also followed a stackoverflow answer, saying that you have to sudo apt-get purge xdg-desktop-portal-gtk Right after I did that, nautilus was starting immediately. But after a reboot the effect was gone and I was back with the old problem. Sper annoying. Best Joachim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 10:56:51 2020 InstallationDate: Installed on 2020-04-23 (196 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-08-31 (66 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903283/+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 1881603] Re: [snap] Cannot open attached file from e-mail
The problem is if you have LibreOffice installed as a snap and try to open an attachment in Thunderbird, LibreOffice will generate an error message saying that it can open the file because it does not exist (in reality it does exist but LibreOffice can't read it, so the message is a bit misleading). This is not a Thunderbird bug as the same thing happens if you try an open a file via Firefox (i.e. you click on a link to download a spreadsheet and select Open With: LibreOffice Calc). If you have LibreOffice installed via apt then you can open files via Thunderbird and other applications, presumably because the .deb version is not confined in the same way as the snap. -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1881603] Re: [snap] Cannot open attached file from e-mail
Sorry, that should be: LibreOffice will generate an error message saying that it *can't* open the file (Launchpad really needs a comment edit function!) -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1903286] [NEW] Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
Public bug reported: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
The issue seems so far resolved by the testing package. After two full power cycles (power off, disconnect power, power on, reconnect power) the audio still works! -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Hui Wang I installed your package and rebooted. It seems to fix the issue, audio is working as expected again. One thing I noticed is that when I mute the speakers or microphone via their media keys (F1 and F4) the LEDs on the keys don't light up. It may not be related to this issue though because when I activate the FnLock the LED on the Esc key also doesn't light up. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1902969] Re: desktop freezes when changing thundebird win decorations
Okay I have created the bug again and here are the requested files. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+attachment/5431891/+files/prevboot.txt -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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/thunderbird/omni.ja:greprefs.js:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1902931] Re: problem with nvidia on Ubuntu 18.04.5 LTS
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902931 Title: problem with nvidia on Ubuntu 18.04.5 LTS Status in xorg package in Ubuntu: New Bug description: I have a recent problem after update my system, but I can't take a real update with otherr distrib' because I'm AMD architecture... Thank's a lot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 4 19:51:30 2020 DistUpgraded: 2019-10-06 10:46:29,388 DEBUG /openCache(), new cache size 61567 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2011-10-18 (3305 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build i386 LIVE Binary 20111013-11:02 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c040 Logitech, Inc. Corded Tilt-Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=a9de46df-beb4-429a-8937-c398129042b1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-10-06 (395 days ago) dmi.bios.date: 03/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 22:48:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Raw Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902931/+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 1902969] Re: desktop freezes when changing thundebird win decorations
Second file. ** Attachment added: "settings.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+attachment/5431892/+files/settings.txt -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 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/thunderbird/omni.ja:greprefs.js:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+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 1902758] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902758 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: 3D is working by compatibility mode not hardware acceleration. I need fix please ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Nov 3 17:51:49 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902758/+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 1816497] Re: [snap] vaapi chromium no video hardware decoding
You're right Marc, the snap currently in the edge channel is missing pieces (specifically building and bundling recent versions of the drivers), I'm still working on merging my changes from the experimental VA-API support branch. -- 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/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
The testing package of libasound2 built by @hui.wang has resolved the issue for me as well. Thank you! -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1900729] Proposed package removed from archive
The version of gtk+3.0 in the proposed pocket of Groovy that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: New Status in gnome-terminal source package in Groovy: Triaged Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an upstream commit which fixes it. [Test case] * Install the binaries built from gtk+3.0 in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows regular fonts only. [ Regression risk ] The upstream commit was written explicitly to fix this issue, so the regression risk should be low. Please note that the only affected file is gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself ought to limit the regression risk. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1900729] Proposed package removed from archive
The version of gtk+3.0 in the proposed pocket of Groovy that was purported to fix this bug report has been removed because one or more bugs that were to be fixed by the upload have failed verification and been in this state for more than 10 days. -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: New Status in gnome-terminal source package in Groovy: Triaged Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an upstream commit which fixes it. [Test case] * Install the binaries built from gtk+3.0 in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows regular fonts only. [ Regression risk ] The upstream commit was written explicitly to fix this issue, so the regression risk should be low. Please note that the only affected file is gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself ought to limit the regression risk. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
i can observe no fractional scaling on a default installation dell xps5790 even with a single monitor (4k). similar connecting a second monitor is not working separately either. I tried different display resolution to no avail. I eventually started changing the display resolution and gave up on fractional scaling. nvidia 450 libmutter-6-0: Installed: 3.36.6-1ubuntu0.20.04.2 xrandr program version 1.5.0 Server reports RandR version 1.6 lspci 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) (rev 02) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell UHD Graphics 630 (Mobile) Flags: bus master, fast devsel, latency 0, IRQ 176 Memory at eb00 (64-bit, non-prefetchable) [size=16M] Memory at 8000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 I found the prime-select toggle and set it to intel... same issue ** Attachment added: "monitors.xml" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+attachment/5431931/+files/monitors.xml -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1903308] [NEW] gnome-shell freezes and restarts itself after login
Public bug reported: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1903308 Title: gnome-shell freezes and restarts itself after login Status in gnome-shell package in Ubuntu: New Bug description: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.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/ubuntu/+source/gnome-shell/+bug/1903308/+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 1857383] Re: Fractional scaling applies to both monitors when you only want it on one
i can observe no fractional scaling on a default installation dell xps5790 even with a single monitor (4k). Connecting a second monitor the scaling is not working separately either. The most obvious effect is that the right side (top bar) goes off screen. I tried scaling with different display resolution to no avail. I eventually started just using a lower display resolution and gave up on fractional scaling. nvidia 450 libmutter-6-0: Installed: 3.36.6-1ubuntu0.20.04.2 xrandr program version 1.5.0 Server reports RandR version 1.6 lspci 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile) (rev 02) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: Dell UHD Graphics 630 (Mobile) Flags: bus master, fast devsel, latency 0, IRQ 176 Memory at eb00 (64-bit, non-prefetchable) [size=16M] Memory at 8000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 I found the prime-select toggle and set it to intel... same issue ** Attachment added: "xrandr --verbose #during broken scaling" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1857383/+attachment/5431932/+files/xrandr.txt -- 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/1857383 Title: Fractional scaling applies to both monitors when you only want it on one Status in Mutter: Invalid Status in mutter package in Ubuntu: Triaged Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857383/+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 1857383] Re: Fractional scaling applies to both monitors when you only want it on one
I found a workaround for a 40" external - 15" internal 4k monitor setup. D = I HAVE TO use Fractional Scaling but only with 200% on the smaller monitor. This is working fine. If I disable fractional scaling the other external monitor is scaled also!! So there is definitely still a bug in the code. One idea for the cause is the 30Hz I get on the larger monitor?!? This is with the prime-select intel setting on Dell XPS15 7590 -- 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/1857383 Title: Fractional scaling applies to both monitors when you only want it on one Status in Mutter: Invalid Status in mutter package in Ubuntu: Triaged Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1857383/+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 1903207] Re: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ )
This bug was fixed in the package rhythmbox - 3.4.4-1ubuntu3.2 --- rhythmbox (3.4.4-1ubuntu3.2) hirsute; urgency=medium * debian/patches/git_xfade_gstreamer.patch: - gst-helper: fix xfade playback with GStreamer 1.18+ (lp: #1903207) -- Sebastien Bacher Fri, 06 Nov 2020 10:51:27 +0100 ** Changed in: rhythmbox (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1903207 Title: Fast forwards through files without playing when Crossfade Playback is enabled ( in gstreamer 1.18+ ) Status in rhythmbox package in Ubuntu: Fix Released Bug description: Playback fails when crossfade is enabled in gstreamer 1.18+ Upstream bug: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1835 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903207/+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 1903308] Re: gnome-shell freezes and restarts itself after login
This seems to be occurred after upgrading nvidia-driver to the latest available version (455) from "Additional drivers" menu. Reverting back to nvidia-driver 450 and the freezing issue is gone. -- 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/1903308 Title: gnome-shell freezes and restarts itself after login Status in gnome-shell package in Ubuntu: New Bug description: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.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/ubuntu/+source/gnome-shell/+bug/1903308/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
While generating the logs I found out that maybe it's not alsa-utils version. It could also be a combination of the following: - Booting up with earphones plugged in makes the sound come out from the internal speakers (and not the earphones). - Changing the sound output device in the settings app to the earphones doesn't work (they remain silent - I tested using the test window) - Unplugging the earphones and plugging them back in works, but only if the settings app is closed. In all cases a window pops up asking what kind of device I plugged in (phones, phones+mic, mic), but the end result differs. - Audacity seems to reset _something_ when it starts up so whatever state the system was in before launching Audacity might need to be set up again (e.g. unplugging and plugging my earphones yet again). - There was another update in the meantime including libasound2, libasound2-data, systemd, libudev1, etc. so that could be related too. Of course I performed most tests using the settings app, that would explain why I couldn't get any sound on my earphones by normal means. I will upload my logs when I have some kind of consistent and reproducible state (unless you want me to send them anyway). -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1903329] [NEW] SRU the current 2.48.9 stable update
Public bug reported: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: New Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1903331] [NEW] usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
Public bug reported: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 20-30 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Tags: groovy regression-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: New Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 20-30 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
** Description changed: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an - arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an - upstream commit which fixes it. + arbitrarily chosen one. The proposed gnome-terminal upload reverts an + upstream commit, which means that all weights/styles for monospace fonts + are shown. It takes us back to how it works in focal. [Test case] - * Install the binaries built from gtk+3.0 in groovy-proposed + * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a - custom font for the profile. Find that it shows regular fonts only. + custom font for the profile. Find that it shows all available monospace + fonts. Confirm for a few fonts that they can actually be selected + without issues. - [ Regression risk ] + [Where problems could occur] - The upstream commit was written explicitly to fix this issue, so the - regression risk should be low. Please note that the only affected file - is gtk/gtkfontchooserwidget.c, so the scope is very limited which in - itself ought to limit the regression risk. + This is a one liner in gnome-terminal and does not affect other + applications. So given a successful verification of the test case, this + ought to be a safe change. + + [Other info] + + Please note that this particular change has not been made in hirsute. + The reason is that we intend to follow upstream there, which means that + the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: New Status in gnome-terminal source package in Groovy: Triaged Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gnome-terminal upload reverts an upstream commit, which means that all weights/styles for monospace fonts are shown. It takes us back to how it works in focal. [Test case] * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows all available monospace fonts. Confirm for a few fonts that they can actually be selected without issues. [Where problems could occur] This is a one liner in gnome-terminal and does not affect other applications. So given a successful verification of the test case, this ought to be a safe change. [Other info] Please note that this particular change has not been made in hirsute. The reason is that we intend to follow upstream there, which means that the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log pre
[Desktop-packages] [Bug 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
Thanks for your report! Since you were not able to file this bug via the "ubuntu-bug" command, can you please provide some additional standard info by running this command: apport-collect 1903331 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: New Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 20-30 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1903334] [NEW] Xsession does not invoke the correct shell profile script
Public bug reported: The gdm3 package comes with a session launcher script /etc/gdm3/Xsession which starts everything up. In that script it unconditionally executes $HOME/.profile (if it exists). But this is not necessarily the correct shell startup file. If your shell is bash and you have a .bash_login file, tty logins will use that and never touch .profile; but logins via /etc/gdm3/Xsession won't execute .bash_login and therefore will not set up your correct environment. If your shell is csh then .profile was never in the picture and you need to instead execute .login and .cshrc (which of course are in a different syntax that the /bin/bash which executes Xsession won't understand). I understand this file comes from upstream, so the bug should probably be filed upstream as well. But Ubuntu doesn't have to include this Xsession in the gdm3 package and could supply its own. (Red Hat have written their own and supply it in their xorg-x11-xinit package; their gdm package simply symlinks that from /etc/gdm. They've solved the profile problem by making the script execute: exec -l $SHELL -c "[command]" where [command] is a shell command that starts up the session.) In fact Ubuntu already does have a more comprehensive Xsession system included as part of the x11-common package. So the Xsession supplied with gdm3 is redundant. (Unfortunately that other Xsession also does not set up your environment correctly; it doesn't seem to call any profile at all.) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1903334 Title: Xsession does not invoke the correct shell profile script Status in gdm3 package in Ubuntu: New Bug description: The gdm3 package comes with a session launcher script /etc/gdm3/Xsession which starts everything up. In that script it unconditionally executes $HOME/.profile (if it exists). But this is not necessarily the correct shell startup file. If your shell is bash and you have a .bash_login file, tty logins will use that and never touch .profile; but logins via /etc/gdm3/Xsession won't execute .bash_login and therefore will not set up your correct environment. If your shell is csh then .profile was never in the picture and you need to instead execute .login and .cshrc (which of course are in a different syntax that the /bin/bash which executes Xsession won't understand). I understand this file comes from upstream, so the bug should probably be filed upstream as well. But Ubuntu doesn't have to include this Xsession in the gdm3 package and could supply its own. (Red Hat have written their own and supply it in their xorg-x11-xinit package; their gdm package simply symlinks that from /etc/gdm. They've solved the profile problem by making the script execute: exec -l $SHELL -c "[command]" where [command] is a shell command that starts up the session.) In fact Ubuntu already does have a more comprehensive Xsession system included as part of the x11-common package. So the Xsession supplied with gdm3 is redundant. (Unfortunately that other Xsession also does not set up your environment correctly; it doesn't seem to call any profile at all.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1903334/+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 1903337] [NEW] [Feature Request] Replace Nautilus with Nemo?
Public bug reported: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the-default- file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1903337 Title: [Feature Request] Replace Nautilus with Nemo? Status in nautilus package in Ubuntu: New Bug description: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903337/+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 1901318] Re: needs to depend on tcl (not just tcl8.6)
See LP: #1903331 for a possible regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1901318 Title: needs to depend on tcl (not just tcl8.6) Status in usb-modeswitch package in Ubuntu: Fix Committed Status in usb-modeswitch source package in Groovy: Fix Committed Bug description: * Impact the usb-modeswitch dispatcher script fails to start on the default installation because it uses tclsh unversioned while we depends on tcl8.6 * Test Case $ /usr/sbin/usb_modeswitch_dispatcher shouldn't bail out on an interpreter error (or better, test that plugging an usb modem is correctly handled) * Regression potential The script was bailing out due to a missing intepreter before so the code wasn't tested, it's possible that it triggers errors or could interact with the system in some way. The dispatcher reacts to udev events when an usb modem is connected, so try to use one of those and make sure that there is no negative effect (and if possible that the modem gets correctly handled) -- the package currently depends on tcl8.6, but /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which isn't provided by tcl8.6, so it likely would need to depend on something like tcl (= 8.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+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 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
apport information ** Description changed: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: - It takes up to 20-30 mins to my USB Drive be recognized as USB mass and + It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. ** Tags added: apport-collected third-party-packages ** Description changed: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: - It takes up to 15-25 mins to my USB Drive be recognized as USB mass and - be truly ready for mobile broadband connection. Until then, any tries to - connect to internet even if it appears to be ready on system menu or - network settings - mobile broadband - results in failure. When I try to - connect in that period, the USB mass is ejected and prepared for ready - mode automatically after few secs beyond every time. + It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-11-05 (1 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 + Tags: groovy third-party-packages + Uname: Linux 5.8.0-26-generic x86_64 + UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1903331/+attachment/5431980/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: New Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
I will right away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: New Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy third-party-packages Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1903331] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903331/+attachment/5431981/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: New Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy third-party-packages Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
Current status of this bug: The gnome-terminal fix for groovy has been pushed to the VCS repo. I'm waiting for a sponsor to upload it. As regards hirsute: We have identified three upstream pango commits which together with the gtk fix in hirsute-proposed fix the issue the 'right' way. The pango PPA now contains all the three commits: https://launchpad.net/~gunnarhj/+archive/ubuntu/pango1.0 ** Changed in: gnome-terminal (Ubuntu Groovy) Status: Triaged => In Progress ** Changed in: gnome-terminal (Ubuntu) Status: New => Invalid ** Changed in: pango1.0 (Ubuntu) Status: New => Triaged -- 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/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Committed Status in pango1.0 package in Ubuntu: Triaged Status in gnome-terminal source package in Groovy: In Progress Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gnome-terminal upload reverts an upstream commit, which means that all weights/styles for monospace fonts are shown. It takes us back to how it works in focal. [Test case] * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows all available monospace fonts. Confirm for a few fonts that they can actually be selected without issues. [Where problems could occur] This is a one liner in gnome-terminal and does not affect other applications. So given a successful verification of the test case, this ought to be a safe change. [Other info] Please note that this particular change has not been made in hirsute. The reason is that we intend to follow upstream there, which means that the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1903337] Re: [Feature Request] Replace Nautilus with Nemo?
Thank you for the bug report, that's not a nautilus bug though nor the right place to discuss such changes, best o post on discourse or similar about the suggestion ** Changed in: nautilus (Ubuntu) Importance: Undecided => Wishlist ** Changed in: nautilus (Ubuntu) Status: New => Opinion -- 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/1903337 Title: [Feature Request] Replace Nautilus with Nemo? Status in nautilus package in Ubuntu: Opinion Bug description: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903337/+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 1903283] Re: Nautilus does not start and if it does takes crazy long time to do so
There was a similar issue discussed on the GNOME channel today pointed to https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , could you try if that command unblocks things for you? $ killall gvfsd-trash ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #485 https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 -- 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/1903283 Title: Nautilus does not start and if it does takes crazy long time to do so Status in nautilus package in Ubuntu: Incomplete Bug description: When starting nautilus (either via clocking the button or using the terminal) after startup, nautilus does not start at all. Starting it via the terminal results in a Timeout error. I can though see the process in the system monitor. If I terminate the process via "End process" and then start nautilus again, the nautilus window appears after around 20 seconds. I then get the same behavior if I want to save a file from within an application. E.g. if I click "save file to" within inkscape, it will take around 20s until the file manager window open. I purged nautilus and reinstalled it already, but it did not help. I also followed a stackoverflow answer, saying that you have to sudo apt-get purge xdg-desktop-portal-gtk Right after I did that, nautilus was starting immediately. But after a reboot the effect was gone and I was back with the old problem. Sper annoying. Best Joachim ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 10:56:51 2020 InstallationDate: Installed on 2020-04-23 (196 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-08-31 (66 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903283/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@3v1n0 Running PopOS 20.10 right from the installer gets fractional scaling working fine (installed nvidia driver version is 455). What is it that you said they already packaged? Is this supposed to be fixed in Groovy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1903329] Re: SRU the current 2.48.9 stable update
Thank you for the bug report! Olivier, assigning to you since you usually do the librsvg updates, would be great if you could SRU this one ** Changed in: librsvg (Ubuntu) Importance: Undecided => High ** Changed in: librsvg (Ubuntu) Status: New => Confirmed ** Changed in: librsvg (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Confirmed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+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 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
@Hui Wang I installed everything and it seems work now properly as well on my T14. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Scaling is working in my Quadro now, but I can't use as I am finding serious performance issues. Not good. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
Could you add the 'journalctl -b 0' log from the system after getting the failure? ** Changed in: usb-modeswitch (Ubuntu) Importance: Undecided => Low ** Changed in: usb-modeswitch (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy third-party-packages Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1903331] Re: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10
is the situation new to 2.6.1-1ubuntu2 or did you have it in 2.6.1-1ubuntu1? (if so the tag regression-proposed sounds wrong) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1903331 Title: usb-modeswitch 2.6.1-1ubuntu2 is very buggy on Ubuntu 20.10 Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: Hi, I recently allowed groovy-proposed package install of usb-modeswitch 2.6.1-1ubuntu2, because the default one which came with the system was useless. * What you expected to happen: My USB drive should be detected as mobile broadband connection faster as possible without any unpleasant inconvenience after boot stage. * What happened instead: It takes up to 15-25 mins to my USB Drive be recognized as USB mass and be truly ready for mobile broadband connection. Until then, any tries to connect to internet even if it appears to be ready on system menu or network settings - mobile broadband - results in failure. When I try to connect in that period, the USB mass is ejected and prepared for ready mode automatically after few secs beyond every time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-11-05 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: usb-modeswitch 2.6.1-1ubuntu2 [origin: unknown] PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Tags: groovy third-party-packages Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1903331/+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 1902761] Re: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: el subproceso instalado paquete gdm3 script post-installation devolvió el código de salida de error
The issue is in grub according to the log ** Changed in: gdm3 (Ubuntu) Importance: Undecided => Low ** Changed in: gdm3 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1902761 Title: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: el subproceso instalado paquete gdm3 script post-installation devolvió el código de salida de error 10 Status in gdm3 package in Ubuntu: Invalid Bug description: System error and i can't install MySQL with Stack LAMP. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: gdm3:amd64: Install libgdm1:amd64: Install gir1.2-gdm-1.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 3 14:44:49 2020 DpkgHistoryLog: Start-Date: 2020-11-03 14:44:40 Commandline: /usr/bin/unattended-upgrade Upgrade: gdm3:amd64 (3.34.1-1ubuntu1, 3.36.3-0ubuntu0.20.04.2), gir1.2-gdm-1.0:amd64 (3.34.1-1ubuntu1, 3.36.3-0ubuntu0.20.04.2), libgdm1:amd64 (3.34.1-1ubuntu1, 3.36.3-0ubuntu0.20.04.2) ErrorMessage: el subproceso instalado paquete gdm3 script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2020-08-25 (70 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.2, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: gdm3 Title: package gdm3 3.36.3-0ubuntu0.20.04.2 failed to install/upgrade: el subproceso instalado paquete gdm3 script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1902761/+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 1901318] Re: needs to depend on tcl (not just tcl8.6)
Thanks for pointing that out Brian, it seems not likely to be a regression but just incorrect tagging, the user reported problems on discourse before the SRU was uploaded but we will check to make sure to do no error -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1901318 Title: needs to depend on tcl (not just tcl8.6) Status in usb-modeswitch package in Ubuntu: Fix Committed Status in usb-modeswitch source package in Groovy: Fix Committed Bug description: * Impact the usb-modeswitch dispatcher script fails to start on the default installation because it uses tclsh unversioned while we depends on tcl8.6 * Test Case $ /usr/sbin/usb_modeswitch_dispatcher shouldn't bail out on an interpreter error (or better, test that plugging an usb modem is correctly handled) * Regression potential The script was bailing out due to a missing intepreter before so the code wasn't tested, it's possible that it triggers errors or could interact with the system in some way. The dispatcher reacts to udev events when an usb modem is connected, so try to use one of those and make sure that there is no negative effect (and if possible that the modem gets correctly handled) -- the package currently depends on tcl8.6, but /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which isn't provided by tcl8.6, so it likely would need to depend on something like tcl (= 8.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+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 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed -- 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/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0) Status in pulseaudio package in Ubuntu: Confirmed Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+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 1903337] Re: [Feature Request] Replace Nautilus with Nemo?
Thanks for a fast answer, is it this web site? https://discourse.ubuntu.com/ -- 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/1903337 Title: [Feature Request] Replace Nautilus with Nemo? Status in nautilus package in Ubuntu: Opinion Bug description: This bug is a feature request to replace Nautilus with Nemo. The Desktop is not working too well in Ubuntu 20.04: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1813441 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1855711 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1857014 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322 https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150 Could it be considered to replace Nautilus with Nemo as the default file manager, including managing desktop icons? With the tweaks outlined in this post, the Desktop works pretty well, and more or less as expected: https://askubuntu.com/questions/1066752/how-to-set-nemo-as-the- default-file-manager-in-ubuntu-18-04/1173861#1173861 I always switch to Nemo when I install a fresh Ubuntu, due to all the extra configuration options it offers. Nautilus seems too minimalistic for a modern file manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903337/+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 1881603] Re: [snap] Cannot open attached file from e-mail
** Changed in: libreoffice (Ubuntu) Importance: High => Wishlist -- 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/1881603 Title: [snap] Cannot open attached file from e-mail Status in libreoffice package in Ubuntu: Confirmed Bug description: I installed the LibreOffice snap to get a newer version compared to the apt package. When I receive a LibreOffice document as attachment and try to open it from Thunderbird, I get the following error message: """ /tmp/mozilla-antoine0/mydoc.docx doesn't exist """ I don't understand the point of restricting filesystem access from a word processor. At least this is a clear regression from the apt package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1881603/+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 1586528] Re: Avahi-daemon withdraws address record
weisswilly1985 THANK YOU - your workaround is a lifesaver on my rpi4, Raspberry Pi OS (stock kernel). Here's my tested script to get it installed locally: # add a workaround script to rememdy eth0 losing it's IP lease randomly wget https://raw.githubusercontent.com/WillyWeiss/Avahi-daemon-withdraws-address-record-/master/isc-dhcp-fix.sh sudo mv isc-dhcp-fix.sh /usr/bin/isc-dhcp-fix.sh sudo chmod +x /usr/bin/isc-dhcp-fix.sh sudo chown root:root /usr/bin/isc-dhcp-fix.sh sudo nano /etc/rc.local # add this line just above the final 'exit 0' line /usr/bin/isc-dhcp-fix.sh & # run it without a reboot to check for errors, then reboot bash /usr/bin/isc-dhcp-fix.sh & sudo reboot now and here it is in action in the daemon.log file - Nov 2 20:51:34 raspberrypi avahi-daemon[385]: Withdrawing address record for 10.0.1.176 on eth0. Nov 2 20:51:34 raspberrypi avahi-daemon[385]: Leaving mDNS multicast group on interface eth0.IPv4 with address 10.0.1.176. Nov 2 20:51:34 raspberrypi avahi-daemon[385]: Interface eth0.IPv4 no longer relevant for mDNS. Nov 2 20:51:34 raspberrypi dhclient[14510]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3 Nov 2 20:51:34 raspberrypi dhclient[14510]: DHCPOFFER of 10.0.1.176 from 10.0.1.1 Nov 2 20:51:34 raspberrypi dhclient[14510]: DHCPREQUEST for 10.0.1.176 on eth0 to 255.255.255.255 port 67 Nov 2 20:51:34 raspberrypi dhclient[14510]: DHCPACK of 10.0.1.176 from 10.0.1.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
** Attachment added: "Using alsa-utils 1.2.2-1ubuntu1. Sound works on all outputs." https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+attachment/5432035/+files/pa-info_01_alsa-utils-ubuntu1.txt -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
OK, I'm attaching the logs since I could reproduce the bug again. When upgrading from alsa-utils 1.2.2-1ubuntu1 to alsa-utils 1.2.2-1ubuntu2 with speakers plugged in the 3.5mm jack, I could clearly hear a "thump" sound when the 3.5mm jack stopped working. Neither a reboot or a cold boot solved it. What's weird is that I couldn't reproduce that same thing earlier today, doing basically the same steps. The only differences were: [1] I had tested with earphones+mic earlier today and now I'm testing with speakers (in the same jack) and [2] When I upgraded with speakers connected I could hear the exact moment when something wrong happened. As you can guess from the file names ("01" and "07") I have intermediate log files that I'm not sending yet to avoid attaching superfluous info. ** Attachment added: "Using alsa-utils 1.2.2-1ubuntu2. Sound doesn't work on the 3.5mm jack." https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+attachment/5432036/+files/pa-info_07_alsa-utils-ubuntu2_cold_boot_no_sound.txt -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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 1901926] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones
I'm not an expert at all but I noticed these lines in my logs: When sound works: Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out [...] Pin-ctls: 0xc0: OUT HP When it doesn't work: Node 0x21 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out [...] Pin-ctls: 0x00: OP has the first form. Would that mean that we are experiencing two different issues? -- 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/1901926 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all from headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: There is no sound at all from the headphones (p3 out). Speakers work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 13:48:59 2020 InstallationDate: Installed on 2020-01-14 (287 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: HDA NVidia - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr2255 F pulseaudio /dev/snd/controlC0: sartojr2255 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-10-04 (24 days ago) dmi.bios.date: 11/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03REZ.041.191104.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03REZ.041.191104.FL:bd11/04/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP03REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P03REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901926/+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