[Desktop-packages] [Bug 1785060] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1785060/+attachment/5413762/+files/ProcEnviron.txt -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1785060/+attachment/5413761/+files/ProcCpuinfoMinimal.txt -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1785060/+attachment/5413759/+files/Dependencies.txt -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-23 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: evince 3.36.7-0ubuntu1 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6e215a61-0873-41a1-a75f-cbaf75c331a6 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected focal -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] KernLog.txt
apport information ** Attachment added: "KernLog.txt" https://bugs.launchpad.net/bugs/1785060/+attachment/5413760/+files/KernLog.txt -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] RelatedPackageVersions.txt
apport information ** Attachment added: "RelatedPackageVersions.txt" https://bugs.launchpad.net/bugs/1785060/+attachment/5413763/+files/RelatedPackageVersions.txt -- 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/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I have the same MSFT0001:00 04F3:3186 touchpad, however, the touchpad will show as Elantech Touch Pad under windows and it is listed under the firmware section: Elantech Touch Pad Firmware 1.0.0.2 Device type:Firmware Manufacturer: Elantech Ltd. Locatioon: on Microsft UEFI-Compliant System https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=88c5455c-404a-4e6b-b2a0-382ff0017406 And I found it's driver on windows is actually raw data called "SA469D-22HM_Fv0x02.bin". I tried to disassembly it but the output doesn't make much sense. I think to try to understand why do this type of touchpads work on windows may help understanding why do them do not work on most Linux distributions. There are also some docs about Precision Touchpad on MS' site: https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchpad-windows-precision-touchpad-collection https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/windows-precision-touchpad-required-hid-top-level-collections -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVer
[Desktop-packages] [Bug 1896878] [NEW] Doesn't compile for groovy
Public bug reported: dkms.conf can be changed to just use PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch" with patches from archlinux: https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx and https://gitlab.manjaro.org/packages/extra/linux57-extramodules/nvidia-340xx/-/raw/master/kernel-5.7.patch?inline=false Except that the kernel-5.7 patch needs to be modified to remove the dkms.conf section therein, and the kernel/ paths for files needs to be removed. A fixed kernel-5.7.patch file is attached. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel-5.7.patch" https://bugs.launchpad.net/bugs/1896878/+attachment/5413753/+files/kernel-5.7.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: dkms.conf can be changed to just use PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch" with patches from archlinux: https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx and https://gitlab.manjaro.org/packages/extra/linux57-extramodules/nvidia-340xx/-/raw/master/kernel-5.7.patch?inline=false Except that the kernel-5.7 patch needs to be modified to remove the dkms.conf section therein, and the kernel/ paths for files needs to be removed. A fixed kernel-5.7.patch file is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896861] Re: Update to 1.90.3
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu1 --- libfprint (1:1.90.3+tod1-0ubuntu1) groovy; urgency=medium * New upstream release (LP: #1896861): - New goodixmoc driver supporting Goodix USB devices: 27C6:5840, 27C6:6496, 27C6:60A2 - Newly added support for Synaptics device: 06CB:00E9 06CB:00DF (LP: #1893719) - Fixed an issue with Synaptics devices sometimes not working at boot (LP: #1893719) - Fix issue with aes3k driver * debian/libfprint-2-tod1.symbols: Added new GType symbols -- Marco Trevisan (Treviño) Thu, 24 Sep 2020 06:14:30 +0200 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1896861 Title: Update to 1.90.3 Status in libfprint package in Ubuntu: Fix Released Bug description: Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1896861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893719] Re: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu1 --- libfprint (1:1.90.3+tod1-0ubuntu1) groovy; urgency=medium * New upstream release (LP: #1896861): - New goodixmoc driver supporting Goodix USB devices: 27C6:5840, 27C6:6496, 27C6:60A2 - Newly added support for Synaptics device: 06CB:00E9 06CB:00DF (LP: #1893719) - Fixed an issue with Synaptics devices sometimes not working at boot (LP: #1893719) - Fix issue with aes3k driver * debian/libfprint-2-tod1.symbols: Added new GType symbols -- Marco Trevisan (Treviño) Thu, 24 Sep 2020 06:14:30 +0200 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1893719 Title: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: In Progress Bug description: [Impact] * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Tested again from focal-proposed (mutter 3.36.6-1ubuntu0.20.04.2). Can confirm it still fixes the problem! (Intel HD Graphics). -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893719] Re: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF
** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1893719 Title: Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF Status in OEM Priority Project: New Status in libfprint package in Ubuntu: In Progress Status in libfprint source package in Focal: In Progress Bug description: [Impact] * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a [Test Case] * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes. [Regression Potential] * Regression potential for an updated libfprint with these new PIDs is low [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896861] [NEW] Update to 1.90.3
Public bug reported: Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader support ** Affects: libfprint (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1896861 Title: Update to 1.90.3 Status in libfprint package in Ubuntu: In Progress Bug description: Fixes various bugs in AuthenTec chip, synapitcs and add goodix reader support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1896861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s
As per comment https://bugs.launchpad.net/mutter/+bug/1857947/comments/11 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes [ Test case ] Four-finger gesture seems to trigger it, in any case it can be monitored via - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). 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/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 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/mutter/+bug/1857947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
As per comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870867/comments/27 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
As per comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/comments/13 We can mark this as verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: Copy/paste still sometimes fails in LibreOffice and Wine apps
I forgot to mention this i changelogs, so this will be closed once bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332 will be ** Changed in: mutter (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1879968 Title: Copy/paste still sometimes fails in LibreOffice and Wine apps Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896416] Re: screen locking no longer works
yep, there we go, works fine now. I wonder what component malfunctioned when setting that, could have been wine or vlc or any number of things that prevent sleep while playing media, I suppose. It's too bad that there's no indicator or overrider to let a user know what's going on in this scenario. -- 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/1896416 Title: screen locking no longer works Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: in the last week, the gnome screen locking functionality stopped working. I'm under the impression this is handled by gdm3, but if not, please point me at the correct package. in any case, now there's no lock icon in the power menu in the top right, win-L does nothing, and trying to invoke manually with the gnome-screensaver package times out after about a minute with the following error: $ gnome-screensaver-command -l ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to send message: Timeout was reached ** Message: 18:46:25.014: Did not receive a reply from the screensaver. as well, if I suspend the system, on resume it dumps right back to the desktop without a prompt to re-authenticate, so this is a security issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 18:47:40 2020 InstallationDate: Installed on 2020-07-15 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6
No issues here either on AMD and Intel. Thankfully this also finally fixes https://bugs.launchpad.net/bugs/1879968 -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ).
** Summary changed: - Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. + Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs ). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Hi, Brian and Marco, I've tested the mutter 3.36.6-1ubuntu0.20.04.2 (from "focal-proposed" repository). Now, all works fine! Without problems. Thanks for your attention and work! :) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750146]
Dear sender! Thank you for your message! Unfortunately, I am out of office until 27.9.2020 and hence will not be able to reply immediately. Your email will not be forwarded, but I will answer your email as soon as possible on my return. In very urgent cases, however, please contact our service center via email mailto:serv...@escrypt.com>> or phone +49 234 43870-200. Yours sincerely, Matthias Pritschet Sehr geehrte Damen und Herren, Vielen Dank für Ihre E-Mail! Ich bin leider bis zum 27.9.2020 nicht erreichbar und kann daher nicht unmittelbar antworten. Ihre Nachricht wird nicht weitergeleitet. In dringenden Fällen können Sie sich jedoch gern an unser Service-Center (mailto:serv...@escrypt.com>> oder +49 234 43870-200) wenden. Mit freundlichen Grüßen Matthias Pritschet -- 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/1750146 Title: Xbox (One) Wireless Controller won't connect Status in gnome-control-center: Confirmed Status in Linux: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1750146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750146]
Yeah, it seems to get worse with every 5.4 LTS update. Worked almost flawless about some months ago (despite taking something from 30-60s to successfully connect). But I don't see a correlation to any commits. But now, it's almost impossible to connect successfully, it usually disconnects after a 1-2 minutes (coincidentally just when entering a game). I usually also see messages like this: During use of the controller (probably around disconnect time): [ 5304.480502] Bluetooth: Unexpected continuation frame (len 52) When plugging the BT dongle: [ 5241.926752] Bluetooth: hci0: unexpected event for opcode 0x While it's in a loop of constantly connecting and disconnecting: [ 1120.736530] Bluetooth: hci0: hardware error 0x58 [ 1120.923550] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 1120.923555] debugfs: File 'le_max_key_size' in directory 'hci0' already present! [ 1120.923557] debugfs: File 'force_bredr_smp' in directory 'hci0' already present! Other BT devices seem to just work fine tho I don't use a lot of them and only occasionally. It seems that the Xbox One S firmware does something strange in the BT protocol. It also needs either ERTM disabled to connect. Alternatively, one can apply this patch to be able to use ERTM: https://github.com/kakra/linux/commit/c8b24d83f227a7fecfa9420d6756074e8f9b542c I'm also feeling there's some internal state getting messed up within the controller on each BT pairing: Results are not really reproducible. I managed to get it to work flawlessly one time (stable connection despite 20-30s connect handshake time), then purged my Bluetooth config from /var/lib, re-paired the controller and now it's a mess - still with the same kernel version. -- 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/1750146 Title: Xbox (One) Wireless Controller won't connect Status in gnome-control-center: Confirmed Status in Linux: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth with Ubuntu 17.10 in the gnome-control-center. Placing the controller into pairing mode makes it visible on the Bluetooth Devices list and the device pairs, but does not make the full connection needed to pull the controller out of pairing mode. This renders my controller unusable with my Ubuntu PC unless I want to resort to using the wire (microUSB). Please fix. See the attached system information below. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13 Uname: Linux 4.13.0-32-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 09:26:14 2018 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1750146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896847] [NEW] Most executables crash when running in GUI but not in terminal
Public bug reported: Most of the executable ELF files in /usr/bin/ will not run from any GUI interface and most do not show up anywhere including in the files list. When I try to execute one from GUI I get the popup box that I have attached to this report. However, when I run the same file from a terminal it will open and run as it should. It would seem the error is either in the GUI or every single ELF file is missing a : in the uri. Many of those are supposed to run in the background. They don't. I will be very happy to see this fixed and everything running as it is supposed to run. Just in case my attachment has something wrong with it too, I will type out what is in the popup box: Invalid url:'/usr/bin/gnome-system-monitor' given, exiting No ':' in the uri ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 17:33:43 2020 InstallationDate: Installed on 2020-09-08 (15 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Popup error code" https://bugs.launchpad.net/bugs/1896847/+attachment/5413649/+files/system-monitor-terminal.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1896847 Title: Most executables crash when running in GUI but not in terminal Status in gnome-system-monitor package in Ubuntu: New Bug description: Most of the executable ELF files in /usr/bin/ will not run from any GUI interface and most do not show up anywhere including in the files list. When I try to execute one from GUI I get the popup box that I have attached to this report. However, when I run the same file from a terminal it will open and run as it should. It would seem the error is either in the GUI or every single ELF file is missing a : in the uri. Many of those are supposed to run in the background. They don't. I will be very happy to see this fixed and everything running as it is supposed to run. Just in case my attachment has something wrong with it too, I will type out what is in the popup box: Invalid url:'/usr/bin/gnome-system-monitor' given, exiting No ':' in the uri ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 17:33:43 2020 InstallationDate: Installed on 2020-09-08 (15 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1896847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1896416] Re: screen locking no longer works
On Wed, Sep 23, 2020 at 10:14:57PM -, Tessa wrote: > Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down, > not locking > > so it appears as if it thinks the screen is already locked, even though > I'm interacting with my session. and the dbus call doesn't have any way This message indicates that the screen lock has been disabled: https://sources.debian.org/src/gnome- shell/3.36.6-1/js/ui/screenShield.js/?hl=595#L595 I'm guessing that the setting may be named 'disable-lock-screen' in the 'org.gnome.desktop.lockdown' schema: https://sources.debian.org/src/gnome- shell/3.36.6-1/js/ui/screenShield.js/?hl=24#L24 try this to see the current value of the setting: gsettings get org.gnome.desktop.lockdown disable-lock-screen try this to change it: gsettings set org.gnome.desktop.lockdown disable-lock-screen false # or true, as needed I hope this helps. Thanks -- 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/1896416 Title: screen locking no longer works Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: in the last week, the gnome screen locking functionality stopped working. I'm under the impression this is handled by gdm3, but if not, please point me at the correct package. in any case, now there's no lock icon in the power menu in the top right, win-L does nothing, and trying to invoke manually with the gnome-screensaver package times out after about a minute with the following error: $ gnome-screensaver-command -l ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to send message: Timeout was reached ** Message: 18:46:25.014: Did not receive a reply from the screensaver. as well, if I suspend the system, on resume it dumps right back to the desktop without a prompt to re-authenticate, so this is a security issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 18:47:40 2020 InstallationDate: Installed on 2020-07-15 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hello, facing the same issue (obviously). I appear to have the MSFT0001:00 04F3:3186, ordered in France, so this model does not seems to be limited to china (R7000 variant). Blacklisting done nothing. I have seen the chinese blog but I'm a little lost with this, is it supposed to work with my model ? I'm available if anyone need something to try or any info regarding this model. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:
[Desktop-packages] [Bug 1558886] Please test proposed package
Hello Anthony, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1558886 Title: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell and using Chrome web browser when computer became unresponsive to any commands or mouse clicks. About 3-4 minutes later a crash report popped up on my screen. I clicked report and now I am reporting this as a new bug as I have never had this happen before on previous versions of Ubuntu. I was attempting to copy and save an image from Google Chrome when this happened. Similar crash still happening, as per https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa [ Test case ] Run xinput and figure device IDs for your mouse. Run this evil script with 9 changed (be sure to change both) to your id: for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo Enabled; done While the script runs, open some context menu in some program. It may require a few clicks due to evil script enabling/disabling mouse. This will sometimes crash GTK programs due to a mirror bug in GTK. GNOME Shell should not crash [ Regression potential ] Devices might be not be properly recognized when plugged and unplugged Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable google-chrome-stable: Installed: 49.0.2623.75-1 Candidate: 49.0.2623.75-1 Version table: *** 49.0.2623.75-1 100 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 16.04 Package: gnome-shell 3.18.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 17 22:20:56 2016 DisplayManager: lightdm ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-02-24 (22 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax PC (0x7f634ba78320) ok source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0 ?? () from /usr/lib/libmutter.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event() UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1558886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896416] Re: screen locking no longer works
why am I not surprised that sending a cryptic dbus command is the "correct" way to lock the screen from the cli these days. in any case, I can run that command as often as you like, and it always returns success to the shell, but it never locks the screen: tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 tessa@boxxy:~/Downloads$ dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock tessa@boxxy:~/Downloads$ echo $? 0 looking at the journalctl output right after running, I see the following, which is clearly incorrect: Sep 23 15:07:58 boxxy gnome-shell[209336]: Screen lock is locked down, not locking so it appears as if it thinks the screen is already locked, even though I'm interacting with my session. and the dbus call doesn't have any way of returning an error state to the cli if the operation fails, which is honestly such a bad design, as it leaves things that rely on it silently failing all over the interface but claiming they're working correctly. -- 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/1896416 Title: screen locking no longer works Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: New Bug description: in the last week, the gnome screen locking functionality stopped working. I'm under the impression this is handled by gdm3, but if not, please point me at the correct package. in any case, now there's no lock icon in the power menu in the top right, win-L does nothing, and trying to invoke manually with the gnome-screensaver package times out after about a minute with the following error: $ gnome-screensaver-command -l ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to send message: Timeout was reached ** Message: 18:46:25.014: Did not receive a reply from the screensaver. as well, if I suspend the system, on resume it dumps right back to the desktop without a prompt to re-authenticate, so this is a security issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55 Uname: Linux 5.4.0-47-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Sep 20 18:47:40 2020 InstallationDate: Installed on 2020-07-15 (67 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1896416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s
Hello errors.ubuntu.com, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1857947 Title: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_stack_later() from call_later_func() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes [ Test case ] Four-finger gesture seems to trigger it, in any case it can be monitored via - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). 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/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 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/mutter/+bug/1857947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hello Cristiano, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))
Hello Ivan, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1870867 Title: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl)) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] GNOME Shell crashes in meta_x11_get_stage_window. [ Test case ] Perform touch events via touchpad or touchscreen, eventually the shell will crash. Errors can be monitored at: https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2 [ Regression potential ] Windows might not be closed correctly when requested via delete-events (clicking on clientside decoration close button). --- ProblemType: CrashDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 22:08:06 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-needed verification-needed-focal -- 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/1887998 Title: Update to 3.36.4 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 screencasting and touch-interaction, so ensure there are no problems with those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896332] Please test proposed package
Hello Marco, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Hello Cristiano, or anyone else affected, Accepted mutter into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895486] Re: [media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll Lock" keyboards
For ABNT2 keyboards, I've removed the "Scroll Lock" key, see:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/merge_requests/112
It is not the right solution (I even regretted it), but it works...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1895486
Title:
[media-keys] Fn media keys with lag slow/delay on Gnome with "Scroll
Lock" keyboards
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
I use Ubuntu 20.04.1.
After some use, I noticed a delay when using keyboard media controls
(for example: increase volume audio).
The first time I push these key Gnome hangs for a short time before
display the action on the screen.
(This problem is still happening in Ubuntu 18.04 too. Even worse some
times, the system crashes when using media keys.)
For some reason, my Gnome freezes when using Fn keys, or when I try to
use two keyboards. A friend of mine pointed to me that it occurs when
switching to a keyboard layout that has Scroll Lock enabled, so I
disabled it in the X11 keyboard layout file for my language, and it
solved the problem.
A workaround to solve the problem is:
1) Opened the keyboard layout file for my language, in my case:
sudo nano /usr/share/X11/xkb/symbols/br
2) Commented the line:
modifier_map Mod3 { Scroll_Lock };
3) Logged out and logged in again or run command setxkbmap.
These steps are specific for the Brazilian Portuguese ABNT2 Layout and
may not work for other layouts, but it can help you find a similar
solution.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: x11-xkb-utils 7.7+5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51
UTC 2020
GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 13 21:52:03 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
Subsystem: Dell UHD Graphics 630 (Desktop) [1028:0859]
NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if
00 [VGA controller])
Subsystem: Dell GP107 [GeForce GTX 1050 Ti] [1028:3512]
InstallationDate: Installed on 2020-08-15 (29 days ago)
InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa"
(20200815)
MachineType: Dell Inc. XPS 8930
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic
root=UUID=706721d5-f527-41fe-98ca-96706a36bb42 ro quiet splash
SourcePackage: x11-xkb-utils
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.15
dmi.board.name: 0T88YD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.15:bd07/01/2020:svnDellInc.:pnXPS8930:pvr1.1.15:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: XPS
dmi.product.name: XPS 8930
dmi.product.sku: 0859
dmi.product.version: 1.1.15
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2020-08-15T17:44:36
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1895486/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested the mutter 3.36.6-1ubuntu0.20.04.2~wip1 (in the PPA). Now, all works fine! Thanks for your attention and work. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896842] [NEW] simple-scan cannot scan a page using EPSON V39 scanner
Public bug reported:
ishabalov@black:~$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.09s] DEBUG: app-window.vala:1906: Loading state from
/home/ishabalov/.cache/simple-scan/state
[+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
[+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.17s] DEBUG: scanner.vala:828: Processing request
[+0.56s] DEBUG: app-window.vala:1981: Saving state to
/home/ishabalov/.cache/simple-scan/state
[+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+8.42s] DEBUG: scanner.vala:353: Device:
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
vendor="EPSON" model="Epson_Perfection_V39" type=""
[+8.72s] DEBUG: app-window.vala:1981: Saving state to
/home/ishabalov/.cache/simple-scan/state
[+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
[+9.90s] DEBUG: scanner.vala:1674: Scanner.scan
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
paper_height=0, brightness=26, contrast=46, delay=3000ms)
[+9.90s] DEBUG: scanner.vala:828: Processing request
[+10.17s] DEBUG: scanner.vala:889: sane_open
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
-> SANE_STATUS_GOOD
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
[+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4
cap=soft-detect,advanced
[+10.17s] DEBUG: scanner.vala:763: Description:
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
[+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general'
title='General' type=group size=0 cap=inactive
[+10.17s] DEBUG: scanner.vala:763: Description: Basic options.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
[+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document
Source' type=string size=15 values=["Document Table"] cap=soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Document Source
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
[+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling'
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
[+10.17s] DEBUG: scanner.vala:763: Description: This option provides the user
with a wider range of supported resolutions. Resolutions not supported by the
hardware will be achieved through image processing methods.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
[+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution'
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Resolution
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
[+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan Area'
type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait",
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape",
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait",
"Manual", "Maximum"] cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Scan Area
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
[+10.17s] DEBUG: scanner.vala:760: Option 6: name='mode' title='Image Type'
type=string size=11 values=["Monochrome", "Grayscale", "Color"]
cap=soft-select,soft-detect,emulated
[+10.17s] DEBUG: scanner.vala:763: Description: Image Type
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (7)
[+10.17s] DEBUG: scanner.vala:760: Option 7: name='device-03-geometry'
title='Geometry' type=group size=0 cap=inactive
[+10.17s] DEBUG: scanner.vala:763: Description: Scan area and image size
related options.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (8)
[+10.17s] DEBUG: scanner.vala:760: Option 8: name='br-x' title='Bottom Right X'
type=fixed size=4 unit=mm min=2.539993, max=218.439987, quant=0
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Bottom Right X
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (9)
[+10.17s] DEBUG: scanner.vala:760: Option 9: name='br-y' title='Bottom Right Y'
type=fixed size=4 unit=mm min=2.539993, max=299.719986, quant=0
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Bottom Right Y
[Desktop-packages] [Bug 1888575] Please test proposed package
Hello Andreas, or anyone else affected, Accepted livecd-rootfs into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.408.60 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in base-files source package in Xenial: Fix Released Status in livecd-rootfs source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: Fix Committed Status in base-files source package in Bionic: Fix Released Status in livecd-rootfs source package in Bionic: Invalid Status in ubuntu-meta source package in Bionic: Fix Released Status in base-files source package in Focal: Fix Released Status in livecd-rootfs source package in Focal: Invalid Status in ubuntu-meta source package in Focal: Fix Released Status in base-files source package in Groovy: Fix Released Status in livecd-rootfs source package in Groovy: Invalid Status in ubuntu-meta source package in Groovy: Fix Released Bug description: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config- news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd-news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is i
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
I have amended test case k) to stipulate that we ensure the base ubuntu- cpc image continues to have grub-legacy-ec2 installed. The intended outcome of this change is that all images that currently have grub- legacy-ec2 installed have it, all images that do not have grub-legacy- ec2 installed continue not to have it, and ubuntu-server is present on all images. ** Description changed: [Impact] The motd-news script is largely useless for desktop users, as they rarely login via a text console. It makes more sense for server users. We can use package dependencies to have the motd-news script enabled on servers, but disabled on desktops, and still handle upgrades. This is the plan: - move /etc/default/motd-news from base-files into a new binary package (motd-news-config, produced by src:base-files) - have ubuntu-server depend on motd-news-config - have base-files break current ubuntu-server, so that if base-files if upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to the new version which has the depends on motd-news-config Care must be taken to preserve a changed /etc/default/motd-news when the upgrade installs the new motd-news-config package. For example, on a server that has set ENABLED=0 in /etc/default/motd-news and upgrades to the new base-files and ubuntu-server, and gets the new motd-config-news package, ENABLED=0 must remain set. [Test Case] a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains, motd-news remains enabled b) base-files installed, ubuntu-server installed, modified /e/d/motd-news apt install base-files - upgrades ubuntu-server - installs motd-news-config - /e/d/motd-news remains with the original modification c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news apt install base-files - upgrades base-files - removes /e/d/motd-news - motd-news is disabled d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news apt install base-files - upgrades base-files - /e/d/motd-news gets renamed to backup - motd-news is disabled e) removing motd-news-config will also remove ubuntu-server (since it's a depends, and not a recommends) f) upgrading just ubuntu-server should pull motd-news-config in, and force-upgrade base-files g) Removing motd-news-server leaves /e/d/motd-news around; purging motd- news-server removes the /e/d/motd-news config file h) base-files installed, ubuntu-server installed, removed /e/d/motd-news - apt install base-files - upgrades base-files, upgrades ubuntu-server, installs motd-news-config - /e/d/motd-news is installed with ENABLED=0 i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news - apt install base-files - base-files is upgraded - no /e/d/motd-news is installed, motd-news remains disabled j) Perform a release upgrade from the previous ubuntu release to the one being tested while having ubuntu-server NOT installed (or use a desktop install). At the end, motd-news should be disabled. Verify with: $ sudo /etc/update-motd.d/50-motd-news --force $ (no output) k) Test that supporting changes for xenial are in place: - i) verify grub-legacy-ec2 is not in the xenial server seed - ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package - iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server + i) verify grub-legacy-ec2 is not in the xenial server seed + ii) verify that the rootfs manifest built from the ubuntu-cpc project contains the ubuntu-server package + iii) verify that images built from the ubuntu-cpc project which purge grub-legacy-ec2 have retained ubuntu-server + iv) verify that the base ubuntu-cpc image continues to have grub-legacy-ec2 installed. [Regression Potential] This update is about config file ownership transfer: /e/d/motd-news belonged to base-files, now it belongs to motd-news-config. We tried to handle two important cases here: a) /e/d/motd-news config was changed while it belonged to base-files. For example, an user could have set ENABLED=0. We need to transfer that change to the motd-news-config package when it is installed, otherwise this SRU would jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's configure case. b) /e/d/motd-news config file was *removed* while it belonged to base-files. In such a case, a normal upgrade of the package (base-files in this example) would not reinstate the file. Much less this upgrade here, which has an explicit rm_conffile maintscript-helper for it. But the motd-news-config package that could be installed in the transaction would place the default config file back, and the de
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Thanks, Trevinho! ;) -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Thanks for making the bug SRU compliant, I've uploaded a new version. In the mean time you can probably test it using the ppa at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4267 ** Description changed: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. + This very fix was already handled as part of bug #1889090 and we had no regression report,. + + However, one possible is that the screen size is not set properly for + the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) - InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) - SourcePackage: mutter + InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => High ** Changed in: mutter (Ubuntu Focal) Status: New => In Progress ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: In Progress Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This very fix was already handled as part of bug #1889090 and we had no regression report,. However, one possible is that the screen size is not set properly for the session, or that panning is enabled. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815)SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1896815] Re: Xorg freeze? Old Arabic Fonts are not working
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896815 Title: Xorg freeze? Old Arabic Fonts are not working Status in xorg package in Ubuntu: New Bug description: Hello, Old Arabic Fonts (not MS fonts) were running on MS Word. they can not working on ubuntu. they listed in LO Writer , but they are not running in all kubuntu 20.10 applications. I used fc-cache for install them. but they are not configured for running. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.452 CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 18:31:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200922) MachineType: MSI MS-7850 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ar_EG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896815/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896815] [NEW] Xorg freeze? Old Arabic Fonts are not working
You have been subscribed to a public bug: Hello, Old Arabic Fonts (not MS fonts) were running on MS Word. they can not working on ubuntu. they listed in LO Writer , but they are not running in all kubuntu 20.10 applications. I used fc-cache for install them. but they are not configured for running. Thank You ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CasperVersion: 1.452 CompositorRunning: None CurrentDesktop: KDE CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Wed Sep 23 18:31:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] LiveMediaBuild: Kubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200922) MachineType: MSI MS-7850 ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ar_EG.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze groovy has-workaround kubuntu single-occurrence ubuntu -- Xorg freeze? Old Arabic Fonts are not working https://bugs.launchpad.net/bugs/1896815 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I mean, this looks like bug #1889090 is back.. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
Oh, crazy... This was supposed to be fixed already, looks like something broke when adapting the patch?! -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lsusb-v.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413598/+files/lsusb-v.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
See also: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 ** Description changed: + In Ubuntu 20.04.1 (focal): + [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: - # set this to 0 to disable apport, or to 1 to enable it - # you can temporarily override this with - # sudo service apport start force_start=1 - enabled=0 + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413597/+files/syslog -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413599/+files/version.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
In my syslog: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Description changed: In Ubuntu 20.04.1 (focal): [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Description changed: - In Ubuntu 20.04.1 (focal): + In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Summary changed: - Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) + Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) ** Description changed: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] - This bug was introduced by Marco Trevisan (Treviño) in the LP #1892440. + This bug was introduced by Marco Trevisan (Treviño) in the LP 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia:
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413602/+files/dmesg.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413601/+files/lspci-vnvn.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
And a new upload now in the queue: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/11 -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [Impact] What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. [Test Case] Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Then install gnome-shell from bionic-proposed, reboot, and find that an added input source now is effective instantly without any of the mentioned workarounds. [Regression Potential] Minimal. The fix consists of a simple upstream commit which has been in use as from GNOME 3.32. [Other info] Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA)
I've tested in a fresh install also. -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896825] [NEW] Mutter 3.28 doesn't compile with mesa 20
Public bug reported: [ Impact ] Mesa 20 update broke mutter builds, as visible in https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1 [ Test case ] Mutter should build cleanly in a bionic chroot [ Regression potential ] Wayland components aren't included in the final mutter build ** Affects: mutter (Ubuntu) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: mutter (Ubuntu Bionic) Importance: High Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Importance: Undecided => High ** Changed in: mutter (Ubuntu Bionic) Status: New => In Progress ** Changed in: mutter (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Status: In Progress => 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/1896825 Title: Mutter 3.28 doesn't compile with mesa 20 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Bug description: [ Impact ] Mesa 20 update broke mutter builds, as visible in https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1 [ Test case ] Mutter should build cleanly in a bionic chroot [ Regression potential ] Wayland components aren't included in the final mutter build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] Re: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+attachment/5413600/+files/uname-a.log -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (NVIDIA) Status in mutter package in Ubuntu: New Bug description: In Ubuntu 20.04.1 [focal-proposed]: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced by Marco Trevisan (Treviño) in the bug 1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6
There is a problem: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1896332 Title: SRU 3.36.6 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in X11 device management, desktop background image handling, screen-casting and night-switch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I've fill another bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892747] Re: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut
Daniel, I'm not sure if this bug is related but, the system also hangs for a few seconds whenever the Wi-Fi gets disconnected. -- 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/1892747 Title: [Dell Vostro 3446] Ubuntu hangs while changing display brightness from keyboard shortcut Status in gnome-shell package in Ubuntu: New Bug description: Whenever I change my display's brightness using keyboard shortcuts (For me F11 & F12), Ubuntu hangs a little, the brightness is changed immediately, but everything (except the mouse) hangs while it is being changed and sometimes for quite some time after. There is no problem doing it through the system. Changing volume using keyboard shortcuts works perfectly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-22 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896818] [NEW] Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia)
Public bug reported: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1896818 Title: Gnome-shell crash after turn display off in mutter 3.36.6-ubuntu0.20.04.1 (mostly on Nvidia) Status in mutter package in Ubuntu: New Bug description: [ Impact ] GNOME Shell crash after updating mutter to version 3.36.6-ubuntu0.20.04.1. With the old version (3.36.4-0ubuntu0.20.04.1) and (3.36.4-0ubuntu0.20.04.2), all works fine. [ Test case ] Steps to reproduce the error: 1) Lock screen; 2) Turn off the display; 3) Turn on the display; And the Gnome Shell crash and show us a blank screen with the message: "Oh no! Something has gone wrong." [ Regression potential ] This bug was introduced in a fix by Marco Trevisan (Treviño) in the LP #1892440. [ Workaround ] Downgrade the libmutter package temporarily. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 23 15:57:17 2020 InstallationDate: Installed on 2020-08-15 (38 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896818/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896756] Re: tracker* startup is defined multiple times
** Package changed: systemd (Ubuntu) => tracker (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
Status in tracker package in Ubuntu:
New
Bug description:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/tracker*.service
Expected Behavior
===
Startup is only defined in one place.
Reason:
- Managing the software does not get confusing
lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Sep 23 20:39:33 2020
MachineType: FUJITSU FMVWB3U27
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows
2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896756/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896756] [NEW] tracker* startup is defined multiple times
You have been subscribed to a public bug:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/tracker*.service
Expected Behavior
===
Startup is only defined in one place.
Reason:
- Managing the software does not get confusing
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Sep 23 20:39:33 2020
MachineType: FUJITSU FMVWB3U27
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows
2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
** Affects: tracker (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
tracker* startup is defined multiple times
https://bugs.launchpad.net/bugs/1896756
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie)
I do not see any window flickering with QEMU hosting 20.10 guest. So specific to intel i915? Sorry - I cannot test radeon or 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) Status in mutter package in Ubuntu: Confirmed Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. Sometimes the flickering is black, sometimes the flickering makes the wallpaper visible, even when there is a window behind the window being resized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Sep 22 14:48:00 2020 InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) 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/1896654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse
Should note - testing mutter package 3.38.0-1ubuntu1 ** Summary changed: - Windows flicker when resizing with mouse + Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie ** Summary changed: - Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie + Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) Status in mutter package in Ubuntu: Confirmed Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. Sometimes the flickering is black, sometimes the flickering makes the wallpaper visible, even when there is a window behind the window being resized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Sep 22 14:48:00 2020 InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) 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/1896654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, After I power down my display and power up again (in the lock screen), the problem is: gnome-shell[3407]: mutter:ERROR:../src/backends/x11/meta-monitor- manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) gnome-shell[3407]: Bail out! mutter:ERROR:../src/backends/x11/meta- monitor-manager- xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+attachment/5413576/+files/syslog -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) Status in mutter package in Ubuntu: Confirmed Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. Sometimes the flickering is black, sometimes the flickering makes the wallpaper visible, even when there is a window behind the window being resized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Sep 22 14:48:00 2020 InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) 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/1896654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse
Note - this affects GNOME-Shell on Xorg as well. Confirmed with intel i915 driver. GNOME-Shell on Wayland there are no window flicker So most probably a regression in mutter (since budgie and GNOME-Shell share the same window manager) in the X11 handling. -- 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/1896654 Title: Windows flicker when resizing with mouse (GNOME-Shell - Xorg & Budgie) Status in mutter package in Ubuntu: Confirmed Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. Sometimes the flickering is black, sometimes the flickering makes the wallpaper visible, even when there is a window behind the window being resized. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Tue Sep 22 14:48:00 2020 InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) 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/1896654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I also have Lenovo Legion 5 15ARH05H, 82B1000AUS and would like to help out with adding support for this device. Any advice on how to get started? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.p
[Desktop-packages] [Bug 1895144] Re: ubuntu-server CET gap analysis
** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1895144 Title: ubuntu-server CET gap analysis Status in golang-defaults package in Ubuntu: New Status in klibc package in Ubuntu: New Status in libunwind package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: New Bug description: * linux lacks CET, not upstream yet * snapd lacks CET, as golang has no support for CET yet * libunwind lacks CET, as no upstream support yet * klibc lacks CET, no upstream support yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-defaults/+bug/1895144/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896814] [NEW] package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-com
Public bug reported: Unable to change drivers ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 23 19:21:05 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lMXS82/4-nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896814 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Unable to change drivers ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 23 19:21:05 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lMXS82/4-nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896814] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896814 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Unable to change drivers ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 23 19:21:05 2020 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.108-0ubuntu2) ... dpkg: error processing archive /tmp/apt-dpkg-install-lMXS82/4-nvidia-340_340.108-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-450 450.66-0ubuntu0.20.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Re: gnome-shell freezes on notification arrival (fixed upstream)
I've prepared a new package with the whole set of fixes: https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text =gnome-shell -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Marco Trevisan, I'll do that. Anyway, thanks for the fix. ;) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896812] [NEW] Failed to start GNOME Shell on X11
Public bug reported: Ubuntu 20.04.1 Package mutter-3.36.6-1ubuntu0.20.04.1 Sep 23 12:30:03 razorback systemd[2389]: Starting GNOME Shell on X11... Sep 23 12:30:03 razorback gnome-shell[26684]: ** Sep 23 12:30:03 razorback gnome-shell[26684]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback gnome-shell[26684]: Bail out! mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Failed with result 'core-dump'. Sep 23 12:30:03 razorback systemd[2389]: Failed to start GNOME Shell on X11. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1896812 Title: Failed to start GNOME Shell on X11 Status in mutter package in Ubuntu: New Bug description: Ubuntu 20.04.1 Package mutter-3.36.6-1ubuntu0.20.04.1 Sep 23 12:30:03 razorback systemd[2389]: Starting GNOME Shell on X11... Sep 23 12:30:03 razorback gnome-shell[26684]: ** Sep 23 12:30:03 razorback gnome-shell[26684]: mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback gnome-shell[26684]: Bail out! mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size: assertion failed: (width > 0 && height > 0 && scale > 0) Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Main process exited, code=dumped, status=6/ABRT Sep 23 12:30:03 razorback systemd[2389]: gnome-shell-x11.service: Failed with result 'core-dump'. Sep 23 12:30:03 razorback systemd[2389]: Failed to start GNOME Shell on X11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@ Cristiano, please fill another bug for that :) -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
The bug is fixed when I updated mutter to 3.36.1-1ubuntu0.20.04.1. BUT After an "Automatic Screen Lock", the display turned off, the Gnome Shell crash and show us a blank screen with the message "Oh no! Something has gone wrong." This bug did not appears before the update. I have a NVIDIA card. I think that this problem occurs only with NVIDIA users. I have other PC (without a NVIDIA card) and the problem not occurs. -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892783] Re: [SRU] libreoffice 6.4.6 for focal
This bug was fixed in the package libreoffice - 1:6.4.6-0ubuntu0.20.04.1 --- libreoffice (1:6.4.6-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1892783) -- Heather Ellsworth Mon, 24 Aug 2020 16:58:01 -0600 ** Changed in: libreoffice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Released Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892783] Update Released
The verification of the Stable Release Update for libreoffice has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891338] Re: apparmor misconfigured for evince
This bug was fixed in the package apparmor - 3.0.0~beta1-0ubuntu6 --- apparmor (3.0.0~beta1-0ubuntu6) groovy; urgency=medium * Drop d/p/lp1824812.patch: this patch was only needed with 2.13 and not 3.0. With AppArmor 3, the patch ends up setting SFS_MOUNTPOINT to the wrong directory in is_container_with_internal_policy(), which causes policy to always fail to load in containers. Thanks to Christian Ehrhardt for the analysis. (LP: #1895967) apparmor (3.0.0~beta1-0ubuntu5) groovy; urgency=medium [ John Johansen ] * d/p/fix-parser-to-emit-proc-attr-access-for-all-situations.patch: fix-automatic-adding-of-rule-for-change-hat-iface.patch fixed the parser to emit rules needed for change_hat in the hat profiles but broke the rule being emitted for the parent profile, this fixes it for both so that it is emitted for any profile that is a hat or that contains a hat. * d/p/fix-change-profile-stack-abstraction.patch: fix the change_profile abstraction so that it allows access to the apparmor attribute paths under LSM stacking. apparmor (3.0.0~beta1-0ubuntu2) groovy; urgency=medium [ John Johansen ] * d/p/fix-automatic-adding-of-rule-for-change-hat-iface.patch: fix parser not adding a rule to profiles if they are a hat or contain hats granting write access to the kernel interfaces. apparmor (3.0.0~beta1-0ubuntu1) groovy; urgency=medium [ John Johansen ] * New upstream release (LP: #1895060, LP: #1887577, LP: #1880841) * Drop all patches backported from upstream: applied in 3.0 * d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch: provide example and base abi to pin pre 3.0 policy * d/p/ubuntu/enable-pinning-of-pre-AppArmor-3.x-poli.patch: enable pinning of pre AppArmor 3.x policy * drop d/p/debian/dont-include-site-local-with-dovecot.patch: no longer needed with upstream 'include if exists' [ Steve Beattie ] * d/p/parser-fix_cap_match.patch: fix cap match to work correctly, important now that groovy has a 5.8 kernel. * d/apparmor-profiles.install: + adjust for renamed postfix profiles + add usr.bin.dumpcap and usr.bin.mlmmj-receive to extra-profiles + remove usr.sbin.nmbd and usr.sbin.smbd from extra-profiles (already in apparmor-profiles) * d/apparmor.install: include abi/ directory and tunables/etc. * d/apparmor.manpages: add apparmor_xattrs.7 manpage * d/control: + apparmor-utils: no more shipped perl tools, drop perl dependency + apparmor-notify: aa-notify was converted to python3 from perl; adjust -notify dependencies to compensate * d/p/fix-tests-regression-apparmor-prologue-inc-settest.patch: fix sed expression in settest() [ Emilia Torino ] * Removing Ubuntu specific chromium-browser profile. This is safe to do since groovy's chromium-browser deb installs the snap. If apparmor3 is backported to 18.04 or earlier, the profile will need to be taken into consideration - d/profiles/chromium-browser: remove chromium-browser profile - d/apparmor-profiles.postinst: remove postinst script as it only contains chromium-browser related functionallity. - d/apparmor-profiles.postrm: remove postrm script as it only contains chromium-browser related functionallity. - d/apparmor-profiles.install: remove ubuntu-specific chromium-browser abstraction and profile - d/apparmor-profiles.lintian-overrides: remove chromium-browser profile lintian overrides - d/p/ubuntu/add-chromium-browser.patch: remove patch which added chrome-browser [ Alex Murray ] * d/p/policy-provide-example-and-base-abi-to-pin-pre-3.0-p.patch: refresh this patch with the official upstream version * d/p/ubuntu/enable-pinning-of-pre-AppArmor-3.x-poli.patch: refresh this patch to match the above * d/p/parser-add-abi-warning-flags.patch: enable parser warnings to be silenced or to be treated as errors [ Jamie Strandboge ] * d/p/adjust-for-ibus-1.5.22.patch: update ibus abstract path for ibus 1.5.22. This can be dropped with AppArmor 3.0 final. * d/p/parser-add-abi-warning-flags.patch: refresh to avoid lintian warnings * d/p/ubuntu/lp1891338.patch: adjust ubuntu-integration to use abstractions/exo-open (LP: #1891338) * d/p/ubuntu/lp1889699.patch: adjust to support brave in ubuntu abstractions. Patch thanks to François Marier (LP: #1889699) * d/p/ubuntu/lp1881357.patch: adjust for new ICEauthority path in /run (LP: #1881357) -- Jamie Strandboge Tue, 22 Sep 2020 15:10:33 + ** Changed in: apparmor (Ubuntu) Status: In Progress => Fix Released -- 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/1891338 Title: apparmor misconfigured for evince Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Triaged Bug description:
[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6
Ah about this: > If this isn't used for generating the final packages at all, why do you propose to make users download an update? Those files aren't included at all into the package, the README.sources there was included to explain why we have such files, even though they are not built. It's just inside an orig file for diff purposes, nothing more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1896334 Title: SRU 3.36.6 Status in gnome-shell package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Incomplete Status in yaru-theme source package in Focal: Incomplete Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1896334] Re: SRU 3.36.6
> I don't understand why yaru-theme needs to be updated, either. I see > that this has been done for yaru-theme once before, but I've found no > explanation as to why. I will make it clearer in the top post, but it should be quite easy to spot looking at the shell's (data subdir) and yaru diffs: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. ** Description changed: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. - The changes involving yaru here are ONLY gnome-shell upstream changes - applied to the Yaru sources, as per this we can consider them also part - of the GNOME release. + The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. + In fact: + - Ubuntu's GNOME shell uses a Yaru theme based on upstream + gnome-shell This theme basically takes the shell's data/ directory, + applies some diffs and generates a gresource file out of it, that it's + then loaded on startup (in place of the upstream one). + - GNOME Shell applied some fixes to the theme (se its data/ + directory diffs) + - In order to get those fixes in Ubuntu main session we have to sync + the upstream changes applied to such dir to yaru's src/gnome-shell + path + - You can easily compare the diffs applied there to match the ones + happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1896334 Title: SRU 3.36.6 Status in gnome-shell package in Ubuntu: In Progress Status in yaru-theme package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Incomplete Status in yaru-theme source package in Focal: Incomplete Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packag
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@ David I think pop-os disabled fractional scaling patch, so get in contact with them please: https://github.com/pop-os/mutter/commit/bc7c2658e4c873a28afeaf621fb24a1341c6d74c -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884850] Re: Xorg server uses unacceptably large amounts of memory (and keep growing)
** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1884850 Title: Xorg server uses unacceptably large amounts of memory (and keep growing) Status in libreoffice package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Description: Xorg server uses unacceptably large amounts of memory (and keep growing) Ever since I upgraded to Ubuntu 20.04 (with fresh install) on my laptop (Lenovo T450s, Intel Core i5-5200U, Intel HD5500 graphics), I have been troubled by the way Xorg process uses memory. Here is an example of memory usage of Xorg as a function of time. I rebooted the laptop on June 17: Xorg-usage-20200617a.txt:root1224 1.9 0.8 948408 98848 tty7 Rsl+ 10:38 0:05 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200617b.txt:root1224 2.2 0.8 978264 105180 tty7 Ssl+ 10:38 0:22 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200618a.txt:root1224 0.3 1.3 1143064 162584 tty7 Ssl+ Jun17 3:15 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200619a.txt:root1224 0.3 2.9 1432232 360700 tty7 Ssl+ Jun17 12:30 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200619b.txt:root1224 0.3 2.7 1313120 338656 tty7 Ssl+ Jun17 12:39 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Xorg-usage-20200623a.txt:root1224 0.3 6.0 1944364 738596 tty7 Ssl+ Jun17 31:55 \_ /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch The filename indicates the date the "ps fuxa" command was run. Contrast this against the memory usage of another Xorg process run for XPRA: Xorg-usage-20200617b.txt:wirawan 4452 2.4 2.0 1106920 244984 ? Ssl 10:46 0:12 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200618a.txt:wirawan 4452 0.2 2.0 1108572 246616 ? Ssl Jun17 2:25 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200619a.txt:wirawan 4452 0.2 2.0 1112460 249516 ? Ssl Jun17 8:34 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200619b.txt:wirawan 4452 0.2 2.0 1112964 250020 ? Ssl Jun17 8:40 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 Xorg-usage-20200623a.txt:wirawan 4452 0.1 2.0 1113092 250544 ? Ssl Jun17 11:22 \_ /usr/lib/xorg/Xorg-for-Xpra-:100 -noreset -novtswitch -nolisten tcp +extension GLX +extension RANDR +extension RENDER -auth /home/wirawan/.Xauthority -logfile /run/user/1000/xpra/Xorg.:100.log -configdir /run/user/1000/xpra/xorg.conf.d/4451 -config /etc/xpra/xorg.conf -depth 24 :100 My desktop usage pattern: * MATE desktop * 4-desktop setting (standard default MATE when shipped) * GNUCASH * about 3 windows of terminal (each about 5-10 tabs) * XPRA running Firefox web browser (to isolate web browser pixmap memory usage, if that was the culprit) * LibreOffice (several windows open at any time) * using "redshift" to change the desktop color to red at night I have never seen this before using Ubuntu 20.04 on this machine. Before, when I was running Debian 8, I could run this machine for months literally without Xorg memory bloating rapidly like this (but then I was using xfce instead of MATE). I viewed the output of xrestop, the pixmap memory usage is dominated by marco and wnck-applet: xrestop - Display: localhost Monitoring 36 clients. XErrors: 0
[Desktop-packages] [Bug 1896774] Re: Headphone output stopped working after perfoming dist-upgrade
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1896774 Title: Headphone output stopped working after perfoming dist-upgrade Status in alsa-driver package in Ubuntu: New Bug description: # What happened: - Upgraded packages using: sudo apt-get update && sudo apt-get dist- upgrade - Following packages were installed: pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-bluetooth:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 - Find the complete update log attached (dpkg.log written to update_log_23_09_20.txt) # Bug description: - Loudspeaker works fine. Inserting headphones is detected correctly in sound settings but no physical output is generated on the headphone port. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 15:32:02 2020 InstallationDate: Installed on 2018-01-11 (986 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago) dmi.bios.date: 07/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838152] Proposed package upload rejected
An upload of gnome-shell to bionic-proposed has been rejected from the upload queue for the following reason: "Fix appears incomplete, and no progress in a month. Please see https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/5 and subsequent discussion.". -- 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/1838152 Title: gnome-shell freezes on notification arrival (fixed upstream) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Description ] Sometimes certain notifications make the desktop unresponsive for a few seconds and then gnome-shell crashes and all extensions are reloaded. [ Test case ] Install gsconnect extension in gnome-shell: https://extensions.gnome.org/extension/1319/gsconnect/ - Start Up system - first Notification from connected device - Hangs for about 20 sec + This should not happen [ Regression potential ] Persistent state is not kept, although the patch is living upstream for many cycles already, so it's pretty safe. - I have found an upstream bug with a patch, but it's probably not in the Ubuntu's package. I thought of creating an issue in case it is something not known. https://gitlab.gnome.org/GNOME/gnome-shell/issues/470 https://gitlab.gnome.org/GNOME/gnome- shell/commit/86a00b6872375a266449beee1ea6d5e94f1ebbcb In my case it happens only with the notifications of gsconnect and maybe android studio. I have reproduced the problem in gsconnect in case it helps. https://github.com/andyholmes/gnome-shell-extension-gsconnect/issues/549 the error is: lug 27 19:55:56 ghv gnome-shell[4071]: Object Meta.Background (0x55ce6b4cf300), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Ubuntu 18.04 gnome-shell Version: 3.28.4-0ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838152/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890875] Proposed package upload rejected
An upload of gnome-shell to bionic-proposed has been rejected from the upload queue for the following reason: "Fix appears incomplete, and no progress in a month. Please see https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1838152/comments/5 and subsequent discussion.". -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [Impact] What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. [Test Case] Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Then install gnome-shell from bionic-proposed, reboot, and find that an added input source now is effective instantly without any of the mentioned workarounds. [Regression Potential] Minimal. The fix consists of a simple upstream commit which has been in use as from GNOME 3.32. [Other info] Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896774] [NEW] Headphone output stopped working after perfoming dist-upgrade
You have been subscribed to a public bug: # What happened: - Upgraded packages using: sudo apt-get update && sudo apt-get dist- upgrade - Following packages were installed: pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio-module-bluetooth:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 pulseaudio:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14 - Find the complete update log attached (dpkg.log written to update_log_23_09_20.txt) # Bug description: - Loudspeaker works fine. Inserting headphones is detected correctly in sound settings but no physical output is generated on the headphone port. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio CurrentDesktop: Unity Date: Wed Sep 23 15:32:02 2020 InstallationDate: Installed on 2018-01-11 (986 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pascal 2210 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago) dmi.bios.date: 07/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UQ.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UQ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UQ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- Headphone output stopped working after perfoming dist-upgrade https://bugs.launchpad.net/bugs/1896774 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
** Also affects: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Importance: Undecided => High ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: + [ Impact ] + + Using discord application, causes the shell to slowdown and trigger lots + of "unable to lookup icon ..." errors + + [ Test case ] + + Install discord app: + - snap install discord + + Run it, starting a call seems to trigger it more + + [ Regression potential ] + + Icons may not be loaded properly, there may be delays between a good + icon and an invalid one (and vice-versa). + + --- + Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso ** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Focal: In Progress Bug description: [ Impact ] Using discord application, causes the shell to slowdown and trigger lots of "unable to lookup icon ..." errors [ Test case ] Install discord app: - snap install discord Run it, starting a call seems to trigger it more [ Regression potential ] Icons may not be loaded properly, there may be delays between a good icon and an invalid one (and vice-versa). --- Updated bug #1817073 about this, but it's not really the same since this does not crash the shell fully. When speaking in discord there is supposed to be an icon change on the appindicator and logs spam me with [AppIndicatorSupport-FATAL] unable to lookup icon for discord1_40. The whole desktop freezes for a moment when talking in discord if the appindicator package is installed. Easily reproduced by joining a voice channel in discord and just doing stuff in the gnome ui, watching a video or whatever while talking. This is pretty bad since it leaves no choice but to uninstall gnome- shell-extension-appindicator and loosing that functionality if people wants to use discord on ubuntu. This is also reported on the extensions github page: https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/171 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/157 Someone also made a video on youtube showing the problem: https://www.youtube.com/watch?v=ABavT7yXlso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update
** Changed in: tracker (Ubuntu Focal) Importance: Undecided => Low ** Changed in: tracker (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: In Progress Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS The update add a 'tracker export' command, that's new and not used into any integration so has no real regression potential. It's an optional new option that can be used to export the data to migrate them to the incoming tracker3. * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hello, I have exactly the same issue as the creator of this bug. I have a Lenovo Legion 5 15ARH05H, model number 82B1000AUS (https://psref.lenovo.com/Detail/Legion/Lenovo_Legion_5_15ARH05H?M=82B1000AUS), and my touchpad is listed as MSFT0001:00 04F3:3186, not 04F3:3140. How can I help add support for this device in linux? @Coiby Xu (coiby), were the files provided by Gerald Bachner (geri1403) in comment #83 sufficient? Is there anything I can provide to help? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 1
[Desktop-packages] [Bug 1884396] Re: Ubuntu freezing intermittently when the mega.nz appindicator is loaded
** Description changed: [ Impact ] Indicators using (big) pixmap icons cause the shell to use a lot of CPU computation, which interfere with user experience - [ Test case ] - Install mega client from https://mega.nz/sync - Run it in ubuntu and ensure it doesn't block the UI while syncing - (but even opening/closing the app should be enough to trigger + (but even opening/closing the app should be enough to trigger Alternatively use this test tool: - https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js + https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js Launch it with `gjs` and select the 'Crazy icons updates' menu item: - - The shell should not hang + - The shell should not hang [ Regression potential ] Icon updates may be late or not apply immediately (or at all). + In general there has been a refactor of the iconCache, so internally it + may happen that we load an icon more times, or that there could be an + increase in RAM usage as per missing garbage collecting of it. + - - I had similar issues when 20.04 was released, then it disappeared with an upgrade - but sadly it's back. I have short intermittent freezings of the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg when writing this description, the OS freezes every second word. When the freeze goes away the OS is snappy. I have tried switching between Wayland and Xorg - but the problem persists. If I write something when it freezes up the last character will be replicated many times - like what happened jut now. This problem did not show up in ubuntu 18.04 through 19.10. Hope U can fix this soon - using my laptop in unbearable. + I had similar issues when 20.04 was released, then it disappeared with + an upgrade - but sadly it's back. I have short intermittent freezings of + the OS. About every 15-30 seconds Ubunut freezes for a second or two. Eg + when writing this description, the OS freezes every second word. When + the freeze goes away the OS is snappy. I have tried switching between + Wayland and Xorg - but the problem persists. If I write something when + it freezes up the last character will be + replicated many times - like what happened + jut now. This problem did not show up in + ubuntu 18.04 through 19.10. Hope U can + fix this soon - using my laptop in unbearable. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 23:54:52 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Huawei Technologies Co., Ltd. UHD Graphics 620 [19e5:3e04] InstallationDate: Installed on 2020-05-12 (38 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03c0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HD Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HUAWEI MACH-WX9 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a2cbbb7f-c619-418a-a98f-9a9cc31b42fa ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2019 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.28 dmi.board.name: MACH-WX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M13 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M13 dmi.modalias: dmi:bvnHUAWEI:bvr1.28:bd03/15/2019:svnHUAWEI:pnMACH-WX9:pvrM13:rvnHUAWEI:rnMACH-WX9-PCB:rvrM13:cvnHUAWEI:ct10:cvrM13: dmi.product.family: MateBook X dmi.product.name: MACH-WX9 dmi.product.sku: C189 dmi.product.version: M13 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A
[Desktop-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
Could you please stop that reassigning game? You are right, it's either
on shared-mime-info or the qt integration, now the result of the
testcase provided is correct on GNOME (see comment 5), it's also correct
on a cloud instance (e.g no desktop integration) so it's only buggy on
KDE, you should rather reassign to the Qt integration, unsure what the
right component for that is though
** Package changed: shared-mime-info (Ubuntu) => kde-cli-tools (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in kde-cli-tools package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings
testing with xdgmime [1] (reference implementation of the spec [2] and
also used tests on shared-mine-type):
> ../xdgmime/src/print-mime-data .
test.py:
name: text/x-python
data: application/xhtml+xml
file: application/xhtml+xml
> ../xdgmime/src/test-mime test.py
File "test.py" has a mime-type of application/xhtml+xml
[1] https://gitlab.freedesktop.org/xdg/xdgmime
[2] https://freedesktop.org/wiki/Specifications/shared-mime-info-spec/
--
kmimetypefinder5 is just a tiny wrapper over QMimeDatabase [3][4]. So
bug is likely on shared-mime-info or Qt implementation.
[3]
https://github.com/KDE/kde-cli-tools/blob/master/kmimetypefinder/kmimetypefinder.cpp
[4] https://bugs.freedesktop.org/show_bug.cgi?id=99672
** Bug watch added: freedesktop.org Bugzilla #99672
https://bugs.freedesktop.org/show_bug.cgi?id=99672
** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1857824
Title:
kmimetypefinder5 misidentifies mimetype of python files containing
certain strings
Status in kde-cli-tools package in Ubuntu:
New
Bug description:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description: Ubuntu 18.04.3 LTS
Release: 18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896073] Re: SRU the current 2.3.6 stable update
Hey Chris, thanks for the review. The GNOME maintainers sometime has a somewhat flexible definition of what is a bugfix indeed. The command has been added to help migrations from tracker2 to the new tracker3, it's not strictly something we need in focal but at the same time it's a new option so has no regression potential and it could help LTS users to work on their tracker database migration for futur Ubuntu versions. I've updated the description to mention that, let me know if you think it's enough there? https://gitlab.gnome.org/GNOME/tracker/-/commit/30ceebf0 ** Description changed: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS + + The update add a 'tracker export' command, that's new and not used into + any integration so has no real regression potential. It's an optional + new option that can be used to export the data to migrate them to the + incoming tracker3. * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1896073 Title: SRU the current 2.3.6 stable update Status in tracker package in Ubuntu: Fix Released Status in tracker source package in Focal: New Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS The update add a 'tracker export' command, that's new and not used into any integration so has no real regression potential. It's an optional new option that can be used to export the data to migrate them to the incoming tracker3. * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that file search works correctly from the command line, shell and nautilus * Regression potential There is no specific change or feature to test in that update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1896073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857824] [NEW] kmimetypefinder5 misidentifies mimetype of python files containing certain strings
You have been subscribed to a public bug:
Expected behavior:
$ kmimetypefinder5 example.py
text/x-python3
or
$ kmimetypefinder5 example.py
text/x-python
or
$ kmimetypefinder5 example.py
text/plain
Actual behavior:
$ kmimetypefinder5 example.py
application/xhtml+xml
Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.
For example, this python script is identified as
"application/xhtml+xml":
#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
Example title
Example body
"""
print('Hello, world!')
This difficulty is not shared by other mimetype identification tools.
$ kmimetypefinder5 example.py
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
*** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64
Packages
100 /var/lib/dpkg/status
4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: shared-mime-info (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
kmimetypefinder5 misidentifies mimetype of python files containing certain
strings
https://bugs.launchpad.net/bugs/1857824
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
