[Desktop-packages] [Bug 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.
Thanks for the clarification. Although assigning the bug to 'wayland' is incorrect because that source package is for the protocol only. No binaries come from 'wayland'. ** Package changed: wayland (Ubuntu) => libreoffice (Ubuntu) ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in libreoffice package in Ubuntu: New Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. 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: zfs zunicode zavl icp zcommon znvpair 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: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 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 20.2.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.
For Firefox, this is a duplicate of bug 1312376. The fix/workaround is to use environment MOZ_USE_XINPUT2=1 or MOZ_ENABLE_WAYLAND=1 in your /etc/environment. For Tor Browser, if that did not come from Ubuntu then we can't track its bugs on this site. For LibreOffice, there doesn't seem to be a bug for this yet that I can find, so this bug is now about LibreOffice. ** No longer affects: firefox (Ubuntu) ** Tags added: touchscreen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in libreoffice package in Ubuntu: New Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. 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: zfs zunicode zavl icp zcommon znvpair 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: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 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 20.2.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/+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 1312376] Re: touch screen in browser not scrolling
** Changed in: firefox (Ubuntu) Status: Fix Committed => Confirmed ** Tags removed: fixed-in-81 fixed-upstream ** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1312376 Title: touch screen in browser not scrolling Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: Hi team, I wanted to highlight a problem with my touch screen laptop not scrolling on touch. It doesn't grab and scroll but highlights the text in the browser. Please feel free to ask for more information as I am more than happy to help! thanks Morlando To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1312376/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.
Since Tor Browser is a modified version of Firefox I am guessing the same fix works there: MOZ_USE_XINPUT2=1 and/or MOZ_ENABLE_WAYLAND=1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in libreoffice package in Ubuntu: New Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. 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: zfs zunicode zavl icp zcommon znvpair 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: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 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 20.2.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 04:33:43PM -, Baq Domalaq wrote: >Hi everyone! I have the same problem with my touchpad on Lenovo Ideapad >Gaming 3 15ARH05 under Pop!_OS. > >My touchpad device number is slightly different: >MSFT0001:00 06CB:CE2D > >I've applied a patch in comment #179 (I assumed that's the most fitting >solution for me) and it works now! Thank you people for trying to fix >this. > >Anyway the comments now are very long and confusing. And I'm not sure if >I used the best solution. So if anyone can point to something better, >let me know. > The touchpads on Legion-5 could be saved by either polling (#179) or interrupt (#171). I've submitted both patches upstream for these two methods. After getting reviewed by the kernel developer community, I will keep improving them until these patches get accepted by the maintainer. I would suggest you try #171 before the patches getting merged into the mainline kernel. If it doesn't work, you can send me your ACPI DSDT table. >Also let me know how to help with pushing this to official kernel. I've >posted an issue to Pop OS Github repo. I'll also add a comment about my >workarounds there. > You can send me your email address. I'll Cc you when submitting the patch(es). Then you can test the received patch and reply to the email with a Tested-by tag if the patch(es) works, Tested-by: Your_name >Have a nice day! > -- 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 amd
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 07:38:15PM -, Azizkhan wrote: >Hi all! >@Coiby Xu (coiby) >When your patch will be applied to mainline kernel? When we can just update >our kernels and do nothing to fix touchpad? I'm not sure when these patch(es) will be accepted and merged. It's up to the maintainers to accept the patch(es). If there is any update, I'll post the notification here. -- 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
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
On Sun, Nov 08, 2020 at 01:14:48PM -, Mike Boruta wrote: >Definitely! The attached output was compiled from 5.4.0-52 with the >patch listed in 171. #171 should fix your touchpad. According to your shared gpio-config, that patch didn't take effect. So I guess you are still using the old pinctrl-amd module. -- 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:cvnL
[Desktop-packages] [Bug 1903329] Re: SRU the current 2.48.9 stable update
Note that the fix for upstream issue 642, which is one of the drivers for this SRU, hasn't been released in the 2.50.x series yet (it's only a commit on the master branch: https://gitlab.gnome.org/GNOME/librsvg/-/commit/da90a31c6604f747f290e236045d8c79d1186747). The SRU process requires that a bug be fixed in the development release first, before considering a stable update (https://wiki.ubuntu.com/StableReleaseUpdates#Procedure). I asked Federico what his plans are for a 2.50.2 release (https://gitlab.gnome.org/GNOME/librsvg/-/issues/642#note_957195), let's see what he says before going ahead. ** Bug watch added: gitlab.gnome.org/GNOME/librsvg/-/issues #642 https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 ** Also affects: librsvg (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: librsvg (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu Focal) Importance: Undecided => High ** Changed in: librsvg (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1903329 Title: SRU the current 2.48.9 stable update Status in librsvg package in Ubuntu: Confirmed Status in librsvg source package in Focal: Confirmed Bug description: * Impact That's the current GNOME stable update, which fixes a number of issues, including a regression[1] since librsvg 2.40.x which was shipped in Ubuntu 16.04. The NEWS file[2] summarizes the relevant changes between Ubuntu 20.04's current librsvg 2.48.7 (that version was also introduced by an SRU back in July[3]) and the current version 2.48.9. The complete list of changes is available on GNOME GitLab[4]. * Test case The update is part of GNOME stable updates[5]. Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. * Notes about this report This is my first SRU request (and at the same time my first launchpad bug report). I'm not really familiar with the whole SRU process which is why I first asked about it on Ubuntu's official discourse forum[6]. Canonical's Sebastien Bacher encouraged me to open this ticket. I've copied over some parts of the last librsvg SRU ticket[3]. I hope this is fine. Thanks for considering this SRU. [1]: https://gitlab.gnome.org/GNOME/librsvg/-/issues/642 [2]: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS [3]: https://bugs.launchpad.net/bugs/1884326 [4]: https://gitlab.gnome.org/GNOME/librsvg/-/compare/2.48.7...2.48.9 [5]: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [6]: https://discourse.ubuntu.com/t/most-straight-forward-way-to-get- librsvg2-microrelease-update-into-focal-updates/19238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1903329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The patch in #239 depends on this patch [1] which requires to build the whole kernel. For now, I would suggest adopting #189 to fix the touchpad for daily use. But if anyone want to test the patch so we can push it into the mainline kernel early, you can send me your email address and I'll Cc you when submitting next version. https://patchwork.ozlabs.org/project/linux- gpio/patch/20201109205332.19592-12-andriy.shevche...@linux.intel.com/. -- 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.moda
[Desktop-packages] [Bug 1877039] Re: gnome-terminal maximize then un-maximize shrinks one pixel
Met with exactly same issue after upgrading from 18.04 to 20.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1877039
Title:
gnome-terminal maximize then un-maximize shrinks one pixel
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
If I open a new terminal ('ctrl-alt-t' or from the run menu), then maximize
and un-maximize i get odd behavior. maximize does fine, but then clicking the
'un-maximize' does restore the terminal window to the previous size *minus* 1
pixel in each horizontal and vertical.
If i repeat that, each time the terminal size shrinks by 1 pixel.
I'd expect that it return it to the size it was before maximize.
I found a similar bug in "Bug #1521302" from a few years ago
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-terminal 3.36.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 6 09:05:32 2020
InstallationDate: Installed on 2020-04-30 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877039/+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 1903668] [NEW] HDMI audio device disappears and is unavailble after several minutes of not being used
Public bug reported: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: New Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fre
[Desktop-packages] [Bug 1877039] Re: gnome-terminal maximize then un-maximize shrinks one pixel
Find a workaround in this link: https://gitlab.gnome.org/GNOME/gnome-
terminal/-/issues/129
Run below command and restart gnome-termianl, works for me.
dconf write /org/gnome/terminal/legacy/headerbar '@mb false'
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #129
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/129
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1877039
Title:
gnome-terminal maximize then un-maximize shrinks one pixel
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
If I open a new terminal ('ctrl-alt-t' or from the run menu), then maximize
and un-maximize i get odd behavior. maximize does fine, but then clicking the
'un-maximize' does restore the terminal window to the previous size *minus* 1
pixel in each horizontal and vertical.
If i repeat that, each time the terminal size shrinks by 1 pixel.
I'd expect that it return it to the size it was before maximize.
I found a similar bug in "Bug #1521302" from a few years ago
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-terminal 3.36.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 6 09:05:32 2020
InstallationDate: Installed on 2020-04-30 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877039/+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 1903668] Re: HDMI audio device disappears and is unavailble after several minutes of not being used
Please try uninstalling 'pipewire', which is used by KDE and is known to interfere with PulseAudio. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: Incomplete Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903668/+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 1902244] Re: Backport packages for 20.04.1 HWE stack
Hello Timo, or anyone else affected, Accepted llvm-toolchain-11 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm- toolchain-11/1:11.0.0-2~ubuntu20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: llvm-toolchain-11 (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: libdrm (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: New Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Please test proposed package
Hello Timo, or anyone else affected, Accepted libdrm into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.102-1ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: New Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: New Status in xorg-server source package in Focal: New Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1679985] Re: Xmir -rootless: Client-side decoration minimize buttons don't yet work
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1679985 Title: Xmir -rootless: Client-side decoration minimize buttons don't yet work Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir -rootless: Client-side decoration minimize buttons don't yet work I know this because I implemented maximize support today. So now both the close and maximize client-side decoration buttons are supported. Just not minimize yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1679985/+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 1672949] Re: nautilus 'Desktop' window on Xmir is transparent
** Changed in: xorg-server (Ubuntu) Status: Fix Committed => Won't Fix -- 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/1672949 Title: nautilus 'Desktop' window on Xmir is transparent Status in Canonical System Image: Fix Committed Status in nautilus package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: nautilus 'Desktop' window on Xmir is transparent. I can't see any wallpaper or icons. Although if you drag within the window you can see the selection rectangle. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672949/+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 1671745] Re: Xmir cursor flickers while holding down modifier keys
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1671745 Title: Xmir cursor flickers while holding down modifier keys Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir cursor flickers while holding down modifier keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671745/+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 1675481] Re: Xmir crashes when using the '-fd' option
** Changed in: xorg-server (Ubuntu) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1675481 Title: Xmir crashes when using the '-fd' option Status in xorg-server package in Ubuntu: Won't Fix Bug description: I'm trying to use the '-fd' option in Xmir and get a crash when Xmir starts up. This is what I'm doing: I'm using socket()/bind()/listen()/accept() on a AF_UNIX socket at /tmp/.X11-unix/X0 (or whatever available display number). DISPLAY is then set based on this. Then, when an X app accesses that socket, the code then starts Xmir and passes the fd returned in the accept() call to Xmir in the '-fd' option. This is what I get in journalctl when this crash occurs: http://pastebin.ubuntu.com/24235520/ I installed the Xmir debug symbols and also passed in '-core' when starting Xmir and here is the bt: http://pastebin.ubuntu.com/24236088/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1675481/+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 1677540] Re: Corrupted mouse pointer icon in Mir/Unity8
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1677540 Title: Corrupted mouse pointer icon in Mir/Unity8 Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in libsdl2 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Won't Fix Bug description: Ubuntu 17.04 unity8 corrupted mouse pointer icon (see attaches screenshot, the mouse pointer is hovering places/Home on the file manager app, the orange block/square) mostly i see when i run apps with Xmir, maybe stuff that uses SDL, mpv, neverball and it's only the arrow pointer, the rest are not affected, resize arrows etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1677540/+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 1671744] Re: Xmir -rootless: xterm menus (Ctrl+button) are nonresponsive
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1671744 Title: Xmir -rootless: xterm menus (Ctrl+button) are nonresponsive Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir -rootless: xterm menus (Ctrl+button) are nonresponsive Workaround: Xmir -rootless -flatten To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1671744/+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 1668449] Re: [unity8] terminator Xmir - transparency doesn't work
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1668449 Title: [unity8] terminator Xmir - transparency doesn't work Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: [unity8] terminator Xmir - transparency doesn't work see attached screenshot (transparency works fine on unity7) although it's a gtk3 app, it doesn't run native. launch terminator with Xmir, right click to open the menu, Preferences -> Profiles -> Background and change transparency to whatever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668449/+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 1664843] Re: Xmir -rootless: glxinfo reports "Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1)."
** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1664843 Title: Xmir -rootless: glxinfo reports "Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1)." Status in xorg-server package in Ubuntu: Won't Fix Bug description: When Xmir is running -rootless, glxinfo reports errors: OpenGL core profile extensions: GL_3DFX_texture_compression_FXT1, GL_AMD_conservative_depth, GL_AMD_draw_buffers_blend, GL_AMD_performance_monitor, GL_AMD_seamless_cubemap_per_texture, GL_AMD_shader_trinary_minmax, GL_AMD_vertex_shader_layer, GL_AMD_vertex_shader_viewport_index, GL_ANGLE_texture_compression_dxt3, GL_ANGLE_texture_compression_dxt5, GL_APPLE_object_purgeable, GL_ARB_ES2_compatibility, GL_ARB_ES3_1_compatibility, GL_ARB_ES3_compatibility, :Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1). This is likely a bug in the X Server that will lead to a crash soon. Failed to open BO for returned DRI2 buffer (100x100, dri2 fake front buffer, named -1). This is likely a bug in the X Server that will lead to a crash soon. GL_ARB_arrays_of_arrays, GL_ARB_base_instance, GL_ARB_blend_func_extended, GL_ARB_buffer_storage, GL_ARB_clear_buffer_object, GL_ARB_clear_texture, GL_ARB_clip_control, GL_ARB_compressed_texture_pixel_storage, ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1664843/+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 1623404] Re: Xmir -rootless: Windows move a little during rapid resizing
** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1623404 Title: Xmir -rootless: Windows move a little during rapid resizing Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir -rootless: Windows move a little during rapid resizing This would be due to some confusion around whether the resizing is coming from Mir or from the X client. We have resizing logic to support both directions so obviously it's getting a bit of feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1623404/+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 1499245] Re: Xmir has its own modified copy of libdri2
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1499245 Title: Xmir has its own modified copy of libdri2 Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir has its own modified copy of libdri2. And I have no idea why... $ diff -qr ./hw/xfree86/dri2 hw/xmir/dri2 Files ./hw/xfree86/dri2/dri2.c and hw/xmir/dri2/dri2.c differ Files ./hw/xfree86/dri2/dri2ext.c and hw/xmir/dri2/dri2ext.c differ Files ./hw/xfree86/dri2/dri2.h and hw/xmir/dri2/dri2.h differ Files ./hw/xfree86/dri2/Makefile.am and hw/xmir/dri2/Makefile.am differ Only in ./hw/xfree86/dri2: pci_ids To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1499245/+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 1617944] Re: Xmir -rootless: rendering out-of-order frames under load in DRI2 mode
** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1617944 Title: Xmir -rootless: rendering out-of-order frames under load in DRI2 mode Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir DRI rendering out-of-order frames under load. Test case: 1. Under Valgrind, start Xmir with DRI rendering (default on desktop) 2. Start 'sol' and drag a card around. Expected: Card follows mouse Observed: Card glitches back and forth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1617944/+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 1498339] Re: Libreoffice can't start in flatten mode: Xmir -rootless -flatten
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1498339 Title: Libreoffice can't start in flatten mode: Xmir -rootless -flatten Status in Canonical Pocket Desktop: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: Libreoffice can't start in flatten mode: Xmir -rootless -flatten Workaround: libreoffice -nologo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1498339/+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 1498737] Re: Xmir -flatten: apps sometimes show the wrong mouse cursor
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1498737 Title: Xmir -flatten: apps sometimes show the wrong mouse cursor Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir apps sometimes show the wrong mouse cursor. As of today I think I've fixed most of the corrupt and missing cursor bugs. Now all that remains is that Xmir displays the wrong cursor in places. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1498737/+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 1481330] Re: Xmir disconnects and reconnects to Mir when the X client count reaches zero
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1481330 Title: Xmir disconnects and reconnects to Mir when the X client count reaches zero Status in Canonical Pocket Desktop: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir reconnects to Mir when the final client drops its connection to Xmir, either through XCloseDisplay, or by normal program termination. This affects xprop and GTK applications (they temporarily open a connection to the X server to obtain the value of the AT_SPI_BUS property on the root window). This is what is printed in application's upstart log: (EE) Fatal server error: (EE) Failed to connect to Mir: Failed to process connect response: /build/mir-3eDTxk/mir-0.14.0+15.10.20150723.1/src/client/probing_client_platform_factory.cpp(37): Throw in function virtual std::shared_ptr mir::client::ProbingClientPlatformFactory::create_client_platform(mir::client::ClientContext*) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: No appropriate client platform module found (EE) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1481330/+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 1420334] Re: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows)
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1420334 Title: [enhancement] Missing client API for relative surface movement (e.g. dragging client-decorated windows) Status in Mir: Fix Released Status in MirAL: In Progress Status in mir package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Mir needs a client API to allow surfaces to move themselves relatively. This is required to support full client-side decorations (bug 1398849), and also other apps like Google Chrome and Gnome Nautilus which can be dragged using part of their client areas. Later additions that are so similar I think they are part of the same bug: there need to be client APIs for "always on top" and "client initiate resize". To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1420334/+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 1494634] Re: Xmir using glamor on mako shows wrong colours
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494634 Title: Xmir using glamor on mako shows wrong colours Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir using glamor on mako shows wrong colours. Test case (after applying the fix for bug 1494240): $ xlogo -fg orange -bg purple shows blue on magenta. Workaround: $ Xmir -sw -damage renders colours correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1494634/+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 1494240] Re: Xmir crashes immediately on startup using glamor on Nexus4
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 Status in libepoxy package in Ubuntu: Triaged Status in libhybris package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: Xmir crashes immediately on startup using glamor on Nexus4. glamor GL version: OpenGL ES 3.0 V@53.0 AU@ (CL@) ... glamor GLSL version: OpenGL ES GLSL ES 3.00 (EE) (EE) Backtrace: (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) The stack trace is lost. However the problem appears to be the glGetStringi() function. This function is new in GLESv3 and libepoxy only uses it because the GLES version is 3.0 on mako. However, libhybris fails to implement glGetStringi() and forward it to the driver correctly. At least that seems to be the problem. Our hybris GLESv2 is missing the function but the Android GLESv2 on the device has it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1494240/+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 1211063] Re: [enhancement] Add support for color profiles
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1211063 Title: [enhancement] Add support for color profiles Status in Mir: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Won't Fix Bug description: Open system settings, select color. Select a color profile. With X, the change was live. With XMir, the profile is not applied. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-system-compositor 0.0.1+13.10.20130810.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Sun Aug 11 23:24:53 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-02-20 (537 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20120220) MarkForUpload: True SourcePackage: unity-system-compositor UpgradeStatus: Upgraded to saucy on 2013-08-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1211063/+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 1605074] Re: Xmir: supertux2 has two mouse pointers (one should be hidden)
** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1605074 Title: Xmir: supertux2 has two mouse pointers (one should be hidden) Status in Mir: Invalid Status in libsdl2 package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Won't Fix Bug description: 2 mouse pointers (one should be hidden) i've seen this in a lot (all?) the games on mir or Xmir see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1605074/+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 1536815] Re: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)]
** Changed in: xorg-server (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1536815 Title: Connecting Xmir to USC fails [std::exception::what: An output ID must be specified from src/server/shell/system_compositor_window_manager.cpp(66)] Status in Mir: New Status in mir package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: As seen here https://unity.ubuntu.com/mir/using_mir_on_pc.html I should be able to install ubuntu-desktop-mir and run unity7, but instead I receive the following error: failed to create a surface: Error processing request: An output ID must be specified Internal error details: /build/mir-1tnxlh/mir-0.18.1+16.04.20160115/src/server/shell/system_compositor_window_manager.cpp(66): Throw in function virtual mir::frontend::SurfaceId mir::shell::SystemCompositorWindowManager::add_surface(const std::shared_ptr&, const mir::scene::SurfaceCreationParameters&, const std::function(const std::shared_ptr&, const mir::scene::SurfaceCreationParameters&)>&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: An output ID must be specified To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536815/+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 1903694] Re: Sound comes out of the wrong place or not at all
A screen capture showing that I have indeed set sound to come out of internal speakers in gnome-control-center, but sound will only come out of the wireless headset. ** Attachment added: "Screenshot from 2020-11-10 12-26-39.png" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903694/+attachment/5433005/+files/Screenshot%20from%202020-11-10%2012-26-39.png -- 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/1903694 Title: Sound comes out of the wrong place or not at all Status in alsa-driver package in Ubuntu: New Bug description: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control- center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into pavucontrol and manually set the appropriate devices for input and output, but for others I am often forced to use the headset regardless of whether I want to or not. I have a number of colleagues that report similar issues when trying to use video conferencing software with Ubuntu. 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.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dmk1976 F pulseaudio /dev/snd/controlC1: dmk1976 F pulseaudio /dev/snd/controlC0: dmk1976 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 12:27:57 2020 InstallationDate: Installed on 2015-08-21 (1907 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7250, Realtek ALC3235, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-25 (137 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G9CNK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0G9CNK:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1903694/+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 1903527] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
This looks like a transient network failure. Relevant excerpt from DpkgTerminalLog.txt: error: cannot perform the following tasks: - Download snap "chromium" (1382) from channel "stable" (unexpected EOF) Please try reinstalling and let us know how it goes: sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1903527 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: When installing the package chromium-browser, it hangs for a while at progress 20%. Then I went out, system got locked and I got an error saying it can't be installed. Ubuntu 20.04 sudo apt install -y chromium-browser [sudo] password for johann: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: chromium-browser 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/48.3 kB of archives. After this operation, 164 kB of additional disk space will be used. Preconfiguring packages ... (Reading database ... 191014 files and directories currently installed.) Preparing to unpack .../chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 9 20:20:06 2020 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-08 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903527/+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 1903534] Re: package chromium-browser 86.0.4240.75-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess was killed by sig
Relevant output from DpkgTerminalLog.txt: => Installing the chromium snap ==> Checking connectivity with the snap store ===> Unable to contact the store This looks like a connectivity issue. Can you try reinstalling, and let us know how it goes? sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1903534 Title: package chromium-browser 86.0.4240.75-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess was killed by signal (Aborted), core dumped Status in chromium-browser package in Ubuntu: Incomplete Bug description: Slow response to key strokes. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 86.0.4240.75-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 DRM.card0-LVDS-1: enabled: disabled dpms: Off status: connected edid-base64: AP///wAGrz4xACEUAQSQHxF4AszOmVhQjiYkS1MBAQEBAQEBAQEBAQEBAQEBsCxAzmGEGDBAKjMANa4QAAAasCxAsGSEeDBAKjMANa4QAAAa/gBXSjEzOYBCMTQwUlczQSqeAREAAAIBCiAgAG8= modes: 1600x900 1600x900 DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-DP-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAQrBXwTDNUSiYVAQOANCB47h7Frk80sSYOUFSlSwCBgKlA0QBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAa/wBDNTkyTTE5REpUM0wK/ABERUxMIFUyNDEwCiAg/QA4TB5REQAKICAgICAgABs= modes: 1920x1200 1600x1200 1280x1024 1280x1024 1152x864 1024x768 1024x768 800x600 800x600 640x480 640x480 720x400 DRM.card1-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-LVDS-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card1-VGA-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Mon Nov 2 17:06:47 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess was killed by signal (Aborted), core dumped InstallationDate: Installed on 2016-07-06 (1586 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Load-Avg-1min: 1.15 Load-Processes-Running-Percent: 0.2% MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=39d1d272-4bac-416f-92af-7bee6a2cf30f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 86.0.4240.75-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to focal on 2020-11-02 (6 days ago) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.asset.tag: 485461 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: 485461 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2017-01-27T08:44:41.639760 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1903534/+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 1903693] [NEW] Fails to download scanner plugin via hp-plugin
Public bug reported: I'm trying to install the plugin to get my scanner of the multi function printer HP M182n working on 18.04, which I am currently still using on my machine and it fails to download the plugin. Looking at https://developers.hp.com/hp-linux-imaging-and-printing/plugins I see that it is likely that the file hplip-3.17.10-plugin.run has been removed from the server. There is a newer one, hplip-3.17.11-plugin.run but it's getting more and more messy trying to make this minor version number bump in the plugin work with the version in Ubuntu and the upstream software quality is terrible too. I started replacing version numbers and hashes in the bash makeself run files, but it fails again. This time with: Uncompressing HPLIP 3.17.10 Plugin Self Extracting Archive gzip: stdin: invalid compressed data--format violated .Extraction failed. Terminated error: Python gobject/dbus may be not installed >From my point of view, no average user should have to suffer through this. I >guess Ubuntu/Debian and HP don't talk to each other to support each other in >delivering a pain free user experience. Can you please look into this and >maybe release the .11 version of point me to a release to test for the users >who are still on a still good 18.04 LTS? Here is my initial attempt: $ hp-plugin HP Linux Imaging and Printing System (ver. 3.17.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.17.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. qt5ct: using qt5ct plugin Checking for network connection... Downloading plug-in from: None Receiving digital keys: /usr/bin/gpg --homedir /home/livewire/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 |Getötet ** Affects: hplip (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1903693 Title: Fails to download scanner plugin via hp-plugin Status in hplip package in Ubuntu: New Bug description: I'm trying to install the plugin to get my scanner of the multi function printer HP M182n working on 18.04, which I am currently still using on my machine and it fails to download the plugin. Looking at https://developers.hp.com/hp-linux-imaging-and-printing/plugins I see that it is likely that the file hplip-3.17.10-plugin.run has been removed from the server. There is a newer one, hplip-3.17.11-plugin.run but it's getting more and more messy trying to make this minor version number bump in the plugin work with the version in Ubuntu and the upstream software quality is terrible too. I started replacing version numbers and hashes in the bash makeself run files, but it fails again. This time with: Uncompressing HPLIP 3.17.10 Plugin Self Extracting Archive gzip: stdin: invalid compressed data--format violated .Extraction failed. Terminated error: Python gobject/dbus may be not installed From my point of view, no average user should have to suffer through this. I guess Ubuntu/Debian and HP don't talk to each other to support each other in delivering a pain free user experience. Can you please look into this and maybe release the .11 version of point me to a release to test for the users who are still on a still good 18.04 LTS? Here is my initial attempt: $ hp-plugin HP Linux Imaging and Printing System (ver. 3.17.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.17.10) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. qt5ct: using qt5ct plugin Checking for network connection... Downloading plug-in from: None Receiving digital keys: /usr/bin/gpg --homedir /home/livewire/.hplip/.gnupg --no-permission-warning --keyserver pgp.mit.edu --recv-keys 0x4ABA2F66DBD5A95894910E0673D770CDA59047B9 |Getötet To
[Desktop-packages] [Bug 1903694] [NEW] Sound comes out of the wrong place or not at all
Public bug reported: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control-center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into pavucontrol and manually set the appropriate devices for input and output, but for others I am often forced to use the headset regardless of whether I want to or not. I have a number of colleagues that report similar issues when trying to use video conferencing software with Ubuntu. 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.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dmk1976 F pulseaudio /dev/snd/controlC1: dmk1976 F pulseaudio /dev/snd/controlC0: dmk1976 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 12:27:57 2020 InstallationDate: Installed on 2015-08-21 (1907 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Latitude E7250, Realtek ALC3235, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to focal on 2020-06-25 (137 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0G9CNK dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd09/01/2015:svnDellInc.:pnLatitudeE7250:pvr:rvnDellInc.:rn0G9CNK:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7250 dmi.product.sku: 062D dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903694 Title: Sound comes out of the wrong place or not at all Status in alsa-driver package in Ubuntu: New Bug description: Since updating to Ubuntu 20.04, I have lots of problems with sound input and output coming from the wrong device or even a device that is not turned on. For example, right now in gnome-control-center sound settings it recognizes three sound output devices - internal speakers, HDMI output and a wireless headset. The wireless headset is off and the HDMI has no speakers, but I am using a HDMI->VGA adapter that gives it the impression that there may be speakers. In gnome-control- center, I have set the internal audio to be both the input and output devices for sound. When I click on the button to test audio output, no sound is produced, but if I have pavucontrol open at the same time, I can see that it is trying to send the sound output to the wireless speakers despite the settings in gnome-control-center. Similarly, if I try to do a video conference, such as skype, sound input and output are almost always wrong. Right now, if I try skype, it will only use the headset speaker and microphone, though it will make the phone ringing sound using the internal speaker. Again, this happens regardless of what I configure the sound settings to be in the skype settings panel. With many other video conferencing applications I have similar problems. With some, I manage to go into pavucontrol and manu
[Desktop-packages] [Bug 1903445] Re: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Not sure what happened, but you should try re-installing as suggested by dpkg: sudo apt reinstall firefox Please let us know how it goes. ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1903445 Title: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in firefox package in Ubuntu: Incomplete Bug description: Package fails to update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 82.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uuu1845 F pulseaudio /dev/snd/controlC1: uuu1845 F pulseaudio /dev/snd/pcmC1D0p: uuu1845 F...m pulseaudio /dev/snd/timer: uuu1845 f pulseaudio BuildID: 20201027185343 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Nov 8 19:33:33 2020 DpkgTerminalLog: dpkg: error processing package firefox (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ForcedLayersAccel: False InstallationDate: Installed on 2020-10-24 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1903445/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@vanvugt Thank you for your quick response! Does that mean I would have to wait for Pulseaudio to fix this in one of their future releases (maybe v.15) or will it be possible to use an alternative soundmanager, where the kernel fixes would be sufficient to use A2DP for bidirectional bluetooth sound? Homeoffice without cableless headset is just not that comfortable :s Best Regards Dennis -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~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 1897396] Re: Unable to make chromium-chromedriver work with selenium
I'm glad this is now working. Let's keep this bug open, if the problem happens again please comment on it, otherwise it will automatically expire in ~60 days. -- 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/1897396 Title: Unable to make chromium-chromedriver work with selenium Status in chromium-browser package in Ubuntu: Incomplete Bug description: Trying to use chrome web driver instead of firefox driver in selenium gives following error. How to use chromium with selenium now when it is packaged in Snap? Error message: selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-chromedriver 1:85.0.4183.83-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 26 19:10:59 2020 InstallationDate: Installed on 2019-11-03 (328 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-03-28 (181 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897396/+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 1881423] Re: error channel closing too late to send/recv
I've occasionally observed similar messages when testing firefox in virtual machines. This usually results in the firefox process taking longer than expected to return after quitting the application, but no other negative side effects. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv Status in firefox package in Ubuntu: Confirmed Bug description: I saw the following in my logs on a fresh install of 18.04.4: May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost May 30 12:57:05 cerberus org.gnome.Shell.desktop[2995]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 Date: Sat May 30 12:57:41 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/firefox/+bug/1881423/+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 1903705] [NEW] gnome-terminal messes up output when in a large directory and maximize the window
Public bug reported: when I "cd" to a directory with a large name, let's say 100 chars, and maximize and demaximize the window, new rows are inserted and also some output is missing. in every repetition the problem becomes worse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:00:47 2020 InstallationDate: Installed on 2020-05-03 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1903705 Title: gnome-terminal messes up output when in a large directory and maximize the window Status in gnome-terminal package in Ubuntu: New Bug description: when I "cd" to a directory with a large name, let's say 100 chars, and maximize and demaximize the window, new rows are inserted and also some output is missing. in every repetition the problem becomes worse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:00:47 2020 InstallationDate: Installed on 2020-05-03 (190 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1903705/+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 1881197] Re: No network usage info presented, always 0 bytes/s.
I have the same issue, in my case at least it's definitely the issue you found Sebastien. As pointed out at https://answers.launchpad.net/ubuntu/+source/gnome- system-monitor/+question/693912, Ubuntu is not a rolling release, but it would improve UX, and as noted at https://wiki.ubuntu.com/StableReleaseUpdates updates with simple changes that don't affect infrastructure may be candidates. Of course, it's not my decision to make, and if there's no interest I will instead report to the Linux Mint people, but I figure trying upstream first is better. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+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 1881197] Re: No network usage info presented, always 0 bytes/s.
NB: I'm using Linux Mint 20, which is based on Ubuntu 20.04 and uses the gnome-system-monitor package from Ubuntu 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+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 1903706] [NEW] Add flathub repository by default
Public bug reported: https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/debian/neon-settings-2.neon-flathub.service https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/neon_update/neon_flathub.rb ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1903706 Title: Add flathub repository by default Status in flatpak package in Ubuntu: New Bug description: https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/debian/neon-settings-2.neon-flathub.service https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/neon_update/neon_flathub.rb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1903706/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@dennis9771 Just get yourself Bluetooth audio card and save yourself a trouble, this will never be fixed. And you will not be able to use A2DP for conversation even if fixed. The goal of the fix is to add HFP 1.6 with mSBC 16kHz audio encoding so you have better quality during conversation. -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~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 1902244] Re: Backport packages for 20.04.1 HWE stack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.1 HWE stack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libclc (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1902244] Re: Backport packages for 20.04.1 HWE stack
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1902244 Title: Backport packages for 20.04.1 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-11 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Focal: Confirmed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-11 source package in Focal: Fix Committed Status in mesa source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: [Impact] These are needed for 20.04.1 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-11: a new package, no regression potential on it's own libclc: just a rebuild against the new llvm mesa: a new major release, but we'll pull the final stable release of 20.2.x series, so there shouldn't be any regressions left at that point xserver: a new point-release xorg drivers: modest updates, if any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1902244/+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 1903710] Re: ubuntu freezes when using remmina
The same problem happened 12 days ago. At that time I have also reported a bug using "ubuntu-bug remmina" command. That bug report is at bug 1902051. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1903710 Title: ubuntu freezes when using remmina Status in remmina package in Ubuntu: New Bug description: On Ubuntu 20.04 I have been using Remmina for whole day (actually several days without issue), but suddenly Remmina froze and I was in full screen mode. Mouse pointer was moving OK, but no click was accepted. Also musing playing in the background on Ubuntu was playing normally, so Ubuntu hasn't froze up, probably just Remmina. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:51:53 2020 InstallationDate: Installed on 2019-10-23 (384 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (87 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903710/+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 1903710] [NEW] ubuntu freezes when using remmina
Public bug reported: On Ubuntu 20.04 I have been using Remmina for whole day (actually several days without issue), but suddenly Remmina froze and I was in full screen mode. Mouse pointer was moving OK, but no click was accepted. Also musing playing in the background on Ubuntu was playing normally, so Ubuntu hasn't froze up, probably just Remmina. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:51:53 2020 InstallationDate: Installed on 2019-10-23 (384 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (87 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1903710 Title: ubuntu freezes when using remmina Status in remmina package in Ubuntu: New Bug description: On Ubuntu 20.04 I have been using Remmina for whole day (actually several days without issue), but suddenly Remmina froze and I was in full screen mode. Mouse pointer was moving OK, but no click was accepted. Also musing playing in the background on Ubuntu was playing normally, so Ubuntu hasn't froze up, probably just Remmina. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:51:53 2020 InstallationDate: Installed on 2019-10-23 (384 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (87 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903710/+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 1903668] Re: HDMI audio device disappears and is unavailble after several minutes of not being used
I only have libpipewire installed, not pipewire media server. -- 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/1903668 Title: HDMI audio device disappears and is unavailble after several minutes of not being used Status in pulseaudio package in Ubuntu: Incomplete Bug description: On system boot both of my audio devices are selectable and useable. After around 10 minutes the HDMI device just disappears and cannot be selected as output in either the task bar audio applet or in Kstart>system settings>audio(either devices or advanced tab). In the devices tab a device called Dummy output is displayed and in the advanced tab the HDMI device is shown, in this case GP107GL, with the profile in the dropdown box underneath it displaying off with no ability to switch it to on. If I go to pulse volume control>configuration i am able to select the HDMI device and the system will use it. If I play a 2 hour movie after this and then turn off the media player the HDMI device will once again disappear after about 10 minutes. When I ran ubuntu-bug the system identified the HDMI device and switched to it (it is set as default) and has remained accessable for 15 minutes now. I am running the NVIDIA 450 driver package. If I run Kubuntu 20.10 a similar problem occurs except the the profile of the device is somehow damaged but by selecting any speaker setup (profile), audio returns. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Nov 10 16:59:24 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-24 (200 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.E0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.E0:bd06/10/2020:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903668/+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 1903588] Re: gnome-calendar crashes when trying to remove and add a calendar
Thank you for your bug report, it sounds similar to https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/567 which should be fixed in the current serie, upstream mentioned that the code in 3.36 was different though so unsure how practical it would be to backport a fix to that serie ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/-/issues #567 https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/567 ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => High ** Changed in: gnome-calendar (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1903588 Title: gnome-calendar crashes when trying to remove and add a calendar Status in gnome-calendar package in Ubuntu: Fix Released Bug description: When trying to remove a calendar and add it back in "Manage your calendars", the process crashes. Running it in the debug mode gives the following message: 00:43:09.477633GcalCalendarManagementPage:DEBUG: Activating GcalCalendarsPage 00:43:09.477853GcalCalendarManagementPage:DEBUG: Deactivating GcalNewCalendarPage 00:43:15.789479 GcalCalendarMonitor:DEBUG: Tearing down view for calendar birthdays 00:43:16.279497 GcalCalendarMonitor:DEBUG: Starting ECalClientView for calendar 'Birthdays & Anniversaries' 00:43:16.281279 GcalCalendarMonitor:DEBUG: Finished initial loading of calendar 'Birthdays & Anniversaries' ** GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted Distro: Ubuntu 20.04.1 LTS Package version details: gnome-calendar: Installed: 3.36.2-0ubuntu1 Candidate: 3.36.2-0ubuntu1 Version table: *** 3.36.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages Uname: 5.4.0-52-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1903588/+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 1903710] Re: ubuntu freezes when using remmina
I forgot to write, the only way I could solved myself out of this problem was by hard-pressing laptop's power button, to poweroff laptop and then manually power it up again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1903710 Title: ubuntu freezes when using remmina Status in remmina package in Ubuntu: New Bug description: On Ubuntu 20.04 I have been using Remmina for whole day (actually several days without issue), but suddenly Remmina froze and I was in full screen mode. Mouse pointer was moving OK, but no click was accepted. Also musing playing in the background on Ubuntu was playing normally, so Ubuntu hasn't froze up, probably just Remmina. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 13:51:53 2020 InstallationDate: Installed on 2019-10-23 (384 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (87 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903710/+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 1903396] Re: libnl-route-3-200 unresolved symbols
Thank you for your bug report, could you provide the output of that command on a system having the issue? $ ldd -r /usr/lib/x86_64-linux-gnu/libnl-route-3.so what version of the library is installed? ** Changed in: libnl3 (Ubuntu) Importance: Undecided => Low ** Changed in: libnl3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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 1902535] Re: Calc freeze when I try to export ods to xlm 2003 format
Thanks for your answer. Not at all : LibreOffice is installed by a conventional manner, not like a snap. It is the package provided by an usual Ubuntu installation (probably 18.04 upgraded until 20.10) Strange ! But I can tell you that nowadays, if I look for LibreOffice app, I can find Writer, Calc, etc but I can't find anymore the LibreOffice app which allowed the user to choose what he wanted to do in a general window. And if I try "sudo apt install libreoffice", the terminal give me 21 extra packages : fonts and the next ones : libbsh-java libcommons-logging-java libpq5 libreoffice-nlpsolver libreoffice-report-builder libreoffice-report-builder-bin libreoffice-script-provider-bsh libreoffice-script-provider-js libreoffice-script-provider-python libreoffice-sdbc-mysql libreoffice-sdbc-postgresql libreoffice-wiki-publisher Paquets suggérés : libavalon-framework-java libcommons-logging-java-doc libexcalibur-logkit-java liblog4j1.2-java gpa libreoffice-grammarcheck libreoffice-librelogo myspell-dictionary openclipart2-libreoffice | openclipart-libreoffice pstoedit unixodbc gstreamer1.0-plugins-bad libofficebean-java default-mysql-server | virtual-mysql-server postgresql mediawiki -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1902535 Title: Calc freeze when I try to export ods to xlm 2003 format Status in libreoffice package in Ubuntu: New Bug description: I have a file saved in ODS format (only 12 sheets with about 60 lines and 20 rows, a planning for a staff) This file was an Excel 2013 file with macro that I opened and modified in LO Calc 7.0.2.2 If I save it in Excel2007-365 with macro format, it works If I export to Excel 2003 xlm format, Calc freezes and once, the system froze ! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 2 14:46:51 2020 InstallationDate: Installed on 2020-04-10 (206 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to groovy on 2020-10-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902535/+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 1839322] Re: Logitech G920 is unusable with Ubuntu 16.04
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: usb-modeswitch (Ubuntu) Importance: Undecided => Low ** Changed in: usb-modeswitch (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1839322 Title: Logitech G920 is unusable with Ubuntu 16.04 Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Version 2.2.5 supplied with Ubuntu 16.04 does not have support to Logitech G920 racing wheel, rendering it unusable. This device is in Xbox mode by default, needing a switch to HID mode to work. The symtoms are: - The device is in 0xFF (vendor) mode after usb cable is plugged in; - The device has an id product of 0xc261 (for Xbox); - The racing wheel keeps calibrating forever, turning left and right by itself with no calibration completion (the device is resetted every time, wich impares the ending of calibration process). The solution for this bug is to update the usb-modeswitch package to the version supplied with Ubuntu 18.04, wich solves the problem. More info on this issue can be found below: http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=2&t=2510 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1839322/+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 1132472] Re: Update-manager list earlier changes for certain packages before the relevant change for the update in question
This appears to be a bug in update-manager, where it fails to match the currently installed version against the changelog, and consequently doesn't truncate the changelog where it should, displaying the entire changelog history. I am not familiar with update-manager's code, but the code in question appears to be in the _get_changelog_or_news() function, in UpdateManager/Core/MyCache.py (https://bazaar.launchpad.net/~ubuntu- core-dev/update- manager/main/view/head:/UpdateManager/Core/MyCache.py#L210, in the 'while True' loop towards the end of the function). ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid ** Changed in: boost-defaults (Ubuntu) Status: New => Invalid -- 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/1132472 Title: Update-manager list earlier changes for certain packages before the relevant change for the update in question Status in boost-defaults package in Ubuntu: Invalid Status in chromium-browser package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have an old version of some boost package when a newer version is available. 2. Open update-manager, select the boost package and look at the "Changes" tab. Expected result: The tab should contain which version I have currently installed, which version is available, and a section from the changelog summarizing the changes between those two versions. Actual result: While the boost packages have this, it is far down below a series of older changelog entries. All of these are for versions older than the one currently installed and as such are already included in the version I have. Furthermore they push down the "currently installed/available version" part which should always be listed at the top. I am not sure why this happens, and why it only happens with boost packages. I have seen this before with a previous boost update (unfortunately I failed to file a bug before updating), but not in any other packages. $ apt-cache policy libboost-date-time1.49.0 libboost-date-time1.49.0: Installed: 1.49.0-3.1ubuntu1.1 Candidate: 1.49.0-3.1ubuntu1.2 Version table: 1.49.0-3.1ubuntu1.2 0 500 http://no.archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ quantal-security/main i386 Packages *** 1.49.0-3.1ubuntu1.1 0 100 /var/lib/dpkg/status 1.49.0-3.1ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages With the package above installed, this issue should be easy to reproduce. I have also attached the content of the "Changes" tab in update-manager. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.4 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sun Feb 24 15:04:06 2013 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1361714262' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'744' b'com.ubuntu.update-manager' b'window-width' b'959' InstallationDate: Installed on 2012-10-20 (127 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1132472/+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 1132472] Re: Update-manager list earlier changes for certain packages before the relevant change for the update in question
And I can reliably observe the issue in a focal VM where I installed the chromium-browser package from bionic. Update-manager offers the update to the newer version in focal, and the changelog textbox displays the entire changelog since the first version of the package. This might be caused by the versioning scheme used to update chromium in stable releases. But it's really a bug in update-manager. ** Changed in: update-manager (Ubuntu) Status: New => Confirmed ** Changed in: update-manager (Ubuntu) Importance: Undecided => Medium -- 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/1132472 Title: Update-manager list earlier changes for certain packages before the relevant change for the update in question Status in boost-defaults package in Ubuntu: Invalid Status in chromium-browser package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have an old version of some boost package when a newer version is available. 2. Open update-manager, select the boost package and look at the "Changes" tab. Expected result: The tab should contain which version I have currently installed, which version is available, and a section from the changelog summarizing the changes between those two versions. Actual result: While the boost packages have this, it is far down below a series of older changelog entries. All of these are for versions older than the one currently installed and as such are already included in the version I have. Furthermore they push down the "currently installed/available version" part which should always be listed at the top. I am not sure why this happens, and why it only happens with boost packages. I have seen this before with a previous boost update (unfortunately I failed to file a bug before updating), but not in any other packages. $ apt-cache policy libboost-date-time1.49.0 libboost-date-time1.49.0: Installed: 1.49.0-3.1ubuntu1.1 Candidate: 1.49.0-3.1ubuntu1.2 Version table: 1.49.0-3.1ubuntu1.2 0 500 http://no.archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ quantal-security/main i386 Packages *** 1.49.0-3.1ubuntu1.1 0 100 /var/lib/dpkg/status 1.49.0-3.1ubuntu1 0 500 http://no.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages With the package above installed, this issue should be easy to reproduce. I have also attached the content of the "Changes" tab in update-manager. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.4 ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 Date: Sun Feb 24 15:04:06 2013 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1361714262' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'744' b'com.ubuntu.update-manager' b'window-width' b'959' InstallationDate: Installed on 2012-10-20 (127 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1132472/+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 1881197] Re: No network usage info presented, always 0 bytes/s.
This issue is a known one in GNOME System monitor, and is fixed with 3.36.1 release of GNOME System Monitor. Hence Ubuntu and Mint should push the the 3.36.1 release to their repositories to fix this issue. ** Also affects: libgtop via https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/142 Importance: Unknown Status: Unknown ** Project changed: libgtop => gnome-system-monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. Status in Gnome System Monitor: Unknown Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 20.04 LTS Release: 20.04 2) gnome-system-monitor: Instalado: 3.36.0-1 Candidato: 3.36.0-1 Tabela de versão: *** 3.36.0-1 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1 500 500 http://cz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3) There should be a graph drawn with the info about my network usage, as well as number on the download/upload speeds. 4) Pretty much nothing happens. It calculates how much data I've downloaded/uploaded since the OS was booted, but that's it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 17:51:55 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2019-12-06 (173 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-04-25 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+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 1377197] Re: Typographies in resources axis doesn't follow scale for menus and title bars
** Bug watch added: gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #46 https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/46 ** Also affects: libgtop via https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues/46 Importance: Unknown Status: Unknown ** Changed in: gnome-system-monitor Importance: Medium => Unknown ** Changed in: gnome-system-monitor Status: Expired => Unknown ** Changed in: gnome-system-monitor Remote watch: GNOME Bug Tracker #737847 => gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues #46 ** No longer affects: libgtop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1377197 Title: Typographies in resources axis doesn't follow scale for menus and title bars Status in Gnome System Monitor: Unknown Status in One Hundred Papercuts: Triaged Status in gnome-system-monitor package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: 1. Open the "System Monitor" application. 2. Go to the "Resources" tab. 3. Open the "System Settings" application. 4. Go to the "Screen Display" section. 5. Change the value for the "scale for menu and tittle bars". EXPECTED BEHAVIOUR: - Axis to change its typography size. REAL BEHAVIOUR: - Axis typography size stays the same, making it difficult to read in high resolution screens; as seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-system-monitor 3.8.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 3 16:59:03 2014 InstallationDate: Installed on 2013-05-21 (500 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to utopic on 2014-09-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1377197/+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 295990] Re: Keyboard layout reset after attaching USB keyboard
I have started to experience this bug after upgrading from Ubuntu 18.04 to 20.04. Whenever I remove my external keyboard and plug it back in, the external keyboard's layout switches to US English instead of whatever it was set to. The laptop's built-in keyboard layout remains correct. I did not notice any warnings in my logs. If you need more information / debug output, I'd be glad to help. Some details: * Laptop: Lenovo T480 * OS: Ubuntu 20.04 * External keyboard: Das Keyboard 4 Professional (model no.: DASK4MKPROSIL-3G7-r1.2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.
"For Firefox, this is a duplicate of bug 1312376. The fix/workaround is to use environment MOZ_USE_XINPUT2=1 or MOZ_ENABLE_WAYLAND=1 in your /etc/environment." Currently I'm using Firefox 82.0.2, the workaround doesn't make any differnce. I tried putting MOZ_USE_XINPUT2=1 and/or MOZ_ENEABLE WAYLAND=1 in my /etc/enviroment. But it doesn't make any differnce. I am using Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in libreoffice package in Ubuntu: New Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. 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: zfs zunicode zavl icp zcommon znvpair 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: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 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 20.2.1-1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1903632/+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 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
Daniel, of course. My point was that I've now seen multiple occurrences where this suspend on login bug, as it continues to occur on a given system, causes Ubuntu to become less and less stable over time. Unfortunately that impact has become predictable at least on the machines here. So to me, this particular bug is of increasing concern and urgency. I'm new to Ubuntu and appreciate your pointers. If I can see consistency and gather enough information to report a new bug, I will. So far, what I see is that this suspend on login bug can follow various events on a docked laptop: loading the Dropbox app, loading the Logitech module for a USB wireless mouse, loading third party nVidia drivers... and then with continued occurrences it goes deeper into the gnome shell. The affected systems have submitted automated crash reports already. But at this point my concern is this suspend on login bug. I certainly didn't intend to shift attention from the bug at hand! Quite the opposite. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 20.04's software updater just applied quite a few updates affecting grub and nvidia. The modules should show in the report just submitted. Also, updates to initramfs had just installed a few days ago. Kudos in that these updates fixed two login/startup issues: I'd been affected by the compression change for initramfs and had started getting the spinning ubuntu circle on the logon splash screen, apparently due to an nvidia driver conflict. I'd turned the splash screen to nosplash, and have now been able to set it back to splash. Both of those issues now appear to be fixed. BUT now when I start Ubuntu with the T570 laptop docked, lid closed, external display and keyboard via the dock: as soon as I enter the login password and press enter, the system goes into suspend. If I then press the dock power button again, the system will resume and proceed normally. It seems that the new startup modules don't realize that the machine is docked; and/or that it erroneously now "detects" the closed lid as a change in lid state during startup, triggering suspend. Prior to today's updates, this was not an issue. I would appreciate seeing this corrected. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 18:15:31 2020 InstallationDate: Installed on 2020-06-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+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 295990] Re: Keyboard layout reset after attaching USB keyboard
Update: The problem does not occur when I use Wayland instead of X. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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 1903396] Re: libnl-route-3-200 unresolved symbols
linux-vdso.so.1 (0x7ffcf0521000) libnl-3.so.200 => /lib/x86_64-linux-gnu/libnl-3.so.200 (0x7f5a697da000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f5a697b7000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f5a695c5000) /lib64/ld-linux-x86-64.so.2 (0x7f5a698a) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1903396 Title: libnl-route-3-200 unresolved symbols Status in libnl3 package in Ubuntu: Incomplete Bug description: $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS" $ arch x86_64 Getting a link error when trying to build Wireshark from source on Ubuntu Focal. I need to build Wireshark for plugin development. Steps to reproduce: 1. Obtain source code from https://gitlab.com/wireshark/wireshark 2. Install build dependencies as per CI ./tools/debian-setup.sh --install-optional --install-test-deps -y 3. mkdir build 4. cmake .. 5. make 6. Observer error: [ 88%] Linking CXX executable run/wireshark /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nla_get_s32' /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference to `nl_strerror_l' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1 make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2 make: *** [Makefile:141: all] Error 2 Those two symbols are not present in any of the other libnl libraries, static or dynamic. /usr/include/libnl3/netlink/attr.h:119:extern int32_t nla_get_s32(const struct nlattr *); $ dpkg -S /usr/include/libnl3/netlink/attr.h libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0 I can build and install libnl-3.2.25 from source and I don't get the linking issues anymore if I replace the .so files installed by the .debs, so it's possible that there is soemthing wrong with the packaging of libnl-route-3-200.deb. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 141081] Re: Firefox opens 2 extra tabs on middle button click
Boris, have you tried what Alexander was suggesting in earlier comments? I.e. start firefox in safe mode, to find out whether the problem might be caused by an extension. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/141081 Title: Firefox opens 2 extra tabs on middle button click Status in firefox package in Ubuntu: Invalid Bug description: Binary package hint: firefox Whenever i click the middle mouse button (scroll wheel) on a weblink to open a new tab firefox opens 2 additional tabs of the same thing. ProblemType: Bug Architecture: i386 Date: Wed Sep 19 16:48:46 2007 DistroRelease: Ubuntu 7.04 Package: firefox 2.0.0.6+1-0ubuntu1 PackageArchitecture: i386 SourcePackage: firefox Uname: Linux jack-desktop 2.6.22.6-custom #1 Fri Sep 7 21:19:59 EDT 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/141081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900167] Re: gnome-software Unable to install updates
I am having the same Problem on my newly installed Ubuntu SAystem. Is there a workaraound or fix for this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1900167 Title: gnome-software Unable to install updates Status in gnome-software package in Ubuntu: Incomplete Bug description: Click on 'Updates' and then on 'Restart & Update' I have a message: Unable to install updates: GDBus.error... Prepared update not found:/var/lib/PackageKit/prepared-update corrado@corrado-x2-gg-1009:~$ apt policy gnome-software gnome-software: Installed: 3.38.0-2build1 Candidate: 3.38.0-2build1 Version table: *** 3.38.0-2build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-x2-gg-1009:~$ inxi -Fx System: Host: corrado-x2-gg-1009 Kernel: 5.8.0-23-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 Sound Server: ALSA v: k5.8.0-23-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives: Local Storage: total: 2.05 TiB used: 9.42 GiB (0.4%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB Partition: ID-1: / size: 31.25 GiB used: 9.41 GiB (30.1%) fs: ext4 dev: /dev/nvme0n1p2 Swap: ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 43.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 224 Uptime: 3h 13m Memory: 7.48 GiB used: 1.66 GiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1874 Shell: Bash v: 5.0.17 inxi: 3.1.07 corrado@corrado-x2-gg-1009:~$ ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:20:00 2020 InstallationDate: Installed on 2020-10-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1900167/+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 1377197] Re: Typographies in resources axis doesn't follow scale for menus and title bars
The issue is fixed upstream now ** Changed in: gnome-system-monitor (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1377197 Title: Typographies in resources axis doesn't follow scale for menus and title bars Status in Gnome System Monitor: Unknown Status in One Hundred Papercuts: Triaged Status in gnome-system-monitor package in Ubuntu: Fix Committed Bug description: HOW TO REPRODUCE: 1. Open the "System Monitor" application. 2. Go to the "Resources" tab. 3. Open the "System Settings" application. 4. Go to the "Screen Display" section. 5. Change the value for the "scale for menu and tittle bars". EXPECTED BEHAVIOUR: - Axis to change its typography size. REAL BEHAVIOUR: - Axis typography size stays the same, making it difficult to read in high resolution screens; as seen in the attached screen-shot. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-system-monitor 3.8.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 3 16:59:03 2014 InstallationDate: Installed on 2013-05-21 (500 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to utopic on 2014-09-24 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1377197/+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 295990] Re: Keyboard layout reset after attaching USB keyboard
@scheleaap: Please don't talk on a 12 years old and closed bug report. You are probably experiencing bug #1899206. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+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 1902898] Re: power-button action inconsistent between user session and greeter
is it important enough to justify doing the SRU work? ** Changed in: ubuntu-settings (Ubuntu Groovy) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: ubuntu-settings (Ubuntu Focal) Importance: Undecided => Low ** Changed in: ubuntu-settings (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: ubuntu-settings (Ubuntu Hirsute) Importance: Undecided => Low ** Tags removed: rls-hh-incoming ** Changed in: ubuntu-settings (Ubuntu Focal) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Groovy) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Hirsute) Assignee: (unassigned) => Didier Roche (didrocks) ** Changed in: ubuntu-settings (Ubuntu Groovy) Status: Confirmed => Incomplete ** Changed in: ubuntu-settings (Ubuntu Focal) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Focal: Incomplete Status in ubuntu-settings source package in Groovy: Incomplete Status in ubuntu-settings source package in Hirsute: Confirmed Bug description: When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1890365] Re: [snap] Web Serial fails to access local device
The denial on /proc/tty/drivers looks relevant.
Can you try the following?
- close chromium
- edit (with sudo)
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium, add the
following line to the profile:
@{PROC}/tty/drivers r,
- reload the apparmor profile with: "sudo apparmor_parser -r
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium"
- run "journalctl -f | grep chromium" in a terminal, start chromium,
and try to access your device
- share the updated journalctl output
Thanks!
--
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/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
New
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1901829] Re: thunderbird fails to open, xml parse error
** Changed in: thunderbird (Ubuntu Groovy) Importance: Undecided => High -- 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 Status in thunderbird source package in Groovy: New 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 1901829] Re: thunderbird fails to open, xml parse error
** Changed in: thunderbird (Ubuntu Groovy) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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 Status in thunderbird source package in Groovy: New 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 1888942]
Hello, The automatic copy into the primary selection has been preventing pasting url with a middle-click in the address bar for many years and it is wonderful that is has been fixed. For me, the current behaviour is the correct one and I would be sad if the change is reverted. Nevertheless, I believe CTRL-A should copy the url to the primary selection in order to be consistent with its behaviour on web pages and with the behaviour of the shift-arrow selection. If some users are confused by text highlighted as selected but not copied into the primary selection, then using a different look in such a case, like text in grey, would avoid any confusion. Cheers, Philippe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Incomplete Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+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 1902900] Re: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it
I tentatively added a gnome-shell task. ** 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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1902900 Title: Workspaces menu flashes when moving between workspace A and workspace B having B Firefox with a video in full screen on it Status in firefox package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: As I said in the title the menu with the 3 workspaces flashes if you switch from a normal workspace to a workspace that has a fullscreen video in Firefox. How to reproduce * Open Firefox * Open a video in full screen (I tested prime video and twitch) * Press and keep pressed ctrl-alt and arrow to move between workspaces * When you reach the video workspaces still keep pressed ctrl-alt ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 82.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sibilant 2096 F pulseaudio BuildID: 20201014125134 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 16:28:48 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:361 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-03 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.92 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:361 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=82.0/20201014125134 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 232.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr232.0.0.0.0:bd04/12/2020:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1902900/+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 1903723] [NEW] Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek AL
Public bug reported: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Nov 10 14:37:41 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.28' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:37:43 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.41' (uid=1000 pid=1083 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Nov 10 14:57:06 AMI-Buntu dbus-daemon[882]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.341' (uid=1000 pid=9531 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23d dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-11-10T14:56:54.599621 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1903723 Title: Audio dropouts and general surround sound issues. Device shown as ALC887-VD Analog instead of ALC1220 as per motherboard specifications [AB350-Gaming, Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: Audio dropouts and general surround sound issues. Incorrect ALC device shown from cat /proc/asound/card1/pcm0c/info card: 1 device: 0 subdevice: 0 stream: CAPTURE id: ALC887-VD Analog name: ALC887-VD Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 1 Device should be shown as ALC1220 as per Motherboard (Gigabyte AB350 Gaming 3) Specifications. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-52.57-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: billy 9531 F pulseaudio /dev/snd/controlC2: billy 9531 F pulseaudio /dev/snd/controlC1: billy 9531 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 15:05:30 2020 InstallationDate: Installed on 2020-11-10 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom:
[Desktop-packages] [Bug 1901318] Re: needs to depend on tcl (not just tcl8.6)
This bug was fixed in the package usb-modeswitch - 2.6.1-1ubuntu3 --- usb-modeswitch (2.6.1-1ubuntu3) hirsute; urgency=medium * debian/control: - Depends on tcl rather than tcl8.6 since the unversioned tclsh is the one being called (lp: #1901318) -- Sebastien Bacher Wed, 28 Oct 2020 17:10:31 +0100 ** Changed in: usb-modeswitch (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1901318 Title: needs to depend on tcl (not just tcl8.6) Status in usb-modeswitch package in Ubuntu: Fix Released Status in usb-modeswitch source package in Groovy: Fix Released Bug description: * Impact the usb-modeswitch dispatcher script fails to start on the default installation because it uses tclsh unversioned while we depends on tcl8.6 * Test Case $ /usr/sbin/usb_modeswitch_dispatcher shouldn't bail out on an interpreter error (or better, test that plugging an usb modem is correctly handled) * Regression potential The script was bailing out due to a missing intepreter before so the code wasn't tested, it's possible that it triggers errors or could interact with the system in some way. The dispatcher reacts to udev events when an usb modem is connected, so try to use one of those and make sure that there is no negative effect (and if possible that the modem gets correctly handled) -- the package currently depends on tcl8.6, but /usr/sbin/usb_modeswitch_dispatcher actually requires /usr/bin/tclsh which isn't provided by tcl8.6, so it likely would need to depend on something like tcl (= 8.6) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1901318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter
On Tue, Nov 10, 2020 at 7:45 AM Sebastien Bacher <1902...@bugs.launchpad.net> wrote: > > is it important enough to justify doing the SRU work? >From my myopic (server-oriented) point-of-view, changing the default in 20.04 to prompt is a good idea. I've found that users often install Ubuntu Desktop on their server-class hardware, using their BMC virtual KVM as a head. These systems tend to support suspend, but suspend rarely works well. Some systems will go to sleep just fine - but have no way to wake them up[*]. Others will try to suspend, only to immediately come back out of suspend (presumably after trying to sleep a device that doesn't support it), so it looks like the system failed to react at all. Both seem like a non-intuitive reaction to an "IPMI power off soft" command. [*] https://bugs.launchpad.net/bugs/1862559 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Focal: Incomplete Status in ubuntu-settings source package in Groovy: Incomplete Status in ubuntu-settings source package in Hirsute: Confirmed Bug description: When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+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 1902535] Re: Calc freeze when I try to export ods to xlm 2003 format
Right so if you are going the deb route, then you should apt install it including the fonts and bits that are needed to ensure libreoffice runs and displays correctly. With the libreoffice deb installed, there will not be a desktop icon for the start center (the all in one libreoffice icon) but you can get there by opening up any libreoffice application and then clicking the X in the right top corner (not the red one that closes the whole app, click the smaller X just below the X to close the window). That will take you to the place where you can launch any libreoffice application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1902535 Title: Calc freeze when I try to export ods to xlm 2003 format Status in libreoffice package in Ubuntu: New Bug description: I have a file saved in ODS format (only 12 sheets with about 60 lines and 20 rows, a planning for a staff) This file was an Excel 2013 file with macro that I opened and modified in LO Calc 7.0.2.2 If I save it in Excel2007-365 with macro format, it works If I export to Excel 2003 xlm format, Calc freezes and once, the system froze ! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Nov 2 14:46:51 2020 InstallationDate: Installed on 2020-04-10 (206 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: libreoffice UpgradeStatus: Upgraded to groovy on 2020-10-24 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902535/+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
Thanks for testing, marking as verified. The autopkgtest regression on arm sounds like flaky tests rather than an issue with the update, they have been retried now ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- 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 source package in Groovy: Fix Committed Status in sane-backends package in Debian: Unknown Bug description: * Impact The plustek driver isn't working in 20.10 * Test case Try doing a copy of a document on a plustek based device * Regression potential The locking option was disabled until 20.10, the locking code relies on a lock directory to exist in /var/lock but that location is not persitant which means the locking can't work. Debian has turned the option off again, we are going the same in the SRU because it's safer than trying to fix an option that never got properly tested. There is special verification to do, just check that plustek and other devices are working correctly. - 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 1853331] Re: nm-applet assertion failure manipulating widgets
This bug was fixed in the package network-manager-applet - 1.8.24-1ubuntu3 --- network-manager-applet (1.8.24-1ubuntu3) focal; urgency=medium * d/p/Support-hiding-rather-than-desensitizing-disallowed-items.patch! - restore the initialization code for the 'allowed' variables which was dropped by error in 16.10, fixes log warnings (lp: #1853331) -- Sebastien Bacher Wed, 29 Jul 2020 23:09:31 +0200 ** Changed in: network-manager-applet (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulating widgets Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Focal: Fix Released Bug description: * Impact the applet keeps logging gtk warnings * Test case Under xubuntu connect to a wifi, the journal shouldn't get nm-applet warnings * Regression potential The change is in the VPN submenu code, check that the items there are still correctly updated and available when needed --- nm-applet is logging a continuous stream of: Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent System updated on 19 Nov 2019 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Nov 20 15:48:21 2019 InstallationDate: Installed on 2018-11-06 (379 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100 192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug
[Desktop-packages] [Bug 1853331] Update Released
The verification of the Stable Release Update for network-manager-applet has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1853331 Title: nm-applet assertion failure manipulating widgets Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Focal: Fix Released Bug description: * Impact the applet keeps logging gtk warnings * Test case Under xubuntu connect to a wifi, the journal shouldn't get nm-applet warnings * Regression potential The change is in the VPN submenu code, check that the items there are still correctly updated and available when needed --- nm-applet is logging a continuous stream of: Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:42:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:44:54 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:45:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:40 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Nov 20 15:46:55 X1 nm-applet[3092]: Can't set a parent on widget which has a parent System updated on 19 Nov 2019 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Nov 20 15:48:21 2019 InstallationDate: Installed on 2018-11-06 (379 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp4s0 proto dhcp metric 600 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.24 metric 100 192.168.178.0/24 dev wlp4s0 proto kernel scope link src 192.168.178.29 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.14 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1853331/+subscriptions -- Mailing list: https
[Desktop-packages] [Bug 1871471] Re: flash end of life soon, suggest remove from hirsute
Gunnar Hjalmarsson (gunnarhj) we no longer ship any web-browsers that can actually use this plugin. It is innert. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1871471 Title: flash end of life soon, suggest remove from hirsute Status in adobe-flashplugin package in Ubuntu: New Status in flashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree package in Ubuntu: New Bug description: Hello, Adobe has said they will not be supporting Flash beyond 2020: https://helpx.adobe.com/acrobat/kb/flash-format-support-in-pdf.html https://theblog.adobe.com/adobe-flash-update/ I think we shouldn't ship Flash in hirsute. Does our agreement with Adobe for distributing Flash installers or code allow us to skip shipping Flash in hirsute? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1871471/+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 1900777] Re: [amdgpu] Screen freeze
Switched to ubuntu (i.e. not ubuntu on wayland) after crash. There were back to back crashes. After posting this, I will try to replicate it. ** Attachment added: "prevboot1.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+attachment/5433053/+files/prevboot1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+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 1900777] Re: [amdgpu] Screen freeze
To reiterate, the prevboot1.txt. and prevboot2.txt posted today, 11/10/20, are from ubuntu. And prevboot.txt, posted 11/10/20, is from ubuntu on wayland. ** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+attachment/5433054/+files/prevboot2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+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 1900777] Re: [amdgpu] Screen freeze
Crash from ubuntu on wayland ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+attachment/5433052/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+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 1900777] Re: [amdgpu] Screen freeze
Can't seem to replicate the crashes from comment #24-#26. Will update if this changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+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 1903755] [NEW] thunderbird 78.4.1 snap connection missing
Public bug reported: --- Description:Ubuntu 20.04.1 LTS Release:20.04 --- thunderbird 74.8.1 - channel lastest/stable --- I try to connect to an exist profile in a ntfs partition. But the "Read/write files on removable storage device option" is missing in permissions. -- I can't launch thunderbird with a profile located in a mnt (ntfs partition) device. Thunderbird does not have auto-connect of removable-media, and i can't connect it manually with: snap connect thunderbird:removable-media ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Missing last option - Read/write files on removable storage devices" https://bugs.launchpad.net/bugs/1903755/+attachment/5433055/+files/Screenshot%20from%202020-11-10%2009-37-48.png -- 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/1903755 Title: thunderbird 78.4.1 snap connection missing Status in thunderbird package in Ubuntu: New Bug description: --- Description: Ubuntu 20.04.1 LTS Release: 20.04 --- thunderbird 74.8.1 - channel lastest/stable --- I try to connect to an exist profile in a ntfs partition. But the "Read/write files on removable storage device option" is missing in permissions. -- I can't launch thunderbird with a profile located in a mnt (ntfs partition) device. Thunderbird does not have auto-connect of removable-media, and i can't connect it manually with: snap connect thunderbird:removable-media To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1903755/+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 1902148] Re: [snap] launchers in app's dock menu do launch general LO
Ok well I've been going down a rabbit hole here, trying to fix /meta/gui/libreoffice.desktop. There is a strange problem here.. I don't know what is creating libreoffice.desktop instead of using the startcenter.desktop file that should fix the issue. However.. In my testing and comparison to the debs, I came across https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1696250 which removed the startcenter and math icons all together. This was done as a cosmetic change really. However since we'd like to see the snap behave *just like* the deb, I will just remove these icons as well from the snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1902148 Title: [snap] launchers in app's dock menu do launch general LO Status in libreoffice package in Ubuntu: In Progress Bug description: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+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 1901829] Re: thunderbird fails to open, xml parse error
I too have this problem. It seems that if you go into your .thunderbird directory and delete the file addonStartup.json.lz4, thunderbird is able to start. Restarting tb usually causes the error to appearagain, but re- deleting this file allows it to start again. -- 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 Status in thunderbird source package in Groovy: New 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 1903759] [NEW] [SRU] Update mutter to 3.36.7 in Focal
Public bug reported: [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:14:13 2020 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1903759 Title: [SRU] Update mutter to 3.36.7 in Focal Status in mutter package in Ubuntu: New Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:14:13 2020 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903759/+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 1901829] Re: thunderbird fails to open, xml parse error
I should also say that the only language pack I have is $ find . -name "*lang*" ./extensions/langpack-en...@thunderbird.mozilla.org.xpi and it is from the same time as I upgraded to Kubuntu 20.10 -- 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 Status in thunderbird source package in Groovy: New 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
Re: [Desktop-packages] [Bug 1901829] Re: thunderbird fails to open, xml parse error
It all points to add-ons updates (language pack mostly) that somehow are not fully compatible with thunderbird 78.3. Those json startups may be somehow putting the references to undefined entities in the xmls > I too have this problem. It seems that if you go into your .thunderbird > directory and delete the file addonStartup.json.lz4, thunderbird is able > to start. Restarting tb usually causes the error to appearagain, but re- > deleting this file allows it to start again. > -- 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 Status in thunderbird source package in Groovy: New 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 1900777] Re: [amdgpu] Screen freeze
Another ubuntu crash. This attached file is not ubuntu on wayland. (This is the third crash of the morning, so I am switching back to ubuntu on wayland) ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+attachment/5433065/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. 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 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+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 1903756] [NEW] show application showing overview instead of showing application
You have been subscribed to a public bug: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug focal -- show application showing overview instead of showing application https://bugs.launchpad.net/bugs/1903756 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 1903756] Re: show application showing overview instead of showing application
Your report is rather confusing: it seem to be several sentences, all run together, without any punctuation. And I fail to understand what it has to with nano. The Gnome shell and dash have nothing to do with nano. Please clarify what your problem is. What do you expect to happen when you click on a running app? Which running app are you clicking on? And so on. -- 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/1903756 Title: show application showing overview instead of showing application Status in gnome-shell package in Ubuntu: Incomplete Bug description: unable to click on running apps and have to lockout to restart the gnome-shell,ctrl + alt f2 to restart the gnome-shell doesn't effects dash show application showing overview instead of showing application ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nano 4.8-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 00:43:36 2020 SourcePackage: nano 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/1903756/+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
