[Desktop-packages] [Bug 1902415] Re: Ubuntu app wont start - shortcut from wslusc
Hi wennaspeedy, Can you check which version of wslu you are using? You can check it via `wslusc --version`. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1902415 Title: Ubuntu app wont start - shortcut from wslusc Status in wslu package in Ubuntu: New Bug description: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither when I run whole command. I tried several gui apps and none of them works. Apps are running well in wsl terminal of course. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1902415/+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 1902018] Re: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version
ScanYourFinger message is not visible, FP is enrolled, Fingerprint identification also working fine. ** Attachment removed: "IMG_0054.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5429346/+files/IMG_0054.jpg ** Attachment added: "ScanYourFinger message is not visible, FP is enrolled" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902018/+attachment/5430192/+files/IMG_0123.jpg -- 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/1902018 Title: Fingerprint: "scan your finger" option is not displayed at login screen on ubuntu 20.10 version Status in gnome-shell package in Ubuntu: New Bug description: OS: Ubuntu 20.10 version Test sequence: Fingeprint is enrolled Win+L: At login screen, earlier in 20.04 version, it used to display "scan your finger", it is not displayed in 20.10 version, but fingerprint identify is working fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-09-29 (29 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: gnome-control-center 1:3.38.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-27 (1 days ago) 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/gnome-shell/+bug/1902018/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Thanks Jakub for that confirmation! But as discussed before that most likely means we can't fix it in Focal as the updates needed bring too much regression potential for a low prio issue that has alternative (to admit - non perfect) workarounds (e.g. the disabling of the clipboard - which avoids the issue but doesn't give you what you actually want). It was very interesting to hear that a guest only update was enough for you to fix it. I wonder if even older guests - let us say Bionic - are affected as well or if now in between Bionic being fixed Focal is the only bad one? Do you happen to know about Bionic guests behavior? Finally for Windows guests I have no idea what to do about, the spice guest bits there are not created from the same source/provider. But if indeed a guest update helped the Linux guest, then a guest update might help Windows as well. Did upgrading the host make any difference for this case when you used a Windows guest? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+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 1902334] Re: Opening folder on Apps Menu Several times Freezes PC
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1872268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1872268 Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) -- 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/1902334 Title: Opening folder on Apps Menu Several times Freezes PC Status in gnome-shell package in Ubuntu: New Bug description: Whenever I click on folder on apps menu and then i realized i was in wrong folder. And then I tried to switch in another folder, again it was wrong and again I tried to enter another one being in apps menu only After around 5 tries , the app menu crashed. This freezes whole PC and the one and only solution is reset button for pc and long press power button for laptops. Please solve it immediately. It's preventing the multitasking ability of ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902334/+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 1902334] Re: Opening folder on Apps Menu Several times Freezes PC
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 user mentions nautilus causing what I read as gnome-shell crashing.. thus change ** Package changed: 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/1902334 Title: Opening folder on Apps Menu Several times Freezes PC Status in gnome-shell package in Ubuntu: New Bug description: Whenever I click on folder on apps menu and then i realized i was in wrong folder. And then I tried to switch in another folder, again it was wrong and again I tried to enter another one being in apps menu only After around 5 tries , the app menu crashed. This freezes whole PC and the one and only solution is reset button for pc and long press power button for laptops. Please solve it immediately. It's preventing the multitasking ability of ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902334/+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 1902334] Re: Opening folder on Apps Menu Several times Freezes PC
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 Thank you for taking the time to report this bug and helping to make Ubuntu better. Thank you again for your response (release detail). Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1902334 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal -- 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/1902334 Title: Opening folder on Apps Menu Several times Freezes PC Status in gnome-shell package in Ubuntu: New Bug description: Whenever I click on folder on apps menu and then i realized i was in wrong folder. And then I tried to switch in another folder, again it was wrong and again I tried to enter another one being in apps menu only After around 5 tries , the app menu crashed. This freezes whole PC and the one and only solution is reset button for pc and long press power button for laptops. Please solve it immediately. It's preventing the multitasking ability of ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902334/+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 1902334] [NEW] Opening folder on Apps Menu Several times Freezes PC
You have been subscribed to a public bug: Whenever I click on folder on apps menu and then i realized i was in wrong folder. And then I tried to switch in another folder, again it was wrong and again I tried to enter another one being in apps menu only After around 5 tries , the app menu crashed. This freezes whole PC and the one and only solution is reset button for pc and long press power button for laptops. Please solve it immediately. It's preventing the multitasking ability of ubuntu. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apps bot-comment menu -- Opening folder on Apps Menu Several times Freezes PC https://bugs.launchpad.net/bugs/1902334 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1902432] Re: Sound card not detected yet seen in the terminal (fictitious output sound)
** Changed in: alsa-driver (Ubuntu) Status: Incomplete => New -- 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/1902432 Title: Sound card not detected yet seen in the terminal (fictitious output sound) Status in alsa-driver package in Ubuntu: New Bug description: Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. Suite à une modification de ma part sur la carte graphique (maj) il y a eut une incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l. Normalement le système d'exploitation installe automatiquement des drivers compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après apt-cache j'use apt 2.0.2ubuntu0.1 (amd64). Oh et j'ai aussi un problème de detection de mise en charge de ma batterie d'ordinateur, je ne sais pas si c'est lié. Cependant cela n'arrivait pas avant. Un informaticien a déjà regardé mon oridinateur, je n'ai pas de problème de disque dur ou de carte mère. I am on an ASUS X555BP initially Windows 8 then update for Windows 10. Following a modification by myself on the graphics card (update) there was an incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits under gnome 3.36.3. No problem to play a video etc except that the sound does not come out. In the terminal I have already uninstalled and reinstalled Pulse Audio, Alsa etc. It is able to give me the name of my graphics card when I query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but no card is detected when I type aplay -l. Normally the operating system automatically installs drivers compatible with my graphics card so I don't know what to do. According to apt-cache I am using apt 2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load detection. It accepts to be in charge once in ten which did not happen before. My computer was checked by a computer scientist, I have no hard drive or motherboard problem. 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: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 13:52:11 2020 InstallationDate: Installed on 2020-10-13 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555BP.326 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555BP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555BP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1902432/+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 1902001] Re: USB keyboard layout incorrect after unplugging and replugging
** Also affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1902001 Title: USB keyboard layout incorrect after unplugging and replugging Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Kernel version: 5.4.0-52-generic (but problem began with 5.4.0-51-generic) Keyboard: Bus 001 Device 018: ID 056e:1063 Elecom Co., Ltd ELECOM TK-FCP097 Expected behaviour: USB keyboard layout remains the same when unplugging and replugging in same keyboard (This was the behaviour on 5.4.0-48-generic and earlier.) What happened instead: USB keyboard layout changes from: < _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,jp,us,us", ",,intl,", "grp_led:scroll" to: > _XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us,us", ",intl", "grp:alt_shift_toggle,grp_led:scroll" (output of xprop -root | grep XKB ) The keyboard layout is reset to the correct layout after logging out and back in (or after suspend/resume); however, unplugging and replugging the keyboard in causes the same unexpected behaviour. Same problem occurs with a different USB keyboard: Bus 001 Device 019: ID 0d62:8070 Darfon Electronics Corp. ELECOM Wired Keyboard ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 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/controlC0: tyler 18578 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 29 16:35:31 2020 InstallationDate: Installed on 2020-02-05 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=fa5c4fdb-0e37-4ef5-b109-3c129736f66c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-12 (170 days ago) dmi.bios.date: 07/06/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd07/06/2020:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902001/+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 1893813] Re: the super key is not working to show the overview of all running applications like before
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1893813 Title: the super key is not working to show the overview of all running applications like before Status in gnome-shell package in Ubuntu: Expired Bug description: my super key used to work before perfectly well on ubuntu but suddenly stopped showing me the recents .Althought if i press alt+ f1 i am getting it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 22:47:58 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-10 (327 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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/1893813/+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 1893846] Re: Sound doesn't switch to headphones automatically when plugged in
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1893846 Title: Sound doesn't switch to headphones automatically when plugged in Status in pulseaudio package in Ubuntu: Expired Bug description: 1) Ubuntu 20.04.1 LTS 2) gnome-control-center 1:3.36.4-0ubuntu1 3) What you expected to happen:I expected to connect my headphone and listen to any sound automatically. 4) What happened instead: In order to make the headset work, I must go to the Control Center, then "Sound" and choose "Headphones-Built-in Audio" as my Output Device, since the default is "Analog Output-Built-in Audio" (getting no sound from my headset). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: douglas1859 F pulseaudio /dev/snd/controlC1: douglas1859 F pulseaudio /dev/snd/controlC3: douglas1859 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (129 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Tags: focal Uname: Linux 5.4.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/20/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: Z68XP-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd03/20/2012:svnGigabyteTechnologyCo.,Ltd.:pnZ68XP-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68XP-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68XP-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1893846/+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 1765189] Re: Partial User Interface freeze
Can you please test Ubuntu 20.04 and tell us if it has the same problem? https://ubuntu.com/download/desktop ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1765189 Title: Partial User Interface freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a Dell Precision 5520 and experience the following problem: After a resume from suspend, I have problems with my keyboard and touchpad: At the password screen everything is working fine, I can click on the password field and enter my password. Then when the screen is unlocked, I can move the mouse cursor, and clicks on the top menu, e.g. on the network button or the shutdown button work perfectly, but a click on an open window like a terminal or on firefox does not give focus to the window and I cannot write into the terminal. Also, shortcuts like the Windows key or Windows+tab key are not working. I can only solve this by rebooting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 18 22:01:56 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed nvidia, 390.48, 4.15.0-15-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: InstallationDate: Installed on 2018-04-12 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot open /sys/bus/pci/devices/:07:00.0/resource: No such file or directory Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765189/+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 1902361] Re: Delete key inputs Unicode Delete character (007F) instead of deleting the next character
** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1902361 Title: Delete key inputs Unicode Delete character (007F) instead of deleting the next character Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When pressed, the delete key inputs the Unicode 007F character instead of deleting the following character. In most cases, this is difficult to see, but in a terminal, the 007F is clearly visible. The xev output for the key press is following: KeyPress event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XmbLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False This is a new fresh install of Ubuntu 20.04, I don't remember the delete key working at any point since the installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:54:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) [1025:1312] InstallationDate: Installed on 2020-10-14 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Swift SF514-53T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd04/25/2019:svnAcer:pnSwiftSF514-53T:pvrV1.09:rvnWL:rnCarlsberg_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902361/+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 1902361] Re: Delete key inputs Unicode Delete character (007F) instead of deleting the next character
Happens in every app: Gnome Terminal, Xterm, Chrome, login screen. It's only in some places, such as terminal or Chrome URL bar where the character displays, but the wrong behaviour is everywhere. There are no accessibility settings turned on. -- 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/1902361 Title: Delete key inputs Unicode Delete character (007F) instead of deleting the next character Status in mutter package in Ubuntu: Incomplete Bug description: When pressed, the delete key inputs the Unicode 007F character instead of deleting the following character. In most cases, this is difficult to see, but in a terminal, the 007F is clearly visible. The xev output for the key press is following: KeyPress event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XmbLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False This is a new fresh install of Ubuntu 20.04, I don't remember the delete key working at any point since the installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:54:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) [1025:1312] InstallationDate: Installed on 2020-10-14 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Swift SF514-53T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd04/25/2019:svnAcer:pnSwiftSF514-53T:pvrV1.09:rvnWL:rnCarlsberg_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1902361/+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 1898905] Re: Unfunctional plustek scanner in Ubuntu 20.10
This bug was fixed in the package sane-backends - 1.0.31-2ubuntu1 --- sane-backends (1.0.31-2ubuntu1) hirsute; urgency=medium * debian/rules: - build again with --disable-locking since the feature currently not working correctly (lp: #1898905) -- Sebastien Bacher Thu, 29 Oct 2020 13:08:07 +0100 ** Changed in: sane-backends (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1898905 Title: Unfunctional plustek scanner in Ubuntu 20.10 Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends package in Debian: Unknown Bug description: There are multiple reports now of failing plustek backend in libsane 1.0.31-2 as shipped in Ubuntu 20.10 and Debian dev My report: https://gitlab.com/sane-project/backends/-/issues/363 Another report: https://gitlab.com/sane-project/backends/-/issues/360 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+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 1902228] Re: Unlocking the screen takes too long
My initial report was wrong, it still occurred in the GNOME session as well, just not at first? I tried it on Wayland and while it was much faster, it was still slower than I'd expect (5-10 seconds). Unfortunately running that command didn't work, as I got frustrated and switched to KDE -- 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/1902228 Title: Unlocking the screen takes too long Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.10, and unlocking the screen takes upwards of 20 seconds. If I switch to the "GNOME on Xorg" session instead of the "Ubuntu" session, the problem doesn't occur. It's only a problem with the Ubuntu session, and I've tried disabling extensions, changing theme, loading fewer apps, etc. The only thing that's made a difference was switching to the GNOME on Xorg session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902228/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
ok, got it, thx a lot. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1767431] Re: restore type-ahead find, again
Hi. I finally upgraded to 18.04 and Nautilus without type-ahead find is extremely limiting when it comes to file/folder navigation. I can't even fathom why it would be dropped. But if search is now the default action for when one starts typing, there should be a way to disable that, or enable type-ahead find, if not in an easily-found, user-friendly way, then at least as an option in Preferences. I know there is a patched version available, but I'd rather not have upgrade headaches which can arise from having patched versions of major system apps, so am just adding my voice to the countless others on the web begging for action on this. -- 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/1767431 Title: restore type-ahead find, again Status in nautilus package in Ubuntu: Confirmed Bug description: The dropping of the type-ahead find patch in 17.10 might deeply affect non-technical users, as pointed out, this is possibly a bad HCI design. As there is a patch exists from the Arch community[1], and the at least some people managed to patch it in 17.10[2], might it be possible to add such patch back before 18.04.1 so that it won't affect people upgraded from 16.04? [1]: https://aur.archlinux.org/nautilus-typeahead.git [2]: https://askubuntu.com/a/1002521 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767431/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
https://github.com/rtlwifi-linux/rtlwifi-next/issues -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I don't know, maybe it is a wireless mouse receiver? -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang, I tried to access https://github.com/rtlwifi-linux, but I didn't find where to report my issue. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Summary changed: - The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time + The rear panel of Lenovo P620 doesn't support more than one audio device at the same time -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 996717] Re: Color from gnome-control-center does nothing when pressed Calibrate button
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Won't Fix -- 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/996717 Title: Color from gnome-control-center does nothing when pressed Calibrate button Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: I try to calibrate my monitor using a i1Display LT using the Color configuration app from the gnome-control-center. The Calibrate...button is disabled until I connect the device, that becomes enabled. But then when pressed does nothing. No action, no error message, nothing. If I launch the app from a terminal I get the following error when the button is pressed: txelu@txelu-acer:~$ gnome-control-center color (gnome-control-center:4790): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed (gnome-control-center:4790): color-cc-panel-WARNING **: failed to install required component: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files I'm using a fresh install of ubuntu Precise Pangolin completely updated. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Tue May 8 21:12:40 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/996717/+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 1719143] Re: Unable to calibrate monitors through Gnome Control Center->Color
** Tags removed: artful ** Tags added: focal ** Summary changed: - Unable to calibrate monitors through Gnome Control Center->Color + Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] ** Tags added: 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/1719143 Title: Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Fresh install of Artful, using gnome-session to access vanilla GNOME session on Wayland (also tried on xorg). Attempting to calibrate monitors through Gnome Control Center->Devices->Color. All attempts ended at the point where I was asked to put the device onto the monitor, with the error: Calibration failed! An internal error occurred that could not be recovered. You can remove the calibration device. Syslog: Sep 24 12:19:31 desktop kernel: [ 262.849675] usb 3-6: new full-speed USB device number 7 using xhci_hcd Sep 24 12:19:32 desktop kernel: [ 262.990880] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:19:32 desktop kernel: [ 262.990882] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:19:32 desktop kernel: [ 262.990884] usb 3-6: Product: colormunki Sep 24 12:19:32 desktop kernel: [ 262.990885] usb 3-6: Manufacturer: X-Rite Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop gnome-shell[876]: drmModeSetCursor2 failed with (Permission denied), drawing cursor with OpenGL from now on Sep 24 12:19:32 desktop pulseaudio[953]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libEGL warning: wayland-egl: could not open /dev/dri/card0 (Permission denied) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: VA error: wayland: failed to open /dev/dri/card0: Permission denied (errno 13) Sep 24 12:19:32 desktop org.gnome.SettingsDaemon.Color.desktop[1000]: libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) I attempted to fix the permissions error for /dev/dri/card0. Current permissions: rwh@desktop:~$ ls -l /dev/dri/card0 crw-rw+ 1 root video 226, 0 Sep 24 12:15 /dev/dri/card0 Tried adding my user to video group, which made no difference. Then made file world r/w: rwh@desktop:~$ sudo chmod o+rw /dev/dri/card0 Which fixed that problem. Now, in the calibrate wizard, on the second step (Display Type) I am offered three options (LCD, CRT, Projector) where I only saw LCD previously. However, the calibration step failed the same as before. Syslog: Sep 24 12:36:46 desktop kernel: [ 1298.430546] usb 3-6: new full-speed USB device number 12 using xhci_hcd Sep 24 12:36:46 desktop kernel: [ 1298.571756] usb 3-6: New USB device found, idVendor=0971, idProduct=2007 Sep 24 12:36:46 desktop kernel: [ 1298.571759] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sep 24 12:36:46 desktop kernel: [ 1298.571760] usb 3-6: Product: colormunki Sep 24 12:36:46 desktop kernel: [ 1298.571762] usb 3-6: Manufacturer: X-Rite Sep 24 12:36:46 desktop pulseaudio[953]: message repeated 3 times: [ W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.] Sep 24 12:36:47 desktop gnome-control-c[5206]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Unable to initialize Clutter: Unable to initialize the Clutter backend: no available drivers found. Sep 24 12:36:47 desktop gnome-control-c[5201]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:36:47 desktop gnome-control-c[5206]: Error 71 (Protocol error) dispatching to Wayland display. Sep 24 12:37:21 desktop dbus-daemon[4121]: Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' Sep 24 12:37:21 desktop systemd[3601]: Starting
[Desktop-packages] [Bug 1902418] Re: Display Calibration: failed to calibrate with xrite colormunki
*** This bug is a duplicate of bug 1719143 *** https://bugs.launchpad.net/bugs/1719143 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1719143, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1719143 Unable to calibrate monitors through Gnome Control Center->Color [calibration failed with code 1: no sensor->get_sample] -- 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/1902418 Title: Display Calibration: failed to calibrate with xrite colormunki Status in gnome-control-center package in Ubuntu: New Bug description: I try to use the built in calibration tool of gnome in the absence of displaycal. Sadly the calibration doesn't start at all. 10:22:58 yelp: Recursion depth exceeded calculating fg color 10:22:42 gnome-control-c: failed to start calibrate: failed to calibrate 10:22:37 systemd: colord-session.service: Succeeded. 10:22:37 gnome-control-c: calibration failed with code 1: no sensor->get_sample 10:22:09 systemd: Started Color management helper. 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Successfully activated service 'org.freedesktop.ColorHelper' 10:22:09 systemd: Starting Color management helper... 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' requested by ':1.679' (uid=1000 pid=91822 comm="gnome-control-center " label="unconfined") ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-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: ubuntu:GNOME Date: Sun Nov 1 10:34:16 2020 InstallationDate: Installed on 2020-10-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902418/+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 1902361] Re: Delete key inputs Unicode Delete character (007F) instead of deleting the next character
That xev output looks correct, I get the same output from 'xev' but don't get this bug. Does the problem occur in GNOME Terminal or some other terminal app? Also do you have any accessibility settings enabled (look in Settings > Universal Access)? ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1902361 Title: Delete key inputs Unicode Delete character (007F) instead of deleting the next character Status in mutter package in Ubuntu: Incomplete Bug description: When pressed, the delete key inputs the Unicode 007F character instead of deleting the following character. In most cases, this is difficult to see, but in a terminal, the 007F is clearly visible. The xev output for the key press is following: KeyPress event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101326, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XmbLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0x5df, subw 0x0, time 81101443, (1403,948), root:(1453,1062), state 0x0, keycode 119 (keysym 0x, Delete), same_screen YES, XLookupString gives 1 bytes: (7f) "" XFilterEvent returns: False This is a new fresh install of Ubuntu 20.04, I don't remember the delete key working at any point since the installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 12:54:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics 620 (Whiskey Lake) [1025:1312] InstallationDate: Installed on 2020-10-14 (16 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Swift SF514-53T ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.name: Carlsberg_WL dmi.board.vendor: WL dmi.board.version: V1.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd04/25/2019:svnAcer:pnSwiftSF514-53T:pvrV1.09:rvnWL:rnCarlsberg_WL:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-53T dmi.product.sku: dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1902361/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Status: New => 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
ok, but what about that "Maxxter wireless receiver"? I don't understand: my laptop has 2 pieces of hardware to manage the wi-fi? -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1902464] [NEW] The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time
Public bug reported: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. ** Affects: oem-priority Importance: Undecided Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1900094 sutton ** Tags added: oem-priority originate-from-1900094 sutton -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device in at the same time Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1902464/+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 1902228] Re: Unlocking the screen takes too long
Please: 1. Tell us if the problem also occurs in 'Ubuntu on Wayland'. 2. Run this command to send us more information about the system: apport-collect 1902228 ** Tags added: groovy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1902228 Title: Unlocking the screen takes too long Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 20.10, and unlocking the screen takes upwards of 20 seconds. If I switch to the "GNOME on Xorg" session instead of the "Ubuntu" session, the problem doesn't occur. It's only a problem with the Ubuntu session, and I've tried disabling extensions, changing theme, loading fewer apps, etc. The only thing that's made a difference was switching to the GNOME on Xorg session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902228/+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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
Nicolas, If disabling 'Ubuntu AppIndicators' worked for you then it was probably bug 1849142. Please go to bug 1849142 and help to test the proposed fix for that. -- 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1900873] Re: dual display scaling broken at 4k
*** This bug is a duplicate of bug 1857383 *** https://bugs.launchpad.net/bugs/1857383 Actually I think bug 1857383 already covers this issue so let's use that. ** This bug has been marked a duplicate of bug 1857383 Fractional scaling applies to both monitors when you only want it on one -- 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/1900873 Title: dual display scaling broken at 4k Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have to 4k monitors. 15" on the dell xps 3840/2160/60 40" philips external BDM4065 3840/2160/30 Obviously i need different scale factors to use them properly. This feature DOES NOT WORK. It seems the scaling is not handled separately per monitor as the UI suggests. The fractional scaling also does not seem to work. any change to the scaling ends seems to be rounded to full. Which meens a compromise scale of 125% is effectively 200% on the large monitor. I havent found any config which would make this useful. So basically when I use the external 40" I cannot use the builtin anymore without an external fresnell magnifier lens (which I dont have ;) updated Ubuntu 20.04.1 LTS on DELL XPS 7590 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz 32GB SODIMM DDR4 Synchronous 2667 (0.4ns) PCI bridge: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] Hostbridge: Intel UHD Graphics 630 (Mobile) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 21 17:35:12 2020 InstallationDate: Installed on 2020-04-22 (181 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1900873/+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 1902436] Re: Mouse slow in fractional scaling
This bug is somewhat expected because fractional scaling works by rendering the desktop at a higher resolution than your screen. So it will take more mouse movement for the pointer to cross the screen. Integer scaling doesn't work that way so the mouse should move at "normal" speed there. ** Tags added: xrandr-scaling ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1902436 Title: Mouse slow in fractional scaling Status in mutter package in Ubuntu: Triaged Bug description: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use both at the same time, my mouse starts to be slow. So in this scenario i have the external monitor at 100% and the notebook screen at 150%. Everything works fine expect the mouse which is slow,on both screens. What I found is, when i set both my screens to 200% while fractional scaling is enabled. The issue is gone. Same with 100%. But as soon as I start using fractions, the mouse is slow again. I don't believe it is an power issue because my hardware is mostly in idle. Also, i tried different mouses over Bluetooth and USB but no change. I am currently using 20.10 but had the same issue with 20.04. But when i use Wayland, the problem is gone. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 14:01:59 2020 DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed soundwire, 1.2.2: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:098f] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f] InstallationDate: Installed on 2020-09-19 (42 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 17 9700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) dmi.bios.date: 08/18/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0P1CHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@smurf, OK, got your wifi's type, it is rtl8822ce, I will check if I could find a machine with this Wifi chip in the office. BTW, you could raise your issue to https://github.com/rtlwifi-linux too, and I found there is a driver specific to 8822ce: https://github.com /rtlwifi-linux/rtk_wifi_driver_rtl8822ce -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~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 1777708] Re: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time
I have updated to 20.10 and can confirm disabling scroll lock workaround is still working. Another thing i've just realized is without this hack, there is a huge lag during lock/unlock/login animations. Commenting scroll lock line in /usr/share/X11/xkb/symbols/br made animations a lot better. -- 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/108 Title: Desktop briefly becomes unresponsive when typing on 2 keyboards at the same time Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04 and Gnome 3.28.1 with all the latest updates from the repos. If I connect 2 (or more) keyboards to my computer and type on both at the same time, the desktop briefly becomes unresponsive. More keypresses increase the time of unresponsiveness. E.g. when typing a full sentence in gedit or the terminal, only very few characters show up on the screen (I guess up until something is pressed on both keyboards at the same time), then everything freezes. Then after a while (some seconds), all the characters show up. And the desktop becomes responsive again. Symptoms: During the freeze, windows stop updating their content. If seconds are enabled on the clock at the top middle, these freeze too. But I'm still able to move the mouse pointer around during the freeze without any problems. The back story: I got an ergonomic keyboard (R-Go Split Keyboard) yesterday, and quickly noticed the issue. But initiallly I thought it was an issue with the keyboard, and the problem wasn't that bad. But as I've gotten more used to the keyboard since yesterday and started picking up a proper typing speed, things got worse. The keyboard is technically two separate cabled USB keyboards each with only about half of they keys of a normal keyboard (or at least that's very much my impression). After getting the suspicion that this was a software issue, not a hardware issue, I tried typing on my old Logitech keyboard (Unifying Receiver) along with one of the R-Go halves: Same issue. Then I tried each of the halves without the other (as in "single" keyboard typing): No issue. Then I connected another Logitech keyboard (separate UR), typed on both Logitechs: Same issue. Some further observations: 1) Nothing of significance in my syslog. 2) If I drop to a non-graphical shell, there's no problem. I suspect this issue is related to X.org or Gnome, but I'm in no position to say anything credible about that. 3) Also no problems when connecting the R-Go keyboard to a Windows or a MacOS machine. Let me know if there are any logs I can provide or things I can run to produce useful debug output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Hui Wang, actually I can't switch to hsp/hfp mode. In BlueMan device window, if I try to switch profile I receive an error (the red bar at window bottom) and in Pulseaudio I don't have the option to switch. Furthermore, in Blueman window manager, when I connect the headphone I see an orange button with an orange bar above, a green button with no bar above and a blue button with a blue bar above. If I use a tp-link dongle I see the green bar as well. On the same laptop I have windows 10 (dual boot) and there the headphone microphone works fine. Here lspci and lusb output,let me know if you need some more info. luca@laptop-luca:~$ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:01.7 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal PCIe GPP Bridge 0 to Bus A 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c2) 03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller 03:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 03:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 03:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 03:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor 03:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller luca@laptop-luca:~$ lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 1358:c123 Realtek Bluetooth Radio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:56f9 IMC Networks Bus 001 Device 004: ID 27c6:5110 Shenzhen Goodix Technology Co.,Ltd. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub luca@laptop-luca:~$ -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20
[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
i have also Problems with my internal MIC on HP x360 1040: https://bugzilla.kernel.org/show_bug.cgi?id=201251#c231 -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Problem on my HP x360 1040 G5 with the internal MIC: https://bugzilla.kernel.org/show_bug.cgi?id=201251#c231 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1898389] Re: browser frequently crashing with trap int3
the new version of Chromium seems to be a disaster when I try to go to full screen in YouTube. It scatters parts of the screen amongst my various virtual desktops and creates a huge mess, forcing me to kill chromium from the command line. On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- 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/1898389 Title: browser frequently crashing with trap int3 Status in chromium-browser package in Ubuntu: Incomplete Bug description: I used to be able to have many tabs open with Chromium without problems. Lately it crashes or gives "aw snap" errors (see kernel messages below) if I start to keep more than 25 or so open. Description:Ubuntu 16.04.7 LTS Release:16.04 chromium-browser: Installed: 85.0.4183.83-0ubuntu0.16.04.2 Candidate: 85.0.4183.121-0ubuntu0.16.04.1 Version table: 85.0.4183.121-0ubuntu0.16.04.1 500
[Desktop-packages] [Bug 1902446] [NEW] Not possible to see list of wifi networks
Public bug reported: Using the default 'light' theme, the network listing is impossible to read ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 19:41:38 2020 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-15 (1355 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Workspace 1_350.png" https://bugs.launchpad.net/bugs/1902446/+attachment/5430088/+files/Workspace%201_350.png -- 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/1902446 Title: Not possible to see list of wifi networks Status in network-manager package in Ubuntu: New Bug description: Using the default 'light' theme, the network listing is impossible to read ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 19:41:38 2020 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-15 (1355 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902446/+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 1879580] Re: Screencast interface missing
We need an update on this issue. The fact that there has not been any progress posted in this thread is very disconcerting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+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 1753509] Re: avahi-daemon adds/installs every printer on network
please also refer to lp:1379359 and to the GTK2/3 patch at https://launchpad.net/~roman- shipovskij/+archive/ubuntu/gtk+3.0-withoutavahiprinters -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups-filters package in Ubuntu: Expired Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+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 1753509] Re: avahi-daemon adds/installs every printer on network
This bug surely does not belong to "cups-filters" package. And probably it does not belong to Avahi. And to CUPS either. This bug does belong to GTK library and GTK apps which do not provide an option like "list only local CUPS printers, not everything Avahi has sniffed on the network". Avahi is right in its actions, and there are other software relying on its "enable-dbus" option. GTK as library is wrong in having this option enabled by default, and probably some of GTK apps have now learned to override this option properly (that is, in usable and understandable way for an end user). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups-filters package in Ubuntu: Expired Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
edit: #236 was for 3140 touchpad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coilby Xu, all good on fresh Ubuntu 20.10 5.8-26 Generic and Manjaro gnome 20.2-Pre4 Testing. For Polling method steps 1. Download file from Message #217 file 2. Extract to folder, enter folder and subfolder. 3. run make (needs apt-get make gcc linux-headers #211 instuctions 4. follow #228 for ubuntu, copy replace existing ko file, rmmod insmod then depmod, change Grub2 for Ubuntu 5. reboot Job done. if want test to see,before 4. Follow #212 Thanks Coilby Xu and others Simples! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.
I have finally ended up with binding both « thumbnails » folders through fstab adding those lines : # .xcf thumbnails from gimp snap for anyone /home/user_1/.cache/thumbnails/ /home/user_1/snap/gimp/common/.cache/thumbnails/nonebind0 0 /home/user_2/.cache/thumbnails/ /home/user_2/snap/gimp/common/.cache/thumbnails/nonebind0 0 /home/user_3/.cache/thumbnails/ /home/user_3/snap/gimp/common/.cache/thumbnails/nonebind0 0 This way, Gimp-snap actually writes its thumbnails there and then Nemo and Nautilus accordingly displays thumbnails for .xcf files. gThumb though still shows empty frames for .xcf files - but my main concern was the file explorer. Thanks to https://forum.ubuntu- fr.org/viewtopic.php?pid=22362050#p22362050 -- 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/1883457 Title: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else. Status in gimp package in Ubuntu: New Status in gnome-xcf-thumbnailer package in Ubuntu: New Status in gthumb package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in nemo package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: Hi, On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see thumbnails for .xcf files only « inside » Gimp and nowhere else ( Nemo, Nautilus, gThumb… ) I did a messy workaround for .xcf thumbnails to appear anywhere expected : I put all of my user’s thumbnails into ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is a symlink targeting the first. You’d agree it’s absolutely a bad idea to store all of an user’s thumbnails into a particular subfolder of a particular snap. How tell my session to look for thumbnails not only in ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/ ? For references : ⋅ https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files ⋅ https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799 ⋅ https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup 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/ubuntu/+source/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 1902436] Re: Mouse slow in fractional scaling
I forgot to say that this problem is only with the external mouse. With the touch pad, i have no issue. I have an RTX 2060 Max-q in my notebook with Nvidia driver installed but it is deactivated as on demand. But even if I enable this card, it has no effect. I believe that because of the fractional scaling, the reading of the input device gets somehow mixed up. -- 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/1902436 Title: Mouse slow in fractional scaling Status in xorg package in Ubuntu: New Bug description: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use both at the same time, my mouse starts to be slow. So in this scenario i have the external monitor at 100% and the notebook screen at 150%. Everything works fine expect the mouse which is slow,on both screens. What I found is, when i set both my screens to 200% while fractional scaling is enabled. The issue is gone. Same with 100%. But as soon as I start using fractions, the mouse is slow again. I don't believe it is an power issue because my hardware is mostly in idle. Also, i tried different mouses over Bluetooth and USB but no change. I am currently using 20.10 but had the same issue with 20.04. But when i use Wayland, the problem is gone. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 14:01:59 2020 DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed soundwire, 1.2.2: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:098f] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f] InstallationDate: Installed on 2020-09-19 (42 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 17 9700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) dmi.bios.date: 08/18/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0P1CHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Desktop-packages] [Bug 1902432] Re: Carte son non detectée pourtant vu dans le terminal (son sortie fictive)
I am on an ASUS X555BP initially Windows 8 then update for Windows 10. Following a modification by myself on the graphics card (update) there was an incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits under gnome 3.36.3. No problem to play a video etc except that the sound does not come out. In the terminal I have already uninstalled and reinstalled Pulse Audio, Alsa etc. It is able to give me the name of my graphics card when I query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but no card is detected when I type aplay -l. Normally the operating system automatically installs drivers compatible with my graphics card so I don't know what to do. According to apt-cache I am using apt 2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load detection. It accepts to be in charge once in ten which did not happen before. My computer was checked by a computer scientist, I have no hard drive or motherboard problem. ** Summary changed: - Carte son non detectée pourtant vu dans le terminal (son sortie fictive) + Sound card not detected yet seen in the terminal (fictitious output sound) ** Description changed: Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. Suite à une modification de ma part sur la carte graphique (maj) il y a eut une incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l. Normalement le système d'exploitation installe automatiquement des drivers compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après apt-cache j'use apt 2.0.2ubuntu0.1 (amd64). + Oh et j'ai aussi un problème de detection de mise en charge de ma batterie d'ordinateur, je ne sais pas si c'est lié. Cependant cela n'arrivait pas avant. Un informaticien a déjà regardé mon oridinateur, je n'ai pas de problème de disque dur ou de carte mère. + + I am on an ASUS X555BP initially Windows 8 then update for Windows 10. Following a modification by myself on the graphics card (update) there was an incompatibility so I went on Ubuntu 20.04.1 LTS by usb key . I am in 64 bits under gnome 3.36.3. No problem to play a video etc except that the sound does not come out. In the terminal I have already uninstalled and reinstalled Pulse Audio, Alsa etc. It is able to give me the name of my graphics card when I query it through sudo lspci A9-9420 radeon r5, 5 compute cores 2c + 3g × 2 but no card is detected when I type aplay -l. + Normally the operating system automatically installs drivers compatible with my graphics card so I don't know what to do. According to apt-cache I am using apt 2.0.2ubuntu0.1 (amd64) and I have also struggle with my computer's load detection. It accepts to be in charge once in ten which did not happen before. My computer was checked by a computer scientist, I have no hard drive or motherboard problem. 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: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 13:52:11 2020 InstallationDate: Installed on 2020-10-13 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555BP.326 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555BP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555BP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- You received this bug notification because you are a member of Desktop
[Desktop-packages] [Bug 1902436] [NEW] Mouse slow in fractional scaling
Public bug reported: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use both at the same time, my mouse starts to be slow. So in this scenario i have the external monitor at 100% and the notebook screen at 150%. Everything works fine expect the mouse which is slow,on both screens. What I found is, when i set both my screens to 200% while fractional scaling is enabled. The issue is gone. Same with 100%. But as soon as I start using fractions, the mouse is slow again. I don't believe it is an power issue because my hardware is mostly in idle. Also, i tried different mouses over Bluetooth and USB but no change. I am currently using 20.10 but had the same issue with 20.04. But when i use Wayland, the problem is gone. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 14:01:59 2020 DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed soundwire, 1.2.2: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:098f] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f] InstallationDate: Installed on 2020-09-19 (42 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 17 9700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) dmi.bios.date: 08/18/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0P1CHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- 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/1902436 Title: Mouse slow in fractional scaling Status in xorg package in Ubuntu: New Bug description: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use
[Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
A mi también me ocurre este error ** Attachment added: "tb-profile-extensions.zip" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+attachment/5430014/+files/tb-profile-extensions.zip -- 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/1901829 Title: thunderbird fails to open, xml parse error Status in thunderbird package in Ubuntu: Confirmed Bug description: launching thunderbird opens a small browser window displaying the following error: XML Parsing Error: undefined entity Location: chrome://messenger/content/messenger.xhtml Line Number 905, Column 3: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901829/+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 1900452] Autopkgtest regression report (ubuntu-drivers-common/1:0.8.6.2)
All autopkgtests for the newly accepted ubuntu-drivers-common (1:0.8.6.2) for groovy have finished running. The following regressions have been reported in tests triggered by the package: software-properties/0.99.3 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#ubuntu-drivers-common [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1900452 Title: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu- drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__ Status in ubuntu-drivers-common package in Ubuntu: Incomplete Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Listing the supported drivers can fail if the linux-restricted-modules for it are not available in the archive. * These changes unify the code for listing drivers (whether --gpgpu is passed in or not) and make it more robust. [Test Case] * Install ubuntu-drivers-common (1:0.8.6.2) from -proposed. * Call "ubuntu-drivers list" and "ubuntu-drivers list --gpgpu", and make sure that neither crashes ubuntu-drivers. [Regression Potential] * Low, the code should catch all the KeyErrors now. The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.4~0.20.04.3, the problem page at https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+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 1902432] Re: Carte son non detectée pourtant vu dans le terminal (son sortie fictive)
Thank you for taking the time to report this issue and helping to make Ubuntu better. We noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be more understandable to triagers. Could you please translate them? ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1902432 Title: Carte son non detectée pourtant vu dans le terminal (son sortie fictive) Status in alsa-driver package in Ubuntu: Incomplete Bug description: Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. Suite à une modification de ma part sur la carte graphique (maj) il y a eut une incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l. Normalement le système d'exploitation installe automatiquement des drivers compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après apt-cache j'use apt 2.0.2ubuntu0.1 (amd64). 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: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 13:52:11 2020 InstallationDate: Installed on 2020-10-13 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555BP.326 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555BP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555BP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1902432/+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 1902432] [NEW] Carte son non detectée pourtant vu dans le terminal (son sortie fictive)
Public bug reported: Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. Suite à une modification de ma part sur la carte graphique (maj) il y a eut une incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l. Normalement le système d'exploitation installe automatiquement des drivers compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après apt-cache j'use apt 2.0.2ubuntu0.1 (amd64). 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: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 13:52:11 2020 InstallationDate: Installed on 2020-10-13 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555BP.326 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555BP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555BP.326:bd05/13/2019:svnASUSTeKCOMPUTERINC.:pnX555BP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555BP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555BP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal -- 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/1902432 Title: Carte son non detectée pourtant vu dans le terminal (son sortie fictive) Status in alsa-driver package in Ubuntu: Incomplete Bug description: Je suis sur un ASUS X555BP initialement Windows 8 puis maj pour windows 10. Suite à une modification de ma part sur la carte graphique (maj) il y a eut une incompatibilité donc j'ai du passé sur Ubuntu 20.04.1 LTS par clé usb. Je suis en 64 bits sous gnome 3.36.3. Aucun problème pour lire une vidéo etc si ce n'est que le son ne sort pas. Dans le terminal j'ai déjà désintallé et réinstallé Pulse Audio. Il est capable de me sortir le nom de ma carte graphique quand je l'interroge par sudo lspci A9-9420 radeon r5, 5 compute cores 2c+3g × 2 mais aucune carte n'est détecté quand je tape aplay -l. Normalement le système d'exploitation installe automatiquement des drivers compatibles avec ma carte graphique donc je ne sais pas quoi faire. D'après apt-cache j'use apt 2.0.2ubuntu0.1 (amd64). 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: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 13:52:11 2020 InstallationDate: Installed on 2020-10-13 (18 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555BP.326 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555BP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Desktop-packages] [Bug 1899509] Re: Mouse/touchpad settings not applied on hotplug/reconnect
I think I am also experiencing this bug. I have a bluetooth trackpad (Magic Trackpad 1 by Apple), and since a few weeks ago, the scrolling direction is reversed by default, and the tap to click feature is disabled. I can go to the trackpad settings and everything is alright. I can disable and re-enable these settings, and it works fine once again, but only until the next reboot, where I have to do the same thing again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1899509 Title: Mouse/touchpad settings not applied on hotplug/reconnect Status in gnome-control-center: Unknown Status in GNOME Settings Daemon: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When I plug in a touchpad via USB, my chosen scrolling and speed settings are not applied, unless I adjust them again in the settings UI. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1899509/+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 1902367] Re: Dock at bottom does not allow icons drag on free space
** Description changed: Ubuntu desktop 20.04.1 up to date to latest @ 31/10/2020 with kernel 5.4.0-52-generic - With the dock placed at bottom, new icons cannot drag onto the (right) free space - of the dock, just in between 2 other icons - - with the dock placed left or right its possible to add icons at (bottom) - free space + The dock does not allow dragging new icons on the free space of the dock + only allows to add in between 2 other icons or when the dock is full with icons it allows adding after the last one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 14:40:09 2020 InstallationDate: Installed on 2020-03-14 (230 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Dock at bottom does not allow icons drag on free space + Dock does not allow icons drag on free space -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1902367 Title: Dock does not allow icons drag on free space Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu desktop 20.04.1 up to date to latest @ 31/10/2020 with kernel 5.4.0-52-generic The dock does not allow dragging new icons on the free space of the dock only allows to add in between 2 other icons or when the dock is full with icons it allows adding after the last one. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 31 14:40:09 2020 InstallationDate: Installed on 2020-03-14 (230 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1902367/+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 1902418] [NEW] Display Calibration: failed to calibrate with xrite colormunki
Public bug reported: I try to use the built in calibration tool of gnome in the absence of displaycal. Sadly the calibration doesn't start at all. 10:22:58 yelp: Recursion depth exceeded calculating fg color 10:22:42 gnome-control-c: failed to start calibrate: failed to calibrate 10:22:37 systemd: colord-session.service: Succeeded. 10:22:37 gnome-control-c: calibration failed with code 1: no sensor->get_sample 10:22:09 systemd: Started Color management helper. 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Successfully activated service 'org.freedesktop.ColorHelper' 10:22:09 systemd: Starting Color management helper... 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' requested by ':1.679' (uid=1000 pid=91822 comm="gnome-control-center " label="unconfined") ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-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: ubuntu:GNOME Date: Sun Nov 1 10:34:16 2020 InstallationDate: Installed on 2020-10-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1902418 Title: Display Calibration: failed to calibrate with xrite colormunki Status in gnome-control-center package in Ubuntu: New Bug description: I try to use the built in calibration tool of gnome in the absence of displaycal. Sadly the calibration doesn't start at all. 10:22:58 yelp: Recursion depth exceeded calculating fg color 10:22:42 gnome-control-c: failed to start calibrate: failed to calibrate 10:22:37 systemd: colord-session.service: Succeeded. 10:22:37 gnome-control-c: calibration failed with code 1: no sensor->get_sample 10:22:09 systemd: Started Color management helper. 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Successfully activated service 'org.freedesktop.ColorHelper' 10:22:09 systemd: Starting Color management helper... 10:22:09 dbus-daemon: [session uid=1000 pid=1525] Activating via systemd: service name='org.freedesktop.ColorHelper' unit='colord-session.service' requested by ':1.679' (uid=1000 pid=91822 comm="gnome-control-center " label="unconfined") ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-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: ubuntu:GNOME Date: Sun Nov 1 10:34:16 2020 InstallationDate: Installed on 2020-10-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1902418/+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 1902415] Re: Apps wont start via wslusc
** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. - There is no error output when I run shortcut in cmd, neither whole - command. + There is no error output when I run shortcut in cmd, neither when I run + whole command. I tried several gui apps and none of them works. App is running well in wsl terminal of course. ** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither when I run whole command. I tried several gui apps and none of them works. App is running well in wsl terminal of course. + + Distributor ID: Ubuntu + Description:Ubuntu 20.04.1 LTS + Release:20.04 + Codename: focal ** Summary changed: - Apps wont start via wslusc + Ubuntu app wont start - shortcut from wslusc ** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither when I run whole command. I tried several gui apps and none of them works. - App is running well in wsl terminal of course. + Apps are running well in wsl terminal of course. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1902415 Title: Ubuntu app wont start - shortcut from wslusc Status in wslu package in Ubuntu: New Bug description: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither when I run whole command. I tried several gui apps and none of them works. Apps are running well in wsl terminal of course. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1902415/+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 1902415] [NEW] Apps wont start via wslusc
Public bug reported: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither whole command. App is running well in wsl terminal of course. ** Affects: wslu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "01.jpg" https://bugs.launchpad.net/bugs/1902415/+attachment/5429956/+files/01.jpg ** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd - app. But nothing happen. + app. But nothing happens. There is no error output when I try it run shortcut in cmd, neither whole command. App is running well in wsl terminal of course. ** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. - There is no error output when I try it run shortcut in cmd, neither - whole command. + There is no error output when I try run shortcut in cmd, neither whole + command. App is running well in wsl terminal of course. ** Description changed: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. - There is no error output when I try run shortcut in cmd, neither whole + There is no error output when I run shortcut in cmd, neither whole command. App is running well in wsl terminal of course. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1902415 Title: Apps wont start via wslusc Status in wslu package in Ubuntu: New Bug description: I am trying to run created desktop shortcut to open my wsl gui doublecmd app. But nothing happens. There is no error output when I run shortcut in cmd, neither whole command. App is running well in wsl terminal of course. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1902415/+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
