[Desktop-packages] [Bug 1858611] [NEW] package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in pa
Public bug reported: after upgrade packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-core 20200103-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 7 10:22:10 2020 Dependencies: ErrorMessage: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 InstallationDate: Installed on 2019-12-22 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.5 SourcePackage: fonts-noto Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-noto (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 fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1858611 Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese- Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 Status in fonts-noto package in Ubuntu: New Bug description: after upgrade packages ProblemType: Package DistroRelease: Ubuntu 20.04 Package: fonts-noto-core 20200103-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 7 10:22:10 2020 Dependencies: ErrorMessage: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 InstallationDate: Installed on 2019-12-22 (15 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.5 SourcePackage: fonts-noto Title: package fonts-noto-core 20200103-1 failed to install/upgrade: trying to overwrite '/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf', which is also in package fonts-noto-unhinted 20181227-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1858611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810126] Re: Extremely visible screen tearing with VLC and Firefox/Chromium
*** This bug is a duplicate of bug 1754284 *** https://bugs.launchpad.net/bugs/1754284 ** This bug has been marked a duplicate of bug 1754284 Fullscreen windows (like Totem) are tearing in gnome-shell Xorg sessions -- 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/1810126 Title: Extremely visible screen tearing with VLC and Firefox/Chromium Status in mutter package in Ubuntu: New Bug description: When watching videos in VLC on an external screen there is extremely visible screen tearing. But it's likely that the external screen only makes the problem worse as this website shows a lot of vsync issues in both Firefox and Chromium even with just the single screen: https://www.vsynctester.com/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 30 23:16:26 2018 InstallationDate: Installed on 2018-05-31 (213 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1810126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853094] Re: [modeset] Screen tearing when using multiple monitors
Triaged. This tearing with multiple monitors is a known consequence of the Xorg modesetting driver. The upstream bug is https://gitlab.freedesktop.org/xorg/xserver/issues/244 (shared with bug 1846398, which needs a similar fix). ** Summary changed: - Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock + [modeset] Screen tearing when using multiple monitors ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Tags removed: xrandr-scaling ** Tags added: multimonitor ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #244 https://gitlab.freedesktop.org/xorg/xserver/issues/244 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/244 Importance: Unknown Status: Unknown ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Tags added: tearing -- 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/1853094 Title: [modeset] Screen tearing when using multiple monitors Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Triaged Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1853094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754284] Re: Fullscreen windows (like Totem) are tearing in gnome-shell Xorg sessions
** Package changed: mutter (Ubuntu) => xorg-server (Ubuntu)
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #244
https://gitlab.freedesktop.org/xorg/xserver/issues/244
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/issues/244
Importance: Unknown
Status: Unknown
** Tags added: tearing
--
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/1754284
Title:
Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
sessions
Status in X.Org X server:
Unknown
Status in xorg-server package in Ubuntu:
Triaged
Bug description:
Fullscreen windows (like Totem) are tearing in gnome-shell Xorg
sessions.
This is probably to do with composite unredirecting... In compiz we
have a workaround to avoid this tearing by disallowing unredirect
("bypass") in known problematic video players. But I'm not sure if
mutter has such a workaround/whitelist/blacklist we can use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1754284/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846398] Re: Fractional scaling has significant visible tearing in Xorg sessions
** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Triaged ** Tags added: tearing -- 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/1846398 Title: Fractional scaling has significant visible tearing in Xorg sessions Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: On my laptop, fractional scaling seems fine, including watching a YouTube video. It has a quad HD display. Enabling fractional scaling on my desktop which is attached to a single 4k display, fractional scaling isn't usable. The video appears to be constantly refreshing and not using the same acceleration as if I just run at 100% or 200%. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 14:23:33 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-07-24 (435 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-07-19 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1846398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
** Tags added: xrandr-scaling ** 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/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: New Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
Hi Daniel, I verified from begining that i have Xorg and i enabeld from the begining only for Xorg by using information from this tutorial: http://ubuntuhandbook.org/index.php/2019/10/how-to-enable-fractional- scaling-in-ubuntu-19-10-eoan/ Using dconf and also using the terminal command afterwards.( I have attached printscreen with the settings from dconf). Also it was strange that after i came back from holiday it worked fine home ( 1x4k (150%scale) + 1xFHD + laptop), then at work i tried to scale the laptop display to 125% ( 2xFHD + laptop display) and had the issue again ... so it is random. ** Attachment added: "Screenshot from 2020-01-07 07-14-58.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+attachment/5318031/+files/Screenshot%20from%202020-01-07%2007-14-58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
** Changed in: pulseaudio (Ubuntu Eoan) Status: Triaged => Fix Committed -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 affects me too. -- 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/1850887 Title: Audio / Sound reverts to HDMI when power event occurs Status in pulseaudio package in Ubuntu: Confirmed Bug description: PulseAudio reverts the sound to HDMI all the time when a HDMI related power event occurs. That means, although I have set another USB sound device plugged in and set as default under sound settings, when an application like Kodi or the system shuts off the HDMI monitor and I reactivate the monitor, the sound is set to HDMI output again and again. That probably has to do with the fix to the reported Bug # 1711101 and definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10 two days ago. Setting the USB device as default does not help, even when done by PulseAudio mixer (gui) and removing HDMI output from the alternatives option. Expected behavior: PulseAudio keeps the sound setting to the selected device Actual behavior: PulseAudio changes to HDMI at every HDMI power event Annoying manual workaround: Setting the desired Audio option on the control panel after every HDMI power event again ProblemType: Bug DistroRelease: Ubuntu 19.10 Component: pulseaudio Version: 1:13.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
At the end of December I remember popey wanted to focus on 'Super' or 'Super-A' leaks so it makes sense to move that into bug 1856838 given there's some agreement on the test case there... ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/issues #1886 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856838] Re: gnome-shell using a lot of RAM
Based on discussions I remember from last month, I think this bug should track: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 ** This bug is no longer a duplicate of bug 1856516 Excessive memory usage by gnome-shell in 19.10 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1886 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1886 Importance: Unknown Status: Unknown ** Summary changed: - gnome-shell using a lot of RAM + gnome-shell using a lot of RAM after repeatedly pressing Super+A ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Confirmed -- 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/1856838 Title: gnome-shell using a lot of RAM after repeatedly pressing Super+A Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Just noticed my gnome-shell was using 3GB RSS. Which seems excessive. Spoke to duflu on irc and he suggested I file a bug, and to make sure I'm not using any extra extensions. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 10:49:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (681 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (89 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1856838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
This bug is now entirely Chris' again :) We still need some idea of a test case though, so 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858120] Re: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode
More likely I think it was the mutter 3.43.3 update, but still good news. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released ** Package changed: firefox (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in Mozilla Firefox: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.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/firefox/+bug/1858120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858120] Re: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode
More likely I think it was the mutter 3.34.3 update, but still good news. -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in Mozilla Firefox: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.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/firefox/+bug/1858120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
Since the bug report seems to suggest you're not using Wayland but have only enabled fractional scaling for Wayland and not Xorg, please try: gsettings set org.gnome.mutter experimental-features "['x11-randr- fractional-scaling']" ** 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/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
Just in case it is relevant, remember you need two different settings: Wayland: gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" Xorg: gsettings set org.gnome.mutter experimental-features "['x11-randr-fractional-scaling']" ** 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/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
Try step 2 in comment #11, or try replacing 'ubuntu-bug' with 'apport- cli'. -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858200] Re: pulseaudio produces garbage on HDMI after 19.10
** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Summary changed: - pulseaudio produces garbage on HDMI after 19.10 + Kernel 5.4.5-050405-generic produces garbage on HDMI audio after 19.10 -- 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/1858200 Title: Kernel 5.4.5-050405-generic produces garbage on HDMI audio after 19.10 Status in linux package in Ubuntu: New Bug description: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
Nevermind. Confirmed the same crash is affecting Ubuntu 19.10 too: https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b + + --- + This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Tags added: eoan -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b --- This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
It doesn't really look the same as bug 1841794 so ignore comment #2. This does however look like a pure gjs/mozjs bug. ** Tags removed: regression-retracer -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b --- This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
It appears you have a number of non-Ubuntu extensions installed: 'dash-to-pa...@jderose9.github.com' 'gpaste_integrat...@awamper.gmail.com' 'appindicatorsupp...@rgcjonas.gmail.com' 'systemmoni...@gnome-shell-extensions.gcampax.github.com' 'mpris22playerindica...@redsoxfan.cz.cc' 'mediapla...@patapon.info' 'indicator-sens...@alexmurray.github.com' 'dash-to-d...@micxgx.gmail.com' 'cpupo...@mko-sl.de' 'system-moni...@paradoxxx.zero.gmail.com' 'sensory-percept...@harlemsquirrel.github.io' 'desktop-icons@csoriano' Since we find so many bugs are caused by extensions we ask that you uninstall ALL of them (don't just disable them) and then tell us if the problem reoccurs. ** 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b --- This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858540] [NEW] /usr/bin/gnome-shell:5:ObjectInstance::disassociate_js_gobject:std::function:ObjectInstance::remove_wrapped_gobjects_if:ObjectInstance::update_heap_wrapper_weak_
*** This bug is a duplicate of bug 1858414 *** https://bugs.launchpad.net/bugs/1858414 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b 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: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1858540 Title: /usr/bin/gnome- shell:5:ObjectInstance::disassociate_js_gobject:std::function:ObjectInstance::remove_wrapped_gobjects_if:ObjectInstance::update_heap_wrapper_weak_pointers:js::gc::GCRuntime::callWeakPointerCompartmentCallbacks Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b 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/gnome-shell/+bug/1858540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858540] Re: /usr/bin/gnome-shell:5:ObjectInstance::disassociate_js_gobject:std::function:ObjectInstance::remove_wrapped_gobjects_if:ObjectInstance::update_heap_wrapper_weak_po
*** This bug is a duplicate of bug 1858414 *** https://bugs.launchpad.net/bugs/1858414 ** This bug has been marked a duplicate of bug 1858414 gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() -- 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/1858540 Title: /usr/bin/gnome- shell:5:ObjectInstance::disassociate_js_gobject:std::function:ObjectInstance::remove_wrapped_gobjects_if:ObjectInstance::update_heap_wrapper_weak_pointers:js::gc::GCRuntime::callWeakPointerCompartmentCallbacks Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.1+git20191024-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b 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/gnome-shell/+bug/1858540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858095] Re: 'Automatic Date and Time' automatically disabled when trying to enable
*** This bug is a duplicate of bug 1848309 *** https://bugs.launchpad.net/bugs/1848309 Confirming this is related to bug #1848309 except in this case was caused by VBoxService. $ systemctl status systemd-timesyncd ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2020-01-06 22:27:32 AEDT; 4min 17s ago └─ ConditionFileIsExecutable=!/usr/sbin/VBoxService was not met Docs: man:systemd-timesyncd.service(8) Jan 04 17:09:56 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. After purging virtualbox-guest-utils and virtualbox-6.0, ntp sync was successful: $ systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: active (running) since Tue 2020-01-07 10:59:06 AEDT; 4min 14s ago Docs: man:systemd-timesyncd.service(8) Main PID: 10499 (systemd-timesyn) Status: "Synchronized to time server for the first time [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com)." Tasks: 2 (limit: 4915) Memory: 1.7M CGroup: /system.slice/systemd-timesyncd.service └─10499 /lib/systemd/systemd-timesyncd Jan 07 10:59:06 ubuntu systemd[1]: Starting Network Time Synchronization... Jan 07 10:59:06 ubuntu systemd[1]: Started Network Time Synchronization. Jan 07 11:03:17 ubuntu systemd-timesyncd[10499]: Synchronized to time server for the first time [2001:67c:1560:8003::c7]:123 (ntp.ubuntu.com). ** This bug has been marked a duplicate of bug 1848309 "Automatic Date & Time" doesn't reflect the service status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1858095 Title: 'Automatic Date and Time' automatically disabled when trying to enable Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When enabling the "Automatic DateTime" in the gnome control center, it instantly turns off. The following is reported in syslog: Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
So, the X11 session is now up to 4526M/906M/107M, so it would seem that there is at least one bug that applies to X11 and one that applies to Wayland; possibly the same bug :) I don't think that I can reproduce the “Super-A leaks 50MB” bug. Repeatedly pressing that doesn't appear to result in any memory use change (except, *maybe*, repeatedly pressing -A and *then* memory usage increases after a minute or so of being idle?) Interestingly, *Xorg* memory usage appears to have increased, too; it's now at 2877M/657M/592M, which seems unusually high? -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-
** Tags added: disco eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1597840 Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in One Hundred Papercuts: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Bug description: Just got back from restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 12:14:30 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu3 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 DuplicateSignature: package:libjpeg-turbo8-dev:1.4.2-0ubuntu3 Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-13 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
2020-01-06 : https://forum.ubuntu- fr.org/viewtopic.php?pid=22202596#p22202596 It seems still broken in not-yet-released ubuntu 20.04. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858120] Re: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode
It looks like the latest gnome-shell fixed the issue for me: apt policy gnome-shell gnome-shell: Installed: 3.34.3-1ubuntu1 Candidate: 3.34.3-1ubuntu1 Version table: *** 3.34.3-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.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/firefox/+bug/1858120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858504] HookError_source_firefox.txt
apport information ** Attachment added: "HookError_source_firefox.txt" https://bugs.launchpad.net/bugs/1858504/+attachment/5318001/+files/HookError_source_firefox.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1858504 Title: Firefox 72 Released Status in firefox package in Ubuntu: New Bug description: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-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/firefox/+bug/1858504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858504] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1858504/+attachment/5318002/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1858504 Title: Firefox 72 Released Status in firefox package in Ubuntu: New Bug description: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-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/firefox/+bug/1858504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858504] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1858504/+attachment/5318000/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1858504 Title: Firefox 72 Released Status in firefox package in Ubuntu: New Bug description: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-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/firefox/+bug/1858504/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858504] [NEW] Firefox 72 Released
Public bug reported: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: - New release of firefox today, see: - https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available + New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu15 + Architecture: amd64 + BuildID: 20191205220404 + CurrentDesktop: ubuntu:GNOME + DefaultProfileExtensions: extensions.sqlite corrupt or missing + DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) + DefaultProfileLocales: extensions.sqlite corrupt or missing + DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 + DefaultProfileThemes: extensions.sqlite corrupt or missing + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-01-02 (4 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: firefox 71.0+build5-0ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 + Profiles: + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=71.0/20191205220404 (In use) + Tags: focal + Uname: Linux 5.4.0-9-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1858504 Title: Firefox 72 Released Status in firefox package in Ubuntu: New Bug description: New release of firefox today, see: https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BuildID: 20191205220404 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-02 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 71.0+build5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205220404 (In use) Tags: focal Uname: Linux 5.4.0-9-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:
[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer
ok actually i was able to fix it by using chrome remote desktop and manually killing the session from there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1848942 Title: Freeze on opening font viewer Status in gnome-font-viewer package in Ubuntu: Expired Bug description: When I open gnome-font-viewer, after few seconds interface freezes and I only can move my cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:02:24 2019 InstallationDate: Installed on 2019-10-20 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer
I'm currently having the same issue. Has anyone been able to fix this without rebooting? like maybe a keyboard shortcut to open some kind of full screen terminal thing and run a command to fix it or something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1848942 Title: Freeze on opening font viewer Status in gnome-font-viewer package in Ubuntu: Expired Bug description: When I open gnome-font-viewer, after few seconds interface freezes and I only can move my cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:02:24 2019 InstallationDate: Installed on 2019-10-20 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858500] [NEW] Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10
Public bug reported: 19.04 has got a higher version chromium-browser now than the transitional deb package that install the snap version, so the 19.04 version will be kept when someone upgrades since 19.04 got a higher version, and then no further updates. apt show chromium-browser -a Package: chromium-browser Version: 79.0.3945.79-0ubuntu0.19.04.3 Status: install ok installed Priority: optional Section: web Maintainer: Ubuntu Developers Installed-Size: 225 MB Provides: chromium-browser-inspector, www-browser Pre-Depends: dpkg (>= 1.15.6) Depends: libasound2 (>= 1.0.16), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 (>= 2.2.0), libatspi2.0-0 (>= 2.9.90), libc6 (>= 2.29), libcairo2 (>= 1.6.0), libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14), libexpat1 (>= 2.0.1), libgcc1 (>= 1:4.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 (>= 3.9.10), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.22), libpango-1.0-0 (>= 1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 7), libx11-6 (>= 2:1.4.99.1), libx11-xcb1, libxcb1 (>= 1.6), libxcomposite1 (>= 1:0.3-1), libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, libxss1, libxtst6, bash (>= 4), xdg-utils, chromium-codecs-ffmpeg-extra (= 79.0.3945.79-0ubuntu0.19.04.3) | chromium-codecs-ffmpeg (= 79.0.3945.79-0ubuntu0.19.04.3) Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, adobe-flashplugin Conflicts: chromium-browser-inspector Replaces: chromium-browser-inspector Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: unknown APT-Manual-Installed: yes APT-Sources: /var/lib/dpkg/status Description: Chromium web browser, open-source version of Chrome An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. Package: chromium-browser Version: 77.0.3865.120-0ubuntu1.19.10.1 Priority: optional Section: universe/web Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 163 kB Provides: www-browser Pre-Depends: debconf, snapd Depends: debconf (>= 0.5) | debconf-2.0 Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: 48.7 kB APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 Packages Description: Transitional package - chromium-browser -> chromium snap This is a transitional dummy package. It can safely be removed. . chromium-browser is now replaced by the chromium snap. Package: chromium-browser Version: 77.0.3865.120-0ubuntu1~snap1 Priority: optional Section: universe/web Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 163 kB Provides: www-browser Pre-Depends: debconf, snapd Depends: debconf (>= 0.5) | debconf-2.0 Homepage: https://chromium.googlesource.com/chromium/src/ Download-Size: 48.8 kB APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages Description: Transitional package - chromium-browser -> chromium snap This is a transitional dummy package. It can safely be removed. . chromium-browser is now replaced by the chromium snap. snap list Name Version Rev Tracking Publisher Notes core 16-2.42.5 8268 stablecanonical✓ core core18201912121288 stablecanonical✓ base gnome-3-28-1804 3.28.0-16-g27c9498.27c9498 110 stable/… canonical✓ - gnome-calculator 3.34.1+git1.d34dc842544 stable/… canonical✓ - gnome-characters v3.32.1+git3.b9120df375 stable/… canonical✓ - gnome-logs3.34.0 81stable/… canonical✓ - gnome-system-monitor 3.32.1-3-g0ea89b4922123 stable/… canonical✓ - gtk-common-themes 0.1-25-gcc83164 1353 stable/… canonical✓ - lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 79.0.3945.79-0ubuntu0.19.04.3 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 21:49:51 2020 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop' Env: 'None' 'None' InstallationDate: Installed on 2019-12-23 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: Load-Avg-1min: 0.58 Load-Processes-Running-Percent: 0.2% Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Desktop-packages] [Bug 1849135] Re: Clicking Activities in the corner doesn't work
This bug was fixed in the package mutter - 3.34.3-1ubuntu1 --- mutter (3.34.3-1ubuntu1) focal; urgency=medium * Merge with debian. Remaining changes: + debian/control: - Update VCS flags to point to launchpad + debian/gbp.conf: update branch to point to ubuntu/master + debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: - X11: Add support for fractional scaling using Randr mutter (3.34.3-1) unstable; urgency=medium * New upstream release + Fix window recording on HiDPI + Fix top-left pixel being insensitive to clicks (LP: #1849135) -- Iain Lane Mon, 06 Jan 2020 17:56:09 + ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released -- 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/1849135 Title: Clicking Activities in the corner doesn't work Status in GNOME Shell: New Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
Also I think at the same time Alt + F4 stops closing apps but instead switches to another console. -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858200] Re: pulseaudio produces garbage on HDMI after 19.10
I was looking at the wrong beast. Upgrading kernel solved the problem. -- 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/1858200 Title: pulseaudio produces garbage on HDMI after 19.10 Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 158483] Re: evince mishandles duplex printing of multiple copies of PDFs with an odd number of pages.
I would like to point that this issue has not been solved as of 2020 (Version 3.30). Thanks for reading! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/158483 Title: evince mishandles duplex printing of multiple copies of PDFs with an odd number of pages. Status in Evince: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: Binary package hint: evince First of all thank you for developing a fairly nice and intuitive document viewer, and if this bug report is best submitted to some subsystem project which specificly handles printing, well I'm sorry and hope that someone can move it to the right place for me. :) Okay so say you have an HP laserjet 4300 DN which is a duplex laser printer. Say you have the proper PPD file for it. Say you have a 3 (or any odd number) of pages in a PDF document Say you want 2 copies of said document. So you select print, and select 2 copies, and also confirm that "Page Setup->Two-sided" is already set to "Flip on Long Edge". What you end up with is 3 pieces of paper. Each printed on both sides. The main problems are that the 2nd piece of paper contains page 3 on one side, and page 1 on the other. And the general side-y-ness is thrown off by 1 for the entire 2nd copy of the document. I strongly think it should make the 2nd side of the 2nd piece of paper blank and start anew for the 2nd document. and I think most people would agree. :) Also if you attempt to collate in the above situation things get even more silly. You end up with 3 pieces of paper. The first with page 1 printed on both sides and the 2nd paper with page2 on both sides, and so on. BTW, I also tried this on a Xerox Phaser 8550 with its own PPD and experienced the same results. Thank you, Zachariah Johnson To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/158483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856707] Re: apport-collect crashes when collecting firefox information
This crash is in the source package hook for firefox, so I'm reassigning the bug to that package. ** Package changed: apport (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1856707 Title: apport-collect crashes when collecting firefox information Status in firefox package in Ubuntu: New Bug description: Whenever I attempt to run "apport-collect -p firefox" and then put in a bug report ID, the apport collection runs, but then crashes with the following: ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_firefox.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_firefox.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.7/re.py", line 192, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object As a result, apport is unable to collect certain kinds of information. This can be reproduced by simply running apport-collect for firefox (the ubuntu default version) Description: Ubuntu 19.10 Release: 19.10 apport: Installed: 2.20.11-0ubuntu8.2 Candidate: 2.20.11-0ubuntu8.2 Version table: *** 2.20.11-0ubuntu8.2 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages firefox: Installed: 71.0+build5-0ubuntu0.19.10.1 Candidate: 71.0+build5-0ubuntu0.19.10.1 Version table: *** 71.0+build5-0ubuntu0.19.10.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashReports: 600:118:124:37:2019-12-15 15:50:26.592426486 -0500:2019-12-15 15:39:57.663061956 -0500:/var/crash/_usr_bin_gnome-font-viewer.1000.uploaded 644:0:124:0:2019-12-15 15:50:24.620455221 -0500:2019-12-15 15:50:24.620455221 -0500:/var/crash/_usr_bin_gnome-font-viewer.1000.upload CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 08:25:29 2019 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 71.0+build5-0ubuntu0.19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) Tags: eoan Uname: Linux 5.3.0-24-generic x86_64
[Desktop-packages] [Bug 1856707] [NEW] apport-collect crashes when collecting firefox information
You have been subscribed to a public bug: Whenever I attempt to run "apport-collect -p firefox" and then put in a bug report ID, the apport collection runs, but then crashes with the following: ERROR: hook /usr/share/apport/package-hooks/source_firefox.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/source_firefox.py", line 1386, in add_info if (profile.current or profile.default) and profile.addon_compat_check_disabled: File "/usr/share/apport/package-hooks/source_firefox.py", line 1227, in addon_compat_check_disabled is_nightly = re.sub(r'^[^\.]+\.[0-9]+([a-z0-9]*).*', r'\1', self.last_version) == 'a1' File "/usr/lib/python3.7/re.py", line 192, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object As a result, apport is unable to collect certain kinds of information. This can be reproduced by simply running apport-collect for firefox (the ubuntu default version) Description:Ubuntu 19.10 Release:19.10 apport: Installed: 2.20.11-0ubuntu8.2 Candidate: 2.20.11-0ubuntu8.2 Version table: *** 2.20.11-0ubuntu8.2 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.11-0ubuntu8 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages firefox: Installed: 71.0+build5-0ubuntu0.19.10.1 Candidate: 71.0+build5-0ubuntu0.19.10.1 Version table: *** 71.0+build5-0ubuntu0.19.10.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status 69.0.3+build1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CrashReports: 600:118:124:37:2019-12-15 15:50:26.592426486 -0500:2019-12-15 15:39:57.663061956 -0500:/var/crash/_usr_bin_gnome-font-viewer.1000.uploaded 644:0:124:0:2019-12-15 15:50:24.620455221 -0500:2019-12-15 15:50:24.620455221 -0500:/var/crash/_usr_bin_gnome-font-viewer.1000.upload CurrentDesktop: ubuntu:GNOME Date: Tue Dec 17 08:25:29 2019 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20191205203726 CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:722 DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-20 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: firefox 71.0+build5-0ubuntu0.19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=71.0/20191205203726 (In use) Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected eoan -- apport-collect crashes when collecting firefox information https://bugs.launchpad.net/bugs/1856707 You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. -- Mailing list:
[Desktop-packages] [Bug 1854363] Re: [upstream] Typo in thunderbird code prevents central configuration
Any ETA for this? We use this to configure thunderbird for more than 100 users… -- 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/1854363 Title: [upstream] Typo in thunderbird code prevents central configuration Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Confirmed Bug description: The latest thunderbird (1:68.2.1+build1-0ubuntu0.18.04.1) introduces a typo that destroys our autoconfiguration. Error messages: Netscape.cfg/AutoConfig failed. Please contact your system administrator. Error: getLDAPAttibutes failed: ReferenceError: processLDAPValues is not defined Netscape.cfg/AutoConfig failed. Please contact your system administrator. Error: authconfig.js failed failed: TypeError: userInfo.mail is undefined Ref: https://bugzilla.mozilla.org/show_bug.cgi?id=1592922 I have downgraded thunderbird and confirmed that this happen when upgrading to 1:68.2.1+build1 My system: Description:Ubuntu 18.04.3 LTS Release:18.04 apt policy thunderbird thunderbird: Installed: 1:52.7.0+build1-0ubuntu1 Candidate: 1:68.2.1+build1-0ubuntu0.18.04.1 Version table: 1:68.2.1+build1-0ubuntu0.18.04.1 500 500 http://ubuntu.uib.no/archive bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 1:52.7.0+build1-0ubuntu1 500 500 http://ubuntu.uib.no/archive bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1854363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858442] [NEW] print screen button not registering in firefox
Public bug reported: Open Firefox. Add a breakpoint to a JavaScript code that listens to keydown or keyup and log the results. Press the Scroll Button and you can see a log Press the Pause button and you can see a log Press the Prnt or PrtSc or Print Screen Button and you can see a white flash but no log result in the console. The same happens in Chrome and Chromium Works great on Ubuntu 16. I didn't know what package to set this bug to so I had the onscreen keyboard package. This reproduces on a physical keyboard as well as the on screen keyboard. Please help with solving this problem. If the answer involves changing the print screen button shortcut option to another key or do nothing, then this is not an option. This should work out of the box. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: onboard 1.4.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 16:58:09 2020 ExecutablePath: /usr/bin/onboard InstallationDate: Installed on 2020-01-06 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterpreterPath: /usr/bin/python3.6 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: onboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1858442 Title: print screen button not registering in firefox Status in onboard package in Ubuntu: New Bug description: Open Firefox. Add a breakpoint to a JavaScript code that listens to keydown or keyup and log the results. Press the Scroll Button and you can see a log Press the Pause button and you can see a log Press the Prnt or PrtSc or Print Screen Button and you can see a white flash but no log result in the console. The same happens in Chrome and Chromium Works great on Ubuntu 16. I didn't know what package to set this bug to so I had the onscreen keyboard package. This reproduces on a physical keyboard as well as the on screen keyboard. Please help with solving this problem. If the answer involves changing the print screen button shortcut option to another key or do nothing, then this is not an option. This should work out of the box. Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: onboard 1.4.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 16:58:09 2020 ExecutablePath: /usr/bin/onboard InstallationDate: Installed on 2020-01-06 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterpreterPath: /usr/bin/python3.6 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 SourcePackage: onboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1858442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
Also FWIW it also happens with amdgpu so I think it's probably mutter and not nvidia -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827428] Re: Mouse cursor left frozen copy of itself
Been experiencing this on multiple distributions but haven't been able to find an upstream bug report -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858440] Re: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()
*** This bug is a duplicate of bug 1300619 *** https://bugs.launchpad.net/bugs/1300619 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1300619, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1858440/+attachment/5317898/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317900/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317904/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317905/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317906/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317907/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1858440/+attachment/5317908/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1300619 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1858440 Title: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock() Status in transmission package in Ubuntu: New Bug description: I don't know how it happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: transmission-gtk 2.94-2ubuntu2 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 10:29:42 2020 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: transmission-gtk magnet:?xt=urn:btih:7DF0545726FE40536AB273E1D46409A021A6A798=The.Silence.of.the.Lambs.1991.lati.mp4=udp%3a%2f%2ftracker.leechers-paradise.org%3a6969%2fannounce=udp%3a%2f%2ftracker.coppersurfer.tk%3a6969%2fannounce=http%3a%2f%2fshare.camoe.cn%3a8080%2fannounce=udp%3a%2f%2ftracker.pirateparty.gr%3a6969 SegvAnalysis: Segfault happened at: 0x7f4a922e4084 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%eax PC (0x7f4a922e4084) ok source "0x10(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: transmission StacktraceTop: __GI___pthread_mutex_lock (mutex=0x8) at ../nptl/pthread_mutex_lock.c:67 tr_lockLock () tr_torrentRecheckCompleteness () () () Title: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1858440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858439] [NEW] When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232]
Public bug reported: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while UpgradeStatus: Upgraded to eoan on 2019-10-31 (66 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232, Black Headphone Out, Right] fails after a while + When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] -- 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/1858439 Title: When docked, laptop switches to HDMI/Display port, instead of headphones. Headset microphone not available. [20BXCTO1WW, Realtek ALC3232] Status in alsa-driver package in Ubuntu: New Bug description: When my laptop is docked, I used to use a headset plugged into the dock for meetings. Both microphone and audio out were connected to my headset. Since the last update, my sound does not work like it used it, and I cannot make it work like I want. In particular, whenever I dock: - the output device changes to "HDMI/DisplayPort 2 - Built-in Audio". I do not know what that is (nothing is connected to HDMI), but it results in strange audio behaviour in which I can hear something through headphones but it's faint and does not respond to volume control. - audio input switches to internal microphone. Worse, there is no longer the choice to use the headset microphone, which is mandatory for those in my meeting not to hear my keyboard taps. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cpbl 3431 F pulseaudio /dev/snd/pcmC2D0c: cpbl 3431 F...m pulseaudio /dev/snd/controlC1: cpbl 3431 F pulseaudio /dev/snd/controlC0: cpbl 3431 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 06:36:12 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-24 (346 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: alsa-driver
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Description changed: - This happened after entering the user's password. It did not boot after - GDM gnome-shell. + This happened after selecting and entering the password of the GDM user. + + GDM gives the pass to gnome-shell, and it does not part. I reboot the + notebook, and it successfully enters gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: This happened after selecting and entering the password of the GDM user. - GDM gives the pass to gnome-shell, and it does not part. I reboot the - notebook, and it successfully enters gnome-shell. + GDM gives the pass to gnome-shell, and it does not start. I reboot the + notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Description changed: - I don't know what happened. + This happened after entering the user's password. It did not boot after + GDM gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: This happened after entering the user's password. It did not boot after GDM gnome-shell. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1857383/+attachment/5317890/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] Re: Fractional scaling does not work anymore
apport information ** Tags added: apport-collected ** Description changed: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. - The monitor on which i want to scale is 4k and is connecting through - DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using - Dell Dock WD19 but same issue). + The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu15 + Architecture: amd64 + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" + InstallationDate: Installed on 2019-12-18 (18 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) + Package: gnome-shell 3.34.1+git20191024-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 + Tags: focal + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1857383/+attachment/5317887/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1857383/+attachment/5317889/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857383] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1857383/+attachment/5317888/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857383 Title: Fractional scaling does not work anymore Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have installed Ubuntu 20.04 about 2-3 weeks ago (for the single motive that has fractional scalling) and when activating fractional scalling worked fine, in the meantime i reinstalled again Ubuntu 20.04 (laptop warranty issue) on same hardware but using the latest Ubuntu 20.04 version and now when i activate fractional scalling it does not work anymore. The issue is that it basically zooms both the displays, i can explain best by attaching the printscreens and a picture with my phone on the same thing.You will see in the photo taken with the phone how it actually scales now and how the screenshots are taken... Let me know what logs/commands etc is needed to pinpoint this which i think is a regression. The monitor on which i want to scale is 4k and is connecting through DELL DA300 adapter through USB-C/Thunderbolt ( i have also tried using Dell Dock WD19 but same issue). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: b'org.gnome.mutter' b'experimental-features' b"['scale-monitor-framebuffer']" InstallationDate: Installed on 2019-12-18 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191127) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed
This bug was fixed in the package linux - 5.3.0-26.28 --- linux (5.3.0-26.28) eoan; urgency=medium * eoan/linux: 5.3.0-26.28 -proposed tracker (LP: #1856807) * nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed modules (LP: #1856407) - Add nvidia-435 dkms build linux (5.3.0-25.27) eoan; urgency=medium * eoan/linux: 5.3.0-25.27 -proposed tracker (LP: #1854762) * CVE-2019-14901 - SAUCE: mwifiex: Fix heap overflow in mmwifiex_process_tdls_action_frame() * CVE-2019-14896 // CVE-2019-14897 - SAUCE: libertas: Fix two buffer overflows at parsing bss descriptor * CVE-2019-14895 - SAUCE: mwifiex: fix possible heap overflow in mwifiex_process_country_ie() * [CML] New device id's for CMP-H (LP: #1846335) - mmc: sdhci-pci: Add another Id for Intel CML - i2c: i801: Add support for Intel Comet Lake PCH-H - mtd: spi-nor: intel-spi: Add support for Intel Comet Lake-H SPI serial flash - mfd: intel-lpss: Add Intel Comet Lake PCH-H PCI IDs * i915: Display flickers (monitor loses signal briefly) during "flickerfree" boot, while showing the BIOS logo on a black background (LP: #1836858) - [Config] FRAMEBUFFER_CONSOLE_DEFERRED_TAKEOVER=y * Please add patch fixing RK818 ID detection (LP: #1853192) - SAUCE: mfd: rk808: Fix RK818 ID template * Kernel build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" (LP: #1853843) - [Debian] Fix warnings when checking for modules signatures * Lenovo dock MAC Address pass through doesn't work in Ubuntu (LP: #1827961) - r8152: Add macpassthru support for ThinkPad Thunderbolt 3 Dock Gen 2 * Dell XPS 13 9350/9360 headphone audio hiss (LP: #1654448) // [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor (LP: #1845810) - ALSA: hda/realtek: Reduce the Headphone static noise on XPS 9350/9360 * no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026 (LP: #1852386) - drm/i915: Add new CNL PCH ID seen on a CML platform - SAUCE: drm/i915: Fix detection for a CMP-V PCH * [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (LP: #1846539) - [Config] Drop snd-sof-intel-bdw build - SAUCE: ASoC: SOF: Intel: Broadwell: clarify mutual exclusion with legacy driver * [CML-S62] Need enable turbostat patch support for Comet lake- S 6+2 (LP: #1847451) - SAUCE: tools/power turbostat: Add Cometlake support * External microphone can't work on some dell machines with the codec alc256 or alc236 (LP: #1853791) - SAUCE: ALSA: hda/realtek - Move some alc256 pintbls to fallback table - SAUCE: ALSA: hda/realtek - Move some alc236 pintbls to fallback table * Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection (LP: #1853197) - xfrm: Fix memleak on xfrm state destroy * CVE-2019-18660: patches for Ubuntu (LP: #1853142) // CVE-2019-18660 - powerpc/64s: support nospectre_v2 cmdline option - powerpc/book3s64: Fix link stack flush on context switch - KVM: PPC: Book3S HV: Flush link stack on guest exit to host kernel * Raydium Touchscreen on ThinkPad L390 does not work (LP: #1849721) - HID: i2c-hid: fix no irq after reset on raydium 3118 * Make Goodix I2C touchpads work (LP: #1853842) - HID: i2c-hid: Remove runtime power management - HID: i2c-hid: Send power-on command after reset * Touchpad doesn't work on Dell Inspiron 7000 2-in-1 (LP: #1851901) - Revert "UBUNTU: SAUCE: mfd: intel-lpss: add quirk for Dell XPS 13 7390 2-in-1" - lib: devres: add a helper function for ioremap_uc - mfd: intel-lpss: Use devm_ioremap_uc for MMIO * CVE-2019-19055 - nl80211: fix memory leak in nl80211_get_ftm_responder_stats * CML: perf enabling for core (LP: #1848978) - perf/x86/intel: Add Comet Lake CPU support - perf/x86/msr: Add Comet Lake CPU support - perf/x86/cstate: Add Comet Lake CPU support - perf/x86/msr: Add new CPU model numbers for Ice Lake - perf/x86/cstate: Update C-state counters for Ice Lake * Boot hangs after "Loading initial ramdisk ..." (LP: #1852586) - SAUCE: Revert "tpm_tis_core: Set TPM_CHIP_FLAG_IRQ before probing for interrupts" - SAUCE: Revert "tpm_tis_core: Turn on the TPM before probing IRQ's" * [CML-S62] Need enable intel_rapl patch support for Comet lake- S 6+2 (LP: #1847454) - powercap/intel_rapl: add support for CometLake Mobile - powercap/intel_rapl: add support for Cometlake desktop * [CML-S62] Need enable intel_pmc_core driver patch for Comet lake- S 6+2 (LP: #1847450) - SAUCE: platform/x86: intel_pmc_core: Add Comet Lake (CML) platform support to intel_pmc_core driver * update ENA driver for DIMLIB dynamic interrupt
[Desktop-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed
This bug was fixed in the package linux-restricted-modules - 5.3.0-26.28
---
linux-restricted-modules (5.3.0-26.28) eoan; urgency=medium
* Master version: 5.3.0-26.28
* nvidia-435 is in eoan, linux-restricted-modules only builds against 430,
ubiquity gives me the self-signed modules experience instead of using the
Canonical-signed modules (LP: #1856407)
- [Packaging] Add support for nvidia-435 dkms builds
linux-restricted-modules (5.3.0-25.27) eoan; urgency=medium
* Master version: 5.3.0-25.27
* Miscellaneous Ubuntu changes
- debian/dkms-versions -- update from master
-- Khalid Elmously Wed, 18 Dec 2019
00:27:52 -0500
** Changed in: linux-restricted-modules (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14895
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14896
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14897
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14901
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-18660
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19055
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19072
--
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/1856407
Title:
nvidia-435 is in eoan, linux-restricted-modules only builds against
430, ubiquity gives me the self-signed modules experience instead of
using the Canonical-signed modules
Status in linux package in Ubuntu:
Invalid
Status in linux-restricted-modules package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Fix Released
Status in linux-restricted-modules source package in Eoan:
Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
Confirmed
Status in ubuntu-drivers-common source package in Eoan:
Confirmed
Bug description:
SRU Justification
Impact: The nvidia-435 drivers are missing from linux-restricted-
modules in eoan. On install ubuntu-drivers picks 435 as the newest
version, and users must use self-signed dkms drivers and enroll a MOK.
Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
Test Case: A test build is available in ppa:sforshee/test-builds.
Verify that signed drivers for nvidia-435 can be installed for eoan
via the linux-modules-nvidia-435-{generic,lowlatency} packages.
Regression Potential: The nvidia-435 l-r-m drivers are new packages
built from the same source as the nvidia-435 dkms driver, so
regressions are unlikely.
---
The linux-restricted-modules package exists so that users who install
the nvidia drivers can get known-good, signed modules instead of
having to locally self-sign and enroll a signing key through MOK. But
lrm in eoan is only building driver packages for nvidia 390 and 430,
and nvidia 435 is present in eoan.
So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
newest driver instead of using the signed 430 driver.
We should never allow the archive to get into this situation. We
should be enforcing that any version of the nvidia driver that we
expect ubuntu-drivers to install by default on any hardware is
integrated into linux-restricted-modules, and we should ensure that
ubuntu-drivers always prefers the signed drivers over other options.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856407/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858072] Re: Webdav is not python3 compatible
The current Ubuntu version now is 0.8.08 which includes the fix
mentioned, closing. The issue still exist in 19.10 and could be a
candidate for a stable update in which case the specific serie can be
targetted but it's rather low importance at the moment so not very
likely to see an update on a non LTS serie
** Changed in: duplicity (Ubuntu)
Importance: Undecided => Low
** Changed in: duplicity (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1858072
Title:
Webdav is not python3 compatible
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
Fix Released
Bug description:
The webdav backend calls base64.encodestring, which
(counterintuitively) expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
--exclude='**' \
'.' \
"$target_url"
Using archive dir:
/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
Using backup name: 74043f3f63750b8654c846cb69e2833f
GPG binary is gpg, version (2, 2, 12)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host REDACTED port None
Using WebDAV directory /webdav/backup/
Main action: inc
Acquiring lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
duplicity $version ($reldate)
Args: /usr/bin/duplicity incremental --asynchronous-upload
--full-if-older-than 1M -v 9 --exclude=./Documents/google_drive/**
--include=./src/** --exclude=** . webdavs://RED:ACT@ED/webdav/backup
Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019
x86_64 x86_64
/usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008]
Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
Registering (mkstemp) temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
Temp has 50636972032 available, backup will use approx 482344960.
WebDAV create connection on 'REDACTED'
WebDAV PROPFIND /remote.php/webdav/backup/ request with headers:
{'Connection': 'keep-alive', 'Depth': '1'}
WebDAV data length: 95
WebDAV response status 401 with reason 'Unauthorized'.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371, in
inner_retry
return fn(self, *args)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580, in
list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 343, in _list
raise e
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 317, in _list
response = self.request(u"PROPFIND", self.directory, self.listbody)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 240, in request
self.headers[u'Authorization'] = self.get_authorization(response,
quoted_path)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 271, in
[Desktop-packages] [Bug 1858355] Re: /usr/lib/gnome-settings-daemon/gsd-print-notifications:free(): invalid pointer
*** This bug is a duplicate of bug 1826159 *** https://bugs.launchpad.net/bugs/1826159 ** This bug has been marked a duplicate of bug 1826159 gsd-print-notifications assert failure: free(): invalid pointer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1858355 Title: /usr/lib/gnome-settings-daemon/gsd-print-notifications:free(): invalid pointer Status in gnome-settings-daemon package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-settings-daemon. This problem was most recently seen with package version 3.34.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3d7933d46e17d4d2ab4cdba47c09ba3f0cb34cf5 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/gnome-settings-daemon/+bug/1858355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1826159
Title:
gsd-print-notifications assert failure: free(): invalid pointer
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
This problem occurs since upgrade to disco dingo. Have not seen this
in earlier releases. It seems to be related to printers in the gnome
settings.
janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installerad: 3.32.0-1ubuntu1
Kandidat:3.32.0-1ubuntu1
Versionstabell:
*** 3.32.0-1ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AssertionMessage: free(): invalid pointer
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 22:16:13 2019
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2018-02-20 (427 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=sv_SE.UTF-8
SHELL=/bin/tcsh
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at
malloc.c:5352
_int_free (av=, p=, have_lock=)
at malloc.c:4181
()
g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-print-notifications assert failure: free(): invalid pointer
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858209] Re: Software has problem with .DEB package
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1858209 Title: Software has problem with .DEB package Status in gnome-software package in Ubuntu: Incomplete Bug description: Hello In Ubuntu 20.04 is a problem in Software! This not install my new Hibiscus .DEB Package I can not test this. control the systemstart time! control the cyberjack driver in recources "SP13" the old "SP09" is broken! Best Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1858209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858368] Re: single-day events on 1st of month show on all days of preceding month
Thank you for your bug report, the issue has already been reported upstream as well https://gitlab.gnome.org/GNOME/gnome-calendar/issues/458 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-calendar/issues #458 https://gitlab.gnome.org/GNOME/gnome-calendar/issues/458 ** Changed in: gnome-calendar (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-calendar (Ubuntu) Status: New => Triaged ** Also affects: gnome-calendar via https://gitlab.gnome.org/GNOME/gnome-calendar/issues/458 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1858368 Title: single-day events on 1st of month show on all days of preceding month Status in GNOME Calendar: Unknown Status in gnome-calendar package in Ubuntu: Triaged Bug description: Single-day events on 1st of month show on all days of preceding month. For example, someone's birthday on April 1 will show up (in the month view) as being a month-long event during all of March. I am using a NextCloud calendar. The events look OK on the NextCloud web-based calendar, on my iphone, and on Mac's Calendar.app. Those same events appear fine in the week view... they are not stretched into the previous month. Alan Porter ubuntu-launch...@kr4jb.net ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-calendar 3.34.2-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 17:24:56 2020 InstallationDate: Installed on 2019-12-30 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1858368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
See LP: #1858414 -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2084 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 Importance: Unknown Status: Unknown ** Description changed: I don't know what happened. + + --- + + https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=es_CL.UTF-8 - LANGUAGE=es_CL:es - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=es_CL.UTF-8 + LANGUAGE=es_CL:es + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: - ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 - ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 - ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 - () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 - () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 + ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 + ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 + ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 + () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 + () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: I don't know what happened. --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858414] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
** Information type changed from Private to Public -- 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/1858414 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in gnome-shell package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856317] Re: [SRU] 3.34.2
I've verified this in line with the bug description (exercise the desktop, check Nautilus thumbnailer, check Settings background panel). All good. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1856317 Title: [SRU] 3.34.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Eoan: Fix Committed Bug description: [ Description ] Update to 3.34.2, which is going to be required by gnome-shell. == Version 3.34.2 == - Add helper to create transient systemd scopes - Translation updates [ QA ] This is uploaded under the GNOME MRE: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This is solely to add new API. Test that the desktop continues to work. Maybe try the thumbnailer in Nautilus, and the background panel in Settings. [ Regression potential ] Not as a result of this SRU itself, *but* when gnome-shell / gnome- settings-daemon are uploaded then *they* could regress if this update is buggy. They should probably be released all together. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1856317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826648] Re: cupds crashes with core dump
I have the same problems as described in this bug. Every time I print something cupsd crashes with core dump and cups-browsed also crashes. My printer is a Samsung CLX 6260 Series. I can successfully print one job, then get the crash, then have to wait some minutes before the services are up again, and so on. I found out that if I stop the cups-browsed service the problem goes away. This is fine for me as I've already added my printer manually and I don't need to automatically find new printers. For some odd reason, another copy of my printer is added even though the service was disabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: Expired Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856846] Re: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work)
I executed "ubuntu-bug /var/crash/crashfile.crash" but can't see a bug ID. On my whoopsie page, no new entry is created. How do I find out which bug ID was assigned to my ubuntu-bug call? -- 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/1856846 Title: Gnome Xorg sessions fail to start with LDAP users (but Wayland or local users work) Status in xorg-server package in Ubuntu: Incomplete Bug description: When trying to login to Gnome with an remote user from an LDAP (LDAP is available and connectable when in GDM) using X11, GDM loops around three to five times before actually granting access to the desktop. This does not happen when a) Wayland is used instead of X11 or, b) the LDAP server is not reachable during login, using X11, or c) a local user is logged in instead, using X11 The LDAP connection is established using the Univention Domain Join Client: https://launchpad.net/~univention- dev/+archive/ubuntu/ppa?field.series_filter=bionic Do you require additional information? Release: Description: Ubuntu 18.04.3 LTS Release: 18.04 GDM3: gdm3: Installed: 3.28.3-0ubuntu18.04.4 Candidate: 3.28.3-0ubuntu18.04.4 Version table: *** 3.28.3-0ubuntu18.04.4 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1856846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Very similar issue to the other reports. I see this every few days when I login. Typically I go to Nautilus, mount an encrypted FUSE drive, open Chrome, then randomly the session just dies. Interesting, my dual monitors are reversed so the order of them is wrong (left is on the right, and vice versa). Restarting seems fine. OS: Ubuntu 18.04.03 Kernel: Linux 4.4.0-148-generic x86_64 Ubuntu Processor: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8 Graphics: GeForce GTX 1060 6GB/PCIe/SSE2 GNOME: 3.28.2 I also have the Chrome Remote Desktop installed. I'll try removing it. Relevant syslog attached for reference. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5317862/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
** Changed in: bluez (Ubuntu Bionic) Milestone: None => ubuntu-18.04.4 -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857340] Re: Setting "IPv6 Method" to "Disable" does not disable IPv6
Thank you for your bug report, indeed that's a known upstream issue see details on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/593 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #593 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/593 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/593 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857340 Title: Setting "IPv6 Method" to "Disable" does not disable IPv6 Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: Setting "IPv6 Method" to "Disable" does not disable IPv6 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 06:50:59 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-11-21 (31 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1857340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858364] Re: /usr/bin/nautilus-desktop:ERROR:../src/nautilus-file.c:729:nautilus_file_get_internal: assertion failed: (location != NULL)
The error reports stop after 3.26, assuming it's fixed in the current versions ** Changed in: nautilus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1858364 Title: /usr/bin/nautilus-desktop:ERROR:../src/nautilus- file.c:729:nautilus_file_get_internal: assertion failed: (location != NULL) Status in nautilus package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu9, the problem page at https://errors.ubuntu.com/problem/8625807832947f023e918eb923eaac89cd468993 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/nautilus/+bug/1858364/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793222] Re: Mousepad doesn't take input after canceled save dialog
After Ubuntu 19.10 I couldn't reproduce on any system. I set the report to "invalid". ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1793222 Title: Mousepad doesn't take input after canceled save dialog Status in ibus package in Ubuntu: Invalid Bug description: 1 Open Mousepad 2 Write something 3 Ctrl+S for save -> dialog opens 4 Exit dialog with ESC -> Mousepad will not take any keyboard input anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mousepad 0.4.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 19 07:17:27 2018 InstallationDate: Installed on 2018-02-12 (218 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: mousepad UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1793222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858362] Re: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source
The issue could be due to bug #1848202 , would be useful to see if there are reports still with glib 2.26.2 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1858362 Title: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_malloc:g_source_set_callback:g_task_attach_source Status in nautilus package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/d27a750c5eaf7972c99c001fbb86cb2e6500594f 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/nautilus/+bug/1858362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857869] Re: Red fill the search stop icon
Thank you for your bug report, that looks like an upstream design decision ** Changed in: nautilus (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857869 Title: Red fill the search stop icon Status in nautilus package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) It might be better if the search stop icon was red filled. Similar to a stop sign. 4) The search stop icon is white filled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1858095] Re: 'Automatic Date and Time' automatically disabled when trying to enable
Thank you for your bug report. Do you have ntpd installed? If so then it's probably the same issue than bug #1848309 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1858095 Title: 'Automatic Date and Time' automatically disabled when trying to enable Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When enabling the "Automatic DateTime" in the gnome control center, it instantly turns off. The following is reported in syslog: Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: Starting resolvconf-pull-resolved.service... Jan 2 12:10:58 ubuntu systemd[1]: resolvconf-pull-resolved.service: Succeeded. Jan 2 12:10:58 ubuntu systemd[1]: Started resolvconf-pull-resolved.service. Jan 2 12:10:58 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Jan 2 12:10:58 ubuntu systemd-timedated[10725]: Set NTP to enabled Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: Starting resolvconf-pull-resolved.service... Jan 2 12:10:59 ubuntu systemd[1]: resolvconf-pull-resolved.service: Succeeded. Jan 2 12:10:59 ubuntu systemd[1]: Started resolvconf-pull-resolved.service. Jan 2 12:10:59 ubuntu systemd-timedated[10725]: Set NTP to disabled Jan 2 12:11:03 ubuntu xdg-desktop-por[3204]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1858095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857655 Title: gdkselection-wayland.c:275: error reading selection buffer Status in nautilus package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No error. 4) Error in Logs app. 6:41:01 PM nautilus: ../../../../../gdk/wayland/gdkselection- wayland.c:275: error reading selection buffer: Operation was cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: nautilus (Ubuntu) Importance: Medium => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer
is the issue specific to wayland sessions? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857655 Title: gdkselection-wayland.c:275: error reading selection buffer Status in nautilus package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) No error. 4) Error in Logs app. 6:41:01 PM nautilus: ../../../../../gdk/wayland/gdkselection- wayland.c:275: error reading selection buffer: Operation was cancelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857736] Re: nautilus crashed with SIGABRT
The issue looks similar to bug #1702082 ** Changed in: nautilus (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857736 Title: nautilus crashed with SIGABRT Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: I do not know, what happened. --- https://gitlab.gnome.org/GNOME/nautilus/issues/1324 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 Uname: Linux 5.4.6-050406-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Dec 27 21:22:37 2019 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2018-12-02 (390 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: nautilus StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () () () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGABRT UpgradeStatus: Upgraded to focal on 2018-12-02 (390 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
Patch for Ubuntu 18.04. ** Changed in: bluez (Ubuntu Bionic) Status: Triaged => In Progress ** Patch added: "bluez_5.48-0ubuntu3.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+attachment/5317855/+files/bluez_5.48-0ubuntu3.3.debdiff ** Changed in: bluez (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766230] Re: Strange window matching behaviour between Slack and Chrome
I can confirm this happens in ubuntu 18.04.3 between Chrome and Slack. Workaround in #3 doesn't work for me, as WM_CLASS is already correctly set, i.e.: * slack: `WM_CLASS(STRING) = "slack", "Slack"` * chrome: `WM_CLASS(STRING) = "google-chrome", "Google-chrome"` However, killing both applications and relaunching seems to correct the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766230 Title: Strange window matching behaviour between Slack and Chrome Status in gnome-shell package in Ubuntu: Confirmed Bug description: There seems to be a window matching bug between the Slack snap and Chrome. If you open a URL from within Slack without Chrome open, then the launcher shows the extra pip next to Slack and doesn't add a Chrome icon to the launcher. If you open Chrome first, then things work as expected. Steps to reproduce 1. Install Slack snap and Chrome deb. 2. Join a Slack channel and open a hyperlink. Notice the extra pip next to Slack in the launcher. 3. Close Chrome and reopen it. 4. Open a URL from Slack again and notice the Chrome icon get added to the launcher. I'm not sure if this is an Ubuntu Dock or GNOME Shell issue. EDIT: Spoke to didrocks, he says that matching is done by Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
