[Desktop-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libevdev in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: Fix Released Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in libevdev source package in Bionic: Fix Released Status in libinput source package in Bionic: Fix Released Status in libevdev source package in Focal: Fix Released Status in libinput source package in Focal: Fix Released Status in libevdev source package in Groovy: Fix Released Status in libinput source package in Groovy: Fix Released Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 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 To
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
*** This bug is a duplicate of bug 1797002 *** https://bugs.launchpad.net/bugs/1797002 Bug 1797002 is still open. We don't consider it resolved so this is now a duplicate of that. Yes you are free to delete any attachments from this bug that you wish. In future if you are concerned about the privacy of attachments you can mark your bugs as Private at the top-right of the page. Then only a very small team of bug reviewers will be able to see them. ** This bug has been marked a duplicate of bug 1797002 Bluetooth audio skips while the settings dialog is open -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
I will be deleting all attachments, unless you think any of them are strictly necessary? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
Thanks for the suggestions. Closing the settings window makes the problem disappear. Good call. Unlike the reporter in the linked bug I wouldn't exactly call that a "solution" (and certainly not "simple") since there is very little chance I would consider closing the settings window before confirming that the speaker works properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
** Tags removed: fixed-in-gnome-shell-40 ** Tags added: fixed-in-gnome-shell-3.38.2 -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Groovy: Triaged Status in gnome-shell-extension-desktop-icons source package in Groovy: In Progress Status in gnome-shell source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from Des
** Tags added: fixed-in-3.38.2 fixed-upstream -- 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/1898910 Title: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206] Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Triaged Status in gnome-shell-extension-desktop-icons source package in Groovy: Confirmed Status in gnome-shell source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Confirmed Bug description: https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 --- Ubuntu on Wayland crashes when you try to change the resolution even if your display supports the Version: 3.38.0-1ubuntu2 Release: 20.10 Groovy Gorilla (development branch) What I expected to happen 1. Login to Wayland 2. Change the resolution 3. Go on with my day What actually happened 1. Login to Wayland 2. Change the resolution 3. Wait a minute to get kicked to the gdm login screen 4. Now I am here. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 12:55:35 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908111] Re: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel
mesa-libgl-devel is not from Ubuntu ** Changed in: libglvnd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1908111 Title: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 Status in libglvnd package in Ubuntu: Invalid Bug description: Just impossible to install. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgl-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: libx11-dev:amd64: Install libglx-dev:amd64: Install libgl-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 19:03:55 2020 ErrorMessage: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 InstallationDate: Installed on 2020-11-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libglvnd Title: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1908111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908164] Re: Impossible to get screenshot of fullscreen games
** Tags added: groovy hirsute -- 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/1908164 Title: Impossible to get screenshot of fullscreen games Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] When I screenshot (by pressing PrintScreen button) pretty much any game (non-game applications like Chromium or VLC don't have this issue) that renders in fullscreen (Vulkan or OpenGL), screenshots always come out completely blank and transparent. [ Test case ] Run a game full-screen, hit Print Screen to get a screenshot: - Expect the screenshot to be saved in the picture folders and to contain the game screen [ Regression potential ] Screenshots on X11 might cause a bit more resources and could be taken with some delay. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6/3.36.7
** Summary changed: - SRU 3.36.6 + SRU 3.36.6/3.36.7 ** Changed in: gnome-shell (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Invalid -- 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/1896334 Title: SRU 3.36.6/3.36.7 Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: In Progress Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903230] Re: Mutter release 3.36.7
** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Status: New => In Progress ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => Medium ** No longer affects: mutter (Ubuntu Bionic) -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Focal: In Progress Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886592] Re: Add support for VMware Horizon SSO to gnome-shell
** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1886592 Title: Add support for VMware Horizon SSO to gnome-shell Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Eoan: Won't Fix Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell source package in Groovy: Fix Released Bug description: [Impact] VMware Horizon is a VDI product that runs atop of VMware's normal virtualisation stack, and it supports SSO authentication for login. In the past, the VMware Horizon agent has been pretty buggy, and requires SSO patches to be present to function, otherwise it breaks and causes entire outages for anyone trying to use the VDI. To solve this, VMware had been custom compiling their own libgnome- shell.so libraries with their SSO patches, which are based on oVirt's SSO implementation. When you install VMware Horizon agent to the instance, it overwrites Ubuntu's libgnome-shell.so with their custom compiled one. VMware don't keep their custom compiled libgnome-shell.so library up to date, so bugs that have already been fixed still live on in their library. Also, when Ubuntu updates our gnome-shell packages, it overwrites the custom libgnome-shell.so library, which then causes the Horizon agent to break, and causes outages for anyone using the VDI, which have to be solved by manually copying the custom library back. This situation is untenable for VMware Horizon users, so I have asked VMware to upstream their SSO patches. After a long painful process, they have landed in gnome-shell master. This SRU will significantly improve the quality of life for VMware Horizon users, and will remove the need for VMware to distribute custom libraries. [Testcase] You need an instance that runs on VMware Horizon, and the Horizon agent needs to be installed and running. Ideally, SSO authentication should be enabled to test all features, but it is not necessary to partially test. Test packages are available in this ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf247978-test If you install the test package in a VMware Horizon VDI, the instance should come up cleanly after reboot and function properly, especially with SSO login. The instance should be able to function without custom libgnome- shell.so libraries provided by VMware. [Regression Potential] The code refactors the oVirt SSO implementation into a more generalised interface, which other virtualisation platforms can use. oVirt has been transitioned to this interface as part of the refactoring, which means that any if the new oVirt SSO implementation is broken, it could break users running in oVirt. VMware's patches also use the new generalised interface, which is much simpler than before, and it has been tested internally by VMware. There was a very long review process with upstream GNOME, which ironed out all of their concerns. I have been reviewing the code along the way, and I am confident that it will not cause any regressions. If a regression did occur, then it would break SSO functionality only. [Other Information] Upstream Issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1983 Upstream merge-request: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/915 Commits: commit 809f820cd4a4eebb120ab5dde3f1985d35bcb540 Author: yun341 <5933...@qq.com> Date: Sat, 4 Jan 2020 00:31:15 +0800 Subject: gdm: Refactor oVirt to a generic CredentialManager interface Link: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/809f820cd4a4eebb120ab5dde3f1985d35bcb540 commit 4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5 Author: yun341 <5933...@qq.com> Date: Thu, 2 Jul 2020 06:54:55 +0800 Subject: gdm: Introduce vmware credential manager for pre-authenticated logins Link: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/4ea0fca4fc09ffd6e0b6994ee1354f07f7d5d2b5 commit 00437750ed9c7e0982854e20be8c36c6bda7b254 Author: Andre Moreira Magalhaes Date: Mon Aug 17 18:41:04 2020 -0300 Subject: authPrompt: Properly get oVirt service name Link: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/00437750ed9c7e0982854e20be8c36c6bda7b254 commit 3fb321fd214469130539e1e31461257a749bff21 Author: yun341 <5933...@qq.com> Date: Mon Sep 21 22:11:41 2020 +0800 Subject: authPrompt: set value of beginRequestType to 'DONT_PROVIDE_USERNAME' Link: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/3fb321fd214469130539e1e31461257a749bff21 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1886592/+subscriptions --
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
Also seeing this on 20.10. Same workaround works. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908187] [NEW] Taking a screenshot during a game may lead to crash
Public bug reported: [ Impact ] A screenshot of the Left 4 Dead 2 or Garry's Mod window causes the gnome-shell to terminate the user's session. [ Test case ] - Launch a game (Left 4 Dead 2 or Garry's Mod) - Open GNOME Screenshot app - Set "Window" in Capture Area menu and "Delay in Seconds" to 2-3 seconds - Alt-tab (or switch by Super key) to an open game - GNOME Screenshot app terminates the user session with an error "something went wrong". [ Regression potential ] No screenshot may be taken when requested ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gnome-shell (Ubuntu Bionic) Importance: Low Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3258 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3258 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3258 Importance: Unknown Status: Unknown -- 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/1908187 Title: Taking a screenshot during a game may lead to crash Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [ Impact ] A screenshot of the Left 4 Dead 2 or Garry's Mod window causes the gnome-shell to terminate the user's session. [ Test case ] - Launch a game (Left 4 Dead 2 or Garry's Mod) - Open GNOME Screenshot app - Set "Window" in Capture Area menu and "Delay in Seconds" to 2-3 seconds - Alt-tab (or switch by Super key) to an open game - GNOME Screenshot app terminates the user session with an error "something went wrong". [ Regression potential ] No screenshot may be taken when requested To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908187/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
[Expired for nvidia-graphics-drivers-435 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Incomplete => Expired -- 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/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898603] Re: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1898603 Title: Kernel Ubuntu 5.4.0-48.52-generic sound broken - headphones detected as output, not speakers Status in alsa-driver package in Ubuntu: Expired Bug description: Starting in Kernel 5.4.0-48-generic on Mint Linux 20 Cinnamon my sound output is detected as "headphones" instead of Speakers when this laptop doesn't even have any headphones connected at all... reverting to a prior kernel fixes the problem and then the output is correctly Speakers... I cannot possibly use sound on Kernel 5.4.0-48-generic and the Mint Linux support chat said I should file a bug for this because this kernel broke something. See attached detailed log reports for more info... Thanks team!!! Best Regards, -Avery Tarasov --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chr0meice2 2656 F pulseaudio /dev/snd/controlC0: chr0meice2 2656 F pulseaudio /dev/snd/pcmC0D0c: chr0meice2 2656 F...m pulseaudio /dev/snd/pcmC0D0p: chr0meice2 2656 F...m pulseaudio CasperMD5CheckResult: skip DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-10-05 (0 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 NonfreeKernelModules: nvidia_modeset nvidia Package: alsa-driver (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: ulyana Uname: Linux 5.4.0-48-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899766] Re: Xorg freeze after selecting large cursor
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1899766 Title: Xorg freeze after selecting large cursor Status in nvidia-graphics-drivers-435 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: After selecting the largest cursor in accessibility settings, the whole system froze. I had to use Magic SysRq to reboot the system. After reboot, the login screen was OK but after logging in it would immediately freeze again. Workaround: from login screen, switch to a VT with Ctrl-F2, log in and run dconf reset /org/gnome/desktop/interface/cursor-size I was playing with the cursor size because I see different cursor sizes in different apps and it was annoying me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_48_52_generic_72 nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 11:25:23 2020 DistUpgraded: 2020-05-02 16:08:06,720 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2018-12-11 (672 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-02 (164 days ago) dmi.bios.date: 07/09/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd07/09/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1899766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899798] Re: Gnome Activities overview broken
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1899798 Title: Gnome Activities overview broken Status in gnome-shell package in Ubuntu: Expired Bug description: Steps to reproduce: open the Gnome activities view via Super key Actual result: I can not choose any application in the overview Expected result: Switching apps on activities overview works. My system is: * Ubuntu 20.04.1 LTS * NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] * Gnome 3.36.3 * Display server: X11 I tried to change betwheen nvidia-driver-450 and xserver-xorg-video-nouveau (with logout/login after switch), but no success. Here is the list of packages which where updated beforehand: 2020-10-14 07:17:51 upgrade cheese-common:all 3.34.0-1build1 3.34.0-1ubuntu1 2020-10-14 07:17:51 upgrade file-roller:amd64 3.36.2-0ubuntu1 3.36.3-0ubuntu1 2020-10-14 07:17:51 upgrade libcheese8:amd64 3.34.0-1build1 3.34.0-1ubuntu1 2020-10-14 07:17:51 upgrade libcheese-gtk25:amd64 3.34.0-1build1 3.34.0-1ubuntu1 2020-10-14 07:17:51 upgrade libinput-bin:amd64 1.15.5-1 1.15.5-1ubuntu0.1 2020-10-14 07:17:52 upgrade libinput10:amd64 1.15.5-1 1.15.5-1ubuntu0.1 2020-10-14 07:17:52 upgrade nvidia-driver-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:17:52 upgrade libnvidia-extra-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:17:52 upgrade libnvidia-common-450:all 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:17:52 upgrade libnvidia-gl-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:17:56 upgrade libnvidia-gl-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:17:57 upgrade nvidia-dkms-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:00 upgrade nvidia-kernel-source-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:01 upgrade nvidia-kernel-common-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:01 upgrade libnvidia-decode-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:01 upgrade libnvidia-decode-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:02 upgrade libnvidia-compute-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:03 upgrade libnvidia-compute-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:04 upgrade nvidia-compute-utils-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade libnvidia-encode-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade libnvidia-encode-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade nvidia-utils-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade xserver-xorg-video-nvidia-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade libnvidia-ifr1-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:05 upgrade libnvidia-ifr1-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:06 upgrade libnvidia-fbc1-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:06 upgrade libnvidia-fbc1-450:i386 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:06 upgrade libnvidia-cfg1-450:amd64 450.66-0ubuntu0.20.04.1 450.80.02-0ubuntu0.20.04.2 2020-10-14 07:18:10 upgrade linux-generic-hwe-20.04:amd64 5.4.0.48.51 5.4.0.51.54 2020-10-14 07:18:11 upgrade linux-image-generic-hwe-20.04:amd64 5.4.0.48.51 5.4.0.51.54 2020-10-14 07:18:14 upgrade linux-headers-generic-hwe-20.04:amd64 5.4.0.48.51 5.4.0.51.54 2020-10-14 07:18:14 upgrade linux-libc-dev:amd64 5.4.0-48.52 5.4.0-51.56 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-11 (156 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo _MarkForUpload: True To
[Desktop-packages] [Bug 1818348] Re: When window title bar controls are on left, close window button is cut off in title bar of Disks application
This is fixed in the upstream, when is it expected to land in Ubuntu? -- 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/1818348 Title: When window title bar controls are on left, close window button is cut off in title bar of Disks application Status in gnome-disk-utility package in Ubuntu: Triaged Bug description: When you configure your window title bar buttons to be on the left instead of the right in the tweaks app, the close window button is cut off in the Disks app. I don't see this behavior in other apps. See attached screenshot for illustration of what I mean. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-disk-utility 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 2 12:32:43 2019 InstallationDate: Installed on 2019-03-02 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1818348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
You can track the official fix coming via bug 1908161.
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell package in Debian:
Unknown
Bug description:
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605
---
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908071] Re: The video card driver is not working well
You appear to have the 'oibaf' PPA installed which is not supported and is known to cause bugs. Please use the 'ppa-purge' tool to remove that PPA from the system, then reboot and if you experience any more problems then open a new bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1908071 Title: The video card driver is not working well Status in Ubuntu: Invalid Bug description: 1)lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2)apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu15 Candidate: 1:7.7+19ubuntu15 Version table: *** 1:7.7+19ubuntu15 500 500 http://ua.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status 3)Normal work ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Dec 14 15:49:46 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics [103c:86a0] InstallationDate: Installed on 2020-12-13 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:8505 Dell Computer Corp. Dell Universal Receiver Bus 001 Device 002: ID 04ca:7095 Lite-On Technology Corp. HP HD Camera Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 450 G7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=227ec1da-8070-4974-9577-9fe4a7428d90 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2020 dmi.bios.release: 6.1 dmi.bios.vendor: HP dmi.bios.version: S71 Ver. 01.06.01 dmi.board.name: 86A0 dmi.board.vendor: HP dmi.board.version: KBC Version 02.2D.00 dmi.chassis.asset.tag: 5CD024GVZP dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 2.45 dmi.modalias: dmi:bvnHP:bvrS71Ver.01.06.01:bd10/19/2020:br6.1:efr2.45:svnHP:pnHPProBook450G7:pvr:rvnHP:rn86A0:rvrKBCVersion02.2D.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 450 G7 dmi.product.sku: 6YY26AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103+git2012121830.d034db~oibaf~g version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2012130730.6a34a6~oibaf~g version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907905] Re: buging
Please attach a photo or video of the problem so we can understand what you are seeing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1907905 Title: buging Status in Ubuntu: Incomplete Bug description: just have a lot of gren points and com`s and disapiering picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 12 15:32:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:5000] InstallationDate: Installed on 2020-11-14 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 33663VG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2013 dmi.bios.release: 2.54 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 33663VG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 2.54 dmi.modalias: dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E530c dmi.product.name: 33663VG dmi.product.sku: LENOVO_MT_3366 dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1907905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908089] Re: gnome-shell-extension-multi-monitors crash on gnome shell 3.36.4
** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell-extension-multi-monitors (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1908089 Title: gnome-shell-extension-multi-monitors crash on gnome shell 3.36.4 Status in gnome-shell-extension-multi-monitors package in Ubuntu: New Bug description: I've installed gnome-shell-extension-multi-monitors 19-1 on ubuntu 20.04 and running gnome-shell 3.36.4: The extension is available within gnome-tweaks and can be enabled. But when logging in it crashes: gnome-tweaks shows "Error loading extension" and the following error shows up in the syslog: Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS WARNING: [/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js 402]: reference to undefined property "_onButtonPress" Dec 14 07:27:27 eso12919 gnome-shell[3569]: JS ERROR: Extension multi-monitors-add-on@spin83: TypeError: this._onButtonPress is undefined#012_init@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmpanel.js:402:4#012_pushPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:220:15#012_monitorsChanged@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:199:11#012showPanel@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/mmlayout.js:87:10#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:209:24#012wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27#012enable@/usr/share/gnome-shell/extensions/multi-monitors-add-on@spin83/extension.js:331:21#012_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32#012loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:349:26#012_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:599:18#012collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17#012_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:574:19#012_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:608:18#012_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:639:18#012init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14#012_initializeUI@resource:///org/gnome/shell/ui/main.js:257:22#012start@resource:///org/gnome/shell/ui/main.js:146:5#012@:1:47 I've checked https://extensions.gnome.org/extension/921/multi-monitors-add-on/ and it seems that the version 19 of the extension is not compatible with 3.36.4. It seems like you need at least version 20 of gnome-shell-extension-multi-monitors. So I guess an update is necessary... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-multi-monitors/+bug/1908089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound
1. This is probably an issue with the Bluetooth kernel driver. Please run: lspci -kv > lspci.txt lsusb > lsusb.txt and attach the resulting text files here. 2. Please ensure the latest driver is installed by running: sudo apt install bcmwl-kernel-source and then reboot. 3. Try closing Settings, in case you are experiencing bug 1797002. ** Tags added: a2dp ** Tags added: a2dp-skip ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908064 Title: [Multiple bluetooth speakers, playback] Stuttering sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Constant stuttering sound, stuttering at maybe 10 times/second. More than one speaker with the same symptoms. Speakers work in Windows 10 / macOS 10.14+ running on same hardware. Same speakers work on Ubuntu Mate 18.04 32 bit running on different hardware. Remote control commands work (play/pause button on speakers). Initial pairing and connection requires from 2 to about 10 retries. All tested within 1 m distance. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username3486 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 13:49:26 2020 InstallationDate: Installed on 2020-10-30 (45 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: Crossbeat Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Crossbeat, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 264.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2E6FAB96566FE58C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir5,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2E6FAB96566FE58C dmi.modalias: dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C: dmi.product.family: MacBook Air dmi.product.name: MacBookAir5,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907904] Re: gnome-shell 20.10 crashes with Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: groovy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1907904 Title: gnome-shell 20.10 crashes with Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu Gnome 20.10 (upgraded from 20.04), 64 bits,Wayland session AMD CPU Fx GPU Radeon Very frequently, Gnome-shell crashes and difficult to understand why or when. Example : open a Libreoffice Calc file ; export it twice in PDF format on the Desktop. Right-click on this files icons on the desktop to delete them : for the 2nd, the screen becomes black (I can do nothing) and after about 20 s, I get the login screen. I exported the journal file (attached file) (and the session crashes again) because the system says nothing ! Doesn't happen with X session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1907904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907906] Re: i want some support
** Package changed: xorg (Ubuntu) => 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/1907906 Title: i want some support Status in Ubuntu: Incomplete Bug description: ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 12 15:39:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:5000] InstallationDate: Installed on 2020-11-14 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 33663VG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2013 dmi.bios.release: 2.54 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 33663VG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 2.54 dmi.modalias: dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E530c dmi.product.name: 33663VG dmi.product.sku: LENOVO_MT_3366 dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1907906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Please try selecting 'Ubuntu on Wayland' from the login screen, before you enter your password. ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.67
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Please also run: grep . /sys/class/drm/*/modes > drmmodes.txt and attach the resulting text file here. -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1 disconnected
[Desktop-packages] [Bug 1907870] Re: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Also, while the monitor is plugged in please run: xrandr --verbose > xrandrv.txt and attach the resulting text file here. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576
[Desktop-packages] [Bug 1907882] Re: paprefs does not find modules
** Tags added: groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1907882
Title:
paprefs does not find modules
Status in pulseaudio package in Ubuntu:
New
Bug description:
on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
workaround:
cd /usr/lib
sudo ln -s pulse-13.99.2 pulse-13.99
see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531251
strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) =
-1 ENOENT (No such file or directory)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1907882/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907865] Re: Xorg crash
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => ubuntu ** Summary changed: - Xorg crash + Session crash -- 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/1907865 Title: Session crash Status in Ubuntu: Incomplete Bug description: I can't reliably reproduce this crash, and I don't know, even approximately, what's causing it, or what I might be doing to possibly cause it. It just randomly crashes, and dumps me back to the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 15:35:06 2020 DistUpgraded: 2020-10-07 09:25:09,468 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu 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:06de] InstallationDate: Installed on 2016-12-06 (1466 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0VHKV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.product.sku: 06DE dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Fri Aug 17 21:02:51 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1523 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1907865/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903230] Re: Mutter release 3.36.7
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Bionic) Status: New => In Progress ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Status: In Progress => Won't Fix -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Bionic: In Progress Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906977] Re: moving cursor to dock causes desktop-icons graphic garbage
Please: 1. Open the 'Extensions' app and verify you only have the three Ubuntu extensions installed. 2. Ensure you don't have any directory named 'extensions' under ~/.local/share/gnome-shell/ ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- 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/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor moves over the dock, a small version of the graphic of the minimised window (ie what would be shown by opening "Activities") appears. It can be cleared by opening another window and sweeping this over the desktop. It only happens once, once for every time you minimise a window. b) Click on "Activities" then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing "Print Scrn" button, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage
Thanks for the video. That looks like a bug in the 'desktop-icons' extension. ** Summary changed: - moving cursor to dock causes desktop graphic garbage + moving cursor to dock causes desktop-icons graphic garbage ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor moves over the dock, a small version of the graphic of the minimised window (ie what would be shown by opening "Activities") appears. It can be cleared by opening another window and sweeping this over the desktop. It only happens once, once for every time you minimise a window. b) Click on "Activities" then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing "Print Scrn" button, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Tags added: oem-priority originate-from-1895332 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Status in pulseaudio source package in Hirsute: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906977] Re: moving cursor to dock causes desktop graphic garbage
Yes it's annoying sometimes that the process of screenshotting actually changes the way the screen is drawn :( -- 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/1906977 Title: moving cursor to dock causes desktop-icons graphic garbage Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor moves over the dock, a small version of the graphic of the minimised window (ie what would be shown by opening "Activities") appears. It can be cleared by opening another window and sweeping this over the desktop. It only happens once, once for every time you minimise a window. b) Click on "Activities" then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, or pressing "Print Scrn" button, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1906977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] [NEW] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
Public bug reported: this bug is for tracking purpose. ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: pulseaudio (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: pulseaudio (Ubuntu Groovy) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: pulseaudio (Ubuntu Hirsute) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: New => In Progress ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Also affects: pulseaudio (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Groovy) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Focal) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Groovy) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Groovy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: pulseaudio (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Groovy: In Progress Status in pulseaudio source package in Hirsute: In Progress Bug description: this bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908158] Re: Update to 3.38.2
mutter (3.38.2-1ubuntu1) hirsute; urgency=medium ** Tags added: groovy hirsute ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed -- 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/1908158 Title: Update to 3.38.2 Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
Thanks. Unfortunately I can't see an explanation in there, and there's no crash either. Please ensure you only have the three Ubuntu extensions (or less) enabled in the Extensions app. If the problem keeps happening then you can work around it by disabling the 'Ubuntu Dock' extension, I am told -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Focal: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) 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-extension-ubuntu-dock/+bug/1872268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing
If you're using KDE on 20.10 then you might want to look at bug 1897965. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903903 Title: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing Status in pulseaudio package in Ubuntu: New Bug description: After every reboot, the profile named "Analog Stereo Duplex" keeps disappearing on my laptop; only "Analog Stereo Input" and "Analog Stereo Output" are present. Without "duplex", I cannot use both the built-in microphone and the speakers/headphones at the same time. A workaround I found is to remove the user's configuration for pulseaudio and restart it: rm -rf .config/pulse pulseaudio -k This brings the "Analog Stereo Duplex" profile back until the next reboot. This problem started after an upgrade from Ubuntu 20.04 to 20.10. I made a screencast of this: https://youtu.be/Vlz5471EYVQ The laptop is MSI WE73-8SK. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf] ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Nov 11 10:50:54 2020 InstallationDate: Installed on 2019-01-08 (673 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago) dmi.bios.date: 05/20/2019 dmi.bios.release: 1.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C5IWS.10F dmi.board.asset.tag: Default string dmi.board.name: MS-17C5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: WE dmi.product.name: WE73 8SK dmi.product.sku: 17C5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908161] Re: Update to 3.38.2
gnome-shell (3.38.2-1ubuntu1) hirsute; urgency=medium ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: groovy hirsute -- 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/1908161 Title: Update to 3.38.2 Status in gnome-shell package in Ubuntu: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Screenshots handling has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766775] Re: "Automatic suspend" notifications do not disappear
** Summary changed: - Notifications do not disappear + "Automatic suspend" notifications do not disappear -- 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/1766775 Title: "Automatic suspend" notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
This bug is closed. If there's a problem with kernel 5.10 then please open a new bug about it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908158] Re: Update to 3.38.2
Oh, didn't get it during auto-search... Sorry, let's merge here indeedd. -- 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/1908158 Title: Update to 3.38.2 Status in mutter package in Ubuntu: In Progress Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906736] Re: Please update package to 3.38.2
*** This bug is a duplicate of bug 1908158 *** https://bugs.launchpad.net/bugs/1908158 ** This bug has been marked a duplicate of bug 1908158 Update to 3.38.2 -- 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/1906736 Title: Please update package to 3.38.2 Status in mutter package in Ubuntu: Triaged Bug description: The latest version in the debian repo fixes this bug, where CSGO can´t be played in fullscreen mode: https://github.com/ValveSoftware/csgo-osx-linux/issues/2551 It´s part of debian SID already: https://packages.debian.org/sid/main/libmutter-7-0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1906736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908158] Re: Update to 3.38.2
We already had bug 1906736, but we can use this one now. -- 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/1908158 Title: Update to 3.38.2 Status in mutter package in Ubuntu: In Progress Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907905] Re: buging
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1907905 Title: buging Status in xorg package in Ubuntu: New Bug description: just have a lot of gren points and com`s and disapiering picture ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 12 15:32:53 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:5000] InstallationDate: Installed on 2020-11-14 (27 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 33663VG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2013 dmi.bios.release: 2.54 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET94WW (2.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 33663VG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 2.54 dmi.modalias: dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E530c dmi.product.name: 33663VG dmi.product.sku: LENOVO_MT_3366 dmi.product.version: ThinkPad Edge E530c dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1907905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908164] [NEW] Impossible to get screenshot of fullscreen games
Public bug reported: [ Impact ] When I screenshot (by pressing PrintScreen button) pretty much any game (non-game applications like Chromium or VLC don't have this issue) that renders in fullscreen (Vulkan or OpenGL), screenshots always come out completely blank and transparent. [ Test case ] Run a game full-screen, hit Print Screen to get a screenshot: - Expect the screenshot to be saved in the picture folders and to contain the game screen [ Regression potential ] Screenshots on X11 might cause a bit more resources and could be taken with some delay. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: mutter (Ubuntu Groovy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1453 https://gitlab.gnome.org/GNOME/mutter/-/issues/1453 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1453 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Groovy) Status: New => In Progress ** Changed in: mutter (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1908164 Title: Impossible to get screenshot of fullscreen games Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] When I screenshot (by pressing PrintScreen button) pretty much any game (non-game applications like Chromium or VLC don't have this issue) that renders in fullscreen (Vulkan or OpenGL), screenshots always come out completely blank and transparent. [ Test case ] Run a game full-screen, hit Print Screen to get a screenshot: - Expect the screenshot to be saved in the picture folders and to contain the game screen [ Regression potential ] Screenshots on X11 might cause a bit more resources and could be taken with some delay. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1908164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908161] [NEW] Update to 3.38.2
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Screenshots handling has changed ** Affects: gnome-shell (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1908161 Title: Update to 3.38.2 Status in gnome-shell package in Ubuntu: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Screenshots handling has changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1908161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908158] [NEW] Update to 3.38.2
Public bug reported: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: mutter (Ubuntu Groovy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Groovy) Status: New => In Progress ** Changed in: mutter (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1908158 Title: Update to 3.38.2 Status in mutter package in Ubuntu: In Progress Status in mutter source package in Groovy: In Progress Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.38.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] Updates on background painting, input devices settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1908158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908153] [NEW] [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound
Public bug reported: With this latest update (Linux 5.4.0-58), the sound is now crackling. Feels like DMA buffer underruns, but I'm not sure. Not seeing a significant CPU load that might have aggravated it, nor am I seeing any complaints in syslog or kern.log. Restarting pulseaudio and running alsa force-reload had no effect. These sound issues started with the same update that caused the ath10k_pci driver to become extremely unreliable (filed as bug 1908106). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt 22891 F pulseaudio /dev/snd/controlC0: ddt 22891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 14:55:14 2020 InstallationDate: Installed on 2020-03-23 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulseAudioLog: Dec 14 07:32:47 ddtlap dbus-daemon[859]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=124 pid=1157 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Dec 14 08:11:14 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:12:19 ddtlap pulseaudio[1157]: Failed to create sink input: sink is suspended. Dec 14 08:13:47 ddtlap dbus-daemon[859]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.70" (uid=1000 pid=1553 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.3" (uid=0 pid=855 comm="/usr/lib/bluetooth/bluetoothd " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out, Left] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to focal on 2020-05-12 (216 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.7.0 dmi.board.name: Alienware 15 R4 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.7.0:bd04/18/2019:svnAlienware:pnAlienware15R4:pvr1.7.0:rvnAlienware:rnAlienware15R4:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R4 dmi.product.sku: 0876 dmi.product.version: 1.7.0 dmi.sys.vendor: Alienware ** 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/1908153 Title: [Alienware 15 R4, Realtek ALC3266, Black Headphone Out or internal speakers] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: New Bug description: With this latest update (Linux 5.4.0-58), the sound is now crackling. Feels like DMA buffer underruns, but I'm not sure. Not seeing a significant CPU load that might have aggravated it, nor am I seeing any complaints in syslog or kern.log. Restarting pulseaudio and running alsa force-reload had no effect. These sound issues started with the same update that caused the ath10k_pci driver to become extremely unreliable (filed as bug 1908106). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ddt 22891 F pulseaudio /dev/snd/controlC0: ddt 22891 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 14 14:55:14 2020 InstallationDate: Installed on 2020-03-23 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=screen-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
[Desktop-packages] [Bug 1050644] Re: eset nod 64bit install caused crash
** Changed in: desktop-file-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/1050644 Title: eset nod 64bit install caused crash Status in desktop-file-utils package in Ubuntu: Fix Released Bug description: eset nod 64bit install caused crash. During install phase Lubuntu caused multiple crashes ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: desktop-file-utils 0.20-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Thu Sep 13 22:41:35 2012 ExecutablePath: /usr/bin/update-desktop-database InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) ProcCmdline: /usr/bin/update-desktop-database ProcEnviron: LANGUAGE=en TERM=unknown PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 4 SourcePackage: desktop-file-utils UpgradeStatus: Upgraded to quantal on 2012-08-26 (18 days ago) UserGroups: mtime.conffile..etc.gnome.defaults.list: 2012-08-24T20:26:23.344598 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1050644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
i don't have dmic_datect=0 in alsa conf, only: options snd-hda-intel index=1 model=laptop-dmic if i delete this, i still have no mic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use
@Walter (wxl) Good questions ... I have been running tests with other file managers in Lubuntu with no success ..will also test pcmanfm-qt and thunar in one or two oth the other flavors. Will report back with more details when I finish. -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) 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: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Fwd: Submit Request Failure
i'll try again with a text file as i got an error sending the error ;) Forwarded Message Subject:Submit Request Failure Date: Mon, 14 Dec 2020 21:12:22 - From: nore...@bugs.launchpad.net Reply-To: nore...@bugs.launchpad.net To: launch...@diversity.nl An error occurred while processing a mail you sent to Launchpad's email interface. Error message: The message you sent included commands to modify the bug report, but you didn't sign the message with an OpenPGP key that is registered in Launchpad. -- For more information about using Launchpad by email, see https://help.launchpad.net/EmailInterface or send an email to h...@launchpad.net ** Attachment added: "thunderbird error.txt" https://bugs.launchpad.net/bugs/1904789/+attachment/5443550/+files/thunderbird%20error.txt -- 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/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875717] Re: Opening file from Samba share results in Document in Use
I wonder… 1. if you use pcmanfm-qt or thunar in any of the flavors, does it fail? 2. if you use one of the other file managers (say, nautilus or caja) in Lubuntu or Xubuntu, does it succeed? -- 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/1875717 Title: Opening file from Samba share results in Document in Use Status in libreoffice package in Ubuntu: New Bug description: This bug is related to bug # 1430531. I am running Lubuntu version 20.04 with all updates installed The Libre Office version : Version: 6.4.2.2 Build ID: 1:6.4.2-0ubuntu3 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: qt5; Locale: en-GB (en_GB.UTF-8); UI-Language: en-US Calc: threaded 1. connect to share on local network with PCManFM-Qt File Manager 2. click on file TEST_Samba.odt 3. The Libre Office splash/Logo screen appears for a split second and the nothing happens and the file is not opened. 4. I then right-click on file and select "open with Libre Office Writer 5. Document in Use" window appears with text: Document file 'TEST_Samba.odt' is locked for editing by: Unknown User Open document read-only or open a copy of the document for editing. Open Read-Only Open Copy Cancel Screen shot attached.. Expected results: The "TEST_Samba.odt" files is opened in read-write mode, user can edit it. Actual results: User can't edit original document (see 3-5 above) I have tested this on several boxes running Lubuntu 20.04 with the exact same results. I have also tested this on SparkyLinux LxQT version 5.11 with the same results. Ubuntu Gnome as well as MS Windows/Office have no problems opening/editing and/or saving this file back to the Samba share. Global Samba config is "default" Usershare config is: $ cat /var/lib/samba/usershares/sameign2 #VERSION 2 path=/home/kbeins/Sameign2 comment= usershare_acl=S-1-1-0:F guest_ok=n sharename=Sameign2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) 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: LXQt Date: Tue Apr 28 17:51:14 2020 InstallationDate: Installed on 2020-04-28 (0 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1875717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Thank you for your bug report, is there a public server which triggers the dialog which could be used for testing? Could you try to start thunderbird --jsconsole and see if any error is printed when trying to validate the exception? ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Low -- 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/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876577] Re: fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display
*** This bug is a duplicate of bug 1871849 *** https://bugs.launchpad.net/bugs/1871849 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1876577 Title: fullscreen in browser and video player with fractional scaling(150%) enabled corrupted display Status in xorg package in Ubuntu: Confirmed Bug description: when fractional scaling is enabled for example 150%, trying to fullscreen the video playing in the browser or in the video player, display suddenly goes black, and then video resolution size is reduced to 1/4 of the actual screen size, with a still frame from the video as background and every app opened in the bacground becomes so large that it goes out of the window. also the mouse cursor stuck on the screen if auto login is disabled 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:20:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] [1043:04c4] InstallationDate: Installed on 2020-04-24 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=a12e4265-d2f1-4a68-b9f4-840dc9e18df1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5406 dmi.board.asset.tag: Default string dmi.board.name: TUF X470-PLUS GAMING 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.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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/1876577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling
I have the same problem using Davinci Resolve in fullscreen mode, as well as VLC. With two 27" 4K monitors it's impossible to use any other scaling factor except 150%. Ubuntu 20.10 GNOME 3.38.1 -- 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/1871849 Title: Full screen videos suddenly change scale when using fractional scaling Status in mutter package in Ubuntu: Confirmed Bug description: firefox does not properly play full screen videos using fractional scale at 125% --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-29 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 Tags: focal Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876383] Re: issues with full screen videos
*** This bug is a duplicate of bug 1871849 *** https://bugs.launchpad.net/bugs/1871849 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1876383 Title: issues with full screen videos Status in xorg package in Ubuntu: Confirmed Bug description: When watching MP4 clips using the default app (videos) I have a display issue. When clicking on the full screen button here is what happens: 1- screen goes blank for a few seconds 2- a new videos window opens up with displaying the move but it it is not maximized or in full screen 3- The original maximized window stays in the background with a still picture 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:21:04 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068] InstallationDate: Installed on 2020-04-24 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0070.2018.1019.1503 dmi.board.name: NUC7i7BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31145-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0070.2018.1019.1503:bd10/19/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-304:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.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/1876383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
On 14/12/2020 18:48, Łukasz Zemczak wrote: > Sadly I cannot release the focal SRU as it seems that the signon package > FTBFS on ppc64el there: > > https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793 > > It seems to have built fine previously. Can someone take a look? > > ** Changed in: signon (Ubuntu Focal) >Status: Fix Committed => Incomplete > seems that failed to build without a log, so likely a launchpad 'burp'. a retry made it build ok -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Incomplete Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876172] Re: While fractional scaling is enabled (125%), fullscreen video resizes
*** This bug is a duplicate of bug 1871849 *** https://bugs.launchpad.net/bugs/1871849 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1876172 Title: While fractional scaling is enabled (125%), fullscreen video resizes Status in mutter package in Ubuntu: Confirmed Bug description: I think it is related to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1862081 If you enable fractional scaling, for example 125%, and play video in fullscreen mode (youtube, vlc, gnome videos), application will constantly resize. This makes fullscreen mode unsuable. Problem does NOT occur when you disable fractional scaling. This bug has 100% reproducibility. I don't really know if it's mutter fault, but this is the only culprit I found in my research. If any more information is required, please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 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: Thu Apr 30 21:09:09 2020 InstallationDate: Installed on 2020-04-10 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876172/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908119] Re: SRU 1.90.7
** Changed in: fprintd (Ubuntu) Status: Fix Released => In Progress ** Summary changed: - SRU 1.90.7 + Update and SRU 1.90.8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1908119 Title: Update and SRU 1.90.8 Status in fprintd package in Ubuntu: In Progress Status in fprintd source package in Focal: In Progress Status in fprintd source package in Groovy: In Progress Bug description: [ Impact ] Fprintd 1.90.7 is a new upstream version of fprintd that addresses many issues that have been here for some years, including some security ones (such as bug #1532264). It was also mostly rewritten to use GDBus and removing the deprecated dbus-glib. [ Test Case ] - Setup fingerprint authentication - Ensure that: - Previously configured access is still working - Configuring fprintd from 0 works as expected Enrollment and verification should both work using GNOME Control center and GNOME Shell (or other setups in KDE or other DE's) and using the `fprintd-enroll` / `fprintd-verify` / `fprintd-delete` utilities. [ Regression potential ] As said changes [1] are not trivial (even though you may want to ignore white spaces, as per new syntax rules), however the fprintd test suite already included quite a lot test cases and many others have been added to this release to ensure that nothing changed. From a dbus-API point of view, there were no changes (just few additions such as the DBus object manager support), so clients should expect no changes. However the new DBus and async polkit authentication machinery could cause regressions, such as: - Races causing wrong client to be authenticated on request - Concurrent requests could lead to other client to be authorized - PAM module could ignore verification events or authorize the wrong request [1] https://launchpadlibrarian.net/51082/fprintd_1.90.1-1ubuntu1_1.90.7-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908125] [NEW] Casting works but I must manually select input.
Public bug reported: Hi, Using other devices, when I cast to a chromecast the TV automatically switches to the HDMI source connecting the TV and chromecast dongle. With the linux snap, I have to manually select the TV input. ** 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/1908125 Title: Casting works but I must manually select input. Status in chromium-browser package in Ubuntu: New Bug description: Hi, Using other devices, when I cast to a chromecast the TV automatically switches to the HDMI source connecting the TV and chromecast dongle. With the linux snap, I have to manually select the TV input. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1908125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1904460] Re: Gnome disks icon is missing when upgraded from 18.04 to 20.04
I have never changed the icon theme, so whatever the ubuntu mate default is. On 17/11/2020 10:07, Sebastien Bacher wrote: > Thank you for your bug report but that seems rather a theme issue. What > icon theme do you use? > > ** Changed in: gnome-disk-utility (Ubuntu) > Importance: Undecided => Low > > ** Changed in: gnome-disk-utility (Ubuntu) > Status: New => Incomplete > -- 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/1904460 Title: Gnome disks icon is missing when upgraded from 18.04 to 20.04 Status in Ubuntu MATE: New Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: Upgraded 18.04 to 20.04 using 'do-release-upgrade'. I now have a missing icon for gnome disks. I have reinstalled adwaita icons and brisk menu, to no avail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1904460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1904460] Re: Gnome disks icon is missing when upgraded from 18.04 to 20.04
I have restored my clonezilla backup of 18.04 as I also have an issue with deja-dup not working after the upgrade (reported as a separate bug). I needed to get back to work urgently and didn't have time to try your suggestion. As a side, I see that icons are missing for certain locales, could this be related? On 16/11/2020 20:39, Norbert wrote: > Can you reproduce this on new user account? > > ** Tags added: focal > > ** Also affects: gnome-disk-utility (Ubuntu) > Importance: Undecided > Status: New > -- 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/1904460 Title: Gnome disks icon is missing when upgraded from 18.04 to 20.04 Status in Ubuntu MATE: New Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: Upgraded 18.04 to 20.04 using 'do-release-upgrade'. I now have a missing icon for gnome disks. I have reinstalled adwaita icons and brisk menu, to no avail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1904460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
This bug was fixed in the package libinput - 1.10.4-1ubuntu0.18.04.2 --- libinput (1.10.4-1ubuntu0.18.04.2) bionic; urgency=medium * Unset INPUT_PROP_BUTTONPAD for Dell Precision 7x50. (LP: #1905819) * Update control build-dep libevdev-dev (>= 1.5.8+dfsg-1ubuntu0.1) for libevdev_disable_property API. -- Kai-Chuan Hsieh Mon, 30 Nov 2020 20:08:24 +0800 ** Changed in: libinput (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libevdev in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in libevdev source package in Bionic: Fix Released Status in libinput source package in Bionic: Fix Released Status in libevdev source package in Focal: Fix Released Status in libinput source package in Focal: Fix Released Status in libevdev source package in Groovy: Fix Released Status in libinput source package in Groovy: Fix Released Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 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
[Desktop-packages] [Bug 1908119] Re: SRU 1.90.7
** Also affects: fprintd (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu Groovy) Importance: Undecided => High ** Changed in: fprintd (Ubuntu Groovy) Status: New => In Progress ** Changed in: fprintd (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: fprintd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu Focal) Importance: Undecided => High ** Changed in: fprintd (Ubuntu Focal) Status: New => In Progress ** Changed in: fprintd (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: fprintd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1908119 Title: SRU 1.90.7 Status in fprintd package in Ubuntu: Fix Released Status in fprintd source package in Focal: In Progress Status in fprintd source package in Groovy: In Progress Bug description: [ Impact ] Fprintd 1.90.7 is a new upstream version of fprintd that addresses many issues that have been here for some years, including some security ones (such as bug #1532264). It was also mostly rewritten to use GDBus and removing the deprecated dbus-glib. [ Test Case ] - Setup fingerprint authentication - Ensure that: - Previously configured access is still working - Configuring fprintd from 0 works as expected Enrollment and verification should both work using GNOME Control center and GNOME Shell (or other setups in KDE or other DE's) and using the `fprintd-enroll` / `fprintd-verify` / `fprintd-delete` utilities. [ Regression potential ] As said changes [1] are not trivial (even though you may want to ignore white spaces, as per new syntax rules), however the fprintd test suite already included quite a lot test cases and many others have been added to this release to ensure that nothing changed. From a dbus-API point of view, there were no changes (just few additions such as the DBus object manager support), so clients should expect no changes. However the new DBus and async polkit authentication machinery could cause regressions, such as: - Races causing wrong client to be authenticated on request - Concurrent requests could lead to other client to be authorized - PAM module could ignore verification events or authorize the wrong request [1] https://launchpadlibrarian.net/51082/fprintd_1.90.1-1ubuntu1_1.90.7-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908119] [NEW] SRU 1.90.7
Public bug reported: [ Impact ] Fprintd 1.90.7 is a new upstream version of fprintd that addresses many issues that have been here for some years, including some security ones (such as bug #1532264). It was also mostly rewritten to use GDBus and removing the deprecated dbus-glib. [ Test Case ] - Setup fingerprint authentication - Ensure that: - Previously configured access is still working - Configuring fprintd from 0 works as expected Enrollment and verification should both work using GNOME Control center and GNOME Shell (or other setups in KDE or other DE's) and using the `fprintd-enroll` / `fprintd-verify` / `fprintd-delete` utilities. [ Regression potential ] As said changes [1] are not trivial (even though you may want to ignore white spaces, as per new syntax rules), however the fprintd test suite already included quite a lot test cases and many others have been added to this release to ensure that nothing changed. >From a dbus-API point of view, there were no changes (just few additions such as the DBus object manager support), so clients should expect no changes. However the new DBus and async polkit authentication machinery could cause regressions, such as: - Races causing wrong client to be authenticated on request - Concurrent requests could lead to other client to be authorized - PAM module could ignore verification events or authorize the wrong request [1] https://launchpadlibrarian.net/51082/fprintd_1.90.1-1ubuntu1_1.90.7-1.diff.gz ** Affects: fprintd (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: fprintd (Ubuntu Focal) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: fprintd (Ubuntu Groovy) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1908119 Title: SRU 1.90.7 Status in fprintd package in Ubuntu: In Progress Status in fprintd source package in Focal: In Progress Status in fprintd source package in Groovy: In Progress Bug description: [ Impact ] Fprintd 1.90.7 is a new upstream version of fprintd that addresses many issues that have been here for some years, including some security ones (such as bug #1532264). It was also mostly rewritten to use GDBus and removing the deprecated dbus-glib. [ Test Case ] - Setup fingerprint authentication - Ensure that: - Previously configured access is still working - Configuring fprintd from 0 works as expected Enrollment and verification should both work using GNOME Control center and GNOME Shell (or other setups in KDE or other DE's) and using the `fprintd-enroll` / `fprintd-verify` / `fprintd-delete` utilities. [ Regression potential ] As said changes [1] are not trivial (even though you may want to ignore white spaces, as per new syntax rules), however the fprintd test suite already included quite a lot test cases and many others have been added to this release to ensure that nothing changed. From a dbus-API point of view, there were no changes (just few additions such as the DBus object manager support), so clients should expect no changes. However the new DBus and async polkit authentication machinery could cause regressions, such as: - Races causing wrong client to be authenticated on request - Concurrent requests could lead to other client to be authorized - PAM module could ignore verification events or authorize the wrong request [1] https://launchpadlibrarian.net/51082/fprintd_1.90.1-1ubuntu1_1.90.7-1.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
This bug was fixed in the package gnome-shell-extension-appindicator - 33.1-0ubuntu0.20.04.1 --- gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream stable release * debian/gbp.conf: - Setup for focal branching and use ubuntu/* tagging - Use multimaint-merge in dch and sign tags * debian/control: - Set Ubuntu Developers as maintainer - Update VCS informations to point to ubuntu/focal * dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669) * dbusMenu: Use proper argument name when parsing error (LP: #1881669) * dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795) * appIndicator: Remove the callbackIdle if we destroy while waiting it (LP: #1849142) * StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785) * appIndicator: Ignore further icons creation during an idle (LP: #1849142) * README: Remove statement about indicator-multiload not being supported * statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and returned error (LP: #1896785) * interfaces: Sync interfaces XML with upstream ones (LP: #1896785) * StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785) * appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396): - util: Use Shell's param to handle multiple named arguments - util: Delete proxyCancellables only if we didn't cancel already - util: Ignore errors if we can't find a listed dbus name - appIndicator: Cleanup the interface info properties map computation - appIndicator: Don't deep unpack changed properties array - appIndicator: Use native checks to look for equal emblems - appIndicator: Mark a valid cached icon as inUse again - appIndicator: Correctly mark cached GIcon's as in use - iconCache: Rewrite simplifying the usage for GIcon's only - iconCache: Dispose an icon when we remove it - iconCache: Increase the garbage-collector timings - appIndicator: Only iterate through the proxy available properties - appIndicator: Don't try to check equality on Pixmap variants - util: Try to batch properties updates when they comes close enough - appIndicator: Accumulate signals to batch close updates - appIndicator: Emit the same signal once on properties updates - appIndicator: Improve the warning message on lookup failed [ Fini Jastrow ] * appIndicator: Remove unneeded padding (LP: #1896779) * appIndicator: Fix 'reduce padding' for some icons (LP: #1896779) [ Sergio Costas ] * Wait until the desktop ends starting up (LP: #1870795) * Wait until Gtk.IconTheme.get_default() works (LP: #1870795) * Don't fail if no icon is found (LP: #1849142) * Use signal to detect display availability (LP: #1870795) [ Tasos Sahanidis ] * kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785) -- Marco Trevisan (Treviño) Wed, 23 Sep 2020 18:47:33 +0200 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Released Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171
[Desktop-packages] [Bug 1870795] Re: Appindicator not showing under wayland
This bug was fixed in the package gnome-shell-extension-appindicator - 33.1-0ubuntu0.20.04.1 --- gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream stable release * debian/gbp.conf: - Setup for focal branching and use ubuntu/* tagging - Use multimaint-merge in dch and sign tags * debian/control: - Set Ubuntu Developers as maintainer - Update VCS informations to point to ubuntu/focal * dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669) * dbusMenu: Use proper argument name when parsing error (LP: #1881669) * dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795) * appIndicator: Remove the callbackIdle if we destroy while waiting it (LP: #1849142) * StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785) * appIndicator: Ignore further icons creation during an idle (LP: #1849142) * README: Remove statement about indicator-multiload not being supported * statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and returned error (LP: #1896785) * interfaces: Sync interfaces XML with upstream ones (LP: #1896785) * StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785) * appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396): - util: Use Shell's param to handle multiple named arguments - util: Delete proxyCancellables only if we didn't cancel already - util: Ignore errors if we can't find a listed dbus name - appIndicator: Cleanup the interface info properties map computation - appIndicator: Don't deep unpack changed properties array - appIndicator: Use native checks to look for equal emblems - appIndicator: Mark a valid cached icon as inUse again - appIndicator: Correctly mark cached GIcon's as in use - iconCache: Rewrite simplifying the usage for GIcon's only - iconCache: Dispose an icon when we remove it - iconCache: Increase the garbage-collector timings - appIndicator: Only iterate through the proxy available properties - appIndicator: Don't try to check equality on Pixmap variants - util: Try to batch properties updates when they comes close enough - appIndicator: Accumulate signals to batch close updates - appIndicator: Emit the same signal once on properties updates - appIndicator: Improve the warning message on lookup failed [ Fini Jastrow ] * appIndicator: Remove unneeded padding (LP: #1896779) * appIndicator: Fix 'reduce padding' for some icons (LP: #1896779) [ Sergio Costas ] * Wait until the desktop ends starting up (LP: #1870795) * Wait until Gtk.IconTheme.get_default() works (LP: #1870795) * Don't fail if no icon is found (LP: #1849142) * Use signal to detect display availability (LP: #1870795) [ Tasos Sahanidis ] * kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785) -- Marco Trevisan (Treviño) Wed, 23 Sep 2020 18:47:33 +0200 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Released Bug description: [ Impact ] An app-indicator icon does not show when I login using the default gnome session (wayland). If I choose the xorg session, the icon shows as normal. Under wayland, the icon does appear if I lock my session then log back in. [ Test case ] Run a desktop session (better if Ubuntu wayland), ensure that all the startup-launched appindicators are showing in the status area. One affected indicator seems to be https://github.com/juliagoda/antimicroX/ [ Regression potential ] Indicators may not load at all, wrong icons are shown instead. --- Upstream change: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/231 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gnome-session-wayland gnome-session-wayland: Installed: (none) Candidate: 3.36.0-2ubuntu1 Version table: 3.36.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 15:30:40 2020
[Desktop-packages] [Bug 1881669] Re: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it
This bug was fixed in the package gnome-shell-extension-appindicator - 33.1-0ubuntu0.20.04.1 --- gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream stable release * debian/gbp.conf: - Setup for focal branching and use ubuntu/* tagging - Use multimaint-merge in dch and sign tags * debian/control: - Set Ubuntu Developers as maintainer - Update VCS informations to point to ubuntu/focal * dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669) * dbusMenu: Use proper argument name when parsing error (LP: #1881669) * dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795) * appIndicator: Remove the callbackIdle if we destroy while waiting it (LP: #1849142) * StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785) * appIndicator: Ignore further icons creation during an idle (LP: #1849142) * README: Remove statement about indicator-multiload not being supported * statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and returned error (LP: #1896785) * interfaces: Sync interfaces XML with upstream ones (LP: #1896785) * StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785) * appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396): - util: Use Shell's param to handle multiple named arguments - util: Delete proxyCancellables only if we didn't cancel already - util: Ignore errors if we can't find a listed dbus name - appIndicator: Cleanup the interface info properties map computation - appIndicator: Don't deep unpack changed properties array - appIndicator: Use native checks to look for equal emblems - appIndicator: Mark a valid cached icon as inUse again - appIndicator: Correctly mark cached GIcon's as in use - iconCache: Rewrite simplifying the usage for GIcon's only - iconCache: Dispose an icon when we remove it - iconCache: Increase the garbage-collector timings - appIndicator: Only iterate through the proxy available properties - appIndicator: Don't try to check equality on Pixmap variants - util: Try to batch properties updates when they comes close enough - appIndicator: Accumulate signals to batch close updates - appIndicator: Emit the same signal once on properties updates - appIndicator: Improve the warning message on lookup failed [ Fini Jastrow ] * appIndicator: Remove unneeded padding (LP: #1896779) * appIndicator: Fix 'reduce padding' for some icons (LP: #1896779) [ Sergio Costas ] * Wait until the desktop ends starting up (LP: #1870795) * Wait until Gtk.IconTheme.get_default() works (LP: #1870795) * Don't fail if no icon is found (LP: #1849142) * Use signal to detect display availability (LP: #1870795) [ Tasos Sahanidis ] * kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785) -- Marco Trevisan (Treviño) Wed, 23 Sep 2020 18:47:33 +0200 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Released Bug description: [ Impact ] Destroying an appindicator dbusmenu we fail with some (non-fatal) errors [ Test case ] Open/Close an application with appindicator Ensure that gnome-shell journal (journalctl -b0 /usr/bin/gnome-shell) doesn't show any error related to Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1. Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy is null DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9 wrapper@resource:///org/gnome/gjs/modules [ Regression potential ] Indicator may not show at all, but that was what we expect on destruction. --- jlquinn@cerberus:~$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell-extension-appindicator gnome-shell-extension-appindicator: Installed: 18.04.1 Candidate: 18.04.1 Version table: *** 18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu
[Desktop-packages] [Bug 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
This bug was fixed in the package gnome-shell-extension-appindicator - 33.1-0ubuntu0.20.04.1 --- gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream stable release * debian/gbp.conf: - Setup for focal branching and use ubuntu/* tagging - Use multimaint-merge in dch and sign tags * debian/control: - Set Ubuntu Developers as maintainer - Update VCS informations to point to ubuntu/focal * dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669) * dbusMenu: Use proper argument name when parsing error (LP: #1881669) * dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795) * appIndicator: Remove the callbackIdle if we destroy while waiting it (LP: #1849142) * StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785) * appIndicator: Ignore further icons creation during an idle (LP: #1849142) * README: Remove statement about indicator-multiload not being supported * statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and returned error (LP: #1896785) * interfaces: Sync interfaces XML with upstream ones (LP: #1896785) * StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785) * appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396): - util: Use Shell's param to handle multiple named arguments - util: Delete proxyCancellables only if we didn't cancel already - util: Ignore errors if we can't find a listed dbus name - appIndicator: Cleanup the interface info properties map computation - appIndicator: Don't deep unpack changed properties array - appIndicator: Use native checks to look for equal emblems - appIndicator: Mark a valid cached icon as inUse again - appIndicator: Correctly mark cached GIcon's as in use - iconCache: Rewrite simplifying the usage for GIcon's only - iconCache: Dispose an icon when we remove it - iconCache: Increase the garbage-collector timings - appIndicator: Only iterate through the proxy available properties - appIndicator: Don't try to check equality on Pixmap variants - util: Try to batch properties updates when they comes close enough - appIndicator: Accumulate signals to batch close updates - appIndicator: Emit the same signal once on properties updates - appIndicator: Improve the warning message on lookup failed [ Fini Jastrow ] * appIndicator: Remove unneeded padding (LP: #1896779) * appIndicator: Fix 'reduce padding' for some icons (LP: #1896779) [ Sergio Costas ] * Wait until the desktop ends starting up (LP: #1870795) * Wait until Gtk.IconTheme.get_default() works (LP: #1870795) * Don't fail if no icon is found (LP: #1849142) * Use signal to detect display availability (LP: #1870795) [ Tasos Sahanidis ] * kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785) -- Marco Trevisan (Treviño) Wed, 23 Sep 2020 18:47:33 +0200 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1884396 Title: Ubuntu freezing intermittently when the mega.nz appindicator is loaded Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Released Bug description: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing (but even opening/closing the app should be enough to trigger Alternatively use this test tool: https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). In general there has been a refactor of the iconCache, so internally it may happen that we load an icon more times, or that there could be an increase in RAM usage as per missing garbage collecting of it. I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when
[Desktop-packages] [Bug 1896779] Re: Appindicators use too much padding
This bug was fixed in the package gnome-shell-extension-appindicator - 33.1-0ubuntu0.20.04.1 --- gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium [ Marco Trevisan (Treviño) ] * New upstream stable release * debian/gbp.conf: - Setup for focal branching and use ubuntu/* tagging - Use multimaint-merge in dch and sign tags * debian/control: - Set Ubuntu Developers as maintainer - Update VCS informations to point to ubuntu/focal * dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669) * dbusMenu: Use proper argument name when parsing error (LP: #1881669) * dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795) * appIndicator: Remove the callbackIdle if we destroy while waiting it (LP: #1849142) * StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785) * appIndicator: Ignore further icons creation during an idle (LP: #1849142) * README: Remove statement about indicator-multiload not being supported * statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and returned error (LP: #1896785) * interfaces: Sync interfaces XML with upstream ones (LP: #1896785) * StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785) * appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396): - util: Use Shell's param to handle multiple named arguments - util: Delete proxyCancellables only if we didn't cancel already - util: Ignore errors if we can't find a listed dbus name - appIndicator: Cleanup the interface info properties map computation - appIndicator: Don't deep unpack changed properties array - appIndicator: Use native checks to look for equal emblems - appIndicator: Mark a valid cached icon as inUse again - appIndicator: Correctly mark cached GIcon's as in use - iconCache: Rewrite simplifying the usage for GIcon's only - iconCache: Dispose an icon when we remove it - iconCache: Increase the garbage-collector timings - appIndicator: Only iterate through the proxy available properties - appIndicator: Don't try to check equality on Pixmap variants - util: Try to batch properties updates when they comes close enough - appIndicator: Accumulate signals to batch close updates - appIndicator: Emit the same signal once on properties updates - appIndicator: Improve the warning message on lookup failed [ Fini Jastrow ] * appIndicator: Remove unneeded padding (LP: #1896779) * appIndicator: Fix 'reduce padding' for some icons (LP: #1896779) [ Sergio Costas ] * Wait until the desktop ends starting up (LP: #1870795) * Wait until Gtk.IconTheme.get_default() works (LP: #1870795) * Don't fail if no icon is found (LP: #1849142) * Use signal to detect display availability (LP: #1870795) [ Tasos Sahanidis ] * kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785) -- Marco Trevisan (Treviño) Wed, 23 Sep 2020 18:47:33 +0200 ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1896779 Title: Appindicators use too much padding Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Released Bug description: [ Impact ] Padding on indicators is too wide, as per double-multiplication of the same, leading to very spread icons: https://user- images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea- 9d65-ec9053290b2f.png [ Test case ] - Open various indicator, padding should be reduced to be consistent with other icons, for example: https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png [ Regression potential ] Very low, there's just a style change to ensure we don't apply the very same padding two times. -- Upstream fix: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896785] Re: Exported DBus interface is missing info or using wrong names
This bug was fixed in the package gnome-shell-extension-appindicator -
33.1-0ubuntu0.20.04.1
---
gnome-shell-extension-appindicator (33.1-0ubuntu0.20.04.1) focal; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream stable release
* debian/gbp.conf:
- Setup for focal branching and use ubuntu/* tagging
- Use multimaint-merge in dch and sign tags
* debian/control:
- Set Ubuntu Developers as maintainer
- Update VCS informations to point to ubuntu/focal
* dbusMenu: Use GCancellable to stop pending async operations (LP: #1881669)
* dbusMenu: Use proper argument name when parsing error (LP: #1881669)
* dbusMenu: Stop idle requests if we've been destroyed (LP: #1870795)
* appIndicator: Remove the callbackIdle if we destroy while waiting it
(LP: #1849142)
* StatusNotifierWatcher: Remove ProtocolVersion method (LP: #1896785)
* appIndicator: Ignore further icons creation during an idle (LP: #1849142)
* README: Remove statement about indicator-multiload not being supported
* statusNotifierWatcher: Fix RegisterStatusNotifierHost method name and
returned error (LP: #1896785)
* interfaces: Sync interfaces XML with upstream ones (LP: #1896785)
* StatusNotifierItem: Disable Tooltip properties and signals (LP: #1896785)
* appIndicator: Don't waste CPU cycles to handle icon updates (LP: #1884396):
- util: Use Shell's param to handle multiple named arguments
- util: Delete proxyCancellables only if we didn't cancel already
- util: Ignore errors if we can't find a listed dbus name
- appIndicator: Cleanup the interface info properties map computation
- appIndicator: Don't deep unpack changed properties array
- appIndicator: Use native checks to look for equal emblems
- appIndicator: Mark a valid cached icon as inUse again
- appIndicator: Correctly mark cached GIcon's as in use
- iconCache: Rewrite simplifying the usage for GIcon's only
- iconCache: Dispose an icon when we remove it
- iconCache: Increase the garbage-collector timings
- appIndicator: Only iterate through the proxy available properties
- appIndicator: Don't try to check equality on Pixmap variants
- util: Try to batch properties updates when they comes close enough
- appIndicator: Accumulate signals to batch close updates
- appIndicator: Emit the same signal once on properties updates
- appIndicator: Improve the warning message on lookup failed
[ Fini Jastrow ]
* appIndicator: Remove unneeded padding (LP: #1896779)
* appIndicator: Fix 'reduce padding' for some icons (LP: #1896779)
[ Sergio Costas ]
* Wait until the desktop ends starting up (LP: #1870795)
* Wait until Gtk.IconTheme.get_default() works (LP: #1870795)
* Don't fail if no icon is found (LP: #1849142)
* Use signal to detect display availability (LP: #1870795)
[ Tasos Sahanidis ]
* kstatusnotifierwatcher: Implement ProtocolVersion property (LP: #1896785)
-- Marco Trevisan (Treviño) Wed, 23 Sep 2020
18:47:33 +0200
** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
Status in gnome-shell-extension-appindicator package in Ubuntu:
Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
Fix Released
Bug description:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods
and properties are missing or invalid
[ Test case ]
Run:
gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher \
--method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher"
ProtocolVersion
-> Should return (<0>,)
In particular, the API should contain
gdbus introspect --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher
node /StatusNotifierWatcher {
Default fdo properties stuff
interface org.kde.StatusNotifierWatcher {
interface org.kde.StatusNotifierWatcher {
methods:
RegisterStatusNotifierItem(in s service);
RegisterStatusNotifierHost(in s service);
signals:
StatusNotifierItemRegistered(s arg_0);
StatusNotifierItemUnregistered(s arg_0);
StatusNotifierHostRegistered();
StatusNotifierHostUnregistered();
properties:
@org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
readonly as RegisteredStatusNotifierItems = [ ... list of indicators
path/obj-names ... ];
readonly b IsStatusNotifierHostRegistered = true;
readonly i ProtocolVersion = 0;
};
};
In the old version we had an invalid "RegisterNotificationHost" method (not
[Desktop-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
This bug was fixed in the package libevdev - 1.5.8+dfsg-1ubuntu0.1 --- libevdev (1.5.8+dfsg-1ubuntu0.1) bionic; urgency=medium * debian/patches/Add libevdev_disable_property: - needed for libinput quirks on some Dell Precision configurations (lp: #1906341) -- Kai-Chuan Hsieh Thu, 03 Dec 2020 15:37:38 +0100 ** Changed in: libevdev (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: libinput (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libevdev in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in libevdev source package in Bionic: Fix Released Status in libinput source package in Bionic: Fix Committed Status in libevdev source package in Focal: Fix Released Status in libinput source package in Focal: Fix Released Status in libevdev source package in Groovy: Fix Released Status in libinput source package in Groovy: Fix Released Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1
[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear
Arff I was too fast. It was ok, but it restarded 5 min ago >.> -- 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/1766775 Title: Notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849142] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870795] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] An app-indicator icon does not show when I login using the default gnome session (wayland). If I choose the xorg session, the icon shows as normal. Under wayland, the icon does appear if I lock my session then log back in. [ Test case ] Run a desktop session (better if Ubuntu wayland), ensure that all the startup-launched appindicators are showing in the status area. One affected indicator seems to be https://github.com/juliagoda/antimicroX/ [ Regression potential ] Indicators may not load at all, wrong icons are shown instead. --- Upstream change: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/231 $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ apt-cache policy gnome-session-wayland gnome-session-wayland: Installed: (none) Candidate: 3.36.0-2ubuntu1 Version table: 3.36.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 15:30:40 2020 InstallationDate: Installed on 2019-12-15 (111 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896779] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1896779 Title: Appindicators use too much padding Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Padding on indicators is too wide, as per double-multiplication of the same, leading to very spread icons: https://user- images.githubusercontent.com/16012374/77627511-505f3780-6f47-11ea- 9d65-ec9053290b2f.png [ Test case ] - Open various indicator, padding should be reduced to be consistent with other icons, for example: https://user-images.githubusercontent.com/16012374/77627515-52c19180-6f47-11ea-8edb-9861ad518f8e.png [ Regression potential ] Very low, there's just a style change to ensure we don't apply the very same padding two times. -- Upstream fix: https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/219 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881669] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1881669 Title: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Destroying an appindicator dbusmenu we fail with some (non-fatal) errors [ Test case ] Open/Close an application with appindicator Ensure that gnome-shell journal (journalctl -b0 /usr/bin/gnome-shell) doesn't show any error related to Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1. Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy is null DBusClient<._beginRequestProperties@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/dbusMenu.js:247:9 wrapper@resource:///org/gnome/gjs/modules [ Regression potential ] Indicator may not show at all, but that was what we expect on destruction. --- jlquinn@cerberus:~$ lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 jlquinn@cerberus:~/Videos$ apt-cache policy gnome-shell-extension-appindicator gnome-shell-extension-appindicator: Installed: 18.04.1 Candidate: 18.04.1 Version table: *** 18.04.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status This may be related to bug 1879016, but my stack trace is smaller and different. I enabled the appindicator extension, and see the following my logs: Jun 01 17:24:15 cerberus gnome-shell[3318]: Object .Gjs_AppIndicatorIconActor__1 (0x5582a2e9b240), has been already finalized. Impossible to set any property to it. Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: == Stack trace for context 0x5582a28894b0 == Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #0 0x7ffc718eda00 b resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f70f00b5de0 @ 87) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #1 0x5582a2c5a930 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:93 (0x7f6ee00 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #2 0x7ffc718ee5e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #3 0x7ffc718eed80 b self-hosted:916 (0x7f70f00f12b8 @ 367) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #4 0x7ffc718eee70 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f70f00d2230 @ 386) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #5 0x5582a2c5a8a8 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:190 (0x7f6ee00adf78 Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #6 0x7ffc718efac0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #7 0x5582a2c5a800 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:176 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #8 0x7ffc718f06a0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #9 0x5582a2c5a760 i /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:170 (0x7f6e Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #10 0x7ffc718f1290 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f70f00b5de0 @ 71) Jun 01 17:24:15 cerberus org.gnome.Shell.desktop[3318]: #11 0x7ffc718f1a50 b self-hosted:918 (0x7f70f00f12b8 @ 394) Jun 01 17:24:15 cerberus gnome-shell[3318]: [AppIndicatorSupport-WARN] While reading menu layout: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1. Jun 01 17:24:15 cerberus gnome-shell[3318]: JS ERROR: TypeError: this._proxy is null
[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
Sadly I cannot release the focal SRU as it seems that the signon package FTBFS on ppc64el there: https://launchpad.net/ubuntu/+source/signon/8.59+17.10.20170606-0ubuntu2.20.04.1/+build/20365793 It seems to have built fine previously. Can someone take a look? ** Changed in: signon (Ubuntu Focal) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Incomplete Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884396] Update Released
The verification of the Stable Release Update for gnome-shell-extension- appindicator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1884396 Title: Ubuntu freezing intermittently when the mega.nz appindicator is loaded Status in Ubuntu AppIndicators: Unknown Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: Fix Committed Bug description: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing (but even opening/closing the app should be enough to trigger Alternatively use this test tool: https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). In general there has been a refactor of the iconCache, so internally it may happen that we load an icon more times, or that there could be an increase in RAM usage as per missing garbage collecting of it. I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Desktop-packages] [Bug 1896785] Update Released
The verification of the Stable Release Update for gnome-shell-extension-
appindicator has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the event that you encounter a regression using the package
from -updates please report a new bug using ubuntu-bug and tag the bug
report regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1896785
Title:
Exported DBus interface is missing info or using wrong names
Status in gnome-shell-extension-appindicator package in Ubuntu:
Fix Released
Status in gnome-shell-extension-appindicator source package in Focal:
Fix Committed
Bug description:
[ Impact ]
GNOME shell when using this indicator should export the
org.kde.StatusNotifierWatcher dbus interface, although some methods
and properties are missing or invalid
[ Test case ]
Run:
gdbus call --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher \
--method org.freedesktop.DBus.Properties.Get "org.kde.StatusNotifierWatcher"
ProtocolVersion
-> Should return (<0>,)
In particular, the API should contain
gdbus introspect --session --dest org.gnome.Shell --object-path
/StatusNotifierWatcher
node /StatusNotifierWatcher {
Default fdo properties stuff
interface org.kde.StatusNotifierWatcher {
interface org.kde.StatusNotifierWatcher {
methods:
RegisterStatusNotifierItem(in s service);
RegisterStatusNotifierHost(in s service);
signals:
StatusNotifierItemRegistered(s arg_0);
StatusNotifierItemUnregistered(s arg_0);
StatusNotifierHostRegistered();
StatusNotifierHostUnregistered();
properties:
@org.qtproject.QtDBus.QtTypeName.Out0("QStringList")
readonly as RegisteredStatusNotifierItems = [ ... list of indicators
path/obj-names ... ];
readonly b IsStatusNotifierHostRegistered = true;
readonly i ProtocolVersion = 0;
};
};
In the old version we had an invalid "RegisterNotificationHost" method (not
specified by specs nor used)
We didn't expose the ProtocolVersion
---
[ Regression potential ]
We won't expose anymore some NON-STANDARD and NEVER USED dbus methods such as:
- RegisterNotificationHost (was un-implemlented anyways)
- ProtocolVersion (this was supposed to be a property, not a method)
There are some changes to the interfaces xml files to follow the
standard ones, but they don't involve any change, could happen though
that we don't list a property that an indicator exposes lazily (don't
think there are in real world).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1896785/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905756] Update Released
The verification of the Stable Release Update for gnome-desktop3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1905756 Title: SRU the current 3.36.8 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.36.8 * Regression potential The update has some test and translations fixes and a change the version, check that translations and version display in settings are correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1905756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905756] Re: SRU the current 3.36.8 stable update
This bug was fixed in the package gnome-desktop3 - 3.36.8-0ubuntu1 --- gnome-desktop3 (3.36.8-0ubuntu1) focal; urgency=medium * New upstream release (lp: #1905756) * debian/patches/tests-Don-t-run-at-build-time.patch: - removed since the change is in the new version -- Sebastien Bacher Thu, 26 Nov 2020 17:37:26 +0100 ** Changed in: gnome-desktop3 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1905756 Title: SRU the current 3.36.8 stable update Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.36.8 * Regression potential The update has some test and translations fixes and a change the version, check that translations and version display in settings are correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1905756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
This bug was fixed in the package libevdev - 1.9.0+dfsg-1ubuntu0.1 --- libevdev (1.9.0+dfsg-1ubuntu0.1) focal; urgency=medium * debian/patches/Add libevdev_disable_property: - needed for libinput quirks on some Dell Precision configurations (lp: #1906341) -- Kai-Chuan Hsieh Thu, 03 Dec 2020 15:32:01 +0100 ** Changed in: libevdev (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libevdev in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in libevdev source package in Bionic: Fix Released Status in libinput source package in Bionic: Fix Committed Status in libevdev source package in Focal: Fix Released Status in libinput source package in Focal: Fix Released Status in libevdev source package in Groovy: Fix Released Status in libinput source package in Groovy: Fix Released Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 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:
[Desktop-packages] [Bug 463762] Re: After update to karmic ALT-F[1-8] switches to text console
*** This bug is a duplicate of bug 520546 *** https://bugs.launchpad.net/bugs/520546 ** This bug is no longer a duplicate of bug 730307 ALT-F[1-8] switches to text console ** This bug has been marked a duplicate of bug 520546 [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right -- 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/463762 Title: After update to karmic ALT-F[1-8] switches to text console Status in xorg-server package in Ubuntu: Expired Bug description: Reporting to X-Server as I don't know where else this could be caused. After upgrading to Karmic I now have the strange behavior that not only ALT-CTRL-F[1-8] switches to the text console from X-Server, but also ALT-F[1-8] does this switching. I don't know where this comes from, but it breaks lots of stuff, i.e. ALT-F4 to close an app, ALT-F2 to open the quick-start-applet, ... Strange thing is that if I switch back to the X-Server from the text console with ALT-F7, the actual keyboard action is executed in the X-Server, i.e. if I press ALT-F4, the text console is shown, when I switch back, the current application is closed! Every time I switch (either with ALT-CTRL-F[1-8] or with ALT-F[1-8]), the following is printed to the system log: Oct 29 21:59:51 dstathink acpid: client 1258[0:0] has disconnected Oct 29 21:59:51 dstathink acpid: client connected from 1258[0:0] Oct 29 21:59:51 dstathink anacron[2150]: Anacron 2.3 started on 2009-10-29 Oct 29 21:59:51 dstathink anacron[2150]: Normal exit (0 jobs run) Oct 29 21:59:51 dstathink kernel: [10749.984755] CPU0 attaching NULL sched-domain. Oct 29 21:59:51 dstathink kernel: [10749.984760] CPU1 attaching NULL sched-domain. Oct 29 21:59:51 dstathink kernel: [10750.010232] CPU0 attaching sched-domain: Oct 29 21:59:51 dstathink kernel: [10750.010240] domain 0: span 0-1 level MC Oct 29 21:59:51 dstathink kernel: [10750.010246] groups: 0 1 Oct 29 21:59:51 dstathink kernel: [10750.010258] CPU1 attaching sched-domain: Oct 29 21:59:51 dstathink kernel: [10750.010263] domain 0: span 0-1 level MC Oct 29 21:59:51 dstathink kernel: [10750.010268] groups: 1 0 $ lsb_release -rd Description:Ubuntu 9.10 Release:9.10 ProblemType: Bug Architecture: amd64 Date: Thu Oct 29 21:56:28 2009 DistroRelease: Ubuntu 9.10 MachineType: LENOVO 205545G Package: xserver-xorg 1:7.4+3ubuntu7 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=UUID=00c3d061-bae6-42a6-a329-deefb7d0d350 ro resume=/dev/sda2 usbcore.autosuspend=1 quiet splash crashkernel=384M-2G:64M,2G-:128M ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-15.49+tuxonice1-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu7 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati N/A SourcePackage: xorg Uname: Linux 2.6.31-15-generic x86_64 dmi.bios.date: 05/15/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET71WW (3.01 ) dmi.board.name: 205545G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET71WW(3.01):bd05/15/2009:svnLENOVO:pn205545G:pvrThinkPadT500:rvnLENOVO:rn205545G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 205545G dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO fglrx: Not loaded system: distro: Ubuntu architecture: x86_64kernel: 2.6.31-15-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/463762/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766775] Re: Notifications do not disappear
Hello, me again. I just did another update with headers (actually 5.4.0-58-generic). I put back notifications from settings before rebooting, and it seems to working perfectly now. I did apt autoremove after reboot, while I did it before the reboot the first time (cf my post #7). -- 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/1766775 Title: Notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900452] Re: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu-drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_
This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.2 --- ubuntu-drivers-common (1:0.8.6.2) groovy; urgency=medium * ubuntu-drivers: - Unify metapackage listing for --gpgpu and non --gpgpu mode. This relies on the more robust metapackage listing of the non --gpgpu mode (LP: #1900452). -- Alberto Milone Mon, 19 Oct 2020 13:42:45 +0200 ** Changed in: ubuntu-drivers-common (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1900452 Title: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu- drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__ Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Listing the supported drivers can fail if the linux-restricted-modules for it are not available in the archive. * These changes unify the code for listing drivers (whether --gpgpu is passed in or not) and make it more robust. [Test Case] * Install ubuntu-drivers-common (1:0.8.6.2) from -proposed. * Call "ubuntu-drivers list" and "ubuntu-drivers list --gpgpu", and make sure that neither crashes ubuntu-drivers. [Regression Potential] * Low, the code should catch all the KeyErrors now. The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.4~0.20.04.3, the problem page at https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** No longer affects: xorg-server (Ubuntu) ** No longer affects: xorg-server (Ubuntu Lucid) ** No longer affects: xorg-server (Ubuntu Maverick) ** No longer affects: xorg-server (Ubuntu Xenial) ** No longer affects: xorg-server (Ubuntu Bionic) ** No longer affects: xorg-server (Ubuntu Cosmic) ** No longer affects: xorg-server (Ubuntu Disco) ** No longer affects: xorg-server (Ubuntu Eoan) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Cosmic) ** No longer affects: linux (Ubuntu Disco) ** No longer affects: linux (Ubuntu Eoan) ** No longer affects: kbd (Ubuntu Maverick) ** No longer affects: kbd (Ubuntu Lucid) ** No longer affects: console-setup (Ubuntu Maverick) ** No longer affects: console-setup (Ubuntu Lucid) -- 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/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $
[Desktop-packages] [Bug 1900452] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1900452 Title: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu- drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__ Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Listing the supported drivers can fail if the linux-restricted-modules for it are not available in the archive. * These changes unify the code for listing drivers (whether --gpgpu is passed in or not) and make it more robust. [Test Case] * Install ubuntu-drivers-common (1:0.8.6.2) from -proposed. * Call "ubuntu-drivers list" and "ubuntu-drivers list --gpgpu", and make sure that neither crashes ubuntu-drivers. [Regression Potential] * Low, the code should catch all the KeyErrors now. The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.4~0.20.04.3, the problem page at https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901609] Update Released
The verification of the Stable Release Update for signon has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Committed Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901609] Re: signond causes qprocess crash
This bug was fixed in the package signon - 8.59+17.10.20170606-0ubuntu2.20.10.1 --- signon (8.59+17.10.20170606-0ubuntu2.20.10.1) groovy; urgency=medium * Add ubuntu_01_rtti.diff to remove the no rtti flags as they'd break compatibility with QProcess (LP: #1901609) * Build depend on quilt and integrate into debian/rules. Since this this source uses the legacy v1 format we need to manually wire up patching instead of having dpkg-source handle it -- Harald Sitter Mon, 23 Nov 2020 13:24:59 +0100 ** Changed in: signon (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash Status in signon package in Ubuntu: Fix Released Status in signon source package in Focal: Fix Committed Status in signon source package in Groovy: Fix Released Status in signon source package in Hirsute: Fix Released Bug description: [Impact] Without the patch users are unable to add google accounts because signond crashes. This prevents users from using KDE's online accounts feature for google. The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. [Test Case] - in a plasma session - install kio-gdrive - run `systemsettings5 kcm_kaccounts` - add a new account - click on google - wait for login window to appear - signond shouldn't be crashing [Where problems could occur] Cannot think of any. It simply adds type info to the objects. Also upstream has rtti disabled for months and I'm not aware of any problems. [Other Info] This is a fairly grave issue as far as user experience is concerned. I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906341] Re: Touchpad button doesn't work on Dell Precision 7550/7750
This bug was fixed in the package libevdev - 1.9.1+dfsg-1ubuntu0.1 --- libevdev (1.9.1+dfsg-1ubuntu0.1) groovy; urgency=medium * debian/patches/Add libevdev_disable_property: - needed for libinput quirks on some Dell Precision configurations (lp: #1906341) -- Kai-Chuan Hsieh Thu, 03 Dec 2020 15:31:26 +0100 ** Changed in: libevdev (Ubuntu Groovy) Status: Fix Committed => Fix Released ** Changed in: libinput (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libevdev in Ubuntu. https://bugs.launchpad.net/bugs/1906341 Title: Touchpad button doesn't work on Dell Precision 7550/7750 Status in OEM Priority Project: New Status in libevdev package in Ubuntu: Fix Released Status in libinput package in Ubuntu: Fix Released Status in libevdev source package in Bionic: Fix Committed Status in libinput source package in Bionic: Fix Committed Status in libevdev source package in Focal: Fix Committed Status in libinput source package in Focal: Fix Committed Status in libevdev source package in Groovy: Fix Released Status in libinput source package in Groovy: Fix Released Bug description: [Impact] * The touchpad's right button become no function after update to 5.4 kernel * The INPUT_PROP_BUTTONPAD property is set by 5.4 kernel, so that libinput regard it as clickpad, the root cause is that the touchpad firmware doesn't config correctly. * Add a model quirk to unset the bit can make touchpad's right button works normally. [Test Case] * 1. Boot into Ubuntu 2. Identify touchpad input device number, can be obtained in $HOME/.local/share/xorg/Xorg.0.log 3. $ udevadm info /sys/class/input/inputX check PROP environment variable, it is 5 if INPUT_PROP_BUTTONPAD property is set 4. And the touchpad right button become no function 5. After update the libevdev with disable_property API and libinput10 with model quirk 6. reboot 7. The input device PROP is still 5, but touchpad right button is workable [Where problems could occur] * For libevdev2 package, backport the upstream commit: https://gitlab.freedesktop.org/libevdev/libevdev/-/commit/4226c7801b4ea1b0c7d1eaac47ca24ece8f24809 The API is not originally exist in the system, so it will only be utilized by our model quirk. * For libinput, add model quirk for the platform to disable INPUT_PROP_BUTTONPAD bit. Only disable the INPUT_PROP_BUTTONPAD for specified model, and it doesn't issue any IO command to kernel, so the behavior should be the same as previous kernel when INPUT_PROP_BUTTONPAD is not set. [Other Info] * A public bug is reported https://www.dell.com/community/Linux-Developer-Systems/Touchpad-right-click-button-not-working-with-Ubuntu-20-04-on/td-p/7636831 * A workable build for Bionic/Focal/Groovy are in my ppa https://launchpad.net/~kchsieh/+archive/ubuntu/training --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1646 F pulseaudio BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09c3] InstallationDate: Installed on 2020-12-01 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Precision 7550 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2964a5af-ac17-45ee-a009-41879da14e1b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic ubuntu Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/01/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/01/2020:svnDellInc.:pnPrecision7550:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7550 dmi.product.sku: 09C3 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1
[Desktop-packages] [Bug 1908111] [NEW] package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-dev
Public bug reported: Just impossible to install. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgl-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: libx11-dev:amd64: Install libglx-dev:amd64: Install libgl-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 19:03:55 2020 ErrorMessage: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 InstallationDate: Installed on 2020-11-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libglvnd Title: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1908111 Title: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 Status in libglvnd package in Ubuntu: New Bug description: Just impossible to install. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgl-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: libx11-dev:amd64: Install libglx-dev:amd64: Install libgl-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Dec 14 19:03:55 2020 ErrorMessage: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 InstallationDate: Installed on 2020-11-27 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libglvnd Title: package libgl-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/GL/gl.h », qui appartient aussi au paquet mesa-libgl-devel 20.2.3-268.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1908111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4
Using the GTK greeter and also tried Slick greeter, both show nothing - a blank screen - and I would have to ctrl alt f1, get to a terminal screen, put in a username and password there and then "startx" but the f7 or wherever the lightdm goes, that does not work when switching to it. -- 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/1849886 Title: lightdm does not work on eoan on raspberry pi 4 Status in lightdm package in Ubuntu: Incomplete Bug description: if you follow the directions on https://wiki.ubuntu.com/ARM/RaspberryPi sudo apt-get install xubuntu-desktop about 20% thru the installation it will ask which window manager you want (using dpkg-reconfigure). if you select lightdm, you will only get a blank greeter screen after you reboot. using sudo dpkg-reconfigure gdm3 resets this to gdm3 and after a reboot, everything is fine. this was done on a clean armhf eoan install on a 4gb raspberry pi 4B. I have done the install several times. This bug is repeatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1849886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908107] [NEW] libfprint may cause fprintd to crash on identification
Public bug reported: [ Impact ] When identification is used we may get a crash or a critical error when parsing the prints gallery data [ Test case ] Run: - fprintd-verify any With a fingerprint reader supporting identification. Fprintd should work as expected and journalctl -u fprintd.service should not show any critical error handling GObject's [ Regression potential ] Prints data can be leaked. ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: libfprint (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Affects: libfprint (Ubuntu Groovy) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: libfprint (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released ** Changed in: libfprint (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Groovy) Status: New => In Progress ** Changed in: libfprint (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1908107 Title: libfprint may cause fprintd to crash on identification Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: In Progress Status in libfprint source package in Groovy: In Progress Bug description: [ Impact ] When identification is used we may get a crash or a critical error when parsing the prints gallery data [ Test case ] Run: - fprintd-verify any With a fingerprint reader supporting identification. Fprintd should work as expected and journalctl -u fprintd.service should not show any critical error handling GObject's [ Regression potential ] Prints data can be leaked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1908107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897454] Re: [snap] Chromium dev cuts off Wayland display
Alberto, please note that the snap already has libEGL.so and libGLESv2.so, they live in /snap/chromium/current/usr/lib/chromium- browser/. -- 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/1897454 Title: [snap] Chromium dev cuts off Wayland display Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since v87 Chromium ships with support for Ozone/Wayland: https://www.phoronix.com/scan.php?page=news_item=Chrome-87-Ozone-Try-Again. This build flag is not disabled in dev (edge) channel build, so it should be possible to run Chromium with flags --enable-features=UseOzonePlatform --ozone-platform=wayland. This does not work due to environment variable DISABLE_WAYLAND set to 1 here: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/tree/snapcraft.yaml?h=dev#n18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908103] Re: /usr/libexec/fprintd:11:img_process_data:vfs301_proto_process_data:vfs301_proto_process_event_cb:transfer_finish_cb:g_task_return_now
*** This bug is a duplicate of bug 1905597 *** https://bugs.launchpad.net/bugs/1905597 ** This bug has been marked a duplicate of bug 1905597 Device using vfs301 driver crashes during verification -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1908103 Title: /usr/libexec/fprintd:11:img_process_data:vfs301_proto_process_data:vfs301_proto_process_event_cb:transfer_finish_cb:g_task_return_now Status in fprintd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/512569f576c2e8557c935f06ab7b881b6fe28a1f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908103] [NEW] /usr/libexec/fprintd:11:img_process_data:vfs301_proto_process_data:vfs301_proto_process_event_cb:transfer_finish_cb:g_task_return_now
*** This bug is a duplicate of bug 1905597 *** https://bugs.launchpad.net/bugs/1905597 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/512569f576c2e8557c935f06ab7b881b6fe28a1f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1908103 Title: /usr/libexec/fprintd:11:img_process_data:vfs301_proto_process_data:vfs301_proto_process_event_cb:transfer_finish_cb:g_task_return_now Status in fprintd package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding fprintd. This problem was most recently seen with package version 1.90.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/512569f576c2e8557c935f06ab7b881b6fe28a1f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1908103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
