[Desktop-packages] [Bug 1892814] [NEW] pulseaudio very unstable
Public bug reported: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. Microphones randomly stop working until changing the active microphone multiple times. Today my mic stopped working 3 times. Sometimes cannot switch bluetooth headset profiles. Or it says that it switched it but when you click on a different tab and go back, it reverts to the old setting. I see some warnings/errors in the logs that could be related: gsd-media-keys[2948]: Unable to get default sink gsd-media-keys[2948]: Unable to get default source kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65 pulseaudio[2489]: q overrun, queuing locally please see the attached log. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal log" https://bugs.launchpad.net/bugs/1892814/+attachment/5404270/+files/journal_log_08252020.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1892814 Title: pulseaudio very unstable Status in gnome-settings-daemon package in Ubuntu: New Bug description: Pulseaudio has been super unstable since ubuntu 20.04. bluetooth has multiple connectivity issues which sometimes can only be resolved by unpairing and then pairing again. Microphones randomly stop working until changing the active microphone multiple times. Today my mic stopped working 3 times. Sometimes cannot switch bluetooth headset profiles. Or it says that it switched it but when you click on a different tab and go back, it reverts to the old setting. I see some warnings/errors in the logs that could be related: gsd-media-keys[2948]: Unable to get default sink gsd-media-keys[2948]: Unable to get default source kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65 pulseaudio[2489]: q overrun, queuing locally please see the attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1892814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882453] Re: [nvidia] GUI blanks after long period of use
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882453 Title: [nvidia] GUI blanks after long period of use Status in gnome-shell package in Ubuntu: Expired Bug description: GUI screen goes blank with a right click on the desktop or a click on the power button. The entire systems seems to slow too, with CPU utilization reaching 100% at a consistent interval. This has happened twice already after a long period of idle or when conducting many actions with several applications. Not sure if any of it is causation given its only happened twice and I can't replicate the problem consistently. If you need further information reach me at clmora...@pm.me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-34.38-generic 5.4.41 Uname: Linux 5.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06: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: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 7 15:00:40 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM204 [GeForce GTX 970] [3842:2974] InstallationDate: Installed on 2020-05-20 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7885 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=40367ef8-089b-4ef9-9b43-d538f9b52b3d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7885 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1882453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1885067] Re: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置
[Expired for emacs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: emacs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs in Ubuntu. https://bugs.launchpad.net/bugs/1885067 Title: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 Status in emacs package in Ubuntu: Expired Bug description: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: emacs 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libcurl4-gnutls-dev:amd64: Install libcurl3-gnutls:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jun 25 06:16:38 2020 ErrorMessage: 依赖关系问题 - 仍未被配置 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: emacs Title: package emacs 1:26.3+1-1ubuntu2 failed to install/upgrade: 依赖关系问题 - 仍未被配置 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1885067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892746] Re: Ubuntu doesn't use Bluetooth headset when connected automatically
*** This bug is a duplicate of bug 1866194 *** https://bugs.launchpad.net/bugs/1866194 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 1866194, 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 1866194 External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1892746 Title: Ubuntu doesn't use Bluetooth headset when connected automatically Status in bluez package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I do not recommend that as a solution. The open source 'nouveau' driver generally causes more problems than it solves. And performance is significantly lower than the proprietary driver. -- 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 1892746] Re: Ubuntu doesn't use Bluetooth headset when connected automatically
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1892746 Title: Ubuntu doesn't use Bluetooth headset when connected automatically Status in bluez package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1892746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
^^^ Daniel, I wrote that answer mostly for the bug you mentioned, but as I mentioned in my answer, it fixes the corrupted background bug as well. -- 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 1892746] [NEW] Ubuntu doesn't use Bluetooth headset when connected automatically
You have been subscribed to a public bug: When I turn on my Bluetooth headset, Ubuntu connects to it automatically and my headset says "Connected!". But the audio still comes out of my PC's main speakers. I have to disconnect my headset in Bluetooth settings and re-connect it for the audio to go to it. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu doesn't use Bluetooth headset when connected automatically https://bugs.launchpad.net/bugs/1892746 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez 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 1892296] Re: gnome-control-center cannot change resolution of external monitor
This reminds me of bug 1890772. Try this: xrandr --output HDMI-1 --set "max bpc" 8 -- 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: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1717458] Re: Panel flickers when scrubbing across in-window menus
Fix released, at some point before focal... ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717458 Title: Panel flickers when scrubbing across in-window menus Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Gnome panel flickers when scrubbing across old-style in-window menus, such as those in Terminal or AisleRiot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Fri Sep 15 15:48:41 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) 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/1717458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404256/+files/journal.txt -- 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: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1892296] Re: gnome-control-center cannot change resolution of external monitor
** Attachment added: "xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404255/+files/xrandr.txt -- 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: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1892296] Re: gnome-control-center cannot change resolution of external monitor
It doesn't work in Wayland, either. ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404254/+files/lspci.txt -- 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: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1798166] Re: “Mouse battery low” notification can't be disabled
N, please don't mark this as invalid. This is the most annoying notification on my wonderful Gnome desktop. It is so premature. First off, it thinks my MX Logitech keyboard is a mouse and secondly, it displays over and over long before the keyboard needs to be charged. I use this keyboard with 2 other operating systems and none of them have this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862308] Re: Desktop wallpaper is slightly blurry
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3087 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3087 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3087 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Milestone: ubuntu-20.04.1 => None -- 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/1862308 Title: Desktop wallpaper is slightly blurry Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: Desktop wallpaper is slightly blurry in Gnome 3.34 and 3.36 Upstream fix pending: https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Feb 7 16:08:58 2020 DisplayManager: InstallationDate: Installed on 2020-02-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1862308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890261] Re: I am not prompted for my password when booting after running out of power (e.g. empty battery)
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1890261 Title: I am not prompted for my password when booting after running out of power (e.g. empty battery) Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 18.04.4 LTS When the system shuts down because of lack of power supply, the next time, I am not prompted for my password; I go directly to the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 11:06:26 2020 InstallationDate: Installed on 2018-10-04 (669 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue 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/1890261/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890802] Re: Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland
The bug you logged here is about Xorg fractional scaling, not Wayland. They are different code bases. Please keep comments here about Xorg and if you see problems with Wayland then open a new bug. -- 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/1890802 Title: Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland Status in mutter package in Ubuntu: Won't Fix Bug description: Laptop: Lenovo ThinkPad L480 Graphics: Intel UHD Graphics 620 (KBL GT2) Second monitor: Philips 276E8VJSB/00 4K UHD There is a big performance degradation in an X11 session + 4K resolution + 125% fractional scaling in the second monitor compared to a Wayland session. The mouse cursor moves very slow, dragging Windows is very slow, scrolling in Firefox is very laggy, so everything becomes unusable. The performance degradation applies in both displays even though fractional scaling is only applied in the second 4K monitor. Whereas in Wayland, the performance is much better in 4K resolution + fractional scaling in the second monitor, the mouse cursor and dragging windows are a lot smoother. I just sometimes notice a slight jump in the mouse cursor but only in the second monitor, the built-in monitor behaves normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 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: Fri Aug 7 12:00:26 2020 InstallationDate: Installed on 2020-04-26 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/1890802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
^^^ That is bug 1892440. It is not relevant here. -- 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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
^^^ That is bug 1892440. It is not relevant here. -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Won't Fix Status in mutter source package in Eoan: Fix Released Bug description: [Impact] The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design (1)) upon resuming from suspend. This creates a poor user experience and gives the impression of severe memory corruption. (1) https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt [Test Case] 0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver. 1. Suspend and resume the machine. Expect: The wallpaper still looks like it did before suspending. [Regression Potential] Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and has been used for a couple of months without issue. [Original Report] https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 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: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string 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.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
I am also having this issue on a brand new laptop (Ryzen 5 4500), however the dead mouse pointer is there from a fresh reboot. It is left over from the login screen and remains there once the system has logged in. If I logout, the 'dead' mouse becomes the only one on the login screen, yet loging back in causes it to freeze while a second pointer becomes active. Very strange behaviour! -- 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 1892788] [NEW] launches yagv when opening FOLDER
Public bug reported: Critical bug. file-roller will make the system user interface sieze up and cause you to lose work. - Ubuntu 18.04 - install firefox and yagv - In firefox, download and select open with archive manager https://www.chepclub.com/uploads/9/2/9/8/9298268/chepbedlevel_3.0.zip - In file roller, click on the folder ChepBedLevel2.0 - It will not browse the folder - Double click on the folder. - Instead of browsing the folder, It will launch yagv on the g-code files. It might also launch the text editor (gedit?) on the STL file. - the system doesn't hang every time but it does occur multiple times. - ssh in remotely and killall file-roller to get control of your machine back. file-roller is very unresponsive, even with the machine working ok. Same thing happens with a 3D model with no g-code downloaded from thingiverse containing no g-code. www.thingiverse.com/thing:2867275 In this case, it tries to open the huge STL file with a text editor. In this case, I noticed that trying to type in a terminal window caused the text editor search box to appear. The hangs might be occuring in gedit and/or yagv (never seen that before) but gedit was launched without consent. This seems to be exciting an existing bug in the system. It not uncommon for certain programs dialog boxes to sieze control of the the mouse pointer and make the machine unusable. I had more trouble than usual recovering, however. Ctrl-Alt-Del and cancel did not work and switching consoles didn't work. I have disabled a few dialog boxes that cause this problem, like the an application is unresponsive, do you want me to make the entire system unresponsive? dialog box. dpkg -l yagv; dpkg -l file-roller; dpkg -l gedit; lsb_release -a Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii yagv 0.4~20130422 all yet another G-code viewer Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii file-roller3.28.0-1ubun amd64archive manager for GNOME Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii gedit 3.28.1-1ubun amd64official text editor of the GNOME No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: file-roller 3.28.0-1ubuntu1.2 ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-61-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 16:58:08 2020 InstallationDate: Installed on 2019-05-02 (480 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1892788 Title: launches yagv when opening FOLDER Status in file-roller package in Ubuntu: New Bug description: Critical bug. file-roller will make the system user interface sieze up and cause you to lose work. - Ubuntu 18.04 - install firefox and yagv - In firefox, download and select open with archive manager https://www.chepclub.com/uploads/9/2/9/8/9298268/chepbedlevel_3.0.zip - In file roller, click on the folder ChepBedLevel2.0 - It will not browse the folder - Double click on the folder. - Instead of browsing the folder, It will launch yagv on the g-code files. It might also launch the text editor (gedit?) on the STL file. - the system doesn't hang every time but it does occur multiple times. - ssh in remotely and killall file-roller to get control of your machine back. file-roller is very unresponsive, even with the machine working ok. Same thing happens with a 3D model with no g-code downloaded from thingiverse containing no g-code.
[Desktop-packages] [Bug 1351025] Re: "Error setting permissions: Operation not permitted" during backup
I think this should be fixed with 42.2, which now looks at /etc/fatal and mounts the target drive if necessary. ** Changed in: deja-dup Status: New => Fix Released ** Changed in: deja-dup (Ubuntu) Status: New => Fix Released -- 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/1351025 Title: "Error setting permissions: Operation not permitted" during backup Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Released Bug description: directory selection to backup /home /etc/tools directories to be ignored Trash ~/Telechargements (using french version) should be something like ~/Downloads ? backup destination set up to local directory /mnt/home-usb-hd/ubuntu_backup : this is an external usb hard disk /mnt$ ls -l total 36 drwxr-xr-x 2 root root 4096 mai 15 22:27 home-smb-hd drwxrwxrwx 23 root root 32768 janv. 1 1970 home-usb-hd hard disk is mounted at startup withing /etc/fstab # External USB drive UUID=18F5-2038/mnt/home-usb-hdvfat user,auto,fmask=0111,dmask= after boot /mnt/home-usb-hd can be browsed, and using a term i'm able to create files using command like cat > hello.txt /mnt/home-usb-hd/ubuntu_backup also exists schedule : each week keep at least 6 months -- $ lsb_release -d Description: Ubuntu 14.04.1 LTS $ dpkg-query -W deja-dup duplicity deja-dup 30.0-0ubuntu4 duplicity 0.6.23-1ubuntu4.1 $ gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings ludovic@ludovic-Inspiron-One-2310:~$ cat gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings cat: gsettings: Aucun fichier ou dossier de ce type cat: list-recursively: Aucun fichier ou dossier de ce type cat: org.gnome.DejaDup: Aucun fichier ou dossier de ce type oops... something is missing ? running DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log reproduced bug $ ls -l total 52 -rw-rw-r-- 1 ludovic ludovic 0 juil. 31 21:38 deja-dup.gsettings -rw-rw-r-- 1 ludovic ludovic 38336 juil. 31 21:48 deja-dup.log drwx-- 2 ludovic ludovic 4096 janv. 1 1970 orbit-ludovic drwx-- 3 ludovic ludovic 4096 juil. 31 21:39 sni-qt_spotify_6779-BcqifS drwx-- 2 ludovic ludovic 4096 juil. 31 19:27 ssh-DTvCOBjq2jSq -rw-rw-r-- 1 ludovic ludovic 0 juil. 31 19:27 unity_support_test.0 /tmp/deja-dup.log will be added to this report cd /mnt/home-usb-hd/ubuntu_backup; ls -ltr -rw-rw-rw- 1 root root 42134104 juil. 25 17:43 duplicity-inc.20140718T210903Z.to.20140725T153906Z.vol17.difftar.gpg -rw-rw-rw- 1 root root 9972670 juil. 25 17:43 duplicity-new-signatures.20140718T210903Z.to.20140725T153906Z.sigtar.gpg -rw-rw-rw- 1 root root 990 juil. 25 17:43 duplicity-inc.20140718T210903Z.to.20140725T153906Z.manifest.gpg -rw-rw-rw- 1 root root 2 juil. 31 19:50 test.txt -rw-rw-rw- 1 root root 10527973 juil. 31 21:47 duplicity-inc.20140725T153906Z.to.20140731T194554Z.vol1.difftar.gpg To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1351025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892779] Re: Browser will not play videos
** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1892779 Title: Browser will not play videos Status in firefox package in Ubuntu: Invalid Bug description: I cannot play videos in either firefox or chromium. The video appears to load but then I just get a spinner and nothing happens. I have tried youtube.com, operavision.eu and metopera.org. All fail. I have installed ubuntu-restricted-extras, turned off acceleration in firefox's preferences, and generally tried all the suggestions I can find on the web. Lots of people seem to have this problem. Firefox is 79.0 Chromium is 84.0.4147.105 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 1595 F pulseaudio /dev/snd/controlC0: raph 1595 F pulseaudio /dev/snd/pcmC0D0c: raph 1595 F...m pulseaudio /dev/snd/pcmC0D0p: raph 1595 F...m pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Mon Aug 24 20:45:02 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:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-08-09 (15 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp82s0 proto dhcp metric 600 169.254.0.0/16 dev wlp82s0 scope link metric 1000 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.30 metric 100 192.168.178.0/24 dev wlp82s0 proto kernel scope link src 192.168.178.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892783] [NEW] [SRU] libreoffice 6.4.6 for focal
Public bug reported: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: New Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I also can't get the hardware acceleration on Youtube.
With Netflix I do get DecryptingVideoDecoder.
Also there is no "Hardware-accelerated video decode" in flags.
Chromium snap version 84.0.4147.135 from candidate/vaapi channel.
$ vainfo
libva info: VA-API version 1.7.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_7
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Mesa Gallium driver 20.0.8 for AMD Radeon RX 5600 XT
(NAVI10, DRM 3.38.0, 5.8.3-xanmod1, LLVM 10.0.0)
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
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0: VAEntrypointVLD
VAProfileVP9Profile2: VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
chrome://media-internals/
render_id: 9
player_id: 24
origin_url: https://www.youtube.com/
kFrameUrl: https://www.youtube.com/watch?v=LXb3EKWsInQ
kFrameTitle: COSTA RICA IN 4K 60fps HDR (ULTRA HD) - YouTube
url: blob:https://www.youtube.com/61c207f8-ceac-4af4-ab57-2e6c0526d53b
info: Effective playback rate changed from 0 to 1
pipeline_state: kPlaying
kAudioTracks: [object Object]
duration: 313.840907
kVideoTracks: [object Object]
kIsAudioDecryptingDemuxerStream: false
kAudioDecoderName: FFmpegAudioDecoder
kIsPlatformAudioDecoder: false
error:
{"causes":[{"causes":[],"data":{"codec":"h264"},"stack":[{"file":"../../media/filters/dav1d_video_decoder.cc","line":165}],"status_code":260,"status_message":""}],"data":{"Decoder
name":"Dav1dVideoDecoder"},"stack":[{"file":"../../media/filters/decoder_selector.cc","line":172}],"status_code":265,"status_message":""}
kIsVideoDecryptingDemuxerStream: false
kVideoDecoderName: FFmpegVideoDecoder
kIsPlatformVideoDecoder: false
audio_buffering_state: [object Object]
dimensions: 1920x1080
kResolution: 1920x1080
video_buffering_state: [object Object]
pipeline_buffering_state: [object Object]
event: kPlay
--
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
[Desktop-packages] [Bug 1892779] Re: Browser will not play videos
Immediately after reporting this I tried again to play a video, and this time it worked. After much frustration the problem just disappeared. -- 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/1892779 Title: Browser will not play videos Status in firefox package in Ubuntu: New Bug description: I cannot play videos in either firefox or chromium. The video appears to load but then I just get a spinner and nothing happens. I have tried youtube.com, operavision.eu and metopera.org. All fail. I have installed ubuntu-restricted-extras, turned off acceleration in firefox's preferences, and generally tried all the suggestions I can find on the web. Lots of people seem to have this problem. Firefox is 79.0 Chromium is 84.0.4147.105 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 1595 F pulseaudio /dev/snd/controlC0: raph 1595 F pulseaudio /dev/snd/pcmC0D0c: raph 1595 F...m pulseaudio /dev/snd/pcmC0D0p: raph 1595 F...m pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Mon Aug 24 20:45:02 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:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-08-09 (15 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp82s0 proto dhcp metric 600 169.254.0.0/16 dev wlp82s0 scope link metric 1000 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.30 metric 100 192.168.178.0/24 dev wlp82s0 proto kernel scope link src 192.168.178.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1892779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892779] [NEW] Browser will not play videos
Public bug reported: I cannot play videos in either firefox or chromium. The video appears to load but then I just get a spinner and nothing happens. I have tried youtube.com, operavision.eu and metopera.org. All fail. I have installed ubuntu-restricted-extras, turned off acceleration in firefox's preferences, and generally tried all the suggestions I can find on the web. Lots of people seem to have this problem. Firefox is 79.0 Chromium is 84.0.4147.105 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 1595 F pulseaudio /dev/snd/controlC0: raph 1595 F pulseaudio /dev/snd/pcmC0D0c: raph 1595 F...m pulseaudio /dev/snd/pcmC0D0p: raph 1595 F...m pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Mon Aug 24 20:45:02 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:725 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-08-09 (15 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev enx3c18a0095fb1 proto dhcp metric 100 default via 192.168.178.1 dev wlp82s0 proto dhcp metric 600 169.254.0.0/16 dev wlp82s0 scope link metric 1000 192.168.178.0/24 dev enx3c18a0095fb1 proto kernel scope link src 192.168.178.30 metric 100 192.168.178.0/24 dev wlp82s0 proto kernel scope link src 192.168.178.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:725 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=79.0/20200720193547 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1892779 Title: Browser will not play videos Status in firefox package in Ubuntu: New Bug description: I cannot play videos in either firefox or chromium. The video appears to load but then I just get a spinner and nothing happens. I have tried youtube.com, operavision.eu and metopera.org. All fail. I have installed ubuntu-restricted-extras, turned off acceleration in firefox's preferences, and generally tried all the suggestions I can find on the web. Lots of people seem to have this problem. Firefox is 79.0 Chromium is 84.0.4147.105 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raph 1595 F pulseaudio /dev/snd/controlC0: raph 1595 F pulseaudio /dev/snd/pcmC0D0c: raph 1595 F...m pulseaudio /dev/snd/pcmC0D0p: raph 1595 F...m pulseaudio BuildID: 20200720193547 CasperMD5CheckResult: skip Channel: Unavailable
[Desktop-packages] [Bug 1888575] Please test proposed package
Hello Andreas, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1888575 Title: Split motd-news config into a new package Status in base-files package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress 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: In Progress 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
[Desktop-packages] [Bug 1888575] Re: Split motd-news config into a new package
Hello Andreas, or anyone else affected, Accepted ubuntu-meta into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.417.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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: In Progress 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: In Progress 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
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
GeForce RTX 2060 Mobile 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://hr.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://hr.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 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
Hi, Sujit Kumar. The solution of disabling NVIDIA drivers is not so right, because I need to use my hardware completely (use the NVIDIA hardware to compute complex matrices in my work). But thanks for your reply. -- 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 1888575] Re: Split motd-news config into a new package
Hello Andreas, or anyone else affected, Accepted ubuntu-meta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-meta/1.450.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Focal) Status: In Progress => Fix Committed -- 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: In Progress Status in base-files source package in Xenial: Fix Committed Status in ubuntu-meta source package in Xenial: In Progress Status in base-files source package in Bionic: Fix Committed Status in ubuntu-meta source package in Bionic: In Progress 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: In Progress 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
Re: [Desktop-packages] [Bug 1892400] Re: Open text files with File manager (mouse won't release)
When clicking on text file being opened in gedit, twice/three times, than the file has been opened, however mouse cursor will be released 15-30 sec later. (going back to arrow). - it seems it doesn't notice that text file is already opened. On Mon, Aug 24, 2020, 12:20 Sebastien Bacher <1892...@bugs.launchpad.net> wrote: > Thank you for your bug report, could you take a video showing the issue? > How does it 'hang' exactly? What applications is used to open the text > document? > > ** Changed in: nautilus (Ubuntu) >Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1892400 > > Title: > Open text files with File manager (mouse won't release) > > Status in nautilus package in Ubuntu: > Incomplete > > Bug description: > When you open Text File from File Manager mouse cursor hangs until > time outs. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: nautilus 1:3.26.4-0~ubuntu18.04.5 > ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 > Uname: Linux 4.15.0-112-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Aug 20 19:01:13 2020 > GsettingsChanges: >b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' >b'org.gnome.nautilus.window-state' b'geometry' b"'864x458+697+195'" >b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' >b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', > 'size', 'type', 'date_modified']" >b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', > 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', > 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" > InstallationDate: Installed on 2017-08-07 (1109 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > SourcePackage: nautilus > UpgradeStatus: Upgraded to bionic on 2020-05-25 (87 days ago) > usr_lib_nautilus: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892400/+subscriptions > -- 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/1892400 Title: Open text files with File manager (mouse won't release) Status in nautilus package in Ubuntu: Incomplete Bug description: When you open Text File from File Manager mouse cursor hangs until time outs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 19:01:13 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x458+697+195'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (87 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
This happend to when, I set the system to update, and then left it unattended and system got suspended, when I wake it up again the dialog was there unclickable, non cancelable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892724] Re: Bump package epoch to 1 to ensure working upgrade path and transition to snap
This bug was fixed in the package chromium-browser - 1:84.0.4147.135-0ubuntu1 --- chromium-browser (1:84.0.4147.135-0ubuntu1) groovy; urgency=medium * New upstream release: 84.0.4147.135 * Bump epoch to 1 to ensure always working upgrade path from bionic (LP: #1892724) -- Olivier Tilloy Mon, 24 Aug 2020 15:49:01 +0200 ** Changed in: chromium-browser (Ubuntu) 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Released Bug description: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- Mailing list: https://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%
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://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 01:00.0 VGA compatible controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1) +-+ | NVIDIA-SMI 390.138 Driver Version: 390.138 | |---+--+--+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 Quadro K1100M Off | :01:00.0 Off | N/A | | N/A 59C P0 N/A / N/A | 1460MiB / 1999MiB | 3% Default | +---+--+--+ I have both discreet and Nvidia. I'd like to use the Nvidia on demand, but there's an issue with prime that I had so I'm on Nvidia permanently at the moment. On 24/08/2020 15:41, Marco Trevisan (Treviño) wrote: > People with that still have the issue, can please give us: > - The card you're using (AFAIK mostly mobile cards are affected) > - The output of: apt-cache policy libmutter-6-0 > -- 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 1892635] Re: mysql-direct-connector not working
** Package changed: ubuntu => libreoffice (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1892635 Title: mysql-direct-connector not working Status in libreoffice package in Ubuntu: New Bug description: After upgrading to (k)ubuntu 20.04.1, both with LibreOffice 6.4. and LibreOffice 7, mysql direct connector doesn't work any more (unlike in (k)ubuntu 18.04 and LO 6.0). Mysql (mariadb, installed with lampp) is perfectly working in browsers: I can see php+mysql pages in localhost, without any problem. But if I try to open a database odb connected with mysql I get an error message [code] Code: SQL Status: HY000 Error code: 2003 Can't connect to MySQL server on 'localhost' (111) /build/libreoffice-ron9it/libreoffice-7.0.0~rc3/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:119 [/code] I believe that is a problem of mysql-connector provided with Ubuntu, in the past so useful (because LO extension are not working). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892635] [NEW] mysql-direct-connector not working
You have been subscribed to a public bug: After upgrading to (k)ubuntu 20.04.1, both with LibreOffice 6.4. and LibreOffice 7, mysql direct connector doesn't work any more (unlike in (k)ubuntu 18.04 and LO 6.0). Mysql (mariadb, installed with lampp) is perfectly working in browsers: I can see php+mysql pages in localhost, without any problem. But if I try to open a database odb connected with mysql I get an error message [code] Code: SQL Status: HY000 Error code: 2003 Can't connect to MySQL server on 'localhost' (111) /build/libreoffice-ron9it/libreoffice-7.0.0~rc3/connectivity/source/drivers/mysqlc/mysqlc_general.cxx:119 [/code] I believe that is a problem of mysql-connector provided with Ubuntu, in the past so useful (because LO extension are not working). ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment direct-connector librebase libreoffice mysql -- mysql-direct-connector not working https://bugs.launchpad.net/bugs/1892635 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice 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 1892727] Re: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1
This appears to be a timeout when downloading the chromium snap from the store. Can you please try again, and let us know how this goes? sudo apt install chromium-browser ** 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/1892727 Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: ；fdlk'l ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) 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 Date: Mon Aug 24 22:14:03 2020 ErrorMessage: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2020-08-24 (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: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 affected NVIDIA GeForce GTX 1070 Nvidia driver 440.100 $ apt-cache policy libmutter-6-0 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://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://gb.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 1892751] [NEW] Brother Printer (HLL295dw) Drivers CUPS errors
Public bug reported: I have a Brother Printer (HLL2935dw) that will not print, which I expected to happen after adding the printer and driver through CUPS. Release is Ubuntu 20.04.1 LTS Package is cups: 2.3.1-9ubuntu1.1 Instead of printing, the process hangs until the I cancel the print job. Output of the CUPS error log. Debugging has been turned on. Error log output: D [20/Aug/2020:03:07:33 -0700] [Client 281] cupsdWriteClient error=0, used=0, state=HTTP_STATE_GET_SEND, data_encoding=HTTP_ENCODING_CHUNKED, data_remaining=0, response=(nil)(), pipe_pid=21083, file=20 D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for CGI data. D [20/Aug/2020:03:07:33 -0700] [Client 281] CGI data ready to be sent. D [20/Aug/2020:03:07:33 -0700] [Client 281] con->http=0x5651d923b1f0 D [20/Aug/2020:03:07:33 -0700] [Client 281] cupsdWriteClient error=0, used=0, state=HTTP_STATE_GET_SEND, data_encoding=HTTP_ENCODING_CHUNKED, data_remaining=0, response=(nil)(), pipe_pid=21083, file=20 D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for CGI data. D [20/Aug/2020:03:07:33 -0700] [Client 281] Sending 0-length chunk. D [20/Aug/2020:03:07:33 -0700] [Client 281] Flushing write buffer. D [20/Aug/2020:03:07:33 -0700] [Client 281] New state is HTTP_STATE_WAITING D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for request. D [20/Aug/2020:03:07:33 -0700] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs" I [20/Aug/2020:03:07:34 -0700] Expiring subscriptions... ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: brother cups hll2935dw printer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892751 Title: Brother Printer (HLL295dw) Drivers CUPS errors Status in cups package in Ubuntu: New Bug description: I have a Brother Printer (HLL2935dw) that will not print, which I expected to happen after adding the printer and driver through CUPS. Release is Ubuntu 20.04.1 LTS Package is cups: 2.3.1-9ubuntu1.1 Instead of printing, the process hangs until the I cancel the print job. Output of the CUPS error log. Debugging has been turned on. Error log output: D [20/Aug/2020:03:07:33 -0700] [Client 281] cupsdWriteClient error=0, used=0, state=HTTP_STATE_GET_SEND, data_encoding=HTTP_ENCODING_CHUNKED, data_remaining=0, response=(nil)(), pipe_pid=21083, file=20 D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for CGI data. D [20/Aug/2020:03:07:33 -0700] [Client 281] CGI data ready to be sent. D [20/Aug/2020:03:07:33 -0700] [Client 281] con->http=0x5651d923b1f0 D [20/Aug/2020:03:07:33 -0700] [Client 281] cupsdWriteClient error=0, used=0, state=HTTP_STATE_GET_SEND, data_encoding=HTTP_ENCODING_CHUNKED, data_remaining=0, response=(nil)(), pipe_pid=21083, file=20 D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for CGI data. D [20/Aug/2020:03:07:33 -0700] [Client 281] Sending 0-length chunk. D [20/Aug/2020:03:07:33 -0700] [Client 281] Flushing write buffer. D [20/Aug/2020:03:07:33 -0700] [Client 281] New state is HTTP_STATE_WAITING D [20/Aug/2020:03:07:33 -0700] [Client 281] Waiting for request. D [20/Aug/2020:03:07:33 -0700] cupsdSetBusyState: newbusy="Printing jobs", busy="Active clients and printing jobs" I [20/Aug/2020:03:07:34 -0700] Expiring subscriptions... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892727] Re: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1
Relevant log from DpkgTerminalLog.txt: ==> Installing the chromium snap error: cannot perform the following tasks: - Download snap "chromium" (1260) from channel "stable" (received an unexpected http response code (408) when trying to download https://api.snapcraft.io/api/v1/snaps/download/XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R_1260.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/1892727 Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: ；fdlk'l ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) 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 Date: Mon Aug 24 22:14:03 2020 ErrorMessage: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2020-08-24 (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: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
I game a bit on my PC(using wine of course!).So changing the driver is out of the question for me. -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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 bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890802] Re: Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland
I tried the old Intel i965 driver, however, I didn't notice any difference, so I switched back. BTW I tested only Wayland because of the fractional scaling. -- 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/1890802 Title: Big performance degradation in X11 + 4K resolution + fractional scaling in second monitor compared to Wayland Status in mutter package in Ubuntu: Won't Fix Bug description: Laptop: Lenovo ThinkPad L480 Graphics: Intel UHD Graphics 620 (KBL GT2) Second monitor: Philips 276E8VJSB/00 4K UHD There is a big performance degradation in an X11 session + 4K resolution + 125% fractional scaling in the second monitor compared to a Wayland session. The mouse cursor moves very slow, dragging Windows is very slow, scrolling in Firefox is very laggy, so everything becomes unusable. The performance degradation applies in both displays even though fractional scaling is only applied in the second 4K monitor. Whereas in Wayland, the performance is much better in 4K resolution + fractional scaling in the second monitor, the mouse cursor and dragging windows are a lot smoother. I just sometimes notice a slight jump in the mouse cursor but only in the second monitor, the built-in monitor behaves normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.3-0ubuntu0.20.04.1 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: Fri Aug 7 12:00:26 2020 InstallationDate: Installed on 2020-04-26 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/1890802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892727] Re: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1
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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1892727 Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 Status in chromium-browser package in Ubuntu: New Bug description: ；fdlk'l ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) 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 Date: Mon Aug 24 22:14:03 2020 ErrorMessage: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2020-08-24 (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: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: 新的 chromium-browser 软件包 pre-installation 脚本 子进程返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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%
GL_VENDOR: NVIDIA Corporation GL_RENDERER: GeForce GTX 1050/PCIe/SSE2 GL_VERSION:4.6.0 NVIDIA 440.100 apt-cache policy libmutter-6-0 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://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1-3ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages I would LOVE to have that fixed!! -- 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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
People with that still have the issue, can please give us: - The card you're using (AFAIK mostly mobile cards are affected) - The output of: apt-cache policy libmutter-6-0 -- 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 1892735] [NEW] package libjavascriptcoregtk-4.0-18 2.28.2-0ubuntu0.20.04.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/x86_64-linux-g
Public bug reported: Les paquets suivants ont des dépendances non satisfaites : libwebkit2gtk-4.0-37: Depends: libjavascriptcoregtk-4.0-18 (= 2.28.3-0ubuntu0.20.04.1) mais la version 2.28.2-0ubuntu0.20.04.1 est installée Depends: libc6 (>= 2.29) mais la version 2.31-0ubuntu9 est installée Depends: libgcc-s1 (>= 7) mais la version 10-20200411-0ubuntu1 est installée Depends: libglib2.0-0 (>= 2.59.0) mais la version 2.64.3-1~ubuntu20.04.1 est installée Depends: libgtk-3-0 (>= 3.23.0) mais la version 3.24.20-0ubuntu1 est installée Depends: libicu66 (>= 66.1-1~) mais la version 66.1-2ubuntu2 est installée Depends: libjpeg8 (>= 8c) mais la version 8c-2ubuntu8 est installée Depends: libsoup2.4-1 (>= 2.69.90) mais la version 2.70.0-1 est installée Depends: libsqlite3-0 (>= 3.7.15) mais la version 3.31.1-4ubuntu0.1 est installée Depends: libstdc++6 (>= 9) mais la version 10-20200411-0ubuntu1 est installée Depends: libtasn1-6 (>= 4.14) mais la version 4.16.0-2 est installée Depends: libxcomposite1 (>= 1:0.4.5) mais la version 1:0.4.5-1 est installée Depends: libxdamage1 (>= 1:1.1) mais la version 1:1.1.5-2 est installée Depends: zlib1g (>= 1:1.2.0) mais la version 1:1.2.11.dfsg-2ubuntu1 est installée ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjavascriptcoregtk-4.0-18 2.28.2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 ApportVersion: 2.20.11-0ubuntu27.3 AptOrdering: libjavascriptcoregtk-4.0-18:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 24 16:27:49 2020 DpkgHistoryLog: Start-Date: 2020-08-24 16:27:48 Commandline: apt-get install -f Requested-By: stef (1000) Upgrade: libjavascriptcoregtk-4.0-18:amd64 (2.28.2-0ubuntu0.20.04.1, 2.28.3-0ubuntu0.20.04.1) ErrorMessage: impossible de copier les données extraites pour « ./usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6 » vers « /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6.dpkg-new » : fin de fichier ou de flux inattendue InstallationDate: Installed on 2020-04-28 (117 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: webkit2gtk Title: package libjavascriptcoregtk-4.0-18 2.28.2-0ubuntu0.20.04.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6 » vers « /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6.dpkg-new » : fin de fichier ou de flux inattendue UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: webkit2gtk (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 webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1892735 Title: package libjavascriptcoregtk-4.0-18 2.28.2-0ubuntu0.20.04.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6 » vers « /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18.16.6.dpkg- new » : fin de fichier ou de flux inattendue Status in webkit2gtk package in Ubuntu: New Bug description: Les paquets suivants ont des dépendances non satisfaites : libwebkit2gtk-4.0-37: Depends: libjavascriptcoregtk-4.0-18 (= 2.28.3-0ubuntu0.20.04.1) mais la version 2.28.2-0ubuntu0.20.04.1 est installée Depends: libc6 (>= 2.29) mais la version 2.31-0ubuntu9 est installée Depends: libgcc-s1 (>= 7) mais la version 10-20200411-0ubuntu1 est installée Depends: libglib2.0-0 (>= 2.59.0) mais la version 2.64.3-1~ubuntu20.04.1 est installée Depends: libgtk-3-0 (>= 3.23.0) mais la version 3.24.20-0ubuntu1 est installée Depends: libicu66 (>= 66.1-1~) mais la version 66.1-2ubuntu2 est installée Depends: libjpeg8 (>= 8c) mais la version 8c-2ubuntu8 est installée Depends: libsoup2.4-1 (>= 2.69.90) mais la version 2.70.0-1 est installée Depends: libsqlite3-0 (>= 3.7.15) mais la version 3.31.1-4ubuntu0.1 est installée Depends: libstdc++6 (>= 9) mais la version 10-20200411-0ubuntu1 est installée Depends:
[Desktop-packages] [Bug 1891974] Re: Can not support Synaptics 06cb:00be fingerprint
** Description changed: We already supported Synaptics 06cb:00bd fingerprint recently, but can not support another ID yet: Synaptics 06cb:00be Tested on Ubuntu 20.04.1. + Platform with this chip https://certification.ubuntu.com/catalog/component/06cb:00be ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu) Importance: Undecided => Wishlist ** Changed in: oem-priority Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1891974 Title: Can not support Synaptics 06cb:00be fingerprint Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Bug description: We already supported Synaptics 06cb:00bd fingerprint recently, but can not support another ID yet: Synaptics 06cb:00be Tested on Ubuntu 20.04.1. Platform with this chip https://certification.ubuntu.com/catalog/component/06cb:00be To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888157] Re: Thunderbird 78
https://launchpad.net/ubuntu/+source/thunderbird/1:78.2.0+build1-0ubuntu1 -- 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/1888157 Title: Thunderbird 78 Status in thunderbird package in Ubuntu: Fix Committed Bug description: There is a new ESR release of Thunderbird and I don't see an issue about the plans for the move to that new version. There looks to be some changes to the profile that are one way--once you have moved that profile to version 78, you can't work with it on older versions of Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1888157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892724] Re: Bump package epoch to 1 to ensure working upgrade path and transition to snap
1:84.0.4147.135-0ubuntu1 uploaded to groovy. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892724] Re: Bump package epoch to 1 to ensure working upgrade path and transition to snap
Quoting the ubuntu-devel@ conversation here for easier future reference: « In doing SRU reviews today, I came across LP: #1889106 which is a request for a no-change rebuild to bump the version so it beats the versions presented in previous releases. The problem is real, but it seems suboptimal to me to keep fixing it this way. We'll need to keep SRUing chromium-browser to Focal (and later releases presumably). Every time we do that, all users (who have the transitional package) get yet another update to download, even if it is small. And every time it takes both Olivier's and the SRU team's time. Would an epoch bump be a better option here? Debian doesn't currently carry a package with that name, so we're already diverged enough that I don't forsee a problem from there. » xnox answered: « lxd used epoch too, to ensure that deb2snap transitional package is always higher whichever backports are uploaded as debs into previous series. https://launchpad.net/ubuntu/+source/lxd So +1 from me. » and vorlon answered: « I agree that an epoch bump on the transitional .deb in focal is a reasonable solution for this issue. » ** Description changed: - For a complete rational, see comments #4, #5, #7 and #8 in bug #1889106, - and the discussion in https://lists.ubuntu.com/archives/ubuntu- - devel/2020-August/041127.html. + For a complete rationale, see comments #4, #5, #7 and #8 in bug + #1889106, and the discussion in https://lists.ubuntu.com/archives + /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. -- 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892724] Re: Bump package epoch to 1 to ensure working upgrade path and transition to snap
** Branch linked: lp:~chromium-team/chromium-browser/groovy-stable -- 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892724] [NEW] Bump package epoch to 1 to ensure working upgrade path and transition to snap
Public bug reported: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. ** Affects: chromium-browser (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Fix Committed ** Description changed: For a complete rational, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives/ubuntu- devel/2020-August/041127.html. + + This needs to be done in groovy and SRUed to focal. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High -- 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/1892724 Title: Bump package epoch to 1 to ensure working upgrade path and transition to snap Status in chromium-browser package in Ubuntu: Fix Committed Bug description: For a complete rationale, see comments #4, #5, #7 and #8 in bug #1889106, and the discussion in https://lists.ubuntu.com/archives /ubuntu-devel/2020-August/041127.html. This needs to be done in groovy and SRUed to focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550 -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Disco: Won't Fix Status in mutter source package in Eoan: Fix Released Bug description: [Impact] The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design (1)) upon resuming from suspend. This creates a poor user experience and gives the impression of severe memory corruption. (1) https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt [Test Case] 0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver. 1. Suspend and resume the machine. Expect: The wallpaper still looks like it did before suspending. [Regression Potential] Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and has been used for a couple of months without issue. [Original Report] https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 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: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-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.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string 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.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550 -- 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 1892600] Re: pdfannotextractor launch script is missing "-jar" flag
Thanks for the link. Recent problems with pax seem to revolve around
pdfbox; however, the current packaging includes pdfbox, possibly to
avoid those problems.
Here is a patch that fixes the bug under discussion:
--- pdfannotextractor.pl2020-08-22 15:40:21.511195000 -0500
+++ pdfannotextractor.pl2020-08-22 16:19:31.196837000 -0500
@@ -186,6 +186,7 @@
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
+push @cmd, "-jar";
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1892600
Title:
pdfannotextractor launch script is missing "-jar" flag
Status in texlive-extra package in Ubuntu:
New
Bug description:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal
/texlive-latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use
the jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1892600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550 -- 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 1892521] Re: UI bug - system fonts enlarge after every reboot
For now you can easily fix this without any third-party applications by following these instructions: https://askubuntu.com/a/1269431/1119550 -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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 bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] 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
Verified working.
For convenience I used a slightly different testing method than the test case
in the bug description: I downloaded and installed (with `dpkg -i`) the
chromium-browser, chromium-browser-l10n and chromium-codecs-ffmpeg-extra debs
from
https://launchpad.net/ubuntu/+source/chromium-browser/84.0.4147.105-0ubuntu0.18.04.1
in a fully up-to-date focal VM. I then ran `sudo apt update` to verify that no
update was available for chromium-browser. I then enabled focal-proposed for
universe and verified that the update to chromium-browser
84.0.4147.105-0ubuntu0.20.04.1 was available, installed it with `sudo apt
install chromium-browser`, and checked that this installed the chromium snap as
expected. I then verified that chromium-browser launches and works as expected.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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 Committed
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 1892723] [NEW] Evince can't open some pdf files correctly
Public bug reported: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-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.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-08-24 17-36-09.png" https://bugs.launchpad.net/bugs/1892723/+attachment/5404150/+files/Screenshot%20from%202020-08-24%2017-36-09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1892723 Title: Evince can't open some pdf files correctly Status in evince package in Ubuntu: New Bug description: I have a pdf file which I can't open with evince. When I try to, suddenly window bar hides and it kind of crashs. There's not any problem with the file since it can be opened with other pdf readers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-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.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 17:33:35 2020 InstallationDate: Installed on 2020-08-03 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1892723/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] 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
Thanks Robie for the suggestion. I hadn't thought of an epoch bump, but
it sounds like a good solution to the recurring problem at hand.
This is the ubuntu-devel@ discussion for reference:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041127.html.
I am going to test the package in focal-proposed and validate this SRU,
and I will then add the epoch in groovy and SRU it to focal.
--
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 Committed
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 1891478] Re: orca ftbfs in focal (amd64 only)
** Also affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New ** Changed in: at-spi2-atk (Ubuntu) Status: New => Fix Committed ** Changed in: at-spi2-atk (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: at-spi2-atk (Ubuntu) Importance: Undecided => High ** Changed in: orca (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orca in Ubuntu. https://bugs.launchpad.net/bugs/1891478 Title: orca ftbfs in focal (amd64 only) Status in at-spi2-atk package in Ubuntu: Fix Committed Status in orca package in Ubuntu: In Progress Bug description: seen in a focal test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal-updates/+build/19791402 [...] checking for ATSPI2... yes checking for ATKBRIDGE... no configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met: Package 'atk', required by 'atk-bridge-2.0', not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1891478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby this as well. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- 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 1870736] Re: [nvidia] Screen scaling 125% gives 200%
This problem still exists on my system (Latest Updates / Nvidia Titan). -- 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 1892712] Re: Printing garbage to Brother HL-L2375DW printer
Bug #1832646 sounds similar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer Status in cups package in Ubuntu: New Bug description: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892712] [NEW] Printing garbage to Brother HL-L2375DW printer
Public bug reported: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: printer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer Status in cups package in Ubuntu: New Bug description: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889992] Re: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens
the real bug is why it's not using the native driver.. run apport- collect which should add relevant logs etc for mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1889992 Title: Ubuntu Focal Fossa freezes spontaneously -- must power off when this happens Status in mesa package in Ubuntu: Incomplete Bug description: I just did a fresh first-time install of Ubuntu on a Dell Inspirion 14 with no modifications apart from installing Canon printer drivers and no 3rd party peripherals. The desktop freezes spontaneously. When it freezes, the display freezes including the mouse pointer, and all keystrokes are unresponsive (can't even do ctrl-alt-F3 to get a tty). Forced power off is the only possible action. I think this is irrelevent, but I'll mention that (I think) the lockup only happens when I'm using VLC to play MythTV-served videos from the LAN. Nothing else is running.. not even a browser. I'm simply watching a video and out of the blue it hangs. After rebooting, I play the same video I was watching just before the hang, and finish watching without a freeze up. Which means there's no relation to the video data. $ inxi -Fxz System:Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Gnome 3.36.3 Distro: Ubuntu 20.04.1 LTS (Focal Fossa) Machine: Type: Portable System: Dell product: Inspiron 14-3452 v: 4.0.7 serial: Mobo: Dell model: 0625M8 v: A00 serial: UEFI: Dell v: 4.0.7 date: 04/26/2016 Battery: ID-1: BAT0 charge: 33.6 Wh condition: 33.6/41.4 Wh (81%) model: Samsung SD DELL 07G075A status: Full CPU: Topology: Dual Core model: Intel Celeron N3050 bits: 64 type: MCP arch: Airmont rev: 3 L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 6400 Speed: 1377 MHz min/max: 480/2160 MHz Core speeds (MHz): 1: 1034 2: 1139 Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 Display: server: X.Org 1.19.2 driver: i915 resolution: 1280x800~60Hz OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 direct render: Yes Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio vendor: Dell driver: snd_hda_intel v: kernel bus ID: 00:1b.0 Sound Server: ALSA v: k5.4.0-42-generic Network: Device-1: Realtek RTL8723BE PCIe Wireless Network Adapter driver: rtl8723be v: kernel port: e000 bus ID: 01:00.0 IF: wlp1s0 state: up mac: Drives:Local Storage: total: 29.12 GiB used: 8.75 GiB (30.0%) ID-1: /dev/mmcblk0 model: HBG4e size: 29.12 GiB Partition: ID-1: / size: 28.05 GiB used: 8.74 GiB (31.2%) fs: ext4 dev: /dev/mmcblk0p2 Sensors: System Temperatures: cpu: 52.0 C mobo: 47.0 C Fan Speeds (RPM): cpu: 3181 Info: Processes: 199 Uptime: 41m Memory: 1.85 GiB used: 891.8 MiB (46.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.17 inxi: 3.0.38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1889992/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Committed -- 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 Committed 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 1892484] Re: Screen Sharing option is missing in 20.10, but exists in 20.04.
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress -- 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 Committed 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 1892657] Re: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd
Sounds like it was fixed upstream with https://gitlab.freedesktop.org/bolt/bolt/-/merge_requests/209.patch which is in 0.9 https://launchpad.net/ubuntu/+source/bolt/0.9-1 We should probably SRU that fix to focal ** Changed in: bolt (Ubuntu) Importance: Undecided => Low ** Changed in: bolt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1892657 Title: boltd1719]: probing: timeout, done - timeouts every few seconds from boltd Status in bolt package in Ubuntu: Fix Released Bug description: This may relate to https://gitlab.freedesktop.org/bolt/bolt/-/issues/156 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bolt 0.8-4 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: Sun Aug 23 17:32:55 2020 InstallationDate: Installed on 2019-05-02 (479 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bolt UpgradeStatus: Upgraded to focal on 2020-04-23 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1892657/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892636] Re: The Files 3.36.3 directory search fails
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892636 Title: The Files 3.36.3 directory search fails Status in nautilus package in Ubuntu: Incomplete Bug description: does not find keywords in PDFA1.b - files when searching the directory. In one file, it works, and on my old windows system, it works with the same files and keywords. 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 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 17:20:15 2020 InstallationDate: Installed on 2020-05-22 (93 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892647] Re: gnome-screensaver can be failed into a locked state.
Thank you for your bug report, could you take a photo showing the issue?
What desktop do you use? The component you reported against is a legacy
and not used in the default Ubuntu Desktop
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1892647
Title:
gnome-screensaver can be failed into a locked state.
Status in gnome-screensaver package in Ubuntu:
Incomplete
Bug description:
When the screen is locked, you can freeze the screensaver application
by holding escape and scrolling up to activate the unlock screen with
the mouse. 'authentication error' pops up and the password input
{widget?} is non-responsive.
this isn't likely to pose a problem, but I will poke at it a bit and
if I see an issue with commands running with the user's privilege I
will let you know.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver 3.6.1-8ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 23 13:14:59 2020
InstallationDate: Installed on 2019-07-05 (415 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1892647/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892698] [NEW] [138A:003A] Validity Sensors, Inc. VFS495 Fingerprint Reader is currently not supported by libfprin
Public bug reported: It's used on a certified paltform, but it's not been supported by libfprint v1.90.2 nor IHV. [1] Validity Sensors, Inc. VFS495 Fingerprint Reader - https://certification.ubuntu.com/catalog/component/138a:003f ** Affects: oem-priority Importance: Low Status: New ** Affects: libfprint (Ubuntu) Importance: Wishlist Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Low ** Changed in: libfprint (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1892698 Title: [138A:003A] Validity Sensors, Inc. VFS495 Fingerprint Reader is currently not supported by libfprin Status in OEM Priority Project: New Status in libfprint package in Ubuntu: New Bug description: It's used on a certified paltform, but it's not been supported by libfprint v1.90.2 nor IHV. [1] Validity Sensors, Inc. VFS495 Fingerprint Reader - https://certification.ubuntu.com/catalog/component/138a:003f To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1892698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892600] Re: pdfannotextractor launch script is missing "-jar" flag
Thank you for your bug report, there are some discussions about that utility on
Debian
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670040
** Bug watch added: Debian Bug tracker #670040
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670040
** Changed in: texlive-extra (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1892600
Title:
pdfannotextractor launch script is missing "-jar" flag
Status in texlive-extra package in Ubuntu:
New
Bug description:
pdfannotextractor is a script that is part of the pax package that is
part of texlive-latex-extra : https://packages.ubuntu.com/focal
/texlive-latex-extra
The default installation throws this error:
$ pdfannotextractor --debug submission.pdf
PDFAnnotExtractor 0.1l, 2012/04/18 - Copyright (c) 2008, 2011, 2012 by Heiko
Oberdiek.
* CLASSPATH: []
* is_win: [0]
* Which kpsewhich: [/usr/bin/kpsewhich]
* Backticks: [kpsewhich --progname pdfannotextractor --format texmfscripts
pax.jar]
* Exit code: [0/success]
* pax.jar: [/usr/share/texlive/texmf-dist/scripts/pax/pax.jar]
* pdfbox.jar: [/usr/share/java/pdfbox.jar]
* Which java: [/usr/bin/java]
* System: [java /usr/share/texlive/texmf-dist/scripts/pax/pax.jar
submission.pdf]
Error: Could not find or load main class
.usr.share.texlive.texmf-dist.scripts.pax.pax.jar
Caused by: java.lang.ClassNotFoundException:
/usr/share/texlive/texmf-dist/scripts/pax/pax/jar
* Exit code: [1]
The problem is that the classpath is not properly configured to use
the jar. Simply adding the "-jar" flag solves the problem:
$ java -jar /usr/share/texlive/texmf-dist/scripts/pax/pax.jar submission.pdf
* Processing file `submission.pdf' ...
In the code, pdfannotextractor.pl, the change would be located here:
sub launch_pax () {
check_prg $prg_java, 1;
my @cmd = ($prg_java);
push @cmd, $path_jar_pax;
push @cmd, @ARGV;
debug 'System', "@cmd";
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-extra/+bug/1892600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892400] Re: Open text files with File manager (mouse won't release)
Thank you for your bug report, could you take a video showing the issue? How does it 'hang' exactly? What applications is used to open the text document? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1892400 Title: Open text files with File manager (mouse won't release) Status in nautilus package in Ubuntu: Incomplete Bug description: When you open Text File from File Manager mouse cursor hangs until time outs. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 19:01:13 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x458+697+195'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1109 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (87 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu- focal=87939c182b ** Changed in: pulseaudio (Ubuntu Focal) Assignee: Sebastien Bacher (seb128) => Daniel van Vugt (vanvugt) ** Changed in: pulseaudio (Ubuntu Focal) Milestone: ubuntu-20.04.1 => focal-updates ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Groovy: Fix Released Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I guess my only request is that: if (EDID_version > 1.4 && EDID_supports_10bit) then don't restrict "max bpc" endif -- 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 Linux: Unknown Status in OEM Priority Project: New 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/linux/+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 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
I guess my only request is that: if (EDID_version >= 1.4 && EDID_supports_10bit) then don't restrict "max bpc" endif ** Also affects: linux via https://gitlab.freedesktop.org/drm/intel/-/issues/1890 Importance: Unknown Status: Unknown -- 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 Linux: Unknown Status in OEM Priority Project: New 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/linux/+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 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libjpeg-turbo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1883798 Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg- turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 Status in libjpeg-turbo package in Ubuntu: Confirmed Bug description: not install file !!! packettracer ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libjpeg-turbo8 2.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 AptOrdering: libjpeg-turbo8:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 17 03:37:01 2020 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ... Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over (2.0.3-0ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 InstallationDate: Installed on 2020-06-16 (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: libjpeg-turbo Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from other instances of package libjpeg-turbo8:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Thanks for understanding. There's an upstream bug discussing this similar issue, we can follow their effort there. https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #1890 https://gitlab.freedesktop.org/drm/intel/-/issues/1890 ** Description changed: 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. + 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 ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- 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 OEM Priority Project: New 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
[Desktop-packages] [Bug 1892521] Re: UI bug - system fonts enlarge after every reboot
It may be related to bug 1892440 as most of us experiencing the bug use NVIDIA cards with driver 440. -- 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/1892521 Title: UI bug - system fonts enlarge after every reboot Status in mutter package in Ubuntu: Confirmed Bug description: I had my system fonts scaled to a FACTOR of 0.90 using GNOME TWEAKS.But after a RECENT UPDATE (which upgraded the following packages : gir1.2-mutter-6:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), libcurl4:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libmutter-6-0:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), rsyslog:amd64 (8.2001.0-1ubuntu1, 8.2001.0-1ubuntu1.1), mutter-common:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2), apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), python3-apport:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), xz-utils:amd64 (5.2.4-1, 5.2.4-1ubuntu1), apport-gtk:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), liblzma5:amd64 (5.2.4-1, 5.2.4-1ubuntu1), liblzma5:i386 (5.2.4-1, 5.2.4-1ubuntu1), curl:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), python3-problem-report:amd64 (2.20.11-0ubuntu27.6, 2.20.11-0ubuntu27.8), libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), libcurl3-gnutls:i386 (7.68.0-1ubuntu2.1, 7.68.0-1ubuntu2.2), mutter:amd64 (3.36.3-0ubuntu0.20.04.1, 3.36.4-0ubuntu0.20.04.2)) - the fonts automatically scale up after every reboot and ruin the look of my desktop.I had never encountered this problem before.It can be fixed by manually scaling back the fonts in GNOME TWEAKS after every reboot , which is annoying.I really would love to have this fixed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-21 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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 bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I encountered this issue on latest Fedora 32. So this is not unique to ubuntu. I have a dual booted system and when I tried to access windows partition data from fedora, I was required to type the password in authentication dialogue, after which I could access windows data. Then when I locked and unlocked again, this unclickable authentication dialogue box was stuck on top-left corner of the screen (If I tried to click it, whatever was 'behind' it was clicked). Pressing Alt + F2 and then 'f' removed it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1824874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
This bug affects me as well but in ubuntu 20.04. It's very annoying. I've open a question -> https://answers.launchpad.net/ubuntu/+question/692509 -- 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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1543 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros
[Desktop-packages] [Bug 1855793] Re: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on
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/1855793 Title: Wi-Fi becomes unusally slow all of a sudden and forces me to turn off Wi-Fi and then turn it back on Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Oftentimes, when I am using my PC, the Wi-Fi will drop all of a sudden and I will then be forced to turn the Wi-Fi off and then back on again, which is annoying. And even then, the Wi-Fi becomes unusually slow afterwards. Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 20:35:53 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575941718 Mon 09 Dec 2019 08:35:18 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575939877 Mon 09 Dec 2019 08:04:37 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/2 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: seija 1543 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros
[Desktop-packages] [Bug 1768920] Re: 2 WiFi Icons in the Panel after installation of 18.04
I still have this bug in 20.04. ** Changed in: ubuntu-mate Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1768920 Title: 2 WiFi Icons in the Panel after installation of 18.04 Status in Ubuntu MATE: Confirmed Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Fix Released Bug description: After installing Ubuntu Mate 18.04, on the First login it shows 2 WiFi icons in the top panel. It goes away after the reboot though. My Laptop: Dell XPS 13 9370 Developer Edition, 16 GB RAM and 1 TB SSD Regards, Saurabh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1768920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892669] Re: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen
I can't see any problems in the attached files. Can you please attach a photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1892669 Title: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen Status in Ubuntu: Incomplete Bug description: the favorite bar is in the middle of the screen and blocks the other side of the screen with a repeat of the left side of the screen ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 23:02:25 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-08-20 (3 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=b938a820-f262-48c7-9d2c-30fed7ef6d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.22 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4A dmi.chassis.asset.tag: CNU2262HKV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SQ530UP#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1892669/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892665] Re: gnome-shell occupy much space in my pc
1. Please provide output from 'ps auxw' showing all your processes with their memory usage. 2. Please don't mention any apps in this bug, since it's just about gnome-shell. ** 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/1892665 Title: gnome-shell occupy much space in my pc Status in gnome-shell package in Ubuntu: Incomplete Bug description: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
No problem. It's not up to me anyway... Long term, to get the GUI work done you will need to request enhancements in both of these projects: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues https://gitlab.gnome.org/GNOME/mutter/-/issues Short term, to get the default changed you will need to request an enhancement here: https://gitlab.freedesktop.org/xorg/xserver/-/issues When done, please tell us the new issue IDs. -- 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 OEM Priority Project: New 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. --- 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/oem-priority/+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 1892665] Re: gnome-shell occupy much space in my pc
Also please be careful to avoid measuring virtual address space (the VSZ column in ps) - that is not memory usage. We need to look at the RSS column instead. -- 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/1892665 Title: gnome-shell occupy much space in my pc Status in gnome-shell package in Ubuntu: Incomplete Bug description: when i boot my laptop then suddenly my ram consumption reaches to about 2 gigabytes though there are no any startup apps running in background.when i had a look in system resources then i found that my gnome shell is occupying most of the space then any other resources running .My ram memory consumption reaches to about 7.8 gigabytes when i open some tabs in vivaldi web browser,visual studio code with flutter and dart plugin installed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~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.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 24 09:07:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892667] Re: On-screen-keyboard shows up after touching the screen, ignoring physical keyboard
Please look in: Settings > Universal Access > Typing > Screen Keyboard and verify the option is turned OFF. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: osk -- 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/1892667 Title: On-screen-keyboard shows up after touching the screen, ignoring physical keyboard Status in gnome-shell package in Ubuntu: Incomplete Bug description: after Every time I touch the screen (regardless of where) the minute the focus shifts to a text-entry field the on-screen-keyboard shows up. This should be disabled completely when there is a physical keyboard attached (as in a laptop with a touch screen.) Your attention to this is appreciated. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Aug 23 17:55:48 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-06-10 (74 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I think different from #32. To adding a GUI configure bpc is a long-term plan. Before that,the default behavior should be designed to get the best user experience. As we all know, there're lot of hardware components on the pipline of display path(e.g. socket, converter, dongle, cable, monitor) With any lower quality component on the pipeline, dark screen or function lost is not acceptable. It should be better to provide lower default bpc than dark user's screen. Afterall, user can adjust the bpc by command in short-term or by UI in long-term plan. But if we just dark user's screen, user mostly thinks the hardware is broken or Ubuntu provides poor compatibility(if they compare the same component to Windows). -- 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 OEM Priority Project: New 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. --- 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/oem-priority/+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
