[Desktop-packages] [Bug 1877710] Re: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted
** Tags removed: need-duplicate-check -- 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/1877710 Title: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js .dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: error happened after terminal update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 9 09:39:36 2020 DuplicateSignature: package:libreoffice-help-common:1:6.4.2-0ubuntu3 Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-bVHLGf/20-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-23 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877710/+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 1877710] [NEW] package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitt
Public bug reported: error happened after terminal update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 9 09:39:36 2020 DuplicateSignature: package:libreoffice-help-common:1:6.4.2-0ubuntu3 Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-bVHLGf/20-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-23 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877710 Title: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js .dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: error happened after terminal update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 9 09:39:36 2020 DuplicateSignature: package:libreoffice-help-common:1:6.4.2-0ubuntu3 Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-bVHLGf/20-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-23 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/prism.js.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877710/+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 1876415] Re: [nvidia+modeset] Fonts in the GNOME shell not shown.
I am having this bug again right now. You advised me in my other bug report to post a file with the contents of journalctl -b0 if this bug reappears, since I was told both are related, I was wondering if the same applies for this one here. Link to other bug report: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1875957 One thing to note: I would prefer to send the file via Mail, if possible. -- 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/1876415 Title: [nvidia+modeset] Fonts in the GNOME shell not shown. Status in gnome-shell package in Ubuntu: Incomplete Bug description: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram icon not displaying the number of unread messages, searches in the search bar. The text however is drawn in applications that are not an integral part of the shell itself, such as the settings application, terminals, Firefox, Rhythmbox, GNOME System montior. The bug appeared seemingly out of nowhere, can be worked around though pretty easily by chainging the fonts of the user interface in the GNOME tweak tool. The problem reappears, if the user interface fonts are changed back to the fonts which were not appearing on the screen originally. Changing the font size does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 04:28:41 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-26-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-28-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (176 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (7 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 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
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100%.
Not sure why there has been no activity...it certainly shouldn't be 'expired', in my view. ** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: New Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+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 1874808] Re: Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1
** Changed in: firefox Importance: Medium => Unknown -- 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/1874808 Title: Unmuting Twitch video pauses playback, when media.autoplay.enabled .user-gestures-needed=false, media.autoplay.default=1 Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: With `media.autoplay.enabled.user-gestures-needed` set to false and `media.autoplay.default` set to 1 (block audio), which is the default (and other autoplay-related settings in their defaults as well), a Twitch video can only be either paused or playing muted; unmuting the video pauses it and vice versa. == Steps to reproduce == 1. Open about:config 2. Search for autoplay in the settings 3. Set media.autoplay.enabled.user-gestures-needed to false 4. Set media.autoplay.default to 1 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 6. Try to unmute the video == What happens == The video is unmuted, but also paused == What I expect to happen == For the video to continue playing, unmuted ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BuildID: 20200403170909 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 16:33:46 2020 InstallationDate: Installed on 2016-10-13 (1289 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+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 1844808] Re: Can't delete file from desktop by clicking it and hitting delete key
This bug still exists in Ubuntu 20.04. It's particularly insidious because it's easy to delete a file by mistake: if a Nautilus window has focus and you click on a desktop icon and press the Delete key, then Nautilus will delete the file (which you might or might not notice). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: Can't delete file from desktop by clicking it and hitting delete key Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Just upgraded to 19.10 today. Previously, in 19.04, I could delete a file from the desktop by clicking on it and hitting the delete key. That no longer works. It's probably relevant that it doesn't appear to be possible to direct keyboard focus to the desktop itself any longer. When I click on an icon on the desktop and then hit the delete key, the keystroke is sent to the window that had focus before I clicked. This appears to be true regardless of what window focus mode I'm using (Click to Focus, Focus on Hover, or Secondary-Click). Note that the description of Secondary- Click, "Window is focused when hovered with the pointer. Hovering the desktop removes focus from the previous window," does not appear to be true. When I select that focus mode and hover my mouse over the desktop I remain focused on the previously focused window. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:12:42 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1844808/+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 1857335] Re: System volume slider only works between ~90% and 100%.
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: Expired Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+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 1877705] [NEW] package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new'
Public bug reported: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877705 Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en- US/text/swriter/main0503.html.dpkg-new': Operation not permitted Status in libreoffice package in Ubuntu: New Bug description: getting this error when running sudo apt --fix-broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-help-en-us 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 8 20:39:30 2020 DpkgTerminalLog: Preparing to unpack .../0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb ... Unpacking libreoffice-help-en-us (1:6.4.3-0ubuntu0.20.04.1) over (1:6.4.2-0ubuntu3) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-w9oOcm/0-libreoffice-help-en-us_1%3a6.4.3-0ubuntu0.20.04.1_all.deb (--unpack): unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-04-29 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: libreoffice Title: package libreoffice-help-en-us 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/share/libreoffice/help/en-US/text/swriter/main0503.html.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877705/+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 1792668] Re: gnome-calendar fails to sync, update, or cache
I have avoided using the calendar application as it has been too buggy to be usable, I will need to see if this issue still occurs. Basically you are saying that it needs to be reported upstream? -- 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/1792668 Title: gnome-calendar fails to sync, update, or cache Status in gnome-calendar package in Ubuntu: Incomplete Bug description: Not sure if this is three different bugs or three symptoms of the same problem, but I am observing three different problematic behaviors on a fresh 18.04.1 install with latest updates: 1. Failure to sync: I have all my online google accounts active, but the calendar does not seem to grab new events from the online database. Nor does it transmit new events to the online database. Nor does it do any of these things when manually selecting the "synchronize" option under the menu. 2. Failure to update: I cannot manually add new events to the calendar. Although the app appears fully interactive, none of my interactions (e.g., adding an event) seem to actually get entered into the calendar, even locally. 3. Failure to cache: I have many local calendars displayed that the calendar app has appeared to pick up from other applications' data. I try to manually remove them by opening the calendars display, clicking on the calendar and clicking "remove." This appears to remove the calendar from this menu, but it doesn't remove it from being displayable. When I close and re-open the application, the local calendars have reappeared. Also, I cannot permanently rename calendars. When I close the app and re-open it, the calendar name has reverted to its original state. This might be related in part to another issue, where I have my UbuntuOne account active, but still get prompted regularly for my username and password from various programs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 15 15:06:10 2018 InstallationDate: Installed on 2018-09-12 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1792668/+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 1877288] Re: Text and icons in top bar is offset and hanging down
I'm also facing this exact behavior after upgrading to 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1877288 Title: Text and icons in top bar is offset and hanging down Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: ## What is the bug When upgradig to Ubuntu 20.04, it also updated Gnome to 3.36.1. When using my ultrawide (and configuring it via xrandr because the gnome config tool does not work properly) the top bar is behaving strange. When no windows are open, the top bar "Activities" are showing correctly, but when opening a window, the text and hitbox doubles in height. The part with the tray icons and power/internet etc is wrong all the time. See attached image. ## What happened Text and open programs field double the bar height. Also affects the tray area. ## What did you expect to happen Normal height on top bar. ## Versions Ubuntu: 20.04 LTS gnome-shell-extension-ubuntu-dock: Installed: 67ubuntu20.04.5 Candidate: 67ubuntu20.04.5 Version table: *** 67ubuntu20.04.5 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://no.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 12:48:36 2020 InstallationDate: Installed on 2020-02-09 (88 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to focal on 2020-05-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1877288/+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 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
This issue persists in lightdm 1.30.0-0ubuntu3.1 in Ubuntu focal. I see the warnings not only for pam_kwallet.so, but also its successor pam_kwallet5.so, as well as pam_gnome_keyring.so (which I do not have installed). All three of these are referenced in /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter as "optional" modules. I attempted to eliminate the warnings by replacing the "optional" keyword with "[success=ok module_unknown=ignore default=ignore]", but that had no visible effect. The entries referring to these modules need to be removed from LightDM's PAM config files. If libpam-gnome-keyring is installed, it will already make itself known to PAM via a pam-auth-update profile, which is the correct approach. The libpam-kwallet5 package has no pam-auth-update profile, but that is an issue for that package, not this one. ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Status in One Hundred Papercuts: Confirmed Status in Light Display Manager: Confirmed Status in systemd: New Status in lightdm package in Ubuntu: Confirmed Bug description: auth.log complaints: Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm. Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "oem" Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for user oem by (uid=0) As per lp:1309535 #18 comment such 'warnings' should be silenced (as they scared unawared users about the both needs of pam's gnome/kde) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0 Uname: Linux 3.18.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Dec 19 10:47:07 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
It is not easy to debug without hardware, so the best way is to report this issue to https://github.com/thesofproject/linux/issues/new -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1872330] Re: Cannot open gear icon of an input source in Region & Language
** Changed in: ibus-unikey (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-unikey in Ubuntu. https://bugs.launchpad.net/bugs/1872330 Title: Cannot open gear icon of an input source in Region & Language Status in ibus-unikey package in Ubuntu: Fix Released Status in ibus-unikey package in Debian: Fix Released Bug description: Using the Ubuntu 20.04 Focal Fossa Beta version. Using the gnome-control-center version 1:3.36.1-1ubuntu4 What should happen: Clicking on the gear icon of an input source in the Input Sources section in Region & Language should open the respective settings menu. What happened: Clicking on the gear icon does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-unikey/+bug/1872330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Toshiba Satellite Radius 12 C-720 same problem ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877686] Re: Mouse lags since 20.04 update
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877686 Title: Mouse lags since 20.04 update Status in xorg package in Ubuntu: New Bug description: After installing ubuntu 20.04, I have an issue with my mouse pointer lagging a lot. It happens on my trackpad, physical mouse, wacom tablet, and trackpoint. It's only a graphical issue (ie: The underlying whatever is actually moving. The visible pointer just isn't). Other mouse moving related actions do not exhibit the same behaviour. Window dragging is smooth. Applications that use custom mouse pointers, such as krita, work smoothly. The issue persists both on nVidia graphics and intel integrated graphics. I am using a lenovo thinkpad p50. The issue persists constantly when I am using the in built laptop screen. However, when I connect a second monitor, it only happens occasionally. I installed ubuntu 20.04 from a usb drive, keeping my home partition from 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 01:28:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:222e] NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] InstallationDate: Installed on 2020-05-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 20EQS2BH00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2BH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS2BH00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877686/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1877686] [NEW] Mouse lags since 20.04 update
You have been subscribed to a public bug: After installing ubuntu 20.04, I have an issue with my mouse pointer lagging a lot. It happens on my trackpad, physical mouse, wacom tablet, and trackpoint. It's only a graphical issue (ie: The underlying whatever is actually moving. The visible pointer just isn't). Other mouse moving related actions do not exhibit the same behaviour. Window dragging is smooth. Applications that use custom mouse pointers, such as krita, work smoothly. The issue persists both on nVidia graphics and intel integrated graphics. I am using a lenovo thinkpad p50. The issue persists constantly when I am using the in built laptop screen. However, when I connect a second monitor, it only happens occasionally. I installed ubuntu 20.04 from a usb drive, keeping my home partition from 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 01:28:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:222e] NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e] InstallationDate: Installed on 2020-05-08 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:0090 Validity Sensors, Inc. VFS7500 Touch Fingerprint Sensor Bus 001 Device 002: ID 04ca:7058 Lite-On Technology Corp. Integrated Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 8: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 9: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 20EQS2BH00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9eb4b789-a22e-455b-8e8b-19e78e0ef3d6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET86W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS2BH00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET86W(1.59):bd08/28/2019:svnLENOVO:pn20EQS2BH00:pvrThinkPadP50:rvnLENOVO:rn20EQS2BH00:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P50 dmi.product.name: 20EQS2BH00 dmi.product.sku: LENOVO_MT_20EQ_BU_Think_FM_ThinkPad P50 dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Mouse lags since 20.04 update https://bugs.launchpad.net/bugs/1877686 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Asus Gl703VD has the same problem Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877675] [NEW] Workspaces broken with latest update
Public bug reported: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:05:52 2020 DistUpgraded: 2020-04-27 21:42:55,589 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1660 Ti] [1458:3fbe] InstallationDate: Installed on 2018-07-01 (677 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6998b6fb-9ba7-4ce9-a023-b36dab34d51a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (10 days ago) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: X470 AORUS ULTRA 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.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnX470AORUSULTRAGAMING:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX470AORUSULTRAGAMING-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X470 AORUS ULTRA GAMING dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877675 Title: Workspaces broken with latest update Status in xorg package in Ubuntu: New Bug description: Multiple workspaces broke with latest gnome config update. Unable to create, or go to different workspaces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8
Re: [Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal
Ok, I understand. I updated from 19.10, so that explains why I have them already. El vie., 8 de may. de 2020 a la(s) 18:25, Matthias Klumpp ( matth...@tenstral.net) escribió: > On a fresh Ubuntu installation, apt-config-icons isn't installed by > default (at least it wasn't when I installed a fresh Ubuntu yesterday, > until I replaced the snap-store with the packaged gnome-software). So > new users who aren't upgrading from a previous Ubuntu version will still > have much less icons than people who get Focal by upgrading from an > older Ubuntu release. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873281). > https://bugs.launchpad.net/bugs/1864307 > > Title: > Many apps have no icon in Software on Focal > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-software/+bug/1864307/+subscriptions > -- Nicolás Abel Carbone Doctor en Física - Becario Posdoctoral CIFICEN-CONICET-UNCPBA https://www.researchgate.net/profile/Nicolas_Carbone *Mi horario de trabajo puede no coincidir con el suyo. Salvo que así lo indique el mail, por favor no se sienta obligado a responder este mensaje fuera de su horario de trabajo habitual.* *My working hours may not be your working hours. Unless otherwise specified in the mail, please do not feel obligated to reply outside of your normal work schedule.* -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1869561] Re: Libreoffice Help does not work
Thank you Sebastien. Following your suggestion, I replaced the main.xcd file in /usr/lib/libreoffice/share/registry/ and F1 now displays the help screens as expected. -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
On my ASUS Rog GL703VD-GC028T Notebook, I was able to use both microphone and sound adding the line options snd-hda-intel model=laptop-dmic,headset-mic,auto to /etc/modprobe.d and modifing the line #load-module module-alsa-sink control=xxx with load-module module-alsa-sink control=PCM and modifying the line load-module module-udev-detect with load-module module-udev-detect ignore_dB=1 to /etc/pulse/default.pa file I'm not sure all the modifications are essential. Check the ubuntu sound setting for output Built-in Audio -- 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/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1811504] Re: Scan with HP LaserJet Pro MFP M28a fails
OK, it was actually a trivial thing, just needed to refresh the search for scanners, it works!! Thanks very much for posting the different solutions -- 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/1811504 Title: Scan with HP LaserJet Pro MFP M28a fails Status in hplip package in Ubuntu: Fix Released Bug description: I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I always get this error when scanning using SANE: error: SANE: Error during device I/O (code=9) I’ve installed hplip hplip-plugins and any other dependencies listed in hp-check but without luck. any hints? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1811504/+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 1864307] Re: Many apps have no icon in Software on Focal
On a fresh Ubuntu installation, apt-config-icons isn't installed by default (at least it wasn't when I installed a fresh Ubuntu yesterday, until I replaced the snap-store with the packaged gnome-software). So new users who aren't upgrading from a previous Ubuntu version will still have much less icons than people who get Focal by upgrading from an older Ubuntu release. -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Another experiment: while emoji are broken, I can do sudo fc-cache -s
-v, and it doesn't find any invalid cache files, and when I restart
chromium, I don't get color emoji.
But then I do sudo apt install --reinstall fonts-noto-color-emoji, and I
see a /var/log/fontconfig.log with an up-to-date timestamp, and it says,
again,
/var/cache/fontconfig: invalid cache file:
0bd3dc0958fa22058ebb13e2872b-le64.cache-7
and I restart chromium again, and now I have working color emoji.
(Until the next snap refresh at least).
I don't understand anything.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version:
[Desktop-packages] [Bug 1877655] Re: Synaptic Trackpad works until actually logged into Xorg desktop
I have no idea what sub group/package this belongs in. I know it affects Gnome and KDE on Xorg. I don't know if GDM (or whatever now handles the login process) does differently from the full gnome that allows the trackpad to at least partially work (movement, but not button clicks) ** Description changed: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. - When at the login page, the trackpad and keyboard operate as they + When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: - Event type 0 (EV_SYN) - Event type 1 (EV_KEY) - Event code 272 (BTN_LEFT) - Event code 325 (BTN_TOOL_FINGER) - Event code 330 (BTN_TOUCH) - Event code 333 (BTN_TOOL_DOUBLETAP) - Event code 334 (BTN_TOOL_TRIPLETAP) - Event type 3 (EV_ABS) - Event code 0 (ABS_X) - Value483 - Min0 - Max 1056 - Resolution 12 - Event code 1 (ABS_Y) - Value266 - Min0 - Max 516 - Resolution 12 - Event code 47 (ABS_MT_SLOT) - Value 0 - Min0 - Max2 - Event code 53 (ABS_MT_POSITION_X) - Value 0 - Min0 - Max 1056 - Resolution 12 - Event code 54 (ABS_MT_POSITION_Y) - Value 0 - Min0 - Max 516 - Resolution 12 - Event code 55 (ABS_MT_TOOL_TYPE) - Value 0 - Min0 - Max2 - Event code 57 (ABS_MT_TRACKING_ID) - Value 0 - Min0 - Max65535 - Event type 4 (EV_MSC) - Event code 5 (MSC_TIMESTAMP) + Event type 0 (EV_SYN) + Event type 1 (EV_KEY) + Event code 272 (BTN_LEFT) + Event code 325 (BTN_TOOL_FINGER) + Event code 330 (BTN_TOUCH) + Event code 333 (BTN_TOOL_DOUBLETAP) + Event code 334 (BTN_TOOL_TRIPLETAP) + Event type 3 (EV_ABS) + Event code 0 (ABS_X) + Value483 + Min0 + Max 1056 + Resolution 12 + Event code 1 (ABS_Y) + Value266 + Min0 + Max 516 + Resolution 12 + Event code 47 (ABS_MT_SLOT) + Value 0 + Min0 + Max2 + Event code 53 (ABS_MT_POSITION_X) + Value 0 + Min0 + Max 1056 + Resolution 12 + Event code 54 (ABS_MT_POSITION_Y) + Value 0 + Min0 + Max 516 + Resolution 12 + Event code 55 (ABS_MT_TOOL_TYPE) + Value 0 + Min0 + Max2 + Event code 57 (ABS_MT_TRACKING_ID) + Value 0 + Min0 + Max65535 + Event type 4 (EV_MSC) + Event code 5 (MSC_TIMESTAMP) Properties: - Property type 0 (INPUT_PROP_POINTER) - Property type 2 (INPUT_PROP_BUTTONPAD) + Property type 0 (INPUT_PROP_POINTER) + Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) - - I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. + I did try to remove xserver-xorg-input-synaptics, but it is not + installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad works until actually logged into Xorg desktop Status in xorg package in Ubuntu: New Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver
[Desktop-packages] [Bug 1877670] [NEW] Display Freezes and frequently mouse cursor disappears.
Public bug reported: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Aspire R3-131T dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd11/30/2016:svnAcer:pnAspireR3-131T:pvrV1.17:rvnAcer:rnAspireR3-131T:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.family: BSW dmi.product.name: Aspire R3-131T dmi.product.sku: Aspire R3-131T_1022_1.17 dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877670 Title: Display Freezes and frequently mouse cursor disappears. Status in xorg package in Ubuntu: New Bug description: Display Freezes and frequently mouse cursor disappears. After restart mouse cursor comes back again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 02:25:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:1022] InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 2386:0401 Raydium Corporation Raydium Touch System Bus 001 Device 002: ID 04f2:b520 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire R3-131T ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=5b613349-680c-466c-b069-960c9c12c462 ro quiet splash vt.handoff=7 SourcePackage:
[Desktop-packages] [Bug 1877666] [NEW] Python syntax warning in LayoutLoaderSVG.py
Public bug reported:
This concerns onboard 1.4.1-2ubuntu7 in Ubuntu focal.
Seen during package installation:
[...]
Setting up onboard (1.4.1-2ubuntu7) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
[...]
** Affects: onboard (Ubuntu)
Importance: Undecided
Status: New
** Tags: focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to onboard in Ubuntu.
https://bugs.launchpad.net/bugs/1877666
Title:
Python syntax warning in LayoutLoaderSVG.py
Status in onboard package in Ubuntu:
New
Bug description:
This concerns onboard 1.4.1-2ubuntu7 in Ubuntu focal.
Seen during package installation:
[...]
Setting up onboard (1.4.1-2ubuntu7) ...
/usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning:
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
[...]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1877666/+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 1811504] Re: Scan with HP LaserJet Pro MFP M28a fails
Hi, I'm an absolute newbie and may be asking something trivial. I've installed the sane-airscan package,so now what? Should I use the same applications that didn't work before such as skanlite or xsane and expect them to work now? This is not the case, is there any other thing that I'm missing? Thanks a lot, -- 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/1811504 Title: Scan with HP LaserJet Pro MFP M28a fails Status in hplip package in Ubuntu: Fix Released Bug description: I’m trying to scan with my new printer Hp LaserJet MFP M28-M31 but I always get this error when scanning using SANE: error: SANE: Error during device I/O (code=9) I’ve installed hplip hplip-plugins and any other dependencies listed in hp-check but without luck. any hints? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1811504/+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 1877655] [NEW] Synaptic Trackpad works until actually logged into Xorg desktop
You have been subscribed to a public bug: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Synaptic Trackpad works until actually logged into Xorg desktop https://bugs.launchpad.net/bugs/1877655 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1873658] Re: Deb Files are not associated with an application that manages packages
This bug was fixed in the package desktop-file-utils - 0.24-1ubuntu4 --- desktop-file-utils (0.24-1ubuntu4) groovy; urgency=medium * debian/defaults.list - Updated for the transition to snap-store (LP: #1873658) -- Ken VanDine Fri, 08 May 2020 10:01:44 -0400 ** Changed in: desktop-file-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Fix Released Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Committed Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1858636] Re: [snap] color emoji not rendered; many bw emoji rendered as boxes
Yesterday I saw a notification about chromium being auto-refreshed,
restarted it, and today I noticed that color emoji are gone again.
I suspect the two facts are related.
--
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/1858636
Title:
[snap] color emoji not rendered; many bw emoji rendered as boxes
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
I’ve recently noticed that Chromium no longer can display emoji. All I
get are square boxes and some black & white symbols. E.g.
https://getemoji.com renders like the screenshot I posted to
https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
to-snap-transition/11179/237.
I'm like 95% sure that this is a recent problem, and that I didn't
have it when I first upgraded to Ubuntu 19.10 and to the snapified
Chromium.
Note that I don't have fonts-symbola installed, and I do have fonts-
not-color-emoji installed. I've also noticed a bunch of
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error:
Cannot load default config file
messages in journalctl when I first launch chromium.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
DRM.card0-DP-4:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-DP-5:
enabled: disabled
dpms: On
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-eDP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
modes: 1920x1080
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
tmpfs tmpfs 7,7G 164M 7,6G 3% /dev/shm
/dev/nvme0n1p5 ext4 284G 241G 29G 90% /
DistroRelease: Ubuntu 19.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-06-12 (208 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20Q0CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
Tags: eoan wayland-session snap
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/18/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET73W (1.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
Great to see traction on this, thank you for all your efforts Daniel! And to everyone else, this is a far more complex problem than you can imagine However it can and will be solved :) -- 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. Status in PulseAudio: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed 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 1877279] Re: my wallpaper is changed after computer sleep
The attachment "journal.txt" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1864307] Re: Many apps have no icon in Software on Focal
@ximion: Sorry, I don't follow. I have both apt-config-icons and appstream installed. I do see the icons for apt apps in snap-store now with the beta version. -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1876693] Re: [SRU] New stable release 1.64.1
Hello Iain, or anyone else affected, Accepted gobject-introspection into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gobject-introspection/1.64.1-1~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: gobject-introspection (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1876693 Title: [SRU] New stable release 1.64.1 Status in gobject-introspection package in Ubuntu: Fix Released Status in gobject-introspection source package in Focal: Fix Committed Bug description: [ Description ] GNOME upstream have released a new stable version of gobject- introspection. Changes: 1.64.1 - 2020-04-05 --- * Replace calls to deprecated xml.etree.cElementTree removed in Python 3.9 :mr:`202` (:user:`Stephen Gallagher `) * gimarshallingtests: Use g_assert_cmpfloat_with_epsilon. Fixes tests on some architectures :mr:`200` (:user:`Iain Lane `) [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. Do this: - Install the update, smoke test some of the reverse depends (apt rdepends libgirepository-1.0-1 and more importantly the indirect rdepends via python3-gi) - Run "reverse-depends -b src:gobject-introspection" and test rebuild a few of them [ Regression potential ] g-i being broken will break pretty much the whole desktop, but you'd know that quite fast. The .py changes, if they're wrong or bad, could break the build of r -build-deps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1876693/+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 1877630] Re: działa bardzo wolno
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877630 Title: działa bardzo wolno Status in gnome-shell package in Ubuntu: New Bug description: Nie potrafię zdiagnozować nie zanam się na tym. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 18:46:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877630/+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 1868116] Re: QEMU monitor no longer works
** Changed in: qemu (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in qemu package in Debian: Fix Released Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+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 1877630] [NEW] działa bardzo wolno
You have been subscribed to a public bug: Nie potrafię zdiagnozować nie zanam się na tym. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 18:46:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- działa bardzo wolno https://bugs.launchpad.net/bugs/1877630 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 1876263] Re: SRU the current 3.36.1 stable update
Hello Sebastien, or anyone else affected, Accepted gnome-settings-daemon into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.36.1-0ubuntu1 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. ** Summary changed: - SRU the current 3.36.2 stable update + SRU the current 3.36.1 stable update ** Changed in: gnome-settings-daemon (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1876263 Title: SRU the current 3.36.1 stable update Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/master/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME session still work correctly, including theme and screen configuration * Regression potential Nothing specific to test in this update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1876263/+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 1874130] Re: lirc fails to install because of a missing /etc/lirc/lirc_options.conf - Ubuntu 20.04
Hello Mastermolch, or anyone else affected, Accepted lirc into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lirc/0.10.1-6.1ubuntu1.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: lirc (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1874130 Title: lirc fails to install because of a missing /etc/lirc/lirc_options.conf - Ubuntu 20.04 Status in lirc package in Ubuntu: Fix Released Status in lirc source package in Focal: Fix Committed Bug description: * Impact the lirc package fails to install, the service segfault on start * Test case install lirc, the installation shouldn't fail, also the service should correctly start * Regression potential the changes are only packaging ones to ensure a configuration is available, check new isntalls and upgrades to make sure the configuration is installed and the service works -- Hello, I have tried to install lirc on a fresh Kubuntu 20.04 Release Candidate installation on a AMD Athlon X2 system. The installation failed, with a half installed lirc package. This is leaving apt-get / apt in a state, that makes it impossible to install other packages or updates anymore, as it first tries to finish the lirc installation. This is leaving the system in a state, where further software changes or the usage of lirc are not possible. After using Google to find a solution for the problem, I found this bug report about lirc on Debian bugs website: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932779 The suggested workaround is to creating the file lirc_options.conf and to continue the failed installation (which worked on my system) via: sudo cp /etc/lirc/lirc_options.conf.dist /etc/lirc/lirc_options.conf sudo apt-get install lirc This worked on my installation brought the system back into a state, where further software installations or updates via apt-get / apt work again. Ubuntu version: user1@AthlonX2:lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 package information: user1@AthlonX2:/etc/lirc$ apt-cache policy lirc lirc: Installiert: 0.10.1-6.1 Installationskandidat: 0.10.1-6.1 Versionstabelle: *** 0.10.1-6.1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Terminal output during the failing installation via apt-get install: user1@AthlonX2:/etc/lirc$ LC_ALL=C sudo apt-get install lirc Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libftdi1-2 liblirc0 Suggested packages: lirc-compat-remotes lirc-drv-irman lirc-doc lirc-x setserial ir-keytable Recommended packages: gir1.2-vte The following NEW packages will be installed: libftdi1-2 liblirc0 lirc 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/571 kB of archives. After this operation, 2897 kB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libftdi1-2:amd64. (Reading database ... 360984 files and directories currently installed.) Preparing to unpack .../libftdi1-2_1.4-2build2_amd64.deb ... Unpacking libftdi1-2:amd64 (1.4-2build2) ... Selecting previously unselected package liblirc0:amd64. Preparing to unpack .../liblirc0_0.10.1-6.1_amd64.deb ... Unpacking liblirc0:amd64 (0.10.1-6.1) ... Selecting previously unselected package lirc. Preparing to unpack .../lirc_0.10.1-6.1_amd64.deb ... Unpacking lirc (0.10.1-6.1) ... Setting up liblirc0:amd64 (0.10.1-6.1) ... Setting up
[Desktop-packages] [Bug 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Trying more things here. I changed Hdmi.conf back to my original file. The system boots with your v5 kernel. http://alsa-project.org/db/?f=441f6bdb49c44e8ce84cee41ef1b6917544febcb Still no sound. Seeing Dummy Output. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368592/+files/dmesg -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Trying more things here. I changed Hdmi.conf back to my original file. The system boots with your v5 kernel. http://alsa-project.org/db/?f=441f6bdb49c44e8ce84cee41ef1b6917544febcb Still no sound. Seeing Dummy Output. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368591/+files/dmesg -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Thanks for this. I tried it with your Hdmi.conf from v4. I could boot up to the login screen. After seeing the login GUI screen for a few seconds, the system just freezes (no longer responds to mouse and keyboard input). Attaching dmesg.0. I guess there is some file system check or something else that gets executed at that moment and disrupts the whole boot sequence. ** Attachment added: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874698/+attachment/5368568/+files/dmesg.0 -- 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/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1877648] [NEW] Laptop video problem
Public bug reported: After a fresh install, the system goes to sleep mode in place of showing logon display. After waking up, the screen stay black but login action and shutdown button seems to work so there's no video on laptop screen (LVDS-1). When i connect an DVI-I monitor before starting, the computer doesn't go in sleep mode at startup. I can see the logon on external monitor but there nothing on internal monitor. I can use the two monitor when i use those commands: xrandr --output DVI-I-1 --mode 1400x1050 --primary xrandr --output LVDS-1 --mode 1440x900 --right-of DVI-I-1 --crtc 0 LVDS-1 is reported as "unknown connection" in place of "connected" or "disconnected". Xorg0.log report that the internal monitor is disconnected : [31.856] (II) NOUVEAU(0): Output VGA-1 disconnected [31.856] (II) NOUVEAU(0): Output LVDS-1 disconnected [31.856] (II) NOUVEAU(0): Output DVI-I-1 connected [31.856] (II) NOUVEAU(0): Output TV-1 disconnected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 8 20:28:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: FUJITSU SIEMENS Amilo M3438 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=f910d7c1-f499-455a-ade2-472c22149dcd ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10C dmi.board.name: P71EN0 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10C:bd10/05/2005:svnFUJITSUSIEMENS:pnAmiloM3438Series:pvr:rvn:rnP71EN0:rvr:cvnFUJITSUSIEMENS:ct10:cvr: dmi.product.name: Amilo M3438 Series dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877648 Title: Laptop video problem Status in xorg package in Ubuntu: New Bug description: After a fresh install, the system goes to sleep mode in place of showing logon display. After waking up, the screen stay black but login action and shutdown button seems to work so there's no video on laptop screen (LVDS-1). When i connect an DVI-I monitor before starting, the computer doesn't go in sleep mode at startup. I can see the logon on external monitor but there nothing on internal monitor. I can use the two monitor when i use those commands: xrandr --output DVI-I-1 --mode 1400x1050 --primary xrandr --output LVDS-1 --mode 1440x900 --right-of DVI-I-1 --crtc 0 LVDS-1 is reported as "unknown connection" in place of "connected" or "disconnected". Xorg0.log report that the internal monitor is disconnected : [31.856] (II) NOUVEAU(0): Output VGA-1 disconnected [31.856] (II) NOUVEAU(0): Output LVDS-1 disconnected [31.856] (II) NOUVEAU(0): Output DVI-I-1 connected [31.856] (II) NOUVEAU(0): Output TV-1 disconnected ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic i686 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: i386 CompositorRunning: None CurrentDesktop: XFCE Date: Fri May 8 20:28:43 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41M [GeForce Go 6800] [10de:00c8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions NV41M [GeForce Go 6800] [1734:107c] InstallationDate: Installed on 2020-04-17 (21 days ago) InstallationMedia: Xubuntu 18.04 LTS
[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal
@nicocarbone: You'll also want to do something that `apt-config-icons` is installed alongside `appstream` in Ubuntu desktops that use the gnome-software Snap. -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1864307] Re: Many apps have no icon in Software on Focal
I update to the beta branch and the icons are there. Thanks! :) Is there anything in particular to test? Something I noticed in this branch (a nitpick and, I guess, completely unrelated): the window control icons (minimize, maximize, close) seems to be bolder that before and than any other app using Yaru. -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1877135] Re: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found]
No problem, glad that we figured it out! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1877135 Title: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found] Status in gvfs package in Ubuntu: Invalid Bug description: After upgrading to Focal, /usr/libexec/gvfs-afc-volume-monitor fails with the message /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory 1) lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 2)apt-cache policy gvfs gvfs: Installed: 1.44.1-1ubuntu1 Candidate: 1.44.1-1ubuntu1 Version table: *** 1.44.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 4) What happens: many applications (nautilus, gedit, etc) take ~30 sec to open. When starting those via the command line, after after those 30 secs the app opens with the following printed to the terminal: "Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)" 3) What you expected to happen: applications to open without delay = Additional info: After calling 'journalctl -b', several instances like dbus-daemon[2031]: [session uid=1000 pid=2031] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.25' (uid=1000 pid=2135 comm="/usr/bin/gnome-shell " label="unconfined") systemd[1964]: Starting Virtual filesystem service - Apple File Conduit monitor... gvfs-afc-volume-monitor[2279]: /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory systemd[1964]: gvfs-afc-volume-monitor.service: Main process exited, code=exited, status=127/n/a systemd[1964]: gvfs-afc-volume-monitor.service: Failed with result 'exit-code'. systemd[1964]: Failed to start Virtual filesystem service - Apple File Conduit monitor. Also upowerd is affected: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory upower.service: Main process exited, code=exited, status=127/n/a upower.service: Failed with result 'exit-code'. Failed to start Daemon for power management. The package libusbmuxd6 is installed (and /usr/lib/x86_64-linux- gnu/libusbmuxd.so.6 is present), but when trying "sudo apt install libusbmuxd4", I get the error "E: Unable to locate package libusbmuxd4". It would appear to me that some dependencies *somewhere* are not properly updated (to libusbmuxd6 from libusbmuxd4). Unfortunately, the huge timeout significantly affects usability of the computer, as one has to wait a lot to perform many tasks (opening nautilus, gedit); one has to wait also before login screen appears after a reboot. Something that appears to be related: https://forum.manjaro.org/t/upower-fails-to-start-becuase-upowerd-is-not-running/117291 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs-backends 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed May 6 13:45:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-18 (1875 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gvfs UpgradeStatus: Upgraded to focal on 2020-04-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1877135/+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 1864307] Re: Many apps have no icon in Software on Focal
I've pushed the fix from @ximion to snap-store in the beta channel for testing. This fix will be published to ubuntu-20.04 after thorough testing Thanks! ** Changed in: snap-store Importance: Undecided => High ** Changed in: snap-store Status: New => Fix Committed -- 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/1864307 Title: Many apps have no icon in Software on Focal Status in GNOME Software: Unknown Status in snap-store: Fix Committed Status in gnome-software package in Ubuntu: Confirmed Bug description: Many applications have no icon displayed in GNOME Software 3.35.91 on latest Ubuntu Focal. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1864307/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
Thanks for the detailed explanation Seth. The bluetooth and wifi are on the same chip and the bluetooth is not even being detected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Output of lsb_release -rd, Description: Ubuntu 20.04 LTS Release: 20.04 Issue: I have Intel AX-201 for wireless but when i do "lspci -k", the driver is detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows that the wireless driver detected is "Intel AX-201". Output of lspci -k, 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 Subsystem: Intel Corporation Wireless-AC 9462 Kernel driver in use: iwlwifi Kernel modules: iwlwifi Output of journalctl -k | grep iwlwifi, May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002) May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0 May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95 May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring In the additional drivers module, it shows that module Intel-9462 no longer works. My bluetooth is also not detected and doesn't work. I came across this but no else responded yet. So decided to report a bug here. https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems Please let me know if any more information is required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srikar 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.20:bd11/29/2019:svnHP:pnHPSpectrex360Convertible15-df1xxx:pvr:rvnHP:rn863F:rvr54.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df1xxx dmi.product.sku: 7UT64UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1877640] Re: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
** Tags added: kernel-sound -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV 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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877640/+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 1877641] [NEW] Gnome Calendar crashes if a calendar is subscribed to
Public bug reported: Gnome Calendar crashes if I (1) subscribe out of a calendar and then (2) subscribe back to the calendar. It does not crash if I close the app between these two steps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:39:23 2020 InstallationDate: Installed on 2018-04-27 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) ** Affects: gnome-calendar (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 gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1877641 Title: Gnome Calendar crashes if a calendar is subscribed to Status in gnome-calendar package in Ubuntu: New Bug description: Gnome Calendar crashes if I (1) subscribe out of a calendar and then (2) subscribe back to the calendar. It does not crash if I close the app between these two steps. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:39:23 2020 InstallationDate: Installed on 2018-04-27 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1877641/+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 1874130] Re: lirc fails to install because of a missing /etc/lirc/lirc_options.conf - Ubuntu 20.04
This bug was fixed in the package lirc - 0.10.1-6.1ubuntu2 --- lirc (0.10.1-6.1ubuntu2) groovy; urgency=medium * debian/lirc.postinst: - restore the postinst snippet ensuring that the configuration files exists. It was removed 0.10.1-5.1 in favor of making those proper conffiles but the changes were reverted in 0.10.1-5.2 in an incomplete way letting the file without configuration installed which leads to the service segfaulting and the install failing (lp: #1874130) -- Sebastien Bacher Fri, 08 May 2020 11:16:15 +0200 ** Changed in: lirc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/1874130 Title: lirc fails to install because of a missing /etc/lirc/lirc_options.conf - Ubuntu 20.04 Status in lirc package in Ubuntu: Fix Released Bug description: * Impact the lirc package fails to install, the service segfault on start * Test case install lirc, the installation shouldn't fail, also the service should correctly start * Regression potential the changes are only packaging ones to ensure a configuration is available, check new isntalls and upgrades to make sure the configuration is installed and the service works -- Hello, I have tried to install lirc on a fresh Kubuntu 20.04 Release Candidate installation on a AMD Athlon X2 system. The installation failed, with a half installed lirc package. This is leaving apt-get / apt in a state, that makes it impossible to install other packages or updates anymore, as it first tries to finish the lirc installation. This is leaving the system in a state, where further software changes or the usage of lirc are not possible. After using Google to find a solution for the problem, I found this bug report about lirc on Debian bugs website: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932779 The suggested workaround is to creating the file lirc_options.conf and to continue the failed installation (which worked on my system) via: sudo cp /etc/lirc/lirc_options.conf.dist /etc/lirc/lirc_options.conf sudo apt-get install lirc This worked on my installation brought the system back into a state, where further software installations or updates via apt-get / apt work again. Ubuntu version: user1@AthlonX2:lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 package information: user1@AthlonX2:/etc/lirc$ apt-cache policy lirc lirc: Installiert: 0.10.1-6.1 Installationskandidat: 0.10.1-6.1 Versionstabelle: *** 0.10.1-6.1 500 500 http://de.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status Terminal output during the failing installation via apt-get install: user1@AthlonX2:/etc/lirc$ LC_ALL=C sudo apt-get install lirc Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libftdi1-2 liblirc0 Suggested packages: lirc-compat-remotes lirc-drv-irman lirc-doc lirc-x setserial ir-keytable Recommended packages: gir1.2-vte The following NEW packages will be installed: libftdi1-2 liblirc0 lirc 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/571 kB of archives. After this operation, 2897 kB of additional disk space will be used. Do you want to continue? [Y/n] y Selecting previously unselected package libftdi1-2:amd64. (Reading database ... 360984 files and directories currently installed.) Preparing to unpack .../libftdi1-2_1.4-2build2_amd64.deb ... Unpacking libftdi1-2:amd64 (1.4-2build2) ... Selecting previously unselected package liblirc0:amd64. Preparing to unpack .../liblirc0_0.10.1-6.1_amd64.deb ... Unpacking liblirc0:amd64 (0.10.1-6.1) ... Selecting previously unselected package lirc. Preparing to unpack .../lirc_0.10.1-6.1_amd64.deb ... Unpacking lirc (0.10.1-6.1) ... Setting up liblirc0:amd64 (0.10.1-6.1) ... Setting up libftdi1-2:amd64 (1.4-2build2) ... Setting up lirc (0.10.1-6.1) ... Job for lircd.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status lircd.service" and "journalctl -xe" for details. invoke-rc.d: initscript lircd, action "start" failed. * lircd.service - Flexible IR remote input/output application support Loaded: loaded (/lib/systemd/system/lircd.service; disabled; vendor preset: enabled) Active: failed (Result: core-dump) since Tue 2020-04-21 20:05:34 CEST; 16ms ago TriggeredBy: * lircd.socket Docs: man:lircd(8) http://lirc.org/html/configure.html Process: 12249 ExecStart=/usr/sbin/lircd --nodaemon (code=dumped, signal=SEGV) Main PID: 12249 (code=dumped, signal=SEGV)
[Desktop-packages] [Bug 1877640] [NEW] [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones.
Public bug reported: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV 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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name: Zephyrus M GU502GV_GU502GV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1877640 Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294] No sound in 3.5mm jack headphones. Status in alsa-driver package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS dual boot with Windows 10. On Windows all is fine. On Ubuntu i have sound for speakers, but no sound at all for 3.5mm jack headphones. Tried using latest kernel versions for 4.*, 5.*, tried even 5.7-rc4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.6.11-050611-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: corsarstl 1728 F pulseaudio /dev/snd/pcmC0D0p: corsarstl 1728 F...m pulseaudio /dev/snd/controlC1: corsarstl 1728 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 8 20:25:27 2020 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio /dev/snd/controlC1: gdm1227 F pulseaudio corsarstl 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Zephyrus M GU502GV_GU502GV, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GU502GV.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GU502GV 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.:bvrGU502GV.307:bd02/15/2020:svnASUSTeKCOMPUTERINC.:pnZephyrusMGU502GV_GU502GV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGU502GV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus M dmi.product.name:
[Desktop-packages] [Bug 1877627] Re: /etc/default/im-config leaves temporary variables fixed in environment
Thanks for your report, but I can't reproduce it. Can you please run: apport-collect 1877627 ** Changed in: im-config (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1877627 Title: /etc/default/im-config leaves temporary variables fixed in environment Status in im-config package in Ubuntu: Incomplete Bug description: Ubuntu 18.04 im-config 0.34-1ubuntu1.3 You can reproduce the issue following these steps: - Open a X terminal - echo $d - Returns "GNOME" The source is this line in /etc/default/im-config: for d in 'Unity' 'MATE' 'GNOME'; do the temporary variable d gets fixed in the environment variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1877627/+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 1876292]
No, because you reported pages issue first and that's WFM. -- 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/1876292 Title: Error in layout from MS DOCX file, especially after saving as ODT Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: New Bug description: For the details and example file please see: https://bugs.documentfoundation.org/show_bug.cgi?id=132552 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1876292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
@Michel: sorry for the late feedback. On that Pentium N5000 system, could you please include the full output of running "chromium --enable- logging=stderr", and the corresponding journalctl entries, filtered on "chromium"? @Miguel: which OS/version are you running the chromium snap on? Can you please include the output of "snap info --abs-time chromium" ? For reference, I tested on my HD Graphics 4000 (Ivy bridge, Core i7) and I'm seeing similar numbers as Michel in comment #21. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Beta Chromium 80 Snap with vaapi enabled : https://code.launchpad.net/~chromium-team/+snap/chromium-snap-from- source-enable- vaapi/+build/918074/+files/chromium_81.0.4044.113_amd64.snap Install it with --devmode --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877135] Re: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found]
Amazing! Indeed there was a forgotten local installation of 'libimobiledevice'. After properly removing it, no problems whatsoever. Thank you so much for your time! ** Changed in: gvfs (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1877135 Title: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found] Status in gvfs package in Ubuntu: Invalid Bug description: After upgrading to Focal, /usr/libexec/gvfs-afc-volume-monitor fails with the message /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory 1) lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 2)apt-cache policy gvfs gvfs: Installed: 1.44.1-1ubuntu1 Candidate: 1.44.1-1ubuntu1 Version table: *** 1.44.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 4) What happens: many applications (nautilus, gedit, etc) take ~30 sec to open. When starting those via the command line, after after those 30 secs the app opens with the following printed to the terminal: "Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)" 3) What you expected to happen: applications to open without delay = Additional info: After calling 'journalctl -b', several instances like dbus-daemon[2031]: [session uid=1000 pid=2031] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.25' (uid=1000 pid=2135 comm="/usr/bin/gnome-shell " label="unconfined") systemd[1964]: Starting Virtual filesystem service - Apple File Conduit monitor... gvfs-afc-volume-monitor[2279]: /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory systemd[1964]: gvfs-afc-volume-monitor.service: Main process exited, code=exited, status=127/n/a systemd[1964]: gvfs-afc-volume-monitor.service: Failed with result 'exit-code'. systemd[1964]: Failed to start Virtual filesystem service - Apple File Conduit monitor. Also upowerd is affected: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory upower.service: Main process exited, code=exited, status=127/n/a upower.service: Failed with result 'exit-code'. Failed to start Daemon for power management. The package libusbmuxd6 is installed (and /usr/lib/x86_64-linux- gnu/libusbmuxd.so.6 is present), but when trying "sudo apt install libusbmuxd4", I get the error "E: Unable to locate package libusbmuxd4". It would appear to me that some dependencies *somewhere* are not properly updated (to libusbmuxd6 from libusbmuxd4). Unfortunately, the huge timeout significantly affects usability of the computer, as one has to wait a lot to perform many tasks (opening nautilus, gedit); one has to wait also before login screen appears after a reboot. Something that appears to be related: https://forum.manjaro.org/t/upower-fails-to-start-becuase-upowerd-is-not-running/117291 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs-backends 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed May 6 13:45:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-18 (1875 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gvfs UpgradeStatus: Upgraded to focal on 2020-04-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1877135/+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 1877279] Re: my wallpaper is changed after computer sleep
** Attachment added: "Screenshot from 2020-05-08 21-44-03.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+attachment/5368539/+files/Screenshot%20from%202020-05-08%2021-44-03.png -- 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/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1876847] Re: HP-Spectre 2019 Intel wireless driver is detected incorrectly.
The firmware load messages are not unusual. The driver will try to load a range of firmware versions, and often the "newest" version the driver looks for has not been released by Intel. As long as it finds supported firmware version (as indicated by the "loaded firmware version" message) there's nothing to worry about. I honestly don't know about the updates UI saying the device is not working. I just looked on my laptop and it says the same thing, even though I'm having no issues at all with my wireless. I'm not entirely sure which package is responsible for making that determination, but I've added ubuntu-drivers-common to the bug as a starting point. ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1876847 Title: HP-Spectre 2019 Intel wireless driver is detected incorrectly. Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Output of lsb_release -rd, Description: Ubuntu 20.04 LTS Release: 20.04 Issue: I have Intel AX-201 for wireless but when i do "lspci -k", the driver is detected as "Intel-9462". When i did "journalctl -k | grep iwlwifi", it shows that the wireless driver detected is "Intel AX-201". Output of lspci -k, 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 Subsystem: Intel Corporation Wireless-AC 9462 Kernel driver in use: iwlwifi Kernel modules: iwlwifi Output of journalctl -k | grep iwlwifi, May 04 23:20:12 kernel: iwlwifi :00:14.3: enabling device ( -> 0002) May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-50.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: Direct firmware load for iwlwifi-QuZ-a0-hr-b0-49.ucode failed with error -2 May 04 23:20:12 kernel: iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Found debug configuration: 0 May 04 23:20:12 kernel: iwlwifi :00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm May 04 23:20:12 kernel: iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 May 04 23:20:12 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:12 kernel: iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. May 04 23:20:12 kernel: iwlwifi :00:14.3: base HW address: 7c:b2:7d:d0:d5:95 May 04 23:20:12 kernel: iwlwifi :00:14.3 wlp0s20f3: renamed from wlan0 May 04 23:20:13 kernel: iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM May 04 23:20:13 kernel: iwlwifi :00:14.3: FW already configured (0) - re-configuring In the additional drivers module, it shows that module Intel-9462 no longer works. My bluetooth is also not detected and doesn't work. I came across this but no else responded yet. So decided to report a bug here. https://askubuntu.com/questions/1232224/intel-ax201-detected-as-ac9462-wifi-connectivity-problems Please let me know if any more information is required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srikar 1447 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Spectre x360 Convertible 15-df1xxx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=8d5d378c-648e-4355-8c1c-10cb298b2677 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.23
[Desktop-packages] [Bug 1877627] [NEW] /etc/default/im-config leaves temporary variables fixed in environment
Public bug reported: Ubuntu 18.04 im-config 0.34-1ubuntu1.3 You can reproduce the issue following these steps: - Open a X terminal - echo $d - Returns "GNOME" The source is this line in /etc/default/im-config: for d in 'Unity' 'MATE' 'GNOME'; do the temporary variable d gets fixed in the environment variables. ** Affects: im-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1877627 Title: /etc/default/im-config leaves temporary variables fixed in environment Status in im-config package in Ubuntu: New Bug description: Ubuntu 18.04 im-config 0.34-1ubuntu1.3 You can reproduce the issue following these steps: - Open a X terminal - echo $d - Returns "GNOME" The source is this line in /etc/default/im-config: for d in 'Unity' 'MATE' 'GNOME'; do the temporary variable d gets fixed in the environment variables. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1877627/+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 1877601] Re: /usr/share/alsa missing within snap
I’m not running any other snaps, which one would you recommend to test this? -- 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1877629] [NEW] An excessive number of AppArmor denials
Public bug reported: On advice given in another bug, I ran `journalctl | fgrep DEN`. This produced as much as a gigabyte of output which certainly sounds excessive for one week that it represents. I replaced numbers with placeholders so I could `uniq -c` it ( stands for N hex characters), the top offenders are below. Is something misconfigured? 1152937 audit[]: AVC apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 455154 audit[]: AVC apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 196028 audit[]: AVC apparmor="DENIED" operation="rename_src" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG" pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" fsuid=1000 ouid=1000 195406 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 195406 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 164056 kernel: audit: type=1400 audit(:): apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/Favicons-journal" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 130756 audit[]: AVC apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 111779 audit[]: AVC apparmor="DENIED" operation="rename_src" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOG" pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" fsuid=1000 ouid=1000 111480 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 111480 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1123/.config/chromium/Default/IndexedDB/https_docs.google.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 96203 kernel: audit: type=1400 audit(:): apparmor="DENIED" operation="truncate" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/History-journal" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 62594 audit[]: AVC apparmor="DENIED" operation="rename_src" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOG" pid= comm="ThreadPoolForeg" requested_mask="wd" denied_mask="wd" fsuid=1000 ouid=1000 62340 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 62340 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/IndexedDB/https_www.youtube.com_0.indexeddb.leveldb/LOCK" pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 49838 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 44399 audit[]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/home/roma/snap/chromium/1135/.config/chromium/Default/Cookies-journal" pid= comm="ThreadPoolForeg" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000 42368 audit[]: AVC apparmor="DENIED" operation="unlink" profile="snap.chromium.chromium" name= pid= comm="ThreadPoolForeg" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000 41786 audit[]: AVC apparmor="DENIED" operation="unlink"
[Desktop-packages] [Bug 1869561] Re: Libreoffice Help does not work
Sebastien - that works for me - I now get the local web-based help (I'd still prefer the old fashioned sort, but never mind!), With the new xcd it reports it is: Version: 6.4.3.2 Build ID: 1:6.4.4~rc1-0ubuntu0.20.04.1 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded Although the version numbers seemed to have got confused. I think I really am on 6.4.4 rc1. Reverting to the original xcd it reports the correct version. I was a little nervous about replacing the xcd (I have no idea what it does), so I'll revert to the original one for now. If there are some fairly simple changes I could make I'd be happy to try that. -- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1877279] Re: my wallpaper is changed after computer sleep
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+attachment/5368521/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877279] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1877279/+attachment/5368519/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877279] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1877279/+attachment/5368517/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877621] Re: Ubuntu 20 Super (search) don't work with second language
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1871913, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1871913 super key does not work with secondary keyboard layout -- 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/1877621 Title: Ubuntu 20 Super (search) don't work with second language Status in gnome-shell package in Ubuntu: New Bug description: I was use Ubuntu 18 before when i click super it go to search view doesn't matter what language i'm use in this case ... but now in Ubuntu 20.4 that work with first language and not work for second whatever what is these languages - i reset the keyboard shortcuts but nothing change ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 19:28:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877621/+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 1877279] Re: my wallpaper is changed after computer sleep
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+attachment/5368520/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877279] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1877279/+attachment/5368518/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877279] Re: my wallpaper is changed after computer sleep
apport information ** Tags added: apport-collected focal third-party-packages ** Description changed: - when my laptop goes in sleep then when I log in to the ubuntu my - wallpaper changes to a bad picture (the bad picture is the white and - black horizontal lines and I should change my wallpaper to get it right + when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-24 (14 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + NonfreeKernelModules: nvidia + Package: gnome-shell 3.36.1-5ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/usr/bin/zsh + ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 + RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 + Tags: focal third-party-packages + Uname: Linux 5.4.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1877279/+attachment/5368516/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1877601] Re: /usr/share/alsa missing within snap
Sure, I didn't imply that you should be using PA. Can you share examples of other snaps with working sound over ALSA ? 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1877621] [NEW] Ubuntu 20 Super (search) don't work with second language
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Public bug reported: I was use Ubuntu 18 before when i click super it go to search view doesn't matter what language i'm use in this case ... but now in Ubuntu 20.4 that work with first language and not work for second whatever what is these languages - i reset the keyboard shortcuts but nothing change ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 19:28:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877621 Title: Ubuntu 20 Super (search) don't work with second language Status in gnome-shell package in Ubuntu: New Bug description: I was use Ubuntu 18 before when i click super it go to search view doesn't matter what language i'm use in this case ... but now in Ubuntu 20.4 that work with first language and not work for second whatever what is these languages - i reset the keyboard shortcuts but nothing change ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 19:28:24 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877621/+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 1877597] Re: Does not see ~/.XCompose
Right, so this is working "as intended". Even though, as you point out, the line between what should be readable in a user's home directory and what shouldn't is a fine one. But that's not a chromium-specific issue. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => 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/1877597 Title: Does not see ~/.XCompose Status in chromium-browser package in Ubuntu: Invalid Bug description: Unless I manually edit ~/.chromium-browser.init to include “export XCOMPOSEFILE=” and take care to put a copy of XCompose at such a path, Chromium does not see the XCompose file and so can’t make use of user-defined Compose sequences. Chromium needs to be able to see ~/.XCompose, possibly other X11 files of similar nature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+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 1876352] Re: App Grid icons out of alignment when opening from overview
I've tried to see if I can find this bug in dash-to-dock master but if it is there it's like finding a needle in a haystack. Do you have any advice for how to track this down? I'm beginning to think that this bug somehow only exists in the ubuntu- dock branch, although I have no strong evidence to support that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1876352 Title: App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+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 1869561] Re: Libreoffice Help does not work
-- 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/1869561 Title: Libreoffice Help does not work Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: Confirmed Bug description: In the latest PPA release of Libreoffice, the Help does not work. IN version 6.3.5.2 it is OK. I the version below it returns an error. Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu0.19.10.3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded The Error is: Object not accessible. The object cannot be accessed due to insufficient user rights. The Help used to open the help in a browser window. This latest version seems to try to open the old type of local help (rather than using a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869561/+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 1870640] Re: Does not register as x-www-browser alternative
Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 from focal-proposed. I verified update-alternatives couldn't be used to set the default value of [x-www-browser|gnome-www-browser] to /usr/bin/chromium-browser in a fully up-to-date focal VM, then I enabled focal-proposed for universe, ran "apt update" and "apt dist-upgrade" to install the updated chromium- browser package, and I verified that update-alternatives now accepted to set the default x-www-browser|gnome-www-browser. I also verified that running x-www-browser|gnome-www-browser did launch chromium-browser, as expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1870640 Title: Does not register as x-www-browser alternative Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: In Progress Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Low. When installing chromium-browser in eoan/focal (which is a transitional package that installs the chromium snap), update- alternatives cannot be used to set it as x-www-browser or gnome-www- browser. This is a regression compared to the version of chromium- browser in bionic. [Test case] # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting [Regression potential] This is fixing a regression by adding back a code snippet that was in the package in bionic and previous releases. If the snippet has incorrect syntax, it could possibly prevent installation of the package. If the package installs fine, it's unlikely that anything could have regressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1815289] Re: Please add Provides: gnome-www-browser
Confirmed fixed with chromium-browser 81.0.4044.129-0ubuntu0.20.04.1 from focal-proposed. I verified chromium-browser didn't appear in the list of reverse provides for x-www-browser and gnome-www-browser in a fully up-to-date focal VM, then I enabled focal-proposed for universe, ran "apt update", and verified that it did appear for both. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1815289 Title: Please add Provides: gnome-www-browser Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: In Progress Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Low. Some Debian packages depend on gnome-www-browser, and chromium- browser should be marked as providing it (similarly, it should provide x-www-browser). For instance, cinnamon-desktop-environment depends on gnome-www- browser and it doesn't have the chromium-browser name in the alternates (it has Debian's chromium name instead). [Test case] The output of `apt-cache showpkg gnome-www-browser` after the "Reverse Provides:" line should contain a chromium-browser entry. Similarly for `apt-cache showpkg x-www-browser`. [Regression potential] This is adding a couple of "provides" entries to the control file. Regressions could happen if other packages depending on or recommending gnome-www-browser (or x-www-browser) were implicitly relying on the fact that chromium-browser wasn't a candidate, but that sounds unlikely, and in any case something that should be fixed in thoses packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1815289/+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 1877567] Re: Automatic Login
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877567 Title: Automatic Login Status in xorg package in Ubuntu: New Bug description: Problem 1. Switched to automatic login option during the fresh install 2. On a start up Login screen is still shown. 3. Typing correct user name and password does not start the system. 4. End up stuck in login loop Solution 1. Restart system 2. Selected Ubuntu Recovery mode 3. Select normal boot 4. System starts 5. Go to to User Settings and disable automatic login 6. Reboot 7. System starts with login screen 8. Type name and password. 9. system starts ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 08:04:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401b] InstallationDate: Installed on 2020-05-04 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: A320M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877567/+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 1877567] [NEW] Automatic Login
You have been subscribed to a public bug: Problem 1. Switched to automatic login option during the fresh install 2. On a start up Login screen is still shown. 3. Typing correct user name and password does not start the system. 4. End up stuck in login loop Solution 1. Restart system 2. Selected Ubuntu Recovery mode 3. Select normal boot 4. System starts 5. Go to to User Settings and disable automatic login 6. Reboot 7. System starts with login screen 8. Type name and password. 9. system starts ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 08:04:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401b] InstallationDate: Installed on 2020-05-04 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: A320M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Automatic Login https://bugs.launchpad.net/bugs/1877567 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1877597] Re: Does not see ~/.XCompose
Ah, I think the true source of the problem was that my .XCompose was a symlink into a subdirectory of .config, so that’s what was actually denied. This is at least understandable, even if it still makes no sense (~/.config/my-dotfiles-git-repository is off limits but ~/Documents /financial-report-top-secret.pdf is not). Sorry for the misleading bug description. -- 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/1877597 Title: Does not see ~/.XCompose Status in chromium-browser package in Ubuntu: Incomplete Bug description: Unless I manually edit ~/.chromium-browser.init to include “export XCOMPOSEFILE=” and take care to put a copy of XCompose at such a path, Chromium does not see the XCompose file and so can’t make use of user-defined Compose sequences. Chromium needs to be able to see ~/.XCompose, possibly other X11 files of similar nature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+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 1870640] Re: Does not register as x-www-browser alternative
@Daniel: that's correct, the fix is part of the transitional package. It's transitional in a slightly different acceptance of the term though, because it installs a snap, not another deb package. And snaps don't have any mechanism to run update-alternatives as part of their install process. So this is the best we can do with what we have. -- 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/1870640 Title: Does not register as x-www-browser alternative Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: In Progress Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Low. When installing chromium-browser in eoan/focal (which is a transitional package that installs the chromium snap), update- alternatives cannot be used to set it as x-www-browser or gnome-www- browser. This is a regression compared to the version of chromium- browser in bionic. [Test case] # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting [Regression potential] This is fixing a regression by adding back a code snippet that was in the package in bionic and previous releases. If the snippet has incorrect syntax, it could possibly prevent installation of the package. If the package installs fine, it's unlikely that anything could have regressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1877614] [NEW] Merge gnome-software 3.36.0-3 (main) from Debian unstable (main)
Public bug reported: Please merge gnome-software 3.36.0-3 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. It fixes LP: #1864307. Explanation of the Ubuntu delta: * debian/patches/0026-Add-a-dialog-to-log-into-the-snap-store.patch: - Fix FTBFS on riscv64 where snap support is disabled * New upstream release * debian/control: - Add build-depends on libostree-dev * d/p/0029-Fix-CSS-colors-to-work-correctly-with-Yaru-Adwaita.patch: - Use theme exported colors (LP: #1862056) * d/p/0001-GsApp-Add-a-new-do-not-auto-update-quirk.patch: * d/p/0002-fwupd-Use-new-GS_APP_QUIRK_DO_NOT_AUTO_UPDATE.patch: * d/p/0003-snap-Stop-snaps-from-being-automatically-updated.patch: - Stop snaps being automatically updated (LP: #1862158) * New upstream release * Rebased on Debian, remaining Ubuntu changes: - Add an "ubuntu-software" package with some branding for Ubuntu. - debian/patches/*.patch: - Various Ubuntu changes from ubuntu-master branch - see patch headers for more information. * debian/patches/0030-snap-Use-new-banner-media.patch: - Use new banner format (LP: #1844799) * debian/patches/0031-Use-plugin-API-to-launch-apps-from-install-notificat.patch: * debian/patches/0032-snap-Allow-snaps-to-be-shown-by-AppStream-ID.patch: - Fix snaps not launchding from the after install notification (LP: #1816396) * Rebuild for new gnome-desktop soname version * debian/control: - Set git branch for vcs * debian/patches/0014-Add-a-basic-permissions-system.patch: - Fix switches being stretched - Use new connections API * debian/patches/0001-snap-Update-Snap-store-category-mapping.patch: - Update snap store categories (LP: #1836826) * debian/patches/0014-Add-a-basic-permissions-system.patch: - Fix interface connections not showing correct state (LP: #1806697) * No change rebuild to handle ABI break in flatpak 1.4.0 which was reverted in 1.4.1 * debian/patches/0016-snap-Use-default-icon-if-none-provided.patch: - Update default snap icon (LP: #1818920) * debian/patches/0014-Add-a-basic-permissions-system.patch: * debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch - Merge u2f changes into original patch * debian/patches/0027-shell-Don-t-progate-CTRL-F-key-pressed-event.patch: - Fix Ctrl-F not opening search bar (LP: #1735071) * debian/patches/0026-odrs-Only-show-reviews-from-the-same-distribution.patch: - Show only Ubuntu reviews (LP: #1825064) * debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch - Allow connections on the u2f-devices interface (LP: #1738164) (the patch has been SRUed to bionic but was missing from Disco) * debian/patches/0025-snap-Use-new-media-API.patch: - Use new snapd media API (LP: #1799614) * Sync with Debian. Remaining changes: + debian/patches/*.patch: Various Ubuntu changes from ubuntu-master branch - see patch headers for more information. + Add an "ubuntu-software" package with some branding for Ubuntu. Changelog entries since current groovy version 3.36.0-0ubuntu3: gnome-software (3.36.0-3) unstable; urgency=medium * Fix missing icons in the store, patch from upstream. (LP: #1864307) Thanks to Matthias Klumpp * Do not fail to load the appstream plugin if any of the metadata directories doesn't exist (Closes: #958915) -- Laurent Bigonville Mon, 27 Apr 2020 15:13:57 +0200 gnome-software (3.36.0-2) unstable; urgency=medium * Add fix-appstream-featured-data.patch - This restores a regression fix that was accidentally reverted in the 3.36.0 release. The issue caused invalid AppStream data to be added to the global metadata pool, resulting in a confusing warning to people using APT or an AppStream cache (Closes: #932747) -- Matthias Klumpp Thu, 02 Apr 2020 18:16:58 +0200 gnome-software (3.36.0-1) unstable; urgency=medium * New upstream release -- Laurent Bigonville Wed, 11 Mar 2020 14:35:17 +0100 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: focal groovy ** Description changed: Please merge gnome-software 3.36.0-3 (main) from Debian unstable (main) - It fixes LP: #1864307. + Sorry, I can't work on this merge myself. It fixes LP: #1864307. Explanation of the Ubuntu delta: - * debian/patches/0026-Add-a-dialog-to-log-into-the-snap-store.patch: - - Fix FTBFS on riscv64 where snap support is disabled - * New upstream release - * debian/control: - - Add build-depends on libostree-dev - * d/p/0029-Fix-CSS-colors-to-work-correctly-with-Yaru-Adwaita.patch: - - Use theme exported colors (LP: #1862056) - * d/p/0001-GsApp-Add-a-new-do-not-auto-update-quirk.patch: - * d/p/0002-fwupd-Use-new-GS_APP_QUIRK_DO_NOT_AUTO_UPDATE.patch: - * d/p/0003-snap-Stop-snaps-from-being-automatically-updated.patch: - - Stop snaps being automatically updated (LP: #1862158) - * New
[Desktop-packages] [Bug 1877135] Re: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found]
The problem is undefined symbol: usbmuxd_connect (/usr/local/lib/libimobiledevice.so.6) Which is a local 'make install type' installation taking over the Ubuntu version, if you remove that copy things should work better (check for other outdated libraries in the same directory) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1877135 Title: Failed to start Virtual filesystem service - Apple File Conduit monitor [libusbmuxd.so.4 not found] Status in gvfs package in Ubuntu: Incomplete Bug description: After upgrading to Focal, /usr/libexec/gvfs-afc-volume-monitor fails with the message /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory 1) lsb_release -rd: Description: Ubuntu 20.04 LTS Release: 20.04 2)apt-cache policy gvfs gvfs: Installed: 1.44.1-1ubuntu1 Candidate: 1.44.1-1ubuntu1 Version table: *** 1.44.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 4) What happens: many applications (nautilus, gedit, etc) take ~30 sec to open. When starting those via the command line, after after those 30 secs the app opens with the following printed to the terminal: "Error creating proxy: Error calling StartServiceByName for org.gtk.vfs.AfcVolumeMonitor: Timeout was reached (g-io-error-quark, 24)" 3) What you expected to happen: applications to open without delay = Additional info: After calling 'journalctl -b', several instances like dbus-daemon[2031]: [session uid=1000 pid=2031] Activating via systemd: service name='org.gtk.vfs.AfcVolumeMonitor' unit='gvfs-afc-volume-monitor.service' requested by ':1.25' (uid=1000 pid=2135 comm="/usr/bin/gnome-shell " label="unconfined") systemd[1964]: Starting Virtual filesystem service - Apple File Conduit monitor... gvfs-afc-volume-monitor[2279]: /usr/libexec/gvfs-afc-volume-monitor: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory systemd[1964]: gvfs-afc-volume-monitor.service: Main process exited, code=exited, status=127/n/a systemd[1964]: gvfs-afc-volume-monitor.service: Failed with result 'exit-code'. systemd[1964]: Failed to start Virtual filesystem service - Apple File Conduit monitor. Also upowerd is affected: /usr/lib/upower/upowerd: error while loading shared libraries: libusbmuxd.so.4: cannot open shared object file: No such file or directory upower.service: Main process exited, code=exited, status=127/n/a upower.service: Failed with result 'exit-code'. Failed to start Daemon for power management. The package libusbmuxd6 is installed (and /usr/lib/x86_64-linux- gnu/libusbmuxd.so.6 is present), but when trying "sudo apt install libusbmuxd4", I get the error "E: Unable to locate package libusbmuxd4". It would appear to me that some dependencies *somewhere* are not properly updated (to libusbmuxd6 from libusbmuxd4). Unfortunately, the huge timeout significantly affects usability of the computer, as one has to wait a lot to perform many tasks (opening nautilus, gedit); one has to wait also before login screen appears after a reboot. Something that appears to be related: https://forum.manjaro.org/t/upower-fails-to-start-becuase-upowerd-is-not-running/117291 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gvfs-backends 1.44.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed May 6 13:45:53 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-18 (1875 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: gvfs UpgradeStatus: Upgraded to focal on 2020-04-24 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1877135/+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 1874727] Re: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling
Good point Sébastien. I've updated the title. @Mike or @Antoine: would you mind filing an upstream bug at https://crbug.com and sharing the link to it here? ** Summary changed: - [snap] fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling + fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling -- 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/1874727 Title: fullscreen uses only 1/4 of screen on secondary monitor with HiDPI scaling Status in chromium-browser package in Ubuntu: Confirmed Bug description: lsb_release -rd -> Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy chromium -> chromium: Installiert: (keine) Installationskandidat: (keine) Versionstabelle: hardware: 2x monitors: 4K scaling: 200% Is: In chromium the fullscreen-mode uses only 1/4 of the screen on the 2nd monitor. Should be: In chromium the fullscreen-mode uses 1/1 of the screen on the 2nd monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874727/+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 1876065] Re: After unplug headphones and plug them again no sound can be heard
** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => High -- 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/1876065 Title: After unplug headphones and plug them again no sound can be heard Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Bug description: * Impact Sound isn't automatically redirected to headphones when those are connected to a jack interface * Test case Disconnect the headsets Start your webbrowser/music player/video player and play some sound Connect the headsets to the jack interface -> the sound should be directly redirected to the plugged headsets * Regression potential Check that audio routing when connecting/disconnecting devices to the hack entry is working correctly After startup with headset plugged in they play sound nicely - no issue. When they are unplugged, the sound is switched to the speaker (laptop) - all good. However, when I plug the headset back there is no sound. I see the app on pavucontrol, the volume is fine - everything looks fine except there is no sound. I dumped output of "pactl list" command on startup (headset plugged), after unplugging the headset, and when it is plugged back. From the comparison of these outputs, it looks like the source has got muted after the headset is plugged. Source #1 State: RUNNING Name: alsa_input.pci-_00_1f.3.analog-stereo Description: Built-in Audio Analog Stereo Driver: module-alsa-card.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 7 Mute: yes Attached three outputs: headset-in.txt - after startup with headset plugged - all fine. headset-out.txt - after unplugged headset - sound through the speaker - all fine. headset-back.txt - after plugged headset back - no sound. Any help greatly appreciated. Regards, Roman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876065/+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 1873060] Re: Large white space between the sections "recent versions" and "categories" in the gnome software application.
** Changed in: gnome-software (Ubuntu) Status: Incomplete => Confirmed -- 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/1873060 Title: Large white space between the sections "recent versions" and "categories" in the gnome software application. Status in gnome-software package in Ubuntu: Confirmed Bug description: After uninstalling the snap support, I installed the classic gnome software center. However, a large white space is visible in the middle of the application, between the sections "recent versions" and "categories". Commands as root: - apt-get install gnome-software - apt-get autoremove --purge snapd gnome-software-plugin-snap ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 21:01:40 2020 InstallationDate: Installed on 2020-04-15 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snapN/A ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/1873060/+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 1873658] Re: Deb Files are not associated with an application that manages packages
Hello Chris, I have tested the latest desktop-file-utils (0.24-1ubuntu3) package from focal-proposed and can confirm that the issue is now fixed - Software installation is now the default action for deb packages opened from Nautilus. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1873658 Title: Deb Files are not associated with an application that manages packages Status in desktop-file-utils package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Invalid Status in desktop-file-utils source package in Focal: Fix Committed Status in gdebi source package in Focal: Invalid Bug description: [Impact] * When a deb is downloaded the default handler is not capable of installing on 20.04. [Test Case] We should perform this test on Ubuntu 20.04 as well as some flavors to ensure we do not regress. * Download any deb in firefox, double click on the downloaded file - On Ubuntu this should open "Ubuntu Software" - On flavors it should open whatever their default app for handling debs is [Regression Potential] * For Ubuntu, very low, rarely would a user expect to open a deb with file-roller * Other flavors of ubuntu are overriding this default and should not be affected. We do need to test this on other flavors to ensure their defaults are still honored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1877601] Re: /usr/share/alsa missing within snap
I am not. This is certainly not the place to discuss advantages and drawbacks of pulseaudio, of which it has both, but seeing as both Chromium and snapd itself support ALSA, the chromium snap should also support it. -- 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1877597] Re: Does not see ~/.XCompose
Could you please examine the journal (`journalctl | grep DEN`) for denials related to ~/.XCompose ? -- 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/1877597 Title: Does not see ~/.XCompose Status in chromium-browser package in Ubuntu: Incomplete Bug description: Unless I manually edit ~/.chromium-browser.init to include “export XCOMPOSEFILE=” and take care to put a copy of XCompose at such a path, Chromium does not see the XCompose file and so can’t make use of user-defined Compose sequences. Chromium needs to be able to see ~/.XCompose, possibly other X11 files of similar nature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+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 1877597] Re: Does not see ~/.XCompose
Note: the x11 interface does #include , which allows
read access to @{HOME}/.XCompose. So this *should* work?
** 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/1877597
Title:
Does not see ~/.XCompose
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
Unless I manually edit ~/.chromium-browser.init to include “export
XCOMPOSEFILE=” and take
care to put a copy of XCompose at such a path, Chromium does not see
the XCompose file and so can’t make use of user-defined Compose
sequences.
Chromium needs to be able to see ~/.XCompose, possibly other X11 files
of similar nature.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/issues #909 https://gitlab.freedesktop.org/xorg/xserver/issues/909 -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: New Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1853357/+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 1877467] Re: Input device does not switch back to internal microphone when analog headset unplugged
Hi Sebastien. Yes, that fixes the problem. Thank you for the fast response! Brian On Fri, May 8, 2020 at 4:05 AM Sebastien Bacher wrote: > Thank you for your bug report, could you check if the stable update > https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.1 > fixes the issue for you? > > ** No longer affects: gnome-control-center (Ubuntu) > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877467 > > Title: > Input device does not switch back to internal microphone when analog > headset unplugged > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > 1. Open Settings - Sound > 2. Confirm Output Device = "Speakers - Built-in Audio" and Input Device > = Internal Microphone - Built-in Audio" > 3. Plug analog headset into jack > 4. When prompted to select audio device, select "Headset" > 5. Confirm Output Device = "Headphones - Built in Audio" and Input > Device = "Headset Microphone - Built-in Audio" > 6. Unplug analog headset from jack > > PROBLEM OCCURS HERE: > > Output Device goes back to "Speakers - Built-in Audio", but Input > Device remains at "Headset Microphone - Built-in Audio". It should go > back to the original setting of "Internal Microphone - Built-in Audio" > > WORKAROUND: > > Manually change Input Device back to "Internal Microphone - Built-in > Audio" > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-control-center 1:3.36.1-1ubuntu5 > ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 > Uname: Linux 5.4.0-29-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Thu May 7 18:01:19 2020 > ExecutablePath: /usr/bin/gnome-control-center > InstallationDate: Installed on 2019-12-26 (133 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > ProcEnviron: >PATH=(custom, user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-control-center > UpgradeStatus: Upgraded to focal on 2020-04-24 (13 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877467/+subscriptions > -- Brian Pursley bpurs...@cinlogic.com -- 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/1877467 Title: Input device does not switch back to internal microphone when analog headset unplugged Status in pulseaudio package in Ubuntu: Incomplete Bug description: 1. Open Settings - Sound 2. Confirm Output Device = "Speakers - Built-in Audio" and Input Device = Internal Microphone - Built-in Audio" 3. Plug analog headset into jack 4. When prompted to select audio device, select "Headset" 5. Confirm Output Device = "Headphones - Built in Audio" and Input Device = "Headset Microphone - Built-in Audio" 6. Unplug analog headset from jack PROBLEM OCCURS HERE: Output Device goes back to "Speakers - Built-in Audio", but Input Device remains at "Headset Microphone - Built-in Audio". It should go back to the original setting of "Internal Microphone - Built-in Audio" WORKAROUND: Manually change Input Device back to "Internal Microphone - Built-in Audio" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 18:01:19 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-12-26 (133 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-24 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877467/+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 1776447] Re: Xorg's Indirect GLX broken from upstream regression
Fixed upstream in xorg-server 1.20.8 --- xorg-server (2:1.20.8-2ubuntu2) focal; urgency=medium * randr-auto-bind-of-gpu-is-a-config-change.diff: Backport GPU hotplug RandR fix. (LP: #1862753) xorg-server (2:1.20.8-2ubuntu1) focal; urgency=medium * Merge from Debian. * modesetting-Disable-atomic-support-by-default.patch: Dropped, upstream. xorg-server (2:1.20.8-2) unstable; urgency=medium * rules: Exclude udeb/ from indep dh_missing. (Closes: #955399) xorg-server (2:1.20.8-1) unstable; urgency=medium * New upstream release. * patches: Dropped patches applied upstream: - fix-modesetting-build.diff - add-EGL_QUERY_DRIVER-check.diff - fix-rotate-crash.diff * control: Use debhelper-compat, bump to 12. * rules: Migrate to dh_missing. ** Changed in: xorg-server (Ubuntu) Status: Triaged => Fix Released ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1776447 Title: Xorg's Indirect GLX broken from upstream regression Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: New Bug description: [Impact] * IGLX is a way for an opengl application sending the 3D drawing GLX commands to the Xorg server for rendering instead of using the DRI infrastructure it is commonplace for High Performance Compute and Scientific institutions to use this feature of the Xorg server. (ref: https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX- Potential-Bye-Bye) * The feature is completely broken, currently, and any attempt to use it will cause the Xorg server to crash. This feature has been broken since a commit upstream in 2016. * The attached patch is from the revert commit entered into the upstream repository on 28 Jan 2020 following a git bisect of the bug discovering the offending commit. [Test Case] * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the following contents: ``` Section "ServerFlags" Option "IndirectGLX" "on" EndSection ``` * Log out of your Xorg session * Switch to a VT (Ctrl+Alt+F2) and login * Run `sudo systemctl restart gdm` to restart Xorg * Login to the graphical session * If you do not have mesa-utils installed, then install it with the terminal command `sudo apt install mesa-utils` * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears` * If the fix is successful then glxgears should start and remain active without the Xorg server or glxgears crashing/segfaulting [Regression Potential] * This change is within DRI-related functionality and so might break all 3D accelerated applications. * There is a potential that the change is insufficient to fix the IGLX feature and so attempts to use it may still have undesirable and undefined results. * Upstream has run the patch through their CI system, which passed with no errors. This does not necessarily mean the patch will achieve the desired results, but at least indicates that the code does compile cleanly and can start an Xvfb headless instance. [Other Info] * This bug affects Ubuntu releases all the way back to, and including, Bionic 18.04. Original Bug Report Follows There's already an upstream bug report here: https://bugs.freedesktop.org/show_bug.cgi?id=99555 Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1 I get immediate crashes e.g. with glxgear: steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. X Error of failed request: 255 Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 1 (X_GLXRender) Serial number of failed request: 42 Current serial number in output stream: 936 I am trying to run what is effectively a traditional X Terminal, but as the hardware I am using has a 3D accelerated chipset it seems sensible to try to use it.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Jun 12 10:09:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes
[Desktop-packages] [Bug 1877601] Re: /usr/share/alsa missing within snap
This is the first report of sound not working in the chromium snap. Are you not using pulseaudio? ** 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: Incomplete Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.
It should indeed be done like this:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
from gi.repository import GObject
mystore = Gtk.ListStore(GObject.TYPE_UINT64)
mystore.insert_with_valuesv(-1, [1], [GObject.Value(GObject.TYPE_UINT64,
1330400507426)])
###
I was completely unaware of that possibility because the source of my
GTK knowlege is
https://lazka.github.io/pgi-
docs/#Gtk-3.0/classes/ListStore.html#Gtk.ListStore.set_column_types
When checking out the available types one ends up here:
https://lazka.github.io/pgi-
docs/#GObject-2.0/classes/GType.html#GObject.GType
Which does not ring any bell ...
So I did it like in
https://python-gtk-3-tutorial.readthedocs.io/en/latest/treeview.html
#the-model
where the Python types are used.
###
With the knowlege I gained through this FR it was possible to find this:
GObject Built-in Type Constants
The Built-in Type constants specify the pre-defined types used by gobject.
https://developer.gnome.org/pygobject/stable/gobject-constants.html
#gobject-type-constants
which is quite useful.
###
Thanks!
On 11.03.20 17:56, Christoph Reiter wrote:
> import gi
> gi.require_version('Gtk', '3.0')
> from gi.repository import Gtk
>
> This works in Python 2:
>
> mystore = Gtk.ListStore(long)
> mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
>
> This does not work in Python 3:
>
> mystore = Gtk.ListStore(int)
> mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1866625
Title:
OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
Integers.
Status in pygobject package in Ubuntu:
New
Bug description:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])
OverflowError: Item 0: out of range for int property
lsb_release -rd
Description: Ubuntu 18.04.4 LTS
Release: 18.04
apt-cache policy python3-gi
python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
*** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
python3 -V
Python 3.6.9
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1866625/+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 1868117] Re: [snap] Adapt chromium user agent to avoid "not supported browser"
Corresponding discussion on snapcraft's forums: https://forum.snapcraft.io/t/chromium-stop-using-custom-user-agent-work- towards-generic-one/17225 -- 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/1868117 Title: [snap] Adapt chromium user agent to avoid "not supported browser" Status in chromium-browser package in Ubuntu: Confirmed Bug description: Currently some websites like netflix.com and web.whatsapp.com does not recognize chromium Ubuntu as chrome because of the different user agent. We need to find a way like vivaldi to avoid such problems for casual users. Current snap chromium UA : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) snap Chromium/80.0.3987.132 Chrome/80.0.3987.132 Safari/537.36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1868117/+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 1877604] [NEW] Keyboard shortcuts Ctrl+C, Ctrl+V, Ctrl+X does not nothing on Desktop area
Public bug reported: Steps to test: 1. Have Ubuntu 20.04 LTS installed with default GNOME Shell 2. Have some files and/or folders on the Desktop 3. Select some object on Desktop, then press Ctrl+C / Ctrl+V / Ctrl+X 4. Open Nautilus and press corresponding Ctrl+C / Ctrl+V / Ctrl+X here Expected results: * user is able to use Ctrl+C / Ctrl+V / Ctrl+X to operate with objects on Desktop Actual results: * user in unable to use Ctrl+C / Ctrl+V / Ctrl+X to operate with objects on Desktop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:52:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877604 Title: Keyboard shortcuts Ctrl+C, Ctrl+V, Ctrl+X does not nothing on Desktop area Status in gnome-shell package in Ubuntu: New Bug description: Steps to test: 1. Have Ubuntu 20.04 LTS installed with default GNOME Shell 2. Have some files and/or folders on the Desktop 3. Select some object on Desktop, then press Ctrl+C / Ctrl+V / Ctrl+X 4. Open Nautilus and press corresponding Ctrl+C / Ctrl+V / Ctrl+X here Expected results: * user is able to use Ctrl+C / Ctrl+V / Ctrl+X to operate with objects on Desktop Actual results: * user in unable to use Ctrl+C / Ctrl+V / Ctrl+X to operate with objects on Desktop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:52:20 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-24 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877604/+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 1877601] [NEW] /usr/share/alsa missing within snap
Public bug reported: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1877601 Title: /usr/share/alsa missing within snap Status in chromium-browser package in Ubuntu: New Bug description: $ ls /snap/chromium/current/usr/share/alsa alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf sndo-mixer.alisp topology ucm $ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa ls: cannot access '/usr/share/alsa': No such file or directory For this reason there’s no sound. How to make sure that /usr/share/alsa which is present in the snap does not somehow go missing when the snap runs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877601/+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 1877597] [NEW] Does not see ~/.XCompose
Public bug reported: Unless I manually edit ~/.chromium-browser.init to include “export XCOMPOSEFILE=” and take care to put a copy of XCompose at such a path, Chromium does not see the XCompose file and so can’t make use of user-defined Compose sequences. Chromium needs to be able to see ~/.XCompose, possibly other X11 files of similar nature. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1877597 Title: Does not see ~/.XCompose Status in chromium-browser package in Ubuntu: New Bug description: Unless I manually edit ~/.chromium-browser.init to include “export XCOMPOSEFILE=” and take care to put a copy of XCompose at such a path, Chromium does not see the XCompose file and so can’t make use of user-defined Compose sequences. Chromium needs to be able to see ~/.XCompose, possibly other X11 files of similar nature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877597/+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 1864901] Re: [snap] suggestion: alert users when the snap has been refreshed while running
@Ebuzer: Downloads are already stored by default outside of the versioned directory, in the user's XDG downloads directory (typically $HOME/Downloads). The rationale for versioning the profile directory is that the storage format isn't backwards compatible, so downgrading a snap to a previous revision would potentially render a profile unusable. @Roman: this is indeed something that, longer-term, should be addressed in snapd itself. This is merely a stop-gap measure to mitigate the problem until this happens. Note that ubuntu-bug hanging sounds unrelated to this particular issue. Can you elaborate on what you're trying to do, and how it hangs? -- 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/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Fix Released Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+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
