[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Here an (monospace) overview of recent focal tests. focal amd64 networkd-testpy(F 5% S 0% B 5% => P 90%/) .B...F.. boot-and-services (F 5% S 0% B 5% => P 90%/) .B...F.. upstream (F 5% S 0% B 5% => P 90%/) .B...F.. systemd-fsckd (F 95% S 0% B 5% => P 0%/) FBFF ppc64el systemd-fsckd (F 45% S 0% B 0% => P 55%/) FFF...F..F.. s390x systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF. There also are some linux-meta uploads blocked by the same, but I don't know what task to add for them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in build-essential source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
A bit more explanation can be found here: https://didrocks.fr/2018/01/23 /welcome-to-the-ubuntu-bionic-age-nautilus-a-lts-and-desktop-icons However, I am extremely disappointed. Ubuntu addresses general public, not only nerds who don't make use of desktop icons. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
This is a kernel bug so not sure if it's wise to fix it from userspace... -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
What is left is the similar situation in Focal (as mentioned before). I have updated the tasks to reflect that properly and get update-excuse tagging there. In Focal it is currently blocking qemu and build-essential SRUs and I wanted to ask if the plan is to do the same upload+test-reset there or anything else. @ddstreet - rbalint said you are prepping the systemd SRUs, could you let us know what is the plan there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in build-essential source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in proposed and I was looking forward to a bunch of custom triggers this morning. But I found everything migrated this morning despite those new tests not being done. https://autopkgtest.ubuntu.com/packages/s/systemd/groovy/amd64 Since the bug had no update about it I checked and found: http://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4957 Thanks rbalint - this certainly unblocks things for now. Anything coming later should test against the new systemd version and then hopefully work. Due to that I think we can set the formerly affected extra tasks to invalid (since they were only here for tracking of the update-excuses tag). ** Changed in: ntpsec (Ubuntu) Status: Confirmed => Invalid ** Changed in: kbd (Ubuntu) Status: Confirmed => Invalid ** Changed in: iputils (Ubuntu) Status: Confirmed => Invalid ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid ** Also affects: build-essential (Ubuntu) Importance: Undecided Status: New ** Changed in: build-essential (Ubuntu Focal) Status: New => Confirmed ** Changed in: build-essential (Ubuntu) Status: New => Invalid ** Changed in: qemu (Ubuntu Focal) Status: New => Confirmed ** Changed in: qemu (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in build-essential source package in Focal: Confirmed Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
** Tags added: multimonitor -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892979] Re: Sizing issue on Startup
*** This bug is a duplicate of bug 1892521 *** https://bugs.launchpad.net/bugs/1892521 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892521, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1892521 UI bug - system fonts enlarge after every reboot -- 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/1892979 Title: Sizing issue on Startup Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I recently put together a new PC and installed a fresh Ubuntu 20.04. Immediately I noticed that, on startup, there was a flashing cursor and the decryption password screen was unusually large, but the login screen and desktop GUI was fine, so I thought nothing of it. With a recent update, the decryption password screen and the login screen are now both sized improperly and the text on the GUI is abnormally sized. I have included an image of the GUI with the bug apparent. If I toggle the 'large text' in universal access on then off, the problem resolves, but this is a hassle and happens every startup. I did have issues with the display driver for the GPU on installation and this may be a contributor but I am not sure and I am also not sure where to begin in troubleshooting this problem. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl 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: Wed Aug 26 14:15:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] [1462:8d92] InstallationDate: Installed on 2020-07-28 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B365M D3H ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: B365M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M D3H dmi.product.sku: Default string dmi.product.version: Default stri
[Desktop-packages] [Bug 1794354] Re: [snap] emoji show as black and white if fonts-symbola is installed
Here's a quick fix: sudo apt remove fonts-noto-color-emoji sudo apt install fonts-noto-color-emoji -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1794354 Title: [snap] emoji show as black and white if fonts-symbola is installed Status in chromium-browser package in Ubuntu: Confirmed Bug description: I'm using the Chromium Snap from the Beta channel. Test Case = 0. Be sure you don't have the Chromium deb running. 1. Visit https://launchpad.net/bugs/1779569 The rainbow emoji 🌈 should show in color 2. sudo apt install fonts-symbola 3. Close Chromium. Wait a few moments to make sure it closes then open it and repeat step 1 4. The rainbow emoji 🌈 shows in black and white Other Info == Firefox and GTK apps like gedit correctly show 🌈 in color as long as fonts-noto-color-emoji is installed, regardless of whether fonts-symbola is also installed. I also was unable to duplicate this bug with the Firefox Snap [edge channel 63.0b9-1 (134)]. System Info === Ubuntu 18.10 fonts-noto-color-emoji 0~20180810-1 $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://forum.snapcraft.io/ license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 8 days ago, at 13:41 EDT channels: stable:69.0.3497.100 (494) 141MB - candidate: 69.0.3497.100 (494) 141MB - beta: 70.0.3538.16 (487) 142MB - edge: 70.0.3538.9 (472) 142MB - installed: 70.0.3538.16 (487) 142MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1794354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892979] Re: Sizing issue on Startup
*** This bug is a duplicate of bug 1892521 *** https://bugs.launchpad.net/bugs/1892521 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892979 Title: Sizing issue on Startup Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I recently put together a new PC and installed a fresh Ubuntu 20.04. Immediately I noticed that, on startup, there was a flashing cursor and the decryption password screen was unusually large, but the login screen and desktop GUI was fine, so I thought nothing of it. With a recent update, the decryption password screen and the login screen are now both sized improperly and the text on the GUI is abnormally sized. I have included an image of the GUI with the bug apparent. If I toggle the 'large text' in universal access on then off, the problem resolves, but this is a hassle and happens every startup. I did have issues with the display driver for the GPU on installation and this may be a contributor but I am not sure and I am also not sure where to begin in troubleshooting this problem. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl 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: Wed Aug 26 14:15:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] [1462:8d92] InstallationDate: Installed on 2020-07-28 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B365M D3H ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: B365M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-v
[Desktop-packages] [Bug 1892979] [NEW] Sizing issue on Startup
Public bug reported: Hello, I recently put together a new PC and installed a fresh Ubuntu 20.04. Immediately I noticed that, on startup, there was a flashing cursor and the decryption password screen was unusually large, but the login screen and desktop GUI was fine, so I thought nothing of it. With a recent update, the decryption password screen and the login screen are now both sized improperly and the text on the GUI is abnormally sized. I have included an image of the GUI with the bug apparent. If I toggle the 'large text' in universal access on then off, the problem resolves, but this is a hassle and happens every startup. I did have issues with the display driver for the GPU on installation and this may be a contributor but I am not sure and I am also not sure where to begin in troubleshooting this problem. Any help would be greatly appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl 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: Wed Aug 26 14:15:32 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] [1462:8d92] InstallationDate: Installed on 2020-07-28 (28 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard Bus 001 Device 003: ID :0538 USB OPTICAL MOUSE Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. B365M D3H ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: Default string dmi.board.name: B365M D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B365M D3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal fonts ubuntu ** Attachment added: "Screenshot of GUI with enlarged text" https://bugs.launchpad.net/bugs/1892979/+attachment/5404595/+files/Screenshot%20from%202020-08-25%2020-36-38.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.l
[Desktop-packages] [Bug 1887383] Re: Yaru updates not related to themes and icons
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887383 Title: Yaru updates not related to themes and icons Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * Several parts of the build, including the yaru README and github actions to stay synced with upstream, are out of date and need updates. Those changes are: - fix Yaru project name + update README pictures - build: deduplicate meson.build and introduce Flavours https://github.com/ubuntu/yaru/pull/1884 - add libgtk-3-dev to the bootstrap script https://github.com/ubuntu/yaru/pull/ - updates to the upstream directories, which include the source code of the unmodified upstream gnome-shell and gtk3 themes https://github.com/ubuntu/yaru/pull/2084 - Use MESON_INSTALL_DESTDIR_PREFIX in post_install.py to avoid errors while building https://github.com/ubuntu/yaru/pull/2206 - Check for updates to GitHub Actions every weekday https://github.com/ubuntu/yaru/pull/2223 - Adding new non-uniform app icon templates https://github.com/ubuntu/yaru/pull/1920 * Backporting these updates to focal, will greatly improve the build process of the yaru project and help to avoid bugs and help the development of the team * all fixes are in yaru master since several weeks and have been tested several times [Test Case] * Look at the yaru project page while in this branch https://github.com/ubuntu/yaru/tree/ubuntu/focal and find the images to be removed * Look at the yaru project page while in the master branch https://github.com/ubuntu/yaru/tree/master and find all images to show what currently is in focal * All other test cases are described in the corresponding pull requests [Regression Potential] * Outdated versions of meson may clash with the current yaru build, otherwise, no regression potential * Unity theme misses assets [Other Info] * Those changes are not "visible" for the end-user while using the ubuntu desktop, i.e. no theme changes, no icon changes here, but they greatly improve the daily work of the yaru team To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887389] Re: Microphone icon outlines can look fuzzy on certain screens
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887389 Title: Microphone icon outlines can look fuzzy on certain screens Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * The microphone icon only consists of small outlines which are very close to each other, making the icon look fuzzy and hard to understand, especially on screens with high sharpness * Backporting this to focal would greatly improve the visibility and legibility of the microphone icon and thus help to improve the overall look of the ubuntu desktop in focal * The fix is already in ubuntu master: https://github.com/ubuntu/yaru/pull/2200 [Test Case] * If your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display until the icon becomes fuzzy and hard to understand * Install yaru from -proposed and if your computer does not have an integrated microphone, connect an external microphone to your computer and see how it shows up in the gnome-shell top panel. Increase the sharpness of your display and watch how the icon stays sharp and "intact" even with high sharpness [Regression Potential] * No regression potential, tested by building the branch of the pull request [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887419] Re: Lollypop music player mixes Yaru and Adwaita symbols
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887419 Title: Lollypop music player mixes Yaru and Adwaita symbols Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * The Yaru theme has some of the icons used by Lollypop but not all of them. This results in the Lollypop sidebar having a mix of Adwaita symbols (with 2px strokes) and Yaru ones (which have 1px). See GitHub issue https://github.com/ubuntu/yaru/issues/2208. * Reason to backport to Focal: displaying symbols from two different themes gives a poor impression of Ubuntu to users who want to use a popular native music player. [Test Case] * Install Lollypop and look at the sidebar. Some of the symbols are heavy and some are light. (Alternatively, the GitHub issue linked above has a screenshot.) * Install yaru from -proposed and notice how the Lollypop sidebar is now consistent with itself and the rest of the Yaru theme. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Links to the GitHub PRs: https://github.com/ubuntu/yaru/pull/2235 and https://github.com/ubuntu/yaru/pull/2253. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887419/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887393] Re: The system-lock-screen icon has a twisted/deformed path
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887393 Title: The system-lock-screen icon has a twisted/deformed path Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * The lock icon in gnome-control-center privacy page has a twisted path in it's key-hole * Backporting this to focal, would greatly increase the level of visual polish and increase the professional look of the ubuntu desktop and the yaru icon theme * The fix is already in the yaru master branch: https://github.com/ubuntu/yaru/issues/2201 [Test Case] * Open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see the twisted path of the key whole * Install yaru from -proposed, open gnome-control-center, AKA "settings" from either clicking on the wheel icon in the gnome shell system tray popup or by searching for "settings" from within the gnome shell search. Scroll until you see the privacy section. Look at the lock icon and see that the path of the key-hole is now an even square [Regression Potential] * No regression potential, tested by building the branch in the pull request [Other Info] * Link to the github issue: https://github.com/ubuntu/yaru/issues/2201 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887300] Re: Wacom overlay text labels are invisible
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887300 Title: Wacom overlay text labels are invisible Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: https://github.com/ubuntu/yaru/issues/2099 [Impact] * The wacom overlay text is invisible and users can not use this gnome-shell dialog to map their wacom tablet hardware buttons * Backporting this to the stable release focal will let wacom users use this dialogue again, which is very important because you have no other way to map it in ubuntu * The fix is already in yaru master https://github.com/ubuntu/yaru/pull/2198 [Test Case] * Plug a wacom tablet to your computer, search for "wacom" in the gnome shell search and press enter to open the corresponding gnome- control-center page. Now open the dialog to map your buttons. See how the labels for each button are invisible * Install yaru from -proposed and repeat these steps and see how the labels appear and you can properly map the correct button [Regression Potential] * No regression potential * Built and tested with the yaru master branch [Other Info] * Yaru issue: https://github.com/ubuntu/yaru/issues/2099 * yaru fix: https://github.com/ubuntu/yaru/pull/2198 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887298] Re: blue GtkSpinner is hard to see on red .destrucive-action buttons
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887298 Title: blue GtkSpinner is hard to see on red .destrucive-action buttons Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * Blue blue GtkSpinner is hard to see on red .destrucive-action buttons, like the "Stop scanning" button in simple-scan, Link to the yaru github issue: https://github.com/ubuntu/yaru/issues/2182 * Reason to backport this to focal: users have it very hard to see the spinner, especially color blind people, backporting this will greatly improve the accessibility and legibility of the yaru theme and the ubuntu desktop for focal users [Test Case] * Press the green "Scan" button in simple-scan and it will turn red with a "Stop" label and a blue spinner inside the button. The spinner is hard to see on this red background * Use yaru from -proposed and notice how the white spinner is much more visible against a red background [Regression Potential] * No regression potential * Tested by building yaru from source [Other Info] * Link to the github pull request: https://github.com/ubuntu/yaru/pull/2187 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887411] Re: system-users-symbolic icon has unclear visual metaphor
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887411 Title: system-users-symbolic icon has unclear visual metaphor Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * The system-users-symbolic icon doesn't represent users in the plural. It shows a single generic figure (head and shoulders) representing one user. This is a misleading visual metaphor, since a single head and shoulders is universally recognised as the current or logged-in user. * Reason to backport to Focal: the corresponding Adwaita icon shows two users. Third party apps that use the icon will expect it to represent more than one person. Failing to provide a suitable icon will have confusing results in Ubuntu. [Test Case] * Install Lollypop and look at the sidebar. "Compilations" has the symbol of a single user, which is confusing. Lollypop requested an icon with multiple figures to represent multiple artists, but Ubuntu supplied something inappropriate. This issue may be duplicated whenever a third party app uses this icon. * Install yaru from -proposed and notice how the icon now has the same visual metaphor as Adwaita (i.e., it shows two users). The Lollypop UI makes more sense and the theme honours the app's intentions. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the Github PR: https://github.com/ubuntu/yaru/pull/2209 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887388] Re: Several mimetype icons are missing
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887388 Title: Several mimetype icons are missing Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * Many mimetype icons are not showing up in yaru, even if they have been included in the yaru theme suite and some mimetype icons are were not included previously * Backporting them to focal would greatly increase the differentiation of the file types that are existent for the average user * All those fixes are already in yaru master: - img and iso https://github.com/ubuntu/yaru/pull/2213 - Lilypond https://github.com/ubuntu/yaru/pull/2230 - QML https://github.com/ubuntu/yaru/pull/2226 - log files https://github.com/ubuntu/yaru/pull/2229 - arduino, jpynbgjson, mswinurl, cursor https://github.com/ubuntu/yaru/pull/2234 - scala https://github.com/ubuntu/yaru/pull/2231 - lmms https://github.com/ubuntu/yaru/pull/2249 - theme files https://github.com/ubuntu/yaru/pull/2243 - rss https://github.com/ubuntu/yaru/pull/2248 - executable https://github.com/ubuntu/yaru/pull/2204 - apple images https://github.com/ubuntu/yaru/pull/2233 [Test Case] * open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have either a generic text file as their mimetype icon or the wrong mimetype icon * install yaru master branch and open nautilus and look at img and iso, Lilypond, QML, log files, arduino, scala, lmms, theme, rss, executable, apple files and notice how they all have the correct mimetype icons which make it very clear what is inside those files [Regression Potential] * No regression potential, tested by building all pull requests [Other Info] * No additional information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1887388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887297] Re: gnome-shell notifications and gtk3 menus are hard to distinguish from the background
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887297 Title: gnome-shell notifications and gtk3 menus are hard to distinguish from the background Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * Gtk and shell menus, popups and notifications are often hard to distinguish against the elements that are beneath them (Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217) * backporting this QOL change to focal would greatly improve the legibility of the yaru theme(s) * the fixes for this are already in the master branch of https://github.com/ubuntu/yaru [Test Case] * populate gtk3 menus against a nautilus window and spawn a notification by either adding or removing a favourite app in the dock with rightclick add/remove favourite. Gtk3 menus almost look like they are part of the window and not a different part of the desktop. Notifications, especially when using yaru-light are also hard to see and recognize [Regression Potential] * No regression potential * Tested by building the fixed branch(es) of yaru and then switching back and forth the gtk3 and shell themes, please see the corresponding github pull requests https://github.com/ubuntu/yaru/pull/2232 + https://github.com/ubuntu/yaru/pull/2236 [Other Info] * Yaru github bugs: https://github.com/ubuntu/yaru/issues/2221 and https://github.com/ubuntu/yaru/issues/2217 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887420] Re: network-cellular-connected-symbolic isn't monochrome
This bug was fixed in the package yaru-theme - 20.04.8 --- yaru-theme (20.04.8) focal; urgency=medium [ Carlo Lobrano, Chris Billington, John Losito, ubuntujaggers ] * updates not related to themes and icons (LP: #1887383) [ Feichtmeier ] * Fix visibility of spinner on destructbutton (LP: #1887298) * Make wacom overlay visible (LP: #1887300) * Increase Gtk3 menu and Shell popup visibility (LP: #1887297) [ MadsRH, Muqtadir, Wes, ubuntujaggers ] * Update supported mimetype icons (LP: #1887388) [ ubuntujaggers ] * Fix system-users-symbolic to represent multiple users (LP: #1887411) * Add missing icons for Lollypop UI (LP: #1887419) * Removing green from network-cellular-connected-symbolic (LP: #1887420) * Rounding corners on avatar-default-symbolic (#2253) [ R. David Dunphy ] * Nemo selected text highlighting and inactive pane shading (#2220) [ Jupiter007 ] * Add a solid background to microphone icons (LP: #1887389) * Fix system-lock-screen twisted path (LP: #1887393) * Add missing Simple-scan symbolic icons (#2244) [ Marco Trevisan (Treviño) ] * debian/rules: enable building unity theme (related to lp:1887383) -- Marco Trevisan (Treviño) Fri, 17 Jul 2020 03:15:44 +0200 ** Changed in: yaru-theme (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1887420 Title: network-cellular-connected-symbolic isn't monochrome Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Focal: Fix Released Bug description: [Impact] * The icon called network-cellular-connected-symbolic appears at the top right of the desktop when users connect to their phones via bluetooth to use data. The icon includes green fill, which is inconsistent with the monochrome icons used for (e.g.) wifi. See GitHub issue https://github.com/ubuntu/yaru/issues/2192. * Reason to backport to Focal: the inconsistency was missed because I don't use this feature and it's an unfortunate oversight. When the icon appears, it does so in a prominent position and is constantly visible to the user, giving a poor impression of Ubuntu. [Test Case] * Use Bluetooth tethering so your laptop is making use of your phone's data connection. Notice that, unlike the rest of the icons at the top right of the screen, the symbol for the connection isn't monochrome. * Install yaru from -proposed and notice how all icons are now monochrome. [Regression Potential] * No regression potential. * Tested by building Yaru from source. [Other Info] * Link to the GitHub PR: https://github.com/ubuntu/yaru/pull/2252. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1887420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
** No longer affects: nvidia-graphics-drivers (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers (Ubuntu) -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] When the nvidia driver is installed, the screen turns off when trying to set some fractional scaling values like 150%. And it stays off even after rebooting and logging in again. And from ssh I can see there's no current mode set anymore (just like in bug 1869750): $ xrandr Screen 0: minimum 8 x 8, current 960 x 600, maximum 16384 x 16384 DVI-I-0 disconnected (normal left inverted right x axis y axis) DVI-I-1 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary (normal left inverted right x axis y axis) 1920x1200 59.95 + 59.88 [ Test case ] In a Nvidia system: - From g-c-c enable fractional scaling - Set all the available fractional scaling values and ensure they work + In any case the screen should be turned off [ Regression potential ] Wrong screen size is set and panning might be enabled. --- ProblemType: BugDistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 17 15:51:15 2020 InstallationDate: Installed on 2020-02-03 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)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/1873403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
** No longer affects: gnome-control-center (Ubuntu Focal) ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers-340 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-440 (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers-440 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-435 (Ubuntu Focal) ** No longer affects: nvidia-graphics-drivers-435 (Ubuntu) -- 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/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-
[Desktop-packages] [Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
This bug was fixed in the package gnome-control-center - 1:3.37.90-1ubuntu2 --- gnome-control-center (1:3.37.90-1ubuntu2) groovy; urgency=medium * d/p/0009-lock-Add-Lock-Screen-on-Suspend-option.patch, d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch: - updated to work correctly with the new libhandy * debian/patches/ubuntu_restore_sharing.patch: - restore the ability to share the screen using vino, upstream is using gnome-remote-desktop but that's not enabled in Ubuntu (lp: #1892484) * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - fix the missing control with the new libhandy (lp: #1892833) -- Sebastien Bacher Mon, 24 Aug 2020 12:27:52 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1892484 Title: Screen Sharing option is missing in 20.10, but exists in 20.04. Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Screen Sharing option is missing in 20.10, but exists in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Aug 21 18:08:23 2020 InstallationDate: Installed on 2020-07-16 (36 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892484/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892833] Re: Fractional Scaling toggle is blank/missing in Settings
This bug was fixed in the package gnome-control-center - 1:3.37.90-1ubuntu2 --- gnome-control-center (1:3.37.90-1ubuntu2) groovy; urgency=medium * d/p/0009-lock-Add-Lock-Screen-on-Suspend-option.patch, d/p/0015-connectivity-add-network-connectivity-checking-toggl.patch: - updated to work correctly with the new libhandy * debian/patches/ubuntu_restore_sharing.patch: - restore the ability to share the screen using vino, upstream is using gnome-remote-desktop but that's not enabled in Ubuntu (lp: #1892484) * d/p/0024-display-Allow-fractional-scaling-to-be-enabled.patch: - fix the missing control with the new libhandy (lp: #1892833) -- Sebastien Bacher Mon, 24 Aug 2020 12:27:52 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- 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/1892833 Title: Fractional Scaling toggle is blank/missing in Settings Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Fractional Scaling toggle is blank/missing in Settings ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 16:11:46 2020 InstallationDate: Installed on 2020-07-16 (40 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200507) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892973] Re: gnome-session fails, and fails, and fails yet again
Next time the hang occurs, please reboot and then immediately run: journalctl -b-1 > prevboot.txt lspci -kv > lspci.txt gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text files here. Please also run this command to complete the bug report: apport-collect 1892973 And in future be careful to only discuss a single topic per bug report. You can also save time by reporting future bugs with the 'ubuntu-bug' command that will do much of this automatically. ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892973 Title: gnome-session fails, and fails, and fails yet again Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most g
[Desktop-packages] [Bug 1892973] Re: gnome-session fails, and fails, and fails yet again
Please also check /var/crash for any crash files. If you find some then please turn those into new bugs using the 'ubuntu-bug' command. And tell us the new bug IDs. -- 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/1892973 Title: gnome-session fails, and fails, and fails yet again Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net
[Desktop-packages] [Bug 1892928] Re: Audio settings shows wrong application icons
It appears you are somehow missing the latest updates. To get them please: sudo apt update sudo apt full-upgrade Reboot. Then if the problem still happens please report it to the developers at: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues and tell us the new issue ID. ** Summary changed: - Audio settings shows wrong icons + Audio settings shows wrong application icons ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1892928 Title: Audio settings shows wrong application icons Status in gnome-control-center package in Ubuntu: Incomplete Bug description: The gnome sound settings show wrong icons https://pasteboard.co/Jo3btdG.png (here e.g. Chromium icon for Opera) In the program menu all icons are correct. (Ubuntu 20.04, Gnome 3.36.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_29_33_generic_69 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 22:34:35 2020 InstallationDate: Installed on 2019-06-22 (430 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/ubuntu/+source/gnome-control-center/+bug/1892928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892898] Re: screen goes down automatic
*** This bug is a duplicate of bug 1892615 *** https://bugs.launchpad.net/bugs/1892615 ** This bug has been marked a duplicate of bug 1892615 screen goes down sometimes -- 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/1892898 Title: screen goes down automatic Status in xorg package in Ubuntu: New Bug description: screen goes down automatic updating will not solve it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Tue Aug 25 23:03:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1774 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu May 28 11:49:11 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892915] Re: gnome-shell crashing with Wayland
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892915 Title: gnome-shell crashing with Wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892975] [NEW] /usr/sbin/gdm3:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session
*** This bug is a duplicate of bug 1878775 *** https://bugs.launchpad.net/bugs/1878775 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c77910928db3b8a07237c3daf98ba0da6aaa48fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1892975 Title: /usr/sbin/gdm3:11:g_str_hash:g_hash_table_lookup:g_autoptr_cleanup_generic_gfree:_systemd_session_is_graphical:_find_graphical_systemd_session Status in gdm3 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gdm3. This problem was most recently seen with package version 3.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/c77910928db3b8a07237c3daf98ba0da6aaa48fb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1892975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892973] [NEW] gnome-session fails, and fails, and fails yet again
Public bug reported: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. Steps to reproduce 1. Install gnome-session. 2. Reboot. 3. Use graphical applications. What happened] The screen froze irretrievably. Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is triggered by activity (launching or using gnome-settings; resizing a window; using Nautilus), sometimes, not. No session lasts more than five minutes. No combination of keystrokes will yield a terminal of any kind. The hang also interrupts System Monitor output, so no information regarding use of system resources is available. A hard system reset and consequent reboot yields a variety of outcomes. Sometimes, a normal gdm login. Sometimes, a black screen with an inverted-black mouse cursor/pointer/arrow that moves. Sometimes an entirely black screen. Sometimes, not even a hard system reset is sufficient and the system has to be booted into recovery mode, the existing driver removed, and another installed, before rebooting again. With nvidia-driver-440, fewer hangs but the monitor resolution can't be set to its capacity. I don't get it. GNOME hangs have been extensively documented for ten years. The drivers expressly support the hardware. This package is part of an Ubuntu LTS release. Is gnome-session intended to be serious, functional, production software subjected to rigorous and competent quality control? This is a serious question because I have a business to run and can't be sucked down some random technical rabbit hole just to do daily work. Is GNOME just a cute code project intended as a resume line for people looking for real work? What kind of quality control processes are in place that allow ancient failures, extensively reported, to persist? Is anyone at GNOME able and willing to put on their big-boy pants to get a reliable package suitable for production deployments, released? The command cat /var/log/syslog | grep gnome-session reveals fundamental errors in implementing systemd syntax and references/calls to nonexistent binaries. See the gnome-sesion units in /usr/lib/systemd/user. Maybe getting this right would be a first step to helping the developers understand the environment better. Please see man systemd. Source is, astonishingly, a hybrid of C and Javascript, which doubtless presents a QC nightmare. Has anyone given this any thought? What does it take to get this package to work today? - What is the procedure? What commands must be run? - Why doesn't GNOME simply include these commands in a script, just to make it easier? Does anyone there know how? - Why doesn't GNOME simply compile these commands into the package so it works in the first place? - Will a different graphics card matter? - Which one? - Why, if the drivers support the existing hardware, according to the documentation if not the function? Can this package be made to work today? If not, will this package be ready for production use in the next Ubuntu release (i.e., 20.04.02)? If not, what alternatives exist for production use? These are all serious questions. It is astonishing that this package has been released to the public. It getting out the door poses an existential reputational threat to the GNOME project. Any help in getting this package to work would be most gratefully appreciated. What did you expect to happen I expected the screen not to freeze. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 gnome-session gnome-shell nvidia xorg ** Information type changed from Private Security to Public ** Tags added: 20.04 gnome-session gnome-shell nvidia xorg -- 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/1892973 Title: gnome-session fails, and fails, and fails yet again Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 20.04.01, gnome-shell 3.36.4, nvidia-driver-450, nvidia- driver-440. Both drivers expressly support the hardware. All varieties of desktop environment (Xorg, Gnome Classic, Ubuntu) Bug summary Screen hangs randomly and iretrievably with the only possibility of recovery being a a hard system reset. Sometimes this is tri
[Desktop-packages] [Bug 1892972] [NEW] package deja-dup 40.6-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: this occur after installing updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: deja-dup 40.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 26 10:49:34 2020 DpkgTerminalLog: dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: deja-dup Title: package deja-dup 40.6-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1892972 Title: package deja-dup 40.6-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in deja-dup package in Ubuntu: New Bug description: this occur after installing updates ProblemType: Package DistroRelease: Ubuntu 20.04 Package: deja-dup 40.6-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Aug 26 10:49:34 2020 DpkgTerminalLog: dpkg: error processing package deja-dup (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: deja-dup Title: package deja-dup 40.6-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1892972/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04
** Summary changed: - [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards + [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 -- 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: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 Status in mutter package in Ubuntu: Confirmed Bug description: 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:GNOME DistroRelease: 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 1892864] Re: gnome-shell font scaling is reset after every reboot after mutter update
*** This bug is a duplicate of bug 1892440 *** https://bugs.launchpad.net/bugs/1892440 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892440, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1892440 [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards -- 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/1892864 Title: gnome-shell font scaling is reset after every reboot after mutter update Status in mutter package in Ubuntu: New Bug description: Hi, after the latest update to mutter, gnome-shell is constantly resetting font-scaling after reboot. All programs scale fine, even nautilus, it's just the shell ui that is being reset. I get this bug in 2 different ubuntu installations on 2 different pcs. I use gnome-tweak-tool to set font scaling to 1.25, everything was working ok until latest mutter update a few days ago. After reboot, gnome shell scaling is reset to 1.00 (thought I still see 1.25 as value in gnome-tweak). It is a very annoying bug for a hidpi screen, expecially because fractional scaling is still too unstable to use. But adjusting fonts was just fine, until a few days ago. Thank you for your help, Alessio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.4-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 14:42:21 2020 InstallationDate: Installed on 2020-05-01 (116 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892847] Re: Xorg freeze
It sounds like something is crashing. If you find any files in /var/crash then please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment Otherwise, next time you have to restart using the power button, please run this command as soon as it restarts: journalctl -b-1 > prevboot.txt and then attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- 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/1892847 Title: Screen freeze Status in Ubuntu: Incomplete Bug description: I plug a network adapter to my pc, it's TP-Link, i connect to a wifi, then i start sharing connection using hostspot (using my pc network card), after maybe 1h, the screen freeze and everything stop, i had to restart it using the power button. After that i did the same thing, everything was ok, than i tried to write ifconfig, nothing happen, the settings freeze, and when i unplug the adabter the screen freeze and i had to restart it using the power button. and even when i just use my network card, it freeze sometime, i don't know why. yesterday it wrote (failed to evaluate _DSM), i searched about it and i didn't understand. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 10:39:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba Corporation 3rd Gen Core processor Graphics Controller [1179:fa33] Subsystem: Toshiba Corporation GeForce 710M [1179:fa33] InstallationDate: Installed on 2020-08-02 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: TOSHIBA SATELLITE C55-A-1UV ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=93843777-b112-4ce6-81dc-fb6cddf7e1f3 ro net.ifnames=0 biosdevname=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: PT10F dmi.board.vendor: Intel dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.30:bd11/22/2013:svnTOSHIBA:pnSATELLITEC55-A-1UV:pvrPSCGCE-02M00KG4:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE C55-A-1UV dmi.product.sku: PSCGCE dmi.product.version: PSCGCE-02M00KG4 dmi.sys.vendor: TOSHIBA 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1892847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
> it looks like g-c-c has chosen a mode that doesn't actually exist for xrandr, because none of the modes have an asterisk next to them. Good point. Please report that as a bug to mutter here: https://gitlab.gnome.org/GNOME/mutter/issues -- 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/1892296 Title: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
My concern is that you might be taking functionality (deep/wide colour) away from people for whom it works. -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in Linux: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Triaged Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Thanks. That new issue you mention is bug 1892521. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-control-center (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) ** No longer affects: gnome-control-center (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1874217 Title: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Just wait for the mutter version 3.36.5 update. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
Although as a workaround, changing your background wallpaper should also resolve it each time. -- 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mesa (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: Ubuntu hangs while changing display brightness from keyboard shortcut
You're probably not using 'gnome-shell-extension-brightness-control'. Please run this command to send us more information about the system: apport-collect 1892747 ** Package changed: gnome-shell-extension-brightness-control (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892747 Title: Ubuntu hangs while changing display brightness from keyboard shortcut Status in gnome-shell package in Ubuntu: Incomplete 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. 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 1892759] Re: Glitches in the application menu
Please also use the 'ubuntu-bug' command to create bugs in future. -- 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/1892759 Title: Glitches in the application menu Status in gnome-shell package in Ubuntu: Incomplete Bug description: There is a bug where when a folder is open and closed, the number of page indications increase for no reason, more than the required number (Refer attachment): https://launchpadlibrarian.net/494901134/Screencast%20from%2025-08-20%2012%2018%2043%20PM%20IST.mp4 Another glitch I noticed is when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 I've also noticed sometimes there is a slight glitch in the animation: (Refer attachments): https://launchpadlibrarian.net/494821177/Screencast%20from%2024-08-20%2009%2014%2030%20PM%20IST%20 %28online-video-cutter.com%29.mp4 and https://launchpadlibrarian.net/494952421/Screencast%20from%2025-08-20%2006%2030%2030%20PM%20IST.mp4 Also,I've noticed this when the menu is opened right after an application is opened from the menu (Refer attachment): https://launchpadlibrarian.net/494952547/Screencast%20from%2025-08-20%2007%2026%2042%20PM%20IST.mp4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889102] Re: App grid has too many page dots on right
I've heard enough reports of this bug recently from multiple people that it is confirmed at least. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1889102 Title: App grid has too many page dots on right Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have noticed a bug with the applications menu. I am having a weird issue with adding apps into folders on the menu. If I try opening a folder, the entire screen glitches out and the bar on the right-hand size showing how many pages are on the menu show more pages than there actually is. Occasionally if I try adding or removing an app to a folder, the entire system freezes. The only way I am able to get things back to normal is a forced restart by holding down the power button. The only way I have been able to not come across this issue is to have no folders in my menu at all, which took a while as the system kept crashing during the process. However, I am no longer experiencing the issue with no folders, but it returns when I try creating a folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 16:31:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3f1a] InstallationDate: Installed on 2020-07-22 (4 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 002: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81VV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1664842e-9af5-44b6-a3c8-f9235f094044 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN21WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.modalias: dmi:bvnLENOVO:bvrCUCN21WW(V1.10):bd05/27/2020:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892759] Re: Glitches in the application menu
Please open a separate bug for each issue. The first issue about page indicators is already bug 1889102. ** Package changed: menu (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892759 Title: Glitches in the application menu Status in gnome-shell package in Ubuntu: Incomplete Bug description: There is a bug where when a folder is open and closed, the number of page indications increase for no reason, more than the required number (Refer attachment): https://launchpadlibrarian.net/494901134/Screencast%20from%2025-08-20%2012%2018%2043%20PM%20IST.mp4 Another glitch I noticed is when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 I've also noticed sometimes there is a slight glitch in the animation: (Refer attachments): https://launchpadlibrarian.net/494821177/Screencast%20from%2024-08-20%2009%2014%2030%20PM%20IST%20 %28online-video-cutter.com%29.mp4 and https://launchpadlibrarian.net/494952421/Screencast%20from%2025-08-20%2006%2030%2030%20PM%20IST.mp4 Also,I've noticed this when the menu is opened right after an application is opened from the menu (Refer attachment): https://launchpadlibrarian.net/494952547/Screencast%20from%2025-08-20%2007%2026%2042%20PM%20IST.mp4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875101] Re: Hidden WiFi does not automatically connect on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1875101 Title: Hidden WiFi does not automatically connect on startup Status in network-manager package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad T430 Ubuntu 20.04 LTS When starting Ubuntu 20.04 LTS from cold boot or reboot, hidden WiFi networks do not automatically connect despite having this option selected. This is new to 20.04 and did not exist in 18.04. Waking from suspend does not have this issue. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-25 (579 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.12 metric 600 Package: network-manager-applet (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-19 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 Pandanet 9254f39c-f7a5-4542-adda-599069bfd65d /org/freedesktop/NetworkManager/ActiveConnection/3 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1875101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] Ubuntu hangs while changing display brightness from keyboard shortcut
You have been subscribed to a public bug: 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. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Ubuntu hangs while changing display brightness from keyboard shortcut https://bugs.launchpad.net/bugs/1892747 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892759] [NEW] Glitches in the application menu
You have been subscribed to a public bug: There is a bug where when a folder is open and closed, the number of page indications increase for no reason, more than the required number (Refer attachment): https://launchpadlibrarian.net/494901134/Screencast%20from%2025-08-20%2012%2018%2043%20PM%20IST.mp4 Another glitch I noticed is when the menu is scrolled before it is fully loaded, the two pages collide (Refer attachment): https://launchpadlibrarian.net/494901346/Screencast%20from%2025-08-20%2012%2020%2046%20PM%20IST.mp4 I've also noticed sometimes there is a slight glitch in the animation: (Refer attachments): https://launchpadlibrarian.net/494821177/Screencast%20from%2024-08-20%2009%2014%2030%20PM%20IST%20 %28online-video-cutter.com%29.mp4 and https://launchpadlibrarian.net/494952421/Screencast%20from%2025-08-20%2006%2030%2030%20PM%20IST.mp4 Also,I've noticed this when the menu is opened right after an application is opened from the menu (Refer attachment): https://launchpadlibrarian.net/494952547/Screencast%20from%2025-08-20%2007%2026%2042%20PM%20IST.mp4 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Glitches in the application menu https://bugs.launchpad.net/bugs/1892759 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3091 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3091 -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682542]
Also tracking in https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/3091 -- 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/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc Status in GNOME Shell: Incomplete Status in gnome-shell package in Ubuntu: Triaged Bug description: This issue will effectively be a regression in desktop usage once Ubuntu switches from Unity to Gnome Shell. Gnome Shell does not work well with multiple monitors unlike every other desktop environment except Budgie, which is switching away from GTK/Gnome to Qt with Budgie 11 due out in the next month or two. I reported it upstream last month but it does not appear to have much traction at the moment. https://bugzilla.gnome.org/show_bug.cgi?id=780078 " It would be nice if the primary included gnome-shell extensions, eg apps-menu and places-menu (and by extension the topbar) supported multi-monitor similar to how the bottom bar 'window-list' currently does. This was easy to achieve on Gnome 2 and now via MATE (out of the box) but there does not appear to be any way to do this with Gnome 3. This also leads to there not being a way to do this via 'Gnome Classic'. Even Windows finally (in W10) does this better out of the box than Gnome 3. BTW - Intel has supported IGP triple head since Ivy Bridge (2012) so it is very cheap to deploy a triple head system (~ $200 for 3 1080p monitors). AMD supports up to quad head in their IGPs. This has been blocking me from moving to Gnome 3 since its release and I finally decided to write a bug report about it. I have had all multi-monitor systems since prior to 2004. " And see comments #11 and #14 from Florian. " No, you don't want that in the extensions. Each extension is separate, so what you are asking for here is that apps-menu and places-menu *both* add top bars to non-primary monitors. We are definitely not going to add two or more stacked panels at the top. What you probably want instead is an option in gnome-shell to put top bars on non-primary monitors, and the aforementioned extensions to handle that case. " " Well, we've established what you want, but that doesn't necessarily mean that we'll implement it. So far the reasoning seems to be: - you really want the feature - GNOME 2 / Windows has it Unlike the case of the window list, nothing in the top bar (except for the app menu to some extent) is tied to a particular monitor, so there's a much weaker case here IMHO. (I'll also note that this wouldn't be a "cheap" option, but require work on lots of details throughout the stack - we'd need to figure out the overview (only include the activities button on the primary monitor? or allow an overview on any monitor?), get API to control the brightness of a particular monitor (rather than the built-in one), don't use "the monitor with the top bar" as indicator for the primary monitor in Settings, ...) " To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586822]
This change will allow more easily to change the default folder through a pref. Though, that bug doesn't exist, so maybe we could convert this one to cover that. [TalktoSonic](https://www.talktosonic.us/) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1586822 Title: Ability to set default save destination for new bookmarks Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Though I can understand the rationale for making all new bookmarks go into an "Unsorted Bookmarks" area, I think that it would be good if Firefox provided an option to allow the user to change the default save location for new bookmarks, because I for one don't want to have to move every new bookmark I make to the "Bookmarks Toolbar", I would like to be able to have them just go there automatically, but I can't currently so it would be good if there were an option to change the default save location of bookmarks. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1586822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732766] Re: firefox 57 does not display fish in fishgl.com on intel 530?
** Changed in: firefox Importance: Medium => Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1732766 Title: firefox 57 does not display fish in fishgl.com on intel 530? Status in Mozilla Firefox: In Progress Status in firefox package in Ubuntu: Confirmed Bug description: On my two intel graphics Ubuntu 16.04 systems (both Dell 3620's), firefox does not display any fish; it simply shows the back wall. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.0.7 OpenGL core profile shading language version string: 4.50 fishgl works fine in chrome, and on other ubuntu systems here. Affects both firefox 56.0+build6-0ubuntu0.16.04.2 and 57.0+build4-0ubuntu0.16.04.5 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 57.0+build4-0ubuntu0.16.04.5 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dank 1843 F...m pulseaudio /dev/snd/controlC0: dank 1843 F pulseaudio /dev/snd/controlC1: dank 1843 F pulseaudio BuildID: 20171115095126 Channel: Unavailable Date: Thu Nov 16 10:55:39 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 10.10.1.1 dev enp0s31f6 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.10.0.0/16 dev enp0s31f6 proto kernel scope link src 10.10.130.236 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. lxcbr0no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=57.0/20171115095126 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.6 dmi.board.name: 09WH54 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.6:bd05/26/2016:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn09WH54:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: Precision Tower 3620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1732766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
If you want to test this, force YouTube to serve H264, which your card supports judging by the vainfo results. A 4k 60fps YouTube video won't be in a codec your hardware can handle, I guess. There are 'h264ify' extensions for Chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding Status in chromium-browser package in Ubuntu: In Progress Bug description: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --Original Bug report - Libva is no longer working for snap installed chromium 72.0.3626.109 (Official Build) snap (64-bit) I followed this instruction sudo snap install --channel=candidate/vaapi chromium My amdgpu can use libva `vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM 3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1) vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointVLD VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
my computer is Lenovo Legion R7000 ，with the MSFT0001:00 04F3:3140 touchpad. and i had tested the kernel 5.9.0 rc2 on fedora 32 with no lucky, -- 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 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.product.version: Lenovo Legion 5 15ARH05 dmi.
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
I`m facing the same issues on both Ubuntu 20.04.1 and Pop Os 20.04. Intel® Core™ i3-9100T CPU @ 3.10GHz × 4 Mesa Intel® UHD Graphics 630 (CFL GT2) Gnome version 3.36.2 -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
Xenial verification
Versions we are handling:
base-files 9.4ubuntu4.12 -> 9.4ubuntu4.13
ubuntu-server 1.361.4-> 1.361.5
motd-news-config n/a -> 9.4ubuntu4.13
Note that in xenial, at the moment, ubuntu-server is not pre-installed
in the images.
This verification is quite long, given the amount of tests involved.
TL;DR All tests from (a) to (j) passed as required.
xenial verification succeeded.
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
starting point:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii base-files 9.4ubuntu4.12 amd64Debian base system miscellaneous
files
ii ubuntu-server 1.361.4 amd64The Ubuntu Server system
unmodified config:
ubuntu@xenial-motd-news-split:~$ dpkg -s base-files | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
motd-news enabled:
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-split:~$ echo $?
0
apt install base-files result:
The following NEW packages will be installed:
motd-news-config
The following packages will be upgraded:
base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
new state:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
ii base-files 9.4ubuntu4.13 amd64Debian base system
miscellaneous files
ii motd-news-config 9.4ubuntu4.13 all Configuration for motd-news
shipped in base-files
ii ubuntu-server1.361.5 amd64The Ubuntu Server system
motd-news remains enabled:
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news
--force;echo $?
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
0
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
Starting point:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii base-files 9.4ubuntu4.12 amd64Debian base system miscellaneous
files
ii ubuntu-server 1.361.4 amd64The Ubuntu Server system
Modified config file, to disable motd-news:
ubuntu@xenial-motd-news-split:~$ sudo sed -i 's,^ENABLED=.*,ENABLED=0,'
/etc/default/motd-news
ubuntu@xenial-motd-news-split:~$ dpkg -s base-files | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news
--force;echo $?
0
base-files install result:
The following NEW packages will be installed:
motd-news-config
The following packages will be upgraded:
base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.
new state:
ii base-files 9.4ubuntu4.13 amd64Debian base system
miscellaneous files
ii motd-news-config 9.4ubuntu4.13 all Configuration for motd-news
shipped in base-files
ii ubuntu-server1.361.5 amd64The Ubuntu Server system
motd-news remains disabled:
ubuntu@xenial-motd-news-split:~$ ll /etc/default/motd-news*
-rw-r--r-- 1 root root 682 Aug 25 21:15 /etc/default/motd-news
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news
--force;echo $?
0
config file moved to the motd-news-config package and the modification was
preserved:
ubuntu@xenial-motd-news-split:~$ dpkg -s motd-news-config | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f
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
initial state:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
dpkg-query: no packages found matching ubuntu-server
dpkg-query: no packages found matching motd-news-config
ii base-files 9.4ubuntu4.12 amd64
[Desktop-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 experiencing this as well Lenovo ideapad 330 jbl live400bt mic over bluetooth not working :( but fully works over cable plugged in -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
For the focal verification, I added a secondary test (j2) like I did for bionic, and that is a release upgrade from an updated focal non-server system to groovy, using the base-files package from focal-proposed, thus simulating the release upgrade once this SRU is complete. Result is correct as well. Details below. j2) do-release-upgrade from focal to groovy with the focal-proposed base-files package installed, no ubuntu-server installed, and thus motd-news-config disabled: Starting point: ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server motd-news-config | grep ^ii dpkg-query: no packages found matching motd-news-config ii base-files 11ubuntu5.2 amd64Debian base system miscellaneous files ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force ubuntu@focal-motd-news-split:~$ echo $? 0 ubuntu@focal-motd-news-split:~$ apt-cache policy base-files base-files: Installed: 11ubuntu5.2 Candidate: 11ubuntu5.2 Version table: *** 11ubuntu5.2 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages (...) Just before running do-release-upgrade, I removed focal-proposed from sources.list, to avoid upgrading other packages, not related to this test. Final state: ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server motd-news-config | grep ^ii dpkg-query: no packages found matching motd-news-config ii base-files 11ubuntu12 amd64Debian base system miscellaneous files ubuntu@focal-motd-news-split:~$ apt-cache policy base-files base-files: Installed: 11ubuntu12 Candidate: 11ubuntu12 Version table: *** 11ubuntu12 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages motd-new disabled as expected: ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force ubuntu@focal-motd-news-split:~$ echo $? 0 -- 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 ubuntu-meta package in Ubuntu: Fix Released Status in base-files 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 Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: Fix Committed Status in base-files source package in Groovy: Fix Released 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/
[Desktop-packages] [Bug 1892928] [NEW] Audio settings shows wrong icons
Public bug reported: The gnome sound settings show wrong icons https://pasteboard.co/Jo3btdG.png (here e.g. Chromium icon for Opera) In the program menu all icons are correct. (Ubuntu 20.04, Gnome 3.36.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_29_33_generic_69 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 22:34:35 2020 InstallationDate: Installed on 2019-06-22 (430 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Description changed: - The gnome sound settings shows wrong icons + The gnome sound settings show wrong icons https://pasteboard.co/Jo3btdG.png (here e.g. Chromium icon for Opera) In the program menu all icons are correct. - (Ubuntu 20.04, Gnome 3.36.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_29_33_generic_69 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 22:34:35 2020 InstallationDate: Installed on 2019-06-22 (430 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1892928 Title: Audio settings shows wrong icons Status in gnome-control-center package in Ubuntu: New Bug description: The gnome sound settings show wrong icons https://pasteboard.co/Jo3btdG.png (here e.g. Chromium icon for Opera) In the program menu all icons are correct. (Ubuntu 20.04, Gnome 3.36.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_29_33_generic_69 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 22:34:35 2020 InstallationDate: Installed on 2019-06-22 (430 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/ubuntu/+source/gnome-control-center/+bug/1892928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
Bionic verification
This verification is quite long, given the amount of tests involved.
TL;DR All tests from (a) to (j) passed as required.
bionic verification succeeded.
Latest updates from bionic:
base-files:
*** 10.1ubuntu2.9 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
and
ubuntu-server:
*** 1.417.4 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
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
Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii base-files 10.1ubuntu2.9 amd64Debian base system miscellaneous
files
ii ubuntu-server 1.417.4 amd64The Ubuntu Server system
Unmodified config:
$ dpkg -s base-files | grep /etc/default/motd-news; echo -n ' '; md5sum
/etc/default/motd-news | awk '{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
Installing base-files pulls in motd-news-config and upgrades base-files and
ubuntu-server:
ubuntu@bionic-motd-news-split:~$ sudo apt install base-files
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
motd-news-config ubuntu-server
Recommended packages:
grub-legacy-ec2
The following NEW packages will be installed:
motd-news-config
The following packages will be upgraded:
base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 14 not upgraded
motd-news remains enabled:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
* Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
sudo snap install microk8s --channel=1.19/candidate --classic
https://microk8s.io/ has docs and details.
config is now part of motd-news-config package:
ubuntu@bionic-motd-news-split:~$ dpkg -s motd-news-config | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
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
Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files ubuntu-server
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii base-files 10.1ubuntu2.9 amd64Debian base system miscellaneous
files
ii ubuntu-server 1.417.4 amd64The Ubuntu Server system
Modified config:
ubuntu@bionic-motd-news-split:~$ sudo sed -i "s,^ENABLED=.*,ENABLED=0,"
/etc/default/motd-news
ubuntu@bionic-motd-news-split:~$ dpkg -s base-files | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f
motd-news disabled with that modification:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@bionic-motd-news-split:~$ echo $?
0
Running apt install base-files also pulls in motd-news-config and upgrades
ubuntu-server:
ubuntu@bionic-motd-news-split:~$ sudo apt install base-files
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
motd-news-config ubuntu-server
Recommended packages:
grub-legacy-ec2
The following NEW packages will be installed:
motd-news-config
The following packages will be upgraded:
base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 14 not upgraded.
Config file now belongs to motd-news-config, and is still flagged as modified:
ubuntu@bionic-motd-news-split:~$ dpkg -s motd-news-config | grep
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk
'{print $2,$1}'
/etc/default/motd-news c08a329a603b640095da5ffe4e73491c
/etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f
And motd-news remains disabled because of the modification:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@bionic-motd-news-split:~$ echo $?
0
And no other config file is in /e/d:
ubuntu@bionic-motd-news-split:~$ ls -la /etc/default/motd-news*
-rw-r--r-- 1 root root 682 Aug 25 19:26 /etc/default/motd-news
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
Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files ubuntu-serv
[Desktop-packages] [Bug 1892915] [NEW] gnome-shell crashing with Wayland
Public bug reported: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1892915 Title: gnome-shell crashing with Wayland Status in gnome-shell package in Ubuntu: New Bug description: Seeing this on groovy installs after an update. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.36.4-1ubuntu2~build1 Uname: Linux 5.8.3-050803-generic x86_64 ApportVersion: 2.20.11-0ubuntu44 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 15:49:17 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-19 (311 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2 ShellJournal: -- Logs begin at Tue 2020-06-16 11:50:01 EDT, end at Tue 2020-08-25 15:49:37 EDT. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-08-10T16:14:34.416087 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- Mailing list: https://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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Error still present after update for me. Two 3840x2160 screens - one a DELL XPS 15 laptop screen which is half the physical size of my BenQ monitor. Using NVIDIA driver metapackage 440. With fractional scaling, if I set the inbuilt monitor to 150%, the EXTERNAL monitor seems to half its visible resolution, quadrupling its virtual screen size, so only the top left corner is actually displayed on the monitor. On 16.05.20 15:55, Ananya Nayan Borah wrote: > I am facing the same problem. > > Nvidia Geforce 940MX/Driver Version: 440.64 . > > I tried xrandr scaling but it just throws part of the desktop out of > the screen. I have a setup of 2 monitors one with 1920x1080 and one with > 1366x768. It would be great if we can have fractional scaling seperately > for seperate monitors because on my laptop its really small and its huge > on the monitor. I tried the workaround provided by @Kristo it works to > an extent but doesn't really solve everything; still its better to have > something than nothing. I am new to ubuntu, could someone help me if > there is any way to manipulate icon size seperately for different > monitors? > -- 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 1892910] [NEW] all passwords disappeared with update to 84.0.4147.105
Public bug reported: Running Linux mint Sylvia 64 bit; updated chromium 08-24-20 with update manager. Discovered today (8-25-20) all (previously saved) passwords have disappeared since update. Other settings/stored information appear unaffected - ONLY passwords disappeared. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1892910 Title: all passwords disappeared with update to 84.0.4147.105 Status in chromium-browser package in Ubuntu: New Bug description: Running Linux mint Sylvia 64 bit; updated chromium 08-24-20 with update manager. Discovered today (8-25-20) all (previously saved) passwords have disappeared since update. Other settings/stored information appear unaffected - ONLY passwords disappeared. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
Focal verification This verification is quite long, given the amount of tests involved. TL;DR All tests from (a) to (j) passed as required. focal verification succeeded. Details below. 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 Starting with: ii base-files 11ubuntu5.1 amd64Debian base system miscellaneous files ii ubuntu-server 1.450.1 amd64The Ubuntu Server system With proposed enabled, an apt install base-files pulls in motd-news-config and upgrades ubuntu-server: $ sudo apt install base-files Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: motd-news-config ubuntu-server The following NEW packages will be installed: motd-news-config The following packages will be upgraded: base-files ubuntu-server (...) And motd-news remains enabled: ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with sudo snap install microk8s --channel=1.19/candidate --classic https://microk8s.io/ has docs and details. ubuntu@focal-motd-news-split:~$ apt-cache policy base-files ubuntu-server motd-news-config base-files: Installed: 11ubuntu5.2 Candidate: 11ubuntu5.2 Version table: *** 11ubuntu5.2 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages (...) ubuntu-server: Installed: 1.450.2 Candidate: 1.450.2 Version table: *** 1.450.2 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status (...) motd-news-config: Installed: 11ubuntu5.2 Candidate: 11ubuntu5.2 Version table: *** 11ubuntu5.2 500 500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 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 First, change /e/d/motd-news to disable the service: ubuntu@focal-motd-news-split:~$ sudo sed -i 's,^ENABLED=.*,ENABLED=0,' /etc/default/motd-news ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force ubuntu@focal-motd-news-split:~$ Confirm installed packages: ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server motd-news-config | grep ^i dpkg-query: no packages found matching motd-news-config ii base-files 11ubuntu5.1 amd64Debian base system miscellaneous files ii ubuntu-server 1.450.1 amd64The Ubuntu Server system Install base-files, which upgrades ubuntu-server, base-files, and installs the new motd-news-config package: ubuntu@focal-motd-news-split:~$ sudo apt install base-files Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: motd-news-config ubuntu-server The following NEW packages will be installed: motd-news-config The following packages will be upgraded: base-files ubuntu-server 2 upgraded, 1 newly installed, 0 to remove and 15 not upgraded. And confirm motd-news remains disabled (which was the modification done): ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force ubuntu@focal-motd-news-split:~$ 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 Starting from: - unmodified config: ubuntu@focal-motd-news-split:~$ dpkg -s base-files | grep /etc/default/motd-news ; md5sum /etc/default/motd-news /etc/default/motd-news c08a329a603b640095da5ffe4e73491c c08a329a603b640095da5ffe4e73491c /etc/default/motd-news - ubuntu-server removed: ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server motd-news-config | grep ^i dpkg-query: no packages found matching ubuntu-server dpkg-query: no packages found matching motd-news-config ii base-files 11ubuntu5.1 amd64Debian base system miscellaneous files apt install base-files upgrades just base-files, and /e/d/motd-news is removed, resulting in a disabled motd-news: $ sudo apt install base-files ... The following packages will be upgraded: base-files 1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded. ... ubuntu@focal-motd-news-split:~$ ls -la /etc/default/motd-news ls: cannot access '/etc/default/motd-news': No such file or directory ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force ubuntu@focal-motd-news-split:~$ 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 Star
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
This is fixed in groovy already. ** Changed in: ubuntu-meta (Ubuntu Groovy) Status: In Progress => Fix Released -- 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 ubuntu-meta package in Ubuntu: Fix Released Status in base-files 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 Committed Status in ubuntu-meta source package in Bionic: Fix Committed Status in base-files source package in Focal: Fix Committed Status in ubuntu-meta source package in Focal: Fix Committed Status in base-files source package in Groovy: Fix Released 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 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) [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 default is ENABLED=1. Thus, a system that had motd-news disabled via removing the config file would now have it re-enabled after the upgrade. This was trickier to handle, and we d
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Thanks Helmut and Francesco I have a (bold ?) question. As previously reported, it works (at least, moves and clicks as expected, not talking gestures here) in the UEFI BIOS prior to the loading of any operating system. Does this mean there is a kind of working driver in code of the UEFI BIOS ? If yes, any hope to get it from Lenovo or other vendors ? -- 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 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:cvnLEN
[Desktop-packages] [Bug 1889106] Re: [SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-browser due to a higher version than the transitional deb in 20.04
This bug was fixed in the package chromium-browser -
84.0.4147.105-0ubuntu0.20.04.1
---
chromium-browser (84.0.4147.105-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release: 84.0.4147.105 (LP: #1889106)
-- Olivier Tilloy Fri, 07 Aug 2020
15:49:00 +0200
** Changed in: chromium-browser (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1889106
Title:
[SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
browser due to a higher version than the transitional deb in 20.04
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Focal:
Fix Released
Bug description:
This bug is another manifestation of bug #1858500, but with a different
upgrade path.
bionic-{security,updates} will soon have chromium-browser
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and
when that happens the version number in focal will be lower, meaning that
chromium-browser won't be updated to the new package that installs the snap for
a user upgrading from 18.04 to 20.04.
Since chromium-browser in 20.04 is a mostly empty transitional package
that installs the chromium snap, all that's needed to fix this is to
bump its version number.
[Impact]
Users upgrading from 18.04 to 20.04 will not get the latest chromium snap
replacing the chromium-browser deb package as intended.
This is because the version number in 18.04 is (will soon be) greater than
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.
[Test Case]
* Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in
bionic-{security,updates}
* On a machine running 18.04, ensure that the chromium snap is *not*
installed, then install the chromium-browser deb package: sudo apt install
chromium-browser
* Upgrade that machine to Ubuntu 20.04
* When upgrading, the chromium-browser package becomes a transitional
package that installs the chromium snap
* Verify that the chromium snap is installed
[Regression Potential]
* The chromium snap has some known shortcomings and regressions
compared to the deb package, they are being tracked at
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
snap is the desired behaviour though.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1889106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889106] Update Released
The verification of the Stable Release Update for chromium-browser 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1889106
Title:
[SRU] Upgrading from 18.04 to 20.04 will keep the 18.04 chromium-
browser due to a higher version than the transitional deb in 20.04
Status in chromium-browser package in Ubuntu:
Fix Released
Status in chromium-browser source package in Focal:
Fix Released
Bug description:
This bug is another manifestation of bug #1858500, but with a different
upgrade path.
bionic-{security,updates} will soon have chromium-browser
84.0.4147.89-0ubuntu0.18.04.2 (pending sponsoring by the security team), and
when that happens the version number in focal will be lower, meaning that
chromium-browser won't be updated to the new package that installs the snap for
a user upgrading from 18.04 to 20.04.
Since chromium-browser in 20.04 is a mostly empty transitional package
that installs the chromium snap, all that's needed to fix this is to
bump its version number.
[Impact]
Users upgrading from 18.04 to 20.04 will not get the latest chromium snap
replacing the chromium-browser deb package as intended.
This is because the version number in 18.04 is (will soon be) greater than
the version in 20.04. Bumping the version number in 20.04 is enough to fix this.
[Test Case]
* Ensure that chromium-browser 84.0.4147.89-0ubuntu0.18.04.2 is available in
bionic-{security,updates}
* On a machine running 18.04, ensure that the chromium snap is *not*
installed, then install the chromium-browser deb package: sudo apt install
chromium-browser
* Upgrade that machine to Ubuntu 20.04
* When upgrading, the chromium-browser package becomes a transitional
package that installs the chromium snap
* Verify that the chromium snap is installed
[Regression Potential]
* The chromium snap has some known shortcomings and regressions
compared to the deb package, they are being tracked at
https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bugs?field.tag=snap. Auto-upgrading users from the deb to the
snap is the desired behaviour though.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1889106/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883819] Update Released
The verification of the Stable Release Update for simple-scan 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 simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1883819 Title: Update to 3.36.3 Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Focal: Fix Released Bug description: [ Description ] GNOME upstream have released a new stable version of simple-scan. Overview of changes in simple-scan 3.36.3 * Change the size of the paper to avoid visual glitches. * Disable possibility of scanning if no device is found, to avoid unnecessary errors. Overview of changes in simple-scan 3.36.2.1 * Revert the higher bit depth text scans changes - they aren't working with PDF saving. Overview of changes in simple-scan 3.36.2 * Use higher bit depth on text scans. * Fix size of first page on second scan. * Don't interrupt scanning if the device is busy. * Support saving files to FUSE file systems. * Update known USB scanner IDs. * Add initial Lexmark printers support. * Add ADF duplex support for Brother DS-720. * Fix setting source for Epson scanner. Overview of changes in simple-scan 3.36.1 * Stop disabling compression to fix slow scanning [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could break existing functionality. Issue would be confined to simple-scan app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883819] Re: Update to 3.36.3
This bug was fixed in the package simple-scan - 3.36.3-0ubuntu0.20.04.0 --- simple-scan (3.36.3-0ubuntu0.20.04.0) focal; urgency=medium * New upstream release (LP: #1883819) -- Robert Ancell Wed, 17 Jun 2020 15:46:35 +1200 ** Changed in: simple-scan (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1883819 Title: Update to 3.36.3 Status in simple-scan package in Ubuntu: Fix Released Status in simple-scan source package in Focal: Fix Released Bug description: [ Description ] GNOME upstream have released a new stable version of simple-scan. Overview of changes in simple-scan 3.36.3 * Change the size of the paper to avoid visual glitches. * Disable possibility of scanning if no device is found, to avoid unnecessary errors. Overview of changes in simple-scan 3.36.2.1 * Revert the higher bit depth text scans changes - they aren't working with PDF saving. Overview of changes in simple-scan 3.36.2 * Use higher bit depth on text scans. * Fix size of first page on second scan. * Don't interrupt scanning if the device is busy. * Support saving files to FUSE file systems. * Update known USB scanner IDs. * Add initial Lexmark printers support. * Add ADF duplex support for Brother DS-720. * Fix setting source for Epson scanner. Overview of changes in simple-scan 3.36.1 * Stop disabling compression to fix slow scanning [ QA ] GNOME has a micro release exception that covers this package. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME So we don't need to verify the fixes explicitly. [ Regression Potential ] Changes could break existing functionality. Issue would be confined to simple-scan app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1883819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892897] [NEW] Cannot access a Samba file share anymore due to "Failed to retrieve file list from server"
Public bug reported: This is a regression bug as I have no problems with another laptop running Ubuntu 18.04 LTS. Trying to access Samba file share on my Synology Diskstation (smb://diskstation.local) gives me just "Failed to retrieve file list from server: Software caused connection abort". See the attached screenshot of the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:34:44 2020 InstallationDate: Installed on 2016-09-13 (1442 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-19 (98 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression ** Attachment added: "Screenshot of the problem" https://bugs.launchpad.net/bugs/1892897/+attachment/5404481/+files/NautilusSambaBug.png ** Tags added: regression -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892897 Title: Cannot access a Samba file share anymore due to "Failed to retrieve file list from server" Status in nautilus package in Ubuntu: New Bug description: This is a regression bug as I have no problems with another laptop running Ubuntu 18.04 LTS. Trying to access Samba file share on my Synology Diskstation (smb://diskstation.local) gives me just "Failed to retrieve file list from server: Software caused connection abort". See the attached screenshot of the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:34:44 2020 InstallationDate: Installed on 2016-09-13 (1442 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-19 (98 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892898] [NEW] screen goes down automatic
Public bug reported: screen goes down automatic updating will not solve it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Tue Aug 25 23:03:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1774 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu May 28 11:49:11 2020 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892898 Title: screen goes down automatic Status in xorg package in Ubuntu: New Bug description: screen goes down automatic updating will not solve it ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18 Uname: Linux 4.15.0-114-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Tue Aug 25 23:03:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1] InstallationDate: Installed on 2015-10-17 (1774 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Hewlett-Packard HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.0B dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C1 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.11 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
Same issue on Ubuntu Mate 20.04 with Radeon RX 5600 XT with stock driver and also with driver version 20.30 (from AMD). Affected : - single DP>VGA monitor - single HDMI>HDMI TV - dual screens DP>VGA monitor with HDMI>HDMI TV Another workaround : no issue if set to marco with GPU compositor compton: `marco-compton` If upgraded from 18.04 to 20.04 compton is still installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in Linux: Unknown Status in libxcb package in Ubuntu: Confirmed Status in xfwm4 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E495 dmi.product.name: 20NECTO1WW dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495 dmi.product.version: ThinkPad E495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1873895/+subscriptions -- Mailing list: https://laun
[Desktop-packages] [Bug 1892440] Re: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
I should add, I don't have an NVIDIA card - intel integrated HD graphics. As it stands, GNOME is a mess with differential scaling everywhere some parts are smaller, some are larger (notably the menu bar). -- 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: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: 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:GNOME DistroRelease: 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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
HSP/HFP does not work on Ubuntu 20.04 with Sony WI-1000X. A2DP does work (output) but as soon as I switch to HSP/HFP then I loose bluetooth audio (input and output). Ran Ubuntu 18.04 from a live USB and HSP/HFP did work so something has changed between 18.04 and 20.04. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
** Summary changed: - [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards + [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards -- 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: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: 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:GNOME DistroRelease: 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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Right, it affects all MSFT touchpads. At the moment there is nothing for MSFT - we will have to be very patient and hope, that someone can find a driver for it. -- 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 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.product.version: Lenovo Legio
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Also struggling since the latest mutter and/or gnome-shell update (3.36.4). Font scaling is mismatched throughout the entire GUI. It's larger than normal in the menu-bar, while it's smaller/squished in terminal. This makes it difficult to fix. If I scale down to 0.9 to fix the menu bar, text elsewhere is simply too small. -- 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: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: 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:GNOME DistroRelease: 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: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
It affects Intel integrated GPUs too. You can downgrade libmutter package temporarily as a workaround: sudo apt install libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3 sudo apt-mark hold libmutter-6-0 Remember to unhold after fix comes out! -- 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: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards Status in mutter package in Ubuntu: Confirmed Bug description: 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:GNOME DistroRelease: 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 1892841] Re: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: sane-backends (Ubuntu) Importance: Undecided => Low ** Changed in: sane-backends (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1892841 Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error Status in sane-backends package in Ubuntu: Invalid Bug description: thats all ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: libsane:amd64: Install libsane-common:amd64: Install sane-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 12:14:22 2020 DpkgTerminalLog: Preparing to unpack .../libsane_1.0.29-0ubuntu5.1_amd64.deb ... Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error DuplicateSignature: package:libsane:1.0.29-0ubuntu5 Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error InstallationDate: Installed on 2020-08-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: sane-backends Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1892841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866732] Re: [snap] Unable to add policies
The following two commits are an attempt at fixing this: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=bfe4c3bf4e082ca6329040db23bdee858bd204d2 https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6c9bd6a725fc7b7d560cc20ac9cee1c7cf84cadf ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1866732 Title: [snap] Unable to add policies Status in chromium-browser package in Ubuntu: Fix Committed Bug description: When using the Chromium snap, the policies located in the directory /etc/chromium-browser/policies/managed/ are no longer being read. The consequence is that the policies are not applied. This is particularly problematic on, for example, public computers, where browsing history and passwords may be saved, or on school computers, where the dinosaur game will be easily available. Is there another way I'm unaware of to add system-wide policies when using the Chromium snap? If not, would it be possible to make the snap read the settings in the /etc/chromium-browser/policies/managed/ directory? This would make the transition from deb to snap easier on systems which are already configured with system-wide policies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
The following two commits are an attempt at fixing this: https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=bfe4c3bf4e082ca6329040db23bdee858bd204d2 https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source/commit/?id=6c9bd6a725fc7b7d560cc20ac9cee1c7cf84cadf ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: Fix Committed Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1714244] Re: [snap] apparmor denials on /etc/chromium-browser/policies/
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1714244 Title: [snap] apparmor denials on /etc/chromium-browser/policies/ Status in chromium-browser package in Ubuntu: In Progress Bug description: [1565519.440403] audit: type=1400 audit(1504185084.568:68574811): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/managed/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [1565519.440527] audit: type=1400 audit(1504185084.568:68574812): apparmor="ALLOWED" operation="open" profile="snap.chromium.chromium" name="/etc/chromium-browser/policies/recommended/" pid=19433 comm ="chromium-browse" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Those denials don't appear to prevent the app from running. Still, they should be investigated and fixed if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1714244/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866732] Re: [snap] Unable to add policies
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1866732 Title: [snap] Unable to add policies Status in chromium-browser package in Ubuntu: In Progress Bug description: When using the Chromium snap, the policies located in the directory /etc/chromium-browser/policies/managed/ are no longer being read. The consequence is that the policies are not applied. This is particularly problematic on, for example, public computers, where browsing history and passwords may be saved, or on school computers, where the dinosaur game will be easily available. Is there another way I'm unaware of to add system-wide policies when using the Chromium snap? If not, would it be possible to make the snap read the settings in the /etc/chromium-browser/policies/managed/ directory? This would make the transition from deb to snap easier on systems which are already configured with system-wide policies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888942] Re: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click
Launchpad has imported 8 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1653191. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2020-07-16T08:09:28+00:00 Github-tbart wrote: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Steps to reproduce: Using Firefox 78.0.2 on Linux/X11: 1. Visit a URL by entering it into the location bar and pressing return 2. Click into the location bar once or press Ctrl+L; the URL gets highlighted 3. Middle click into any text area (inside firefox or some other window/application) Actual results: URL does not get pasted. Expected results: URL should be in PRIMARY as soon as it gets highlighted and be able to be pasted somewhere else. This bug has been introduced only shortly before my current 78.0.2 as I regularly use this procedure to paste URLs into mails and constantly end up not pasting what I want. I don't know how others feel, but I miss the triple-click to select which is the standard in any other application (or even within text areas inside firefox)! This is a real break in usability standards. With the current way of automatic full selection of the URL by the first click, I also cannot select parts of the URL (which I have to do all the time because of unnecessary sessionid, tracking and whatnot parameters in today's urls) without clicking a second time, which is also completely uncommon to any selectable text. clipboard.autocopy is set (untouched). The description of http://kb.mozillazine.org/Clipboard.autocopy is also wrong now with the current behavior. If this is a feature and not a bug, please make it configurable (and I'd suggest to make the standard of a whole desktop environment the standard and not this way that breaks the standard). If you do not agree please at least make it configurable and leave the "feature" the standard. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888942/comments/0 On 2020-07-16T08:17:47+00:00 Release-mgmt-account-bot wrote: [Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should belong to this component, but please revert this change in case of error. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888942/comments/1 On 2020-07-21T08:36:58+00:00 Mak-g wrote: For how much it may look confusing (it is definitely a shift in behavior and habits), this is the expected behavior currently. Clicking on the urlbar focuses and selects its contents, but because the selection is programmatic we don't override the primary selection, that is because maybe you are selecting the urlbar to paste something, and we don't want to overwrite that. triple-click should work correctly if you start from an unfocused urlbar (please let us know otherwise), or it's bug 1633203 (allow to re-select). Would fixing that bug help? You can also drag select starting from the unfocused urlbar. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888942/comments/2 On 2020-08-04T10:06:05+00:00 Github-tbart wrote: Using 79.0 now things have improved a lot. Triple clicking works again, partial selection of URLs also works again. Ctrl-A still does not work, Ctrl-L also does not work. Still, (and the linked bug also shows other people feel like this) I think breaking a well established behavior that is common across thousands of other applications is a regression. The intended functionality (at least I think that has been the motivation behind this change) of only having to click once into the location bar and being able to type a new URL would not be hindered by adhering to the established standard of copying selected text into PRIMARY. You mention you don't want to override possibly existing clipboard contents. I don't think anyone uses the PRIMARY to paste URLs into address bars (or has done so before) as it involves/involved selecting (parts of) the URL anyway. That's what CLIPBOARD is for. (And no, I am not asking for overwriting the CLIPBOARD contents upon selection!) Apart from that, I'd rather introduce a new button/shortcut/etc for a new functionality (clear and focus) instead of breaking standards Input from a few other users would help, I think. Reply at: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888942/comments/8 On 2020-08-04T12:11:39+00:00 Release-mgmt-account-bot wrote: The severity field is not set for this bug. :adw, could you have a look please?
[Desktop-packages] [Bug 1892888] [NEW] problem renaming multiple files
Public bug reported: When using nautilus renaming multiple files file-001, file-002, ..., file-009 to file-009, file-008, ..., file-001, the program is not responding and take up more and more memory (up to 2GB). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 23:30:32 2020 InstallationDate: Installed on 2020-03-14 (164 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-09 (108 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892888 Title: problem renaming multiple files Status in nautilus package in Ubuntu: New Bug description: When using nautilus renaming multiple files file-001, file-002, ..., file-009 to file-009, file-008, ..., file-001, the program is not responding and take up more and more memory (up to 2GB). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 23:30:32 2020 InstallationDate: Installed on 2020-03-14 (164 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-09 (108 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866732] Re: [snap] Unable to add policies
** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1866732 Title: [snap] Unable to add policies Status in chromium-browser package in Ubuntu: Confirmed Bug description: When using the Chromium snap, the policies located in the directory /etc/chromium-browser/policies/managed/ are no longer being read. The consequence is that the policies are not applied. This is particularly problematic on, for example, public computers, where browsing history and passwords may be saved, or on school computers, where the dinosaur game will be easily available. Is there another way I'm unaware of to add system-wide policies when using the Chromium snap? If not, would it be possible to make the snap read the settings in the /etc/chromium-browser/policies/managed/ directory? This would make the transition from deb to snap easier on systems which are already configured with system-wide policies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1866732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892373] Re: Firefox crashes on logout
I cannot reproduce the problem is a stock GNOME session (neither by logging out nor by abruptly killing the firefox process). I wonder whether this is XFCE-specific? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1892373 Title: Firefox crashes on logout Status in firefox package in Ubuntu: New Bug description: Every time I logout or shutdown the system with firefox open, it will generate a crash report in about:crashes. However, there is no crash dump in /var/crash. I noticed this before I upgraded from 18.04 LTS recently, and at first I thought the crash went away after the upgrade, but sadly it's not the case. I've tested with a fresh new user, with the same result. I'm running Xubuntu 20.04.1 LTS. This may be the same bug as bug #73536 ( Mozilla Bugzilla #336193), but I can't be sure. To reproduce: Open firefox. Logout with firefox window open. login again and check "about:crashes" in firefox. The output of: lsb_release -a; uname -a; apt-cache policy firefox No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal Linux celia 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux firefox: Installed: 79.0+build1-0ubuntu0.20.04.1 Candidate: 79.0+build1-0ubuntu0.20.04.1 Version table: *** 79.0+build1-0ubuntu0.20.04.1 500 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-updates/main amd64 Packages 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 75.0+build3-0ubuntu1 500 500 http://mirror.csclub.uwaterloo.ca/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892373/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Still doesn't work for me after all updates :( GPU: GeForce MX 250 Command output: libmutter-6-0: Installed: 3.36.4-0ubuntu0.20.04.2 Candidate: 3.36.4-0ubuntu0.20.04.2 Version table: *** 3.36.4-0ubuntu0.20.04.2 500 500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages -- 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 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium
Indeed, deleting the ~/snap folder isn't a reasonable use case, it will break much more than just window tracking (for starters it will remove your entire chromium profile, including bookmarks and navigation history, which you most likely don't want). That said, I can't seem to reproduce the bug. After deleting the ~/snap folder and restarting chromium, the window is mapped to the launcher icon as expected. What is the output of the following command on your system? gsettings get org.gnome.shell favorite-apps ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1892146 Title: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: Deleting the ~/snaps folder in ubuntu seems to permanently break gnome dash window tracking. Steps to reproduce: 1) Add chromium-browser.desktop to your dash / dock favourites. Chromium Windows get attributed to this favourite when created. 2) Delete the ~/snaps folder, quit all chromium processes and / or reboot 3) The ~/snaps folder gets recreated, but Chromium windows now get attributed to a new chromium-browser dash icon, ignoring the favourite created in step 1 I know I know, don't delete the ~/snaps folder then! Unfortunately, there are situations when this is beyond my control. These desktops are gonna get into the hands of normal users, like my dad and my colleagues. They will delete the folder by accident or because they don't know and don't care about snaps. Deleting it shouldn't permanently break window tracking. This is on a fully patched 20.04 system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently forgot setting that in my email. the last systemd upload should fix everything except for the livecd-rootfs revert that made fstab in lxd images invalide [16:45] rbalint: " the last systemd upload" means groovy I guess, what about focal? [16:47] cpaelzer, sru-s are usually prepared by ddstreet, but i guess you mean the flakiness [16:49] cpaelzer, as i look at the last runs the latest focal systemd upload got flakier without a change in systemd so it may be an infra issue or needs more investigation [16:50] rbalint: do you want a new bug about it for you and ddstreet then? [16:50] to focus the discussion in one place I mean [16:50] cpaelzer, LP: #1892358 is not open against focal so i think just adding focal would be enough Task added ** Also affects: iputils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: glib2.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: kbd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ntpsec (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: qemu (Ubuntu Focal) ** No longer affects: kbd (Ubuntu Focal) ** No longer affects: ntpsec (Ubuntu Focal) ** No longer affects: glib2.0 (Ubuntu Focal) ** No longer affects: iputils (Ubuntu Focal) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in glib2.0 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in ntpsec package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in systemd source package in Focal: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/)
[Desktop-packages] [Bug 1888942] Re: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click
** Bug watch added: Mozilla Bugzilla #1653191 https://bugzilla.mozilla.org/show_bug.cgi?id=1653191 ** Changed in: firefox Status: Invalid => Unknown ** Changed in: firefox Remote watch: Mozilla Bugzilla #1656045 => Mozilla Bugzilla #1653191 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1888942 Title: marked url in firefox by using one click isn't copied to clipboard, only with a triple mouse-click Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Incomplete Bug description: Hi, if I click in an url in firefox, the whole url ist marked, i.e. highlighted. If I now use a click on the mousewheel to paste the content of the clipboard into another software, I discover that the url wasn't copied into the clipboard - the previous content ist filled in. That's confusing to me. I would expect: If I can mark an url in Firefox with a single mouse-click, which looks like a marking with a triple click, then it should be copied also in the clipboard. That would be a consisting behavior. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 78.0.2+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matthias 1453 F pulseaudio /dev/snd/controlC1: matthias 1453 F pulseaudio /dev/snd/pcmC1D0c: matthias 1453 F...m pulseaudio /dev/snd/pcmC1D0p: matthias 1453 F...m pulseaudio BuildID: 20200708170202 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 25 16:44:27 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/firefox ForcedLayersAccel: False InstallationDate: Installed on 2020-04-24 (92 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.11.1 dev wlp4s0 proto dhcp metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.11.0/24 dev wlp4s0 proto kernel scope link src 192.168.11.66 metric 600 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:730 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=74.0.1/20200403064753 (Out of date) Profile0 (Default) - LastVersion=78.0.2/20200708170202 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET53W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS06G0J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: R90GJVAH dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET53W(1.31):bd11/12/2019:svnLENOVO:pn20BTS06G0J:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS06G0J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BTS06G0J dmi.product.sku: LENOVO_MT_20BT_BU_Think_FM_ThinkPad X1 Carbon 3rd dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1888942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Seems like everyone having a AMD GPU is the common denominator. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892841] Re: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1892841 Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error Status in sane-backends package in Ubuntu: New Bug description: thats all ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: libsane:amd64: Install libsane-common:amd64: Install sane-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 12:14:22 2020 DpkgTerminalLog: Preparing to unpack .../libsane_1.0.29-0ubuntu5.1_amd64.deb ... Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error DuplicateSignature: package:libsane:1.0.29-0ubuntu5 Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error InstallationDate: Installed on 2020-08-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: sane-backends Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1892841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
Just to confirm my monitor is set to 100% scaling and I still get the duplicate cursor after wake from sleep. 20.04.1 here with latest updates still has the issue. -- 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/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: Expected: After my computer had gone to sleep and I log in I should see only a single active mouse cursor. What happened instead: After my computer had gone to sleep and I logged in I noticed a second frozen/stuck mouse cursor was on screen and was rendered in one place over any active application windows. I recently upgraded to 20.04 from 19.10 but the same issue was occurring in 19.10 as well. Logging out completely then logging back in again removed the extra frozen cursor. lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 apt-cache policy mutter mutter: Installed: 3.36.1-3ubuntu3 Candidate: 3.36.1-3ubuntu3 Version table: *** 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 19:53:03 2020 InstallationDate: Installed on 2019-03-09 (415 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890939] Re: [snap] The SUID sandbox helper binary was found, but is not configured correctly.
That's suspicious, can you please share the output of `ls -l /snap/chromium/current/usr/lib/chromium-browser/chrome-sandbox` ? Is the latest update (revision 1269) similarly affected? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1890939 Title: [snap] The SUID sandbox helper binary was found, but is not configured correctly. Status in chromium-browser package in Ubuntu: Incomplete Bug description: The chromium snap version 1260 has the wrong mode for chrome-sandbox, as it happened also in bug #1854091: ``` $ /snap/bin/chromium [4009:4009:0809/115259.781182:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /snap/chromium/1260/usr/lib/chromium-browser/chrome-sandbox is owned by root and has mode 4755. Trace/breakpoint trap $ [4134:4134:0100/00.834554:ERROR:zygote_linux.cc(653)] write: Broken pipe (32) ``` I have reverted it to the previous version (1244) and this one works (and has the right mode for chromium-sandbox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892841] Re: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1892841 Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error Status in sane-backends package in Ubuntu: New Bug description: thats all ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: libsane:amd64: Install libsane-common:amd64: Install sane-utils:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 25 12:14:22 2020 DpkgTerminalLog: Preparing to unpack .../libsane_1.0.29-0ubuntu5.1_amd64.deb ... Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error DuplicateSignature: package:libsane:1.0.29-0ubuntu5 Unpacking libsane:amd64 (1.0.29-0ubuntu5.1) over (1.0.29-0ubuntu5) ... dpkg: error processing archive /var/cache/apt/archives/libsane_1.0.29-0ubuntu5.1_amd64.deb (--unpack): unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error ErrorMessage: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error InstallationDate: Installed on 2020-08-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) 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: sane-backends Title: package libsane 1.0.29-0ubuntu5 failed to install/upgrade: unable to stat './usr/share/doc/libsane' (which I was about to install): Input/output error UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1892841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1891649] Re: [snap] Gnome dash window tracking is broken when using chromium snap
** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Summary changed: - [snap] Gnome dash window tracking is broken when using chromium snap + [snap] No separate icon/window tracking for app launchers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1891649 Title: [snap] No separate icon/window tracking for app launchers Status in chromium-browser package in Ubuntu: Confirmed Bug description: I've created a custom chromium launcher for an internal website, starting chromium in --app mode. The launcher should get it's own Gnome dash icon. To match the created windows to the dash icon, I've taken the following measures: - include "StartupWMClass=myfoo" in the myfoo.desktop file - gave chromium the "--class=myfoo" parameter to make it set it's WM_CLASS to myfoo I've verified the WM_CLASS to be properly set to myfoo using xprop. However, this does not work when chromium is launched via snap. All windows get attributed to the chromium dash icon no matter what their WM_CLASS is. Bypassing snap and launching chromium via /snap/chromium/current/usr/lib/chromium-browser/chrome fixes the problem. Here are the full chromium exec lines: Broken: Exec=chromium --class=myfoo --no-first-run --app=https://internal.example.com/ Working: Exec=/snap/chromium/current/usr/lib/chromium-browser/chrome --class=myfoo --no-first-run --app=https://internal.example.com/ This is on a fully patched 20.04 system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1891649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's comment's about what his plan is after his revert. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in glib2.0 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in ntpsec package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/) ...F.FB.F.F.F..FFF.F root-unittests (F 12% S 0% B 2% => P 85%/) ..B.F...F.FF...F (I'm sure LP will make this unreadable, but is is nice in monospace) Whatever the root cause is - the success rate of these has reduced so much that the (even formerly questionable) practice of retry-until- success won't work anymore. I have run the two tests in a local VM and systemd-fsckd works there while tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services". We had the discussion in the past, but I think I need to again bring up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until they are on reasonable success rates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1892358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
When you do report it upstream, please share the link to the upstream bug report here. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Confirmed Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
