[Desktop-packages] [Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #732 https://gitlab.gnome.org/GNOME/gvfs/-/issues/732 ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/-/issues/732 Importance: Unknown Status: Unknown ** Summary changed: - OneDrive integration causes sigfault after entering My Files + Unable to browse My Files using OneDrive integration ** Information type changed from Public to Private -- 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/2064147 Title: Unable to browse My Files using OneDrive integration Status in gvfs: Unknown Status in gvfs package in Ubuntu: New Bug description: The new OneDrive integration is causing a sigfault when opening the My Files folder. Release information: No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 Apt Cache: gvfs: Installed: 1.54.0-1ubuntu2 Candidate: 1.54.0-1ubuntu2 Version table: *** 1.54.0-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status Expected result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus displays files in OneDrive Actual result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus shows "This location could not be displayed. Sorry, could not display all the contents of "My Files": The connection is closed" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gvfs 1.54.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 18:03:59 2024 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/2064147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064147] [NEW] Unable to browse My Files using OneDrive integration
Private bug reported: The new OneDrive integration is causing a sigfault when opening the My Files folder. Release information: No LSB modules are available. Description:Ubuntu 24.04 LTS Release:24.04 Apt Cache: gvfs: Installed: 1.54.0-1ubuntu2 Candidate: 1.54.0-1ubuntu2 Version table: *** 1.54.0-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status Expected result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus displays files in OneDrive Actual result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus shows "This location could not be displayed. Sorry, could not display all the contents of "My Files": The connection is closed" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gvfs 1.54.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 18:03:59 2024 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs Importance: Unknown Status: Unknown ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screencast of fault" https://bugs.launchpad.net/bugs/2064147/+attachment/5772559/+files/Screencast%20from%202024-04-29%2018-09-30.webm -- 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/2064147 Title: Unable to browse My Files using OneDrive integration Status in gvfs: Unknown Status in gvfs package in Ubuntu: New Bug description: The new OneDrive integration is causing a sigfault when opening the My Files folder. Release information: No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 Apt Cache: gvfs: Installed: 1.54.0-1ubuntu2 Candidate: 1.54.0-1ubuntu2 Version table: *** 1.54.0-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status Expected result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus displays files in OneDrive Actual result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus shows "This location could not be displayed. Sorry, could not display all the contents of "My Files": The connection is closed" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gvfs 1.54.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 18:03:59 2024 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/2064147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2064147] Re: OneDrive integration causes sigfault after entering My Files
Captured gvfsd debug log of entering My Files ** Attachment added: "gvfs debug log" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/2064147/+attachment/5772565/+files/gvfsd.log -- 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/2064147 Title: Unable to browse My Files using OneDrive integration Status in gvfs: Unknown Status in gvfs package in Ubuntu: New Bug description: The new OneDrive integration is causing a sigfault when opening the My Files folder. Release information: No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 Apt Cache: gvfs: Installed: 1.54.0-1ubuntu2 Candidate: 1.54.0-1ubuntu2 Version table: *** 1.54.0-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status Expected result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus displays files in OneDrive Actual result: 1. Sign in to Microsoft 365 using personal account 2. Open Nautilus 3. Mount OneDrive storage 4. Enter My Files 5. Nautilus shows "This location could not be displayed. Sorry, could not display all the contents of "My Files": The connection is closed" ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gvfs 1.54.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 18:03:59 2024 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/2064147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2018425] Re: apt install ubuntu-desktop takes forever
Hi, I’ve run into this issue many times and today tracked down the cause to this open bug: https://bugs.launchpad.net/netplan/+bug/1999178 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2018425 Title: apt install ubuntu-desktop takes forever Status in subiquity: Invalid Status in ubuntu-meta package in Ubuntu: New Bug description: Install server 23.04 to take advantage of flexible disk partitioning/raid. While installing desktop over the installed server (apt install ubuntu-desktop) it proceeds normally about 40% of the way but after that it slows down tremendously, hanging for minutes in between packages. It eventually (after several hours) completes without error. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 3 11:41:00 2023 InstallationDate: Installed on 2023-04-29 (3 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2018425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11
Daniel (@vanvugt) Thank you very much for your hard work, out-of-band patch (the ppa!), and speed addressing this extremely subtle, yet annoying bug... much appreciated! -- 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/2059847 Title: Input lag or freezes on Nvidia desktops with X11 Status in Mutter: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Jammy: Triaged Status in mutter source package in Mantic: Triaged Status in mutter source package in Noble: In Progress Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Verify that input never froze for any perceptible period of time. 4. Run: journalctl -b0 | grep MetaSyncRing 5. Verify the above command does NOT show messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since that's the code being modified. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2058307] [NEW] package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: issue arose while installing first updates after install of ubuntu 20.04 operating system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjurt-java 1:6.4.7-0ubuntu0.20.04.9 ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 19 09:52:18 2024 DuplicateSignature: package:libjurt-java:1:6.4.7-0ubuntu0.20.04.9 Setting up uno-libs-private (1:6.4.7-0ubuntu0.20.04.9) ... dpkg: error processing package libjurt-java (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libreoffice Title: package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal 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/2058307 Title: package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: issue arose while installing first updates after install of ubuntu 20.04 operating system ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjurt-java 1:6.4.7-0ubuntu0.20.04.9 ProcVersionSignature: Ubuntu 5.15.0-101.111~20.04.1-generic 5.15.143 Uname: Linux 5.15.0-101-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 19 09:52:18 2024 DuplicateSignature: package:libjurt-java:1:6.4.7-0ubuntu0.20.04.9 Setting up uno-libs-private (1:6.4.7-0ubuntu0.20.04.9) ... dpkg: error processing package libjurt-java (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-18 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libreoffice Title: package libjurt-java 1:6.4.7-0ubuntu0.20.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2058307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049321] Re: xcalc needs a font
Installing x11fonts-100dpi fixed this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/2049321 Title: xcalc needs a font Status in x11-apps package in Ubuntu: New Bug description: When I launch xcalc, some of the symbols on the buttons are wrong (e.g. no divide symbol) and I get 'Warning: Cannot convert string "-adobe-symbol-*-*-*-*-*-120-*-*-*-*-*-*" to type FontStruct'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-apps 7.7+8build2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 16:54:39 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev d4) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2022-05-27 (597 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=d735b1e5-edce-40f0-af9c-c7a03597914c ro quiet splash vt.handoff=7 SourcePackage: x11-apps UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 03WC5R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn03WC5R:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-apps/+bug/2049321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2049321] [NEW] xcalc needs a font
Public bug reported: When I launch xcalc, some of the symbols on the buttons are wrong (e.g. no divide symbol) and I get 'Warning: Cannot convert string "-adobe- symbol-*-*-*-*-*-120-*-*-*-*-*-*" to type FontStruct'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-apps 7.7+8build2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 16:54:39 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev d4) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2022-05-27 (597 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=d735b1e5-edce-40f0-af9c-c7a03597914c ro quiet splash vt.handoff=7 SourcePackage: x11-apps UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 03WC5R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn03WC5R:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: x11-apps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-apps in Ubuntu. https://bugs.launchpad.net/bugs/2049321 Title: xcalc needs a font Status in x11-apps package in Ubuntu: New Bug description: When I launch xcalc, some of the symbols on the buttons are wrong (e.g. no divide symbol) and I get 'Warning: Cannot convert string "-adobe-symbol-*-*-*-*-*-120-*-*-*-*-*-*" to type FontStruct'. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: x11-apps 7.7+8build2 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 16:54:39 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev d4) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2022-05-27 (597 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic root=UUID=d735b1e5-edce-40f0-af9c-c7a03597914c ro quiet splash vt.handoff=7 SourcePackage: x11-apps UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 03WC5R dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:br5.3:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn03WC5R:rvrA00:cvnDellInc.:ct10:cvr1.3.0:sku087E: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A
[Desktop-packages] [Bug 2041736] [NEW] dm crypt unlock prompt doesn't respond to key presses
Public bug reported:
After upgrading my MacbookPro 14,1 from 23.04 to 23.10 dm-crypt unlock prompt
doesn't respond to key presses and I'm not able to type in my password to
unlock the disk.
The only option that works now is to boot with the kernel left from 23.04
(6.2.0-35-generic).
Any tips to troubleshoot the issue would be much appreciated.
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename: mantic
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: plymouth 22.02.122-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 10:25:26 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-04-22 (190 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: Upgraded to mantic on 2023-10-27 (2 days ago)
dmi.bios.date: 08/22/2022
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 499.40.2.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias:
dmi:bvnAppleInc.:bvr499.40.2.0.0:bd08/22/2022:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/2041736
Title:
dm crypt unlock prompt doesn't respond to key presses
Status in plymouth package in Ubuntu:
New
Bug description:
After upgrading my MacbookPro 14,1 from 23.04 to 23.10 dm-crypt unlock prompt
doesn't respond to key presses and I'm not able to type in my password to
unlock the disk.
The only option that works now is to boot with the kernel left from 23.04
(6.2.0-35-generic).
Any tips to troubleshoot the issue would be much appreciated.
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: plymouth 22.02.122-3ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-35.35-generic 6.2.16
Uname: Linux 6.2.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 10:25:26 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-04-22 (190 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-35-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
[Desktop-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same issue on Razer Blade 16. Please help -- 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/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021940] Re: firefox (114.0+build1-0ubuntu0.22.04.1~mt1) No GPU Hardware Acceleraton on Arm64
I'm experiencing this too, which has caused WebGL not to work. I'm
however on an x64 machine, not Arm64, so it's not limited to that
architecture.
I have the same logs as above:
[GFX1-]: FireTestProcess failed: Failed to spawn child process
“/usr/lib/firefox/glxtest” >
[GFX1-]: glxtest: ManageChildProcess failed
[GFX1-]: No GPUs detected via PCI
Browsing to a page which uses WebGL gives the following messages in the
console:
WebGL warning: : WebglAllowWindowsNativeGl:false restricts context
creation on this system.
Failed to create WebGL context: WebGL creation failed:
* WebglAllowWindowsNativeGl:false restricts context creation on this system. ()
* Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS)
--
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/2021940
Title:
firefox (114.0+build1-0ubuntu0.22.04.1~mt1) No GPU Hardware
Acceleraton on Arm64
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Ubuntu Jammy and Lunar. The latest upgrade to Firefox
114.0+build1-0ubuntu0.22.04.1~mt1 arm64 lead to GPU Hardware
Acceleration no longer available on Firefox. GPU Hardware
Acceleration is available on Firefox
113.0.2+build1-0ubuntu0.22.04.1~mt1 and earlier versions.
Could it be due to this:
* Install glxtest and vaapitest
Where it was not in Firefox 113.0.2+build1-0ubuntu0.22.04.1~mt1.
Publishing details
Published on 2023-05-30
Changelog
firefox (114.0+build1-0ubuntu0.23.04.1~mt1) lunar; urgency=medium
* New upstream release (114.0+build1)
* Install glxtest and vaapitest
- debian/firefox.install.in
{
"application": {
"name": "Firefox",
"osVersion": "Linux 5.15.112-ophub #1 SMP PREEMPT Wed May 17 22:26:56 EDT
2023",
"version": "114.0",
"buildID": "20230529085652",
"distributionID": "canonical",
"userAgent": "Mozilla/5.0 (X11; Ubuntu; Linux aarch64; rv:109.0)
Gecko/20100101 Firefox/114.0",
"safeMode": false,
"memorySizeBytes": 3498860544,
"diskAvailableBytes": 54004117504,
"supportURL": "https://support.mozilla.org/1/firefox/114.0/Linux/en-US/;,
"osTheme": "Yaru-dark / Yaru",
"numTotalWindows": 1,
"numFissionWindows": 1,
"numRemoteWindows": 1,
"fissionAutoStart": true,
"fissionDecisionStatus": "enabledByDefault",
"remoteAutoStart": true,
"policiesStatus": 0,
"keyLocationServiceGoogleFound": true,
"keySafebrowsingGoogleFound": true,
"keyMozillaFound": false
},
"securitySoftware": {
"registeredAntiVirus": "",
"registeredAntiSpyware": "",
"registeredFirewall": ""
},
"environmentVariables": {
"MOZ_ENABLE_WAYLAND": "1",
"DISPLAY": ":0",
"MOZ_APP_LAUNCHER": "/usr/bin/firefox",
"MOZ_ASSUME_USER_NS": "1",
"MOZ_LAUNCHED_CHILD": "",
"MOZ_APP_SILENT_START": "",
"XRE_PROFILE_PATH": "",
"XRE_PROFILE_LOCAL_PATH": "",
"XRE_START_OFFLINE": "",
"XRE_BINARY_PATH": "",
"XRE_RESTARTED_BY_PROFILE_MANAGER": ""
},
"modifiedPreferences": {
"accessibility.typeaheadfind.flashBar": 0,
"browser.contentblocking.category": "strict",
"browser.privatebrowsing.autostart": true,
"browser.search.region": "MY",
"browser.startup.homepage_override.mstone": "114.0",
"browser.startup.homepage_override.once":
"{\"message_id\":\"WNP_MOMENTS_14\",\"url\":\"https://www.mozilla.org/firefox/welcome/14\",\"expire\":166847040};,
"browser.startup.homepage_override.buildID": "20230529085652",
"browser.urlbar.quicksuggest.migrationVersion": 2,
"browser.urlbar.tipShownCount.searchTip_onboard": 4,
"browser.urlbar.quicksuggest.scenario": "history",
"browser.urlbar.placeholderName.private": "DuckDuckGo",
"doh-rollout.home-region": "MY",
"doh-rollout.balrog-migration-done": true,
"doh-rollout.doneFirstRun": true,
"extensions.lastAppVersion": "114.0",
"idle.lastDailyNotification": 1685513742,
"media.gmp-manager.lastEmptyCheck": 1685513619,
"media.gmp-manager.lastCheck": 1685513619,
"media.gmp-manager.buildID": "20230529085652",
"media.gmp.storage.version.observed": 1,
"network.dns.disablePrefetch": true,
"network.http.referer.disallowCrossSiteRelaxingDefault.top_navigation":
true,
"network.http.speculative-parallel-limit": 0,
"network.predictor.enabled": false,
"network.prefetch-next": false,
"places.database.lastMaintenance": 1685513742,
"privacy.purge_trackers.last_purge": "1685513742669",
"privacy.purge_trackers.date_in_cookie_database": "0",
"privacy.sanitize.pending":
"[{\"id\":\"shutdown\",\"itemsToClear\":[\"cache\",\"cookies\",\"offlineApps\"],\"options\":{}},{\"id\":\"newtab-container\",\"itemsToClear\":[],\"options\":{}}]",
[Desktop-packages] [Bug 2020030] [NEW] System 76 Lemur Pro - Light Display Manager failed on boot
Public bug reported: I have executed a ubuntu-bug lightdm as requested here: https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709 In my case I did nano /etc/systemd/system/display-manager.service and double checked Restart=Always was on (it was) and added RestartSec=0.5. So far it’s booting every single time without issue. It might be better to include that in the config by default so less people run into this issue. Most of the people who were addressing this ended up reinstalling Ubuntu Budgie and this fix can avoid that issue entirely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service] Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed May 17 21:50:52 2023 InstallationDate: Installed on 2022-09-21 (239 days ago) InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) LightdmConfig: [Seat:*] greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/2020030 Title: System 76 Lemur Pro - Light Display Manager failed on boot Status in lightdm package in Ubuntu: New Bug description: I have executed a ubuntu-bug lightdm as requested here: https://discourse.ubuntubudgie.org/t/failed-to-start-light-display-manager/6709 In my case I did nano /etc/systemd/system/display-manager.service and double checked Restart=Always was on (it was) and added RestartSec=0.5. So far it’s booting every single time without issue. It might be better to include that in the config by default so less people run into this issue. Most of the people who were addressing this ended up reinstalling Ubuntu Budgie and this fix can avoid that issue entirely. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: lightdm 1.30.0-0ubuntu5 [modified: lib/systemd/system/lightdm.service] Uname: Linux 6.2.6-76060206-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed May 17 21:50:52 2023 InstallationDate: Installed on 2022-09-21 (239 days ago) InstallationMedia: Ubuntu-Budgie 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) LightdmConfig: [Seat:*] greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2020030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009684] [NEW] package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-lin
Public bug reported: apt dist-upgrade crashed ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .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 525.85.12 Sat Jan 28 02:10:06 UTC 2023 GCC version: ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Wed Mar 8 12:48:25 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 GraphicsCard: NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] [10de:2488] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GA104 [GeForce RTX 3070 Lite Hash Rate] [1569:f280] InstallationDate: Installed on 2023-03-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Micro-Star International Co., Ltd. MS-7D28 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=8a4a53bf-0539-4847-80b7-e688eea77975 ro quiet nomodeset Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.20ubuntu2 apt 2.5.6 SourcePackage: mesa Title: package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2022 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.90 dmi.board.asset.tag: Default string dmi.board.name: MEG Z690 UNIFY (MS-7D28) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.90:bd11/07/2022:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D28:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ690UNIFY(MS-7D28):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D28 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar single-occurrence ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2009684 Title: package libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: apt dist-upgrade crashed ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1 [modified: usr/share/drirc.d/00-mesa-defaults.conf] ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry:
[Desktop-packages] [Bug 2008905] [NEW] Two-finger scrolling on touchpad not working as expected
Public bug reported: My touchpad works normally except for two-finger scrolling, where it frequently jumps/skips instead of scrolling smoothly. I was originally using libinput drivers and switched to synaptics drivers, but it did not resolve the issue. I am hoping to get some help identifying the root cause ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 09:29:29 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-11-07 (113 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 5560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=c80e66ed-7a8a-4922-9819-2e31d3312e40 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0G06MM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd11/16/2022:br1.16:svnDellInc.:pnPrecision5560:pvr:rvnDellInc.:rn0G06MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A62: dmi.product.family: Precision dmi.product.name: Precision 5560 dmi.product.sku: 0A62 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6 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: xserver-xorg-input-synaptics (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 xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/2008905 Title: Two-finger scrolling on touchpad not working as expected Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: My touchpad works normally except for two-finger scrolling, where it frequently jumps/skips instead of scrolling smoothly. I was originally using libinput drivers and switched to synaptics drivers, but it did not resolve the issue. I am hoping to get some help identifying the root cause ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-60.66~20.04.1-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: falcon_lsm_serviceable falcon_nf_netcontain falcon_kal falcon_lsm_pinned_14713 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 1 09:29:29 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu InstallationDate: Installed on 2022-11-07 (113 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Precision 5560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=c80e66ed-7a8a-4922-9819-2e31d3312e40 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2022 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0G06MM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd11/16/2022:br1.16:svnDellInc.:pnPrecision5560:pvr:rvnDellInc.:rn0G06MM:rvrA00:cvnDellInc.:ct10:cvr:sku0A62: dmi.product.family: Precision dmi.product.name: Precision 5560 dmi.product.sku: 0A62 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.6
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Noting 4.0.1 stable has now been released, perhaps we could have an update to fix this issue now (if not in 22.10, perhaps in 23.04?). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006636] [NEW] Many Cyan Lines Cover Computer Screen
Public bug reported: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2006636 Title: Many Cyan Lines Cover Computer Screen Status in xorg package in Ubuntu: New Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
[Desktop-packages] [Bug 1973084] Re: transmission-daemon high RAM usage
Confirmed happening in x86_64 build (and has been for at least six months, under both 22.04 and 22.10...though it was fine at some point in the past as I used it successfully for many years with no issue. Please, please, please fix (even if the solution is giving us some mechanism to upgrade to the 4.0 beta via PPA or something (as the commits mention several fixes to memory leaks)...this has been driving me nuts! No specific torrent, reboot or restart fixes issue (temporarily). Transmission 3.00 (bb6b5a062e). 51 files seeding (currently), though it doesn't seem sensitive to the number. 16MB disk cache. Max 240 peers. Tried disabling PEX, DHT and LPD to see if that would help as I don't particularly need them anyway (but it doesn't help). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1973084 Title: transmission-daemon high RAM usage Status in transmission package in Ubuntu: Confirmed Bug description: Transmission uses a lot of RAM in ubuntu 22.04 server (arm64) runnign on a Raspberry Pi 4. It "eats" RAM and the RAM usage grows each hour until it crashes the system. I sideloaded transmission-daemon and its dependancies from debian 11 (arm64) locked the packages so apt won't update them and, ever since, this issue hasn't happened. Description:Ubuntu 22.04 LTS Release:22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1973084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986415] [NEW] package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: driver issues,,, i also cant launch genymotion ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Aug 8 00:23:36 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-16 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1986415 Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: driver issues,,, i also cant launch genymotion ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Aug 8 00:23:36 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-07-16 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.5 SourcePackage: firefox Title: package firefox (not installed) failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1986415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
Matthieu, more recently a more likely problem has been characterized by Alberto Mardegan and found the line in question in https://bugs.launchpad.net/snapd/+bug/1973321 In particular, restarting snapd doesn't help at all for me, so having the directory mounted before snapd starts doesn't help, and the same problem occurs with other file systems. However _starting_ outside the home directory does help. This is the situation for me with Kerberos authenticated NFS, and others with sshfs. I don't know whether it is relevant for people using NFS without authentication. It is easy to test for yourself - restart snapd and see if that helps. So I think there is progress in understanding the problem, even if not working out how to fix it. FYI: I initially tried a work around where I used the debian repository for firefox instead of the snap version, but despite giving it a higher priority (confirmed via "sudo apt policy firefox") I found the debian package twice over a week uninstalled and replaced by the snap version that then would not start. I can manually revert it but it is inconvenient. Any suggestions on how to make that work reliably would be appreciated. -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Thanks Alberto. I tried running "hello" in a different directory, and you were correct: arc@andrewfairfield:~$ hello cannot open path of the current working directory: Permission denied arc@andrewfairfield:~$ cd / arc@andrewfairfield:/$ hello Hello, world! arc@andrewfairfield:/$ [ This is in 20.04, not 22.04 ] Yay! that is the first time I have seen a snap actually work with my normal user account. This feels like significant progress in working out what is going on! Of course firefox needs access to the home directory to load the profile and store downloads. Is the whole process run as some other user (a la sudo) or is there just some starting stub running as some other user doing something that returns to the actual user after doing something that thinks it needs access to the current directory but could get by without it? Actually, I can sort of answer that - I tried running "musescore" as a snap, starting from / It successfully ran. I tried saving something, and it sort of did... but in a new, empty "home" directory in a /home/arc/snap/musescore/216/ that the save file dialog went to when I pressed the home button. Is this normal behaviour for a snap? Regardless of the inconvenience of the subdirectory, that is running over nfs successfully. I can close Musescore and load it again. But not with cwd=/home/arc. So that is fairly strong evidence supporting your idea that it is the same root cause as https://bugs.launchpad.net/bugs/1973321 . I will add a comment there. Thanks for the insight Alberto! -- 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/1784774 Title: snapd is not autofs aware and fails with nfs home dir Status in snapd: Fix Released Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Incomplete Bug description: This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand asked me to open a new bug for this specific issue. In 1662552, snapd fails for nfs mounted home directories as network permissions are not enabled. A work around was implemented that works if the mount is done via a /home mount at boot. However this does not work if people mount home directories via autofs. This is probably the fundamental problem for 1782873 although there may be other issues. [ Why use autofs? If some but not all of users want to use nfs homes. In particular, I have a local user on all my accounts that does not require the nfs server to be up or the kerberos server to be up, or kerberos working on the client machines, etc. It is very useful when something goes wrong. It means I mount /home/user rather than /home (for several users). ] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
I (using Kerberos) don't the get apparmor DENIED messages that Eric (not using Kerberos) did, but I get exactly the same "cannot open path of the current working directory: Permission denied" error. -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Using NVFv4, kerberos authenticated, mounted by autofs: arc@andrewshoreham:~$ hello cannot open path of the current working directory: Permission denied [ Then as user with sudo privs, sudo systemctl restart snapd ] arc@andrewshoreham:~$ hello cannot open path of the current working directory: Permission denied Logs since just before restarting snapd syslog -- May 15 14:54:09 andrewshoreham kernel: [12319.195323] audit: type=1400 audit(1652590449.676:183): apparmor="ALLOWED" operation="open" profile="/usr/sbin/sssd" name="/proc/24886/cmdline" pid=910 comm="sssd_nss" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 May 15 14:54:09 andrewshoreham systemd[1]: Stopping Snap Daemon... May 15 14:54:09 andrewshoreham snapd[726]: main.go:155: Exiting on terminated signal. May 15 14:54:09 andrewshoreham snapd[726]: overlord.go:504: Released state lock file May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Deactivated successfully. May 15 14:54:09 andrewshoreham systemd[1]: Stopped Snap Daemon. May 15 14:54:09 andrewshoreham systemd[1]: snapd.service: Consumed 2.753s CPU time. May 15 14:54:09 andrewshoreham systemd[1]: Starting Snap Daemon... May 15 14:54:09 andrewshoreham snapd[24890]: AppArmor status: apparmor is enabled and all features are available May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:263: Acquiring state lock file May 15 14:54:09 andrewshoreham snapd[24890]: overlord.go:268: Acquired state lock file May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:247: started snapd/2.55.3+22.04 (series 16; classic) ubuntu/22.04 (amd64) linux/5.15.0-25-generic. May 15 14:54:09 andrewshoreham kernel: [12319.270748] loop11: detected capacity change from 0 to 8 May 15 14:54:09 andrewshoreham snapd[24890]: daemon.go:340: adjusting startup timeout by 1m10s (pessimistic estimate of 30s plus 5s per snap) May 15 14:54:09 andrewshoreham systemd[1]: tmp-sanity\x2dmountpoint\x2d2760788470.mount: Deactivated successfully. May 15 14:54:09 andrewshoreham snapd[24890]: backend.go:133: snapd enabled NFS support, additional implicit network permissions granted May 15 14:54:10 andrewshoreham kernel: [12319.549118] audit: type=1400 audit(1652590450.028:184): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=24926 comm="apparmor_parser" May 15 14:54:10 andrewshoreham kernel: [12319.578896] audit: type=1400 audit(1652590450.060:185): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=24926 comm="apparmor_parser" May 15 14:54:10 andrewshoreham kernel: [12319.969313] audit: type=1400 audit(1652590450.448:186): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/15534/usr/lib/snapd/snap-confine" pid=24946 comm="apparmor_parser" May 15 14:54:10 andrewshoreham kernel: [12319.983029] audit: type=1400 audit(1652590450.464:187): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/snap/snapd/15534/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=24946 comm="apparmor_parser" May 15 14:54:10 andrewshoreham kernel: [12320.165228] audit: type=1400 audit(1652590450.644:188): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.snapd-desktop-integration.hook.configure" pid=24950 comm="apparmor_parser" May 15 14:54:10 andrewshoreham kernel: [12320.341043] audit: type=1400 audit(1652590450.820:189): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.snapd-desktop-integration.snapd-desktop-integration" pid=24951 comm="apparmor_parser" May 15 14:54:11 andrewshoreham kernel: [12320.633250] audit: type=1400 audit(1652590451.112:190): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.snap-store" pid=24948 comm="apparmor_parser" May 15 14:54:11 andrewshoreham kernel: [12320.721431] audit: type=1400 audit(1652590451.200:191): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.snapd-desktop-integration" pid=24949 comm="apparmor_parser" May 15 14:54:11 andrewshoreham kernel: [12320.727129] audit: type=1400 audit(1652590451.208:192): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.hello" pid=24954 comm="apparmor_parser" May 15 14:54:11 andrewshoreham systemd[1]: Started Snap Daemon. May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.166' (uid=0 pid=24890 comm="/usr/lib/snapd/snapd " label="unconfined") May 15 14:54:11 andrewshoreham systemd[1]: Starting Time & Date Service... May 15 14:54:11 andrewshoreham dbus-daemon[693]: [system] Successfully
[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
I got exactly the same errors as Miles above; a simple permission denied error stopping things before AppArmor got involved. I.e., the answer to Markus Kuhn's question is no, in fact even in enforce mode there are no denied apparmor complaints. I don't know whether this is because the gating problem is not being able to read the ticket in /tmp, or whether being in the kernel solves some of the apparmor issues, but the greater pickiness of kerberos user definition is an issue. Do snaps run as a different uid? -- 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/1784774 Title: snapd is not autofs aware and fails with nfs home dir Status in snapd: Fix Released Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: Fix Released Bug description: This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand asked me to open a new bug for this specific issue. In 1662552, snapd fails for nfs mounted home directories as network permissions are not enabled. A work around was implemented that works if the mount is done via a /home mount at boot. However this does not work if people mount home directories via autofs. This is probably the fundamental problem for 1782873 although there may be other issues. [ Why use autofs? If some but not all of users want to use nfs homes. In particular, I have a local user on all my accounts that does not require the nfs server to be up or the kerberos server to be up, or kerberos working on the client machines, etc. It is very useful when something goes wrong. It means I mount /home/user rather than /home (for several users). ] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884299] Re: Chromium snap won't run with nfs home drive
Firefox also doesn't work now it is a snap in 22.04. I think there are still multiple issues here. The original poster seems to be using NVSv3 I believe based on the RPC errors (NFSv3 uses multiple ports, one of which is called something like RPC, but I am not an expert in this as I have only used NFSv4, which uses a single port). Is this correct tylerecouture? NFSv3 has no user authentication; NFSv4 uses Kerberos for authentication (and privacy and tamper resistance). I think this brings in additional problems as snaps don't appear to work with Kerberos e.g. https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346 https://bugzilla.mozilla.org/show_bug.cgi?id=1734791 I get a very different error - a simple permission denied error rather than an AppArmor problem. ** Bug watch added: Mozilla Bugzilla #1734791 https://bugzilla.mozilla.org/show_bug.cgi?id=1734791 ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
I did some more investigating, and I think there are two independent problems here: (1) The problem as believed so far, network access permissions (2) New insight: Kerberos doesn't work with snaps. This explains why fixing (1) didn't help me (or Adam). Background: Kerberos is the authentication mechanism used for NFS. Assuming you are using authentication (as almost everyone does), then when you access NFS contents, you need to provide kerberos credentials. These are stored outside of your home directory (after all, home directories are one of the most common reasons to use NFS, so you can't store them there). I believe snaps restrict access to just your home directory, so you can't access the Kerberos key and therefore can't access your home directory. This is supported by various bugs like https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346 (unresolved) which is a different but relevant issue - people who don't use NFS but do use Kerberos features in Firefox found they don't work post snap conversion. -- 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/1784774 Title: snapd is not autofs aware and fails with nfs home dir Status in snapd: Fix Released Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: Fix Released Bug description: This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand asked me to open a new bug for this specific issue. In 1662552, snapd fails for nfs mounted home directories as network permissions are not enabled. A work around was implemented that works if the mount is done via a /home mount at boot. However this does not work if people mount home directories via autofs. This is probably the fundamental problem for 1782873 although there may be other issues. [ Why use autofs? If some but not all of users want to use nfs homes. In particular, I have a local user on all my accounts that does not require the nfs server to be up or the kerberos server to be up, or kerberos working on the client machines, etc. It is very useful when something goes wrong. It means I mount /home/user rather than /home (for several users). ] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
I never got it to work in 20.04, so I don't know whether your fix ever made it in. I have just installed Jammy Jellyfish (22.04), and can confirm snaps don't work in it when using autofs and nfs mounted home directories. The prior work around was just never use any snap applications, which was OK as nothing important was in snaps prior to 22.04. This is harder in 22.04 as firefox is distributed as a snap, and so firefox doesn't work in 22.04 if you have autofs NFS home directories. Work around is to use a different source for firefox, https://ubuntuhandbook.org/index.php/2022/04/install-firefox-deb- ubuntu-22-04/ but I don't know whether that will get security updates as quickly, so this is a serious problem. ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1784774 Title: snapd is not autofs aware and fails with nfs home dir Status in snapd: Fix Released Status in firefox package in Ubuntu: New Status in snapd package in Ubuntu: Fix Released Bug description: This is similar to bugs 1662552 and 1782873. In 1782873, jdstrand asked me to open a new bug for this specific issue. In 1662552, snapd fails for nfs mounted home directories as network permissions are not enabled. A work around was implemented that works if the mount is done via a /home mount at boot. However this does not work if people mount home directories via autofs. This is probably the fundamental problem for 1782873 although there may be other issues. [ Why use autofs? If some but not all of users want to use nfs homes. In particular, I have a local user on all my accounts that does not require the nfs server to be up or the kerberos server to be up, or kerberos working on the client machines, etc. It is very useful when something goes wrong. It means I mount /home/user rather than /home (for several users). ] To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956243] Re: Ping give socket error initially if IPv6 is disabled
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1956243 Title: Ping give socket error initially if IPv6 is disabled Status in iputils package in Ubuntu: New Bug description: With IpV6 enabled everything works well. However if you disable ipv6 by editing /etc/default/grub with the following entry GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" then when you ping there is an initial socket error ping localhost ping: socket: Address family not supported by protocol PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms however ping -4 works ping -4 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms so it looks like ping is trying ipv6 first and not detecting that its disabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iputils-ping 3:20210202-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 3 17:42:07 2022 InstallationDate: Installed on 2022-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211029) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1956243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1751954] Re: Bluetooth and Wi-Fi items in Power are worded ambiguously
It says above fix released in August, however I still have the bad wording and it has caught me out today. I'm running Ubuntu 20.04.03 gnome 3.36.8. Why has the fix not reached me yet please? -- 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/1751954 Title: Bluetooth and Wi-Fi items in Power are worded ambiguously Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Committed Bug description: In the gnome-control-center, in the power section, there is a checkbox that says: Wi-Fi Turn off Wi-Fi to save power I have it checked, so after a few minutes without using my computer, the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this box, but it disables my wi-fi immediately. So, it's obviously wrong to disable the wi-fi when I click that checkbox. And I don't seem to have a way to keep my wi-fi enabled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 18:27:16 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-04 (145 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eo SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1751954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Having a similar issue on my ASUS Zenbook UX434, also using the ALC294 as above, Kernel: 5.13.0-28-generic. In my case after a reboot from my Windows 10 dual boot the audio out is fine, but the microphone has very loud crackling which makes it unusable. The problem isn't fixed by a reboot but after a full shutdown and restart the problem seems to go away. Thanks to Hilikus for the workaround! Had an identical problem on Kubuntu 20.04 and now ZorinOS 16 - clearly this issue isn't entirely fixed even with more recent kernel patches. -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR 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/1742852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959513] [NEW] image crashes image viewer
Public bug reported: when viewing pixie02.jpg image crashes the image viewer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 10:57:16 2022 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2022-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "pixie02.jpg" https://bugs.launchpad.net/bugs/1959513/+attachment/5558270/+files/pixie02.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1959513 Title: image crashes image viewer Status in eog package in Ubuntu: New Bug description: when viewing pixie02.jpg image crashes the image viewer ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: eog 3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 10:57:16 2022 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2022-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1959513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959512] [NEW] playing a video cause the video player to crash
Public bug reported: when attempting to play the vp8.webm file causes the Videos file to crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 10:36:31 2022 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2022-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "vp8.webm" https://bugs.launchpad.net/bugs/1959512/+attachment/5558263/+files/vp8.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1959512 Title: playing a video cause the video player to crash Status in gstreamer1.0 package in Ubuntu: New Bug description: when attempting to play the vp8.webm file causes the Videos file to crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 30 10:36:31 2022 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2022-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1959512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957716] [NEW] Update for CVE-2021-43860 and second github advisory
*** This bug is a security vulnerability *** Public security bug reported: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx https://security-tracker.debian.org/tracker/CVE-2021-43860 [Impact] Versions in Ubuntu right now: Jammy: 1.12.2-2 Impish: 1.10.2-3ubuntu0.1 Focal: 1.6.5-0ubuntu0.4 Bionic: 1.0.9-0ubuntu0.4 Affected versions: all Patched versions: 1.12.3, 1.10.6 [Test Case] Unknown [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Patches] There are two separate github advisories but only one of them has a CVE. The advisory with the CVE has 5 patches, the other has 2 patches. [Other Information] For the first advisory with the CVE: Ryan Gonzalez discovered that Flatpak doesn't properly validate that the permissions displayed to the user for an app at install time match the actual permissions granted to the app at runtime, in the case that there's a null byte in the metadata file of an app. Therefore apps can grant themselves permissions without the consent of the user. Flatpak shows permissions to the user during install by reading them from the "xa.metadata" key in the commit metadata. This cannot contain a null terminator, because it is an untrusted GVariant. Flatpak compares these permissions to the actual metadata, from the "metadata" file to ensure it wasn't lied to. However, the actual metadata contents are loaded in several places where they are read as simple C-style strings. That means that, if the metadata file includes a null terminator, only the content of the file from before the terminator gets compared to xa.metadata. Thus, any permissions that appear in the metadata file after a null terminator are applied at runtime but not shown to the user. Maliciously crafted apps can use this to give themselves hidden permissions. In addition, a similar weakness was discovered, where if the permissions in the summary metadata are invalid, they would not be displayed to the user, but the the actual permissions would be granted, even though it didn't match the invalid version. For the second advisory: flatpak-builder applies finish-args last in the build. At this point the build directory will have the full access that is specified in the manifest, so running flatpak build against it will gain that permissions. Normally this will not be done, so this is not problem. However, if --mirror-screenshots-url is specified, then flatpak-builder will launch flatpak build --nofilesystem=host appstream-utils mirror- screenshots after finalization, which can lead to issues even with the --nofilesystem=host protection. These changes result in a behaviour change as debian have noted in their changelog: * Behaviour changes, as a result of how GHSA-8ch7-5j3h-g4fx was fixed: - --nofilesystem=host is now special-cased to negate all --filesystem permissions. Previously, it would cancel out --filesystem=host but not --filesystem=/some/dir. - --nofilesystem=home is now special-cased to negate several home-directory-related filesystem permssions such as --filesystem=xdg-config/foo, not just --filesystem=host. ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Information type changed from Public to Public Security ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-43860 ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1957716 Title: Update for CVE-2021-43860 and second github advisory Status in flatpak package in Ubuntu: In Progress Bug description: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-qpjc-vq3c-572j https://github.com/flatpak/flatpak/security/advisories/GHSA-8ch7-5j3h-g4fx https://security-tracker.debian.org/tracker/CVE-2021-43860 [Impact] Versions in Ubuntu right now: Jammy: 1.12.2-2 Impish: 1.10.2-3ubuntu0.1 Focal: 1.6.5-0ubuntu0.4 Bionic: 1.0.9-0ubuntu0.4 Affected versions: all Patched versions: 1.12.3, 1.10.6 [Test Case] Unknown [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak .
[Desktop-packages] [Bug 124406] Re: Keyboard keys get stuck and repeat
I have a keyboard a4tech KV-300h and the bug reproduce on windows too. I have already tried to replace to another a new keyboard. The problem isn't gone. I found out if I use embedded USB port of keyboard to connect a mouse then the problem reproduce very often. Also I tested my keyboard on macbook pro. There is everything works fine. System: Host: adrug-X470-AORUS-ULTRA-GAMING Kernel: 5.13.0-23-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.0.7 Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Desktop System: Gigabyte product: X470 AORUS ULTRA GAMING v: N/A serial: N/A Mobo: Gigabyte model: X470 AORUS ULTRA GAMING-CF v: x.x serial: N/A UEFI: American Megatrends LLC. v: F61 date: 07/13/2021 CPU: Topology: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86394 Speed: 2200 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2200 2: 2189 3: 2199 4: 2200 5: 2199 6: 2199 7: 2199 8: 2200 9: 2249 10: 2198 11: 2200 12: 2199 Graphics: Device-1: AMD vendor: Gigabyte driver: amdgpu v: kernel bus ID: 0c:00.0 Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 2560x1080~60Hz OpenGL: renderer: AMD Radeon RX 6600 XT (DIMGREY_CAVEFISH DRM 3.41.0 5.13.0-23-generic LLVM 12.0.1) v: 4.6 Mesa 21.3.0-devel direct render: Yes -- 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/124406 Title: Keyboard keys get stuck and repeat Status in GNU Emacs: Invalid Status in Linux: Confirmed Status in X.Org X server: In Progress Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Status in linux source package in Jaunty: Won't Fix Status in xorg-server source package in Jaunty: Invalid Status in Gentoo Linux: New Bug description: Keyboard keys such as the arrows, Alt-F4, PageUp/PageDown, etc. often get 'stuck' and continue being 'clicked' even after they are physically released. For example when clicking Alt-F4, sometimes it gets stuck so all the windows are closed instead of just one. My configuration is Feisty + Xgl + Compiz Fusion. My previous configuration was Edgy + Xgl + Beryl, where this didn't happen. Others have reported the same problem without using either Xgl or Compiz. The keyboard itself isn't the problem. When dual-booting to Windows, everything works fine. Also, the problem happens with two different keyboards (internal laptop, external USB). My best guess is that the problem occurs at time of high system load. Somehow during these times the key-release signal gets lost and the key-press is repeated indefinitely. This happens more often with Compiz configurations because Compiz tends to increase system load. It also happens more often with power-hungry apps like Firefox and Acrobat Reader for similar reasons. PS: When the keys would repeat all input devices would be locked up. ie. mouse won't move, clicks don't do anything, keyboard presses don't register. Then when it becomes unstuck, the mouse moves around and everything. Hope this helps. See also this forum thread for other people with the same problem: http://ubuntuforums.org/showthread.php?t=432057 To manage notifications about this bug go to: https://bugs.launchpad.net/emacs/+bug/124406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956243] [NEW] Ping give socket error initially if IPv6 is disabled
Public bug reported: With IpV6 enabled everything works well. However if you disable ipv6 by editing /etc/default/grub with the following entry GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" then when you ping there is an initial socket error ping localhost ping: socket: Address family not supported by protocol PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms however ping -4 works ping -4 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms so it looks like ping is trying ipv6 first and not detecting that its disabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iputils-ping 3:20210202-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 3 17:42:07 2022 InstallationDate: Installed on 2022-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211029) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages uec-images -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1956243 Title: Ping give socket error initially if IPv6 is disabled Status in iputils package in Ubuntu: New Bug description: With IpV6 enabled everything works well. However if you disable ipv6 by editing /etc/default/grub with the following entry GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" then when you ping there is an initial socket error ping localhost ping: socket: Address family not supported by protocol PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms however ping -4 works ping -4 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms so it looks like ping is trying ipv6 first and not detecting that its disabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iputils-ping 3:20210202-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 3 17:42:07 2022 InstallationDate: Installed on 2022-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211029) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1956243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953116] [NEW] Mouse not staying powered
Public bug reported: Mouse receives power via USB when plugged in, immediately loses it. Mouse on other devices, USB port provides power to other mice. Manufacturer: Microsoft Model: Microsoft Ergonomic Mouse (Wired) Connection: USB Mechanism: Optical Buttons: 4 Buttons + 1 Scrollwheel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 3 00:14:13 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2021-11-01 (32 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e3adb636-cdf3-436a-8963-358dfa8e0a4e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0D65FD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1953116 Title: Mouse not staying powered Status in xorg package in Ubuntu: New Bug description: Mouse receives power via USB when plugged in, immediately loses it. Mouse on other devices, USB port provides power to other mice. Manufacturer: Microsoft Model: Microsoft Ergonomic Mouse (Wired) Connection: USB Mechanism: Optical Buttons: 4 Buttons + 1 Scrollwheel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 3 00:14:13 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2021-11-01 (32 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e3adb636-cdf3-436a-8963-358dfa8e0a4e ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 0D65FD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1
[Desktop-packages] [Bug 1949909] [NEW] bluetooth crashes on resume from suspend
Public bug reported: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: bluetooth crashes on resume from suspend Status in bluez package in Ubuntu: New Bug description: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946578] [NEW] Placeholder for CVE-2021-41133
Public bug reported: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-67h7-w3jq-vh4q https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995935 https://security-tracker.debian.org/tracker/CVE-2021-41133 ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1946578 Title: Placeholder for CVE-2021-41133 Status in flatpak package in Ubuntu: New Bug description: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-67h7-w3jq-vh4q https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995935 https://security-tracker.debian.org/tracker/CVE-2021-41133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1946578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944431] Re: Changing the resolution while in the activites overview changes to the desktop
Reported an issue upstream https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4626 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4626 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4626 -- 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/1944431 Title: Changing the resolution while in the activites overview changes to the desktop Status in gnome-shell package in Ubuntu: New Bug description: What Happened 1) Open GNOME Shell to the activities overview 2) Change the resolution (eg if using a VM resize it) 3) Notice that we switch to the desktop view What I expected to happen: At step 3 to remain in the activities overview. $ apt policy gnome-shell gnome-shell: Installed: 40.2-1ubuntu6 Candidate: 40.2-1ubuntu6 Version table: *** 40.2-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1944431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944431] Re: Changing the resolution while in the activites overview changes to the desktop
** Description changed: What Happened - 1) Installed the package gnome-session (ensuring it is the latest version) - 2) At gdm picked "GNOME" and not "Ubuntu" - 3) Reboot and login to the desktop - 4) Notice that initially the activity overview is shown (correctly) - 5) Then within a second or so, something causes the desktop to be focused and activity overview closed (incorrect) - - Further notes: - - if you log out and log back in again, it doesn't happen ? - - if you wait on the gdm login for a long period of time (eg over a minute) then it doesn't happen ? - - this is *not* the Ubuntu session but the GNOME session + 1) Open GNOME Shell to the activities overview + 2) Change the resolution (eg if using a VM resize it) + 3) Notice that we switch to the desktop view What I expected to happen: - At step 5 for the activity overview to stay and not switch to the desktop until the user has interacted. + At step 3 to remain in the activities overview. - - I understand that the Ubuntu session with the dock enabled wants the desktop to be the current state after login. But for the GNOME session with no extensions enabled, the way that if one logs in quickly and something is triggering the activity overview to be dismissed appears to be a bug. - - - $ apt policy gnome-session - gnome-session: - Installed: 40.1.1-1ubuntu1 - Candidate: 40.1.1-1ubuntu1 + $ apt policy gnome-shell + gnome-shell: + Installed: 40.2-1ubuntu6 + Candidate: 40.2-1ubuntu6 Version table: - *** 40.1.1-1ubuntu1 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages - 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages + *** 40.2-1ubuntu6 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 ** Package changed: gnome-session (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1944431 Title: Changing the resolution while in the activites overview changes to the desktop Status in gnome-shell package in Ubuntu: New Bug description: What Happened 1) Open GNOME Shell to the activities overview 2) Change the resolution (eg if using a VM resize it) 3) Notice that we switch to the desktop view What I expected to happen: At step 3 to remain in the activities overview. $ apt policy gnome-shell gnome-shell: Installed: 40.2-1ubuntu6 Candidate: 40.2-1ubuntu6 Version table: *** 40.2-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1944431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944431] Re: gnome-session impish 40 update login quickly causes desktop rather than activites overview
OK, I've figured out what is going on. If you are on the activities overview and you change the resolution of the VM it then goes back to the desktop. I'll see if there are any bugs upstream as it happens on Fedora rawhide as well ... ** Summary changed: - gnome-session impish 40 update login quickly causes desktop rather than activites overview + Changing the resolution while in the activites overview changes to the desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1944431 Title: Changing the resolution while in the activites overview changes to the desktop Status in gnome-session package in Ubuntu: New Bug description: What Happened 1) Installed the package gnome-session (ensuring it is the latest version) 2) At gdm picked "GNOME" and not "Ubuntu" 3) Reboot and login to the desktop 4) Notice that initially the activity overview is shown (correctly) 5) Then within a second or so, something causes the desktop to be focused and activity overview closed (incorrect) Further notes: - if you log out and log back in again, it doesn't happen ? - if you wait on the gdm login for a long period of time (eg over a minute) then it doesn't happen ? - this is *not* the Ubuntu session but the GNOME session What I expected to happen: At step 5 for the activity overview to stay and not switch to the desktop until the user has interacted. I understand that the Ubuntu session with the dock enabled wants the desktop to be the current state after login. But for the GNOME session with no extensions enabled, the way that if one logs in quickly and something is triggering the activity overview to be dismissed appears to be a bug. $ apt policy gnome-session gnome-session: Installed: 40.1.1-1ubuntu1 Candidate: 40.1.1-1ubuntu1 Version table: *** 40.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1944431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944431] [NEW] gnome-session impish 40 update login quickly causes desktop rather than activites overview
Public bug reported: What Happened 1) Installed the package gnome-session (ensuring it is the latest version) 2) At gdm picked "GNOME" and not "Ubuntu" 3) Reboot and login to the desktop 4) Notice that initially the activity overview is shown (correctly) 5) Then within a second or so, something causes the desktop to be focused and activity overview closed (incorrect) Further notes: - if you log out and log back in again, it doesn't happen ? - if you wait on the gdm login for a long period of time (eg over a minute) then it doesn't happen ? - this is *not* the Ubuntu session but the GNOME session What I expected to happen: At step 5 for the activity overview to stay and not switch to the desktop until the user has interacted. I understand that the Ubuntu session with the dock enabled wants the desktop to be the current state after login. But for the GNOME session with no extensions enabled, the way that if one logs in quickly and something is triggering the activity overview to be dismissed appears to be a bug. $ apt policy gnome-session gnome-session: Installed: 40.1.1-1ubuntu1 Candidate: 40.1.1-1ubuntu1 Version table: *** 40.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description:Ubuntu Impish Indri (development branch) Release:21.10 ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1944431 Title: gnome-session impish 40 update login quickly causes desktop rather than activites overview Status in gnome-session package in Ubuntu: New Bug description: What Happened 1) Installed the package gnome-session (ensuring it is the latest version) 2) At gdm picked "GNOME" and not "Ubuntu" 3) Reboot and login to the desktop 4) Notice that initially the activity overview is shown (correctly) 5) Then within a second or so, something causes the desktop to be focused and activity overview closed (incorrect) Further notes: - if you log out and log back in again, it doesn't happen ? - if you wait on the gdm login for a long period of time (eg over a minute) then it doesn't happen ? - this is *not* the Ubuntu session but the GNOME session What I expected to happen: At step 5 for the activity overview to stay and not switch to the desktop until the user has interacted. I understand that the Ubuntu session with the dock enabled wants the desktop to be the current state after login. But for the GNOME session with no extensions enabled, the way that if one logs in quickly and something is triggering the activity overview to be dismissed appears to be a bug. $ apt policy gnome-session gnome-session: Installed: 40.1.1-1ubuntu1 Candidate: 40.1.1-1ubuntu1 Version table: *** 40.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1944431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943769] [NEW] Update impish to 1.10.3 microrelease
Public bug reported: Placeholder ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: flatpak (Ubuntu) Status: New => In Progress ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1943769 Title: Update impish to 1.10.3 microrelease Status in flatpak package in Ubuntu: In Progress Bug description: Placeholder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1943769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1937914] [NEW] Laptop Monitor Turns off During Startup
Public bug reported: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48..., while I believe the latest version is ...5.8.0-66...). It seems clear that this problem is caused by a bug that was introduced in one of the more recent updates (...5.8.0-59..., maybe?). I am not at all sure that the problem is in xorg; the package identification webpage just suggested that, if the monitor is blank when I would expect to see the Ubuntu logo during startup, then I should say that the relevant package is xorg. I am more than happy to run additional diagnostics that you would recommend if that would help you diagnose and fix the problem. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 14:28:51 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) [103c:8538] Subsystem: Hewlett-Packard Company GM108M [GeForce MX130] [103c:8542] InstallationDate: Installed on 2021-07-06 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00b7 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b66a Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 004: ID 0bda:b00b Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=8bde40df-a693-4c3a-b5be-05611212add4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2020 dmi.bios.vendor: HP dmi.bios.version: R71 Ver. 01.11.01 dmi.board.name: 8538 dmi.board.vendor: HP dmi.board.version: KBC Version 51.2A.00 dmi.chassis.asset.tag: 5CD9308H3X dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook450G6:pvr:rvnHP:rn8538:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G6 dmi.product.sku: 5YH15UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1937914 Title: Laptop Monitor Turns off During Startup Status in xorg package in Ubuntu: New Bug description: While starting the my laptop (Computer Model: HP Probook 450 G6 ProdID 5YH15UT#ABA Memory: 15.5 GB Processor: Intel Core i7-8565U CPU @ 1.80GHz x 8 Graphics: NV118 / Mesa Intel UHD Graphics 620 (WHL GT2) Disk Capacity: 256.1 GB) which runs (OS Name: Ubuntu 20.04.2 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11) the monitor turns off as soon as Ubuntu loads. The OS loads as normal and my external monitor still works, but my laptop monitor does not. I was able to fix the problem by pressing ESC as soon as the HP logo appears during start-up, then selecting "Advanced Ubuntu Options", then choosing an older version of Ubuntu (currently that's ...5.4.0-48...,
[Desktop-packages] [Bug 1936981] [NEW] Apparmor Error when running chromium snap via selenium
Public bug reported: After transition to chromium-browser/chromium-chromedriver snap, selenium is no longer able to follow it's script to grab portions of a website. ** 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/1936981 Title: Apparmor Error when running chromium snap via selenium Status in chromium-browser package in Ubuntu: New Bug description: After transition to chromium-browser/chromium-chromedriver snap, selenium is no longer able to follow it's script to grab portions of a website. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1936981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812456] Re: [MIR] libflatpak0
tl;dr; Flatpak currently considers remotes as trusted, so after you have added one with a password at system level, you don't need a password to install apps for that remote. I don't about how polkit rules work, but this is just a comment describing what happens from a user perspective with flatpak. If you want to tighten it, I suggest discussing with upstream to ensure docs or any other assumptions etc are correct (please also ensure any changes make it into Debian, generally we have been able to avoid diffs with Debian so far - we do have a diff right now as Debian is in freeze). - Flatpak has two locations that you can add remotes and install apps to, user level and system level. System level ones are available to all users, user level ones are available to just that user - Adding a flatpak remote or installing an app at *user* level does not require any password So far I think this all makes sense, the interesting part up for debate is the next part. - When a remote is added to flatpak at *system* level, it asks for a password to verify the remote - When an app is installed at *system* level for this trusted remote, it installs without needing a password (as stated in previous comments, assuming the user is in the wheel group) To try this out you can do the following commands, the remote-add and remote-delete will need a password, the install and uninstall won't. $ flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo $ flatpak install kdeapps org.kde.kate $ flatpak uninstall org.kde.kate $ flatpak remote-delete kdeapps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1812456 Title: [MIR] libflatpak0 Status in flatpak package in Ubuntu: New Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak0 in main so we can easily build such applications. It takes a lot of work to make these dependencies optional and sometimes that is not possible. We don't need the Flatpak functionality to work by default and do not expect any other Flatpak packages to be installed by default. Default packages that have flatpak integration: - gnome-control-center (application panel). - malcontent (parental controls) Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Multiple default packages have libflatpak as a dependency, including malcontent (LP: #1892456). Security This will need a Security review. https://security-tracker.debian.org/tracker/source-package/flatpak There have been two CVEs, both have been fixed in all supported Ubuntu releases. More recently, there is LP: #1815528 Quality Assurance = Bug subscriber: should be Ubuntu Desktop Bugs https://bugs.launchpad.net/ubuntu/+source/flatpak https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=flatpak https://github.com/flatpak/flatpak/issues tests are run as build tests (with dh_auto_test) and installed autopkgtests on Debian and Ubuntu. https://ci.debian.net/packages/f/flatpak http://autopkgtest.ubuntu.com/packages/f/flatpak UI Standards N/A Dependencies All in main except for libostree-1-1 (LP: #1892454) Standards Compliance Package uses standards version 4.5.0. Maintenance === - Actively developed upstream https://github.com/flatpak/flatpak - Maintained in Debian by the pkg-utopia team but more specifically, it is maintained by Simon McVittie (smcv) who maintains Flatpak, ostree, xdg-dbus-proxy, xdg-desktop-portal and xdg-desktop-portal-gtk. short dh7 style rules, dh compat 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875796] Re: HP Envy 5530 printer/scanner does not work
I have one printer. It is a HP Envy 5530. I'm experiencing multiple issues. Sometimes CUPS finds printers, sometimes it doesn't. It auto-adds printers randomly. It auto-deletes printers randomly. One day the printer works, the next it does not. Also seeing these errors in syslog: Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=1, index=3 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface 7/1/4: Device or resource busy Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, iface=3, altset=0, index=9 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on interface=3 ret=0 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface ff/4/1: Device or resource busy Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 427: Found interface conf=0, iface=0, altset=0, index=11 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 389: Active kernel driver on interface=0 ret=0 Jun 9 12:42:14 yellow hp[34756]: io/hpmud/musb.c 515: invalid claim_interface ff/cc/0: Device or resource busy Jun 9 12:42:14 yellow hp[34756]: prnt/backend/hp.c 825: INFO: open device failed stat=21: hp:/usb/ENVY_5530_series?serial=CN57A5636Z05XT; will retry in 30 seconds... ** Attachment added: "Screenshot of duplicate printers in CUPS Find New Printers." https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+attachment/5503675/+files/screenshot-127.0.0.1_631-2021.06.09-12_38_33%281%29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1875796 Title: HP Envy 5530 printer/scanner does not work Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 20.04 LTS see troubleshoot.txt please ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 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: Wed Apr 29 08:15:00 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for ENVY_5530_series_CN4A5310HJ067B_: implicitclass://ENVY_5530_series_CN4A5310HJ067B_/ device for HP-ENVY-5530-series: hp:/usb/ENVY_5530_series?serial=CN4A5310HJ067B Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver Bus 001 Device 003: ID 03f0:c311 HP, Inc ENVY 5530 series Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-ENVY-5530-series.ppd', '/etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-ENVY-5530-series.ppd: Permission denied grep: /etc/cups/ppd/ENVY_5530_series_CN4A5310HJ067B_.ppd: Permission denied ProcEnviron: LANGUAGE=nl_BE:nl PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=77c5fdfc-4b0d-48ce-93d9-8aba51f17f9b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: Default string dmi.board.name: H110M-A/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd12/12/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-A/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1875796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
Another confirmation for the 9i. After set-verb.sh script my bass speaker is working. Thanks Hui Wang! You're such a helpful person. I've heard you've managed to fix a bunch of these, where people would just be frustrated for months and years without you. If you're ever in Pittsburgh, I'll buy you a beer or a dinner or whatever! Thanks again! -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@hui.wang is my hero! I can't wait to test this when I get home tonight! -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928475] Re: Xorg freeze when booting up
here is the file ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1928475/+attachment/5498299/+files/journal.txt -- 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/1928475 Title: Xorg freeze when booting up Status in xorg-server package in Ubuntu: Incomplete Bug description: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1928475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928590] [NEW] slow pc resposnisivnes when using multple programs
Public bug reported: sometimes when using multaple programs on Ubuntu 21 it causes some parts of Ubuntu to freeze up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 16 11:27:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute performance ubuntu wayland-session -- 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/1928590 Title: slow pc resposnisivnes when using multple programs Status in xorg package in Ubuntu: New Bug description: sometimes when using multaple programs on Ubuntu 21 it causes some parts of Ubuntu to freeze up. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 16 11:27:05 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias:
[Desktop-packages] [Bug 1928475] [NEW] Xorg freeze when booting up
Public bug reported: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute ubuntu wayland-session -- 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/1928475 Title: Xorg freeze when booting up Status in xorg package in Ubuntu: New Bug description: when booting up Ubuntu 21 it hangs for a few minutes then it becomes responsive it should not hang ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 10:42:48 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: I don't know GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2211] InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Hewlett-Packard HP 15 TS Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=c4c005df-0176-4582-a70b-d2a43dc51b21 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version:
[Desktop-packages] [Bug 1928407] [NEW] Screen not locked when coming out of suspend/hibernate
Public bug reported: when using my hp if my screen is a sleep and i wake it up it dosen't ask me for my password it should ask me i'm using Ubuntu 21 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:41:23 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1928407 Title: Screen not locked when coming out of suspend/hibernate Status in gnome-screensaver package in Ubuntu: New Bug description: when using my hp if my screen is a sleep and i wake it up it dosen't ask me for my password it should ask me i'm using Ubuntu 21 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:41:23 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1928407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928406] [NEW] [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume
Public bug reported: speaker audio is low compared to windows 10 the sound needs to be better optimized im using ubuntu 21 it should sound the same as in windows 10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: familypc 1345 F pulseaudio /dev/snd/controlC1: familypc 1345 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:31:32 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1928406 Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: speaker audio is low compared to windows 10 the sound needs to be better optimized im using ubuntu 21 it should sound the same as in windows 10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: familypc 1345 F pulseaudio /dev/snd/controlC1: familypc 1345 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:31:32 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Desktop-packages] [Bug 1001035] Re: lightdm uses a hardcoded path to .xsession-errors, please make it configurable
Any update on this? I'd love to move xsession-errors file out of my SSD
to minimize writes.
--
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/1001035
Title:
lightdm uses a hardcoded path to .xsession-errors, please make it
configurable
Status in Light Display Manager:
Triaged
Status in lightdm package in Ubuntu:
Triaged
Bug description:
LightDM uses always $HOME/.xsession-errors as the log file because is
harcoded in xsession.c. But sometimes you want to use a logfile
outside your $HOME, suposse your $HOME is in an SSD and you want to
minimize writes, so you want to put it in /tmp/${USER}_xsession-errors
for example. If you try to make a $HOME/.xsession_errors ->
/tmp/{$USER}_xsession-errors symlink to cheat LightDM, then LightDM
will recreate the $HOME/.xsession_errors file and the hack will not
work.
LightDM _always_ recreates $HOME/.xsession_errors and you can't change
it without recompiling. So, I think this log file needs to be
configurable, or at least preserve the symlink if one is present.
Ubuntu 12.04 LTS
LightDM 1.2.1-0ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1001035/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
https://cdraustralia.org/ provided hassle-free professional CDR Writing Services. I got my CDR professionally prepared on time. They offered me a detailed questionnaire relevant to my projects and prepared the Career Episodes Report and summary statements based on the information. Thanks to your team member. Well-done! -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918482] Re: Update for GHSA-xgh4-387p-hqpp
Hirsute now contains 1.10.2-1 with the fix, so I am marking it as fixed released. ** Changed in: flatpak (Ubuntu) Status: In Progress => Fix Released ** Description changed: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 + https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/share/applications/*.desktop (typically ~/.local/share/flatpak/exports/share/applications/*.desktop and /var/lib/flatpak/exports/share/applications/*.desktop) to make sure that literal filenames do not follow @@ or @@u. References Acknowledgements Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Update for GHSA-xgh4-387p-hqpp Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: In Progress Status in flatpak source package in Focal: In Progress Status in flatpak source package in Groovy: In Progress Bug description: [Links] https://github.com/flatpak/flatpak/security/advisories/GHSA-xgh4-387p-hqpp https://github.com/flatpak/flatpak/pull/4156 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984859 https://security-tracker.debian.org/tracker/CVE-2021-21381 [Impact] Versions in Ubuntu right now: Hirsute: 1.10.1-4 Groovy: 1.8.2-1ubuntu0.1 Focal: 1.6.5-0ubuntu0.2 Bionic: 1.0.9-0ubuntu0.2 Affected versions: >= 0.9.4 Patched versions: >= 1.10.2 [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all relevant architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Sandbox escape via special tokens in .desktop file (flatpak#4146) Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions. Impact By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app. A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required. Workarounds Avoid installing Flatpak apps from untrusted sources, or check the contents
[Desktop-packages] [Bug 1918482] [NEW] Placeholder for GHSA-xgh4-387p-hqpp
Public bug reported: Patches and description coming soon ! I need this to generate a LP bug number :-) ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: flatpak (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1918482 Title: Placeholder for GHSA-xgh4-387p-hqpp Status in flatpak package in Ubuntu: In Progress Bug description: Patches and description coming soon ! I need this to generate a LP bug number :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1918482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730612] Re: Enable Remote desktop feature during build
@jik, I think that you need the package gnome-remote-desktop, this has a MIR request in bug 1802614. And then another package will need to recommend it to have it installed by default, you can follow this on the Trello board here https://trello.com/c/NnUq5bHv/15-mir-gnome-remote- desktop-and-seed-recommend-it -- 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/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Fix Released Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793124]
Related meta: Bug 98754 Current ticket will celebrate 10th anniversary in a week -- 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/1793124 Title: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: I sometimes receive Calc documents where the content of an individual cell is split on so many lines that it fills up the whole screen and more. I can easily see the top part of these cells but scrolling to the bottom does not seem to work. Whether I try dragging the scrollbar or moving the screen with my laptop’s touchpad, Calc seems to skip the bottom part of the cell and jump directly to the following cell. See the attached screenshots of a document which has numbers 1 to 50 so that numbers 4 to 40 occupy one single cell (A4). In the first screenshot I see the top part of that cell (4 to 23) and in the next I have scrolled down the screen as little as possible, and now I see cell A5 (number 41) on the top. Everything in between is visually inaccessible whatever I try. Description: Ubuntu 18.04.1 LTS Release: 18.04 Installed: 1:6.0.3-0ubuntu1 Candidate: 1:6.0.3-0ubuntu1 Version table: *** 1:6.0.3-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-calc 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 18 11:16:17 2018 InstallationDate: Installed on 2017-02-13 (582 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913602] [NEW] Rendering of formatted cells is at odfds with Excel and Open Office
Public bug reported: I have been writing an .xlsx file using java POI from InteliJ. Rendering the sheet does not reflect the cell-styles which have been applied. The sheet is absolutely as expected in Excel (on Windows 10) and OpenOffice on Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Jan 28 14:42:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-08-18 (163 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-08-25 (155 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "peter.xlsx" https://bugs.launchpad.net/bugs/1913602/+attachment/5457770/+files/peter.xlsx -- 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/1913602 Title: Rendering of formatted cells is at odfds with Excel and Open Office Status in libreoffice package in Ubuntu: New Bug description: I have been writing an .xlsx file using java POI from InteliJ. Rendering the sheet does not reflect the cell-styles which have been applied. The sheet is absolutely as expected in Excel (on Windows 10) and OpenOffice on Ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice-calc 1:6.4.6-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu Jan 28 14:42:29 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-08-18 (163 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: libreoffice UpgradeStatus: Upgraded to focal on 2020-08-25 (155 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1913602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911473] Re: Update for ghsa-4ppf-fxf6-vxg2
1.8.5 has landed in hirsute now, so marking hirsute as fixed released. ** Changed in: flatpak (Ubuntu Hirsute) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1911473 Title: Update for ghsa-4ppf-fxf6-vxg2 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Bionic: New Status in flatpak source package in Focal: In Progress Status in flatpak source package in Groovy: New Status in flatpak source package in Hirsute: Fix Released Bug description: [Links] Upstream Advisory: https://github.com/flatpak/flatpak/security/advisories/GHSA-4ppf-fxf6-vxg2 Debian: https://security-tracker.debian.org/tracker/CVE-2021-21261 DSA: https://security-tracker.debian.org/tracker/DSA-4830-1 [Impact] Versions in Ubuntu right now: Hirsute: 1.8.4-2 Groovy: 1.8.2-1 Focal: 1.6.5-0ubuntu0.1 Bionic: 1.0.9-0ubuntu0.1 Affected versions: >= 0.11.4 and < 1.9.4, except for 1.8.x >= 1.8.5 Patched versions: Expected to be >= 1.9.4, 1.8.x >= 1.8.5 There are also branches with patches for 1.6.x (Ubuntu 20.04), but nothing available yet for 1.0.x (Ubuntu 18.04). [Test Case] No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests. [Regression Potential] Flatpak has a test suite, which is run on build across all architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak . Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak . Regression potential is low, and upstream is very responsive to any issues raised. [Other information] Simon McVittie discovered a bug in the flatpak-portal service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller- specified environment variables to non-sandboxed processes on the host system, and in particular to the flatpak run command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the flatpak run command, and use them to execute arbitrary code that is not in a sandbox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1911473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1684755] Re: Missing dependency to libtxc-dxtn-s2tc:amd64
Thank you for taking the time to report this bug and helping to make Ubuntu better. The package libtxc-dxtn-s2tc has been removed from later versions of Ubuntu, therefore I am going to mark this bug as invalid for Steam. ** Changed in: steam (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1684755 Title: Missing dependency to libtxc-dxtn-s2tc:amd64 Status in mesa package in Ubuntu: New Status in steam package in Ubuntu: Invalid Bug description: Steam is missing a dependency to libtxc-dxtn-s2tc:amd64 How to reproduce: - Install steam from the Ubuntu repositories - Use the mesa drivers - Download a game that requires GL_EXT_TEXTURE_COMPRESSION_S3TC (e.g. Dota 2) - Steam throws an error on game start Workaround: - Install libtxc-dxtn-s2tc:amd64 https://github.com/ValveSoftware/Dota-2/issues/1213 Release: Ubuntu 17.04 Package: steam:i386 (1:1.0.0.54+repack-2ubuntu5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1684755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873411] Re: steam installs generic Desktop icons for games that require an explicit 'Allow Launching'
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can reproduce this issue, but I think that is potentially a security feature of the gnome-shell-extension-desktop-icons. As if you navigate to the folder in Nautilus, then select open, it allows for running the game and not opening gedit. And I can see that the permissions of the file has been set correctly by Steam. Therefore I am going to reassign this bug from the Steam package to gnome-shell-extension-desktop-icons as it doesn't appear that Steam is doing anything incorrectly and it is likely due to the desktop icons implementation (potentially even a security feature). ** Package changed: steam (Ubuntu) => gnome-shell-extension-desktop- icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- 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/1873411 Title: steam installs generic Desktop icons for games that require an explicit 'Allow Launching' Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: The 1.0.0.61-2ubuntu3 steam package installs a steam which creates generic icons on the Desktop for games. These Desktop game icons open in gedit rather than launching when double clicked. One has to explicitly right-click on the icon and select 'Allow Launching' for the Desktop icons that steam creates upon game installation to become usable for launching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1873411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910613] [NEW] Crash of gnome shell potentially from "JS ERROR: too much recursion" from app indicators
Public bug reported: What Happened: 1) Have gnome-shell-extensions-appindicator enabled 2) The only running app using the indicator was charmtimetracker ( https://github.com/KDAB/Charm ) 3) At some point usually within 1-2 days of office usage gnome shell crashes 4) Notice "JS ERROR: too much recursion" and then a stacktrace coming from appindicator extension in journalctl What I expected to happen: For gnome-shell not to crash :-) Full logs: - Recursion warnings - https://pastebin.ubuntu.com/p/hfKMmH4Dpx/ - Stack trace - https://pastebin.ubuntu.com/p/2TC6WFVcsG/ Short Summary of Logs: === First sign of incoming crash === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: too much recursion set active@resource:///org/gnome/shell/ui/popupMenu.js:199:29 _init@resource:///org/gnome/shell/ui/popupMenu.js:104:18 _init@resource:///org/gnome/shell/ui/popupMenu.js:273:15 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:498:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === This continues many times, last instance is like this === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: JS ERROR: Exception in callback for signal: child-added: too much recursion PopupSubMenu@resource:///org/gnome/shell/ui/popupMenu.js:1017:9 _init@resource:///org/gnome/shell/ui/popupMenu.js:1201:21 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:494:29 createItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:520:60 === Then there is a stacktrace (shortened repeats) === Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: The offending signal was notify on StLabel 0x5615bd3eee80. Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: == Stack trace for context 0x56159bbee930 == Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #0 7ffca7535bb0 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:620 (1c7e392cc2e0 @ 100) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #1 7ffca7535c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:510 (1c7e392cae98 @ 357) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #2 5615a5c69340 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:771 (1c7e392cc880 @ 41) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #3 7ffca7536b70 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #4 7ffca7536c60 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #5 7ffca7536d70 b resource:///org/gnome/gjs/modules/core/_signals.js:133 (1c7e392a84c0 @ 427) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #6 5615a5c69290 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:134 (1c7e392c5c40 @ 74) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #7 7ffca7537c80 b /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:365 (1c7e392ca718 @ 837) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #8 5615a5c690d0 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:326 (1c7e392ca6a0 @ 423) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #9 7ffca7538970 b self-hosted:1013 (264b03e13e20 @ 492) Jan 05 17:59:01 MACHINE-NAME gnome-shell[3315]: #10 5615a5c69018 i resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2784371926a0 @ 312) Versions: $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 $ apt policy gnome-shell mutter gnome-shell-extension-appindicator gnome-shell: Installed: 3.36.4-1ubuntu1~20.04.2 Candidate: 3.36.4-1ubuntu1~20.04.2 Version table: *** 3.36.4-1ubuntu1~20.04.2 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages mutter: Installed:
[Desktop-packages] [Bug 1906744] Re: xdg-document-portal creates a mountpoint which produces an error report from df
*** This bug is a duplicate of bug 1905623 *** https://bugs.launchpad.net/bugs/1905623 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 1905623, 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 1905623 df: /run/user/1000/doc: Operation not permitted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1906744 Title: xdg-document-portal creates a mountpoint which produces an error report from df Status in xdg-desktop-portal package in Ubuntu: New Bug description: If I run "df" it starts with an error message: [parent]: df df: /run/user/4410/doc: Operation not permitted Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1630320 1604 1628716 1% /run . The /run/user/4410/doc (mode r-x--) has been created by: /usr/libexec/xdg-document-portal started by: /lib/systemd/systemd --user using: /usr/lib/systemd/user/xdg-document-portal.service I'm not sure why this is there, but i appear to have no control over it. It should not result in simple tools such as df producing error messages just because it exists. /proc/mounts shows it as: portal /run/user/4410/doc fuse.portal rw,nosuid,nodev,relatime,user_id=4410,group_id=1001 0 0 If it is a required mount then perhaps df should be made to ignore portal mounts by default? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xdg-desktop-portal 1.8.0-1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 4 02:09:11 2020 InstallationDate: Installed on 2020-05-03 (214 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to groovy on 2020-10-26 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1906744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897460] Re: VLC Snap Incompatible With Thunderbird
This bug report documents an incompatibility between the version of
Thunderbird distributed with Ubuntu 18.04 and the version of VLC. One or
the other must be changed so that a video attachment opened by
Thunderbird is accessible to the user's default video player, VLC.
** Changed in: gnome-software (Ubuntu)
Status: Expired => 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/1897460
Title:
VLC Snap Incompatible With Thunderbird
Status in gnome-software package in Ubuntu:
Confirmed
Bug description:
When I changed my default video player from Totem to VLC, Thunderbird
was no longer able to play an email message video attachment. By
default, Ubuntu Software installs the VLC snap package, whose
permission scheme prohibits it from accessing the directory where
Thunderbird saves the video file to be played (/tmp/mozilla_andy0).
VLC reports:
Your input can't be opened:
VLC is unable to open the MRL 'file:///tmp/mozilla_andy0/[VIDEO FILENAME]'.
Check the log for details.
To reproduce the bug:
1. Open a Thunderbird message.
2. Single left click on an attached video file handled by VLC.
3. VLC starts and then opens an error dialog with the above "Your
input can't be opened" message.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:68.10.0+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-1097.107-oem 4.15.18
Uname: Linux 4.15.0-1097-oem x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: andy 3256 F pulseaudio
/dev/snd/controlC1: andy 3256 F pulseaudio
/dev/snd/controlC0: andy 3256 F pulseaudio
BuildID: 20200629235513
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 27 07:25:42 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X59
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-10-28 (334 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
IpRoute:
default via 10.3.2.1 dev eno1 proto dhcp metric 100
10.3.2.0/24 dev eno1 proto kernel scope link src 10.3.2.3 metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
MostRecentCrashID: bp-9a0bd632-9768-4302-9c91-9f4f60200616
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-9a0bd632-9768-4302-9c91-9f4f60200616
bp-914925c7-43d8-44c0-a57a-4af430200101
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 0Y2K8N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0Y2K8N:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3630 Tower
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1897460/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3
** Changed in: flatpak (Ubuntu Groovy) Status: New => In Progress ** Changed in: flatpak (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1904640 Title: [SRU] [groovy] New upstream microrelease flatpak 1.8.3 Status in flatpak package in Ubuntu: Fix Released Status in flatpak source package in Groovy: In Progress Bug description: This is a request to SRU the latest release of flatpak into groovy. [Impact] New upstream release of flatpak, which brings fixes and improvements. Groovy is currently at 1.8.2, whereas 1.8.3 is available upstream. [Test Case] The bugs being resolved are not simple to reproduce, see the test plan below for testing flatpak itself. [Regression Potential] Flatpak has a test suite, which is run on build across all architectures and passes. There is also a manual test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak. I have confirmed that 1.8.3 passes with this test plan on groovy. Flatpak has autopkgtests enabled http://autopkgtest.ubuntu.com/packages/f/flatpak which is passing on groovy. Regression potential is low, and upstream is very responsive to any issues raised. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1904640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904640] [NEW] Placeholder for 1.8.3 update
Public bug reported: https://github.com/flatpak/flatpak/releases/tag/1.8.3 ** Affects: flatpak (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: flatpak (Ubuntu) Status: New => In Progress ** Changed in: flatpak (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1904640 Title: Placeholder for 1.8.3 update Status in flatpak package in Ubuntu: In Progress Bug description: https://github.com/flatpak/flatpak/releases/tag/1.8.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1904640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903706] Re: Add flathub repository by default
Thank you for taking the time to report this bug and helping to make Ubuntu better. The Ubuntu package of flatpak is synced from Debian, so any decision about whether to enable the flathub repository by default should be made there - as I do not want to create a delta between Ubuntu and Debian. Please report a bug against Debian if you think this should be the case, then once it is resolved the package will be synced in the latest Ubuntu development version. Furthermore the approach that Neon has used, by using a service, to enable flathub by default looks non-optimal, I think the preferred approach would be to use something like a drop in configuration file ( as described under custom installations here https://blogs.gnome.org/mclasen/2018/08/26/about-flatpak-installations/ ) - I am not sure if this only supports local repositories or could support flathub too though so it might need work. Until there is movement with Debian, I am going to mark this bug as "opinion". ** Changed in: flatpak (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1903706 Title: Add flathub repository by default Status in flatpak package in Ubuntu: Opinion Bug description: https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/debian/neon-settings-2.neon-flathub.service https://invent.kde.org/neon/neon/settings/-/blob/Neon/unstable/usr/lib/neon_update/neon_flathub.rb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1903706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901187] Re: Keyboard layout switch problem
Reproducible on desktop system (Lenovo Thinkstation S30) with Ubuntu 20.04.1 LTS with Gnome Shell 3.36.4-1ubuntu1~20.04.2. Steps: log in, physically unplug USB keyboard, plug it again. Keyboard switchers show the switching happens, but layout is not changing actually. It's also reproducible on Thinkpad X230 with exactly the same package versions. Keyboard is Logitech K780, same for both systems. I've also tried another keyboard (some A4Tech one), the problem is reproducible with it too. It's not reproducible for me with suspend and resume, only in the conditions mentioned above. Here is dmesg output from my system during keyboard plug/unplug. 65536.705683] logitech-hidpp-device 0003:046D:405B.0012: HID++ 4.5 device connected. [65584.128856] usb 3-1.3: USB disconnect, device number 3 [65588.703094] usb 3-1.3: new full-speed USB device number 4 using xhci_hcd [65588.814024] usb 3-1.3: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.10 [65588.814026] usb 3-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [65588.814027] usb 3-1.3: Product: USB Receiver [65588.814028] usb 3-1.3: Manufacturer: Logitech [65588.835398] logitech-djreceiver 0003:046D:C52B.0015: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-:07:00.0-1.3/input2 [65588.970091] input: Logitech K780 as /devices/pci:00/:00:1c.6/:07:00.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0015/0003:046D:405B.0016/input/input43 [65588.970364] logitech-hidpp-device 0003:046D:405B.0016: input,hidraw1: USB HID v1.11 Keyboard [Logitech K780] on usb-:07:00.0-1.3/input2:1 [65590.930221] logitech-hidpp-device 0003:046D:405B.0016: HID++ 4.5 device connected. Xorg.0.log [ 66212.318] (II) config/udev: removing device Logitech K780 [ 66212.318] (**) Option "fd" "84" [ 66212.322] (II) UnloadModule: "libinput" [ 66212.322] (II) systemd-logind: not releasing fd for 13:75, still in use [ 66212.322] (II) config/udev: removing device Logitech K780 [ 66212.322] (**) Option "fd" "84" [ 66212.322] (II) event11 - Logitech K780: device removed [ 66212.323] (II) UnloadModule: "libinput" [ 66212.324] (II) systemd-logind: releasing fd for 13:75 [ 66226.101] (II) config/udev: Adding input device Logitech K780 (/dev/input/event11) [ 66226.101] (**) Logitech K780: Applying InputClass "libinput keyboard catchall" [ 66226.101] (II) Using input driver 'libinput' for 'Logitech K780' [ 66226.102] (II) systemd-logind: got fd for /dev/input/event11 13:75 fd 84 paused 0 [ 66226.103] (**) Logitech K780: always reports core events [ 66226.103] (**) Option "Device" "/dev/input/event11" [ 66226.103] (**) Option "_source" "server/udev" [ 66226.105] (II) event11 - Logitech K780: is tagged by udev as: Keyboard [ 66226.105] (II) event11 - Logitech K780: device is a keyboard [ 66226.105] (II) event11 - Logitech K780: device removed [ 66226.105] (II) libinput: Logitech K780: needs a virtual subdevice [ 66226.105] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1c.6/:07:00.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0020/0003:046D:405B.0021/input/input46/event11" [ 66226.105] (II) XINPUT: Adding extended input device "Logitech K780" (type: MOUSE, id 8) [ 66226.106] (**) Option "AccelerationScheme" "none" [ 66226.107] (**) Logitech K780: (accel) selected scheme none/0 [ 66226.107] (**) Logitech K780: (accel) acceleration factor: 2.000 [ 66226.107] (**) Logitech K780: (accel) acceleration threshold: 4 [ 66226.108] (II) event11 - Logitech K780: is tagged by udev as: Keyboard [ 66226.109] (II) event11 - Logitech K780: device is a keyboard [ 66226.109] (**) Logitech K780: Applying InputClass "libinput keyboard catchall" [ 66226.109] (II) Using input driver 'libinput' for 'Logitech K780' [ 66226.109] (II) systemd-logind: returning pre-existing fd for /dev/input/event11 13:75 [ 66226.109] (**) Logitech K780: always reports core events [ 66226.109] (**) Option "Device" "/dev/input/event11" [ 66226.109] (**) Option "_source" "_driver/libinput" [ 66226.109] (II) libinput: Logitech K780: is a virtual subdevice [ 66226.109] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:1c.6/:07:00.0/usb3/3-1/3-1.3/3-1.3:1.2/0003:046D:C52B.0020/0003:046D:405B.0021/input/input46/event11" [ 66226.109] (II) XINPUT: Adding extended input device "Logitech K780" (type: KEYBOARD, id 9) [ 66226.109] (**) Option "xkb_model" "pc105" [ 66226.110] (**) Option "xkb_layout" "us" [ 66226.110] (WW) Option "xkb_variant" requires a string value [ 66226.110] (WW) Option "xkb_options" requires a string value The problem is not happening randomly, I was able to replicate it straight after reboot. Workaround is to restart gnome-shell with Alt-F2, then 'r'. I can provide additional information if needed. -- 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/1901187 Title: Keyboard layout switch problem
[Desktop-packages] [Bug 1900063] [NEW] Sync flatpak 1.8.2-3 (universe) from Debian sid (main)
Public bug reported: Please sync flatpak 1.8.2-3 (universe) from Debian sid (main) Changelog entries since current groovy version 1.8.2-2: flatpak (1.8.2-3) unstable; urgency=medium * d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch: Add proposed patch to skip parental controls if accountsservice is not installed. The malcontent package (which activates parental controls support) depends on accountsservice, but the libmalcontent-0-0 client library does not, so we need to cope gracefully with the case where neither malcontent nor accountsservice is installed. Presumably, in such installations the sysadmin did not want the parental controls feature. Ideally libmalcontent would do this itself (#972145). (Closes: #972138) * Add Depends on dbus, for the well-known system bus service. Now that the parental controls feature is enabled, Flatpak will refuse to run apps if the D-Bus system bus is unavailable. Previously, it would have partially worked (but with severely reduced functionality, in particular only --user installations). * d/control: Canonicalize case of Multi-Arch * Update lintian overrides to silence some false-positives -- Simon McVittie Thu, 15 Oct 2020 09:47:28 +0100 ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1900063 Title: Sync flatpak 1.8.2-3 (universe) from Debian sid (main) Status in flatpak package in Ubuntu: New Bug description: Please sync flatpak 1.8.2-3 (universe) from Debian sid (main) Changelog entries since current groovy version 1.8.2-2: flatpak (1.8.2-3) unstable; urgency=medium * d/p/Skip-parental-controls-checks-on-ServiceUnknown-or-NameHa.patch: Add proposed patch to skip parental controls if accountsservice is not installed. The malcontent package (which activates parental controls support) depends on accountsservice, but the libmalcontent-0-0 client library does not, so we need to cope gracefully with the case where neither malcontent nor accountsservice is installed. Presumably, in such installations the sysadmin did not want the parental controls feature. Ideally libmalcontent would do this itself (#972145). (Closes: #972138) * Add Depends on dbus, for the well-known system bus service. Now that the parental controls feature is enabled, Flatpak will refuse to run apps if the D-Bus system bus is unavailable. Previously, it would have partially worked (but with severely reduced functionality, in particular only --user installations). * d/control: Canonicalize case of Multi-Arch * Update lintian overrides to silence some false-positives -- Simon McVittie Thu, 15 Oct 2020 09:47:28 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1900063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897460] Re: VLC Snap Incompatible With Thunderbird
Matthew, thank you for properly identifying the responsible component of
Ubuntu 18.04 that prevents Thunderbird and VLC from interoperating.
"gnome-software" is more precise.
This is not a Thunderbird, VLC or snapd problem. This is an Ubuntu 18.04
application packaging issue. The problem is that Thunderbird saves a
temporary attachment file in /tmp before invoking a helper application
to open it. If the helper application associated with the file is VLC,
VLC does not have permission to open the file. (In fact, the system /tmp
directory is not even in the VLC snap's filesystem name space.)
The solution is to build and configuration VLC for this Ubuntu release
so that it shares its /tmp directory with the system /tmp directory,
i.e. they are one and the same.
--
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/1897460
Title:
VLC Snap Incompatible With Thunderbird
Status in gnome-software package in Ubuntu:
Incomplete
Bug description:
When I changed my default video player from Totem to VLC, Thunderbird
was no longer able to play an email message video attachment. By
default, Ubuntu Software installs the VLC snap package, whose
permission scheme prohibits it from accessing the directory where
Thunderbird saves the video file to be played (/tmp/mozilla_andy0).
VLC reports:
Your input can't be opened:
VLC is unable to open the MRL 'file:///tmp/mozilla_andy0/[VIDEO FILENAME]'.
Check the log for details.
To reproduce the bug:
1. Open a Thunderbird message.
2. Single left click on an attached video file handled by VLC.
3. VLC starts and then opens an error dialog with the above "Your
input can't be opened" message.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:68.10.0+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-1097.107-oem 4.15.18
Uname: Linux 4.15.0-1097-oem x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: andy 3256 F pulseaudio
/dev/snd/controlC1: andy 3256 F pulseaudio
/dev/snd/controlC0: andy 3256 F pulseaudio
BuildID: 20200629235513
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 27 07:25:42 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X59
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-10-28 (334 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
IpRoute:
default via 10.3.2.1 dev eno1 proto dhcp metric 100
10.3.2.0/24 dev eno1 proto kernel scope link src 10.3.2.3 metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
MostRecentCrashID: bp-9a0bd632-9768-4302-9c91-9f4f60200616
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-9a0bd632-9768-4302-9c91-9f4f60200616
bp-914925c7-43d8-44c0-a57a-4af430200101
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 0Y2K8N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0Y2K8N:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3630 Tower
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1897460/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897460] [NEW] VLC Snap Incompatible With Thunderbird
Public bug reported:
When I changed my default video player from Totem to VLC, Thunderbird
was no longer able to play an email message video attachment. By
default, Ubuntu Software installs the VLC snap package, whose permission
scheme prohibits it from accessing the directory where Thunderbird saves
the video file to be played (/tmp/mozilla_andy0). VLC reports:
Your input can't be opened:
VLC is unable to open the MRL 'file:///tmp/mozilla_andy0/[VIDEO FILENAME]'.
Check the log for details.
To reproduce the bug:
1. Open a Thunderbird message.
2. Single left click on an attached video file handled by VLC.
3. VLC starts and then opens an error dialog with the above "Your input
can't be opened" message.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:68.10.0+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-1097.107-oem 4.15.18
Uname: Linux 4.15.0-1097-oem x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: andy 3256 F pulseaudio
/dev/snd/controlC1: andy 3256 F pulseaudio
/dev/snd/controlC0: andy 3256 F pulseaudio
BuildID: 20200629235513
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 27 07:25:42 2020
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X59
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-10-28 (334 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary
20180608-09:38
IpRoute:
default via 10.3.2.1 dev eno1 proto dhcp metric 100
10.3.2.0/24 dev eno1 proto kernel scope link src 10.3.2.3 metric 100
169.254.0.0/16 dev eno1 scope link metric 1000
MostRecentCrashID: bp-9a0bd632-9768-4302-9c91-9f4f60200616
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:1141
PrefSources: prefs.js
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-9a0bd632-9768-4302-9c91-9f4f60200616
bp-914925c7-43d8-44c0-a57a-4af430200101
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/05/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 0Y2K8N
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3630Tower:pvr:rvnDellInc.:rn0Y2K8N:rvrA01:cvnDellInc.:ct3:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3630 Tower
dmi.sys.vendor: Dell Inc.
** Affects: thunderbird (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 thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1897460
Title:
VLC Snap Incompatible With Thunderbird
Status in thunderbird package in Ubuntu:
New
Bug description:
When I changed my default video player from Totem to VLC, Thunderbird
was no longer able to play an email message video attachment. By
default, Ubuntu Software installs the VLC snap package, whose
permission scheme prohibits it from accessing the directory where
Thunderbird saves the video file to be played (/tmp/mozilla_andy0).
VLC reports:
Your input can't be opened:
VLC is unable to open the MRL 'file:///tmp/mozilla_andy0/[VIDEO FILENAME]'.
Check the log for details.
To reproduce the bug:
1. Open a Thunderbird message.
2. Single left click on an attached video file handled by VLC.
3. VLC starts and then opens an error dialog with the above "Your
input can't be opened" message.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: thunderbird 1:68.10.0+build1-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-1097.107-oem 4.15.18
Uname: Linux 4.15.0-1097-oem x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: andy 3256 F pulseaudio
/dev/snd/controlC1: andy 3256 F pulseaudio
/dev/snd/controlC0: andy 3256 F pulseaudio
BuildID: 20200629235513
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 27 07:25:42 2020
DistributionChannelDescriptor:
# This is the
[Desktop-packages] [Bug 1896133] [NEW] [Audio Playback] right channel attenuated after random length of time
Public bug reported: After playing sound for a while (minutes, not seconds), the right channel will become attenuated. Restoring balance can be done by unplugging the headphones (from the built-in sound card) or disconnecting the external DAC and reconnecting it. Balance can be restored by altering balance in pavucontrol, but if you balance by increasing the right side volume, it introduces a lot of distortion. Same behavior observed using both the internal sound device as well as the Sound Blaster USB sound device, so it's in the mixing software somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 14:33:43 2020 InstallationDate: Installed on 2020-07-10 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+ Symptom_PulseAudioLog: Sep 15 15:45:31 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.29' (uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Sep 15 15:45:32 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:0 Sep 15 15:45:33 vmhost01 pulseaudio[2024]: No UCM verb is valid for hw:2 Sep 15 15:45:34 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.45' (uid=125 pid=2024 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Sep 15 19:01:54 vmhost01 dbus-daemon[1765]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.114' (uid=1000 pid=4820 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Sound Blaster MP3+, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2901:bd10/16/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1896133 Title: [Audio Playback] right channel attenuated after random length of time Status in alsa-driver package in Ubuntu: New Bug description: After playing sound for a while (minutes, not seconds), the right channel will become attenuated. Restoring balance can be done by unplugging the headphones (from the built-in sound card) or disconnecting the external DAC and reconnecting it. Balance can be restored by altering balance in pavucontrol, but if you balance by increasing the right side volume, it introduces a lot of distortion. Same behavior observed using both the internal sound device as well as the Sound Blaster USB sound device, so it's in the mixing software somewhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 14:33:43 2020 InstallationDate: Installed on 2020-07-10 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster MP3+ - Sound Blaster MP3+ Symptom_PulseAudioLog: Sep 15 15:45:31 vmhost01 dbus-daemon[1765]:
[Desktop-packages] [Bug 1892600] Re: pdfannotextractor launch script is missing "-jar" flag
Thanks for the link. Recent problems with pax seem to revolve around
pdfbox; however, the current packaging includes pdfbox, possibly to
avoid those problems.
Here is a patch that fixes the bug under discussion:
--- pdfannotextractor.pl2020-08-22 15:40:21.511195000 -0500
+++ pdfannotextractor.pl2020-08-22 16:19:31.196837000 -0500
@@ -186,6 +186,7 @@
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
+push @cmd, "-jar";
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1892600
Title:
pdfannotextractor launch script is missing "-jar" flag
Status in texlive-extra package in Ubuntu:
New
Bug description:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal
/texlive-latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use
the jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1892600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892600] [NEW] pdfannotextractor launch script is missing "-jar" flag
Public bug reported:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal/texlive-
latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use the
jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description:Ubuntu 20.04.1 LTS
Release:20.04
Codename: focal
** Affects: texlive-extra (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1892600
Title:
pdfannotextractor launch script is missing "-jar" flag
Status in texlive-extra package in Ubuntu:
New
Bug description:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal
/texlive-latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use
the jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1892600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 360970] Re: Multi-monitor - When using two displays with different vertical resolution, icons get lost on the shorter display
This bug is in 20.04 lts for me. Using Dell Precision with USB-C and
HDMI and Quadro T2000/PCIe/SSE2 / Quadro T2000/PCIe/SSE2 Display cards
Under settings, if I attach the external, the scalling goes out of wack.
Laptop screen scalling changes zooms out, while the external screen
scale zooms completely in. It's as if the adjustment is managing the
wrong screen. Even if I try scalling the external screen, the laptop
screen is impacted. Gotten to the point where I cannot use the external
screens. You know how it is with coding, really great to have external
screens to move stuff too. It's exactly like this
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/360970/+attachment/557624/+files/Screenshot-2.png
Not sure it's related to nautilus, but you'd probably know better. It's
as if the usb-c and hdmi ports are not getting the right signals. Also
HDMI and USB-C can cause the OS to hang if I pull it in and out quickly.
That area of 20.04 screen management setting is quite buggie for me.
Hope you're able to address it soon as I really miss my external
monitors.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/360970
Title:
Multi-monitor - When using two displays with different vertical
resolution, icons get lost on the shorter display
Status in Ayatana Design:
Fix Committed
Status in Nautilus:
Expired
Status in Unity:
Confirmed
Status in nautilus package in Ubuntu:
Triaged
Bug description:
On a Multi-Monitor setup, where the extended desktop is non-
rectangular in shape (ie. the displays are of a different resolution,
and their top/bottom/left/right edges are not aligned), desktop icons
are placed in non-accessible areas when arranged using the menu option
'View-Organise Desktop by Name' from the Desktop.
See the attached image. The top three desktop items are not
accessible, and can only be seen in the Workspace Switcher.
Please also refer to the 'Non-Rectangular Extended Desktops' section of the
Multi-Monitor spec:
https://docs.google.com/a/canonical.com/document/d/1aHvJ-iIw-59bXTYBmIhQqEx0za2h9jpFE_RhZ2VOvJc/edit#bookmark=id.yph05n82oeff
--
[Test Case]
1. Set up two monitors side by side
2. Set left monitor to a smaller vertical resolution than the right monitor
3. for i in $(seq 1 50) ; do touch file-${i} ; done
4. Right click on desktop to bring up context menu, then 'Organize Desktop by
Name'
5. Should be: All icons from file-1 to file-50 (or as many fit on the screen)
should be visible
Is: Icons for files at the top and/or bottom of the arranged columns are
not visible on any display
6. xrandr --output LVDS1 --off
7. Verify icons are arranged properly on the external monitor
8. Set up monitors one over the other
9. Verify icons are displayed in long columns spanning both displays with all
icons shown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/360970/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box
I am experiencing this in Ubuntu 20.04. I have not subscribed to pre-released updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1588197 Title: Can't type anything in search box Status in evince package in Ubuntu: Invalid Bug description: Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer. Clicking search button or CTRL+F shows search box, but I can't type anything inside. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772683] Re: [snap] Cannot sign a document, gpg keys are not listed
I've discovered that this bug affects the non-snap version of libreoffice on focal too. https://listarchives.libreoffice.org/global/users/msg54820.html suggests that the problem is likely within the apparmor profile - and that apparmor is preventing libreoffice from accessing .gnupg but I have not attempted to change the profile to see if this fixes things. -- 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/1772683 Title: [snap] Cannot sign a document, gpg keys are not listed Status in LibreOffice: Won't Fix Status in libreoffice package in Ubuntu: Triaged Bug description: (initially reported on the forum: https://forum.snapcraft.io/t /libreoffice-snap-missing-features-and-known-bugs/3920/10) Libreoffice 6.0.4.2 (64, candidate channel). Steps to reproduce: 1) snap run libreoffice.writer 2) write something, then save the document (anywhere) on disk 3) Open the File menu, then Digital Signatures > Digital Signatures… 4) in the dialog, click "Sign Document…" Expected result: your GPG keys are listed Current result: no keys are listed To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1770783] Re: Noto emoji should provide a fontconfig file to prioritize emoji fonts
The problem is not Noto Color Emoji's fault - the problem lies in DejaVu Sans providing emoji glyphs. These need to be removed or at least separated out from the standard DejaVu Sans and DejaVu Monospace fonts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1770783 Title: Noto emoji should provide a fontconfig file to prioritize emoji fonts Status in fonts-noto-color-emoji package in Ubuntu: Invalid Bug description: In order to get the emoji font to work in various apps (including chrome and electron based) the font should provide a fontconfig file to priotitize these fonts serif Noto Color Emoji sans-serif Noto Color Emoji monospace Noto Color Emoji Is what I've in ~/.config/fontconfig/conf.d/01-emoji.conf and that should instead be provided in /usr/share/fontconfig/conf.avail/01 -emoji-default.conf or similiar ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: fonts-noto-color-emoji 0~20180424-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 12 02:42:21 2018 Dependencies: InstallationDate: Installed on 2010-07-10 (2862 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) PackageArchitecture: all SourcePackage: fonts-noto-color-emoji UpgradeStatus: Upgraded to bionic on 2012-10-10 (2039 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1770783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
I'm new on here - sorry for any mistakes. I didn't know if it's worth adding, or where to add... that after I got this crash, I closed everything (and had my Android plugged in and mounted, but ejected it) and rebooted. Now, when I plug my phone back in, it makes the little alert noise, but I cannot find my phone drive. It doesn't show up in Files like it did last time, even when I click "other locations". (Files was what I was using to look at the phone files before the reboot) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879580] Re: Screencast interface missing
Thank you for taking the time to report this bug and helping to make Ubuntu better. Note that this requires pipewire support to be enabled in mutter and xdg-desktop-portal, which are both in main, which then means pipewire needs to be in main (see bug 1802533). I believe this is what is blocking https://salsa.debian.org/debian/xdg-desktop-portal/-/blob/debian/master/debian/rules#L8 from being set to --enable-pipewire. Also note that pipewire 0.3 is needed for GNOME Shell 3.36, which isn't packaged in Debian or Ubuntu yet ( see https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=954022 ). Once these are sorted then I guess potentially -Dremote_desktop=false could be set to true here as well https://salsa.debian.org/gnome- team/mutter/-/blob/debian/master/debian/rules#L33 ** Bug watch added: Debian Bug tracker #954022 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954022 ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1879580 Title: Screencast interface missing Status in xdg-desktop-portal package in Ubuntu: Confirmed Bug description: The `org.freedesktop.portal.ScreenCast` inferface is missing in the version shipped with Ubuntu 20.04. This interface is needed for OBS no work in non-X11 environments. Further reading: https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.portal.ScreenCast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1879580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Exact same here with a GTX 760. Arranging in a "L" shape as mentioned here works: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/974#note_783569 -- 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/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash 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/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
This copy/paste is also an Ubuntu 20.04 bug in wine 4 and 5 running Lotus Approach -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876487] Re: The screen is blinking at a random time
It looks like visual bell goes crazy (but I'm not sure in that). And yes, I love visual bell and usually do enable visual bell instead of audio bell. -- 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/1876487 Title: The screen is blinking at a random time Status in xorg package in Ubuntu: New Bug description: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9427d12e-3c69-4eb4-aa23-52bfe8bd2641 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 0T0V7J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn0T0V7J:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1876487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876487] [NEW] The screen is blinking at a random time
Public bug reported: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=9427d12e-3c69-4eb4-aa23-52bfe8bd2641 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.3 dmi.board.name: 0T0V7J dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:svnDellInc.:pnLatitudeE7270:pvr:rvnDellInc.:rn0T0V7J:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7270 dmi.product.sku: 06DB dmi.sys.vendor: Dell Inc. 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/1876487 Title: The screen is blinking at a random time Status in xorg package in Ubuntu: New Bug description: I've seen this error on Dell Latitude E7270 (with an internal video card) as well as Dell Precision 7540 (with NVidia card). I've seen this error on Ubuntu 18.04 and now on 20.04 I've never reported it yet but I think the time has come. In a random time (~ once a couple of weeks) I see a blinking screen. Today I've recorded a video on my phone to show you how it looks. You can see it here: https://youtu.be/JiUu7Ydg6uM This is bug finishes when I do logout from my desktop. Could you help me eliminate this error? 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 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 2 19:28:27 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-21-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-25-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-26-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06db] InstallationDate: Installed on 2020-04-09 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude E7270 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
I think it has a bigger impact. I have noticed that while trying to log in, some keys don't work. Is this restricted to only the cntr-c and cntrl-v? Strange behaviour when some keys don't seem to register. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
Looking forward to this one being deployed. Really love my Ubuntu and 20.40 -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
Bug impacts cntl-c and and cntrl-v between txt documents and the terminal. It's intermittent as I can copy sometime. There is the strange effect if I am in the terminal and copy from the browser. Occasionally it copies text to the window I am not on. I'm surprised its not effecting more people. Really impact my productivity. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872681] [NEW] Overview shortcut does not work on non-latin keyboard layout
Public bug reported: Hello, Latest Ubuntu 20.04. After latest upgrade the shortcut key for the Overview (Expose?) function doesn't work on non-latin keyboard layout: 1. Switch current input language to Russian 2. Press Super key. 3. Nothing happens 4. Switch language to English 5. Press Super key 6. Windows overview screen is opened /usr/bin/xev reports the same keyscan for the button, if that matters. Other Super- shortcuts (like Super-`) do work in any keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 13:00:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (124 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1872681 Title: Overview shortcut does not work on non-latin keyboard layout Status in gnome-shell package in Ubuntu: New Bug description: Hello, Latest Ubuntu 20.04. After latest upgrade the shortcut key for the Overview (Expose?) function doesn't work on non-latin keyboard layout: 1. Switch current input language to Russian 2. Press Super key. 3. Nothing happens 4. Switch language to English 5. Press Super key 6. Windows overview screen is opened /usr/bin/xev reports the same keyscan for the button, if that matters. Other Super- shortcuts (like Super-`) do work in any keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 13:00:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (124 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872681/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1393502] Re: [MacBookPro11, 3, Cirrus Logic CS4208, Pink Mic] Combo jack not recognized.
I am also experiencing this issue, MacbookPro11,5 -- 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/1393502 Title: [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic] Combo jack not recognized. Status in alsa-driver package in Ubuntu: Confirmed Bug description: New Macbook comes with a four-conductor TRRS jack for headset. With headset plugged in the microfone is recognized on Mac os-x. Ubuntu recognizes the external headphones but not the microphone. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikaelb2403 F pulseaudio /dev/snd/controlC0: mikaelb2403 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 17 18:58:35 2014 InstallationDate: Installed on 2014-10-20 (28 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Pink Mic, N/A Symptom_Type: No auto-switch between inputs Title: [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic, N/A] No autoswitch UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2014 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B07.1402121134 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-11-10T22:25:45.211791 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1393502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870868] [NEW] No close button for Disks window
Public bug reported: When opening Disks in Gnome, there is no close button for the window. Must use context menu from the icon in the dock to select 'Quit' to close the window. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Attachment added: "Screenshot showing lack of close button" https://bugs.launchpad.net/bugs/1870868/+attachment/5346835/+files/Screenshot%20from%202020-04-05%2013-04-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1870868 Title: No close button for Disks window Status in gnome-disk-utility package in Ubuntu: New Bug description: When opening Disks in Gnome, there is no close button for the window. Must use context menu from the icon in the dock to select 'Quit' to close the window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1870868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870865] Re: Firefox background update 74.0 to 74.0.1 prevents using any active tab
$uname -a
Linux {host} 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"
--
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/1870865
Title:
Firefox background update 74.0 to 74.0.1 prevents using any active tab
Status in firefox package in Ubuntu:
New
Bug description:
I opened several new tabs via context menu, then when switching to one
of those new tabs was presented with the "Firefox must be restarted to
continue" type message when an update had been applied in the
background. On attempt to switch back to an already active tab in
order to securely close existing site sessions, form submissions, etc.
before restarting Firefox, I found that I was unable to use existing
tabs.
Problem presented as the newly opened tab was not rendering any page
(completely white). Clicking any existing tab would not switch from
the newly opened tab. Clicking on "help - troubleshooting information"
and "help - submit feedback" opened those tabs in the background but
alas was not able to switch to those tabs to view them.
I think this is a bug and user should be able to continue to use
existing tabs to complete their existing sessions when a Firefox
background update has been applied.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870865/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870865] [NEW] Firefox background update 74.0 to 74.0.1 prevents using any active tab
Public bug reported: I opened several new tabs via context menu, then when switching to one of those new tabs was presented with the "Firefox must be restarted to continue" type message when an update had been applied in the background. On attempt to switch back to an already active tab in order to securely close existing site sessions, form submissions, etc. before restarting Firefox, I found that I was unable to use existing tabs. Problem presented as the newly opened tab was not rendering any page (completely white). Clicking any existing tab would not switch from the newly opened tab. Clicking on "help - troubleshooting information" and "help - submit feedback" opened those tabs in the background but alas was not able to switch to those tabs to view them. I think this is a bug and user should be able to continue to use existing tabs to complete their existing sessions when a Firefox background update has been applied. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Attachment added: "Firefox Troubleshooting Information output" https://bugs.launchpad.net/bugs/1870865/+attachment/5346821/+files/firefox-prevents-switching-tabs-troubleshooting-information.txt -- 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/1870865 Title: Firefox background update 74.0 to 74.0.1 prevents using any active tab Status in firefox package in Ubuntu: New Bug description: I opened several new tabs via context menu, then when switching to one of those new tabs was presented with the "Firefox must be restarted to continue" type message when an update had been applied in the background. On attempt to switch back to an already active tab in order to securely close existing site sessions, form submissions, etc. before restarting Firefox, I found that I was unable to use existing tabs. Problem presented as the newly opened tab was not rendering any page (completely white). Clicking any existing tab would not switch from the newly opened tab. Clicking on "help - troubleshooting information" and "help - submit feedback" opened those tabs in the background but alas was not able to switch to those tabs to view them. I think this is a bug and user should be able to continue to use existing tabs to complete their existing sessions when a Firefox background update has been applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870865] Re: Firefox background update 74.0 to 74.0.1 prevents using any active tab
Added screenshot that was taken while experiencing the issue ** Attachment added: "Screenshot of Firefox 74" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870865/+attachment/5346822/+files/Screenshot%20from%202020-04-05%2012-32-08.png -- 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/1870865 Title: Firefox background update 74.0 to 74.0.1 prevents using any active tab Status in firefox package in Ubuntu: New Bug description: I opened several new tabs via context menu, then when switching to one of those new tabs was presented with the "Firefox must be restarted to continue" type message when an update had been applied in the background. On attempt to switch back to an already active tab in order to securely close existing site sessions, form submissions, etc. before restarting Firefox, I found that I was unable to use existing tabs. Problem presented as the newly opened tab was not rendering any page (completely white). Clicking any existing tab would not switch from the newly opened tab. Clicking on "help - troubleshooting information" and "help - submit feedback" opened those tabs in the background but alas was not able to switch to those tabs to view them. I think this is a bug and user should be able to continue to use existing tabs to complete their existing sessions when a Firefox background update has been applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1870865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
My issue has been marked as duplicate of https://gitlab.gnome.org/GNOME /gnome-shell/issues/2255 which is already fixed 1 week ago. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2255 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2255 -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
Could some one please test it and confirm? Just disable animation and then lock the screen. That might be my local issue. -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
HI, That was my first thought. However, Focal repo does not provide the latest GNOME Shell version, that it might have been already fixed. So i decided to report here first. So i'll report it now. -- 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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
lcipcik data ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+attachment/5334235/+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/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking Status in gnome-shell package in Ubuntu: New Bug description: Dear Ubuntu Team, I'm using the latest Ubuntu 20 focal, update it every day. After some of the upgrades something happened and screenlock and other dialogs became broken (i'll describe below). It was very hard to find what caused this (i reset all keys in dconf one by one and restarted) and finally i found it: /org/gnome/desktop/interface/enable-animations My animations were disabled (they are slow even on supertop hardware). So the problem is: it seems that new GNOME 3.36 lock screen and other dialogs like "Ask for a root password" rely on animations and without it they do not work or work incorrectly/insecure. 1. Screenlock can lock a screen without any problem. When i try to unlock it and click by mouse/key, i except a dialog with password prompt to appear. However, instead of the dialog Screenlock just shows my screen and running applications with all my data, for some time. Then it again locks the screen. I can repeat this as many times as i want and steal all the information. See the attached video, you will see the dconf-editor running. Sorry for the video quality. The only way to unlock the screen is to click an icon at the bottom- right "Change user". Then i get a list of users, can choose myself and type a password. 2. Other dialogs like asking for a root password (when it's required to run an application under root), just do not appear. Screen blinks and that's all. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 23:32:51 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (85 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
I believe this issue is because we now show pending snap updates in gnome-software (useful when one has manually set the refresh timer), which causes them to be categorised as "updatable live". gnome-software then has an update monitor that automatically tries to apply any updatable live apps (which causes the polkit dialogs and updates complete notifications) - but we don't want this as snapd does this. I have an untested patch here https://gitlab.gnome.org/ahayzen/gnome- software/commit/0597be6f317a38aa64ac86280d7b05a1aa242a70 which I believe should disable snap app updates from the update monitor. If it looks good let me know and I can proposed it against gnome- software master :-) -- 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/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages Status in gnome-software package in Ubuntu: New Bug description: Every morning about ~30mins after powering on my focal machine I get (unprompted) a gnome-shell policykit authorisation popup saying 'authentication is required to install software' - I haven't yet actually authorised it since I wasn't sure what was causing it, however I notice that if I cancel the authorisation then I see a bunch of notifications from gnome-software about updates having been successfully installed (even though I presume it hasn't been since I never authorised it). Is gnome-software fighting snapd to refresh snaps? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 21:37:29 2020 InstallationDate: Installed on 2019-11-18 (79 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-01-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
